Communication method and apparatus

By acquiring and updating S-NSSAI, the problem of access frequency band and mobility management strategy updates of terminal devices during network slice replacement is solved, and the rapid adaptation of terminal devices and service stability is achieved.

WO2024234885A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/087093
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-04-10
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

When the network slices accessed by terminal devices are replaced, it is difficult for the prior art to update the corresponding access frequency band and mobility management strategies in a timely manner, resulting in service interruption or inefficiency.

Method used

The S-NSSAI is obtained through the first policy control network element, and the access and mobility management policies are updated to ensure that the terminal device can adapt to new network conditions in a timely manner after network slice replacement, including receiving indication information from the binding support network element and from the second The second policy controls the network element to obtain S-NSSAI or obtain replacement event notifications through subscription information to realize automatic policy updates.

Benefits of technology

It realizes the rapid adaptation of terminal devices during network slicing replacement, ensures access to appropriate frequency bands and update strategies, improves service stability and efficiency, and avoids service interruptions caused by failure to update policies in time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024087093_21112024_PF_FP_ABST
    Figure CN2024087093_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A communication method and apparatus. The method comprises: a first policy control network element acquires a first S-NSSAI, wherein the first policy control network element serves a terminal device, and the first S-NSSAI is used for identifying a network slice where a session of the terminal device is located after network slice replacement; and the first policy control network element updates an access and mobility management (AM) policy and / or a terminal device policy according to the first S-NSSAI. By using the method, under the condition that the network slice where the session of the terminal device is located is replaced, the first policy control network element can obtain an S-NSSAI corresponding to a network slice after replacement in time, namely the first S-NSSAI, and then update an AM policy or a UE policy according to the first S-NSSAI.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on May 12, 2023, with application number 202310541478.4 and invention name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] A network slice is a virtual network created on a single hardware infrastructure using network slicing technology. Each network has different network functions to meet the needs of different services. Different network slices may require different frequency bands.

[0005] Therefore, when the network slice accessed by the terminal device is replaced, the corresponding access frequency band, that is, the access and mobility management (AM) strategy, needs to be updated in a timely manner.

[0006] Summary of the Invention

[0007] The present application provides a communication method and apparatus for timely updating of AM policies.

[0008] In a first aspect, the present application provides a communication method, which includes: a first policy control network element obtains a first S-NSSAI, wherein the first policy control network element serves a terminal device, and the first S-NSSAI is used to identify the network slice where the session of the terminal device is located after the network slice is replaced; the first policy control network element updates the access and mobility management policy and / or terminal device policy according to the first S-NSSAI.

[0009] In one possible design, when the first policy control network element obtains the first S-NSSAI, the first policy control network element receives first indication information from the binding support network element, where the first indication information is used to determine the first S-NSSAI.

[0010] In one possible design, the first indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0011] In one possible design, the first indication information indicates that the policy control network element corresponding to the first S-NSSAI is registered with the binding support network element.

[0012] In one possible design, the first indication information includes the first S-NSSAI and a second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0013] In one possible design, the first indication information includes the first S-NSSAI but does not include a second S-NSSAI, where the second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI and is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0014] In one possible design, when the first policy control network element obtains the first S-NSSAI, the first policy control network element obtains the first S-NSSAI from the second policy control network element.

[0015] In a possible design, before the first policy control network element obtains the first S-NSSAI from the second policy control network element, the first policy control network element sends first subscription information to the second policy control network element, where the first subscription information is used to subscribe to a network slice replacement event for the session of the terminal device; the second policy control network element serves the session of the terminal device; when the first policy control network element obtains the first S-NSSAI from the second policy control network element, the first policy control network element receives first notification information for the first subscription information from the second policy control network element; the first policy control network element determines the first S-NSSAI based on the first notification information.

[0016] In one possible design, the network slice replacement event includes that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI; wherein the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI; the first notification information indicates that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI.

[0017] In one possible design, the network slice replacement event indicates that the network slice where the session of the terminal device is located is replaced; the first notification information indicates that the network slice where the session of the terminal device is located is replaced, and the first notification information includes the S-NSSAI of the replaced network slice, and the S-NSSAI of the replaced network slice is the first S-NSSAI.

[0018] In a second aspect, the present application provides a communication method, which includes: a second policy control network element receives a first S-NSSAI from a session management network element, wherein the second policy control network element serves a session of a terminal device, and the first S-NSSAI is used to identify the network slice where the session of the terminal device is located after the network slice is replaced; the second policy control network element notifies the first policy control network element of the first S-NSSAI, and the first policy control network element serves the terminal device.

[0019] In one possible design, when the second policy control network element notifies the first policy control network element of the first S-NSSAI, the second policy control network element sends registration update information to the binding support network element, and the registration update information is used to notify the first S-NSSAI.

[0020] In one possible design, the registration update information indicates that the second S-NSSAI is replaced by the first S-NSSAI, the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, or the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0021] In one possible design, the registration update information includes the first S-NSSAI and the second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0022] In one possible design, the registration update information includes the first S-NSSAI but does not include a second S-NSSAI. The second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI. The second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0023] In one possible design, before the second policy control network element notifies the first policy control network element of the first S-NSSAI, the second policy control network element receives first subscription information from the first policy control network element, and the first subscription information is used to subscribe to the network slice replacement event for the session of the terminal device; when the second policy control network element notifies the first policy control network element of the first S-NSSAI, the second policy control network element sends first notification information for the first subscription information to the first policy control network element, and the first notification information is used to determine the first S-NSSAI.

[0024] In one possible design, the network slice replacement event includes that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI; wherein the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI; the first notification information indicates that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI.

[0025] In one possible design, the network slice replacement event indicates that the network slice where the session of the terminal device is located is replaced; the first notification information indicates that the network slice where the session of the terminal device is located is replaced, and the first notification information packet includes the S-NSSAI of the replaced network slice, and the S-NSSAI of the replaced network slice is the first S-NSSAI.

[0026] In one possible design, the second policy control network element sends a second indication message to the application function network element, and the second indication message indicates that the second S-NSSAI is replaced with the first S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0027] In a third aspect, the present application provides a communication method, which includes: a binding support network element obtains a first S-NSSAI from a second policy control network element, wherein the second policy control network element serves a session of a terminal device, and the first S-NSSAI is used to identify the network slice where the session of the terminal device is located after the network slice is replaced; the binding support network element sends a first indication information to the first policy control network element, and the first indication information is used to determine the first S-NSSAI, wherein the first policy control network element serves the terminal device.

[0028] In one possible design, when the binding support network element obtains the first S-NSSAI from the second policy control network element, the binding support network element receives registration update information from the second policy control network element, and the registration update information is used to notify the first S-NSSAI.

[0029] In one possible design, the registration update information indicates that the second S-NSSAI is replaced by the first S-NSSAI, the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0030] In one possible design, the registration update information includes the first S-NSSAI and the second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0031] In one possible design, the registration update information includes the first S-NSSAI but does not include a second S-NSSAI. The second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI. The second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0032] In one possible design, the first indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0033] In one possible design, the first indication information indicates that the policy control network element corresponding to the first S-NSSAI is registered with the binding support network element.

[0034] In one possible design, the first indication information includes the first S-NSSAI and a second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0035] In one possible design, the first indication information includes the first S-NSSAI but does not include a second S-NSSAI, where the second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI and is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0036] In one possible design, when the binding support network element sends the first S-NSSAI to the application function network element, the binding support network element sends third indication information to the application function network element, and the third indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0037] In a fourth aspect, the present application provides a communication device, comprising a transceiver unit and a processing unit, wherein the transceiver unit is used to obtain first single network slice selection auxiliary information S-NSSAI, wherein the first policy control network element serves the terminal device, and the first S-NSSAI is used to identify the network slice where the session of the terminal device is located after the network slice is replaced; the processing unit is used to update the access and mobility management policy and / or terminal device policy according to the first S-NSSAI.

[0038] In one possible design, the transceiver unit is used to receive first indication information from a binding support network element, and the first indication information is used to determine the first S-NSSAI.

[0039] In one possible design, the first indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0040] In one possible design, the first indication information indicates that the policy control network element corresponding to the first S-NSSAI is registered with the binding support network element.

