CN109525412B

CN109525412B - Method and device for managing network slices

Info

Publication number: CN109525412B
Application number: CN201710852957.2A
Authority: CN
Inventors: 孙文琦; 杨水根; 陆伟; 谭巍
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-09-19
Filing date: 2017-09-19
Publication date: 2021-04-20
Anticipated expiration: 2037-09-19
Also published as: CN109525412A; WO2019056954A1

Abstract

The application provides a method and a device for managing network slices, wherein the method comprises the following steps: a first management function entity sends a first management request to a second management function entity, wherein the first management request comprises identification used for identifying one or more network slice subnet instances of a network slice instance, and the first management request is used for requesting to process the one or more network slice subnet instances; and receiving a first management request response message sent by the second management functional entity, wherein the first management request response message is used for indicating the second management functional entity to complete the processing of the one or more network slice subnet instances, so that the high-efficiency management of the network slice subnet instances can be realized, and the purpose of managing the network slice instances is realized.

Description

Method and device for managing network slices

Technical Field

The present application relates to the field of communications, and in particular, to a method and apparatus for managing network slices.

Background

With the rapid development of mobile communication, digital transformation has involved almost all the conventional industries. However, the conventional cellular network architecture can only provide uniform network services, and it is difficult to satisfy the very different communication requirements, including functional differences and performance differences, caused by the digitalized transition wave. In a fifth Generation (5th Generation, 5G) communication system, the network will be abstracted as "network slices," one network slice meeting the connectivity communication service requirements of a certain class or use case. A 5G system may consist of a large number of network slices that satisfy different connection capabilities.

The network slice example is a real running logic network created by a network management system, and can meet certain network characteristics or service requirements. A network management system may create and manage one or more network slice instances simultaneously, including performance monitoring, fault management, modification, etc. during operation of the network slice instances. A complete network slice instance is capable of providing a complete end-to-end network service, while the network slice instances may be composed of network slice subnet instances and/or network functions. In order to provide differentiated communication requirements quickly and flexibly, efficient management of network slices is needed. However, the network management architecture in the prior art does not provide a complete set of solutions to implement the management of network slices. Therefore, it is desirable to provide a solution to the problem of how to efficiently manage network slices.

Disclosure of Invention

The application provides a method and a device for managing network slices, which can realize the efficient management of subnet instances of the network slices, thereby realizing the purpose of managing the subnet instances of the network slices.

In a first aspect, a method for managing network slices is provided, including:

the first management function entity sends a first management request to a second management function entity, wherein the first management request comprises an identifier for identifying one or more network slice subnet instances of a network slice instance, and the first management request is used for requesting to process the one or more network slice subnet instances;

and the first management function entity receives a first management request response message sent by the second management function entity, wherein the first management request response message is used for indicating the second management function entity to complete the processing of the one or more network slice subnet instances.

In this embodiment of the present application, the first management functional entity processes one or more network slice subnet instances of the network slice instance through the identifier, and performs corresponding management operation, so as to implement efficient management of the network slice subnet instances, thereby implementing the purpose of managing the network slice instance.

In one possible design, one identifier may indicate a plurality of network slice subnet instances, for example, grouping network slice subnet instances, and this identifier may be a group identifier; alternatively, each identity may indicate one network slice subnet instance.

In one possible design, before the first management function entity sends the first management request to the second management function entity, the method further includes:

the first management function entity determines to manage the network slice instance, the network slice instance comprising at least one network slice subnet instance.

In one possible design, the first identifier is used to identify the network slice instance. Wherein the identification of the one or more network slice subnet instances for identifying the network slice instance may be the second identification. The first identification and the second identification have a corresponding relationship.

In the embodiment of the present application, the first management function entity or the second management function entity is implemented by software, that is, a network slice management function is implemented by software. In one possible design, the software described above may be installed on a general purpose computer hardware device.

In one possible design, the first management functional entity may send the first management request to the plurality of second management functional entities at the same time, and may implement parallel request of the corresponding second management functional entities, thereby processing the plurality of network slice subnet instances and improving management efficiency.

In one possible design, the first management function entity may send the first management request to the plurality of second management function entities in a certain order. After receiving the first management request response message sent by one of the second management function entities, the first management function entity sends the first management request to the other second management function entity, so that the corresponding processing of the network slice subnet instances can be realized in a certain sequence.

In one possible design, the first management request may further include the first identifier.

In one possible design, the first management request response message may include the second identifier.

In one possible design, the first management request response message may further include the first identifier.

In one possible design, before sending the first management request to the second management function entity, the method further includes:

the first management function entity acquires the first identifier;

and the first management functional entity acquires the second identifier.

In one possible design, the first identifier may be obtained by the first management function entity from a local or other management function entity, or may be generated when the network slice instance is created. Therefore, the first identifier is acquired in a flexible manner.

In one possible design, the obtaining, by the first management function entity, the second identifier includes:

and the first management function entity receives the second identifier sent by the second management function entity.

In one possible design, the second identifier is generated by the second management function entity.

In one possible design, the method further includes:

the first management function entity sending a second management request to the second management function entity, the second management request being used for requesting the second management function entity to create the one or more network slice subnet instances;

wherein, the receiving, by the first management function entity, the second identifier sent by the second management function entity includes:

the first management function entity receives a second management request response message sent by the second management function entity, where the second management request response message is used to indicate that the second management function entity has completed creating the one or more network slice subnet instances, and the second management request response message includes the second identifier.

Here, the first management function entity may obtain the second identifier through a creation completion message fed back by the second management function entity in creating one or more network slice subnet instances. Therefore, after receiving the second management request response message, the first management functional entity may obtain the corresponding relationship according to the first identifier and the second identifier.

In one possible design, the receiving, by the first management function entity, the second identifier sent by the second management function entity includes:

the first management function entity receives a capability openness message sent by the second management function entity, where the capability openness message is used to indicate information of a network slice subnet instance supported by the second management function entity, and the capability openness message includes the second identifier.

In one possible design, the capability openness message may include at least one of the following information: an identification of the one or more network slice subnet instances, a type of the one or more network slice subnet instances, a capability of the one or more network slice subnet instances, a capacity of the one or more network slice subnet instances, and the like. In a possible design, the capability openness message further includes information, such as, but not limited to, the type, identification, capability, and capacity of other network slice subnet instances supported by the second management function entity.

Therefore, the first management function entity may acquire the second identifier through the capability openness message.

In one possible design, the method further includes:

the first management function entity sending a third management request to the second management function entity, the third management request requesting the second management function entity to use the one or more network slice subnet instances, the third management request including the second identifier;

the first management function entity receives a third management request response message sent by the second management function entity, where the third management request response message is used for the second management function entity to notify the network slice instance that the one or more network slice subnet instances can be used.

In one possible design, specifically for example, the third management request is used to request the second management function entity to modify the one or more network slice subnet instances.

In one possible design, the third management request may also be a reuse or usage request. Wherein the third management request includes a requirement description for one or more network slice subnet instances, and the third management request carries a second identifier.

In particular, the second management function entity may configure or reconfigure one or more network slice subnet instances according to the third management request. After the configuration or reconfiguration is completed, the second management function entity sends a third management request response message to the first management function entity so as to inform the first management function entity that the processing of the one or more network slice subnet instances is completed, so that the one or more network slice subnet instances become part of the network slice instances. In embodiments of the present application, "a network slice instance can use one or more network slice subnet instances," one or more network slice subnet instances become part of a network slice instance "means the same, i.e., one or more network slice subnet instances can provide services as part of a network slice instance.

In one possible design, the third management request includes the second identification.

In one possible design, the third management request may further include the first identifier.

Therefore, after receiving the third management request response message, the first management functional entity may obtain the corresponding relationship according to the first identifier and the second identifier.

In a possible design, after the first management functional entity receives the capability openness message, the first management functional entity may send the third management request to the second management functional entity.

Or, although the first management function entity has obtained the second identifier through the second management request response message, there may be a scenario in which the first management function entity has released the second identifier without using the network slice subnet instance, and at this time, the first management function entity may still send the third management request to the second management function entity.

In a second aspect, a method for managing network slices is provided, including:

a second management function entity receives a first management request sent by a first management function entity, wherein the first management request comprises an identifier used for identifying one or more network slice subnet instances of a network slice instance, and the first management request is used for requesting to process the one or more network slice subnet instances;

the second management functional entity processes the one or more network slice subnet instances according to the first management request;

and the second management function entity sends a first management request response message to the first management function entity, wherein the first management request response message is used for indicating that the processing of the one or more network slice subnet instances is finished.

In the embodiment of the present application, the second management function entity receives the management request issued by the first management function entity according to the identifier, and completes corresponding processing according to the management request, so as to implement efficient management of the network slice subnet instance, thereby implementing the purpose of managing the network slice instance.

