WO2019056954A1 - Network slice management method and device - Google Patents

Abstract

Provided in the present application are a network slice management method and device, the method comprising: a first management function entity sends a first management request to a second management function entity, the first management request comprising an identifier used for identifying one or more network slice subnet instances of a network slice instance, the first management request being 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 function entity, the first management request response message being used to indicate that the second management function entity has completed processing of the one or more network slice subnet instances, thereby managing network slice subnet instances efficiently so as to manage the network slice instances.

Description

Method and apparatus for managing network slices

The present application claims priority to Chinese Patent Application No. PCT Application No. No. No. No. No. No. No. No. No. No. No. No. .

Technical field

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

Background technique

With the rapid development of mobile communications, digital transformation involves almost all traditional industries. However, the traditional cellular network architecture can only provide a unified network service, and it is difficult to meet the extremely different communication requirements brought about by the digital transformation wave, including functional differences and performance differences. In a 5th generation (5G) communication system, the network will be abstracted as a "network slice", and a network slice satisfies the connection communication service requirements of a certain class or a use case. A 5G system can consist of a large number of network slices that meet different connectivity capabilities.

Network Slicing Instance A real-running logical network created by the network management system to meet certain network characteristics or service requirements. A network management system may create one or more network slice instances and manage them at the same time, including performance monitoring, fault management, modification, etc. during the running of the network slicing instance. A complete network slicing instance is capable of providing complete end-to-end network services, and the network slicing instances may be network slicing subnet instances and/or network functions. In order to provide differentiated communication requirements quickly and flexibly, network slicing needs to be managed efficiently. However, the prior art network management architecture does not provide a complete solution for network slice management. Therefore, there is a need to propose a solution to solve the problem of how to effectively manage network slicing.

Summary of the invention

The present application provides a method and apparatus for managing network slices, which can implement efficient management of network slice subnet instances, thereby achieving the purpose of managing network slice instances.

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

The first management function entity sends a first management request to the second management function entity, where the first management request includes an identifier of one or more network slice subnet instances for identifying a network slice instance, the first management Requesting to request processing of the one or more network slice subnet instances;

Receiving, by the first management function entity, a first management request response message sent by the second management function entity, where the first management request response message is used to indicate that the second management function entity completes the one or more Processing of network slice subnet instances.

In the embodiment of the present application, the first management function entity processes one or more network slice subnet instances of the network slice instance by using the identifier, and performs corresponding management operations to implement the network slice subnet instance. Efficient management to achieve the purpose of managing network slicing instances.

In one possible design, an identifier may indicate multiple network slice subnet instances, such as grouping network slice subnet instances, which may be group identifiers; or each identity may indicate a network slice subnet instance.

In a 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 including at least one network slice subnet instance.

In one possible design, the first identification is used to identify the network slice instance. The identifier of one or more network slice subnet instances used to identify the network slice instance may be the second identifier. The first identifier and the second identifier 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 using software, that is, the network slice management function is implemented by software. In one possible design, the above software can be installed on a general purpose computer hardware device.

In a possible design, the first management function entity may send the first management request to the plurality of second management function entities at the same time, and may request the corresponding second management function entity in parallel, thereby slicing the plurality of network The network instance is processed to improve management efficiency.

In a 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 a first management request to another second management function entity, so that the network slice subnet can be implemented. The examples are processed in a certain order.

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

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

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

The first management function entity acquires the first identifier;

The first management function entity acquires the second identifier.

In a possible design, the first identifier may be obtained by a first management function entity from a local or other management function entity, or may be generated when a network slice instance is created. Therefore, the acquisition method of the first identifier is relatively flexible.

In a possible design, the first management function entity obtains the second identifier, including:

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

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

In one possible design, the method further includes:

The first management function entity sends a second management request to the second management function entity, where the second management request is used to request the second management function entity to create the one or more network slice subnet instances;

The first management function entity receives the second identifier sent by the second management function entity, including:

Receiving, by the first management function entity, 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 the one or more The creation of a network slice subnet instance, wherein the second management request response message includes the second identity.

Here, the first management function entity may acquire the second identifier by creating a 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 function entity may obtain the correspondence according to the first identifier and the second identifier.

In a possible design, the first management function entity receives the second identifier sent by the second management function entity, including:

Receiving, by the first management function entity, a capability open message sent by the second management function entity, where the capability open message is used to indicate information about a network slice subnet instance supported by the second management function entity, where the capability is open The message includes the second identification.

In one possible design, the capability open message may include at least one of the following: an identification of the one or more network slice subnet instances, a type of the one or more network slice subnet instances, Information such as the capabilities of the one or more network slice subnet instances, the capacity of the one or more network slice subnet instances, and the like. In a possible design, the capability open message further includes information about the type, identifier, capability, capacity, and the like of other network slice subnet instances supported by the second management function entity, which is not limited thereto.

Therefore, the first management function entity may acquire the second identifier by using a capability open message.

In one possible design, the method further includes:

The first management function entity sends a third management request to the second management function entity, where the third management request is used to request the second management function entity to use the one or more network slice subnet instances The third management request includes the second identifier;

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

In a possible design, 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 use request. The third management request includes a requirement description for one or more network slice subnet instances, where the third management request carries a second identifier.

Specifically, 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 notify the first management function entity that the one or more network slice subnet instances have been completed. Processing such that the one or more network slice subnet instances become part of a network slice instance. In the embodiment of the present application, “the network slice instance can use one or more network slice subnet instances” and “one or more network slice subnet instances become part of the network slice instance” have the same meaning, that is, one or more networks. A sliced subnet instance can serve 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 function entity may obtain the correspondence according to the first identifier and the second identifier.

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

Alternatively, although the first management function entity has obtained the foregoing second identifier by using the foregoing second management request response message, the first management function entity may have released the first part without using the network slice subnet instance. The second identified scenario, the first management function entity can still send the foregoing third management request to the second management function entity.

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

Receiving, by the second management function entity, a first management request sent by the first management function entity, where the first management request includes an identifier of one or more network slice subnet instances for identifying a network slice instance, the first management request Used to request processing of the one or more network slice subnet instances;

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

The second management function entity sends 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 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 realizing The purpose of managing network tile instances.

In one possible design, an identifier may indicate multiple network slice subnet instances, such as grouping network slice subnet instances, which may be group identifiers; or each identity may indicate a network slice subnet instance.

In one possible design, the first identifier is used to identify the network slice instance, and the identifier of one or more network slice subnet instances used to identify the network slice instance may be the second identifier. The first identifier and the second identifier 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 using software, that is, the network slice management function is implemented by software. In one possible design, the above software can be installed on a general purpose computer hardware device.

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

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

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

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

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

In one possible design, the method further includes:

Receiving, by the second management function entity, a second management request sent by the first management function entity, where the second management request is used to request the second management function entity to create the one or more network slice subnet instances ;

Creating, by the second management function entity, the one or more network slice subnet instances for the first management function entity according to the second management request;

The second management function entity sends the second identifier to the first management function entity, including:

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 the one or more network slicers The creation or configuration of the network instance, wherein the second management request response message includes the second identifier.

Here, after receiving the foregoing second management request, the second management function entity may create or configure the one or more networks for the first management function entity according to the requested content and the managed network slice subnet instance. Slice a subnet instance.

