Communication method and communication device

Abstract

The present application provides a communication method and an apparatus for providing a solution for non-3GPP path switching in a multi-access session. The method includes: a session management device determines to perform a non-3GPP transmission path switching in a multi-access session, the multi-access session including at least two non-3GPP transmission paths, the session management device sends a first offload rule to a user plane device and / or sends a second offload rule to a terminal device, the first offload rule is for supporting the user plane device in determining a first target transmission path from the at least two 3GPP transmission paths, and the second offload rule is for supporting the terminal device in determining a second target transmission path from the at least two non-3GPP transmission paths. According to the method, when it is determined to perform a non-3GPP path switching, the UE and the UPF can select an appropriate path from multiple non-3GPP access paths for data transmission in a switching process based on the new offload rule to ensure service continuity during the session switching.

Description

[Technical Field]

[0001] The present application relates to the field of communication technologies, and in particular to communication methods and devices. [Background technology]

[0002] In the communication transmission process, the service flow data to be transmitted is usually transmitted by establishing a multi-access PDU session (MA PDU session) across a 3rd Generation Partnership Project (3GPP) access network (path) and a non-3GPP access network (path) to improve transmission efficiency.

[0003] However, existing multi-access session technologies only support transmission across one 3GPP access network (route) and one non-3GPP access network (route), but do not support transmission across two or more access networks (routes). For example, in a multi-access session scenario, when transmission across at least two non-3GPP access networks (routes) is required, multiple non-3GPP routes coexist to implement non-3GPP route switching. As a result, the user equipment (UE) and user plane function (UPF) cannot effectively offload service data during the switchover, resulting in service interruptions and affecting the user experience.

[0004] Currently, there is no method to support non-3GPP route switching in multi-access session scenarios. Summary of the Invention

[0005] The present application provides a solution for non-3GPP route switching in multi-access sessions, and provides a communication method and a communication device to better support offloading of service flow data, ensure communication continuity, and reduce system overhead.

[0006] According to a first aspect, there is provided a communication method. The method may be executed by a session management device or a chip having similar functionality to that of the session management device. In the method, the session management device determines to perform non-3GPP transmission path switching in a multi-access session, where the multi-access session includes at least two non-3GPP transmission paths. The session management device then transmits a first offload rule to a user plane device and / or a second offload rule to a terminal device, where the first offload rule is for supporting the user plane device in determining a first target transmission path from the at least two non-3GPP transmission paths, and the second offload rule is for supporting the terminal device in determining a second target transmission path from the at least two non-3GPP transmission paths.

[0007] In this embodiment, the first target transmission path may be one or more of a plurality of non-3GPP transmission paths.

[0008] In addition, if no non-3GPP transmission path is available, the first target transmission path in the embodiment of the present application may alternatively not include a non-3GPP transmission path.

[0009] The second target transmission path may be one or more of a plurality of non-3GPP transmission paths. In addition, if none of the non-3GPP transmission paths is available, the second target transmission path in this embodiment of the present application may alternatively not include a non-3GPP transmission path.

[0010] In this embodiment of the present application, the first offload rule is for supporting a user plane device in determining a first target transmission path from at least two non-3GPP transmission paths, which may mean that when a non-3GPP transmission path is implemented, the user plane device may determine the transmission path by using the first offload rule. Similarly, the second offload rule is for supporting a terminal device in determining a second target transmission path from at least two non-3GPP transmission paths, which may mean that when a non-3GPP transmission path is implemented, the user plane device may determine the transmission path by using the second offload rule.

[0011] In this embodiment, the multi-access session management procedure may be a multi-access session establishment procedure, a multi-access session modification procedure, a multi-access session attachment procedure, a multi-access session release procedure, a multi-access session activation procedure, or the like.

[0012] According to the above solution, when it is determined that a non-3GPP transmission path switching is to be performed in the multipath session switching procedure, the terminal equipment and the user plane equipment activate an offload rule that supports multiple non-3GPP transmission paths in the switching process. For example, the activated offload rule supports the UE and / or the UPF in selecting an appropriate transmission path from multiple non-3GPP transmission paths for data transmission, thereby allowing service data to be effectively offloaded and ensuring service continuity during the session switching.

[0013] If possible, the session management device determines to perform a non-3GPP transmission path switch in the multi-access session based on a received session request message, where the session request message includes switch instruction information indicating that a non-3GPP transmission path switch is to be performed and / or indicating that the established target transmission path is a non-3GPP transmission path. The session request message is a first session request message sent by a terminal device after the terminal device has decided to perform a non-3GPP transmission path. Alternatively, the session request message is a second session request message sent by a mobility management device after the mobility management device has decided to perform a non-3GPP transmission path.

[0014] In this embodiment, the first session request message may be a session establishment request message, or the first session request message may be a session modification request message, or the like, which is not limited herein.

[0015] The second session request message may be a create session context message, or the second session request message may be a session update session context message, or the like, which is not limited herein.

[0016] Based on the above solution, an embodiment of the present application provides a method for a session management device to determine whether to perform non-3GPP transmission path switching. For example, the session management device may determine whether to perform non-3GPP transmission path switching based on a received session request message.

[0017] If possible, if the switching instruction information indicates that the established target transmission path is a non-3GPP transmission path, and if the session management equipment determines that the established source transmission path of the multi-access session is a non-3GPP transmission path, the session management equipment decides to perform a non-3GPP path switching based on the session request.

[0018] Where possible, the session request message further includes a session identifier of the multi-access session, which session identifier is used to determine the multi-access session of the terminal equipment.

[0019] Where possible, the session request message further includes a session context identifier of the multi-access session, the session context identifier being used to determine the multi-access session of the terminal equipment.

[0020] Where possible, the primary off-road rules include: an offload rule used by the user plane equipment before non-3GPP path switching, and access priority indication information, where the access priority indication information indicates a first target transmission path.

[0021] The second off-road rule includes: an offloading rule used by the terminal device before non-3GPP path switching, and access priority indication information, where the access priority indication information indicates a second target transmission path.

[0022] In this embodiment, the access priority information may be a type of radio access technology (RAT). If the RAT type is trusted non-3GPP access, it indicates that the non-3GPP transmission path of the user plane equipment is a trusted non-3GPP path. If the RAT type is untrusted non-3GPP access, it indicates that the non-3GPP transmission path of the user plane equipment is an untrusted non-3GPP path. If the RAT type is 3GPP access, it indicates that all non-3GPP transmission paths of the user plane equipment are migrated to 3GPP transmission paths.

[0023] Where possible, the first target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path; and The second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.

[0024] In a possible case, when a non-3GPP transmission path switching is performed, the source non-3GPP transmission path before the switching may be an untrusted non-3GPP transmission path, and the target non-3GPP transmission path after the switching may be a trusted non-3GPP transmission path. When a non-3GPP transmission path switching is performed, the source non-3GPP transmission path before the switching may be a trusted non-3GPP transmission path, and the target non-3GPP transmission path after the switching may be an untrusted non-3GPP transmission path.

[0025] In a possible case, the first offload rule includes a third offload rule, where the third offload rule instructs the user plane equipment to perform redundant transmission over at least two non-3GPP transmission paths.

[0026] Where possible, the second offload rule includes a fourth offload rule, where the fourth offload rule instructs the terminal device to perform redundant transmission over at least two non-3GPP transmission paths.

[0027] Where possible, the first offload rule includes an offload rule used by the user plane equipment before a non-3GPP path switch, a third offload rule, and a rule application condition, where the third offload rule instructs the user plane equipment to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offload rule is to be applied when a path switch is performed.

[0028] If possible, the second offload rule includes an offload rule used by the terminal device before a non-3GPP path switch, a fourth offload rule, and a rule application condition, where the fourth offload rule instructs the terminal device to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offload rule is to be applied when a path switch is performed.

[0029] According to a second aspect, a communication method is provided. The method may be executed by a terminal device or a chip having similar functions to those of the terminal device. In the method, the terminal device determines to perform non-3GPP transmission path switching in a multi-access session, where the multi-access session includes at least two non-3GPP transmission paths. The terminal device sends a first session request message to a session management device, where the first session request message includes switching instruction information indicating that non-3GPP transmission path switching is to be performed and / or indicating that an established target transmission path is a non-3GPP transmission path. The terminal device receives a second offload rule sent by the session management device, where the second offload rule is for supporting the terminal device in determining a second target transmission path from the at least two non-3GPP transmission paths. The terminal device determines the transmission path based on the second offload rule.

[0030] In this embodiment, the second target transmission path may be one or more of a plurality of non-3GPP transmission paths. In addition, if any of the non-3GPP transmission paths is not available, the second target transmission path in this embodiment of the present application may alternatively not include a non-3GPP transmission path.

[0031] The second offload rule is for supporting the terminal device in determining a second target transmission path from at least two non-3GPP transmission paths, which may mean that when a non-3GPP transmission path is implemented, the user plane equipment may determine the transmission path by using the second offload rule.

[0032] In this embodiment, the multi-access session management procedure may be a multi-access session establishment procedure, a multi-access session modification procedure, a multi-access session attachment procedure, a multi-access session release procedure, a multi-access session activation procedure, or the like.

[0033] According to the above solution, when it is determined that a non-3GPP transmission path switching is to be performed in the multipath session switching procedure, the terminal equipment and the user plane equipment activate an offload rule that supports multiple non-3GPP transmission paths in the switching process. For example, the activated offload rule supports the UE and / or the UPF in selecting an appropriate transmission path from multiple non-3GPP transmission paths for data transmission, thereby allowing service data to be effectively offloaded and ensuring service continuity during the session switching.

[0034] In a possible implementation, the first session request message further includes a multi-access session identifier, which is for determining a multi-access session of the terminal device.

[0035] In a possible implementation, the second offload rule includes an offload rule used by the terminal equipment before non-3GPP path switching, and access priority indication information, where the access priority indication information indicates the second target transmission path.

[0036] In a possible implementation, the second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.

[0037] In a possible implementation, the second offload rule includes a fourth offload rule, where the fourth offload rule instructs the terminal device to perform redundant transmission over at least two non-3GPP transmission paths.

[0038] In a possible implementation, the second offload rule includes an offload rule used by the terminal device before a non-3GPP path switch, a fourth offload rule, and a rule application condition, where the fourth offload rule instructs the terminal device to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offload rule is to be applied when a path switch is performed.

[0039] According to a third aspect, there is provided a communication method, which may be executed by a user plane device or a chip having similar functions to those of the user plane device, in which, when a non-3GPP transmission path switching is performed in a multi-access session, the user plane device receives a first offload rule sent by a session management device, where the first offload rule is for supporting the user plane device in determining a first target transmission path from at least two non-3GPP transmission paths, the multi-access session includes at least two non-3GPP transmission paths, and the user plane device determines the transmission path based on the first offload rule.

[0040] In this embodiment, the first target transmission path may be one or more of a plurality of non-3GPP transmission paths.

[0041] In addition, if no non-3GPP transmission path is available, the first target transmission path in this embodiment of the present application may alternatively not include a non-3GPP transmission path.

[0042] The second target transmission path may be one or more of a plurality of non-3GPP transmission paths. In addition, if none of the non-3GPP transmission paths is available, the second target transmission path in this embodiment of the present application may alternatively not include a non-3GPP transmission path.

[0043] In this embodiment of the present application, the first offload rule is for supporting the user plane equipment in determining a first target transmission path from at least two non-3GPP transmission paths, which may mean that when implementing a non-3GPP transmission path, the user plane equipment may determine a transmission path by using the first offload rule.

