CN112118120A

CN112118120A - Slicing signing method, system and computer readable storage medium

Info

Publication number: CN112118120A
Application number: CN201910534382.9A
Authority: CN
Inventors: 谢沛荣; 刘桂清; 何志强; 曹磊; 王庆扬; 陈洁
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2019-06-20
Filing date: 2019-06-20
Publication date: 2020-12-22
Anticipated expiration: 2039-06-20
Also published as: CN112118120B

Abstract

The disclosure provides a slicing signing method, a slicing signing system and a computer readable storage medium, and relates to the technical field of communication. The slicing signing method comprises the following steps: the AF receives a slice signing instruction from a user and sends a slice signing request to the capability open platform; the capability open platform sends a user slice signing request to the UDM and the PCF; PCF updates URSP of user according to user slice signing request and sends updated URSP to user; the UDM updates NSSAI of the user according to the slice identifier provided by the capability open platform and sends the NSSAI to AMF serving the user currently; and the AMF generates or acquires the allowed NSSAI of the user and sends the NSSAI to the terminal. By the method, the slice can be generated for the application function in the network in advance, and the user signs the slice when needing to use the slice, so that the user can use the slice in real time, and the slice signing flexibility and signing efficiency are improved.

Description

Slicing signing method, system and computer readable storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a slicing and signing method, a slicing and signing system, and a computer-readable storage medium.

Background

The concept of network slices is introduced into the 5G system, each network slice can have different mobility, security, time delay and reliability, even different charging modes, and can better provide wide connection service for various industries.

To access a network slice, a user needs to sign the slice in UDM (Unified Data Management) in advance, and also needs to determine URSP (UE Routing Selection Policy) in PCF (Policy Control Function) in advance. The URSP includes a plurality of NSSP (Network Slice Selection Policy) rules, and each NSSP rule is a corresponding relationship between an application and a Slice. The terminal will select which slice to use for the application based on the NSSP in the URSP.

Disclosure of Invention

The inventor finds that the current network slicing mechanism needs the user to sign in advance, and cannot deal with the situation that the user suddenly accesses some services needing slicing support.

One object of the present disclosure is to improve the flexibility and efficiency of slice signup.

According to an aspect of the present disclosure, a slicing and signing method is provided, including: an AF (Application Function) sends a slice signing request to an ability open platform, wherein a network side creates a slice of the AF in advance, and the slice signing request comprises a user identifier and a slice identifier of the AF; the capability open platform sends a user slice signing request to the UDM and the PCF; PCF updates URSP of user according to user slice signing request and sends updated URSP to user; the UDM updates NSSAI (Network Slice Selection Assistance Information) of the user according to a Slice identifier provided by the capability open platform, and issues the NSSAI to an AMF (Access and Mobility Management Function) serving the user at present; and the AMF generates or acquires the allowed NSSAI of the user according to the updated signed NSSAI and sends the allowed NSSAI to the terminal.

In some embodiments, the slice signing method further comprises: after finishing the user slicing subscription, PCF and UDM feed back a slicing completion response to the capability open platform; and the capability open platform feeds back subscription completion information to the AF according to the slicing completion response.

In some embodiments, the AF receiving the slice contract instruction from the user comprises: under the condition that the user accesses the AF, the AF provides slice information for the user to select; and when the user selects to sign the slice, executing the operation of sending a slice signing request to the capacity open platform.

In some embodiments, in the case that the user identifier included in the slice subscription request is a user IP address, sending, by the capability openness platform, the user slice subscription request to the UDM and the PCF includes: the capability opening platform sends the user slice signing request to a DRA (Diameter Routing Agent, Routing Agent node), and the DRA forwards the user slice signing request to a PCF (subscriber telephony interface) of a user according to a user IP (Internet protocol) address in the user slice signing request; the PCF feeds back the SUPI (Subscription Permanent Identifier) of the user to the capability open platform; the capability openness platform queries an NRF (NF replication Function) for a UDM determined to serve a user according to SUPI.

