WO2021115438A1

WO2021115438A1 - Network slice capacity setting method, control method, apparatus and device, and medium

Info

Publication number: WO2021115438A1
Application number: PCT/CN2020/135800
Authority: WO
Inventors: 周俊超; 蔡建楠
Original assignee: 中兴通讯股份有限公司
Priority date: 2019-12-13
Filing date: 2020-12-11
Publication date: 2021-06-17
Also published as: CN112968788A

Abstract

Provided are a network slice capacity setting method, a control method, apparatus and device, and a medium. The network slice capacity setting method comprises: acquiring a slice capacity parameter, wherein the slice capacity parameter comprises a capacity requirement of a network slice or a service level protocol parameter; determining, according to the slice capacity parameter, a network slice capacity threshold value respectively corresponding to at least one slice instance which provides a service for the network slice; and sending a network slice capacity setting instruction to each slice instance, wherein the setting instruction comprises the network slice capacity threshold value corresponding to each slice instance.

Description

Network slice capacity setting method, control method, device, equipment and medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office with an application number of 201911284846.1 on December 13, 2019. The entire content of this application is incorporated into this application by reference.

Technical field

This application relates to a wireless communication network, for example, to a network slice capacity setting method, control method, device, device, and medium.

Background technique

Network slicing is a new type of communication network service technology and architecture defined based on Network Function Virtualization (NFV) and Software Defined Network (SDN) technologies. It builds an end-to-end communication network service technology based on virtual or physical resources. An isolated logical communication network at the end provides users with at least one specific communication network service on demand. Under this architecture, a user (terminal) can be allocated to multiple network slices of an operator at the same time. Because there are a large number of users, slice instances, and network functions (NF) in the network, and the physical resources on the network nodes are limited, the network slice capacity is limited. Currently, there is no effective mechanism to control the network slice capacity. If online users Excessive number or number of sessions can cause network slice capacity overload, unstable business services, and even service interruptions for online users.

Summary of the invention

This application provides a network slicing capacity setting method, control method, device, equipment, and medium to improve the controllability and service stability of the network slicing capacity.

The embodiment of the application provides a method for setting network slicing capacity, which is applied to network slicing management network elements, including:

Acquiring a slice capacity parameter, where the slice capacity parameter includes a capacity requirement of a network slice or a service level agreement (Service Levle Agreement, SLA) parameter;

Determine, according to the slice capacity parameter, a network slice capacity threshold corresponding to at least one slice instance that provides services for the network slice;

Send a network slice capacity setting instruction to each slice instance, where the setting instruction includes a network slice capacity threshold corresponding to each slice instance.

The embodiment of the present application also provides a network slice capacity control method, which is applied to a core network element, and includes:

Receiving a setting instruction for a network slice capacity, where the setting instruction includes a network slice capacity threshold of the current slice instance;

Setting the network slice capacity threshold of the current slice instance according to the setting instruction;

The network slice capacity provided to the user is controlled according to the network slice capacity threshold.

The embodiment of the present application also provides a device for setting network slicing capacity, including:

An obtaining module, configured to obtain slice capacity parameters, where the slice capacity parameters include network slice capacity requirements or service level agreement parameters;

A threshold determination module, configured to determine, according to the slice capacity parameter, a network slice capacity threshold corresponding to at least one slice instance that provides services for the network slice;

The instruction sending module is configured to send a network slice capacity setting instruction to each slice instance, where the setting instruction includes a network slice capacity threshold corresponding to each slice instance.

The embodiment of the present application also provides a network slicing capacity control device, including:

An instruction receiving module, configured to receive a setting instruction of the network slice capacity, the setting instruction including the network slice capacity threshold of the current slice instance;

A threshold setting module, configured to set the network slice capacity threshold of the current slice instance according to the setting instruction;

The capacity control module is configured to control the network slice capacity provided to the user according to the network slice capacity threshold.

An embodiment of the present application also provides a device, including:

At least one processor;

The storage device is set to store at least one program;

When the at least one program is executed by the at least one processor, the at least one processor implements the network slice capacity setting method or the network slice capacity control method described above.

The embodiments of the present application also provide a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned network slice capacity setting method or network slice capacity control method is implemented.

Description of the drawings

FIG. 1 is a flowchart of a method for setting network slicing capacity according to an embodiment;

FIG. 2 is a flowchart of a method for controlling network slicing capacity according to an embodiment;

FIG. 3 is a flow chart of the S-NSSAI-based network slicing capacity control process provided by an embodiment;

FIG. 4 is a schematic diagram of a flow of a network slice capacity threshold setting end provided by an embodiment;

