CN114727297A - Network slice management method and device, electronic equipment and readable storage medium - Google Patents

Abstract

The present invention provides a network slice management method, apparatus, electronic device and readable storage medium. The network slice management method includes: acquiring overall demand parameters for network slices, wherein the resources of the network slice are composed of subdomain resources of multiple subdomains; disassembling the overall demand parameters into the multiple subdomains to generate all the Determine the sub-domain resource allocation scheme corresponding to the overall demand parameter; determine the target allocation scheme in the sub-domain resource allocation scheme, wherein the target allocation scheme for each of the sub-domain resources The demand is less than or equal to the sub-domain resources Availability of domain resources; establish a network slice instance according to the target allocation scheme. In the embodiment of the present invention, the convenience of establishing the target allocation scheme is improved, and the utilization rate of the sub-domains is also improved.

Description

Network slice management method, apparatus, electronic device and readable storage medium

technical field

Embodiments of the present invention relate to the field of communications technologies, and in particular, to a network slice management method, apparatus, electronic device, and readable storage medium.

Background technique

Network slicing is a method of separating multiple virtual end-to-end logical private networks on a unified infrastructure as needed. In the related art, when establishing a network slice, it is usually necessary to manually set allocation parameters and then perform allocation, which is relatively inconvenient.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a network slice management method, apparatus, electronic device, and readable storage medium, so as to solve the problem of inconvenience in network slice allocation.

In order to solve the above-mentioned problems, the present invention is realized as follows:

In a first aspect, an embodiment of the present invention provides a network slice management method, the method includes:

Obtaining overall demand parameters for network slices, wherein the resources of the network slices are composed of sub-domain resources of multiple sub-domains;

disassemble the overall demand parameter into the plurality of subdomains, and generate a subdomain resource allocation scheme corresponding to the overall demand parameter;

determining a target allocation scheme in the sub-domain resource allocation scheme, wherein the target allocation scheme has a demand for each of the sub-domain resources less than or equal to the available amount of the sub-domain resources;

Create a network slice instance according to the target allocation scheme.

Optionally, the level of the overall demand parameter includes a first level, a second level, and a third level in which the resource demand increases in sequence, and in the subdomain resource allocation scheme, the resource allocation level of the subdomain resources includes the resource allocation amount. The first grade, the second grade and the third grade in order of increasing;

The disassembling the overall demand parameter into the multiple subdomains, and generating the subdomain resource allocation scheme corresponding to the overall demand parameter, includes:

Allocating the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the first level as the first level;

Allocating the resource allocation level of at least some subdomain resources corresponding to the overall demand parameter of the second level as the first level, and assigning the resource allocation level of at least some subdomain resources as the third level;

Allocate the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the third level as the third level;

At least one sub-domain resource allocation scheme is generated, and the sub-domain resource allocation scheme includes an allocation result of sub-domain resources corresponding to at least one overall demand parameter.

Optionally, the determining the target allocation scheme in the subdomain resource allocation scheme includes:

determining, in the sub-domain allocation scheme, a first allocation scheme in which the demand for each of the sub-domain resources is less than or equal to the available amount of the sub-domain resources;

In the case that the number of the first allocation schemes is more than one, determining the ratio of the demand of each of the first allocation schemes for the sub-domain resources to the available amount of the sub-domain resources;

A first allocation scheme with the smallest ratio of the demand for the sub-domain resources to the available amount of the sub-domain resources is selected as the target allocation scheme.

Optionally, after disassembling the overall demand parameter into the multiple subdomains and generating a subdomain resource allocation scheme corresponding to the overall demand parameter, the method further includes:

determining resource allocation levels for different subdomains in the subdomain resource allocation scheme;

The demand for subdomain resources corresponding to each resource allocation level is determined according to a preset deployment template.

Optionally, the establishing a network slice instance according to the target allocation scheme includes:

establishing a subdomain instance corresponding to the subdomain resource according to the target allocation scheme;

Obtain the instance identifier of the network slice to be established;

According to the description, the sub-instance identification of the sub-domain instance, the instance identification and the scheme identification of the target allocation scheme are bound.

In a second aspect, an embodiment of the present invention provides a network slice management device, including:

an acquisition module, configured to acquire overall demand parameters for the network slice, wherein the resources of the network slice are composed of sub-domain resources of a plurality of sub-domains;

A disassembly module, configured to disassemble the overall demand parameter into the plurality of subdomains, and generate a subdomain resource allocation scheme corresponding to the overall demand parameter;

