Service Request and Provision Method, Device, and Storage Medium

Abstract

An embodiment of the present application provides a service request and provision method, device, and storage medium. In the embodiment of the present application, by further opening up the capabilities of the network slice management system, the application server can request network slice template services or network slice capability services other than network slice services from the network slice management system through the open capabilities, which can make full use of the slice management capabilities and resources of the slice management system and improve the utilization efficiency of the slice management capabilities and resources.

Description

Technical Field

[0001] This application relates to the field of mobile communication technologies, and particularly to a service request and provision method, device, and storage medium. Background Art

[0002] The fifth-generation mobile communication technology (5G) system needs to meet different network requirements, such as large bandwidth, low latency, multi-access, etc. Therefore, the network slicing technology is introduced. Network slicing is a way of networking on demand. By using Network Functions Virtualization (NFV) technology, operators can separate multiple virtual end-to-end networks on the unified infrastructure, so as to meet the network performance requirements of different scenarios. In this way, a complete operator network system may be jointly composed of a large number of network slices that meet different scenarios or network characteristics, facing the problem of network slice management.

[0003] Regarding the problem of network slice management, 3GPP SA5 defines a slice management system for operators for network slices, mainly including Communication Service Management Function (CSMF), Network Slice Management Function (NSMF), and Network Slice Subnet Management Function (NSSMF). Among them, CSMF is mainly responsible for converting the communication service requirements of the slice requester into network slice requirements; NSMF is mainly responsible for the management and coordination of Network Slice Instances (NSIs); NSSMF is mainly responsible for the management and coordination of Network Subnet Slice Instances (NSSIs). Then, the NFV Orchestrator (NFVO) and NFV Manager (NFVM) assist in generating slice network entities corresponding to NSSIs or NSIs.

[0004] Through the above slice management system, operators can provide network slice services for slice requesters in different application scenarios, that is, they can reasonably manage the entire life cycle of network slice creation, activation, update, release, etc. In the prior art, the main research or use is the ability of the slice management system to provide network slice services, which does not fully utilize the slice management capabilities and resources of the slice management system, resulting in low utilization efficiency of the slice management capabilities and resources in the slice management system. Summary of the Invention

[0005] Multiple aspects of the present application provide a service request and provision method, device, and storage medium for using a network slice management system to provide more abundant services related to network slices, and improve slice management capabilities and resource utilization efficiency.

[0006] An embodiment of the present application provides a service request method applicable to an application server. The method includes: sending a service request message to a network entity in a network slice management system, where the service request message includes service parameters to request the network slice management system to provide a target service for it, and the target service includes a network slice template service or a network slice capability service; receiving a response message returned by the network entity for the service request message, where the response message carries information on whether the network slice management system can successfully provide the target service for the application server.

[0007] An embodiment of the present application further provides a service provision method applicable to a network entity in a network slice management system. The method includes: receiving a service request message sent by an application server, where the service request message includes service parameters for requesting a target service from the network slice management system; providing the target service for the application server according to the service parameters, where the target service includes a network slice template service or a network slice capability service; and returning a response message to the application server, where the response message carries information on whether the network slice management system can successfully provide the target service for the application server.

[0008] An embodiment of the present application further provides an application server, including: a memory and a processor; the memory is used for storing a computer program; the processor is coupled to the memory and is used for executing the computer program to: send a service request message to a network entity in a network slice management system, where the service request message includes service parameters to request the network slice management system to provide a target service for it, and the target service includes a network slice template service or a network slice capability service; receive a response message returned by the network entity for the service request message, where the response message carries information on whether the network slice management system can successfully provide the target service for the application server.

[0009] An embodiment of the present application further provides a network entity, including: a memory and a processor; the memory is used for storing a computer program; the processor is coupled to the memory and is used for executing the computer program to: receive a service request message sent by an application server, where the service request message includes service parameters for requesting a target service from the network slice management system; provide the target service for the application server according to the service parameters, where the target service includes a network slice template service or a network slice capability service; and return a response message to the application server, where the response message carries information on whether the network slice management system can successfully provide the target service for the application server.

[0010] The embodiments of the present application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to implement the steps in each of the methods provided by the embodiments of the present application.

[0011] The embodiments of the present application also provide a computer program product, including a computer program or instruction, which, when executed by a processor, causes the processor to implement the steps in each of the methods provided by the embodiments of the present application.

[0012] In the embodiments of the present application, by further opening up the capabilities of the network slice management system, the application server can request network slice template services or network slice capability services other than network slice services from the network slice management system through capability opening, which can make full use of the slice management capabilities and resources of the slice management system and improve the utilization efficiency of slice management capabilities and resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation of the present application. In the drawings:

[0014] Figure 1a is a schematic structural diagram of a network system provided by an embodiment of the present application;

[0015] Figure 1b is a schematic architecture diagram of a network slice management system adopting two-level deployment in an embodiment of the present application;

[0016] Figure 2 is a schematic flowchart of an application server requesting a network slice template service from a network slice management system provided by an embodiment of the present application;

[0017] Figure 3 is a schematic flowchart of an application server requesting a network slice capability service from a network slice management system provided by an exemplary embodiment of the present application;

[0018] Figures 4a - 4c is a schematic service flowchart of requesting a customized slice template through CSMF, NSMF, and NSSMF respectively provided by an embodiment of the present application;

[0019] Figures 4d - 4f is a schematic service flowchart of requesting to change a slice template through CSMF, NSMF, and NSSMF respectively provided by an embodiment of the present application;

[0020] Figures 4g - 4i is a schematic service flowchart of requesting to delete a slice template through CSMF, NSMF, and NSSMF respectively provided by an embodiment of the present application;

[0021] Figures 5a - 5c Schematic diagram of service processes for querying network slice capability information respectively through CSMF, NSMF, and NSSMF provided by embodiments of this application;

[0022] Figures 5d - 5f Schematic diagram of service processes for deploying network slice capabilities respectively through CSMF, NSMF, and NSSMF provided by embodiments of this application;

[0023] Figures 5g - 5i Schematic diagram of the process for subscribing to network slice capability information update notification services respectively through CSMF, NSMF, and NSSMF provided by embodiments of this application;

[0024] Figure 6 Schematic diagram of the structure of an application server provided by embodiments of this application;

[0025] Figure 7 Schematic diagram of the structure of a network entity provided by embodiments of this application. Detailed implementation manners

[0026] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments of this application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the scope of protection of this application.

[0027] Figure 1a Schematic diagram of the structure of a network system provided by embodiments of this application. As Figure 1a shown, the network system 100 includes: a network slice management system 20 and an application server 30 in a mobile communication network 10.

[0028] In this embodiment, the network architecture of the mobile communication network 10 and the communication system used are not limited. Any mobile communication network introducing network slice technology is applicable to the embodiments of this application. As Figure 1aAs shown, the mobile communication network 10 can be a 5G mobile communication network (abbreviated as 5G network). In addition, it can also be a 4G network or a mobile communication network of a higher standard that may appear in the future. Regardless of the standard of the mobile communication network 10, its architecture mainly includes, but is not limited to: Radio Access Network (RAN) and Core Network (CN), and further includes a transmission network. According to the different network standards, the network elements included in the access network and core network of the mobile communication network 10 will also vary. Taking the 5G network as an example, the access network in the 5G network mainly includes 5G base stations; the 5G Core Network (5GC) includes, but is not limited to, the following network functions and entities: Authentication Server Function (AUSF), User plane Function (UPF), Access and Mobility Management Function (AMF), Unified Data Management (UDM), Network Exposure Function (NEF), Session Management Function (SMF), Network Slice Selection Function (NSSF), Network Storage Function (NF Repository Function, NRF), Policy Control function (PCF), Application Function (AF), and other network elements. In Figure 1a only PCF, UDM, and UPF are shown.

[0029] In this embodiment, the mobile communication network 10 introduces network slicing technology, which can cut out multiple virtual end-to-end networks (i.e., network slices) on a unified infrastructure to meet different communication service requirements, such as high-bandwidth requirements, low-latency requirements, and multi-access requirements. Among them, the network slicing technology can be implemented in different parts of the mobile communication network 10, such as the access network side, the core network side, and the transmission network side. For the sake of distinction, the network slices implemented in different parts (or different domains) of the mobile communication network 10 are regarded as subnet slices. The subnet slices of one or more of the above parts can be connected together to form a network slice that can provide complete services for users. Each network slice is logically isolated from the access network to the transmission network and then to the core network.

[0030] The mobile communication network 10 supports network slicing technology, allowing multiple network slices to be sliced out on its underlying devices according to different communication services. However, the specific method of slicing network slices on the infrastructure of the mobile communication network 10 depends on the network slice management system 20. As Figure 1a shown, the network slice management system 20 includes network entities such as CSMF 21, NSMF 22, and NSSMF 23; CSMF 21 provides an interface to communicate with NSMF 22, and NSMF 22 provides an interface to communicate with NSSMF 23. Among them, CSMF 21 is responsible for receiving the communication service requirements provided by scenario users, completing the conversion of user communication service requirements into network slice requirements, and sending the network slice requirements to NSMF 22. Among them, the network slice requirements can be implemented as Service Level Agreement (SLA) requirements. NSMF 22 is mainly responsible for creating NSIs according to network slice requirements, decomposing network sub-slice requirements to each sub-slice, and sending the network sub-slice requirements to NSSMF 23 of each subnet; NSSMF 23 is responsible for completing the mapping from NSI to NSSI according to the received network sub-slice requirements, and calling NFVO, NFVM, and Element Management System (EMS), etc. to assist in generating slice network entities corresponding to NSSI or NSI, that is, completing the deployment of each subnet slice and its dependent computing, network, storage resources, etc. on the Network Functions Virtualization Infrastructure (NFVI) of the mobile communication network 10.

[0031] In this embodiment, the deployment implementation method of the network slice management system 20 is not limited. For example, the network slice management system 20 can be deployed at one level or multiple levels; in the case of multiple-level deployment, NSMF 22 is deployed in each level of the management system, and one or more NSSMF 23 are deployed under NSMF 22. NSMF 22 is responsible for managing and scheduling the NSIs at its own level, and the NSSIs at its own level are managed and scheduled by NSSMF 23. Optionally, the NSMF 22 at the upper level can be connected to the NSMF 22 at the lower level to achieve interconnection between the upper and lower management systems, but it is not limited to this. For example, it can also be the NSSMF 23 in two adjacent levels that are connected to achieve interconnection between the upper and lower management systems; or, it can also be the NSMF 22 at the upper level and the NSSMF 23 at the lower level that are connected to achieve interconnection between the upper and lower management systems. As Figure 1b shown, it is the architecture of the network slice management system 20 with two-level deployment. In Figure 1bIn the network slice management architecture shown, the sub-slices (such as NSI and / or NSSI) in the access network and transport network of Area A are responsible by the secondary management system deployed in Area A. Specifically, NSI is responsible by NSMF 22 deployed in Area A, and NSSI is responsible by NSSMF 23 deployed in Area A; the sub-slices in the access network and transport network of Area B are responsible by the secondary management system deployed in Area B. Specifically, NSI is responsible by NSMF 22 deployed in Area B, and NSSI is responsible by NSSMF 23 deployed in Area B; the sub-slices in the core network (including user plane and control plane) of Area A and Area B are all responsible by the primary management system. Optionally, the network slice management system 20 can be hierarchically deployed with administrative regions as the granularity. For example, the primary management system can be deployed in each province, and one NSMF and several NSSMFs are correspondingly deployed within the province; or, the primary management system can also be deployed across several provinces. In this case, one NSMF can be deployed across provinces, and this NSMF is responsible for scheduling and managing the NSIs within these provinces, and several NSSMFs are deployed in each province, responsible for scheduling and managing the NSSIs within each province.

[0032] In this embodiment, the scenario user refers to the application server 30. That is, the mobile communication network 10 and the network slice management system 20 cooperate with each other to provide network slice-related services for the application server 30, meeting the requirements of the application server 30 for network performance in different scenarios. Among them, the application server 30 can be a third-party server. For example, it can be an edge server in an edge cloud system, but not limited to this. In Figure 1a the figure, taking the application server 30 as an edge server in an edge cloud system as an example. The application server 30 can be one or more. When there are multiple application servers 30, the multiple application servers 30 can come from the same third party or different third parties. Of course, the application server 30 can also come from the operator. Among them, for the application server 30 from a third party and the application server 30 from an operator, they may have different permissions when using the network slice-related services provided by the network slice management system 20. In the embodiments of this application, the case where the application server 30 is a third-party server is mainly concerned, and the case where the application server 30 comes from the operator will be briefly described.

[0033] In this embodiment, the network slice management system 20 can provide management capabilities related to network slices, referred to as network slice management capabilities. Such management capabilities include, in addition to the ability to provide network slice services to the application server 30 according to the communication service requirements of the application server 30, the management of network slice-related templates and the management of the network slice capabilities of the mobile communication network 10 itself. Among them, the management of the network slice capabilities of the mobile communication network 10 itself means that it can identify whether the mobile communication network 10 has network slice capabilities and, in the case of having network slice capabilities, manage information such as the coverage range and topology of the network slice capabilities it has. To make full use of the network slice management capabilities of the network slice management system 20, this embodiment can, by means of the capability open function of the mobile communication network 10, fully open the network slice management capabilities of the network slice management system 20 to the application server 30. That is, the capabilities of the network slice management system 20 to provide network slice services to the application server 30, the management capabilities of network slice-related templates, and the management capabilities of the network slice capabilities of the mobile communication network 10 itself are all opened to the application server 30, so as to fully utilize the network slice management resources of the network slice management system 20 and improve the utilization efficiency of network slice management resources.

[0034] In the embodiment of this application, the focus is on the opening process of the "management capabilities of network slice-related templates" and the "management capabilities of the network slice capabilities of the mobile communication network 10 itself" of the network slice management system 20. Based on the opening of these two capabilities, the application server 30 can interact with network entities in the network slice management system 20 and request the network slice management system 20 to provide it with other network slice-related services other than "network slice services", denoted as target services. In the embodiment of this application, the target services mainly refer to network slice template services and network slice capability services. Among them, based on the opening of the "management capabilities of network slice-related templates" of the network slice management system 20, the application server 30 can request the network slice management system 20 to provide it with network slice template services; based on the opening of the "management capabilities of the network slice capabilities of the mobile communication network 10 itself" of the network slice management system 20, the application server 30 can request the network slice management system 20 to provide it with network slice capability services.

[0035] Specifically, the application server 30 sends a service request message to a network entity in the network slice management system 20. The service request message includes service parameters, which are used to request the network slice management system 20 to provide a target service for it. The target service includes a network slice template service or a network slice capability service different from the network slice service; the network entity in the network slice management system 20 receives the service request message sent by the application server 30, provides the target service for the application server 30 according to the service parameters in the service request message, and returns a response message for the service request message to the application server 30. The application server 30 receives the response message returned by the network entity in the network slice management system 20, and the response message carries information on whether the network slice management system 20 can successfully provide the target service for the application server 30.

[0036] One case: The application server 30 can interact with a network entity in the network slice management system 20 to request the network slice management system 20 to provide a service related to the template of the network slice, which is simply referred to as the network slice template service, that is, the target service can be implemented as the network slice template service. For the convenience of distinction and description, the template related to the network slice is simply referred to as the slice template, and the slice template includes a Network Slice Template (NST) and / or a Network Slice Subnet Template (NSST). As Figure 2 shown, the interaction process in which the application server 30 requests the network slice template service from the network slice management system 20 includes:

[0037] 201. The application server 30 sends a service request message to a network entity in the network slice management system 20. The service request message includes service parameters, which are used to request the network slice management system 20 to provide the network slice template service for it.

[0038] 202. After receiving the service request message, the network entity in the network slice management system 20 provides the network slice template service for the application server 30 according to the service parameters in the service request message.

[0039] 203. The network entity in the network slice management system 20 returns a response message for the service request message to the application server 30. The response message carries information on whether the network slice management system 20 can successfully provide the network slice template service for the application server 30.

[0040] Optionally, after receiving the service request message, the network slice management system 20 can determine whether it can successfully provide the network slice template service for the application server 30 according to the service parameters. If it can successfully provide the network slice template service for the application server 30, it returns a confirmation message of the service request to the application server 30 as a response message, indicating that the network slice management system 20 can successfully provide the network slice template service for the application server 30. If it cannot successfully provide the network slice template service for the application server 30, it returns a message indicating a service request error to the application server 30 as a response message, indicating that the network slice management system 20 cannot successfully provide the network slice template service for the application server 30. Further, in the case of returning a message indicating a service request error to the application server 30 as a response message, the error reason or reason code for the inability to provide the network slice template service can also be carried in the response message. Among them, the error reason can be any one of the following: 1. The application server 30 does not have the permission to customize the slice template. Here, the permission can refer to that the operator and the manufacturer to which the application server belongs have not signed an SLA related to slice template management, etc.; 2. The operator core network resources cannot support the generation of a customized slice template that meets the requirements of the application server 30.

[0041] Further optionally, in the case where the network slice management system 20 can successfully provide the network slice template service for the application server 30, considering that the network slice management system 20 providing the network slice template service for the application server 30 may be asynchronous, that is, after the application server provides the slice template requirement to the network slice management system 20, it may take a certain amount of time to receive the notification message from the network slice management system 20 confirming the completion of the slice template generation. Therefore, as Figure 2 shown, after step 203, it further includes:

[0042] 204. The network entity in the network slice management system 20 returns a notification message indicating that the network slice template service has been completed to the application server 30.

[0043] In this embodiment, the network slice management system 20 may provide a default slice template for the application server 30. Whether the application server 30 is from a third party or from an operator, it can request to use the default slice template provided by the network slice management system 20. The default slice template includes a default NST and / or a default NSST. That is to say, the network slice template service may include the service that the application server 30 requests to use the default NST and / or the default NSST provided by the operator. However, the default slice template provided by the network slice management system 20 is fixed, and the resources instantiated according to this default slice template are fixed, which may not meet the requirements of the application server 30, especially when the application server 30 is from a third party. For example, the application server 30 requires the deployment of the UPF to sink into the DN domain and requires the UPF to have a Deep Packet Inspection (DPI) function, etc., but the default slice template cannot meet this requirement. In view of this, in addition to providing a default slice template for the application server 30, the network slice management system 20 also allows the application server 30 from a third party to customize the slice template according to its own application requirements. The customized slice template includes a customized NST and / or a customized NSST. Optionally, the operator may maintain two template libraries, namely a default template library and a customized template library. The default template library is used to store the default slice templates provided by the operator; the customized template library is used to store the customized slice templates triggered and generated by a third-party server (such as the application server 30 from a third party). For any service provider S, it can use its own customized slice template alone. For example, some slice templates with strong specialization are mainly used by the service provider S. However, for some slice templates with generality, the service provider S can also share or license them to other service providers for use. Among them, in addition to being identified by a template identifier (ID), the customized slice template may optionally also manage a third-party server identifier or an identifier that can represent a third party, which is not limited herein. For example, an identifier field of a customized manufacturer may be added to the ID of the customized slice template to carry the identifier of the customized manufacturer. If the application server 30 is from the service provider that requests the customized slice template, after the network slice management system 20 generates the customized slice template for the application server 30, the identifier of the application server 30 may also be stored in the identifier field of the customized manufacturer in the ID of the customized slice template, so as to establish an association relationship among the ID of the customized slice template, the identifier of the customized manufacturer, and the identifier of the application server 30. Of course, the ID of the customized slice template may not carry the identifier of the customized manufacturer, but the network slice management system 20 is responsible for associating the ID of the customized slice template with the identifier of the customized manufacturer and the identifier of the application server 30, and maintaining the association relationship among the three.

[0044] Furthermore, the network slice management system 20 also allows the application server 30 to change its customized slice template at any time according to application requirements, and allows the application server 30 to delete its customized slice template according to application requirements. For application servers 30 from third parties, they have the authority to change or delete their customized slice templates; for application servers deployed by operators, they can change or delete the system default slice templates. In view of this, when the network slice management system 20 receives a request to delete a slice template from a third-party application server 30, it can determine whether the slice template to be deleted is a system default slice template or a customized slice template; if the slice template to be deleted is a customized slice template, the ID of the customized manufacturer can be obtained from the ID of the customized slice template to be deleted, or the ID of the customized manufacturer corresponding to the customized slice template to be deleted can be obtained from the association between the ID of the maintained customized slice template and the ID of the customized manufacturer; then it is determined whether the ID of the customized manufacturer matches the ID of the application server 30 that initiates the deletion request, that is, it is determined whether the application server 30 has the authority to delete the customized slice template; if the two match, it means that the application server 30 has the authority to delete the customized slice template, and the deletion operation of the customized slice template is performed; if the two do not match, an error is reported, such as outputting a deletion error message, to notify the application server 30 that it does not have the authority to delete the customized slice template. In addition, if the slice template to be deleted is the system default slice template, an error can also be reported to notify the application server 30 as a third-party server that does not have the authority to delete the system default slice template. Optionally, custom templates and default templates can also be placed in the same template library.