FIG. 5 is a schematic diagram of a flow of a network slicing capacity control terminal provided by an embodiment;

FIG. 6 is a schematic structural diagram of a device for setting network slicing capacity according to an embodiment;

FIG. 7 is a schematic structural diagram of a network slicing capacity control device provided by an embodiment;

FIG. 8 is a schematic diagram of the hardware structure of a device provided by an embodiment.

Detailed ways

The 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) standard defines that the core network slicing subnet consists of multiple 5th Generation Core Network Function (5GC NF), such as: access and Mobility Management Function (Access and Mobility Management Function, AMF), Session Management Function (SMF), User Plane Function (UPF), Unified Data Management (UDM), Unified Data Storage ( Unified Data Repository (UDR), Network Slice Selection Function (NSSF), etc. The NF example described in the embodiments of this application is the core network element. The network slice capacity control is also the control of the sub-slice capacity of the core network element. For the capacity control of other sub-slices, reference may be made to the various embodiments. The described network slicing capacity control method.

Fig. 1 is a flowchart of a method for setting network slicing capacity according to an embodiment. The method in this embodiment can be applied to network slicing management network elements. As shown in Figure 1, the method provided in this embodiment includes steps 110-130.

In step 110, a slice capacity parameter is obtained, where the slice capacity parameter includes a capacity requirement of a network slice or a service level agreement parameter.

In step 120, a network slice capacity threshold corresponding to at least one slice instance that provides services for the network slice is determined according to the slice capacity parameter.

In step 130, a network slice capacity setting instruction is sent to each slice instance, where the setting instruction includes a network slice capacity threshold corresponding to each slice instance.

In this embodiment, the network slice management network element refers to the network slice management system (NSMS), including the communication service management function (Communication Service Management Function, CSMF) defined by 3GPP, and the network slice management function (Network Slice Management) Function, NSMF) and Network Slice Subnet Management Function (NSSMF). By adding a logical module or component that decomposes or maps the capacity requirements of the network slice or SLA parameters in the NSMS, the logical module or component is set to decompose or map the slice capacity parameters to at least one slice instance that provides services for the network slice In this way, the network slice capacity requirement from the customer is converted into the capacity requirement for the NF instance in the network slice; by sending a setting instruction to the slice instance, the slice instance is notified to set its corresponding network slice capacity threshold, so that the slice instance is based on the network slice. The slice capacity threshold efficiently manages online users and sessions, and establishes a complete network slice capacity setting mechanism, thereby improving the controllability of network slice capacity and service stability.

In an embodiment, the network slice capacity threshold includes: the maximum number of static users, the maximum number of online dynamic users, and the maximum number of online dynamic sessions.

When an operator provides network slicing, the capacity of the network slicing is limited in the SLA parameters, such as the maximum number of static users supported by the network slicing instance, the maximum number of online dynamic users, or the number of sessions. In this embodiment, the network slice is decomposed into at least one slice instance according to the capacity requirements of the network slice or preset SLA parameters, and the network slice capacity threshold of each slice instance is determined. The network slice capacity threshold includes three items: the maximum number of static users , The maximum number of online dynamic users and the maximum number of online dynamic sessions. Among them, the maximum number of static users can be managed and maintained through NF instances such as UDM or UDR, and the maximum number of online dynamic users or sessions can be maintained through NF instances such as AMF, SMF or UPF. .

In this embodiment, the network slice is marked with Single Network Slice Select Assistant Information (S-NSSAI), and the control of the network slice capacity is the maximum number of static users and the maximum number of online users based on S-NSSAI. Control of the number of dynamic users or the number of sessions.

For example, in step 110, the slice capacity parameter is obtained. For a network slice (for example, S-NSSAI = 011A0B01), the NSMS receives the user's capacity demand or obtains the SLA parameter indicating that the slice capacity parameter of the network slice is:

NSSAI＝011A0B01

{

Maximum number of static users = 1 million;

Maximum number of online dynamic users = 100,000;

Maximum number of online dynamic sessions = 300,000;

}

In step 120, a network slice capacity threshold corresponding to a slice instance that provides services for the network slice is determined, where there is at least one slice instance. In this process, the NSMS decomposes or maps the slice capacity parameter of the network slice to at least one slice instance corresponding to the S-NSSAI, which can be decomposed to at least one NF instance in the slice instance. For example, S-NSSAI = 011A0B01 corresponds to slice instance 1 and slice instance 2, and the maximum number of static users can be decomposed into:

Slicing example 1, in the case of S-NSSAI = 011A0B01, the maximum number of static users is, for example, 300,000, which is managed by UDM or UDR;

Slicing instance 2, in the case of S-NSSAI = 011A0B01, the maximum number of static users is, for example, 700,000, which is managed by UDM or UDR;

