WO2023185411A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2023185411A1
WO2023185411A1 PCT/CN2023/080460 CN2023080460W WO2023185411A1 WO 2023185411 A1 WO2023185411 A1 WO 2023185411A1 CN 2023080460 W CN2023080460 W CN 2023080460W WO 2023185411 A1 WO2023185411 A1 WO 2023185411A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission path
session
rule
3gpp
access
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/080460
Other languages
English (en)
French (fr)
Inventor
黄康
徐艺珊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to JP2024557484A priority Critical patent/JP7804101B2/ja
Priority to EP23777789.1A priority patent/EP4485889A4/en
Publication of WO2023185411A1 publication Critical patent/WO2023185411A1/zh
Priority to US18/897,771 priority patent/US20250024332A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present application relates to the field of communication technology, and in particular, to a communication method and device.
  • the business flow data that needs to be sent is often established by establishing a multi-access PDU Session (MA PDU Session) and accessed through the 3rd Generation Partnership Project (3GPP) at the same time.
  • MA PDU Session multi-access PDU Session
  • 3GPP 3rd Generation Partnership Project
  • network path
  • non-3GPP access network path
  • existing multi-access session technology only supports transmission through one 3GPP access network (path) and one non-3GPP access network (path), and does not support transmission through more than two access networks (paths).
  • path 3GPP access network
  • paths non-3GPP access networks
  • implementing non-3GPP path switching will cause multiple non-3GPP paths to exist at the same time, resulting in terminal equipment (user equipment, UE) and The user plane function (UPF) cannot effectively perform the offloading of business data during the handover process, which may cause business interruption and thus affect the user experience.
  • UPF user plane function
  • This application provides a communication method and device to provide a non-3GPP path switching solution in a multi-access session, better support the offloading of business flow data, ensure communication continuity, and reduce system overhead.
  • the first aspect is to provide a communication method.
  • This method may be executed by the session management device, or by a chip similar to the function of the session management device.
  • the session management device determines to perform non-3GPP transmission path switching in a multi-access session, the multi-access session includes at least two non-3GPP transmission paths;
  • the session management device sends a first offload rule to the user plane device and/or send a second offload rule to the terminal device;
  • the first offload rule is used to support the user plane device in determining a first target transmission path among the at least two non-3GPP transmission paths;
  • the second offload rule Used to support the terminal device in determining a second target transmission path among the at least two non-3GPP transmission paths.
  • the first target transmission path may be one or more of multiple non-3GPP transmission paths.
  • the first target transmission path in the embodiment of the present application may not include non-3GPP transmission paths.
  • the second target transmission path may be one or more of multiple non-3GPP transmission paths.
  • the second target transmission path in the embodiment of the present application may also not include non-3GPP transmission paths.
  • the first offloading rule in the embodiment of the present application is used to support the user plane device in determining the first target transmission path among the at least two non-3GPP transmission paths. It can be understood that the user plane device is executing the non-3GPP transmission path. When using a 3GPP transmission path, the first offloading rule may be used to determine the transmission path. Similarly, the second offloading rule is used to support the terminal device in determining the second target transmission path among the at least two non-3GPP transmission paths. It can be understood that when the user plane device executes the non-3GPP transmission path, The second branching rule may be used to determine the transmission path.
  • the multi-access session management process may be a multi-access session establishment process, a multi-access session modification process, a multi-access session adding process, a multi-access session release process, or a multi-access session release process. Enter the session activation process, etc.
  • the terminal device and the user plane device trigger the offloading rule that supports the existence of multiple non-3GPP transmission paths during the switching process, for example, trigger
  • the offloading rules can support the UE and/or UPF to select an appropriate transmission path for data transmission among multiple non-3GPP transmission paths, effectively performing the offloading of service data, thereby ensuring business continuity during session switching.
  • the session management device determines to perform non-3GPP transmission path switching in the multi-access session according to the received session request message, the session request message includes switching indication information, and the switching indication information indicates Perform non-3GPP transmission path switching and/or indicate that the target transmission path established is a non-3GPP transmission path; the session request message is the first session request message sent by the terminal device after determining to perform a non-3GPP transmission path; or, The session request message is a second session request message sent by the mobile management device after determining to execute a non-3GPP transmission path.
  • 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, etc., which is not limited here.
  • the second session request message may be a session creation context message, or the second session request message may be a session update session context message, etc., which is not limited here.
  • embodiments of the present application provide 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 it needs to be performed based on a received session request message.
  • the session management device determines that the source transmission path that the multi-access session has established is a non-3GPP transmission path. When, it is determined to perform the non-3GPP path switching according to the session request.
  • the session request message further includes a session identifier of the multi-access session; the session identifier is used to determine the multi-access session of the terminal device.
  • the session request message further includes a session context identifier of the multi-access session; the session context identifier is used to determine the multi-access session of the terminal device.
  • the first diversion rule includes:
  • the offloading rules used by the user plane device before non-3GPP path switching, and the access priority indication information is used to indicate the first target transmission path;
  • the second diversion rule includes:
  • the access priority information may be a radio access technology (RAT) type.
  • RAT radio access technology
  • the RAT type is trusted non-3GPP access, it indicates that the non-3GPP transmission path of the user plane device is a trusted non-3GPP path.
  • the RAT type is distrust non-3GPP access (untrusted non-3GPP access), indicating that the non-3GPP transmission path of the user plane device is an untrusted non-3GPP path.
  • the RAT type is 3GPP access, it indicates that all non-3GPP transmission paths of the user plane device are migrated to 3GPP transmission paths.
  • the first target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path;
  • the second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.
  • the source non-3GPP transmission path before the switching can be an untrusted non-3GPP transmission path
  • the target non-3GPP transmission path after the switching can be a trusted non-3GPP transmission path.
  • the source non-3GPP transmission path before switching may be a trusted non-3GPP transmission path
  • the target non-3GPP transmission path after switching may be an untrusted non-3GPP transmission path.
  • the first offloading rule includes: a third offloading rule, the third offloading rule is used to instruct the user plane device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the second offloading rule includes: a fourth offloading rule, the fourth offloading rule instructs the terminal device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the first offloading rule includes: the offloading rule used by the user plane device before non-3GPP path switching, the third offloading rule and the rule application condition, and the third offloading rule is used to indicate The user plane device performs redundant transmission through the at least two non-3GPP transmission paths, and the rule application condition is used to indicate the application of offloading rules when performing path switching.
  • the second offloading rule includes: the offloading rule used by the terminal device before the non-3GPP path switching, the fourth offloading rule, and the rule application condition, and the fourth offloading rule is used to indicate the offloading rule.
  • the terminal device performs redundant transmission through the at least two non-3GPP transmission paths, and the rule application condition is used to indicate that the offloading rule should be applied when performing path switching.
  • the second aspect is to provide a communication method.
  • This method can be executed by a terminal device, or a chip with functions similar to the terminal device.
  • the terminal device determines to perform non-3GPP transmission path switching in a multi-access session, and the multi-access session includes at least two non-3GPP transmission paths;
  • the terminal device sends a first session request message to the session management device,
  • the first session request message includes switching indication information, the switching indication information indicates performing a non-3GPP transmission path switching and/or indicates that the established target transmission path is a non-3GPP transmission path;
  • the terminal device receives a message from the session management device.
  • the second offloading rule sent; the second offloading rule is used to support the terminal device in determining a second target transmission path among the at least two non-3GPP transmission paths; the terminal device determines according to the second offloading rule transmission path.
  • the second target transmission path may be one or more of multiple non-3GPP transmission paths.
  • the second target transmission path in the embodiment of the present application may also not include non-3GPP transmission paths.
  • the second offloading rule is used to support the terminal device in determining the second target transmission path among the at least two non-3GPP transmission paths. It can be understood that when the user plane device executes the non-3GPP transmission path, The second diversion rule is used to determine the transmission path.
  • the multi-access session management process may be a multi-access session establishment process, a multi-access session modification process, a multi-access session adding process, a multi-access session release process, or a multi-access session release process. Enter the session activation process, etc.
  • the terminal device and the user plane device trigger the offloading rule that supports the existence of multiple non-3GPP transmission paths during the switching process, for example, trigger
  • the offloading rules can support the UE and/or UPF to select an appropriate transmission path for data transmission among multiple non-3GPP transmission paths, effectively performing the offloading of service data, thereby ensuring business continuity during session switching.
  • the first session request message further includes the multi-access session identifier, and the multi-access session identifier is used to determine the multi-access session of the terminal device.
  • the second offloading rule includes: the offloading rule used by the terminal device before non-3GPP path switching, and access priority indication information; the access priority indication information, Used to indicate the second target transmission path.
  • the second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.
  • the second offloading rule includes: a fourth offloading rule, the fourth offloading rule instructs the terminal device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the second offloading rule includes: the offloading rule used by the terminal device before the non-3GPP path switching, the fourth offloading rule, and the rule application condition, and the fourth offloading rule is used to The terminal device is instructed to perform redundant transmission through the at least two non-3GPP transmission paths, and the rule application condition is used to instruct the offloading rule to be applied when performing path switching.
  • the third aspect is to provide a communication method.
  • This method can be executed by a user plane device, or a chip with functions similar to the user plane device.
  • the user plane device when performing non-3GPP transmission path switching in a multi-access session, the user plane device receives the first offload rule sent from the session management device; the first offload rule is used to support the user plane device in the The first target transmission path is determined among at least two non-3GPP transmission paths, and the multi-access session includes at least two non-3GPP transmission paths; the user plane device determines the transmission path according to the first offloading rule.
  • the first target transmission path may be one or more of multiple non-3GPP transmission paths.
  • the first target transmission path in the embodiment of the present application may not include non-3GPP transmission paths.
  • the second target transmission path may be one or more of multiple non-3GPP transmission paths.
  • the second target transmission path in the embodiment of the present application may also not include non-3GPP transmission paths.
  • the first offloading rule in the embodiment of the present application is used to support the user plane device in determining the first target transmission path among the at least two non-3GPP transmission paths. It can be understood that the user plane device is executing the non-3GPP transmission path. When using a 3GPP transmission path, the first offloading rule may be used to determine the transmission path.
  • the multi-access session management process may be a multi-access session establishment process, a multi-access session modification process, a multi-access session adding process, a multi-access session release process, or a multi-access session release process. Enter the session activation process, etc.
  • the terminal device and the user plane device trigger the offloading rule that supports the existence of multiple non-3GPP transmission paths during the switching process, for example, trigger
  • the offloading rules can support the UE and/or UPF to select an appropriate transmission path for data transmission among multiple non-3GPP transmission paths, effectively performing the offloading of service data, thereby ensuring business continuity during session switching.
  • the first diversion rule includes:
  • the offloading rules used by the user plane device before non-3GPP path switching, and the access priority indication information is used to indicate the first target transmission path.
  • the first target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.
  • the first diversion rule includes:
  • the third offloading rule is used to instruct the user plane device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the first diversion rule includes:
  • the offloading rules, the third offloading rule and the rule application conditions used by the user plane device before non-3GPP path switching are used to instruct the user plane device to perform transmission through the at least two non-3GPP transmission paths.
  • the rule application condition is used to indicate that the offloading rule should be applied when performing path switching.
  • the fourth aspect is to provide a communication method.
  • This method can be executed by a mobile management device, or a chip with similar functions to the mobile management device.
  • the mobility management device determines to perform non-3GPP transmission path switching in a multi-access session, the multi-access session includes at least two non-3GPP transmission paths;
  • the mobility management device sends a second request message to the session management device , the second request message includes switching indication information, the switching indication information indicates to perform non-3GPP transmission path switching and/or indicates that the established target transmission path is a non-3GPP transmission path;
  • the mobile management device receives a message from the session management a second offload rule sent by the device; the second offload rule is used to support the terminal device in determining a second target transmission path among the at least two non-3GPP transmission paths;
  • the mobile management device The rules are sent to the terminal device.
  • the second target transmission path may be one or more of multiple non-3GPP transmission paths.
  • the second target transmission path in the embodiment of the present application may also not include non-3GPP transmission paths.
  • the second offloading rule is used to support the terminal device in determining the second target transmission path among the at least two non-3GPP transmission paths. It can be understood that when the user plane device executes the non-3GPP transmission path, The second diversion rule is used to determine the transmission path.
  • the multi-access session management process may be a multi-access session establishment process, a multi-access session modification process, a multi-access session adding process, a multi-access session release process, or a multi-access session release process. Enter the session activation process, etc.
  • the terminal device and the user plane device trigger the offloading rule that supports the existence of multiple non-3GPP transmission paths during the switching process, for example, trigger
  • the offloading rules can support the UE and/or UPF to select an appropriate transmission path for data transmission among multiple non-3GPP transmission paths, effectively performing the offloading of service data, thereby ensuring business continuity during session switching.
  • the second request message further includes the multi-access session identifier, and the multi-access session identifier is used to determine the multi-access session of the terminal device.
  • the second request message further includes a context identifier of the multi-access session, and the context identifier of the multi-access session is used to determine the multi-access session of the terminal device. .
  • the second offloading rule includes: the offloading rule used by the terminal device before non-3GPP path switching, and access priority indication information; the access priority indication information, Used to indicate the second target transmission path.
  • the second target transmission path is a trusted non-3GPP transmission path or an untrusted Non-3GPP transmission path.
  • the second diversion rule includes:
  • a fourth offload rule instructs the terminal device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the second diversion rule includes:
  • the fourth offloading rule is used to instruct the terminal equipment to perform redundancy through the at least two non-3GPP transmission paths.
  • Transmission, the rule application condition is used to indicate that the offloading rule should be applied when performing path switching.
  • the mobility management device determines to perform non-3GPP transmission path switching based on the received non-access layer message sent by the terminal device for requesting path switching.
  • the switching instruction information includes switching indication information, which indicates performing non-3GPP transmission path switching and/or indicates that the established target transmission path is a non-3GPP transmission path.
  • the method further includes:
  • the mobility management device determines that the first condition for signaling connection release is met; the mobility management device releases the signaling of the terminal device on the target non-3GPP transmission path or the source non-3GPP transmission path. connect.
  • the signaling connection release may be an access network signaling release, or may be a terminal device de-registration, etc., which is not limited here.
  • the mobile management device determines whether the terminal device is used for subsequent session switching when registering, and decides whether to release the signaling connection of the terminal device on the target path or the source path, effectively avoiding the terminal device remaining trusted non-3GPP and non-3GPP for a long time. Dual registration status on the trusted non-3GPP path. At the same time, it can also support MA PDU session switching on the non-3GPP path.
  • the first condition for signaling connection release includes:
  • the second timer is used to indicate triggering the target non-3GPP transmission path signaling connection release.
  • the method further includes:
  • the mobile management device After the mobile management device determines that the terminal device has completed non-3GPP transmission path switching, it sends a third request message to the session management device.
  • the third request message is used to instruct the application of the terminal device and/or user plane device. Offloading rules used before non-3GPP transmission path switching.
  • the fifth aspect provides a communication method.
  • This method can be executed by a mobile management device, or a chip with similar functions to the mobile management device.
  • the mobility management device determines that the first condition for signaling connection release is met during the non-3GPP path switching process; the mobility management device releases the signaling of the terminal device on the target non-3GPP transmission path or the source non-3GPP transmission path. connect.
  • the signaling connection release may be an access network signaling release, or may be a terminal device de-registration, etc., which is not limited here.
  • the mobile management device determines whether the terminal device is used for subsequent session switching when registering. Whether to release the signaling connection of the terminal device on the target path or the source path, which effectively avoids the terminal device maintaining dual registration status on the trusted non-3GPP and untrusted non-3GPP paths for a long time, and can also support MA on the non-3GPP path. PDU session switching.
  • the first condition for signaling connection release includes:
  • the second timer is used to indicate triggering the target non-3GPP transmission path signaling connection release.
  • embodiments of the present application provide a communication device, which may be a session management device or a chip used for the session management device.
  • the device has the function of implementing any implementation method of the above-mentioned first aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a communication device which may be a terminal device or a chip or module for the terminal device.
  • the terminal device may be, for example, a smart mobile terminal, a smart home device, a smart car, a smart wearable device, etc.
  • smart mobile terminals include mobile phones, tablets, laptops, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA), etc.
  • Smart home devices such as smart refrigerators, smart washing machines, smart TVs, speakers, etc.
  • Smart car wearable devices such as smart headphones, smart glasses, smart clothing or shoes, etc.
  • the device has the function of implementing any implementation method of the above second aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • embodiments of the present application provide a communication device, which may be a UPF or a chip or module for UPF.
  • the device has the function of implementing any implementation method of the above third aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • inventions of the present application provide a communication device.
  • the device may be a mobility management device, or may be a chip or module for the mobility management device.
  • the device has the function of implementing any implementation method of the fourth aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • inventions of the present application provide a communication device.
  • the device may be a mobility management device, or may be a chip or module for the mobility management device.
  • the device has the function of implementing any implementation method of the fifth aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • embodiments of the present application provide a communication device, including a processor and a memory; the memory is used to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory, so that the device Execute any implementation method in the above first to fifth aspects.
  • an embodiment of the present application provides a communication device, including units or means for executing each step of any implementation method in the above-mentioned first to fifth aspects.
  • embodiments of the present application provide a communication device, including a processor and an interface circuit.
  • the processor is configured to communicate with other devices through the interface circuit and perform any implementation method in the above first to fifth aspects.
  • the processor includes one or more.
  • embodiments of the present application provide a communication device, including a processor coupled to a memory, and the processor is configured to call a program stored in the memory to execute any implementation of the above first to fifth aspects.
  • the memory may be located within the device or external to the device.
  • the processor can be one or more.
  • embodiments of the present application further provide a computer-readable storage medium, in which instructions are stored, and when run on a communication device, the computer-readable storage medium causes the above-described first to fifth aspects to occur. Any implementation method of is executed.
  • embodiments of the present application further provide a computer program product.
  • the computer program product includes a computer program or instructions.
  • the computer program or instructions are run by a communication device, any one of the above-mentioned first to fifth aspects is enabled.
  • the implementation method is executed.
  • embodiments of the present application further provide a chip system, including: a processor, configured to execute any of the implementation methods in the above first to fifth aspects.
  • embodiments of the present application further provide a communication system, including: the communication device of the sixth aspect to the communication device of the ninth aspect.
  • the communication device of the tenth aspect is also included.
  • Figure 1 is a schematic diagram of an existing multi-access session system
  • Figure 2 is a schematic diagram of the first multi-access session scenario provided by the embodiment of the present application.
  • Figure 3 is a schematic diagram of the second multi-access session scenario provided by the embodiment of the present application.
  • Figure 4 is a schematic diagram of the third multi-access session scenario provided by the embodiment of the present application.
  • Figure 5 is a schematic diagram of the fourth multi-access session scenario provided by the embodiment of the present application.
  • Figure 6 is a schematic diagram of a communication path switching system provided by an embodiment of the present application.
  • Figure 7 is a schematic flow chart of a communication path switching method provided by an embodiment of the present application.
  • Figure 8 is a schematic flow chart of the first path switching situation provided by the embodiment of the present application.
  • Figure 9 is a schematic flow chart of the second path switching situation provided by the embodiment of the present application.
  • Figure 10 is a schematic flow chart of the third path switching situation provided by the embodiment of the present application.
  • Figure 11 is a schematic diagram of a first communication path switching device provided by an embodiment of the present application.
  • Figure 12 is a schematic diagram of a second communication path switching device provided by an embodiment of the present application.
  • Non-3GPP access types include untrusted non-3GPP access technologies (untrusted non-3GPP access), such as access to the core network through individually purchased wireless access nodes, and trusted non-3GPP access technologies. (trusted non-3GPP access) such as accessing the core network through wireless access nodes deployed by operators, wired access technology (wireline access).
  • untrusted non-3GPP access such as access to the core network through individually purchased wireless access nodes
  • trusted non-3GPP access technologies such as accessing the core network through wireless access nodes deployed by operators, wired access technology (wireline access).
  • Non-3GPP access technologies may include wireless communication technology (WiFi), Bluetooth or ZigBee.
  • Non-3GPP access network equipment may include non-3GPP interworking function (N3IWF), trusted non-3GPP gateway function (TNGF), trusted non-3GPP access point (trusted non- 3GPP access point (TNAP), trusted wireless local area network interworking function (TWIF), wired access gateway function (W-AGF).
  • W-AGF can also be called AGF.
  • the access technology is an untrusted non-3GPP access technology
  • its corresponding non-3GPP access network equipment can include N3IWF
  • its network topology is equivalent to the radio access network (RAN) in the 3GPP access network.
  • RAN radio access network
  • N3 interfaces the access network
  • the access technology is a trusted non-3GPP access technology
  • its corresponding non-3GPP access network equipment can include TNGF. Its network topology is equivalent to the RAN in the 3GPP access network and can support N2 and N3 interfaces.
  • the untrusted non-3GPP access point may be an access node deployed by a non-operator, such as a WiFi access point (AP) deployed at home or in a business.
  • the trusted non-3GPP access point can be an access node deployed by the operator, which can be called a trusted non-3GPP access point (TNAP).
  • TNAP trusted non-3GPP access point
  • Multi-access PDU Session used to refer to the UE and/or UPF accessing the network through 3GPP (can also be understood as 3GPP access path) and non-3GPP access network (can also be understood as a non-3GPP access path) for transmission to improve transmission efficiency.
  • 3GPP can also be understood as 3GPP access path
  • non-3GPP access network can also be understood as a non-3GPP access path
  • the user plane channel may include two access network devices (3GPP access network device and non-3GPP access network device), which are connected to the same UPF (or connected to the same UPF through another UPF) .
  • the UE may send uplink data to the UPF through the RAN and/or N3IWF; and the UPF may send downlink data to the UE through the RAN and/or N3IWF.
  • Offload rules used to indicate how to send the data to be sent through the path of the 3GPP access network and/or through the path of the non-3GPP access network.
  • the business flow data that needs to be sent is often established through the establishment of a multi-access PDU Session (MA PDU Session) at the same time through the 3GPP access network (path) and the non-3GPP access network ( path) for transmission to improve transmission efficiency.
  • the user plane channel may include two access network devices (3GPP access network device and non-3GPP access network device).
  • the two access network devices are connected to the same UPF (or through another UPF is connected to the same UPF), in which the UE can send uplink data to the UPF through the Radio Access Network (RAN) and/or the non-3GPP interworking function (N3IWF); the UPF can send uplink data to the UPF through the RAN and/or non-3GPP interworking function (N3IWF). /or N3IWF sends downlink data to the UE.
  • RAN Radio Access Network
  • N3IWF non-3GPP interworking function
  • N3IWF non-3GPP interworking function
  • N3IWF sends downlink data to the UE.
  • existing multi-access session technology only supports transmission through a 3GPP access network (path) and a non-3GPP access network (path), and does not support transmission through more than two paths. That is, when a multi-access session When the scenario involves more than two transmission paths, the UE and UPF cannot effectively offload service data, which may cause service interruption and thus affect user experience.
  • existing multi-access session technology does not support multi-access session transmission through at least two non-3GPP paths as shown in Figure 2.
  • the at least two non-3GPP paths include trusted non-3GPP paths and non-3GPP paths. Trusted non-3GPP paths; for another example, the existing multi-access session technology does not support the form of multi-access session transmission through at least two 3GPP paths as shown in Figure 3; for another example, the existing multi-access session technology does not support passing a A form of multi-access session transmission through 3GPP paths and at least two non-3GPP paths; for another example, existing multi-access session technology does not support transmission through at least two 3GPP paths and one non-3GPP path as shown in Figure 5 Multiple access session format.
  • N3GPP path switching will cause multiple N3GPP paths to exist at the same time, resulting in no way to support business flow data offloading during the switching process.
  • the existing UE is often unable to complete the handover process on time, or does not actively trigger the original path after completing the handover process. De-registration, which causes the UE to maintain dual registration status in the network for a long time, affecting the UE's ability to obtain services through the network.
  • embodiments of the present application provide a method for non-3GPP path switching.
  • multi-access session management process described in the embodiment of this application may be a multi-access session establishment process, a multi-access session modification process, a multi-access session adding process, or a multi-access session release process. Or multi-access session activation process, etc., which are not limited here.
  • the communication system may include a terminal device 600, an access and mobility management function (AMF) 610, a session management function (SMF) 620 and a user plane function (user) plane function, UPF)630.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • the terminal equipment 600 may also be called user equipment (UE), mobile station, mobile terminal, etc.
  • UE is used to represent the terminal.
  • Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of Things ( internet of things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • Terminals can be mobile phones, tablets, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.
  • the embodiments of this application do not limit the specific technology and specific equipment form used by the terminal.
  • the terminal device described in the embodiment of this application can be used for:
  • the AMF610 is used to perform functions such as mobility management and access authentication/authorization.
  • the access and mobility management function network element is also responsible for transmitting user policies to the terminal.
  • the AMF described in the embodiments of this application can be used for:
  • the SMF620 is used to perform functions such as session management, execution of control policies, selection of user plane functional network elements, and terminal Internet Protocol (IP) address allocation.
  • IP Internet Protocol
  • the SMF described in the embodiments of this application can be used for:
  • the first offloading rule is sent to the user plane device and/or the second offloading rule is sent to the terminal device.
  • the UPF630 is used to complete functions such as user plane data forwarding, session/flow level-based billing statistics, and bandwidth limitation.
  • the UPF described in the embodiments of this application can be used for:
  • the first offloading rule sent from the session management device is received, and the transmission path is determined according to the first offloading rule.
  • the multi-access session introduced above includes at least two non-3GPP transmission paths.
  • the first session request message includes switching indication information, and the switching indication information indicates to perform non-3GPP transmission path switching and/or indicates that the established target transmission path is a non-3GPP transmission path.
  • the first offloading rule is used to support the user plane device in determining a first target transmission path among the at least two non-3GPP transmission paths.
  • the second offloading rule is used to support the terminal device in determining a second target transmission path among the at least two non-3GPP transmission paths.
  • the first target transmission path in this embodiment of the present application may be one or more of multiple non-3GPP transmission paths.
  • the second target transmission path may be one or more of multiple non-3GPP transmission paths.
  • the first target transmission path in the embodiment of the present application may not include non-3GPP transmission paths.
  • the second target transmission path in the embodiment of the present application may also not include non-3GPP transmission paths.
  • the first offloading rule in the embodiment of the present application is used to support the user plane device in determining the first target transmission path among the at least two non-3GPP transmission paths. It can be understood that the user plane device is executing the non-3GPP transmission path. When using a 3GPP transmission path, the first offloading rule may be used to determine the transmission path. Similarly, the second offloading rule is used to support the terminal device in determining the second target transmission path among the at least two non-3GPP transmission paths. It can be understood that when the user plane device executes the non-3GPP transmission path, The second branching rule may be used to determine the transmission path.
  • the communication system can also include other network elements or networks.
  • it can also include unified data management (UDM) network elements and policy control function (PCF) network elements, located in Network DNs other than the operator's network are not limited here.
  • UDM unified data management
  • PCF policy control function
  • an embodiment of the present application provides a communication path switching method.
  • an exemplary flow chart of a communication method provided by an embodiment of the present application may include the following operations.
  • the embodiment shown in FIG. 7 can be applied to a communication system in a multi-session access scenario with at least two non-3GPP paths, such as the communication system shown in FIG. 6 .
  • the SMF 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 SMF can determine whether to perform non-3GPP path switching through multiple methods.
  • Determination method 1 The SMF receives the first session request message from the UE, and determines to perform the non-3GPP path switching according to the first session request message.
  • the first session request message may be a session establishment request message, or may be a session modification request message, which is not limited here.
  • the SMF determines to perform the non-3GPP path switching according to the first switching indication information, and the first switching indication information indicates to perform the non-3GPP path switching.
  • the 3GPP transmission path is switched and/or the target transmission path established is instructed to be a non-3GPP transmission path.
  • the SMF determines that the source transmission path for which the multi-access session has been established is a non-3GPP transmission path, according to the The session request determines to perform the non-3GPP transmission path switching.
  • the first session request message in this embodiment of the present application may also include a session identifier of the multi-access session, and the session identifier is used to determine the multi-access session of the terminal device.
  • Determination method 2 The SMF receives the second session request message from the AMF, and determines to perform the non-3GPP path switching according to the second session request message.
  • the second session request message may be a session creation session context message, or may be a session update session context message, which is not limited here.
  • the SMF determines to perform the non-3GPP path switching according to the second switching indication information, and the second switching indication information indicates to perform the non-3GPP path switching.
  • the 3GPP transmission path is switched and/or the target transmission path established is instructed to be a non-3GPP transmission path.
  • the SMF determines that the source transmission path for which the multi-access session has been established is a non-3GPP transmission path, according to the The session request determines to perform the non-3GPP transmission path switching.
  • the second session request message in this embodiment of the present application may also include a session identifier and/or a session context identifier of the multi-access session, where the session identifier is used to determine the multi-access session of the terminal device. Enter the session.
  • the second session request message may be sent after the AMF determines to perform non-3GPP transmission path switching in the multi-access session.
  • the AMF receives a non-access stratum (NAS) message for requesting path switching sent by the terminal device, determines that non-3GPP transmission path switching is performed in the multi-access session, and triggers the transmission to the SMF sends the second session request message.
  • NAS non-access stratum
  • the NAS message includes switching indication information, and the switching indication information indicates to perform non-3GPP transmission path switching and/or indicates that the established target transmission path is a non-3GPP transmission path.
  • the SMF sends the first offload rule to the UPF and/or the second offload rule to the UE.
  • the first offload rule is used to support the user plane device in determining a first target transmission path among the at least two non-3GPP transmission paths; the second offload rule is used to support the terminal device in the Determine a second target transmission path among at least two non-3GPP transmission paths.
  • the second offload rule may be sent to the corresponding UE through the AMF.
  • the SMF sends the first offloading rule to the corresponding UPF, which can be implemented by sending an N4 session modification request carrying the first offloading rule to the UPF.
  • contents of the first offloading rule and/or the second offloading rule used to perform transmission path switching described in the embodiments of this application may have multiple contents, and are not limited to the following ones:
  • the first offloading rule and/or the second offloading rule include the offloading rule used before non-3GPP path switching (original transmission path switching offloading rule) and the access priority indication used to indicate non-3GPP path switching. information.
  • the access priority indication information is used to indicate the target transmission path.
  • the target transmission path in the embodiment of the present application may be one or more of multiple non-3GPP transmission paths.
  • the non-3GPP transmission path may not be included.
  • the first offloading rule includes the offloading rule used by the user plane device before non-3GPP path switching, and access priority indication information.
  • the third offloading rule includes the offloading rule used by the terminal device before non-3GPP path switching, and access priority indication information.
  • the first offloading rule and/or the second offloading rule include offloading rules supporting non-3GPP path switching. Wherein, the offloading rules for non-3GPP path switching are different from the offloading rules for original path switching.
  • the first offloading rule includes a third offloading rule
  • the third offloading rule is used to instruct the user plane device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the second offloading rule includes a fourth offloading rule, and the fourth offloading rule instructs the terminal device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the first offloading rule and/or the second offloading rule include offloading rules supporting non-3GPP path switching, original path switching offloading rules, and trigger conditions corresponding to the offloading rules.
  • the first offloading rule includes the offloading rule used by the user plane device before non-3GPP path switching, the third offloading rule and the rule application condition, and the third offloading rule is used to instruct the user plane
  • the device performs redundant transmission through the at least two non-3GPP transmission paths, and the rule application condition is used to indicate that the offloading rule should be applied when performing path switching.
  • the second offloading rule includes the offloading rule used by the terminal device before the non-3GPP path switching, the fourth offloading rule and the rule application condition.
  • the fourth offloading rule is used to instruct the terminal device to pass the at least two offloading rules.
  • a non-3GPP transmission path performs redundant transmission, and the rule application condition is used to indicate that the offloading rule should be applied when performing path switching.
  • the first offloading rule and/or the second offloading rule is used to instruct the UPF to switch the service flow transmitted through the source non-3GPP transmission path to the target non-3GPP transmission path for transmission.
  • the target non-3GPP transmission path when 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.
  • the target non-3GPP transmission path when 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.
  • the first offloading rule may also instruct the UPF to switch the service flow transmitted through the source non-3GPP transmission path to the target 3GPP transmission path for transmission.
  • the second offloading rule may also instruct the UE to switch the service flow transmitted through the source non-3GPP transmission path to the target 3GPP transmission path for transmission.
  • the first offload rule and/or the second offload rule are determined according to local configuration before the SMF sends the first offload rule to the UPF and/or the second offload rule to the UE; or, the The first diversion rule and /or the second offloading rule is based on the policy and charging control (PCC) rule obtained from the PCF before the SMF sends the first offloading rule to the UPF and/or the second offloading rule to the UE.
  • PCC policy and charging control
  • the embodiment of the present application can also complete the non-3GPP path handover. Afterwards, the release of the signaling connection of the original non-3GPP transmission path is triggered.
  • the release of the signaling connection described in the embodiments of this application may be the release of signaling by the access network, or may also be the registration of the terminal device.
  • the AMF determines that the first condition for signaling connection release is met.
  • the AMF triggers the release of the trusted non-3GPP path after determining that the UE has completed switching from the trusted non-3GPP path to the untrusted non-3GPP path.
  • the AMF determines that the UE completes switching from the non-trusted non-3GPP path to the trusted non-3GPP path, it triggers the release of the non-trusted non-3GPP path.
  • the first condition described in the embodiments of this application is not limited to the following situations:
  • Case 1 The first timer started by the AMF after the terminal device completes the registration of the target non-3GPP transmission path expires.
  • the first timer is used to indicate the release of the triggering source non-3GPP transmission path signaling connection.
  • the AMF determines that when performing non-3GPP path switching, after the UE completes the registration of the first target transmission path, the source path de-registration timer is started, and the AMF determines that the source path de-registration timer expires. Finally, the AMF initiates a deregistration request to the UE.
  • Case 2 The second timer started by the AMF after the terminal device completes the registration of the target non-3GPP transmission path expires, and the terminal device does not complete the switching of the target non-3GPP transmission path. The second timer expires. The timer is used to indicate triggering the target non-3GPP transmission path signaling connection release.
  • the AMF determines that when performing non-3GPP path switching, after the UE completes the registration of the first target transmission path, the target path de-registration timer is started, and the AMF determines that the target path de-registration timer expires. , and then, the AMF initiates a deregistration request to the UE.
  • Case 3 After the AMF receives the request message for signaling connection release from the UE, the AMF initiates a deregistration request to the UE.
  • the request message for signaling connection release is used to instruct the AMF to The UE initiates a deregistration request for the target path or the source path.
  • Scenario 1 Perform path switching based on the first diversion rule and/or the second diversion rule provided by this application.
  • the method corresponding to this scenario can perform the following steps. It is assumed that before the process starts, the UE has established an MA PDU session through the trusted non-3GPP gateway function (TNGF), and The registration has been completed through the non-3GPP interworking function (N3IWF) and the connection of the Internet Protocol Security Protocol (IPSec) secure signaling plane of the UE and the N3IWF has been established.
  • TNGF trusted non-3GPP gateway function
  • IPSec Internet Protocol Security Protocol
  • the UE On the non-trusted non-3GPP path, the UE sends a NAS message to the AMF, where the NAS message carries the first session request message.
  • the first session request message may be a session establishment request message, or may also be a session modification request message.
  • the NAS message carries a session identifier and/or first switching indication information, and the session identifier is used to uniquely determine the session.
  • the first handover indication information may be a session request type (Request Type), where the request type may indicate an existing PDU session (Existing PDU Session), or a multiple access session request (MA PDU Request), or a new instruction mark.
  • Request Type a session request type
  • the request type may indicate an existing PDU session (Existing PDU Session), or a multiple access session request (MA PDU Request), or a new instruction mark.
  • the first switching indication information indicates to perform non-3GPP transmission path switching and/or indicates that the established target transmission path is a non-3GPP transmission path.
  • the session identifier and/or the first switching indication information in this embodiment of the present application may be carried in the first session request message, or the session identifier may be included in the NAS message in addition to the third Carried outside a session request message.
  • the AMF does not perceive the first switching indication information, and the SMF directly perceives the first switching indication information. If the first switching indication information is outside the first session establishment request and within the NAS message, the AMF directly senses the indication, and the AMF may instruct SMF the first switching indication information in subsequent step S803.
  • the AMF selects an appropriate SMF based on the received NAS message.
  • the AMF may select an appropriate SMF based on the session identifier in the received NAS message.
  • S803 AMF sends a second session request message to SMF.
  • the AMF may send the second session request message to the SMF after determining to perform non-3GPP path switching based on the NAS message received from the terminal device.
  • the second session request message may be a session creation session context message or a session update session context message.
  • the AMF identifies the first handover instruction information carried in the NAS message, determines based on the first handover instruction information that the current session management process is used to perform non-3GPP transmission path switching, and then sends the SMF the The second session request message.
  • the second session request message may carry one or more of the identifier of the session, the context identifier of the session, second handover indication information, or a radio access technology type (RAT Type).
  • RAT Type radio access technology type
  • the second switching indication information is used to indicate the access path type requested by the current session.
  • the second switching indication information indicates to perform non-3GPP transmission path switching and/or indicates that the established target transmission path is a non-3GPP transmission path.
  • the AMF may directly send the first switching indication information in the received NAS message as the second switching indication information in the second session request message to the SMF.
  • the first switching instruction information and the second switching instruction information are the same.
  • the second session request message sent by the AMF to the SMF may also carry the session identifier indicated in the NAS message, and/or the session context identifier, etc., which are not limited here.
  • the SMF obtains the subscription information of the UE from the unified data management (unified data management, UDM) device based on the second session request message, where the subscription information includes the session context information of the UE.
  • unified data management unified data management, UDM
  • the SMF may be based on the session identifier in the second session request message or the session context.
  • the document identifier obtains the UE's subscription information from UDM.
  • S805 SMF feeds back the above update session context response message to AMF.
  • S806 The SMF determines to perform non-3GPP transmission path switching in the multi-access session.
  • the SMF may determine to perform non-3GPP transmission path switching based on the second session request message received from the AMF.
  • the SMF determines to perform non-3GPP transmission path switching based on the second switching instruction information included in the second session request message.
  • the second switching instruction information indicates performing non-3GPP transmission path switching.
  • the SMF determines that the source transmission path for which the multi-access session has been established is a non-3GPP transmission path
  • the SMF determines that the established source transmission path is a non-3GPP transmission path.
  • the session request determines to perform the non-3GPP path switching.
  • the SMF determines the first offloading rule for UPF and/or the second offloading rule for UE.
  • the SMF may determine the first offloading rule and/or the second offloading rule based on local configuration; or, the SMF may determine the first offloading rule based on the PCC rule obtained from the PCF. and/or the second diversion rule.
  • the first offloading rule is included in a multiple access rule (Multiple Access Rule), used to support UPF in determining the first target transmission path among multiple transmission paths, and the multiple access session includes at least two non-3GPP transmissions. path.
  • Multiple Access Rule Multiple Access Rule
  • the second traffic splitting rule is included in the Access Traffic Steering Switching Splitting Rule (ATSSS rule) of the access service, and is used to support the UE in determining the second target transmission path among multiple transmission paths.
  • ATSSS rule Access Traffic Steering Switching Splitting Rule
  • the content of the first offloading rule and/or the second offloading rule can be referred to the relevant content introduction shown in FIG. 7 above, and will not be described again here.
  • the SMF selects the UPF corresponding to the multi-access session to initiate an N4 session modification request, where the N4 session modification request includes the first offloading rule.
  • the first offloading rule may be carried in the N4 rule included in the N4 session modification request.
  • the N4 rules described in the embodiments of this application may include packet detection rules (Packet Detection Rule, PDR), forwarding action rules (Forwarding Action Rule, FAR), multi-access rules (Multi Access Rule, MAR) and other rules.
  • the MAR rule includes the first offloading rule.
  • the UPF performs offloading of the service data flow based on the received first offloading rule.
  • the SMF sends an N1N2 transmission message to the AMF, where the N1N2 transmission message includes the second offloading rule.
  • the N1N2 transmission message includes information such as session identification, N2 interface session management information (N2SM information), and N1 interface session management container (N1SM Container).
  • N2SM information N2 interface session management information
  • N1SM Container N1 interface session management container
  • N1SM Container contains session-related parameter information such as PDU Session Establishment Accept (PDU Session Establishment Accept) and ATSSS rule.
  • PDU Session Establishment Accept PDU Session Establishment Accept
  • ATSSS rule is the first diversion rule mentioned above.
  • S811 AMF initiates a session request message to N3IWF, and the session request message carries the second offloading rule.
  • N3IWF determines how many Internet Protocol Security Protocol (Internet Protocol Security, IPSec) Child SAs to establish based on its own policies and configurations and which Quality of Service (QoS) flow (Flow) data each IPSec Child SA transmits.
  • IP Security Internet Protocol Security
  • QoS Quality of Service
  • Flow Quality of Service
  • N3IWF establishes an IPSec security association (Security Association, SA).
  • N3IWF will allocate the IP address of the IPSec Child SA (UP_IP_ADDRESS) to the UE. That is, if the UE wants 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.
  • UP_IP_ADDRESS IP address of the IPSec Child SA
  • the N3IWF initiates a session establishment accept message to the UE, which carries the second offloading rule.
  • the N3IWF initiates an N2 session response message to the AMF, indicating that the user plane resources on the N3IWF access network side have been established and carrying the tunnel endpoint identifier on the N3IWF side.
  • S816 The AMF initiates a session update request to the SMF and forwards session-related information from the access network side.
  • S817 SMF sends access network (AN) tunnel endpoint identification information on the N3IWF side to UPF through the N4 session modification process.
  • AN access network
  • S818 SMF sends a protocol data unit (PDU) session update context response message to AMF.
  • PDU protocol data unit
  • S820 TNGF initiates information exchange with the UE, and deletes the session context between the UE and TNGF on the trusted non-3GPP.
  • S821 TNGF sends an N2 resource release response to AMF.
  • the AMF initiates a session update request to the SMF, indicating that the trusted non-3GPP path session resources have been released.
  • the first offloading rule includes the offloading rule used by UPF before non-3GPP path switching
  • the second offloading rule includes the offloading rule used by the terminal device before non-3GPP path switching
  • the first offloading rule does not include the offloading rule used by UPF before non-3GPP path switching, and/or the second offloading rule does not include the offloading rule used by the terminal device before non-3GPP path switching, If the rules are met, subsequent steps S823 to S829 are executed.
  • S823 After the handover is completed, the SMF initiates an N4 session modification request, which carries the MAR offloading rules of the original MA PDU session.
  • the MAR offloading rules of the original MA PDU session refer to the offloading rules used before non-3GPP path switching.
  • the downlink data of the UE is offloaded according to the above MAR offloading rule.
  • the SMF initiates an N1N2 transmission message to the AMF, where the N1N2 transmission message carries the ATSSS offloading rule for the original MA PDU session.
  • S826 AMF initiates a session request to N3IWF, where the session request carries the ATSSS offloading rule of the original MA PDU session.
  • N3IWF initiates a PDU session modification instruction to the UE, where the PDU session modification instruction carries the ATSSS offloading rules of the original MA PDU session.
  • S828 After receiving the PDU session modification instruction, the UE accepts and executes the above ATSSS offloading rules. After completion, the UE sends a PDU session modification instruction response to N3IWF.
  • the uplink data of the UE is offloaded according to the above MAR offloading rule.
  • N3IWF forwards the response message received from the UE to the AMF.
  • the overall handover process can be divided into four stages, namely, the UE passes through the target path. Registration, establishing/adding MA PDU session on the target path, releasing source path session resources, and UE registering on the source path.
  • this embodiment uses the example of switching the non-3GPP path in the MA PDU from a trusted non-3GPP access path to an untrusted non-3GPP access path.
  • the reverse is also applicable.
  • the non-3GPP path in the MA PDU is switched from a trusted non-3GPP access path to an untrusted non-3GPP access path.
  • the process of switching the 3GPP path from the untrusted non-3GPP access path to the trusted non-3GPP access path can be obtained by referring to the content shown in Figure 8 above. Simply replace N3IWF with TNGF, which will not be described again here.
  • the MA PDU session handover process enables the UE and UPF to trigger new offload rules during the handover process.
  • the new offload rules can support the UE and/or UPF to select appropriate ones among multiple non-3GPP access paths. Path for data transmission to ensure business continuity during session switching.
  • Scenario 2 Path switching is performed based on the de-registration principle provided by this application.
  • De-registration situation 1 After the source path-based de-registration timer expires, source path de-registration is triggered.
  • Figure 9 takes the registration process under untrusted 3GPP access technology as an example.
  • the UE connects to an untrusted non-3GPP access network and is assigned an IP address.
  • the UE selects N3IWF and obtains the address information of the N3IWF.
  • IPsec Security Association IPsec Security Association
  • IPSec SA IPsec Security Association
  • IKE Internet Key Exchange
  • S903 The UE sends an IKE_AUTH request message to N3IWF.
  • the UE may carry first indication information in the registration request message, and the first indication information may be used to instruct execution of non-3GPP path switching and/or instruct establishment of a second non-3GPP transmission path.
  • the first indication information can be used by the AMF to determine whether the current registration request is used for subsequent session switching.
  • the AMF may also determine whether the current registration request is used for subsequent session switching based on the local configuration information when receiving the registration request message.
  • N3IWF sends an IKE_AUTH response message to the UE.
  • the response message includes an EAP-Request/5G-Start data packet.
  • the EAP-Request/5G-Start data packet can be used to notify the UE to initiate an EAP-5G session, for example, to notify the UE to start sending NAS messages (by adding the NAS Messages are encapsulated in EAP-5G data packets).
  • S905 The UE sends an IKE_AUTH request message to N3IWF.
  • the request message may include an EAP-Response/5G-NAS data packet, and the data packet may include AN parameters and a registration request message.
  • the AN parameters may include parameter information used by the N3IWF to select an AMF, such as GUAMI, selected public land mobile network (PLMN) ID (or a combination of PLMN ID and network identifier (network identifier, NID)), etc. .
  • N3IWF performs AMF selection and sends the registration request message to AMF.
  • the N3IWF may also forward the first indication information in the registration request message to the AMF.
  • S907 AMF sends an NGAP initial context setup request (NGAP initial context setup request) message to N3IWF, which includes the N3IWF key.
  • NGAP initial context setup request NGAP initial context setup request
  • S907 is executed after the authentication between the AMF and the UE is successful.
  • the AMF selects an authentication server function (AUSF) and sends an authentication request message to the AUSF. Then, the AUSF performs the authentication process on the UE and obtains authentication data from the UDM.
  • AUSF authentication server function
  • the authentication-related data packets can be encapsulated through NAS messages, and the NAS messages can be encapsulated through EAP/5G-NAS data packets.
  • the AUSF sends the security anchor function (seaf) key to the AMF, and the AMF uses the key to derive the NAS security key and the N3IWF security key.
  • the N3IWF key is used by the UE and N3IWF.
  • the AMF sends a NAS security mode command (NAS security mode command) to the UE to activate NAS security, and executes S907 after successfully activating NAS security.
  • NAS security mode command NAS security mode command
  • N3IWF sends the authentication protocol (extensible authentication protocol, EAP) success (Success) information to the UE.
  • the AMF sends an N2 message to the N3IWF, where the N2 message includes a NAS Registration Accept message (NAS Registration Accept) sent to the UE.
  • N2 message includes a NAS Registration Accept message (NAS Registration Accept) sent to the UE.
  • N3IWF sends a NAS registration acceptance message to the UE through the newly established signaling IPSec SA (signalling IPSec SA).
  • AMF selects to start the first timer of the source path (trusted non-3GPP).
  • AMF will determine that the current registration request is suitable for subsequent session switching based on the above handover indication information or locally configured UE registration information, and select the first timing to open the source path (trusted non-3GPP)
  • the first timer is used to release the signaling connection of the source path.
  • S912 When the UE performs the handover process between trusted non-3GPP and untrusted non-3GPP, when the first timer expires, trigger the AMF to release the source path signaling connection to the UE.
  • the AMF is triggered to execute the access network side resource release process of the source path, or the AMF is triggered to execute the UE de-registration process of the source path.
  • S914 AMF sends an N2UE context release instruction of the origin path (trusted non-3GPP) to TNGF.
  • S915 An IKE INFORMATIONAL message is initiated between TNGF and UE, releasing the IKEv2 tunnel between UE and TNGF and deleting the UE context on TNGF.
  • S916 TNGF feeds back the N2UE context to AMF to complete the release.
  • the AMF determines whether the UE is used for subsequent session switching when registering, and decides to start the de-registration timer on the source path to prevent the UE from maintaining dual registration status on the trusted non-3GPP and non-trusted 3GPP paths for a long time.
  • MA PDU session switching on non-3GPP paths can also be supported.
  • De-registration situation 2 After the de-registration timer expires based on the target path, the target path is triggered to register.
  • Figure 5 takes the registration process under untrusted 3GPP access technology as an example.
  • the UE connects to a non-trusted non-3GPP access network and is assigned an IP address.
  • the UE selects N3IWF and obtains the address information of the N3IWF.
  • S1002 The UE establishes IPsec Security Association (IPSec SA) with N3IWF by initiating Internet Key Exchange (IKE) initial exchange.
  • IPSec SA IPsec Security Association
  • IKE Internet Key Exchange
  • S1003 The UE sends an IKE_AUTH request message to N3IWF.
  • the UE may carry first indication information in the registration request message, and the first indication information may be used to instruct execution of non-3GPP path switching and/or instruct establishment of a second non-3GPP transmission path.
  • the first indication information can be used by the AMF to determine whether the current registration request is used for subsequent session switching.
  • the AMF may also determine whether the current registration request is used for subsequent session switching based on the local configuration information when receiving the registration request message.
  • N3IWF sends an IKE_AUTH response message to the UE.
  • the response message includes an EAP-Request/5G-Start data packet.
  • the EAP-Request/5G-Start data packet can be used to notify the UE to initiate an EAP-5G session, for example, to notify the UE to start sending NAS messages (by adding the NAS Messages are encapsulated in EAP-5G data packets).
  • S1005 The UE sends an IKE_AUTH request message to N3IWF.
  • the request message may include an EAP-Response/5G-NAS data packet, and the data packet may include AN parameters and a registration request message.
  • the AN parameters may include parameter information used by the N3IWF to select an AMF, such as GUAMI, selected PLMN ID (or PLMN ID and NID), etc.
  • N3IWF performs AMF selection and sends the registration request message to AMF.
  • the N3IWF may also forward the first indication information in the registration request message to the AMF.
  • S1007 AMF sends an NGAP Initial Context Setup Request message to N3IWF, including the N3IWF key.
  • S1007 is executed after the authentication between the AMF and the UE is successful.
  • the AMF selects the AUSF and sends an authentication request message to the AUSF. Then, the AUSF performs the authentication process on the UE and obtains authentication data from the UDM.
  • the authentication-related data packets can be encapsulated through NAS messages, and the NAS messages can be encapsulated through EAP/5G-NAS data packets.
  • AUSF sends the SEAF key to AMF, and AMF uses the key to derive the NAS security key and the N3IWF security key.
  • the N3IWF key is used by the UE and N3IWF to establish IPSec SA.
  • the AMF sends a NAS Security Mode Command to the UE to activate NAS security, and executes S1007 after successfully activating NAS security.
  • N3IWF sends EAP-Success to the UE.
  • AMF sends an N2 message to N3IWF, where the N2 message includes a NAS Registration Accept message (NAS Registration Accept) sent to the UE.
  • N2 message includes a NAS Registration Accept message (NAS Registration Accept) sent to the UE.
  • N3IWF sends a NAS registration acceptance message to the UE through the newly established signaling IPSec SA.
  • AMF selects to start the second timer of the target path (trusted non-3GPP).
  • AMF will determine that the current registration request is suitable for subsequent session switching based on the above handover indication information or locally configured UE registration information, and select the second timing to open the target path (trusted non-3GPP)
  • the second timer is used to release the signaling connection of the source path.
  • S1012 When the UE is executing the handover process between trusted non-3GPP and untrusted non-3GPP, when the second timer expires and the UE has not completed the switch of the target path, trigger the AMF to execute the source to the UE. Release of path signaling connection.
  • the AMF is triggered to execute the access network side resource release process of the target path, or the AMF is triggered to execute the UE de-registration process of the target path.
  • S1014 AMF initiates an N2UE context release instruction for the target path (trusted non-3GPP) to TNGF.
  • S1015 An IKE INFORMATIONAL message is initiated between TNGF and UE, releasing the IKEv2 tunnel between UE and TNGF and deleting the UE context on TNGF.
  • S1016 TNGF feeds back the N2UE context to AMF to complete the release.
  • the AMF determines whether the UE is used for subsequent session switching when registering, and decides to start the de-registration timer on the target path to prevent the UE from maintaining dual registration status on the trusted non-3GPP and non-trusted 3GPP paths for a long time.
  • MA PDU session switching on non-3GPP paths can also be supported.
  • the UE in the embodiment of the present application can send a signaling connection release request message to the corresponding AMF at any time according to the actual situation, so that the signal is received.
  • the AMF of the request message for connection release causes the UE to perform signaling connection release of the target path or source path to the UE.
  • the request message for signaling connection release is used to instruct the AMF to initiate a deregistration request for a target path or a source path to the UE.
  • FIGS 11 and 12 are schematic structural diagrams of possible communication devices provided by embodiments of the present application. These communication devices can be used to implement the functions of SMF, UE, UPF or AMF in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments.
  • the communication device may be an SMF, UE, UPF or AMF, or may be a module (such as a chip) applied to the SMF, UE, UPF or AMF.
  • the communication device 1100 includes a processing unit 1110 and a transceiver unit 1120 .
  • the communication device 1100 is used to implement the functions of SMF, UE, UPF or AMF in the method embodiments shown in FIGS. 6 to 9 .
  • the processing unit 1110 is configured to determine 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 transceiver unit 1120 is configured to send a first offload rule to the user plane device and/or send a second offload rule to the terminal device; the first offload rule is used to support the user plane device in the at least two non-3GPP transmissions.
  • the first target transmission path is determined among the paths; the second offloading rule is used to support the terminal device in determining the second target transmission path among the at least two non-3GPP transmission paths.
  • processing unit 1110 is specifically used to:
  • the session request message includes switching indication information, the switching indication information indicates performing non-3GPP transmission path switching and/or indicates the establishment of The target transmission path is a non-3GPP transmission path;
  • the session request message is a first session request message sent by the terminal device after determining to execute a non-3GPP transmission path; or, the session request message is a second session message sent by the mobile management device after determining to execute a non-3GPP transmission path. Request message.
  • processing unit 1110 is specifically used to:
  • the handover indication information indicates that the established target transmission path is a non-3GPP transmission path, and when it is determined that the source transmission path for which the multi-access session has been established is a non-3GPP transmission path, it is determined to execute the non-3GPP transmission path according to the session request. 3GPP path switching.
  • the session request message further includes a session identifier of the multi-access session; the session identifier is used to determine the multi-access session of the terminal device.
  • the session request message further includes a session context identifier of the multi-access session; the session context identifier is used to determine the multi-access session of the terminal device.
  • the first diversion rule includes:
  • the offloading rules used by the user plane device before non-3GPP path switching, and the access priority indication information is used to indicate the first target transmission path;
  • the second diversion rule includes:
  • the first target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path;
  • the second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.
  • the first diversion rule includes:
  • the third offloading rule is used to instruct the user plane device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the second diversion rule includes:
  • a fourth offload rule instructs the terminal device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the first diversion rule includes:
  • the offloading rules, the third offloading rule and the rule application conditions used by the user plane device before non-3GPP path switching are used to instruct the user plane device to perform transmission through the at least two non-3GPP transmission paths.
  • the rule application condition is used to indicate that the offloading rule should be applied when performing path switching.
  • the second diversion rule includes:
  • the fourth offloading rule is used to instruct the terminal equipment to perform redundancy through the at least two non-3GPP transmission paths.
  • Transmission, the rule application condition is used to indicate that the offloading rule should be applied when performing path switching.
  • the processing unit 1110 is configured to determine 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.
  • Transceiver unit 1120 configured to send a first session request message to the session management device, where the first session request message includes switching indication information, the switching indication information indicates execution of non-3GPP transmission path switching and/or indicates an established target transmission path.
  • the transceiver unit 1120 is also configured to receive a second offload rule sent from the session management device; the second offload rule is used to support the terminal device in the at least two non-3GPP Determine a second target transmission path among the transmission paths; the processing unit 1110 is further configured to determine a transmission path according to the second offloading rule.
  • the first session request message further includes the multi-access session identifier, and the multi-access session identifier is used to determine the multi-access session of the terminal device.
  • the second diversion rule includes:
  • the second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.
  • the second diversion rule includes:
  • a fourth offload rule instructs the terminal device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the second diversion rule includes:
  • the fourth offloading rule is used to instruct the terminal equipment to perform redundancy through the at least two non-3GPP transmission paths.
  • Transmission, the rule application condition is used to indicate that the offloading rule should be applied when performing path switching.
  • the transceiver unit 1120 is configured to receive the first offload rule sent from the session management device when performing non-3GPP transmission path switching in a multi-access session; the first offload rule Used to support the user plane device in determining the first target transmission path among the at least two non-3GPP transmission paths, and the multi-access session includes at least two non-3GPP transmission paths; the processing unit 1110 is configured to determine the first target transmission path according to the The first offloading rule determines the transmission path.
  • the first diversion rule includes:
  • the offloading rules used by the user plane device before non-3GPP path switching, and the access priority indication information is used to indicate the first target transmission path.
  • the first target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.
  • the first diversion rule includes:
  • the third offloading rule is used to instruct the user plane device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the first diversion rule includes:
  • the offloading rules, the third offloading rule and the rule application conditions used by the user plane device before non-3GPP path switching are used to instruct the user plane device to perform transmission through the at least two non-3GPP transmission paths.
  • the rule application condition is used to indicate that the offloading rule should be applied when performing path switching.
  • the processing unit 1110 is configured to determine 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 transceiver unit 1120 is configured to send a second request message to the session management device, where the second request message includes switching indication information, the switching indication information indicates performing a non-3GPP transmission path switching and/or indicates that the established target transmission path is a non-3GPP transmission path switching.
  • the second offloading rule is used to support the terminal device in determining a second target transmission path among the at least two non-3GPP transmission paths;
  • the second offloading rule is sent to the terminal device.
  • the second request message further includes the multi-access session identifier, and the multi-access session identifier is used to determine the multi-access session of the terminal device.
  • the second request message further includes a context identifier of the multi-access session, and the context identifier of the multi-access session is used to determine the multi-access session of the terminal device.
  • the second diversion rule includes:
  • the second target transmission path is a trusted non-3GPP transmission path or an untrusted non-3GPP transmission path.
  • the second diversion rule includes:
  • a fourth offload rule instructs the terminal device to perform redundant transmission through the at least two non-3GPP transmission paths.
  • the second diversion rule includes:
  • the fourth offloading rule is used to instruct the terminal equipment to perform redundancy through the at least two non-3GPP transmission paths.
  • Transmission, the rule application condition is used to indicate that the offloading rule should be applied when performing path switching.
  • processing unit 1110 is used for:
  • the non-access layer message includes switching instruction information, and the switching instruction information indicates performing non-3GPP transmission path switching.
  • the transmission path is switched and/or the target transmission path established is instructed to be a non-3GPP transmission path.
  • processing unit 1110 is also used to:
  • the mobility management device determines that the first condition for signaling connection release is met; the mobility management device releases the signaling of the terminal device on the target non-3GPP transmission path or the source non-3GPP transmission path. connect.
  • the first condition for signaling connection release includes:
  • the second timer is used to indicate triggering the target non-3GPP transmission path signaling connection release.
  • processing unit 1110 is also used to:
  • a third request message is sent to the session management device.
  • the third request message is used to instruct the application of the terminal device and/or the user plane device in the non-3GPP transmission path. Switch the previously used diversion rule.
  • processing unit 1110 and the transceiver unit 1120 can be obtained directly by referring to the relevant descriptions in the method embodiments shown in Figures 7 to 10, and will not be described again here.
  • FIG. 12 is a schematic diagram of a device 1200 provided by an embodiment of the present application.
  • the device 1200 may be an electronic device, or a component of an electronic device, such as a chip or an integrated circuit.
  • the device 1200 may include at least one processor 1202 and a communication interface 1204. Further, optionally, the device may also include at least one memory 1201. Furthermore, bus 1203 can optionally be included. Among them, the memory 1201, the processor 1202 and the communication interface 1204 are connected through the bus 1203.
  • the memory 1201 is used to provide storage space, and the operating system and computer programs can be stored in the storage space. Wait for data.
  • the memory 1201 mentioned in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories.
  • the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the processor 1202 is a module that performs arithmetic operations and/or logical operations, and may be a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor unit (MPU), Application specific integrated circuit (ASIC), field programmable gate array (FPGA), complex programmable logic device (CPLD), co-processor (assisting the central processor to complete Corresponding processing and application), microcontroller unit (microcontroller unit, MCU) and other processing modules, or a combination of one or more.
  • CPU central processing unit
  • GPU graphics processing unit
  • MPU microprocessor unit
  • ASIC Application specific integrated circuit
  • FPGA field programmable gate array
  • CPLD complex programmable logic device
  • co-processor assisting the central processor to complete Corresponding processing and application
  • microcontroller unit microcontroller unit, MCU
  • other processing modules or a combination of one or more.
  • the processor is a general-purpose processor, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • Communication interface 1204 may be used to provide information input or output to the at least one processor. And/or the communication interface can be used to receive data sent from the outside and/or send data to the outside. It can be a wired link interface such as an Ethernet cable, or a wireless link (Wi-Fi, Bluetooth, Universal wireless transmission, vehicle short-distance communication technology, etc.) interface. Optionally, the communication interface 1204 may also include a transmitter (such as a radio frequency transmitter, an antenna, etc.) or a receiver coupled to the interface.
  • a transmitter such as a radio frequency transmitter, an antenna, etc.
  • the above-mentioned device 1200 may be the SMF in the above method embodiment or a component in the SMF, such as a chip or an integrated circuit.
  • the processor 1202 in the device 1200 is used to read the computer program stored in the memory 1201 and control the SMF to perform the following operations:
  • the first offload rule is used to support the user plane device in determining a first target transmission path among the at least two non-3GPP transmission paths; the second offload rule is used to support the terminal device in the at least two non-3GPP transmission paths. Determine the second target transmission path among the non-3GPP transmission paths.
  • the processor 1202 in the SMF can also be used to read the program in the memory 1201 and execute the SMF execution method flow in S701 to S702 as shown in Figure 7; or execute S800 as shown in Figure 8 ⁇ The method flow of SMF execution in S829; or the method flow of SMF execution in S901 ⁇ S916 shown in Figure 9; or the method flow of S1001 ⁇ S1016 shown in Figure 10.
  • the above-mentioned device 1200 may be the terminal device or the terminal device in the above method embodiment. components in a device, such as chips or integrated circuits.
  • the processor 1202 in the device 1200 is used to read the computer program stored in the memory 1201 and control the terminal device to perform the following operations:
  • non-3GPP transmission path switching in a multi-access session including at least two non-3GPP transmission paths; sending a first session request message to the session management device, the first session request message including switching indication information , the switching indication information indicates execution of non-3GPP transmission path switching and/or indicates that the established target transmission path is a non-3GPP transmission path; receiving a second offloading rule sent from the session management device; the second offloading rule is used to The terminal device is supported to determine a second target transmission path among the at least two non-3GPP transmission paths; and the transmission path is determined according to the second offloading rule.
  • the processor 1202 in the UE can also be used to read the program in the memory 1201 and execute the method flow of SMF execution in S701 to S702 as shown in Figure 2; or execute S800 as shown in Figure 8 ⁇ The method flow of SMF execution in S829; or the method flow of SMF execution in S901 ⁇ S916 shown in Figure 9; or the method flow of S1001 ⁇ S1016 shown in Figure 10.
  • the above-mentioned device 1200 may be the AMF in the above method embodiment or a component in the AMF, such as a chip or an integrated circuit.
  • the processor 1202 in the device 1200 is used to read the computer program stored in the memory 1201 and control the AMF to perform the following operations:
  • the multi-access session including at least two non-3GPP transmission paths; sending a second request message to the session management device, where the second request message includes switching indication information,
  • the switching instruction information indicates to perform non-3GPP transmission path switching and/or indicates that the established target transmission path is a non-3GPP transmission path; receives a second offloading rule sent from the session management device; the second offloading rule is used to support
  • the terminal device determines a second target transmission path among the at least two non-3GPP transmission paths; sends the second offloading rule to the terminal device; or,
  • the processor 1202 in the device 1200 is used to read the computer program stored in the memory 1201 and control the AMF to perform the following operations:
  • the processor 1202 in the AMF can also be used to read the program in the memory 1201 and execute the method flow of SMF execution in S701 to S702 as shown in Figure 2; or execute S800 as shown in Figure 8 ⁇ The method flow of SMF execution in S829; or the method flow of SMF execution in S901 ⁇ S916 shown in Figure 9; or the method flow of S1001 ⁇ S1016 shown in Figure 10.
  • the above-mentioned device 1200 may be the UPF in the above method embodiment or a component in the UPF, such as a chip or an integrated circuit.
  • the processor 1202 in the device 1200 is used to read the computer program stored in the memory 1201 and control the UPF to perform the following operations:
  • the first offload rule Used to receive a first offload rule sent from a session management device when performing non-3GPP transmission path switching in a multi-access session; the first offload rule is used to support the user plane device in the at least two non-3GPP A first target transmission path is determined among the transmission paths, and the multi-access session includes at least two non-3GPP transmission paths; the transmission path is determined according to the first offloading rule.
  • the processor 1202 in the UPF can also be used to read the program in the memory 1201 and execute the method flow of SMF execution in S701 to S702; or execute the SMF execution in S800 to S829 as shown in Figure 8 The method flow; or execute the method flow of SMF execution in S901 to S916 as shown in Figure 9; or execute the method flow of SMF execution in S1001 to S1016 as shown in Figure 10.
  • An embodiment of the present application also provides a communication path switching system, including a terminal device, an SMF, and an AMF.
  • a communication path switching system including a terminal device, an SMF, and an AMF.
  • UPF is also included.
  • the processor in the embodiment of the present application can be a central processing unit (Central Processing Unit, CPU), or other general-purpose processor, digital signal processor (Digital Signal Processor, DSP), or application specific integrated circuit. (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • At least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or Multiple. "Multiple" means two or more, and other quantifiers are similar.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the computer program product includes one or more computer instructions.
  • 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 in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, solid state disk (SSD)), etc.
  • the various illustrative logic units and circuits described in the embodiments of this application can be implemented by a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, Discrete gate or transistor logic, discrete hardware components, or any combination of the foregoing are designed to implement or operate the functions described.
  • the general-purpose processor may be a microprocessor.
  • the general-purpose processor may also be any conventional processor, controller, microcontroller or state machine.
  • a processor may also be implemented as a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration. accomplish.
  • the steps of the method or algorithm described in the embodiments of this application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • Software units can be stored in Random Access Memory (RAM), flash memory, read-only memory (Read-Only Memory, ROM), EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROM or laptops. Any other form of storage media in the field.
  • the storage medium can be connected to the processor, so that the processor can read information from the storage medium and can store and write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and storage medium can be housed in an ASIC.
  • the above functions described in this application may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions may be stored on a computer-readable medium, or transmitted on a computer-readable medium in the form of one or more instructions or code.
  • Computer-readable media includes computer storage media and communications media that facilitate transfer of a computer program from one place to another. Storage media can be any available media that can be accessed by a general purpose or special purpose computer.
  • Such computer-readable media may include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that may be used to carry or store instructions or data structures and Other media containing program code in a form readable by a general-purpose or special-purpose computer, or by a general-purpose or special-purpose processor.
  • any connection may be properly defined as a computer-readable medium, for example, if the software is transferred from a website, server, or other remote source to a computer over a coaxial cable, fiber optic cable, twisted pair cable, or digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless and microwave are also included in the definition of computer-readable media.
  • DSL digital subscriber line
  • the discs and discs include compressed discs, laser discs, optical discs, Digital Versatile Discs (DVD), floppy disks and Blu-ray discs. Disks usually copy data magnetically, while discs usually use Lasers optically copy data. Combinations of the above can also be contained in a computer-readable medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种通信方法及装置，用于在多接入会话中，提供非3GPP路径切换的方案。方法包括：会话管理设备确定在多接入会话中执行非3GPP传输路径切换，多接入会话包括至少两个非3GPP传输路径；会话管理设备向用户面设备发送第一分流规则和/或向终端设备发送第二分流规则；第一分流规则用于支持所述用户面设备在所述至少两个3GPP传输路径中确定第一目标传输路径；第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径。通过该方法，当确定执行非3GPP路径切换时，使得UE和UPF在切换过程中，基于新的分流规则能够在多条非3GPP接入路径中选择合适的路径进行数据传输，保障会话切换时的业务连续性。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2022年03月29日提交中国专利局、申请号为202210318790.2、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
在通信传输过程中，经常通过建立多接入会话(multi-access PDU Session，MA PDU Session)将需要发送的业务流数据，同时通过第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)接入网络(路径)以及非3GPP接入网络(路径)进行传输，以提升传输效率。
然而，现有多接入会话技术仅支持通过一个3GPP接入网络(路径)以及一个非3GPP接入网络(路径)进行传输，并不支持通过两个以上的接入网络(路径)传输。例如，当多接入会话场景为通过至少两个非3GPP接入网络(路径)传输时，实现非3GPP路径切换会使得多个非3GPP路径同时存在，从而导致终端设备(user equipment，UE)和用户面设备(user plane function，UPF)无法在切换的过程中有效的执行业务数据的分流，可能会导致业务中断，从而影响用户体验。
综上，目前并没有在多接入会话场景下，支持非3GPP路径切换的方法。
发明内容
本申请提供一种通信方法和装置，用以在多接入会话中，提供非3GPP路径切换的方案，更好的支持业务流数据的分流，保障通信的连续性，降低系统开销。
第一方面，提供一种通信方法。该方法可以由会话管理设备执行，或者类似会话管理设备功能的芯片执行。该方法中，会话管理设备确定在多接入会话中执行非3GPP传输路径切换，所述多接入会话包括至少两个非3GPP传输路径；所述会话管理设备向用户面设备发送第一分流规则和/或向终端设备发送第二分流规则；所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径；所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径。
在该实施例中，所述第一目标传输路径可以是多个非3GPP传输路径中的一个或者多个。
此外，当非3GPP传输路径都不可用时，本申请实施例中所述第一目标传输路径也可以是不包括非3GPP传输路径。
所述第二目标传输路径可以是多个非3GPP传输路径中的一个或者多个。此外，当非3GPP传输路径都不可用时，本申请实施例中所述第二目标传输路径也可以是不包括非3GPP传输路径。
其中，本申请实施例中所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径，可以理解为所述用户面设备在执行非3GPP传输路径时，可以使用所述第一分流规则来确定传输路径。同理，所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径，可以理解为所述用户面设备在执行非3GPP传输路径时，可以使用所述第二分流规则来确定传输路径。
在该实施例中，所述多接入会话管理流程可以是多接入会话建立流程，或多接入会话修改流程，或多接入会话添加流程，或多接入会话释放流程，或多接入会话激活流程等。
基于上述方案，在多路径会话切换流程中，当确定需要执行非3GPP传输路径切换时，使得终端设备和用户面设备在切换过程中触发支持存在多条非3GPP传输路径的分流规则，例如，触发的分流规则可以支持UE和/或UPF在多条非3GPP传输路径中选择合适的传输路径进行数据传输，有效的执行业务数据的分流，从而保障会话切换时的业务连续性。
一种可能的情况中，所述会话管理设备根据接收到的会话请求消息，确定在多接入会话中执行非3GPP传输路径切换，所述会话请求消息包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径；所述会话请求消息是所述终端设备在确定执行非3GPP传输路径后发送的第一会话请求消息；或者，所述会话请求消息是移动管理设备在确定执行非3GPP传输路径后发送的第二会话请求消息。
在该实施例中，所述第一会话请求消息可以是会话建立请求消息，或者，所述第一会话请求消息可以是会话修改请求消息等，在此并不进行限定。
所述第二会话请求消息可以是会话创建上下文消息，或者，所述第二会话请求消息可以是会话更新会话上下文消息等，在此不进行限定。
基于上述方案，本申请实施例提供了一种会话管理设备确定是否执行非3GPP传输路径切换的方式，例如，所述会话管理设备可以根据接收到的会话请求消息进行确定是否需要执行。
一种可能的情况中，当所述切换指示信息指示建立的目标传输路径为非3GPP传输路径时，所述会话管理设备在确定所述多接入会话已建立的源传输路径为非3GPP传输路径时，根据所述会话请求确定执行所述非3GPP路径切换。
一种可能的情况中，所述会话请求消息还包括所述多接入会话的会话标识；所述会话标识用于确定所述终端设备的所述多接入会话。
一种可能的情况中，所述会话请求消息还包括所述多接入会话的会话上下文标识；所述会话上下文标识用于确定所述终端设备的所述多接入会话。
一种可能的情况中，所述第一分流规则，包括：
所述用户面设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息；所述接入优先级指示信息，用于指示所述第一目标传输路径；
所述第二分流规则，包括：
所述终端设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息；所述接入优先级指示信息，用于指示所述第二目标传输路径。
在该实施例中，接入优先级信息可以是无线接入技术(radio access technology，RAT)类型(type)。其中，如果RAT type为可惜非3GPP接入(trusted non-3GPP access)，则指示用户面设备的非3GPP传输路径为可信非3GPP路径。如果RAT type为不信任非3GPP 访问(untrusted non-3GPP access)，则指示用户面设备的非3GPP传输路径为非可信非3GPP路径。如果，RAT type为3GPP访问(3GPP access)，则指示用户面设备的非3GPP传输路径全部迁移到3GPP传输路径。
一种可能的情况中，所述第一目标传输路径为可信非3GPP传输路径或非可信非3GPP传输路径；
所述第二目标传输路径为可信非3GPP传输路径或非可信非3GPP传输路径。
一种可能的情况中，在执行非3GPP传输路径切换时，切换之前的源非3GPP传输路径可以为非可信非3GPP传输路径，切换之后的目标非3GPP传输路径可以为可信非3GPP传输路径；或，
在执行非3GPP传输路径切换时，切换之前的源非3GPP传输路径可以为可信非3GPP传输路径，切换之后的目标非3GPP传输路径可以为非可信非3GPP传输路径。
一种可能的情况中，所述第一分流规则，包括：第三分流规则，所述第三分流规则用于指示所述用户面设备通过所述至少两个非3GPP传输路径进行冗余传输。
一种可能的情况中，所述第二分流规则，包括：第四分流规则，所述第四分流规则指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输。
一种可能的情况中，所述第一分流规则，包括：所述用户面设备在非3GPP路径切换之前使用的分流规则、第三分流规则以及规则应用条件，所述第三分流规则用于指示所述用户面设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
一种可能的情况中，所述第二分流规则，包括：所述终端设备在非3GPP路径切换之前使用的分流规则、第四分流规则以及规则应用条件，所述第四分流规则用于指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
第二方面，提供一种通信方法。该方法可以由终端设备执行，或者类似终端设备功能的芯片执行。该方法中，终端设备确定在多接入会话中执行非3GPP传输路径切换，所述多接入会话包括至少两个非3GPP传输路径；所述终端设备向会话管理设备发送第一会话请求消息，所述第一会话请求消息包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径；所述终端设备接收来自所述会话管理设备发送的第二分流规则；所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径；所述终端设备根据所述第二分流规则确定传输路径。
在该实施例中，所述第二目标传输路径可以是多个非3GPP传输路径中的一个或者多个。此外，当非3GPP传输路径都不可用时，本申请实施例中所述第二目标传输路径也可以是不包括非3GPP传输路径。
其中，所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径，可以理解为所述用户面设备在执行非3GPP传输路径时，可以使用所述第二分流规则来确定传输路径。
在该实施例中，所述多接入会话管理流程可以是多接入会话建立流程，或多接入会话修改流程，或多接入会话添加流程，或多接入会话释放流程，或多接入会话激活流程等。
基于上述方案，在多路径会话切换流程中，当确定需要执行非3GPP传输路径切换时，使得终端设备和用户面设备在切换过程中触发支持存在多条非3GPP传输路径的分流规则，例如，触发的分流规则可以支持UE和/或UPF在多条非3GPP传输路径中选择合适的传输路径进行数据传输，有效的执行业务数据的分流，从而保障会话切换时的业务连续性。
在一种可能的实现方式中，所述第一会话请求消息还包括所述多接入会话标识，所述多接入会话标识用于确定所述终端设备的所述多接入会话。
在一种可能的实现方式中，所述第二分流规则，包括：所述终端设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息；所述接入优先级指示信息，用于指示所述第二目标传输路径。
在一种可能的实现方式中，所述第二目标传输路径为可信非3GPP传输路径或非可信非3GPP传输路径。
在一种可能的实现方式中，所述第二分流规则，包括：第四分流规则，所述第四分流规则指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输。
在一种可能的实现方式中，所述第二分流规则，包括：所述终端设备在非3GPP路径切换之前使用的分流规则、第四分流规则以及规则应用条件，所述第四分流规则用于指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
第三方面，提供一种通信方法。该方法可以由用户面设备执行，或者类似用户面设备功能的芯片执行。该方法中，在多接入会话中执行非3GPP传输路径切换时，用户面设备接收来自会话管理设备发送的第一分流规则；所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径，所述多接入会话包括至少两个非3GPP传输路径；所述用户面设备根据所述第一分流规则确定传输路径。
在该实施例中，所述第一目标传输路径可以是多个非3GPP传输路径中的一个或者多个。
此外，当非3GPP传输路径都不可用时，本申请实施例中所述第一目标传输路径也可以是不包括非3GPP传输路径。
所述第二目标传输路径可以是多个非3GPP传输路径中的一个或者多个。此外，当非3GPP传输路径都不可用时，本申请实施例中所述第二目标传输路径也可以是不包括非3GPP传输路径。
其中，本申请实施例中所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径，可以理解为所述用户面设备在执行非3GPP传输路径时，可以使用所述第一分流规则来确定传输路径。
在该实施例中，所述多接入会话管理流程可以是多接入会话建立流程，或多接入会话修改流程，或多接入会话添加流程，或多接入会话释放流程，或多接入会话激活流程等。
基于上述方案，在多路径会话切换流程中，当确定需要执行非3GPP传输路径切换时，使得终端设备和用户面设备在切换过程中触发支持存在多条非3GPP传输路径的分流规则，例如，触发的分流规则可以支持UE和/或UPF在多条非3GPP传输路径中选择合适的传输路径进行数据传输，有效的执行业务数据的分流，从而保障会话切换时的业务连续性。
在一种可能的实现方式中，所述第一分流规则，包括：
所述用户面设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息；所述接入优先级指示信息，用于指示所述第一目标传输路径。
在一种可能的实现方式中，所述第一目标传输路径为可信非3GPP传输路径或非可信非3GPP传输路径。
在一种可能的实现方式中，所述第一分流规则，包括：
第三分流规则，所述第三分流规则用于指示所述用户面设备通过所述至少两个非3GPP传输路径进行冗余传输。
在一种可能的实现方式中，所述第一分流规则，包括：
所述用户面设备在非3GPP路径切换之前使用的分流规则、第三分流规则以及规则应用条件，所述第三分流规则用于指示所述用户面设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
第四方面，提供一种通信方法。该方法可以由移动管理设备执行，或者类似移动管理设备功能的芯片执行。该方法中，移动管理设备确定在多接入会话中执行非3GPP传输路径切换，所述多接入会话包括至少两个非3GPP传输路径；所述移动管理设备向会话管理设备发送第二请求消息，所述第二请求消息包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径；所述移动管理设备接收来自所述会话管理设备发送的第二分流规则；所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径；所述移动管理设备将所述第二分流规则发送给终端设备。
在该实施例中，所述第二目标传输路径可以是多个非3GPP传输路径中的一个或者多个。此外，当非3GPP传输路径都不可用时，本申请实施例中所述第二目标传输路径也可以是不包括非3GPP传输路径。
其中，所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径，可以理解为所述用户面设备在执行非3GPP传输路径时，可以使用所述第二分流规则来确定传输路径。
在该实施例中，所述多接入会话管理流程可以是多接入会话建立流程，或多接入会话修改流程，或多接入会话添加流程，或多接入会话释放流程，或多接入会话激活流程等。
基于上述方案，在多路径会话切换流程中，当确定需要执行非3GPP传输路径切换时，使得终端设备和用户面设备在切换过程中触发支持存在多条非3GPP传输路径的分流规则，例如，触发的分流规则可以支持UE和/或UPF在多条非3GPP传输路径中选择合适的传输路径进行数据传输，有效的执行业务数据的分流，从而保障会话切换时的业务连续性。
在一种可能的实现方式中，所述第二请求消息还包括所述多接入会话标识，所述多接入会话标识用于确定所述终端设备的所述多接入会话。
在一种可能的实现方式中，所述第二请求消息还包括所述多接入会话的上下文标识，所述多接入会话的上下文标识用于确定所述终端设备的所述多接入会话。
在一种可能的实现方式中，所述第二分流规则，包括：所述终端设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息；所述接入优先级指示信息，用于指示所述第二目标传输路径。
在一种可能的实现方式中，所述第二目标传输路径为可信非3GPP传输路径或非可信 非3GPP传输路径。
在一种可能的实现方式中，所述第二分流规则，包括：
第四分流规则，所述第四分流规则指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输。
在一种可能的实现方式中，所述第二分流规则，包括：
所述终端设备在非3GPP路径切换之前使用的分流规则、第四分流规则以及规则应用条件，所述第四分流规则用于指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
在一种可能的实现方式中，所述移动管理设备根据接收到的终端设备发送的用于请求路径切换的非接入层消息，确定执行非3GPP传输路径切换，所述非接入层消息中包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径。
在一种可能的实现方式中，所述方法还包括：
所述移动管理设备在执行非3GPP路径切换过程中，确定满足信令连接释放的第一条件；所述移动管理设备释放所述终端设备在目标非3GPP传输路径或源非3GPP传输路径的信令连接。
在该实施例中，所述信令连接释放可以为接入网信令释放，或者，也可以为终端设备去注册等，在此并不进行限定。
基于上述方法，移动管理设备通过判断终端设备注册时是否用于后续会话切换，决定是否释放终端设备在目标路径或源路径的信令连接，有效避免了终端设备长时间保持可信非3GPP和非可信非3GPP路径上的双注册状态，同时，也可以支持非3GPP路径上进行MA PDU会话切换。
在一种可能的实现方式中，所述信令连接释放的第一条件，包括：
所述移动管理设备在所述终端设备完成所述目标非3GPP传输路径注册后开启的第一定时器到期，所述第一定时器用于指示触发源非3GPP传输路径信令连接释放；或者，所述移动管理设备在所述终端设备完成所述目标非3GPP传输路径注册后开启的第二定时器到期，以及所述终端设备没有完成在所述目标非3GPP传输路径的切换，所述第二定时器用于指示触发目标非3GPP传输路径信令连接释放。
在一种可能的实现方式中，所述方法还包括：
所述移动管理设备确定所述终端设备完成非3GPP传输路径切换后，向所述会话管理设备发送第三请求消息，所述第三请求消息用于指示应用所述终端设备和/或用户面设备在非3GPP传输路径切换之前使用的分流规则。
第五方面，提供一种通信方法。该方法可以由移动管理设备执行，或者类似移动管理设备功能的芯片执行。该方法中，移动管理设备在执行非3GPP路径切换过程中，确定满足信令连接释放的第一条件；所述移动管理设备释放终端设备在目标非3GPP传输路径或源非3GPP传输路径的信令连接。
在该实施例中，所述信令连接释放可以为接入网信令释放，或者，也可以为终端设备去注册等，在此并不进行限定。
基于上述方法，移动管理设备通过判断终端设备注册时是否用于后续会话切换，决定 是否释放终端设备在目标路径或源路径的信令连接，有效避免了终端设备长时间保持可信非3GPP和非可信非3GPP路径上的双注册状态，同时也可以支持非3GPP路径上进行MA PDU会话切换。
在一种可能的实现方式中，所述信令连接释放的第一条件，包括：
所述移动管理设备在所述终端设备完成所述目标非3GPP传输路径注册后开启的第一定时器到期，所述第一定时器用于指示触发源非3GPP传输路径信令连接释放；或者，所述移动管理设备在所述终端设备完成所述目标非3GPP传输路径注册后开启的第二定时器到期，以及所述终端设备没有完成在所述目标非3GPP传输路径的切换，所述第二定时器用于指示触发目标非3GPP传输路径信令连接释放。
第六方面，本申请实施例提供一种通信装置，该装置可以是会话管理设备，还可以是用于会话管理设备的芯片。该装置具有实现上述第一方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面，本申请实施例提供一种通信装置，该装置可以是终端设备，还可以是用于终端设备的芯片或模块。所述终端设备例如可以是智能移动终端、智能家居设备、智能汽车、智能穿戴设备等等。
其中，智能移动终端比如手机、平板电脑、笔记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本、个人数字助理(personal digital assistant，PDA)等。智能家居设备比如智能冰箱、智能洗衣机、智能电视机、音箱等。智能汽车穿戴设备比如智能耳机、智能眼镜、智能服饰或鞋子等。该装置具有实现上述第二方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，本申请实施例提供一种通信装置，该装置可以是UPF，还可以是用于UPF的芯片或模块。该装置具有实现上述第三方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第九方面，本申请实施例提供一种通信装置，该装置可以是移动管理设备，还可以是用于移动管理设备的芯片或模块。该装置具有实现上述第四方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十方面，本申请实施例提供一种通信装置，该装置可以是移动管理设备，还可以是用于移动管理设备的芯片或模块。该装置具有实现上述第五方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十一方面，本申请实施例提供一种通信装置，包括处理器和存储器；该存储器用于存储计算机指令，当该装置运行时，该处理器执行该存储器存储的计算机指令，以使该装置执行上述第一方面至第五方面中的任意实现方法。
第十二方面，本申请实施例提供一种通信装置，包括用于执行上述第一方面至第五方面中的任意实现方法的各个步骤的单元或手段(means)。
第十三方面，本申请实施例提供一种通信装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行上述第一方面至第五方面中的任意实现方法。该处理器包括一个或多个。
第十四方面，本申请实施例提供一种通信装置，包括与存储器耦合的处理器，该处理器用于调用所述存储器中存储的程序，以执行上述第一方面至第五方面中的任意实现方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器可以是一个或多个。
第十五方面，本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在通信装置上运行时，使得上述第一方面至第五方面中的任意实现方法被执行。
第十六方面，本申请实施例还提供一种计算机程序产品，该计算机程序产品包括计算机程序或指令，当计算机程序或指令被通信装置运行时，使得上述第一方面至第五方面中的任意实现方法被执行。
第十七方面，本申请实施例还提供一种芯片系统，包括：处理器，用于执行上述第一方面至第五方面中的任意实现方法。
第十八方面，本申请实施例还提供一种通信系统，包括：上述第六方面的通信装置至上述第九方面的通信装置。可选的，还包括第十方面的通信装置。
上述第六方面至第十八方面中各个方面中的各种设计方案可以达到的技术效果，请参照上述第一方面至第五方面中相应方案的技术效果描述，这里不再重复赘述。
附图说明
图1为现有提供的一种多接入会话系统示意图；
图2为本申请实施例提供的第一种多接入会话场景示意图；
图3为本申请实施例提供的第二种多接入会话场景示意图；
图4为本申请实施例提供的第三种多接入会话场景示意图；
图5为本申请实施例提供的第四种多接入会话场景示意图；
图6为本申请实施例提供的一种通信路径切换系统示意图；
图7为本申请实施例提供的一种通信路径切换方法流程示意图；
图8为本申请实施例提供的第一种路径切换情况的流程示意图；
图9为本申请实施例提供的第二种路径切换情况的流程示意图；
图10为本申请实施例提供的第三种路径切换情况的流程示意图；
图11为本申请实施例提供的第一种通信路径切换装置的示意图；
图12为本申请实施例提供的第二种通信路径切换装置的示意图。
具体实施方式
为了便于理解本申请实施例提供的技术方案，以下对本申请涉及的技术术语进行解释和说明。
1)非3GPP接入类型，非3GPP接入类型包括非可信非3GPP接入技术(untrusted non-3GPP access)如通过个人购买的无线接入节点接入核心网、可信非3GPP接入技术(trusted non-3GPP access)如通过运营商部署的无线接入节点接入核心网、有线接入技术 (wireline access)。
非3GPP接入技术可以包括无线通信技术(WiFi)、蓝牙或紫峰(ZigBee)等技术。非3GPP接入网设备可以包括非3GPP互通功能(non-3GPP interworking function，N3IWF)、可信非3GPP网关功能(trusted non-3GPP gateway function，TNGF)、可信非3GPP接入点(trusted non-3GPP access point，TNAP)、可信无线局域网互通功能(trusted wireless local area network interworking function，TWIF)、有线接入网关功能(wireline access gateway function，W-AGF)。其中，W-AGF也可以称为AGF。若接入技术为非可信非3GPP接入技术，则其对应的非3GPP接入网设备可以包括N3IWF，其网络拓扑结构相当于3GPP接入网中的无线接入网(radio access network，RAN)，可以支持N2、N3接口。若接入技术为可信非3GPP接入技术，则其对应的非3GPP接入网设备可以包括TNGF，其网络拓扑结构相当于3GPP接入网中的RAN，可以支持N2、N3接口。
作为一种示例，非可信非3GPP接入点可以是非运营商部署的接入节点，例如家里或者商家部署的WiFi接入点(access point，AP)。可信非3GPP接入点可以是运营商部署的接入节点，可以称为可信非3GPP接入节点(trusted N3GPP Access Point，TNAP)。
2)多接入会话(multi-access PDU Session，MA PDU Session)，用于指UE和/或UPF通过3GPP接入网络(也可以理解为3GPP接入路径)以及非3GPP接入网络(也可以理解为非3GPP接入路径)进行传输，以提升传输效率。
例如，用户面通道可以包括两个接入网设备(3GPP接入网设备和非3GPP接入网设备)，该两个接入网设备连接同个UPF(或者通过另一UPF连接同个UPF)。例如，UE可以通过RAN和/或N3IWF向UPF发送上行数据；UPF通过RAN和/或N3IWF向UE发送下行数据。
3)分流规则，用于指示如何将待发送数据通过3GPP接入网的路径和/或通过非3GPP接入网的路径发送。
目前，在通信传输过程中，经常通过建立多接入会话(multi-access PDU Session，MA PDU Session)将需要发送的业务流数据，同时通过3GPP接入网络(路径)以及非3GPP接入网络(路径)进行传输，以提升传输效率。例如，如图1所示，用户面通道可以包括两个接入网设备(3GPP接入网设备和非3GPP接入网设备)，该两个接入网设备连接同个UPF(或者通过另一UPF连接同个UPF)，其中，UE可以通过无线接入网(RAN Radio Access Network，RAN)和/或非3GPP互通功能(non-3GPP interworking function，N3IWF)向UPF发送上行数据；UPF通过RAN和/或N3IWF向UE发送下行数据。
然而，现有多接入会话技术仅支持通过一个3GPP接入网络(路径)以及一个非3GPP接入网络(路径)进行传输，并不支持通过两个以上的路径传输，即当多接入会话场景多于2条路径传输的情况时，UE和UPF无法有效的执行业务数据的分流，可能会导致业务中断，从而影响用户体验。
例如，现有多接入会话技术并不支持如图2所示的通过至少两个非3GPP路径传输进行多接入会话的形式，所述至少两个非3GPP路径包括可信非3GPP路径和非可信非3GPP路径；再例如，现有多接入会话技术并不支持如图3所示的通过至少两个3GPP路径传输进行多接入会话的形式；再例如，现有多接入会话技术并不支持如图4所示的通过一个 3GPP路径以及至少两个非3GPP路径传输进行多接入会话的形式；再例如，现有多接入会话技术并不支持如图5所示的通过至少两个3GPP路径以及一个非3GPP路径传输进行多接入会话的形式。
并且，若当前场景为通过至少两个非3GPP路径传输进行多接入会话时，实现N3GPP路径切换会使得多个N3GPP路径同时存在，从而导致没有办法支持在切换的过程中实现业务流数据分流。此外，由于网络本身的要求，可能在切换完成后最终只允许保留其中一条路径，而现有UE在目标路径注册完成后，经常无法按时完成切换流程，或者完成切换流程后没有主动触发原路径的去注册，从而导致UE长时间的在网络维持双注册状态，影响UE通过该网络获取服务。
因此，如何使能在多接入会话中N3GPP路径切换的过程中，支持业务流数据的分流，保障通信的连续性，降低系统开销，有待解决。
基于此，本申请实施例为了能够实现多接入会话中N3GPP路径切换，更好的保证通信的连续性，本申请实施例提供了非3GPP路径切换的方法。
需要说明的是，本申请实施例所述多接入会话管理流程可以是多接入会话建立流程，或多接入会话修改流程，或多接入会话添加流程，或多接入会话释放流程，或多接入会话激活流程等，在此并不进行限定。
下面，参阅图6所示，为本申请实施例提供一种多接入会话中非3GPP路径切换的简化架构示意图。该通信系统可以包括终端设备600、接入与移动性管理功能网元(access and mobility management function，AMF)610、会话管理功能网元(session management function，SMF)620以及用户面功能网元(user plane function，UPF)630。
所述终端设备600，也可以称为用户设备(user equipment，UE)、移动台、移动终端等。图6中用UE代表终端。终端可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、无人机、直升机、飞机、轮船、机器人、机械臂、智能家居设备等。本申请的实施例对终端所采用的具体技术和具体设备形态不做限定。
具体地，本申请实施例中所述终端设备可以用于：
确定在多接入会话中执行非3GPP传输路径切换，向会话管理设备发送第一会话请求消息，接收来自所述会话管理设备发送的第二分流规则，以及根据所述第二分流规则确定传输路径。
所述AMF610，用于执行移动性管理、接入鉴权/授权等功能。此外，接入与移动性管理功能网元还负责向终端传递用户策略。
具体地，本申请实施例中所述AMF可以用于：
确定在多接入会话中执行非3GPP传输路径切换，向会话管理设备发送第二请求消息，接收来自所述会话管理设备发送的第二分流规则，以及将所述第二分流规则发送给终端设备。
所述SMF620，用于执行会话管理、控制策略的执行、用户面功能网元的选择、终端的互联网协议(internet protocol，IP)地址分配等功能。
具体地，本申请实施例中所述SMF可以用于：
确定在多接入会话中执行非3GPP传输路径切换，向用户面设备发送第一分流规则和/或向终端设备发送第二分流规则。
所述UPF630，用于完成执行用户面数据转发、基于会话/流级的计费统计，带宽限制等功能。
具体地，本申请实施例中所述UPF可以用于：
在多接入会话中执行非3GPP传输路径切换时，接收来自会话管理设备发送的第一分流规则，以及根据所述第一分流规则确定传输路径。
上述介绍的所述多接入会话包括至少两个非3GPP传输路径。所述第一会话请求消息包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径。
以及，所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径。所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径。
进一步的，本申请实施例中所述第一目标传输路径可以是多个非3GPP传输路径中的一个或者多个。所述第二目标传输路径可以是多个非3GPP传输路径中的一个或者多个。
此外，当非3GPP传输路径都不可用时，本申请实施例中所述第一目标传输路径也可以是不包括非3GPP传输路径。同理，当非3GPP传输路径都不可用时，本申请实施例中所述第二目标传输路径也可以是不包括非3GPP传输路径。
其中，本申请实施例中所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径，可以理解为所述用户面设备在执行非3GPP传输路径时，可以使用所述第一分流规则来确定传输路径。同理，所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径，可以理解为所述用户面设备在执行非3GPP传输路径时，可以使用所述第二分流规则来确定传输路径。
可选的，该通信系统中还可以包括其他网元或网络等，例如，还可以包括统一数据管理(unified data management，UDM)网元、策略控制功能(policy control function，PCF)网元，位于运营商网络之外的网络DN等，在此并不进行限定。
下面，本申请实施例提供一种通信路径切换方法。参阅图7所示，为本申请实施例提供的一种通信方法的示例性流程图，可以包括以下操作。其中，所述图7所示的实施例可以应用于存在至少两个非3GPP路径的多会话接入场景下的通信系统，如图6所示的通信系统中。
S701：SMF确定在多接入会话中执行非3GPP传输路径切换，所述多接入会话包括至少两个非3GPP传输路径。
其中，本申请实施例中，SMF可以通过多种方式确定是否执行非3GPP路径切换。
确定方式1：所述SMF接收来自所述UE的第一会话请求消息，根据所述第一会话请求消息确定执行所述非3GPP路径切换。
其中，所述第一会话请求消息可以是会话建立请求消息，或者，可以是会话修改请求消息，在此并不进行限定。
示例性的，当所述第一会话请求消息包括第一切换指示信息时，所述SMF根据所述第一切换指示信息确定执行所述非3GPP路径切换，所述第一切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径。
其中，当所述第一切换指示消息指示建立的目标传输路径为非3GPP传输路径时，所述SMF在确定所述多接入会话已建立的源传输路径为非3GPP传输路径时，根据所述会话请求确定执行所述非3GPP传输路径切换。
进一步的，本申请实施例中所述第一会话请求消息还可以包括所述多接入会话的会话标识，所述会话标识用于确定所述终端设备的所述多接入会话。
确定方式2：所述SMF接收来自AMF的第二会话请求消息，根据所述第二会话请求消息确定执行所述非3GPP路径切换。
其中，所述第二会话请求消息可以是会话创建会话上下文消息，或者，可以是会话更新会话上下文消息，在此并不进行限定。
示例性的，当所述第二会话请求消息包括第二切换指示信息时，所述SMF根据所述第二切换指示信息确定执行所述非3GPP路径切换，所述第二切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径。
其中，当所述第二切换指示消息指示建立的目标传输路径为非3GPP传输路径时，所述SMF在确定所述多接入会话已建立的源传输路径为非3GPP传输路径时，根据所述会话请求确定执行所述非3GPP传输路径切换。
进一步的，本申请实施例中所述第二会话请求消息还可以包括所述多接入会话的会话标识和/或会话上下文标识，所述会话标识用于确定所述终端设备的所述多接入会话。
其中，所述第二会话请求消息可以是所述AMF确定在多接入会话中执行非3GPP传输路径切换后发送的。
例如，所述AMF接收到终端设备发送的用于请求路径切换的非接入层(non-access stratum，NAS)消息，确定在多接入会话中执行非3GPP传输路径切换后，触发向所述SMF发送所述第二会话请求消息。其中，所述NAS消息中包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径。
S702：SMF向UPF发送第一分流规则和/或向UE发送第二分流规则。
其中，所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径；所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径。
作为一种示例，当所述SMF向UE发送所述第二分流规则时，可以通过AMF将所述第二分流规则发送给对应的UE。
作为一种示例，所述SMF向对应的UPF发送所述第一分流规则，可以通过向所述UPF发送携带所述第一分流规则的N4会话修改请求实现。
进一步的，本申请实施例所述的用于执行传输路径切换的第一分流规则和/或第二分流规则的内容可以有多种，具体并不限于下述几种：
内容形式1：第一分流规则和/或第二分流规则包括在非3GPP路径切换之前使用的分流规则(原有传输路径切换分流规则)以及用于指示进行非3GPP路径切换的接入优先级指示信息。
其中，所述接入优先级指示信息，用于指示目标传输路径。本申请实施例中所述目标传输路径可以是多个非3GPP传输路径中的一个或者多个，此外，如果非3GPP传输路径都不可用，也可以不包括非3GPP传输路径。
示例性的，所述第一分流规则包括所述用户面设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息。
所述第而分流规则包括所述终端设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息。
内容形式2：第一分流规则和/或第二分流规则包括支持非3GPP路径切换的分流规则。其中，所述非3GPP路径切换的分流规则不同于所述原有路径切换分流规则。
示例性的，所述第一分流规则包括第三分流规则，所述第三分流规则用于指示所述用户面设备通过所述至少两个非3GPP传输路径进行冗余传输。
所述第二分流规则包括第四分流规则，所述第四分流规则指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输。
内容形式3：第一分流规则和/或第二分流规则包括支持非3GPP路径切换的分流规则，原有路径切换分流规则以及分流规则对应的触发条件。
示例性的，所述第一分流规则，包括所述用户面设备在非3GPP路径切换之前使用的分流规则、第三分流规则以及规则应用条件，所述第三分流规则用于指示所述用户面设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
所述第二分流规则，包括所述终端设备在非3GPP路径切换之前使用的分流规则、第四分流规则以及规则应用条件，所述第四分流规则用于指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
其中，基于上述内容形式1～3，列举几种第一分流规则以及第二分流规则可能指示的实际内容如下：
所述第一分流规则和/或所述第二分流规则用于指示UPF将通过源非3GPP传输路径传输的业务流切换至目标非3GPP传输路径进行传输。
其中，当所述源非3GPP传输路径为非可信非3GPP传输路径时，所述目标非3GPP传输路径可以为可信非3GPP传输路径。当所述源非3GPP传输路径为可信非3GPP传输路径时，所述目标非3GPP传输路径可以为非可信非3GPP传输路径。
此外，当所述多接入会话还包括3GPP传输路径时，所述第一分流规则还可以指示UPF将通过源非3GPP传输路径传输的业务流切换至目标3GPP传输路径进行传输。所述第二分流规则还可以指示UE将通过源非3GPP传输路径传输的业务流切换至目标3GPP传输路径进行传输。
其中，所述第一分流规则和/或所述第二分流规则是所述SMF向UPF发送第一分流规则和/或向UE发送第二分流规则之前，根据本地配置确定的；或者，所述第一分流规则和 /或所述第二分流规则是所述SMF向UPF发送第一分流规则和/或向UE发送第二分流规则之前，根据从PCF获取的策略和计费控制(policy and charging control，PCC)规则确定的。
此外，为了更好的符合网络本身的要求，及时完成切换流程，避免导致UE长时间的在网络维持双注册状态，影响UE通过该网络获取服务，本申请实施例还可以在完成非3GPP路径切换后，触发原非3GPP传输路径的信令连接的释放。
其中，本申请实施例中所述的信令连接的释放可以是接入网信令释放，或者，还可以是终端设备去注册。
作为一种示例，AMF在执行非3GPP路径切换过程中，确定满足信令连接释放的第一条件。
例如，所述AMF确定UE完成可信非3GPP路径切换到非可信非3GPP路径后，触发所述可信非3GPP路径释放。
再例如，所述AMF确定UE完成非可信非3GPP路径切换到可信非3GPP路径后，触发所述非可信非3GPP路径释放。
具体地，本申请实施例所述第一条件具体并不限于下述几种情况：
情况1：AMF在所述终端设备完成所述目标非3GPP传输路径注册后开启的第一定时器到期，所述第一定时器用于指示触发源非3GPP传输路径信令连接释放。
示例性的，所述AMF确定在进行非3GPP路径切换时，UE完成所述第一目标传输路径注册后，开启源路径去注册定时器，所述AMF确定所述源路径去注册定时器到期后，所述AMF向所述UE发起去注册请求。
情况2：AMF在所述终端设备完成所述目标非3GPP传输路径注册后开启的第二定时器到期，以及所述终端设备没有完成在所述目标非3GPP传输路径的切换，所述第二定时器用于指示触发目标非3GPP传输路径信令连接释放。
示例性的，所述AMF确定在进行非3GPP路径切换时，UE完成所述第一目标传输路径注册后，开启目标路径去注册定时器，所述AMF确定所述目标路径去注册定时器到期，且后，所述AMF向所述UE发起去注册请求。
情况3：所述AMF接收到来自所述UE的信令连接释放的请求消息后，所述AMF向所述UE发起去注册请求，所述信令连接释放的请求消息用于指示所述AMF向所述UE发起目标路径或者源路径的去注册请求。
其中，为了更好的对本申请提供的通信路径切换方法进行介绍，基于上述图7所示的内容，结合下述两种路径切换场景，进一步详细介绍。
其中，下文所涉及的路径切换方式中的部分步骤可以是可选的，步骤顺序也不代表实际的执行顺序，因此本申请不限定完全按照下文的步骤和顺序执行，此外，下述两种路径切换场景彼此之间可以结合应用，在此并不进行限定。
场景一、基于本申请提供的第一分流规则和/或第二分流规则进行路径切换。
参阅图8所示，该场景一对应的方法可以执行下述步骤，其中，假设在流程开始前，UE已经通过可信非3GPP网关功能(trusted非3GPP gateway function，TNGF)建立MA PDU会话，且已经通过非3GPP互通功能(非3GPP interworking function，N3IWF)完成注册并建立UE和N3IWF的因特网协议安全协议(internet protocol security，IPSec)安全信令面的连接。
S801：在非可信非3GPP路径上，UE向AMF发送NAS消息，其中，所述NAS消息携带第一会话请求消息。
其中，所述第一会话请求消息可以是会话建立请求消息，或者，还可以是会话修改请求消息。
作为一种示例，所述NAS消息中携带会话标识，和/或第一切换指示信息，所述会话标识用于唯一确定所述会话。
其中，所述第一切换指示信息可以是会话请求类型(Request Type)，其中，请求类型可以指示已有PDU会话(Existing PDU Session)，或者多接入会话请求(MA PDU Request)，或者是新的指示标识。
例如，所述第一切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径。
进一步的，本申请实施例所述会话标识，和/或所述第一切换指示信息可以在所述第一会话请求消息中携带，或者，所述会话标识可以在所述NAS消息除所述第一会话请求消息之外携带。
其中，若所述第一切换指示信息在所述第一会话建立请求之内，则AMF不感知所述第一切换指示信息，SMF直接感知所述第一切换指示信息。若所述第一切换指示信息在所述第一会话建立请求之外，NAS消息之内，则AMF直接感知该指示，AMF可以在后续步骤S803中指示SMF所述第一切换指示信息。
S802：AMF基于接收到的所述NAS消息选择合适的SMF。
具体地，所述AMF可以基于接收到的所述NAS消息中的会话标识选择合适的SMF。
S803：AMF向SMF发送第二会话请求消息。
作为一种示例，所述AMF可以基于接收到的来自所述终端设备的NAS消息，确定执行非3GPP路径切换后，向所述SMF发送所述第二会话请求消息。其中，所述第二会话请求消息可以是会话创建会话上下文消息，或者是会话更新会话上下文消息。
例如，所述AMF识别所述NAS消息中携带的所述第一切换指示信息，根据所述第一切换指示信息确定当前会话管理流程用于执行非3GPP传输路径切换后，向所述SMF发送所述第二会话请求消息。
作为一种示例，所述第二会话请求消息中可以携带所述会话的标识、所述会话的上下文标识、第二切换指示信息或无线接入技术类型(RAT Type)中的一个或多个。
其中，所述第二切换指示信息用于指示当前会话请求的接入路径类型。
例如，所述第二切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径。
其中，所述AMF可以直接将接收到的所述NAS消息中的第一切换指示信息作为所述第二会话请求消息中的第二切换指示信息，发送给所述SMF。
可以理解的，在这种情况下，所述第一切换指示信息与所述第二切换指示信息相同。同理，在AMF向SMF发送的第二会话请求消息中也同样可以携带所述NAS消息中指示的所述会话标识，和/或所述会话上下文标识等，在此不进行限定。
S804：SMF基于所述第二会话请求消息向统一数据管理(unified data management，UDM)设备获取UE的签约信息，所述签约信息包括所述UE的会话上下文信息。
具体地，所述SMF可以基于所述第二会话请求消息中的会话标识或者所述会话上下 文标识向UDM获取UE的签约信息。
S805：SMF向AMF反馈上述更新会话上下文响应消息。
S806：SMF确定在多接入会话中执行非3GPP传输路径切换。
作为一种示例，所述SMF可以基于接收到的来自所述AMF的所述第二会话请求消息，确定执行非3GPP传输路径切换。
例如，所述SMF根据所述第二会话请求消息中包括的第二切换指示信息，确定执行非3GPP传输路径切换，此时，所述第二切换指示信息指示执行非3GPP传输路径切换。
再例如，当所述第二切换指示信息指示建立的目标传输路径为非3GPP传输路径时，所述SMF在确定所述多接入会话已建立的源传输路径为非3GPP传输路径时，根据所述会话请求确定执行所述非3GPP路径切换。
S807：SMF确定用于UPF的第一分流规则和/或用于UE的第二分流规则。
作为一种示例，所述SMF可以根据本地配置确定所述第一分流规则和/或所述第二分流规则；或者，所述SMF可以根据从PCF获取的PCC规则，确定所述第一分流规则和/或所述第二分流规则。
其中，所述第一分流规则包含于多接入规则(Multiple Access Rule),用于支持UPF在多个传输路径中确定第一目标传输路径,所述多接入会话包括至少两个非3GPP传输路径。
其中，所述第二分流规则包含于存取业务的分流/切换/分离规则(Access Traffic Steering Switching Splitting rule，ATSSS rule),用于支持UE在多个传输路径中确定第二目标传输路径。
为简洁描述，所述第一分流规则和/或所述第二分流规则的内容可以参见上述图7所示的相关内容介绍，在此不进行赘述。
S808：SMF基于本地的所述多接入会话上下文，选择所述多接入会话对应的UPF发起N4会话修改请求，其中，所述N4会话修改请求中包括所述第一分流规则。
作为一种示例，所述第一分流规则可以在所述N4会话修改请求包括的N4规则中携带。
例如，本申请实施例所述N4规则可以包括数据包检测规则(Packet Detection Rule，PDR)、转发动作规则(Forwarding Action Rule，FAR)、多接入规则(Multi Access Rule，MAR)等规则。其中，MAR规则中包括所述第一分流规则。
S809：UPF基于收到的所述第一分流规则执行业务数据流的分流。
S810：SMF向AMF发送N1N2传输消息，所述N1N2传输消息中包括所述第二分流规则。
作为一种示例，所述N1N2传输消息中，包含了会话标识、N2接口会话管理信息(N2SM information)以及N1接口会话管理容器(N1SM Container)等信息。
其中，N1SM Container中包含了PDU会话建立接受消息(PDU Session Establishment Accept)以及ATSSS rule等与会话相关的参数信息。所述ATSSS rule为上述所述第一分流规则。
S811：AMF向N3IWF发起会话请求消息，会话请求消息中携带所述第二分流规则。
S812：N3IWF基于自身策略和配置决定建立多少因特网协议安全协议(internet protocol security，IPSec)Child SA以及每个IPSec Child SA传输哪些服务质量(quality of service，QoS)流(Flow)数据。
S813：N3IWF与UE建立用于传输用户面数据的IPSec安全关联(Security Association， SA)。
在此过程中，N3IWF会为UE分配该IPSec Child SA的IP地址(UP_IP_ADDRESS)，即若UE要发送上行数据时，在内部(inner)IP协议栈中，目的IP地址应设为该UP_IP_ADDRESS，而源IP地址则为注册时候分配“inner”IP地址(address)。
S814：IPsec用户面连接完成后，N3IWF向UE发起会话建立接受消息，其中携带所述第二分流规则。
S815：N3IWF向AMF发起N2会话响应消息，指示N3IWF接入网侧的用户面资源已建立完成，并携带N3IWF侧的隧道端点标识。
S816：AMF向SMF发起会话更新请求，转发来自接入网侧会话相关的信息。
S817：SMF通过N4会话修改流程向UPF发送N3IWF侧的接入网(access network，AN)隧道端点标识信息。
S818：SMF向AMF发送协议数据单元(protocol data unit，PDU)会话更新上下文响应消息。
S819：当非可信非3GPP路径的N3隧道建立完成后，AMF触发原可信非3GPP路径N2资源的释放，向TNGF发起N2会话资源释放请求。
S820：TNGF发起和UE的信息交换，删除UE和TNGF在可信非3GPP上的会话上下文。
S821：TNGF向AMF发送N2资源释放响应。
S822：AMF向SMF发起会话更新请求，指示可信非3GPP路径会话资源已释放。
作为一种示例，若所述第一分流规则中包含UPF在非3GPP路径切换之前使用的分流规则，和/或所述第二分流规则中包含终端设备在非3GPP路径切换之前使用的分流规则，则本发明方案后续流程不再进行。
作为一种示例，若所述第一分流规则中未包含UPF在非3GPP路径切换之前使用的分流规则，和/或所述第二分流规则中未包含终端设备在非3GPP路径切换之前使用的分流规则，则执行后续步骤S823～S829。
S823：SMF在切换完成后发起N4会话修改请求，其中携带原MA PDU会话的MAR分流规则。
其中，所述原MA PDU会话的MAR分流规则指在非3GPP路径切换之前使用的分流规则。
S824：UPF在收到N4会话修改请求后，接受并执行上述MAR分流规则。
其中，在执行完所述S824以后，UE的下行数据便通过上述MAR分流规则进行分流。
S825：SMF向AMF发起N1N2传输消息，其中，所述N1N2传输消息中携带用于原MA PDU会话的ATSSS分流规则。
S826：AMF向N3IWF发起会话请求，其中，所述会话请求中携带原MA PDU会话的ATSSS分流规则。
S827：N3IWF向UE发起PDU会话修改指令，其中，所述PDU会话修改指令中携带原MA PDU会话的ATSSS分流规则。
S828：UE收到PDU会话修改指令后，接受并执行上述ATSSS分流规则，完成后UE向N3IWF发送PDU会话修改指令响应。
其中，在执行完所述S828以后，UE的上行数据便通过上述MAR分流规则进行分流。
S829：N3IWF将收到来自UE的响应消息转发给AMF。
其中，在该场景一中，主要是解决切换时保障会话连续性的问题，通过上述图3所示的流程图可以看出，整体的切换流程可以分为4个阶段，分别是UE通过目标路径注册，在目标路径建立/添加MA PDU会话，源路径会话资源的释放，UE在源路径去注册。
需要说明是，该实施例以MA PDU其中的非3GPP路径从可信非3GPP接入路径切换到非可信非3GPP接入路径为例，反之也可以适用，为简洁描述，MA PDU中的非3GPP路径从非可信非3GPP接入路径切换到可信非3GPP接入路径的过程可以参见上述图8所示的内容进行变形得到，只需将N3IWF替换成TNGF，在此不进行赘述。
通过上述实施例，MA PDU会话切换流程，使得UE和UPF在切换过程中触发新的分流规则，其中，新的分流规则可以支持UE和/或UPF在多条非3GPP接入路径中选择合适的路径进行数据传输，从而保障会话切换时的业务连续性。
场景二、基于本申请提供的去注册原则进行路径切换。
其中，本申请实施例在该场景二下，基于去注册原则进行路径切换的情况有多种，具体并不限于下述几种：
去注册情况1：基于源路径去注册定时器到时后，触发源路径去注册。
参阅图9所示，该去注册情况1可以执行下述步骤。其中，下述图9是以非可信3GPP接入技术下的注册流程为例。
S901：UE连接至非可信非3GPP接入网，并被分配了一个IP地址，UE选择N3IWF，并获取该N3IWF的地址信息。
S902：UE通过发起因特网密钥交换协议(Internet Key Exchange，IKE)初始交换与N3IWF建立IPsec安全协议(IPsec Security Association，IPSec SA)。
S903：UE向N3IWF发送IKE_AUTH请求消息。
作为一种示例，UE在注册请求消息中可以携带第一指示信息，所述第一指示信息可以用于指示执行非3GPP路径切换和/或指示建立第二非3GPP传输路径。
基于此，所述第一指示信息可以用于AMF判断当前的注册请求是否用于后续的会话切换。此外，若注册请求消息中未携带所述第一指示信息，AMF也可以在收到注册请求消息时基于本地配置信息判断当前注册请求是否用于后续的会话切换。
S904：N3IWF向UE发送IKE_AUTH响应消息。
其中，该响应消息中包括EAP-Request/5G-Start数据包，所述EAP-Request/5G-Start数据包可以用于通知UE发起EAP-5G会话，例如通知UE开始发送NAS消息(通过将NAS消息封装在EAP-5G数据包中)。
S905：UE向N3IWF发送IKE_AUTH请求消息。
其中，所述请求消息中可以包括EAP-Response/5G-NAS数据包，所述数据包中可以包括AN参数和注册请求消息。所述AN参数可以包括N3IWF用于选择AMF的参数信息，例如GUAMI、选择的公共陆地通信网(public land mobile network，PLMN)ID(或者PLMN ID和网络标识(network identifier，NID)的组合)等。
S906：N3IWF执行AMF选择，并将注册请求消息发给AMF。
作为一种示例，当所述UE向N3IWF发送的请求消息中包括所述第一指示信息时，所述N3IWF也可以将注册请求消息中的所述第一指示信息转发给AMF。
S907：AMF向N3IWF发送NGAP初始连接建立请求(NGAP initial context setup request)消息，当中包括N3IWF密钥。
作为一种示例，所述S907是在所述AMF与UE之间鉴权成功后执行的。
例如，所述AMF选择鉴权服务器功能(authentication server function，AUSF)，并向AUSF发送鉴权请求消息，然后，AUSF对UE执行鉴权流程，并从UDM获取鉴权数据。
其中，与鉴权相关的数据包可以通过NAS消息封装，而该NAS消息可以通过EAP/5G-NAS数据包封装。
在鉴权完成后，AUSF向AMF发送安全锚点功能(seaf)密钥，AMF用该密钥推衍获取NAS安全密钥和N3IWF的安全密钥，其中，该N3IWF密钥是UE和N3IWF用于建立IPSec SA的。
然后，AMF向UE发送NAS安全模式命令(NAS security mode command)，以激活NAS安全，在成功激活NAS安全后执行所述S907。
S908：N3IWF向UE发送身份验证协议(extensible authentication protocol，EAP)成功(Success)的信息。
此时，EAP-5G会话完成，后续没有EAP-5G数据包交互。
S909：AMF向N3IWF发送N2消息，其中，所述N2消息包括向UE发送的NAS注册接受消息(NAS Registration Accept)。
S910：N3IWF通过刚刚建立的信号IPSec SA(signalling IPSec SA)向UE发送NAS注册接受消息。
S911：AMF选择开启源路径(可信非3GPP)的第一定时器。
作为一种示例，注册流程完成后，AMF会基于上述切换指示信息或者本地配置的UE注册信息判断当前注册请求适用于后续的会话切换，并选择开启源路径(可信非3GPP)的第一定时器，其中，所述第一定时器用于释放源路径的信令连接。
S912：UE在执行可信非3GPP和非可信非3GPP的切换流程时，当所述第一定时器到期后，触发AMF向UE执行源路径信令连接的释放。
例如，当所述第一定时器到期后，触发AMF执行源路径的接入网侧资源释放流程，或者，触发AMF执行源路径的UE去注册流程。
S913：UE在接收到去注册请求后，发送给AMF去注册接收消息。
S914：AMF向TNGF发起源路径(可信非3GPP)的N2UE上下文释放指令。
S915：TNGF和UE之间发起IKE INFORMATIONAL消息，释放UE和TNGF之间的IKEv2隧道以及在TNGF上删除UE上下文。
S916：TNGF向AMF反馈N2UE上下文以完成释放。
通过上述实施例，AMF通过判断UE注册时是否用于后续会话切换，决定在源路径开启去注册定时器，避免UE长时间保持可信非3GPP和非可信3GPP路径上的双注册状态，同时也可以支持非3GPP路径上进行MA PDU会话切换。
去注册情况2：基于目标路径去注册定时器到时后，触发目标路径去注册。
参阅图10所示，该去注册情况2可以执行下述步骤。其中，下述图5是以非可信3GPP接入技术下的注册流程为例。
S1001：UE连接至非可信非3GPP接入网，并被分配了一个IP地址，UE选择N3IWF，并获取该N3IWF的地址信息。
S1002：UE通过发起因特网密钥交换协议(Internet Key Exchange，IKE)初始交换与N3IWF建立IPsec Security Association(IPSec SA)。
S1003：UE向N3IWF发送IKE_AUTH请求消息。
作为一种示例，UE在注册请求消息中可以携带第一指示信息，所述第一指示信息可以用于指示执行非3GPP路径切换和/或指示建立第二非3GPP传输路径。
基于此，所述第一指示信息可以用于AMF判断当前的注册请求是否用于后续的会话切换。此外，若注册请求消息中未携带所述第一指示信息，AMF也可以在收到注册请求消息时基于本地配置信息判断当前注册请求是否用于后续的会话切换。
S1004：N3IWF向UE发送IKE_AUTH响应消息。
其中，该响应消息中包括EAP-Request/5G-Start数据包，所述EAP-Request/5G-Start数据包可以用于通知UE发起EAP-5G会话，例如通知UE开始发送NAS消息(通过将NAS消息封装在EAP-5G数据包中)。
S1005：UE向N3IWF发送IKE_AUTH请求消息。
其中，所述请求消息中可以包括EAP-Response/5G-NAS数据包，所述数据包中可以包括AN参数和注册请求消息。所述AN参数可以包括N3IWF用于选择AMF的参数信息，例如GUAMI、选择的PLMN ID(或者PLMN ID和NID)等。
S1006：N3IWF执行AMF选择，并将注册请求消息发给AMF。
作为一种示例，当所述UE向N3IWF发送的请求消息中包括所述第一指示信息时，所述N3IWF也可以将注册请求消息中的所述第一指示信息转发给AMF。
S1007：AMF向N3IWF发送NGAP Initial Context Setup Request消息，当中包括N3IWF密钥。
作为一种示例，所述S1007是在所述AMF与UE之间鉴权成功后执行的。
例如，所述AMF选择AUSF，并向AUSF发送鉴权请求消息，然后，AUSF对UE执行鉴权流程，并从UDM获取鉴权数据。其中，与鉴权相关的数据包可以通过NAS消息封装，而该NAS消息可以通过EAP/5G-NAS数据包封装。
在鉴权完成后，AUSF向AMF发送SEAF密钥，AMF用该密钥推衍获取NAS安全密钥和N3IWF的安全密钥，其中，该N3IWF密钥是UE和N3IWF用于建立IPSec SA的。
然后，AMF向UE发送NAS Security Mode Command，以激活NAS安全，在成功激活NAS安全后执行所述S1007。
S1008：N3IWF向UE发送EAP-Success。
此时，EAP-5G会话完成，后续没有EAP-5G数据包交互。
S1009：AMF向N3IWF发送N2消息，其中，所述N2消息包括向UE发送的NAS注册接受消息(NAS Registration Accept)。
S1010：N3IWF通过刚刚建立的signalling IPSec SA向UE发送NAS注册接受消息。
S1011：AMF选择开启目标路径(可信非3GPP)的第二定时器。
作为一种示例，注册流程完成后，AMF会基于上述切换指示信息或者本地配置的UE注册信息判断当前注册请求适用于后续的会话切换，并选择开启目标路径(可信非3GPP)的第二定时器，其中，所述第二定时器用于释放源路径的信令连接。
S1012：UE在执行可信非3GPP和非可信非3GPP的切换流程时，当所述第二定时器到期，且所述UE未完成所述目标路径的切换时，触发AMF向UE执行源路径信令连接的释放。
例如，当所述第二定时器到期后，触发AMF执行目标路径的接入网侧资源释放流程，或者，触发AMF执行目标路径的UE去注册流程。
S1013：UE在接收到去注册请求后，发送给AMF去注册接收消息。
S1014：AMF向TNGF发起目标路径(可信非3GPP)的N2UE上下文释放指令。
S1015：TNGF和UE之间发起IKE INFORMATIONAL消息，释放UE和TNGF之间的IKEv2隧道以及在TNGF上删除UE上下文。
S1016：TNGF向AMF反馈N2UE上下文以完成释放。
通过上述实施例，AMF通过判断UE注册时是否用于后续会话切换，决定在目标路径开启去注册定时器，避免UE长时间保持可信非3GPP和非可信3GPP路径上的双注册状态，同时也可以支持非3GPP路径上进行MA PDU会话切换。
进一步的，本申请实施例UE在执行可信非3GPP和非可信非3GPP的切换流程时，可以根据实际情况随时向对应的AMF发送信令连接释放的请求消息，从而使接收到所述信令连接释放的请求消息的AMF向所述UE执行目标路径或者源路径的信令连接释放。其中，所述信令连接释放的请求消息用于指示所述AMF向所述UE发起目标路径或者源路径的去注册请求。
基于与上述实施例相同的构思，本申请实施例提供一种通信装置。图11和图12为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中SMF、UE、UPF或AMF的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是SMF、UE、UPF或AMF，还可以是应用于SMF、UE、UPF或AMF的模块(如芯片)。
如图11所示，通信装置1100包括处理单元1110和收发单元1120。通信装置1100用于实现上述图6至图9中所示的方法实施例中SMF、UE、UPF或AMF的功能。
当通信装置1100用于实现SMF的功能时：处理单元1110，用于确定在多接入会话中执行非3GPP传输路径切换，所述多接入会话包括至少两个非3GPP传输路径。收发单元1120，用于向用户面设备发送第一分流规则和/或向终端设备发送第二分流规则；所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径；所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径。
在一种设计中，所述处理单元1110，具体用于：
根据接收到的会话请求消息，确定在多接入会话中执行非3GPP传输路径切换，所述会话请求消息包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径；
所述会话请求消息是所述终端设备在确定执行非3GPP传输路径后发送的第一会话请求消息；或者，所述会话请求消息是移动管理设备在确定执行非3GPP传输路径后发送的第二会话请求消息。
在一种设计中，所述处理单元1110，具体用于：
当所述切换指示信息指示建立的目标传输路径为非3GPP传输路径时，在确定所述多接入会话已建立的源传输路径为非3GPP传输路径时，根据所述会话请求确定执行所述非3GPP路径切换。
在一种设计中，所述会话请求消息还包括所述多接入会话的会话标识；所述会话标识用于确定所述终端设备的所述多接入会话。
在一种设计中，所述会话请求消息还包括所述多接入会话的会话上下文标识；所述会话上下文标识用于确定所述终端设备的所述多接入会话。
在一种设计中，所述第一分流规则，包括：
所述用户面设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息；所述接入优先级指示信息，用于指示所述第一目标传输路径；
在一种设计中，所述第二分流规则，包括：
所述终端设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息；所述接入优先级指示信息，用于指示所述第二目标传输路径。
在一种设计中，所述第一目标传输路径为可信非3GPP传输路径或非可信非3GPP传输路径；所述第二目标传输路径为可信非3GPP传输路径或非可信非3GPP传输路径。
在一种设计中，所述第一分流规则，包括：
第三分流规则，所述第三分流规则用于指示所述用户面设备通过所述至少两个非3GPP传输路径进行冗余传输。
在一种设计中，所述第二分流规则，包括：
第四分流规则，所述第四分流规则指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输。
在一种设计中，所述第一分流规则，包括：
所述用户面设备在非3GPP路径切换之前使用的分流规则、第三分流规则以及规则应用条件，所述第三分流规则用于指示所述用户面设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
在一种设计中，所述第二分流规则，包括：
所述终端设备在非3GPP路径切换之前使用的分流规则、第四分流规则以及规则应用条件，所述第四分流规则用于指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
当通信装置1100用于实现终端设备的功能时：处理单元1110，用于确定在多接入会话中执行非3GPP传输路径切换，所述多接入会话包括至少两个非3GPP传输路径。收发单元1120，用于向会话管理设备发送第一会话请求消息，所述第一会话请求消息包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径；所述收发单元1120，还用于接收来自所述会话管理设备发送的第二分流规则；所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径；所述处理单元1110，还用于根据所述第二分流规则确定传输路径。
在一种设计中，所述第一会话请求消息还包括所述多接入会话标识，所述多接入会话标识用于确定所述终端设备的所述多接入会话。
在一种设计中，所述第二分流规则，包括：
所述终端设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息；所述接入优先级指示信息，用于指示所述第二目标传输路径。
在一种设计中，所述第二目标传输路径为可信非3GPP传输路径或非可信非3GPP传输路径。
在一种设计中，所述第二分流规则，包括：
第四分流规则，所述第四分流规则指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输。
在一种设计中，所述第二分流规则，包括：
所述终端设备在非3GPP路径切换之前使用的分流规则、第四分流规则以及规则应用条件，所述第四分流规则用于指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
当通信装置1100用于实现UPF的功能时：收发单元1120，用于在多接入会话中执行非3GPP传输路径切换时，接收来自会话管理设备发送的第一分流规则；所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径，所述多接入会话包括至少两个非3GPP传输路径；处理单元1110，用于根据所述第一分流规则确定传输路径。
在一种设计中，所述第一分流规则，包括：
所述用户面设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息；所述接入优先级指示信息，用于指示所述第一目标传输路径。
在一种设计中，所述第一目标传输路径为可信非3GPP传输路径或非可信非3GPP传输路径。
在一种设计中，所述第一分流规则，包括：
第三分流规则，所述第三分流规则用于指示所述用户面设备通过所述至少两个非3GPP传输路径进行冗余传输。
在一种设计中，所述第一分流规则，包括：
所述用户面设备在非3GPP路径切换之前使用的分流规则、第三分流规则以及规则应用条件，所述第三分流规则用于指示所述用户面设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
当通信装置1100用于实现AMF的功能时：处理单元1110，用于确定在多接入会话中执行非3GPP传输路径切换，所述多接入会话包括至少两个非3GPP传输路径。收发单元1120，用于向会话管理设备发送第二请求消息，所述第二请求消息包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径；接收来自所述会话管理设备发送的第二分流规则；所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径；将所述第二分流规则发送给终端设备。
在一种设计中，所述第二请求消息还包括所述多接入会话标识，所述多接入会话标识用于确定所述终端设备的所述多接入会话。
在一种设计中，所述第二请求消息还包括所述多接入会话的上下文标识，所述多接入会话的上下文标识用于确定所述终端设备的所述多接入会话。
在一种设计中，所述第二分流规则，包括：
所述终端设备在非3GPP路径切换之前使用的分流规则，以及接入优先级指示信息；所述接入优先级指示信息，用于指示所述第二目标传输路径。
在一种设计中，所述第二目标传输路径为可信非3GPP传输路径或非可信非3GPP传输路径。
在一种设计中，所述第二分流规则，包括：
第四分流规则，所述第四分流规则指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输。
在一种设计中，所述第二分流规则，包括：
所述终端设备在非3GPP路径切换之前使用的分流规则、第四分流规则以及规则应用条件，所述第四分流规则用于指示所述终端设备通过所述至少两个非3GPP传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
在一种设计中，所述处理单元1110，用于：
根据接收到的终端设备发送的用于请求路径切换的非接入层消息，确定执行非3GPP传输路径切换，所述非接入层消息中包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径。
在一种设计中，所述处理单元1110，还用于：
所述移动管理设备在执行非3GPP路径切换过程中，确定满足信令连接释放的第一条件；所述移动管理设备释放所述终端设备在目标非3GPP传输路径或源非3GPP传输路径的信令连接。
在一种设计中，所述信令连接释放的第一条件，包括：
所述移动管理设备在所述终端设备完成所述目标非3GPP传输路径注册后开启的第一定时器到期，所述第一定时器用于指示触发源非3GPP传输路径信令连接释放；或者，所述移动管理设备在所述终端设备完成所述目标非3GPP传输路径注册后开启的第二定时器到期，以及所述终端设备没有完成在所述目标非3GPP传输路径的切换，所述第二定时器用于指示触发目标非3GPP传输路径信令连接释放。
在一种设计中，所述处理单元1110，还用于：
确定所述终端设备完成非3GPP传输路径切换后，向所述会话管理设备发送第三请求消息，所述第三请求消息用于指示应用所述终端设备和/或用户面设备在非3GPP传输路径切换之前使用的分流规则。
有关上述处理单元1110和收发单元1120更详细的描述可以直接参考图7至图10所示的方法实施例中相关描述直接得到，这里不加赘述。
请参见图12，图12为本申请实施例提供的装置1200的示意图，该装置1200可以为电子装置，或者电子装置中的一部件，例如芯片或集成电路等。该装置1200可包括至少一个处理器1202和通信接口1204。进一步，可选的，所述装置还可以包括至少一个存储器1201。更进一步，可选的，还可以包含总线1203。其中，存储器1201、处理器1202和通信接口1204通过总线1203相连。
其中，存储器1201用于提供存储空间，存储空间中可以存储操作系统和计算机程序 等数据。本申请实施例中提及的存储器1201可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。处理器1202是进行算术运算和/或逻辑运算的模块，具体可以是中央处理器(central processing unit，CPU)、图片处理器(graphics processing unit，GPU)、微处理器(microprocessor unit，MPU)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程逻辑门阵列(field programmable gate array，FPGA)、复杂可编程逻辑器件(complex programmable logic device，CPLD)、协处理器(协助中央处理器完成相应处理和应用)、微控制单元(microcontroller unit，MCU)等处理模块中的一种或者多种的组合。
需要说明的是，当处理器为通用处理器、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
通信接口1204可以用于为所述至少一个处理器提供信息输入或者输出。和/或所述通信接口可以用于接收外部发送的数据和/或向外部发送数据，可以为包括诸如以太网电缆等的有线链路接口，也可以是无线链路(Wi-Fi、蓝牙、通用无线传输、车载短距通信技术等)接口。可选的，通信接口1204还可以包括与接口耦合的发射器(如射频发射器、天线等)，或者接收器等。
在一些实施例中，上述装置1200可以为上文方法实施例中的SMF或者SMF中的部件，例如芯片或者集成电路。该装置1200中的处理器1202用于读取所述存储器1201中存储的计算机程序，控制所述SMF执行以下操作：
确定在多接入会话中执行非3GPP传输路径切换，所述多接入会话包括至少两个非3GPP传输路径；向用户面设备发送第一分流规则和/或向终端设备发送第二分流规则；所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径；所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径。
可选的，该SMF中的处理器1202，还可以用于读取存储器1201中的程序并执行如图7所示的S701～S702中SMF执行的方法流程；或执行如图8所示的S800～S829中SMF执行的方法流程；或者执行如图9所示的S901～S916中SMF执行的方法流程；或者执行如图10所示的S1001～S1016中SMF执行的方法流程。
关于具体细节，可参见上文方法实施例中的记载，在此不再赘述。
在另一些实施例中，上述装置1200可以为上文方法实施例中的终端设备或者终端设 备中的部件，例如芯片或者集成电路。该装置1200中的处理器1202用于读取所述存储器1201中存储的计算机程序，控制所述终端设备执行以下操作：
在多接入会话中执行非3GPP传输路径切换，所述多接入会话包括至少两个非3GPP传输路径；向会话管理设备发送第一会话请求消息，所述第一会话请求消息包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径；接收来自所述会话管理设备发送的第二分流规则；所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径；根据所述第二分流规则确定传输路径。
可选的，该UE中的处理器1202，还可以用于读取存储器1201中的程序并执行如图2所示的S701～S702中SMF执行的方法流程；或执行如图8所示的S800～S829中SMF执行的方法流程；或者执行如图9所示的S901～S916中SMF执行的方法流程；或者执行如图10所示的S1001～S1016中SMF执行的方法流程。
关于具体细节，可参见上文方法实施例中的记载，在此不再赘述。
在另一些实施例中，上述装置1200可以为上文方法实施例中的AMF或者AMF中的部件，例如芯片或者集成电路。该装置1200中的处理器1202用于读取所述存储器1201中存储的计算机程序，控制所述AMF执行以下操作：
确定在多接入会话中执行非3GPP传输路径切换，所述多接入会话包括至少两个非3GPP传输路径；向会话管理设备发送第二请求消息，所述第二请求消息包括切换指示信息，所述切换指示信息指示执行非3GPP传输路径切换和/或指示建立的目标传输路径为非3GPP传输路径；接收来自所述会话管理设备发送的第二分流规则；所述第二分流规则用于支持所述终端设备在所述至少两个非3GPP传输路径中确定第二目标传输路径；将所述第二分流规则发送给终端设备；或者，
该装置1200中的处理器1202用于读取所述存储器1201中存储的计算机程序，控制所述AMF执行以下操作：
在执行非3GPP路径切换过程中，确定满足信令连接释放的第一条件；释放所述终端设备在目标非3GPP传输路径或源非3GPP传输路径的信令连接。
可选的，该AMF中的处理器1202，还可以用于读取存储器1201中的程序并执行如图2所示的S701～S702中SMF执行的方法流程；或执行如图8所示的S800～S829中SMF执行的方法流程；或者执行如图9所示的S901～S916中SMF执行的方法流程；或者执行如图10所示的S1001～S1016中SMF执行的方法流程。
关于具体细节，可参见上文方法实施例中的记载，在此不再赘述。
在另一些实施例中，上述装置1200可以为上文方法实施例中的UPF或者UPF中的部件，例如芯片或者集成电路。该装置1200中的处理器1202用于读取所述存储器1201中存储的计算机程序，控制所述UPF执行以下操作：
用于在多接入会话中执行非3GPP传输路径切换时，接收来自会话管理设备发送的第一分流规则；所述第一分流规则用于支持所述用户面设备在所述至少两个非3GPP传输路径中确定第一目标传输路径，所述多接入会话包括至少两个非3GPP传输路径；根据所述第一分流规则确定传输路径。
可选的，该UPF中的处理器1202，还可以用于读取存储器1201中的程序并执行S701～S702中SMF执行的方法流程；或执行如图8所示的S800～S829中SMF执行的方法流程；或者执行如图9所示的S901～S916中SMF执行的方法流程；或者执行如图10所示的S1001～S1016中SMF执行的方法流程。
关于具体细节，可参见上文方法实施例中的记载，在此不再赘述。
本申请实施例还提供一种通信路径切换系统，包括终端设备、SMF和AMF。可选的，还包括UPF。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也不表示先后顺序。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。“至少一个”是指一个或者多个。至少两个是指两个或者多个。“至少一个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个、种)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。“多个”是指两个或两个以上，其它量词与之类似。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置， 离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中。
在一个或多个示例性的设计中，本申请所描述的上述功能可以在硬件、软件、固件或这三者的任意组合来实现。如果在软件中实现，这些功能可以存储与电脑可读的媒介上，或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通用或特殊电脑可以接入访问的可用媒体。例如，这样的电脑可读媒体可以包括但不限于RAM、ROM、EEPROM、CD-ROM或其它光盘存储、磁盘存储或其它磁性存储装置，或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理器读取形式的程序代码的媒介。此外，任何连接都可以被适当地定义为电脑可读媒介，例如，如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线(DSL)或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。所述的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、数字通用光盘(Digital Versatile Disc，DVD)、软盘和蓝光光盘，磁盘通常以磁性复制数据，而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。