[0044] In this embodiment, the multi-access session management procedure may be a multi-access session establishment procedure, a multi-access session modification procedure, a multi-access session attachment procedure, a multi-access session release procedure, a multi-access session activation procedure, or the like.

[0045] According to the above solution, when it is determined that a non-3GPP transmission path switching is to be performed in the multipath session switching procedure, the terminal equipment and the user plane equipment activate an offload rule that supports multiple non-3GPP transmission paths in the switching process. For example, the activated offload rule supports the UE and / or the UPF in selecting an appropriate transmission path from multiple non-3GPP transmission paths for data transmission, thereby allowing service data to be effectively offloaded and ensuring service continuity during the session switching.

[0046] In a possible implementation, the first offload rule includes: an offload rule used by the user plane equipment before non-3GPP path switching, and access priority indication information, where the access priority indication information indicates a first target transmission path.

[0047] In a possible implementation, the first target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.

[0048] In a possible implementation, the first offload rule includes: Third offload rule: Wherein the third offload rule instructs the user plane equipment to perform redundant transmission over at least two non-3GPP transmission paths.

[0049] In a possible implementation, the first offload rule includes: an offload rule, a third offload rule, and a rule application condition to be used by the user plane equipment before a non-3GPP path switch, where the third offload rule instructs the user plane equipment to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offload rule is to be applied when a path switch is performed.

[0050] According to a fourth aspect, there is provided a communication method. The method may be executed by a mobility management device or a chip having similar functions to those of the mobility management device. In the method, the mobility management device determines to perform a non-3GPP transmission path switch in a multi-access session, where the multi-access session includes at least two non-3GPP transmission paths. The mobility management device sends a second request message to a session management device, where the second request message includes switch instruction information indicating that a non-3GPP transmission path switch is to be performed and / or indicating that an established target transmission path is a non-3GPP transmission path. The mobility management device receives a second offload rule sent by the session management device, where the second offload rule is for supporting a terminal device in determining a second target transmission path from the at least two non-3GPP transmission paths. The mobility management device then sends the second offload rule to the terminal device.

[0051] In this embodiment, the second target transmission path may be one or more of a plurality of non-3GPP transmission paths. In addition, if any of the non-3GPP transmission paths is not available, the second target transmission path in this embodiment of the present application may alternatively not include a non-3GPP transmission path.

[0052] The second offload rule is for supporting the terminal device in determining a second target transmission path from at least two non-3GPP transmission paths, which may mean that when a non-3GPP transmission path is implemented, the user plane equipment may determine the transmission path by using the second offload rule.

[0053] In this embodiment, the multi-access session management procedure may be a multi-access session establishment procedure, a multi-access session modification procedure, a multi-access session attachment procedure, a multi-access session release procedure, a multi-access session activation procedure, or the like.

[0054] According to the above solution, when it is determined that a non-3GPP transmission path switching is to be performed in the multipath session switching procedure, the terminal equipment and the user plane equipment activate an offload rule that supports multiple non-3GPP transmission paths in the switching process. For example, the activated offload rule supports the UE and / or the UPF in selecting an appropriate transmission path from multiple non-3GPP transmission paths for data transmission, thereby allowing service data to be effectively offloaded and ensuring service continuity during the session switching.

[0055] In a possible implementation, the second request message further includes a multi-access session identifier, the multi-access session identifier being for determining a multi-access session of the terminal equipment.

[0056] In a possible implementation, the second request message further includes a multi-access session context identifier, the multi-access session context identifier being for determining the multi-access session of the terminal device.

[0057] In a possible implementation, the second offload rule includes an offload rule used by the terminal equipment before non-3GPP path switching, and access priority indication information, where the access priority indication information indicates the second target transmission path.

[0058] In a possible implementation, the second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.

[0059] In a possible implementation, the second offload rule includes a fourth offload rule, where the fourth offload rule instructs the terminal device to perform redundant transmission over at least two non-3GPP transmission paths.

[0060] In a possible implementation, the second offload rule includes: a fourth offloading rule, where the fourth offloading rule instructs a terminal device to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offloading rule is applied when a path switch is performed.

[0061] In a possible implementation, the mobility management device decides to perform a non-3GPP transmission path switch based on a received non-access stratum message sent by the terminal device to request a path switch, where the non-access stratum message includes switch instruction information, which indicates that a non-3GPP transmission path switch is to be performed and / or indicates that the established target transmission path is a non-3GPP transmission path.

[0062] In a possible implementation, the method further includes:

[0063] In the process of performing non-3GPP path switching, the mobility management device determines that a first condition for releasing a signaling connection is met, and the mobility management device releases the signaling connection of the terminal device on the target non-3GPP transmission path or the source non-3GPP transmission path.

[0064] In this embodiment, the release of the signaling connection may be the release of the access network signaling, or the deregistration of the terminal device, or the like, which is not limited in this specification.

[0065] According to the above-mentioned method, the mobility management device determines whether to release the signaling connection of the terminal device on the target path or the source path by determining whether the terminal device will be used for subsequent session switching during registration. This effectively avoids the case where the terminal device maintains a double registration state for the trusted non-3GPP path and the untrusted non-3GPP path for a long time. In addition, MA PDU session switching on the non-3GPP path can also be supported.

[0066] In a possible implementation, the first condition for releasing the signaling connection includes:

[0067] After the terminal device completes the registration of the target non-3GPP transmission path, a first timer started by the mobility management device expires, where the first timer is configured to indicate that the signaling connection of the source non-3GPP transmission path is to be released. Alternatively, after the terminal device completes the registration of the target non-3GPP transmission path, a second timer started by the mobility management device expires, where the terminal device does not complete the switching of the target non-3GPP transmission path, where the second timer is configured to indicate that the signaling connection of the target non-3GPP transmission path is to be released.

[0068] In a possible implementation, the method further includes:

[0069] After determining that the terminal device has completed the non-3GPP transmission path switching, the mobility management device sends a third request message to the session management device, where the third request message indicates applying an offload rule used by the terminal device and / or the user plane device before the non-3GPP transmission path switching.

[0070] According to a fifth aspect, there is provided a communication method, which may be executed by a mobility management device or a chip having similar functions to those of the mobility management device, in which the mobility management device determines, in a process of performing a non-3GPP path switch, that a first condition for releasing a signaling connection is met, and the mobility management device releases the signaling connection of the terminal device on the target non-3GPP transmission path or the source non-3GPP transmission path.

[0071] In this embodiment, the release of the signaling connection may be the release of the access network signaling, or the deregistration of the terminal device, or the like, which is not limited in this specification.

[0072] According to the above-mentioned method, the mobility management device determines whether to release the signaling connection of the terminal device on the target path or the source path by determining whether the terminal device will be used for subsequent session switching during registration. This effectively avoids the case where the terminal device maintains a double registration state for the trusted non-3GPP path and the untrusted non-3GPP path for a long time. In addition, MA PDU session switching on the non-3GPP path can also be supported.

[0073] In a possible implementation, the first condition for releasing the signaling connection includes:

[0074] After the terminal device completes the registration of the target non-3GPP transmission path, a first timer started by the mobility management device expires, where the first timer is configured to indicate that the signaling connection of the source non-3GPP transmission path is to be released. Alternatively, after the terminal device completes the registration of the target non-3GPP transmission path, a second timer started by the mobility management device expires, where the terminal device does not complete the switching of the target non-3GPP transmission path, where the second timer is configured to indicate that the signaling connection of the target non-3GPP transmission path is to be released.

[0075] According to a sixth aspect, an embodiment of the present application provides a communication device. The device may be a session management device or a chip used in the session management device. The device has a function for implementing any of the implementation methods in the first aspect. The function may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0076] According to a seventh aspect, an embodiment of the present application provides a communication device, which may be a terminal device, or a chip or module used in a terminal device, for example, a smart mobile terminal, a smart home device, a smart car, or a smart wearable device.

[0077] The smart mobile terminal is, for example, a mobile phone, a tablet computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA). The smart home device is, for example, a smart refrigerator, a smart washing machine, a smart TV, or a speaker. The wearable device for an intelligent automobile is, for example, a smart headset, smart glasses, smart clothing, or smart shoes. The device has a function for implementing any of the methods described in the second aspect. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0078] According to an eighth aspect, an embodiment of the present application provides a communication device. The device may be a UPF or a chip or module used in a UPF. The device has a function for implementing any of the methods described in the third aspect. The function may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0079] According to a ninth aspect, an embodiment of the present application provides a communication device. The device may be a mobility management device, or a chip or module used in the mobility management device. The device has a function for implementing any of the methods described in the fourth aspect. The function may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0080] According to a tenth aspect, an embodiment of the present application provides a communication device. The device may be a mobility management device, or a chip or module used in the mobility management device. The device has a function for implementing any of the methods described in the fifth aspect. The function may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0081] According to an eleventh aspect, an embodiment of the present application provides a communications device comprising a processor and a memory, the memory configured to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory to enable the device to perform any of the methods of the first to fifth aspects.

[0082] According to a twelfth aspect, an embodiment of the present application provides a communication device, comprising units or means for performing the steps of any of the methods according to the first to fifth aspects.

[0083] According to a thirteenth aspect, an embodiment of the present application provides a communication device including a processor and an interface circuit, wherein the processor is configured to: communicate with another device through the interface circuit; and perform any of the methods of the first to fifth aspects. There may be one or more processors.

[0084] According to a fourteenth aspect, an embodiment of the present application provides a communication device including a processor coupled to a memory. The processor is configured to invoke a program stored in the memory to perform any of the methods described in the first to fifth aspects. The memory may be located internally or externally to the device. In addition, there may be one or more processors.

[0085] According to a fifteenth aspect, an embodiment of the present application further provides a computer-readable storage medium having stored thereon instructions that, when executed on a communication device, perform any of the methods of the first to fifth aspects.

[0086] According to a sixteenth aspect, an embodiment of the present application further provides a computer program product, the computer program product including computer programs or instructions that, when executed by a communication device, perform any of the methods in the first to fifth aspects.

[0087] According to a seventeenth aspect, an embodiment of the present application further provides a chip system including a processor configured to execute any of the implementation methods in the first to fifth aspects.

[0088] According to an eighteenth aspect, an embodiment of the present application further provides a communication system including the communication device according to the sixth aspect to the communication device according to the ninth aspect. Optionally, the communication system further includes the communication device according to the tenth aspect.

[0089] For the technical advantages that can be achieved by the various design solutions in the sixth to eighteenth aspects, please refer to the descriptions of the technical advantages of the corresponding solutions in the first to fifth aspects, and these will not be described again in detail herein. [Brief explanation of the drawings]

[0090] [Figure 1] 1 is a diagram illustrating a multi-access session system according to the prior art. [Figure 2] FIG. 1 illustrates a first multi-access session scenario according to an embodiment of the present application. [Figure 3] FIG. 10 illustrates a second multi-access session scenario according to an embodiment of the present application. [Figure 4] FIG. 10 illustrates a third multi-access session scenario according to an embodiment of the present application. [Figure 5] FIG. 10 illustrates a fourth multi-access session scenario according to an embodiment of the present application. [Figure 6] 1 illustrates a communication path switching system according to an embodiment of the present application; [Figure 7] 1 is a schematic flow chart illustrating a communication path switching method according to an embodiment of the present application; [Figure 8A] 4 is a schematic flow chart illustrating a first case for path switching according to an embodiment of the present application; [Figure 8B] 4 is a schematic flow chart illustrating a first case for path switching according to an embodiment of the present application; [Figure 8C] 4 is a schematic flow chart illustrating a first case for path switching according to an embodiment of the present application; [Figure 9] 10 is a schematic flow chart illustrating a second case for path switching according to an embodiment of the present application; [Figure 10] 10 is a schematic flow chart illustrating a third case for path switching according to an embodiment of the present application; [Figure 11] FIG. 2 illustrates a first communication path switching device according to an embodiment of the present application; [Figure 12] FIG. 2 illustrates a second communication path switching device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0091] In order to facilitate understanding of the technical solutions provided in the embodiments of the present application, the following describes technical terms used in the present application.