Therefore, the second management function entity may notify the first management function entity of the second identifier by using the foregoing second management request response message.

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

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

In a possible design, the second management function entity sends the second identifier to the first management function entity, including:

The second management function entity sends a capability open message to the first management function entity, where the capability open message is used to indicate information about a network slice subnet instance supported by the second management entity, where the capability open message includes The second identifier.

Therefore, the second management function entity can notify the first management function entity of the second identifier by using the force open message.

In one possible design, the capability open message may include at least one of the following: an identification of the one or more network slice subnet instances, a type of the one or more network slice subnet instances, Information such as the capabilities of the one or more network slice subnet instances, the capacity of the one or more network slice subnet instances, and the like. In a possible design, the capability open message further includes information about the type, identifier, capability, capacity, and the like of other network slice subnet instances supported by the second management function entity, which is not limited thereto.

In one possible design, the method further includes:

Receiving, by the second management function entity, a third management request sent by the first management function entity, where the third management request is used to request the second management function entity to use the one or more network slice subnets Instance

The second management function entity configures 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, where the third management request response message is used to notify the network slice instance to use the one or more network slices. Network instance.

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

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

Specifically, 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 notify the first management function entity that the one or more network slice subnet instances have been completed. Processing such that the one or more network slice subnet instances become 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, the second management function entity may send a third management request response message to the first management function entity, so that the first management function entity may generate the first identifier and the second identifier according to the third management request response message. Correspondence.

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

Alternatively, although the first management function entity has obtained the foregoing second identifier by using the foregoing second management request response message, there may be a case where the first management function entity has not used the one or more network slice subnet instances. The scenario of the second identifier is released, and the first management function entity may still send the foregoing third management request to the second management function entity.

In a third aspect, an apparatus for managing a network slice is provided for performing the method of any of the first aspect or the first aspect of the first aspect. In particular, the apparatus comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.

In a fourth aspect, an apparatus for managing a network slice is provided for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect. In particular, the apparatus comprises means for performing the method of any of the possible implementations of the second aspect or the second aspect described above.

In a fifth aspect, an apparatus for managing a network slice is provided, the apparatus comprising a processor, a memory, and a transceiver. The processor is coupled to the memory and the transceiver. The memory is for storing instructions for the processor to execute, and the transceiver is for communicating with other network elements under the control of the processor. When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.

In a sixth aspect, an apparatus for managing a network slice is provided, the apparatus comprising a processor, a memory, and a transceiver. The processor is coupled to the memory and the transceiver. The memory is for storing instructions for the processor to execute, and the transceiver is for communicating with other network elements under the control of the processor. When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the possible implementations of the second aspect or the second aspect.

In a seventh aspect, a computer readable storage medium storing a program for causing an apparatus for managing network slicing to perform the first aspect described above, and any of the various implementations thereof The method of network slicing.

In an eighth aspect, a computer readable storage medium is provided, the computer readable storage medium storing a program that causes an apparatus for managing network slicing to perform the second aspect described above, and management of any of the various implementations thereof The method of network slicing.

A ninth aspect, a communication chip is provided, wherein instructions are stored, when executed on a first management function entity, causing the communication chip to perform the first aspect or any of the possible implementations of the first aspect method.

According to a tenth aspect, there is provided a communication chip, wherein instructions are stored, which when executed on a second management function entity, cause the communication chip to perform any of the second aspect or any of the possible implementations of the second aspect method.

In an eleventh aspect, a system for managing a network slice is provided, the system comprising the apparatus of any of the possible implementations of the fourth aspect or the fourth aspect, and any one of the fifth aspect or the fifth aspect The device in an implementation manner; or the system includes the device in any one of the possible implementations of the sixth aspect or the sixth aspect, and the device in any one of the seventh aspect or the seventh aspect.

According to 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 or any possible implementation thereof.

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

The first management function entity acquires a second identifier, where the second identifier is used to identify one or more network slice subnet instances of the network slice instance;

The first management function entity manages the one or more network slice subnet instances by using the second identifier when managing the network slice instance.

In the embodiment of the present application, the first management function entity processes one or more network slice subnet instances according to the second identifier by acquiring the second identifier, and performs corresponding management operations to implement the network slice subnet instance. Efficient management to achieve the purpose of managing network slicing instances.

In one possible design, the method further includes:

The first management function entity acquires a first identifier, where the first identifier is used to identify the network slice instance, and the first identifier has a corresponding relationship with the second identifier.

In a possible design, the first management function entity obtains the first identifier, including:

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

In a possible design, the first identifier may be obtained by a first management function entity from a local or other management function entity, or may be generated when a network slice instance is created. Therefore, the acquisition method of the first identifier is relatively flexible.

In a possible design, the first management function entity obtains the second identifier, including:

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

In one possible design, the method further includes:

The first management function entity sends a second management request to the second management function entity, where the second management request is used to request the second management function entity to create the one or more network slice subnet instances;

The first management function entity receives the second identifier sent by the second management function entity, including:

Receiving, by the first management function entity, 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 the one or more The creation of a network slice subnet instance, wherein the second management request response message includes the second identity.

Here, the first management function entity may acquire the second identifier by creating a 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 function entity may obtain the correspondence according to the first identifier and the second identifier.

In a possible design, the first management function entity receives the second identifier sent by the second management function entity, including:

Receiving, by the first management function entity, a capability open message sent by the second management function entity, where the capability open message is used to indicate information about a network slice subnet instance supported by the second management function entity, where the capability is open The message includes the second identification.

Therefore, the first management function entity may acquire the second identifier by using a capability open message.

In one possible design, the method further includes:

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

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

In a possible design, the first management function entity manages the one or more network slice subnet instances by using the second identifier, including:

The first management function entity sends a first management request to the second management function entity, where the first management request is used to request the second management function entity to perform the one or more network slice subnet instances Processing, where the processing includes at least one of modifying, monitoring, terminating, and measuring, wherein the first management request includes the second identifier;

The method further includes:

Receiving, by the first management function entity, a first management request response message sent by the second management function entity, where the first management request response message is used to indicate that the second management function entity completes the one or more The processing of the network slice subnet instance.

In a possible design, the first management function entity may send the first management request to the plurality of second management function entities at the same time, and may request the corresponding second management function entity in parallel, thereby slicing the plurality of network The network instance is processed to improve management efficiency.

In a 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 a first management request to another second management function entity, so that the network slice subnet can be implemented. The examples are processed in a certain order.

In a fourteenth aspect, a method of managing network slices is provided, comprising:

The second management function entity generates an identifier of one or more network slice subnet instances for identifying the network slice instance;

Sending, by the second management function entity, the identifier to the first management function entity;

When the second management function entity receives the first management request sent by the first management function entity, the second management function entity performs the one or more network slice subnet instances corresponding to the identifier Processing, the identifier is included in the first management request.

In the embodiment of the present application, the second management function entity receives the management request sent 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 the network slicing subnet. Efficient management of instances to achieve the purpose of managing network slicing instances.

In one possible design, the method further includes:

Receiving, by the second management function entity, a second management request sent by the first management function entity, where the second management request is used to request 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 first management request;

The sending, by the second management function entity, the identifier to the first management function entity, including:

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 the one or more network slicers Creation or configuration of a network instance, wherein the second management request response message includes the identification.

