CN108092789B

CN108092789B - Method and device for managing network slice template

Info

Publication number: CN108092789B
Application number: CN201611026503.1A
Authority: CN
Inventors: 杨水根; 孙文琦; 陆伟
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-11-21
Filing date: 2016-11-21
Publication date: 2021-03-05
Anticipated expiration: 2036-11-21
Also published as: CN108092789A; WO2018090993A1

Abstract

The invention discloses a method and a device for managing a network slice template. The method comprises the following steps: the network management system receives requests of putting on shelves, updating, forbidding, enabling, inquiring, deleting and the like of the network slice template sent by the sender functional entity, decides to request a third-party functional entity to provide related network function information according to the support capability of the current network to the network slice template, and informs a storage library to execute corresponding operation on the network slice template, thereby realizing the effective management of the network slice template.

Description

Method and device for managing network slice template

Technical Field

The present invention relates to the field of wireless network communications, and in particular, to a method and an apparatus for managing a network slice template.

Background

With the rapid development of wireless communication technology, the fifth Generation (5th Generation, abbreviated as 5G) wireless communication technology has been the hot spot in the industry. The 5G will support diverse application requirements including access capability supporting higher rate experience and larger bandwidth, lower latency and highly reliable information interaction, and access and management of larger-scale and low-cost machine type communication devices, etc. In addition, 5G can support various vertical industry application scenes such as vehicle networking, emergency communication, industrial internet and the like. In the face of the performance requirements and application scenarios of 5G, the 5G network needs to be closer to the specific requirements of users, and the customization capability needs to be further improved.

To this end, 5G introduces the important concept of network slicing. A network slice is a combination of one or more network functions and corresponding resources that implement a communication service. The 5G network is composed of a large number of network slices that satisfy different connection capabilities, one network slice satisfying the communication service requirements of a certain class or one use case. Fig. 1 shows a 5G network scenario after introducing a network slicing concept, which includes Communication of three cases, namely Critical Machine Type Communication (referred to as Critical MTC), Massive Machine Type Communication (referred to as Massive MTC), and Mobile broadband (referred to as MBB). As shown in fig. 1, a 3GPP operator network may include a critical machine type communication network slice, a large scale machine type communication network slice, and a mobile broadband network slice, where each network slice serves different use cases of communication services.

A unified network platform, which supports communication services with different functions and quality of service requirements using dynamic, secure network slices, is one of the basic capabilities of a 5G network. The logical network formed by a network slice is realized by the network slice instance, namely, a network slice is formed by instantiating each network function and corresponding resource of the network slice. And a network slice instance may be created from a network slice template. The network slice template information contains constituent elements (such as network function description, resource requirement description, and the like) describing the network slice and/or relationships between the constituent elements (such as network function organization architecture, network function/resource configuration, workflow between network functions, and the like). As a basis for successful deployment of network slices, a 5G network first needs to manage a network slice template. How to manage the network slice template has no appropriate solution at present.

Disclosure of Invention

The embodiment of the invention provides a method and a device for managing a network slice template, thereby providing support for the deployment of network slices. Specifically, the management of the network slice template includes operations of shelving, updating, disabling, enabling, querying, deleting, and the like of the network slice template.

In a first aspect, an embodiment of the present invention provides a method for managing a network slice template, where the method includes: a network management system receives a network slicing template management request sent by a sender functional entity; the network management system informs a storage library to manage the network slice template; and the network management system sends a response of the network slicing template management to a sender functional entity.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the network slice template management request is a network slice template racking request, and the network management system notifies the repository to load the network slice template into the repository.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, before the network management system notifies a repository to manage the network slice template, the method further includes: the network management system judges that the current network does not support at least one part of network functions in the network slice template on the shelf; the network management system requests a third-party functional entity to provide network function information of at least one part of network functions; and the network management system receives network function information of the at least one part of network functions provided by a third-party functional entity.

The first and second implementation manners of the first aspect enable the network management system to confirm that the network slice template is uploaded to the repository according to the network function of the network slice template in the network slice template uploading request, whether the network supports the network function, and whether a third-party functional entity supports the network function.

With reference to the first aspect, in a third possible implementation manner of the first aspect, the network slice template management request is a network slice template update request, and the network management system notifies the repository to store a new version of a network slice template in the repository and/or disable an old version of the network slice template.

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, before the network management system notifies a repository to manage the network slice template, the method further includes: the network management system judges that the current network does not support at least one part of network functions in the updated network slice template; the network management system requests a third-party functional entity to provide network function information of at least one part of network functions; and the network management system receives network function information of the at least one part of network functions provided by a third-party functional entity.

The third and fourth implementation manners of the first aspect of this embodiment enable the network management system to confirm that the network slice template is updated to the repository according to the network function of the network slice template in the network slice template update request, whether the network supports the network function, and whether the third-party functional entity supports the network function.

With reference to the first aspect, in a fifth possible implementation manner of the first aspect, the network slice template management request is a network slice template disabling request, and the network management system notifies the repository to set the network slice template to a disabled state, so that the network slice template cannot be used to create, configure, or control a network slice instance.

With reference to the first aspect, in a sixth possible implementation manner of the first aspect, the network slice template management request is a network slice template enabling request, and the network management system notifies the repository to enable the network slice template in a disabled state, so that the enabled network slice template may be used to create a create, configure, or control network slice instance.

With reference to the first aspect, in a seventh possible implementation manner of the first aspect, the network slice template management request is a network slice template query request, and the network management system queries the repository for relevant information of the network slice templates stored in the repository.

With reference to the first aspect, in an eighth possible implementation manner of the first aspect, the network slice template management request is a network slice template deletion request, and the network management system notifies the repository of deleting the network slice template stored in the repository.

In a second aspect, an embodiment of the present invention provides a network management system, including: the receiving module is used for receiving a network slicing template management request sent by a sender functional entity; the processing module is used for informing the repository to manage the network slice template; and the sending module is used for sending the response of the network slicing template management to the sender functional entity.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the network slice template management request is a network slice template racking request, and the processing module notifies the repository to load the network slice template into the repository.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, before the processing module notifies the repository to manage the network slice template, the method further includes: the processing module judges that the current network does not support at least one part of network functions in the network slice template on the shelf; the processing module requests a third-party functional entity to provide network function information of the at least one part of network functions; the processing module receives network function information of the at least one part of network functions provided by the third-party functional entity.