[0092] (1) Types of non-3GPP access: Forms of non-3GPP access include, for example, untrusted non-3GPP access technologies that access the core network via private wireless access points, trusted non-3GPP access technologies that access the core network via wireless access points deployed by carriers, and wireline access technologies.

[0093] Non-3GPP access technologies include wireless communication technologies (Wi-Fi), Bluetooth (registered trademark), ZigBee, or the like. The non-3GPP access network equipment may include a non-3GPP interworking function (N3IWF), a trusted non-3GPP gateway function (TNGF), a trusted non-3GPP access point (TNAP), a trusted wireless local area network interworking function (TWIF), and a wireline access gateway function (W-AGF). The W-AGF may also be referred to as an AGF. If the access technology is an untrusted non-3GPP access technology, the non-3GPP access network equipment corresponding to the untrusted non-3GPP access technology may include an N3IWF. The network topology structure of the N3IWF corresponds to a radio access network (RAN) in a 3GPP access network, and an N2 interface and an N3 interface may be supported. If the access technology is a trusted non-3GPP access technology, the non-3GPP access network equipment corresponding to the trusted non-3GPP access technology may include a TNGF, whose network topology structure corresponds to the RAN in a 3GPP access network and can support an N2 interface and an N3 interface.

[0094] In one example, an untrusted non-3GPP access point may be an access point deployed by a non-carrier, such as a Wi-Fi access point (AP) deployed at home or by an operator. A trusted non-3GPP access point may be an access point deployed by a carrier and may be referred to as a trusted non-3GPP access point (TNAP).

[0095] (2) Multi-access Session (MA PDU Session): A multi-access session is used by the UE and / or UPF for transmission across a 3GPP access network (which may also be understood as a 3GPP access path) and a non-3GPP access network (which may also be understood as a non-3GPP access path) to improve transmission efficiency.

[0096] For example, a user plane channel may include two access network devices (a 3GPP access network device and a non-3GPP access network device) that are connected to the same UPF (or connected to the same UPF via different UPFs). For example, a UE may send uplink data to the UPF via the RAN and / or N3IWF, and the UPF may send downlink data to the UE via the RAN and / or N3IWF.

[0097] (3) Offloading rules: Offloading rules indicate how to transmit data to be transmitted over 3GPP access network paths and / or non-3GPP access network paths.

[0098] Currently, in a communication transmission process, service flow data to be transmitted is typically transmitted by establishing a multi-access PDU session (MA PDU session) across a 3GPP access network (path) and a non-3GPP access network (path) to improve transmission efficiency. For example, as shown in FIG. 1, a user plane channel may include two access network devices (a 3GPP access network device and a non-3GPP access network device). The two access network devices are connected to the same UPF (or connected to the same UPF via different UPFs). The UE may transmit uplink data to the UPF via a Radio Access Network (RAN) and / or a non-3GPP interworking function (N3IWF), and the UPF may transmit downlink data to the UE via the RAN and / or N3IWF.

[0099] However, existing multi-access session technologies only support transmission across one 3GPP access network (route) and one non-3GPP access network (route), and do not support transmission across two or more routes. Specifically, when transmission across two or more routes is performed in a multi-access session scenario, the UE and UPF cannot effectively offload service data, which may result in service interruptions and affect user experience.

[0100] For example, existing multi-access session technologies do not support a configuration in which a multi-access session is performed across at least two non-3GPP routes for transmission, as shown in FIG. 2, where the at least two non-3GPP routes include a trusted non-3GPP route and an untrusted non-3GPP route. As another example, existing multi-access session technologies do not support a configuration in which a multi-access session is performed across at least two 3GPP routes for transmission, as shown in FIG. 3. As another example, existing multi-access session technologies do not support a configuration in which a multi-access session is performed across one 3GPP route and at least two non-3GPP routes for transmission, as shown in FIG. 4. As another example, existing multi-access session technologies do not support a configuration in which a multi-access session is performed across at least two 3GPP routes and one non-3GPP route for transmission, as shown in FIG. 5.

[0101] In addition, in the current scenario where a multi-access session is performed over at least two non-3GPP routes for transmission, multiple N3GPP routes coexist due to N3GPP route switching. As a result, it is not possible to support offloading of service flow data during the switching process. Also, due to network requirements, only one route may be allowed to be retained after the switching is completed. However, after the registration of the target route is completed, the existing UE often fails to complete the switching procedure on time or does not proactively trigger deregistration of the original route after the switching procedure is completed. As a result, the UE remains in a dual-registration state in the network for a long time, and the UE is unable to obtain services from the network.

[0102] Therefore, it is necessary to solve how to support offloading of service flow data in the N3GPP route switching process in multi-access sessions, ensure communication continuity, and reduce system overhead.

[0103] Based on this, the embodiment of the present application implements N3GPP path switching in a multi-access session, and in order to better ensure communication continuity, the embodiment of the present application provides a non-3GPP path switching method.

[0104] It should be noted that the multi-access session management procedure in the embodiments of the present application may be a multi-access session establishment procedure, a multi-access session modification procedure, a multi-access session attachment procedure, a multi-access session release procedure, a multi-access session activation procedure, or the like, which is not limited herein.

[0105] 6 illustrates a simplified architecture of non-3GPP path switching in a multi-access session according to an embodiment of the present invention. The communication system may include a terminal device 600, an access and mobility management function (AMF) network element 610, a session management function (SMF) network element 620, and a user plane function (UPF) network element 630.

[0106] The terminal device 600 may also be referred to as user equipment (UE), a mobile station, a mobile terminal, or the like. In FIG. 6, the UE corresponds to a terminal. The terminal can be widely used in various scenarios, such as device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable devices, smart transportation, and smart cities. The terminal can be a mobile phone, a tablet computer, a computer with a wireless transceiver function, a wearable device, a vehicle, an unmanned aerial vehicle, a helicopter, an aircraft, a ship, a robot, a robotic arm, a smart home device, or the like. The specific technology used by the terminal and the specific device form are not limited in the embodiments of the present application.

[0107] Specifically, in an embodiment of the present application, the terminal equipment may be configured to: Determine to perform non-3GPP transmission path switching in a multi-access session, send a first session request message to a session management device, receive a second offload rule sent by the session management device, and determine a transmission path based on the second offload rule.

[0108] The AMF 610 is configured to perform mobility management, access authentication / authorization, and the like. In addition, the access and mobility management function network element is further responsible for forwarding user policies to the terminal.

[0109] Specifically, in embodiments of the present application, the AMF may be configured to: Determine to perform non-3GPP transmission path switching in the multi-access session, send a second request message to the session management device, receive a second offload rule sent by the session management device, and send the second offload rule to the terminal device.

[0110] The SMF 620 is configured to perform session management, control policy enforcement, user plane function network element selection, internet protocol (IP) address allocation for terminals, and the like.

[0111] Specifically, in embodiments of the present application, the SMF may be configured to: determining to perform a non-3GPP transmission path switch in the multi-access session, and sending a first offload rule to the user plane equipment and / or sending a second offload rule to the terminal equipment;

[0112] The UPF 630 is configured to perform user plane data forwarding, session / flow level billing statistics, bandwidth limiting, and the like.

[0113] Specifically, in an embodiment of the present application, the UPF may be configured to: When non-3GPP transmission path switching in a multi-access session is performed, a first offload rule sent by the session management device is received, and a transmission path is determined based on the first offload rule.

[0114] The above-mentioned multi-access session includes at least two non-3GPP transmission paths, and the first session request message includes switch instruction information, which indicates that a non-3GPP transmission path switch is to be performed and / or indicates that the established target transmission path is a non-3GPP transmission path.

[0115] The first offloading rule is for supporting a user plane device in determining a first target transmission path from at least two non-3GPP transmission paths, and the second offloading rule is for supporting a terminal device in determining a second target transmission path from at least two non-3GPP transmission paths.

[0116] Furthermore, in the embodiment of the present application, the first target transmission path may be one or more of a plurality of non-3GPP transmission paths, and the second target transmission path may be one or more of a plurality of non-3GPP transmission paths.

[0117] In addition, if any of the non-3GPP transmission paths is unavailable, the first target transmission path in the embodiment of the present application may alternatively not include a non-3GPP transmission path.Similarly, if any of the non-3GPP transmission paths is unavailable, the second target transmission path in the embodiment of the present application may alternatively not include a non-3GPP transmission path.

[0118] In an embodiment of the present application, the first offload rule is for supporting a user plane device in determining a first target transmission path from at least two non-3GPP transmission paths, which may mean that when a non-3GPP transmission path is implemented, the user plane device may determine the transmission path by using the first offload rule. Similarly, the second offload rule is for supporting a terminal device in determining a second target transmission path from at least two non-3GPP transmission paths, which may mean that when a non-3GPP transmission path is implemented, the user plane device may determine the transmission path by using the second offload rule.

[0119] Optionally, the communication system may further include another network element, another network, or the like. For example, the communication system may further include a unified data management (UDM) network element, a policy control function (PCF) network element, and a network DN located outside the carrier network, which is not limited herein.

[0120] The following provides a communication path switching method according to an embodiment of the present application. Figure 7 is an exemplary flowchart of the communication method according to an embodiment of the present application. The communication method may include the following operations. The embodiment shown in Figure 7 may be applied to a communication system in a multi-session access scenario in which at least two non-3GPP paths exist, such as the communication system shown in Figure 6.

[0121] S701: The SMF decides to perform a non-3GPP transmission path switch in a multi-access session, where the multi-access session includes at least two non-3GPP transmission paths.

[0122] In this embodiment of the present application, the SMF may determine whether to perform a non-3GPP path switch in several aspects.

[0123] Determination method 1: The SMF receives a first session request message from the UE and determines to perform non-3GPP path switching based on the first session request message.

[0124] The first session request message may be a session establishment request message or a session modification request message, which is not limited herein.

[0125] For example, if the first session request message includes first switching instruction information, the SMF decides to perform non-3GPP path switching based on the first switching instruction information, and the first switching instruction information indicates that non-3GPP transmission path switching is to be performed and / or indicates that the established target transmission path is a non-3GPP transmission path.

[0126] If the first switching instruction message indicates that the established target transmission path is a non-3GPP transmission path, and if the SMF determines that the established source transmission path of the multi-access session is a non-3GPP transmission path, the SMF decides to perform a non-3GPP transmission path switch based on the session request.

[0127] Furthermore, in this embodiment of the present application, the first session request message may further include a session identifier of the multi-access session, where the session identifier is for determining the multi-access session of the terminal device.

[0128] Decision method 2: The SMF receives a second session request message from the AMF and decides to perform non-3GPP path switching based on the second session request message.

[0129] The second session request message may be a session creation session context message or a session update session context message, which is not limited in this specification.

[0130] For example, if the second session request message includes second switching instruction information, the SMF decides to perform non-3GPP path switching based on the second switching instruction information, and the second switching instruction information indicates that non-3GPP transmission path switching is to be performed and / or indicates that the established target transmission path is a non-3GPP transmission path.