[0045] That is to say, the network slice template services that the application server 30 from a third party can request from the network slice management system 20 include but are not limited to: requesting the network slice management system 20 to customize and generate a slice template for it, requesting the network slice management system 20 to change the slice template for it, and requesting the network slice management system 20 to delete the slice template for it. It should be noted that for different network slice template services, the service parameters included in the service request will also be different. Among them, for the case of requesting the network slice management system 20 to generate a customized slice template, the service parameters included in the service request message may include a first parameter set required to create the customized slice template, and the first parameter set includes at least one of quality of service (QoS) parameters, network capacity parameters, configuration parameters of network elements, application-related parameters, geographical location of the DN, and deployment method of the UPF; further, the QoS parameters can also be referred to as network KPI parameters, for example, they may include but are not limited to: end-to-end delay, rate, bandwidth, uplink and downlink throughput, network jitter, packet loss rate, etc., where the rate includes uplink guaranteed bit rate (GBR), downlink GBR, uplink aggregate maximum bit rate (AMBR), downlink AMBR. In addition, it may also include application type-related parameters or descriptive information; the network capacity parameters include but are not limited to: maximum number of users or maximum number of terminal accesses, number of active users, maximum number of protocol data unit (PDU) session establishments, regional capacity, user density, etc.; the application-related parameters include but are not limited to: access type, billing requirements, coverage area, isolation, mobility support, reliability indicators, security, etc. For the case of requesting the network slice management system 20 to change the slice template, the service parameters included in the service request message may include: a template identifier (ID) for identifying the slice template to be changed, and a first parameter set required to change the template. Among them, the first parameter set required to change the template is the same or similar to the first parameter set required to create the template, which can be referred to the foregoing and will not be elaborated here. For the case of requesting the network slice management system 20 to delete the customized slice template, the service parameters included in the service request message may include: a template identifier (ID) for identifying the slice template to be deleted.

[0046] Among them, in the process of generating a customized slice template for the application server, a customized NST can be generated for the application server and an NSST can be associated with the customized NST. The NSST associated with the customized NST may include at least one NSST customized by the service provider corresponding to the application server, or may include at least one NSST customized by the service provider corresponding to the application server and at least one system default NSST, or may all be system default NSSTs.

[0047] Among them, during the process of changing the customized slice template for the application server, only the customized NST can be changed. For example, change the NST A customized by the service provider P1 corresponding to the application server to the NST B customized by the service provider P1, and directly associate the NSST associated with the customized NST A under the customized NST B. Or, only the NSST customized by the service provider P1 can be changed. For example, change the NSST A_1 customized by the service provider P1 associated with the NST A customized by the service provider P1 to the NSST C_1 customized by another service provider P2 and authorized to the service provider P1. Then, the NSST A_1 associated with the NST A can be changed to the NSST C_1, and the mapping relationship between the NST A and the NSST A_1 can be modified to the mapping relationship between the NST A and the NSST C_1. Of course, the NST and NSST customized by the service provider P1 can also be changed simultaneously. Among them, the application server can indicate whether it needs to change the NST or NSST, or both the NST and NSST simultaneously, through the template identifier included in the service parameters. That is to say, the slice template to be changed can be the NST and / or NSST, and the template identifier included in the service parameters can be the NST identifier and / or the NSST identifier.

[0048] Among them, during the process of deleting the customized slice template for the application server, the NST customized by the service provider P1 corresponding to the application server and its associated NSST customized by the service provider P1 can be deleted. For example, delete the NST A customized by the service provider P1. At this time, it is necessary to delete the NSST A customized by the service provider P1 associated with the customized NST A, and delete the customized NST A and the mapping relationship between the NST A and all NSSTs. It should be noted that if the customized NST A is also associated with the system default NSST or the NSST authorized by other service providers for use, only the mapping relationship between the customized NST A and these NSSTs needs to be deleted, and these NSSTs are not deleted. Or, only the NSST customized by the service provider P1 can be deleted. For example, delete the NSST A_1 customized by the service provider P1 associated with the NST A customized by the service provider P1. Then, the NSST A_1 associated with the NST A can be deleted, and the mapping relationship between the NST A and the NSST A_1 can be deleted. Among them, the application server can indicate whether it needs to delete the NST or NSST, or both the NST and NSST simultaneously, through the template identifier included in the service parameters. That is to say, the slice template to be deleted can be the NST and / or NSST, and the template identifier included in the service parameters can be the NST identifier and / or the NSST identifier.

[0049] It should be noted that when only the NSST is changed or deleted, the network slice management system 20 can send an inquiry message to the application server to inquire whether the application server needs to change or delete the corresponding NST; and further process according to the response message returned by the application server for this inquiry message. If the response message returned by the application server indicates that there is no need to change or delete the corresponding NST, only the NSST is changed or deleted; if the response message returned by the application server indicates that the corresponding NST needs to be changed or deleted, the processing is performed according to the situation of changing or deleting the NST and NSST simultaneously.

[0050] Further optionally, when the application server requests to specify the use of a customized template that does not belong to the service provider corresponding to the application server, or the relevant parameters in the parameter set sent by the application server have been proposed by other third-party manufacturers and the customized template ID has been successfully generated, the network slice management system 20 can first request the manufacturer to which the customized slice template belongs for authorization. After the manufacturer to which the customized slice template belongs confirms the authorization, the ID of the customized slice template is sent to the application server, and the permission is opened to the application server so that the application server can use the specified customized slice template. Among them, the ID of a customized slice template can be associated with multiple application service providers to provide slice template services for multiple application service providers.

[0051] Another case: The application server 30 can interact with the network entities in the network slice management system 20 to request the network slice management system 20 to provide it with services related to the network slice capabilities of the mobile communication network 10, simply referred to as network slice capability services, that is, the target service can be implemented as network slice capability services. As Figure 3 shown, the interaction process of the application server 30 requesting network slice capability services from the network slice management system 20 includes:

[0052] 301. The application server 30 sends a service request message to the network entities in the network slice management system 20. The service request message includes service parameters, and the service parameters are used to request the network slice management system 20 to provide it with network slice capability services.

[0053] 302. After receiving the service request message, the network entities in the network slice management system 20 provide network slice capability services for the application server 30 according to the service parameters in the service request message.

[0054] 303. The network entities in the network slice management system 20 return a response message for the service request message to the application server 30. The response message carries information on whether the network slice management system 20 can successfully provide network slice capability services for the application server 30.

[0055] Optionally, after receiving the service request message, the network slice management system 20 can determine whether it can successfully provide the network slice capability service for the application server 30 according to the service parameters. If it can successfully provide the network slice capability service for the application server 30, it returns an acknowledgement message of the service request message to the application server 30 as a response message, indicating that the network slice management system 20 can successfully provide the network slice capability service for the application server 30. If it cannot successfully provide the network slice capability service for the application server 30, it returns a message indicating an error in the service request message to the application server 30 as a response message, indicating that the network slice management system 20 cannot successfully provide the network slice capability service for the application server 30. Further, in the case of returning a message indicating an error in the service request message to the application server 30 as a response message, the error reason or reason code for the inability to provide the network slice capability service can also be carried in the response message. The error reason can be at least one of the following: 1. The application server 30 does not have the permission to perform operations related to the slice capability; 2. The operator network resources in the relevant area cannot implement the network slice function (except for the branch requesting the deployment of the network slice capability).

[0056] Further optionally, in the case where the network slice management system 20 can successfully provide the network slice capability service for the application server 30, considering that the network slice management system 20 providing the network slice capability service for the application server 30 may be asynchronous, that is, it may take a certain amount of time to receive the notification message from the network slice management system 20 confirming the network slice capability service after the application server provides the prelude of the slice capability service to the network slice management system 20, therefore, as Figure 3 shown, after step 303, it further includes:

[0057] 304. The network entity in the network slice management system 20 returns a notification message indicating that the network slice capability service has been completed to the application server 30.

[0058] In this embodiment, the network slice management system 20 may manage the network slice capabilities of the mobile communication network 10. For example, it can identify whether the mobile communication network 10 has network slice capabilities. In the case where the mobile communication network 10 has network slice capabilities, it can also manage information such as the coverage, deployment, and topology of the network slice capabilities of the mobile communication network 10. Among them, the mobile communication network 10 may not have network slice capabilities, may only have static network slice capabilities, may only have dynamic network slice capabilities, or may have both static and dynamic network slice capabilities at the same time. Among them, the static network slice capability means that there are pre-deployed network slices in the mobile communication network 10, and the number and corresponding resources of these network slices are fixed. The terminal can select the corresponding static slice through the pre-set slice identifier (Single-Network Slice Selection Assitance Information, S-NSSAI). Or obtain the corresponding static slice identifier through the NSSF. The dynamic network slice capability refers to the ability to dynamically deploy network slices in the mobile communication network 10 according to application requirements. Specifically, the operator can perform slice management according to relevant network elements of the slice management system (such as CSMF, NSMF, NSSMF, etc.). The slice management may include slice generation, slice modification, and slice resource release, etc.

[0059] For whether the mobile communication network 10 has dynamic network slice capabilities, it can be determined by checking whether the network slice management system 20 is deployed in the mobile communication network 10. If the network slice management system 20 is deployed, it can be considered that the mobile communication network 10 has or will have dynamic network slice capabilities. Optionally, whether it has dynamic network slice capabilities can also consider whether the operator core network resources can support the generation of new slices, etc. Further, information such as the coverage, deployment, and topology of the network slice capabilities of the mobile communication network 10 is mainly affected by the deployment architecture of the network slice management system 20. Therefore, the deployment architecture information of the network slice management system can be obtained. For example, information such as how many levels of management systems are deployed, how many NSMFs and NSSMFs are deployed at each level of the management system, and in which regions these NSMFs and NSSMFs are deployed can be obtained. Through this information, the coverage, deployment, topology, etc. of the network slice capabilities of the communication network 10 can be identified. In this embodiment, the case where the mobile communication network 10 has dynamic network slice capabilities is taken as an example for illustration.

[0060] In addition to the above judgment methods, it is also possible to determine whether a network entity called Network Slice Selection Function (NSSF) is deployed in the mobile communication network 10. The NSSF is mainly responsible for selecting network slices for terminals accessing the mobile communication network. If the NSSF is deployed, it indicates that the mobile communication network 10 has the network slicing capability. If the NSSF is not deployed, it means that the mobile communication network 10 does not have the network slicing capability. Whether the mobile communication network 10 has dynamic network slicing capability or static network slicing capability, it can be identified by determining whether the NSSF is deployed in the mobile communication network 10.

[0061] By opening the capability of managing the network slicing capability of the above-mentioned mobile communication network 10, before deploying network slices, the application server 30 can query through the network slice management system 20 whether the mobile communication network 10 has the network slicing capability, and can also query information such as the coverage range, deployment situation, and topological structure of the network slicing capability of the mobile communication network 10, so as to determine whether to deploy network slices in this mobile communication network and make preparations for the successful deployment of network slices. In addition, considering that over time and with the development of technology, the network slicing capability of the mobile communication network 10 may change. For example, an operator may deploy network slicing capability in some areas where there was originally no such capability. Another example is that an operator may also integrate the network slicing capabilities of some areas or even stop the network slicing capabilities in certain areas, etc. To facilitate timely understanding of the changes in the network slicing capability of the mobile communication network 10, the application server 30 can also subscribe to the update notification service of network slicing capability information from the network slice management system 20, that is, when the network slicing capability of the mobile communication network 10 changes, the network slice management system 20 will provide the application server 30 with the change information of the network slicing capability. For example, it can be the changed network slicing capability information or the change amount of the network slicing capability information. Specifically, it can be at least one of the two situations of adding a slice management system or adding an NSSF to the core network elements. In addition, the network slicing capability deployed by the operator in the mobile communication network 10 may not meet the requirements of the application server 30 for network slices. For example, the application server 30 needs to deploy network slices in area D, but the currently available network slicing capability of the mobile communication network 10 cannot cover area D. In this case, the application server 30 can also request the network slice management system 20 to deploy network slicing capability for it in area D.

[0062] That is to say, the network slice capability services that the application server 30 can request from the network slice management system 20 include, but are not limited to: requesting the network slice management system 20 to query the network slice capability information of the mobile communication network 10 for it, requesting the network slice management system 20 to deploy network slice capabilities in the mobile communication network 10 for it, and subscribing to the update notification service of the network slice capability information from the network slice management system 20. In the case of requesting network slice capability services, the service parameters in the service request message include a second parameter set, which is used for the network slice management system 20 to provide network slice capability services for it. It should be noted that for different network slice capability services, the second parameter sets included in the service request message will be different. Among them, for the case of requesting the network slice management system 20 to query the network slice capability information of the mobile communication network 10, the second parameter set included in the service request message may include specified area information, indicating that the network slice capability information of the mobile communication network 10 within the specified area needs to be queried; optionally, the second parameter set may also be empty, indicating that the global network slice capability information of the mobile communication network 10 is defaultly queried. For example, the global network slice capability information may be the network slice capability information of the 5G networks deployed by the operator in each province and city across the country. For the case of requesting the network slice management system 20 to deploy network slice capabilities in the mobile communication network 10 for it, the second parameter set included in the service request message may include specified area information, indicating that the network slice management system 20 needs to deploy network slice capabilities within the specified area. For the case of subscribing to the update notification service of the network slice capability information from the network slice management system 20, the second parameter set included in the service request message may include specified area information, indicating that the change information of the network slice capabilities of the mobile communication network 10 (such as 5G network) within the specified area needs to be understood. Optionally, the second parameter set may also be empty, indicating that the change information of the global network slice capabilities of the mobile communication network 10 is defaultly needed to be understood. Optionally, the global network slice capability may refer to the comprehensive information of the network slice capabilities of the operators in each province and city across the country.

[0063] In some embodiments of the present application, regardless of which of the above situations, the network entities in the network slice management system 20 can directly expose their capabilities externally. Then, the network entities in the network slice management system 20 that are docked with the application server 30 can be the CSMF 21, NSMF 22, or NSSMF 23. That is to say, the application server 30 can request network slice template services or network slice capability services from the network slice management system 20 through the CSMF 21, NSMF 22, or NSSMF 23.

[0064] In addition to the above methods, in some other embodiments of the present application, such as Figure 1aAs shown, the network system 100 may further include: a functional entity responsible for exposing the slice management capabilities of the network slice management system 20, simply referred to as the Slice Management Exposure Function. The name of this functional entity is not limited in this embodiment. In this alternative embodiment, each network entity in the network slice management system 20 exposes its capabilities to other objects through this slice management exposure function entity, such as the application server 30. Based on this, the application server 30 can communicate with the CSMF 21, NSMF 22, or NSSMF 23 in the network slice management system 20 through this slice management exposure function entity, so as to request a network slice template service or a network slice capability service from the network slice management system 20. Specifically, when the application server 30 needs to request a network slice template service or a network slice capability service from the network slice management system 20, it can send a service request message to the slice management exposure function entity, and the slice management exposure function entity sends this service request message to the network entity in the network slice management system 20, such as CSMF 21, NSMF 22, or NSSMF 23. Further, in Figure 2 or Figure 3 In the embodiment shown, in step 201 or 301, specifically: the application server 30 sends a service request message to the network entity in the network slice management system 20 through the slice management exposure function entity; in step 203 or 303, specifically: the network entity in the network slice management system 20 returns a response message to the application server 30 through the slice management exposure function entity; in step 204 or 304, specifically: the network entity in the network slice management system 20 sends a notification message to the application server 30 through the slice management exposure function entity. It should be noted that the application server 30 can directly send the service request message to the slice management exposure function entity, and the slice management exposure function entity forwards the service request message to the network entity in the network slice management system 20; or, the application server 30 can also agree on the message transmission format used with the slice management exposure function entity, and encapsulate the service request message or response message between the application server 30 and the network entity in the network slice management system 20 according to this message transmission format for transmission.

[0065] Among them, according to the differences of the network entities in the network slice management system 20 that are docked with the application server 30, the processes of the application server 30 requesting various network slice template services from the network slice management system 20 and the processes of requesting various network slice capability services from the network slice management system 20 will also be different. In the following some embodiments, either taking the application server 30 directly docking with the CSMF 21, NSMF 22 or NSSMF 23 as an example, or taking the application server 30 docking with the CSMF 21, NSMF 22 or NSSMF 23 through the slice management open function entity as an example, the processes of the application server 30 requesting network slice template services or network slice capability services from the network slice management system 20 are respectively described through detailed interaction flowcharts.

[0066] See Figures 4a - 4c , for the service process of requesting a customized slicing template:

[0067] Exemplary embodiment A1: The service process in which the application server 30 docks with the CSMF through the slice management open function entity and requests a customized slice template from the network slice management system 20 is as Figure 4a shown and includes the following steps:

[0068] 40a. The application server and the network slice management system complete mutual authentication through methods such as PSK.

[0069] 41a. The application server sends a slice template customization request message to the slice management open function entity, requesting the slice management open function entity to send this request message to the CSMF in the network slice management system.

[0070] 42a. The slice management open function entity sends the slice template customization request message from the application server to the CSMF in the network slice management system, and the request message includes a parameter set required for customizing the slice template.

[0071] It should be noted that the application server can also directly dock with the CSMF and can directly send a slice template customization request message to the CSMF in the network slice management system.

[0072] Optionally, the parameter set includes at least one of: network KPI parameters, application-related parameters, network capacity parameters, configuration parameters of network elements, geographical location of the DN, and deployment method of the UPF. Among them, the deployment method of the UPF can include the method of sinking to the DN or the method in the operator domain.

[0073] 43a. After receiving the slice template customization request message, the CSMF sends the relevant parameters in the parameter set to the corresponding NSMF.

[0074] Optionally, if the application server needs to deploy network slices in a specified region, a customized slice template can be generated in advance in the specified region. In this application scenario, the slice template customization request message sent by the application server can also carry the specified region information. Optionally, this region information can be used as one of the parameters in the parameter set. Accordingly, the CSMF can select the NSMF that covers the specified area corresponding to the region information according to the region information specified in the slice template customization request message, and send the region information and the relevant parameters in the parameter set to the selected NSMF.

[0075] 44a. The NSMF decomposes the relevant parameters in the parameter set into subnet slice template parameters required to generate the NSST, and sends the subnet slice template parameters to the selected NSSMF for the NSSMF to generate the NSST accordingly.

[0076] For example, the NSMF can send the requirements parameters related to the radio access side (such as the delay requirement on the radio side, etc.) to the NSSMF that manages the radio side sub-slices. The NSMF can also send the requirements parameters related to the core network side (such as the 5G QoS indicator (5G QoS indicator) translated from the delay requirement, Allocation and Retention Priority (ARP)) to the NSSMF that manages the core network side sub-slices.

[0077] Optionally, upon receiving the specified region information sent by the CSMF, the NSMF can select the NSSMF according to the region information, such as selecting the NSSMF deployed within the specified area corresponding to the region information, which can be, for example, the NSSMF that manages the radio side sub-slices and / or the NSSMF that manages the core network side sub-slices.

[0078] Optionally, the NSMF determines the subnet slice template parameters according to the relevant parameters in the parameter set and the decomposition strategy of these relevant parameters. The decomposition strategy is used to decompose the parameters corresponding to the NST-related parameters (i.e., the relevant parameters in the parameter set) into subnet slice template parameters corresponding to at least one NSST. The second method can be that the NSMF decomposes the parameters corresponding to the NST-related parameters (i.e., the relevant parameters in the parameter set) into subnet slice template parameters corresponding to at least one NSST according to the decomposition strategy carried in the NST. Among them, the decomposed subnet slice template parameters include at least one of the core network slice template parameters, the transport network slice template parameters, and the access network slice template parameters, and each subnet slice template parameter can be sent to the NSSMF in the corresponding subnet.

[0079] 45a. The NSSMF generates the NSST required by the application server according to the received subnet slice template parameters.

[0080] 46a. After generating the NSST, the NSSMF returns the ID of the NSST to the NSMF.

[0081] 47a. The NSMF generates an NST associated with the NSST according to the relevant parameters in the parameter set, and associates the ID of the NST with the ID of the NSST returned by the NSSMF to form a mapping relationship between the NST and the NSST.