In some embodiments, the capability openness platform sending the user slice subscription request to the UDM and the PCF further comprises: the capacity open platform sends a signing query request to a UDM (universal data management) serving a user; the UDM judges whether the user signs the section of the AF or not according to the signing inquiry request; under the condition that the user has signed the AF section, the signed information is fed back to the capability open platform; and under the condition that the user does not sign the AF slice, feeding back the non-signing information to the capability opening platform, and sending a user slice signing request to the UDM by the capability opening platform.

In some embodiments, the slice signing method further comprises: the terminal selects a used slice according to the updated URSP; determining whether the slice used is in an allowed NSSAI according to the AMF updated configuration information; in case the slice identity of the slice is successful in allowing the matching in NSSAI, the slice is used; in the event that the slice identification of a slice is successful in allowing the mismatch in NSSAI, the URSP is queried for additional slices.

By the method, the slice can be generated for the application function in the network in advance, and the user signs the slice when needing to use the slice, so that the user can use the slice in real time, and the slice signing flexibility and signing efficiency are improved.

According to an aspect of some embodiments of the present disclosure, there is provided a slicing and signing system, including: the system comprises an AF and a network side, wherein the AF is configured to send a slice signing request to an ability open platform, a network side creates a slice of the AF in advance, and the slice signing request comprises a user identifier and a slice identifier of the AF; the capability opening platform is configured to send a user slice signing request to the UDM and the PCF; PCF, configured to update URSP of user according to user slice signing request, and send updated URSP to user; the UDM is configured to update the signed NSSAI of the user according to the slice identifier provided by the capability open platform and send the updated signed NSSAI to the AMF serving the user currently; and the AMF is configured to generate or acquire the allowed NSSAI of the user according to the updated signed NSSAI and send the allowed NSSAI to the terminal.

In some embodiments, the PCF and UDM are further configured to: after the user slicing subscription is finished, feeding back slicing completion responses to the capability open platform respectively; the capability openness platform is further configured to feed back subscription completion information to the AF according to the slicing completion response.

In some embodiments, the AF is configured to: providing slice information to the user for selection by the user when the user accesses the AF; and when the user selects to sign the slice, executing the operation of sending a slice signing request to the capacity open platform.

In some embodiments, the capability openness platform is configured to, in the event that the user identification included in the slice subscription request is a user IP address: sending the user slicing subscription request to the DRA so that the DRA can forward the user slicing subscription request to the PCF of the user according to the user IP address in the user slicing subscription request; inquiring NRF according to SUPI fed back by PCF, and determining UDM serving for user; the PCF is further configured to feed back the SUPI of the user to the capability openness platform according to the user slice subscription request forwarded by the DRA.

In some embodiments, the capability openness platform is further configured to send a subscription query request to a UDM serving the user, and perform an operation of sending a user slice subscription request to the UDM after receiving non-subscription information fed back by the UDM; the UDM is also configured to judge whether the user has signed a slice of the AF after receiving the signing inquiry request; under the condition that the user has signed the AF section, the signed information is fed back to the capability open platform; and under the condition that the user does not sign the AF slice, feeding back the non-signing information to the capability open platform.

In some embodiments, the slicing signing system further comprises: a terminal configured to select a slice for use according to the updated URSP; determining whether the slice used is in an allowed NSSAI according to the AMF updated configuration information; using the slice if the slice identification of the slice allows a successful match in NSSAI; in the event that the slice identification of a slice is successful in allowing the mismatch in NSSAI, the URSP is queried for additional slices.

In accordance with an aspect of still other embodiments of the present disclosure, a slicing and contracting system is provided, in which each node includes: a memory; and a processor coupled to the memory, the processor configured to execute a method performed by a corresponding node in any of the above slicing signing methods based on instructions stored in the memory.

The slicing signing system can generate the slices for the application functions in the network in advance, and when the user needs to use the slices, the user signs the slices, so that the user can use the slices in real time, and the slicing signing flexibility and signing efficiency are improved.