In one possible design, the first identifier is used to identify the network slice instance, wherein the identifier used to identify one or more network slice subnet instances of the network slice instance may be the second identifier. The first identification and the second identification have a corresponding relationship.

In one possible design, the first management request may further include a first identifier.

In one possible design, before the second management function entity receives the first management request sent by the first management function entity, the method further includes:

and the second management function entity sends the second identifier to the first management function entity.

In one possible design, the method further includes:

the second management function entity receives a second management request sent by the first management function entity, wherein the second management request is used for requesting the second management function entity to create the one or more network slice subnet instances;

the second management function entity creates or configures the one or more network slice subnet instances for the first management function entity according to the second management request;

wherein, the sending, by the second management function entity, the second identifier to the first management function entity includes:

and the second management function entity sends a second management request response message to the first management function entity, wherein the second management request response message is used for indicating that the second management function entity completes the creation or configuration of the one or more network slice subnet instances, and the second management request response message comprises the second identifier.

Here, after receiving the second management request, the second management functional entity may create or configure the one or more network slice subnet instances for the first management functional entity according to the request content and the situation of the managed network slice subnet instances.

Therefore, the second management function entity may notify the second identifier to the first management function entity through the second management request response message.

In one possible design, the second management function may select an existing network slice subnet instance for use by the first management function. For the case that the existing network slice subnet instance has been shared by other network slice instances, the second identification may not only identify the one or more network slice subnet instances, but may also indicate that the one or more network slice subnet instances correspond to the network slice instances.

In one possible design, the first identifier may be included in the second management request.

In one possible design, the sending, by the second management function entity, the second identifier to the first management function entity includes:

and the second management function entity sends a capability openness message to the first management function entity, where the capability openness message is used to indicate information of the network slice subnet instances supported by the second management entity, and the capability openness message includes the second identifier.

Therefore, the second management function entity may inform the first management function entity of the second identifier through the force opening message.

In one possible design, the method further includes:

the second management function entity receives a third management request sent by the first management function entity, wherein the third management request is used for requesting the second management function entity to use the one or more network slice subnet instances;

the second management function entity configuring the one or more network slice subnet instances for the first management function entity;

the second management function entity sends a third management request response message to the first management function entity, the third management request response message being used for notifying the network slice instance that the one or more network slice subnet instances can be used.

In a possible design, specifically, for example, the third management request is used to request the second management function entity to modify the first network slice subnet instance.

In particular, the second management function entity may configure or reconfigure one or more network slice subnet instances according to the third management request. After the configuration or reconfiguration is completed, the second management function entity sends a third management request response message to the first management function entity so as to inform the first management function entity that the processing of the one or more network slice subnet instances is completed, so that the one or more network slice subnet instances become part of the network slice instances.

In one possible design, the third management request includes the second identification. In one possible design, the third management request may further include the first identifier.

Therefore, the second management functional entity may send a third management request response message to the first management functional entity, so that the first management functional entity may generate the corresponding relationship between the first identifier and the second identifier according to the third management request response message.

In one possible design, the third management request may be sent by the first management function entity after receiving the capability openness message.

Or, although the first management function entity has obtained the second identifier through the second management request response message, there may be a scenario in which the first management function entity has released the second identifier without using the one or more network slice subnet instances, and at this time, the first management function entity may still send the third management request to the second management function entity.

In a third aspect, an apparatus for managing network slices is provided, which is configured to perform the method of the first aspect or any possible implementation manner of the first aspect. In particular, the apparatus comprises means for performing the method of the first aspect described above or any possible implementation manner of the first aspect.

In a fourth aspect, an apparatus for managing network slices is provided to perform the method of the second aspect or any possible implementation manner of the second aspect. In particular, the apparatus comprises means for performing the method of the second aspect described above or any possible implementation of the second aspect.

In a fifth aspect, an apparatus for managing network slices is provided that includes a processor, a memory, and a transceiver. The processor is coupled to the memory and the transceiver. The memory is for storing instructions, the processor is for executing the instructions, and the transceiver is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the method of the first aspect or any possible implementation of the first aspect.

In a sixth aspect, an apparatus for managing network slices is provided that includes a processor, a memory, and a transceiver. The processor is coupled to the memory and the transceiver. The memory is for storing instructions, the processor is for executing the instructions, and the transceiver is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the second aspect or the method of any possible implementation of the second aspect.

In a seventh aspect, there is provided a computer-readable storage medium storing a program for causing an apparatus for managing network slices to execute the first aspect described above and any of its various implementations.

In an eighth aspect, there is provided a computer-readable storage medium storing a program for causing an apparatus for managing network slices to execute the second aspect described above and a method for managing network slices in any of its various implementations.

A ninth aspect provides a communication chip having instructions stored therein, which when run on a first management function entity, cause the communication chip to perform the method of the first aspect or any possible implementation manner of the first aspect.

A tenth aspect provides a communication chip having instructions stored therein, which when run on a second management function entity, cause the communication chip to perform the method of the first aspect or any possible implementation manner of the first aspect.

In an eleventh aspect, there is provided a system for managing network slices, the system comprising the apparatus of any one of the possible implementations of the fourth aspect or the fourth aspect and the apparatus of any one of the possible implementations of the fifth aspect or the fifth aspect; alternatively, the system comprises the apparatus of any of the possible implementations of the sixth aspect or the sixth aspect and the apparatus of any of the possible implementations of the seventh aspect or the seventh aspect.

In a twelfth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first or second aspect described above or any possible implementation thereof.

In a thirteenth aspect, a method for managing network slices is provided, including:

the first management functional entity acquires a second identifier, wherein the second identifier is used for identifying one or more network slice subnet instances of the network slice instances;

and when managing the network slice instance, the first management function entity uses the second identifier to manage the one or more network slice subnet instances.

In the embodiment of the application, the first management functional entity processes one or more network slice subnet instances according to the second identifier by acquiring the second identifier, and executes corresponding management operation, so as to realize efficient management of the network slice subnet instances, and further realize the purpose of managing the network slice instances.

In one possible design, the method further includes:

the first management function entity obtains a first identifier, wherein the first identifier is used for identifying the network slice instance, and the first identifier and the second identifier have a corresponding relation.

In one possible design, the obtaining, by the first management function entity, the first identifier includes:

the first management function entity creates the network slice instance and generates the first identifier.

In one possible design, the method further includes:

the first management function entity sending a third management request to a second management function entity, the third management request being used for requesting the second management function entity to use the one or more network slice subnet instances, the third management request including the second identifier;

the first management function entity receives a third management request response message sent by the second management function entity, where the third management request response message is used for the second management function entity to notify the first network slice instance that the one or more network slice subnet instances can be used.

In one possible design, the first management function entity managing the one or more network slice subnet instances using the second identification includes:

the first management functional entity sends a first management request to the second management functional entity, where the first management request is used to request the second management functional entity to process the one or more network slice subnet instances, where the processing includes at least one of modification, monitoring, terminating, and measurement, and the first management request includes the second identifier;

the method further comprises the following steps:

the first management function entity receives a first management request response message sent by the second management function entity, where the first management request response message is used to instruct the second management function entity to complete the processing of the one or more network slice subnet instances.

In a fourteenth aspect, a method for managing network slices is provided, including:

the second management function entity generating an identification for identifying one or more network slice subnet instances of the network slice instance;

the second management function entity sends the identification to the first management function entity;

and when the second management functional entity receives a first management request sent by the first management functional entity, the second management functional entity processes the one or more network slice subnet instances corresponding to the identifier, wherein the first management request comprises the identifier.

In the embodiment of the present application, the second management function entity receives the management request issued by the first management function entity by sending the identifier to the first management function entity, and completes corresponding processing according to the management request, so as to implement efficient management of the network slice subnet instance, thereby implementing the purpose of managing the network slice instance.

In one possible design, the method further includes:

the second management function entity creates or configures the one or more network slice subnet instances for the first management function entity according to the first management request;

wherein, the sending the identifier to the first management function entity by the second management function entity comprises:

the second management function entity sends a second management request response message to the first management function entity, where the second management request response message is used to indicate that the second management function entity has completed creation or configuration of the one or more network slice subnet instances, and the second management request response message includes the identifier.

Therefore, the second management function entity may notify the identifier to the first management function entity through the second management request response message.

In one possible design, the sending, by the second management function entity, the identifier to the first management function entity includes:

the second management function entity sends a capability openness message to the first management function entity, where the capability openness message is used to indicate information of the network slice subnet instances supported by the second management entity, and the capability openness message includes the identifier.

Therefore, the second management function entity can inform the first management function entity of the identifier through the force opening message.

