Communication method and communication apparatus

Abstract

Provided in the present application are a communication method. The method is applied to a multi-connection device, which comprises a plurality of pieces of subscription data. The multi-connection device uses first subscription data to execute the method, wherein the first subscription data is one of the plurality of pieces of subscription data. The method comprises: sending a first session establishment request, which comprises first instruction information and a session identifier of a multi-connection session, wherein the first instruction information is used for instructing the establishment of the multi-connection session; and receiving a first session establishment acceptance message, which comprises session association information and a first IP address, wherein the session association information is used for associating session transmission paths of a plurality of pieces of subscription data, the first IP address comprises an IP address allocated to a first session by an SMF, and the first session is a sub-session of the multi-connection session which is established by using first subscription data. The technical solution of the present application can associate sessions of a multi-connection device.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on February 6, 2024, with application number 202410171483.5 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more specifically, to a communication method and device. Background Art

[0003] Existing standards define access traffic steering, switching, and splitting (ATSS) features, allowing user equipment (UE) to access the core network through both a 3rd Generation Partnership Project (3GPP) connection and a non-3GPP connection to obtain services. When the UE is not within the coverage of its home public land mobile network (HPLMN), it can access a visited public land mobile network (VPLMN) through 3GPP and simultaneously access the HPLMN through a non-3GPP connection. After the UE accesses the network through two different access types, it can establish a multi-access protocol data unit (MA PDU) session to obtain services.

[0004] The concept of dual-connectivity devices was introduced in the Release 19 standardization discussions. A dual-connectivity device can be a terminal device containing two subscriptions, or it can include two independent user equipment (UE), with the subscriptions of these two UEs associated with each other in the network. For example, the device can be a UE with two subscriber identity modules (SIMs) that supports dual-SIM dual access, or it can be two completely independent UEs that are encapsulated in the same device or connected together by some other means.

[0005] In the prior art, when a UE establishes a session, since they are two different access types of the same UE, the session management function (SMF) network element naturally knows that they are the same UE. The two can be associated through the MA PDU session, using the same IP address, ensuring that the IP address remains unchanged during session switching. However, when a dual-connected device establishes a session, each UE session has a separate IP address. During a session switch, for example, switching from UE1's session to UE2's session, the IP address change is equivalent to reestablishing the session, resulting in a brief session interruption and affecting the user experience. Summary of the Invention

[0006] The present application provides a communication method and a communication device that can associate sessions established by dual-connection devices through different subscription data.

[0007] In a first aspect, a communication method is provided, which is applied to a multi-connection device, wherein the multi-connection device includes multiple contract data, and the multi-connection device uses first contract data to execute the method, where the first contract data is one of the multiple contract data. The method includes: sending a first session establishment request, the first session establishment request including first indication information and a session identifier of the multi-connection session, the first indication information being used to indicate the establishment of the multi-connection session; receiving a first session establishment acceptance message, the first session establishment acceptance message including session association information and a first network protocol (internet protocol, IP) address, the session association information being used to associate session transmission paths of the multiple contract data, the first IP address including an IP address allocated by a session management function (SMF) network element to the first session, and the first session being a sub-session of the multi-connection session established using the first contract data.

[0008] In the technical solution provided by the present application, sub-sessions established by multi-connected devices through different contract data can be associated together through session association information, and each sub-session is assigned a different IP address to jointly complete the transmission of the session.

[0009] The multiple subscription data included in the multi-connection device are associated with each other.

[0010] In some possible implementations, the multi-connection device may be a dual-steer device. The multi-connection device includes a first subscription data and a second subscription data, UE1 communicates via the first subscription data, and UE2 communicates via the second subscription data. Optionally, the multi-connection device may further include a third subscription data, a fourth subscription data, and the like, UE3 communicates via the third subscription data, and UE4 communicates via the fourth subscription data. This application does not limit the amount of subscription data included in the multi-connection device.

[0011] In this application, when a multi-connection device communicates via a first subscription, the multi-connection device may be referred to as UE1. When the multi-connection device communicates via a second subscription, the multi-connection device may be referred to as UE2, and so on.

[0012] Exemplarily, the subscription data may be a subscriber permanent identifier (SUPI) or a universal subscriber identity module (USIM). In some possible application scenarios, the subscription data may also be directly referred to as user equipment or terminal equipment, and this application does not limit the name.

[0013] In some possible implementations, the session identifier of the multi-connection session may be an identifier (ID) assigned by UE1 to the multi-connection session, and the SMF may associate the assigned ID with the ID of UE1. Optionally, in order to avoid conflicts between the IDs of the sessions established by UE1 and UE2, the session identifier of the multi-connection session may also include the ID of UE1. The ID of UE1 may be a 5G-globally unique temporary UE identifier (5G-GUTI) in the 5G system, a temporary mobile subscription identifier (5G-S-TMSI) in the 5G system, or a SUPI. The specific format of the session identifier of the dual-connection session should not be understood as a limitation to the present application.

[0014] Optionally, the session identifier of the dual-connection session may also be included in the first indication information.

[0015] The first indication information is used to indicate the establishment of a multi-connection session, wherein the multi-connection session is a session established by the multi-connection device. The multi-connection session includes a session established using at least one subscription data from a plurality of subscription data, and the session established using the subscription data is called a subsession of the multi-connection session.

[0016] The first session is a sub-session of a multi-connection session established by the multi-connection device using the first subscription data. The multi-connection device may also use other subscription data to establish other sub-sessions of the multi-connection session. These sub-sessions together constitute the multi-connection session.

[0017] In some possible implementations, the session association information may also include the first IP address, that is, the first session establishment accept message includes the session association information, and the session association information includes the first IP address.

[0018] In combination with the first aspect, in certain implementations of the first aspect, the session association information includes a session public IP address and / or a connection ID, the session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0019] Exemplarily, the multipath transmission connection may be a connection established through multipath transmission control protocol (MPTCP) and multipath quick user datagram protocol internet connections (MPQUIC) functions.

[0020] When the multipath transport connection is an MPTCP connection, the session association information may be a session public IP address; when the multipath transport connection is an MPQUIC connection, the session association information may be a session public IP address and / or a connection ID.

[0021] After the session establishment of the multi-connection device is completed, the multi-connection device can perform data transmission with the application server through the session association information and the allocated IP address, wherein the first session can use the first IP address for data transmission.

[0022] In the technical solution provided in the present application, sub-sessions established by multi-connected devices through different contract data can be associated together through session association information to jointly complete the transmission of the session.

[0023] In a second aspect, a communication method is provided, which is applied to a multi-connection device, wherein the multi-connection device includes multiple contract data, and the multi-connection device uses second contract data to execute the method, where the second contract data is one of the multiple contract data. The method includes: sending a second session establishment request, the second session establishment request includes second indication information and a session identifier of the multi-connection session, and the second indication information is used to indicate the establishment of the multi-connection session; receiving a second session establishment acceptance message, the second session establishment acceptance message includes a second IP address, the second IP address includes the IP address assigned by the SMF to the second session, and the second session is a sub-session of the multi-connection session established using the second contract data.

[0024] In the technical solution provided by the present application, sub-sessions established by multi-connected devices through different contract data can be associated together through session association information, and each sub-session is assigned a different IP address to jointly complete the transmission of the session.

[0025] In some possible implementations, the multi-connection device may be a dual-connection device. The multi-connection device includes a first subscription data and a second subscription data, UE1 communicates via the first subscription data, and UE2 communicates via the second subscription data. Optionally, the multi-connection device may further include a third subscription data, a fourth subscription data, and the like, UE3 communicates via the third subscription data, and UE4 communicates via the fourth subscription data. This application does not limit the amount of subscription data included in the multi-connection device.

[0026] In this application, when a multi-connection device communicates via a first subscription, the multi-connection device may be referred to as UE1. When the multi-connection device communicates via a second subscription, the multi-connection device may be referred to as UE2, and so on.

[0027] Exemplarily, the subscription data may be SUPI or USIM. In some possible application scenarios, the subscription data may also be directly referred to as user equipment or terminal equipment, and this application does not limit the name.

[0028] UE1 may send the session association information and the session identifier of the multi-connection session to UE2. In some possible implementations, since multiple subscription data of a multi-connection device are associated with each other, UE2 may also directly obtain the session association information and the session identifier of the multi-connection session of UE1.

[0029] In some possible implementations, the session identifier of the multi-connection session may be an ID assigned by UE1 to the multi-connection session, and the SMF may associate the assigned ID with the ID of UE1. Optionally, to avoid conflicts between the IDs of the sessions established by UE1 and UE2, the session identifier of the multi-connection session may also include the ID of UE1. The ID of UE1 may be 5G-GUTI, 5G-S-TMSI, or SUPI. The specific format of the session identifier of the dual-connection session should not be understood as a limitation to this application.

[0030] Optionally, the session identifier of the dual-connection session may also be included in the second indication information. The second indication information may be the same as the first indication information.

[0031] The second indication information is used to indicate the establishment of a multi-connection session, where the multi-connection session is a session established by the multi-connection device. The multi-connection session includes a session established using at least one subscription data from a plurality of subscription data, where the session established using the subscription data is called a subsession of the multi-connection session.

[0032] The second session is a sub-session of the multi-connection session established by the multi-connection device using the second subscription data. The multi-connection device may also use other subscription data to establish other sub-sessions of the multi-connection session. These sub-sessions together constitute the multi-connection session.

[0033] In combination with the second aspect, in certain implementations of the second aspect, the session association information includes a session public IP address and / or a connection ID, the session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0034] Exemplarily, the multipath transmission connection may be a connection established through MPTCP or MPQUIC functions.

[0035] When the multipath transport connection is an MPTCP connection, the session association information may be a session public IP address; when the multipath transport connection is an MPQUIC connection, the session association information may be a session public IP address and / or a connection ID.

[0036] After the multi-connection device session is established, the multi-connection device can perform data transmission with the application server through the session association information and the allocated IP address, wherein the second session can use the second IP address for data transmission.

[0037] In the technical solution provided in the present application, sub-sessions established by multi-connected devices through different contract data can be associated together through session association information to jointly complete the transmission of the session.

[0038] According to a third aspect, a communication method is provided, which is applied to SMF, and the method includes: receiving a first session establishment request sent by a multi-connection device using first contract data, the first session establishment request including first indication information and a session identifier of the multi-connection session, the first indication information being used to indicate the establishment of the multi-connection session, the multi-connection device including multiple contract data, the multiple contract data including the first contract data; sending a first session establishment acceptance message, the first session establishment acceptance message including session association information and a first IP address, the session association information being used to associate the session transmission path of the multiple contract data, the first IP address including the IP address assigned by the SMF to the first session, and the first session being a sub-session of the multi-connection session established using the first contract data.

[0039] In the technical solution provided by this application, sub-sessions established by multi-connected devices through different contract data can be associated together through session association information. Each sub-session is assigned a different IP address by SMF to jointly complete the transmission of the session.

[0040] The multiple subscription data included in the multi-connection device are associated with each other.

[0041] In some possible implementations, the multi-connection device may be a dual-connection device. The multi-connection device includes a first subscription data and a second subscription data, UE1 communicates via the first subscription data, and UE2 communicates via the second subscription data. Optionally, the multi-connection device may further include a third subscription data, a fourth subscription data, and the like, UE3 communicates via the third subscription data, and UE4 communicates via the fourth subscription data. This application does not limit the amount of subscription data included in the multi-connection device.

[0042] In this application, when a multi-connection device communicates via a first subscription, the multi-connection device may be referred to as UE1. When the multi-connection device communicates via a second subscription, the multi-connection device may be referred to as UE2, and so on.

[0043] Exemplarily, the subscription data may be SUPI or USIM. In some possible application scenarios, the subscription data may also be directly referred to as user equipment or terminal equipment, and this application does not limit the name.

[0044] In some possible implementations, the session identifier of the multi-connection session may be an ID assigned by UE1 to the multi-connection session, and the SMF may associate the assigned ID with the ID of UE1. Optionally, to avoid conflicts between the IDs of the sessions established by UE1 and UE2, the session identifier of the multi-connection session may also include the ID of UE1. The ID of UE1 may be 5G-GUTI, 5G-S-TMSI, or SUPI. The specific format of the session identifier of the dual-connection session should not be understood as a limitation to this application.

[0045] Optionally, the session identifier of the dual-connection session may also be included in the first indication information.

[0046] After receiving the first session establishment request, SMF determines that the session type established by UE1 is a multi-connection session. It checks whether the session association information and / or the first IP address of the multi-connection session exists in the context based on the session identifier. If not, it indicates that it is a brand new multi-connection session. SMF allocates session association information and the first IP address to the first session.

[0047] In some possible implementations, the session association information may also include the first IP address, that is, the first session establishment accept message includes the session association information, and the session association information includes the first IP address.

[0048] In combination with the third aspect, in certain implementations of the third aspect, the session association information includes a session public IP address and / or a connection ID, the session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0049] Exemplarily, the multipath transmission connection may be a connection established through MPTCP or MPQUIC functions.

[0050] When the multipath transport connection is an MPTCP connection, the session association information may be a session public IP address; when the multipath transport connection is an MPQUIC connection, the session association information may be a session public IP address and / or a connection ID.

[0051] In the technical solution provided in the present application, sub-sessions established by multi-connected devices through different contract data can be associated together through session association information to jointly complete the transmission of the session.

[0052] In combination with the third aspect, in certain implementations of the third aspect, before sending the first session establishment acceptance message, the method also includes: sending a third session establishment request to the UPF, the third session establishment request being used to establish a session with the UPF, the third session establishment request including the session association information and the first IP address, or the third session establishment request including the session identifier and the first IP address, and the UPF being used to aggregate sub-sessions of the multi-connection session.

[0053] In some possible implementations, the third session establishment request includes the first IP address and also includes session association information and / or a session identifier. The UPF may return a response message to the SMF, indicating that the N4 session between the SMF and the UPF is established. The response message includes CN resources for the access network to send uplink data to the UPF.

[0054] In the technical solution provided in this application, the SMF can select the same UPF to establish a session for multiple associated UEs, and the UPF aggregates the sub-sessions to communicate with the application server to complete the transmission of the session.

