Communication method and communication apparatus

Abstract

The present application is applied to the field of communications. Provided are a communication method and a communication apparatus. In the technical solution of the present application, whether a terminal supports a network slice replacement characteristic is determined, and if it is determined that the terminal does not support the network slice replacement characteristic, a network slice replacement procedure between an RAN and a UPF is executed. In the technical solution of the present application, when a terminal does not support a network slice replacement characteristic, the service experience of a UE can be guaranteed by means of guaranteeing the service experience between an RAN and a UPF.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202411216354.X, filed with the State Intellectual Property Office of China on August 30, 2024, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to communication methods and communication devices. Background Technology

[0003] To ensure a satisfactory user experience, the communication system defines a network slice replacement feature. This feature is used to temporarily replace the currently used network slice with another network slice when the current network slice becomes unavailable or congested, thus maintaining a good service experience. However, the terminal must support this network slice replacement feature to implement the replacement and ensure the desired service experience.

[0004] Therefore, there is an urgent need for a technical solution that can ensure the service experience even if the terminal does not support the network slice replacement feature. Summary of the Invention

[0005] The communication method and communication device provided in this application can ensure the service experience of the terminal even if the terminal does not support the network slice replacement feature.

[0006] In a first aspect, this application provides a communication method applicable to access and mobility management function network elements. The communication method includes: determining whether a terminal supports network slice replacement features; if the terminal does not support network slice replacement features, determining to send first information to a session management function network element, the first information indicating that a first network slice associated with a protocol data unit session be replaced with a second network slice.

[0007] In this communication method, when it is necessary to update the original network slice (first network slice) associated with the protocol data unit session to a replacement network slice (second network slice), it is determined whether the terminal supports the network slice replacement feature. If the terminal does not support the network slice replacement feature, the access and mobility management function network element still determines to instruct the session management function network element to update the original network slice associated with the protocol data unit session to the replacement network slice. This can realize the update of services on the protocol data unit session between the access network device and the user plane function network element to the replacement network slice for transmission, thereby ensuring the transmission performance of services between the access network device and the user plane function network element, and ultimately ensuring the service experience.

[0008] In this communication method, it can be understood that after the access and mobility management function network element determines that it will send the first information to the session management function network element, it will send the first information to the session management function network element.

[0009] In some possible implementations, when the terminal does not support the network slice replacement feature, the access and mobility management function network element may not send an instruction to the terminal to update the original network slice associated with the protocol data unit session to the replacement network slice.

[0010] Because the terminal itself does not support the network slice replacement feature, even if the access and mobility management function network element sends an instruction to update the original network slice associated with the protocol data unit session to a replacement network slice, the terminal cannot update the original network slice associated with the protocol data unit session to a replacement network slice. Therefore, the access and mobility management function network element does not send an instruction to the terminal to update the original network slice associated with the protocol data unit session to a replacement network slice, which can avoid the waste of signaling overhead.

[0011] In some possible implementations, this communication method further includes: receiving second information, the second information being used to trigger the sending of third information to the access network device and the sending of fourth information to the terminal, the third information indicating that the network slice associated with the protocol data unit session be replaced with the second network slice, and the fourth information indicating that the network slice associated with the protocol data unit session be replaced with the second network slice; if the terminal does not support the network slice replacement feature, determining not to send the fourth information to the terminal.

[0012] It is understandable that the second information is used to trigger the sending of the third information to the access network device and the fourth information to the terminal. This means that, normally, after receiving the second information, the access and mobility management function (AM) network element will send the third information to the access network device and the fourth information to the terminal. However, in this implementation, after receiving the second information, the AM network element must determine whether to send an indication (fourth information) to the terminal to update the network slice associated with the Protocol Data Unit (PDU) session to a replacement network slice, depending on whether the terminal supports the network slice replacement feature. If the terminal does not support the network slice replacement feature, the AM network element will not send the indication to the terminal to update the network slice associated with the PDU session to a replacement network slice, even if it receives the second information.

[0013] It is understandable that in this implementation, after receiving the second information, the access and mobility management function network element will still send the third information to the access network device if the terminal does not support the network slice replacement feature. This will update the network slice associated with the protocol data unit session to the replacement network slice. In this way, the network slice associated with the protocol data unit can be updated between the access network device and the user plane function network element, thereby ensuring the service experience on the protocol data unit.

[0014] In some possible implementations, the communication method further includes: determining to send fifth information to the access network device, the fifth information indicating a list of network slices allowed by the access network device, the list of network slices including the second network slice.

[0015] It is understandable that in this implementation, after the access and mobility management function network element determines that it will send the fifth information to the access network device, it can send the fifth information to the access network device.

[0016] This implementation enables the access network device to successfully replace the network slice after receiving the instruction to switch the Protocol Data Unit (PDU) session to a replacement network slice. This allows the technical solution of this application to be used even when the access network device has slice admission control enabled, thus broadening its application scenarios.

[0017] In some possible implementations, this communication method further includes: determining the first information based on a local configuration policy. That is, the access and mobility management function (AM) network element can determine whether it is necessary to update the network element associated with the protocol data unit (DAC) session to a new network slice based on the locally configured policy. Thus, even if the AM does not receive information from other network elements triggering network slice replacement, the AM can make the decision to ensure a smooth service experience on the DAC session.