In one possible design, the method further includes:

the second management function entity receiving a third management request sent by the first management function entity, the third management request being used for requesting the second management function entity to use the one or more network slice subnet instances, the third management request including the identifier;

the second management function entity configures the first network slice subnet instance for the first management function entity;

the second management function entity sends a third management request response message to the first management function entity, wherein the third management request response message is used for the second management function entity to inform the first network slice instance that the one or more network slice subnet instances can be used.

In one possible design, the method further includes:

the second management function entity receives the first management request sent by the first management function entity, where the first management request is used to request processing on the one or more network slice subnet instances, where the processing includes at least one of modification, monitoring, terminating, and measurement, and the first management request includes the identifier;

the second management function entity sends a first management request response message to the first management function entity, the first management request response message being used for indicating that the processing of the one or more network slice subnet instances is completed.

In a fifteenth aspect, an apparatus for managing network slices is provided to perform the method of the thirteenth aspect or any possible implementation manner of the thirteenth aspect. In particular, the apparatus comprises means for performing the method of the thirteenth aspect or any possible implementation of the thirteenth aspect.

In a sixteenth aspect, an apparatus for managing network slices is provided, which is configured to perform the method in any possible implementation manner of the fourteenth aspect or the fourteenth aspect. In particular, the apparatus comprises means for performing the method of the fourteenth aspect or any possible implementation manner of the fourteenth aspect.

In a seventeenth aspect, an apparatus for managing network slices is provided that includes a processor, a memory, and a transceiver. The processor is coupled to the memory and the transceiver. The memory is for storing instructions, the processor is for executing the instructions, and the transceiver is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the method of the thirteenth aspect or any possible implementation of the thirteenth aspect.

In an eighteenth aspect, an apparatus for managing network slices is provided that includes a processor, a memory, and a transceiver. The processor is coupled to the memory and the transceiver. The memory is for storing instructions, the processor is for executing the instructions, and the transceiver is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the method of the fourteenth aspect or any possible implementation manner of the fourteenth aspect.

A nineteenth aspect provides a computer-readable storage medium storing a program that causes an apparatus for managing network slices to execute the method of managing network slices of the thirteenth aspect described above, and any of its various implementations.

A twentieth aspect provides a computer-readable storage medium storing a program that causes an apparatus for managing network slices to execute the fourteenth aspect described above, and any of its various implementations, a method of managing network slices.

A twenty-first aspect provides a communication chip having instructions stored therein, which when run on a first management function entity, cause the communication chip to perform the method of the thirteenth aspect or any possible implementation of the thirteenth aspect.

A twenty-second aspect provides a communication chip having instructions stored therein, which when run on a second management function entity, cause the communication chip to perform the method of the above-mentioned fourteenth aspect or any possible implementation manner of the fourteenth aspect.

A twenty-third aspect provides a system for managing network slices, the system comprising the apparatus of any one of the possible implementations of the fifteenth aspect or the fifteenth aspect and the apparatus of any one of the possible implementations of the sixteenth aspect or the sixteenth aspect; alternatively, the system comprises the apparatus of any of the possible implementations of the seventeenth aspect or the seventeenth aspect and the apparatus of any of the possible implementations of the eighteenth aspect or the eighteenth aspect.

A twenty-fourth aspect provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of the thirteenth or fourteenth aspect or any possible implementation thereof.

Drawings

Fig. 1 is a schematic diagram of a network slice management system architecture.

Fig. 2 is a schematic interaction diagram of a method of managing network slices according to an embodiment of the application.

Fig. 3 is a schematic interaction diagram of a method of managing network slices according to another embodiment of the present application.

Fig. 4 is a schematic interaction diagram of a method of managing network slices according to yet another embodiment of the present application.

Fig. 5 is a schematic interaction diagram of a method of managing network slices according to another embodiment of the present application.

Fig. 6 is a schematic interaction diagram of one example of managing network slices according to an embodiment of the application.

Fig. 7 is a schematic interaction diagram of another example of managing network slices according to an embodiment of the application.

Fig. 8 is a schematic interaction diagram of yet another example of managing network slices according to an embodiment of the application.

Fig. 9 is a schematic block diagram of an apparatus for managing network slices according to an embodiment of the present application.

Fig. 10 is a schematic block diagram of an apparatus for managing network slices according to another embodiment of the present application.

Fig. 11 is a block diagram of an apparatus for managing network slices according to an embodiment of the present disclosure.

Fig. 12 is a block diagram of an apparatus for managing network slices according to another embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The technical solution of the embodiment of the present application may be applied to various communication systems or network management systems supporting network slicing, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a future fifth Generation (5th Generation, 5G) system, or a New Radio (NR).

Terminal equipment in the embodiments of the present application may refer to user equipment, access terminals, subscriber units, subscriber stations, mobile stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents, or user devices. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G Network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like, which are not limited in this embodiment.

The embodiment of the application relates to a Network slice (Network slice) technology. A network slice is a logical network that can provide certain network capabilities, with certain network characteristics. Network slice is the concept of a logical network, embodied by network slice instances. The network slice instance contains several network function instances, as well as the computing, storage, network, etc. resources needed to compose a deployed logical network. For example, in a 5G network, network slicing is an on-demand networking mode, and brings a new service which can be adjusted according to changing user requirements and quickly meet new application requirements for operators.

The network slicing technique abstracts 5G network physical infrastructure resources into a plurality of network slices according to scene requirements. And each network slice carries out customized cutting of network functions and arrangement management of corresponding network functions according to the requirements of the service scenes and the service models. One network slice can be considered as one instantiated 5G network. Such a network structure allows an operator to provide a network as a service to users, and can freely combine physical networks according to the indexes of rate, capacity, coverage, delay, reliability, security, availability, and the like, so as to meet the requirements of different users.

It should be noted that the terms "network management architecture", "network system", "system", etc. may be used interchangeably herein. For ease of understanding, some terms appearing herein are introduced:

network slicing: network slicing is a concept that different logical networks are customized according to different service requirements on top of a physical or virtual network infrastructure. The network slice may be a complete end-to-end network including the terminal, the access network, the transport network, the core network and the application server, and may provide complete telecommunication services with certain network capabilities. The network slice may also be any combination of the above-mentioned terminal, access network, transport network, core network and application server. A network slice may have one or more of the following characteristics: the access network may or may not be sliced. The access network may be common to multiple network slices. Wherein the characteristics of the different network slices and the network functions that make up them may be different.

Network Slice Template (NST): refers to a way to generate a network slice instance, which is used to provide a reference for generating the network slice instance. The network slice template specifies how the network slice instance should be generated. For example, the network slice module may indicate which network functions the network slice contains, Key Performance Indicators (KPI) Indicators that should be achieved, and so on.

Network Slice example (NSI): the method is a real operating logic network and can meet certain network characteristics or service requirements. One network slice instance may provide one or more services. The network slice instance can be created by a network management system, and one network management system can create a plurality of network slice instances and manage the network slice instances simultaneously, including performance monitoring, fault management and the like in the operation process of the network slice instances. When multiple network slice instances coexist, portions of the network resources and network functions may be shared between the network slice instances. The network slice instance may or may not be created from a network slice template. A complete Network Slice Instance is capable of providing a complete end-to-end Network service, and what constitutes the Network Slice Instance may be a Network Slice Subnet Instance (NSSI) and/or a Network Function (NF). The network functions may include physical network functions and/or virtual network functions. Hereinafter, a physical network function and/or a virtual network function are collectively referred to as a network function.

Network slice subnet example: the network slice subnet instance may not need to provide complete network service end to end, and the network slice subnet instance may be a set formed by network functions of the same equipment provider in the network slice instance, or may be a set formed by network functions divided by domains, such as a core network slice subnet instance, an access network slice subnet instance, or a set formed by other manners, such as a deployment location. A network slice subnet instance may be shared by multiple network slice instances. The network slicing sub-network example is provided, so that the management of a network management system can be facilitated. Wherein, a network slice subnet instance may be composed of a plurality of network slice subnet instances, each network slice subnet instance is composed of a plurality of network slice subnet instances and network functions which are not converted into network slice subnet instances; alternatively, a network slice subnet instance may consist of only a few network functions.

Network function: the network function is a processing function in the network, defines the behavior and the interface of the functionality, and can be realized by special hardware or a universal hardware platform in the form of virtual function. Thus, from an implementation point of view, network functions may be divided into physical network functions and virtual network functions. From a usage point of view, network functions can be divided into dedicated network functions and shared network functions. In particular, for multiple (sub) network slice instances, different network functions, referred to as proprietary network functions, may be used independently; alternatively, the same network function may be shared, and such a network function is referred to as a shared network function.