[0131] If the second switching instruction message indicates that the established target transmission path is a non-3GPP transmission path, and if the SMF determines that the established source transmission path of the multi-access session is a non-3GPP transmission path, the SMF decides to perform a non-3GPP transmission path switch based on the session request.

[0132] Further, in this embodiment of the present application, the second session request message may further include a session identifier and / or a session context identifier of the multi-access session, the session identifier being for determining the multi-access session of the terminal device.

[0133] The second session request message may be sent by the AMF after the AMF decides to perform a non-3GPP transmission path switch in the multi-access session.

[0134] For example, after receiving a non-access stratum (NAS) message sent by a terminal device to request a path switch and deciding to perform a non-3GPP transmission path switch in a multi-access session, the AMF triggers the transmission of a second session request message to the SMF, where the NAS message includes a switch indication, which indicates that a non-3GPP transmission path switch is to be performed and / or indicates that the established target transmission path is a non-3GPP transmission path.

[0135] S702: The SMF sends the first offload rule to the UPF and / or sends the second offload rule to the UE.

[0136] The first offload rule is for supporting a user plane device in determining a first target transmission path from at least two non-3GPP transmission paths, and the second offload rule is for supporting a terminal device in determining a second target transmission path from at least two non-3GPP transmission paths.

[0137] In one example, when sending a second offload rule to a UE, the SMF may send the second offload rule to the corresponding UE through the AMF.

[0138] In one example, the SMF sending the first offload rule to the corresponding UPF may be performed by sending an N4 session modification request carrying the first offload rule to the UPF.

[0139] Furthermore, in this embodiment of the present application, the first offload rule and / or the second offload rule, which are for performing transmission path switching, may have multiple types of content, which are not particularly limited to the following types:

[0140] Content type 1: The first offload rule and / or the second offload rule include the offload rule used before the non-3GPP path switching (the original offload rule for the transmission path switching) and access priority indication information indicating the execution of the non-3GPP path switching.

[0141] The access priority indication information indicates a target transmission path. In an embodiment of the present application, the target transmission path may be one or more of a plurality of non-3GPP transmission paths. In addition, if any of the non-3GPP transmission paths is not available, the target transmission path may alternatively not include a non-3GPP transmission path.

[0142] For example, the first offload rule includes an offload rule to be used by the user plane equipment before a non-3GPP path switch and access priority indication information.

[0143] The second offload rule includes an offload rule used by the terminal device before non-3GPP path switching and access priority indication information.

[0144] Content Type 2: The first offload rule and / or the second offload rule includes an offload rule that supports non-3GPP path switching, and the offload rule for the non-3GPP path switching is different from the original offload rule for the path switching.

[0145] For example, the first offload rule includes a third offload rule, where the third offload rule instructs the user plane equipment to perform redundant transmission over at least two non-3GPP transmission paths.

[0146] The second offloading rule includes a fourth offloading rule, and the fourth offloading rule instructs the terminal device to perform redundant transmission over at least two non-3GPP transmission paths.

[0147] Content type 3: The first offload rule and / or the second offload rule include an offload rule that supports non-3GPP path switching, an original offload rule for path switching, and a trigger condition corresponding to the offload rule.

[0148] For example, the first offload rule includes an offload rule used by the user plane equipment before a non-3GPP path switch, a third offload rule, and a rule application condition, where the third offload rule instructs the user plane equipment to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offload rule is to be applied when a path switch is performed.

[0149] The second offload rule includes an offload rule used by the terminal device before non-3GPP path switching, a fourth offload rule, and a rule application condition, where the fourth offload rule instructs the terminal device to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offload rule is to be applied when path switching is performed.

[0150] Based on the above content types 1 to 3, some types of actual content that can be indicated by the first offload rule and the second offload rule are listed as follows:

[0151] The first offload rule and / or the second offload rule instruct the UPF to switch a service flow transmitted over a source non-3GPP transmission path to a target non-3GPP transmission path for transmission.

[0152] If the source non-3GPP transmission path is an untrusted non-3GPP transmission path, the target non-3GPP transmission path may be a trusted non-3GPP transmission path. If the source non-3GPP transmission path is a trusted non-3GPP transmission path, the target non-3GPP transmission path may be an untrusted non-3GPP transmission path.

[0153] Additionally, if the multi-access session further includes a 3GPP transmission path, the first offload rule may further instruct the UPF to switch the service flow transmitted over the source non-3GPP transmission path to the target 3GPP transmission path for transmission, and the second offload rule may further instruct the UE to switch the service flow transmitted over the source non-3GPP transmission path to the target 3GPP transmission path for transmission.

[0154] The first offload rule and / or the second offload rule are determined based on a local configuration before the SMF sends the first offload rule to the UPF and / or the second offload rule to the UE, or the first offload rule and / or the second offload rule are determined based on a policy and charging control (PCC) rule obtained from the PCF before the SMF sends the first offload rule to the UPF and / or the second offload rule to the UE.

[0155] In addition, in order to better meet the requirements of the network, complete the switching procedure in a timely manner, and avoid the case where the UE maintains a dual registration state in the network for a long time and the case where the UE cannot obtain service from the network, in this embodiment of the present application, after the switching of the non-3GPP path is completed, the release of the signaling connection of the source non-3GPP transmission path may be further triggered.

[0156] In the embodiment of the present application, the release of the signaling connection may be the release of the access network signaling or the deregistration of the terminal equipment.

[0157] In one example, in the process of performing a non-3GPP path switch, the AMF determines that a first condition for releasing a signaling connection is met.

[0158] For example, after determining that the UE has completed switching from a trusted non-3GPP path to an untrusted non-3GPP path, the AMF triggers the release of the trusted non-3GPP path.

[0159] As another example, after determining that the UE has completed switching from an untrusted non-3GPP path to a trusted non-3GPP path, the AMF triggers the release of the untrusted non-3GPP path.

[0160] Specifically, the first condition in this embodiment of the present application is not particularly limited to the following several cases.

[0161] Case 1: After the terminal device completes registration of the target non-3GPP transmission path, a first timer started by the AMF expires, where the first timer is configured to indicate that the signaling connection of the source non-3GPP transmission path is to be released.

[0162] For example, when the UE performs a non-3GPP path switch, after determining that the UE has completed registration of the first target transmission path, the AMF starts a source path deregistration timer. After determining that the source path deregistration timer has expired, the AMF initiates a deregistration request to the UE.

[0163] Case 2: After the terminal device completes the registration of the target non-3GPP transmission path, the second timer started by the AMF expires, and the terminal device does not complete the switching of the target non-3GPP transmission path, where the second timer is configured to indicate that the signaling connection of the target non-3GPP transmission path is to be released.

[0164] For example, when the UE performs a non-3GPP path switch, after determining that the UE has completed registration of the first target transmission path, the AMF starts a target path deregistration timer. After determining that the target path deregistration timer has expired, the AMF initiates a deregistration request to the UE.

[0165] Case 3: After the AMF receives a signaling disconnection request message from the UE, the AMF initiates a deregistration request to the UE, where the signaling disconnection request message indicates to the AMF to initiate a deregistration request to the UE for the target path or the source path.

[0166] To better explain the communication path switching method provided in the present application, the following two path switching scenarios will be further described in detail based on the contents shown in FIG.

[0167] Some steps in the following path switching method may be optional, and the step sequence does not represent an actual execution sequence. Therefore, the present application is not limited to being performed completely according to the following steps and sequences. In addition, the following two path switching scenarios may be combined for application, which is not limited in this specification.

[0168] Scenario 1: Performing route switching based on the first offload rule and / or the second offload rule provided in this application.

[0169] Please refer to Figures 8A to 8C. The following steps may be performed in a manner corresponding to Scenario 1. Before the procedure starts, it is assumed that the UE has established an MA PDU session via a trusted non-3GPP gateway function (TNGF). In addition, registration has been completed via a non-3GPP interworking function (N3IWF) and an internet protocol security (IPSec) security signaling plane connection between the UE and the N3IWF has been established.

[0170] S801: The UE sends a NAS message to the AMF on an untrusted non-3GPP path, where the NAS message carries a first session request message.

[0171] The first session request message may be a session establishment request message or a session modification request message.

[0172] In one example, the NAS message carries a session identifier and / or first switching instruction information, where the session identifier is for uniquely determining the session.

[0173] The first switching instruction information may be a session request type, and the request type may indicate an existing PDU session, a multi-access session request, or a new instruction identifier.

[0174] For example, the first switching instruction information indicates that a non-3GPP transmission path switching is to be performed and / or indicates that the established target transmission path is a non-3GPP transmission path.

[0175] Furthermore, in an embodiment of the present application, the session identifier and / or the first switching instruction information may be carried in the first session request message, or the session identifier may be carried in a NAS message other than the first session request message.

[0176] If the first switching instruction information is in the first session establishment request, the AMF does not detect the first switching instruction information, and the SMF directly detects the first switching instruction information.If the first switching instruction information is in a NAS message other than the first session establishment request, the AMF directly detects the instruction, and the AMF may indicate the first switching instruction information to the SMF in the subsequent step S803.

[0177] S802: The AMF selects an appropriate SMF based on the received NAS message.

[0178] Specifically, the AMF may select an appropriate SMF based on a session identifier in a received NAS message.

[0179] S803: The AMF sends a second session request message to the SMF.

[0180] In one example, after determining to perform a non-3GPP path switch based on the NAS message received from the terminal device, the AMF may send a second session request message to the SMF. The second session request message may be a session creation session context message or a session update session context message.

[0181] For example, after identifying the first switching instruction information carried in the NAS message and determining, based on the first switching instruction information, that the current session management procedure is for performing a non-3GPP transmission path switch, the AMF sends a second session request message to the SMF.

[0182] In one example, the second session request message may carry one or more of a session identifier, a session context identifier, second switching instruction information, or a radio access technology type (RAT Type).

[0183] The second switching instruction information indicates the access path type requested by the current session.

[0184] For example, the second switching instruction information indicates that a non-3GPP transmission path switching is to be performed, and / or indicates that the established target transmission path is a non-3GPP transmission path.

[0185] The AMF may directly use the first switching instruction information in the received NAS message as the second switching instruction information in the second session request message and send the second switching instruction information to the SMF.

[0186] In this case, the first switching instruction information may be understood to be the same as the second switching instruction information. Similarly, the second session request message sent by the AMF to the SMF may carry a session identifier, a session context identifier, and / or the like indicated in the NAS message. This is not limited herein.

[0187] S804: The SMF obtains subscription information of the UE from a unified data management (UDM) device based on the second session request message, where the subscription information includes session context information of the UE.

[0188] Specifically, the SMF may obtain subscription information from the UDM to the UE based on the session identifier or session context identifier in the second session request message.

[0189] S805: The SMF feeds back an update session context response message to the AMF.

[0190] S806: The SMF decides to perform non-3GPP transmission path switching in the multi-access session.

[0191] In one example, the SMF may decide to perform a non-3GPP transmission path switch based on a second session request message received from the AMF.

[0192] For example, the SMF determines to perform non-3GPP transmission path switching based on second switching instruction information included in the second session request message. In this case, the second switching instruction information indicates that non-3GPP transmission path switching is to be performed.

[0193] As another example, if the second switching instruction information indicates that the established target transmission path is a non-3GPP transmission path, and if the SMF determines that the established source transmission path of the multi-access session is a non-3GPP transmission path, the SMF decides to perform a non-3GPP path switch based on the session request.

[0194] S807: The SMF determines a first offload rule for the UPF and / or a second offload rule for the UE.