a determining module, configured to determine a target allocation scheme in the sub-domain resource allocation scheme, wherein the required amount of the target allocation scheme for each of the sub-domain resources is less than or equal to the available amount of the sub-domain resources;

A establishing module is configured to establish a network slice instance according to the target allocation scheme.

Optionally, the level of the overall demand parameter includes a first level, a second level, and a third level in which the resource demand increases in sequence, and in the subdomain resource allocation scheme, the resource allocation level of the subdomain resources includes the resource allocation amount. The first grade, the second grade and the third grade in order of increasing;

The dismantling module includes:

a first allocation submodule, configured to allocate the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the first level as the first level;

Disassembling the sub-module, configured to allocate the resource allocation level of at least some subdomain resources corresponding to the overall demand parameter of the second level as the first level, and assign the resource allocation level of at least some subdomain resources to the third level;

The second allocation submodule is used to allocate the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the third level to the third level;

A generating sub-module is configured to generate at least one sub-domain resource allocation scheme, wherein the sub-domain resource allocation scheme includes an allocation result of sub-domain resources corresponding to at least one overall demand parameter.

Optionally, the determining module includes:

a first determining submodule, configured to determine, in the subdomain allocation scheme, a first allocation scheme in which the demand for each of the subdomain resources is less than or equal to the available amount of the subdomain resources;

A second determination submodule, configured to determine the demand of each of the first allocation schemes for the subdomain resources and the available amount of the subdomain resources when the number of the first allocation schemes is more than one proportion;

A selection sub-module, configured to select a first allocation scheme with the smallest ratio of the demand of the sub-domain resources to the available amount of the sub-domain resources as the target allocation scheme.

Optionally, it further includes: a resource allocation level determination module, configured to determine resource allocation levels for different subdomains in the subdomain resource allocation scheme;

A subdomain resource requirement determination module, configured to determine the subdomain resource requirement corresponding to each resource allocation level according to a preset deployment template.

Optionally, the establishment module includes:

a sub-domain instance establishment submodule, configured to establish a sub-domain instance corresponding to the sub-domain resource according to the target allocation scheme;

The instance identifier acquisition sub-module is used to acquire the instance identifier of the network slice to be established;

A binding sub-module, configured to bind the sub-instance identifier of the sub-domain instance, the instance identifier and the scheme identifier of the target allocation scheme according to the description.

In a third aspect, an embodiment of the present invention further provides a communication device, including: a transceiver, a memory, a processor, and a program stored in the memory and running on the processor; the processor, for Reading the program in the memory implements the steps in the method described in the aforementioned first aspect.

In a fourth aspect, an embodiment of the present invention further provides a readable storage medium for storing a program, and when the program is executed by a processor, the steps in the method described in the foregoing first aspect are implemented.

In the embodiment of the present invention, a sub-domain resource allocation scheme is obtained by disassembling the overall demand parameters for network slices, and the sub-domain resources are selected in the obtained sub-domain resource allocation scheme to meet the target of the demand for the sub-domain resources In the case of an allocation scheme, the network slice is established according to the target allocation scheme, which improves the convenience of establishing the target allocation scheme. At the same time, the sub-domain resource allocation scheme is obtained by disassembling the overall demand parameters of the network slice, which can provide various The optimized sub-domain resource allocation scheme helps to improve the utilization of sub-domains.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative labor.

1 is a schematic flowchart of a network slice management method provided by an embodiment of the present invention;

2 is a schematic structural diagram of a network slice management device provided by the implementation of the present invention;

FIG. 3 is a schematic structural diagram of a communication device provided by the implementation of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

The terms "first", "second" and the like in the embodiments of the present invention are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices. In addition, the use of "and/or" in this application means at least one of the connected objects, such as A and/or B and/or C, means A alone, B alone, C alone, and both A and B are present, Both B and C exist, both A and C exist, and 7 cases where A, B, and C all exist.

With the development of 5G (5th generation mobile networks or 5th generation wireless systems, 5th-Generation, fifth generation mobile communication technology) technology, the application of network slicing becomes possible.

A network slice is an end-to-end logical private network that provides specific network capabilities. A network slice instance is a collection of network functions and required physical/virtual resources, consisting of network slice subnet instances for wireless, transport, and core networks.

Network slicing instances are sharable for services. Generally speaking, service providers can provide different network isolation features for vertical industries based on different dimensions such as network slicing end-to-end, subnets, virtual network elements, virtual resources, and physical resources. Application modes, such as "end-to-end slice sharing", "end-to-end slice sharing", "core network user plane exclusive", etc.

The following describes the network slice management method provided by the embodiment of the present invention.