According to an aspect of still further embodiments of the present disclosure, a computer-readable storage medium is proposed, on which computer program instructions are stored, which instructions, when executed by a processor, implement the steps of any of the above slicing signing methods.

By executing the instructions on the computer-readable storage medium, the slice can be generated in advance for the application function in the network, and the user signs the slice when the user needs to use the slice, so that the user can use the slice in real time, and the slice signing flexibility and signing efficiency are improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this disclosure, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure and not to limit the disclosure. In the drawings:

fig. 1 is a flow diagram of some embodiments of a slice signup method of the present disclosure.

Fig. 2 is a flow diagram of further embodiments of a slice signup method of the present disclosure.

Fig. 3 is a schematic diagram of some embodiments of a slicing sign-up system of the present disclosure.

Fig. 4 is a signaling interaction diagram of some embodiments of the slicing signup system of the present disclosure.

Fig. 5 is a schematic diagram of further embodiments of a slicing signup system of the present disclosure.

Fig. 6 is a schematic diagram of still other embodiments of slicing and signing systems of the present disclosure.

Detailed Description

The technical solution of the present disclosure is further described in detail by the accompanying drawings and examples.

A flow diagram of some embodiments of a slice signup method of the present disclosure is shown in fig. 1.

In step 101, the AF sends a slice contract request to the capability openness platform. In some embodiments, the slice subscription request includes a user identification and a slice identification of the AF. In some embodiments, the network side creates a slice of the AF, a service dedicated to the AF platform, or a certain service or certain services of the AF platform in advance, and stores a corresponding description in the AF, where the described information may include a predefined service identifier, a triplet including a target IP, a target port number, and a protocol number, and the like. The AF stores configuration Information of Slice identification, i.e., S-NSSAI (Single Network Slice Selection Assistance Information).

In some embodiments, where the user accesses the AF, the AF may provide the user with slice information for selection by the user, which may include permissions, services, and corresponding fees, among others. And when the user selects to sign the section, the AF sends a section signing request to the capability open platform.

In other embodiments, the AF may actively trigger a slice that signs up for the AF for the user in the event that the user visits the AF.

In step 102, the capability openness platform sends a user slice subscription request to the UDM and PCF. In some embodiments, the user slice subscription request may include a user identifier and a slice identifier, and may further include user IP address information and the like.

In some embodiments, step 103 and step 104, as follows, are not sequential and may be performed synchronously or asynchronously.

In step 103, the PCF updates the URSP of the user according to the user slice subscription request after receiving the user slice subscription request, and sends the updated URSP to the user. In some embodiments, the PCF generates corresponding NSSP rules, and adds the generated NSSP rules to the URSP of the subscriber to update the URSP.

In step 104, the UDM updates NSSAI of the user according to the slice identifier provided by the capability openness platform, and issues the updated NSSAI to the AMF currently serving the user.

In step 105, the AMF generates or acquires an allowed NSSAI of the user according to the updated subscribed NSSAI, and sends the generated or acquired NSSAI to the terminal to update the user profile.

A flow diagram of some embodiments of a slice signup method of the present disclosure is shown in fig. 2.

In step 201, the user accesses the AF.

In step 202, the AF provides slice information to the user for selection by the user. In some embodiments, the AF may prompt the user for a signable slice to provide better service while providing information about the slice (e.g., service area, tariff, etc.).

In step 203, the user selects a subscription slice, and triggers a slice subscription process.

In step 204, the AF sends a slice subscription request to the capability openness platform. In some embodiments, a user identifier (such as a user IP address, and in some embodiments, a user mobile phone number) and a service description (which may be a predefined service identifier or a triplet containing a target IP/target port number/protocol number) and a corresponding slice identifier may be included in the slice subscription request.

In step 205, the capability openness platform queries the UDM whether the user has signed up.