[0018] In some possible implementations, this communication method further includes: receiving network slice replacement information from the policy control function network element, and determining first information based on the network slice replacement information. That is, the access and mobility management function network element can assist in implementing network slice replacement based on the instructions of the policy control function network element, thereby ensuring the service experience on the protocol data unit session.

[0019] In some possible implementations, this communication method further includes sending a sixth piece of information to the policy control function network element, the sixth piece of information being used to indicate whether the terminal supports the network slice replacement feature. This provides the policy control function network element with a decision-making basis for determining whether to instruct network slice replacement, supporting the policy control function network element in making accurate decisions.

[0020] In some possible implementations, the sixth information is carried within the terminal's mobility management capability information. Reusing the terminal's mobility management capability information to carry the sixth information can avoid wasting signaling overhead.

[0021] Secondly, this application provides a communication method applied in a policy control function network element. The communication method includes: receiving third information from the access and mobility management function network element, the third information being used to indicate whether the terminal supports network slice replacement features; if the terminal supports network slice replacement features, determining to send network slice replacement information to the access and mobility management function network element.

[0022] If the terminal does not support the network slice replacement feature, even if the policy control function network element sends network slice replacement information to the access and mobility management function network element, the access and mobility management function network element cannot assist the terminal in replacing the network slice based on the instruction of the network slice replacement information. Therefore, in this communication method, the policy control function network element only instructs the access and mobility management function network element to replace the network slice when the terminal supports the network slice replacement feature, which can ensure the effectiveness of the network slice replacement information.

[0023] In some possible implementations, before sending network slice replacement information to the access and mobility management function network element, the communication method further includes: receiving an application detection and control trigger message and / or receiving seventh information, wherein the seventh information indicates that the first network slice is unavailable, and the application service associated with the application detection and control trigger message is transmitted through the protocol data unit session.

[0024] In this implementation, when the policy control function network element receives application detection and control trigger messages and / or seventh information, it can trigger the network slice switching process, thereby ensuring service experience when these situations occur.

[0025] In some possible implementations, this communication method further includes: if the terminal does not support the network slice replacement feature, determining not to send network slice replacement information to the access and mobility management function network element.

[0026] If the terminal does not support network slice replacement, even if the policy control function network element sends network slice replacement information to the access and mobility management function network element, the access and mobility management function network element cannot help the terminal replace the network slice based on the instructions in the network slice replacement information. In this case, not sending network slice replacement information can avoid wasting signaling overhead compared to sending it.

[0027] Thirdly, this application provides a communication device. This communication device may include modules corresponding to the methods / operations / steps / actions described in the first aspect or any possible implementation of the first aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0028] In one design, the communication device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in the first aspect or any possible implementation thereof, while the processing module is used to perform the processing actions involved in the method described in the first aspect or any possible implementation thereof.

[0029] In one design, the communication device may be an access and mobility management function network element, or a device, module, circuit or chip configured in the access and mobility management function network element, or a device that can be used in conjunction with the access and mobility management function network element.

[0030] Fourthly, this application provides a communication device. This communication device may include modules corresponding to the methods / operations / steps / actions described in the second aspect or any possible implementation of the second aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0031] In one design, the communication device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in the second aspect or any possible implementation thereof, while the processing module is used to perform the processing actions involved in the method described in the second aspect or any possible implementation thereof.

[0032] In one design, the communication device can be a policy control function network element, or a device, module, circuit, or chip configured in the policy control management function network element, or a device that can be used in conjunction with the policy control function network element.

[0033] Fifthly, this application provides a communication device including a processor, wherein instructions are executed by the processor to cause the method as described in the first aspect or any possible implementation thereof to be implemented.

[0034] Optionally, the communication device may further include a storage medium that stores the instructions executed by the processor.

[0035] In a sixth aspect, this application provides a communication device including a processor, wherein instructions are executed by the processor to cause the method as described in the second aspect or any possible implementation thereof to be implemented.

[0036] Optionally, the communication device may further include a storage medium that stores the instructions executed by the processor.

[0037] In a seventh aspect, this application provides a chip including a processing circuit for running a program or instructions to implement a method as described in the first aspect or any possible implementation thereof.

[0038] Optionally, the chip may further include a memory for storing programs or instructions.

[0039] Optionally, the chip may also include the transceiver circuit, or an input / output interface.

[0040] Eighthly, this application provides a chip including processing circuitry for running programs or instructions to implement methods as described in the second aspect or any possible implementation thereof.

[0041] Optionally, the chip may further include a memory for storing programs or instructions.

[0042] Optionally, the chip may also include the transceiver circuit, or an input / output interface.

[0043] A ninth aspect provides a computer-readable storage medium comprising instructions that, when executed by a processor, cause the method as described in the first aspect or any possible implementation thereof to be implemented.

[0044] In a tenth aspect, this application provides a computer-readable storage medium including instructions that, when executed by a processor, cause the method as described in the second aspect or any possible implementation thereof to be implemented.

[0045] Eleventhly, this application provides a computer program product comprising computer program code or instructions that, when executed, cause the method as described in the first aspect or any possible implementation thereof to be implemented.

[0046] In a twelfth aspect, this application provides a computer program product comprising computer program code or instructions that, when executed, cause the method as described in the second aspect or any possible implementation thereof to be implemented.