[0082] Further optionally, the slice template customization request message includes a customization identifier for indicating a request to customize the template, and the CSMF may also send the customization identifier to the NSMF. Based on this, the NSMF may generate a customized NST for the application server 30 according to the customization identifier in the request message, and instruct the NSSMF to generate a corresponding NSST for the application server. Alternatively, a set of third-party server identifiers with the permission to customize the slice template may be maintained in advance. Based on this, the NSMF may determine whether the identifier of the application server 30 belongs to the set of third-party server identifiers. When the identifier of the application server 30 belongs to the set of third-party server identifiers, a customized NST is generated for the application server 30, and the NSSMF is instructed to generate a corresponding NSST for the application server. The identifier of the third-party server may be at least one of DNN, IP address, and FQDN.

[0083] It should be noted here that an NST may be associated with multiple customized NSSTs, or may be associated with at least one default NSST and at least one customized NSST. That is to say, the NSSTs associated with the NST may all be customized NSSTs, or some may be customized NSSTs and some may be default NSSTs.

[0084] Further explanation, in this embodiment, the sequence of generating the NSST and the NST for the application server is not limited. In Figure 4a the figure shows an example where the NSSMF first generates the NSST, and then the NSMF generates the NST associated with the NSST, but it is not limited to this. In addition, the NSMF may also first generate the NST or reference an existing NST, and then instruct the NSSMF to generate the NSST associated with the NST. Alternatively, the NSMF and the NSSMF may also perform the operation of generating the template in parallel, and finally the NSMF establishes the mapping relationship between the NST and the NSST.

[0085] 48a. The NSMF maintains the mapping relationship between the NSST and the NST, and sends the ID of at least one of the NSST and the NST templates to the CSMF for the CSMF to feedback the ID of at least one of the templates to the application server through the slice management open function entity.

[0086] After receiving the ID of at least one template returned by the NSMF, the CSMF returns a slice template customization request confirmation message to the application server via the slice management open function entity, and the confirmation message contains the ID of at least one template.

[0087] 492a. After the slice template generation operation is completed, the CSMF sends a notification message indicating that the operation of generating the slice template has been completed to the application server via the slice management open function entity.

[0088] Optionally, if the operation of generating the slice template by the NSMF or NSSMF fails, the CSMF may send a slice template customization request error message to the application server, and the error message includes the reason or reason code for the slice template generation error.

[0089] Exemplary embodiment A2: The service process in which the application server 30 directly docks with the NSMF and requests a service for customizing a slice template from the network slice management system 20 is as Figure 4b shown and includes the following steps:

[0090] 41b. Bidirectional authentication is completed between the application server and the network slice management system through methods such as PSK.

[0091] 42b. The application server sends a slice template customization request message to the NSMF in the network slice management system, and the request message includes a parameter set required for customizing the slice template.

[0092] Optionally, the application server may also send a slice template customization request message to the slice management open function entity, and the slice management open function entity sends the slice template customization request message to the NSMF in the network slice management system.

[0093] 43b. The NSMF decomposes the relevant parameters in the parameter set into subnet slice template parameters required for generating the NSST, and sends the subnet slice template parameters to the selected NSSMF for the NSSMF to generate the NSST accordingly.

[0094] Optionally, the slice template customization request message sent by the application server may also include specified area information. Optionally, the area information may be used as one of the parameters in the parameter set. Based on this, the NSMF may select the NSSMF according to the area information, for example, select the NSSMF deployed in the specified area corresponding to the area information.

[0095] For a detailed description of decomposing the relevant parameters in the parameter set into subnet slice template parameters, reference may be made to the Figure 4a illustrated embodiment, which will not be elaborated here.

[0096] 44b. The NSSMF generates the NSST required by the application server according to the received subnet slice template parameters.

[0097] 45b. After generating the NSST, the NSSMF returns the ID of the NSST to the NSMF.

[0098] 46b. The NSMF generates an NST associated with the NSST according to the relevant parameters in the parameter set, and associates the ID of the NST with the ID of the NSST returned by the NSSMF to form a mapping relationship between the NST and the NSST.

[0099] Further optionally, the slice template customization request message includes a customization identifier for indicating a request to customize the template. Based on this, the NSMF can generate a customized NST for the application server 30 according to the customization identifier in the request message, and instruct the NSSMF to generate a corresponding NSST for the application server. Alternatively, the NSMF can also pre-maintain a set of identifiers of third-party servers authorized to customize the slice template. Based on this, after receiving the slice template customization request message, it can determine whether the identifier of the application server 30 belongs to the set of identifiers of third-party servers. When the identifier of the application server 30 belongs to the set of identifiers of third-party servers, it generates a customized NST for the application server 30 and instructs the NSSMF to generate a corresponding NSST for the application server.

[0100] It should be noted here that an NST can be associated with multiple customized NSSTs, or can be associated with at least one default NSST and at least one customized NSST. That is to say, the NSSTs associated with an NST can all be customized NSSTs, or some can be customized NSSTs and some can be default NSSTs.

[0101] Further explanation, in this embodiment, there is no limitation on the sequence of generating the NSST and the NST for the application server. In Figure 4b , taking the NSSMF generating the NSST first and then the NSMF generating the NST associated with the NSST as an example for illustration, but it is not limited to this. In addition, the NSMF can also generate the NST first or reference an existing NST, and then instruct the NSSMF to generate the NSST associated with the NST. Alternatively, the NSMF and the NSSMF can also perform the operation of generating the template in parallel, and finally the NSMF establishes the mapping relationship between the NST and the NSST.

[0102] 47b. The NSMF maintains the mapping relationship between the NSST and the NST, and returns a slice template customization request confirmation message to the application server, and the confirmation message contains the ID of at least one of the NSST and the NST templates.

[0103] 48b. After the slice template generation operation is completed, the NSMF sends a notification message indicating that the operation of generating the slice template has been completed to the application server.

[0104] Optionally, if the operation of generating the slice template by the NSMF or NSSMF fails, the NSMF may send a slice template customization request error message to the application server, and the error message includes the reason or reason code for the slice template generation error.

[0105] Exemplary embodiment A3: The application server 30 directly interfaces with the NSSMF to request the service process of customizing the slice template from the network slice management system 20, as Figure 4c shown, including the following steps:

[0106] 41c. The application server and the network slice management system complete mutual authentication through methods such as PSK.

[0107] 42c. The application server sends a slice template customization request message to the NSSMF in the network slice management system, and the request message includes a parameter set required for customizing the slice template.

[0108] Optionally, the application server may also send a slice template customization request message to the slice management open function entity, and the slice management open function entity sends the slice template customization request message to the NSSMF in the network slice management system.

[0109] 43c. After receiving the slice template customization request message, the NSSMF generates the NSST required by the application server according to the relevant parameters in the parameter set.

[0110] It should be noted here that the NSST generated by the NSSMF can all be customized NSST, or part of it can be customized NSST and part can be default NSST.

[0111] Further optionally, the slice template customization request message includes a customization identifier for indicating a request to customize the template. Based on this, the NSSMF can generate a customized NSST for the application server 30 according to the customization identifier in the request message. Or, the NSSMF may also pre-maintain a set of third-party server identifiers with the permission to customize the slice template. Based on this, after receiving the slice template customization request message, it can determine whether the identifier of the application server 30 belongs to the set of third-party server identifiers. In the case where the identifier of the application server 30 belongs to the set of third-party server identifiers, a customized NSST is generated for the application server 30.

[0112] In an alternative embodiment, as shown in step 44c1, after generating the NSST, the NSSMF can directly return a slice template customization request confirmation message to the application server, and the confirmation message contains the ID of the NSST. Further, as shown in step 45c1, after determining that the generation operation of the slice template is completed, the NSSMF sends a notification message to the application server indicating that the operation of generating the slice template has been completed. Thus, the customization service of the slice template is completed. In this alternative embodiment, service providers are allowed to customize only the required NSSTs.

[0113] In another alternative embodiment, as shown in step 44c2, the NSSMF reports the identifier of the generated NSST to the corresponding NSMF for the NSMF to generate an NST corresponding to the NSST and enters step 45c2.

[0114] 45c2. The NSMF generates an NST associated with the NSST according to the received identifier of the NSST, and associates the ID of the NST with the ID of the NSST returned by the NSSMF to form a mapping relationship between the NST and the NSST.

[0115] 46c. After generating the NST, the NSMF returns the ID of the NST to the NSSMF and enters step 47c.

[0116] 47c. The NSSMF returns a slice template customization request confirmation message to the application server, and the confirmation message contains the ID of at least one of the NSST and the NST and enters step 48c.

[0117] 48c. After determining that the generation operation of the slice template is completed, the NSSMF sends a notification message to the application server indicating that the operation of generating the slice template has been completed. Thus, the customization service of the slice template is completed.

[0118] Further explanation, in this embodiment, the order of generating the NSST and the NST for the application server is not limited. In Figure 4c the figure, the case where the NSSMF first generates the NSST and then the NSMF generates the NST associated with the NSST is taken as an example for illustration, but it is not limited to this. In addition, the NSMF can also first generate the NST or reference an existing NST, and then instruct the NSSMF to generate the NSST associated with the NST. Or, the NSMF and the NSSMF can also perform the operation of generating the template in parallel, and finally the NSMF establishes the mapping relationship between the NST and the NSST.

[0119] Optionally, regardless of the above situation, if the operation of generating the slice template fails, the NSSMF can send a slice template customization request error message to the application server, and the error message includes the reason or reason code for the slice template generation error.

[0120] See Figures 4d - 4f , for the service process of requesting to change the slice template:

[0121] Exemplary embodiment A4: The application server 30 docks with the CSMF through the slice management open function entity and requests the network slice management system 20 to change the slice template. The service process is as Figure 4d shown and includes the following steps:

[0122] 40d. Perform two-way authentication between the application server and the network slice management system through methods such as PSK.

[0123] 41d. The application server sends a slice template change request message to the slice management open function entity, requesting the slice management open function entity to send the request message to the CSMF in the network slice management system.

[0124] 42d. The slice management open function entity sends the slice template change request message from the application server to the CSMF in the network slice management system. The request message includes the template ID indicating the slice template to be changed and the parameter set required to change the slice template.

[0125] It should be noted that the application server can also directly dock with the CSMF and directly send a slice template change request message to the CSMF in the network slice management system.

[0126] Among them, the template ID indicating the slice template to be changed can be the NST ID, or the NSST ID, or can also include both the NST ID and the NSST ID. When the template ID is the NSST ID, it can indicate to change the NSST; when the template ID includes both the NST ID and the NSST ID, it can indicate to change both the NST and the corresponding NSST at the same time; when the template ID is the NST ID, it can indicate to change the NST, or may also indicate to change both the NST and the associated NSST.

[0127] Optionally, the parameter set required to change the slice template includes at least one of the following: network KPI parameters, application-related parameters, network capacity parameters, network element configuration parameters, geographical location information of the DN, and the deployment method of the UPF. Among them, the deployment method of the UPF can include the method of sinking to the DN or the method in the operator domain.

[0128] 43d. After receiving the slice template change request message, the CSMF sends the relevant parameters in the parameter set and the template ID indicating the slice template to be changed to the NSMF.

[0129] Optionally, if the application server needs to change the slice template in a specified area, the slice template change request message may also include the specified area information. Optionally, the specified area information can be one of the parameters in the parameter set. Accordingly, the CSMF can select the NSMF that covers the specified area corresponding to the area information according to the specified area information carried in the slice template change request message, and send the area information and the relevant parameters in the parameter set to the selected NSMF together.

[0130] 44d. If the NSMF determines that the NST and its associated NSST need to be changed according to the template ID indicating the slice template to be changed, it decomposes the relevant parameters in the parameter set into subnet slice template parameters required to change the NSST, and sends the subnet slice template parameters and the ID of the NSST to be changed to the selected NSSMF to instruct the NSSMF to change the NSST.

[0131] Optionally, upon receiving the specified area information sent by the CSMF, the NSMF can select the NSSMF according to the area information, for example, select the NSSMF deployed in the specified area corresponding to the area information.

[0132] In this embodiment, taking the template ID indicating the slice template to be changed as the NST ID, and it can be known from the NST ID that the NST and the NSST associated with the NST need to be changed as an example. When it is determined that the NST and the NSST associated with the NST need to be changed, on the one hand, the NSMF queries the mapping relationship between the NST and the NSST it maintains to obtain the ID of the NSST to be changed, and on the other hand, it decomposes the relevant parameters in the parameter set into subnet slice template parameters required to change the NSST, and then sends the subnet slice template parameters together with the ID of the NSST to be deleted to the NSSMF to instruct the NSSMF to change the corresponding NSST. For example, the NSSMF can delete the original NSST and regenerate a new NSST according to the new subnet slice template parameters, or it can also modify the original NSST according to the new subnet slice template parameters.

[0133] For a detailed description of decomposing the relevant parameters in the parameter set into subnet slice template parameters, reference can be made to Figure 4a the embodiments shown, which will not be elaborated here.

[0134] 45d. The NSSMF changes the corresponding NSST according to the received subnet slice template parameters and the ID of the NSST to be changed.

[0135] 46d. After changing the NSST, the NSSMF returns the ID of the changed NSST to the NSMF.

[0136] 47d. The NSMF changes the NST corresponding to the NST ID according to the received ID of the changed NSST, then updates the mapping relationship between the NST and the NSST, and returns a change confirmation message to the CSMF, as in step 48d.

[0137] Furthermore, when the application server is a third-party server, before changing the NSST, it is also possible to determine whether the NST or NSST to be changed is a customized NST or a customized NSST according to the template ID indicating the slice template to be changed; if the NST or NSST to be changed is a customized NST or a customized NSST, the identifier of the customized manufacturer can be obtained from the template ID indicating the slice template to be changed, or according to the corresponding relationship between the ID of the maintained customized slice template and the identifier of the customized manufacturer, the corresponding identifier of the customized manufacturer can be obtained; further, it is determined whether the identifier of the application server matches the identifier of the customized manufacturer; if the two match, the operation of changing the customized NST or its associated customized NSST and the mapping relationship between the NST and the NSST is performed, and if the two do not match, a change error message is output. Of course, if the NST or NSST to be changed is the system default NST or the system default NSST, since the application server 30 does not have the permission to change the system default NST or the system default NSST, a change error message can also be output. Among them, the identifier of the application server and the identifier of the customized manufacturer can be in one-to-one correspondence in the form of a mapping relationship. For example, the identifier of a third-party application server can be at least one of DNN, IP address, and FQDN. The identifier of the customized manufacturer can be represented by several bits. For example, the identifier of application manufacturer A is 01011, and its application server identifier is IP address 1, then 01011 and IP address 1 form a mapping relationship. In this way, when the IP address of the application server is 1 and the identifier of the customized manufacturer is 01011, the two match; otherwise, they do not match.

[0138] Among them, updating the mapping relationship between the NST and the NSST, for example, changing from a customized NST corresponding to a default NSST1 and a customized NSST1 to the customized NST corresponding to a customized NSST1 and a customized NSST2; it is also possible to change the customized NSTA corresponding to a default NSST1 and a customized NSST1 to the customized NSI template B corresponding to a default NSST1, a customized NSST1, and a customized NSST2. This is only an example of updating the mapping relationship between the NST and the NSST.

[0139] It should be noted that if the slice template customized by the service manufacturer corresponding to the application server only contains the NSST, after the NSMF receives the ID of the changed NSST, it can directly return a change confirmation message to the CSMF without performing the operation of updating the mapping relationship between the NST and the NSST.

[0140] 491d. After receiving the change confirmation message returned by the NSMF, the CSMF returns a slice template change request confirmation message to the application server via the slice management open function entity.

[0141] 492d. After determining that the change operation of the slice template is completed, the CSMF sends a notification message indicating that the operation of changing the slice template has been completed to the application server via the slice management open function entity.

[0142] Optionally, if the operation of changing the slice template fails, the CSMF may send a slice template change request error message to the application server, and the error message includes the reason or reason code for the slice template change error.

[0143] In Figure 4d the illustrated embodiment, the template ID of the slice template to be changed is the ID of the NST, and taking the need to change the NST and the NSST associated with the NST as an example, the process of changing the slice template is described. In this slice template change process, the order of changing the NST and the NSST is not limited. In Figure 4d it, taking the NSSMF changing the NSST first, and then the NSMF changing the NST and updating the mapping relationship between the NST and the NSST as an example for illustration. In addition, the NSMF may also change the NST first, instruct the NSSMF to change the NSST, and then after the NSST is changed, the NSMF updates the mapping relationship between the NST and the NSST. Or, the NSMF and the NSSMF may also perform the change operation in parallel, and finally the NSMF updates the mapping relationship between the NST and the NSST.

[0144] In an alternative embodiment, the template ID of the slice template to be changed is the NST ID, and only the NST needs to be changed. Then in Figure 4d the illustrated embodiment, after receiving the relevant parameters and the NST ID in the parameter set, the NSMF may change the NST corresponding to the NST ID according to the relevant parameters in the parameter set, and update the mapping relationship between the NST and the NSST after the NST is changed. For example, if the original NST A is changed to the new NST B, then the ID of NST A in the mapping relationship between the NST and the NSST needs to be changed to the ID of NST B. Further, the ID of the new NST B may also be sent to the NSSMF for the NSSMF to know that the NST associated with the NSST has changed and the ID of the new NST B after the change. After updating the mapping relationship between the NST and the NSST, the NSMF may return a change confirmation message to the CSMF.

[0145] In another alternative embodiment, the template ID of the slice template to be changed is the NSST ID, which means that the NSST needs to be changed. Then in Figure 4dIn the illustrated embodiment, after receiving the relevant parameters in the parameter set and the NST ID, on the one hand, the NSMF decomposes the relevant parameters in the parameter set into subnet slice template parameters required to change the NSST, and sends the subnet slice template parameters and the NSST ID to the selected NSSMF so that the NSSMF changes the NSST; the NSSMF changes the corresponding NSST according to the subnet slice template parameters and the NSST ID, for example, changes NSST A_1 to NSST A_2, and returns the ID of the changed NSST A_2 to the NSMF; the NSMF updates the mapping relationship between the NST and the NSST according to the received ID of the changed NSST, that is, updates the ID of the original NSST A_1 in the mapping relationship to the ID of the changed NSST A_2. After updating the mapping relationship between the NST and the NSST, the NSMF can return a change confirmation message to the CSMF.

[0146] Similarly, in the above two alternative embodiments, when the application server is a third-party server, before changing the NST or NSST, it is also possible to determine whether the NST or NSST to be changed is a customized NST or a customized NSST; if the NST or NSST to be changed is a customized NST or a customized NSST, the identifier of the customization manufacturer can be obtained, and it is determined whether the identifier of the application server matches the identifier of the customization manufacturer; if the two match, the operation of changing the customized NST or customized NSST and the mapping relationship between the NST and the NSST is performed, and if the two do not match, a change error message is output.

[0147] Exemplary embodiment A5: The service process in which the application server 30 directly docks with the NSMF and requests to change the slice template from the network slice management system 20 is as Figure 4e shown and includes the following steps:

[0148] 41e. The application server and the network slice management system complete two-way authentication through methods such as PSK.

[0149] 42e. The application server sends a slice template change request message to the NSMF in the network slice management system. The request message includes the template ID indicating the slice template to be changed and the parameter set required to change the slice template.

[0150] Optionally, the application server can also send a slice template change request message to the slice management open function entity, and the slice management open function entity sends the slice template change request message to the NSMF in the network slice management system.

[0151] Among them, the template ID indicating the slice template to be changed can be the NST ID, the NSST ID, or both the NST ID and the NSST ID. When the template ID is the NSST ID, it can indicate a change to the NSST; when the template ID includes both the NST ID and the NSST ID, it can indicate a change to both the NST and the corresponding NSST; when the template ID is the NST ID, it can indicate a change to the NST, or it may also indicate a change to both the NST and the associated NSST.

[0152] Optionally, the parameter set required to change the slice template includes at least one of: network KPI parameters, application-related parameters, network capacity parameters, configuration parameters of network elements, geographical location information of the DN, and the deployment method of the UPF. Among them, the deployment method of the UPF can include the method of sinking to the DN or the method in the operator domain.

[0153] 43e. If the NSMF determines that the NST and its associated NSST need to be changed according to the template ID indicating the slice template to be changed, it decomposes the relevant parameters in the parameter set into subnet slice template parameters required to change the NSST, and sends the subnet slice template parameters and the ID of the NSST to be changed to the selected NSSMF to instruct the NSSMF to change the NSST.

[0154] Optionally, if the application server may need to change the slice template in a specified area, the slice template change request message may also include the specified area information. Optionally, the specified area information can be used as one of the parameters in the parameter set. Accordingly, the NSMF can select the NSSMF according to the area information, for example, select the NSSMF deployed in the specified area corresponding to the area information.