In some embodiments, if the slice subscription request includes a user mobile phone number, the capability openness platform may query the UDM determined to serve the user according to the user mobile phone number, and further query the UDM whether the user has signed a subscription.

In other embodiments, if the user identifier in the slicing subscription request is only the user IP address, the capability opening platform sends the user slicing subscription request to the DRA, and the DRA forwards the user slicing subscription request to the PCF of the user according to the user IP address in the user slicing subscription request; the PCF feeds back the SUPI of the user to the capability open platform, and then the capability open platform inquires the NRF according to the SUPI to determine the UDM serving the user, and inquires the UDM whether the user has signed a contract.

In step 206, the UDM determines the slices that the user has signed up for AF. In some embodiments, the UDM may determine whether the user has signed up for the slice of the AF according to whether a correspondence relationship between the user identifier and the slice identifier of the AF is prestored. If the user is determined to have signed a contract, go to step 207; if it is determined that the user is not signed up, step 208 is performed.

In step 207, the UDM feeds back the signed up information to the capability openness platform. In some embodiments, the capability openness platform may further feed back the signed information of the user to the AF, and the AF prompts that the user has signed a subscription, and the service may be received without repeated signing, and the signing process is ended.

In step 208, the capability openness platform sends a user slice subscription request to the UDM and PCF.

In step 209, the PCF adds the NSSP rule corresponding to the new subscription slice to the URSP of the user according to the user slice subscription request, updates the URSP of the user, and sends the updated URSP to the user.

In step 210, the PCF feeds back a slice complete response to the capability openness platform after completing the user slice subscription.

In step 211, the UDM updates the NSSAI of the user according to the slice identifier provided by the capability openness platform, for example, adds the S-NSSAI in the request to the subscribed NSSAI of the user and sends the S-NSSAI to the AMF currently serving the user.

In step 212, the UDM feeds back a slice complete response to the capability openness platform after completing the user slice subscription.

In some embodiments, the operations of the UDM sending information to the AMF and feeding back the slice completion information to the capability openness platform are not in tandem and can be performed synchronously or asynchronously.

In step 213, the AMF generates or obtains a new Allowed NSSAI (Allowed NSSAI) for the user based on the information received from the UDM. The AMF may generate the allowed NSSAI by itself, or may generate the allowed NSSAI by an NSSF (Network Slice Selection Function) and send the allowed NSSAI to the AMF. And the AMF initiates a configuration updating process after obtaining the new allowed NSSAI and transmits the new allowed NSSAI of the user to the terminal.

And after receiving the new URSP, the terminal stores and applies the new URSP, and can access the specific service into the newly signed slice for transmission according to the new URSP.

By the method, the slice signing process can be simplified, the user does not need to sign in advance, but automatically signs the application slices when accessing the application, the flexibility and efficiency of signing are improved, and the user friendliness is improved.

A schematic diagram of some embodiments of the slicing signup system of the present disclosure is shown in fig. 3.

The AF 301 can send a slice contract request to the capability openness platform. In some embodiments, slices of AF may be created in advance on the network side, with the AF storing slice identifications, such as S-NSSAI. And the AF sends the user identification of the user needing to be bound and the slice identification of the AF to the capability open platform in the slice signing request. In some embodiments, the sending of the slice subscription request may be triggered actively by the AF upon discovering user access, or may be triggered by user selection.

The capability openness platform 302 can send a user slice subscription request to the UDM and PCF after receiving the slice subscription request from the AF. In some embodiments, the user slice subscription request may include a user identifier and a slice identifier, and may further include user IP address information and the like.

PCF 303 may update the terminal routing policy URSP of the user according to the user slice subscription request after receiving the user slice subscription request, and send the updated URSP to the user.

The UDM 304 can update the subscription NSSAI of the user according to the slice identifier provided by the capability openness platform after receiving the user slice subscription request, and issue the updated subscription NSSAI to the AMF currently serving the user. The AMF 305 can generate or obtain the allowed NSSAI of the user according to the updated contracted NSSAI, and send it to the terminal to update the user profile.