The management process of the network slice comprises the following steps: creation of a network slice instance, modification of a network slice instance (including capacity expansion, capacity reduction, topology modification, network function addition, network function deletion, and the like), termination of a network slice instance, and the like. In one possible design, management of network slice instances may be decomposed into management of network slice subnet instances. It should be noted that the life cycles of the network slice instance and the network slice subnet instance are independent, for example, the terminating network slice instance is not equal to the network slice subnet instance that is necessarily to be terminated, but the network slice instance and the network slice subnet instance have a management association, for example, creating a network slice instance may require creating one or more new network slice subnet instances, and modifying a network slice instance may require modifying one or more network slice subnet instances.

To facilitate understanding of the embodiments of the present application, a network slice management system architecture is first introduced with reference to fig. 1. Fig. 1 shows a schematic diagram of a network slice management system architecture 100. As shown in fig. 1, the Network Slice Management system architecture 100 includes a Communication Service Management Function (CSMF), a Network Slice Management Function (NSMF), and a Network Slice Subnet Management Function (NSSMF). The communication service management function and the network slice management function, or the network slice management function and the network slice subnet management function can be connected through an interface (for example, Itf-csm).

It should be understood that, in the embodiment of the present application, there is no limitation on how each module in fig. 1 corresponds to an existing network management system, or the location of each module in fig. 1 in a 5G network management system is not limited. The above management functions will be described in turn.

The communication service management function is mainly responsible for one or more of, for example, converting communication service requirements of the operator and/or the third-party customer into requirements for network slices, sending the requirements for network slices (e.g., request for creating, terminating, modifying network slice instance, etc.) to the NSMF through an interface with the NSMF, acquiring management data (e.g., performance, fault data, etc.) of the network slices from the NSMF, generating management data of the communication service running on the network slice instance, receiving subscription requirements of the operator and/or the third-party customer for the network slice management data and/or the management data of the communication service, and the like.

The network slice management function is mainly responsible for one or more of the following functions, for example, receiving a network slice requirement sent by the CSMF, managing the life cycle, performance, and failure of the network slice instance (hereinafter, life cycle, performance, and failure management are simply referred to as management), arranging the composition of the network slice instance, decomposing the requirement of the network slice instance into the requirement of each network slice subnet instance and/or network function, and sending a network slice subnet instance management request to each NSSMF. Wherein the network slice management function may manage one or more network slice instances.

The network slice subnet management function is mainly responsible for one or more of the following functions, for example, receiving network slice subnet requirements sent by the NSMF, managing the network slice subnet instances, arranging the composition of the network slice instances, decomposing the requirements of the network slice subnet instances into the requirements of each network function and/or nested network slice subnet instances, and possibly sending nested network slice subnet instance management requests to other NSSMFs. Wherein the network slice subnet management function can manage one or more network slice subnet instances.

The method for managing the network slices of the embodiment of the application can be applied to the network slice management system architecture. Alternatively, the method for managing network slices may also be applied to other similar network management architectures, which is not limited in this embodiment of the present application. In the method for managing network slices described below, the first management function entity may be a network slice management function in the network slice management system architecture, and the second management function entity may be a network slice subnet management function in the network slice management system architecture. Alternatively, the first management function entity and the second management function entity may also be other entity devices having corresponding functions in a network slice management system architecture, which is not limited in this embodiment of the present application.

Fig. 2 shows a schematic interaction diagram of a method 200 of managing network slices according to an embodiment of the application. As shown in fig. 2, the method 200 includes:

s210, the first management function entity determines to manage the network slice instance, wherein the network slice instance comprises at least one network slice subnet instance.

It should be understood that, in a specific implementation, the step S210 in the method 200 may or may not be present, and this is not limited in this embodiment of the application.

It should be noted that, here, the management of the network slice instance may specifically be to manage the network slice subnet instances included in the network slice instance. For example, the NSMF determines that the NSI is required to be managed, and the NSI is composed of one or more NSSIs, so that the corresponding NSSI can be managed.

In one possible design, before S210, the first management functional entity may receive a management request sent by the CSMF, where the management request is used to request management of the network slice instance, and the management request may carry a first identifier, where the first identifier is used to identify the network slice instance. Alternatively, the first management function entity may decide to manage the network slice instance according to the network slice management policy itself.

S220, the first management functional entity sends a first management request to a second management functional entity, where the first management request includes an identifier for identifying one or more network slice subnet instances of a network slice instance, and the first management request is used to request processing of the one or more network slice subnet instances. For convenience of description, the description will be given below taking the identifier as the second identifier as an example.

Correspondingly, the second management function entity receives the first management request sent by the first management function entity.

In one possible design, an identifier may indicate one or more network slice subnet instances, such as grouping one or more network slice subnet instances, and this identifier may be a group identifier; alternatively, each identification may indicate one or more network slice subnet instances.

Wherein the first identifier is used to identify the network slice instance and the second identifier is used to identify the one or more network slice subnet instances. The first identification and the second identification have a corresponding relationship.

Wherein the correspondence exists in the first management function entity. The first management function entity maintains the corresponding relationship.

In a possible design, the first management function entity may also issue the correspondence to the second management function entity, that is, the correspondence may also exist in the second management function entity, which is helpful for the second management function entity to manage its corresponding network slice subnet instance.

In particular, the first management function entity may decompose management requirements for network slice instances onto a plurality of network slice subnet instances. Wherein the first identifier is used to identify a network slice instance and the second identifier is used to identify one or more network slice subnet instances. And the first management functional entity determines the network slice subnet instances contained in the network slice instances according to the corresponding relation between the first identifier and the second identifier, determines that one or more network slice subnet instances identified by the second identifier need to be modified, and sends a first management request to the second management functional entity to request for processing the one or more network slice subnet instances.

In a possible design, the first identifier may be obtained by the first management function entity from a local or other management function entity, or may be generated when the network slice instance is created, which is not limited to this.

In one possible design, before S220, the first management function entity may directly decide to modify one or more network slice subnet instances, which may belong to one or more network slice instances or do not currently belong to any network slice instance, according to its own management policy. For example, the first management function entity may measure and monitor a network slice subnet instance to obtain the operation condition of the network slice subnet instance.

S230, the second management functional entity processes the one or more network slice subnet instances according to the first management request.

Wherein the processing comprises at least one of modifying, monitoring, terminating, measuring.

S240, the second management functional entity sends a first management request response message to the first management functional entity, where the first management request response message is used to indicate that the processing on the one or more network slice subnet instances is completed.

Correspondingly, the first management functional entity receives the first management request response message sent by the second management functional entity.

Specifically, the first management functional entity may find one or more network slice subnet instances that need to be managed through a corresponding relationship between the first identifier and the second identifier, for example, the first identifier- > the second identifier. Then, the first management functional entity sends a first management request to the second management functional entity to request the second management functional entity to process the one or more network slice subnet instances, for example, to perform management operations such as modification, monitoring, terminating, measuring, and the like on the one or more network slice subnet instances. The second management function entity carries out corresponding processing according to the content requested by the first management request, and feeds back a first management request response message to the first management function entity after the processing is finished so as to inform the first management function entity that the processing is finished.

Therefore, the first management functional entity determines the one or more network slice subnet instances identified by the second identifier, which need to be managed, through the corresponding relationship between the first identifier and the second identifier, and executes corresponding management operation, so as to implement efficient management of the network slice subnet instances, thereby implementing the purpose of managing the network slice instances.

It should be understood that, in the embodiment of the present application, the first management functional entity may send the first management request to the plurality of second management functional entities at the same time, and may implement parallel request of the corresponding second management functional entities, so as to process one or more network slice subnet instances, thereby improving management efficiency.

It should also be understood that the first management function entity may also send the first management request to a plurality of second management function entities in a certain order. After receiving the first management request response message sent by one of the second management function entities, the first management function entity sends the first management request to the other second management function entity, so that the corresponding processing of the network slice subnet instances can be realized in a certain sequence.

It is described above that the first management functional entity may manage the network slice subnet instance according to the correspondence between the first identifier and the second identifier. How the first management function entity obtains the first identity and the second identity will be described below.

Fig. 3 shows a schematic interaction diagram of a method 300 of managing network slices according to another embodiment of the present application. As shown in fig. 3, the method 300 includes:

s310, the first management function entity obtains a first identifier, and the first identifier is used for identifying the network slice instance.

In one possible design, the first identity may be private, or fully standardized, or partially standardized.

For example, the first Identifier may include an NSI Identifier (ID) for identifying an NSI. The NSI ID may include a plurality of fields, for example, a Public Land Mobile Network (PLMN) ID, a slice type, a service type, a tenant ID, and a differentiator.

