Processing method for terminating slice replacement, device, storage medium, and program product

By including the effective conditions in the slice replacement request of AF, AMF detects and terminates the slice replacement event, solving the problem of untimely slice replacement termination in the prior art and realizing a more efficient slice replacement termination process.

WO2026237561A1PCT designated stage Publication Date: 2026-11-19ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/086310
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-15
Filing Date
2026-03-26
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

In the existing technology, the slice replacement termination request needs to be transmitted through other network elements between AF and AMF, resulting in low transmission efficiency and the problem of untimely termination of slice replacement events.

Method used

The slice replacement request sent by AF carries the slice replacement effective conditions. AMF checks whether the effective conditions are met based on the request. If they are met, the slice replacement event is terminated to avoid sending the request again.

Benefits of technology

It improves the timeliness of slice replacement events, reduces transmission latency, and ensures the efficiency of the slice replacement termination process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026086310_19112026_PF_FP_ABST
    Figure CN2026086310_19112026_PF_FP_ABST
Patent Text Reader

Abstract

A processing method for terminating slice replacement, a device, a storage medium, and a program product. The method comprises: in response to an AMF executing a slice replacement event on the basis of a target slice replacement request, and detecting that a slice replacement activation condition is not satisfied, controlling the AMF to terminate execution of the slice replacement event, wherein the target slice replacement request is sent by an application function (AF) and carries the slice replacement activation condition.
Need to check novelty before this filing date? Find Prior Art

Description

Processing methods, equipment, storage media, and program products for terminating slice replacement

[0001] Cross-reference to related applications

[0002] This application is based on and claims priority to Chinese Patent Application No. 202510630518.1, filed on May 15, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication equipment technology, and in particular to a processing method, device, storage medium, and program product for terminating slice replacement. Background Technology

[0004] With the development of wireless communication technology, wireless communication systems have the function of application function (AF) requesting slice replacement. That is, the AF can send a slice replacement request to the access and mobility management function (AMF) to execute a slice replacement event, which means that the allowed network slice of the user equipment (UE) associated with the AMF is switched from the replaced slice to the replacement slice.

[0005] In related technologies, if it is necessary to implement the AMF termination of slice replacement event, that is, to switch the UE's allowed network slice (i.e., the currently used network slice) back from the replacement slice to the replaced slice, the AF needs to send a slice replacement termination request again to request the AMF to terminate the slice replacement event. However, since the slice replacement termination request usually needs to be transmitted to the AMF through other network elements between the AF and the AMF, the transmission efficiency is not high, resulting in the problem of untimely termination of slice replacement event. Summary of the Invention

[0006] This application provides a method, apparatus, storage medium, and program product for handling termination slice replacement events.

[0007] In a first aspect, embodiments of this application provide a method for processing a termination slice replacement event, comprising: responding to an access and mobility management function (AMF) to execute a slice replacement event based on a target slice replacement request, and detecting that the slice replacement effective conditions have not been met, controlling the AMF to terminate the execution of the slice replacement event, wherein the target slice replacement request is sent by an application network element (AF) and carries the slice replacement effective conditions.

[0008] Secondly, embodiments of this application provide a method for processing a termination slice replacement event. The method is applied to the AF and includes: sending a target slice replacement request carrying slice replacement effective conditions, wherein the target slice replacement request is used to instruct the AMF to execute a slice replacement event.

[0009] Thirdly, embodiments of this application provide a communication device, including: one or more processors; a memory storing one or more programs thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement a processing method such as the termination slice replacement method of the first aspect or the second aspect.

[0010] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a processing method for terminating slice replacement as described in the first or second aspect.

[0011] Fifthly, embodiments of this application provide a computer program product, including a computer program, which, when executed by a processor, implements a processing method for terminating slice replacement, such as the first or second aspect. Attached Figure Description

[0012] Figure 1 is a schematic diagram of the processing flow of the AF request slice replacement function in related technologies;

[0013] Figure 2 is a schematic diagram of another processing flow for the AF request slice replacement function in related technologies;

[0014] Figure 3 is a flowchart illustrating an embodiment of the method for handling termination slice replacement events provided in this application;

[0015] Figure 4 is a flowchart illustrating an application example of the method for handling termination slice replacement events provided in this application;

[0016] Figure 5 is a flowchart illustrating another application example of the method for handling the termination slice replacement event provided in this application;

[0017] Figure 6 is a flowchart illustrating another application example of the method for handling the termination slice replacement event provided in this application;

[0018] Figure 7 is a flowchart illustrating another application example of the method for handling the termination slice replacement event provided in this application;

[0019] Figure 8 is another flowchart illustrating an embodiment of the method for handling termination slice replacement events provided in this application;

[0020] Figure 9 is a structural schematic diagram of an embodiment of the communication device provided in this application. Detailed Implementation

[0021] To enable those skilled in the art to better understand the technical solutions of this application, the technical solutions provided in this application will be described in detail below with reference to the accompanying drawings.

[0022] Exemplary embodiments will be described more fully below with reference to the accompanying drawings; however, the described exemplary embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will enable those skilled in the art to fully understand the scope of this application.

[0023] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application. As used herein, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of a feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded.

[0025] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0026] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in common dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this application, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined in the embodiments of this application.

[0027] Network slicing (NS) is a key technology in wireless communication systems (e.g., 5G mobile communication systems). It is a complete, instantiated logical network composed of a set of network functions, designed to more efficiently address the specific needs of vertical services (such as high-bandwidth-demanding high-definition video services and low-latency-demanding gaming services) using optimized resource allocation. Network slicing enables operators to build multiple end-to-end, virtual, isolated, and customized dedicated logical networks on a single physical network. Each logical network has different network functions, thus better adapting to the differentiated needs of various vertical services.

[0028] With the development of wireless communication technology, wireless communication systems have the function of AF requesting slice replacement. That is, AF can send a slice replacement request to request access and AMF to execute a slice replacement event, which means that the allowed network slice of the UE associated with AMF is switched from the replaced slice to the replacement slice.

[0029] In related technologies, after the AMF executes a slice replacement event, there may be a need for the AMF to terminate the slice replacement event, that is, to switch the UE's allowed network slice back from the replacement slice to the replaced slice. In this case, the AF usually needs to send a slice replacement termination request again to request the AMF to terminate the slice replacement event. For example, see the following AF request slice replacement function processing flow 1) and 2).