[0055] In combination with the third aspect, in some implementations of the third aspect, the method also includes: receiving a second session establishment request sent by the multi-connection device using second subscription data, the second session establishment request including second indication information and the session identifier, the second indication information being used to indicate the establishment of the multi-connection session, and the multiple subscription data including the second subscription data; sending a second session establishment acceptance message, the second session establishment acceptance message including a second IP address, the second IP address including the IP address assigned by the SMF to the second session, and the second session being a sub-session of the multi-connection session established using the second subscription data.

[0056] Optionally, the session identifier of the dual-connection session may also be included in the second indication information. The second indication information may be the same as the first indication information.

[0057] When SMF determines that the session type established by UE2 is a dual-connection session, it checks whether there is session association information and / or a first IP address in the context corresponding to the session identifier. If so, it indicates that a session sub-path needs to be added to an existing dual-connection session, and SMF allocates a second IP address to the second session.

[0058] The second session is a sub-session of the multi-connection session established by the multi-connection device using the second subscription data. The first session and the second session may together constitute the multi-connection session.

[0059] In the technical solution provided by the present application, sub-sessions established by multi-connected devices through different contract data can be associated together through session association information, and each sub-session is assigned a different IP address to jointly complete the transmission of the session.

[0060] In combination with the third aspect, in certain implementations of the third aspect, before sending the second session establishment acceptance message, the method also includes: sending a fourth session establishment request to the UPF, the fourth session establishment request being used to establish a session with the UPF, the fourth session establishment request including the session association information and the second IP address, or the fourth session establishment request including the session identifier and the second IP address.

[0061] The SMF receives the session identifier sent by UE2, determines the UPF connected to UE1 according to the context information corresponding to the identifier, and sends a fourth session establishment request to the UPF.

[0062] In some possible implementations, the fourth session establishment request includes the second IP address and session association information and / or a session identifier. The UPF can aggregate the first session and the second session through the session association information and / or the session identifier.

[0063] The UPF may return a response message to the SMF, indicating that the N4 session between the SMF and the UPF is established. The response message includes CN resource information, which is used by the access network to send uplink data to the UPF.

[0064] In the technical solution provided in the present application, sub-sessions established by multi-connected devices through different contract data can be aggregated together through UPF. After aggregating the sub-sessions, UPF communicates with the application server to complete the transmission of the session.

[0065] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: sending a session registration message, wherein the session registration message is used to register the context information of the multi-connection session in a unified data management (UDM) network element, and the context information includes the type of the multi-connection session and the session identifier.

[0066] The SMF registers the context information of the multi-connection session with the UDM, which includes the type of the multi-connection session and the session identifier, and may also include the ID of the UE.

[0067] The UDM is configured with association information of multiple contract data of multi-connected devices. Based on this association information, the UDM can determine other contract data associated with a certain contract data, and determine the corresponding access and mobility management function (AMF) network element according to the context of the other contract data, and update the session information to the AMF network element. When the multi-connected device subsequently establishes a multi-connection session through other contract data, the AMF can select the same SMF to establish the multi-connection session.

[0068] In a fourth aspect, a communication method is provided, which is applied to a multi-connection device, wherein the multi-connection device includes multiple contract data, and the multi-connection device uses first contract data to execute the method, where the first contract data is one of the multiple contract data. The method includes: sending a first session establishment request, the first session establishment request includes first indication information, the first indication information is used to indicate that an agent is assigned to the multi-connection device, and the agent is used to establish a multi-path connection for the multi-connection device; receiving a first session establishment acceptance message, the first session establishment acceptance message includes information of the agent, the first session establishment acceptance message is used to indicate that the establishment of the first session is complete, and the first session is a session established by the multi-connection device using the first contract data; sending a connection establishment request to the agent according to the information of the agent; receiving a connection establishment acceptance message sent by the agent, the connection establishment acceptance message includes session association information, and the session association information is used to associate the session transmission paths of the multiple contract data.

[0069] In the technical solution provided in this application, a conventional session establishment process is performed for the session establishment request sent by the UE, but an agent is selected for the UE to aggregate the sessions of multiple UEs and establish a multi-path transmission connection on top of the session.

[0070] The multiple subscription data included in the multi-connection device are associated with each other.

[0071] In some possible implementations, the multi-connection device may be a dual-connection device. The multi-connection device includes a first subscription data and a second subscription data, UE1 communicates via the first subscription data, and UE2 communicates via the second subscription data. Optionally, the multi-connection device may further include a third subscription data, a fourth subscription data, and the like, UE3 communicates via the third subscription data, and UE4 communicates via the fourth subscription data. This application does not limit the amount of subscription data included in the multi-connection device.

[0072] In this application, when a multi-connection device communicates via a first subscription, the multi-connection device may be referred to as UE1. When the multi-connection device communicates via a second subscription, the multi-connection device may be referred to as UE2, and so on.

[0073] Exemplarily, the subscription data may be SUPI or USIM. In some possible application scenarios, the subscription data may also be directly referred to as user equipment or terminal equipment, and this application does not limit the name.

[0074] The first session is a PDU session established by the multi-connection device using the first subscription data. The multi-connection device can also use other subscription data to establish other PDU sessions, which are aggregated together through the proxy and share a multi-path transmission connection.

[0075] In combination with the fourth aspect, in certain implementations of the fourth aspect, the session association information includes a session public IP address and / or a connection ID, the session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0076] Exemplarily, the multipath transmission connection may be a connection established through MPTCP or MPQUIC functions.

[0077] When the multipath transport connection is an MPTCP connection, the session association information may be a session public IP address; when the multipath transport connection is an MPQUIC connection, the session association information may be a session public IP address and / or a connection ID.

[0078] It should be understood that the information of the agent may be the IP address of the agent, and may also include the ID of the agent, the type of the agent, etc.

[0079] In the technical solution provided in this application, a conventional session establishment process is performed for the session establishment request sent by the UE, but an agent is selected for the UE to aggregate the sessions of multiple UEs and establish a multi-path transmission connection on top of the session.

[0080] In combination with the fourth aspect, in some implementations of the fourth aspect, the first session establishment request further includes a session identifier of the first session.

[0081] In some possible implementations, the session identifier of the multi-connection session may be an ID assigned by UE1 for the multi-connection session, and the SMF may associate the assigned ID with the ID of UE1. Optionally, in order to avoid conflicts between the IDs of the sessions established by UE1 and UE2, the session identifier of the multi-connection session may also include the ID of UE1. The ID of UE1 may be 5G-GUTI, 5G-S-TMSI or SUPI, and the specific format of the session identifier should not be understood as a limitation to the present application. The SMF receives the first session establishment request, checks whether there is a corresponding context for the session identifier or whether there is information about an agent in the context. If not, it indicates that it is a brand new session, selects an agent that can serve as an anchor point, and a UPF that can connect to the anchor point.

[0082] In the technical solution provided in this application, the first session establishment request sent by UE1 to the SMF may also include a session identifier of the first session. Subsequently, other UEs associated with UE1 may send the session identifier of the first session to the SMF. The SMF may determine that it is the same session based on the context corresponding to the session identifier. Therefore, the SMF may allocate the same proxy and a UPF that can connect to the proxy to the other UEs.

[0083] In a fifth aspect, a communication method is provided, which is applied to a multi-connection device, wherein the multi-connection device includes multiple contract data, and the multi-connection device uses second contract data to execute the method, where the second contract data is one of the multiple contract data. The method includes: sending a second session establishment request, the second session establishment request includes second indication information and agent information, the second indication information is used to indicate the assignment of an agent to the multi-connection device, and the agent is used to establish a multi-path connection for the multi-connection device; receiving a second session establishment acceptance message, the second session establishment acceptance message is used to indicate that the establishment of the second session is complete, and the second session is a session established by the multi-connection device using the second contract data; sending a connection join request to the agent according to the agent information, the connection join request includes session association information, the connection join request is used to request to join the connection corresponding to the session association information, and the session association information is used to associate the session transmission paths of the multiple contract data.

[0084] In the technical solution provided in this application, a conventional session establishment process is performed for the session establishment request sent by the UE, but an agent is selected for the UE to aggregate the sessions of multiple UEs and establish a multi-path transmission connection on top of the session.

[0085] The multiple subscription data included in the multi-connection device are associated with each other.

[0086] In some possible implementations, the multi-connection device may be a dual-connection device. The multi-connection device includes a first subscription data and a second subscription data, UE1 communicates via the first subscription data, and UE2 communicates via the second subscription data. Optionally, the multi-connection device may further include a third subscription data, a fourth subscription data, and the like, UE3 communicates via the third subscription data, and UE4 communicates via the fourth subscription data. This application does not limit the amount of subscription data included in the multi-connection device.

[0087] In this application, when a multi-connection device communicates via a first subscription, the multi-connection device may be referred to as UE1. When the multi-connection device communicates via a second subscription, the multi-connection device may be referred to as UE2, and so on.

[0088] Exemplarily, the subscription data may be SUPI or USIM. In some possible application scenarios, the subscription data may also be directly referred to as user equipment or terminal equipment, and this application does not limit the name.

[0089] It should be understood that the information of the agent may be the IP address of the agent, and may also include the ID of the agent, the type of the agent, etc.

[0090] Optionally, the agent information may be included in the second indication information, and the second indication information may be the same as the first indication information.

[0091] UE1 may send the session association information and the proxy information to UE2. In some possible implementations, since multiple subscription data of a multi-connection device are associated with each other, UE2 may also directly obtain the session association information and the proxy information of UE1.

[0092] UE2 sends a connection joining request to the proxy, and after joining the connection corresponding to the session association information, the first session and the second session share a multipath transmission connection.

[0093] In combination with the fifth aspect, in certain implementations of the fifth aspect, the session association information includes a session public IP address and / or a connection ID, the session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0094] Exemplarily, the multipath transmission connection may be a connection established through MPTCP or MPQUIC functions.

[0095] When the multipath transport connection is an MPTCP connection, the session association information may be a session public IP address; when the multipath transport connection is an MPQUIC connection, the session association information may be a session public IP address and / or a connection ID.

[0096] The connection joining request sent by UE2 includes session association information, so the proxy knows which connection UE2 wants to associate with. Subsequently, UE2 and UE1 can send data using the same public IP address.

[0097] In the technical solution provided in this application, a conventional session establishment process is performed for the session establishment request sent by the UE, but an agent is selected for the UE to aggregate the sessions of multiple UEs and establish a multi-path transmission connection on top of the session.

[0098] In combination with the fifth aspect, in some implementations of the fifth aspect, the method further includes: receiving response information from the proxy, where the response information is used to indicate that joining the connection corresponding to the session association information is successful.

[0099] In combination with the fifth aspect, in certain implementations of the fifth aspect, the second session establishment request also includes a session identifier of a first session, the first session is a session established by the multi-connection device using first contract data, and the first contract data is one of the multiple contract data other than the second contract data.

[0100] In some possible implementations, the session identifier of the multi-connection session may be an ID assigned by UE1 to the multi-connection session, and the SMF may associate the assigned ID with the ID of UE1. Optionally, to avoid conflicts between the IDs of the sessions established by UE1 and UE2, the session identifier of the multi-connection session may also include the ID of UE1. The ID of UE1 may be 5G-GUTI, 5G-S-TMSI, or SUPI. The specific format of the session identifier should not be construed as a limitation to this application.

[0101] UE1 may send the session identifier of the first session to UE2. In some possible implementations, since multiple subscription data of the multi-connection device are associated with each other, UE2 may also directly obtain the session identifier of the first session of UE1.

[0102] In some possible implementations, if UE2 can obtain the session identifier of UE1's first session, it can send the second indication information and the session identifier to the SMF, that is, the second session establishment request can include the second indication information and the session identifier, and the SMF can assign the same agent as UE1 and the UPF that can be connected to the agent to UE2 based on the context corresponding to the session identifier.

[0103] In the technical solution provided in this application, the second session establishment request sent by UE2 to SMF can also include the session identifier of the first session. SMF can assign the same agent as UE1 and a UPF that can be connected to the agent to UE2 based on the context corresponding to the session identifier.

[0104] In a sixth aspect, a communication method is provided, which is applied to SMF, and the method includes: receiving a first session establishment request sent by a multi-connection device using first contract data, the first session establishment request including first indication information, the first indication information being used to indicate the assignment of an agent to the multi-connection device, the agent being used to establish a multi-path connection for the multi-connection device, the multi-connection device including multiple contract data, the multiple contract data including the first contract data; sending a first session establishment acceptance message, the first session establishment acceptance message including information of the agent, the first session establishment acceptance message being used to indicate that the establishment of the first session is complete, and the first session is a session established by the multi-connection device using the first contract data.

[0105] In the technical solution provided in this application, the SMF performs a regular session establishment process for the session establishment request sent by the UE, but selects an agent for the UE to aggregate the sessions of multiple UEs and establish a multi-path transmission connection on top of the session.

[0106] The multiple subscription data included in the multi-connection device are associated with each other.

[0107] In some possible implementations, the multi-connection device may be a dual-connection device. The multi-connection device includes a first subscription data and a second subscription data, UE1 communicates via the first subscription data, and UE2 communicates via the second subscription data. Optionally, the multi-connection device may further include a third subscription data, a fourth subscription data, and the like, UE3 communicates via the third subscription data, and UE4 communicates via the fourth subscription data. This application does not limit the amount of subscription data included in the multi-connection device.

[0108] In this application, when a multi-connection device communicates via a first subscription, the multi-connection device may be referred to as UE1. When the multi-connection device communicates via a second subscription, the multi-connection device may be referred to as UE2, and so on.

[0109] Exemplarily, the subscription data may be SUPI or USIM. In some possible application scenarios, the subscription data may also be directly referred to as user equipment or terminal equipment, and this application does not limit the name.

[0110] After receiving the first session establishment request, the SMF selects a proxy that can serve as a session anchor point and a UPF that can connect to the anchor point for UE1.

[0111] It should be understood that the information of the agent may be the IP address of the agent, and may also include the ID of the agent, the type of the agent, etc.

[0112] The first session is a PDU session established by the multi-connection device using the first subscription data. The multi-connection device can also use other subscription data to establish other PDU sessions, which are aggregated together through the proxy and share a multi-path transmission connection.