Claims (30)

  1. 一种通信方法，其特征在于，所述方法包括：
    会话管理设备确定在多接入会话中执行非第三代合作伙伴计划传输路径切换，所述多接入会话包括至少两个非第三代合作伙伴计划传输路径；
    所述会话管理设备向用户面设备发送第一分流规则和/或向终端设备发送第二分流规则；所述第一分流规则用于支持所述用户面设备在所述至少两个非第三代合作伙伴计划传输路径中确定第一目标传输路径；所述第二分流规则用于支持所述终端设备在所述至少两个非第三代合作伙伴计划传输路径中确定第二目标传输路径。
  2. 根据权利要求1所述的方法，其特征在于，所述会话管理设备确定在多接入会话中执行非第三代合作伙伴计划传输路径切换，包括：
    所述会话管理设备根据接收到的会话请求消息，确定在多接入会话中执行非第三代合作伙伴计划传输路径切换，所述会话请求消息包括切换指示信息，所述切换指示信息指示执行非第三代合作伙伴计划传输路径切换和/或指示建立的目标传输路径为非第三代合作伙伴计划传输路径；
    所述会话请求消息是所述终端设备在确定执行非第三代合作伙伴计划传输路径后发送的第一会话请求消息；或者，所述会话请求消息是移动管理设备在确定执行非第三代合作伙伴计划传输路径后发送的第二会话请求消息。
  3. 根据权利要求2所述的方法，其特征在于，所述会话管理设备根据接收到的会话请求消息，确定在多接入会话中执行非第三代合作伙伴计划传输路径切换，包括：
    当所述切换指示信息指示建立的目标传输路径为非第三代合作伙伴计划传输路径时，所述会话管理设备在确定所述多接入会话已建立的源传输路径为非第三代合作伙伴计划传输路径时，根据所述会话请求确定执行所述非第三代合作伙伴计划路径切换。
  4. 根据权利要求2或3所述的方法，其特征在于，所述会话请求消息还包括所述多接入会话的会话标识；
    所述会话标识用于确定所述终端设备的所述多接入会话。
  5. 根据权利要求2～4中任一项所述的方法，其特征在于，所述会话请求消息还包括所述多接入会话的会话上下文标识；
    所述会话上下文标识用于确定所述终端设备的所述多接入会话。
  6. 根据权利要求1～5中任一项所述的方法，其特征在于，所述第一分流规则，包括：
    所述用户面设备在非第三代合作伙伴计划路径切换之前使用的分流规则，以及接入优先级指示信息；
    所述接入优先级指示信息，用于指示所述第一目标传输路径；
    所述第二分流规则，包括：
    所述终端设备在非第三代合作伙伴计划路径切换之前使用的分流规则，以及接入优先级指示信息；
    所述接入优先级指示信息，用于指示所述第二目标传输路径。
  7. 根据权利要求6所述的方法，其特征在于，所述第一目标传输路径为可信非第三代合作伙伴计划传输路径或非可信非第三代合作伙伴计划传输路径；
    所述第二目标传输路径为可信非第三代合作伙伴计划传输路径或非可信非第三代合 作伙伴计划传输路径。
  8. 根据权利要求1～5中任一项所述的方法，其特征在于，所述第一分流规则，包括：
    第三分流规则，所述第三分流规则用于指示所述用户面设备通过所述至少两个非第三代合作伙伴计划传输路径进行冗余传输；
    所述第二分流规则，包括：
    第四分流规则，所述第四分流规则指示所述终端设备通过所述至少两个非第三代合作伙伴计划传输路径进行冗余传输。
  9. 根据权利要求1～5中任一项所述的方法，其特征在于，所述第一分流规则，包括：
    所述用户面设备在非第三代合作伙伴计划路径切换之前使用的分流规则、第三分流规则以及规则应用条件，所述第三分流规则用于指示所述用户面设备通过所述至少两个非第三代合作伙伴计划传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则；
    所述第二分流规则，包括：
    所述终端设备在非第三代合作伙伴计划路径切换之前使用的分流规、第四分流规则以及规则应用条件，所述第四分流规则用于指示所述终端设备通过所述至少两个非第三代合作伙伴计划传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
  10. 一种通信方法，其特征在于，所述方法包括：
    终端设备确定在多接入会话中执行非第三代合作伙伴计划传输路径切换，所述多接入会话包括至少两个非第三代合作伙伴计划传输路径；
    所述终端设备向会话管理设备发送第一会话请求消息，所述第一会话请求消息包括切换指示信息，所述切换指示信息指示执行非第三代合作伙伴计划传输路径切换和/或指示建立的目标传输路径为非第三代合作伙伴计划传输路径；
    所述终端设备接收来自所述会话管理设备发送的第二分流规则；所述第二分流规则用于支持所述终端设备在所述至少两个非第三代合作伙伴计划传输路径中确定第二目标传输路径；
    所述终端设备根据所述第二分流规则确定传输路径。
  11. 根据权利要求10所述的方法，其特征在于，所述第一会话请求消息还包括所述多接入会话标识，所述多接入会话标识用于确定所述终端设备的所述多接入会话。
  12. 根据权利要求10或11所述的方法，其特征在于，所述第二分流规则，包括：
    所述终端设备在非第三代合作伙伴计划路径切换之前使用的分流规则，以及接入优先级指示信息；
    所述接入优先级指示信息，用于指示所述第二目标传输路径。
  13. 根据权利要求12所述的方法，其特征在于，所述第二目标传输路径为可信非第三代合作伙伴计划传输路径或非可信非第三代合作伙伴计划传输路径。
  14. 根据权利要求10或11所述的方法，其特征在于，所述第二分流规则，包括：
    第四分流规则，所述第四分流规则指示所述终端设备通过所述至少两个非第三代合作伙伴计划传输路径进行冗余传输。
  15. 根据权利要求10或11所述的方法，其特征在于，所述第二分流规则，包括：
    所述终端设备在非第三代合作伙伴计划路径切换之前使用的分流规则、第四分流规则以及规则应用条件，所述第四分流规则用于指示所述终端设备通过所述至少两个非第三代合作伙伴计划传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
  16. 一种通信方法，其特征在于，所述方法包括：
    移动管理设备确定在多接入会话中执行非第三代合作伙伴计划传输路径切换，所述多接入会话包括至少两个非第三代合作伙伴计划传输路径；
    所述移动管理设备向会话管理设备发送第二请求消息，所述第二请求消息包括切换指示信息，所述切换指示信息指示执行非第三代合作伙伴计划传输路径切换和/或指示建立的目标传输路径为非第三代合作伙伴计划传输路径；
    所述移动管理设备接收来自所述会话管理设备发送的第二分流规则；所述第二分流规则用于支持所述终端设备在所述至少两个非第三代合作伙伴计划传输路径中确定第二目标传输路径；
    所述移动管理设备将所述第二分流规则发送给终端设备。
  17. 根据权利要求16所述的方法，其特征在于，所述第二请求消息还包括所述多接入会话标识，所述多接入会话标识用于确定所述终端设备的所述多接入会话。
  18. 根据权利要求16或17所述的方法，其特征在于，所述第二请求消息还包括所述多接入会话的上下文标识，所述多接入会话的上下文标识用于确定所述终端设备的所述多接入会话。
  19. 根据权利要求16～18中任一项所述的方法，其特征在于，所述第二分流规则，包括：
    所述终端设备在非第三代合作伙伴计划路径切换之前使用的分流规则，以及接入优先级指示信息；
    所述接入优先级指示信息，用于指示所述第二目标传输路径。
  20. 根据权利要求19所述的方法，其特征在于，所述第二目标传输路径为可信非第三代合作伙伴计划传输路径或非可信非第三代合作伙伴计划传输路径。
  21. 根据权利要求16～18中任一项所述的方法，其特征在于，所述第二分流规则，包括：
    第四分流规则，所述第四分流规则指示所述终端设备通过所述至少两个非第三代合作伙伴计划传输路径进行冗余传输。
  22. 根据权利要求16～18中任一项所述的方法，其特征在于，所述第二分流规则，包括：
    所述终端设备在非第三代合作伙伴计划路径切换之前使用的分流规则、第四分流规则以及规则应用条件，所述第四分流规则用于指示所述终端设备通过所述至少两个非第三代合作伙伴计划传输路径进行冗余传输，所述规则应用条件用于指示执行路径切换时应用分流规则。
  23. 根据权利要求16～22中任一项所述的方法，其特征在于，所述移动管理设备确定在多接入会话中执行非第三代合作伙伴计划传输路径切换，包括：
    所述移动管理设备根据接收到的终端设备发送的用于请求路径切换的非接入层消息，确定执行非第三代合作伙伴计划传输路径切换，所述非接入层消息中包括切换指示信息，所述切换指示信息指示执行非第三代合作伙伴计划传输路径切换和/或指示建立的目标传输路径为非第三代合作伙伴计划传输路径。
  24. 根据权利要求16～23中任一项所述的方法，其特征在于，所述方法还包括：
    所述移动管理设备在执行非第三代合作伙伴计划路径切换过程中，确定满足信令连接释放的第一条件；
    所述移动管理设备释放所述终端设备在目标非第三代合作伙伴计划传输路径或源非第三代合作伙伴计划传输路径的信令连接。
  25. 根据权利要求24所述的方法，其特征在于，所述信令连接释放的第一条件，包括：
    所述移动管理设备在所述终端设备完成所述目标非第三代合作伙伴计划传输路径注册后开启的第一定时器到期，所述第一定时器用于指示触发源非第三代合作伙伴计划传输路径信令连接释放；或者，
    所述移动管理设备在所述终端设备完成所述目标非第三代合作伙伴计划传输路径注册后开启的第二定时器到期，以及所述终端设备没有完成在所述目标非第三代合作伙伴计划传输路径的切换，所述第二定时器用于指示触发目标非第三代合作伙伴计划传输路径信令连接释放。
  26. 根据权利要求16～25中任一项所述的方法，其特征在于，所述方法还包括：
    所述移动管理设备确定所述终端设备完成非第三代合作伙伴计划传输路径切换后，向所述会话管理设备发送第三请求消息，所述第三请求消息用于指示应用所述终端设备和/或用户面设备在非第三代合作伙伴计划传输路径切换之前使用的分流规则。
  27. 一种通信装置，其特征在于，包括用于执行如权利要求1～9中任一项所述的方法的模块，或者包括用于执行如权利要求10～15中任一项所述的方法的模块，或者包括用于执行如权利要求16～26中任一项所述的方法的模块。
  28. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1～9中任一项所述的方法，或用于实现如权利要求10～15中任一项所述的方法，或用于实现如权利要求16～26中任一项所述的方法。
  29. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1～9中任一项所述的方法，或用于实现如权利要求10～15中任一项所述的方法，或用于实现如权利要求16～26中任一项所述的方法。
  30. 一种计算机程序产品，其特征在于，包含计算机可执行指令，当所述指令在计算机上运行时，使得如权利要求1～9中任一项所述的方法被执行，或者如权利要求10～15中任一项所述的方法被执行，或者如权利要求16～26中任一项所述的方法被执行。