[0030] 1) As shown in Figure 1, the processing flow of the AF request slice replacement function when the UE is online can include the following steps.

[0031] Step S101: The UE initiates a network registration request, requesting to register with the network. After receiving the UE's network registration request, the Radio Access Network (RAN) selects an AMF for the UE and forwards the UE registration request to the AMF.

[0032] Step S102: The AMF selects a PCF for the UE and sends an AM policy connection creation request to that PCF.

[0033] In step S103, the PCF makes a policy decision and sends an AM policy connection creation response message to the AMF, which carries the policy decision made by the PCF.

[0034] Step S104: The AMF sends a registration acceptance message to the UE, and the UE successfully registers with the network.

[0035] Step S105: When a network slice needs to be replaced, the trusted AF directly sends the slice replacement request to the PCF; the slice replacement request of the untrusted AF is forwarded to the PCF after authorization by the Network Exposure Function (NEF). The slice replacement request carries the UE identifier, the slice information of the slice to be replaced (Initial S-NSSAI), and the slice information of the replacement slice (Alternative S-NSSAI).

[0036] Step S106: After receiving the slice replacement request, the PCF sends an AM policy update notification message to the AMF. This policy update notification message contains Initial S-NSSAI and Alternative S-NSSAI.

[0037] Step S107: After receiving the slice replacement request, the AMF executes the slice replacement event, including: adding the Alternative S-NSSAI to the Allowed NSSAI; deleting the initial S-NSSAI from the Allowed NSSAI and adding the initial S-NSSAI to the Rejected S-NSSAI; and initiating a UE configuration update procedure to update the Allowed NSSAI and Rejected S-NSSAI on the UE side, thereby switching the UE's allowed network slice from the replaced slice to the replacement slice.

[0038] Step S108: When it is necessary to terminate the slice replacement event, the AF directly sends a request to the PCF or sends a slice replacement termination request to the PCF through the NEF. The slice replacement termination request carries a slice replacement termination indication.

[0039] Step S109: After receiving the slice replacement termination request, the PCF sends an AM policy update notification message to the AMF, which carries a slice replacement termination indication.

[0040] Step S110: After receiving the slice replacement termination instruction, the AMF terminates the slice replacement event, including: adding the initial S-NSSAI to the Allowed NSSAI and deleting the initial S-NSSAI from the Rejected S-NSSAI; and the AMF initiates a UE configuration update procedure to update the Allowed NSSAI and Rejected S-NSSAI on the UE side, thereby switching the UE's allowed network slice back from the replacement slice to the replaced slice.

[0041] 2) As shown in Figure 2, the processing flow for the AF request slice replacement function when the UE is offline can include the following steps.

[0042] In step S201, the slice replacement request from the AF is stored in the Unified Data Repository (UDR) after being authorized by the NEF. The slice replacement request carries the UE identifier and slice replacement information (initial S-NSSAI and Alternative S-NSSAI). Alternatively, the AF may send the slice replacement request in step S208, in which case step S201 is not executed.

[0043] Step S202: The UE initiates a network registration request to register with the network. After receiving the UE's registration request, the RAN selects an AMF for the UE and forwards the network registration request to the AMF.

[0044] Step S203: The AMF selects a PCF for the UE and sends an AM policy connection creation request to that PCF.

[0045] Step S204: In response to the policy connection creation request, the PCF performs a UDR data query. The UDR data includes policy subscription data, information carried by the slice replacement request, etc.

[0046] Step S205: PCF subscribes to UDR data. Subsequently, once the UDR data is updated, the UDR can report the updated data to PCF.

[0047] In step S206, the PCF makes a policy decision based on the information provided by the AMF, the data obtained from the UDR, and local policies, and sends an AM policy connection creation response message to the AMF. If the AF sends a slice replacement request in step 201 above, the policy connection creation response message carries slice replacement information (initial S-NSSAI and Alternative S-NSSAI).

[0048] Step S207: The AMF sends a registration acceptance message to the UE. The UE successfully registers with the network and then proceeds to step S211.

[0049] In step S208, the slice replacement request from the AF is stored in the UDR after being authorized by the NEF. The slice replacement request carries the UE identifier and slice replacement information (initial S-NSSAI and Alternative S-NSSAI).

[0050] Step S209: UDR sends a data update notification message to PCF, which contains slice replacement information (initial S-NSSAI and Alternative S-NSSAI) for the slice replacement request.

[0051] In step S210, after receiving the slice replacement information from the slice replacement request, the PCF sends an AM policy update message to the AMF. The policy update message contains slice replacement information (initial S-NSSAI and Alternative S-NSSAI).

[0052] Step S211: After receiving the slice replacement information, the AMF executes the slice replacement event, including: adding the Alternative S-NSSAI to the Allowed NSSAI; deleting the initial S-NSSAI from the Allowed NSSAI and adding the initial S-NSSAI to the Rejected S-NSSAI; and initiating a UE configuration update procedure to update the Allowed NSSAI and Rejected S-NSSAI on the UE side.

[0053] Step S212: When it is necessary to terminate the slice replacement event, the slice replacement termination request of AF is stored in UDR after being authorized by NEF. The slice replacement termination request carries a slice replacement termination indication.

[0054] Step S213: UDR sends a data update notification message to PCF again, which includes a slice replacement termination request.

[0055] Step S214: After receiving the slice replacement termination request, the PCF sends an AM policy update notification message to the AMF, which carries a slice replacement termination indication.

[0056] Step S215: After receiving the slice replacement termination instruction, the AMF terminates the slice replacement event, including: adding the initial S-NSSAI to the Allowed NSSAI and deleting the initial S-NSSAI from the Rejected S-NSSAI; and the AMF initiates a UE configuration update procedure to update the Allowed NSSAI and Rejected S-NSSAI on the UE side, thereby switching the UE's allowed network slice back from the replacement slice to the replaced slice.

[0057] As can be seen from the above processing flow 1) and 2), the slice replacement termination request usually needs to be transmitted to the AMF through other network elements (such as NEF and PCF) between AF and AMF. The transmission efficiency is not high, which leads to the problem of untimely slice replacement termination.

[0058] To address the aforementioned problems in the related technologies, embodiments of this application propose a processing method, apparatus, storage medium, and program product for terminating slice replacement.