[0195] In one example, the SMF may determine the first offloading rule and / or the second offloading rule based on a local configuration, or the SMF may determine the first offloading rule and / or the second offloading rule based on a PCC rule obtained from a PCF.

[0196] The first offload rule is included in the multi-access rule (MultIPle AcceSS Rule) and is intended to support UPF in determining the first target transmission path from multiple transmission paths. A multi-access session includes at least two non-3GPP transmission paths.

[0197] The second offload rule is included in the Access Traffic Steering Switching Splitting Rule (ATSSS rule) and is intended to assist the UE in determining a second target transmission path from multiple transmission paths.

[0198] For the sake of brevity, the contents of the first off-load rule and / or the second off-load rule are referred to in the description of the related contents shown in Figure 7. The details will not be described again in this specification.

[0199] S808: The SMF selects a UPF corresponding to the multi-access session based on the local multi-access session context and initiates an N4 session modification request, where the N4 session modification request includes a first offload rule.

[0200] In one example, the first offloading rule may be carried in an N4 rule included in an N4 session modification request.

[0201] For example, in this embodiment of the present application, the N4 rules may include rules such as a Packet Detection Rule (PDR), a Forwarding Action Rule (FAR), and a Multi Access Rule (MAR), etc. The MAR rule includes the first offload rule.

[0202] S809: The UPF offloads the service data flow based on the received first offload rule.

[0203] S810: The SMF sends an N1N2 forwarding message to the AMF, where the N1N2 forwarding message includes a second offload rule.

[0204] In one example, the N1N2 forward message includes information such as a session identifier, N2 interface session management information (N2 SM Information), and an N1 interface session management container (N1 SM Container).

[0205] The N1 SM container includes session-related parameter information, such as a PDU Session Establishment Accept message and an ATSSS rule, which is the first offload rule.

[0206] S811: The AMF initiates a session request message to the N3IWF, where the session request message carries a second offload rule.

[0207] S812: The N3IWF determines the number of internet protocol security (IPSec) child SAs to be established and the quality of service (QoS) flow data to be transmitted by each IPSec child SA based on the N3IWF's policies and configuration.

[0208] S813: The N3IWF establishes an IPSec security association (SA) with the UE for user plane data transmission.

[0209] In this process, the N3IWF assigns an IP address (UP_IP_ADDRESS) of the IPSec child SA to the UE. Specifically, when the UE needs to send uplink data in the inner IP protocol stack, the destination IP address should be set to UP_IP_ADDRESS, and the source IP address is the "inner" IP address assigned during registration.

[0210] S814: After the IPSec user plane connection is completed, the N3IWF initiates a session establishment accept message to the UE, where the session establishment accept message carries the second offload rule.

[0211] S815: The N3IWF initiates an N2 session response message to the AMF to indicate that user plane resources on the N3IWF access network side have been established, where the N2 session response message carries a tunnel endpoint identifier on the N3IWF side.

[0212] S816: The AMF initiates a session update request to the SMF and forwards session-related information from the access network side.

[0213] S817: The SMF sends the access network (AN) tunnel endpoint identifier information on the N3IWF side to the UPF in the N4 session modification procedure.

[0214] S818: The SMF sends a protocol data unit (PDU) session update context response message to the AMF.

[0215] S819: After the establishment of the N3 tunnel of the untrusted non-3GPP path is completed, the AMF triggers the release of N2 resources of the source trusted non-3GPP path and initiates an N2 session resource release request to the TNGF.

[0216] S820: The TNGF initiates information exchange with the UE and deletes the session context of the UE and the TNGF on the trusted non-3GPP.

[0217] S821: TNGF sends an N2 resource release response to AMF.

[0218] S822: The AMF initiates a session update request to the SMF to indicate that session resources on the trusted non-3GPP path are being released.

[0219] In one example, if the first offload rule includes an offload rule used by the UPF before a non-3GPP path switch and / or the second offload rule includes an offload rule used by the terminal device before a non-3GPP path switch, the subsequent procedures in the solution of the present invention are not executed.

[0220] In one example, if the first offload rule does not include an offload rule used by the UPF before the non-3GPP path switch and / or the second offload rule does not include an offload rule used by the terminal device before the non-3GPP path switch, subsequent steps S823 to S829 are executed.

[0221] S823: After the switching is completed, the SMF initiates an N4 session change modification request, where the N4 session change request carries the MAR offload rule of the original MA PDU session.

[0222] The MAR offloading rule of the original MA PDU session is the offloading rule used before the non-3GPP path switch.

[0223] S824: After receiving the N4 session modification request, the UPF accepts and executes the MAR offloading rules.

[0224] After S824 is executed, the downlink data of the UE is offloaded according to the MAR offload rule.

[0225] S825: The SMF initiates an N1N2 forwarding message to the AMF, where the N1N2 forwarding message carries the ATSSS offloading rule used for the original MA PDU session.

[0226] S826: The AMF initiates a session request to the N3IWF, where the session request carries the ATSSS offload rules of the original MA PDU session.

[0227] S827: The N3IWF initiates a PDU session change instruction to the UE, where the PDU session change instruction carries the ATSSS offload rule of the original MA PDU session.

[0228] S828: After receiving the PDU session change instruction, the UE accepts and executes the ATSSS offload rule, and after completing the execution, the UE sends a PDU session change instruction response to the N3IWF.

[0229] After S828 is executed, the uplink data of the UE is offloaded according to the MAR offload rule.

[0230] S829: The N3IWF forwards the response message received from the UE to the AMF.

[0231] Scenario 1 mainly solves the problem of session continuity during handover. As can be seen from the flowchart shown in Figure 3, the overall handover procedure can be divided into four phases: UE registers the target path, an MA PDU session is established / attached on the target path, session resources on the source path are released, and the UE deregisters from the source path.

[0232] It should be noted that this embodiment uses an example in which the non-3GPP path in the MA PDU is switched from a trusted non-3GPP access path to an untrusted non-3GPP access path, and vice versa. For simplicity of description, the process of switching the non-3GPP path in the MA PDU from an untrusted non-3GPP access path to a trusted non-3GPP access path can be converted from the above content shown in Figures 8A to 8C, with only the need to replace N3IWF with TNGF. The details will not be described again in this specification.

[0233] According to the above-described embodiment, the MA PDU session switching procedure enables the UE and the UPF to activate new offloading rules in the switching process, which may support the UE and / or the UPF in selecting a suitable path from multiple non-3GPP access paths for data transmission, ensuring service continuity during the session switching.

[0234] Scenario 2: Performing a route switch based on the deregistration principles provided in this application.

[0235] In this embodiment of the present application, in scenario 2, there are multiple cases in which route switching is performed based on the deregistration principle, and these cases are not particularly limited to the following several cases.

[0236] Deregistration Case 1: Causes deregistration of the source route after the source route deregistration timer expires.

[0237] See Figure 9. The following steps may be performed in deregistration case 1. In the following Figure 9, the registration procedure in untrusted 3GPP access technology is used as an example.

[0238] S901: A UE is connected to an untrusted non-3GPP access network, and an IP address is assigned to the UE. The UE selects an N3IWF and obtains address information of the N3IWF.

[0239] S902: The UE establishes an IPSec security association (IPSec SA) with the N3IWF by initiating an initial Internet Key Exchange (IKE) exchange.

[0240] S903: The UE sends an IKE_AUTH request message to the N3IWF.

[0241] In one example, the UE may include first instruction information in the registration request message, and the first instruction information may indicate to perform a non-3GPP path switch and / or may indicate to establish a second non-3GPP transmission path.

[0242] Based on this, the first indication information may be used by the AMF to determine whether the current registration request is for a subsequent session switch. In addition, if the registration request message does not carry the first indication information, the AMF may alternatively determine whether the current registration request is for a subsequent session switch based on local configuration information upon receiving the registration request message.

[0243] S904: The N3IWF sends an IKE_AUTH response message to the UE.

[0244] The response message includes an EAP-Request / 5G-Start data packet, which may be for instructing the UE to start an EAP-5G session, for example, to start transmitting NAS messages (by encapsulating the NAS messages in EAP-5G data packets).

[0245] S905: The UE sends an IKE_AUTH request message to the N3IWF.

[0246] The request message may include an EAP-ReSponSe / 5G-NAS data packet, and the data packet may include an AN parameter and a registration request message. The AN parameter may include parameter information used by the N3IWF to select an AMF, such as a GUAMI and a selected public land mobile network (PLMN) ID (or a combination of a PLMN ID and a network identifier (NID)).

[0247] S906: The N3IWF performs AMF selection and sends a registration request message to the AMF.

[0248] In one example, if the request message sent by the UE to the N3IWF includes first indication information, the N3IWF may also forward the first indication information in the registration request message to the AMF.

[0249] S907: The AMF sends an NGAP initial connection setup request (NGAP initial context setup request) message to the N3IWF, where the NGAP initial context setup request message includes the N3IWF key.

[0250] In one example, S907 is executed after successful authentication between the AMF and the UE.

[0251] For example, the AMF selects an Authentication Server Function (AUSF) and sends an authentication request message to the AUSF, which then performs an authentication procedure on the UE and obtains authentication data from the UDM.

[0252] The authentication-related data packets may be encapsulated by using NAS messages, and the NAS messages may be encapsulated by using EAP / 5G-NAS data packets.

[0253] After authentication is complete, the AUSF sends a Security Anchor Function (Seaf) key to the AMF, which derives the NAS security key and the N3IWF security key from the key. The N3IWF key is used by the UE and the N3IWF to establish an IPSec SA.

[0254] The AMF then sends a NAS Security mode command to the UE to activate NAS security, and executes S907 after NAS security is successfully activated.

[0255] S908: The N3IWF sends extensible authentication protocol (EAP) success information to the UE.

[0256] In this case, the EAP-5G session is completed and no EAP-5G data packets are exchanged thereafter.

[0257] S909: The AMF sends an N2 message to the N3IWF, where the N2 message includes a NAS Registration Accept message to be sent to the UE.

[0258] S910: The N3IWF sends a NAS registration accept message to the UE by using the signaling IPsec SA just established.

[0259] S911: The AMF selects to start the first timer for the source route (trusted non-3GPP).

[0260] In one example, after the registration procedure is completed, the AMF determines, based on the switching instruction information or the locally configured UE registration information, that the current registration request is applicable to a subsequent session switching, and selects to start a first timer for the source path (trusted non-3GPP). The first timer is configured to release the signaling connection of the source path.

[0261] S912: When the UE performs a switching procedure between trusted non-3GPP and untrusted non-3GPP, after the first timer expires, the UE activates the AMF to release the signaling connection of the UE's source path.

[0262] For example, after the first timer expires, the AMF is activated to perform a procedure to release access network side resources on the source path, or the AMF is activated to perform a deregistration procedure for the UE on the source path.

[0263] S913: After receiving the deregistration request, the UE sends a deregistration accept message to the AMF.

[0264] S914: The AMF initiates an N2 UE context release indication for the source route (trusted non-3GPP) to the TNGF.

[0265] S915: Initiate an IKE INFORMATIONAL message between the TNGF and the UE, release the IKEv2 tunnel between the UE and the TNGF, and delete the UE context on the TNGF.

[0266] S916: The TNGF feeds back the N2 UE context to the AMF to complete the release.

[0267] According to the above embodiment, the AMF decides to start the deregistration timer on the source path by determining whether the UE will be used for subsequent session switching during registration, thereby avoiding the case where the UE maintains a dual registration state for the trusted non-3GPP path and the untrusted 3GPP path for a long time. In addition, MA PDU session switching can be performed on the non-3GPP path.