The first and second implementation manners of the second aspect described above enable the network management system to confirm that the network slice template is uploaded to the repository according to the network function of the network slice template in the network slice template uploading request, whether the network supports the network function, and whether a third-party functional entity supports the network function.

With reference to the second aspect, in a third possible implementation manner of the second aspect, the network slice template management request is a network slice template update request, and the processing module notifies the repository to store a new version of a network slice template in the repository, and/or to disable an old version of the network slice template.

With reference to the third possible implementation manner of the second aspect, in a fourth possible implementation manner of the second aspect, before the processing module notifies the repository of management of the network slice template, the method further includes: the processing module judges that the current network does not support at least one part of network functions in the updated network slice template; the processing module requests a third-party functional entity to provide network function information of the at least one part of network functions; the processing module receives network function information of the at least one part of network functions provided by the third-party functional entity.

The third and fourth implementations of the second aspect of this embodiment enable the network management system to confirm updating of the network slice template to the repository according to the network function of the network slice template in the network slice template update request, whether the network supports the network function, and whether the third-party functional entity supports the network function.

With reference to the second aspect, in a fifth possible implementation manner of the second aspect, the network slice template management request is a network slice template disabling request, and the processing module notifies the repository to set the network slice template to a disabled state, so that the network slice template cannot be used for creating, configuring or controlling a network slice instance.

With reference to the second aspect, in a sixth possible implementation manner of the second aspect, the network slice template management request is a network slice template enabling request, and the processing module notifies the repository to enable the network slice template in a disabled state, so that the enabled network slice template may be used to create a create, configure, or control network slice instance.

With reference to the second aspect, in a seventh possible implementation manner of the second aspect, the network slice template management request is a network slice template query request, and the processing module queries the repository for relevant information of the network slice templates stored in the repository.

With reference to the second aspect, in an eighth possible implementation manner of the second aspect, the network slice template management request is a network slice template deletion request, and the processing module notifies the repository to delete the network slice template stored in the repository.

In a third aspect, an embodiment of the present invention provides a network management system, including: a communication interface for receiving and transmitting signaling and data; a memory for storing computer executable code; a processor coupled to the memory and configured to invoke the computer executable code to perform the following steps: receiving a network slicing template management request sent by a sender functional entity; informing a repository to manage the network slice template; and sending a response of the network slicing template management to a sender functional entity.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the network slice template management request is a network slice template racking request, and the processor notifies the repository to load the network slice template into the repository.

With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, before the processor notifies a repository to manage the network slice template, the method further includes: the processor judges that the current network does not support at least part of network functions in the network slice template on the shelf; the processor requests a third-party functional entity to provide network function information of the at least one part of the network function; the processor receives network function information of the at least one part of the network function provided by the third-party functional entity.

The first and second implementations of the third aspect described above implement that the network management system confirms that the network slice template is uploaded to the repository according to the network function of the network slice template in the network slice template uploading request, whether the network supports the network function, and whether a third-party functional entity supports the network function.

With reference to the third aspect, in a third possible implementation manner of the third aspect, the network slice template management request is a network slice template update request, and the processor notifies the repository to store a new version of a network slice template in the repository and/or to disable an old version of the network slice template.

With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, before the processor notifies the repository to manage the network slice template, the method further includes: the processor judges that the current network does not support at least a part of network functions in the updated network slice template; the processor requests a third-party functional entity to provide network function information of the at least one part of the network function; the processor receives network function information of the at least one part of the network function provided by the third-party functional entity.

The third and fourth implementations of the third aspect of this embodiment enable the network management system to confirm updating of the network slice template to the repository according to the network function of the network slice template in the network slice template update request, whether the network supports the network function, and whether the third-party functional entity supports the network function.

With reference to the third aspect, in a fifth possible implementation manner of the third aspect, the network slice template management request is a network slice template disabling request, and the processor notifies the repository to set the network slice template to a disabled state, so that the network slice template cannot be used for creating, configuring, or controlling a network slice instance.

With reference to the third aspect, in a sixth possible implementation manner of the third aspect, the network slice template management request is a network slice template enabling request, and the processor notifies the repository to enable the network slice template in a disabled state, so that the enabled network slice template may be used to create a create, configure, or control network slice instance.

With reference to the third aspect, in a seventh possible implementation manner of the third aspect, the network slicing template management request is a network slicing template query request, and the processor queries the repository for relevant information of the network slicing templates stored in the repository.

With reference to the third aspect, in an eighth possible implementation manner of the third aspect, the network slice template management request is a network slice template deletion request, and the processor notifies the repository of deleting the network slice template stored in the repository.

In the embodiment of the invention, the network management system receives the requests of putting on shelves, updating, forbidding, enabling, inquiring, deleting and the like of the network slice template sent by the functional entity of the sender, decides to request the third-party functional entity to provide related network function information according to the supporting capability of the current network to the network slice template, and informs the repository to execute corresponding operation on the network slice template, thereby realizing the effective management of the network slice template.

These and other aspects of the invention will be apparent from and elucidated with reference to the embodiment(s) described hereinafter.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained by those skilled in the art according to the drawings.

Fig. 1 is a 5G network scenario provided by an embodiment of the present invention;

FIG. 2 is a diagram of a network slice, an example of a network slice, and a relationship of a template of a network slice according to an embodiment of the present invention;

fig. 3 is a management architecture of a network slice template according to an embodiment of the present invention;

FIG. 4 is a flow chart of a network slice template shelving provided by an embodiment of the invention;

FIG. 5 is a flowchart illustrating a network slice template update according to an embodiment of the present invention;

FIG. 6 is a flow chart illustrating the disabling of a network slice template according to an embodiment of the present invention;

FIG. 7 is a flow chart illustrating the enablement of a network slicing template according to an embodiment of the present invention;

FIG. 8 is a flow chart of a web slice template query according to an embodiment of the present invention;

FIG. 9 is a flowchart illustrating the deletion of a network slice template according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a network management system according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of another network management system according to an embodiment of the present invention.

Detailed Description

The embodiments of the present invention will be described below with reference to the drawings.