[0059] Please refer to Figure 3, which is a flowchart illustrating the method for terminating slice replacement provided in this embodiment of the application. This method can be applied to a first network element. As shown in Figure 3, the method for terminating slice replacement includes the following steps:

[0060] Step S301: In response to the AMF executing a slice replacement event based on the target slice replacement request, and detecting that the slice replacement effective conditions have not been met, control the AMF to terminate the execution of the slice replacement event.

[0061] The target slice replacement request is sent by the application network element (AF) and carries the conditions for slice replacement to take effect.

[0062] In this embodiment, by including a slice replacement activation condition in the target slice replacement request sent by the AF, when the AMF executes a slice replacement event based on the target slice replacement request, the first network element can detect whether the slice replacement activation condition has been met based on the target slice replacement request. If the slice replacement activation condition is detected to have been met, the first network element controls the AMF to terminate the slice replacement event. Thus, when the AMF needs to terminate the slice replacement event, the AF does not need to send a request again; instead, the AMF terminates the slice replacement event through the slice replacement activation condition in the slice replacement request, making the termination of the slice replacement event more timely.

[0063] In step S301 above, the target slice replacement request can be a request initiated by the AF and used to instruct the AMF to execute the slice replacement event. The target slice replacement request may include slice replacement information and the slice replacement activation conditions. The slice replacement information includes the slice information of the replacement slice and the slice information of the slice being replaced.

[0064] In some implementations, the target slice replacement request may include a first slice replacement request, which is a slice replacement request sent by the AF to the PCF associated with the AMF, and the slice replacement event is an event executed in response to the PCF receiving the first slice replacement request; or, the target slice replacement request may include a second slice replacement request, which is a slice replacement request sent by the AF to the Unified Data Store (UDR), and the slice replacement event is an event executed in response to the PCF obtaining target UDR data from the UDR, and the target UDR data is UDR data generated by the UDR based on the second slice replacement request.

[0065] In this embodiment, the aforementioned target slice replacement request may include a slice replacement request sent by the AF to the PCF or UDR, thereby improving the timeliness of the termination of the slice replacement event in the scenario where the AF sends a slice replacement request to the PCF or UDR.

[0066] The first slice replacement request is a slice replacement request sent by the AF to the PCF associated with the AMF. It can be that if the AF is an untrusted AF of the PCF, the first slice replacement request is a slice replacement request sent by the untrusted AF to the NEF. In this case, the NEF authorizes the first slice replacement request and forwards it to the PCF. Alternatively, if the AF is a trusted AF of the PCF, the first slice replacement request is a slice replacement request sent directly by the trusted AF to the PCF.

[0067] If the target slice replacement request includes the second slice replacement request, the UDR generates target UDR data including the second slice replacement request; the PCF obtains the UDR data from the UDR, and then obtains the second slice replacement request.

[0068] The aforementioned second slice replacement request is a slice replacement request sent by the AF to the UDR. In some embodiments, the second slice replacement request includes any one of the following: a slice replacement request sent before the UE initiates a network registration request; or a slice replacement request sent after the UE completes network registration.

[0069] In this embodiment, the second slice replacement request can be sent before the UE initiates the network registration request or after the UE completes the network registration, thus making it more flexible for the AF to send the slice replacement request to the UDR.

[0070] The aforementioned AMF executes a slice replacement event based on a target slice replacement request. This can be achieved by the PCF receiving a target slice replacement request (e.g., receiving the first slice replacement request or the second slice replacement request mentioned above) and generating a policy update notification in response to the target slice replacement request, sending the policy update notification to the AMF. The policy update notification carries the slice replacement information from the target slice replacement request. In response to the policy update notification, the AMF executes a slice replacement event based on the slice replacement information to switch the UE's allowed network slice from the replaced slice to the replacement slice.

[0071] In step S301 above, the AMF executes the slice replacement event based on the target slice replacement information. This can be because the AMF can directly execute the slice replacement event based on the slice replacement information in the slice replacement request. In other words, the AMF's execution of the slice replacement event is unrelated to the slice replacement effective conditions.

[0072] Alternatively, in some implementations, the slice replacement event is an event executed in response to the target UDR data detecting that the slice replacement activation condition has been met. That is, in the scenario where the AF sends a second slice replacement request to the UDR, the AMF only executes the slice replacement event based on the slice replacement information if the slice replacement activation condition has been met; otherwise, it does not execute the slice replacement event. In this way, it can be avoided that when the UE is offline, the AF sends a second slice replacement request to the UDR without knowing the UE's information, resulting in the second slice replacement request being no longer needed when the UE limit is reached.

[0073] In step S301 above, when the AMF executes the slice replacement event, the first network element can detect whether the slice replacement effective condition carried in the target slice replacement request has been met. If the first network element determines that the slice replacement effective condition has been met, it controls the AMF to terminate the execution of the slice replacement event so as to switch the UE's allowed network slice from the replacement slice back to the replaced slice.

[0074] The above-mentioned conditions for slice replacement to take effect can be any conditions that can determine whether there is an event that requires AMF to terminate the slice replacement.

[0075] In some implementations, the above-mentioned slice replacement effective conditions may include at least one of the following: whether the duration of the slice replacement event is less than or equal to a preset slice replacement duration; whether the UE associated with the AMF is located in a preset slice replacement effective area; and whether the current time is within a preset slice replacement time period.

[0076] In this embodiment, the above-mentioned slice replacement effective conditions can enable the first network element to flexibly determine the need to terminate the slice replacement event.

[0077] If the duration of the slice replacement event is less than or equal to the preset slice replacement duration, and the duration of the slice replacement event is greater than the preset slice replacement duration, then the first network element determines that the slice replacement effective condition has not been met; otherwise, the slice replacement effective condition has been met.

[0078] If the above-mentioned slice replacement activation conditions include whether the UE associated with the AMF is located in the preset slice replacement activation area, then if the UE is not located in the preset slice replacement activation area, the first network element determines that the slice replacement activation conditions have not been met; otherwise, the slice replacement activation conditions have been met.

[0079] If the current time is not within the preset slice replacement time period, the first network element determines that the slice replacement effective condition has not been met; otherwise, the slice replacement effective condition has been met.