[0268] Deregistration Case 2: Causes deregistration of the target route after the target route's deregistration timer expires.

[0269] See Figure 10. The following steps may be performed in deregistration case 2. 10 In this paper, the registration procedure in untrusted 3GPP access technology is used as an example.

[0270] S1001: A UE is connected to an untrusted non-3GPP access network and is assigned an IP address. The UE selects an N3IWF and obtains address information of the N3IWF.

[0271] S1002: The UE establishes an IPSec security association (IPSec SA) with the N3IWF by initiating an Internet Key Exchange (IKE) initial exchange.

[0272] S1003: The UE sends an IKE_AUTH request message to the N3IWF.

[0273] In one example, the UE may include first instruction information in the registration request message, and the first instruction information may indicate to perform a non-3GPP path switch and / or may indicate to establish a second non-3GPP transmission path.

[0274] Based on this, the first indication information may be used by the AMF to determine whether the current registration request is for a subsequent session switch. In addition, if the registration request message does not carry the first indication information, the AMF may alternatively determine whether the current registration request is for a subsequent session switch based on local configuration information upon receiving the registration request message.

[0275] S1004: The N3IWF sends an IKE_AUTH response message to the UE.

[0276] The response message includes an EAP-Request / 5G-Start data packet, which may be intended to instruct the UE to start an EAP-5G session, e.g., to start transmitting NAS messages (by encapsulating them in EAP-5G data packets).

[0277] S1005: The UE sends an IKE_AUTH request message to the N3IWF.

[0278] The request message may include an EAP-Response / 5G-NAS data packet, and the data packet may include an AN parameter and a registration request message. The AN parameter may include parameter information used by the N3IWF to select an AMF, such as a GUAMI and a selected PLMN ID (or a PLMN ID and an NID).

[0279] S1006: The N3IWF performs AMF selection and sends a registration request message to the AMF.

[0280] In one example, if the request message sent by the UE to the N3IWF includes first indication information, the N3IWF may also forward the first indication information in the registration request message to the AMF.

[0281] S1007: The AMF sends an NGAP initial context setup request message to the N3IWF, where the NGAP initial context setup request message includes an N3IWF key.

[0282] In one example, S1007 is executed after successful authentication between the AMF and the UE.

[0283] For example, the AMF selects an AUSF and sends an authentication request message to the AUSF. The AUSF then performs an authentication procedure on the UE and obtains authentication data from the UDM. The authentication-related data packet can be encapsulated by using a NAS message, and the NAS message can be encapsulated by using an EAP / 5G-NAS data packet.

[0284] After authentication is complete, the AUSF sends the SEAF key to the AMF, which then derives the NAS security key and the N3IWF security key from the SEAF key. The N3IWF key is used by the UE and the N3IW to establish an IPSec SA.

[0285] The AMF then sends a NAS security mode command to the UE to activate NAS security, and executes S1007 after NAS security is successfully activated.

[0286] S1008: The N3IWF sends EAP-Success to the UE.

[0287] In this case, the EAP-5G session is completed and no EAP-5G data packets are exchanged thereafter.

[0288] S1009: The AMF sends an N2 message to the N3IWF, where the N2 message includes a NAS Registration Accept message to be sent to the UE.

[0289] S1010: The N3IWF sends a NAS registration accept message to the UE by using the signaling IPSec SA just established.

[0290] S1011: The AMF selects to start a second timer for the target path (trusted non-3GPP).

[0291] In one example, after the registration procedure is completed, the AMF determines, based on the switching instruction information or the locally configured UE registration information, that the current registration request is applicable to a subsequent session switching, and selects to start a second timer for the target path (trusted non-3GPP). The second timer is configured to release the signaling connection of the source path.

[0292] S1012: When the UE performs a switching procedure between trusted non-3GPP and untrusted non-3GPP, and when the second timer expires and the UE has not completed switching of the target path, the UE activates the AMF to release the signaling connection of the UE's source path.

[0293] For example, after the second timer expires, the AMF is activated to perform a procedure to release access network side resources on the target path, or the AMF is activated to perform a UE deregistration procedure on the target path.

[0294] S1013: After receiving the deregistration request, the UE sends a deregistration accept message to the AMF.

[0295] S1014: The AMF initiates an N2 UE context release indication for the target path (trusted non-3GPP) to the TNGF.

[0296] S1015: Initiate an IKE INFORMATIONAL message between the TNGF and the UE, release the IKEv2 tunnel between the UE and the TNGF, and delete the UE context on the TNGF.

[0297] S1016: The TNGF feeds back the N2 UE context to the AMF to complete the release.

[0298] According to the above embodiment, the AMF decides to start the deregistration timer on the target path by determining whether the UE is used for subsequent session switching during registration, thereby avoiding the case where the UE maintains a dual registration state for the trusted non-3GPP path and the untrusted 3GPP path for a long time. In addition, the MA PDU session switching can be performed on the non-3GPP path.

[0299] Furthermore, in this embodiment of the present application, when performing a switching procedure between trusted non-3GPP and untrusted non-3GPP, the UE may send a request message to release a signaling connection to a corresponding AMF at any time based on actual circumstances, so that the AMF that receives the request message to release a signaling connection releases the signaling connection on the target path or the source path for the UE. The request message to release a signaling connection indicates to the AMF to initiate a deregistration request of the target path or the source path for the UE.

[0300] Based on the same concept as the above-mentioned embodiments, an embodiment of the present application provides a communication device. Figures 11 and 12 are diagrams respectively showing possible configurations of a communication device according to an embodiment of the present application. The communication device may be configured to implement the functions of the SMF, UE, UPF, or AMF in the above-mentioned method embodiments, and thus can also implement the beneficial effects of the above-mentioned method embodiments. In the embodiment of the present application, the communication device may be the SMF, UE, UPF, or AMF, or may be a module (e.g., a chip) used for the SMF, UE, UPF, or AMF.

[0301] 11, the communication device 1100 includes a processing unit 1110 and a transceiver unit 1120. The communication device 1100 is configured to implement the functions of the SMF, UE, UPF, or AMF in the embodiments of the methods shown in FIGS.

[0302] When the communication device 1100 is configured to implement the functionality of an SMF, the processing unit 1110 is configured to determine whether to perform a non-3GPP transmission path switch in a multi-access session, where the multi-access session includes at least two non-3GPP transmission paths. The transceiver unit 1120 is configured to send a first offload rule to a user plane equipment and / or a second offload rule to a terminal equipment, where the first offload rule is for supporting the user plane equipment in determining a first target transmission path from the at least two non-3GPP transmission paths, and the second offload rule is for supporting the terminal equipment in determining a second target transmission path from the at least two non-3GPP transmission paths.

[0303] In one design, processing unit 1110 is specifically configured to: Determine to perform a non-3GPP transmission path switch in a multi-access session based on a received session request message, where the session request message includes switch instruction information, and the switch instruction information indicates that a non-3GPP transmission path switch is to be performed and / or indicates that the established target transmission path is a non-3GPP transmission path; and The session request message is a first session request message sent by a terminal device after the terminal device determines to execute a non-3GPP transmission path, or a second session request message sent by a mobility management device after the mobility management device determines to execute a non-3GPP transmission path.

[0304] In one design, processing unit 1110 is specifically configured to: If the switching instruction information indicates that the established target transmission path is a non-3GPP transmission path, and if it is determined that the established source transmission path of the multi-access session is a non-3GPP transmission path, determine to perform non-3GPP path switching based on the session request.

[0305] In one design, the session request message further includes a session identifier of the multi-access session, the session identifier for determining the multi-access session of the terminal device.

[0306] In one design, the session request message further includes a session context identifier of the multi-access session, the session context identifier for determining the multi-access session of the terminal device.

[0307] In one design, the first off-load rule includes: an offload rule used by the user plane equipment before non-3GPP path switching, and access priority indication information, where the access priority indication information indicates a first target transmission path.

[0308] In one design, the second off-load rule includes: an offloading rule to be used by the terminal device before non-3GPP path switching, and access priority indication information, where the access priority indication information indicates a second target transmission path;

[0309] In one design, the first target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path, and the second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.

[0310] In one design, the first off-load rule includes: Third offload rule: Wherein the third offload rule instructs the user plane equipment to perform redundant transmission over at least two non-3GPP transmission paths.

[0311] In one design, the second off-load rule includes: A fourth offloading rule, where the fourth offloading rule instructs a terminal device to perform redundant transmission over at least two non-3GPP transmission paths.

[0312] In one design, the first off-load rule includes: an offloading rule, a third offloading rule, and a rule application condition to be used by the user plane equipment before a non-3GPP path switch, where the third offloading rule instructs the user plane equipment to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offloading rule is to be applied when a path switch is performed.

[0313] In one design, the second off-load rule includes: an offloading rule, a fourth offloading rule, and a rule application condition to be used by the terminal device before a non-3GPP path switch, where the fourth offloading rule instructs the terminal device to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offloading rule is to be applied when a path switch is performed.

[0314] When the communication device 1100 is configured to implement a terminal device function, the processing unit 1110 is configured to determine execution of a non-3GPP transmission path switch in a multi-access session, where the multi-access session includes at least two non-3GPP transmission paths. The transceiver unit 1120 is configured to send a first session request message to a session management device, where the first session request message includes switch instruction information, and the switch instruction information indicates that a non-3GPP transmission path switch is to be executed and / or indicates that the established target transmission path is a non-3GPP transmission path. The transceiver unit 1120 is further configured to receive a second offload rule sent by the session management device, where the second offload rule is for supporting the terminal device in determining a second target transmission path from the at least two non-3GPP transmission paths. The processing unit 1110 is further configured to determine a transmission path based on the second offload rule.

[0315] In one design, the first session request message further includes a multi-access session identifier, the multi-access session identifier for determining a multi-access session of the terminal device.

[0316] In one design, the second off-load rule includes: an offloading rule used by the terminal device before non-3GPP path switching, and access priority indication information, where the access priority indication information indicates a second target transmission path.

[0317] In one design, the second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.

[0318] In one design, the second off-load rule includes: A fourth offloading rule, where the fourth offloading rule instructs a terminal device to perform redundant transmission over at least two non-3GPP transmission paths.

[0319] In one design, the second off-load rule includes: an offloading rule, a fourth offloading rule, and a rule application condition used by the terminal device before a non-3GPP path switch, where the fourth offloading rule instructs the terminal device to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offloading rule is to be applied when a path switch is performed.

[0320] When the communication apparatus 1100 is configured to implement the functionality of UPF, the transceiver unit 1120 is configured to: receive a first offload rule sent by a session management device when a non-3GPP transmission path switch in a multi-access session is performed, where the first offload rule is for supporting a user plane equipment in determining a first target transmission path from at least two non-3GPP transmission paths, the multi-access session includes at least two non-3GPP transmission paths, and the processing unit 1110 is configured to determine the transmission path based on the first offload rule.

[0321] In one design, the first off-load rule includes: an offload rule used by the user plane equipment before non-3GPP path switching, and access priority indication information, where the access priority indication information indicates a first target transmission path.

[0322] In one design, the first target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.

[0323] In one design, the first off-load rule includes: Third offload rule: Wherein the third offload rule instructs the user plane equipment to perform redundant transmission over at least two non-3GPP transmission paths.

[0324] In one design, the first off-load rule includes: an offloading rule, a third offloading rule, and a rule application condition to be used by the user plane equipment before a non-3GPP path switch, where the third offloading rule instructs the user plane equipment to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offloading rule is to be applied when a path switch is performed.