Specifically, S310 includes:

and the first management function entity creates the network slice instance and acquires or generates the first identifier.

Specifically, to meet the business requirements, the first management function entity may create a network slice instance and generate a first identification to identify the network slice instance.

S320, the first management functional entity obtains a second identifier, where the second identifier is used to identify one or more network slice subnet instances, where the network slice instances include at least one network slice subnet instance.

Wherein the first management function entity determines that the network slice instance requires at least one network slice subnet instance component. For example, it can be determined by calculation.

In one possible design, the second identity may be private, or fully standardized, or partially standardized.

For example, the second identifier may be an NSSI ID for identifying an NSSI. The NSSI ID may include at least one field, such as a PLMN ID, a slice subnet type, and other identifier.

In a possible design, the second identifier may be obtained locally by the first management function entity or obtained from a message sent by another management function entity, which is not limited herein. For example, if the first management function entity has previously used one or more network slice subnet instances and has learned the second identity, the first management function entity may directly obtain the second identity from local.

In one possible design, S320 includes:

s321, the second management function entity sends the second identifier to the first management function entity.

Correspondingly, the first management function entity receives the second identifier sent by the second management function entity.

It should be noted that, in the embodiment of the present application, a timing for sending the second identifier by the second management function entity is not limited. Specifically, the second management functional entity may send the second identifier after receiving the request for creating the network slice subnet instance sent by the first management functional entity, or may send the second identifier to the first management functional entity in advance before receiving the request for creating the network slice subnet instance sent by the first management functional entity. As will be described in detail below.

In one possible design, as one embodiment, fig. 4 illustrates a schematic flow chart diagram of a method 400 of managing network slices in accordance with yet another embodiment of the present application. As shown in fig. 4, the method 400 includes:

s401, the first management functional entity sends a second management request to a second management functional entity, where the second management request is used to request the second management functional entity to create the one or more network slice subnet instances.

Correspondingly, the second management function entity receives the second management request sent by the first management function entity.

In a possible design, the second management request may carry a description of a Requirement for a network slice subnet instance, and may include a network slice/network slice subnet type, a resolved Service Level Agreement (SLA) or a Service Level Requirement (SLR), and the like.

S402, the second management functional entity creates or configures the one or more network slice subnet instances for the first management functional entity according to the first management request.

One implementation form of the "first management functional entity receives the second identifier sent by the second management functional entity" may be:

s403, the second management function entity sends a second management request response message to the first management function entity.

Correspondingly, the first management function entity receives a second management request response message sent by a second management function entity, where the second management request response message is used to indicate that the second management function entity has completed creation of the one or more network slice subnet instances, and the second management request response message includes the second identifier.

It should be understood that the above S403 may be a specific implementation of step S321 in fig. 3.

Specifically, when judging that one or more network slice subnet instances need to be created, the first management functional entity sends a second management request to the second management functional entity to request the second management functional entity to create the one or more network slice subnet instances. Correspondingly, after receiving the second management request, the second management functional entity may create or configure the one or more network slice subnet instances for the first management functional entity according to the request content and the situation of the managed network slice subnet instances. For example, the second management function entity may generate a new network slice subnet instance for use by the first management function entity; alternatively, the second management function entity may select an existing network slice subnet instance (or multiple existing network slice subnet instances) for use by the first management function entity. After the creation or configuration is completed, the second management function entity may send a second management request response message to the first management function entity to inform that the creation or configuration of the one or more network slice subnet instances has been completed. In a possible design, after receiving the second management request response message, the first management functional entity may associate or map the first identifier and the second identifier to obtain a corresponding relationship between the first identifier and the second identifier. In this way, the first management function entity may manage the one or more network slice subnet instances using the correspondence.

Wherein, for the case that "the second management function entity selects an existing network slice subnet instance to be used by the first management function entity", if the existing network slice subnet instance is not shared by other network slice instances, the second management function entity may configure the existing network slice subnet instance to be used only by the first management function entity; alternatively, if the existing network slice subnet instance is shared by other network slice instances, the second management function entity may configure the existing network slice subnet instance to be shared for use by the network slice instances as well. For the case that the existing network slice subnet instance has been shared by other network slice instances, the second identifier may not only identify the existing network slice subnet instance, but may also indicate that the existing network slice subnet instance corresponds to the network slice instance. For example, the second identifier is NSSI id2.x, where x is used by the second management function entity to distinguish between different network slice instances. For example, if the second management function entity receives management requests (e.g., modification request, monitoring request, termination request, measurement request, etc.) of multiple network slice instances, the NSSI id2.x can distinguish from which network slice instance the management request is corresponding to.

That is to say, the first management functional entity may carry the first identifier when issuing the second management request. The second management function entity may determine a correspondence relationship according to the first identifier and the second identifier. For the case that the one or more network slice subnet instances are shared by multiple network slice instances, the second management function entity may identify the one or more shared network slice subnet instances according to the correspondence. Since the second management functional entity can definitely know the relationship between the one or more network slice subnet instances and the network slice instances through the corresponding relationship, the second management functional entity can directly identify the one or more network slice subnet instances by using the second identifier, and the x is not required to be used again to indicate that the one or more network slice subnet instances correspond to the network slice instances.

In one possible design, as an embodiment, S321 includes:

and the second management function entity sends the capability opening message to the first management function entity.

Correspondingly, the first management function entity receives a capability openness message sent by the second management function entity, where the capability openness message is used to indicate information of a network slice subnet instance supported by the second management function entity, and the capability openness message includes the second identifier.

S330, the first management function entity obtains the corresponding relation between the first identification and the second identification according to the first identification and the second identification.

In the embodiment of the application, the first management functional entity acquires the first identifier and the second identifier and generates the corresponding relationship between the first identifier and the second identifier, so that the management of the network slice subnet instance is realized, and the management efficiency of the network slice instance can be improved.

In one possible design, as one embodiment, fig. 5 illustrates a schematic flow chart diagram of a method 500 of managing network slices in accordance with another embodiment of the present application. It should be understood that the method 500 shown in fig. 5 may be used in combination with the method 300 or the method 400 described above, without limitation. As shown in fig. 5, the method 500 includes:

s501, the first management functional entity sends a third management request to a second management functional entity, where the third management request is used to request the second management functional entity to use the one or more network slice subnet instances, and the third management request includes the second identifier.

Correspondingly, the second management function entity receives the third management request sent by the first management function entity.

S502, the second management function entity configures the one or more network slice subnet instances for the first management function entity.

S503, the second management functional entity sends a third management request response message to the first management functional entity.

Correspondingly, the first management function entity receives a third management request response message sent by the second management function entity, where the third management request response message is used to notify the network slice instance that the one or more network slice subnet instances can be used. For example, the third management request response message is used to indicate that the second management function entity has completed configuration or reconfiguration of the one or more network slice subnet instances.

In one possible design, the third management request may be carried in different types of messages, such as a use/reuse request message for a network slice subnet instance, a creation request message for a network slice subnet instance, a modification request message for a network slice subnet instance, and so on.

Specifically, for the case that the first management function entity already knows the second identifier, such as by a capability openmessage, or knows the second identifier when the one or more network slice subnet instances are used before, the first management function entity may send a third management request to the second management function entity to request to use the one or more network slice subnet instances. In a possible design, the third management request carries the second identifier and description information of the requirements of the network slice subnet instance, such as SLA information and/or SLR information. In a possible design, the third management request may further carry the first identifier. Correspondingly, the second management functional entity may complete corresponding configuration or reconfiguration according to the third management request, and feed back a third management request response message after the configuration or reconfiguration is completed, so as to notify that the processing of the one or more network slice subnet instances has been completed. In a possible design, the third management request response message may further carry the first identifier.

In one possible design, specifically for example, the third management request is used to request the second management function entity to modify the one or more network slice subnet instances. In one possible design, the third management request may also be a reuse or usage request. Wherein the third management request includes a requirement description for one or more network slice subnet instances, and the third management request carries a second identifier.

In particular, the second management function entity may configure or reconfigure one or more network slice subnet instances according to the third management request. After the configuration or reconfiguration is completed, the second management function entity sends a third management request response message to the first management function entity so as to inform the first management function entity that the processing of the one or more network slice subnet instances is completed, so that the one or more network slice subnet instances become part of the network slice instance.

Or, although the first management function entity has obtained the second identifier through the second management request response message, there may be a scenario in which the first management function entity has released the second identifier without using one or more network slice subnet instances, and at this time, the first management function entity may still send the third management request to the second management function entity.

Therefore, the first management function entity may directly issue the third management request to the second management function entity, knowing the second identifier, so as to use the one or more network slice subnet instances.