[0113] In combination with the sixth aspect, in some implementations of the sixth aspect, the first session establishment request further includes a session identifier of the first session.

[0114] In some possible implementations, the session identifier of the multi-connection session may be an ID assigned by UE1 to the multi-connection session, and the SMF may associate the assigned ID with the ID of UE1. Optionally, to avoid conflicts between the IDs of the sessions established by UE1 and UE2, the session identifier of the multi-connection session may also include the ID of UE1. The ID of UE1 may be 5G-GUTI, 5G-S-TMSI, or SUPI. The specific format of the session identifier should not be construed as a limitation to this application.

[0115] The SMF receives the first session establishment request and can check whether there is a corresponding context for the session identifier or whether there is agent information in the context. If not, it indicates that it is a brand new session. It selects a proxy that can serve as a session anchor point and a UPF that can connect to the anchor point.

[0116] In the technical solution provided by this application, the first session establishment request sent by UE1 to the SMF may also include a session identifier of the first session. Subsequently, other UEs associated with UE1 may send the session identifier of the first session to the SMF. The SMF may allocate the same proxy and a UPF that can connect to the proxy to the other UEs based on the context corresponding to the session identifier.

[0117] In combination with the sixth aspect, in some implementations of the sixth aspect, the method further includes: receiving a second session establishment request sent by the multi-connection device using second contract data, the second session establishment request including second indication information and information of the agent, the second indication information being used to indicate that the agent is assigned to the multi-connection device, the second contract data being one of the multiple contract data other than the first contract data; sending a second session establishment acceptance message, the second session establishment acceptance message being used to indicate that the establishment of the second session is complete, and the second session is a session established by the multi-connection device using the second contract data.

[0118] Optionally, the agent information may be included in the second indication information, and the second indication information may be the same as the first indication information.

[0119] The SMF can select a UPF that can connect to the proxy for UE2 based on the proxy information.

[0120] UE1 may send the session association information and the proxy information to UE2. In some possible implementations, since multiple subscription data of a multi-connection device are associated with each other, UE2 may also directly obtain the session association information of UE1 and the session identifier of the multi-connection session.

[0121] In some possible implementations, if UE2 can obtain the session identifier of UE1's first session, it can send the second indication information and the session identifier to the SMF, that is, the second session establishment request can include the second indication information and the session identifier, and the SMF can assign the same agent as UE1 and the UPF that can be connected to the agent to UE2 based on the context corresponding to the session identifier.

[0122] In the technical solution provided in this application, SMF processes the session establishment requests sent by multiple UEs as separate PDU sessions, but selects the same agent for multiple UEs to aggregate the sessions of multiple UEs.

[0123] In combination with the sixth aspect, in certain implementations of the sixth aspect, the method further includes: sending an agent request message, wherein the agent request message is used to request a first network element to allocate the agent to the multi-connection device, and the first network element is used to manage the session of the multi-connection device; and receiving an agent allocation message, wherein the agent allocation message includes information about the agent.

[0124] In some possible implementations, when selecting a proxy that can serve as a session anchor, the selection can be made by a network element other than the SMF. Exemplarily, this network element is a first network element, which can manage the session as a whole and ensure that multiple UEs select the same proxy. Exemplarily, this network element is a DualSteer SMF (DS-SMF). When the SMF receives a request to allocate a proxy, it sends a proxy request message to the DS-SMF and then selects a UPF that can connect to the proxy based on the obtained proxy information.

[0125] In the technical solution provided in the present application, the SMF can select a same proxy for multiple UEs through other network elements in response to session establishment requests sent by multiple UEs, so as to aggregate the sessions of multiple UEs.

[0126] In the seventh aspect, a communication device is provided, comprising various modules or units for executing the method in the first aspect or any possible implementation of the first aspect, or comprising various modules or units for executing the method in the second aspect or any possible implementation of the second aspect, or comprising various modules or units for executing the method in the fourth aspect or any possible implementation of the fourth aspect, or comprising various modules or units for executing the method in the fifth aspect or any possible implementation of the fifth aspect.

[0127] In an eighth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the method in the first aspect or any possible implementation of the first aspect, or to implement the method in the second aspect or any possible implementation of the second aspect, or to implement the method in the fourth aspect or any possible implementation of the fourth aspect, or to implement the method in the fifth aspect or any possible implementation of the fifth aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface to control the communication interface to implement communication with other devices.

[0128] In one implementation, the communication apparatus is a multi-connection device. When the communication apparatus is a multi-connection device, the communication interface may be a transceiver, or an input / output interface.

[0129] In another implementation, the communication device is a chip configured in a multi-connection device. When the communication device is a chip configured in a multi-connection device, the communication interface may be an input / output interface.

[0130] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0131] In the ninth aspect, a communication device is provided, comprising various modules or units for executing the method in the third aspect or any possible implementation of the third aspect, or comprising various modules or units for executing the method in the sixth aspect or any possible implementation of the sixth aspect.

[0132] In a tenth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be configured to execute instructions in the memory to implement the method of the third aspect or any possible implementation of the third aspect, or to implement the method of the sixth aspect or any possible implementation of the sixth aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface and controlling the communication interface to enable communication with other devices.

[0133] In one implementation, the communication device is an SMF network element. When the communication device is an SMF network element, the communication interface may be a transceiver, or an input / output interface.

[0134] In another implementation, the communication device is a chip configured in an SMF network element. When the communication device is a chip configured in an SMF network element, the communication interface may be an input / output interface.

[0135] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0136] In the eleventh aspect, a communication system is provided, comprising: a multi-connection device and an SMF network element; the multi-connection device executes a method as described in any one of the first aspect to the second aspect and any one of the possible implementations of the first aspect to the second aspect, and the SMF network element executes a method as described in any one of the third aspect and any one of the possible implementations of the third aspect.

[0137] In the twelfth aspect, a communication system is provided, including: a multi-connection device and an SMF network element; the multi-connection device executes a method as described in any one of the fourth to fifth aspects and any possible implementation of the fourth to fifth aspects, and the SMF network element executes a method as described in any one of the sixth aspect and any possible implementation of the sixth aspect.

[0138] In a thirteenth aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and send a signal through the output circuit, so that the processor executes the method of aspects 1 to 6 and any possible implementation of aspects 1 to 6.

[0139] In a specific implementation, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter. The input circuit and the output circuit may be the same circuit, which functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0140] In a fourteenth aspect, a processing device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory and receive signals via a receiver and transmit signals via a transmitter to execute the method of aspects 1 to 6 and any possible implementation of aspects 1 to 6.

[0141] Optionally, there are one or more processors and one or more memories.

[0142] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0143] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0144] It should be understood that related data interaction processes, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of receiving input capability information from the processor. Specifically, the output data of the processing can be output to the transmitter, and the input data received by the processor can come from the receiver. The transmitter and receiver can be collectively referred to as a transceiver.

[0145] The processing device in the above-mentioned fourteenth aspect can be a chip. The processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor or can be located outside the processor and exist independently.

[0146] In the fifteenth aspect, a computer-readable storage medium is provided, storing a computer program or instruction, which is used to implement the method described in the first to sixth aspects, and any possible implementation of the first to sixth aspects.

[0147] In the sixteenth aspect, a computer program product is provided, which, when run on a computer, enables the computer to execute the method described in the first to sixth aspects, and any possible implementation of the first to sixth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0148] FIG1 is a schematic diagram of a dual-connection device provided in an embodiment of the present application.

[0149] Figure 2 is a schematic diagram of the ATSSS architecture.

[0150] Figure 3 is a schematic diagram of the ATSSS architecture.

[0151] FIG4 is a schematic diagram of an application scenario of a multi-access session.

[0152] FIG5 is an exemplary flowchart of a communication method provided in an embodiment of the present application.

[0153] FIG6 is an exemplary flowchart of another communication method provided in an embodiment of the present application.

[0154] Figure 7 is a schematic diagram of an application scenario in which two UEs select the same UPF to establish a session, provided by an embodiment of the present application.

[0155] Figure 8 is a schematic diagram of an application scenario in which two UEs select different UPFs to establish a session, provided by an embodiment of the present application.

[0156] FIG9 is an exemplary flowchart of UE1-related operations in a communication method provided in an embodiment of the present application.

[0157] FIG10 is an exemplary flowchart of UE2-related operations in a communication method provided in an embodiment of the present application.

[0158] FIG11 is an exemplary flowchart of UE1-related operations in another communication method provided in an embodiment of the present application.

[0159] FIG12 is an exemplary flowchart of UE2-related operations in another communication method provided in an embodiment of the present application.

[0160] FIG13 is an exemplary flowchart of UE1-related operations in another communication method provided in an embodiment of the present application.

[0161] FIG14 is an exemplary flowchart of UE2-related operations in another communication method provided in an embodiment of the present application.

[0162] FIG15 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0163] FIG16 is a schematic block diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0164] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making any creative efforts should fall within the scope of protection of this application.

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

[0166] The business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0167] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: including the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0168] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fourth generation (4G), fifth generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area networks (WLAN) systems, satellite communication systems, future communication systems, such as sixth generation (6G) mobile communication systems, or a fusion system of multiple systems. The technical solutions provided in the present application can also be applied to device to device (D2D) communication, vehicle to everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0169] The above-mentioned communication systems applicable to the present application are merely examples, and the communication systems applicable to the present application are not limited thereto. A unified description is given here, and no further details are given below. In order to facilitate understanding of the technical solution of the present application, the following briefly describes concepts or related technologies related to the present application.

[0170] 1. Terminal equipment: This term may be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. A terminal device can be a device that provides voice / data connectivity to a user, such as a handheld device or vehicle-mounted device with wireless connectivity. At present, some examples of terminals may include: mobile phones, tablet computers, computers with wireless transceiver functions (such as laptops, PDAs, etc.), mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (PLMNs). terminal equipment in network, PLMN, etc.

[0171] Furthermore, terminal devices can also be end devices in the Internet of Things (IoT) system. IoT is a crucial component of future information technology development. Its primary technical feature is connecting objects to the Internet through communications technology, thereby enabling intelligent networks that interconnect humans and machines, and objects and things. IoT technology, for example, utilizes narrowband (NB) technology to achieve massive connectivity, deep coverage, and power-saving terminals.

[0172] In addition, terminal devices can also include sensors such as smart printers, train detectors, and gas stations. Their main functions include collecting data (part of the terminal devices), receiving control information and downlink data from network devices, and sending electromagnetic waves to transmit uplink data to network devices.

[0173] It should be understood that the terminal device can be any device that can access the network. The terminal device and the access network device can communicate with each other using a certain air interface technology.

[0174] 2. Access network (AN): The access network can provide network access functions for authorized users in a specific area. Terminal devices can access the core network using access networks with different access technologies, for example: using non-3GPP technology and 3GPP technology to access the core network. As an example and not a limitation, access technologies may include NR, Evolved Universal Mobile Telecommunication System (UMTS) Terrestrial Radio Access Network (E-UTRAN), Multefire, 3GPP access technology, non-3GPP access technology, 4G cellular access technology, 5G cellular access technology, trusted or untrusted wireless fidelity (WiFi) access technology, fixed-line or wired access technology, etc. There is no limitation on this.

[0175] Among them, the access network using non-3GPP technology may include, but is not limited to: WiFi network, WLAN, MulteFire network, wired network (for example: wireless and wireline convergence (WWC) network), or home base station network. Correspondingly, the access network equipment using non-3GPP technology may include, for example: access point (AP), trusted WLAN interworking function (TWIF) network element, trusted non-3GPP gateway function (TNGF), wireline access gateway function (W-AGF), access gateway function (AGF), broadband network gateway (BNG), fixed-mobile interworking function (FMIF), non-3GPP interworking function (N3IWF), etc.

[0176] Access networks using 3GPP technologies may include, but are not limited to, LTE networks, NR networks, 5G networks, or subsequently evolved mobile communication networks. Correspondingly, access network equipment using 3GPP technologies may include, for example, radio access network (RAN) equipment, g-NodeB, e-NodeB, and home-NodeB.

[0177] The access network (RAN) is a network that implements access network functions based on wireless communication technologies. The RAN is responsible for radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. It provides access services to terminal devices and forwards control signals and user data between them and the core network.

[0178] The wireless access network equipment may include, for example, but is not limited to: a macro base station, a micro base station (also known as a small station), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), an AP in a WiFi system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc. It can also be a gNB or a transmission point (TRP or TP) in a 5G (e.g., NR) system, one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), or a base station in a next-generation communication 6G system. The embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network equipment.

[0179] The access network can provide services for the cell. The terminal device can communicate with the cell through the transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the access network equipment.

[0180] 3. User plane function (UPF) network element: The UPF network element is responsible for forwarding and receiving user data in the terminal device. The UPF network element can receive user data from the data network (DN) and transmit it to the terminal device through the access network device. The UPF network element can also receive user data from the terminal device through the access network device and forward it to the data network. The transmission resources and scheduling functions that provide services to the terminal device in the UPF network element are managed and controlled by the SMF network element. UPF network functions include data packet routing and transmission, data packet detection, service usage reporting, quality of service (QoS) processing, legal monitoring, uplink data packet detection, downlink data packet storage and other user-plane related functions. In future communication systems, the user plane function network element can still be a UPF network element, or it can have other names, which are not limited in this application.

[0181] 4. Access and Mobility Management Function (AMF) Network Element: A control plane network function provided by the operator network, responsible for access control and mobility management of terminal devices accessing the operator network. For example, this includes functions such as mobility status management, allocating temporary user identities, authentication, and authorization. In future communication systems, the access management network element may still be the AMF network element, or it may have other names, which are not limited in this application.

[0182] 5. Session management function (SMF) network element: A control plane network function provided by the operator network, responsible for managing the protocol data unit (PDU) session of the terminal device (including session establishment, modification and release), and used for the selection and reselection of user plane function network elements, IP address allocation of terminal devices, QoS control, etc. Among them, a PDU session is a channel for transmitting PDUs, and the terminal device transmits PDUs to and from the DN through the PDU session. The SMF network function is responsible for establishing, maintaining and deleting PDU sessions. The SMF network function includes session management (such as session establishment, modification and release, including tunnel maintenance between the user plane function UPF and the (R)AN), selection and control of the UPF network function, service and session continuity (SSC) mode selection, roaming and other session-related functions. In future communication systems, the session management function network element can still be an SMF network element, or it can have other names, which are not limited in this application.