[0041] In one possible design, the first indication information includes the first S-NSSAI and a second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0042] In one possible design, the first indication information includes the first S-NSSAI but does not include a second S-NSSAI, where the second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI and is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0043] In one possible design, the transceiver unit is used to obtain the first S-NSSAI from a second policy control network element.

[0044] In one possible design, the transceiver unit is used to send first subscription information to the second policy control network element before obtaining the first S-NSSAI from the second policy control network element, where the first subscription information is used to subscribe to a network slice replacement event for the session of the terminal device; the second policy control network element serves the session of the terminal device; and receives first notification information for the first subscription information from the second policy control network element, where the first notification information is used to determine the first S-NSSAI.

[0045] In one possible design, the network slice replacement event includes that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI; wherein the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI; the first notification information indicates that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI.

[0046] In one possible design, the network slice replacement event indicates that the network slice where the session of the terminal device is located is replaced; the first notification information indicates that the network slice where the session of the terminal device is located is replaced, and the first notification information includes the S-NSSAI of the replaced network slice, and the S-NSSAI of the replaced network slice is the first S-NSSAI.

[0047] In a fifth aspect, the present application provides a communication device, which includes a transceiver unit and a processing unit, wherein the processing unit calls the transceiver unit to receive a first S-NSSAI from a session management network element, wherein the second policy control network element serves the session of the terminal device, and the first S-NSSAI is used to identify the network slice where the session of the terminal device is located after the network slice is replaced; notifying the first policy control network element of the first S-NSSAI, and the first policy control network element serves the terminal device.

[0048] In one possible design, the transceiver unit is used to send registration update information to the binding support network element, and the registration update information is used to notify the first S-NSSAI.

[0049] In one possible design, the registration update information indicates that the second S-NSSAI is replaced by the first S-NSSAI, the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, or the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0050] In one possible design, the registration update information includes the first S-NSSAI and the second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0051] In one possible design, the registration update information includes the first S-NSSAI but does not include a second S-NSSAI. The second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI. The second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0052] In one possible design, the transceiver unit is used to receive first subscription information from the first policy control network element before notifying the first S-NSSAI, where the first subscription information is used to subscribe to a network slice replacement event for the session of the terminal device; and send first notification information for the first subscription information to the first policy control network element, where the first notification information is used to determine the first S-NSSAI.

[0053] In one possible design, the network slice replacement event includes that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI; wherein the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI; the first notification information indicates that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI.

[0054] In one possible design, the network slice replacement event indicates that a network slice where a session of the terminal device is located is replaced;

[0055] The first notification information indicates that the network slice where the session of the terminal device is located has been replaced, and the first notification information packet contains the S-NSSAI of the replaced network slice, and the S-NSSAI of the replaced network slice is the first S-NSSAI.

[0056] In one possible design, the transceiver unit is used to send a second indication message to the application function network element, where the second indication message indicates that the second S-NSSAI is replaced with the first S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0057] In a sixth aspect, the present application provides a communication device, which includes a transceiver unit and a processing unit, wherein the processing unit calls the transceiver unit to obtain a first S-NSSAI from a second policy control network element, wherein the second policy control network element serves the session of the terminal device, and the first S-NSSAI is used to identify the network slice where the session of the terminal device is located after the network slice is replaced; and sends a first indication information to the first policy control network element, wherein the first indication information is used to determine the first S-NSSAI, wherein the first policy control network element serves the terminal device.

[0058] In one possible design, the transceiver unit is used to receive registration update information from the second policy control network element, and the registration update information is used to notify the first S-NSSAI.

[0059] In one possible design, the registration update information indicates that the second S-NSSAI is replaced by the first S-NSSAI, the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0060] In one possible design, the registration update information includes the first S-NSSAI and the second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0061] In one possible design, the registration update information includes the first S-NSSAI but does not include a second S-NSSAI. The second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI. The second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0062] In one possible design, the first indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0063] In one possible design, the first indication information indicates that the policy control network element corresponding to the first S-NSSAI is registered with the binding support network element.

[0064] In one possible design, the first indication information includes the first S-NSSAI and a second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0065] In one possible design, the first indication information includes the first S-NSSAI but does not include a second S-NSSAI, where the second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI and is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0066] In one possible design, the transceiver unit is used to send a third indication information to the application function network element, and the third indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0067] In the seventh aspect, the present application provides a communication device, which can be a first device, or a module or unit (for example, a chip, or a chip system, or a circuit) in the first device that corresponds one-to-one to the method / operation / step / action described in any one of the first or third aspects above, or can be used in combination with the first device.

[0068] In an eighth aspect, the present application provides a communication device comprising at least one processing element, wherein at least one storage element is used to store programs and data, and the at least one processing element is used to read and execute the programs and data stored in the storage element so that any method described in any one of the above aspects of the present application is implemented.

[0069] In one possible design, the communication device further includes the at least one storage element.

[0070] In a ninth aspect, the present application further provides a computer program, which, when executed on a computer, enables the computer to execute any of the methods described in any of the above aspects.

[0071] In the tenth aspect, the present application provides a communication device, which includes: an interface circuit and at least one processor; the interface circuit is used to provide input and / or output of programs or instructions to the at least one processor; the at least one processor is used to execute the program or instructions so that the communication device can implement any method described in any of the above aspects.

[0072] In one possible manner, the communication device includes the at least one memory, and the at least one memory is used to store the program or instruction.

[0073] In an eleventh aspect, the present application provides a computer storage medium storing a software program. When the software program is read and executed by one or more processors, the software program can implement any of the methods described in any of the above aspects.

[0074] In a twelfth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute any of the methods described in any of the above aspects.

[0075] In a thirteenth aspect, the present application provides a chip system, which includes at least one chip and a memory, and the at least one chip is used to read and execute a program stored in the memory to implement any of the methods described in any of the above aspects.

[0076] In the fourteenth aspect, the present application provides a communication system, which includes: a first policy control network element, a second policy control network element and a binding support network element, the first policy control network element is used to execute the method described in any one of the first aspect, the second policy control network element is used to execute the method described in any one of the second aspect, and the binding support network element is used to execute the method described in any one of the third aspect.

[0077] Based on the implementations provided in the above aspects, this application can also be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Figure 1 is a schematic diagram of the 5G network slicing architecture in this application;

[0079] FIG2A is a schematic diagram of a 5G non-roaming system architecture based on a service-oriented interface in this application;

[0080] FIG2B is a schematic diagram of a 5G non-roaming system architecture based on reference points in this application;

[0081] FIG3A is a schematic diagram of a 5G roaming system architecture based on a service-oriented interface under a home routing solution in this application;

[0082] FIG3B is a schematic diagram of a 5G roaming system architecture based on a reference point under a home routing solution in this application;

[0083] FIG4A is a schematic diagram of a 5G roaming system architecture based on a service-based interface under a local breakout solution in this application;

[0084] FIG4B is a schematic diagram of a 5G roaming system architecture based on a reference point under a local grooming solution in this application;

[0085] FIG5 is a schematic diagram of the deployment of a first policy control network element and a second policy control network element in this application;

[0086] FIG6 is a schematic diagram showing the deployment of another first policy control network element and a second policy control network element in the present application;

[0087] FIG7 is a flowchart illustrating an overview of a communication method in the present application;

[0088] FIG8 is a specific flow chart of updating AM strategy and / or UE strategy in this application;

[0089] FIG9 is a specific flowchart of another method for updating AM strategy and / or UE strategy in the present application;

[0090] FIG10 is a schematic structural diagram of a communication device in this application;

[0091] FIG11 is a schematic structural diagram of another communication device in this application. DETAILED DESCRIPTION

[0092] In the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can represent: a, b, c, a and b, a and c, b and c, or a, b and c, where each of a, b, c can be an element itself, or a set containing one or more elements.

[0093] In this application, the terms "exemplarily," "in some embodiments," "in other embodiments," and the like are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0094] In this application, the terms "of," "corresponding," and "relevant" may be used interchangeably. It should be noted that, when the distinction is not emphasized, the meanings they convey are the same. In the embodiments of this application, the terms "communication" and "transmission" may be used interchangeably. It should be noted that, when the distinction is not emphasized, the meanings they convey are the same. For example, "transmission" may include "send" and "receive" and may be either a noun or a verb.