On this basis, slice instance 1 can control the number of static users in it to be less than or equal to 300,000, and slice instance 2 can control the number of static users in it to be less than or equal to 700,000, so as to ensure the stability of the service.

In some embodiments, slice instance 1 and slice instance 2 may share UDM or UDR, then for the maximum number of static users, directly mapped to the shared UDM or UDR. The maximum number of static users in the case of S-NSSAI = 011A0B01 is 100. Ten thousand is enough.

For the maximum number of online dynamic users, it can be broken down into:

Slicing example 1, in the case of S-NSSAI = 011A0B01, the maximum number of online dynamic users is, for example, 30,000, which is managed by AMF, SMF, or UPF;

Slicing instance 2, in the case of S-NSSAI = 011A0B01, the maximum number of online dynamic users is, for example, 70,000, which is managed by AMF, SMF or UPF;

On this basis, slice instance 1 can control the number of online dynamic users in it to be less than or equal to 30,000, and slice instance 2 can control the number of online dynamic users in it to be less than or equal to 70,000, so as to ensure the stability of the service.

For the maximum number of online dynamic sessions, it can be broken down into:

Slicing example 1, in the case of S-NSSAI = 011A0B01, the maximum number of online dynamic sessions (for example, 90,000), managed by AMF, SMF or UPF;

Slicing instance 2, in the case of S-NSSAI = 011A0B01, the maximum number of online dynamic sessions (for example, 210,000) is managed by AMF, SMF or UPF;

On this basis, slice instance 1 can control the number of online dynamic sessions in it to be less than or equal to 90,000, and slice instance 2 can control the number of online dynamic sessions in it to be less than or equal to 210,000, thereby ensuring the stability of the service.

In step 130, the NSMS can determine the network slice capacity threshold corresponding to at least one slice instance or NF instance according to the above-mentioned decomposition situation, and issue a setting instruction to each slice instance through the element management system (EMS). NF instance, so as to realize the setting of S-NSSAI-based network slice capacity threshold for each slice instance. E.g:

The maximum number of static users of the UDM or UDR shared by slice instance 1 and slice instance 2 is set to 1 million when S-NSSAI = 011A0B01;

Slicing example 1, the maximum number of online users of AMF, SMF or UPF in the case of S-NSSAI = 011A0B01 is set to 30,000;

Slicing example 2, the maximum number of online users of AMF, SMF or UPF in the case of S-NSSAI = 011A0B01 is set to 70,000;

Slicing example 1, the maximum number of online dynamic sessions of AMF, SMF or UPF in the case of S-NSSAI = 011A0B01 is set to 90,000;

Slicing instance 2, the maximum number of online dynamic sessions of AMF, SMF or UPF in the case of S-NSSAI = 011A0B01 is set to 210,000;

It should be noted that the setting command sent to slice instance 1 only needs to carry the network slice capacity threshold corresponding to slice instance 1; the setting command sent to slice instance 2 only needs to carry the network slice capacity threshold corresponding to slice instance 2. Individuals are independent of each other, set up and controlled separately.

In an embodiment, the network slice capacity setting method further includes: receiving setting failure information returned by a target slice instance, the target slice instance being a slice instance whose corresponding network slice capacity threshold is greater than the remaining capacity supported by the current slice instance; Adjust the network slice capacity threshold corresponding to the target slice instance according to the setting failure information.

In this embodiment, the NSMS also receives the setup failure information returned by the target slice instance, and can retrieve the slice capacity parameters or obtain the processing instructions (such as expansion instructions) from the user or the Operation Support Systems (OSS) accordingly. Adjust the network slice capacity threshold corresponding to the target slice instance and resend the setting instruction. The remaining capacity refers to the network slice capacity that can be supported by the current slice instance, excluding the network slice capacity allocated to other S-NSSAIs. For the target slice instance, the maximum supported capacity is given in the license. For example, for the AMF in the target slice instance, one item of the maximum capacity supported by all S-NSSAIs is given as the maximum online dynamic The number of sessions is 200,000. If the maximum number of online dynamic sessions has not been allocated to other S-NSSAIs, the maximum number of online dynamic sessions with remaining capacity is 200,000. In this case, for the current S-NSSAI, if it is decomposed to the target slice instance The maximum number of online dynamic sessions in the network slice capacity threshold is 210,000, which is greater than the remaining capacity supported by the slice instance, and the target slice instance will feed back the setting failure instruction to the NSMS; for another example, for the AMF in the target slice instance, for other S -NSSAI has allocated a certain maximum number of online dynamic sessions, assuming that the maximum number of online dynamic sessions of the remaining capacity is 100,000, and for the current S-NSSAI has allocated a maximum number of online dynamic sessions of 120,000, which is greater than the maximum number of online dynamic sessions of the remaining capacity Number of dynamic sessions (It can also be understood that after the maximum number of online dynamic sessions set for the current S-NSSAI is added, the maximum number of online dynamic sessions set for all S-NSSAIs is greater than the maximum number of online dynamic sessions specified in the license. Dynamic sessions), refuse to set the network slice capacity threshold of the current NF instance, and feed back the setting failure instruction to the NSMS. The NSMS can re-acquire the slice capacity parameters according to the setting failure information, or adjust the network slice capacity threshold corresponding to the target slice instance and resend the setting instruction.