Referring to FIG. 1, FIG. 1 is a schematic flowchart of a network slice management method provided by an embodiment of the present invention.

In one embodiment, the network slice management method includes:

Step 101: Obtain overall demand parameters for network slicing.

The overall demand parameter may be determined according to the usage requirements of users who need to use the network slicing service.

In this embodiment, the overall demand parameter for the network slice refers to a requirement for the performance of the network slice or the services or resources that can be provided. A network slice can be understood as being composed of three sub-slices of wireless, transmission, and core network, which are referred to as three sub-domains in this embodiment.

Step 102: Disassemble the overall demand parameter into the plurality of subdomains, and generate a subdomain resource allocation scheme corresponding to the overall demand parameter.

After the overall demand parameter is obtained, the overall demand parameter is disassembled and allocated to multiple subdomains corresponding to the network slice.

It should be understood that since a network slice is composed of three sub-domains of radio, transmission and core network, the resources or performance of the network slice are actually provided by the sub-domain resources of these sub-domains. In this embodiment, the allocation is performed according to the overall demand parameter required for the network slicing, so as to determine the resources contributed by each sub-domain resource to the network slicing.

In an optional embodiment, the level of the overall demand parameter includes a first level, a second level, and a third level in which the resource demand increases in sequence. In the subdomain resource allocation scheme, the resource allocation level of the subdomain resources includes resource allocation. The first level, the second level and the third level in increasing order.

In this embodiment, the first level of requirements for network slicing is low level, the second level is medium level, and the third level is high level, and the first level of subdomain resource allocation level is low level, the second level is low level, and the second level is high level. An example is given for the middle level and the third level is the high level.

In this embodiment, if the demand level of network slicing is low, it means that the performance requirements for network slicing are low; if the demand level of network slicing is medium, it means that there are certain requirements for the performance of network slicing, but no need Network slicing has too high performance; if the demand level of network slicing is high, it means that network slicing needs to have higher performance.

Similarly, taking the sub-domain as the transmission example, if the transmission demand level is low, it means that the transmission speed requirements are relatively low; if the transmission demand level is medium, it means that the transmission speed requirements are relatively high, but not required. Too high; if the transmission demand level is high, it means that a higher transmission speed needs to be provided.

The step 102 specifically includes:

Allocating the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the first level as the first level;

Allocating the resource allocation level of at least some subdomain resources corresponding to the overall demand parameter of the second level as the first level, and assigning the resource allocation level of at least some subdomain resources as the third level;

Allocate the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the third level as the third level;

At least one sub-domain resource allocation scheme is generated, and the sub-domain resource allocation scheme includes an allocation result of sub-domain resources corresponding to at least one overall demand parameter.

In this embodiment, if the overall demand parameter of a network slice is the first level, that is, the low level, the network slice has a lower resource requirement. Therefore, the resource allocation levels of the subdomain resources corresponding to the network slice may be equal to each other. The allocation is the first level, that is, the resources of each subdomain are allocated to the low level, so as to save the resources of the subdomain and avoid wasting resources.

If the overall demand parameter of a network slice is the third level, that is, the high level, the network slice has higher requirements for resources. Therefore, it is necessary to assign the resource allocation level of the subdomain resources corresponding to the network slice to the third level. , that is, all sub-domain resources are also allocated to a high level, so as to provide enough sub-domain resources to meet the performance and resource requirements for network slicing.

In this embodiment, if the overall demand parameter of a network slice is the second level, that is, the middle level, the overall demand parameter may be split in different ways to realize the allocation of sub-domain resources.

Exemplarily, the transmission can be set to a medium level, the wireless can be set to a high level, and the core network can be set to a low level; for another example, the transmission can be set to a medium level, the wireless can be set to a low level, and the core network can be set to a low level. high grade. In this way, the demand levels of the radio and the core network are neutralized, so that the level of the overall demand parameter affected by the radio, transmission and core network is neutral.

Step 103: Determine a target allocation scheme in the subdomain resource allocation scheme.

After the sub-domain resource allocation scheme is determined, further, it is necessary to determine whether the sub-domain resource allocation scheme can be applied.

It should be understood that due to the limitation of hardware resources, the resources that may be allocated to the network slice are limited, that is, there may not be enough hardware resources or other resources to support the implementation of the corresponding subdomain resource allocation scheme, Therefore, in this embodiment, it is necessary to further determine whether the subdomain resource allocation scheme can be satisfied. And further take the subdomain resource allocation scheme that can be satisfied as the target allocation scheme.

It can also be understood that the demand for each sub-domain resource in the target allocation scheme is less than or equal to the available amount of the sub-domain resources, so that sufficient sub-domain resources can be provided to implement the sub-domain resource allocation scheme, that is, the target allocation scheme. .