[0080] In step S301 above, the first network element can be a network element configured between the AF and the UE in a wireless communication system. In some embodiments, the first network element can be a PCF, that is, the above-mentioned method for terminating slice replacement is applied to the PCF; or, the first network element can also be an AMF, that is, the above-mentioned method for terminating slice replacement is applied to the AMF.

[0081] In some implementations, when the above-described method for terminating slice replacement is applied to an AMF, the method may further include: receiving a slice replacement effective condition sent by a PCF associated with the AMF in response to a target slice replacement request; and controlling the AMF to terminate the slice replacement event, including: terminating the slice replacement event.

[0082] In this embodiment, the AMF can receive the slice replacement effective condition sent by the PCF, detect whether the slice replacement effective condition has been met, and terminate the slice replacement event if the slice replacement effective condition is detected to have been met, thereby enabling the AMF to actively terminate the slice replacement event.

[0083] The aforementioned AMF receiving the slice replacement effective conditions sent by the PCF in response to the target slice replacement request can be achieved by the PCF sending a message carrying the slice replacement effective conditions in the target slice replacement request to the AMF after the AF sends the target slice replacement request, and the AMF obtaining the slice replacement effective conditions from the message.

[0084] In some embodiments, when the PCF receives the first slice replacement request, the PCF responds to the first slice replacement request by generating a policy update notification corresponding to the first slice replacement request. The policy update notification carries the slice replacement activation conditions and slice replacement information in the first slice replacement request. The PCF sends the policy update notification corresponding to the first slice replacement request to the AMF. The AMF receives the slice replacement activation conditions and slice replacement information sent by the PCF in response to the target slice replacement request, which is associated with the receiving AMF.

[0085] In some implementations, the target slice replacement request includes a second slice replacement request sent before the UE initiates a network registration request, and receiving the slice replacement activation condition sent by the PCF associated with the AMF in response to the target slice replacement request includes: receiving a policy connection creation response message carrying the slice replacement activation condition in the second slice replacement request, wherein the policy connection creation response message is a message sent by the PCF associated with the AMF in response to the queried target UDR data.

[0086] In this embodiment, if the AF sends a second slice replacement request to the UDR before the UE initiates a network registration request, the AMF can obtain the above-mentioned slice replacement effective conditions through the policy connection creation response message sent by the PCF in response to the target UDR data queried from the UDR, thereby enabling the AMF to actively terminate the slice replacement event when the UE is offline.

[0087] The above-mentioned processing procedure may involve the AF sending a second slice replacement request to the UDR before the UE sends a network registration request, carrying slice replacement activation conditions and slice replacement information; the UDR generating and storing target UDR data based on the second slice replacement request; subsequently, when the UE sends a network registration request to the AF, the AMF responds to the network registration request by sending a policy connection creation request to the PCF; the PCF responds to the AM policy connection creation request by querying the target UDR data in the UDR; the PCF sends a policy connection creation response message to the AMF based on the target UDR data, the policy connection creation response message carrying slice replacement activation conditions and slice replacement information; and the AMF receiving the policy connection creation response message sent by the PCF.

[0088] It should be noted that after receiving the aforementioned policy creation response message, the AMF can send a registration acceptance message to the UE in response to the policy connection creation response message, so that the UE can complete network registration; after the UE completes network registration, the AMF executes a slice replacement event based on the slice replacement information; and after the AMF executes the slice replacement event, the AMF checks whether the slice replacement effective condition has been met. If the AMF detects that the slice replacement effective condition has been met, the AMF terminates the execution of the slice replacement event.

[0089] After receiving the aforementioned policy creation response message, the AMF executes a slice replacement event based on the slice replacement information. This can be achieved by the AMF detecting whether the slice replacement activation conditions have been met. If the slice replacement activation conditions are met, the AMF executes the slice replacement event based on the slice replacement information. If the slice replacement activation conditions are not met, the AMF does not execute the slice replacement event based on the slice replacement information. In other words, the slice replacement event is an event executed in response to the detection that the slice replacement activation conditions have been met in the target UDR data.

[0090] In some implementations, the target slice replacement request includes a second slice replacement request sent after the UE completes network registration. Receiving the slice replacement activation condition sent by the PCF associated with the AMF in response to the target slice replacement request includes: receiving a first policy update message carrying the slice replacement activation condition in the second slice replacement request, wherein the first policy update message is a message sent by the PCF associated with the AMF in response to the second slice replacement request based on the target UDR data.

[0091] In this embodiment, when the AF sends a second slice replacement request to the UDR after the UE completes network registration, the AMF can obtain the above-mentioned slice replacement effective conditions through the PCF responding to the first policy update message sent by the target UDR data obtained from the UDR. Thus, the AMF can also actively terminate the slice replacement event when the UE is offline.

[0092] The above-mentioned processing procedure can be as follows: after the UE completes the network registration request, the AF sends a second slice replacement request to the UDR, carrying slice replacement activation conditions and slice replacement information; the UDR updates its data based on the second slice replacement request and sends a data update message carrying the updated target UDR data to the PCF; in response to the data update message, the PCF sends a first policy update message corresponding to the target UDR data to the AMF, the first policy update message carrying slice replacement activation conditions and slice replacement information; the AMF receives the first policy update message.

[0093] It should be noted that after receiving the first policy update message, the AMF can respond to the first policy update message by executing a slice replacement event based on the slice replacement information; and after the AMF executes the slice replacement event, the AMF checks whether the slice replacement effective condition has been met. If the AMF detects that the slice replacement effective condition has been met, the AMF terminates the execution of the slice replacement event.

[0094] Similarly, after the AMF receives the first policy update message, the AMF executes a slice replacement event based on the slice replacement information. This can be done by the AMF detecting whether the slice replacement activation condition has been met. If the slice replacement activation condition is met, the AMF executes the slice replacement event based on the slice replacement information. If the slice replacement activation condition is not met, the AMF does not execute the slice replacement event based on the slice replacement information. In other words, the slice replacement event is an event executed in response to the detection that the slice replacement activation condition has been met in the target UDR data.

[0095] In some implementations, when the above-described method for terminating slice replacement is applied to the PCF, controlling the AMF to terminate the slice replacement event includes: sending a second policy update message to the AMF, the second policy update message being used to instruct the AMF to terminate the slice replacement event.