Fig. 2 is a flowchart of a method for controlling network slice capacity according to an embodiment. The method in this embodiment can be applied to core network elements, such as AMF, UDF, and so on. As shown in Figure 2, the method provided in this embodiment includes steps 210-230.

In step 210, a network slice capacity setting instruction is received, where the setting instruction includes a network slice capacity threshold of the current slice instance.

In step 220, the network slice capacity threshold of the current slice instance is set according to the setting instruction.

In step 230, the network slice capacity provided to the user is controlled according to the network slice capacity threshold.

In this embodiment, an S-NSSAI-based capacity control logic module or component is added to the slice instance, and the S-NSSAI-based capacity control logic module or component is set to implement S-NSSAI-based capacity control and license for the slice instance. Conflict management in capacity. After the slice instance receives the setting instructions sent by the NSMS through the EMS, it sets the network slice capacity threshold of the current slice instance according to the setting instructions, controls the network slice capacity provided to users accordingly, and efficiently manages online users and sessions, and establishes a complete Network slicing capacity control mechanism to improve the controllability of network slicing capacity and service stability. Among them, the slice instance can be a 5GC NF instance. For example, the maximum number of static users can be controlled by NF instances such as UDM or UDR, and the maximum number of online dynamic users or sessions can be controlled by NF instances such as AMF, SMF, or UPF.

In an embodiment, the setting instruction received by one slice instance may only include its corresponding network slice capacity threshold, and does not need to include the network slice capacity threshold under other slice instances (or other S-NSSAI). A slice instance independently sets its own network slice capacity threshold and independently controls its own network slice capacity.

In an embodiment, the controlling the network slice capacity provided to the user according to the network slice capacity threshold includes: after the network slice capacity provided to the user is greater than the network slice capacity threshold, rejecting and requesting access to the user Sign up, or refuse to have a session with the user requesting access.

In this embodiment, when the network slice capacity provided to the user is greater than the set network slice capacity threshold, the user is refused to sign a contract with the user requesting access, or is refused to have a session with the user requesting access, so as to ensure that the network slice is not Will be overloaded to ensure service stability.

Fig. 3 is a flowchart of an S-NSSAI-based network slice capacity control process provided by an embodiment. As shown in Figure 3:

In step 201, a network slice capacity setting instruction is received, where the setting instruction includes the network slice capacity threshold of the current slice instance.

In this step, the slice instance receives an S-NSSAI-based capacity threshold setting instruction from the EMS, and the slice instance may be a 5GC NF instance (for example, AMF, SMF, or UPF).

In step 202, the network slice capacity threshold of the current slice instance is set according to the setting instruction.

In this step, the 5GC NF instance sets the network slice capacity threshold supported by the S-NSSAI. For example, if AMF, SMF or UPF is set to S-NSSAI = 011A0B01, the maximum number of online dynamic sessions is 9 Ten thousand; set UDM or UDR in the case of S-NSSAI = 011A0B01, the maximum number of static users is 300,000, etc.

In step 203, is it calculated in real time whether the actual network slice capacity provided to the user is greater than the network slice capacity threshold or the given value of the license? In the case that the actual network slice capacity provided to the user is greater than the network slice capacity threshold or the given value of the license, step 204 is executed. When the actual network slice capacity provided to the user is less than or equal to the network slice capacity threshold and less than or equal to In the case of a given value of License, step 203 is executed cyclically.

In step 204, the slice capacity alarm information is generated and notified to the NSMS through EMS.

In step 205, the slice is denied to add new subscribers or new users to access.

In an embodiment, before setting the network slice capacity threshold of the current slice instance according to the setting instruction, the method further includes: if the network slice capacity threshold is greater than the remaining capacity supported by the current slice instance, generating setting failure information, And send the setting failure information to the network slicing management network element.