Step 104: Create a network slice instance according to the target allocation scheme.

After the target allocation scheme is determined, a required network slice instance is further established according to the target allocation scheme, and then a network slice that meets the requirements can be obtained.

In the embodiment of the present invention, a sub-domain resource allocation scheme is obtained by disassembling the overall demand parameters for network slices, and the sub-domain resources are selected in the obtained sub-domain resource allocation scheme to meet the target of the demand for the sub-domain resources In the case of an allocation scheme, the network slice is established according to the target allocation scheme, which improves the convenience of establishing the target allocation scheme. At the same time, the sub-domain resource allocation scheme is obtained by disassembling the overall demand parameters of the network slice, which can provide various The optimized sub-domain resource allocation scheme helps to improve the utilization of sub-domains.

In some of these embodiments, the above step 103 specifically includes:

determining, in the sub-domain allocation scheme, a first allocation scheme in which the demand for each of the sub-domain resources is less than or equal to the available amount of the sub-domain resources;

In the case that the number of the first allocation schemes is more than one, determining the ratio of the demand of each of the first allocation schemes for the sub-domain resources to the available amount of the sub-domain resources;

A first allocation scheme with the smallest ratio of the demand for the sub-domain resources to the available amount of the sub-domain resources is selected as the target allocation scheme.

In the obtained sub-domain allocation scheme, if there is only one sub-domain allocation scheme, the demand for sub-domain resources is less than or equal to the available amount of sub-domain resources, that is, only this scheme can be implemented. The subdomain allocation scheme is used as the target allocation scheme, and network slice instances are established according to the scheme.

In the obtained sub-domain allocation schemes, if there are multiple sub-domain allocation schemes, the demand for sub-domain resources is less than or equal to the available amount of sub-domain resources, that is, these schemes are all achievable, and it is necessary to filter out relatively more efficient sub-domain allocation schemes. optimal allocation plan.

In this embodiment, the ratio of the demanded amount of the subdomain resources to the available amount of the subdomain resources is calculated, and the allocation scheme with the smallest ratio is selected as the target allocation scheme.

It should be understood that this ratio actually represents the occupancy of the available subdomain resources. If the obtained ratio is small, it means that the occupancy of the available subdomain resources is small, and the allocation of the subdomain resources is more reasonable.

If the ratio is large, it means that more available subdomain resources are occupied, and the resource allocation may be unreasonable.

During implementation, the ratios of the three sub-domain resources of transmission, wireless and core network can be calculated separately, and the sum of the three sub-domain resources can be calculated for comparison.

Exemplarily, in an embodiment, the first allocation scheme includes two types, the first is that the transmission is set to a medium level, the wireless is set to a high level, the core network is set to a low level, and the second is that the transmission is set to a medium level. , the wireless is set to a low level, and the core network is set to a high level.

Among the available subdomain resources, the radio resources are few, while the core network resources are sufficient. In this case, the ratio between the demanded amount and the available amount of transmission resources in the two schemes is equal; since there are enough core network resources, the ratio between the demanded amount and the available amount of the core network resources in the two schemes is basically the same; One solution needs to occupy more wireless resources because the radio is set to a high level. Therefore, the ratio obtained by the first solution is higher, and the ratio obtained by the second solution is relatively lower.

It can be understood that if the first solution is selected, it will occupy more available wireless resources that are not originally available. If the second solution is selected, it will occupy more available core network resources, and the available core network resources are sufficient. Therefore, the resource allocation is more reasonable and the impact on the overall performance is relatively small.

In some of these embodiments, after step 102, the method further includes:

determining resource allocation levels for different subdomains in the subdomain resource allocation scheme;

The demand for subdomain resources corresponding to each resource allocation level is determined according to a preset deployment template.

In this embodiment, the deployment template is used to quantify the corresponding sub-domain resources according to the resource allocation level to obtain the specific demand of the sub-domain resources. For example, during implementation, the number of corresponding base stations and frequency bands may be determined according to the wireless level.

In some of these embodiments, the establishing a network slice instance according to the target allocation scheme includes:

establishing a subdomain instance corresponding to the subdomain resource according to the target allocation scheme;

Obtain the instance identifier of the network slice to be established;

According to the description, the sub-instance identification of the sub-domain instance, the instance identification and the scheme identification of the target allocation scheme are bound.

It should be understood that since each network slice instance is actually composed of its corresponding sub-domain sub-instances, in other words, each network slice instance is composed of the wireless sub-instances, transmission sub-instances and core network sub-instances it includes. Instances form together.