[0155] In this embodiment, taking the template ID of the slice template to be changed as the NST ID, and it can be known from the NST ID that the NST and the NSST associated with the NST need to be changed as an example. When it is determined that the NST and the NSST associated with the NST need to be changed, on the one hand, the NSMF queries the mapping relationship between the NST and the NSST it maintains to obtain the ID of the NSST to be changed, and on the other hand, it decomposes the relevant parameters in the parameter set into subnet slice template parameters required to change the NSST, and then sends the subnet slice template parameters together with the ID of the NSST to be deleted to the NSSMF to instruct the NSSMF to change the corresponding NSST. For example, the NSSMF can delete the original NSST and regenerate a new NSST according to the new subnet slice template parameters, or it can also modify the original NSST according to the new subnet slice template parameters.

[0156] 44e. The NSSMF changes the corresponding NSST according to the received subnet slice template parameters and the ID of the NSST to be changed.

[0157] 45e. After changing the NSST, the NSSMF returns the ID of the changed NSST to the NSMF.

[0158] 46e. The NSMF changes the NST corresponding to the above NST ID according to the received ID of the changed NSST, then updates the mapping relationship between the NST and the NSST, and returns a slice template change request confirmation message to the application server, see step 47e.

[0159] Further, when the application server is a third-party server, before changing the NSST, it is also possible to determine whether the NST or NSST to be changed is a customized NST or a customized NSST according to the template ID indicating the slice template to be changed; if the NST or NSST to be changed is a customized NST or a customized NSST, the identifier of the customized manufacturer can be obtained from the template ID indicating the slice template to be changed, or according to the corresponding relationship between the ID of the maintained customized slice template and the identifier of the customized manufacturer, the corresponding identifier of the customized manufacturer can be obtained; further, it is determined whether the identifier of the application server matches the identifier of the customized manufacturer; if the two match, the operation of changing the customized NST or its associated customized NSST and the mapping relationship between the NST and the NSST is performed, if the two do not match, a change error message is output. Of course, if the NST or NSST to be changed is the system default NST or system default NSST, since the application server 30 does not have the permission to change the system default NST or system default NSST, a change error message can also be output.

[0160] Among them, updating the mapping relationship between the NST and the NSST, for example, changing from a customized NST corresponding to a default NSST1 and a customized NSST1 to the customized NST corresponding to a customized NSST1 and a customized NSST2; it is also possible to change the customized NSTA corresponding to a default NSST1 and a customized NSST1 to the customized NSTB corresponding to a default NSST1, a customized NSST1 and a customized NSST2. This is only an example of updating the mapping relationship between the NST and the NSST.

[0161] It should be noted that if the slice template customized by the service manufacturer corresponding to the application server only contains the NSST, after the NSMF receives the ID of the changed NSST, it can directly return a slice template change request confirmation message to the application server without performing the operation of updating the mapping relationship between the NST and the NSST.

[0162] After 48e and NSMF determine that the operation of changing the slice template is completed, they send a notification message indicating that the operation of changing the slice template has been completed to the application server.

[0163] Optionally, if the operation of changing the slice template fails, NSMF may send a slice template change request error message to the application server, and the error message includes the reason or reason code for the slice template change error.

[0164] In Figure 4e In the illustrated embodiment, the template ID indicating the slice template to be changed is the NST ID, and taking the need to change the NST and the NSST associated with the NST as an example to illustrate the template change process. In this template change process, the order of changing the NST and the NSST is not limited. In Figure 4e In it, an example is illustrated in which the NSSMF first changes the NSST, and then the NSMF changes the NST and updates the mapping relationship between the NST and the NSST. In addition, the NSMF may also first change the NST, instruct the NSSMF to change the NSST, and then, after the NSST is changed, the NSMF updates the mapping relationship between the NST and the NSST. Or, the NSMF and the NSSMF may also perform the change operation in parallel, and finally the NSMF updates the mapping relationship between the NST and the NSST.

[0165] In an alternative embodiment, the template ID indicating the slice template to be changed is the NST ID, and only the NST needs to be changed. Then in Figure 4e In the illustrated embodiment, after receiving the slice template change request message, the NSMF may change the NST corresponding to the NST ID according to the relevant parameters in the parameter set included in the request message, and update the mapping relationship between the NST and the NSST after the NST is changed. For example, if the original NST A is changed to the new NST B, then the ID of NST A in the mapping relationship between the NST and the NSST needs to be changed to the ID of NST B. Further, the ID of the new NST B may also be sent to the NSSMF for the NSSMF to know that the NST associated with the NSST has changed and the ID of the new NST B after the change. After updating the mapping relationship between the NST and the NSST, the NSMF returns a slice template change request confirmation message to the application server.

[0166] In another alternative embodiment, the template ID indicating the slice template to be changed is the NSST ID, which means that the NSST needs to be changed. Then in Figure 4eIn the illustrated embodiment, after receiving the slice template change request message, on the one hand, the NSMF decomposes the relevant parameters in the parameter set included in the request message into subnet slice template parameters required to change the NSST, and sends the subnet slice template parameters and the NSST ID to the selected NSSMF so that the NSSMF changes the NSST; the NSSMF changes the corresponding NSST according to the subnet slice template parameters and the NSST ID, for example, changes NSST A_1 to NSST A_2, and returns the ID of the changed NSST A_2 to the NSMF; the NSMF updates the mapping relationship between the NST and the NSST according to the received ID of the changed NSST, that is, updates the ID of the original NSST A_1 in the mapping relationship to the ID of the changed NSST A_2. After updating the mapping relationship between the NST and the NSST, the NSMF returns a slice template change request confirmation message to the application server.

[0167] Similarly, in the above two alternative embodiments, when the application server is a third-party server, before changing the NST or NSST, it is also possible to determine whether the NST or NSST to be changed is a customized NST or a customized NSST; if the NST or NSST to be changed is a customized NST or a customized NSST, the identifier of the customization manufacturer can be obtained, and it can be determined whether the identifier of the application server matches the identifier of the customization manufacturer; if the two match, the operation of changing the customized NST or customized NSST and the mapping relationship between the NST and the NSST is performed, and if the two do not match, a change error message is output.

[0168] Exemplary embodiment A6: The service process in which the application server 30 directly docks with the NSSMF and requests the network slice management system 20 to change the slice template is as Figure 4f shown and includes the following steps:

[0169] 41f. The application server and the network slice management system complete two-way authentication through methods such as PSK.

[0170] 42f. The application server sends a slice template change request message to the NSSMF in the network slice management system. The request message includes the template ID indicating the slice template to be changed and the parameter set required to change the slice template.

[0171] Optionally, the application server may also send a slice template change request message to the slice management open function entity, and the slice management open function entity sends the slice template change request message to the NSSMF in the network slice management system.

[0172] Among them, the template ID indicating the slice template to be changed can be the NST ID, the NSST ID, or both the NST ID and the NSST ID. When the template ID is the NSST ID, it can indicate a change to the NSST; when the template ID includes both the NST ID and the NSST ID, it can indicate a change to both the NST and the corresponding NSST; when the template ID is the NST ID, it can indicate a change to the NST or may indicate a change to both the NST and the associated NSST.

[0173] Optionally, the set of parameters required to change the slice template includes at least one of: network KPI parameters, application-related parameters, network capacity parameters, configuration parameters of network elements, geographical location information of the DN, and the deployment method of the UPF. Among them, the deployment method of the UPF can include the method of sinking to the DN or the method in the operator domain.

[0174] 43f. The NSSMF determines whether the NSST needs to be changed according to the template ID indicating the slice template to be changed. For example, when the template ID is the NSST ID and it is determined that the corresponding NSST needs to be changed, the NSSMF changes the NSST corresponding to the NSST ID according to the relevant parameters in the parameter set.

[0175] In Figure 4f In the shown embodiment, taking the need to change the NSST as an example, optionally, if the template ID indicating the slice template to be changed contains the NSST ID, the NSSMF can directly use the included NSST ID as the ID of the NSST to be changed and change the corresponding NSST accordingly; or, if the template ID indicating the slice template to be changed only contains the NST ID and it means that both the NST and its associated NSST need to be changed, the NSSMF can report the NST ID to the NSMF. The NSMF looks up the mapping relationship between the NST and the NSST maintained according to the NST ID, obtains the ID of the NSST to be changed, and returns it to the NSSMF. The NSSMF changes the corresponding NSST accordingly.

[0176] 44f. After the NSSMF changes the corresponding NSST, it can also report the ID of the changed NSST to the NSMF so that the NSMF can update the mapping relationship between the NST and the NSST according to the ID of the changed NSST.

[0177] 45f. The NSMF updates the mapping relationship between the NST and the NSST according to the ID of the changed NSST reported by the NSSMF. For example, if the NSSMF changes NSSTA_1 to NSSTA_2, the NSMF can update the ID of NSSTA_1 in the mapping relationship to the ID of NSSTA_2.

[0178] After 46f and NSMF update the mapping relationship between NST and NSST, they return a change confirmation message to NSSMF.

[0179] Optionally, if only NSST needs to be changed, for example, when the template ID indicating the slice template to be changed is the NSST ID, after NSMF receives the ID of the changed NSST reported by NSSMF, it only needs to change the mapping relationship between NST and NSST. Further optionally, if not only NSST needs to be changed but also NST, for example, when the template ID indicating the slice template to be changed is the NST ID or includes both the NSST ID and the NST ID, NSSMF not only changes the corresponding NSST according to the relevant parameters and template ID in the parameter set, but also reports the parameter set and the template ID to the corresponding NSMF; for NSMF, it also needs to change the corresponding NST according to the relevant parameters and template ID in the parameter set, and then update the mapping relationship between NST and NSST. For example, when NSSMF changes NSST A_1 to NSST B_1 and NSMF changes NST A to NST B, the mapping relationship between NST A and NSST A_1 needs to be updated to the mapping relationship between NST B and NSST B_1.

[0180] Furthermore, when the application server is a third-party server, before changing NST or NSST, it can also judge whether the NST or NSST to be changed is a customized NST or a customized NSST according to the template ID; if the NST or NSST to be changed is a customized NST or a customized NSST, the identifier of the customized manufacturer can be obtained from the template ID, or according to the corresponding relationship between the ID of the maintained customized slice template and the identifier of the customized manufacturer, the corresponding identifier of the customized manufacturer can be obtained; further, judge whether the identifier of the application server matches the identifier of the customized manufacturer; if the two match, perform the operation of changing the customized NST or customized NSST and the mapping relationship between NST and NSST, if the two do not match, output a change error message. Of course, if the NST or NSST to be changed is the system default NST or the system default NSST, since the application server 30 does not have the permission to change the system default NST or the system default NSST, a change error message can also be output. For the mapping method between the identifier of the application server and the identifier of the customized manufacturer, reference can be made to the foregoing embodiments.

[0181] Among them, the mapping relationship between the updated NST and NSST is changed. For example, from a customized NST corresponding to a default NSST1 and a customized NSST1 to the customized NST corresponding to a customized NSST1 and a customized NSST2. This is only an example of updating the mapping relationship between the NST and NSST.

[0182] 47f. After receiving the change confirmation message returned by the NSMF, the NSSMF returns a slice template change request confirmation message to the application server.

[0183] 48f. After determining that the change operation of the slice template is completed, the NSSMF sends a notification message indicating that the operation of changing the slice template has been completed to the application server.

[0184] Optionally, if the operation of changing the slice template fails, the NSSMF may send a slice template change request error message to the application server, and the error message includes the reason or reason code for the slice template change error.

[0185] In Figure 4f In the illustrated embodiment, the case of only changing the NSST or changing both the NSST and NST is described in detail. In an optional embodiment, the template ID of the slice template to be changed is the NST ID, and only the NST needs to be changed. Then in Figure 4f In the illustrated embodiment, after receiving the slice template change request message, the NSSMF may report the parameter set and the NST ID in the request message to the NSMF for the NSMF to change the corresponding NST and update the mapping relationship between the NST and NSST after the NST is changed; after receiving the parameter set and the NST ID, the NSMF changes the NST corresponding to the NST ID according to the relevant parameters in the parameter set. For example, if the original NST A is changed to the new NST B, the ID of NST A in the mapping relationship between the NST and NSST needs to be changed to the ID of NST B. Further, the ID of the new NST B can also be sent to the NSSMF through the change confirmation message for the NSSMF to know that the NST associated with the NSST has changed and the ID of the new NST B after the change. After receiving the change confirmation message returned by the NSMF, the NSSMF returns a slice template change request confirmation message to the application server.

[0186] Similarly, in the above optional embodiments, when the application server is a third-party server, before changing the NST, it is also possible to determine whether the NST to be changed is a customized NST; if the NST to be changed is a customized NST, the identifier of the customization manufacturer can be obtained, and it can be determined whether the identifier of the application server matches the identifier of the customization manufacturer; if the two match, the operation of changing the customized NST and the mapping relationship between the NST and the NSST is performed, and if the two do not match, a change error message is output.

[0187] In Figure 4f the illustrated embodiment, when it is necessary to change the NST and the NSST associated with the NST, the order of changing the NST and the NSST is not limited. In Figure 4f it, the NSSMF first changes the NSST, and then the NSMF changes the NST and updates the mapping relationship between the NST and the NSST as an example for illustration. In addition, the NSSMF can also first request the NSMF to change the NST, and then the NSSMF changes the NSST. Then, after the NSST is changed, the NSMF updates the mapping relationship between the NST and the NSST. Or, the NSMF and the NSSMF can also perform the change operations in parallel, and finally the NSMF updates the mapping relationship between the NST and the NSST.

[0188] See Figures 4g - 4i , for the service process of requesting to delete a slice template:

[0189] Exemplary embodiment A7: The service process in which the application server 30 docks with the CSMF through the slice management open function entity and requests the network slice management system 20 to delete the slice template is as Figure 4g shown and includes the following steps:

[0190] 40g. The application server and the network slice management system complete two-way authentication through methods such as PSK.

[0191] 41g. The application server sends a slice template deletion request message to the slice management open function entity to request the slice management open function entity to send the request message to the CSMF in the network slice management system.

[0192] 42g. The slice management open function entity sends the slice template deletion request message from the application server to the CSMF in the network slice management system, and the request message includes the template ID indicating the slice template to be deleted.

[0193] It should be noted that the application server can also directly dock with the CSMF and directly send a slice template deletion request message to the CSMF in the network slice management system.

[0194] Among them, the template ID indicating the slice template to be deleted can be the NST ID, the NSST ID, or both the NST ID and the NSST ID. When the template ID is the NSST ID, it can indicate the deletion of the NSST; when the template ID includes both the NST ID and the NSST ID, or only includes the NST ID, it can indicate the simultaneous deletion of the NST and the corresponding NSST. In addition, when the template ID only includes the NST ID, it can also only indicate the deletion of the NST. For example, when all the NSTs customized by the service provider corresponding to the application server are associated with the system default NSST and / or the NSSTs customized by other service providers, the service provider corresponding to the application server has no permission to delete the system default NSST and / or the NSSTs customized by other service providers. Therefore, it can only delete its own customized NST and the mapping relationship between the NST and the NSST, which belongs to the case where only the NST can be deleted.

[0195] Furthermore, when the application server 30 is a third-party server, the slice template deletion request from the application server 30 can only request the deletion of the customized NST and the customized NSST, and cannot delete the system default NST or the default NSST. In this case, the template ID indicating the slice template to be deleted can be: the customized NST ID and / or the customized NSST ID. Of course, if the application server 30 is from the operator, the application server 30 can delete the system default NST and the system default NSST. That is to say, different application servers have different template deletion permissions. In the embodiments of the present application, the case where the application server 30 is a third-party server is mainly concerned.

[0196] In this embodiment, taking the indication of simultaneous deletion of the NST and the NSST associated with the NST as an example, the template deletion process will be described in detail. For example, the template ID indicating the slice template to be deleted can be the NST ID or the case of including both the NST ID and the NSST ID.

[0197] 43g. After receiving the slice template deletion request message, the CSMF sends the template ID indicating the slice template to be deleted to the NSMF.

[0198] Optionally, if the application server may need to delete the slice template in a specified area, the slice template deletion request message may also include the specified area information. Correspondingly, the CSMF can select the NSMF covering the area information according to the area information specified in the request message, and send the area information and the template ID to the selected NSMF together.

[0199] 44g. The NSMF selects the NSSMF and sends the ID of the NSST to be deleted to the selected NSSMF to instruct the selected NSSMF to delete the corresponding NSST.

[0200] Optionally, upon receiving the specified area information sent by the CSMF, the NSMF may select the NSSMF according to the area information. For example, it may select the NSSMF deployed within the specified area corresponding to the area information.

[0201] Optionally, if the template ID of the slice template to be deleted contains the NSST ID, the contained NSST ID may be directly sent to the NSSMF as the ID of the NSST to be deleted; if the template ID of the slice template to be deleted only contains the NST ID, the mapping relationship between the maintained NST and NSST may be searched according to the contained NST ID to obtain the ID of the NSST to be deleted and sent to the NSSMF.

[0202] 45g. The NSSMF deletes the corresponding NSST according to the received ID of the NSST to be deleted and returns a first deletion confirmation message to the NSMF, as shown in step 46g.

[0203] In this embodiment, the network slice management system can provide a default NSST, and the service provider corresponding to the application server can also customize the NST and NSST. For the case where the service provider corresponding to the application server customizes the NST, the customized NST can be associated with the NSST customized by the service provider corresponding to the application server, or may be associated with the default NSST of the system. However, in the case where the application server 30 is a third-party server, the slice template deletion request from the application server 30 can only request the deletion of the NST and the customized NSST customized by the service provider corresponding to the application server 30, and cannot delete the default NST or default NSST of the system, nor can it delete the NST and customized NSST customized by other service providers. For this case, when the application server 30 is a third-party server, before deleting the corresponding NSST, it can be determined whether the NSST is a customized NSST or a system default NSST. If it is a customized NSST, the identifier of the customized manufacturer can be obtained from the template ID indicating the slice template to be deleted, or according to the corresponding relationship between the ID of the maintained customized slice template and the identifier of the customized manufacturer, the identifier of the corresponding customized manufacturer can be obtained; further, it is determined whether the identifier of the application server matches the identifier of the customized manufacturer; if the two match, the operation of deleting the NSST and the subsequent operation of deleting the mapping relationship between the NST and the NSST are executed, and if the two do not match, an error message for deletion is output. Of course, if it is a system default NSST, only the mapping relationship between the NSST and the NST needs to be deleted, and the system default NSST needs to be retained. For the mapping method between the identifier of the application server and the identifier of the customized manufacturer, reference can be made to the foregoing embodiment.

[0204] 47g. After the NSMF receives the first deletion confirmation message returned by the NSSMF, it deletes the mapping relationship between the NST and the NSST and deletes the NST, and returns a second deletion confirmation message to the CSMF. See step 48g.

[0205] It should be noted that the operation of determining whether the identifier of the above judgment application server matches the identifier of the customization manufacturer can be performed by the NSSMF during the process of deleting the NSST, or can be performed by the NSMF during the process of deleting the NST. Alternatively, after receiving the template ID of the slice template to be deleted, the NSMF can first perform the judgment, that is, before deleting the NSST and NSST, the NSMF determines whether the NST to be deleted is a customized NST according to the template ID of the slice template to be deleted; if the NST to be deleted is a customized NST, obtain the identifier of the customization manufacturer from the template ID of the slice template to be deleted, or obtain the corresponding identifier of the customization manufacturer according to the corresponding relationship between the ID of the maintained customized slice template and the identifier of the customization manufacturer; further, determine whether the identifier of the application server matches the identifier of the customization manufacturer; if the two match, perform the subsequent operation of deleting the NSST, NST, and the mapping relationship between the NST and the NSST; if the two do not match, output a deletion error message and end this template deletion operation.

[0206] 491g. After receiving the second deletion confirmation message returned by the NSMF, the CSMF returns a slice template deletion request confirmation message to the application server via the slice management open function entity.

[0207] 492g. After determining that the deletion operation of the slice template is completed, the CSMF sends a notification message indicating that the operation of deleting the slice template has been completed to the application server via the slice management open function entity.

[0208] Optionally, if the operation of deleting the slice template fails, the CSMF can send a slice template deletion request error message to the application server, and the error message includes the reason or reason code for the slice template deletion error.