Here, after receiving the foregoing second management request, the second management function entity may create or configure the one or more networks for the first management function entity according to the requested content and the managed network slice subnet instance. Slice a subnet instance.

Therefore, the second management function entity may notify the first management function entity of the identifier by using the second management request response message.

In a possible design, the second management function entity sends the identifier to the first management function entity, including:

The second management function entity sends a capability open message to the first management function entity, where the capability open message is used to indicate information about a network slice subnet instance supported by the second management entity, where the capability open message includes The identification.

Therefore, the second management function entity can notify the first management function entity of the identifier by using the force open message.

In one possible design, the method further includes:

Receiving, by the second management function entity, a third management request sent by the first management function entity, where the third management request is used to request the second management function entity to use the one or more network slice subnets An example, the third management request includes 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, where the third management request response message is used by the second management function entity to notify the first network slice instance to use The one or more network slice subnet instances.

In one possible design, the method further includes:

Receiving, by the second management function entity, the first management request sent by the first management function entity, where the first management request is used to request to process the one or more network slice subnet instances, where The processing includes at least one of modifying, monitoring, terminating, and measuring, wherein 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, where the first management request response message is used to indicate that the completion of the one or more network slice subnet instances deal with.

In a fifteenth aspect, there is provided apparatus for managing a network slice for performing the method of any of the thirteenth aspect or any of the possible implementations of the thirteenth aspect. In particular, the apparatus comprises means for performing the method of any of the above-described thirteenth aspect or any of the possible implementations of the thirteenth aspect.

In a sixteenth aspect, an apparatus for managing a network slice is provided for performing the method of any of the above-described fourteenth or fourteenth aspects. In particular, the apparatus comprises means for performing the method of any of the above-described fourteenth or fourteenth aspects of the fourteenth aspect.

In a seventeenth aspect, an apparatus for managing a network slice is provided, the apparatus comprising a processor, a memory, and a transceiver. The processor is coupled to the memory and the transceiver. The memory is for storing instructions for the processor to execute, and the transceiver is for communicating with other network elements under the control of the processor. When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the thirteenth aspect or any of the possible implementations of the thirteenth aspect.

In an eighteenth aspect, an apparatus for managing a network slice is provided, the apparatus comprising a processor, a memory, and a transceiver. The processor is coupled to the memory and the transceiver. The memory is for storing instructions for the processor to execute, and the transceiver is for communicating with other network elements under the control of the processor. When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the fourteenth or fourteenth aspects.

A nineteenth aspect, a computer readable storage medium storing a program for causing a device for managing network slicing to perform the thirteenth aspect described above, and any of its various implementations A method of managing network slices.

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

A twenty-first aspect, a communication chip is provided, wherein instructions are stored, which, when run on a first management function entity, cause the communication chip to perform any of the thirteenth aspects or the thirteenth aspect described above The method in the implementation.

A twenty-second aspect, a communication chip is provided, wherein instructions are stored, which, when run on a second management function entity, cause the communication chip to perform any of the fourteenth or fourteenth aspects described above The method in the implementation.

A twenty-third aspect, a system for managing a network slice, the system comprising the device of any one of the fifteenth aspect or the fifteenth aspect, and the sixteenth or sixteenth aspect A device in any of the possible implementations; or the system includes the device of any one of the seventeenth or seventeenth aspects, and the eighteenth or eighteenth aspect A device in a possible implementation.

In a twenty-fourth 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 thirteenth aspect or the fourteenth aspect or any possible implementation thereof.

DRAWINGS

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

2 is a schematic interaction diagram of a method of managing network slices in accordance with an embodiment of the present application.

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

4 is a schematic interaction diagram of a method of managing network slices in accordance with still another embodiment of the present application.

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

6 is a schematic interaction diagram of one example of managing a network slice in accordance with an embodiment of the present application.

7 is a schematic interaction diagram of another example of managing a network slice in accordance with an embodiment of the present application.

FIG. 8 is a schematic interaction diagram of still another example of managing a network slice according to an embodiment of the present application.

9 is a schematic block diagram of an apparatus for managing network slices in accordance with an embodiment of the present application.

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

FIG. 11 is a structural block diagram of an apparatus for managing a network slice according to an embodiment of the present application.

FIG. 12 is a structural block diagram of an apparatus for managing a network slice according to another embodiment of the present application.

Detailed ways

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

The technical solutions of the embodiments of the present application can be applied to various communication systems or network management systems that support network slicing, such as a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), future fifth generation (5th generation, 5G) system or new radio (NR).

The terminal device in the embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or User device. 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), with wireless communication. Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks, or in future public land mobile networks (PLMNs) The terminal device and the like are not limited in this embodiment of the present application.

Embodiments of the present application relate to a network slice technology. Network slicing is a logical network that provides certain network capabilities and certain network characteristics. Network slicing is a concept of a logical network, which is implemented by a network slicing instance. A network slice instance contains several network function instances and the computing, storage, networking, and other resources required to form a deployed logical network. For example, in a 5G network, network slicing is an on-demand networking approach that provides operators with new services that can be adapted to changing user needs and quickly meet the needs of new applications.

The network slicing technology abstracts the 5G network physical infrastructure resources into multiple network slices according to the scene requirements. Each network slice performs customized tailoring of network functions and management of corresponding network functions according to the needs of the business scenario and the business model. A network slice can be thought of as an instantiated 5G network. Such a network structure allows operators to provide the network as a service to users, and can freely combine physical networks according to indicators such as rate, capacity, coverage, delay, reliability, security, and availability to meet different users. Claim.

It should be noted that the terms "network management architecture", "network system", "system" and the like may be replaced with each other. For ease of understanding, first introduce some of the terms that appear in this article:

Network slicing: Network slicing is a concept that refers to the customization of different logical networks based on different service requirements on a physical or virtual network infrastructure. The network slice can be a complete end-to-end network including the terminal, the access network, the transmission network, the core network and the application server, and can provide complete telecommunication services and have certain network capabilities. The network slice may also be any combination of the above-mentioned terminal, access network, transport network, core network, and part of the application server. A network slice may have one or more of the following characteristics: the access network may or may not slice. The access network may be shared by multiple network slices. Among them, the characteristics of different network slices and the network functions that make them up may be different.

Network slice template (NST): A method of generating a network slice instance to provide a reference for generating a network slice instance. The network slice template specifies how the network slice instance should be generated. For example, the network slicing module can indicate which network functions are included in the network slice, and key performance indicators (KPI) indicators that should be achieved.

Network slice instance (NSI): A real-world logical network that meets certain network characteristics or service requirements. A network slice instance may provide one or more services. A network sharding instance can be created by the network management system. A network management system may create multiple network shard instances and manage them at the same time, including performance monitoring and fault management during network snippet instance running. When multiple network slice instances coexist, some network resources and network functions may be shared between network slice instances. A network tile instance may or may not be created from a network tile template. A complete network slicing instance can provide complete end-to-end network services, and the network slicing instances can be network slice subnet instances (NSSI) and/or network functions (NF). . Network functions may include physical network functions and/or virtual network functions. The following are collectively referred to as physical network functions and/or virtual network functions as network functions.