[0095] It should be pointed out that the words "first", "second", etc. involved in the embodiments of the present application are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

[0096] The following is a brief introduction to the technical concepts involved in this application:

[0097] 1. Three typical scenarios supported by the fifth generation mobile communication technology (5G)

[0098] 5G will usher in an era of the Internet of Everything. 5G supports three key scenarios: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low-latency communications (uRLLC). These three scenarios encompass diverse and differentiated applications.

[0099] Among them, eMBB: Based on breakthroughs in wireless spectrum utilization and spectrum bandwidth technology, 5G can provide transmission rates more than 10 times faster than fourth-generation mobile communication technology (4G). 5G's ultra-high speeds meet the needs of currently popular augmented reality (AR) and virtual reality (VR), high-definition video live streaming, and wireless connections over 5G networks provide a fast experience that 4G transmission rates cannot support.

[0100] mMTC: Through technologies such as multi-user shared access and ultra-dense heterogeneous networks, 5G can support up to one million devices per square kilometer, ten times the capacity of 4G. With the recent rapid development of smart cities, public infrastructure such as streetlights, manhole covers, and water meters have gained network connectivity, enabling remote management. Leveraging the powerful connectivity of 5G networks, it is possible to connect public equipment across various sectors of a city to intelligent management platforms. These public infrastructures work collaboratively through 5G networks, enabling unified management with a minimal maintenance staff, significantly improving city operational efficiency.

[0101] uRRLC: The most typical application in 5G scenarios is autonomous driving. Common scenarios for autonomous driving include sudden braking, vehicle-to-vehicle, vehicle-to-pedestrian, and vehicle-to-infrastructure communications, and multiple simultaneous communications. These require instantaneous processing of large amounts of data and decision-making. Therefore, the network requires high bandwidth, low latency, and high reliability.

[0102] 2. Network slicing technology and network slicing

[0103] In the 4G era, a single network was used to meet all application scenarios and customer groups, continuously adding features to meet the market's evolving demands. For example, if a network needed to support narrowband IoT (NB-IoT), narrowband (NB) features would be enabled on the network elements. Another example, if network reliability needed to be improved, redundancy would be added to the network elements. However, in vertical industries, the requirements for latency, number of connections, reliability, and security vary widely and are unpredictable. For example, AR services require ultra-high bandwidths exceeding 1600Mbps, energy meter reading services require massive connections, and autonomous driving requires end-to-end latency of a few milliseconds and high reliability exceeding 99.999%. Using a single network to meet all current and future demands would be challenging.

[0104] Network slicing technology refers to the ability of operators to divide hardware infrastructure into multiple virtual networks, allocate resources on demand, and flexibly configure virtual networks to meet the different needs of various businesses.

[0105] Network slicing is the virtualization of multiple end-to-end networks on a hardware infrastructure using network slicing technology. Each network has different network functions to adapt to the needs of different types of services. In this application, network slicing can be simply referred to as slices.

[0106] When new business requirements arise and the current network cannot meet them, operators need to virtualize a new network slice for this business without affecting the existing network slices, so as to launch the business as quickly as possible.

[0107] While vertical industries have diverse demands for network functions, these requirements can be broken down into requirements for network bandwidth, number of connections, latency, reliability, and other network functions. The 5G standard also categorizes the network function requirements of different services into three typical scenarios. The corresponding network slices for these three scenarios are eMBB-type slices, mMTC-type slices, and uRLLC-type slices. For example, a schematic diagram of the 5G network slicing architecture is shown in Figure 1.

[0108] Network slicing has the following three characteristics:

[0109] First, isolation, which includes resource isolation, security isolation, and operation, administration, and maintenance isolation. Different domains can use different isolation technologies.

[0110] Second, on-demand customization, including: providing the life cycle of network slices on demand, on-demand distributed deployment of network slices, and on-demand network services.

[0111] Third, end-to-end. Network slicing is an end-to-end network, including access network, transmission network and core network, which requires a cross-network slicing management system.

[0112] 3. Single network slice selection assistance information (S-NSSAI)

[0113] S-NSSAI is used to identify a network slice. Based on the operator's operational or deployment needs, an S-NSSAI can be associated with one or more network slice instances, and a network slice instance can be associated with one or more S-NSSAIs.

[0114] For example, UeMBB slice 1, UeMBB slice 2, and fixed wireless access (FWA) slice 1 are all eMBB type slices, and their S-NSSAI values ​​can all be 0x01000000. Among them, FWA refers to an access method in which wireless transmission is partially or completely used from the service node to the terminal device. eMBB+mMTC slice 4 can provide services for both eMBB type services and mMTC type services. Therefore, it is both an eMBB type slice and an mMTC type slice. The corresponding eMBB type S-NSSAI value is 0x01000000, and the corresponding mMTC type S-NSSAI value is 0x02000000.

[0115] S-NSSAI consists of two parts: slice / service type (SST) and slice differentiator (SD):

[0116] SST refers to the expected network slice behavior in terms of features and services. For example, the standard range of SST values ​​is 1, 2, and 3, where 1 represents eMBB, 2 represents URLLC, and 3 represents massive internet of things (MIoT).

[0117] SD is an optional information used to supplement SST to distinguish multiple network slices of the same slice / service type.

[0118] The SST and SD components together represent the slice type and multiple slices of the same slice type. For example, S-NSSAI values ​​of 0x01000000, 0x02000000, and 0x03000000 represent eMBB slices, uRLLC slices, and MIoT slices, respectively. S-NSSAI values ​​of 0x01000001 and 0x01000002 represent eMBB slices, serving user groups 1 and 2, respectively.

[0119] 4. Network slice selection assistance information (NSSAI)

[0120] NSSAI is a set of S-NSSNIs. For example, in a 5G network, the NSSAI used includes requested NSSAI, allowed NSSAI, configured NSSAI, and target NSSAI. Their specific definitions are shown in Table 1 below:

[0121] Table 1

[0122] 5. AM Strategy

[0123] AM policies can include an index to RAT / frequency selection priority (RFSP). The RFSP index (RFSPIndex) can be mapped by the radio access network (RAN) to a locally defined configuration to apply a specific radio resource management policy. The RFSP index is device-granular and applies to all radio bearers.

[0124] For example, different network slices may require access to different frequency bands. For example, different network slice types may require access to different frequency bands. As shown in Table 2, an eMBB slice may require access from 2.6 GHz or 4.9 GHz, while a URLLC slice may require access from 4.9 GHz.

[0125] Table 2

[0126] For example, for the same type of network slices, the frequency bands that need to be accessed corresponding to different network slices may be different.

[0127] In addition, different types of terminal devices, that is, terminal devices that need to access different types of network slices, may also need to prioritize access to different frequency bands in different areas, as shown in Table 3. For the same slice, the spectrum accessed in Area 1 and Area 2 is different.

[0128] Table 3

[0129] Of course, the AM policy also includes other content, such as service area restrictions, aggregated maximum bit rate (such as UE Slice Maximum Bit Rate (UE-Slice-MBR)), etc., which may also be affected by changes in network slicing. Here we only take the RFSP index as an example.

[0130] 6.UE Strategy

[0131] Among them, the UE policy includes the UE route selection policy (URSP). The terminal device acts as the executor of the policy, and the terminal device uses the UE policy to select a suitable protocol data unit (PDU) session for the uplink service flow. Among them, the PDU session established by the terminal device has attributes such as network slice, data network name (DNN) and session service continuity (SSC) mode. The UE route selection policy (URSP) is used to determine the correspondence between the application (APP) and the network slice, DNN and SSC mode.

[0132] Among them, URSP may include one or more URSP rules, and a URSP rule mainly includes two parts: traffic descriptor and route selection descriptor (RSD). Among them, the traffic descriptor includes the names or identifiers of multiple APPs, etc., the route selection descriptor includes the network slice selection information corresponding to each APP, and the wildcard network slice selection information (that is, the network slice selection information that can be used by the APP not included in the traffic descriptor), etc. The network slice selection information here includes one or more S-NSSAIs.