In some embodiments, the UDM and PCF feedback a slice complete response to the capability openness platform after completing the operation performed by themselves. And the capability open platform feeds back subscription completion information to the AF according to the slice completion response, and the AF can prompt the user that the subscription is completed so that the user can determine the slice which can use the AF and further initiate the application.

In some embodiments, the capability openness platform 302 may determine UDMs and PCFs serving a user based on a user identification. In some embodiments, if the slice subscription request includes a user mobile phone number, the capability openness platform may query the UDM determined to serve the user according to the user mobile phone number. In other embodiments, if the slice subscription request only includes the user IP address, the user slice subscription request is sent to the DRA, the DRA forwards the user slice subscription request to the PCF of the user according to the user IP address in the user slice subscription request, the PCF feeds back the SUPI of the user to the capability openness platform, and the capability openness platform queries the NRF for the UDM determined to be a user service according to the SUPI.

The system can search the UDM and the PCF which provide services for the user under the condition that different information amounts are provided in the user identification, and further update the user subscription information, so that the user can use the slicing function of new subscription, the existing user access operation is not influenced, and the user experience is improved.

In some embodiments, to avoid the additional burden on the network node due to repeated and unnecessary subscriptions, the capability openness platform may send a subscription query request to the UDM before sending a user slice subscription request to the UDM. The UDM can judge whether the user has signed the AF section or not after receiving the signing inquiry request; under the condition that the user has signed the AF section, the signed information is fed back to the capability open platform; and under the condition that the user does not sign the AF slice, feeding back the non-signing information to the capability open platform. And the capacity open platform executes the operation of sending a user slice signing request to the UDM after receiving the non-signing information fed back by the UDM, and sends the signed information to the AF under the condition of receiving the signed information so that the AF can feed back the signed information to the user.

In some embodiments, as shown in fig. 3, the slice subscription system may further include a terminal 306 capable of selecting a slice to use according to the updated URSP after obtaining the URSP from the PCF, and determining whether the slice to use is in the allowed NSSAI according to the updated configuration information of the AMF. If the slice identifier of the slice is successfully matched in the NSSAI, using the slice; if the slice identification of the slice is not successfully matched in the NSSAI allowed, the URSP is queried for additional slices.

In the slicing subscription system, the terminal can use the slices according to the updated subscription configuration information, so that a user can use the slices in real time, and the user experience is improved.

A signaling interaction diagram of some embodiments of the slicing subscription system of the present disclosure is shown in fig. 4.

In 401, a network side node (including AMF, UDM and PCF) creates a slice for AF.

In 402, the correspondence between the service and the newly created slice is configured in the AF.

In 403, the user accesses the network through 5G and accesses the AF.

At 404, the AF triggers a subscription for the user. This trigger may be an AF auto-trigger or a user selection trigger at the application server.

In 405, the AF sends a slice subscription request to the capability openness platform, where the slice subscription request carries a mobile phone number of the user, a terminal IP address, triple information of the application (target IP/target port number/protocol number) and an S-NSSAI of the AF slice.

In 406, the capability openness platform searches for the UDM according to the received mobile phone number of the user, and if the UDM checks that the user has not signed a requested slice, the UDM feeds back the slice to the capability openness platform, and obtains a user slice signing request from the capability openness platform.

In 407, the UDM adds a new subscription slice for the specified user, including adding the new S-NSSAI received from the capability openness platform to the subscription NSSAI of the specified user.

In 408, PCF updates the URSP, i.e. PCF generates new NSSP rules based on the service description and S-NSSAI received from the capability openness platform and inserts them into the URSP of the specified subscriber.

In 409, the capability openness platform notifies the AF user that the slice subscription is successful.

In 410, the UDM informs the AMF of the information that the user slice has signed up for updates.

At 411, the AMF generates a new allowed NSSAI for the user after receiving the updated slice subscription information.