Network-sliced subnet instance: A network-sliced subnet instance does not need to provide end-to-end complete network services. The network-sliced subnet instance can be a set of network functions of the same device vendor in the network sharding instance, or it can be divided into domains. A collection of network functions, such as a core network network slice subnet instance, an access network network slice subnet instance, or a collection of other ways, such as a deployment location. A network sliced subnet instance may be shared by multiple network slice instances. The proposed network slicing subnet instance can facilitate the management of the network management system. Wherein, one network slice subnet instance may be composed of several network slice subnet instances, each network slice subnet instance consisting of several network slice subnet instances and network functions not subdivided into network slice subnet instances; or A network slice subnet instance may also consist of only a few network functions.

Network function: It is a processing function in the network, which defines functional behaviors and interfaces. The network functions can be implemented by dedicated hardware or virtual functions on a common hardware platform. Therefore, from an implementation point of view, network functions can be divided into physical network functions and virtual network functions. From the perspective of usage, network functions can be divided into dedicated network functions and shared network functions. Specifically, for multiple (sub)network slice instances, different network functions may be used independently, such network functions are called exclusive network functions; or, the same network function may be shared, and the network function is called Shared network features.

The network segment management process includes: creating a network snippet instance, modifying the network snippet instance (including expanding, shrinking, modifying the topology, adding network functions, deleting network functions, etc.), and terminating the network snippet instance. In one possible design, management of network slice instances can be broken down into management of network slice subnet instances. It should be noted that the lifetimes of network slice instances and network slice subnet instances are independent. For example, terminating a network slice instance is not equivalent to terminating a network sliced subnet instance, but a network slice instance and a network slice subnet. There are administrative associations between instances. For example, creating a network slice instance may require creating one or more new network slice subnet instances. 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, the network slice management system architecture is first introduced in conjunction with FIG. 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 (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 may be connected through an interface (for example, Itf-csm).

It should be understood that the embodiment of the present application does not limit how each module in FIG. 1 corresponds to the existing network management system, or the position of each module in FIG. 1 in the 5G network management system is not limited. The above management functions will be described in turn below.

The communication service management function is mainly responsible for one or more of the following functions, for example, converting the communication service requirements of the operator and/or the third party customer into the requirements for network slicing, and through the interface with the NSMF to the NSMF Sending requirements for network slicing (eg, creating, terminating, modifying network slice instance requests, etc.), obtaining management data (eg, performance, fault data, etc.) of the network slice from the NSMF, and generating a communication service running on the network slice instance Management data, receiving subscription requirements of management data of network slice management data and/or communication services by operators and/or third party customers, and the like.

The network slice management function is mainly responsible for one or more of the following functions, for example, receiving the network slice requirement sent by the CSMF, and managing the life cycle, performance, fault, and the like of the network slice instance (hereinafter, the life cycle, performance, and failure) Management short name management), compiles the composition of the network slicing instance, decomposes the requirements of the network slicing instance as the requirements of each network slicing subnet instance and/or network function, and sends a network slicing subnet instance management request to each NSSMF. The network slice management function can 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 the network slice subnet requirement sent by the NSMF, managing the network slice subnet instance, orchestrating the composition of the network slice instance, and decomposing the network slice. The need for a subnet instance is a requirement for each network function and/or nested network slice subnet instance, and may send nested network slice subnet instance management requests to other NSSMFs. The network slice subnet management function can manage one or more network slice subnet instances.

The method for managing network slicing in the embodiment of the present application can be applied to the above network slice management system architecture. Alternatively, the method for managing a network slice 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 a network slice, 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 in the network slice management system architecture. Network management function. Alternatively, the first management function entity and the second management function entity may also be other physical devices that have corresponding functions in the 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 in accordance with an embodiment of the present application. As shown in FIG. 2, the method 200 includes:

S210. The first management function entity determines a management network slice instance, where the network slice instance includes at least one network slice subnet instance.

It should be understood that, in the specific implementation, the step S210 in the foregoing method 200 may or may not exist, and the embodiment of the present application does not limit this.

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

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

S220. The first management function entity sends a first management request to a second management function entity, where the first management request includes an identifier of one or more network slice subnet instances for identifying a network slice instance, where A management request is for requesting processing of the one or more network slice subnet instances. For the convenience of description, the description will be made by 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, which may be a group identity; or, each identity may indicate a Or multiple network slice subnet instances.

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 identifier and the second identifier have a corresponding relationship.

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

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

Specifically, the first management function entity may decompose the management requirement for the network slice instance onto multiple network slice subnet instances. 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. Determining, by the first management function entity, the network slice subnet instance included in the network slice instance according to the correspondence between the first identifier and the second identifier, and determining that one or more network slice subnet instances that are identified by the second identifier are needed Modifying and sending a first management request to the second management function entity to request processing of the one or more network slice subnet instances.

In a possible design, the foregoing 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 thereto.

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

In a possible design, before S220, the first management function entity may directly decide to modify one or more network slice subnet instances according to the management policy that it has, and the one or more network slice subnet instances may belong to one Or multiple network slice instances, or currently do not belong to any network slice instance. For example, the first management function entity can measure, monitor, and learn the operation of the network slice subnet instance.

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

The processing includes at least one of modifying, monitoring, terminating, and measuring.

S240, the second management function entity sends a first management request response message to the first management function entity, where the first management request response message is used to indicate completion of the one or more network slice subnet instances. deal with.

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

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

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

Specifically, the first management function entity may find one or more network slice subnet instances that need to be managed by using a correspondence between the first identifier and the second identifier, for example, the first identifier->the second identifier. Then, the first management function entity sends a first management request to the second management function entity to request the second management function entity to process the one or more network slice subnet instances, for example, the one or more The network slicing subnet instance performs management operations such as modification, monitoring, termination, and measurement. The second management function entity performs corresponding processing according to the content requested by the foregoing first management request, and feeds back a first management request response message to the first management function entity after the processing is completed, to notify the first management function entity that the completion is completed. deal with.

Therefore, the first management function entity determines, by using the correspondence between the first identifier and the second identifier, the one or more network slice subnet instances identified by the second identifier that are to be managed, and performs corresponding management operations to Efficient management of network slicing subnet instances is implemented to achieve the purpose of managing network slicing instances.

It should be understood that, in the embodiment of the present application, the first management function entity may send the first management request to multiple second management function entities at the same time, and may request the corresponding second management function entity in parallel, thereby performing one or more Network slice subnet instances are processed to improve management efficiency.

It should also be understood that the first management function entity may also 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 a first management request to another second management function entity, so that the network slice subnet can be implemented. The examples are processed in a certain order.

The first management function entity can manage the network slice subnet instance according to the correspondence between the first identifier and the second identifier. How the first management function entity acquires the first identifier and the second identifier will be described below.

FIG. 3 shows a schematic interaction diagram of a method 300 of managing network slices in accordance with another embodiment of the present application. As shown in FIG. 3, the method 300 includes:

S310. The first management function entity acquires a first identifier, where the first identifier is used to identify a network slice instance.

In one possible design, the first identification 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 multiple fields, such as a Public Land Mobile Network (PLMN) ID, a slice type slice type, a service type service type, a tenant ID, and a distinguisher differentiator.

Specifically, S310 includes:

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

Specifically, in order to meet the service requirement, the first management function entity may create a network slice instance and generate a first identifier to identify the network slice instance.