[0096] In this embodiment, when the AMF executes a slice replacement event, the PCF detects whether the slice replacement activation condition it has obtained has been met. If the slice replacement activation condition is detected to be met, the PCF sends a second policy update message to the AMF to instruct the AMF to terminate the slice replacement event. This allows the PCF to actively control the AMF to terminate the slice replacement event.

[0097] The PCF obtains the slice replacement effective condition in the above-mentioned case where the target slice replacement request includes a first slice replacement request. The PCF receives the first slice replacement request directly sent by the AF or forwarded by the NEF, and the first slice replacement request carries the slice replacement effective condition.

[0098] Alternatively, the PCF may obtain the slice replacement effective conditions in the case where the target slice replacement request includes a second slice replacement request, and the PCF obtains the target UDR data from the UDR, which carries the slice replacement effective conditions.

[0099] It should be noted that the above process can specifically involve the following scenario: if the second slice replacement request is sent before the UE sends the network registration request, the AMF, in response to the network registration request, queries the target UDR data from the UDR through the PCF and sends a policy connection creation response message based on the target UDR data to obtain the slice replacement information carried in the slice replacement request. After the AMF sends a registration acceptance message to the UE in response to the policy connection creation response message (i.e., the UE completes network registration), the AMF directly executes the slice replacement event based on the slice replacement information. Alternatively, the AMF can also obtain the slice replacement activation conditions based on the policy connection creation response message. If the AMF detects that the slice replacement activation conditions have been met, it executes the slice replacement event based on the slice replacement information. In other words, the AMF decides to execute the slice replacement event itself, while the PCF decides to execute the slice replacement termination event.

[0100] In some implementations, the target slice replacement request includes a second slice replacement request sent before the UE initiates a network registration request. The method further includes: responding to the second slice replacement request based on target UDR data in response to the UE completing network registration, and sending a third policy update message to the AMF, wherein the target UDR data is the UDR data queried by the PCF in response to the network registration request, and the third policy update message is used to instruct the AMF to perform a slice replacement event.

[0101] In this embodiment, if the AF sends a second slice replacement request to the UDR before the UE initiates a network registration request, the PCF can respond by sending a third policy update message to the AMF based on the target UDR data queried from the UDR, and instruct the AMF to perform a slice replacement event through the third policy update message.

[0102] Specifically, the above process can be as follows: before the UE sends a network registration request, the AF sends a second slice replacement request to the UDR, carrying slice replacement activation conditions and slice replacement information; the UDR generates and stores target UDR data based on the second slice replacement request; subsequently, when the UE sends a network registration request to the AF, the AMF responds to the network registration request by sending a policy connection creation request to the PCF; the PCF responds to the AM policy connection creation request by querying the target UDR data in the UDR; the PCF sends a policy connection creation response message to the AMF based on the target UDR data, responding to the policy connection creation request; the AMF responds to the policy connection creation response message by sending a registration acceptance message to the UE, enabling the UE to complete network registration; after the UE completes network registration, the PCF responds to the second slice replacement request of the target UDR data by sending a third policy update message to the AMF; the AMF receives the third policy update message and executes a slice replacement event in response to the third policy update message.

[0103] In response to the second slice replacement request of the target UDR data, the PCF sends a third policy update message to the AMF. This can be done when the PCF detects that the slice replacement effective conditions have been met. In this case, the slice replacement event is an event that is executed in response to the detection that the slice replacement effective conditions have been met in the target UDR data.

[0104] After the AMF responds to the third policy update message and performs slice replacement, the PCF can detect whether the slice replacement effective conditions have been met. If the slice replacement effective conditions are not met, the PCF sends the aforementioned second policy update message to the AMF, and the AMF terminates the slice replacement event in response to the second policy update message.

[0105] In some implementations, the target slice replacement request includes a second slice replacement request sent by the UE after completing network registration. The method further includes: receiving target UDR data, which is UDR data sent by the UDR in response to the second slice replacement request to update UDR data; responding to the second slice replacement request based on the target UDR data and sending a fourth policy update message to the AMF, wherein the fourth policy update message is used to instruct the AMF to perform a slice replacement event.

[0106] In this embodiment, when the AF sends a second slice replacement request to the UDR after the UE completes network registration, the UDR can proactively send updated target UDR data to the PCF, so that the PCF responds to the second slice replacement request of the target UDR data and sends the target UDR data to the AMF, thereby instructing the AMF to perform a slice replacement event.

[0107] The above process can be as follows: after the UE completes network registration, the UDR receives a second slice replacement request sent by the AF; the UDR updates its data based on the second slice replacement request; the UDR sends the updated target UDR data to the PCF; in response to the second slice replacement request in the target UDR data, the PCF sends a fourth policy update message to the AMF; and in response to the fourth policy update message, the AMF executes a slice replacement event.

[0108] The PCF responds to the second slice replacement request based on the target UDR data and sends a fourth policy update message to the AMF. This fourth policy update message can be sent to the AMF only if the PCF detects that the slice replacement effective condition in the second slice replacement request has been met. In this case, the slice replacement event is an event that is executed in response to the target UDR data detecting that the slice replacement effective condition has been met.

[0109] After the AMF responds to the fourth policy update message and performs slice replacement, the PCF can detect whether the slice replacement effective conditions have been met. If the slice replacement effective conditions are not met, the PCF sends the aforementioned second policy update message to the AMF, and the AMF terminates the slice replacement event in response to the second policy update message.

[0110] To facilitate understanding of the above-described method for terminating slice replacement in this application, several practical application examples of the above-described method for terminating slice replacement in this application are provided below.

[0111] Example 1: AF or NEF sends a slice replacement request (i.e., target slice replacement request) to PCF, and AMF detects the slice replacement effective conditions, as shown in Figure 4, including the following steps.

[0112] Step S401: The UE initiates a network registration request, requesting to register with the network. After receiving the UE's network registration request, the RAN selects an AMF for the UE and forwards the UE registration request to the AMF.

[0113] Step S402: The AMF selects a PCF for the UE and sends an AM policy connection creation request to that PCF.

[0114] In step S403, the PCF makes a policy decision and sends an AM policy connection creation response message to the AMF. This policy connection creation response message carries the policy decision made by the PCF.

[0115] Step S404: The AMF response policy connection creation response message is sent to the UE to enable the UE to complete network registration.