[0183] 6. Unified Data Management (UDM): A control plane function provided by the operator, responsible for storing information such as the subscriber permanent identifier (SUPI) of the subscriber in the operator network, the generic public subscription identifier (GPSI) of the subscriber, and credentials. The SUPI will be encrypted during transmission, and the encrypted SUPI is called a hidden subscriber subscription identifier (SUCI). The information stored by the UDM network function can be used for authentication and authorization of terminal devices to access the operator network. The subscribers of the above-mentioned operator network can specifically be users who use services provided by the operator network, such as users who use operator SIM cards. The credentials of the above-mentioned subscribers can be a long-term key stored in the mobile phone chip or a small file stored based on information related to the mobile phone chip encryption, which is used for authentication and / or authorization. It should be noted that the permanent identifier, credentials, security context, authentication data, and token are equivalent to information related to verification / authentication and authorization. In future communication systems, the unified data management function network element can still be a UDM network element, or it can have other names, which are not limited in this application.

[0184] 7. Data network (DN): A network used to provide data services to users, such as the Internet, third-party service networks, and IP Multimedia Service (IMS) networks.

[0185] 8. Traffic Switching: Traffic switching is the process of switching a session from one path to another in multi-path transmission based on changes in network conditions or policies. When network conditions change, such as congestion or instability on a particular path, session switching can redirect data traffic from the affected path to an available path. This maintains session continuity and stability while optimizing data transmission performance and reliability.

[0186] 9. Traffic Steering: Session steering is the process of distributing data traffic to different paths or sub-flows based on specific policies. Unlike session switching, session steering distributes data traffic to multiple paths during session establishment or during an ongoing process. Session steering enables load balancing, optimized bandwidth utilization, and efficient use of network resources. Specific traffic steering policies can be adjusted based on factors such as path characteristics, network load, and latency to achieve optimal data transmission performance.

[0187] FIG1 is a schematic diagram of a dual-connection device provided in an embodiment of the present application.

[0188] The concept of dual-steer device was introduced in the R19 standard discussion. A dual-steer device can be a terminal device containing two contract data, or a dual-steer device can include two independent UEs, and the contract data of these two UEs will be stored in a corresponding association relationship in the network. The contract data of the two UEs belongs to the same operator.

[0189] The dual-connection device 100 includes a first subscription data and a second subscription data. When the dual-connection device 100 communicates through the first subscription data, the dual-connection device 100 can be called UE1. When the dual-connection device 100 communicates through the second subscription data, the dual-connection device 100 can be called UE2.

[0190] Exemplarily, the subscription data (first subscription data and second subscription data) may be a subscriber permanent identifier (SUPI) or a universal subscriber identity module (USIM). In some possible application scenarios, the subscription data may also be directly referred to as a user device or terminal device, and this application does not limit the name.

[0191] The dual-connectivity device 100 includes UE1 and UE2. The specific form of the dual-connectivity device 100 is not currently limited. For example, the device can be a UE with two subscriber identity modules (SIMs) and can implement dual-SIM dual-communication. That is, the two SIM cards can simultaneously send and receive data, such as playing a game on one card while making a voice call on the other. The dual-connectivity device 100 can also be two completely independent UEs, which are encapsulated in the same device or connected together by some other means.

[0192] Figures 2 and 3 are schematic diagrams of the ATSSS architecture.

[0193] The UE and UPF have multipath transmission control protocol (MPTCP) function, multipath quick user datagram protocol internet connections (MPQUIC) function, ATSSS-low-layer (ATSSS-LL) function and performance measurement function (PMF).

[0194] The network elements in Figures 2 and 3 can communicate with each other via the interfaces shown in the figures. Some interfaces can be implemented as service-oriented interfaces. The UE and AMF network elements can interact via the N1 interface. The interaction messages can be called N1 messages, for example. The RAN and AMF network elements can interact via the N2 interface. The N2 interface can be used to send non-access stratum (NAS) messages. The RAN and UPF can interact via the N3 interface. The N3 interface can be used to transmit user plane data, etc. The SMF network element and UPF can interact via the N4 interface. The N4 interface can be used to transmit information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages. The UPF and DN can interact via the N6 interface. The N6 interface can be used to transmit user plane data, etc. The PCF and SMF network elements can interact via the N7 interface. The N7 interface can be used to issue protocol data unit (PDU) session granularity and service data flow granularity control policies, etc. The N9 interface is an interface between UPFs, such as the interface between the home-user plane function (H-UPF) connected to the DN and the visited-user plane function (V-UPF) connected to the RAN, and is used to transfer user plane data between UPFs. The SMF network element and the AMF network element can interact through the N11 interface. The N11 interface can be used to transfer PDU session tunnel information between the RAN and UPF, transfer control messages sent to the UE, transfer radio resource control information sent to the RAN, etc. The N16 interface is an interface between SMFs, such as the interface between the visited-session management function (V-SMF) and the home-session management function (H-SMF). The relationship between other interfaces and each network element is shown in Figures 2 and 3. For the sake of brevity, they are not described in detail here.

[0195] Existing standards define access traffic steering, switching, and splitting (ATSS) features, allowing user equipment (UE) to access the core network through both a 3rd Generation Partnership Project (3GPP) connection and a non-3GPP connection to obtain services. When the UE is not within the coverage of its home public land mobile network (HPLMN), it can access a visited public land mobile network (VPLMN) through 3GPP and simultaneously access the HPLMN through a non-3GPP connection. After the UE accesses the network through two different access types, it can establish a multi-access protocol data unit (MA PDU) session to obtain services.

[0196] As shown in Figure 2, when the UE accesses the same public land mobile network (PLMN), since the AMF selected by 3GPP and non-3GPP is the same, the UE can establish an MA PDU session on both the 3GPP and non-3GPP sides by sending a session establishment request.

[0197] As shown in Figure 3, when the UE accesses two different networks at the same time, the UE needs to initiate the session establishment process on both sides when establishing a MAPDU session, and use the same PDU session ID to indicate that it is the same session.

[0198] The MA PDU session is anchored at the UPF, and specific rules issued by the network determine how the session traffic is split. When a UE accesses two different PLMNs, the session is anchored at the UPF of the HPLMN. Therefore, the VPLMN session is based on a hierarchical routing (HR) architecture.

[0199] FIG4 is a schematic diagram of an application scenario of a multi-access session.

[0200] A multi-access PDU (MA PDU) session allows a UE to establish and maintain sessions simultaneously across multiple access networks. With MA PDU sessions, the UE can dynamically select and switch access networks based on varying network conditions and requirements to achieve optimal network connectivity and performance.

[0201] In ATSSS, when the UE uses the MPTCP function to establish an MA PDU session, the UE's MPTCP function can communicate with the MPTCP proxy function in the UPF through the user plane of 3GPP or non-3GPP access. The MPTCP function can be enabled when the UE provides "MPTCP capability" during the PDU session establishment process. If the UE supports the MPTCP function and the network agrees to enable the MPTCP function for the MA PDU session, the network will allocate an IP address / prefix to the UE for the MA PDU session, as well as two additional IP addresses / prefixes, called "MPTCP specific link multipath" addresses / prefixes, which are associated with 3GPP and non-3GPP access respectively. For example, the IP address / prefix allocated by the network to the UE for associating with 3GPP can be IP@2, and the IP address / prefix for associating with non-3GPP can be IP@1. The network can send MPTCP proxy information to the UE, including the IP address, port number and MPTCP proxy type.

[0202] Similarly, when the UE uses the MPQUIC function to establish an MA PDU session, the UE's MPQUIC function can communicate with the MPQUIC proxy function in the UPF through the user plane of 3GPP or non-3GPP access. The MPQUIC function can be enabled when the UE provides "MPQUIC capability" during the PDU session establishment process. If the UE supports the MPQUIC function and the network agrees to enable the MPQUIC function for the MA PDU session, the network will allocate an IP address / prefix to the UE for the MA PDU session, as well as two additional IP addresses / prefixes, called "MPQUIC specific link multipath" addresses / prefixes, which are associated with 3GPP and non-3GPP access respectively. For example, the IP address / prefix allocated by the network to the UE for associating with 3GPP can be IP@5, and the IP address / prefix for associating with non-3GPP can be IP@4. The network can send MPQUIC proxy information to the UE, including the IP address, port number and MPQUIC proxy type.

[0203] The existing MA PDU session allocates IP addresses corresponding to different paths and MA PDU session IP addresses for different access paths of a single UE, enabling the establishment of an MPTCP / MPQUIC connection with the MPTCP / MPQUIC proxy UPF. When the UE requests to establish a session, the network allocates three IP addresses to the UE, one of which is the IP address of the MA PDU session, and the other two addresses are the sub-stream IP addresses of the 3GPP connection and the non-3GPP connection, respectively. The two connections in the prior art belong to the same UE. When a dual-connection device establishes a dual-connection session based on MPTCP / MPQUIC, the sessions of the two UEs have independent IPs. When the session is switched, for example, switching from UE1's session to UE2's session is equivalent to rebuilding the session, which will cause a brief interruption of the session and affect the user experience.

[0204] FIG5 is an exemplary flowchart of a communication method provided in an embodiment of the present application.

[0205] This communication method is applied to a multi-connection device, which includes multiple subscriptions, including a first subscription, a second subscription, a third subscription, and so on. The multiple subscriptions included in the multi-connection device are associated with each other. When the multi-connection device communicates using the first subscription, the multi-connection device may be referred to as UE1. When the multi-connection device communicates using the second subscription, the multi-connection device may be referred to as UE2, and so on.

[0206] 510. UE1 sends a first session establishment request to the SMF.

[0207] The first session establishment request includes first indication information and a session identifier of the multi-connection session, wherein the first indication information is used to indicate the establishment of the multi-connection session. Optionally, the session identifier of the dual-connection session may also be included in the first indication information.

[0208] In some possible implementations, the session identifier of the multi-connection session may be an ID assigned by UE1 to the multi-connection session, and the SMF may associate the assigned ID with the ID of UE1. Optionally, in order to avoid conflicts between the IDs of the sessions established by UE1 and UE2, the session identifier of the multi-connection session may also include the ID of UE1. The ID of UE1 may be a 5G-globally unique temporary UE identifier (5G-GUTI) in the 5G system, a temporary mobile subscription identifier (5G-S-TMSI) in the 5G system, or a SUPI. The specific format of the session identifier of the dual-connection session should not be understood as a limitation to the present application.

[0209] 520. UE1 receives a first session establishment accept message sent by the SMF.

[0210] The first session establishment acceptance message includes session association information and a first IP address. The session association information is used to associate session transmission paths for multiple contract data, and the first IP address includes the IP address assigned by the SMF to the first session, which is a subsession of the multi-connection session established using the first contract data.

[0211] The first session is a sub-session of a multi-connection session established by the multi-connection device using the first subscription data. The multi-connection device may also use other subscription data to establish other sub-sessions of the multi-connection session. These sub-sessions together constitute the multi-connection session.

[0212] The session association information includes a session public IP address and / or a connection ID, wherein the session public IP address is a public IP address for establishing a multi-path transmission connection using multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0213] Exemplarily, the multipath transport connection may be a connection established via MPTCP or MPQUIC functionality. When the multipath transport connection is an MPTCP connection, the session association information may be the session public IP address; when the multipath transport connection is an MPQUIC connection, the session association information may be the session public IP address and / or connection ID.

[0214] After the session establishment of the multi-connection device is completed, the multi-connection device can perform data transmission with the application server through the session association information and the allocated IP address, wherein the first session can use the first IP address for data transmission.

[0215] 530. UE1 sends the session identifier and session association information to UE2.

[0216] UE1 may send the session association information and the session identifier of the multi-connection session to UE2. In some possible implementations, since multiple subscription data of a multi-connection device are associated with each other, UE2 may also directly obtain the session association information and the session identifier of the multi-connection session of UE1.

[0217] 540. UE2 sends a second session establishment request to the SMF.

[0218] The second session establishment request includes second indication information and the session identifier of the multi-connection session in step 510 , where the second indication information is used to instruct the establishment of the multi-connection session.

[0219] Optionally, the session identifier of the dual-connection session may also be included in the second indication information. The second indication information may be the same as the first indication information.

[0220] 550. UE2 receives a second session establishment acceptance message sent by the SMF.

[0221] The second session establishment acceptance message includes a second IP address, where the second IP address includes an IP address allocated by the SMF to the second session. The second session is a sub-session of the multi-connection session established using the second subscription data.

[0222] In the case that the multi-connection device is a dual-connection device, the first session and the second session together constitute the multi-connection session.

[0223] It should be understood that the session association between UE1 and UE2 in the above embodiment is only an example. If there are sessions established by multi-connected devices through other contract data, such as sessions established by UE3, UE4, etc., they can also be associated with the sessions of UE1 and UE2 through methods similar to those performed by UE2. This application will not repeat them, and the number of associated sessions should not be understood as a limitation on this application.

[0224] In the technical solution provided by the present application, sub-sessions established by multi-connected devices through different contract data can be associated together through session association information, and each sub-session is assigned a different IP address to jointly complete the transmission of the session.

[0225] FIG6 is an exemplary flowchart of another communication method provided in an embodiment of the present application.

[0226] This communication method is applied to a multi-connection device, which includes multiple subscriptions, including a first subscription, a second subscription, a third subscription, and so on. The multiple subscriptions included in the multi-connection device are associated with each other. When the multi-connection device communicates using the first subscription, the multi-connection device may be referred to as UE1. When the multi-connection device communicates using the second subscription, the multi-connection device may be referred to as UE2, and so on.

[0227] 610. UE1 sends a first session establishment request to SMF1.

[0228] The first session establishment request includes first indication information, where the first indication information is used to instruct allocation of an agent for the multi-connection device, where the agent is used to establish a multi-path connection for the multi-connection device.

[0229] 620. UE1 receives a first session establishment accept message sent by SMF1.

[0230] After receiving the first session establishment request, SMF1 selects a proxy that can serve as a session anchor point and a UPF that can connect to the anchor point for UE1.