[0133] The URSP delivery path is: policy control function (PCF) network element -> access and mobility management function (AMF) network element -> terminal device.

[0134] URSP execution: Taking the terminal device as UE as an example, the UE may trigger the establishment or modification of a PDU session. For example, when there is no PDU session that meets the requirements, the UE will initiate the PDU session establishment process; when there is a session that meets the requirements, it may directly use the existing PDU session. Every time a new application is detected, the UE evaluates whether the application matches the traffic descriptor in the rule according to the order of the URSP rules indicated by the rule precedence in the URSP. If it matches, the UE selects the RSD in the rule according to the order of the RSD indicated by the path selection descriptor priority in the URSP.

[0135] 7. Alternative S-NSSAI

[0136] The alternative S-NSSAI refers to the compatible S-NSSAI of the S-NSSAI in the allowed NSSAI. When an S-NSSAI in the allowed NSSAI is unavailable or congested, the AMF network element or other network element can use the alternative S-NSSAI to replace the S-NSSAI.

[0137] The embodiments of the present application can be applied to the 5G system architecture, and can also be applied to other system architectures, such as the 6G system architecture, etc. This application is not limited to this. The following description will only take the 5G system architecture as an example.

[0138] The 5G system architecture further includes the 5G non-roaming architecture and the 5G roaming scenario architecture. In the 5G system, both the service-oriented architecture and the reference point-based architecture can be used.

[0139] 2A shows a 5G non-roaming system architecture based on a service-oriented interface, and FIG2B shows a 5G non-roaming system architecture based on a reference point.

[0140] There are two main networking modes for 5G core network roaming, namely home routed (HR) and local breakout (LBO).

[0141] The home routing solution is shown in Figures 3A and 3B. User plane traffic flows return to the home user plane network element to access the data network. Figure 3A shows the 5G roaming system architecture based on service-based interfaces under the home routing solution, while Figure 3B shows the 5G roaming system architecture based on reference points under the home routing solution.

[0142] The local grooming solution, as shown in Figures 4A and 4B, allows user plane traffic to access the data network via the user plane network element in the roaming location, without requiring assistance from the home network. This solution offers the advantage of a short user plane data transmission path. Figure 4A illustrates the 5G roaming system architecture based on service-based interfaces for the local grooming solution, while Figure 4B illustrates the 5G roaming system architecture based on reference points for the local grooming solution.

[0143] The 5G system includes terminal equipment (e.g., user equipment (UE)), access network (AN) equipment or RAN equipment, and core network (CN).

[0144] Terminal device: can be UE, handheld terminal, laptop computer, subscriber unit, cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem, handheld device, laptop computer, cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal or other device that can access the network.

[0145] RAN equipment: mainly refers to the wireless network equipment of the 3rd Generation Partnership Project (3GPP) network. AN can be an access network equipment defined by non-3GPP. RAN equipment is mainly responsible for wireless resource management, quality of service (QoS) management, data compression and encryption and other functions on the air interface side. The RAN equipment may include various forms of base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, access points, etc. In systems using different wireless access technologies, the names of devices with base station functions may be different. For example, in the fifth generation (5G) system, it is called RAN or gNB (5G NodeB); in the LTE system, it is called evolved NodeB (eNB or eNodeB); in the third generation (3G) system, it is called Node B, etc.

[0146] AN equipment: This equipment allows terminal devices to interconnect with the 3GPP core network using non-3GPP technologies. Non-3GPP technologies include Wireless Fidelity (Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), and Code Division Multiple Access (CDMA) networks.

[0147] The user plane of the core network includes the user plane function (UPF); the control plane of the core network includes the access and mobility management function (AMF) network element, the session management function (SMF) network element, the network exposure function (NEF) network element, the network function repository function (NRF) network element, the unified data management (UDM) network element, the policy control function (PCF) network element, the application function (AF) network element, the network slice admission control function (NSACF) network element, etc.

[0148] Among them, the AMF network element is mainly responsible for mobility management in the mobile network, such as user location update, user registration network, user switching, etc.

[0149] SMF network element: Mainly responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating IP addresses to users and selecting the UPF that provides packet forwarding functions.

[0150] The UPF network element is responsible for forwarding and receiving user data from terminal devices. It receives user data from the data network and transmits it to the terminal device via the access network equipment. The UPF network element also receives user data from the terminal device via the access network equipment and forwards it to the data network. The transmission resources and scheduling functions provided by the UPF network element to the terminal device are managed and controlled by the SMF network element.

[0151] PCF network element: mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is responsible for obtaining user subscription information related to policy decisions.

[0152] NEF network element: mainly used to support the opening of capabilities and events.

[0153] NSACF network element: supports monitoring and controlling the number of registered users of each network slice, supports monitoring and controlling the number of PDU sessions established for each network slice, supports event-based network slice status notification and reporting to other NFs.

[0154] AF network element: mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0155] UDM network element: used for generating authentication credentials, user identification processing (such as storing and managing user permanent identities), access authorization control and contract data management, etc.

[0156] It is understandable that the core network may also include other network elements, and this application does not limit this. It should be understood that the network architectures shown in Figures 2A, 2B, 3A, 3B, 4A, and 4B above can be applied to the embodiments of this application. In addition, the network architecture applicable to the embodiments of this application is not limited to this. Any network architecture that can implement the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0157] It should also be understood that the interface name between the various network elements in the above figure is only an example. The name of the interface in the specific implementation may be other names, and this application does not make specific restrictions on this. The naming of the above network elements is only used to distinguish different functions and should not constitute any limitation on this application. This application does not exclude the possibility of adopting other names in 5G networks and other future networks, and the above naming does not mean that these network elements are independent physical devices. This application does not limit the specific form of the above functional entities. For example, they can be integrated in the same physical device or they can be different physical devices. For example, they can be combined into network slices as needed.

[0158] It should be noted that the above-mentioned "network element" can also be called a functional entity, entity, equipment, device or module, etc., which is not specifically limited in this application.

[0159] It should be noted that in the specific application scenario of the embodiment of the present application, the first policy control network element and the second policy control network element are two different network elements. The first policy control network element serves the terminal device, and the second policy control network element serves the session of the terminal device.

[0160] For example, in a roaming scenario under a home routing solution, as shown in FIG5 , two policy control network elements may be provided for serving a terminal device, one located in the home location and the other in the roaming location. The policy control network element located in the home location and serving the terminal device is the first policy control network element, and the second policy control network element is located in the roaming location.

[0161] Exemplarily, in a roaming scenario under a local relief solution, for example, as shown in FIG6 , the policy control network element serving the terminal device may include two, located in the home location and the roaming location respectively, wherein the policy control network element serving the terminal device located in the home location is the first policy control network element, and the second policy control network element is also located in the home location.

[0162] It should be noted that before the process shown in Figure 7 below, the session of the terminal device (for example, a PDU session) has been established, and the session of the terminal device is located on the network slice identified by the second S-NSSAI. When the network slice identified by the second S-NSSAI is unavailable, the session management network element can initiate the replacement of the network slice, or it can be described as follows: when the network slice identified by the second S-NSSAI is unavailable, the session management network element can modify the network slice where the session of the terminal device is located.

[0163] Based on this, the present application provides a communication method for timely updating of AM policies. As shown in FIG7 , the method includes:

[0164] Step 700: The first policy control network element obtains a first S-NSSAI.

[0165] The first S-NSSAI is used to identify the network slice where the session of the terminal device is located after the network slice is replaced. That is, when the network slice where the session of the terminal device is located is replaced, the replaced network slice is the network slice identified by the first S-NSSAI.

[0166] Step 710: The first policy control network element updates the access and mobility management policy and / or the terminal device policy according to the first S-NSSAI.

[0167] Exemplarily, when the first policy control network element updates the access and mobility management policy based on the first S-NSSAI, the first policy control network element can determine the corresponding RFSP index based on the first S-NSSAI, and use the RFSP index corresponding to the first S-NSSAI as the updated access and mobility management policy.

[0168] For example, in the RFSP index corresponding to the second S-NSSAI, the priority of frequency band 1 is higher than the priority of frequency band 2. In the RFSP index corresponding to the first S-NSSAI, the priority of frequency band 2 is higher than the priority of frequency band 1.