In this embodiment, after the target allocation scheme is determined, corresponding sub-domain instances, that is, the above-mentioned wireless sub-instance, transmission sub-instance, and core network sub-instance, are respectively established according to the scheme. Further, the sub-instance identifiers of these sub-domain instances, the instance identifiers of the network slices to be established, and the scheme identifiers of the target allocation scheme are bound to establish the corresponding relationship between the target allocation scheme, the sub-domain instances and the network slice instances. , to complete the establishment of the network slice instance.

The various optional implementation manners introduced in the embodiments of the present invention may be implemented in combination with each other under the condition that they do not conflict with each other, or may be implemented independently, which are not limited by the embodiments of the present invention.

For ease of understanding, an example is described below:

S1: CSMF (Communication Service Management Function, communication service management end) sends and determines the establishment requirements of end-to-end network slicing (hereinafter referred to as network slicing), for example, to obtain the user requirements of a user for network slicing, and use the requirements. To the service provisioning request to NSMF (Network Slice Management Function, network slice management end).

S2: NSMF converts the above-mentioned user requirements or establishment requirements into the overall requirement parameters of the network slice. At this time, a corresponding network slice instance identifier may be further generated.

S3: NSMF disassembles the overall demand parameters that can be split into wireless, transmission, and core network sub-domains according to the level of the overall demand parameters. When splitting the overall demand parameters of medium-level network slices, based on the high, The allocation of low-level subnet requirements and the generation of multiple allocation schemes, generate multiple sub-domain resource allocation schemes. Further, a scheme identifier corresponding to each subdomain resource allocation scheme may also be generated.

Exemplarily, a certain network slicing requirement includes parameter 1, parameter 2, and parameter 3, and the levels of these three parameters are high, medium, and low, respectively. In this way, parameter 2 can be divided into parameters. When NSMF splits parameter 2, it can fix the transmission subnet demand as medium, and define the wireless and core network subnet requirements as high and low levels to neutralize the demand levels to form two parameter split schemes, as follows: shown in Table 1 and Table 2.

Table 1: The first split method scheme

parameter wireless transmission Core Network 1 high high high 2 high middle Low 3 Low Low Low Internet resources reAn1 reTn reCn1

Table 2: The second split method scheme

S4: The NSMF distributes the subnet requirements under different allocation schemes to each NSSMF (Network Slice Subnet Management Function, network slice subnet management terminal), carrying the scheme identifier and the network slice instance identifier.

Here, the NSSMF specifically includes NSSMFs corresponding to the three sub-domains of wireless, transmission and core network respectively.

S5: Each subdomain NSSMF receives the subnet requirements under different allocation schemes, matches the deployment template NSST (NetworkSlice Subnet Template, network slice subnet template), and records the subnet requirements and deployment template NSST under different schemes.

S6: Each sub-domain NSSMF sends resource requirements to the RMS (Resource Management System, resource management system), and the RMS queries whether the network resources corresponding to the network slicing sub-network requirements of the professional domain under each allocation scheme are satisfied.

Exemplarily, the wireless subnet requirements in parameter allocation scheme 1 (parameter 1 is high, parameter 2 is high, parameter 3 is low) corresponds to network resources specifically that reAn1 is m base stations, and n frequency bands are exclusively shared; Transmission subnet requirements (parameter 1 is high, parameter 2 is medium, parameter 3 is low), the corresponding resource reTn is a shared FlexE (a transmission method) hard pipe; the core network subnet requirements in parameter allocation scheme 1 (parameter 1 is high, parameter 2 is high) Low, parameter 3 is low) The corresponding resource reCn1 is the network element of the shared core network.

The wireless subnet requirements in parameter allocation scheme 2 (parameter 1 is high, parameter 2 is low, parameter 3 is low) corresponds to the network resources specifically reAn2 is n base stations, and m frequency bands are exclusively shared; the transmission subnet requirements in parameter allocation scheme 2 (parameter 1 high, parameter 2 medium, parameter 3 low) the corresponding resource reTn is the shared FlexE hard pipe; the core network subnet requirements in parameter allocation scheme 2 (parameter 1 high, parameter 2 high, parameter 3 low) corresponding resource reCn2 is Shared core network control plane NEs and exclusive user plane NEs.

The NSSMF sends Scheme 1 (reAn1, reTn, reCn1), Scheme 2 (reAn2, reTn, reCn2) to the RMS.

S7: RMS returns the resource satisfaction result of each allocation scheme to NSSMF, and returns the proportion of network resources corresponding to the network slicing subnet requirements of the professional domain to the remaining network resources of the professional domain for the allocation scheme that meets the resource requirements.