[0325] When the communication device 1100 is configured to implement AMF functionality, the processing unit 1110 is configured to determine whether to perform a non-3GPP transmission path switch in a multi-access session, where the multi-access session includes at least two non-3GPP transmission paths. The transceiver unit 1120 is configured to send a second request message to the session management equipment, where the second request message includes switch instruction information indicating that a non-3GPP transmission path switch is to be performed and / or indicating that the established target transmission path is a non-3GPP transmission path. The transceiver unit 1120 is configured to receive a second offload rule sent by the session management equipment, where the second offload rule is for supporting the terminal device in determining a second target transmission path from the at least two non-3GPP transmission paths, and the transceiver unit 1120 is configured to send the second offload rule to the terminal device.

[0326] In one design, the second request message further includes a multi-access session identifier, the multi-access session identifier for determining a multi-access session of the terminal device.

[0327] In one design, the second request message further includes a multi-access session context identifier, the multi-access session context identifier for determining a multi-access session of the terminal device.

[0328] In one design, the second off-load rule includes: an offloading rule used by the terminal device before non-3GPP path switching, and access priority indication information, where the access priority indication information indicates a second target transmission path.

[0329] In one design, the second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.

[0330] In one design, the second off-load rule includes: A fourth offloading rule, where the fourth offloading rule instructs a terminal device to perform redundant transmission over at least two non-3GPP transmission paths.

[0331] In one design, the second off-load rule includes: an offloading rule, a fourth offloading rule, and a rule application condition used by the terminal device before a non-3GPP path switch, where the fourth offloading rule instructs the terminal device to perform redundant transmission over at least two non-3GPP transmission paths, and the rule application condition indicates that the offloading rule is applied when a path switch is performed.

[0332] In one design, processing unit 1110 is configured to: determining to perform a non-3GPP transmission path switch based on a received non-access stratum message sent by the terminal device to request a path switch, where the non-access stratum message includes switch indication information, and the switch indication information indicates that a non-3GPP transmission path switch is to be performed and / or indicates that the established target transmission path is a non-3GPP transmission path.

[0333] In one design, processing unit 1110 is further configured to: determining, for a mobility management device, that a first condition for releasing a signaling connection is met in a process of performing non-3GPP path switching, and releasing, for the mobility management device, a signaling connection of a terminal device on a target non-3GPP transmission path or a source non-3GPP transmission path.

[0334] In one design, the first condition for releasing the signaling connection includes:

[0335] After the terminal device completes the registration of the target non-3GPP transmission path, a first timer started by the mobility management device expires, where the first timer is configured to indicate that a signaling connection of the source non-3GPP transmission path is to be released. Alternatively, after the terminal device completes the registration of the target non-3GPP transmission path, a second timer started by the mobility management device expires, where the terminal device does not complete switching of the target non-3GPP transmission path, where the second timer is configured to indicate that a signaling connection of the target non-3GPP transmission path is to be released.

[0336] In one design, processing unit 1110 is further configured to: After determining that the terminal device has completed switching of the non-3GPP transmission path, sending a third request message to the session management device, where the third request message indicates applying an offloading rule used by the terminal device and / or the user plane device before switching of the non-3GPP transmission path.

[0337] For a more detailed description of the processing unit 1110 and the transceiver unit 1120, please directly refer to the relevant descriptions in the method embodiments shown in Figures 7 to 10. The details will not be described again here.

[0338] 12 is a diagram illustrating an apparatus 1200 according to an embodiment of the present application. The apparatus 1200 may be an electronic device or a component within an electronic device, such as a chip or an integrated circuit. The apparatus 1200 may include at least one processor 1202 and a communication interface 1204. Optionally, the apparatus may further include at least one memory 1201. Optionally, the apparatus may further include a bus 1203. The memory 1201, the processor 1202, and the communication interface 1204 are connected via the bus 1203.

[0339] The memory 1201 is configured to provide storage space that can store data, such as an operating system and computer programs. The memory 1201 referred to in this embodiment of the present application may be volatile memory, nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM) used as an external cache. By way of example and not limitation, many forms of RAM may be used. Examples include static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink RAM, SLDRAM), and direct Rambus random access memory (DR RAM).

[0340] It should be noted that memory as described herein is intended to include, but is not limited to, these and any other suitable types of memory. The processor 1202 is a module for performing arithmetic and / or logical operations and may be one or a combination of multiple processing modules, such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor unit (MPU), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a complex programmable logic device (CPLD), a synergistic processing unit (which assists the central processing unit to complete corresponding processes and applications), and a microcontroller unit (MCU).

[0341] It should be noted that if the processor is a general-purpose processor, an ASIC, an FPGA or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (storage module) may be integrated into the processor.

[0342] The communication interface 1204 may be configured to provide input or output of information to at least one processor, and / or the communication interface may be configured to receive data transmitted from an external source and / or transmit data to an external source, and may be a wired link interface, including an Ethernet cable and the like, or a wireless link (Wi-Fi, Bluetooth, universal wireless transmission, in-vehicle short-range communication technology, or the like) interface. Optionally, the communication interface 1204 may further include a transmitter (e.g., a radio frequency transmitter, or an antenna, etc.), a receiver, or the like, coupled to the interface.

[0343] In some embodiments, the apparatus 1200 may be an SMF in the method embodiments described above, or may be a component within the SMF, such as a chip or integrated circuit. The processor 1202 within the apparatus 1200 is configured to read a computer program stored in the memory 1201 to control the SMF to perform the following operations: determining to perform a non-3GPP transmission path switch in a multi-access session, where the multi-access session includes at least two non-3GPP transmission paths; and transmitting a first offload rule to a user plane equipment and / or a second offload rule to a terminal equipment, where the first offload rule is for supporting the user plane equipment in determining a first target transmission path from the at least two non-3GPP transmission paths, and the second offload rule is for supporting the terminal equipment in determining a second target transmission path from the at least two non-3GPP transmission paths.

[0344] Optionally, the processor 1202 in the SMF is further configured to: read the program in the memory 1201; and perform steps of the method performed by the SMF at S701 and S702 shown in Figure 7, or perform steps of the method performed by the SMF at S800 to S829 shown in Figures 8A to 8C, or perform steps of the method performed by the SMF at S901 to S916 shown in Figure 9, or perform steps of the method performed by the SMF at S1001 to S1016 shown in Figure 10.

[0345] For specific details, please refer to the records in the above-mentioned method embodiments, and the details will not be described again.

[0346] In some other embodiments, the device 1200 may be a terminal device in the above-described method embodiments, or may be a component in the terminal device, such as a chip or integrated circuit. The processor 1202 in the device 1200 is configured to read a computer program stored in the memory 1201 and control the terminal device to perform the following operations: Performing non-3GPP transmission path switching in a multi-access session, where the multi-access session includes at least two non-3GPP transmission paths; sending a first session request message to a session management device, where the first session request message includes switching instruction information, which indicates that a non-3GPP transmission path switching is to be performed and / or indicates that an established target transmission path is a non-3GPP transmission path; receiving a second offload rule sent by the session management device, where the second offload rule is for supporting a terminal device in determining a second target transmission path from at least two non-3GPP transmission paths; and determining a transmission path based on the second offload rule.

[0347] Optionally, the processor 1202 in the UE may be further configured to: read the program in the memory 1201; and perform the steps of the method performed by the SMF at S701 and S702 shown in Figure 2; or perform the steps of the method performed by the SMF at S800 to S829 shown in Figures 8A to 8C; or perform the steps of the method performed by the SMF at S901 to S916 shown in Figure 9; or perform the steps of the method performed by the SMF at S1001 to S1016 shown in Figure 10.

[0348] For specific details, please refer to the records in the above-mentioned method embodiments, and the details will not be described again.

[0349] In some other embodiments, the device 1200 may be the AMF in the method embodiments described above, or may be a component within the AMF, such as a chip or integrated circuit. The processor 1202 within the device 1200 is configured to read a computer program stored in the memory 1201 and control the AMF to perform the following operations: determining to perform non-3GPP transmission path switching in a multi-access session, where the multi-access session includes at least two non-3GPP transmission paths; sending a second request message to a session management device, where the second request message includes switching instruction information, which indicates that non-3GPP transmission path switching is to be performed and / or indicates that an established target transmission path is a non-3GPP transmission path; receiving a second offload rule sent by the session management device, where the second offload rule is for supporting the terminal device in determining a second target transmission path from at least two non-3GPP transmission paths; and sending the second offload rule to the terminal device.

[0350] Alternatively, the processor 1202 in the device 1200 is configured to read a computer program stored in the memory 1201 and control the AMF to perform the following operations: In the process of performing non-3GPP path switching, determining that a first condition for releasing a signaling connection is met, and releasing the signaling connection of a terminal device on the target non-3GPP transmission path or the source non-3GPP transmission path.

[0351] Optionally, the processor 1202 in the AMF is configured to: read the program in the memory 1201; and perform the steps of the method performed by the SMF at S701 and S702 shown in Figure 2; or perform the steps of the method performed by the SMF at S800 to S829 shown in Figures 8A to 8C; or perform the steps of the method performed by the SMF at S901 to S916 shown in Figure 9; or perform the steps of the method performed by the SMF at S1001 to S1016 shown in Figure 10.

[0352] For specific details, please refer to the records in the above-mentioned method embodiments, and the details will not be described again.

[0353] In some other embodiments, the device 1200 may be a UPF in the method embodiments described above, or may be a component in a UPF, such as a chip or integrated circuit. The processor 1202 in the device 1200 is configured to read a computer program stored in the memory 1201 and control the UPF to perform the following operations: When non-3GPP transmission path switching in a multi-access session is performed, receiving a first offload rule sent by a session management device, where the first offload rule is for supporting a user plane device in determining a first target transmission path from at least two non-3GPP transmission paths, and the multi-access session includes at least two non-3GPP transmission paths, and determining a transmission path based on the first offload rule.

[0354] Optionally, the processor 1202 in the UPF is configured to: read the program in the memory 1201; and perform the steps of the method performed by the SMF at S701 and S702; or perform the steps of the method performed by the SMF at S800 to S829 shown in Figures 8A to 8C; or perform the steps of the method performed by the SMF at S901 to S916 shown in Figure 9; or perform the steps of the method performed by the SMF at S1001 to S1016 shown in Figure 10.

[0355] For specific details, please refer to the records in the above-mentioned method embodiments, and the details will not be described again.

[0356] The embodiment of the present application further provides a communication path switching system, including a terminal device, an SMF, and an AMF. Optionally, a UPF is further included.

[0357] It will be understood that the processor in the embodiments of the present application may be a Central Processing Unit (CPU), or may be another general-purpose processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The general-purpose processor may be a microprocessor or a conventional processor or the like.

[0358] Those skilled in the art will understand that the various numbers, such as "first" and "second," used in this application are merely used for distinction to facilitate description and are not used to limit the scope of the embodiments of this application or to represent a sequence. "And / or" describes an association relationship for describing associated objects and indicates that three relationships may exist. For example, A and / or B may represent the following three cases: only A is present, both A and B are present, and only B is present. The character " / " generally indicates the "or" relationship between associated objects. "At least one" means one or more. "At least two" means two or more. "At least one" or similar expressions refer to any combination of items, including any combination of one item (moiety) or multiple items (moieties). For example, at least one of a, b, or c may refer to the following: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural. "Plurality" means two or more, and other quantifiers similarly.

[0359] It should be understood that the sequence numbers of the above processes do not mean the execution sequence in various embodiments of the present application. The execution sequence of the processes should be determined according to the functions and internal logic of the processes, and should not be construed as any limitation on the implementation process in the embodiments of the present application.