[0209] In Figure 4g the illustrated embodiment, taking the indication to delete the NST and the NSST associated with the NST as an example to illustrate the template deletion process. In this template deletion process, the order of deleting the NST and the NSST is not limited. In Figure 4g it is illustrated with the NSSMF first deleting the NSST, and then the NSMF deleting the mapping relationship between the NST and the NSST, and further deleting the NST as an example. In addition, the NSMF can also first delete the NST, and then instruct the NSSMF to delete the NSST, and then after the NST and the NSST are deleted, the NSMF deletes the mapping relationship between the NST and the NSST. Or, the NSMF can also first delete the mapping relationship between the NST and the NSST, then delete the NST, and then instruct the NSSMF to delete the NSST. Or, the NSMF and the NSSMF can also perform the deletion operation in parallel, and finally the NSMF deletes the mapping relationship between the NST and the NSST.

[0210] In an optional embodiment, the template ID indicating the slice template to be deleted may be the NSST ID, which is used to indicate the deletion of the NSST. Then, in Figure 4g the embodiment shown, after receiving the NSST ID, the NSMF may directly send the NSST ID to the selected NSSMF to enable the NSSMF to delete the corresponding NSST. For example, NSSTA_1 is deleted, and a first deletion confirmation message is returned to the NSMF; after receiving the deletion confirmation message, the NSMF updates the mapping relationship between the NST and the NSST, that is, deletes the ID of NSST A_1 corresponding to the NST in the mapping relationship. After deleting the mapping relationship corresponding to the deleted NSST, the NSMF returns a second deletion confirmation message to the CSMF for the CSMF to return a slice template deletion request confirmation message to the application server. Similarly, in this optional embodiment, when the application server is a third-party server, before deleting the NSST, it may also be determined whether the NSST to be deleted is a customized NSST; if it is a customized NSST, the identifier of the customization manufacturer may be obtained, and it may be determined whether the identifier of the application server matches the identifier of the customization manufacturer; if the two match, the operation of deleting the customized NSST and the mapping relationship between the NST and the NSST is performed, and if the two do not match, a change error message is output.

[0211] In an optional embodiment, the template ID indicating the slice template to be deleted may be the NST ID, which is used to indicate the deletion of the NST. For example, all the NSSTs associated with the NST are system default NSSTs and / or NSSTs customized by other manufacturers. Then, in Figure 4g the embodiment shown, before deleting the NSST, the NSSMF will determine that all the NSSTs are system default NSSTs and / or NSSTs customized by other manufacturers, so it cannot be deleted, and a notification message that the NSST cannot be deleted may be returned to the NSMF; after receiving the notification message that the NSST cannot be deleted returned by the NSSMF, the NSMF may delete the mapping relationship between the NST and the NSST and delete the NST, and return a deletion confirmation message to the CSMF for the CSMF to return a slice template deletion request confirmation message to the application server.

[0212] Exemplary embodiment A8: The service process in which the application server 30 directly docks with the NSMF and requests the network slice management system 20 to delete the slice template, as Figure 4h shown, includes the following steps:

[0213] 41h. The application server and the network slice management system complete two-way authentication through methods such as PSK.

[0214] 42h. The application server sends a slice template deletion request message to the NSMF in the network slice management system. The request message includes a template ID indicating the slice template to be deleted.

[0215] Optionally, the application server may also send a slice template deletion request message to the slice management open function entity, and the slice management open function entity sends the slice template deletion request message to the NSMF in the network slice management system.

[0216] Among them, the template ID indicating the slice template to be deleted may be an NST ID, an NSST ID, or may include both an NST ID and an NSST ID at the same time. When the template ID is an NSST ID, it may indicate the deletion of the NSST; when the template ID includes both an NST ID and an NSST ID, or only includes an NST ID, it may indicate the simultaneous deletion of the NST and the corresponding NSST. In addition, when the template ID only includes an NST ID, it may also only indicate the deletion of the NST. For example, when all the NSTs customized by the service provider corresponding to the application server are associated with the system default NSST and / or NSSTs customized by other service providers, the service provider corresponding to the application server has no permission to delete the system default NSST and / or NSSTs customized by other service providers. Therefore, only the NSTs customized by itself and the mapping relationship between the NST and the NSST can be deleted, which belongs to the case where only the NST can be deleted.

[0217] Further, when the application server 30 is a third-party server, the slice template deletion request from the application server 30 can only request the deletion of the NST and the customized NSST customized by the service provider corresponding to the application server 30, and cannot delete the system default NST or default NSST, nor can it delete the NST and customized NSST customized by other service providers. In this case, the template ID indicating the slice template to be deleted may be: the customized NST ID and / or the customized NSST ID.

[0218] In this embodiment, taking the indication of simultaneous deletion of the NST and the NSST associated with the NST as an example, the template deletion process is described in detail. For example, the template ID indicating the slice template to be deleted may be an NST ID or the case of including both an NST ID and an NSST ID at the same time.

[0219] 43h. The NSMF selects the NSSMF and sends the ID of the NSST to be deleted to the selected NSSMF to indicate the selected NSSMF to delete the corresponding NSST.

[0220] Optionally, if the application server needs to delete the slice templates in a specified area, the slice template deletion request message may further include the specified area information. Accordingly, the NSMF may select the NSSMF according to the area information specified in the request message.

[0221] Optionally, if the template ID of the slice template to be deleted contains the NSST ID, the included NSST ID can be directly sent to the NSSMF as the ID of the NSST to be deleted; if the template ID of the slice template to be deleted only contains the NST ID, the mapping relationship between the maintained NST and NSST can be found according to the included NST ID, and the ID of the NSST to be deleted can be obtained and sent to the NSSMF.

[0222] 44h. The NSSMF deletes the corresponding NSST according to the received ID of the NSST to be deleted, and returns a deletion confirmation message to the NSMF, as shown in step 45h.

[0223] In this embodiment, the network slice management system may provide default NSSTs, and the service providers corresponding to the application servers may also customize NSTs and NSSTs. For the case where the service provider corresponding to the application server customizes the NST, the customized NST may be associated with the NSST customized by the service provider, or may be associated with the default NSST of the system. However, when the application server 30 is a third-party server, the slice template deletion request from the application server 30 can only request to delete the NST and the customized NSST customized by the service provider corresponding to the application server 30, and cannot delete the default NST or default NSST of the system, nor can it delete the NSTs and customized NSSTs customized by other service providers. For this case, before deleting the corresponding NSST, it can be determined whether the NSST is a customized NSST or a system default NSST. If it is a customized NSST, the identifier of the customized manufacturer can be obtained from the template ID of the slice template to be deleted, or according to the corresponding relationship between the ID of the maintained customized slice template and the identifier of the customized manufacturer, the corresponding identifier of the customized manufacturer can be obtained; further, it is determined whether the identifier of the application server matches the identifier of the customized manufacturer; if the two match, the operation of deleting the NSST and the subsequent operation of deleting the mapping relationship between the NST and the NSST are performed, and if the two do not match, a deletion error message is output. If it is a system default NSST, only the mapping relationship between the NSST and the NST needs to be deleted, and the system default NSST needs to be retained. For the mapping method between the identifier of the application server and the identifier of the customized manufacturer, reference can be made to the foregoing embodiments.

[0224] After 46h and NSMF receives the deletion confirmation message returned by NSSMF, it deletes the mapping relationship between NST and NSST, deletes NST, and returns a slice template deletion request confirmation message to the application server. See step 47h.

[0225] It should be noted that the operation of determining whether the identifier of the application server matches the identifier of the customization manufacturer can be performed by NSSMF during the process of deleting NSST, or can be performed by NSMF during the process of deleting NST. Alternatively, it can also be judged by NSMF first, that is, after receiving the slice template deletion request message and before deleting NSST and NSST, it is performed by NSMF. The execution process is the same and will not be elaborated here. Preferably, in each embodiment, during the process of deleting NSST, NSSMF can judge whether the manufacturer identifier of the customized NSST matches the ID of the application server; during the process of deleting NST, NSMF can judge whether the manufacturer identifier of the customized NST matches the ID of the application server.

[0226] 48h、After NSMF determines that the deletion operation of the slice template is completed, it sends a notification message indicating that the operation of deleting the slice template has been completed to the application server.

[0227] Optionally, if the operation of deleting the slice template fails, NSMF can send a slice template deletion request error message to the application server, and the error message includes the reason or reason code for the slice template deletion error.

[0228] In Figure 4h In the illustrated embodiment, the process of deleting the template is described by taking the indication to delete NST and the NSST associated with the NST as an example. In this process of deleting the template, the order of deleting NST and NSST is not limited. In Figure 4h In the figure, NSSMF first deletes NSST, and then NSMF deletes the mapping relationship between NST and NSST, and further deletes NST as an example. In addition, NSMF can also first delete NST, and then instruct NSSMF to delete NSST. Then, after NST and NSST are deleted, NSMF deletes the mapping relationship between NST and NSST. Alternatively, NSMF can also first delete the mapping relationship between NST and NSST, then delete NST, and then instruct NSSMF to delete NSST. Alternatively, NSMF and NSSMF can also perform the deletion operation in parallel, and finally NSMF deletes the mapping relationship between NST and NSST.

[0229] In an alternative embodiment, the template ID indicating the slice template to be deleted can be the NSST ID, which is used to indicate the deletion of NSST. Then in Figure 4hIn the illustrated embodiment, after receiving the slice template deletion request message, the NSMF can directly send the NSST ID to the selected NSSMF to enable the NSSMF to delete the corresponding NSST. For example, delete NSST A_1 and return a deletion confirmation message to the NSMF; after receiving the deletion confirmation message, the NSMF updates the mapping relationship between the NST and the NSST, that is, deletes the ID of NSST A_1 corresponding to the NST in the mapping relationship. After deleting the mapping relationship corresponding to the deleted NSST, the NSMF returns a slice template deletion request confirmation message to the application server. Similarly, in this alternative embodiment, when the application server is a third-party server, before deleting the NSST, it is also possible to determine whether the NSST to be deleted is a customized NSST; if it is a customized NSST, the identifier of the customization manufacturer can be obtained, and it can be determined whether the identifier of the application server matches the identifier of the customization manufacturer; if the two match, the operation of deleting the customized NSST and the mapping relationship between the NST and the NSST is performed, and if the two do not match, a change error message is output.

[0230] In an alternative embodiment, the template ID indicating the slice template to be deleted may be the NST ID, which is used to indicate the deletion of the NST. For example, all NSSTs associated with the NST are system default NSSTs and / or NSSTs customized by other manufacturers. Then, Figure 4h In the illustrated embodiment, before deleting the NSST, the NSSMF will determine that all NSSTs are system default NSSTs and / or NSSTs customized by other manufacturers, so it cannot be deleted, and a notification message that the NSST cannot be deleted can be returned to the NSMF; after receiving the notification message that the NSST cannot be deleted returned by the NSSMF, the NSMF can delete the mapping relationship between the NST and the NSST and delete the NST, and return a slice template deletion request confirmation message to the application server.

[0231] Exemplary embodiment A9: The service process in which the application server 30 directly interfaces with the NSSMF and requests the network slice management system 20 to delete the slice template is as Figure 4i shown and includes the following steps:

[0232] 41i. The application server and the network slice management system complete two-way authentication through methods such as PSK.

[0233] 42i. The application server sends a slice template deletion request message to the NSSMF in the network slice management system, and the request message includes the template ID indicating the slice template to be deleted.

[0234] Optionally, the application server may also send a slice template deletion request message to the slice management open function entity, and the slice management open function entity sends the slice template deletion request message to the NSSMF in the network slice management system.

[0235] Among them, the template ID indicating the slice template to be deleted may be the NST ID, or the NSST ID, or may include both the NST ID and the NSST ID at the same time. When the template ID is the NSST ID, it may indicate the deletion of the NSST; when the template ID includes both the NST ID and the NSST ID, or only includes the NST ID, it may indicate the simultaneous deletion of the NST and the corresponding NSST. In addition, when the template ID only includes the NST ID, it may also only indicate the deletion of the NST. For example, when all the NSTs customized by the service provider corresponding to the application server are associated with the system default NSST and / or NSSTs customized by other service providers, the service provider corresponding to the application server has no permission to delete the system default NSST and / or NSSTs customized by other service providers. Therefore, only the NSTs customized by itself and the mapping relationship between the NST and the NSST can be deleted, which belongs to the case where only the NST can be deleted.

[0236] Furthermore, when the application server 30 is a third-party server, the slice template deletion request from the application server 30 can only request the deletion of the NST and the customized NSST customized by the service provider corresponding to the application server 30, and cannot delete the system default NST or default NSST, nor can it delete the NST and customized NSST customized by other service providers. In this case, the template ID indicating the slice template to be deleted may be: the customized NST ID and / or the customized NSST ID.

[0237] In this embodiment, taking the indication of simultaneous deletion of the NST and the NSST associated with the NST as an example, the template deletion process is described in detail. For example, the template ID indicating the slice template to be deleted may be the NST ID or the case where both the NST ID and the NSST ID are included at the same time.

[0238] 43i. The NSSMF deletes the corresponding NSST according to the template ID of the slice template to be deleted.

[0239] 44i. The NSSMF reports the ID of the NST to be deleted to the corresponding NSMF.

[0240] 45i. The NSMF deletes the corresponding NST and its mapping relationship with the NSST according to the ID of the NST to be deleted, and returns a deletion confirmation message to the NSSMF, as shown in step 46i.

[0241] Optionally, if the template ID of the slice template to be deleted contains the NSST ID, the NSSMF may directly delete the NSST corresponding to this ID, and send this NSST ID as the ID of the NST to be deleted to the NSMF, so that the NSMF can find the mapping relationship between the maintained NST and NSST based on this ID, obtain the ID of the NST to be deleted, and delete the NST corresponding to this ID and its mapping relationship with the NSST. If the template ID of the slice template to be deleted contains the NST ID, the NSSMF may report this NST ID as the ID of the NST to be deleted to the NSMF. The NSMF finds the mapping relationship between the maintained NST and NSST, obtains the ID of the NSST to be deleted and returns it to the NSSMF. The NSSMF deletes the corresponding NSST accordingly; the NSMF deletes the corresponding NST and its mapping relationship with the NSST based on the ID of the NST reported by the NSSMF.

[0242] Further optionally, considering that the customized NST of the application server corresponding to the service provider may be associated with the NSST customized by this provider, may also be associated with the system default NSST, or may also be associated with the NSST customized by other providers. However, in the case where the application server 30 is a third-party server, the slice template deletion request from the application server 30 can only request to delete the NST and the customized NSST customized by the service provider corresponding to this application server 30, and cannot delete the system default NST or default NSST, nor can it delete the NST and the customized NSST customized by other service providers. In view of this, before deleting the corresponding NSST, the NSSMF may determine whether this NSST is a customized NSST or a system default NSST. If it is a customized NSST, it may obtain the identifier of the customized provider from the template ID of the slice template to be deleted, or obtain the corresponding identifier of the customized provider according to the corresponding relationship between the ID of the maintained customized slice template and the identifier of the customized provider; further, determine whether the identifier of the application server matches the identifier of the customized provider; if the two match, perform the operation of deleting this NSST and the subsequent operation of deleting the mapping relationship between the NST and this NSST. If the two do not match, output an error message for deletion. If it is a system default NSST, only the mapping relationship between this NSST and the NST needs to be deleted, and the system default NSST needs to be retained. For the mapping method between the identifier of the application server and the identifier of the customized provider, reference may be made to the foregoing embodiments.

[0243] It should be noted that the operation of determining whether the identifier of the application server matches the identifier of the customized provider may be performed by the NSSMF during the process of deleting the NSST, or may be performed by the NSMF during the process of deleting the NST. Alternatively, during the two deletion processes, the NSSMF or the NSMF may perform the operation respectively, and the execution process is the same and will not be elaborated.

[0244] 47i. After the NSSMF receives the deletion confirmation message returned by the NSMF, it returns a slice template deletion request confirmation message to the application server.

[0245] 48i. After the NSSMF determines that the deletion operation of the slice template is completed, it sends a notification message to the application server indicating that the operation of deleting the slice template has been completed.

[0246] Optionally, if the operation of deleting the slice template fails, the NSSMF may send a slice template deletion request error message to the application server, and the error message includes the reason or reason code for the slice template deletion error.

[0247] In Figure 4i the illustrated embodiment, taking the indication to delete the NST and the NSST associated with the NST as an example to illustrate the template deletion process. In this template deletion process, the sequence of deleting the NST and the NSST is not limited. In Figure 4i it is illustrated with the NSSMF first deleting the NSST, and then the NSMF deleting the mapping relationship between the NST and the NSST, and further deleting the NST as an example. In addition, the NSSMF may also first request the NSMF to delete the NST, and then the NSSMF deletes the NSST. Then, after the NST and the NSST are deleted, the NSMF deletes the mapping relationship between the NST and the NSST. Or, the NSMF may also, according to the request of the NSSMF, first delete the mapping relationship between the NST and the NSST, then delete the NST, and then the NSSMF deletes the NSST. Or, the NSMF and the NSSMF may also perform the deletion operation in parallel, and finally the NSMF deletes the mapping relationship between the NST and the NSST.

[0248] In an alternative embodiment, the template ID indicating the slice template to be deleted may be the NSST ID, which is used to indicate the deletion of the NSST. Then, in Figure 4i the illustrated embodiment, after the NSSMF receives the slice template deletion request message, it may directly delete the corresponding NSST according to the NSST ID. For example, it deletes the NSST A_1 and reports the NSST ID to the NSMF; after receiving the NSST ID, the NSMF updates the mapping relationship between the NST and the NSST, that is, deletes the ID of the NSST A_1 corresponding to the NST in the mapping relationship. After deleting the mapping relationship corresponding to the deleted NSST, the NSMF returns a deletion confirmation message to the NSSMF for the NSSMF to return a slice template deletion request confirmation message to the application server.

[0249] In an optional embodiment, the template ID indicating the slice template to be deleted may be the NST ID, which is used to indicate the deletion of the NST. For example, all NSSTs associated with the NST are system default NSSTs and / or NSSTs customized by other vendors. Then, in Figure 4i In the illustrated embodiment, after receiving the slice template deletion request message, before performing the operation of deleting the NSST, the NSSMF determines that all NSSTs are system default NSSTs and / or NSSTs customized by other vendors, so they cannot be deleted. On the one hand, it sends a notification message to the NSMF indicating that the NSST cannot be deleted, and on the other hand, it sends the ID of the NST to be deleted to the NSMF. After receiving the notification message sent by the NSSMF indicating that the NSST cannot be deleted, the NSMF can delete the mapping relationship between the NST and the NSST and delete the NST according to the ID of the NST to be deleted, and return a deletion confirmation message to the NSSMF for the NSSMF to return a slice template deletion request confirmation message to the application server.

[0250] It should be noted here that in the above embodiments, the slice template customization request message, the slice template change request message, and the slice template deletion request message can be carried by HTTP messages or HTTPs messages, or can be carried by a message format customized by the network slice management system, which is not limited herein. In addition, the names of these messages are only examples, and any message names that can implement the corresponding functions are applicable to the embodiments of the present application. For example, they can also be simply named the first request message, the second request message, the third request message, etc.

[0251] See Figures 5a - 5c , which is the service process for requesting to query network slice capability information:

[0252] Exemplary embodiment B1: The service process in which the application server 30 docks with the CSMF through the slice management open function entity and requests the network slice management system 20 to query the network slice capability information, as Figure 5a shown, includes the following steps:

[0253] 50a. Perform two-way authentication between the application server and the network slice management system through methods such as PSK.

[0254] 51a. The application server sends a slice capability query request message to the slice management open function entity, requesting the slice management open function entity to send the request message to the CSMF in the network slice management system.

[0255] 52a. The slice management open function entity sends the slice capability query request message from the application server to the CSMF in the network slice management system, and the request message includes the specified area information.

[0256] After the CSMF receives the slice capability query request message, it sends the specified area information to the NSMF.

[0257] Optionally, the CSMF may select the NSMF that covers the specified area information according to the specified area information, and send the area information to the selected NSMF.

[0258] 54a. The NSMF cooperates with the NSSMF corresponding to the specified area information to obtain the network slice capability information of the mobile communication network within the specified area.

[0259] In an optional embodiment, as shown in step 54a1, the NSSMFs in each area may report the network slice capability information of the mobile communication network within the area where the NSSMF is located to the NSMF in real time, and the NSMF locally maintains the network slice capability information of the mobile communication network within each area covered by the NSMF. Based on this, after the NSMF receives the specified area information sent by the CSMF, it can directly obtain the network slice capability information of the mobile communication network within the specified area from the local. Among them, the specified area information points to the specified area.