Here, the allocation scheme that satisfies the resources is the first allocation scheme in the foregoing network slice management method.

S8: Each sub-domain NSSMF returns the resource satisfaction result of each allocation scheme to NSMF, and returns the proportion of the network resources corresponding to the network slicing subnet requirements of the professional domain to the remaining network resources of the professional domain for the allocation scheme that satisfies the resources.

Exemplarily, the network resources required for parameter allocation schemes 1 and 2 in S7 and S8 are all satisfied, and the proportion of the returned subdomain required resources is as follows:

The wireless NSSMF returns that the ratio of the resources corresponding to the wireless subnet requirements in Scheme 1 to the total remaining wireless resources is reAn1/reAnAll; the ratio of the resources corresponding to the wireless subnet requirements in Scheme 2 to the total remaining wireless resources is reAn2/reAnAll.

Transmission NSSMF returns the ratio of the resources corresponding to the transmission subnet requirements in Scheme 1 to the total remaining transmission resources as reTn/reTnAll; the ratio of the resources corresponding to the transmission subnet requirements in Scheme 2 to the total remaining transmission resources is reTn/reTnAll.

The core network NSSMF returns the ratio of the resources corresponding to the subnet requirements of the core network in Scheme 1 to the total remaining resources of the core network as reCn1/reACnAll; the ratio of the resources corresponding to the subnet requirements of the core network in Scheme 2 to the total remaining resources of the core network is reCn2/reACnAll.

S9: NSMF summarizes the resource satisfaction status of each subdomain under each scheme, and for parameter allocation schemes that satisfy the network resources of the three subdomains, by comparing the proportion of network resources corresponding to the sub-network requirements of each network slice under each scheme to the remaining total resources of the professional domain The average value (that is, the average end-to-end network slice resource ratio) determines which parameter allocation scheme is used to activate services.

Exemplarily, the average share of end-to-end network slice resources in Scheme 1 is:

p1=(reAn1/reAnAll+reTn/reTnAll+reCn1/reCnAll)/3;

The average proportion of end-to-end network slice resources in Scheme 2 is:

p2=(reAn2/reAnAll+reTn/reTnAll+reCn2/reCnAll)/3;

Compare the average end-to-end network slice resource ratios p1 and p2 of parameter allocation schemes 1 and 2, and select a parameter allocation scheme with a smaller end-to-end network resource ratio.

S10: The NSMF notifies the NSSMF to generate a subnet instance, which carries the instance identifier of the network slice and the provisioning scheme identifier, and the scheme is the scheme identifier corresponding to the above target allocation scheme.

If there is no parameter allocation scheme that satisfies all three subdomains, it is confirmed that the establishment of the network slice fails.

S11: Match each sub-domain NSSMF with the saved sub-domain resource allocation scheme, arrange the subnet instances according to the corresponding subnet requirements and matching templates, generate network slicing subnet maintenance management information and network slicing subnet instance identifiers, and Bind the ID to the network slice instance ID.

S12: NSSMF passes the virtualized network slice subnet management requirements to MANO (virtualized resource and orchestration function).

S13: MANO allocates virtualized resources, generates network slice subnet resource instances, and configures the resource instances.

S14: MANO notifies NSSMF of the virtualized network resource instance generation result.

S15: The NSSMF notifies the NSMF of the network slice subnet instance generation result, and carries the network slice subnet instance identifier.

S16: The NSMF binds the network slice instance identifier and the network slice subnet instance identifier.

S17: Perform network slicing configuration, including necessary configurations such as network connectivity configuration.

S18: The NSMF returns that the CSMF network slice is successfully established, and returns the network slice instance identifier.

Referring to FIG. 2, FIG. 2 is a structural diagram of a network slice management apparatus provided by an embodiment of the present invention. As shown in FIG. 3, the network slice management apparatus 200 includes:

an obtaining module 201, configured to obtain overall demand parameters for the network slice, wherein the resources of the network slice are composed of sub-domain resources of a plurality of sub-domains;

A disassembly module 202, configured to disassemble the overall demand parameter into the plurality of subdomains, and generate a subdomain resource allocation scheme corresponding to the overall demand parameter;

A determination module 203, configured to determine a target allocation scheme in the sub-domain resource allocation scheme, wherein the target allocation scheme has a demand for each of the sub-domain resources less than or equal to the available amount of the sub-domain resources;

The establishing module 204 is configured to establish a network slice instance according to the target allocation scheme.