At 412, the AMF initiates a user profile update procedure by which the terminal is informed of the new NSSAI allowed.

In 413, the PCF initiates a configuration update procedure, through which the new URSP is delivered to the terminal.

In 414, the terminal stores the received new URSP and immediately executes the routing policy as per the new URSP.

In 415, the terminal accesses the new slice access AF according to the new URSP.

The slicing signing system can automatically sign the AF corresponding slices for the user when the user accesses the service, thereby greatly simplifying the signing work of the slices and improving the user experience of the slicing signing efficiency.

A schematic structural diagram of an embodiment of the slicing and signing system of the present disclosure is shown in fig. 5. The slicing signing system includes a memory 501 and a processor 502. Wherein: the memory 501 may be a magnetic disk, flash memory, or any other non-volatile storage medium. The memory is for storing instructions in the corresponding embodiments of the slice signing method above. The processor 502 is coupled to the memory 501 and may be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. The processor 502 is configured to execute instructions stored in a memory, and can improve flexibility and signing efficiency of slicing and signing.

In one embodiment, as also shown in fig. 6, the slicing signing system 600 includes a memory 601 and a processor 602. The processor 602 is coupled to the memory 601 by a BUS 603. The slicing signing system 600 may also be connected to an external storage 605 via a storage interface 604 for invoking external data, and may also be connected to a network or another computer system (not shown) via a network interface 606. And will not be described in detail herein.

In this embodiment, the data instructions are stored in the memory, and the processor processes the data instructions, so that the slice signing flexibility and the signing efficiency can be improved.

In another embodiment, a computer-readable storage medium has stored thereon computer program instructions which, when executed by a processor, implement the steps of the method in the corresponding embodiment of the slice subscription method. As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, apparatus, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Thus far, the present disclosure has been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.

The methods and apparatus of the present disclosure may be implemented in a number of ways. For example, the methods and apparatus of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

Finally, it should be noted that: the above examples are intended only to illustrate the technical solutions of the present disclosure and not to limit them; although the present disclosure has been described in detail with reference to preferred embodiments, those of ordinary skill in the art will understand that: modifications to the specific embodiments of the disclosure or equivalent substitutions for parts of the technical features may still be made; all such modifications are intended to be included within the scope of the claims of this disclosure without departing from the spirit thereof.

Claims

1. A slice signing method comprising:

an Application Function (AF) sends a slice signing request to an ability open platform, wherein a network side creates a slice of the AF in advance, and the slice signing request comprises a user identifier and a slice identifier of the AF;

the capacity open platform sends a user slice signing request to a Unified Data Management (UDM) and a Policy Control Function (PCF);

the PCF updates a terminal routing strategy URSP of the user according to the user slice signing request and sends the updated URSP to the user;

the UDM updates the subscription network slice selection auxiliary information NSSAI of the user according to the slice identification provided by the capability open platform, and issues the subscription network slice selection auxiliary information NSSAI to an access and mobility management function AMF currently serving the user;

and the AMF generates or acquires the allowed NSSAI of the user according to the updated signed NSSAI and sends the allowed NSSAI to the terminal.

2. The method of claim 1, further comprising:

after finishing user slicing subscription, the PCF and the UDM feed back a slicing completion response to the capability open platform;

and the capability open platform feeds back subscription completion information to the AF according to the slice completion response.

3. The method of claim 1, wherein the AF receiving a slice contract instruction from a user comprises:

in the case that a user accesses the AF, the AF provides slice information to the user for selection by the user;

and when the user selects to sign the slice, executing the operation of sending a slice signing request to the capacity open platform.

4. The method of claim 1, wherein in the case that the user identifier included in the slice subscription request is a user IP address, the capability openness platform sending a user slice subscription request to the UDM and the PCF comprises:

the capability open platform sends the user slice signing request to a routing agent node DRA, and the DRA forwards the user slice signing request to a PCF (subscriber directory access control) of a user according to a user IP (Internet protocol) address in the user slice signing request;