S320. The first management function entity acquires a second identifier, where the second identifier is used to identify one or more network slice subnet instances, where the network slice instance includes at least one network slice subnet instance.

The first management function entity determines that the network slice instance needs to be composed of at least one network slice subnet instance. For example, it can be determined by calculation.

In one possible design, the second identification 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 of the following fields, such as a PLMN ID, a slice subnet type, a slice identifier, and another identifier.

In a possible design, the foregoing second identifier may be obtained by the first management function entity, or may be obtained from a message sent by another management function entity, which is not limited. 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 foregoing second identity from the local.

In one possible design, the S320 includes:

S321. The second management function entity sends a 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.

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

It should be noted that the timing of sending the second identifier by the second management function entity is not limited in the embodiment of the present application. Specifically, the second management function entity may send the second identifier after receiving the request for creating a network slice subnet instance sent by the first management function entity, or may also create a network slice sent by the first management function entity. The second identifier is sent to the first management function entity in advance before the network instance requests. A detailed description will be given below.

In one possible design, as an embodiment, FIG. 4 illustrates a schematic flow 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 function entity sends a second management request to the second management function entity, where the second management request is used to request the second management function entity to create the one or more network slice subnet instances.

Correspondingly, the second management function entity is configured to receive the second management request sent by the first management function entity.

In a possible design, the second management request may carry a description of the requirements of the network slice subnet instance, and may include a network slice/network slice subnet type, and a decomposed service level agreement (SLA). ) or service level requirement (SLR).

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

The implementation form that the “first management function entity receives the second identifier sent by the second management function 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 the second management function entity, where the second management request response message is used to indicate that the second management function entity has completed the one or more networks Creating a subnet instance, wherein the second management request response message includes the second identity.

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

Specifically, when determining that one or more network slice subnet instances need to be created, the first management function entity sends a second management request to the second management function entity to request the second management function entity to create one or more network slices. Subnet instance. Correspondingly, after receiving the foregoing second management request, the second management function entity may create or configure the one or more for the first management function entity according to the requested content and the managed network slice subnet instance. Network slice subnet instance. For example, the second management function entity may generate a new network slice subnet instance for use by the first management function entity; or the second management function entity may select an existing network slice subnet instance (or multiple The existing network slice subnet instance) is used 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 function entity may associate or map the first identifier and the second identifier to obtain a correspondence between the first identifier and the second identifier. relationship. In this way, the first management function entity can use the correspondence to manage the one or more network slice subnet instances.

Wherein, in 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 another network slice instance Sharing, the second management function entity may configure the existing network slice subnet instance to be used only by the first management function entity; or, if the existing network slice subnet instance has been shared by other network slice instances, Then, the second management function entity can configure the existing network slice subnet instance to be shared and used by the network slice instance. For the case where the existing network slice subnet instance has been shared by another network slice instance, the second identifier may not only identify the existing network slice subnet instance, but also indicate the existing network slice subnet instance. Corresponding to the network slice instance. For example, the second identifier is NSSI ID 2.x, where x is used by the second management function entity to distinguish different network slice instances. For example, if the second management function entity receives management requests (for example, modification request, monitoring request, termination request, measurement request, etc.) of multiple network slice instances, the NSSI ID 2.x can be used to distinguish which management request is from which The management request corresponding to the network slice instance.

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

That is, the first management function entity may carry the first identifier when the second management request is sent. The second management function entity may determine the correspondence according to the first identifier and the second identifier. For the case where the one or more network slice subnet instances are shared by multiple network slice instances, the second management function entity may identify the shared one or more network slice subnet instances according to the correspondence. The second management function entity may directly identify the relationship between the one or more network slice subnet instances and the network slice instance by using the second management function entity, and the second management function entity may directly identify the One or more network slice subnet instances, no longer using the above x to indicate that the one or more network slice subnet instances correspond to the network slice instance.

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

The second management function entity sends the capability open message to the first management function entity.

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

In one possible design, the capability open message may include at least one of the following: an identification of the one or more network slice subnet instances, a type of the one or more network slice subnet instances, Information such as the capabilities of the one or more network slice subnet instances, the capacity of the one or more network slice subnet instances, and the like. In a possible design, the capability open message further includes information about the type, identifier, capability, capacity, and the like of other network slice subnet instances supported by the second management function entity, which is not limited thereto.

S330. The first management function entity obtains a correspondence between the first identifier and the second identifier according to the first identifier and the second identifier.

In the embodiment of the present application, the first management function entity obtains the first identifier and the second identifier, and generates a correspondence between the first identifier and the second identifier, so as to implement management of the network slice subnet instance, and the network slice can be improved. The management efficiency of the instance.

In one possible design, as an embodiment, FIG. 5 shows a schematic flow 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 can be used in combination with the foregoing method 300 or method 400, which is not limited thereto. As shown in FIG. 5, the method 500 includes:

S501. The first management function entity sends a third management request to the second management function entity, where the third management request is used to request the second management function entity to use the one or more network slice subnet instances. 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 function entity sends a third management request response message to the first management function 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 to use the one or more Network slice subnet instances. 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 a possible design, the third management request may be carried in different types of messages, for example, a usage/reuse request message of a network slice subnet instance, a creation request message of a network slice subnet instance, a network slice subnet. The modification request message of the instance, and the like.

Specifically, for the case where the first management function entity has learned the second identifier, for example, the second identifier is learned by the capability open message, or the previous one is used when the one or more network slice subnet instances are used. The second identity, 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 about a network slice subnet instance requirement, such as SLA information and/or SLR information. In a possible design, the first identifier may also be carried in the third management request. Correspondingly, the second management function entity may perform 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, to notify that the one or the Processing of multiple network slice subnet instances. In a possible design, the third management request response message may further carry the first identifier.

In a possible design, 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 use request. The third management request includes a requirement description for one or more network slice subnet instances, where the third management request carries a second identifier.

Specifically, 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 notify the first management function entity that the one or more network slice subnet instances have been completed. Processing that causes one or more network slice subnet instances to be part of a network slice instance.

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

Alternatively, although the first management function entity has obtained the foregoing second identifier by using the foregoing second management request response message, there may be a first management function entity that has been released without using one or more network slice subnet instances. The scenario of the second identifier is deleted, and the first management function entity may still send the foregoing third management request to the second management function entity.

Therefore, if the first management function entity knows the second identifier, the third management request may be directly sent to the second management function entity, 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 function entity may associate or map the first identifier and the second identifier to obtain a correspondence between the first identifier and the second identifier. relationship.

In this way, the first management function entity can use the correspondence to manage the one or more network slice subnet instances.

The technical solution of the foregoing embodiment is described in the scenario that 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 nested between network sliced subnet instances, that is, the network sliced subnet instance includes at least one network sliced subnet instance. Correspondingly, 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 still applies. For example, the first management function entity in each of the above embodiments is replaced with a second management function entity, and the network slice instance managed by the first management function entity is replaced with one or more network slice subnet instances.

The method for managing network slices in the embodiment of the present application is described above with reference to FIG. 2 to FIG. 5. The specific flow of the method for managing network slices in the embodiment of the present application will be described below with reference to the examples in FIG. 6 to FIG. 8. It should be understood that the examples in FIG. 6 to FIG. 8 are only for facilitating the understanding of the embodiments of the present application, and the embodiments of the present application are not limited to the specific scenarios illustrated. It is apparent to those skilled in the art that various modifications and changes can be made in the embodiments of the present invention in accordance with the examples of FIG. 6 to FIG. 8. Such modifications or variations are also within the scope of the embodiments of the present invention.