[0231] The first session establishment accept message includes the proxy information. The first session establishment accept message is used to indicate that the establishment of the first session is completed, and the first session is a session established by the multi-connection device using the first subscription data.

[0232] It should be understood that the information of the agent may be the IP address of the agent, and may also include the ID of the agent, the type of the agent, etc.

[0233] The first session is a PDU session established by the multi-connection device using the first subscription data. The multi-connection device can also use other subscription data to establish other PDU sessions, which are aggregated together through the proxy and share a multi-path transmission connection.

[0234] 630. UE1 sends a connection establishment request to the proxy.

[0235] UE1 may send an MPTCP / MPQUIC connection establishment request to the proxy according to the proxy's IP address. In one possible implementation, UE1 may send an MP_CAPABLE message to the proxy to trigger the establishment of an MPTCP connection.

[0236] 640. UE1 receives a connection establishment acceptance message sent by the proxy.

[0237] The connection establishment accept message includes session association information, where the session association information is used to associate session transmission paths of multiple contract data.

[0238] The session association information includes a session public IP address and / or a connection ID, wherein the session public IP address is a public IP address for establishing a multi-path transmission connection using multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0239] Exemplarily, the multipath transport connection may be a connection established via MPTCP or MPQUIC functionality. When the multipath transport connection is an MPTCP connection, the session association information may be the session public IP address; when the multipath transport connection is an MPQUIC connection, the session association information may be the session public IP address and / or connection ID.

[0240] 650. UE1 sends session association information and proxy information to UE2.

[0241] UE1 may send the session association information and the proxy information to UE2. In some possible implementations, since multiple subscription data of a multi-connection device are associated with each other, UE2 may also directly obtain the session association information and the proxy information of UE1.

[0242] 660. UE2 sends a second session establishment request to SMF2.

[0243] The second session establishment request includes second indication information and information of a proxy, where the second indication information is used to indicate that a proxy is allocated to the multi-connection device, and the proxy is used to establish a multi-path connection for the multi-connection device.

[0244] Optionally, the agent information may be included in the second indication information, and the second indication information may be the same as the first indication information.

[0245] 670. UE2 receives the second session establishment accept message sent by SMF2.

[0246] SMF2 can select a UPF that can connect to the proxy for UE2 based on the proxy information.

[0247] The second session establishment accept message is used to indicate that the establishment of the second session is complete, where the second session is a session established by the multi-connection device using the second subscription data.

[0248] 680. UE2 sends a connection joining request to the proxy.

[0249] UE2 sends a connection joining request to the proxy according to the proxy information. The connection joining request includes session association information. The connection joining request is used to request to join the connection corresponding to the session association information.

[0250] It should be understood that SMF1 and SMF2 in the embodiments of the present application may be the same or different, and the present application does not impose any limitation on this.

[0251] In the technical solution provided in this application, a conventional session establishment process is performed for the session establishment request sent by the UE, but an agent is selected for the UE to aggregate the sessions of multiple UEs and establish a multi-path transmission connection on top of the session.

[0252] Exemplarily, if the multi-connection device is a dual-connection device, the first session and the second session share a multi-path transmission connection, and the multi-path transmission connection can be a connection established through MPTCP and MPQUIC functions.

[0253] It should be understood that the session association between UE1 and UE2 in the above embodiment is only an example. If there are sessions established by multi-connected devices through other contract data, such as sessions established by UE3, UE4, etc., they can also be associated with the sessions of UE1 and UE2 through methods similar to those performed by UE2. This application will not repeat them, and the number of associated sessions should not be understood as a limitation on this application.

[0254] In the following embodiments, the communication method provided by the present application is described in detail by taking the multi-connection device as a dual-connection device as an example.

[0255] Figure 7 is a schematic diagram of an application scenario in which two UEs select the same UPF to establish a session, provided by an embodiment of the present application.

[0256] Exemplarily, UE1 and UE2 can be universal subscriber identity modules (USIMs). If UE1 and UE2 select the same UPF, the UPF can act as an MPTCP / MPQUIC agent, that is, as the anchor point of the session, aggregating the PDU session of USIM1 and the PDU session of USIM2. When UE1 establishes a session, it can obtain session association information and a first IP address. The session association information can be the public IP address or connection ID of the entire session. The first IP address is the IP address of the sub-session established by UE1. When UE2 establishes a session, a path will be added. At this time, only one IP address is obtained as the IP address of the sub-session established by UE2. UE2 can reuse UE1's session association information, such as reusing the public IP address of the entire session.

[0257] Figure 8 is a schematic diagram of an application scenario in which two UEs select different UPFs to establish a session, provided by an embodiment of the present application.

[0258] If UE1 and UE2 select different UPFs, for example, UE1 selects UPF1 and UE2 selects UPF2, then SMF can additionally select an MPTCP / MPQUIC proxy that can serve as a session anchor point, and the two UEs select the same proxy.

[0259] Figure 9 is an exemplary flow chart of UE1-related operations in a communication method provided by an embodiment of the present application. In this application scenario, UE1 and UE2 can select the same UPF to establish a session.

[0260] 801. UE1 sends a session establishment request to AMF1.

[0261] The session establishment request includes first indication information and a dual-connectivity session (DualSteer Session) ID. The first indication information is used to indicate to the network that a dual-connectivity (DualSteer) session needs to be established. The dual-connectivity session ID allocated by UE1 to the session may be included in the first indication information.

[0262] The dual-connection session ID can uniquely identify the session in UE1 and UE2. Exemplarily, the multi-connection session ID can be the ID assigned by UE1 for the multi-connection session, and the SMF can associate the assigned ID with the ID of UE1. Optionally, the composition of the dual-connection session ID can also be UE1's ID + UE1's assigned ID. The ID assigned by UE1 can be guaranteed to be unique in UE1 and UE2, and UE1's ID is unique within the network, so the ID can be guaranteed to be unique. This application does not limit the specific format of the dual-connection session ID. The ID of UE1 can be a 5G-globally unique temporary UE identifier (5G-GUTI) in the 5G system, a temporary mobile subscription identifier (5G-S-TMSI) in the 5G system, or SUPI. The specific format of the dual-connection session ID should not be understood as a limitation on this application.

[0263] 802. AMF1 sends a session context creation request to SMF.

[0264] The session context creation request may include the first indication information and the dual-connection session ID. The dual-connection session ID may also be included in the first indication information.

[0265] 803. The SMF receives the session context creation request sent by AMF1. The SMF sends a first response message to AMF1, where the first response message is used to confirm the creation of the session context.

[0266] When the SMF determines that the session type established by UE1 is a dual-connection session, it will check whether the session association information and / or the first IP address of the dual-connection session exists in the context. If not, it indicates that it is a brand new dual-connection session, and the SMF allocates the session association information and the first IP address to UE1. The session association information includes the session public IP address and / or the connection ID. The session public IP address is the public IP address for establishing a multi-path transmission connection, and the connection ID is used to identify the multi-path transmission connection. The first IP address is the IP address allocated by the SMF to the first session. The first session is a sub-session of the multi-connection session established by UE1. The first IP address can be represented by IP@1.

[0267] Exemplarily, the multipath transport connection may be a connection established by MPTCP or MPQUIC functionality. When the multipath transport connection is an MPTCP connection, the session association information may be the session public IP address; when the multipath transport connection is an MPQUIC connection, the session association information may be the session public IP address and / or connection ID.

[0268] 804. SMF sends an N4 session creation request to UPF to request the creation of an N4 session.

[0269] The session creation request may include IP@1 and a dual-connection session ID, or the session creation request may include IP@1 and session association information, or the session creation request may include IP@1, a dual-connection session ID, and session association information.

[0270] 805. UPF sends a second response message to SMF, where the second response message is used to indicate that the N4 session creation is completed.

[0271] The second response message includes CN resources, which are represented by CN tunnel info1 and are used by RAN1 to send uplink data to UPF.

[0272] 806. SMF sends a forwarding request to AMF1, where the forwarding request is used to instruct AMF1 to forward the N1 and N2 messages.

[0273] The forwarding request message may include session association information, IP@1, and CN tunnel info1.

[0274] 807. AMF1 sends an N2 message to RAN1. The N2 message may include session association information, IP@1, and CN tunnel info1.

[0275] 808 , RAN1 allocates AN resources to UE1, which are represented by AN tunnel info1, and forwards an N1 session establishment accept message to UE1, which includes session association information and IP@1.

[0276] 809. RAN1 sends an N2 session establishment response message to AMF1. The session establishment response message includes AN tunnel info1.

[0277] 810. AMF1 sends an N2 session establishment response message to SMF. The session establishment response message includes AN tunnel info1.

[0278] 811. SMF updates session information to UPF and sends AN tunnel info1 to UPF.

[0279] 812. UPF sends a third response message to SMF, where the third response message is used to indicate that the session information update is completed.

[0280] 813. SMF registers the session context with UDM.

[0281] After SMF receives the third response message sent by UPF, it indicates that the dual-connection session is established. SMF registers the session context with UDM, which includes the session type as a dual-connection session, the corresponding dual-connection session ID and the ID of UE1.

[0282] 814. After the SMF registers the session context with the UDM, the UDM can determine that the session type is a dual-connection session. The UDM can determine the information of the associated UE2 based on the ID of UE1.

[0283] The UDM is configured with the association information of UE1 and UE2, as well as the UE context information of UE1 and UE2. When the session type registered by the SMF is a dual-connection session, the UDM determines the corresponding UE2 information based on the association relationship stored in the UE1 subscription data, and determines the corresponding AMF2 based on the UE2 context information.

[0284] 815. UDM sends updated session information to AMF2. The updated session information includes the dual-connection session ID and the ID of the corresponding SMF.

[0285] Figure 10 is an exemplary flow chart of UE2-related operations in a communication method provided by an embodiment of the present application. Figure 10 corresponds to Figure 9. In this application scenario, UE1 and UE2 select the same UPF to establish a session.

[0286] 821 , UE1 sends the dual-connectivity session ID in step 801 and the session association information received in step 808 to UE2.

[0287] UE1 may send the session association information and the dual-connection session ID to UE2. In some possible implementations, since the two subscription data of the dual-connection device are associated with each other, UE2 may also directly obtain the session association information and the dual-connection session ID of UE1.

[0288] 822. UE2 sends a session establishment request to AMF2.

[0289] The session establishment request includes the second indication information and the dual-connection session ID obtained in step 821. The second indication information is used to indicate to the network that a dual-connection session needs to be established.

[0290] Optionally, the dual-connection session ID may also be included in the second indication information, and the second indication information may be the same as the first indication information.

[0291] 823. AMF2 has obtained the context information corresponding to the dual-connection session ID established by UE1 based on the message pushed by UDM in step 815, and can determine the SMF corresponding to the dual-connection session. Therefore, the same SMF can be selected to establish the dual-connection session.

[0292] 824. AMF2 sends a session context update request to SMF.

[0293] The session context update request may include the second indication information and the dual-connection session ID. The dual-connection session ID may also be included in the second indication information.

[0294] 825. The SMF receives the session context update request sent by AMF2. When the SMF determines that the session type established by UE2 is a dual-connection session, it checks whether the dual-connection session ID contains session association information and / or a first IP address. If so, it indicates that a session subpath needs to be added to an existing dual-connection session. The SMF then allocates a second IP address to UE2. The second IP address is the IP address allocated by the SMF for the second session, which is a subsession of the multi-connection session established by UE2. The second IP address can be represented by IP@2.

[0295] SMF sends a fourth response message to AMF2, where the fourth response message is used to determine the updated session context.

[0296] 826. SMF sends an N4 session creation request to UPF to request the creation of an N4 session.

[0297] The session creation request may include IP@2 and a dual-connection session ID, or the session creation request may include IP@2 and session association information, or the session creation request may include IP@2, session association information, and a dual-connection session ID.

[0298] 827. UPF sends a fifth response message to SMF. The second response message is used to indicate that the N4 session creation is completed.

[0299] The fifth response message includes CN resources, which are represented by CN tunnel info2 and are used by RAN2 to send uplink data to UPF.

[0300] 828. SMF sends a forwarding request to AMF2, which is used to instruct AMF2 to forward the N1 and N2 messages.

[0301] The forwarding request message includes IP@2 and CN tunnel info2.

[0302] 829. AMF2 sends an N2 message to RAN2. The N2 message includes IP@2 and CN tunnel info2.

[0303] 830 , RAN2 allocates AN resources to UE2, which are represented by AN tunnel info2, and forwards an N1 session establishment accept message to UE2, which includes IP@2.

[0304] 831. RAN2 sends an N2 session establishment response message to AMF2. The session establishment response message includes AN tunnel info2.

[0305] 832. AMF2 sends an N2 session establishment response message to SMF, where the session establishment response message includes AN tunnel info2.

[0306] 833. SMF updates the session information to UPF and sends AN tunnel info2 to UPF.

[0307] 834. UPF sends a sixth response message to SMF, where the sixth response message is used to indicate that the session information update is completed.

[0308] At this time, the session establishment of the dual-connected device is completed. The dual-connected device can transmit data with the application server through the session association information. UE1 can use IP@1 for data transmission as one of the session sub-paths, and UE2 can use IP@2 for data transmission as the other session sub-path.

[0309] In the embodiment of the present application, for the case where UE1 and UE2 select the same SMF and UPF, the logic of SMF allocating IP is optimized. First, the SMF is informed through indication information that a new type of session needs to be established. Then, the new session is identified by the dual-connection session ID. The SMF uses this information to find the corresponding UE context and determine how many IPs to allocate, thereby establishing two session sub-paths for UE1 and UE2 for the same MPTCP / MPQUIC connection, completing the information transmission of the same session.

[0310] It should be understood that RAN1 and RAN2 in Figures 9 and 10 may be the same or different, and AMF1 and AMF2 may be the same or different, and this application does not limit this.

[0311] It should be understood that the session association between the two devices UE1 and UE2 in the above embodiment is only an example. If there are other devices, such as UE3, UE4..., they can also be associated with the sessions of UE1 and UE2 through the method shown in Figure 10. This application will not repeat them, and the number of session-associated devices should not be understood as a limitation to this application.

[0312] Figure 11 is an exemplary flow chart of UE1-related operations in another communication method provided by an embodiment of the present application. In this application scenario, UE1 and UE2 can select different SMFs and UPFs to establish a session.