In a possible design, after receiving the third management request response message, the first management functional entity may associate or map the first identifier and the second identifier to obtain a corresponding relationship between the first identifier and the second identifier.

In this way, the first management function entity may manage the one or more network slice subnet instances using the correspondence.

The technical solution of the above embodiment is described in a scenario where the network slice instance includes at least one network slice subnet instance. In one possible design, the above scenario may be extended to a scenario where nesting between network slice subnet instances is possible, i.e. a network slice subnet instance comprises at least one network slice subnet instance. Accordingly, the first management function entity and the second management function entity may both be NSSMFs. For this scenario, the technical solution of the embodiment of the present application is still applicable. For example, the first management function entity in the above embodiments is replaced by the second management function entity, and the network slice instances managed by the first management function entity are replaced by one or more network slice subnet instances.

The method for managing network slices according to the embodiment of the present application is described above with reference to fig. 2 to 5. The following describes a specific flow of the method for managing network slices according to the embodiment of the present application, with reference to the examples in fig. 6 to 8. It should be understood that the examples in fig. 6 to 8 are only for facilitating the understanding of the embodiments of the present application by those skilled in the art, and are not intended to limit the embodiments of the present application to the specific scenarios illustrated. It will be apparent to those skilled in the art that various equivalent modifications or variations are possible in light of the examples shown in fig. 6-8, and such modifications or variations are within the scope of the embodiments of the invention.

For convenience of description, the following example will be described with the first network slice example as an example. In embodiments of the present application, the first network slice instance is used to generally refer to one of the network slice instances managed by the first management function entity.

Fig. 6 is a schematic interaction diagram of one example 600 of managing network slices according to an embodiment of the application. As shown in fig. 6, the method 600 includes:

s601, the first management function entity creates a first network slice instance and generates a first identifier for identifying the first network slice instance.

For example, the first identifier is an NSI ID, which is used to identify an NSI.

In one possible design, the first management function entity knows, by calculation, that the first network slice instance needs to be composed of multiple network slice subnet instances, e.g., NSI is composed of 2 NSSI.

S602, the first management functional entity sends a first creation request to the second management functional entity 1.

Correspondingly, the second management functional entity 1 receives the first creation request sent by the first management functional entity.

Wherein the first creation request is for requesting the second management function entity 1 to create a network slice subnet instance.

In one possible design, the first creation request carries description information of the network slice subnet instance. In one possible design, the description information may include one or more of the following: description information of service requirements of the network slice subnet instance, identification of a Network Slice Subnet Template (NSST) of the network slice subnet instance, and NSST-related configuration parameter information.

In one possible design, the first creation request may or may not carry the first identifier.

S603, the first management functional entity sends a second creation request to the second management functional entity 2.

Correspondingly, the second management functional entity 2 receives the second creation request sent by the first management functional entity.

It should be understood that the definitions of the first creation request and the second creation request are similar, and are not described herein.

It should also be understood that there is no sequence between the above S602 and S603, and the first creation request and the second creation request are messages sent to different management function entities.

In one possible design, the first identifier may or may not be carried in the second creation request.

S604, the second management function entity 1 generates or configures the network slice subnet instance 1.

Specifically, the second management function entity 1 may create the network slice subnet instance 1 for the first network slice instance to use after receiving the first creation request. Alternatively, if the network-slice subnet instance 1 already exists, the second management function entity 1 may configure the network-slice subnet instance 1 to be used only by the first network-slice instance. Where the network slice subnet instance 1 is unshared, i.e., not shared by other network slice instances.

In one possible design, the second management function entity 1 generates an identification of the network slice subnet instance 1, such as NSSI ID 1.

In a possible design, if the first creation request carries the first identifier, such as an NSI ID, the second management functional entity 1 may map the NSI ID with the NSSI ID 1.

S605, the second management function entity 1 sends a first creation complete message to the first management function entity.

Correspondingly, the first management functional entity receives the first creation completion message sent by the second management functional entity 1.

Wherein the first creation completion message is used for feeding back that the creation of the network slice subnet instance 1 is completed.

In one possible design, the first create complete message includes an identification of network slice subnet instance 1, such as NSSI ID 1. In a possible design, if the first creation request carries the first identifier, such as an NSI ID, the first creation completion message may include the first identifier, such as an NSI ID.

S606, the second management function entity 2 configures the network slice subnet instance 2.

In particular, if a network-slice subnet instance 2 already exists and has been shared by at least one other network-slice instance, the second management function entity 2 may configure the network-slice subnet instance 2 to be used by the first network-slice instance as well.

In one possible design, the second management function entity may directly use the identification of network slice subnet instance 2, such as NSSI ID 2; alternatively, the second management function entity determines the identity of network slice subnet instance 2 as NSSI id2.x, where x is used by the second management function entity to distinguish between different network slice instances.

In one possible design, if the first identifier, such as the NSI ID, is carried in the second creation request, the second management functional entity 2 may map the NSI ID with the NSI ID2 or NSI ID2. x.

S607, the second management functional entity 2 sends a second creation complete message to the first management functional entity.

Correspondingly, the first management functional entity receives the second creation completion message sent by the second management functional entity 2.

Wherein the second creation completion message is used for feeding back that the creation of the network slice subnet instance 2 is completed.

In one possible design, the second create complete message includes an identification of network slice subnet instance 2, such as NSSI ID2 or NSSI ID2. x. In a possible design, if the first creation request carries the first identifier, such as an NSI ID, the first creation completion message may include the first identifier, such as an NSI ID.

S608, the first management function entity obtains the corresponding relation.

For example, the first management function entity may associate or map the NSI ID with the NSSI ID1, or with the NSSI ID2, or with the NSSI ID2. x.

It should be understood that the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Fig. 7 is a schematic interaction diagram of another example 700 of managing network slices according to an embodiment of the application. As shown in fig. 7, the method 700 includes:

s701, the first management function entity determines to modify the first network slice instance.

It should be noted that, here, the modification of the first network slice instance may specifically be to modify the network slice subnet instances included in the first network slice instance. For example, the NSMF determines that the NSI needs to be modified, which in turn is composed of one or more NSSIs, so that the corresponding NSSI can be modified.

For example, the identification of the first network slice instance is an NSI ID.

Specifically, when determining to modify the first network slice instance, the first management function entity may decompose the modification requirement into the network slice subnet instances, for example, into network slice subnet instance 1 and network slice subnet instance 2, and then determine to modify network slice subnet instance 1 corresponding to NSSI ID1 and network slice subnet instance 2 corresponding to NSSI ID2 or NSSI ID2.x according to the correspondence (NSI ID- > NSSI ID 1; NSI ID- > NSSI ID2 or NSSI ID2. x).

S702, the first management function entity sends a first modification request to the second management function entity 1.

Correspondingly, the second management functional entity 1 receives the first modification request sent by the first management functional entity.

Wherein the first modification request is used for requesting the second management function entity 1 to modify the network slice subnet instance 1 corresponding to the NSSI ID 1.

In one possible design, the first modification request includes the NSSI ID 1. In one possible design, the first modification request may also include an NSI ID.

S703, the first management functional entity sends a second modification request to the second management functional entity 2.

Correspondingly, the second management function entity 2 receives the second modification request sent by the first management function entity.

Wherein the second modification request is used for requesting the second management function entity 2 to modify the network slice subnet instance 2 corresponding to the NSSI ID2.

In one possible design, the second modification request includes NSSI ID2 or NSSI ID2. x. Here, the NSSI ID2 or NSSI ID2.x included in the second modification request coincides with the content fed back by the second management functional entity 2. For example, if the second management functional entity 2 feeds back the NSSI ID2 to the first management functional entity, the second modification request includes the NSSI ID 2; if the second management function entity 2 feeds back NSSI id2.x to the first management function entity, the second modification request includes NSSI id2. x. In one possible design, the first modification request may also include an NSI ID.

S704, the second management function entity 1 modifies the network slice subnet instance 1.

S705, the second management functional entity 1 sends a first modification completion message to the first management functional entity.

Correspondingly, the first management function entity receives the first modification completion message sent by the second management function entity 1.

Wherein the first modification completion message is used for feeding back that the network slice subnet instance 1 is modified.

In one possible design, the first modification complete message includes an identification of network slice subnet instance 1, such as NSSI ID 1. In one possible design, the first modification completion message may further include an identification NSI ID of the network slice instance.

S706, the second management function entity 2 modifies the network slice subnet instance 2.

S707, the second management function entity 2 sends a second modification completion message to the first management function entity.

Correspondingly, the first management function entity receives the second modification completion message sent by the second management function entity 2.

Wherein the second modification completion message is used for feeding back that the network slice subnet instance 2 has been modified.