[0169] For another example, in the RFSP index corresponding to the second S-NSSAI, the priority of the high-frequency band is higher than the priority of the low-frequency band. In the RFSP index corresponding to the first S-NSSAI, the priority of the low-frequency band is higher than the priority of the high-frequency band.

[0170] For another example, the RFSF index corresponding to the first S-NSSAI may be the same as the RFSF index corresponding to the second S-NSSAI. In this case, there is no need to update the RFSP index, that is, there is no need to update the AM policy.

[0171] For example, when the first policy control network element updates the terminal device policy according to the first S-NSSAI, the first policy control network element may determine the corresponding URSP according to the first S-NSSAI, and use the URSP corresponding to the first S-NSSAI as the updated terminal device policy.

[0172] For example, the first policy control network element can update the UE policy based on the service information in the session of the terminal device (such as the connection capability reported by the second policy control network element and the first S-NSSAI). This application does not limit the information required to update the UE policy.

[0173] In the event that the network slice where the session of the terminal device is located is replaced, the terminal device can update the URSP rules used. If the first policy control network element does not obtain the first S-NSSAI, the first policy control network element may determine that the terminal device uses the wrong URSP rules. In an embodiment of the present application, the first policy control network element can obtain the first S-NSSAI, and then determine whether the URSP rules used by the UE are accurate, or described as determining whether the terminal device uses non-up-to-date URSP rules. If the UE has used the latest URSP rules, the first policy control network element does not need to notify the UE of the latest URSP rules. Otherwise, the first policy control network element needs to generate the latest URSP rules, that is, update the UE policy, and notify the UE of the latest URSP rules.

[0174] With respect to step 700, the first policy control network element may obtain the first S-NSSAI in the following manners, but not limited to:

[0175] Method 1: The first policy control network element receives first indication information from the binding support network element, and the first indication information is used to determine the first S-NSSAI. Furthermore, the first policy control network element determines the first S-NSSAI according to the first indication information.

[0176] Exemplarily, the second policy control network element receives the first S-NSSAI from the session management network element, the second policy control network element determines that the network slice where the session of the terminal device is located has been replaced, and then sends registration update information to the binding support network element. The registration update information is used to notify the first S-NSSAI, so that the binding support network element notifies the first policy control network element of the first S-NSSAI, that is, the binding support network element obtains the first S-NSSAI from the second policy control network element and sends the first indication information to the first policy control network element.

[0177] Regarding possible implementations of the registration update information and the first indication information, please refer to the relevant description in the following embodiment 1 for details.

[0178] Method 2: The first policy control network element obtains the first S-NSSAI from the second policy control network element.

[0179] Exemplarily, before the first policy control network element obtains the first S-NSSAI, the first policy control network element sends first subscription information to the second policy control network element, where the first subscription information is used to subscribe to a network slice replacement event for a session of the terminal device. Further, if the second policy control network element receives the first S-NSSAI from the session management network element, the second policy control network element determines that the network slice where the session of the terminal device is located has been replaced, and then the second policy control network element may send first notification information regarding the first subscription information to the first policy control network element, so that the first policy control network element determines the first S-NSSAI based on the first notification information.

[0180] Regarding possible implementations of the first subscription information and the first notification information for the first subscription information, please refer to the relevant description in the following embodiment 2 for details.

[0181] In summary, the above embodiments can be used to achieve that when the network slice where the session of the terminal device is located is replaced, the first policy control network element can promptly obtain the S-NSSAI corresponding to the replaced network slice, that is, the first S-NSSAI, and then update the AM policy or UE policy according to the first S-NSSAI.

[0182] Specifically, updating the AM policy can enable the terminal device to access a suitable frequency band. For example, for some S-NSSAI, the terminal device needs to access a high-frequency frequency band to obtain a larger bandwidth.

[0183] Updating the UE policy can prevent the URSP rules on the terminal device from not being updated in time, and can enable the terminal device to obtain the updated URSP rules in time.

[0184] In addition, the second policy control network element or the binding support network element may also notify the application function network element of the S-NSSAI.

[0185] Exemplarily, the second policy control network element sends a second indication message to the application function network element, where the second indication message indicates that the second S-NSSAI is replaced with the first S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0186] Alternatively, if the second policy control network element knows the relationship between the first S-NSSAI and the second S-NSSAI, the second policy control network element may send a second indication message to the application function network element, the second indication message includes the first S-NSSAI and the second S-NSSAI, and the first S-NSSAI is an alternative S-NSSAI for the second S-NSSAI; or the second policy control network element may send a second indication message to the application function network element, the second indication message includes the first S-NSSAI, does not include the second S-NSSAI, and the second S-NSSAI is an alternative S-NSSAI for the first S-NSSAI.

[0187] Exemplarily, the binding support network element sends a third indication message to the application function network element, where the third indication message indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0188] Alternatively, if the binding support network element knows the relationship between the first S-NSSAI and the second S-NSSAI, the binding support network element may send a third indication message to the application function network element, the third indication message includes the first S-NSSAI and the second S-NSSAI, and the first S-NSSAI is an alternative S-NSSAI for the second S-NSSAI; or the binding support network element may send a third indication message to the application function network element, the third indication message includes the first S-NSSAI but does not include the second S-NSSAI, and the second S-NSSAI is an alternative S-NSSAI for the first S-NSSAI.

[0189] It should be noted that in the following Examples 1 and 2, the UE has established a PDU session. It is understandable that only when a network slice is an allowed NSSAI can the UE initiate a PDU session for the corresponding network slice. The second S-NSSAI is used to identify the network slice where the UE's PDU session is located before the network slice is replaced. The first S-NSSAI is used to identify the network slice where the UE's PDU is located after the network slice is replaced. In addition, the AM-PCF network element can also subscribe to service information from the SM-PCF network element. It can be the start and stop of the service, or whether there is a PDU session with the corresponding DNN / S-NSSAI.

[0190] The AM-PCF network element is equivalent to the first policy control network element in the embodiment shown in FIG7 , the SM-PCF network element is equivalent to the second policy control network element in the embodiment shown in FIG7 , and the UE is equivalent to the terminal device in the embodiment shown in FIG7 . The BSF network element is equivalent to the binding support network element in the embodiment shown in FIG7 .

[0191] Example 1: Specific process of updating AM policy and / or UE policy

[0192] S801: The AMF network element establishes an AM policy association and / or a UE policy association with the AM-PCF network element.

[0193] Exemplarily, the AM-PCF network element determines an AM policy, wherein the AM policy includes an RFSP index. The RFSP index may depend on the application being used by the UE, the DNN, the second S-NSSAI, etc. The UE policy may include a URSP.

[0194] S802: The AMF network element determines that the network slice identified by the second S-NSSAI is unavailable or congested, for example, the network slice identified by the second S-NSSAI is congested, then the AMF network element notifies the SMF network element to replace the second S-NSSAI with the first S-NSSAI.

[0195] S803: The SMF network element can modify the S-NSSAI of the UE's PDU session according to the notification from the AMF network element, and replace the second S-NSSAI with the first S-NSSAI, that is, the network slice where the UE's PDU session is located is replaced from the network slice identified by the second S-NSSAI to the network slice identified by the first S-NSSAI.

[0196] The first S-NSSAI and the second S-NSSAI may be stored in the SMF network element.

[0197] S804: The SMF network element sends a first S-NSSAI to the SM-PCF network element.

[0198] S805: The SM-PCF network element sends registration update information to the BSF network element.

[0199] The registration update information is used to notify the first S-NSSAI. The registration update information can be sent in the following ways, but is not limited to:

[0200] Method 1: The registration update information indicates that the second S-NSSAI is replaced by the first S-NSSAI, and the second S-NSSAI is used to identify the network slice where the UE's PDU session is located before the network slice replacement.

[0201] The first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0202] In mode 1, the SM-PCF network element may not determine the relationship between the first S-NSSAI and the second S-NSSAI.