In this embodiment, in the process of setting the network slice capacity threshold, it is also necessary to consider whether the sum of the capacity thresholds of all S-NSSAI corresponding to this item will be greater than the license of the NF instance itself after adding a threshold of the current S-NSSAI. The maximum capacity corresponding to the specified item, after adding a threshold of the current S-NSSAI, the sum of the capacity thresholds of all S-NSSAI corresponding to this item is less than or equal to the maximum capacity of the item given by the license of the NF instance itself. In this case, proceed to step 202; after adding a threshold of the current S-NSSAI, the sum of the capacity thresholds of all S-NSSAIs corresponding to this item is greater than the maximum capacity of the item given by the license of the NF instance itself, Refuse to set the network slice capacity threshold of the current slice instance, and feedback the setting failure information to the NSMS through EMS, and wait for the next processing instruction.

FIG. 4 is a schematic diagram of a process of a network slice capacity threshold setting end provided by an embodiment. As shown in Figure 4, for NSMS, the process of determining the network slice capacity threshold is as follows:

1) License management. Through the license management system of EMS, the maximum capacity supported by each slice instance (5GC NF instance) is set. The maximum capacity refers to the sum of the network slice capacity thresholds supported by each NF instance for multiple S-NSSAIs For example, given the UDM of slice instance 1 in the License, the sum of the maximum number of static users allocated by all S-NSSAIs is less than or equal to 2 million.

2) Obtain the slice capacity parameter. It can be to obtain the capacity requirement of the network slice or obtain the SLA parameter.

3) Determine the NF instance that provides services for the network slice, and decompose the slice capacity parameter to at least one NF instance, to obtain the network slice capacity threshold corresponding to the at least one NF instance.

4) NF slice level capacity counter setting request. The NSMS sends a setting instruction to the EMS, which includes the S-NSSAI-based network slice capacity threshold of each NF instance.

5) NF slice level capacity counter setting request. The EMS sends a setting instruction to the NF instance in the slice, and the setting instruction sent to each NF instance includes the S-NSSAI-based network slice capacity threshold of the NF instance.

6) Slice-level capacity control. The NF instance in the slice receives the capacity setting instruction, sets the network slice capacity threshold based on S-NSSAI, and turns on the network slice capacity threshold control.

It should be noted that during the setting process, if the NF instance determines that the network slice capacity threshold (any item in) is greater than the remaining capacity supported by it (the corresponding item in), or determines that the network slice capacity threshold is added (in If any item of) is greater than the maximum capacity supported by it (the corresponding item in), the setting is rejected.

7) NF slice level capacity counter setting response. The NF instance returns a response message for setting the network slice capacity threshold to the EMS.

8) NF slice level capacity counter setting response. The response message for the network slice capacity threshold setting reaches the NSMS via the EMS.

FIG. 5 is a schematic diagram of a process of a network slicing capacity control terminal provided by an embodiment. As shown in Figure 5, for NF, the process of network slice capacity threshold control is as follows:

a) The equipment is operating normally, and the slice user signs up and uses the services provided by the slice.

b) Slice-level capacity control. Calculate the actual network slice capacity based on S-NSSAI in real time and compare it with the set network slice capacity threshold and the given value of the license. When the actual network slice capacity based on S-NSSAI is greater than the set network slice capacity threshold Or in the case of the given value of the license, execute c); in the case that the actual network slice capacity based on S-NSSAI is less than or equal to the set network slice capacity threshold and less than or equal to the given value of the license, execute b cyclically ), continue to monitor the network slice capacity.

c) If the NF slice level capacity exceeds the limit, an alarm will be notified. The 5GC NF instance generates capacity alarm information based on the S-NSSAI, and sends the capacity alarm information to the EMS.

d) The NF slice level capacity exceeds the limit, and the alarm is notified. The capacity alarm information is sent to the NSMS via the EMS.

e) Notify OSS or the customer to deal with it. The NSMS sends the capacity alarm information to the OSS or the client, and the OSS or the client decides the processing action.

f) Slice-level capacity overrun processing: deny new subscribers or deny user access to generate new sessions. For the NF instance, if it is UDM or UDR, the new subscriber is rejected; if it is AMF, SMF or UPF, etc., the user is denied access to generate a new session.

g) Over-limit processing of slice-level capacity. NSMS processes according to OSS or customer processing actions, such as: processing slice-level slice capacity alarm information by expanding or adjusting the network slice capacity threshold. This processing may again trigger the network slice capacity threshold setting process or the NF license expansion process .

The following describes the network slice capacity threshold setting and control process of the foregoing embodiment through specific examples.

For example, a user purchases and uses a slice service marked with S-NSSAI = 011A0B01, and selects SLA parameters and capacity requirements. The slice capacity parameters are:

S-NSSAI＝011A0B01