[0116] Step S405: When slice replacement is required, the trusted AF will send the slice replacement request directly to the PCF; the slice replacement request from the untrusted AF will be forwarded to the PCF after authorization by the NEF. The AF request carries the UE identifier, slice replacement information (Initial S-NSSAI and Alternative S-NSSAI), and slice replacement effective conditions (such as slice replacement duration, slice replacement area, and slice replacement time period, etc., at least one of these).

[0117] Step S406: After receiving the slice replacement request, the PCF sends an AM policy update notification message to the AMF. The message contains slice replacement information and the conditions under which the slice replacement takes effect.

[0118] Step S407: After receiving the AF slice replacement request, the AMF executes the slice replacement event, including: adding the Alternative S-NSSAI to the Allowed NSSAI (if the Alternative S-NSSAI is not already in the Allowed NSSAI); the AMF removes the initial S-NSSAI from the Allowed NSSAI and adds the initial S-NSSAI to the Rejected S-NSSAI; the AMF initiates a UE configuration update procedure to update the Allowed NSSAI and Rejected S-NSSAI on the UE side.

[0119] Step S408: The AMF detects that the slice replacement activation conditions have not been met (such as the UE leaving the slice replacement activation area or not being in the slice time period), and the AMF decides to terminate the slice replacement event.

[0120] Step S409: The AMF executes the termination slice replacement event, including: the AMF adds the initial S-NSSAI to the Allowed NSSAI and removes the initial S-NSSAI from the Rejected S-NSSAI; the AMF initiates the UE configuration update process to update the Allowed NSSAI and Rejected S-NSSAI on the UE side.

[0121] Example 2: AF or NEF sends a slice replacement request (i.e., target slice replacement request) to PCF, and PCF detects the slice replacement effective conditions, as shown in Figure 5, including the following steps.

[0122] Step S501: The UE initiates a network registration request, requesting to register with the network. After receiving the UE's network registration request, the RAN selects an AMF for the UE and forwards the UE registration request to the AMF.

[0123] Step S502: The AMF selects a PCF for the UE and sends an AM policy connection creation request to that PCF.

[0124] Step S503: In response to the policy connection creation request, the PCF makes a policy decision and sends an AM policy connection creation response message to the AMF. This policy connection creation response message then distributes the policy decided by the PCF.

[0125] Step S504: The AMF responds to the policy connection creation response message by sending a registration acceptance message to the UE, so that the UE can successfully register with the network.

[0126] Step S505: When slice replacement is required, the trusted AF will send the slice replacement request directly to the PCF; the untrusted AF will forward the slice replacement request to the PCF after authorization by the NEF. The slice replacement request carries the UE identifier, slice replacement information (initial S-NSSAI and Alternative S-NSSAI), and slice replacement effective conditions (such as slice replacement duration, slice replacement area, and slice replacement time period, etc., at least one of these).

[0127] Step S506: After receiving the handover / replacement request, the PCF sends an AM policy update notification message to the AMF. The message contains slice replacement information.

[0128] Step S507: After receiving the slice replacement request information, the AMF executes the slice replacement event, including: the AMF adds the Alternative S-NSSAI to the Allowed NSSAI (if the Alternative S-NSSAI is not already in the Allowed NSSAI); the AMF removes the initial S-NSSAI from the Allowed NSSAI and adds the initial S-NSSAI to the Rejected S-NSSAI; the AMF initiates a UE configuration update procedure to update the Allowed NSSAI and Rejected S-NSSAI on the UE side.

[0129] In step S508, if the PCF detects that the handover replacement conditions have not been met (such as the UE leaving the slice replacement effective area, or not being in the slice time period, or exceeding the slice replacement duration), the PCF decides to terminate the handover replacement.

[0130] Step S509: PCF sends an AM policy update notification message to AMF, which carries a slice replacement termination indication.

[0131] Step S510: After receiving the slice replacement termination instruction, the AMF executes the slice replacement termination event, including: the AMF adds the initial S-NSSAI to the Allowed NSSAI and deletes the initial S-NSSAI from the Rejected S-NSSAI; the AMF initiates the UE configuration update procedure to update the Allowed NSSAI and Rejected S-NSSAI on the UE side.

[0132] Example 3: AF or NEF sends a slice replacement request (i.e., target slice replacement request) to PCF via UDR, and AMF detects the slice replacement effective conditions, as shown in Figure 6, including the following steps.

[0133] In step S601, the slice replacement request from the AF is stored in the UDR after being authorized by the NEF. The slice replacement request carries the UE identifier, slice replacement information (initial S-NSSAI and Alternative S-NSSAI), and slice replacement effective conditions (such as slice replacement time period, slice replacement area, etc.).

[0134] Step S601 can occur at any time. If step S601 occurs after the UE registers with the network, the UDR sends the slice replacement request information to the PCF via a data update notification message.

[0135] Step S602: The UE initiates a network registration request, requesting to register with the network. After receiving the UE's registration request, the RAN selects an AMF for the UE and forwards the UE registration request to the AMF. The RAN will also inform the AMF of the UE's location information.

[0136] Step S603: The AMF selects a PCF for the UE and sends an AM policy connection creation request to that PCF. The request also includes the UE location information obtained by the AMF from the RAN.

[0137] Step S604: PCF queries UDR data (i.e. target UDR data). UDR data includes policy signing data, slice replacement request information, etc.

[0138] Step S604: PCF subscribes to UDR data. Subsequently, once UDR data is updated, UDR can report the updated data to PCF.

[0139] In step S605, the PCF makes a policy decision based on the information provided by the AMF, the data obtained from the UDR, and local policies, and sends an AM policy connection creation response message to the AMF. The policy connection creation response message contains slice replacement information (initial S-NSSAI and Alternative S-NSSAI) for the slice replacement request.

[0140] Step S606: The AMF response policy connection creation response message is sent to the UE to enable successful UE registration.

[0141] Step S607: The AMF detects that the handover replacement conditions have been met (e.g., the UE is located in the handover replacement area, or during the handover period), and the AMF decides to execute the slice replacement event.

[0142] Step S608: The AMF executes a slice replacement event, including: the AMF adding the Alternative S-NSSAI to the Allowed NSSAI (if the Alternative S-NSSAI is not already in the Allowed NSSAI); the AMF deleting the initial S-NSSAI from the Allowed NSSAI and adding the initial S-NSSAI to the Rejected S-NSSAI; and the AMF initiating a UE configuration update procedure to update the Allowed NSSAI and Rejected S-NSSAI on the UE side.