[0203] Method 2: The registration update message includes the first and second S-NSSAIs. This means that the SM-PCF network element determines the first S-NSSAI as a candidate S-NSSAI for the second S-NSSAI, and then registers the first and second S-NSSAIs with the BSF network element. Since existing registration update messages only include one S-NSSAI, the first S-NSSAI is added as a new parameter. In other words, the registration update message now includes two S-NSSAIs.

[0204] Method 3: The registration update information includes the first S-NSSAI but does not include the second S-NSSAI, that is, the SM-PCF network element determines that the second S-NSSAI is the alternative S-NSSAI of the first S-NSSAI, or it can be described as restoring the network slice corresponding to the alternative S-NSSAI to the original network slice, then registering the first S-NSSAI in the BSF network element without registering the second S-NSSAI.

[0205] For the above-mentioned method 2 and method 3, the SM-PCF network element needs to determine the relationship between the first S-NSSAI and the second S-NSSAI, and the SM-PCF network element needs to save the relationship between the first S-NSSAI and the second S-NSSAI in advance.

[0206] In addition, for the above methods 1 to 3, the SM-PCF network element can also register the UE address (address) in the BSF network element. Optionally, the SM-PCF network element can also register parameters such as the data network name (DNN) and the user permanent identifier (SUPI) in the BSF network element.

[0207] S806: The BSF network element sends first indication information to the AM-PCF network element.

[0208] The first indication information is used to determine the first S-NSSAI. The first indication information can be provided in, but not limited to, the following ways:

[0209] Method A: Corresponding to the above method 1, the first indication information indicates that the second S-NSSAI is replaced by the first S-NSSAI.

[0210] Method B: Corresponding to the above method 2, the first indication information includes the first S-NSSAI and the second S-NSSAI.

[0211] Method C: Corresponding to the above method 3, the first indication information includes the first S-NSSAI but does not include the second S-NSSAI.

[0212] It can be understood that for the above-mentioned methods A to B, the AM-PCF network element has sent subscription information 1 to the BSF network element. The subscription information 1 includes a user permanent identifier (SUPI) and a second S-NSSAI. The subscription information 1 is used to indicate that when the PCF network element (i.e., the SM-PCF network element) serving the PDU session of this SUPI registers or deregisters in the network slice corresponding to the second S-NSSAI, the AM-PCF network element is notified. Therefore, the BSF network element determines the AM-PCF network element based on the subscription information 1 and the registration update information, and sends notification information for the subscription information 1, i.e., the first indication information, to the AM-PCF network element.

[0213] Method D: Corresponding to the above methods 1 to 3, the AM-PCF network element has sent subscription information 2 to the BSF network element. Subscription information 2 includes SUPI and the first S-NSSAI. Subscription information 2 is used to instruct the PCF network element (i.e., SM-PCF network element) serving the PDU session of this SUPI to notify the AM-PCF network element when registering or deregistering in the network slice corresponding to the first S-NSSAI. Therefore, the BSF network element determines the AM-PCF network element based on subscription information 2 and registration update information, and sends notification information for subscription information 2, i.e., first indication information, to the AM-PCF network element. The first indication information indicates that the SM-PCF network element corresponding to the first S-NSSAI is registered with the BSF network element, that is, the SM-PCF network element is registered with the first S-NSSAI. Exemplarily, the first indication information may include the first S-NSSAI. In this case, the first S-NSSAI may not be included, but the identifier of the PCF network element corresponding to the first S-NSSAI may be included. Then, the AM-PCF network element determines the first S-NSSAI based on the identifier. When the BSF network element notifies the PCF network element of the identifier, it means that the PCF is registered with the first S-NSSAI. The AM-PCF can know that there is a PDU session corresponding to the first S-NSSAI.

[0214] The BSF network element may further send a deregistration notification to the AM-PCF network element that subscribes to the second S-NSSAI. The deregistration notification instructs the SM-PCF network element corresponding to the second S-NSSAI to deregister, that is, the SM-PCF network element deregisters from the second S-NSSAI.

[0215] The SM-PCF network element corresponding to the first S-NSSAI and the SM-PCF network element corresponding to the second S-NSSAI may represent the same network element or two different network elements. The SM-PCF network element corresponding to the first S-NSSAI may be a network element reselected by the SMF network element.

[0216] S807: The AM-PCF network element updates the AM policy and / or UE policy according to the first S-NSSAI.

[0217] For details, please refer to the above step 710, which will not be repeated here.

[0218] Example 2: Specific process of updating AM policy and / or UE policy

[0219] S901: The AMF network element establishes an AM policy association and / or a UE policy association with the AM-PCF network element.

[0220] S902: The AM-PCF network element sends first subscription information to the SM-PCF network element. The first subscription information is used to subscribe to a network slice replacement event for a PDU session of the UE.

[0221] In a first possible implementation, the network slice replacement event includes that the network slice where the UE's PDU session is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI. In addition, the network slice replacement event may also include that the network slice where the UE's PDU session is located is replaced from the network slice corresponding to the first S-NSSAI to the network slice corresponding to the second S-NSSAI.

[0222] The first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0223] In a second possible implementation, the network slice replacement event indicates that the network slice where the UE's PDU session is located is replaced. This does not limit the network slices before and after the replacement to have an alternative relationship.

[0224] S903: The AMF network element determines that the network slice identified by the second S-NSSAI is unavailable or congested, for example, the network slice identified by the second S-NSSAI is congested, then the AMF network element notifies the SMF network element to replace the second S-NSSAI with the first S-NSSAI.

[0225] S904: The SMF network element can modify the S-NSSAI of the UE's PDU session according to the notification from the AMF network element, and replace the second S-NSSAI with the first S-NSSAI, that is, the network slice where the UE's PDU session is located is replaced from the network slice identified by the second S-NSSAI to the network slice identified by the first S-NSSAI.

[0226] S905: The SMF network element sends the first S-NSSAI to the SM-PCF network element.

[0227] S906: The SM-PCF network element sends first notification information for the first subscription information to the AM-PCF network element, so that the AM-PCF network element determines the first S-NSSAI according to the first notification information.

[0228] Corresponding to the first possible implementation method mentioned above, when the network slice where the UE's PDU session is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI, the SM-PCF network element sends a first notification message for the first subscription information to the AM-PCF network element, wherein the first notification message indicates that the network slice where the UE's PDU session is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI. Therefore, the AM-PCF network element can determine, based on the first notification message, that the network slice where the UE's PDU session is located is replaced with the network slice corresponding to the first S-NSSAI, that is, determine the first S-NSSAI.

[0229] Similarly, when the network slice where the UE's PDU session is located is replaced from the network slice corresponding to the first S-NSSAI to the network slice corresponding to the second S-NSSAI, the SM-PCF network element sends a first notification message for the first subscription information to the AM-PCF network element, wherein the first notification message indicates that the network slice where the UE's PDU session is located is replaced from the network slice corresponding to the first S-NSSAI to the network slice corresponding to the second S-NSSAI. Therefore, the AM-PCF network element can determine, based on the first notification message, that the network slice where the UE's PDU session is located is replaced with the network slice corresponding to the second S-NSSAI, and then determine the second S-NSSAI.

[0230] Corresponding to the second possible implementation method mentioned above, when the network slice where the UE's PDU session is located sends a replacement, the SM-PCF network element sends a first notification message for the first subscription information to the AM-PCF network element, wherein the first notification message indicates that the network slice where the UE's PDU session is located is replaced, and the first notification message includes the S-NSSAI of the replaced network slice, and the S-NSSAI of the replaced network slice is the first S-NSSAI.

[0231] S907: The AM-PCF network element updates the AM policy and / or UE policy according to the first S-NSSAI.

[0232] For details, please refer to the above step 710, which will not be repeated here.

[0233] In addition, if the indication method of replacing the second S-NSSAI with the first S-NSSAI is adopted, that is, the above-mentioned method 1 and method A, the AF network element may not be able to find the SM-PCF network element. It is necessary to further notify the AF network element of the first S-NSSAI. Exemplarily, the BSF network element may notify the AF network element or the SM-PCF network element may notify the AF network element. See the dotted parts in Figures 6 and 7 for details. For example, the SM-PCF network element may send a second indication message to the AF network element, or the BSF network element may send a third indication message to the AF network element. For the second indication message and the third indication message, please refer to the relevant content in the previous text and will not be repeated here. Among them. In Figure 6, the second indication message is after S804, and the third indication message is after S805, and may be before or after S806. This application does not limit this. In Figure 7, the second indication message is after S905, and may be before or after S906. This application does not limit this.