[0260] In another optional embodiment, the NSSMFs in each area do not report the network slice capability information of the mobile communication network within the area where the NSSMF is located to the NSMF in real time, but the NSMF obtains the network slice capability information of the mobile communication network within the area where the NSSMF is located from the NSSMF in real time according to the demand. Based on this, as shown in steps 54a2 and 54a3, after the NSMF receives the specified area information sent by the CSMF, it can select the NSSMF according to the area information, and send an information acquisition request message to the selected NSSMF to request the NSSMF to report the network slice capability information of the mobile communication network within the specified area; the NSMF receives the network slice capability information of the mobile communication network within the specified area reported by the NSSMF.

[0261] 55a. The NSMF sends the network slice capability information of the mobile communication network within the specified area to the CSMF.

[0262] 56a. After the CSMF receives the network slice capability information of the mobile communication network within the specified area returned by the NSMF, it returns a slice capability query request confirmation message to the application server through the slice management open function entity, and the confirmation message contains the network slice capability information of the mobile communication network within the specified area.

[0263] 57a. After the CSMF determines that the slice capability query operation is completed, it sends a notification message indicating that the slice capability query operation has been completed to the application server through the slice management open function entity.

[0264] Optionally, if the slice capability query operation fails, the CSMF may send a slice capability query request error message to the application server, which includes the reason or reason code for the slice capability query error.

[0265] Exemplary embodiment B2: The service process in which the application server 30 directly interfaces with the NSMF to request the service of querying network slice capability information from the network slice management system 20 is as Figure 5b shown and includes the following steps:

[0266] 51b. The application server and the network slice management system complete mutual authentication through methods such as PSK.

[0267] 52b. The application server sends a slice capability query request message to the NSMF in the network slice management system, and the request message includes the specified area information.

[0268] Optionally, the application server may also send a slice capability query request message to the slice management open function entity, and the slice management open function entity sends the slice capability query request message to the NSMF in the network slice management system.

[0269] 53b. The NSMF cooperates with the NSSMF corresponding to the specified area information to obtain the network slice capability information of the mobile communication network in the specified area.

[0270] In an alternative embodiment, as shown in step 53b1, the NSSMFs in each area may report in real time the network slice capability information of the mobile communication network in the area where the NSSMF is located to the NSMF, and the NSMF locally maintains the network slice capability information of the mobile communication network in each area covered by the NSMF. Based on this, after receiving the specified area information sent by the CSMF, the NSMF can directly obtain the network slice capability information of the mobile communication network in the specified area from local. Among them, the specified area information points to the specified area.

[0271] In another alternative embodiment, the NSSMFs in each area do not report in real time the network slice capability information of the mobile communication network in the area where the NSSMF is located to the NSMF, but the NSMF obtains in real time from the NSSMF the network slice capability information of the mobile communication network in the area where the NSSMF is located according to requirements. Based on this, as shown in steps 53b2 and 53b3, after receiving the specified area information sent by the CSMF, the NSMF can select the NSSMF according to the area information and send an information acquisition request message to the selected NSSMF to request the NSSMF to report the network slice capability information of the mobile communication network in the specified area; the NSMF receives the network slice capability information of the mobile communication network in the specified area reported by the NSSMF.

[0272] 54b. The NSMF returns a slice capability query request confirmation message to the application server, and the confirmation message contains the network slice capability information of the mobile communication network in the specified area.

[0273] 55b. After determining that the slice capability query operation is completed, the NSMF sends a notification message indicating that the slice capability query operation is completed to the application server.

[0274] Optionally, if the slice capability query operation fails, the NSMF may send a slice capability query request error message to the application server, and the error message includes the reason or reason code for the slice capability query error.

[0275] Exemplary embodiment B3: The service process in which the application server 30 directly interfaces with the NSSMF to request the network slice capability information query service from the network slice management system 20 is as Figure 5c shown and includes the following steps:

[0276] 51c. The application server and the network slice management system complete mutual authentication through methods such as PSK.

[0277] 52c. The application server sends a slice capability query request message to the NSSMF in the network slice management system, and the request message includes the specified area information.

[0278] Optionally, the application server may also send a slice capability query request message to the slice management open function entity, and the slice management open function entity sends the slice capability query request message to the NSSMF in the network slice management system.

[0279] 53c. The NSSMF obtains the network slice capability information of the mobile communication network in the specified area according to the specified area information.

[0280] 54c. The NSSMF returns a slice capability query request confirmation message to the application server, and the confirmation message contains the network slice capability information of the mobile communication network in the specified area.

[0281] 55c. After determining that the slice capability query operation is completed, the NSMF sends a notification message indicating that the slice capability query operation is completed to the application server.

[0282] Optionally, if the slice capability query operation fails, the NSSMF may send a slice capability query request error message to the application server, and the error message includes the reason or reason code for the slice capability query error.

[0283] See Figures 5d - 5f , for the service process of requesting the deployment of network slicing capabilities:

[0284] Exemplary embodiment B4: The application server 30 directly interfaces with the CSMF and requests the network slice management system 20 to deploy the service process of network slice capabilities for it. As Figure 5d shown, it includes the following steps:

[0285] 51d. Bidirectional authentication is completed between the application server and the network slice management system through methods such as PSK.

[0286] 52d. The application server sends a slice capability deployment request message to the CSMF in the network slice management system, and the specified regional information is included in the request message.

[0287] Optionally, the application server can also send a slice capability deployment request message to the slice management open function entity, and the slice management open function entity sends the slice capability deployment request message to the CSMF in the network slice management system.

[0288] 53d. After receiving the slice capability deployment request message, the CSMF sends a network slice capability query request message to the corresponding network management subsystem according to the specified regional information to query the existing network slice capability information of the mobile communication network in the specified region.

[0289] Among them, the specified regional information points to the specified region, and the network management subsystem is the network management system of the specified region, which can manage various information of the mobile communication network in the specified region.

[0290] 54d. The CSMF receives the existing network slice capability information of the mobile communication network in the specified region returned by the network management subsystem.

[0291] 55d. The CSMF determines the network slice capability information yet to be deployed in the specified region according to the existing network slice capability information of the mobile communication network in the specified region.

[0292] Here it is noted that the CSMF can adopt the method described in steps 53d and 54d, that is, determine the network slice capability information yet to be deployed in the specified region by querying the existing network slice capability information of the mobile communication network, but it is not limited to this, and other methods can also be used to determine the network slice capability information yet to be deployed in the specified region.

[0293] 56d. The CSMF sends the network slice capability information yet to be deployed to the network management subsystem for the network management subsystem to deploy the network slice capability yet to be deployed in the specified region accordingly.

[0294] Among them, the CSMF can query the network management subsystem whether there is a corresponding level of NSMF and NSSMF in the specified region, and can also query whether there is an NSSF in the core network of the specified region.

[0295] Scenario 1: If there is no NSMF and NSSMF in the specified area, and there is no NSSF in the core network of the specified area, it is necessary to deploy the corresponding-level NSMF and NSSMF in the specified area, and it is necessary to deploy NSSF in the core network of the specified area. NSMF, NSSMF, and NSSF are the network slice capability information to be deployed. In this case, as shown in step 56d1, the CSMF directly sends the network slice capability information to be deployed to the network management subsystem.

[0296] Scenario 2: If there is NSMF in the specified area but no NSSMF, and there is no NSSF in the core network of the specified area, it is necessary to deploy the corresponding-level NSSMF in the specified area, and it is necessary to deploy NSSF in the core network of the specified area. NSSMF and NSSF are the network slice capability information to be deployed.

[0297] Scenario 3: If there is NSMF in the specified area but no NSSMF, and there is NSSF in the core network of the specified area, it is necessary to deploy the corresponding-level NSSMF in the specified area, and NSSMF is the network slice capability information to be deployed.

[0298] For Scenario 2 and Scenario 3, as shown in step 56d2, the CSMF can send the network slice capability information to be deployed to the network management subsystem via the NSMF.

[0299] Optionally, the CSMF can select the NSMF that covers the area information according to the area information specified in the request message, and send the specified area information to the selected NSMF.

[0300] 57d. After receiving the network slice capability information to be deployed, the network management subsystem starts the network slice capability deployment work.

[0301] 58d. The network management subsystem directly returns a deployment confirmation message to the CSMF or returns a deployment confirmation message to the CSMF via the NSMF.

[0302] 591d. After receiving the deployment confirmation message, the CSMF returns a slice capability deployment request confirmation message to the application server via the slice management open function entity.

[0303] 592d. After determining that the slice capability deployment operation is completed, the CSMF sends a notification message indicating that the slice capability deployment operation has been completed to the application server via the slice management open function entity.

[0304] Optionally, if the slice capability deployment operation fails, the CSMF may send a slice capability deployment request error message to the application server, which includes the reason or reason code for the slice capability deployment error.

[0305] Exemplary embodiment B5: The service process in which the application server 30 directly interfaces with the NSMF to request the network slice management system 20 to deploy network slice capabilities for it is as follows Figure 5e shown and includes the following steps:

[0306] 51e. Bidirectional authentication is completed between the application server and the network slice management system through methods such as PSK.

[0307] 52e. The application server sends a slice capability deployment request message to the first NSMF in the network slice management system, and the specified regional information is included in the request message. Among them, the specified regional information points to the specified region.

[0308] Optionally, the application server may also send a slice capability deployment request message to the slice management open function entity, and the slice management open function entity sends the slice capability deployment request message to the first NSMF in the network slice management system.

[0309] 53e. After receiving the slice capability deployment request message, the first NSMF determines whether it is the NSMF within the specified region; if so, it executes steps 54e1 - 57e1; if not, but it is the upper-level NSMF or the lower-level NSMF, it executes steps 54e2 - 58e2.

[0310] 54e1. The first NSMF sends a network slice capability query request message to the network management subsystem to query the existing network slice capability information of the mobile communication network within the specified region.

[0311] 55e1. The first NSMF receives the existing network slice capability information of the mobile communication network within the specified region returned by the network management subsystem.

[0312] 56e1. The first NSMF determines the network slice capability information yet to be deployed within the specified region based on the existing network slice capability information of the mobile communication network within the specified region.

[0313] 57e1. The first NSMF sends the network slice capability information yet to be deployed to the network management subsystem for the network management subsystem to deploy the network slice capabilities yet to be deployed accordingly.

[0314] 54e2. The first NSMF forwards the slice capability deployment request message to the second NSMF within the specified area, so that the second NSMF cooperates with the corresponding network management subsystem to complete the deployment of network slice capabilities within the specified area.

[0315] 55e2. The second NSMF sends a network slice capability query request message to the network management subsystem according to the slice capability deployment request message, so as to query the existing network slice capability information of the mobile communication network within the specified area.

[0316] 56e2. The second NSMF receives the existing network slice capability information of the mobile communication network within the specified area returned by the network management subsystem.

[0317] 57e2. The second NSMF determines the network slice capability information yet to be deployed within the specified area according to the existing network slice capability information of the mobile communication network within the specified area.

[0318] 58e2. The second NSMF sends the network slice capability information yet to be deployed to the network management subsystem for the network management subsystem to deploy the network slice capabilities yet to be deployed accordingly.

[0319] In the above process, it is shown that the existing network slice capabilities within the specified area already include the NSMF, and the network slice capabilities yet to be deployed may include the NSSMF and / or NSSF.

[0320] Here it is noted that the first NSMF or the second NSMF can determine the network slice capability information yet to be deployed in the specified area by querying the existing network slice capability information of the mobile communication network, but it is not limited to this, and it can also determine the network slice capability information yet to be deployed in the specified area by other means.

[0321] 591e. After receiving the network slice capability information yet to be deployed, the network management subsystem starts the network slice capability deployment work.

[0322] 592e. The network management subsystem directly returns a deployment confirmation message to the first NSMF or returns a deployment confirmation message to the first NSMF via the second NSMF.

[0323] 593e. After receiving the deployment confirmation message, the first NSMF returns a slice capability deployment request confirmation message to the application server.

[0324] 594e. After determining that the slice capability deployment operation is completed, the first NSMF sends a notification message indicating that the slice capability deployment operation has been completed to the application server.

[0325] Optionally, if the slice capability deployment operation fails, the first NSMF may send a slice capability deployment request error message to the application server, which includes the reason or reason code for the slice capability deployment error.

[0326] Exemplary embodiment B6: The service process in which the application server 30 directly interfaces with the NSSMF to request the network slice management system 20 to deploy network slice capabilities for it is as Figure 5f shown and includes the following steps:

[0327] 51f. Bidirectional authentication is completed between the application server and the network slice management system through methods such as PSK.

[0328] 52f. The application server sends a slice capability deployment request message to the first NSSMF in the network slice management system, and the request message includes the specified area information.

[0329] Optionally, the application server may also send a slice capability deployment request message to the slice management open function entity, and the slice management open function entity sends the slice capability deployment request message to the first NSSMF in the network slice management system.

[0330] 53f. After receiving the slice capability deployment request message, the first NSSMF determines whether it is the NSSMF within the specified area; if so, it executes steps 54f1 - 57f1, and if not, it executes 54f2 - 58f2.

[0331] 54f1. The first NSSMF sends a network slice capability query request message to the network management subsystem within the specified area to query the existing network slice capability information of the mobile communication network within the specified area.

[0332] 55f1. The first NSSMF receives the existing network slice capability information of the mobile communication network within the specified area returned by the network management subsystem.

[0333] 56f1. The first NSSMF determines the network slice capability information yet to be deployed within the specified area based on the existing network slice capability information of the mobile communication network within the specified area.

[0334] 57f1. The first NSSMF sends the network slice capability information yet to be deployed to the network management subsystem for the network management subsystem to deploy the network slice capabilities yet to be deployed accordingly.

[0335] 54f2. The first NSSMF forwards the slice capability deployment request message to the second NSSMF within the specified area through the corresponding first NSMF and second NSMF.

[0336] Among them, the first NSMF is the NSMF corresponding to the first NSSMF, and the second NSMF is the NSMF corresponding to the second NSSMF.

[0337] 55f2. The second NSSMF sends a network slice capability query request message to the network management subsystem to query the existing network slice capability information of the mobile communication network in the specified area.

[0338] 56f2. The second NSSMF receives the existing network slice capability information of the mobile communication network in the specified area returned by the network management subsystem.

[0339] 57f2. The second NSSMF determines the network slice capability information to be deployed in the specified area according to the existing network slice capability information of the mobile communication network in the specified area.

[0340] 58f2. The second NSSMF sends the network slice capability information to be deployed to the network management subsystem for the network management subsystem to deploy the network slice capability to be deployed accordingly.

[0341] It should be noted here that the first NSSMF or the second NSSMF can determine the network slice capability information to be deployed in the specified area by querying the existing network slice capability information of the mobile communication network, but it is not limited to this, and other methods can also be used to determine the network slice capability information to be deployed in the specified area.

[0342] 591f. After receiving the network slice capability information to be deployed, the network management subsystem starts the network slice capability deployment work.

[0343] 592f. The network management subsystem directly returns a deployment confirmation message to the first NSSMF or returns a deployment confirmation message to the first NSSMF via the second NSSMF.

[0344] 593f. After receiving the deployment confirmation message, the first NSSMF returns a slice capability deployment request confirmation message to the application server.

[0345] 594f. After determining that the slice capability deployment operation is completed, the first NSSMF sends a notification message indicating that the slice capability deployment operation has been completed to the application server.

[0346] Optionally, if the slice capability deployment operation fails, the first NSSMF can send a slice capability deployment request error message to the application server, and the error message includes the reason or reason code for the slice capability deployment error.

[0347] See Figures 5g - 5i , for the process of subscribing to the network slice capability information update notification service:

[0348] Exemplary embodiment B7:The process in which the application server 30 directly interfaces with the CSMF and requests a subscription to the slice capability information update notification service from the network slice management system 20 is as follows Figure 5g shown and includes the following steps:

[0349] 51g. Bidirectional authentication is completed between the application server and the network slice management system through methods such as PSK.

[0350] 52g. The application server sends a slice capability subscription request message to the CSMF in the network slice management system. The specified area information is included in the request message. The specified area information points to the specified area.

[0351] Optionally, the application server can also send a slice capability subscription request message to the slice management open function entity, and the slice management open function entity sends the slice capability subscription request message to the CSMF in the network slice management system.

[0352] 53g. After receiving the slice capability subscription request message, the CSMF performs subscription processing for the application server for the slice capability update notification service within the specified area.

[0353] 54g. If the slice capability update notification service subscription processing is successful, the CSMF sends a slice capability subscription request confirmation message to the application server.

[0354] 55g. If the slice capability update notification service subscription processing fails, the CSMF sends a slice capability subscription request error message to the application server. The error message includes the reason or reason code for the slice capability subscription error.

[0355] 56g. In the case where the slice capability update notification service subscription processing is successful, the CSMF cooperates with the NSMF and NSSMF corresponding to the specified area to monitor whether the network slice capability information in the specified area of the mobile communication network has changed.

[0356] 57g. In the case where it is monitored that the network slice capability information has changed, the CSMF sends a slice capability change notification message to the application server through the slice management open function entity. The notification message includes the slice capability update information in the specified area of the mobile communication network.

[0357] Exemplary embodiment B8: The process in which the application server 30 directly interfaces with the NSMF and requests a subscription to the slice capability information update notification service from the network slice management system 20 is as follows Figure 5h shown and includes the following steps:

[0358] 51h. Bidirectional authentication is completed between the application server and the network slice management system through methods such as PSK.

[0359] 52h. The application server sends a slice capability subscription request message to the NSMF in the network slice management system. The specified area information is included in the request message, where the specified area information points to a specified area.

[0360] Optionally, the application server may also send a slice capability subscription request message to the slice management open function entity, and the slice management open function entity sends the slice capability subscription request message to the NSMF in the network slice management system.

[0361] 53h. After receiving the slice capability subscription request message, the NSMF performs subscription processing for the slice capability update notification service for the application server.

[0362] 54h. If the subscription processing for the slice capability update notification service is successful, the NSMF sends a slice capability subscription request confirmation message to the application server.

[0363] 55h. If the subscription processing for the slice capability update notification service fails, the NSMF sends a slice capability subscription request error message to the application server. The error message includes the reason or reason code for the slice capability subscription error.

[0364] 56h. When the subscription processing for the slice capability update notification service is successful, the NSMF and the NSSMF corresponding to the specified area cooperate with each other to monitor whether the network slice capability information in the specified area of the mobile communication network has changed.

[0365] 57h. When it is monitored that the network slice capability information has changed, the NSMF sends a slice capability change notification message to the application server. The notification message includes the slice capability update information in the specified area of the mobile communication network.

[0366] Exemplary embodiment B9: The process of the application server 30 directly docking with the NSSMF and requesting to subscribe to the slice capability information update notification service from the network slice management system 20 is as Figure 5i shown and includes the following steps:

[0367] 51i. The application server and the network slice management system complete mutual authentication through methods such as PSK.

[0368] 52i. The application server sends a slice capability subscription request message to the NSSMF in the network slice management system. The request message includes the specified area information, where the specified area information points to the area where the NSSMF is located.

[0369] Optionally, the application server may also send a slice capability subscription request message to the slice management open function entity, and the slice management open function entity sends the slice capability subscription request message to the NSSMF in the network slice management system.

[0370] 53i. After receiving the slice capability subscription request message, the NSSMF performs subscription processing for the slice capability update notification service for the application server.

[0371] 54i. If the subscription processing for the slice capability update notification service is successful, the NSSMF sends a slice capability subscription request confirmation message to the application server.

[0372] 55i. If the subscription processing for the slice capability update notification service fails, the NSSMF sends a slice capability subscription request error message to the application server, and the error message includes the reason or reason code for the slice capability subscription error.

[0373] 56i. When the subscription processing for the slice capability update notification service is successful, the NSSMF monitors whether the network slice capability information in the specified area of the mobile communication network has changed.

[0374] 57i. When it is monitored that the network slice capability information has changed, the NSSMF sends a slice capability change notification message to the application server, and the notification message includes the slice capability update information in the specified area of the mobile communication network.

[0375] It should be noted here that in the above embodiments, the slice capability query request message, the slice capability deployment request message, and the slice capability subscription request message can be carried by HTTP messages or HTTPs messages, or can also be carried by a message format customized by the network slice management system, and this is not limited. In addition, the names of these messages are only examples, and any message name that can implement the corresponding function is applicable to the embodiments of the present application. For example, it can also be simply named the fourth request message, the fifth request message, the sixth request message, etc.

[0376] It should be noted that the execution subject of each step of the method provided in the above embodiments can be the same device, or the method can also be executed by different devices as the execution subject. For example, the execution subject of steps 201 to 204 can be device A; or, the execution subject of step 201 can be device A, and the execution subject of step 202 can be device B; and so on.