[0313] 901. UE1 sends a session establishment request to AMF1.

[0314] The session establishment request includes first indication information, which is used to indicate to the network that an agent needs to be allocated.

[0315] 902. AMF1 sends a session context creation request to SMF1.

[0316] The session context creation request may include the first indication information in step 901, which is used to indicate to the network that an agent needs to be allocated.

[0317] 903. SMF1 sends a first response message to AMF1. The first response message is used to confirm the creation of the session context.

[0318] 904. After receiving the session context creation request, if the request does not carry the proxy information, SMF1 selects a proxy that can serve as a session anchor point and a UPF1 that can connect to the anchor point to UE1.

[0319] In some other possible implementations, when selecting a proxy that can serve as a session anchor, the selection can be made by a network element other than SMF1, which can manage the session as a whole to ensure that the two UEs select the same proxy. Exemplarily, this network element is a dual-connection SMF (DualSteer SMF, DS-SMF), and SMF1 sends a proxy request message to DS-SMF, requesting DS-SMF to assign a proxy to the UE1. In a possible implementation scenario, the DS-SMF is configured with a proxy selection list, which stores the correspondence between the slice / data network name (DNN) and the proxy. DS-SMF1 selects a proxy for UE1 based on the proxy selection list, and then sends the proxy information to SMF1. After receiving the proxy information, SMF1 selects a UPF1 that can connect to the proxy for UE1 based on the proxy information.

[0320] 905. SMF1 sends an N4 session creation request to UPF1 to request creation of an N4 session.

[0321] 906. UPF1 sends a second response message to SMF1. The second response message is used to indicate that the N4 session creation is completed.

[0322] The second response message includes CN resources, which are represented by CN tunnel info1 and are used by RAN1 to send uplink data to UPF1.

[0323] 907. SMF1 sends a forwarding request to AMF1. The forwarding request is used to instruct AMF1 to forward the N1 and N2 messages.

[0324] If a proxy is selected in step 904, the forwarding request message may include proxy information and CN tunnel info1.

[0325] It should be understood that the information of the agent may be the IP address of the agent, and may also include the ID of the agent, the type of the agent, etc.

[0326] 908. AMF1 sends an N2 message to RAN1. The N2 message includes the proxy information and CN tunnel info1.

[0327] 909 , RAN1 allocates AN resources to UE1, which are represented by AN tunnel info1, and forwards an N1 session establishment accept message to UE1, which includes proxy information.

[0328] 910. RAN1 sends an N2 session establishment response message to AMF1. The session establishment response message includes AN tunnel info1.

[0329] 911. AMF1 sends an N2 session establishment response message to SMF1. The session establishment response message includes AN tunnel info1.

[0330] 912. SMF1 updates session information to UPF1 and sends AN tunnel info1 to UPF1.

[0331] 913. UPF1 sends a third response message to SMF1. The third response message is used to indicate that the session information update is completed.

[0332] At 914, the session establishment is complete, and UE1 sends an MPTCP / MPQUIC connection establishment request to the proxy based on the proxy information. In one possible implementation, UE1 may send an MP_CAPABLE message to the proxy to trigger the establishment of the MPTCP connection.

[0333] 915 , after completing the connection establishment, the proxy may return a fourth response message to UE1, where the fourth response message includes session association information.

[0334] The session association information includes a session public IP address and / or a connection ID. The session public IP address is a public IP address for establishing a multi-path transmission connection. The connection ID is used to identify the multi-path transmission connection.

[0335] Exemplarily, the multipath transport connection may be a connection established by MPTCP or MPQUIC functionality. When the multipath transport connection is an MPTCP connection, the session association information may be the session public IP address; when the multipath transport connection is an MPQUIC connection, the session association information may be the session public IP address and / or connection ID.

[0336] Figure 12 is an exemplary flow chart of UE2-related operations in another communication method provided by an embodiment of the present application. Figure 12 corresponds to Figure 11. In this application scenario, UE1 and UE2 can select different SMFs and UPFs to establish a session.

[0337] 921, UE1 sends proxy information and session association information to UE2.

[0338] UE1 may send the proxy information and session association information to UE2. In some possible implementations, since two subscription data of the dual-connection device are associated with each other, UE2 may also directly obtain the proxy information and session association information of UE1.

[0339] 922. UE2 sends a session establishment request to AMF2.

[0340] The session establishment request includes the second indication information and the proxy information received in step 921. The second indication information is used to indicate to the network that a proxy needs to be allocated. The proxy information may also be included in the second indication information.

[0341] 923. AMF2 sends a session context creation request to SMF2.

[0342] The session context creation request may include the second indication information and the agent information. The agent information may also be included in the second indication information.

[0343] 924. SMF2 receives the session context creation request sent by AMF2. SMF2 sends a fifth response message to AMF2, where the fifth response message is used to confirm the creation of the session context.

[0344] 925. After receiving the session context creation request, SMF2 selects a UPF2 that can connect to the proxy based on the proxy information.

[0345] In other possible implementations, when selecting a proxy that can serve as a session anchor, the selection can be made by a network element other than SMF2, which can manage the session as a whole to ensure that the two UEs select the same proxy. In this scenario, UE2 may not send proxy information to SMF2, nor does UE2 need to obtain proxy information from UE1, but SMF2 should return the selected proxy information to UE2. Exemplarily, this network element is a dual-connected SMF (DualSteer SMF, DS-SMF), and SMF2 sends a proxy request message to DS-SMF, requesting DS-SMF to assign a proxy to UE2. In a possible implementation scenario, DS-SMF is configured with a proxy selection list that stores the correspondence between slices / data network names (DNNs) and proxies. Since UE1 and UE2 use the same slice / DNN, the selected proxy is also the same. DS-SMF sends the proxy information to SMF2, and SMF2 receives the proxy information sent by DS-SMF and selects a UPF2 for UE2 that can connect to the proxy based on the obtained proxy information.

[0346] 926. SMF2 sends an N4 session creation request to UPF2 to request creation of an N4 session.

[0347] 927. UPF2 sends a sixth response message to SMF2. The sixth response message is used to indicate that the N4 session creation is completed.

[0348] The sixth response message includes CN resources, which are represented by CN tunnel info2 and are used by RAN2 to send uplink data to UPF2.

[0349] 928. SMF2 sends a forwarding request to AMF2, where the forwarding request is used to instruct AMF2 to forward the N1 and N2 messages.

[0350] The forwarding request message may include CN tunnel info2.

[0351] 929. AMF2 sends an N2 message to RAN2. The N2 message includes CN tunnel info2.

[0352] 930 , RAN2 allocates AN resources to UE2, which are represented by AN tunnel info2, and forwards an N1 session establishment accept message to UE2, where the N1 session establishment accept message is used to indicate that the session establishment of UE2 is complete.

[0353] 931. RAN2 sends an N2 session establishment response message to AMF2. The session establishment response message includes AN tunnel info2.

[0354] 932. AMF2 sends an N2 session establishment response message to SMF2. The session establishment response message includes AN tunnel info2.

[0355] 933. SMF2 updates the session information to UPF2 and sends AN tunnel info2 to UPF2.

[0356] 934. UPF2 sends a seventh response message to SMF2. The seventh response message is used to indicate that the session information update is completed.

[0357] At 935, the session is now established. UE2 sends an MPTCP / MPQUIC connection join request to the proxy based on the proxy information. This connection join request includes session association information. In one possible implementation, UE2 can send an MP_JOIN message to the proxy to trigger the addition of a connection sub-path. The session association information carried in the request message is used to identify the corresponding connection.

[0358] For example, when UE2 establishes a connection with the proxy, the connection ID is provided so that the proxy knows which connection UE2 is to be associated with and can subsequently send data using the same public IP address.

[0359] 936. After completing the connection establishment, the proxy may return an eighth response message to UE2. The eighth response message is used to indicate that the connection establishment is completed.

[0360] It should be understood that in the embodiment of the present application, step 904 for establishing a session for UE1 and step 925 for establishing a session for UE2 are distinguished by the information of the UE actively reporting the agent. In some possible implementations, the same agent selection list can also be configured for the two SMFs, which stores the correspondence between the slice / data network name (DNN) and the agent. Since UE1 and UE2 use the same slice / DNN, the agent selected by the SMF should also be the same. When using this solution, the process of UE1 establishing a session can be repeated when UE2 establishes a session, that is, UE1 does not need to send the agent information to UE2 in step 921, and UE2 does not need to report the agent information in steps 922 and 923.

[0361] In the embodiment of the present application, for the case where UE1 and UE2 select different SMFs and UPFs, the SMF is not aware of the overall session and processes the session requested by the UE as a separate PDU session. However, an agent will be selected as an anchor point for the UE to aggregate the sessions of the two UEs. Each sub-path is the PDU session of the UE, and an MPTCP / MPQUIC connection is established on top of the session.

[0362] It should be understood that RAN1 and RAN2 in Figures 11 and 12 can be the same or different, AMF1 and AMF2 can be the same or different, SMF1 and SMF2 can be the same or different, UPF1 and UPF2 can be the same or different, and this application does not impose any restrictions on this.

[0363] It should be understood that the session association between the two devices UE1 and UE2 in the above embodiment is only an example. If there are other devices, such as UE3, UE4..., they can also be associated with the sessions of UE1 and UE2 through the method shown in Figure 12. This application will not repeat them, and the number of session-associated devices should not be understood as a limitation to this application.

[0364] Figure 13 is an exemplary flow chart of UE1-related operations in another communication method provided by an embodiment of the present application. In this application scenario, UE1 and UE2 can select the same SMF and different UPFs to establish a session. UE1 and UE2 select the same SMF to better manage the UE's session.

[0365] 1001. UE1 sends a session establishment request to AMF1.

[0366] The session establishment request includes first indication information and a session ID. The first indication information is used to indicate to the network that a proxy needs to be allocated, and the session ID is used to identify the first session established by UE1.

[0367] The session ID can uniquely identify the first session in UE1 and UE2. Exemplarily, the session ID can be the ID assigned by UE1 for the session, and the SMF can associate the assigned ID with the ID of UE1. Optionally, the composition of the session ID can also be UE1's ID + UE1's assigned ID. The ID assigned by UE1 can be guaranteed to be unique in UE1 and UE2, and UE1's ID is unique within the network, so the ID can be guaranteed to be unique. This application does not limit the specific format of the session ID. The ID of UE1 can be a 5G-globally unique temporary UE identifier (5G-GUTI) in the 5G system, a temporary mobile subscription identifier (5G-S-TMSI) in the 5G system, or SUPI. The specific format of the session ID should not be understood as a limitation on this application.

[0368] 1002. AMF1 sends a session context creation request to SMF.

[0369] The session context creation request may include first indication information and a session ID. The session ID may also be included in the first indication information.

[0370] 1003. SMF sends a first response message to AMF1. The first response message is used to confirm the creation of the session context.

[0371] 1004. After receiving the session context creation request, SMF checks whether there is a corresponding context for the session ID or whether there is agent information in the context. If not, it indicates that this is a brand new session. It selects an agent that can serve as a session anchor point for UE1 and UPF1 that can connect to the anchor point.

[0372] In some other possible implementations, when selecting a proxy that can serve as a session anchor, the selection can be made by a network element other than the SMF, which can manage the session as a whole to ensure that the two UEs select the same proxy. Exemplarily, this network element is the DS-SMF, and the SMF sends a proxy request message to the DS-SMF, requesting the DS-SMF to assign a proxy to the UE1. In a possible implementation scenario, the DS-SMF is configured with a proxy selection list, which stores the correspondence between slices / DNNs and proxies. The DS-SMF selects a proxy for the UE1 based on the proxy selection list, and then sends the proxy information to the SMF. After receiving the proxy information, the SMF selects a UPF1 that can connect to the proxy for the UE1 based on the proxy information.

[0373] 1005. SMF sends an N4 session creation request to UPF1 to request the creation of an N4 session.

[0374] 1006. UPF1 sends a second response message to SMF, where the second response message is used to indicate that the N4 session creation is completed.

[0375] The second response message includes CN resources, which are represented by CN tunnel info1 and are used by RAN1 to send uplink data to UPF1.

[0376] 1007. SMF sends a forwarding request to AMF1, which is used to instruct AMF1 to forward N1 and N2 messages.

[0377] If a proxy is selected in step 1004, the forwarding request message may include proxy information and CN tunnel info1.

[0378] It should be understood that the information of the agent may be the IP address of the agent, and may also include the ID of the agent, the type of the agent, etc.

[0379] 1008. AMF1 sends an N2 message to RAN1. The N2 message includes the proxy information and CN tunnel info1.

[0380] 1009 , RAN1 allocates AN resources to UE1, which are represented by AN tunnel info1, and forwards an N1 session establishment accept message to UE1, which includes proxy information.

[0381] 1010. RAN1 sends an N2 session establishment response message to AMF1. The session establishment response message includes AN tunnel info1.

[0382] 1011. AMF1 sends an N2 session establishment response message to SMF. The session establishment response message includes AN tunnel info1.

[0383] 1012. SMF updates session information to UPF1 and sends AN tunnel info1 to UPF1.

[0384] 1013. UPF1 sends a third response message to SMF, where the third response message is used to indicate that the session information update is completed.

[0385] At 1014, the session establishment is complete, and UE1 sends an MPTCP / MPQUIC connection establishment request to the proxy based on the proxy information. In one possible implementation, UE1 may send an MP_CAPABLE message to the proxy to trigger the establishment of the MPTCP connection.

[0386] 1015 , after completing the connection establishment, the proxy may return a fourth response message to UE1, where the fourth response message may include session association information.

[0387] The session association information includes a session public IP address and / or a connection ID. The session public IP address is a public IP address for establishing a multi-path transmission connection. The connection ID is used to identify the multi-path transmission connection.

[0388] Exemplarily, the multipath transport connection may be a connection established by MPTCP or MPQUIC functionality. When the multipath transport connection is an MPTCP connection, the session association information may be the session public IP address; when the multipath transport connection is an MPQUIC connection, the session association information may be the session public IP address and / or connection ID.