In this application, the word "exemplary" is used to mean "serving as an example, instance, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The following description is presented to enable any person skilled in the art to make and use the invention. In the following description, details are set forth for the purpose of explanation. It will be apparent to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and processes are not shown in detail to avoid obscuring the description of the invention with unnecessary detail. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

The technical solution of the present invention will be described in detail below with specific examples. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.

As a key feature of 5G, a mobile network may be divided into multiple network slices. A network slice is a combination of one or more network functions and corresponding resources that implement a communication service to meet the communication service requirements of a use case. For example, a network slice may be made up of a set of network functions and a particular radio access technology configuration. A network slice may also be made up of a selected set of logical network functions to support the communication service requirements of a particular use case. A network slice is implemented by the network slice instance, i.e., a network slice is formed by instantiating the network functions and corresponding resources of the network slice. One network slice may contain one or more network slice instances, and different network slice instances may have different configurations of network functions or resources. Different network slice instances may be created from the network slice template. The network slice template information may include constituent elements describing the network slice (e.g., network function descriptions, resource requirement descriptions, etc.) and/or relationships between the constituent elements (e.g., network function organization architecture, network function/resource configuration, workflows between network functions, etc.).

Fig. 2 illustrates the relationship between a network slice, an instance of a network slice, and a network slice template. As shown in fig. 2, network slice a and network slice B correspond to communication services of different use cases. Network slice a may further include network slice instance 1, network slice instance 2, and network slice instance 3, and each network slice instance is created by network slice template a. The template information of the network slice template a contains a set of constituent elements of the network slice and/or a set of parameters of the relationship between the constituent elements, and different network slice instances created from the network slice template may correspond to different subsets of parameters in the set of parameters.

The embodiment of the invention provides a template management method of a network slice, which is used for managing the network slice template in the life cycle process of the network slice, and comprises the operations of putting on shelf, updating, forbidding, enabling, inquiring, deleting and the like of the network slice template. The network slice template contains at least one network function required to describe the network slice, resource requirements of the network functions, and/or relationships between the network functions, etc. The network functions may include mobility management, connection management, and other functions required for implementing communication services. Resource requirements may include virtual and physical resources, such as computing resources, storage resources, and network resources, etc., needed to run network functions. The relationships between the network functions may include dependencies and/or connection relationships between the network functions, creation and configuration of the network slice instances and operation of the control flow, physical locations of the network functions in the resource domain, and configuration information of the network functions in the network slice lifecycle, among others.

For example, the shelving of a network slice template contains uploading the network slice template so that a user can create, configure, and control a corresponding network slice instance from the network slice template. The update of the network slice template includes updating the network slice template so that the user can create, configure, and control a corresponding network slice instance from the new version of the network slice template. Disabling of a network slice template involves setting a state of the network slice template to a disabled state such that the network slice template is no longer available for use in creating, configuring, and controlling a corresponding network slice instance. Enabling of the network slice template includes enabling the network slice template in a disabled state such that the network slice template may be used to create, configure, and control a corresponding network slice instance. The query of the network slice template contains relevant information for querying the network slice template. The deleting of the network slice template includes deleting the network slice template, which may be deleting only a specific version of the network slice template or deleting all versions of the network slice template.

The embodiment of the invention provides a management method of a network slice templateThe method and the device can be applied to a 5G network management system. Fig. 3 illustrates a management architecture of a network slice template according to an embodiment of the present invention. As shown in fig. 3, the Management architecture of the Network slice template includes a Sender function entity (Sender), a Network Management System (NMS), and a Repository (hierarchy). Further, the network slicing template management architecture can also comprise a third party functional entity (3)^rdparty). The sender functional entity is configured to initiate a network slicing template management request, such as requesting the network slicing template to be shelved, updated, disabled, enabled, queried, deleted, and the like. The sender functional entity may be a conventional network management functional entity of a network operator, an application providing a network service, or a functional entity of a service provider. The network management system is used for managing the network slice template, such as informing a repository of shelving, updating, disabling, enabling, querying, deleting, and the like of the network slice template. The network management system may comprise a functional entity for managing network slices, such as a network slice manager or a network slice manager and orchestrator. In this case, the network slice template is managed by the network slice manager or network slice management and orchestrator. The repository is a storage functional entity in the network, and is used for saving the network slice template and operations on the network slice template, such as loading, updating, disabling, enabling, querying, deleting, and the like. The third party functional entity is used for providing at least one network function required in the network slice template, the resource requirements of each network function, and/or information of the relationship between each network function, such as a firewall function, a data compression function, the resource requirements corresponding to each network function, and/or the relationship between each network function. For example, the network function provided by the third party functional entity is a network function that is not provided by the network of the network operator, but is required to be provided by a third party such as another network operator or a service provider. In the management architecture of the network slice template, a sender entity and/or a third-party functional entity interact with a network management system, and the management of the network slice template in a storage library is realized through the network management system.

Fig. 4 is a flowchart illustrating a network slice template shelving method according to an embodiment of the present invention, where the network slice template shelving method includes loading a network slice template by a repository, so that a network user can create, configure, and control a corresponding network slice instance according to the network slice template. The process illustrated in FIG. 4 includes the following steps:

401. sender sends network slice template on shelf request to NMS.

Wherein the network slice template onboarding request includes network slice template information requesting onboarding.

In an embodiment of the present invention, the network slice template information requesting to be shelved may include at least one network function in the network slice template, a resource requirement of the network function, and/or a description of a relationship between the network functions. The network slice template information for the request to be staged may contain an identification of the network slice template if the NMS has already saved a description of the network functions, resource requirements, and/or interrelationships of the network slice template at replication before the network slice template is staged. The identifier of the network slice template may include version information of the network slice template, such as a version number.

402. And the NMS judges whether the network supports the network function of the network slice template on the shelf requested by the network. If yes, go to step 405; otherwise, go to step 403.