[0360] For the sake of convenient and concise description, it can be clearly understood by those skilled in the art that the detailed working processes of the above-mentioned systems, devices and units should be referred to the corresponding processes in the above-mentioned method embodiments, and the details will not be described again in this specification.

[0361] All or part of the above-described embodiments may be implemented by software, hardware, firmware, or any combination thereof. When software is used to implement an embodiment, all or part of the embodiment may be implemented in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored on a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, fiber optics, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave) transmission. The computer-readable storage medium may be any available medium accessible by a computer, or may be a data storage device, such as a server or data center, that integrates one or more available media. The usable media may be magnetic media (such as a floppy disk, hard disk, or magnetic tape), optical media (such as a DVD), semiconductor media (such as a solid-state drive (SSD)), or the like.

[0362] The various exemplary logic units and logic circuits described in the embodiments of the present application may implement or operate the described functions by using a design of a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor may be a microprocessor. Optionally, the general-purpose processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors with a digital signal processor core, or any other similar configuration.

[0363] The steps of a method or algorithm described in the embodiments of the present application may be embodied directly in hardware, in a software unit executed by a processor, or in a combination thereof. The software unit may be stored in a random access memory (RAM), flash memory, read-only memory (ROM), EPROM memory, EEPROM memory, registers, a hard disk, a removable magnetic disk, a CD-ROM, or any other form of storage medium known in the art. For example, the storage medium may be connected to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may be located in an ASIC.

[0364] In one or more exemplary designs, the functions described herein may be implemented using hardware, software, firmware, or any combination thereof. If the functions are implemented in software, they may be stored on or transmitted to a computer-readable medium in the form of one or more instructions or code. Computer-readable media includes computer storage media and communication media that enable a computer program to travel from one place to another. Storage media may be any available medium that can be accessed by a general computer or a specialized computer. For example, such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, disk storage, or other magnetic storage, or any other medium that can be used to hold or store program code, where the program code is in the form of instructions or data structures and is in a form that can be read by a general computer or a specialized computer, or a general or specialized processor. Additionally, any connection may be properly defined as a computer-readable medium. For example, software is included within the defined computer-readable medium if it is transmitted from a website, server, or other remote resource using coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL), or in a wireless manner such as infrared, radio, or microwave. Disks and discs include compact discs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data in a magnetic format, while discs typically reproduce data optically in a laser format. Combinations of the above may also be included within computer-readable media.

Claims

1. 1. A communication method comprising: determining, by a session management device, to perform non-third generation partnership project transmission path switching in a multi-access session, wherein the multi-access session includes at least two non-third generation partnership project transmission paths, and the at least two non-third generation partnership project transmission paths include a source non-third generation partnership project transmission path and a target non-third generation partnership project transmission path; sending, by the session management equipment, a first offload rule to a user plane equipment, the first offload rule instructing the user plane equipment to switch a service flow transmitted via the source non-third generation partnership project transmission path to the target non-third generation partnership project transmission path; In the process of performing the non-3G Partnership Project transmission path switching, determining, by a mobility management device, that a first condition for releasing a signaling connection is met; Releasing, by the mobility management device, a signaling connection of a terminal device on the target non-third generation partnership project transmission path or the source non-third generation partnership project transmission path; A method comprising:

2. The step of determining by the session management device to perform a non-3G Partnership Project transmission path switch in the multi-access session includes: determining, by the session management device based on a received session request message, to perform the non-third generation partnership project transmission path switching in the multi-access session, wherein the session request message includes switching instruction information, and the switching instruction information indicates that the non-third generation partnership project transmission path switching is to be performed, and / or indicates that an established target transmission path is the non-third generation partnership project transmission path; Including, the session request message is a non-access stratum message sent by the terminal device after the terminal device decides to perform the non-third generation partnership project transmission path switching, or the session request message is a second session request message sent by the mobility management device after the mobility management device decides to perform the non-third generation partnership project transmission path switching; The method of claim 1.

3. The step of determining to perform a non-3G Partnership Project transmission path switch in the multi-access session by the session management device based on the received session request message includes: determining, based on the session request message, to perform switching of the non-third generation partnership project transmission path when the switching instruction information indicates that the established target transmission path is the non-third generation partnership project transmission path, and when the session management device determines that the established source transmission path of the multi-access session is the non-third generation partnership project transmission path; The method of claim 2 , comprising:

4. the session request message further includes a session identifier for the multi-access session; the session identifier is for determining the multi-access session of the terminal device; The method of claim 2.

5. the session request message further includes a session context identifier for the multi-access session; the session context identifier is for determining the multi-access session of the terminal device; The method of claim 2.

6. The first offload rule includes an offload rule used by the user plane equipment before the non-3G Partnership Project transmission path switching and access priority indication information; The access priority indication information indicates a target non-third generation partnership project; The method of claim 1.

7. The target non-third generation partnership project transmission path is a trusted non-third generation partnership project transmission path or an untrusted non-third generation partnership project transmission path; The method of claim 6.

8. the first off-road rule includes a third off-road rule, the third offload rule instructs the user plane equipment to perform redundant transmission over the at least two non-3G Partnership Project transmission paths; The method of claim 1.

9. The first offload rule includes an offload rule used by the user plane equipment before the non-third generation partnership project transmission path switching, a third offload rule, and a rule application condition; the third offload rule instructs the user plane equipment to perform redundant transmission across the at least two non-3G Partnership Project transmission paths, and the rule application condition instructs the offload rule to be applied when a path switch is performed; The method of claim 1.

10. 1. A communication method comprising: determining, by a terminal device, to perform non-third generation partnership project transmission path switching in a multi-access session, the multi-access session including at least two non-third generation partnership project transmission paths, the at least two non-third generation partnership project transmission paths including a source non-third generation partnership project transmission path and a target non-third generation partnership project transmission path; sending a first session request message to a session management device by the terminal device, the first session request message including switching instruction information, the switching instruction information indicating that the non-third generation partnership project transmission path switching is to be performed, and / or indicating that an established target transmission path is the non-third generation partnership project transmission path; In the process of performing the non-3G Partnership Project transmission path switching, determining, by a mobility management device, that a first condition for releasing a signaling connection is met; Releasing, by the mobility management device, a signaling connection of a terminal device on the target non-third generation partnership project transmission path or the source non-third generation partnership project transmission path; A method comprising:

11. The method of claim 10, wherein the first session request message further includes a multi-access session identifier, the multi-access session identifier for determining the multi-access session of the terminal device.

12. The method of claim 10 , wherein the target non-third generation partnership project transmission path is a trusted non-third generation partnership project transmission path or an untrusted non-third generation partnership project transmission path.

13. receiving, by the terminal device, a second offload rule sent by the session management device, the second offload rule instructing the terminal device to switch a service flow transmitted over the source non-third generation partnership project transmission path to the target non-third generation partnership project transmission path for transmission; The method of claim 10 further comprising:

14. 1. A communication method comprising: determining, by a mobility management device, to perform a non-third generation partnership project transmission path switching in a multi-access session, wherein the multi-access session includes at least two non-third generation partnership project transmission paths, and the at least two non-third generation partnership project transmission paths include a source non-third generation partnership project transmission path and a target non-third generation partnership project transmission path; sending, by the mobility management device, a second session request message to a session management device, the second session request message including switching instruction information, the switching instruction information indicating that the non-third generation partnership project transmission path switching is to be performed, and / or indicating that an established target transmission path is the non-third generation partnership project transmission path; In the process of performing the non-3G Partnership Project transmission path switch, determining, by the mobility management device, that a first condition for releasing a signaling connection is met; Releasing, by the mobility management device, a signaling connection of a terminal device on the target non-third generation partnership project transmission path or the source non-third generation partnership project transmission path; A method comprising:

15. 15. The method of claim 14, wherein the second session request message further includes a multi-access session identifier, the multi-access session identifier for determining the multi-access session of a terminal device.

16. 15. The method of claim 14, wherein the second session request message further includes a context identifier of the multi-access session, the context identifier of the multi-access session being for determining the multi-access session of a terminal device.

17. The method of claim 14 , wherein the target non-third generation partnership project transmission path is a trusted non-third generation partnership project transmission path or an untrusted non-third generation partnership project transmission path.

18. The step of determining to perform a non-3G Partnership Project transmission path switch in a multi-access session by a mobility management device includes: determining, by the mobility management device based on a received non-access stratum message sent by a terminal device to request a path switch, to perform the non-third generation partnership project transmission path switch, wherein the non-access stratum message includes the switch instruction information, and the switch instruction information indicates that the non-third generation partnership project transmission path switch is to be performed and / or indicates that the established target transmission path is the non-third generation partnership project transmission path; 15. The method of claim 14, comprising:

19. The first condition for releasing a signaling connection is: After the terminal device completes registration of the target non-third generation partnership project transmission path, a first timer started by the mobility management device expires, and the first timer is configured to indicate causing release of a signaling connection of the source non-third generation partnership project transmission path; or After the terminal equipment completes registration of the target non-third generation partnership project transmission path, a second timer started by the mobility management device expires, and the terminal equipment does not complete switching of the target non-third generation partnership project transmission path, and the second timer is configured to indicate causing release of a signaling connection of the target non-third generation partnership project transmission path.

15. The method of claim 14, comprising:

20. sending, by the mobility management device, a third request message to the session management device after determining that the terminal device has completed the non-third generation partnership project transmission path switching, the third request message instructing to apply an offload rule used by the terminal device and / or user plane equipment before the non-third generation partnership project transmission path switching; The method of claim 14 further comprising:

21. A communication device comprising a module adapted to carry out the method according to any one of claims 1 to 9.

22. A communication device comprising a processor and an interface circuit, the interface circuit being configured to receive signals from a communication device other than the communication device and to transmit the signals to the processor or to transmit signals from the processor to a communication device other than the communication device, the processor being configured to implement a method according to any one of claims 1 to 9 by using logic circuits or by executing code instructions.

23. A computer-readable storage medium having stored thereon a computer program or instructions, the computer program or instructions implementing the method of any one of claims 1 to 9 when executed by a communication device.

24. A computer program comprising computer-executable instructions, which, when run on a computer, perform the method of any one of claims 1 to 9.

25. A communication device comprising a module configured to perform a method according to any one of claims 10 to 13.

26. A communications device comprising a processor and an interface circuit, wherein the interface circuit is configured to receive signals from a communications device other than the communications device and transmit the signals to the processor, or transmit signals from the processor to a communications device other than the communications device, and wherein the processor is configured to implement a method according to any one of claims 10 to 13 by using logic circuits or by executing code instructions.

27. ​​A computer-readable storage medium, the computer-readable storage medium storing a computer program or instructions, the computer program or instructions, when executed by a communications device, implementing a method according to any one of claims 10 to 13.

28. A computer program comprising computer-executable instructions, which, when executed on a computer, performs a method according to any one of claims 10 to 13.

29. A communication device comprising a module configured to perform a method according to any one of claims 14 to 20.

30. A communications device comprising a processor and an interface circuit, wherein the interface circuit is configured to receive signals from a communications device other than the communications device and transmit the signals to the processor, or transmit signals from the processor to a communications device other than the communications device, and wherein the processor is configured to implement a method according to any one of claims 14 to 20 by using logic circuits or by executing code instructions.

31. A computer-readable storage medium, the computer-readable storage medium storing a computer program or instructions, the computer program or instructions, when executed by a communications device, implementing a method according to any one of claims 14 to 20.

32. A computer program comprising computer-executable instructions, which, when executed on a computer, performs a method according to any one of claims 14 to 20.

Images