{

Maximum number of static users = 1 million;

Maximum number of online dynamic users = 100,000;

Maximum number of online dynamic sessions = 300,000;

}

The operator uses a separate slice instance to provide services to the user. 5GC NF is deployed in the slice instance. When the actual network slice capacity is greater than the value of the slice capacity parameter mentioned above, the UDM or UDR will refuse to open an account for new users belonging to the slice service. , AMF, SMF, or UPF will reject the user-initiated new access request belonging to the slice service, and notify the user that the slice capacity has reached the threshold through the slice capacity alarm information, and remind the user to expand or do other processing. The end-to-end process is as step 1 to step 11.

In step 1, the maximum capacity supported by at least one 5GC NF instance in at least one slice instance is respectively given by the license management system of the EMS. For example, the maximum number of static users for a given UDM or UDR is 12 million; the maximum number of online dynamic users for AMF, SMF or UPF is 2 million, and the maximum number of online dynamic sessions is 6 million.

In step 2, obtain the capacity requirement provided by the user for the network slicing service to be purchased or obtain the SLA parameters:

S-NSSAI＝011A0B01

{

Maximum number of static users = 1 million;

Maximum number of online dynamic users = 100,000;

Maximum number of online dynamic sessions = 300,000;

}.

In step 3, an NF instance that provides services for the network slice is determined, and the NSMS decomposes the slice capacity parameter into at least one NF instance in at least one slice instance, and obtains a network slice capacity threshold corresponding to the at least one NF instance. Take slice instance 1 and slice instance 2 as examples:

For slice instance 1:

When UDM or UDR is S-NSSAI = 011A0B01, the maximum number of static users is 1 million;

When AMF, SMF or UPF is S-NSSAI = 011A0B01, the maximum number of online dynamic users is 100,000;

The maximum number of online dynamic sessions for AMF, SMF or UPF is 300,000 when S-NSSAI = 011A0B01;

In step 4, the NSMS sends a setting instruction to the EMS. The setting instruction is used to instruct each NF instance to set the S-NSSAI-based network slice capacity threshold according to the setting instruction.

In step 5, the EMS sends a setting command based on S-NSSAI to the NF instance.

In step 6, the NF instance receives the setting instruction, sets the S-NSSAI-based network slice capacity threshold according to the setting instruction, and starts the network slice capacity threshold control process. For example, for the AMF, SMF, or UPF of slice instance 1, set When S-NSSAI = 011A0B01, the maximum number of online dynamic users is 100,000 and the maximum number of online dynamic sessions is 300,000.

In step 7, the business is proceeding normally, and the slice user signs up and uses the service provided by the slice.

In step 8, the NF instance counts the actual network slice capacity based on S-NSSAI in real time, and judges whether the actual network slice capacity based on S-NSSAI is greater than the set network slice capacity threshold or the given value in the license. If the actual network slice capacity based on S-NSSAI is greater than the set network slice capacity threshold or the given value in the license, go to step 9; if the actual network slice capacity based on S-NSSAI is less than or equal to the setting If the network slice capacity threshold is less than or equal to the given value in the license, repeat step 8 to check the actual network slice capacity based on S-NSSAI with the set network slice capacity threshold or with the given value in the license The corresponding relationship.

In step 9, the slice capacity alarm information based on the S-NSSAI is generated, the slice capacity alarm information is sent to the NSMS via the EMS, and the OSS or the customer decides the processing action for the capacity overrun alarm.

In step 10, if the current NF instance is UDM or UDR, the new subscriber is rejected; if the current NF instance is AMF, SMF or UPF, the user is rejected to generate a new session.

In step 11, the NSMS processes the slice capacity alarm information according to the processing actions (such as capacity expansion) of the OSS or the customer, and this processing may again trigger the network slice capacity threshold setting process or the license expansion process.

The embodiment of the present application also provides a device for setting network slicing capacity. Fig. 6 is a schematic structural diagram of a network slice capacity setting device provided by an embodiment. As shown in FIG. 6, the network slice capacity setting device includes: an acquisition module 310, a threshold determination module 320, and an instruction sending module 330.

The obtaining module 310 is configured to obtain slice capacity parameters, where the slice capacity parameters include network slice capacity requirements or service level agreement parameters.

The threshold determination module 320 is configured to determine, according to the slice capacity parameter, a network slice capacity threshold corresponding to at least one slice instance that provides services for the network slice.

The instruction sending module 330 is configured to send a network slice capacity setting instruction to each slice instance, where the setting instruction includes a network slice capacity threshold corresponding to each slice instance.