Optionally, the level of the overall demand parameter includes a first level, a second level, and a third level in which the resource demand increases in sequence, and in the subdomain resource allocation scheme, the resource allocation level of the subdomain resources includes the resource allocation amount. The first grade, the second grade and the third grade in order of increasing;

The dismantling module 202 includes:

a first allocation submodule, configured to allocate the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the first level as the first level;

Disassembling the sub-module, configured to allocate the resource allocation level of at least some subdomain resources corresponding to the overall demand parameter of the second level as the first level, and assign the resource allocation level of at least some subdomain resources to the third level;

The second allocation submodule is used to allocate the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the third level to the third level;

A generating sub-module is configured to generate at least one sub-domain resource allocation scheme, wherein the sub-domain resource allocation scheme includes an allocation result of sub-domain resources corresponding to at least one overall demand parameter.

Optionally, the determining module 203 includes:

a first determining submodule, configured to determine, in the subdomain allocation scheme, a first allocation scheme in which the demand for each of the subdomain resources is less than or equal to the available amount of the subdomain resources;

A second determination submodule, configured to determine the demand of each of the first allocation schemes for the subdomain resources and the available amount of the subdomain resources when the number of the first allocation schemes is more than one proportion;

A selection sub-module, configured to select a first allocation scheme with the smallest ratio of the demand of the sub-domain resources to the available amount of the sub-domain resources as the target allocation scheme.

Optionally, it further includes: a resource allocation level determination module, configured to determine resource allocation levels for different subdomains in the subdomain resource allocation scheme;

A subdomain resource requirement determination module, configured to determine the subdomain resource requirement corresponding to each resource allocation level according to a preset deployment template.

Optionally, the establishing module 204 includes:

a sub-domain instance establishment submodule, configured to establish a sub-domain instance corresponding to the sub-domain resource according to the target allocation scheme;

The instance identifier acquisition sub-module is used to acquire the instance identifier of the network slice to be established;

A binding sub-module, configured to bind the sub-instance identifier of the sub-domain instance, the instance identifier and the scheme identifier of the target allocation scheme according to the description.

The network slice management apparatus 200 can implement each process of the method embodiment in FIG. 1 in the embodiment of the present invention, and achieve the same beneficial effect. To avoid repetition, details are not described here.

The embodiment of the present invention also provides a communication device. Referring to FIG. 3 , the communication device may include a processor 301 , a memory 302 , and a program 3021 stored on the memory 302 and executable on the processor 301 .

In the case where the communication device is a terminal, when the program 3021 is executed by the processor 301, any steps in the method embodiment corresponding to FIG. 1 can be implemented and the same beneficial effects can be achieved, which will not be repeated here.

When the communication device is a network-side device, when the program 3021 is executed by the processor 301, any steps in the method embodiment corresponding to FIG. 3 can be implemented and the same beneficial effects can be achieved, which will not be repeated here.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the methods of the above embodiments can be completed by program instructions related to hardware, and the program can be stored in a readable medium. An embodiment of the present invention further provides a readable storage medium, where a computer program is stored on the readable storage medium, and when the computer program is executed by a processor, any step in the method embodiment corresponding to FIG. 1 can be implemented, and The same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.

The storage medium is, for example, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.

The above are preferred implementations of the embodiments of the present invention. It should be pointed out that for those skilled in the art, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and Retouching should also be regarded as the protection scope of the present invention.

Claims (12)