PCT/CN2023/080460 2022-03-29 2023-03-09 一种通信方法及装置 Ceased WO2023185411A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2024557484A JP7804101B2 (ja) 2022-03-29 2023-03-09 通信方法および通信装置
EP23777789.1A EP4485889A4 (en) 2022-03-29 2023-03-09 COMMUNICATION METHOD AND APPARATUS
US18/897,771 US20250024332A1 (en) 2022-03-29 2024-09-26 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210318790.2 2022-03-29
CN202210318790.2A CN116939727A (zh) 2022-03-29 2022-03-29 一种通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/897,771 Continuation US20250024332A1 (en) 2022-03-29 2024-09-26 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2023185411A1 true WO2023185411A1 (zh) 2023-10-05

Family

ID=88198976

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/080460 Ceased WO2023185411A1 (zh) 2022-03-29 2023-03-09 一种通信方法及装置

Country Status (5)

Country Link
US (1) US20250024332A1 (zh)
EP (1) EP4485889A4 (zh)
JP (1) JP7804101B2 (zh)
CN (1) CN116939727A (zh)
WO (1) WO2023185411A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN120034986A (zh) * 2023-11-23 2025-05-23 华为技术有限公司 一种通信方法、装置及系统
WO2025152068A1 (zh) * 2024-01-17 2025-07-24 Oppo广东移动通信有限公司 无线通信的方法、终端设备和核心网设备
CN120786342A (zh) * 2024-04-03 2025-10-14 华为技术有限公司 一种通信方法、装置及可读存储介质
CN121310308A (zh) * 2024-07-09 2026-01-09 华为技术有限公司 一种通信方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104349413A (zh) * 2013-08-06 2015-02-11 电信科学技术研究院 一种不同接入技术的网络间分流的控制方法及装置
US20210127271A1 (en) * 2018-03-29 2021-04-29 Telefonaktiebolaget Lm Ericsson (Publ) Methods for support of user plane separation and user plane local offloading for 5g non-3gpp access

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102859329B1 (ko) * 2022-01-24 2025-09-12 엘지전자 주식회사 트래픽 조향을 위한 네트워크 등록 방법 및 이를 지원하는 장치
EP4456655A4 (en) * 2022-01-29 2025-04-30 Huawei Technologies Co., Ltd. Communication method and apparatus

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104349413A (zh) * 2013-08-06 2015-02-11 电信科学技术研究院 一种不同接入技术的网络间分流的控制方法及装置
US20210127271A1 (en) * 2018-03-29 2021-04-29 Telefonaktiebolaget Lm Ericsson (Publ) Methods for support of user plane separation and user plane local offloading for 5g non-3gpp access

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CHARTER COMMUNICATIONS, LENOVO, MOTOROLA MOBILITY, CABLELABS: "KI for WT#5.1", 3GPP TSG-WG SA2 MEETING #149E, S2-2200516, 27 January 2022 (2022-01-27), XP052104051 *
HUAWEI, HISILICON: "Solution for supporting traffic switching between two N3GPP paths", 3GPP TSG-WG SA2 MEETING #150E, S2-2203075, 12 April 2022 (2022-04-12), XP052135499 *
LENOVO, SAMSUNG, LG, CHARTER COMMUNICATIONS, NOKIA, NOKIA SHANGHAI BELL, BROADCOM, CABLELABS: "Consolidated solution for KI#5", SA WG2 MEETING #151E, S2-2204761, 21 May 2022 (2022-05-21), XP052160247 *
See also references of EP4485889A4 *