The network slice capacity setting device of this embodiment decomposes or maps slice capacity parameters to at least one slice instance in the network, thereby converting the network slice capacity demand from the customer into the capacity demand for NF in the network slice; The slice instance sends setting instructions to notify the slice instance to set the corresponding network slice capacity threshold, so that the slice instance can efficiently manage online users and sessions according to the network slice capacity threshold, and establish a complete network slice capacity setting mechanism to improve the network Controllability of slice capacity and service stability.

In an embodiment, it further includes:

A setting failure information receiving module, configured to receive setting failure information returned by a target slice instance, where the target slice instance is a slice instance whose corresponding network slice capacity threshold is greater than the remaining capacity supported by the current slice instance;

The adjustment module is configured to adjust the network slice capacity threshold corresponding to the target slice instance according to the setting failure information.

The network slice capacity control device proposed in this embodiment and the network slice capacity control method proposed in the foregoing embodiments belong to the same inventive concept. For technical details not described in detail in this embodiment, please refer to any of the foregoing embodiments.

The embodiment of the present application also provides a network slicing capacity control device. Fig. 7 is a schematic structural diagram of a network slicing capacity control apparatus provided by an embodiment. As shown in FIG. 7, the network slice capacity control device includes: an instruction receiving module 410, a threshold setting module 420, and a capacity control module 430.

The instruction receiving module 410 is configured to receive a network slice capacity setting instruction, where the setting instruction includes the network slice capacity threshold of the current slice instance.

The threshold setting module 420 is configured to set the network slice capacity threshold of the current slice instance according to the setting instruction.

The capacity control module 430 is configured to control the network slice capacity provided to the user according to the network slice capacity threshold.

The network slicing capacity control device of this embodiment receives the setting instructions sent by NSMS through EMS, and sets the network slicing capacity threshold according to the setting instructions, thereby controlling the network slicing capacity provided to users, and efficiently performing online users and sessions Management has established a complete network slicing capacity control mechanism, thereby improving the controllability of network slicing capacity and service stability.

In an embodiment, it further includes:

The setting failure alarm module is set to generate setting failure information if the network slice capacity threshold is greater than the remaining capacity supported by the current slice instance before setting the network slice capacity threshold of the current slice instance according to the setting instruction, and The setting failure information is sent to the network slice management network element.

In an embodiment, the capacity control module 430 is configured to:

After the network slice capacity provided to the user is greater than the network slice capacity threshold, refuse to sign up with the user requesting access, or refuse to generate a session with the user requesting access.

The embodiment of the present application also provides a device. The network slice capacity setting method can be executed by a network slice capacity setting device, which can be implemented by at least one of software and hardware, and integrated in the device. The device is a network slice management network element (for example, an NSMS).

The network slice capacity control method can be executed by a network slice capacity control device, which can be implemented by at least one of software and hardware, and integrated in the device. The device is a core network element (for example, AMF).

FIG. 8 is a schematic diagram of the hardware structure of a device provided by an embodiment. As shown in FIG. 8, a device provided in this embodiment includes: a processor 510 and a storage device 520. There may be at least one processor in the device. In FIG. 8, one processor 510 is taken as an example. The processor 510 and the storage device 520 in the device may be connected by a bus or other means. example.

The at least one program is executed by the at least one processor 510, so that the at least one processor implements the network slice capacity setting method or the network slice capacity control method described in any of the foregoing embodiments.

As a computer-readable storage medium, the storage device 520 in the device can be configured to store at least one program. The program can be a software program, a computer-executable program, and a module, such as the network slice capacity control method in the embodiment of the present invention. Corresponding program instructions/modules (for example, the modules in the network slice capacity setting device shown in FIG. 6 include: an acquisition module 310, a threshold determination module 320, and an instruction sending module 330). The processor 510 executes various functional applications and data processing of the device by running the software programs, instructions, and modules stored in the storage device 520, that is, implements the network slice capacity setting method or the network slice capacity control method in the above method embodiment .

The storage device 520 mainly includes a storage program area and a storage data area. The storage program area can store an operating system and an application program required by at least one function; the storage data area can store data created according to the use of the device, etc. (as in the above implementation) Example setting instructions, network slice capacity threshold, etc.). In addition, the storage device 520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some examples, the storage device 520 may include memories remotely provided with respect to the processor 510, and these remote memories may be connected to the device through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

In addition, when at least one program included in the above-mentioned device is executed by the at least one processor 510, the following operations are implemented: obtaining slice capacity parameters, where the slice capacity parameters include network slice capacity requirements or service level agreement parameters; The slice capacity parameter determines a network slice capacity threshold corresponding to at least one slice instance that provides services for the network slice; and sends a network slice capacity setting instruction to each slice instance, and the setting instruction includes each of the slice instances. The network slice capacity threshold corresponding to the slice instance.