For convenience of description, the following example will be described by taking the first network slice instance as an example. In the embodiment of the present application, the first network slice instance is used to refer to a network slice instance in the network slice instance managed by the first management function entity.

6 is a schematic interaction diagram of an example 600 of managing network slices in accordance with an embodiment of the present 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, and the NSI ID is used to identify the NSI.

In a possible design, the first management function entity learns that the first network slice instance needs to be composed of multiple network slice subnet instances, for example, the NSI is composed of two NSSIs.

S602. The first management function entity sends a first creation request to the second management function entity 1.

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

The first creation request is used to request the second management function entity 1 to create a network slice subnet instance.

In a possible design, the first creation request carries description information about a network slice subnet instance. In one possible design, the description information may include one or more of the following: description information of a service requirement of a network slice subnet instance, a network slice subnet template (NSST) of a network slice subnet instance Identification, NSST related configuration parameter information.

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

S603. The first management function entity sends a second creation request to the second management function entity 2.

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

It should be understood that the foregoing first creation request is similar to the definition of the second creation request, and details are not described herein.

It should also be understood that there is no order 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 a possible design, the first identification may or may not be carried in the second creation request.

S604. The second management function entity 1 generates or configures a network slice subnet instance 1.

Specifically, after receiving the first creation request, the second management function entity 1 may create a network slice subnet instance 1 for use by the first network slice instance. Alternatively, if the network slice subnet instance 1 already exists, the second management function entity 1 can configure the network slice subnet instance 1 to be used only by the first network slice instance. The network slice subnet instance 1 is non-shared, that is, it is not shared by other network slice instances.

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

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

S605. The second management function entity 1 sends a first creation completion message to the first management function entity.

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

The first creation completion message is used to feed back the network slice subnet instance 1 has been created.

In a possible design, the first creation completion message includes an identifier of the network slice subnet instance 1, such as NSSI ID1. 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.

Specifically, if the network slice subnet instance 2 already exists and has been shared by the other at least one network slice instance, the second management function entity 2 can configure the network slice subnet instance 2 to be also used by the first network slice instance.

In a possible design, the second management function entity may directly use the identifier of the network slice subnet instance 2, such as NSSI ID2; or the second management function entity determines that the identifier of the network slice subnet instance 2 is NSSI ID2.x, Wherein x is used by the second management function entity to distinguish different network slice instances.

In a possible design, if the second creation request carries the first identifier, such as an NSI ID, the second management function entity 2 may map the NSI ID with the NSSI ID2 or the NSSI ID2.x.

S607. The second management function entity 2 sends a second creation completion message to the first management function entity.

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

The second creation completion message is used to feedback that the network slice subnet instance 2 has been created.

In a possible design, the second creation completion message includes an identifier of the 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 a correspondence.

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

It should be understood that the size of the sequence numbers of the above-mentioned processes does not imply a sequence of executions, and the order of execution of the processes should be determined by its function and internal logic, and should not be construed as limiting the implementation process of the embodiments of the present application.

7 is a schematic interaction diagram of another example 700 of managing network slices in accordance with an embodiment of the present 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 the modification of the first network slice instance may be specifically performed to modify the network slice subnet instance included in the first network slice instance. For example, the NSMF determines that the NSI needs to be modified, and the NSI is composed of one or more NSSIs, so that the corresponding NSSI can be modified.

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

Specifically, when determining that the first network slice instance is modified, the first management function entity may decompose the modification requirement into a network slice subnet instance, for example, decomposed into network slice subnet instance 1 and network slice subnet instance 2, and then according to Corresponding relationship (NSI ID->NSSI ID1; NSI ID->NSSI ID2 or NSSI ID2.x), determining to modify the network slice subnet instance 1 corresponding to NSSI ID1, and the network slice subnet corresponding to NSSI ID2 or NSSI ID2.x Example 2.

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

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

The first modification request is used to request the second management function entity 1 to modify the network slice subnet instance 1 corresponding to the NSSI ID1.

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

S703. The first management function entity sends a second modification request to the second management function entity 2.

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

The second modification request is used to request 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 the NSSI ID2.x included in the second modification request is consistent with the content fed back by the second management function entity 2. For example, if the second management function entity 2 feeds back the NSSI ID2 to the first management function entity, the second modification request includes the NSSI ID2; if the second management function entity 2 feeds back the NSSI to the first management function entity, ID2.x, then 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 function entity 1 sends a first modification complete message to the first management function entity.

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

The first modification completion message is used to feed back the network slice subnet instance 1 that has been modified.

In a possible design, the first modification completion message includes an identifier of the network slice subnet instance 1, such as NSSI ID1. In a possible design, the first modification completion message may further include an identifier 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.

The second modification completion message is used to feedback that the network slice subnet instance 2 has been modified.

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

It should be understood that, in FIG. 7 , an example of modifying a network slice subnet is taken as an example. The foregoing modification process may also be other management processes, such as termination, monitoring, measurement, etc., which are not limited.

The modification process of the network slicing subnet instance by the first management function entity according to the corresponding relationship is described in FIG. 7 above. It should be understood that the above-described flow in FIG. 7 can be used in combination with FIG. 6 described above.

FIG. 8 is a schematic interaction diagram of still another example 800 of managing network slices in accordance with an embodiment of the present application. As shown in FIG. 8, the method 800 includes:

S801. The second management function entity sends capability open information to the first management function entity.

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

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

In one possible design, the capability open information includes an identifier of the network slice subnet instance 1, such as NSSI ID1.

In a possible design, the second management function entity includes a network slice subnet instance shared by multiple network slice instances, and the capability open information may also provide shared information, for example, a network slice subnet instance. Whether it is shared, or which shared network slice subnet instances are shared by which network slice instances.

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

In a possible design, after the first network function instance is created, the first management function entity decides to use the network according to the requirements of the network sliced subnet instance and the information of several network slice subnet instances provided by the capability open message. The subnet instance 1 is sliced to form a first network slice instance.

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.

The usage request is used to request a network sliced subnet instance NSSI managed by the second management function entity.

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

In a possible design, the usage request may further 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 an NSSI usage/reuse request message, an NSSI creation request message, and an NSSI modification request message.

It should be noted that S803 and S801 may or may not have a coupling relationship. Specifically, the first management function entity may send a use request to the second management function entity even if the capability open message is not received; or, after receiving the capability open message, send the use request to the second management function entity. There is no limit to this.

It should be understood that FIG. 8 is merely illustrative of one possibility and does not constitute a limitation of the scope of protection of the embodiments of the present application.

S804. The second management function entity is configured correspondingly according to the use request, so that the network slice subnet instance 1 becomes part of the first network slice instance.

S805. The second management function entity sends a configuration completion 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.

The configuration completion message is used to feed back the network slice subnet instance 1 that has been configured.

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

S806. The first management function entity generates a correspondence.

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

It should be understood that the first management function entity may also obtain the identifier of the network slice subnet instance 1 by other means.