In the embodiment of the invention, the NMS checks the network functions in the network and judges whether the network supports the network functions in the network slice template requesting to be put on shelf, such as whether the network functions exist in the network. If the current network supports network functions in the network slice template requested to be placed on shelf, step 405 is entered to notify reproducibility to place the network slice template on shelf. If the current network does not support or partially supports the network function of the network slice template requested to be on-shelf, for example, the network function of the network slice template requested to be on-shelf includes a network function (such as a firewall function, a data compression function, etc.) that is not supported by the current network, step 403 is entered, and request 3 is made^rdparty provides network function information for network functions not supported by the network.The network function information may include network functions not supported by the network, a description of a relationship between the network functions, and/or a description of resource requirements of the network functions.

403. NMS request 3^rdparty provides network function information for network functions not supported by the network in the network slice template.

In the embodiment of the present invention, the network function information may include a description of at least one network function, a description of a relationship between network functions, and/or a resource requirement description of network functions. The network function information may include an identification of a network slice template. The identifier of the network slice template may include version information of the network slice template, such as a version number.

404、3^rdparty sends a response to the NMS.

In the present embodiment, if 3^rdThe party can provide network function information of network functions not supported by the network in the network slice template sent by the NMS, and the response can contain 3^rdparty provides the required network function information. If 3 is^rdIf the party cannot provide the network function information of the network function which is not supported by the network in the network slice template sent by the NMS, a failure response is sent.

The above steps 403, 404 are optional steps, and are executed after the NMS determines in step 402 that the network does not support or partially supports the network function in the network slice template requested to be put on shelf.

405. The NMS sends a notification to have the replication shelve the network slice template.

Wherein the notification includes network slice template information.

In an embodiment of the present invention, the NMS notifies replication to shelve the network slice template is to let replication load the network slice template to replication. This step is an optional step that is performed after the NMS determines the network functions in the network slice template that the network support request is on shelf. This step may be performed after step 404 described above. The network slice template information may include at least one network function in the network slice template on which the request is made, resource requirements of the network functions, and/or a description of a relationship between the network functions. The network slice template information may include an identification of the network slice template on which the request is placed. The identifier of the network slice template may include version information, such as a version number, of the network slice template on which the request is placed.

406. And the NMS sends a network slice template on-shelf response to the Sender.

In an embodiment of the present invention, if the NMS performs step 405 above, indicating a successful onboarding of the network slice template, the network slice template onboarding response may include an indication that the network slice template onboarding was successful. If the NMS does not perform step 405 above, indicating that the network slice template cannot be successfully onboarded, the network slice template onboarding response may include an indication that network slice template onboarding failed. The network slice template onboarding response may include the network slice template information. The network slice template onboarding response may include an identification of the network slice template. The identification of the network slice template may include version information, such as a version number, of the network slice template.

The embodiment realizes that the NMS supports the network function according to the network slice template in the network slice template uploading request, whether the network supports the network function, and 3^rdWhether party supports the network function to confirm that the network slice template is popped up to reproducibility. After the network slice template is put on shelf, the network needs to manage the corresponding network slice template, including updating, disabling, enabling, querying and deleting the network slice template.

Fig. 5 is a schematic diagram illustrating an update flow of a network slice template provided by an embodiment of the present invention, where the repository stores a new version of the network slice template in the repository, and/or disables an old version of the network slice template, so that a network user can create, configure, and control a corresponding network slice instance according to the updated network slice template. The process illustrated in FIG. 5 includes the following steps:

501. sender sends a network slice template update request to the NMS.

Wherein the network slice template update request includes network slice template information requesting an update.

In an embodiment of the present invention, the network slice template information requesting for updating may include at least one new version of the network function in the network slice template, resource requirements of each new version of the network function, and/or a description of a relationship between each new version of the network function. If the NMS has saved in the reproducibility a description of the network functions, resource requirements, and/or interrelationships of a new version of the network slice template prior to the network slice template update, the network slice template information requesting the update may contain version information, such as a version number, of the network slice template.

502. The NMS judges whether the network supports the network function in the network slice template requesting updating. If yes, go to step 505; otherwise, go to step 503.

In the embodiment of the present invention, the NMS checks the network functions in the network, and determines whether the network supports the new version of the network functions in the network slice template requesting the update, for example, whether the new version of the network functions exists in the network. If the current network supports the new version of network functions in the network slice template requested to be updated, step 505 is entered to notify the reproducibility to update the new version of the network slice template. If the current network does not support or partially supports the new version of the network function of the network slice template requested to be updated, for example, the network function of the network slice template requested to be updated includes a new version of the network function that is not supported by the current network (e.g., the network supports a low version of the mobility management function, but the user needs to use a high version of the mobility management function, etc.), wherein the network function of the new version of the network function may have a function enhancement than the network function of the older version of the network function, etc., step 503 is entered, and request 3 is performed^rdparty provides network function information for new versions of network functions not supported by the network. The network function information may include new versions of network functions that are not supported by the network, descriptions of relationships between the new versions of network functions, and/or resource requirement descriptions of the new versions of network functions.

503. NMS request 3^rd partAnd y provides network function information of the new version network functions which are not supported by the network in the network slice template.

In the embodiment of the present invention, the network function information may include a description of at least one new version of network function, a description of a relationship between each new version of network function, and/or a description of resource requirements of each new version of network function. The network function information may include an identification of a new version of the network slice template. The identifier of the network slice template may include version information, such as a version number, of the new version network slice template.

504、3^rdparty sends a response to the NMS.

In the present embodiment, if 3^rdThe party can provide new versions of network function information that are not supported by the network in the network slice template sent by the NMS, the response may contain 3^rdThe party provides the network function information of the required new version of the network function. If 3 is^rdAnd if the party cannot provide the network function information of the new version which is not supported by the network in the network slice template sent by the NMS, sending a failure response.

The above steps 503, 504 are optional steps, and are executed after the NMS determines in step 502 that the network does not support or partially supports the new version of the network function in the network slice template that is requested to be updated.

505. The NMS sends a notification to have the hierarchy update on the new version of the network slice template.

Wherein the notification includes network slice template information.

In an embodiment of the invention, the NMS informs the hierarchy that the update to the network slice template is to have the hierarchy save a new version of the network slice template in the hierarchy. This step is an optional step that is performed after the NMS determines that the network supports the new version of the network function in the network slice template that requested the update. This step may be performed after step 504 described above. The network slice template information may include at least one new version of the network function in the network slice template requested to be updated, resource requirements of each new version of the network function, and/or a description of a relationship between each new version of the network function. The network slice template information may include an identification of the network slice template that requested the update. The identification of the network slice template may include version information, such as a version number, of the network slice template that requested the update.