Alternatively, when at least one program included in the above-mentioned device is executed by the at least one processor 510, the following operations are implemented: receiving a network slice capacity setting instruction, where the setting instruction includes the network slice capacity threshold of the current slice instance; The setting instruction sets the network slice capacity threshold of the current slice instance; and controls the network slice capacity provided to the user according to the network slice capacity threshold.

The device proposed in this embodiment and the network slice capacity setting method or network slice capacity control method proposed in the above embodiments belong to the same inventive concept. For technical details not described in detail in this embodiment, please refer to any of the above embodiments.

The embodiment of the present application also provides a storage medium containing computer-executable instructions. When the computer-executable instructions are executed by a computer processor, they are used to execute a network slice capacity setting method or a network slice capacity control method.

Based on the above description of the implementation manners, those skilled in the art can understand that this application can be implemented by software and general hardware, or can be implemented by hardware. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), Random Access Memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including multiple instructions to make a computer device (which can be a personal computer, server, or network device, etc.) execute any of this application The method described in the embodiment.

The above are only exemplary embodiments of the present application, and are not used to limit the protection scope of the present application.

The block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on the memory. The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read only memory (ROM), random access memory (RAM), optical storage devices and systems (digital multi-function optical discs) (Digital Video Disc, DVD) or Compact Disk (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Process, DSP), application specific integrated circuits (ASICs) ), Field Programmable Gate Array (FGPA), and processors based on multi-core processor architecture.

Claims

A method for setting network slicing capacity, applied to network slicing management network elements, includes:

Acquiring a slice capacity parameter, where the slice capacity parameter includes a capacity requirement of a network slice or a service level agreement parameter;

Determine, according to the slice capacity parameter, a network slice capacity threshold corresponding to at least one slice instance that provides services for the network slice;

Send a network slice capacity setting instruction to each slice instance, where the setting instruction includes a network slice capacity threshold corresponding to each slice instance.
The method according to claim 1, wherein the network slice capacity threshold includes: a maximum number of static users, a maximum number of online dynamic users, and a maximum number of online dynamic sessions.
The method according to claim 1, further comprising:

Receiving setting failure information returned by a target slice instance, where the target slice instance is a slice instance whose corresponding network slice capacity threshold is greater than the remaining capacity supported by the current slice instance;

According to the setting failure information, the network slice capacity threshold corresponding to the target slice instance is adjusted.
A network slicing capacity control method, applied to core network elements, includes:

Receiving a setting instruction for a network slice capacity, where the setting instruction includes a network slice capacity threshold of the current slice instance;

Setting the network slice capacity threshold of the current slice instance according to the setting instruction;

The network slice capacity provided to the user is controlled according to the network slice capacity threshold.
The method according to claim 4, wherein the network slice capacity threshold includes: a maximum number of static users, a maximum number of online dynamic users, and a maximum number of online dynamic sessions.
The method according to claim 4, before setting the network slice capacity threshold of the current slice instance according to the setting instruction, further comprising:

In the case that the network slice capacity threshold is greater than the remaining capacity supported by the current slice instance, generating setting failure information, and sending the setting failure information to the network slice management network element.
The method according to claim 4, wherein the controlling the network slice capacity provided to the user according to the network slice capacity threshold comprises:

After the network slice capacity provided to the user is greater than the network slice capacity threshold, refuse to sign up with the user requesting access, or refuse to generate a session with the user requesting access.
A network slicing capacity setting device, including:

An obtaining module, configured to obtain slice capacity parameters, where the slice capacity parameters include network slice capacity requirements or service level agreement parameters;

A threshold determination module, configured to determine, according to the slice capacity parameter, a network slice capacity threshold corresponding to at least one slice instance that provides services for the network slice;

The instruction sending module is configured to send a network slice capacity setting instruction to each of the slice instances, where the setting instruction includes a network slice capacity threshold corresponding to each of the slice instances.
A network slicing capacity control device, including:

An instruction receiving module, configured to receive a setting instruction of the network slice capacity, the setting instruction including the network slice capacity threshold of the current slice instance;

A threshold setting module, configured to set the network slice capacity threshold of the current slice instance according to the setting instruction;

The capacity control module is configured to control the network slice capacity provided to the user according to the network slice capacity threshold.
A device that includes:

At least one processor;

The storage device is set to store at least one program;

When the at least one program is executed by the at least one processor, the at least one processor implements the network slice capacity setting method according to any one of claims 1-3 or any one of claims 4-7 The described network slicing capacity control method.
A computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, it implements the network slice capacity setting method according to any one of claims 1-3 or The network slice capacity control method according to any one of claims 4-7.