[0047] In a thirteenth aspect, this application provides a communication system for performing the methods described in the first aspect or any possible implementation thereof and for performing the methods described in the second aspect or any possible implementation thereof. Attached Figure Description

[0048] Figure 1 is an exemplary structural diagram of a communication system according to an embodiment of this application;

[0049] Figures 2 to 11 are exemplary flowcharts of communication methods according to various embodiments of this application;

[0050] Figure 12 is an exemplary structural diagram of a communication device according to an embodiment of this application;

[0051] Figure 13 is an exemplary structural diagram of a communication device according to an embodiment of this application. Detailed Implementation

[0052] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0053] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0054] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0055] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and / or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0056] Figure 1 is an exemplary architecture diagram of a communication system according to an embodiment of this application. As shown in Figure 1, the communication system may include PCF, AMF, SMF, NWDAF, UE, RAN, UPF, and DN.

[0057] AMF is short for Access and Mobility Management Function (AMF) network element. AMF is mainly used to receive network slice replacement policies from PCF or to configure network slice replacement policies locally, and to determine whether the UE supports network slice replacement capabilities in order to select an appropriate network slice replacement scheme and drive the UE, RAN and core network to implement the network slice replacement process.

[0058] SMF is short for Session Management Function. SMF is primarily responsible for handling network slice replacement requests from AMF and managing Protocol Data Unit (PDU) sessions and N4 sessions during network slice replacement.

[0059] PCF is short for Policy Control Function (PCF) network element. PCF can issue service rules to SMF based on user-subscribed services (application services, location / time period, etc.), subscribe to relevant experience analysis results from NWDAF, and decide whether to issue network slice replacement policies to AMF based on whether UE supports network slice replacement capability.

[0060] UPF is short for User Plane Function (UPF) network element. UPF is mainly responsible for application service identification, responding to PCF service rules by reporting application detection and control (ADC) events to PCF through SMF, and reporting subscribed application service experience data to NWDAF.

[0061] NWDAF is short for Network Data Analytics Function (NWDAF) network element. NWDAF is primarily responsible for subscribing to application service experience data from UPF and notifying the PCF of the analysis results.

[0062] DN is short for Data Network. DN is primarily responsible for providing data for user access.

[0063] UE is short for User Equipment. In some scenarios, the UE supports network slice replacement. In other scenarios, the UE does not support network slice replacement.

[0064] RAN is short for Radio Access Network. RAN includes access network equipment.

[0065] Access network equipment is used to communicate with terminal equipment and can also be called wireless access network equipment. For example, access network equipment can be a base station.

[0066] The aforementioned network element or device may be a hardware device, or a software function running on dedicated hardware or general-purpose hardware. For example, it may be a virtualization function instantiated on a platform (e.g., a cloud platform), or it may be an entity that includes dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the aforementioned network element or device.

[0067] Figure 2 is an exemplary flowchart of a communication method according to an embodiment of this application. As shown in Figure 2, the communication method includes steps S201 to S211.

[0068] S201, Establish PDU session.

[0069] For example, when a UE registers, a PDU session is established.

[0070] This PDU session is associated with a network slice. For ease of description, the network slice associated with the PDU session at this time is referred to as the original network slice.

[0071] The UE has signed up for network slice replacement service with PCF.

[0072] PCF subscribes to experience analytics data for a specified network slice from NWDAF. This experience analytics data includes whether the network slice is available or congested. For example, PCF sends a subscription message to NWDAF that carries the network slice ID.

[0073] As an example, the ID of the network slice is Single Network Slice Selection Assistance Information (S-NSSAI).

[0074] S202, PCF uses experience analysis data of subscribed network slices to decide whether to issue a network slice replacement policy to AMF. The network slices subscribed to by PCF include the original network slices.

[0075] For example, when the PCF determines, based on subscription experience analysis data, that the original network slice cannot meet the UE's service requirements, it will issue a network slice replacement policy to the AMF.

[0076] As an example, a network slice replacement policy includes the identifier of the original network slice, the identifier of the new network slice, and the status of the original network slice. The status of the original network slice may include whether it is available or congested. The network slice replacement policy can also be called network slice replacement information. The new network slice can be called the replaced network slice.

[0077] S203, the PCF sends the network slice replacement policy to the AMF. Correspondingly, the AMF receives the network slice replacement policy.

[0078] In S204, the AMF decision will switch the original network slice of the current PDU session of a UE that supports the network slice replacement feature to a replacement network slice. The UE that supports the network slice replacement feature can be referred to as the supporting UE.

[0079] For example, when the original network slice in the network slice replacement policy is unavailable or congested, the AMF can determine the first information, which indicates that the original network slice associated with the PDU session should be switched to the replacement network slice.

[0080] Once AMF has determined the first piece of information, it can determine whether the UE supports the network slice replacement feature and identify UEs that support the network slice replacement feature as supporting UEs.

[0081] S205, the AMF sends a UE configuration update message to the UE. Correspondingly, the UE receives the UE configuration update message.

[0082] As an example, the UE Configuration Update message carries the identifier of the network slice to be replaced and the identifier of the allowed network slice, with the identifier of the allowed network slice containing the identifier of the network slice to be replaced.

[0083] The UE configuration update message includes a replacement network slice identifier to inform the UE to switch the PDU session to the replacement network slice. The UE configuration update message also includes an allowed network slice identifier containing the replacement network slice identifier to let the UE know that the replacement network slice is an allowed network slice, so that the UE can access the replacement network slice normally after switching the PDU session to the replacement network slice.