506. The NMS sends a notification to have the hierarchy disabled for the old version of the network slice template.

Wherein the notification includes old version network slice template information.

The above step 506 is an optional step, which is optionally performed after the NMS performs the completion step 505. And after the NMS notifies the reproducibility of the network slice template requesting to be updated, indicating the reproducibility to disable the old version network slice template of the network slice template. The network slice template information may include at least one old version of a network function in the old version of the network slice template, resource requirements of the old version of the network function, and/or a description of a relationship between the old version of the network function. The network slice template information may include an identification of an old version of a network slice template. The identifier of the network slice template may include version information, such as a version number, of the old version of the network slice template.

507. The NMS sends a network slice template update response to the Sender.

In an embodiment of the present invention, if the NMS performs the above steps 505, 506 indicating that the network slice template was successfully updated, the network slice template update response may include an indication that the network slice template update was successful. If the NMS does not perform step 503 above, indicating that the network slice template cannot be successfully updated, the network slice template update response may include an indication that the network slice template update failed. The network slice template update response may include the network slice template information. The network slice template update response may include an identification of the network slice template. The identifier of the network slice template may include version information of the network slice template, such as a version number.

Fig. 6 is a schematic diagram illustrating a flow of network slice template disabling according to an embodiment of the present invention, where the network slice template disabling is a state in which repetition sets a state of the network slice template to a disabled state, so that the network slice template can no longer be used for creating, configuring and controlling a corresponding network slice instance. The process illustrated in FIG. 6 includes the following steps:

601. sender sends a network slice template disable request to the NMS.

Wherein the network slice template disable request includes network slice template information requesting disabling.

In an embodiment of the present invention, the network slice template information requesting to be disabled may include at least one network function in the network slice template, a resource requirement of each network function, and/or a description of a relationship between each network function. The network slice template information requested to be disabled may include an identification of the network slice template. The identification of the network slice template requested to be disabled may include version information of the network slice template, such as a version number.

602. And the NMS judges whether the network slice template is in an enabling state. If yes, go to step 603; otherwise, go to step 604.

In the embodiment of the invention, the NMS checks whether the network slice template requested to be disabled exists or not, and further judges whether the network slice template requested to be disabled is in an enabled state or not. If the network slice template requested to be disabled does not exist, jumping to step 604; if the network slice template requested to be disabled exists and is already in a disabled state, jumping to step 604; if the network slice template requested to be disabled exists and is in the enabled state, step 603 is entered.

603. The NMS sends a notification to have the hierarchy disable the network slice template.

Wherein the notification includes network slice template information.

In an embodiment of the present invention, the NMS informing the reproducibility of disabling a network slice template is for the reproducibility to set the network slice template to a disabled state, such that the network slice template cannot be used to create, configure and control a corresponding network slice instance. The network slice template information may include at least one network function in the network slice template requested to be disabled, a resource requirement of each network function, and/or a description of a relationship between each network function. The network slice template information may include an identification of the network slice template that is requested to be disabled. The identification of the network slice template may include version information, such as a version number, of the network slice template requested to be disabled.

The above step 603 is an optional step, and the NMS determines in step 602 that the network slice template requested to be disabled exists and is in an enabled state, and then executes the step.

604. The NMS sends a network slice template disable response to the Sender.

In an embodiment of the present invention, if the NMS performs step 603 described above, the network slice template disable response may include an indication that the network slice template disable was successful. If the NMS does not perform step 603 above, the network slice template disable response may include an indication indicating that the network slice template disable failed. If the NMS determines in step 602 above that the network slice template requested to be disabled does not exist, the network slice template disable response may include an indication that the network slice template requested to be disabled does not exist. If the NMS determines in step 602 above that the network slice template requested to be disabled has been disabled, the network slice template disable response may include an indication that the network slice template requested to be disabled has been disabled. The network slice template disable response may include network slice template information for the request disable. The network slice template disable response may include an identification of the network slice template requested to be disabled. The identification of the network slice template requested to be disabled may include version information of the network slice template, such as a version number.

605. NMS to 3^rdparty sends a network slice template disable indication.

In the embodiment of the invention, if the network slice template information requesting to be disabled contains 3^rdparty provided network function information, the NMS may direct 3 upon notifying reproducibility to disable the network slice template^rdparty sends the network slice template disable indication to inform 3^rdparty provides network capability information that is disabled.

The above step 605 is optional and may be performed after the NMS notifies the reproducibility to disable the network slice template in step 603. There is no front-to-back order relationship between this step and the above step 604, and the NMS may not execute the step 604 and the step 605 successively, or may execute only the step 604.

When a network slice template is disabled, the network slice template may be in the following states: the state is that the network slice template is disabled and cannot be used subsequently by a user; in this state the NMS may perform enabling and deleting operations on the network slice template. State two, the network slice template is disabled, but the network slice template is currently being used by the user; in this state, the NMS may perform an enabling operation on the network slice template, but may not perform a deleting operation, and may only mark the network slice template as a to-be-deleted state. The third state is that the network slice template is forbidden and is in a state to be deleted; the NMS in this state cannot perform such operations as enabling the network slice template, but may perform a delete operation that deletes the network slice template after it is used up by the user.

Fig. 7 is a schematic diagram illustrating a network slice template enabling process provided by an embodiment of the present invention, where the enabling of the network slice template is to enable the network slice template in a disabled state by using repetition, such as restarting read selection of the network slice template, so that the template can be used to create, configure and control a corresponding network slice instance in the future. The process illustrated in FIG. 7 includes the following steps:

701. sender sends a network slice template enable request to the NMS.

Wherein the network slice template enable request includes request-enabled network slice template information.

In an embodiment of the present invention, the request-enabled network slice template information may include at least one network function in the network slice template, a resource requirement of each network function, and/or a description of a relationship between each network function. The request-enabled network slice template information may include an identification of the network slice template. The identification of the request-enabled network slice template may include version information, such as a version number, of the network slice template.

702. The NMS determines whether the network slice template is in an enabled state. If yes, go to step 703; otherwise, go to step 704.