the PCF feeds back a user permanent identity (SUPI) of a user to the capability open platform;

and the capability open platform inquires the UDM which is determined to serve the user to a network function storage function (NRF) according to the SUPI.

5. The method of claim 1 or 4, wherein the capability openness platform sending a user slice subscription request to the UDM and the PCF further comprises:

the capability open platform sends a signing query request to the UDM serving the user;

the UDM judges whether the user signs the section of the AF or not according to the signing inquiry request;

under the condition that the user has signed the AF slice, feeding back signed information to the capability open platform;

and under the condition that the user does not sign the AF slice, feeding back non-signing information to the capability open platform, and sending the user slice signing request to the UDM by the capability open platform.

6. The method of claim 1, further comprising:

the terminal selects a used slice according to the updated URSP;

determining whether the used slice is in the allowed NSSAI according to the AMF updated configuration information;

using a slice if the slice identification of the slice succeeds in the allowed NSSAI;

in the event that the slice identification of the slice is not successfully matched in the allowed NSSAI, querying the URSP for additional slices.

7. A slicing signing system comprising:

the system comprises an Application Function (AF) and a capability opening platform, wherein the Application Function (AF) is configured to send a slice signing request to the capability opening platform, a slice of the AF is created in advance on a network side, and the slice signing request comprises a user identifier and a slice identifier of the AF;

the capability opening platform is configured to send a user slice signing request to the unified data management UDM and the policy control function PCF;

the PCF is configured to update a terminal routing policy (URSP) of the user according to the user slice subscription request and send the updated URSP to the user;

the UDM is configured to update the signed network slice selection auxiliary information NSSAI of the user according to the slice identification provided by the capability open platform, and issues the updated signed network slice selection auxiliary information NSSAI to an access and mobility management function AMF serving the user at present;

and the AMF is configured to generate or acquire the allowed NSSAI of the user according to the updated signed NSSAI and send the allowed NSSAI to the terminal.

8. The system of claim 7, wherein,

the PCF and the UDM are further configured to: after the user slicing subscription is finished, feeding back slicing completion responses to the capability open platform respectively;

the capability openness platform is further configured to feed back subscription completion information to the AF according to the slice completion response.

9. The system of claim 7, wherein the AF is configured to:

providing slice information to a user for selection by the user when the user accesses the AF;

10. The system of claim 7, wherein,

the capability openness platform is configured to, in a case where the user identifier included in the slice subscription request is a user IP address:

sending the user slice subscription request to a routing agent node DRA, so that the DRA forwards the user slice subscription request to a PCF (subscriber directory access point) of a user according to a user IP (Internet protocol) address in the user slice subscription request; inquiring a network function storage function (NRF) according to the SUPI fed back by the PCF to determine the UDM serving the user;

the PCF is also configured to feed back a user permanent identity (SUPI) of the user to the capability open platform according to the user slice signing request forwarded by the DRA.

11. The system of claim 7 or 10,

the capability open platform is further configured to send a signing query request to the UDM serving a user, and after receiving non-signing information fed back by the UDM, the capability open platform executes an operation of sending the user slice signing request to the UDM; the UDM is further configured to determine whether a user has signed a slice of the AF after receiving the signing inquiry request;

and under the condition that the user does not sign the AF slice, feeding back non-signing information to the capability open platform.

12. The system of claim 7, further comprising:

a terminal configured to select a slice to use according to the updated URSP; determining whether the used slice is in the allowed NSSAI according to the AMF updated configuration information; using a slice if the slice identification of the slice succeeds in the allowed NSSAI; in the event that the slice identification of the slice is not successfully matched in the allowed NSSAI, querying the URSP for additional slices.

13. A slicing signup system, wherein each node comprises:

a memory; and

a processor coupled to the memory, the processor configured to perform the method of the corresponding node as recited in any of claims 1 to 6 based on instructions stored in the memory.

14. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 6.