Also Published As

Publication number Publication date
CN116939727A (zh) 2023-10-24
EP4485889A4 (en) 2025-07-02
US20250024332A1 (en) 2025-01-16
JP7804101B2 (ja) 2026-01-21
EP4485889A1 (en) 2025-01-01
JP2025510955A (ja) 2025-04-15

Similar Documents

Publication Publication Date Title
US11844142B2 (en) Communications method and apparatus
US11071015B2 (en) Access traffic steering/switching/splitting method in a network and network entity performing the same
JP7804101B2 (ja) 通信方法および通信装置
EP3694181B1 (en) Session establishment method, device and system
KR102469973B1 (ko) 통신 방법 및 장치
JP7307060B2 (ja) ベアラ識別子を決定する方法及び装置、並びに記憶媒体
US12464464B2 (en) Managing a ue preferred configuration
EP3799514B1 (en) Rate control methods, devices, computer program and system
WO2020135850A1 (zh) 通信方法和装置
JP7544430B2 (ja) 通信方法及び装置
CN109673060A (zh) 一种通信方法及装置
WO2021169683A1 (zh) 一种通信的方法及装置
WO2022155853A1 (zh) 无线通信方法、通信装置及通信系统
WO2024032207A1 (zh) 通信方法、装置和系统
WO2024027320A1 (zh) 无线通信的方法、装置和系统
WO2023143459A1 (zh) 授权方法及装置
WO2025200873A1 (zh) 信息传输方法及通信装置
WO2024051600A1 (zh) 网络信息处理方法及装置
WO2024001524A1 (zh) 一种通信方法及装置
CN118102407A (zh) 号段割接的方法、装置和系统
CN116671235A (zh) 通信方法、装置及系统
WO2025082240A1 (zh) 一种中央单元切换方法及相关装置
CN111436086B (zh) 安全保护方法及装置
WO2026092257A1 (zh) 通信方法和通信装置
WO2026026407A1 (zh) 一种通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23777789

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023777789

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2024557484

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202417073496

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2023777789

Country of ref document: EP

Effective date: 20240926

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202417073496

Country of ref document: IN