[0377] In addition, in some of the processes described in the above embodiments and the accompanying drawings, a plurality of operations appear in a specific order. However, it should be clearly understood that these operations may not be executed in the order in which they appear herein or may be executed in parallel. The serial numbers of the operations, such as 201, 202, etc., are only used to distinguish the different operations, and the serial numbers themselves do not represent any order of execution. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions such as "first" and "second" in this article are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, nor do they limit that "first" and "second" are of different types.

[0378] Figure 6 This is a schematic structural diagram of an application server provided by an embodiment of the present application. As Figure 6 shown, the application server includes: a memory 604 and a processor 605;

[0379] The memory 604 is used to store computer programs and can be configured to store various other data to support operations on the application server. Examples of these data include instructions for any application program or method for operating on the application server, etc.

[0380] The memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk, or an optical disc.

[0381] The processor 605 is coupled to the memory 604 and is used to execute the computer program in the memory 604 for: sending a service request message to a network entity in the network slice management system, where the service request message includes service parameters, to request the network slice management system to provide a target service for it, and the target service includes a slice template service or a network slice capability service; receiving a response message returned by the network entity for the service request message, and the response message carries information on whether the network slice management system can successfully provide the target service for the application server.

[0382] In an optional embodiment, when the result message is affirmative, the processor 605 is further used to: receive a notification message returned by the network entity indicating that the target service has been completed.

[0383] In an alternative embodiment, when the processor 605 sends a service request message to a network entity in the network slice management system, it is specifically configured to: send the service request message to the slice management open function entity, so that the open network entity sends the service request message to the network entity in the network slice management system.

[0384] In an alternative embodiment, when the target service is a slice template service, the service parameters include at least one of a first parameter set and a template identifier, so that the network slice management system can perform operations such as creating, changing, or deleting a slice template.

[0385] In an alternative embodiment, if the service request message is a slice template customization request message, the service parameters include a first parameter set; or if the service request message is a slice template change request message, the service parameters include a first parameter set and a template identifier; or if the service request message is a slice template deletion request message, the service parameters include a template identifier; wherein, the first parameter set includes at least one of: quality of service parameters, configuration parameters of network elements, application-related parameters, geographical location of the data network DN, deployment method of the user plane function UPF, and network capacity parameters.

[0386] In an alternative embodiment, when the target service is a network slice capability service, the service parameters include a second parameter set, so that the network slice management system can perform operations such as querying, subscribing to, or deploying the network slice capabilities of the mobile communication network.

[0387] In an alternative embodiment, the service request message is a slice capability query request message, a slice capability deployment request message, or a slice capability subscription request message; wherein, the second parameter set includes: specified area information.

[0388] Further, as Figure 6 shown, the application server further includes: a communication component 606, a power supply component 608, and other components. Figure 6 Only some components are schematically shown, and it does not mean that the application server only includes Figure 6 the components shown.

[0389] Correspondingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, and when the computer program is executed, it can implement each step executable by the application server in the above service request method embodiment.

[0390] Correspondingly, an embodiment of the present application further provides a computer program product, including a computer program or instruction, and when the computer program or instruction is executed by a processor, it can implement each step executable by the application server in the above service request method embodiment.

[0391] Figure 7A schematic structural diagram of a network entity provided by an embodiment of this application. As Figure 7 shown, the network entity includes: a memory 704 and a processor 705;

[0392] The memory 704 is used to store computer programs and can be configured to store various other data to support operations on the network entity. Examples of such data include instructions for any application or method for operating on the network entity, etc.

[0393] The memory 704 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk, or an optical disk.

[0394] The processor 705 is coupled to the memory 704 and is used to execute the computer program in the memory 704 for: receiving a service request message sent by an application server, where the service request message includes service parameters for requesting a target service from a network slice management system; providing the target service for the application server according to the service parameters, where the target service includes a network slice template service or a network slice capability service; and returning a response message to the application server, where the response message carries information on whether the network slice management system can successfully provide the target service for the application server.

[0395] In an optional embodiment, the processor 705 is further used for: when the result message is an affirmative result message, returning a notification message indicating that the target service has been completed to the application server.

[0396] In an optional embodiment, when receiving the service request message sent by the application server, the processor 705 is specifically used for: receiving the service request message sent by the application server from a slice management open function entity.

[0397] In an optional embodiment, when the target service is a network slice template service, the service parameters at least include one of a first parameter set and a template identifier; when providing the target service for the application server according to the service parameters, the processor 705 is specifically used for: performing operations of creating, changing, or deleting a slice template according to at least one of the first parameter set and the template identifier included in the service parameters.

[0398] In an optional embodiment, the service request message is a slice template customization request message, and the service parameters include a first parameter set. When the processor 705 creates, changes, or deletes a slice template according to at least one of the first parameter set and the template identifier included in the service parameters, it is specifically used for: creating a slice template according to the first parameter set; or the service request message is a slice template change request message, and the service parameters include the first parameter set and the template identifier. When creating, changing, or deleting a slice template according to at least one of the first parameter set and the template identifier included in the service parameters, it is specifically: changing the network slice template according to the template identifier and the first parameter set; or the service request message is a slice template deletion request message, and the service parameters include the template identifier. When creating, changing, or deleting a slice template according to at least one of the first parameter set and the template identifier included in the service parameters, it is specifically: deleting the slice template according to the template identifier. Among them, the first parameter set includes at least one of: quality of service parameters, configuration parameters of network elements, application-related parameters, geographical location of the data network DN, deployment method of the user plane function UPF, and network capacity parameters. The template identifier includes at least one of the NST identifier and the NSST identifier.

[0399] In an optional embodiment, the network entity is the SMF in the network slice management system. When the processor 705 creates a slice template according to the first parameter set, it is specifically used for: sending the first parameter set to the corresponding NSMF, so that the NSMF sends the subnet slice template parameters required to generate the NSST to the selected NSSMF according to the first parameter set and generates an NST associated with the NSST; receiving at least one of the identifiers of the NST and the NSST sent by the NSMF, where the identifier of the NSST is returned by the NSSMF after generating the NSST according to the subnet slice template parameters; where the response message is a slice template customization request confirmation message and is returned by the CSMF to the application server, and the slice template customization request confirmation message includes at least one of the identifiers of the NST and the NSST.

[0400] In an optional embodiment, the network entity is the NSMF in the network slice management system. When the processor 705 creates a slice template according to the first parameter set, it is specifically used for: sending the subnet slice template parameters required to generate the NSST to the selected NSSMF according to the first parameter set and generating an NST associated with the NSST; and receiving the identifier of the NSST returned by the NSSMF after generating the NSST according to the subnet slice template parameters; where the response message is a slice template customization request confirmation message and is returned by the NSMF to the application server, and the slice template customization request confirmation message includes at least one of the identifiers of the NST and the NSST.

[0401] In an optional embodiment, if the network entity is the NSSMF in the network slice management system, when the processor 705 creates a slice template according to the first parameter set, it is specifically configured to: generate an NSST according to the first parameter set, and report the identifier of the NSST to the corresponding NSMF, so that the NSMF generates an NST corresponding to the NSST; and receive the identifier of the NST returned by the NSMF after generating the NST; wherein, the response message is a slice template customization request confirmation message, and is returned by the NSSMF to the application server, and the slice template customization request confirmation message includes the identifier of at least one of the NST and the NSST.

[0402] In an optional embodiment, the generated NST is a customized NST, and the NSST includes at least one customized NSST. Further, the identifier of the customized NST or the customized NSST includes an identifier field of the customized manufacturer, or the identifier of the customized NST or the customized NSST is associated with the identifier of the customized manufacturer.

[0403] Further optionally, the slice template customization request message includes a customization identifier, or the application server belongs to a set of third-party servers that are pre-maintained and have the permission to customize slice templates.

[0404] In an optional embodiment, if the network entity is the CSMF in the network slice management system, when the processor 705 changes a slice template according to the template identifier and the first parameter set, it is specifically configured to: send the first parameter set and the template identifier to the corresponding NSMF, so that the NSMF changes the NST according to the first parameter set and the template identifier and / or sends subnet slice template parameters to the selected NSSMF so that the selected NSSMF changes the NSST accordingly, and update the mapping relationship between the NST and the NSST after the NST and / or the NSST are changed; receive the change confirmation message returned by the NSMF; wherein, the response message is a slice template change request confirmation message, and is returned by the CSMF to the application server.

[0405] In an optional embodiment, if the network entity is the NSMF in the network slice management system, when the processor 705 changes a slice template according to the template identifier and the first parameter set, it is specifically configured to: change the NST according to the first parameter set and the template identifier and / or send subnet slice template parameters to the selected NSSMF so that the selected NSSMF changes the NSST accordingly; and update the mapping relationship between the NST and the NSST after the NST and / or the NSST are changed; wherein, the response message is a slice template change request confirmation message, and is returned by the NSMF to the application server.

[0406] In an optional embodiment, when the template is identified as an NST identifier and the network entity is implemented as an NSMF, the processor 705 is specifically configured to: change the NST corresponding to the NST identifier according to the first parameter set, and update the mapping relationship between the NST and the NSST after the NST is changed;

[0407] Or

[0408] When the template is identified as an NST identifier and the network entity is implemented as an NSMF, the processor 705 is specifically configured to: change the NST according to the first parameter set, send the subnet slice template parameters to the selected NSSMF to cause the NSSMF to change the NSST, and update the mapping relationship between the NST and the NSST after the NST and the NSST are changed.

[0409] In an optional embodiment, when the template is identified as an NSST identifier and the network entity is implemented as an NSMF, the processor 705 is specifically configured to: send the subnet slice template parameters and the NSST identifier to the selected NSSMF to cause the NSSMF to change the NSST, and update the mapping relationship between the NST and the NSST after the NSST is changed.

[0410] In an optional embodiment, if the network entity is an NSSMF in the network slice management system, when the processor 705 performs a change operation on the slice template according to the template identifier and the first parameter set, it is specifically configured to: when the template identifier is an NSST identifier, change the NSST according to the first parameter set and the template identifier, and report the identifier of the changed NSST to the corresponding NSMF for the NSMF to update the mapping relationship between the NST and the NSST; wherein, the response message is a slice template change request confirmation message and is returned by the NSSMF to the application server.

[0411] In an optional embodiment, when the template is identified as an NST identifier, the processor 705 is specifically configured to: report the first parameter set and the NST identifier to the corresponding NSMF for the NSMF to change the NST and update the mapping relationship between the NST and the NSST;

[0412] Or

[0413] When the template is identified as an NST identifier, the processor 705 is specifically configured to: change the NSST according to the first parameter set and the template identifier, and report the first parameter set and the NST identifier to the corresponding NSMF for the NSMF to change the NST and update the mapping relationship between the NST and the NSST.

[0414] In an optional embodiment, when the network entity is the CSMF, NSMF, or NSSMF in the network slice management system, the processor 705 is further configured to: if the template identifier identifies a customized NST and / or a customized NSST, obtain the identifier of the customized manufacturer corresponding to the customized NST according to the template identifier; if the identifier of the application server matches the identifier of the customized manufacturer, perform an operation of changing the customized NST and / or the customized NSST and the mapping relationship between the NST and the NSST.

[0415] Further optionally, the processor 705 is further configured to: if the template identifier identifies a system default NST and / or a system default NSST, or the identifier of the application server does not match the identifier of the customized manufacturer, output a change error message.

[0416] In an optional embodiment, the first parameter set further includes: specified area information, which is used for the CSMF to determine the corresponding NSMF or for the NSMF to select the NSSMF.

[0417] In an optional embodiment, when the network entity is the CSMF in the network slice management system, when the processor 705 performs a deletion operation on the slice template according to the template identifier, it is specifically configured to: send the template identifier to the corresponding NSMF for the NSMF to delete the corresponding NST and / or instruct the selected NSSMF to delete the corresponding NSST, and delete the mapping relationship corresponding to the deleted NST and / or NSST in the NST and NSST mapping relationship; receive a first deletion confirmation message returned by the NSMF; where the response message is a slice template deletion request confirmation message and is returned by the CSMF to the application server.

[0418] In an optional embodiment, when the network entity is the NSMF in the network slice management system, when the processor 705 performs a deletion operation on the slice template according to the template identifier, it is specifically configured to: delete the NST and / or instruct the NSSMF to delete the corresponding NSST according to the template identifier, and delete the mapping relationship corresponding to the deleted NST and / or NSST in the NST and NSST mapping relationship; where the response message is a slice template deletion request confirmation message and is returned by the NSMF to the application server.

[0419] In an optional embodiment, when the template identifier is an NST identifier and the network entity is implemented as the NSMF, the processor 702 is specifically configured to: send the NSST identifier corresponding to the NST identifier to the selected NSSMF for the NSSMF to delete the corresponding NSST, and delete the NST corresponding to the NST identifier and its mapping relationship with the NSST; or,

[0420] When the template is identified as the NSST identifier and the network entity is implemented as the NSMF, the processor 702 is specifically configured to: send the NSST identifier to a selected NSSMF for the NSSMF to delete the corresponding NSST, and delete the mapping relationship corresponding to the deleted NSST in the NST and NSST mapping relationship corresponding to the NSST identifier.

[0421] In an optional embodiment, the network entity is the NSSMF in the network slice management system. When the processor 705 performs a deletion operation on the slice template according to the template identifier, it is specifically configured to: delete the corresponding NSST according to the template identifier, and report the template identifier to the corresponding NSMF for the NSMF to delete the mapping relationship corresponding to the deleted NSST in the NST and NSST mapping relationship; receive a third deletion confirmation message returned by the NSMF; wherein the response message is a slice template deletion request confirmation message and is returned by the NSSMF to the application server.

[0422] Further optionally, before the processor 705 deletes the mapping relationship corresponding to the deleted NST and / or NSST, it is further configured to: if the template identifier identifies a customized NST and / or a customized NSST, obtain the identifier of the customized manufacturer corresponding to the customized NST according to the template identifier; if the identifier of the application server matches the identifier of the customized manufacturer, then perform the operation of deleting the customized NST and / or the customized NSST and the mapping relationship corresponding to the deleted customized NST and / or customized NSST in the NST and NSST mapping relationship.

[0423] Further optionally, the processor 705 is further configured to: if the template identifier identifies a system default NST and / or a system default NSST, or the identifier of the application server does not match the identifier of the customized manufacturer, output a deletion error message.

[0424] In an optional embodiment, when the target service is a network slice capability service, the service parameter includes a second parameter set; correspondingly, when the processor 705 provides the target service for the application server according to the service parameter, it is specifically configured to: perform query, subscription or deployment operations on the network slice capability of the mobile communication network according to the second parameter set.

[0425] In an optional embodiment, the second parameter set includes: specified area information; when the service request message is a slice capability query request message, when the processor 705 performs a query, subscription, or deployment operation on the network slice capability of the mobile communication network according to the second parameter set, it is specifically used for: querying the network slice capability of the mobile communication network according to the specified area information; or when the service request message is a slice capability deployment request message, when the processor 705 performs a query, subscription, or deployment operation on the network slice capability of the mobile communication network according to the second parameter set, it is specifically used for: deploying the network slice capability of the mobile communication network according to the specified area information; or when the service request message is a slice capability subscription request message, when the processor 705 performs a query, subscription, or deployment operation on the network slice capability of the mobile communication network according to the second parameter set, it is specifically used for: subscribing to the network slice capability of the mobile communication network according to the specified area information.

[0426] In an optional embodiment, if the network entity is the CSMF in the network slice management system, when the processor 705 performs a query operation on the network slice capability of the mobile communication network according to the specified area information, it is specifically used for: sending the specified area information to the corresponding NSMF, so that the NSMF obtains the network slice capability information of the mobile communication network in the specified area from the local or from the NSSMF corresponding to the specified area information and returns it to the CSMF; receiving the network slice capability information of the mobile communication network in the specified area returned by the NSMF; wherein, the response message is a slice capability query request confirmation message and is returned by the CSMF to the application server, and the slice capability query request confirmation message includes the network slice capability information of the mobile communication network in the specified area.

[0427] In an optional embodiment, if the network entity is the NSMF in the network slice management system, when the processor 705 performs a query operation on the network slice capability of the mobile communication network according to the specified area information, it is specifically used for: obtaining the network slice capability information of the mobile communication network in the specified area from the local or from the NSSMF corresponding to the specified area information; wherein, the response message is a slice capability query request confirmation message and is returned by the NSMF to the application server, and the slice capability query request confirmation message includes the network slice capability information of the mobile communication network in the specified area.

[0428] In an optional embodiment, if the network entity is the NSSMF in the network slice management system, when the processor 705 queries the network slice capabilities of the mobile communication network according to the specified area information, it is specifically configured to: obtain the network slice capability information of the mobile communication network in the specified area according to the specified area information; wherein, the response message is a slice capability query request confirmation message, and is returned by the NSSMF to the application server, and the slice capability query request confirmation message includes the network slice capability information of the mobile communication network in the specified area.

[0429] In an optional embodiment, if the network entity is the CSMF in the network slice management system, when the processor 705 deploys the network slice capabilities of the mobile communication network according to the specified area information, it is specifically configured to: determine the network slice capability information to be deployed in the specified area according to the specified area information; send the network slice capability information to be deployed to the network management subsystem, so that the network management subsystem deploys the network slice capabilities to be deployed in the specified area accordingly, and receive the deployment confirmation message returned by the network management subsystem; wherein, the response message is a slice capability deployment request confirmation message, and is returned by the CSMF to the application server.

[0430] In an optional embodiment, if the network entity is the first NSMF in the network slice management system, when the processor 705 deploys the network slice capabilities of the mobile communication network according to the specified area information, it is specifically configured to: in the case where the first NSMF is the NSMF in the specified area, determine the network slice capability information to be deployed in the specified area according to the specified area information, and send it to the network management subsystem, so that the network management subsystem deploys the network slice capabilities to be deployed in the specified area accordingly, and receive the deployment confirmation message returned by the network management subsystem; in the case where the first NSMF is not the NSMF in the specified area, forward the slice capability deployment request message to the second NSMF in the specified area, so that the second NSMF cooperates with the corresponding network management subsystem to complete the deployment of the network slice capabilities in the specified area, and receive the deployment confirmation message returned by the network management subsystem through the second NSMF; wherein, the response message is a slice capability deployment request confirmation message, and is returned by the CSMF to the application server.

[0431] In an alternative embodiment, the network entity is the first NSSMF in the network slice management system. When the processor 705 performs a deployment operation on the network slice capabilities of the mobile communication network according to the specified area information, it is specifically configured to: when the first NSSMF is the NSSNF within the specified area, determine the network slice capability information yet to be deployed in the specified area according to the specified area information, and send it to the network management subsystem, so that the network management subsystem deploys the network slice capabilities yet to be deployed within the specified area accordingly, and receive the deployment confirmation message returned by the network management subsystem; when the first NSSMF is not the NSMF within the specified area, forward the slice capability deployment request message to the second NSSMF within the specified area, so that the second NSSMF cooperates with the corresponding network management subsystem to complete the deployment of the network slice capabilities within the specified area, and receive the deployment confirmation message returned by the network management subsystem via the second NSSMF; wherein, the response message is a slice capability deployment request confirmation message, and is returned by the CSMF to the application server.

[0432] In an alternative embodiment, the network entity is the CSMF, NSMF or NSSMF in the network slice management system. When the processor 705 performs a subscription operation on the network slice capabilities of the mobile communication network according to the specified area information, it is specifically configured to: perform a subscription process for the application server to the slice capability update notification service within the specified area according to the specified area information, and when the subscription process is successful and the network slice capability information of the mobile communication network within the specified area changes, return a slice capability change notification message to the application server, and the notification message includes the slice capability update information of the mobile communication network within the specified area.

[0433] Further, as Figure 7 shown, the network entity further includes: other components such as a communication component 706, a display 707, a power supply component 708, and an audio component 709. Figure 7 Only some components are schematically shown, and it does not mean that the network entity only includes Figure 7 the components shown.

[0434] Correspondingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, and when the computer program is executed, it can implement the steps executable by the network entity in the network slice management system in the above service providing method embodiment.

[0435] Correspondingly, an embodiment of the present application further provides a computer program product, including a computer program or instruction, and when the computer program or instruction is executed by a processor, it can implement the steps executable by the network entity in the network slice management system in the above service providing method embodiment.

[0436] The above Figure 6and Figure 7 The communication component in Figure 7 is configured to facilitate communication, either wired or wireless, between the device where the communication component is located and other devices. The device where the communication component is located can access a communication standard-based wireless network, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0437] The above-mentioned Figure 7 The display in Figure 7 includes a screen, and the screen can include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes and gestures on the touch panel. The touch sensors can sense not only the boundaries of touch or swipe actions, but also detect the duration and pressure associated with the touch or swipe operation.