In one possible design, the second modification complete message includes an identification of network slice subnet instance 2, such as NSSI ID2 or NSSI ID2. x. In one possible design, the second modification completion message may further include an identification NSI ID of the network slice instance.

It should be understood that fig. 7 illustrates an example of modifying a network slice subnet, and the modification process may also be other management processes, such as termination, monitoring, measurement, and the like, which is not limited thereto.

The above-mentioned process of modifying the network slice subnet instance by the first management function entity according to the corresponding relationship is described in fig. 7. It should be understood that the flow described above in fig. 7 may be used in combination with the flow described above in fig. 6.

Fig. 8 is a schematic interaction diagram of yet another example 800 of managing network slices according to an embodiment of the application. As shown in fig. 8, the method 800 includes:

s801, the second management functional entity sends the capability opening information to the first management functional entity.

Correspondingly, the first management function entity receives the capability opening information sent by the second management function entity.

The capability openness information includes description information of the network slice subnet instance that the second management function entity can support, such as information of network slice subnet instance identification, type, capacity, capability, and the like.

In one possible design, the capability openness information includes an identification of network slice subnet instance 1, such as NSSI ID 1.

In a possible design, the second management function entity includes a network slice subnet instance shared by multiple network slice instances, and then the capability openness information may further provide shared information, such as whether the network slice subnet instance is shared or not, or by which network slice instances the shared network slice subnet instance is shared.

S802, the first management function entity generates a first identifier when creating the first network slice instance.

In one possible design, after creating the first network slice instance, the first management function entity decides to use network slice subnet instance 1 to compose the first network slice instance according to the requirements for the network slice subnet instance and the information of the several network slice subnet instances provided by the capability openness message.

S803, the first management function entity sends a use request to the second management function entity.

Correspondingly, the second management function entity receives the use request sent by the first management function entity.

Wherein the usage request is for requesting a network slice subnet instance NSSI managed using a second management function entity.

In one possible design, the usage request carries an identifier of the network slice subnet instance 1, such as NSSI ID1, and a requirement description for NSSI, such as SLA information or SLR information.

In one possible design, the usage request may also carry an identifier of the first network slice instance, such as an NSI ID.

It should be noted that the request sent by the first management function entity to the second management function entity may be carried in different types of messages, such as NSSI use/reuse request message, NSSI creation request message, NSSI modification request message.

It should be noted that S803 and S801 may have no coupling relationship or no correlation. Specifically, even if the first management function entity does not receive the capability opening message, the first management function entity can also send a use request to the second management function entity; alternatively, the capability openness message may be received, and then the usage request may be sent to the second management function entity, which is not limited to this.

It should be understood that fig. 8 merely illustrates one possibility and does not limit the scope of the embodiments of the present application.

S804, the second management function entity carries out corresponding configuration according to the use request, so that the network slice subnet example 1 becomes a part of the first network slice example.

S805, the second management function entity sends a configuration complete message to the first management function entity.

Correspondingly, the first management function entity receives the configuration completion message sent by the second management function entity.

Wherein, the configuration completion message is used for feeding back that the network slice subnet instance 1 is configured completely.

In one possible design, the configuration complete message includes the NSSI ID1 and/or the NSI ID.

S806, the first management function entity generates the corresponding relation.

The first management function entity associates or maps the identity of the first network slice instance with network slice subnet instance 1. For example, the first management function entity maps the NSI ID with the NSSI ID 1.

It should be understood that the first management function entity may also learn the identity of the network slice subnet instance 1 in other ways.

The above-mentioned process of the first management functional entity obtaining the first identifier and the second identifier and generating the corresponding relationship is described in fig. 8. It should also be understood that the flow in fig. 8 described above may be used in combination with fig. 6 described above, and the steps in fig. 6 may be performed after the above correspondence is obtained in fig. 8.

The method for managing network slices according to the embodiment of the present application is described in detail above with reference to fig. 1 to 8, and the apparatus for managing network slices according to the embodiment of the present application is described in detail below with reference to fig. 9 to 12.

Fig. 9 shows a schematic block diagram of an apparatus 900 for managing network slices according to an embodiment of the present application. The apparatus 900 is configured to execute the method or steps corresponding to the first management function entity. Alternatively, the modules in the apparatus 900 may be implemented by software. The corresponding function of each module is used for realizing the network slice management function. The apparatus 900 may be installed in a general-purpose computer device. As shown in fig. 9, the apparatus 900 includes:

a processing module 910 configured to determine a management network slice instance, the network slice instance comprising at least one network slice subnet instance;

a transceiver module 920, configured to send a first management request to a second management function entity, where the first management request includes an identifier for identifying one or more network slice subnet instances of a network slice instance, and the first management request is used to request processing on the one or more network slice subnet instances;

the transceiver module 920 is further configured to receive a first management request response message sent by the second management function entity, where the first management request response message is used to instruct the second management function entity to complete processing on the one or more network slice subnet instances.

In one possible design, the processing includes at least one of modifying, monitoring, terminating, and measuring.

In one possible design, before sending the first management request to the second management function entity, the processing module 910 is further configured to: and acquiring the identifier.

In one possible design, the transceiver module 920 is specifically configured to:

and receiving the identification sent by the second management function entity.

In one possible design, the transceiver module 920 is further configured to:

sending a second management request to the second management function entity, the second management request requesting the second management function entity to create the one or more network slice subnet instances;

the transceiver module 920 is specifically configured to:

receiving a second management request response message sent by the second management function entity, where the second management request response message is used to indicate that the second management function entity has completed creating the one or more network slice subnet instances, and the second management request response message includes the identifier.

and receiving a capability openness message sent by the second management function entity, where the capability openness message is used to indicate information of the network slice subnet instances supported by the second management function entity, and the capability openness message includes the identifier.

In one possible design, the transceiver module 920 is further configured to:

sending a third management request to the second management function entity, the third management request requesting use of the one or more network slice subnet instances from the second management function entity, the third management request including the second identification; and receiving a third management request response message sent by the second management function entity, wherein the third management request response message is used for indicating the second management function entity to inform the network slice instance that the one or more network slice subnet instances can be used.

It should be understood that the apparatus 900 according to the embodiment of the present application may correspond to the first management function entity in the management network slice of the foregoing method embodiment, and the above and other management operations and/or functions of each module in the apparatus 900 are respectively for implementing corresponding steps of each foregoing method, so that beneficial effects in the foregoing method embodiment may also be implemented, and for brevity, no further description is provided herein.

It should also be understood that the processing module in the embodiments of the present application may be implemented by a processor, and the transceiver module may be implemented by a transceiver.

Fig. 10 shows a schematic block diagram of an apparatus 1000 for managing network slices according to another embodiment of the present application. The apparatus 1000 is configured to execute the method or steps corresponding to the foregoing second management function entity. Alternatively, the modules in the apparatus 1000 may be implemented by software. The corresponding function of each module is used for realizing the network slice management function. The apparatus 1000 may be installed in a general-purpose computer device. As shown in fig. 10, the apparatus 1000 includes:

a transceiver module 1010, configured to receive a first management request sent by a first management function entity, where the first management request includes an identifier for identifying one or more network slice subnet instances of a network slice instance, and the first management request is used to request processing on the one or more network slice subnet instances;

a processing module 1020, configured to process the one or more network slice subnet instances according to the first management request;

the transceiver module 1010 is further configured to send a first management request response message to the first management function entity, where the first management request response message is used to indicate that the processing of the one or more network slice subnet instances is completed.

In a possible design, before the second management function entity receives the first management request sent by the first management function entity, the transceiver module 1010 is further configured to:

and sending the identification to the first management function entity.

In one possible design, the transceiver module 1010 is specifically configured to:

receiving a second management request sent by the first management function entity, wherein the second management request is used for requesting the second management function entity to create the one or more network slice subnet instances;

the processing module 1020 is specifically configured to create or configure the one or more network slice subnet instances for the first management function entity according to the second management request;

wherein the transceiver module 1010 is further configured to: sending a second management request response message to the first management function entity, the second management request response message being used for indicating that the second management function entity completes the creation or configuration of the one or more network slice subnet instances, wherein the second management request response message includes the identifier.

and sending a capability openness message to the first management function entity, wherein the capability openness message is used for indicating information of the network slice subnet instances supported by the second management entity, and the capability openness message comprises the identifier.

In a possible design, after the second management function entity sends the capability openness message to the first management function entity, the transceiver module 1010 is further configured to:

receiving a third management request sent by the first management function entity, wherein the third management request is used for requesting the second management function entity to use the one or more network slice subnet instances;

the processing module 1020 is specifically configured to configure the one or more network slice subnet instances for the first management function entity;

the transceiver module 1010 is further configured to send a third management request response message to the first management function entity, where the third management request response message is used to notify the network slice instance that the one or more network slice subnet instances can be used.