Wherein the enabled state refers to the network slice template being in a disabled state but not in a to-be-deleted state.

In the embodiment of the invention, the NMS checks whether the request-enabled network slice template exists, further judges whether the request-enabled network slice template is in a disabled state, and further judges whether the request-enabled network slice template is in a to-be-deleted state. If the request-enabled network slice template does not exist, jumping to step 704; if the request-enabled network slice template exists but is in a to-be-deleted state, jumping to step 704; if the request-enabled network slice template exists and is already in an enabled state, jumping to step 704; if the request-enabled network slice template is in the disabled state but not in the to-be-deleted state, step 703 is entered.

703. The NMS sends a notification to enable the hierarchy for the network slice template.

Wherein the notification includes network slice template information.

In the embodiment of the present invention, the NMS notifies the reproducibility that enabling the network slice template is enabling the network slice template in the disabled state, such as restarting the reading selection of the network slice template, so that the template can be used for creating, configuring and controlling the corresponding network slice instance in the future. The network slice template information may include at least one network function in the request-enabled network slice template, resource requirements of the network functions, and/or a description of a relationship between the network functions. The network slice template information may include an identification of the request-enabled network slice template. The identification of the network slice template may include version information, such as a version number, of the request-enabled network slice template.

The above step 703 is an optional step, and is executed after the NMS determines that the request-enabled network slice template exists and is in an enabled state in step 702.

704. The NMS sends a network slice template enabled response to the Sender.

In an embodiment of the present invention, if the NMS performs step 703 above, the network slice template enabled response may include an indication that network slice template enablement was successful. If the NMS does not perform step 703 above, the network slice template enable response may include an indication that network slice template enablement failed. If the NMS determines in step 702 that the request-enabled network slice template does not exist, the network slice template enabled response may include an indication that the request-enabled network slice template does not exist. If the NMS determines in step 702 above that the request-enabled network slice template is disabled and is in a to-be-deleted state, the network slice template enabled response may include an indication that the request-enabled network slice template is in a to-be-deleted state. If the NMS determines in step 702 above that the request-enabled network slice template is already in an enabled state, the network slice template enable response may include an indication that the request-enabled network slice template is enabled. The network slice template enabled response may include the request-enabled network slice template information. The network slice template enabled response may include an identification of the request-enabled network slice template. The identification of the request-enabled network slice template may include version information, such as a version number, of the network slice template.

705. NMS to 3^rdparty sends a network slice template enable indication.

In the embodiment of the present invention, if the request-enabled network slice template information contains 3^rdparty provided network function information, the NMS may then notify the reproducibility to enable the network slice template to 3^rdparty sends the network slice template enable indication, inform 3^rdparty is enabled with the network function information it provides.

The above step 705 is optional and may be performed after the NMS notifies the reproducibility to enable the network slice template in step 703. There is no front-to-back order relationship between this step and the above step 704, and the NMS may not execute the step 704 and the step 705 in sequence, or may execute only the step 704.

Fig. 8 is a flowchart illustrating a network slice template query according to an embodiment of the present invention, where the query of the network slice template is to query relevant information of the network slice templates stored in the repository, such as version numbers of the network slice templates, network functions of the network slice templates, resource requirements of the network functions, and/or relationships between the network functions. The process illustrated in FIG. 8 includes the following steps:

801. sender sends a network slice template query request to the NMS.

Wherein the network slice template query request contains an identification of the network slice template and/or a query object requesting the query.

In an embodiment of the present invention, the identifier of the network slice template requesting the query may include version information of the network slice template, such as a version number. The query object of the network slice template requesting query may include a state of the network slice template, a network function of the network slice template, a resource requirement of each network function, and/or a relationship between each network function, etc.

802. And NMS judges whether the network slice template exists. If yes, go to step 803; otherwise, go to step 805.

In the embodiment of the present invention, the NMS checks whether the network slice template requested to be queried exists, and if the network slice template requested to be queried does not exist, step 805 is performed; if the network slice template of the request query exists, step 803 is entered.

803. The NMS forwards the network slice template query request to the hierarchy.

In the embodiment of the present invention, the NMS forwards the network slice template query request received in step 802 to the hierarchy, and queries the relevant information of the network slice template stored in the Repository, such as the version number of the network slice template, the network function of the network slice template, the resource requirement of each network function, and/or the relationship between each network function. This step is an optional step, and the NMS performs after determining that the network slice template requesting query is present in step 802.

804. The reproducibility sends the network slice template information to the NMS.

The network slice template information may include related information of the network slice template requested to be queried, such as a version number of the network slice template requested to be queried, a state of the network slice template, network functions of the network slice template, resource requirements of the network functions, and/or relationships between the network functions.

The above step 804 is an optional step, and the NMS forwards the network slice template query request to the hierarchy in step 803, and then executes it.

805. The NMS sends a network slice template query response to the Sender.

In an embodiment of the present invention, if the NMS performs step 803 above, the network slice template query response may contain an indication that the network slice template query was successful. The network slice template query response may include the network slice template information received by the NMS in step 804. If the NMS does not perform step 803 above, the network slice template query response may include an indication that the network slice template query failed.

Fig. 9 is a schematic flowchart illustrating a network slice template deletion process according to an embodiment of the present invention, where the network slice template deletion process is to delete a network slice template stored in a hierarchy by the hierarchy, and may be to delete one or more versions of the network slice template. The process illustrated in FIG. 9 includes the following steps:

901. sender sends a network slice template delete request to NMS.

Wherein the network slice template deletion request includes network slice template information requesting deletion.

In an embodiment of the present invention, the network slice template information requesting deletion may include at least one network function in the network slice template, a resource requirement of each network function, and/or a description of a relationship between each network function. The network slice template information requesting deletion may include an identification of the network slice template. The identifier of the network slice template requesting deletion may include version information of the network slice template, such as a version number. If the network slice template deletion request contains template information of one version of the network slice template, the network slice template deletion request may contain an identifier of the network slice template and a corresponding version number. If the network slice template deletion request contains template information of all versions of the network slice template, the network slice template deletion request may contain an identification of the network slice template.

902. And the NMS judges whether the network slice template is in a disabled state. If yes, go to step 903 or 904; otherwise, go to step 905.