[0438] The above-mentioned Figure 6 and Figure 7 The power supply component in Figure 7 provides power for various components of the device where the power supply component is located. The power supply component can include a power management system, one or more power supplies, and other components associated with generating, managing and distributing power for the device where the power supply component is located.

[0439] The above-mentioned Figure 7 The audio component in Figure 7 can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), and when the device where the audio component is located is in an operating mode, such as a call mode, a recording mode and a voice recognition mode, the microphone is configured to receive external audio signals. The received audio signals can be further stored in a memory or sent via the communication component. In some embodiments, the audio component further includes a speaker for outputting audio signals.

[0440] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0441] This application is described with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a means for implementing the functions specified in one or more flows in the flowchart and / or one or more blocks in the block diagram.

[0442] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufacture including an instruction means that implements the functions specified in one or more flows in the flowchart and / or one or more blocks in the block diagram.

[0443] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more flows in the flowchart and / or one or more blocks in the block diagram.

[0444] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0445] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory such as read-only memory (ROM) or flash RAM. The memory is an example of computer-readable media.

[0446] A computer-readable medium includes both permanent and non-permanent, removable and non-removable media and can implement information storage by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer-readable medium does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0447] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or apparatus comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or apparatus. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising the element.

[0448] The above are only examples of the present application and are not intended to limit the present application. For those skilled in the art, the present application can have various changes and modifications. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. A service request method, applicable to an application server, characterized in that, The method includes: Sending a service request message to a network entity in a network slice management system, the service request message including service parameters, to request the network slice management system to provide a target service for it, the target service including a network slice capability service; the network slice capability service refers to a service for identifying whether a mobile communication network has network slice capabilities and, in the case of having network slice capabilities, managing information on the network slice capabilities it has; Receiving a response message returned by the network entity for the service request message, the response message carrying information on whether the network slice management system can successfully provide the target service for the application server.

2. The method according to claim 1, characterized in that, In the case where the response message is an affirmative result message, it further includes: receiving a notification message returned by the network entity indicating that the target service has been completed.

3. The method according to claim 1, wherein Sending a service request message to a network entity in a network slice management system includes: Sending a service request message to a slice management open function entity, so that the slice management open function entity sends the service request message to the network entity in the network slice management system.

4. The method according to any one of claims 1 to 3, characterized in that, If the target service further includes a network slice template service, then in the case where the target service is a network slice template service, the service parameters include at least one of a first parameter set and a template identifier, so that the network slice management system performs operations of creating, changing, or deleting a slice template.

5. The method according to claim 4, characterized in that If the service request message is a slice template customization request message, then the service parameters include the first parameter set; Or If the service request message is a slice template change request message, then the service parameters include the first parameter set and a template identifier; Or If the service request message is a slice template deletion request message, then the service parameters include a template identifier; Wherein, the first parameter set includes at least one of: quality of service parameters, configuration parameters of network elements, application-related parameters, geographical location of a data network DN, deployment method of a user plane function UPF, and network capacity parameters; the template identifier includes at least one of a network slice template NST identifier and a network slice sub-template NSST identifier.

6. The method according to any one of claims 1-3, characterized in that In the case where the target service is a network slice capability service, the service parameters include a second parameter set, so that the network slice management system performs operations of querying, subscribing to, or deploying the network slice capabilities of a mobile communication network.

7. The method according to claim 6, characterized in that, The service request message is a slice capability query request message, a slice capability deployment request message, or a slice capability subscription request message; Wherein, the second parameter set includes: specified area information.

8. A service providing method, applicable to a network entity in a network slice management system, characterized in that, The method includes: Receiving a service request message sent by an application server, the service request message including service parameters for requesting a target service from the network slice management system; Providing the target service for the application server according to the service parameters, the target service including a network slice capability service; the network slice capability service refers to a service for identifying whether a mobile communication network has network slice capabilities and, in the case of having network slice capabilities, managing information on the network slice capabilities it has; Return a response message to the application server, where the response message carries information on whether the network slice management system can successfully provide the target service for the application server.

9. The method according to claim 8, wherein It further includes: In the case where the response message is an affirmative result message, return a notification message indicating that the target service has been completed to the application server.

10. The method according to claim 8, characterized in that, Receive a service request message sent by the application server, including: Receive a service request message from the application server sent by the slice management open function entity.

11. The method according to claim 8, wherein If the target service further includes a network slice template service, then in the case where the target service is a network slice template service, the service parameters at least include one of a first parameter set and a template identifier; Accordingly, provide the target service for the application server according to the service parameters, including: perform operations of creating, changing, or deleting a slice template according to at least one of the first parameter set and the template identifier included in the service parameters.

12. The method according to claim 11, wherein If the service request message is a slice template customization request message and the service parameters include the first parameter set, then perform operations of creating, changing, or deleting a slice template according to at least one of the first parameter set and the template identifier included in the service parameters. Specifically: create a slice template according to the first parameter set; Or If the service request message is a slice template change request message and the service parameters include the first parameter set and the template identifier, then perform operations of creating, changing, or deleting a slice template according to at least one of the first parameter set and the template identifier included in the service parameters. Specifically: change the slice template according to the template identifier and the first parameter set; Or If the service request message is a slice template deletion request message and the service parameters include the template identifier, then perform operations of creating, changing, or deleting a slice template according to at least one of the first parameter set and the template identifier included in the service parameters. Specifically: delete the slice template according to the template identifier; Wherein, the first parameter set includes at least one of: quality of service parameters, configuration parameters of network elements, application-related parameters, geographical location of the data network DN, deployment method of the user plane function UPF, and network capacity parameters; the template identifier includes at least one of a network slice template NST identifier and a network slice sub-template NSST identifier.

13. The method according to claim 12, wherein If the network entity is the communication service management function CSMF in the network slice management system, then performing the operation of creating a slice template according to the first parameter set includes: Send the first parameter set to the corresponding network slice management function NSMF, so that the NSMF sends the subnet slice template parameters required to generate the NSST to the selected network slice subnet management function NSSMF according to the first parameter set and generates an NST associated with the NSST; Receive the identifier of at least one of the NST and the NSST sent by the NSMF; wherein, the identifier of the NSST is returned by the NSSMF after generating the NSST according to the subnet slice template parameters. Wherein, the response message is a slice template customization request confirmation message, and is returned by the CSMF to the application server, and the slice template customization request confirmation message includes the identifier of at least one of the NST and the NSST.

14. The method according to claim 12, wherein If the network entity is the NSMF in the network slice management system, the operation of creating a slice template according to the first parameter set includes: Sending the subnet slice template parameters required to generate the NSST to the selected NSSMF according to the first parameter set and generating an NST associated with the NSST; and, Receiving the identifier of the NSST returned by the NSSMF after generating the NSST according to the subnet slice template parameters; Wherein, the response message is a slice template customization request confirmation message, and is returned by the NSMF to the application server, and the slice template customization request confirmation message includes the identifier of at least one of the NST and the NSST.

15. The method according to claim 12, wherein If the network entity is the NSSMF in the network slice management system, the operation of creating a slice template according to the first parameter set includes: Generating an NSST according to the first parameter set and reporting the identifier of the NSST to the corresponding NSMF, so that the NSMF generates an NST corresponding to the NSST; and Receiving the identifier of the NST returned by the NSMF after generating the NST; Wherein, the response message is a slice template customization request confirmation message, and is returned by the NSSMF to the application server, and the slice template customization request confirmation message includes the identifier of at least one of the NST and the NSST.

16. The method according to any one of claims 13-15, characterized in that, The NST is a customized NST, and the NSST includes at least one customized NSST; The identifier of the customized NST or the customized NSST contains an identifier field of the customized manufacturer, or the identifier of the customized NST or the customized NSST is associated with the identifier of the customized manufacturer.

17. The method according to claim 16, wherein The slice template customization request message includes a customization identifier, or the identifier of the application server belongs to a set of third-party server identifiers that are pre-maintained and have the right to customize slice templates.

18. The method according to claim 12, wherein If the network entity is the CSMF in the network slice management system, the operation of changing a slice template according to the template identifier and the first parameter set includes: Sending the first parameter set and the template identifier to the corresponding NSMF, so that the NSMF changes the NST according to the first parameter set and the template identifier and / or sends subnet slice template parameters to the selected NSSMF to enable the NSSMF to change the NSST, and updating the mapping relationship between the NST and the NSST after the NST and / or the NSST are changed; Receiving the change confirmation message returned by the NSMF; wherein, the response message is a slice template change request confirmation message, and is returned by the CSMF to the application server.

19. The method according to claim 12, wherein If the network entity is the NSMF in the network slice management system, the operation of changing a slice template according to the template identifier and the first parameter set includes: Changing the NST and / or sending subnet slice template parameters to a selected NSSMF according to the first parameter set and the template identifier, so that the NSSMF changes the NSST; and Updating the mapping relationship between the NST and the NSST after the NST and / or NSST is changed; wherein the response message is a slice template change request confirmation message and is returned by the NSMF to the application server.

20. The method according to claim 18 or 19, wherein when the template identifier is an NST identifier, the NSMF changes the NST corresponding to the NST identifier according to the first parameter set, and updates the mapping relationship between the NST and the NSST after the NST is changed; or when the template identifier is an NST identifier, the NSMF changes the NST according to the first parameter set, sends subnet slice template parameters to a selected NSSMF to enable the NSSMF to change the NSST, and updates the mapping relationship between the NST and the NSST after the NST and the NSST are changed.

21. The method according to claim 18 or 19, wherein when the template identifier is an NSST identifier, the NSMF sends subnet slice template parameters and the NSST identifier to a selected NSSMF to enable the NSSMF to change the NSST, and updates the mapping relationship between the NST and the NSST after the NSST is changed.

22. The method according to claim 12, wherein If the network entity is the NSSMF in the network slice management system, the operation of changing the slice template according to the template identifier and the first parameter set includes: when the template identifier is an NSST identifier, changing the NSST according to the first parameter set and the template identifier, and reporting the identifier of the changed NSST to the corresponding NSMF for the NSMF to update the mapping relationship between the NST and the NSST; wherein the response message is a slice template change request confirmation message and is returned by the NSSMF to the application server.

23. The method according to claim 22, wherein It further includes: when the template identifier is an NST identifier, reporting the first parameter set and the NST identifier to the corresponding NSMF for the NSMF to change the NST and update the mapping relationship between the NST and the NSST; or when the template identifier is an NST identifier, changing the NSST according to the first parameter set and the template identifier, and reporting the first parameter set and the NST identifier to the corresponding NSMF for the NSMF to change the NST and update the mapping relationship between the NST and the NSST.

24. The method according to claim 18, 19, 22 or 23, characterized in that, It further includes: if the template identifier identifies a customized NST and / or a customized NSST, obtaining the identifier of the customized manufacturer corresponding to the customized NST and / or the customized NSST according to the template identifier; if the identifier of the application server matches the identifier of the customized manufacturer, performing the operation of changing the customized NST and / or the customized NSST and the mapping relationship between the NST and the NSST.

25. The method according to claim 24, wherein It further includes: If the template identifier identifies the system default NST and / or the system default NSST, or the identifier of the application server does not match the identifier of the custom manufacturer, an error message for the change is output.

26. The method according to claim 13, 14, 18 or 19, characterized in that, The first parameter set further includes: specified regional information, which is used for the communication service management function CSMF in the network slice management system to determine the corresponding NSMF or for the NSMF to select the NSSMF.

27. The method according to claim 12, wherein If the network entity is the CSMF in the network slice management system, the deletion operation on the slice template is performed according to the template identifier, including: Sending the template identifier to the corresponding NSMF for the NSMF to delete the NST and / or instruct the selected NSSMF to delete the corresponding NSST, and deleting the mapping relationship corresponding to the deleted NST and / or NSST in the NST and NSST mapping relationship; Receiving a first deletion confirmation message returned by the NSMF; wherein, the response message is a slice template deletion request confirmation message and is returned by the CSMF to the application server.

28. The method according to claim 12, characterized in that, If the network entity is the NSMF in the network slice management system, the deletion operation on the slice template is performed according to the template identifier, including: Deleting the NST according to the template identifier and / or instructing the NSSMF to delete the corresponding NSST, and deleting the mapping relationship corresponding to the deleted NST and / or NSST in the NST and NSST mapping relationship; Wherein, the response message is a slice template deletion request confirmation message and is returned by the NSMF to the application server.

29. The method according to claim 27 or 28, wherein When the template identifier is an NST identifier, the NSMF sends the NSST identifier corresponding to the NST identifier to the selected NSSMF for the NSSMF to delete the corresponding NSST, and deletes the NST corresponding to the NST identifier and its mapping relationship with the NSST; When the template identifier is an NSST identifier, the NSMF sends the NSST identifier to the selected NSSMF for the NSSMF to delete the corresponding NSST, and deletes the mapping relationship corresponding to the deleted NSST in the NST and NSST mapping relationship corresponding to the NSST identifier.

30. The method according to claim 12, wherein If the network entity is the NSSMF in the network slice management system, the deletion operation on the slice template is performed according to the template identifier, including: Deleting the corresponding NSST according to the template identifier and reporting the template identifier to the corresponding NSMF for the NSMF to delete the mapping relationship corresponding to the deleted NSST in the NST and NSST mapping relationship; Receiving a third deletion confirmation message returned by the NSMF; wherein, the response message is a slice template deletion request confirmation message and is returned by the NSSMF to the application server.

31. The method according to claim 27, 28 or 30, characterized in that, Before deleting the mapping relationship corresponding to the deleted NST and / or NSST, further includes: If the template identifier identifies a customized NST and / or a customized NSST, obtain the identifier of the customized manufacturer corresponding to the customized NST according to the template identifier; If the identifier of the application server matches the identifier of the customized manufacturer, then perform deletion of the customized NST and / or the customized NSST and the mapping relationship in the NST and NSST mapping relationship corresponding to the deleted customized NST and / or customized NSST.

32. The method according to claim 31, wherein It further includes: If the template identifier identifies a system default NST and / or a system default NSST, or the identifier of the application server does not match the identifier of the customized manufacturer, then output a deletion error message.

33. The method according to claim 8, characterized in that, When the target service is a network slice capability service, the service parameter includes a second parameter set; Correspondingly, providing the target service for the application server according to the service parameter includes: performing a query, subscription, or deployment operation on the network slice capability of the mobile communication network according to the second parameter set.

34. The method according to claim 33, wherein The second parameter set includes: specified area information; If the service request message is a slice capability query request message, then performing a query, subscription, or deployment operation on the network slice capability of the mobile communication network according to the second parameter set includes: performing a query operation on the network slice capability of the mobile communication network according to the specified area information; Or If the service request message is a slice capability deployment request message, then performing a query, subscription, or deployment operation on the network slice capability of the mobile communication network according to the second parameter set includes: performing a deployment operation on the network slice capability of the mobile communication network according to the specified area information; Or If the service request message is a slice capability subscription request message, then performing a query, subscription, or deployment operation on the network slice capability of the mobile communication network according to the second parameter set includes: performing a subscription operation on the network slice capability of the mobile communication network according to the specified area information.

35. The method according to claim 34, wherein If the network entity is the CSMF in the network slice management system, then performing a query operation on the network slice capability of the mobile communication network according to the specified area information includes: Sending the specified area information to the corresponding NSMF for the NSMF to obtain the network slice capability information of the mobile communication network in the specified area from the NSSMF corresponding to the specified area information and return it to the CSMF; Receiving the network slice capability information of the mobile communication network in the specified area returned by the NSMF; Wherein, the response message is a slice capability query request confirmation message and is returned by the CSMF to the application server, and the slice capability query request confirmation message includes the network slice capability information of the mobile communication network in the specified area.

36. The method according to claim 34, wherein If the network entity is the NSMF in the network slice management system, then performing a query operation on the network slice capability of the mobile communication network according to the specified area information includes: Obtaining the network slice capability information of the mobile communication network in the specified area from the NSSMF corresponding to the specified area information; Wherein, the response message is a slice capability query request confirmation message, and is returned by the NSMF to the application server. The slice capability query request confirmation message includes the network slice capability information of the mobile communication network in a specified area.

37. The method according to claim 34, characterized in that, If the network entity is the NSSMF in the network slice management system, the operation of querying the network slice capability of the mobile communication network according to the specified area information includes: Obtaining the network slice capability information of the mobile communication network in the specified area according to the specified area information; Wherein, the response message is a slice capability query request confirmation message, and is returned by the NSSMF to the application server. The slice capability query request confirmation message includes the network slice capability information of the mobile communication network in a specified area.

38. The method according to claim 34, wherein If the network entity is the CSMF in the network slice management system, the operation of deploying the network slice capability of the mobile communication network according to the specified area information includes: Determining the network slice capability information to be deployed in the specified area according to the specified area information; Sending the network slice capability information to be deployed to the network management subsystem corresponding to the specified area, so that the network management subsystem deploys the network slice capability to be deployed in the specified area accordingly, and receiving the deployment confirmation message returned by the network management subsystem; Wherein, the response message is a slice capability deployment request confirmation message, and is returned by the CSMF to the application server.

39. The method according to claim 34, wherein If the network entity is the first NSMF in the network slice management system, the operation of deploying the network slice capability of the mobile communication network according to the specified area information includes: When the first NSMF is the NSMF in the specified area, determining the network slice capability information to be deployed in the specified area according to the specified area information, and sending it to the network management subsystem corresponding to the specified area, so that the network management subsystem deploys the network slice capability to be deployed in the specified area accordingly, and receiving the deployment confirmation message returned by the network management subsystem; When the first NSMF is not the NSMF in the specified area, forwarding the slice capability deployment request message to the second NSMF in the specified area, so that the second NSMF cooperates with the corresponding network management subsystem to complete the deployment of the network slice capability in the specified area, and receiving the deployment confirmation message returned by the network management subsystem through the second NSMF; Wherein, the response message is a slice capability deployment request confirmation message, and is returned by the CSMF to the application server.

40. The method according to claim 34, wherein If the network entity is the first NSSMF in the network slice management system, the operation of deploying the network slice capability of the mobile communication network according to the specified area information includes: When the first NSSMF is the NSSNF within the specified area, determine the network slice capability information yet to be deployed in the specified area according to the specified area information, and send it to the network management subsystem corresponding to the specified area, so that the network management subsystem deploys the network slice capability yet to be deployed within the specified area accordingly, and receive the deployment confirmation message returned by the network management subsystem; When the first NSSMF is not the NSMF within the specified area, forward the slice capability deployment request message to the second NSSMF within the specified area, so that the second NSSMF cooperates with the corresponding network management subsystem to complete the deployment of the network slice capability within the specified area, and receive the deployment confirmation message returned by the network management subsystem via the second NSSMF; Wherein, the response message is a slice capability deployment request confirmation message, and is returned by the CSMF to the application server.

41. The method according to claim 34, characterized in that, If the network entity is the CSMF, NSMF or NSSMF in the network slice management system, perform a subscription operation on the network slice capability of the mobile communication network according to the specified area information, including: Perform a subscription process for the slice capability update notification service within the specified area for the application server according to the specified area information; When the subscription process is successful and the network slice capability information of the mobile communication network changes within the specified area, return a slice capability change notification message to the application server, and the notification message includes the slice capability update information of the mobile communication network within the specified area.

42. An application server, characterized in that, Including: A memory and a processor; The memory is used to store computer programs; The processor is coupled to the memory and is used to execute the computer program to: send a service request message to a network entity in the network slice management system, the service request message includes service parameters, to request the network slice management system to provide it with a target service, and the target service includes a network slice capability service; The network slice capability service refers to a service for identifying whether the mobile communication network has a network slice capability and, in the case of having a network slice capability, managing the information of the network slice capability it has; receive a response message returned by the network entity for the service request message, and the response message carries information on whether the network slice management system can successfully provide the target service for the application server.

43. A network entity, characterized in that, Including: A memory and a processor; The memory is used to store computer programs; the processor is coupled to the memory and is used to execute the computer program to: receive a service request message sent by the application server, the service request message includes service parameters, and is used to request a target service from the network slice management system; provide the target service for the application server according to the service parameters, and the target service includes a network slice capability service; The network slice capability service refers to a service that identifies whether a mobile communication network has network slice capabilities and manages information about the network slice capabilities it has when it does; and returns a response message to the application server, where the response message carries information on whether the network slice management system can successfully provide the target service to the application server.

44. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it causes the processor to implement the steps in the method according to any one of claims 1-41.

45. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instruction is executed by a processor, it causes the processor to implement the steps in the method according to any one of claims 1-41.

Images