[0084] After receiving the UE configuration update message, the UE updates its own configuration based on the UE configuration update message.

[0085] S206, the AMF sends a PDU session update session management context message to the SMF. Correspondingly, the SMF receives this PDU session update session management context message. This message requests the SMF to update the PDU session. The message carries first information.

[0086] As an example, the PDU session update session management context (Nsmf_PDUSession_UpdateSMContext) message carries the identifier of the original network slice and the identifier of the replacement network slice, that is, it requests SMF to switch the PDU session from the original network slice to the replacement network slice.

[0087] S207, the SMF initiates an N4 session modification message to the UPF. Correspondingly, the UPF receives the N4 session modification message.

[0088] N4 session modification messages can also be called packet forwarding control policy (PFCP) session modification messages.

[0089] As an example, during the execution of PDU session modification, SMF sends an N4 session modification request to UPF with an S-NSSAI value assigned to Alternative S-NSSAI.

[0090] Alternatively, the SMF sends an N4 session modification message to the UPF, which carries the identifier of the network slice as the identifier of the replacement network slice, that is, it requests to update the PDU session to the replacement network slice and requests to modify the N4 session.

[0091] S208, SMF requests AMF to initiate a PDU session modification request to RAN and UE.

[0092] As an example, after the SMF completes the PDU session update and N4 session modification, it sends a Namf_Communication_N1N2MessageTransfer message to the AMF, triggering the AMF to initiate a PDU session resource modification request message to the RAN and a PDU session modification command to the UE. The network slice identifier carried in the message and command is assigned the value of the identifier of the replacement network slice.

[0093] The Namf_Communication_N1N2MessageTransfer message contains N2SmInformation information, which may include an identifier for replacing network slices.

[0094] S209, the AMF sends a PDU session resource modification request message to the RAN. Correspondingly, the RAN receives this PDU session resource modification request message. This PDU session resource modification request message is used to request the RAN to modify the network slice resources associated with the PDU session.

[0095] As an example, after parsing the N2SmInformation information, the AMF sends a PDU session resource modification request message to the RAN. The message specifies the ID of the PDU session to be modified and the identifier of the replacement network slice, that is, it requests to modify the network slice resources associated with the PDU session to the resources on the replacement network slice.

[0096] S210, the AMF sends a PDU session modification command to the UE. The UE then receives the PDU session modification command.

[0097] As an example, the AMF sends a PDU Session Modification Command to the UE, instructing the UE to modify the network slice for the specified PDU session.

[0098] The PDU session modification command can carry the identifier of the PDU session and the identifier of the replacement network slice, that is, request to modify the network slice resource associated with the PDU session to the resource on the replacement network slice.

[0099] S211, RAN reallocates resources for replacing network slices for PDU sessions.

[0100] As an example, the RAN reallocates resources for the replacement network slice for the PDU session and updates the N3 tunnel with the UPF. In this way, subsequent application services from the UE are transmitted uplink and downlink over the replacement network slice.

[0101] However, the communication method in this embodiment has the following problem: in scenarios where the UE does not support the network slice replacement feature, at least steps S204 and thereafter will not be executed, which will result in the UE's service experience not being guaranteed.

[0102] To address the aforementioned issues, this application provides a new communication method that can also improve the guarantee of the UE's service experience.

[0103] In the novel communication method provided in this application, the RAN can reallocate and replace network slice resources for PDU sessions, and update the N3 tunnel between the RAN and UPF. In this way, at least the network slice resources associated with the PDU session between the RAN and UPF can be updated, ensuring the transmission of subsequent application services for the UE.

[0104] Figure 3 is an exemplary flowchart of a communication method according to an embodiment of this application. As shown in Figure 3, the communication method includes steps S310 and S320.

[0105] S310, AMF determines whether the terminal supports the network slice replacement feature.

[0106] The network slice replacement feature is used to temporarily replace the currently used network slice with another network slice to ensure service experience when the currently used network slice is unavailable or congested.

[0107] In some implementations, when the terminal supports the network slice replacement feature, the terminal indicates that it supports the network slice replacement feature in the Mobility Management Capability (MM Capability) information reported to the AMF during the registration process.

[0108] In this implementation, the AMF can determine whether a terminal supports network slice replacement based on indications in the mobility management capability information. Specifically, if the terminal's mobility management capability information does not indicate support for network slice replacement, then it can be determined that the terminal does not support network slice replacement.

[0109] In some implementations, regardless of whether the terminal supports the network slice replacement feature, the Mobility Management Capability (MM Capability) information reported by the terminal to the AMF during the registration process indicates the terminal's network slice replacement feature capability. Specifically, if the terminal supports the network slice replacement feature, the MM Capability information indicates that the terminal supports the network slice replacement feature; if the terminal does not support the network slice replacement feature, the MM Capability information indicates that the terminal does not support the network slice replacement feature.

[0110] In this implementation, AMF can directly determine whether a terminal supports network slice replacement features based on indications from mobility management capability information.

[0111] S320, if the terminal does not support the network slice replacement feature, the AMF determines to send first information to the SMF, the first information indicating that the first network slice associated with the protocol data unit session should be replaced with the second network slice.