In the embodiment of the invention, the NMS checks whether the network slice template requested to be deleted exists, further judges whether the network slice template requested to be deleted is in a forbidden state, and further judges whether the network slice template requested to be deleted is used by a user. If the network slice template requested to be deleted does not exist, jumping to step 905; if the network slice template requested to be deleted is in the enabled state, jumping to step 905; if the network slice template requested to be deleted is in a disabled state and is being used by a user, step 903 is entered; if the network slice template requested to be deleted is in a disabled state and not used by the user, then jump to step 904.

903. The NMS marks the network slice template as to be deleted.

In the embodiment of the present invention, when the network slice template requested to be deleted is in a disabled state and is being used by a user, the network slice template cannot be deleted, and the NMS marks the network slice template in a to-be-deleted state. The network slice template is in a state to be deleted until the user using the network slice template stops using the network slice template, and then the step 904 is executed.

The above step 903 is an optional step, and the NMS determines in step 902 that the network slice template requested to be deleted is in a disabled state and is being used by the user.

904. The NMS sends a notification to have the hierarchy delete the network slice template.

Wherein the notification includes network slice template information.

In an embodiment of the present invention, the NMS sends a notification for the hierarchy to delete the network slice template stored in the hierarchy, which may be network slice template information for deleting one or more versions of the network slice template. The network slice template requesting deletion may be deleted by reproducibility if the network slice template requesting deletion is in a disabled state and not used by a user. And if the network slice template requested to be deleted is in a state to be deleted, the network slice template requested to be deleted can be deleted by reproducibility after the user stops using the network slice template. The network slice template information may include at least one network function in the network slice template requested to be deleted, a resource requirement of each network function, and/or a description of a relationship between each network function. The network slice template information may include an identification of the network slice template requested for deletion. The identifier of the network slice template may include version information, such as a version number, of the network slice template requested to be deleted.

The above step 904 is an optional step, and may be executed after the NMS determines in step 902 that the network slice template requested to be deleted is in the disabled state and is not used by the user, or may be executed after the NMS marks in step 903 the network slice template requested to be deleted as a state to be deleted until the user stops using the network slice template.

905. The NMS sends a network slice template delete response to the Sender.

In the embodiment of the present invention, if the NMS performs the step 903 or the NMS performs the step 904 and deletes the network slice template after the network slice template stops being used, the network slice template deletion response may include an indication indicating that the network slice template deletion is successful. The network slice template delete response may contain an indication that the network slice template deletion failed if the NMS did not perform step 903 or step 904 above and deletes the network slice template after it ceases to be used. If the NMS determines in step 902 above that the network slice template requested for deletion is not present, the network slice template deletion response may include an indication that the network slice template requested for deletion is not present or has been deleted. If the NMS determines in step 902 above that the network slice template requested for deletion is in the enabled state, the network slice template deletion response may include an indication that the network slice template requested for deletion is in the enabled state. If the NMS marks the network slice template requested for deletion as pending deletion in step 903 above and the network slice template requested for deletion is still in use by the user, the network slice template deletion response may contain an indication that the network slice template requested for deletion is in pending deletion. The network slice template deletion response may include network slice template information for the requested deletion. The network slice template deletion response may include an identification of the network slice template requested for deletion. The identifier of the network slice template requesting deletion may include version information of the network slice template, such as a version number.

906. NMS to 3^rdparty sends a network slice template delete indication.

In the embodiment of the invention, if the network slice template information requesting deletion contains 3^rdThe network function information provided by party, the NMS may send 3 the notification to replay to delete the network slice template^rdparty sends the network slice template deletion indication to inform 3^rdparty's provided network function information is deleted.

The above step 906 is optional and may be performed after the NMS notifies the reproducibility to delete the network slice template in step 904. There is no front-to-back order relationship between this step and the above step 905, and the NMS may not execute the step 905 and the step 906 sequentially, or may execute only the step 905.

The above-mentioned scheme provided by the embodiment of the present invention is introduced mainly from the perspective of interaction between network elements. It will be appreciated that each network element, in order to implement the above-described functions, comprises corresponding hardware structures and/or software modules for performing the respective functions. Those skilled in the art will readily appreciate that the present patent application, in conjunction with the embodiments disclosed herein, may be implemented in hardware or a combination of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present patent application.

The present application further provides embodiments of apparatus for performing the steps and methods of the above-described method embodiments. It is noted that the device embodiments may be used in conjunction with the above-described methods, or may be used alone.

Fig. 10 is a schematic structural diagram of a network management system according to an embodiment of the present invention. As shown in fig. 10, the network management system 1000 includes a processor 1001, a memory 1002, and a communication interface 1003. The processor 1001 is connected to the memory 1002 and the communication interface 1003, for example, the processor 1001 may be connected to the memory 1002 and the communication interface 1003 by a bus. The network management system in the embodiment of the invention can be a network slice manager or a network slice management and orchestrator.

The processor 1001 is configured to support the network management system to perform the corresponding functions in the above-described method. The Processor 1001 may be a Central Processing Unit (CPU), a Network Processor (NP), a hardware chip, or any combination thereof. The hardware chip may be an Application-Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a Field Programmable Gate Array (FPGA), a General Array Logic (GAL), or any combination thereof.

The memory 1002 is used for storing signaling and data that the network management system needs to send, receiving signaling and data from the sender functional entity, the repository, and/or the third party functional entity, saving the state of the network slice template, and the like. The Memory 1002 may include a Volatile Memory (Volatile Memory), such as a Random-Access Memory (RAM); the Memory 1002 may also include a Non-Volatile Memory (Non-Volatile Memory), such as a Read-Only Memory (ROM), a Flash Memory (Flash Memory), a Hard Disk Drive (Hard Disk Drive, HDD) or a Solid-State Drive (SSD); the memory 1002 may also comprise a combination of the above-described types of memory.

The communication interface 1003 is used for the network management system to communicate with the sender functional entity, the repository, and/or the third party functional entity, and to send and receive signaling and data involved in the above methods to and from the sender functional entity, the repository, and/or the third party functional entity.

The processor 1001 may perform the following operations:

transmit upstream signaling and data and/or receive downstream signaling and data through communication interface 1003. The processor 1001 receives requests for putting on shelf, updating, disabling, enabling, querying, deleting, and the like of the network slice template sent by the sender functional entity through the communication interface 1003, and decides and stores interaction of the third-party functional entity and interaction of the third-party functional entity according to the support condition of the network slice template by the current network and the state of the network slice template. The processor 1001 notifies the repository of the shelving, updating, disabling, enabling, querying, deleting, etc. of the network slice template through the communication interface 1003. Alternatively, when the network slice template requested to be shelved or updated is not supported by the current network, the processor 1001 requests the third-party functional entity to provide the first-pass network function information through the communication interface 1003 and receives a corresponding response. Please refer to the embodiments of fig. 4 to 9.

Fig. 11 is a schematic structural diagram of another network management system according to an embodiment of the present invention. As shown in fig. 11, the network management system 1100 includes a receiving module 1101, a processing module 1102, and a sending module 1103. The network management system in the embodiment of the invention can be a network slice manager or a network slice management and orchestrator.

The receiving module 1101 is configured to receive requests for shelving, updating, disabling, enabling, querying, deleting, and the like of the network slice template sent by the sender functional entity, and receive a response for providing the network function information in the network slice template sent by the third party functional entity.

The processing module 1102 performs corresponding processing according to the information received by the receiving module 1101, and sends a partial result of the processing through the sending module 1103. The processing module 1102 determines and stores interactions of the third-party functional entity according to the requests of putting on shelves, updating, disabling, enabling, querying, deleting and the like of the network slice template sent by the sender functional entity, and according to the support condition of the current network on the network slice template and the state of the network slice template. The processing module 1102 notifies the repository of the shelving, updating, disabling, enabling, querying, deleting, etc. of the network slice template through the sending module 1103. Alternatively, when the network slice template requesting for listing or updating is not supported by the current network, the processing module 1102 requests the third-party functional entity to provide the first-pass network function information through the sending module 1103 and receives a corresponding response through the receiving module 1101. Please refer to the embodiments of fig. 4 to 9.

A sending module 1103, configured to send messages notifying the repository of shelving, updating, disabling, enabling, querying, deleting, etc. of the network slice template, send response messages of shelving, updating, disabling, enabling, querying, and deleting of the network slice template to the sender functional entity, and send a request for providing network function information in the network slice template to a third party functional entity.

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

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

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

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

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

Claims

1. A method for managing a network slice template, the method comprising:

a network management system receives a network slicing template management request sent by a sender functional entity;

the network management system informs a storage library to manage the network slice template;

and the network management system sends a response of the network slicing template management to a sender functional entity.

2. The method of claim 1, wherein the network slice template management request is a network slice template onboarding request,

the network management system notifies the repository to load the network slice template into the repository.

3. The method of claim 1, wherein the network slice template management request is a network slice template update request,

the network management system notifies the repository to save a new version of a network slice template in the repository, and/or to disable an old version of a network slice template.

4. The method of claim 1, wherein the network slice template management request is a network slice template disable request,

the network management system notifies the repository to set the network slice template to a disabled state such that the network slice template cannot be used to create, configure, or control network slice instances.

5. The method of claim 1, wherein the network slice template management request is a network slice template enable request, and wherein the network management system notifies the repository to enable the network slice template in a disabled state, such that the enabled network slice template can be used to create, configure, or control a network slice instance.

6. The method of claim 1, wherein the network slice template management request is a network slice template query request,

the network management system queries the repository for information about the network slice templates stored in the repository.

7. The method of claim 1, wherein the network slice template management request is a network slice template delete request,

the network management system informs the repository to delete the network slice template stored in the repository.

8. The method of claim 2, wherein prior to the network management system notifying a repository of management of the network slice template, the method further comprises:

the network management system judges that the current network does not support at least one part of network functions in the network slice template on the shelf;

the network management system requests a third-party functional entity to provide network function information of at least one part of network functions;

and the network management system receives network function information of the at least one part of network functions provided by a third-party functional entity.

9. The method of claim 3, wherein prior to the network management system notifying a repository of the management of the network slice template, the method further comprises:

the network management system judges that the current network does not support at least one part of network functions in the updated network slice template;

10. A network management system, comprising:

the receiving module is used for receiving a network slicing template management request sent by a sender functional entity;

the processing module is used for informing the repository to manage the network slice template; and

and the sending module is used for sending the response of the network slicing template management to the sender functional entity.

11. The network management system of claim 10, wherein the network slice template management request is a network slice template onboarding request,

the processing module notifies the repository to load the network slice template into the repository.

12. The network management system of claim 10, wherein the network slice template management request is a network slice template update request,

the processing module notifies the repository to save a new version of a network slice template in the repository, and/or to disable an old version of a network slice template.

13. The network management system of claim 10, wherein the network slice template management request is a network slice template disable request,

the processing module notifies the repository to set the network slice template to a disabled state such that the network slice template cannot be used to create, configure, or control a network slice instance.

14. The system of claim 10, wherein the network slice template management request is a network slice template enable request, and wherein the processing module notifies the repository to enable the network slice template in a disabled state such that the enabled network slice template can be used to create, configure, or control a network slice instance.

15. The network management system of claim 10, wherein the network slice template management request is a network slice template query request,

the processing module queries the repository for information about the network slice templates stored in the repository.

16. The network management system of claim 10, wherein the network slice template management request is a network slice template delete request,

the processing module notifies the repository to delete a network slice template stored in the repository.

17. The network management system according to claim 11, wherein the processing module is further configured to determine that a current network does not support at least a portion of network functions in the network slice template on shelf before notifying the repository of the management of the network slice template; requesting a third party functional entity to provide network function information of the at least one part of the network function; and receiving network function information of the at least one part of network functions provided by the third-party functional entity.

18. The network management system according to claim 12, wherein the processing module is further configured to determine that a current network does not support at least a portion of network functions in the updated network slice template before notifying the repository to perform the management of the network slice template; requesting a third party functional entity to provide network function information of the at least one part of the network function; and receiving network function information of the at least one part of network functions provided by the third-party functional entity.

19. A computer-readable storage medium, characterized in that it stores a computer program which, when executed by a computer device, is capable of implementing the method of any one of claims 1 to 9.