[0143] Step S609: The AMF detects that the handover replacement conditions have not been met (such as the UE moving out of the handover replacement area or not being in the handover time period), and the AMF decides to terminate the slice replacement event.

[0144] Step S610: The AMF executes the termination slice replacement event, including: the AMF adds the initial S-NSSAI to the Allowed NSSAI and removes the initial S-NSSAI from the Rejected S-NSSAI; the AMF initiates the UE configuration update process to update the Allowed NSSAI and Rejected S-NSSAI on the UE side.

[0145] Example 4: AF or NEF sends a slice replacement request (i.e., target slice replacement request) to PCF via UDR, and PCF detects the slice replacement effective conditions, as shown in Figure 7, including the following steps.

[0146] In step S701, the slice replacement request from the AF is stored in the UDR after being authorized by the NEF. The slice replacement request carries the UE identifier, slice replacement information (initial S-NSSAI and Alternative S-NSSAI), and slice replacement effective conditions (handover time period and handover area).

[0147] Step S701 can occur at any time. If step S701 occurs after the UE registers with the network, the UDR sends the slice replacement request information to the PCF via a data update notification message.

[0148] Step S702: The UE initiates a registration request to register with the network. After receiving the UE's registration request, the RAN selects an AMF for the UE and forwards the UE's registration request to the AMF. The RAN will also inform the AMF of the UE's location information.

[0149] Step S703: The AMF selects a PCF for the UE and sends an AM policy connection creation request to that PCF. The request also includes the UE location information obtained by the AMF from the RAN.

[0150] Step S704: PCF performs UDR data query. UDR data includes policy subscription data, AF request information, etc.

[0151] In step S705, the PCF subscribes to UDR data. Subsequently, once the UDR data is updated, the UDR can report the updated data to the PCF.

[0152] In step S706, the PCF makes a policy decision based on the information provided by the AMF, the data obtained from the UDR, and local policies, and sends an AM policy connection creation response message to the AMF. If the handover replacement conditions are met (such as the UE's current location being in the handover replacement area, or the handover time period being met), the AM policy connection creation response message contains slice replacement information (initial S-NSSAI and Alternative S-NSSAI).

[0153] Step S707: In response to the policy connection creation response message, the AMF sends a registration acceptance message to the UE to ensure successful UE registration.

[0154] Step S708: If the PCF did not send slice replacement information in step S706, and the PCF detects that the handover replacement conditions have been met (such as the UE entering the handover replacement area, or during the handover period), the PCF decides to send slice replacement information for the slice replacement request.

[0155] Step S709: PCF sends an AM policy update notification message to AMF. The policy update notification message contains the slice replacement information requested by AF (initial S-NSSAI and Alternative S-NSSAI).

[0156] Step S710: After receiving the AF slice replacement request information, the AMF executes the slice replacement event, including: the AMF adds the Alternative S-NSSAI to the Allowed NSSAI (if the Alternative S-NSSAI is not already in the Allowed NSSAI); the AMF removes the initial S-NSSAI from the Allowed NSSAI and adds the initial S-NSSAI to the Rejected S-NSSAI; the AMF initiates a UE configuration update procedure to update the Allowed NSSAI and Rejected S-NSSAI on the UE side.

[0157] Step S711: The PCF detects that the handover replacement conditions have not been met (such as the UE leaving the slice replacement effective area or not being in the slice time period), and the PCF decides to terminate the handover replacement event.

[0158] Step S712: PCF sends an AM policy update notification message to AMF, which carries a slice replacement termination indication.

[0159] Step S713: After receiving the slice replacement termination instruction, the AMF executes the slice replacement termination event, including: the AMF adds the initial S-NSSAI to the Allowed NSSAI and deletes the initial S-NSSAI from the Rejected S-NSSAI; the AMF initiates the UE configuration update procedure to update the Allowed NSSAI and Rejected S-NSSAI on the UE side.

[0160] Please refer to Figure 8, which is a flowchart illustrating a method for terminating slice replacement according to an embodiment of this application. This method can be applied to AF. As shown in Figure 8, the method includes:

[0161] Step S801: Send a target slice replacement request carrying the slice replacement effective conditions. The target slice replacement request is used to instruct AMF to execute the slice replacement event.

[0162] In some implementations, the conditions for slice replacement to take effect include at least one of the following: whether the duration of the slice replacement event is less than or equal to a preset slice replacement duration; whether the UE associated with the AMF is located in a preset slice replacement effective area; and whether the current time is within a preset slice replacement time period.

[0163] In some implementations, sending a target slice replacement request carrying slice replacement activation conditions includes: sending a first slice replacement request to a PCF associated with the AMF, the target slice replacement request including the first slice replacement request, and a slice replacement event being an event executed in response to the first slice replacement request received by the PCF; or, sending a second slice replacement request to the UDR, the target slice replacement request including the second slice replacement request, and a slice replacement event being an event executed in response to target UDR data obtained by the PCF from the UDR, the target UDR data being UDR data generated by the UDR based on the second slice replacement request.

[0164] In some implementations, the second slice replacement request includes any one of the following: a slice replacement request sent before the UE initiates a network registration request; or a slice replacement request sent after the UE completes network registration.

[0165] It should be noted that the implementation methods of the termination slice replacement process shown in Figure 8 above correspond to the implementation methods of the termination slice replacement process shown in Figures 3 to 7 above. Their implementation processes and the beneficial effects they can achieve are similar, and will not be described again here.

[0166] Please refer to Figure 9, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device includes the bus routing node described above. As shown in Figure 9, the communication device 900 includes: one or more processors 910; and a memory 920 storing one or more programs. When the one or more programs are executed by the one or more processors 910, the one or more processors 910 implement the termination slice replacement processing method described in any of the above embodiments.

[0167] The memory 920, as a non-transitory network system, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, the memory 920 may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory 920 may include remotely located memories 920 relative to the processor 910, which can be connected to the processor 910 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0168] The memory 920 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 920 can store the operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 920 and is called and executed by the processor 910.