[0112] In this embodiment, the first network slice can be referred to as the original network slice, and the second network slice can be referred to as the replacement network slice.

[0113] In some implementations, the first information includes the original network slice's S-NSSAI and the alternative network slice's Alternative S-NSSAI, which is used to request the SMF to implement network slice updates for the PDU session.

[0114] In some implementations, the first information can be called the network slice replacement strategy, or in other words, the first information can be carried in the network slice replacement strategy.

[0115] In this embodiment, the AMF determines whether the terminal supports the network slice replacement feature. Even if the terminal does not support the network slice replacement feature, it still instructs the SMF to update the original network slice associated with the PDU session to a replacement network slice. This differs from the AMF only instructing the SMF to update the original network slice associated with the PDU session to a replacement network slice when the terminal supports the network slice replacement feature, and not sending such an instruction to the SMF when the terminal does not support the feature. This ensures that services on the PDU session between the RAN and UPF network elements are updated to the replacement network slice, thereby guaranteeing the transmission performance of services between the RAN and UPF network elements and ultimately ensuring a better service experience.

[0116] In this embodiment, whether it is necessary to switch the original network slice associated with the PDU session to a replacement network slice can be determined by the AMF itself based on the locally configured network slice replacement policy, or it can be indicated by other network elements (such as PCF), or it can be determined based on the network slice replacement policy sent by other network elements (such as PCF).

[0117] In this embodiment, after the AMF learns the first information, namely that it needs to switch the original network slice associated with the PDU session to a replacement network slice, it can determine whether to implement end-to-end (e.g., UE to DN) network slice replacement or RAN to UPF network slice replacement based on whether the UE supports the network slice replacement feature.

[0118] For example, if the UE supports the network slice replacement feature, then end-to-end network slice replacement can be determined; if the UE does not support the network slice replacement feature, then network slice replacement from RAN to UPF can be determined.

[0119] To achieve end-to-end network slice replacement, the AMF can send first information to the SMF and a UE configuration update message to the UE. After receiving the SMF's PDU session update request, the AMF can send a PDU session resource modification request message to the RAN and a PDU session modification command to the UE to achieve end-to-end network slice replacement.

[0120] To achieve network slice replacement from RAN to UPF, AMF can send first information to SMF, and upon receiving the SMF's PDU session update request, can send an instruction PDU session resource modification request message to RAN to complete the network slice replacement from RAN to UPF. AMF may choose not to send UE configuration update messages or PDU session modification commands to the UE.

[0121] In some implementations of this embodiment, as shown in Figure 4, step S325 may also be included, whereby after the AMF determines that it will send the first information to the session management function network element, the AMF sends the first information to the SMF. Correspondingly, the SMF receives the first information.

[0122] As an example, S325 can be referred to S206, which will not be repeated here.

[0123] In some implementations of this embodiment, when the AMF determines that the terminal does not support the network slice replacement feature, it does not send a UE configuration update message to the UE, for example, it does not perform steps similar to S205.

[0124] In some implementations of this embodiment, step S330 may also be included, whereby the SMF initiates an N4 session modification message to the UPF. Correspondingly, the UPF receives the N4 session modification message.

[0125] As an example, S330 can be referenced from S207, which will not be repeated here.

[0126] In some implementations of this embodiment, step S335 may also be included, whereby the SMF sends second information to the AMF. This second information triggers the sending of third information to the access network device and fourth information to the terminal. The third information indicates that the network slice associated with the PDU should be replaced with the second network slice, and the fourth information indicates that the network slice associated with the PDU should be replaced with the second network slice. Correspondingly, the AMF receives the second information.

[0127] The second message is used to trigger the sending of the third message to the access network device and the fourth message to the terminal. It can also be understood as: the second message is used to request the AMF to send the third message to the access network device and the fourth message to the terminal.

[0128] As an example, S335 can refer to S208. For example, the second information is N2SmInformation information, the third information is the information carried in the PDU session resource modification request message in S209, and the fourth information is the information carried in the PDU session modification command in S210.

[0129] In some implementations of this embodiment, the method may further include: if the terminal does not support the network slice replacement feature, determining not to send the fourth information to the terminal. That is, if the terminal does not support the network slice replacement feature, even if the AMF receives the second information from the SMF, the AMF will not send the fourth information to the UE to save signaling overhead. For example, steps similar to S210 may not be performed.

[0130] In some implementations of this embodiment, S340 may also be included, whereby the AMF sends a PDU session resource modification request message to the RAN.

[0131] As an example, S340 can refer to S209.

[0132] In some implementations of this embodiment, step S345 may also be included, whereby the RAN reallocates resources for replacing network slices for the PDU session. As an example, step S345 can be referenced to step S211.

[0133] In some implementations of this embodiment, step S322 may also be included, whereby after the AMF determines to switch the original network slice associated with the PDU session to the replacement network slice, it sends fifth information to the access network device. The fifth information indicates a list of network slices allowed by the access network device, and the list of network slices includes the second network slice. This ensures that after the RAN receives the instruction to switch the original network slice associated with the PDU session to the replacement network slice, it can successfully and normally implement the network slice replacement.

[0134] For example, the AMF carries the RAN's allowed network slice identifier through the UE INFORMATION TRANSFER message, which contains the identifier for replacing the network slice.