[0389] Figure 14 is an exemplary flowchart of UE2-related operations in another communication method provided by an embodiment of the present application. Figure 14 corresponds to Figure 13. In this application scenario, UE1 and UE2 can select the same SMF and different UPFs to establish a session. UE1 and UE2 select the same SMF to better manage the UE's session.

[0390] 1021 , UE1 sends the session ID established in step 1001 and the session association information in step 1015 to UE2.

[0391] UE1 may send the session ID and session association information to UE2. In some possible implementations, since two subscription data of the dual-connection device are associated with each other, UE2 may also directly obtain the session ID and session association information of UE1.

[0392] 1022. UE2 sends a session establishment request to AMF2.

[0393] The session establishment request includes second indication information and a session ID. The second indication information is used to indicate to the network that an agent needs to be allocated.

[0394] Optionally, the session ID may be included in the second indication information.

[0395] 1023. AMF2 sends a session context creation request to SMF.

[0396] The session context creation request may include the second indication information and a session ID. The session ID may also be included in the second indication information.

[0397] 1024. The SMF receives the session context creation request sent by AMF2. The SMF sends a fifth response message to AMF2, where the fifth response message is used to confirm the creation of the session context.

[0398] 1025. After receiving the session context creation request, the SMF can check whether there is a corresponding context for the session ID or whether there is agent information in the context. If so, the SMF obtains the agent information from the context and selects a UPF2 for UE2 that can connect to the agent based on the agent information.

[0399] In other possible implementations, UE1 may also send the proxy information to UE2 at the same time, and UE2 sends the proxy information to SMF. SMF directly selects a UPF2 that can connect to the proxy based on the proxy information without checking the context corresponding to the session ID.

[0400] In some other possible implementations, when selecting a proxy that can serve as a session anchor, the selection can be made by a network element other than the SMF, which can manage the session as a whole to ensure that the two UEs select the same proxy. Exemplarily, this network element is the DS-SMF, and the SMF sends a proxy request message to the DS-SMF, requesting the DS-SMF to assign a proxy to the UE2. In a possible implementation scenario, the DS-SMF is configured with a proxy selection list, which stores the correspondence between slices / DNNs and proxies. Since the slices / DNNs used by UE1 and UE2 are the same, the selected proxy is also the same. The DS-SMF sends the proxy information to the SMF, and the SMF receives the proxy information sent by the DS-SMF. Based on the obtained proxy information, it selects a UPF2 for UE2 that can connect to the proxy.

[0401] 1026. SMF sends an N4 session creation request to UPF2 to request the creation of an N4 session.

[0402] 1027. UPF2 sends a sixth response message to SMF, where the sixth response message is used to indicate that the N4 session creation is completed.

[0403] The sixth response message includes CN resources, which are represented by CN tunnel info2 and are used by RAN2 to send uplink data to UPF2.

[0404] 1028. SMF sends a forwarding request to AMF2, which is used to instruct AMF2 to forward the N1 and N2 messages.

[0405] The forwarding request message may include CN tunnel info2.

[0406] If, in step 1021, UE1 does not send the proxy information to UE2, the forwarding request message may include the proxy information.

[0407] 1029. AMF2 sends an N2 message to RAN2. The N2 message includes CN tunnel info2.

[0408] If, in step 1021, UE1 does not send the proxy information to UE2, the N2 message may include the proxy information.

[0409] 1030 , RAN2 allocates AN resources to UE2, which are represented by AN tunnel info2, and forwards an N1 session establishment accept message to UE2. The N1 session establishment accept message is used to indicate that the session establishment of UE2 is complete.

[0410] 1031. RAN2 sends an N2 session establishment response message to AMF2. The session establishment response message includes AN tunnel info2.

[0411] 1032. AMF2 sends an N2 session establishment response message to SMF. The session establishment response message includes AN tunnel info2.

[0412] 1033. SMF updates the session information to UPF2 and sends AN tunnel info2 to UPF2.

[0413] 1034. UPF2 sends a seventh response message to SMF, where the seventh response message is used to indicate that the session information update is completed.

[0414] At 1035, the session is now established. UE2 sends an MPTCP / MPQUIC connection join request to the proxy based on the proxy information. This connection join request includes session association information. In one possible implementation, UE2 can send an MP_JOIN message to the proxy to trigger the addition of a connection sub-path. The session association information carried in the request message is used to identify the corresponding connection.

[0415] For example, when UE2 establishes a connection with the proxy, the connection ID may be provided so that the proxy knows which connection UE2 is to be associated with and can subsequently send data using the same public IP address.

[0416] 1036. After completing the connection establishment, the proxy may return an eighth response message to UE2. The eighth response message is used to indicate that the connection establishment is completed.

[0417] In the embodiment of the present application, when UE1 and UE2 select the same SMF and different UPFs, the SMF is unified as the control node on both UEs, but the UPF selection does not need to be the same. The SMF is unaware of the association between the two sessions of UE1 and UE2 and still executes the method of establishing separate sessions. It only selects an additional proxy as an anchor point for the UE to aggregate the sessions of the two UEs. Each connection subpath is a UE PDU session, and an MPTCP / MPQUIC connection is established on top of the session.

[0418] It should be understood that RAN1 and RAN2 in Figures 13 and 14 can be the same or different, AMF1 and AMF2 can be the same or different, UPF1 and UPF2 can be the same or different, and this application does not impose any restrictions on this.

[0419] It should be understood that the session association between the two devices UE1 and UE2 in the above embodiment is only an example. If there are other devices, such as UE3, UE4..., they can also be associated with the sessions of UE1 and UE2 through the method shown in Figure 14. This application will not repeat them, and the number of session-associated devices should not be understood as a limitation on this application.

[0420] It should be understood that the above-mentioned network architecture applied to the embodiments of the present application is only an exemplary description, and the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0421] It should also be understood that the AMF, SMF, UPF, etc. shown in Figures 5 to 14 can be understood as network elements for implementing different functions, for example, they can be combined into network slices as needed. These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, or they can be software functions running on dedicated hardware, or they can be virtualized functions instantiated on a platform (for example, a cloud platform). This application does not limit the specific form of the above network elements.

[0422] In actual deployment, network elements with different functions can be co-located. For example, the access and mobility management network element can be co-located with the session management network element; and the session management network element can be co-located with the user plane network element. When two network elements are co-located, the interaction between the two network elements provided in the embodiments of the present application becomes an internal operation of the co-located network element or can be omitted.

[0423] It should also be understood that the above naming is defined only to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 5G networks and other future networks. For example, in a 6G network, some or all of the above network elements may continue to use the terminology used in 5G, or may adopt other names.

[0424] It should also be understood that the interface names between the various network elements in the figure are merely examples, and the names of the interfaces in a specific implementation may be other names, which are not specifically limited in this application. In addition, the names of the messages (or signaling) transmitted between the various network elements are merely examples and do not constitute any limitation on the functions of the messages themselves.

[0425] The communication method provided in the embodiments of the present application is described in detail above with reference to Figures 5 to 14. Below, the communication device provided in the embodiments of the present application is described in detail with reference to Figures 15 and 16. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, reference can be made to the method embodiment above. For the sake of brevity, they will not be repeated here.

[0426] FIG15 is a schematic block diagram of a communication device according to an embodiment of the present application. As shown in FIG15 , the communication device 1100 may include a sending unit 1110 and a receiving unit 1120 .

[0427] It should be understood that the communication device 1100 may correspond to a multi-connection device, a dual-connection device, UE1, or UE2 according to the embodiments of the present application. As an exemplary description, the communication device 1100 can implement the actions, steps, or methods related to the multi-connection device, dual-connection device, UE1, or UE2 in Figures 5 to 14 of the aforementioned method embodiments.

[0428] The present application provides a communication device, including: a sending unit, used to send a first session establishment request, the first session establishment request including first indication information and a session identifier of a multi-connection session, the first indication information being used to indicate the establishment of the multi-connection session; a receiving unit, used to receive a first session establishment acceptance message, the first session establishment acceptance message including session association information and a first IP address, the session association information being used to associate session transmission paths of multiple contract data included in a multi-connection device, the first IP address including an IP address assigned by an SMF to the first session, the first session being a sub-session of the multi-connection session established using the first contract data, and the first contract data being one of the multiple contract data.

[0429] Optionally, in some implementations, the session association information includes a session public IP address and / or a connection ID, where the session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0430] The present application also provides a communication device, including: a sending unit, used to send a second session establishment request, the second session establishment request includes second indication information and a session identifier of a multi-connection session, the second indication information is used to indicate the establishment of the multi-connection session; a receiving unit, used to receive a second session establishment acceptance message, the second session establishment acceptance message includes a second IP address, the second IP address includes the IP address allocated by the SMF to the second session, and the second session is a sub-session of the multi-connection session established using the second subscription data.

[0431] Optionally, in some implementations, the session association information includes a session public IP address and / or a connection ID, where the session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0432] The present application also provides a communication device, including: a receiving unit, used to receive a first session establishment request sent by a multi-connection device using first contract data, the first session establishment request including first indication information and a session identifier of the multi-connection session, the first indication information being used to indicate the establishment of the multi-connection session, the multi-connection device including multiple contract data, the multiple contract data including the first contract data; a sending unit, used to send a first session establishment acceptance message, the first session establishment acceptance message including session association information and a first IP address, the session association information being used to associate the session transmission path of the multiple contract data, the first IP address including the IP address assigned by the SMF to the first session, and the first session being a sub-session of the multi-connection session established using the first contract data.

[0433] Optionally, in some implementations, the session association information includes a session public IP address and / or a connection ID, where the session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0434] Optionally, in some implementations, the sending unit is further used to send a third session establishment request to the UPF, where the third session establishment request is used to establish a session with the UPF, and the third session establishment request includes the session association information and the first IP address, or the third session establishment request includes the session identifier and the first IP address, and the UPF is used to aggregate sub-sessions of the multi-connection session.

[0435] Optionally, in some implementations, the receiving unit is further used to receive a second session establishment request sent by the multi-connection device using second contract data, the second session establishment request including second indication information and the session identifier, the second indication information being used to indicate the establishment of the multi-connection session, the multiple contract data including the second contract data; the sending unit is further used to send a second session establishment acceptance message, the second session establishment acceptance message including a second IP address, the second IP address including the IP address assigned by the SMF to the second session, the second session being a sub-session of the multi-connection session established using the second contract data.

[0436] Optionally, in some implementations, the sending unit is further used to send a fourth session establishment request to the UPF, where the fourth session establishment request is used to establish a session with the UPF, and the fourth session establishment request includes the session association information and the second IP address, or the fourth session establishment request includes the session identifier and the second IP address.

[0437] Optionally, in some implementations, the sending unit is further used to send a session registration message, where the session registration message is used to register the context information of the multi-connection session in a unified data management (UDM) network element, where the context information includes the type of the multi-connection session and the session identifier.

[0438] The present application also provides a communication device, including: a sending unit, used to send a first session establishment request, the first session establishment request including first indication information, the first indication information being used to indicate the allocation of an agent for a multi-connection device, the agent being used to establish a multi-path connection for the multi-connection device; a receiving unit, used to receive a first session establishment acceptance message, the first session establishment acceptance message including information of the agent, the first session establishment acceptance message being used to indicate that the establishment of the first session is complete, the first session being a session established by the multi-connection device using first subscription data; the sending unit is also used to send a connection establishment request to the agent based on the agent information; the receiving unit is also used to receive a connection establishment acceptance message sent by the agent, the connection establishment acceptance message including session association information, the session association information being used to associate session transmission paths for the multiple subscription data.

[0439] Optionally, in some implementations, the session association information includes a session public IP address and / or a connection ID, where the session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0440] Optionally, in some implementations, the first session establishment request further includes a session identifier of the first session.

[0441] The present application also provides a communication device, including: a sending unit, used to send a second session establishment request, the second session establishment request includes second indication information and agent information, the second indication information is used to indicate the allocation of an agent for a multi-connection device, and the agent is used to establish a multi-path connection for the multi-connection device; a receiving unit, used to receive a second session establishment acceptance message, the second session establishment acceptance message is used to indicate that the establishment of the second session is complete, and the second session is a session established by the multi-connection device using second subscription data; the sending unit is also used to send a connection joining request to the agent based on the agent information, the connection joining request includes session association information, the connection joining request is used to request to join the connection corresponding to the session association information, and the session association information is used to associate session transmission paths of multiple subscription data.

[0442] Optionally, in some implementations, the session association information includes a session public IP address and / or a connection ID, where the session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data, and the connection ID is used to identify the multi-path transmission connection.

[0443] Optionally, in some implementations, the receiving unit is further configured to receive response information from the proxy, where the response information is used to indicate that joining the connection corresponding to the session association information is successful.

[0444] Optionally, in some implementations, the second session establishment request also includes a session identifier of a first session, where the first session is a session established by the multi-connection device using first subscription data, and the first subscription data is one of the multiple subscription data other than the second subscription data.

[0445] The present application also provides a communication device, including: a receiving unit, configured to receive a first session establishment request sent by a multi-connection device using first subscription data, the first session establishment request including first indication information, the first indication information being used to indicate the allocation of an agent for the multi-connection device, the agent being used to establish a multi-path connection for the multi-connection device, the multi-connection device including multiple subscription data, the multiple subscription data including the first subscription data; a sending unit, configured to send a first session establishment acceptance message, the first session establishment acceptance message including information of the agent, the first session establishment acceptance message being used to indicate that the establishment of the first session is complete, the first session being a session established by the multi-connection device using the first subscription data.

[0446] Optionally, in some implementations, the first session establishment request further includes a session identifier of the first session.

[0447] Optionally, in some implementations, the receiving unit is further used to receive a second session establishment request sent by the multi-connection device using second contract data, the second session establishment request including second indication information and information of the agent, the second indication information being used to indicate assignment of the agent to the multi-connection device, the second contract data being one of the multiple contract data other than the first contract data; the sending unit is further used to send a second session establishment acceptance message, the second session establishment acceptance message being used to indicate completion of the second session establishment, the second session being a session established by the multi-connection device using the second contract data.

[0448] Optionally, in some implementations, the sending unit is further used to send an agent request message, wherein the agent request message is used to request the first network element to allocate the agent to the multi-connection device, and the first network element is used to manage the session of the multi-connection device; the receiving unit is also used to receive an agent allocation message, wherein the agent allocation message includes information about the agent.