It should be understood that the apparatus 1000 according to the embodiment of the present application may correspond to the second management function entity in the management network slice of the foregoing method embodiment, and the above and other management operations and/or functions of each module in the apparatus 1000 are respectively for implementing corresponding steps of each foregoing method, so that beneficial effects in the foregoing method embodiment may also be implemented, and for brevity, no further description is provided herein.

Fig. 11 is a block diagram illustrating an apparatus 1100 for managing network slices according to an embodiment of the present disclosure. The apparatus 1100 for managing a network slice shown in fig. 11 includes: a processor 1101, a memory 1102, and a transceiver 1103.

The processor 1101, memory 1102, and transceiver 1103 communicate with each other, passing control and/or data signals, over the internal connection paths. In one possible design, the processor 1101, the memory 1102, and the transceiver 1103 may be implemented by a chip. The memory 1102 may store program code, which the processor 1101 calls to implement the corresponding functions of the apparatus for managing network slices.

The processor 1101 is configured to:

determining to manage a first network slice instance, the first network slice instance comprising at least one network slice subnet instance;

sending, by the transceiver 1103, a first management request to a second management function entity, where the first management request includes the second identifier, and the first management request is used to request processing of a first network slice subnet instance of a first network slice instance, where the second identifier is used to identify the first network slice subnet instance, and the first network slice subnet instance is one of one or more network slice subnet instances included in the first network slice instance;

and receiving, by the transceiver 1103, a first management request response sent by the second management function entity

The first management request response message is used to instruct the second management function entity to complete the processing of the first network slice subnet instance.

It is understood that although not shown, the apparatus 1100 for managing network slices may also include other devices, such as input devices, output devices, batteries, etc.

Optionally, in some embodiments, the memory 1102 may store some or all of the instructions for performing the method performed by the first management function entity in the aforementioned methods. The processor 1101 may execute the instructions stored in the memory 1102 to complete the steps performed by the first management functional entity in the foregoing method in combination with other hardware (e.g., the transceiver 1103), and specific working procedures and beneficial effects may be referred to the description in the foregoing method embodiments.

Fig. 12 is a block diagram of an apparatus 1200 for managing network slices according to another embodiment of the present application. The apparatus 1200 for managing a network slice shown in fig. 12 includes: a processor 1201, a memory 1202, and a transceiver 1203.

The processor 1201, the memory 1202, and the transceiver 1203 communicate with each other via internal connection paths, passing control and/or data signals. In one possible design, the processor 1201, the memory 1202, and the transceiver 1203 may be implemented as a chip. The memory 1202 may store program codes, which the processor 1201 calls to implement the corresponding functions of the apparatus for managing network slices.

The processor 1201 is configured to:

receiving, by the transceiver 1203, a first management request sent by a first management function entity, where the first management request includes a second identifier, the first management request is used to request processing of a first network slice subnet instance of a first network slice instance, and the second identifier is used to identify the first network slice subnet instance, where the first network slice subnet instance is one of one or more network slice subnet instances included in the first network slice instance;

processing the first network slice subnet instance according to the first management request;

sending, by the transceiver 1203, a first management request response message to the first management function entity, where the first management request response message is used to indicate that processing of the first network slice subnet instance is completed.

It is understood that, although not shown, the apparatus 1200 for managing network slices may also include other devices, such as input devices, output devices, batteries, etc.

In one possible design, in some embodiments, memory 1202 may store instructions for performing one of the methods described above as being performed by the second management function entity. The processor 1201 may execute the instructions stored in the memory 1202 to complete the steps performed by the second management function entity in the foregoing method in combination with other hardware (e.g., the transceiver 1203), and specific working procedures and beneficial effects may be referred to the description in the foregoing method embodiment.

The embodiment of the present application further provides a system for managing network slices, which includes a device corresponding to the first management function entity and a device corresponding to the second management function entity in the foregoing embodiments.

The method disclosed in the embodiments of the present application may be applied to a processor, or may be implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a general-purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a Digital Signal Processor (DSP), a Microcontroller (MCU), a programmable logic controller (PLD), or other integrated chip. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a Random Access Memory (RAM), a flash memory, a read-only memory (ROM), a programmable ROM, an electrically erasable programmable memory, a register, or other storage media that are well known in the art. The storage medium is located in a memory, and a processor reads instructions in the memory and combines hardware thereof to complete the steps of the method.

It should be understood that, in the embodiment of the present application, the numbers "first" and "second" … are introduced only for distinguishing different objects, such as different "identifications", or different "management requests", and do not limit the scope of the embodiment of the present application.

It should also be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

It should also be understood that the term "and/or" herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of managing network slices, comprising:

a first management function entity receives a capability openness message sent by a second management function entity, wherein the capability openness message is used for indicating information of network slice subnet instances supported by the second management function entity, and the capability openness message comprises identifications of one or more network slice subnet instances of the network slice instances;

the first management function entity sends a first management request to the second management function entity, wherein the first management request comprises the identifier, and the first management request is used for requesting to process the one or more network slice subnet instances;

2. The method of claim 1, wherein the processing comprises at least one of modifying, monitoring, terminating, and measuring.

3. The method of claim 1, further comprising:

the first management function entity sending a third management request to the second management function entity, the third management request requesting the second management function entity to use the one or more network slice subnet instances, the third management request including the identification;

4. A method of managing network slices, comprising:

the second management function entity sends a capability opening message to the first management function entity, wherein the capability opening message is used for indicating information of the network slice subnet instances supported by the second management function entity, and the capability opening message comprises identification of one or more network slice subnet instances of the network slice instances;

the second management function entity receives a first management request sent by the first management function entity, wherein the first management request comprises the identifier, and the first management request is used for requesting to process the one or more network slice subnet instances;

5. The method of claim 4, wherein the processing comprises at least one of modifying, monitoring, terminating, and measuring.

6. The method of claim 4, further comprising:

7. An apparatus for managing network slices, comprising:

a transceiver for receiving and transmitting a signal from the wireless communication device,

a processor coupled to the transceiver for performing the steps of:

receiving, by the transceiver, a capability openness message sent by a second management function entity, the capability openness message being used to indicate information of network slice subnet instances supported by the second management function entity, the capability openness message including an identification of one or more network slice subnet instances of a network slice instance;

sending, by the transceiver, a first management request to the second management function entity, the first management request including the identification, the first management request requesting processing of the one or more network slice subnet instances;

and receiving, by the transceiver, a first management request response message sent by the second management function entity, the first management request response message being used to instruct the second management function entity to complete processing of the one or more network slice subnet instances.

8. The apparatus of claim 7, wherein the processing comprises at least one of modifying, monitoring, terminating, and measuring.

9. The apparatus of claim 7, wherein the processor is specifically configured to:

sending, by the transceiver, a third management request to the second management function entity, the third management request requesting use of the one or more network slice subnet instances from the second management function entity, the third management request including the identification;

and receiving, by the transceiver, a third management request response message sent by the second management function entity, the third management request response message being used by the second management function entity to inform the network slice instance that the one or more network slice subnet instances are available for use.

10. The apparatus of any one of claims 7 to 9, further comprising:

a memory for storing instructions that, when read by the processor, cause the processor to perform the steps of any of claims 7 to 9.

11. An apparatus for managing network slices, comprising:

a processor coupled to the transceiver for performing the steps of:

sending, by the transceiver, a capability openness message to a first management function entity, the capability openness message indicating information of network slice subnet instances supported by a second management function entity, the capability openness message including an identification of one or more network slice subnet instances of a network slice instance;

receiving, by the transceiver, a first management request sent by the first management function entity, where the first management request includes the identifier, and the first management request is used to request processing of the one or more network slice subnet instances;

processing the one or more network slice subnet instances according to the first management request;

sending, by the transceiver, a first management request response message to the first management function entity, the first management request response message indicating completion of processing of the one or more network slice subnet instances.

12. The apparatus of claim 11, wherein the processing comprises at least one of modifying, monitoring, terminating, and measuring.

13. The apparatus of claim 11, wherein the processor is further configured to:

receiving, by the transceiver, a third management request sent by the first management function entity, the third management request requesting use of the one or more network slice subnet instances from the second management function entity, the third management request including the identification;

configuring the one or more network slice subnet instances for the first management function entity;

sending, by the transceiver, a third management request response message to the first management function entity, the third management request response message for notifying the network slice instance that the one or more network slice subnet instances are available.

14. The apparatus of any one of claims 11 to 13, further comprising:

a memory for storing instructions that, when read by the processor, cause the processor to perform the steps of any of claims 11 to 13.

15. A computer-readable storage medium comprising a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 6.