[0135] It is understandable that if the UE supports the network slice replacement feature, the AMF can send the fifth information to the access network device after determining that the original network slice associated with the PDU session has been switched to the replacement network slice. In other words, regardless of whether the UE supports the network slice replacement feature, the AMF can send the fifth information to the access network device after determining that the original network slice associated with the PDU session has been switched to the replacement network slice. This ensures that after the RAN receives the indication information to switch the original network slice associated with the PDU session to the replacement network slice, it can normally or successfully complete the network slice replacement.

[0136] As an example, when the RAN has slice admission control enabled, the AMF will only send the fifth message to the RAN after determining that the original network slice associated with the PDU session will be switched to the replacement network slice.

[0137] It is understandable that S322 can be located before S325 or after S325.

[0138] In some implementations of this embodiment, step S309 may also be included, whereby the PCF sends network slice replacement information to the AMF, and correspondingly, the AMF receives the network slice replacement information from the PCF. Alternatively, the network slice replacement information for the AMF is sent by the PCF. After receiving the network slice replacement information, the AMF can determine the first information based on the network slice replacement information.

[0139] As an example, S309 can refer to S203.

[0140] In some implementations of this embodiment, as shown in FIG5, S301 to S304 and S306 to S308 may also be included.

[0141] S301, Establish PDU session.

[0142] This step can be referenced in S201.

[0143] S302, PCF sends ADC dynamic rules to UPF through SMF.

[0144] As an example, the ADC dynamic rule specifies the application services that need to be detected.

[0145] As an example, after a UE that has signed up for the network slice replacement service with PCF initially establishes a PDU session for a network slice, PCF, based on the service policy configuration, sends ADC dynamic rules for specific application services to UPF through SMF.

[0146] S303, UPF detects packets of application services specified in the ADC dynamic rules.

[0147] S304, UPF reports the ADC trigger event to SMF.

[0148] As an example, UPF reports application detection information through the PFCP Session Report.

[0149] S306, the SMF sends an ADC trigger message to the PCF, indicating that a specified application service has been detected. Correspondingly, the PCF receives the ADC trigger message.

[0150] As an example, the SMF reports to the PCF via the Npcf_SMPolicyControl_Update message in the N7 session, where the PolicyControlRequestTrigger is APP_STA, thereby informing the PCF that the current UE has started using the application services specified in the ADC rules.

[0151] S307, PCF subscribes to NWDAF for experience analysis data of application services.

[0152] As an example, after receiving an ADC event notification, PCF subscribes to the NWDAF for experience analysis data of the application service through the Nnwdaf_AnalyticsSubscription_Subscribe message. The subscription message may include the ID of the application and the ID of the original network slice.

[0153] S308, PCF uses experience analysis data from subscribed application services to decide whether to issue a network slice replacement policy to AMF.

[0154] This step can be referenced in S202.

[0155] It is understandable that steps S302 to S308 may be performed only partially or in full, or similar operations may be performed. For example, S302 may be omitted, and the ADC dynamic rules may be configured in other ways. For example, S307 may be omitted; the PCF receives the seventh information, which indicates that the original network slice is unavailable or congested. In S308, the PCF decides whether to send network slice replacement information to the AMF based on the seventh information.

[0156] In this embodiment, when the UPF detects a specified application service, it sends an ADC trigger event to the PCF through the SMF, triggering the PCF to obtain the experience analysis data of the application service. This allows the PCF to determine whether the network slice associated with the application service needs to be replaced based on the experience analysis data of the application service. This helps to achieve network switching and replacement at the application service granularity, thereby helping to ensure the experience at the application service granularity.

[0157] As you can understand, Figures 3 to 5 illustrate the slice replacement process when the AMF determines that the UE does not support the network slice replacement feature. The following describes the slice replacement process when the AMF determines that the UE supports the network slice replacement feature.

[0158] When the AMF determines that the UE supports the network slice replacement feature, as an example, S204 of the embodiment shown in Figure 2 can be replaced as follows: The AMF decides whether to switch the original network slice of the UE's current PDU session to the replacement network slice based on whether the terminal supports the network slice replacement feature. If the terminal supports the network slice replacement feature, it decides to switch the original network slice of the UE's current PDU session to the replacement network slice, that is, to execute S205 and subsequent steps. If the terminal does not support the network slice replacement feature, it decides to switch the resources used between the RAN and UPF for transmitting the UE's current PDU session from the original network slice to the replacement network slice, that is, at least S206, S207, S208, S209 and S211 can be executed.

[0159] Figure 6 shows an example of the communication process when AMF determines that the UE supports the network slice replacement feature. The differences between the process shown in Figure 6 and the process shown in Figure 5 include the steps corresponding to the dashed boxes and dashed arrows in Figure 6.

[0160] Specifically, S321 in Figure 6 is different from S320 in Figure 5; the process shown in Figure 6 also includes S343; optionally, the process shown in Figure 6 also includes S323.

[0161] S321, if the terminal supports the network slice replacement feature, the AMF determines to send the first information to the SMF, send the UE configuration update message to the UE, and send the PDU session modification command to the UE.

[0162] S323, the AMF sends a UE configuration update message to the UE. Correspondingly, the UE receives the UE configuration update message.

[0163] This step can be referenced in S205.

[0164] S343, the AMF sends a PDU session modification command to the UE. The UE then receives the PDU session modification command.