[0169] The processor 910 can be implemented using a general-purpose central processing unit (CPU), microprocessor, application specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0170] In some embodiments, the communication device further includes: an input / output interface for inputting and outputting information; a communication interface for communication interaction between the device and other devices, which can be implemented via wired means (e.g., USB, Ethernet cable, etc.) or wireless means (e.g., mobile network, WIFI, Bluetooth, etc.); and a bus for transmitting information between various components of the device (e.g., processor 910, memory 920, input / output interface, and communication interface); wherein the processor 910, memory 920, input / output interface, and communication interface can be interconnected within the device via the bus.

[0171] One embodiment of this application also provides a computer-readable storage medium storing computer-executable instructions for performing a process method for terminating slice replacement as described in any of the embodiments above.

[0172] An embodiment of this application also provides a computer program product, including a computer program or computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the computer device to perform a processing method for terminating slice replacement as described in any of the above embodiments.

[0173] The system architecture and application scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will know that as the system architecture evolves and new application scenarios emerge, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0174] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0175] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0176] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0177] The above description, with reference to the accompanying drawings, illustrates some embodiments of this application, but does not limit the scope of this application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of this application shall be within the scope of this application.

Claims

1. A method for terminating slice replacement, comprising: In response to the Access and Mobility Management Function (AMF) executing a slice replacement event based on a target slice replacement request, and detecting that the slice replacement effective conditions have not been met, the AMF is controlled to terminate the execution of the slice replacement event. The target slice replacement request is sent by the application network element (AF) and carries the slice replacement effective conditions.

2. The method of claim 1, wherein, The conditions for the slice replacement to take effect include at least one of the following: Whether the duration of the slice replacement event is less than or equal to the preset slice replacement duration; Whether the user terminal (UE) associated with the AMF is located in the preset slice replacement effective area; Is the current time within the preset slice replacement time period? 3. The method of claim 1, wherein, The target slice replacement request includes a first slice replacement request, which is a slice replacement request sent by the AF to the policy control network element (PCF) associated with the AMF. The slice replacement event is an event executed in response to the first slice replacement request received by the PCF. or, The target slice replacement request includes a second slice replacement request, which is a slice replacement request sent by the AF to the unified data storage UDR. The slice replacement event is an event executed in response to the target UDR data obtained by the PCF from the UDR. The target UDR data is UDR data generated by the UDR based on the second slice replacement request.

4. The method of claim 3, wherein, The second slice replacement request includes any of the following: A slice replacement request sent before the UE initiates a network registration request; A slice replacement request sent after the UE completes network registration.

5. The method of claim 3, wherein, The slice replacement event is an event that is executed in response to the detection of the slice replacement taking effect condition in the target UDR data.

6. The method of claim 1, wherein, The method is applied to the AMF, and the method further includes: Receive the slice replacement effective conditions sent by the PCF associated with the AMF in response to the target slice replacement request; The control of the AMF to terminate the execution of the slice replacement event includes: The slice replacement event is terminated.

7. The method of claim 6, wherein, The target slice replacement request includes a second slice replacement request sent before the UE initiates a network registration request. The condition for receiving the slice replacement activation sent by the PCF associated with the AMF in response to the target slice replacement request includes: Receive a policy connection creation response message carrying the slice replacement effective conditions described in the second slice replacement request. The policy connection creation response message is a message sent by the PCF associated with the AMF in response to the queried target UDR data.

8. The method of claim 6, wherein, The target slice replacement request includes a second slice replacement request sent after the UE completes network registration. The condition for receiving the slice replacement activation sent by the PCF associated with the AMF in response to the target slice replacement request includes: Receive the first policy update message carrying the slice replacement effective conditions in the second slice replacement request. The first policy update message is a message sent by the PCF associated with the AMF in response to the second slice replacement request based on the target UDR data.

9. The method of claim 1, wherein, The method is applied to the PCF associated with the AMF. The control of the AMF to terminate the execution of the slice replacement event includes: A second policy update message is sent to the AMF, which instructs the AMF to terminate the slice replacement event.

10. The method of claim 9, wherein, The target slice replacement request includes a second slice replacement request sent before the UE initiates a network registration request. The method further includes: In response to the UE completing network registration, the system responds to the second slice replacement request based on the target UDR data and sends a third policy update message to the AMF. The target UDR data is the UDR data that the PCF retrieves from the UDR in response to the network registration request, and the third policy update message is used to instruct the AMF to execute the slice replacement event.

11. The method of claim 9, wherein, The target slice replacement request includes a second slice replacement request sent by the UE after completing network registration, and the method further includes: Receive target UDR data, which is the UDR data sent by the UDR in response to the second slice replacement request to update the UDR data; In response to the second slice replacement request based on the target UDR data, a fourth policy update message is sent to the AMF. The fourth strategy update message is used to instruct the AMF to perform the slice replacement event.

12. A method for terminating slice replacement, applied to AF, comprising: Send a target slice replacement request carrying the slice replacement effective conditions, the target slice replacement request being used to instruct AMF to perform a slice replacement event.

13. The method of claim 12, wherein, The conditions for the slice replacement to take effect include at least one of the following: Whether the duration of the slice replacement event is less than or equal to the preset slice replacement duration; Whether the UE associated with the AMF is located in the preset slice replacement effective area; Is the current time within the preset slice replacement time period? 14. The method of claim 13, wherein, Sending the target slice replacement request carrying the slice replacement effective conditions includes: A first slice replacement request is sent to a PCF associated with the AMF, the target slice replacement request including the first slice replacement request, and the slice replacement event is an event executed in response to the first slice replacement request received by the PCF; or, A second slice replacement request is sent to the UDR, the target slice replacement request including the second slice replacement request, the slice replacement event being an event executed in response to target UDR data obtained by the PCF from the UDR, the target UDR data being UDR data generated by the UDR based on the second slice replacement request.

15. The method of claim 14, wherein, The second slice replacement request includes any of the following: A slice replacement request sent before the UE initiates a network registration request; A slice replacement request sent after the UE completes network registration.

16. A communication device, comprising: One or more processors; a memory having stored thereon one or more programs, which, when executed by the one or more processors, cause the one or more processors to perform the process of any of claims 1-15. The processing method of claim 1-15.

17. A computer readable storage medium having stored thereon a computer program, which, when executed by a processor, causes the processor to perform the process of any of claims 1-15. The processing method of claim 1-15.

18. A computer program product comprising a computer program which, when executed by a processor, causes the processor to perform the process of any of claims 1-15. ​