[0449] It should be understood that when the communication device 1100 is a chip, the chip includes a transmitting unit 1110 and a receiving unit 1120. The transmitting unit 1110 and the receiving unit 1120 may be input / output circuits or communication interfaces. The transmitting unit 1110 and the receiving unit 1120 are used to implement signal transmission and reception operations of the communication device 1100.

[0450] Optionally, the communication device 1100 may further include a storage unit 1130, where the storage unit 1130 is used to store instructions.

[0451] Figure 16 is a schematic block diagram of a communication device provided in an embodiment of the present application. As shown, the communication device 1200 includes at least one processor 1210 and may also include a transceiver 1220. Optionally, the communication device 1200 also includes a memory 1230 for storing instructions. The processor 1210 is coupled to the memory 1230 and is configured to execute the instructions stored in the memory 1230 to control the transceiver 1220 to transmit and / or receive signals.

[0452] It should be understood that the processor 1210 and memory 1230 may be combined into a processing device, and the processor 1210 is used to execute the program code stored in the memory 1230 to implement the above functions. In specific implementations, the memory 1230 may also be integrated into the processor 1210 or independent of the processor 1210.

[0453] It should also be understood that the transceiver 1220 may include a receiver (or receiver) and a transmitter (or transmitter). The transceiver 1220 may further include an antenna, and the number of antennas may be one or more. The transceiver 1220 may also be a communication interface or interface circuit.

[0454] When the communication device 1200 is a chip, the chip may include a transceiver unit and a processing unit. The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. This embodiment of the application also provides a processing device including a processor and an interface. The processor may be used to execute the method described in the above method embodiment.

[0455] It should be understood that the processing device may be a chip. For example, the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0456] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0457] An embodiment of the present application further provides a computer-readable storage medium storing a computer program or instruction for implementing the method executed by the multi-connection device, dual-connection device, UE1 or UE2 in the above method embodiment.

[0458] For example, when the computer program is executed by a computer, the computer can implement the method performed by the multi-connection device, the dual-connection device, UE1 or UE2 in the above method embodiment.

[0459] An embodiment of the present application further provides a computer-readable storage medium storing a computer program or instruction for implementing the method executed by the SMF in the above method embodiment.

[0460] For example, when the computer program is executed by a computer, the computer can implement the method performed by the SMF in the above method embodiment.

[0461] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method performed by the multi-connection device, dual-connection device, UE1 or UE2 in the above method embodiment.

[0462] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method executed by the SMF in the above method embodiment.

[0463] An embodiment of the present application also provides a communication system, which includes a multi-connection device and a session-associated network element, wherein the multi-connection device is used to execute the steps of the method executed by the multi-connection device, dual-connection device, UE1 or UE2 in the aforementioned method embodiment, and the SMF is used to execute the steps of the method executed by the SMF in the aforementioned method embodiment.

[0464] Those skilled in the art can clearly understand that, for the sake of convenience and brevity of description, the explanation and beneficial effects of the relevant contents in any of the communication devices provided above can refer to the corresponding method embodiments provided above, and will not be repeated here.

[0465] The embodiments of the present application do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application; as long as it is capable of communicating according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application, it is sufficient. For example, the execution subject of the method provided in the embodiments of the present application may be a multi-connection device or a session-associated network element, or a functional module in the multi-connection device or session-associated network element that is capable of calling and executing the program.

[0466] Various aspects or features of the present application can be implemented as a method, apparatus, or article of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein can encompass a computer program accessible from any computer-readable device, carrier, or media.

[0467] The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that includes one or more available media. Available media (or computer-readable media) may include, but are not limited to, magnetic media or magnetic storage devices (e.g., floppy disks, hard disks (such as removable hard disks), magnetic tapes), optical media (e.g., optical disks, compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives), or semiconductor media (e.g., solid-state drives (SSDs), USB flash drives, read-only memories (ROMs), random access memories (RAMs), and other media that can store program code.

[0468] The various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0469] It should be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM may include the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0470] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0471] It should also be noted that the memory described herein is intended to comprise, but not be limited to, these and any other suitable types of memory.

[0472] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above-mentioned units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0473] The units described above as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected according to actual needs to implement the solutions provided in this application.

[0474] In addition, each functional unit in each embodiment of the present application may be integrated into one unit, each unit may exist physically separately, or two or more units may be integrated into one unit.

[0475] In the above embodiments, all or part of them can be implemented by software, hardware, firmware or any combination thereof.

[0476] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode. Regarding computer-readable storage media, reference can be made to the above description.

[0477] It should be understood that in the embodiments of the present application, the numbers "first", "second"... are only for distinguishing different objects, such as to distinguish different network devices, and do not constitute a limitation on the scope of the embodiments of the present application. The embodiments of the present application are not limited to this.

[0478] It should also be understood that in this application, "when", "if" and "if" all mean that the network element will make corresponding processing under certain objective circumstances, which is not a time limit, and does not require the network element to make judgment actions when implementing it, nor does it mean that there are other limitations.

[0479] It should also be understood that in each embodiment of the present application, "A corresponds to B" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A, and B can also be determined based on A and / or other information.

[0480] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: Applied to a multi-connection device, the multi-connection device includes multiple subscription data, the multi-connection device uses first subscription data to perform the method, the first subscription data being one of the multiple subscription data, the method comprising: Sending a first session establishment request, where the first session establishment request includes first indication information and a session identifier of a multi-connection session, where the first indication information is used to instruct establishment of the multi-connection session; Receive a first session establishment acceptance message, the first session establishment acceptance message includes session association information and a first network protocol IP address, the session association information is used to associate the session transmission path of the multiple contracted data, the first IP address includes the IP address allocated by the session management network element SMF to the first session, and the first session is a sub-session of the multi-connection session established using the first contracted data.

2. The method according to claim 1, characterized in that The session association information includes a session public IP address and / or a connection identification ID. The session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data. The connection ID is used to identify the multi-path transmission connection.

3. A communication method, characterized in that: Applied to a multi-connection device, the multi-connection device includes multiple subscription data, the multi-connection device uses second subscription data to perform the method, the second subscription data being one of the multiple subscription data, the method comprising: Sending a second session establishment request, where the second session establishment request includes second indication information and a session identifier of the multi-connection session, where the second indication information is used to instruct establishment of the multi-connection session; Receive a second session establishment acceptance message, where the second session establishment acceptance message includes a second IP address, where the second IP address includes an IP address allocated by the session management network element SMF to the second session, and the second session is a sub-session of the multi-connection session established using the second subscription data.

4. The method according to claim 3, characterized in that The session association information includes a session public IP address and / or a connection identification ID. The session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data. The connection ID is used to identify the multi-path transmission connection.

5. A communication method, characterized in that: Applied to a session management network element (SMF), the method includes: receiving a first session establishment request sent by a multi-connection device using first subscription data, where the first session establishment request includes first indication information and a session identifier of the multi-connection session, where the first indication information is used to indicate establishment of the multi-connection session, the multi-connection device includes multiple subscription data, and the multiple subscription data includes the first subscription data; A first session establishment acceptance message is sent, wherein the first session establishment acceptance message includes session association information and a first IP address, wherein the session association information is used to associate the session transmission paths of the multiple contracted data, and the first IP address includes the IP address assigned by the SMF to the first session, and the first session is a sub-session of the multi-connection session established using the first contracted data.

6. The method according to claim 5, characterized in that The session association information includes a session public IP address and / or a connection identification ID. The session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data. The connection ID is used to identify the multi-path transmission connection.

7. The method according to claim 5 or 6, characterized in that Before sending the first session establishment accept message, the method further includes: A third session establishment request is sent to the user plane network element UPF, where the third session establishment request is used to establish a session with the UPF, and the third session establishment request includes the session association information and the first IP address, or the third session establishment request includes the session identifier and the first IP address, and the UPF is used to aggregate sub-sessions of the multi-connection session.

8. The method according to claim 7, characterized in that The method further comprises: receiving a second session establishment request sent by the multi-connection device using second subscription data, where the second session establishment request includes second indication information and the session identifier, where the second indication information is used to instruct establishment of the multi-connection session, and the multiple subscription data include the second subscription data; Send a second session establishment acceptance message, where the second session establishment acceptance message includes a second IP address, where the second IP address includes the IP address allocated by the SMF to the second session, and the second session is a sub-session of the multi-connection session established using the second subscription data.

9. The method according to claim 8, characterized in that Before sending the second session establishment accept message, the method further includes: Send a fourth session establishment request to the UPF, where the fourth session establishment request is used to establish a session with the UPF, the fourth session establishment request includes the session association information and the second IP address, or the fourth session establishment request includes the session identifier and the second IP address.

10. The method according to any one of claims 5 to 9, characterized in that The method further comprises: A session registration message is sent, where the session registration message is used to register the context information of the multi-connection session in a unified data management (UDM) network element, where the context information includes the type of the multi-connection session and the session identifier.

11. A communication method, characterized in that: Applied to a multi-connection device, the multi-connection device includes multiple subscription data, the multi-connection device uses first subscription data to perform the method, the first subscription data being one of the multiple subscription data, the method comprising: Sending a first session establishment request, where the first session establishment request includes first indication information, where the first indication information is used to indicate that an agent is assigned to the multi-connection device, where the agent is used to establish a multi-path connection for the multi-connection device; receiving a first session establishment accept message, where the first session establishment accept message includes information about the agent, and the first session establishment accept message is used to indicate that establishment of a first session is complete, where the first session is a session established by the multi-connection device using the first subscription data; Sending a connection establishment request to the proxy according to the proxy information; A connection establishment acceptance message sent by the proxy is received, where the connection establishment acceptance message includes session association information, where the session association information is used to associate session transmission paths of the multiple contract data.

12. The method according to claim 11, characterized in that The session association information includes a session public IP address and / or a connection identification ID. The session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data. The connection ID is used to identify the multi-path transmission connection.

13. The method according to claim 11 or 12, characterized in that The first session establishment request also includes a session identifier of the first session.

14. A communication method, characterized in that: Applied to a multi-connection device, the multi-connection device includes multiple subscription data, the multi-connection device uses second subscription data to perform the method, the second subscription data being one of the multiple subscription data, the method comprising: Sending a second session establishment request, where the second session establishment request includes second indication information and proxy information, where the second indication information is used to indicate that a proxy is assigned to the multi-connection device, and the proxy is used to establish a multi-path connection for the multi-connection device; receiving a second session establishment accept message, where the second session establishment accept message is used to indicate that establishment of a second session is complete, where the second session is a session established by the multi-connection device using the second subscription data; A connection joining request is sent to the agent according to the agent information, the connection joining request including session association information, the connection joining request is used to request to join the connection corresponding to the session association information, and the session association information is used to associate the session transmission path of the multiple contract data.

15. The method according to claim 14, characterized in that The session association information includes a session public IP address and / or a connection identification ID. The session public IP address is a public IP address for establishing a multi-path transmission connection using the multiple subscription data. The connection ID is used to identify the multi-path transmission connection.

16. The method according to claim 14 or 15, characterized in that The method further comprises: Receive response information from the proxy, where the response information is used to indicate that joining the connection corresponding to the session association information is successful.

17. The method according to any one of claims 14 to 16, characterized in that The second session establishment request also includes a session identifier of a first session, where the first session is a session established by the multi-connection device using first subscription data, and the first subscription data is one of the multiple subscription data except the second subscription data.

18. A communication method, characterized in that: Applied to a session management network element (SMF), the method includes: receiving a first session establishment request sent by a multi-connection device using first subscription data, the first session establishment request including first indication information, the first indication information being used to instruct allocation of an agent to the multi-connection device, the agent being used to establish a multi-path connection for the multi-connection device, the multi-connection device including multiple subscription data, the multiple subscription data including the first subscription data; Send a first session establishment accept message, where the first session establishment accept message includes information about the agent, and the first session establishment accept message is used to indicate that establishment of a first session is complete, where the first session is a session established by the multi-connection device using the first subscription data.

19. The method according to claim 18, characterized in that The first session establishment request also includes a session identifier of the first session.

20. The method according to claim 18 or 19, characterized in that The method further comprises: receiving a second session establishment request sent by the multi-connection device using second subscription data, where the second session establishment request includes second indication information and information about the proxy, where the second indication information is used to indicate assignment of the proxy to the multi-connection device, and the second subscription data is one of the multiple subscription data other than the first subscription data; Send a second session establishment accept message, where the second session establishment accept message is used to indicate that establishment of a second session is complete, where the second session is a session established by the multi-connection device using the second subscription data.

21. The method according to any one of claims 18 to 20, characterized in that The method further comprises: Sending a proxy request message, where the proxy request message is used to request a first network element to allocate the proxy to the multi-connection device, where the first network element is used to manage the session of the multi-connection device; An agent allocation message is received, where the agent allocation message includes information of the agent.

22. A communication device, characterized in that: comprising a module or unit for executing the method of claim 1 or 2, or comprising a module or unit for executing the method of claim 3 or 4, or comprising a module or unit for executing the method of any one of claims 5 to 10, or comprising a module or unit for executing the method of any one of claims 11 to 13, or comprising a module or unit for executing the method of any one of claims 14 to 17, or comprising a module or unit for executing the method of any one of claims 18 to 21.

23. A communication device, characterized in that: The apparatus includes a processor coupled to a memory, wherein the memory stores instructions, and when the instructions are executed by the processor, the processor performs the method according to any one of claims 1 to 21.

24. A communication system, characterized in that: The method comprises a multi-connection device and a session management network element; wherein the multi-connection device is used to execute the method according to any one of claims 1 to 4, and the session management network element is used to execute the method according to any one of claims 5 to 10.

25. A communication system, characterized in that: The method comprises a multi-connection device and a session management network element; wherein the multi-connection device is used to execute the method according to any one of claims 11 to 17, and the session management network element is used to execute the method according to any one of claims 18 to 21.

26. A computer-readable storage medium, characterized in that A computer program or instructions is stored, wherein the computer program or instructions are used to implement the method according to any one of claims 1 to 21.

27. A chip, characterized in that: include: A processor and an interface, configured to call from a memory and run a computer program stored in the memory to execute the method according to any one of claims 1 to 21.

Images