[0165] This step can be referenced from S210.

[0166] In the embodiments of this application, when the AMF determines that the UE supports the network slice replacement feature, it can realize end-to-end network slice replacement, thereby better ensuring the service experience.

[0167] In some examples of this application, optionally, the AMF is locally configured with a network slice replacement policy. In this case, the AMF can determine the first information based on the locally configured network slice replacement policy.

[0168] An example of a locally configured network slice replacement policy in AMF includes triggering network slice replacement if the UE's current location is within a specific Tracking Area Indication (TAI) list location area. Optionally, replaceable network slices can be specified in the locally configured network slice replacement policy.

[0169] In some examples, if the AMF has a network slice replacement policy configured locally, it can also receive a network slice replacement policy from the PCF. In this case, if the AMF receives a network slice replacement policy from the PCF, it determines the first information based on the network slice replacement policy indicated by the PCF; if the AMF does not receive a network slice replacement policy from the PCF, it can determine the first information based on the locally configured network slice replacement policy. This better ensures the service experience.

[0170] Figure 7 illustrates an exemplary slice replacement process when the AMF has a locally configured network slice replacement policy and determines that the UE does not support the network slice replacement feature. The difference between the process shown in Figure 7 and the process shown in Figure 4 includes the steps corresponding to the dashed boxes in Figure 7.

[0171] S310-1, AMF determines the first information based on the locally configured network slice replacement policy.

[0172] Figure 8 shows an exemplary slice replacement process when the AMF has a locally configured network slice replacement policy and determines that the UE supports the network slice replacement feature. The differences between the process shown in Figure 8 and the process shown in Figure 7 include the steps corresponding to the dashed boxes and dashed arrows in Figure 8.

[0173] The above describes how the AMF determines whether the UE supports the network slice replacement feature, and based on the determination result, decides whether to execute an end-to-end network slice handover procedure or an RAN-to-UPF network slice handover procedure. In some embodiments provided in this application, the PCF can determine whether the UE supports the network slice replacement feature and, based on the determination result, decide whether to instruct the AMF to execute the network slice handover procedure. Compared to the AMF, the PCF-based solution for determining whether the UE supports the network slice replacement feature has the advantage of allowing user-level network slice replacement decisions and ensuring user-level service experience because the PCF can access each user's subscription information.

[0174] In some implementations, the AMF sends a sixth message to the PCF, which indicates whether the terminal supports the network slice replacement feature.

[0175] As an example, the sixth piece of information is carried in the UE's mobility management capability information.

[0176] In some implementations, the PCF determines whether the UE supports the network slice replacement feature. If the PCF determines that the UE supports the network slice replacement feature, the PCF sends network slice replacement information to the AMF.

[0177] Figure 9 shows an exemplary network slice replacement process when the PCF determines that the UE supports the network slice replacement feature. This example differs from the example shown in Figure 6 in that it includes S308-1; and it does not include S310 and S320.

[0178] S308-1, PCF determines whether UE supports network slice replacement feature. If PCF determines that UE supports network slice replacement feature, then PCF determines to send network slice replacement information to AMF.

[0179] Another exemplary network slice replacement process when the PCF determines that the UE supports the network slice replacement feature is shown in Figure 10. This example differs from the example shown in Figure 9 in that Figure 10 also includes steps S310 and S321. With both the PCF and AMF making decisions, dual assurance can be provided for the service experience.

[0180] In some implementations, if the PCF determines that the UE does not support the network slice replacement feature, the PCF will not send the first information to the AMF.

[0181] In scenarios where the PCF determines whether the UE supports the network slice replacement feature, in some implementations, the AMF has a network slice replacement policy configured locally.

[0182] In some implementations where the AMF has a locally configured network slice replacement policy, if the PCF determines that the UE does not support the network slice replacement feature, the PCF sends an eighth message to the AMF. The eighth message instructs the AMF to determine whether to perform network slice replacement based on the locally configured network slice replacement policy.

[0183] The details of AMF's implementation of the network slice replacement process based on the locally configured network slice replacement policy can be found in the aforementioned content.

[0184] In a scenario where the PCF determines whether the UE supports the network slice replacement feature, and the AMF has a network slice replacement policy configured locally, an exemplary network slice replacement process is shown in Figure 11. Figure 11 illustrates the communication flow when the UE supports the network slice replacement feature. If the UE does not support the network slice replacement feature, then S321 in Figure 11 can be replaced with S320, S323 and S343 can be omitted, and S346 can be replaced with S345.

[0185] Figure 12 is a schematic diagram of the structure of a communication device according to an embodiment of this application. As shown in Figure 12, the communication device 1200 may include a processing module 1201 and a communication module 1202.

[0186] As an example, the communication device 1200 can be used to implement the steps performed by the AMF in any of the foregoing method embodiments. For example, the processing module 1201 is used to implement the processing-related steps performed by the AMF in any of the foregoing method embodiments, and the communication module 1202 is used to implement the sending and / or receiving steps performed by the AMF in any of the foregoing method embodiments.

[0187] As another example, the communication device 1200 can be used to implement the steps performed by the PCF in any of the foregoing method embodiments. For example, the processing module 1201 is used to implement the processing-related steps performed by the PCF in any of the foregoing method embodiments, and the communication module 1202 is used to implement the sending and / or receiving steps performed by the PCF in any of the foregoing method embodiments.