The process of acquiring the first identifier and the second identifier by the first management function entity and generating the corresponding relationship is described in FIG. 8 above. It should also be understood that the above-described flow in FIG. 8 can be used in combination with FIG. 6 described above. After the above correspondence is obtained in FIG. 8, the steps in FIG. 6 can be performed.

The method for managing network slices according to an embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 8. Hereinafter, an apparatus for managing network slices according to an embodiment of the present application will be described in detail with reference to FIG. 9 to FIG.

FIG. 9 shows a schematic block diagram of an apparatus 900 for managing network slices in accordance with an embodiment of the present application. The apparatus 900 is configured to execute a method or a step corresponding to the foregoing first management function entity. Optionally, each module in the device 900 may be implemented by software. Among them, the function corresponding to each module is used to implement the network slice management function. The device 900 can be installed in a general purpose computer device. As shown in FIG. 9, the apparatus 900 includes:

The processing module 910 is configured to determine a management network slice instance, where the network slice instance includes at least one network slice subnet instance;

The transceiver module 920 is configured to send a first management request to the second management function entity, where the first management request includes an identifier of one or more network slice subnet instances for identifying a network slice instance, the first management request Used to request processing of 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 indicate that the second management function entity completes the one or Processing of multiple network slice subnet instances.

In one possible design, the processing includes at least one of modification, monitoring, termination, and measurement.

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

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

Receiving the identifier sent by the second management function entity.

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

Sending, to the second management function entity, a second management request, where the second management request is used to request the second management function entity to create the one or more network slice subnet instances;

The transceiver module 920 is specifically configured to:

Receiving, by the second management function entity, a second management request response message, 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 The second management request response message includes the identifier.

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

And receiving, by the second management function entity, a capability open message, where the capability open message is used to indicate information about a network slice subnet instance supported by the second management function entity, where the capability open message includes the identifier.

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

Sending, to the second management function entity, a third management request, where the third management request is used to request the second management function entity to use the one or more network slice subnet instances, the third management request Include the second identifier; and receive a third management request response message sent by the second management function entity, where the third management request response message is used to instruct the second management function entity to notify the network slice instance that Use the one or more network slice subnet instances.

It should be understood that the apparatus 900 according to an 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 foregoing and other management operations and/or functions of the respective modules in the 900 apparatus are respectively implemented in order to implement The respective steps of the foregoing methods can also achieve the beneficial effects in the foregoing method embodiments. For brevity, no further details are provided herein.

It should also be understood that the processing module in the embodiment 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 in accordance with another embodiment of the present application. The apparatus 1000 is configured to execute a method or a step corresponding to the foregoing second management function entity. Optionally, each module in the device 1000 may be implemented by software. Among them, the function corresponding to each module is used to implement the network slice management function. The device 1000 can be installed in a general purpose computer device. As shown in FIG. 10, the apparatus 1000 includes:

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

The processing module 1020 is 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 completion of the one or more network slice subnet instances. deal with.

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:

Sending the identity to the first management function entity.

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

Receiving, by the first management function entity, a second management request, where the second management request is used to request 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.

The transceiver module 1010 is further configured to: send 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 the one or more Creation or configuration of a network slice subnet instance, wherein the second management request response message includes the identity.

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

And sending, to the first management function entity, a capability open message, where the capability open message is used to indicate information about a network slice subnet instance supported by the second management entity, where the capability open message includes the identifier.

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

Receiving, by the first management function entity, a third management request, where the third management request is used to request 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 to use the one or more networks. Slice a subnet instance.

It should be understood that the apparatus 1000 according to an 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 foregoing and other management operations and/or functions of the respective modules in the 1000 apparatus are respectively implemented in order to implement The respective steps of the foregoing methods can also achieve the beneficial effects in the foregoing method embodiments. For brevity, no further details are provided herein.

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

FIG. 11 is a structural block diagram of an apparatus 1100 for managing network slices according to an embodiment of the present application. The apparatus 1100 for managing network slices shown in FIG. 11 includes a processor 1101, a memory 1102, and a transceiver 1103.

The processor 1101, the memory 1102, and the transceiver 1103 communicate with each other through an internal connection path to transfer control and/or data signals. In one possible design, the processor 1101, the memory 1102, and the transceiver 1103 can be implemented by a chip. The memory 1102 can store program code, and the processor 1101 calls the program code stored in the memory 1102 to implement the corresponding functions of the device that manages network slicing.

The processor 1101 is configured to:

Determining to manage a first network slice instance, the first network slice instance including at least one network slice subnet instance;

Transmitting, by the transceiver 1103, a first management request to a second management function entity, where the first management request includes the second identifier, where the first management request is used to request a first network of a first network slice instance Processing the sliced subnet instance, where the second identifier is used to identify the first network slice subnet instance, where the first network slice subnet instance is one or more included in the first network slice instance One of the network slicing subnet instances;

And receiving, by the transceiver 1103, 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 slice of the first network Processing of subnet instances.

It will be appreciated that although not shown, the device 1100 managing the network slice may also include other devices, such as input devices, output devices, batteries, and the like.

Alternatively, in some embodiments, the memory 1102 can store some or all of the instructions for performing the method performed by the first management function entity in the aforementioned method. The processor 1101 can execute the instructions stored in the memory 1102 to complete the steps performed by the first management function entity in the foregoing method in combination with other hardware (for example, the transceiver 1103). For the specific working process and the beneficial effects, refer to the description in the foregoing method embodiments.

FIG. 12 is a structural block diagram of an apparatus 1200 for managing network slices according to another embodiment of the present application. The apparatus 1200 for managing network slices 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 through an internal connection path to transfer control and/or data signals. In one possible design, the processor 1201, the memory 1202, and the transceiver 1203 can be implemented by a chip. The memory 1202 can store program code, and the processor 1201 invokes the program code stored in the memory 1202 to implement the corresponding functions of the device that manages network slicing.

The processor 1201 is configured to:

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

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

Sending, by the transceiver 1203, the 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 first network slice subnet instance is completed.

It will be appreciated that although not shown, the device 1200 that manages network slices may also include other devices, such as input devices, output devices, batteries, and the like.

In one possible design, in some embodiments, the memory 1202 can store instructions for performing the method of the second management function entity execution in the foregoing method. The processor 1201 can execute the instructions stored in the memory 1202 in combination with other hardware (for example, the transceiver 1203) to complete the steps performed by the second management function entity in the foregoing method. For the specific working process and the beneficial effects, refer to the description in the foregoing method embodiments.

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