1. A network slice management method, wherein the method comprises: Obtaining overall demand parameters for network slices, wherein the resources of the network slices are composed of sub-domain resources of multiple sub-domains; disassemble the overall demand parameter into the plurality of subdomains, and generate a subdomain resource allocation scheme corresponding to the overall demand parameter; determining a target allocation scheme in the sub-domain resource allocation scheme, wherein the target allocation scheme has a demand for each of the sub-domain resources less than or equal to the available amount of the sub-domain resources; Create a network slice instance according to the target allocation scheme. 2. The method according to claim 1, wherein the level of the overall demand parameter comprises a first level, a second level, and a third level in which the resource demand increases in sequence, and in the sub-domain resource allocation scheme, The resource allocation levels of the sub-domain resources include the first level, the second level and the third level in which the resource allocation amount increases in sequence; The disassembling the overall demand parameter into the multiple subdomains, and generating the subdomain resource allocation scheme corresponding to the overall demand parameter, includes: Allocating the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the first level as the first level; Allocating the resource allocation level of at least some subdomain resources corresponding to the overall demand parameter of the second level as the first level, and assigning the resource allocation level of at least some subdomain resources as the third level; Allocate the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the third level as the third level; At least one sub-domain resource allocation scheme is generated, and the sub-domain resource allocation scheme includes an allocation result of sub-domain resources corresponding to at least one overall demand parameter. 3. The method according to claim 1 or 2, wherein the determining the target allocation scheme in the subdomain resource allocation scheme comprises: determining, in the sub-domain allocation scheme, a first allocation scheme in which the demand for each of the sub-domain resources is less than or equal to the available amount of the sub-domain resources; In the case that the number of the first allocation schemes is more than one, determining the ratio of the demand of each of the first allocation schemes for the sub-domain resources to the available amount of the sub-domain resources; A first allocation scheme with the smallest ratio of the demand for the sub-domain resources to the available amount of the sub-domain resources is selected as the target allocation scheme. 4. The method according to claim 2, wherein after disassembling the overall demand parameter into the plurality of subdomains and generating a subdomain resource allocation scheme corresponding to the overall demand parameter, the method Also includes: determining resource allocation levels for different subdomains in the subdomain resource allocation scheme; The demand for subdomain resources corresponding to each resource allocation level is determined according to a preset deployment template. 5. The method according to claim 1, wherein the establishing a network slice instance according to the target allocation scheme comprises: establishing a subdomain instance corresponding to the subdomain resource according to the target allocation scheme; Obtain the instance identifier of the network slice to be established; According to the description, the sub-instance identification of the sub-domain instance, the instance identification and the scheme identification of the target allocation scheme are bound. 6. A network slice management device, comprising: an acquisition module, configured to acquire overall demand parameters for the network slice, wherein the resources of the network slice are composed of sub-domain resources of a plurality of sub-domains; A disassembly module, configured to disassemble the overall demand parameter into the plurality of subdomains, and generate a subdomain resource allocation scheme corresponding to the overall demand parameter; a determining module, configured to determine a target allocation scheme in the sub-domain resource allocation scheme, wherein the required amount of the target allocation scheme for each of the sub-domain resources is less than or equal to the available amount of the sub-domain resources; A establishing module is configured to establish a network slice instance according to the target allocation scheme. 7. The apparatus according to claim 6, wherein the level of the overall demand parameter comprises a first level, a second level and a third level in which the resource demand increases in sequence, and in the sub-domain resource allocation scheme, The resource allocation levels of the sub-domain resources include the first level, the second level and the third level in which the resource allocation amount increases in sequence; The dismantling module includes: a first allocation submodule, configured to allocate the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the first level as the first level; Disassembling the sub-module, configured to allocate the resource allocation level of at least some subdomain resources corresponding to the overall demand parameter of the second level as the first level, and assign the resource allocation level of at least some subdomain resources to the third level; The second allocation submodule is used to allocate the resource allocation levels of the subdomain resources corresponding to the overall demand parameters of the third level to the third level; A generating sub-module is configured to generate at least one sub-domain resource allocation scheme, wherein the sub-domain resource allocation scheme includes an allocation result of sub-domain resources corresponding to at least one overall demand parameter. 8. The apparatus according to claim 6 or 7, wherein the determining module comprises: a first determining submodule, configured to determine, in the subdomain allocation scheme, a first allocation scheme in which the demand for each of the subdomain resources is less than or equal to the available amount of the subdomain resources; A second determination submodule, configured to determine the demand of each of the first allocation schemes for the subdomain resources and the available amount of the subdomain resources when the number of the first allocation schemes is more than one proportion; A selection sub-module, configured to select a first allocation scheme with the smallest ratio of the demand of the sub-domain resources to the available amount of the sub-domain resources as the target allocation scheme. 9. The apparatus of claim 7, further comprising: a resource allocation level determination module, configured to determine resource allocation levels for different subdomains in the subdomain resource allocation scheme; A subdomain resource requirement determination module, configured to determine the subdomain resource requirement corresponding to each resource allocation level according to a preset deployment template. 10. The apparatus according to claim 6, wherein the establishing module comprises: a sub-domain instance establishment submodule, configured to establish a sub-domain instance corresponding to the sub-domain resource according to the target allocation scheme; The instance identifier acquisition sub-module is used to acquire the instance identifier of the network slice to be established; A binding sub-module, configured to bind the sub-instance identifier of the sub-domain instance, the instance identifier and the scheme identifier of the target allocation scheme according to the description. 11. An electronic device, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; characterized in that, the processor is configured to read the memory in the memory The program implements the steps in the network slice management method according to any one of claims 1 to 5. 12. A readable storage medium for storing a program, wherein when the program is executed by a processor, the steps in the network slice management method according to any one of claims 1 to 5 are implemented.

Images