[0188] Figure 13 is a schematic diagram of a communication device provided in another embodiment of this application. As shown in Figure 13, the communication device 1300 includes a processor 1301 and a communication circuit 1302. The processor 1301 and the communication circuit 1302 are coupled to each other. It is understood that the communication circuit 1302 can be a transceiver or an input / output interface. Optionally, the communication device 1300 may also include a memory 1303 for storing instructions executed by the processor 1301, or storing input data required by the processor 1301 to execute instructions, or storing data generated after the processor 1301 executes instructions. It is understood that the memory 1303 can be located outside the processor 1301, or inside the processor 1301.

[0189] As an example, processor 1301 is used to implement the functions of the processing module 1201, and communication circuit 1302 is used to implement the functions of the communication module 1202.

[0190] The communication device 1300 can be an AMF or a chip used in an AMF.

[0191] It is understandable that when the communication device 1300 is an AMF (Advanced Feature Module), the communication circuit 1302 can be a transceiver. When the communication device 1300 is a chip, the communication circuit 1302 can be an input / output interface.

[0192] The communication device 1300 can be a PCF or a chip used in a PCF.

[0193] It is understandable that when the communication device 1300 is a PCF, the communication circuit 1302 can be a transceiver. When the communication device 1300 is a chip, the communication circuit 1302 can be an input / output interface.

[0194] Some embodiments of this application also provide a computer program product that, when run on a processor, can implement the methods implemented by AMF in any of the above embodiments.

[0195] Some embodiments of this application also provide a computer program product that, when run on a processor, can implement the method implemented by the PCF in any of the above embodiments.

[0196] In some embodiments of this application, a computer-readable storage medium is also provided, which contains computer instructions that, when executed on a processor, can implement the methods implemented by the AMF in any of the above embodiments.

[0197] In some embodiments of this application, a computer-readable storage medium is also provided, which contains computer instructions that, when executed on a processor, can implement the methods implemented by the PCF in any of the above embodiments.

[0198] In some embodiments of this application, a communication system is also provided, which can implement the methods implemented by AMF and PCF in any of the above method embodiments.

[0199] It is understood that the processor in the embodiments of this application may be any of the following devices or all or part of the circuitry used for processing functions: a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0200] The method steps or functions in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which 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 disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a network device or terminal device. Alternatively, the processor and storage medium can exist as discrete components in the network device or terminal device.

[0201] The steps or functions in the above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented, in whole or in part, 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 this application are executed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can 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 can 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 can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive.

[0202] In the various embodiments of this application, unless otherwise specified or in case of 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.

[0203] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, Applied to network elements for access and mobility management functions, the method includes: Determine whether the terminal supports the network slice replacement feature; If the terminal does not support the network slice replacement feature, it determines to send first information to the session management function network element, the first information indicating that the first network slice associated with the protocol data unit session be replaced with the second network slice.

2. The method according to claim 1, characterized in that, The method further includes: The system receives a second message, which triggers the sending of a third message to the access network device and a fourth message to the terminal. The third message indicates that the network slice associated with the protocol data unit session should be replaced with the second network slice, and the fourth message indicates that the network slice associated with the protocol data unit session should be replaced with the second network slice. If the terminal does not support the network slice replacement feature, it is determined not to send the fourth information to the terminal.

3. The method according to claim 2, characterized in that, The method further includes: A fifth message is sent to the access network device, the fifth message indicating a list of network slices allowed by the access network device, the list of network slices including the second network slice.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first information is determined based on the local configuration policy.

5. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Receive network slice replacement information from the policy control function network element, and determine the first information based on the network slice replacement information.

6. The method according to claim 5, characterized in that, The method further includes: The sixth information is sent to the policy control function network element, and the sixth information is used to indicate whether the terminal supports the network slice replacement feature.

7. The method according to claim 6, characterized in that, The sixth piece of information is carried in the mobility management capability information of the terminal.

8. A communication method, characterized in that, The method, applied to policy control function network elements, includes: The terminal receives sixth information from the access and mobility management function network element, the sixth information being used to indicate whether the terminal supports network slice replacement features; If the terminal supports the network slice replacement feature, it determines to send network slice replacement information to the access and mobility management function network element.

9. The method according to claim 8, characterized in that, Before sending network slice replacement information to the access and mobility management function network element, the method further includes: The system receives an application detection and control trigger message and / or a seventh message indicating that the first network slice is unavailable. The application service associated with the application detection and control trigger message is transmitted through the protocol data unit session.

10. The method according to claim 8 or 9, characterized in that, The method further includes: If the terminal does not support the network slice replacement feature, it is determined not to send the first information to the access and mobility management function network element.

11. A communication device, characterized in that, The communication device includes a module for performing the method of any one of claims 1 to 7, or includes a module for performing the method of any one of claims 8 to 10.

12. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1 to 7, or to implement the method as described in any one of claims 8 to 10, through logic circuits or executing code instructions.

13. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 7, or implement the method as described in any one of claims 8 to 10.

14. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the communication device, they implement the method as described in any one of claims 1 to 7, or implement the method as described in any one of claims 8 to 10.

15. A communication system, characterized in that, It includes: a communication device for implementing the method as described in any one of claims 1 to 7, and a communication device for implementing the method as described in any one of claims 8 to 10.

Images