[0234] When the PDU session is established, the SMF network element will register the S-NSSAI (i.e., the second S-NSSAI) of the network slice where the PDU session is located in the UDM network element (mainly used for intercommunication between 5G and 4G or switching between 3GPP and non-3GPP access). When the S-NSSAI of the PDU session changes, the SMF network element can store the updated S-NSSAI (i.e., the first S-NSSAI) and its own identifier in the UDM network element.

[0235] The SMF network element may store the updated S-NSSAI (i.e., the first S-NSSAI) in the UDM network element in the following ways, but not limited to:

[0236] In one possible implementation, the SMF network element registers the first S-NSSAI and the second S-NSSAI with the UDM network element. The first S-NSSAI is registered with the UDM network element as a new parameter, and the first S-NSSAI is an alternative S-NSSAI for the second S-NSSAI. Alternatively, the SMF network element registers the first S-NSSAI with the UDM network element, and the second S-NSSAI is an alternative S-NSSAI for the first S-NSSAI.

[0237] In another possible implementation, the SMF network element replaces the second S-NSSAI registered in the UDM network element with the first S-NSSAI.

[0238] With the above design, when the UE initiates a public data network (PDN) connection establishment or a PDU session establishment using the alternative S-NSSAI in 4G or non-3GPP, the network side device (for example, the AMF network element) obtains the SMF identifier from the UDM so that it can find the corresponding SMF network element.

[0239] It is understandable that in order to implement the functions in the above embodiments, the terminal device or each functional module (NSWOF, UDM, AUSF) includes a hardware structure and / or software module corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software-driven hardware manner depends on the specific application scenario and design constraints of the technical solution.

[0240] Figures 10 and 11 are schematic diagrams of the structures of possible communication devices provided in the embodiments of the present application. These communication devices can be used to implement the functions of the first policy control network element, the second policy control network element, or the binding support network element in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments. In the embodiments of the present application, the communication device can be the first policy control network element, the second policy control network element, or the binding support network element, and can also be a module (such as a chip) applied to the first policy control network element, the second policy control network element, or the binding support network element.

[0241] As shown in FIG. 10 , the communication device 1000 includes a processing unit 1010 and a transceiver unit 1020 .

[0242] When the communication device 1000 is used to implement the function of the first policy control network element in the method embodiments shown in Figures 7 to 9 above: the transceiver unit 1020 is used to obtain first single network slice selection auxiliary information S-NSSAI, wherein the first policy control network element serves the terminal device, and the first S-NSSAI is used to identify the network slice where the session of the terminal device is located after the network slice is replaced; the processing unit 1010 is used to update the access and mobility management policy and / or terminal device policy according to the first S-NSSAI.

[0243] In one possible design, the transceiver unit 1020 is used to receive first indication information from a binding support network element, and the first indication information is used to determine the first S-NSSAI.

[0244] In one possible design, the first indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0245] In one possible design, the first indication information indicates that the policy control network element corresponding to the first S-NSSAI is registered with the binding support network element.

[0246] In one possible design, the first indication information includes the first S-NSSAI and a second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0247] In one possible design, the first indication information includes the first S-NSSAI but does not include a second S-NSSAI, where the second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI and is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0248] In one possible design, the transceiver unit 1020 is used to obtain the first S-NSSAI from the second policy control network element.

[0249] In one possible design, the transceiver unit 1020 is used to send first subscription information to the second policy control network element before obtaining the first S-NSSAI from the second policy control network element, where the first subscription information is used to subscribe to a network slice replacement event for the session of the terminal device; the second policy control network element serves the session of the terminal device; and receives first notification information for the first subscription information from the second policy control network element, where the first notification information is used to determine the first S-NSSAI.

[0250] In one possible design, the network slice replacement event includes that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI; wherein the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI; the first notification information indicates that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI.

[0251] In one possible design, the network slice replacement event indicates that the network slice where the session of the terminal device is located is replaced; the first notification information indicates that the network slice where the session of the terminal device is located is replaced, and the first notification information includes the S-NSSAI of the replaced network slice, and the S-NSSAI of the replaced network slice is the first S-NSSAI.

[0252] When the communication device 1000 is used to implement the function of the second policy control network element in the method embodiments shown in Figures 7 to 9 above: the processing unit 1010 calls the transceiver unit 1020 to receive the first S-NSSAI from the session management network element, wherein the second policy control network element serves the session of the terminal device, and the first S-NSSAI is used to identify the network slice where the session of the terminal device is located after the network slice is replaced; and notifies the first policy control network element of the first S-NSSAI, and the first policy control network element serves the terminal device.

[0253] In one possible design, the transceiver unit 1020 is used to send registration update information to the binding support network element, and the registration update information is used to notify the first S-NSSAI.

[0254] In one possible design, the registration update information indicates that the second S-NSSAI is replaced by the first S-NSSAI, the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, or the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0255] In one possible design, the registration update information includes the first S-NSSAI and the second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0256] In one possible design, the registration update information includes the first S-NSSAI but does not include a second S-NSSAI. The second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI. The second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0257] In one possible design, the transceiver unit 1020 is used to receive first subscription information from the first policy control network element before notifying the first S-NSSAI, where the first subscription information is used to subscribe to a network slice replacement event for the session of the terminal device; and send first notification information for the first subscription information to the first policy control network element, where the first notification information is used to determine the first S-NSSAI.

[0258] In one possible design, the network slice replacement event includes that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI; wherein the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI; the first notification information indicates that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI.

[0259] In one possible design, the network slice replacement event indicates that a network slice where a session of the terminal device is located is replaced;

[0260] The first notification information indicates that the network slice where the session of the terminal device is located has been replaced, and the first notification information packet contains the S-NSSAI of the replaced network slice, and the S-NSSAI of the replaced network slice is the first S-NSSAI.

[0261] In one possible design, the transceiver unit 1020 is used to send a second indication message to the application function network element, where the second indication message indicates that the second S-NSSAI is replaced with the first S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0262] When the communication device 1000 is used to implement the function of binding a supporting network element in the method embodiments shown in Figures 7 to 9 above: the processing unit 1010 calls the transceiver unit 1020 to obtain a first S-NSSAI from a second policy control network element, wherein the second policy control network element serves the session of the terminal device, and the first S-NSSAI is used to identify the network slice where the session of the terminal device is located after the network slice is replaced; and sends a first indication message to the first policy control network element, wherein the first indication message is used to determine the first S-NSSAI, wherein the first policy control network element serves the terminal device.

[0263] In one possible design, the transceiver unit 1020 is used to receive registration update information from the second policy control network element, and the registration update information is used to notify the first S-NSSAI.

[0264] In one possible design, the registration update information indicates that the second S-NSSAI is replaced by the first S-NSSAI, the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0265] In one possible design, the registration update information includes the first S-NSSAI and the second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0266] In one possible design, the registration update information includes the first S-NSSAI but does not include a second S-NSSAI. The second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI. The second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0267] In one possible design, the first indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0268] In one possible design, the first indication information indicates that the policy control network element corresponding to the first S-NSSAI is registered with the binding support network element.

[0269] In one possible design, the first indication information includes the first S-NSSAI and a second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

[0270] In one possible design, the first indication information includes the first S-NSSAI but does not include a second S-NSSAI, where the second S-NSSAI is an alternative S-NSSAI to the first S-NSSAI and is used to identify the network slice in which the session of the terminal device is located before the network slice is replaced.

[0271] In one possible design, the transceiver unit 1020 is used to send a third indication information to the application function network element, where the third indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

[0272] For a more detailed description of the processing unit 1010 and the transceiver unit 1020 , reference may be made to the relevant descriptions in the method embodiments shown in FIG. 7 to FIG. 10 .