The method disclosed in the foregoing embodiment of the present application may be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software. The above 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 the like. Programming logic device, discrete gate or transistor logic device, discrete hardware component, system chip (SoC), central processor unit (CPU), or network processor (network) Processor, NP), can also be a digital signal processor (DSP), can also be a microcontroller (micro controller unit (MCU), can also be a programmable logic device (PLD) or other Integrated chip. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read only memory or an electrically erasable programmable memory, a register, etc. In the storage medium. The storage medium is located in the memory, and the processor reads the instructions in the memory and combines the hardware to complete the steps of the above method.

It should be understood that, in the embodiment of the present application, the numbers "first" and "second" are introduced only to distinguish different objects, for example, to distinguish different "identities", or to distinguish different "management requests", and The scope of protection of the embodiments of the present application is limited.

It should also be understood that, in various embodiments of the present application, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the present application. The implementation of the examples constitutes any limitation.

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

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

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

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk, and the like, which can store program codes.

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

Claims (27)

1. A method for managing network slicing, comprising:

   The first management function entity sends a first management request to the second management function entity, where the first management request includes an identifier for identifying one or more network slice subnet instances of the network slice instance, where the first management request is Processing the one or more network slice subnet instances to request processing;

   Receiving, by the first management function entity, a first management request response message sent by the second management function entity, where the first management request response message is used to indicate that the second management function entity completes the one or more Processing of network slice subnet instances.
2. The method of claim 1 wherein the processing comprises at least one of modifying, monitoring, terminating, measuring.
3. The method according to claim 1 or 2, wherein the method further comprises:

   The first management function entity receives the identifier sent by the second management function entity.
4. The method of claim 3, wherein the method further comprises:

   The first management function entity sends a second management request to the second management function entity, where the second management request is used to request the second management function entity to create the one or more network slice subnet instances;

   The first management function entity receives the identifier sent by the second management function entity, including:

   Receiving, by the first management function entity, 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 the one or more Creation of a network slice subnet instance, wherein the second management request response message includes the identity.
5. The method according to claim 3, wherein the receiving, by the first management function entity, the identifier sent by the second management function entity comprises:

   Receiving, by the first management function entity, a capability open message sent by the second management function entity, where the capability open message is used to indicate information about a network slice subnet instance supported by the second management function entity, where the capability is open The message includes the identification.
6. The method according to any one of claims 1 to 5, wherein the method further comprises:

   The first management function entity sends a third management request to the second management function entity, where the third management request is used to request the second management function entity to use the one or more network slice subnet instances The third management request includes the identifier;

   Receiving, by the first management function entity, a third management request response message sent by the second management function entity, where the third management function response message is used by the second management function entity to notify the network slice instance that the network slice instance can use the One or more network slice subnet instances.
7. A method for managing network slicing, comprising:

   Receiving, by the second management function entity, a first management request sent by the first management function entity, where the first management request includes an identifier of one or more network slice subnet instances for identifying a network slice instance, the first management request Used to request processing of the one or more network slice subnet instances;

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

   The second management function entity sends 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.
8. The method of claim 7, wherein the processing comprises at least one of modifying, monitoring, terminating, measuring.
9. The method according to claim 7 or 8, wherein before the second management function entity receives the first management request sent by the first management function entity, the method further includes:

   The second management function entity sends the identifier to the first management function entity.
10. The method of claim 9 wherein the method further comprises:

    Receiving, by the second management function entity, a second management request sent by the first management function entity, where the second management request is used to request the second management function entity to create the one or more network slice subnet instances ;

    Creating, by the second management function entity, the one or more network slice subnet instances for the first management function entity according to the second management request;

    The sending, by the second management function entity, the identifier to the first management function entity, including:

    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 the one or more network slicers Creation or configuration of a network instance, wherein the second management request response message includes the identification.
11. The method according to claim 9, wherein the sending, by the second management function entity, the second identifier to the first management function entity comprises:

    The second management function entity sends a capability open message to the first management function entity, where the capability open message is used to indicate information about a network slice subnet instance supported by the second management entity, where the capability open message includes The identification.
12. The method according to any one of claims 7 to 11, wherein the method further comprises:

    Receiving, by the second management function entity, a third management request sent by the first management function entity, where the third management request is used to request the second management function entity to use the one or more network slice subnets An example, the third management request includes the identifier;

    The second management function entity configures 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, where the third management request response message is used to notify the network slice instance to use the one or more network slices. Network instance.
13. An apparatus for managing network slicing, comprising:

    transceiver,

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

    Transmitting, by the transceiver, 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 the network slice instance, where the first management request is Processing the one or more network slice subnet instances to request processing;

    And receiving, by the transceiver, a first management request response message sent by the second management function entity, where the first management request response message is used to indicate that the second management function entity completes the one or more networks The processing of slicing a subnet instance.
14. The apparatus of claim 13 wherein said processing comprises at least one of modifying, monitoring, terminating, measuring.
15. The device according to claim 13 or 14, wherein before the sending the first management request to the second management function entity, the processor is further configured to:

    Receiving, by the transceiver, the identifier sent by the second management function entity.
16. The device according to claim 15, wherein the processor is specifically configured to:

    Sending, by the transceiver, a second management request to the second management function entity, where the second management request is used to request the second management function entity to create the one or more network slice subnet instances; Receiving, by the transceiver, 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 the one or more network slicers Creation of a network instance, wherein the second management request response message includes the identifier.
17. The device according to claim 15, wherein the processor is specifically configured to:

    Receiving, by the transceiver, a capability open message sent by the second management function entity, where the capability open message is used to indicate information about a network slice subnet instance supported by the second management function entity, where the capability open message includes The identification.
18. The device according to any one of claims 13 to 17, wherein the processor is specifically configured to:

    Sending, by the transceiver, a third management request to the second management function entity, where the third management request is used to request the second management function entity to use the one or more network slice subnet instances, The third management request includes the identifier; and receiving, by the transceiver, a third management request response message sent by the second management function entity, where the third management request response message is used by the second management function entity Notifying the first network slice instance to use the one or more network slice subnet instances.
19. The device according to any one of claims 13 to 18, wherein the device further comprises:

    A memory for storing instructions that, when read by the processor, cause the processor to perform the steps of any one of claims 13-18.
20. An apparatus for managing network slicing, comprising:

    transceiver,

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

    Receiving, by the transceiver, a first management request sent by a first management function entity, where the first management request includes an identifier of one or more network slice subnet instances for identifying a network slice instance, the first management request 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;

    Transmitting, by the transceiver, 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 one or more network slice subnet instances is completed.
21. The apparatus of claim 20 wherein said processing comprises at least one of modifying, monitoring, terminating, measuring.
22. The device according to claim 20 or 21, wherein before the second management function entity receives the first management request sent by the first management function entity, the processor is further configured to:

    The identification is sent by the transceiver to the first management function entity.
23. The device according to claim 22, wherein the processor is specifically configured to:

    Receiving, by the transceiver, a second management request sent by the first management function entity, where the second management request is used to request the second management function entity to create the one or more network slice subnet instances;

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

    Transmitting, by the transceiver, the 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 the one or more network slicers Creation or configuration of a network instance, wherein the second management request response message includes the identification.
24. The device according to claim 22, wherein the processor is specifically configured to:

    Transmitting, by the transceiver, a capability open message to the first management function entity, where the capability open message is used to indicate information about a network slice subnet instance supported by the second management entity, where the capability open message includes the Logo.
25. The device according to any one of claims 20 to 24, wherein the processor is further configured to:

    Receiving, by the transceiver, a third management request sent by the first management function entity, where the third management request is used to request the second management function entity to use the one or more network slice subnet instances, The third management request includes the identifier;

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

    Transmitting, by the transceiver, 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 to use the one or more network slice subnet instances .
26. The device according to any one of claims 20 to 25, wherein the device further comprises:

    A memory for storing instructions that, when read by the processor, cause the processor to perform the steps of any one of claims 20-25.
27. A computer readable storage medium comprising a computer program that, when executed on a computer, causes the computer to perform the method of any one of claims 1 to 12.

Images