[0273] As shown in Figure 11, communication device 1100 includes a processor 1110 and an interface circuit 1120. Processor 1110 and interface circuit 1120 are coupled to each other. It will be appreciated that interface circuit 1120 may be a transceiver or an input / output interface. Optionally, communication device 1100 may further include a memory 1130 for storing instructions executed by processor 1110, input data required by processor 1110 to execute instructions, or data generated by processor 1110 after executing instructions.

[0274] When the communication device 1100 is used to implement the methods shown in FIG. 7 to FIG. 9 , the processor 1110 is used to implement the functions of the processing unit 1010 , and the interface circuit 1120 is used to implement the functions of the transceiver unit 1020 .

[0275] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0276] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. The processor and storage medium can also exist in a base station or a terminal as discrete components.

[0277] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0278] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0279] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

Claims

1. A communication method, characterized in that: The method includes: The first policy control network element obtains first single network slice selection auxiliary information S-NSSAI, wherein the first policy control network element serves a terminal device, and the first S-NSSAI is used to identify a network slice where a session of the terminal device is located after the network slice is replaced; The first policy control network element updates the access and mobility management policy and / or terminal device policy according to the first S-NSSAI.

2. The method according to claim 1, characterized in that The first policy control network element obtains the first S-NSSAI, including: The first policy control network element receives first indication information from the binding support network element, where the first indication information is used to determine the first S-NSSAI.

3. The method according to claim 2, characterized in that The first indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

4. The method according to claim 2, characterized in that The first indication information indicates that the policy control network element corresponding to the first S-NSSAI is registered with the binding support network element.

5. The method according to claim 2, characterized in that The first indication information includes the first S-NSSAI and the second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

6. The method according to claim 2, characterized in that The first indication information includes the first S-NSSAI but does not include a second S-NSSAI, where the second S-NSSAI is an alternative S-NSSAI for the first S-NSSAI and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

7. The method according to claim 1, characterized in that The first policy control network element obtains the first S-NSSAI, including: The first policy control network element obtains the first S-NSSAI from the second policy control network element.

8. The method according to claim 7, characterized in that Before the first policy control network element obtains the first S-NSSAI from the second policy control network element, the method further includes: The first policy control network element sends first subscription information to the second policy control network element, where the first subscription information is used to subscribe to a network slice replacement event for a session of the terminal device; the second policy control network element serves the session of the terminal device; The first policy control network element obtaining the first S-NSSAI from the second policy control network element includes: The first policy control network element receives first notification information for the first subscription information from the second policy control network element; the first notification information is used to determine the first S-NSSAI.

9. The method according to claim 8, characterized in that The network slice replacement event includes that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI; wherein the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI; The first notification information indicates that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI.

10. The method according to claim 8, characterized in that The network slice replacement event indicates that the network slice where the session of the terminal device is located is replaced; The first notification information indicates that the network slice where the session of the terminal device is located is replaced, and the first notification information includes the S-NSSAI of the replaced network slice, and the S-NSSAI of the replaced network slice is the first S-NSSAI.

11. A communication method, characterized in that: The method includes: The second policy control network element receives a first S-NSSAI from the session management network element, wherein the second policy control network element serves a session of the terminal device, and the first S-NSSAI is used to identify a network slice where the session of the terminal device is located after the network slice is replaced; The second policy control network element notifies the first policy control network element of the first S-NSSAI, and the first policy control network element serves the terminal device.

12. The method according to claim 11, characterized in that The second policy control network element notifying the first policy control network element of the first S-NSSAI includes: The second policy control network element sends registration update information to the binding support network element, where the registration update information is used to notify the first S-NSSAI.

13. The method according to claim 12, characterized in that The registration update information indicates that the second S-NSSAI is replaced by the first S-NSSAI, the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, or the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

14. The method according to claim 12, characterized in that The registration update information includes the first S-NSSAI and the second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

15. The method according to claim 12, characterized in that The registration update information includes the first S-NSSAI but does not include the second S-NSSAI, where the second S-NSSAI is an alternative S-NSSAI for the first S-NSSAI and is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

16. The method according to claim 11, characterized in that Before the second policy control network element notifies the first policy control network element of the first S-NSSAI, the method further includes: The second policy control network element receives first subscription information from the first policy control network element, where the first subscription information is used to subscribe to a network slice replacement event for a session of the terminal device; The second policy control network element notifying the first policy control network element of the first S-NSSAI includes: The second policy control network element sends first notification information for the first subscription information to the first policy control network element, where the first notification information is used to determine the first S-NSSAI.

17. The method according to claim 16, characterized in that The network slice replacement event includes that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI; wherein the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI; The first notification information indicates that the network slice where the session of the terminal device is located is replaced from the network slice corresponding to the second S-NSSAI to the network slice corresponding to the first S-NSSAI.

18. The method according to claim 16, characterized in that The network slice replacement event indicates that the network slice where the session of the terminal device is located is replaced; The first notification information indicates that the network slice where the session of the terminal device is located is replaced, and the first notification information contains the S-NSSAI of the replaced network slice, and the S-NSSAI of the replaced network slice is the first S-NSSAI.

19. The method according to any one of claims 11 to 18, characterized in that: Also includes: The second policy control network element sends a second indication message to the application function network element, and the second indication message indicates that the second S-NSSAI is replaced with the first S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

20. A communication method, characterized in that: The method includes: The binding support network element obtains a first S-NSSAI from a second policy control network element, wherein the second policy control network element serves a session of a terminal device, and the first S-NSSAI is used to identify a network slice where a session of the terminal device is located after the network slice is replaced; The binding support network element sends first indication information to a first policy control network element, where the first indication information is used to determine the first S-NSSAI, wherein the first policy control network element serves the terminal device.

21. The method of claim 20, wherein: The binding support network element obtains the first S-NSSAI from the second policy control network element, including: The binding support network element receives registration update information from the second policy control network element, where the registration update information is used to notify the first S-NSSAI.

22. The method according to claim 21, characterized in that The registration update information indicates that the second S-NSSAI is replaced by the first S-NSSAI, the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

23. The method of claim 21, wherein: The registration update information includes the first S-NSSAI and the second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

24. The method of claim 21, wherein: The registration update information includes the first S-NSSAI but does not include the second S-NSSAI, where the second S-NSSAI is an alternative S-NSSAI for the first S-NSSAI and is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

25. The method according to any one of claims 20 to 24, characterized in that The first indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

26. The method according to any one of claims 20 to 24, characterized in that The first indication information indicates that the policy control network element corresponding to the first S-NSSAI is registered with the binding support network element.

27. The method according to any one of claims 20 to 24, characterized in that The first indication information includes the first S-NSSAI and the second S-NSSAI, the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI, and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

28. The method according to any one of claims 20 to 24, characterized in that: The first indication information includes the first S-NSSAI but does not include a second S-NSSAI, where the second S-NSSAI is an alternative S-NSSAI for the first S-NSSAI and the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced.

29. The method according to any one of claims 20 to 28, characterized in that The binding support network element sends the first S-NSSAI to the application function network element, including: The binding support network element sends a third indication information to the application function network element, and the third indication information indicates that the second S-NSSAI is replaced with the first S-NSSAI, wherein the second S-NSSAI is used to identify the network slice where the session of the terminal device is located before the network slice is replaced, and the first S-NSSAI is an alternative S-NSSAI of the second S-NSSAI; or, the second S-NSSAI is an alternative S-NSSAI of the first S-NSSAI.

30. A communication device, characterized in that: The communication device comprises at least one processor; the at least one processor is configured to execute the method according to any one of claims 1 to 29.

31. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction, and when the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 29 is implemented.

32. A computer program product, characterized in that The computer program product comprises a program or instructions, which, when executed, causes the method according to any one of claims 1 to 29 to be performed.

33. A communication system, characterized in that: The communication system includes a first policy control network element, a second policy control network element and a binding support network element, wherein the first policy control network element executes the method as described in any one of claims 1 to 10, the second policy control network element executes the method as described in any one of claims 11 to 19, and the binding support network element executes the method as described in any one of claims 20 to 29.

Citation Information

Patent Citations

  • Communication method, first policy control network element and communication system

    CN113993094A

  • Method, device and system for acquiring information

    CN115643559A

  • Switching method, apparatus and system

    WO2022028114A1

  • Communication method, apparatus and system

    WO2022228192A1