Multi-path redundant transmission method, user equipment, network entity and storage medium

Abstract

The embodiments of the present application provide a multi-path redundant transmission method, user equipment, network entity, and storage medium. In the embodiments of the present application, the user equipment and the network entity in the mobile communication network cooperate with each other to realize the activation and deactivation of multi-path-based asynchronous redundant transmission for the MA PDU session. In this way, for data packets that have been transmitted on one access path but have not been confirmed in time, these data packets can be asynchronously redundantly transmitted on another access path, enriching the implementation methods of the redundant transmission mechanism, allowing the UE to effectively solve the multi-path late-arrival problem in downlink transmission, obtain the corresponding data packets as soon as possible, and improve the user's QoE of data streams, especially data streams with high real-time requirements.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a multi-path redundant transmission method, user equipment, network entity, and storage medium. Background Art

[0002] Access Traffic Steering, Switching and Splitting (ATSSS) was added in 3GPP Release 16. To support ATSSS, the 5G system architecture was extended to include one or more steering functions on the user equipment (UE), each of which supports traffic steering, switching, and splitting across 3GPP and non-3GPP accesses.

[0003] Currently, ATSSS supports redundant transmission mode, which means that the same data packet is transmitted on the 3GPP path and non-3GPP path at the same time. By performing redundant transmission on the 3GPP path with better Quality of Service (QoS), the UE is guaranteed to obtain the corresponding data packet as quickly as possible, thereby improving the Quality of Experience (QoE) of the data flow.

[0004] Existing redundant transmission modes are relatively simple in their implementation and fail to address the multi-path head of line blocking problem. This problem occurs when, in multi-path transmission, the transmission latency of one path is significantly greater than that of another. Consequently, packets transmitted earlier on this path often have not yet been received by the time packets later on the other path arrive, leading to packet loss or out-of-order transmission. To address this issue, a new multi-path redundant transmission solution is needed. Summary of the Invention

[0005] Multiple aspects of the present application provide a multi-path redundant transmission method, user equipment, network entity and storage medium, which are used to provide a new multi-path redundant transmission mode, so that the UE can effectively solve the multi-path late-arrival problem in downlink transmission, obtain the corresponding data packet as soon as possible, and improve the QoE of the data stream.

[0006] An embodiment of the present application provides a multi-path redundant transmission method, applicable to a user equipment, the method comprising: sending a first message to a first network entity, the first message including at least first indication information of a multi-anchor protocol data unit (MA PDU) session requesting the use of an asynchronous redundant transmission mode, so that the first network entity sends a second message to a second network entity, the asynchronous redundant transmission mode being one of the redundant transmission modes; and receiving a fourth message returned by the first network entity, the second message and the fourth message including at least configuration indication information for performing asynchronous redundant transmission on unconfirmed data packets on a first access path, so that the second network entity performs asynchronous redundant transmission on the unconfirmed data packets on the first access path through a second access path according to the configuration indication information.

[0007] An embodiment of the present application also provides a multi-path redundant transmission method, applicable to a first network entity, the method comprising: receiving a first message sent by a user device, the first message including at least first indication information of a multi-anchor protocol data unit MAPDU session requesting the use of an asynchronous redundant transmission mode, the asynchronous redundant transmission mode being one of the redundant transmission modes; determining, based on the first indication information, configuration indication information for performing asynchronous redundant transmission on unconfirmed data packets on a first access path; sending a second message to a second network entity, and sending a fourth message to the user device, the second message and the fourth message including at least the configuration indication information, so that the second network entity performs asynchronous redundant transmission on the unconfirmed data packets on the first access path through a second access path.

[0008] An embodiment of the present application also provides a multi-path redundant transmission method, applicable to a second network entity, the method comprising: receiving a second message sent by a first network entity, the second message including at least configuration indication information for asynchronous redundant transmission of unconfirmed data packets on a first access path, the multi-anchor protocol data unit MA PDU session corresponding to the first access path requesting to use an asynchronous redundant transmission mode; configuring a first data stream for unconfirmed data packets on the first access path on a second access path according to the configuration indication information; caching the unconfirmed data packets on the first access path into the first data stream for asynchronous redundant transmission through the second access path, the second access path being another access path corresponding to the MA PDU session.

[0009] An embodiment of the present application also provides a user device, comprising: a memory, a processor, and a communication component; the memory is used to store a computer program; the processor is used to execute the computer program to implement the steps in the multi-path redundant transmission method that can be executed by the user device provided in the embodiment of the present application.

[0010] An embodiment of the present application further provides a network entity that can be implemented as a first network entity, comprising: a memory, a processor, and a communication component; the memory is used to store a computer program; the processor is used to execute the computer program to implement the steps of the multi-path redundant transmission method provided in the embodiment of the present application and that can be performed by the first network entity.

[0011] An embodiment of the present application also provides a network entity that can be implemented as a second network entity, including: a memory, a processor, and a communication component; the memory is used to store a computer program; the processor is used to execute the computer program to implement the steps of the multi-path redundant transmission method provided in the embodiment of the present application and which can be performed by the second network entity.

[0012] An embodiment of the present application further provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor is enabled to implement the steps of the multi-path redundant transmission method provided in each embodiment of the present application.

[0013] In an embodiment of the present application, the user equipment and the network entity in the mobile communication network cooperate with each other to realize the activation and deactivation of asynchronous redundant transmission based on multiple paths for the MAPDU session. In this way, for the data packets that have been transmitted on an access path but have not been confirmed in time, these data packets can be asynchronously redundantly transmitted on another access path. The implementation method of the redundant transmission mechanism is enriched, and the UE can effectively solve the multi-path late-arrival problem in downlink transmission, obtain the corresponding data packets as soon as possible, and improve the user's QoE of data streams, especially data streams with high real-time requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0015] Figure 1a A schematic diagram of a partial architecture of a mobile communication network provided by an exemplary embodiment of the present application;

[0016] Figure 1b A schematic diagram of a transmission state of an asynchronous redundant transmission mode provided by an exemplary embodiment of the present application;

[0017] Figure 2a A schematic diagram of an interactive flow of a multi-path redundant transmission method provided by an exemplary embodiment of the present application;

[0018] Figure 2b A schematic diagram of an interactive flow of another multi-path redundant transmission method provided by an exemplary embodiment of the present application;

[0019] Figure 2c A schematic diagram of an interactive flow of another multi-path redundant transmission method provided by an exemplary embodiment of the present application;

[0020] Figure 3a A schematic diagram of an interactive flow of another multi-path redundant transmission method provided by an exemplary embodiment of the present application;

[0021] Figure 3b A schematic diagram of an interactive flow of another multi-path redundant transmission method provided by an exemplary embodiment of the present application;

[0022] Figure 4a A flowchart of another multi-path redundant transmission method provided by an exemplary embodiment of the present application;

[0023] Figure 4b A flowchart of another multi-path redundant transmission method provided by an exemplary embodiment of the present application;

[0024] Figure 4c A flowchart of another multi-path redundant transmission method provided by an exemplary embodiment of the present application;

[0025] Figure 5a A schematic structural diagram of a multi-path redundant transmission device provided as another exemplary embodiment of the present application;

[0026] Figure 5b A schematic structural diagram of a multi-path redundant transmission device provided as another exemplary embodiment of the present application;

[0027] Figure 5c A schematic structural diagram of a multi-path redundant transmission device provided as another exemplary embodiment of the present application;

[0028] Figure 6a A schematic diagram of the structure of a user equipment provided by an exemplary embodiment of the present application;

[0029] Figure 6b A schematic diagram of the structure of a network entity provided by an exemplary embodiment of the present application;

[0030] Figure 6c A structural diagram of another network entity provided for an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0031] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0032] The implementation of the existing redundant transmission mode is relatively simple and cannot solve the technical problem of late arrival first under multi-path. In the embodiment of the present application, the user equipment and the network entity in the mobile communication network cooperate with each other to realize the activation and deactivation of asynchronous redundant transmission based on multi-path for the MA PDU session. In this way, for the data packets that have been transmitted on an access path but have not been confirmed in time, these data packets can be asynchronously redundantly transmitted on another access path, enriching the implementation method of the redundant transmission mechanism, allowing the UE to effectively solve the multi-path late arrival first problem in downlink transmission, obtain the corresponding data packets as soon as possible, and improve the user's QoE for data streams, especially data streams with high real-time requirements.

[0033] The mobile communication network of this embodiment includes an access network and a core network. The access network mainly includes base stations. There may be multiple access networks, for example, it may include both a 3GPP access network and a non-3GPP (Non-3GPP) access network; the core network includes but is not limited to the following multiple network entities: Authentication Server Function (AUSF), User Plane Function (UPF), Access and Mobility Management Function (AMF), Unified Data Management (UDM), Network Exposure Function (NEF), Session Management Function (SMF), Network Slice Selection Function (NSSF), Network Storage Function (NFRepository Function, NRF), Policy Control Function (PCF), Application Layer Function (AF), etc.

[0034] In addition, the mobile communication network of this embodiment supports the ATSSS feature, which supports a redundant transmission mode, which can be called a redundant steering mode. The redundant transmission mode is a mode in which data packets can be redundantly transmitted on multiple paths. In order to support the ATSSS feature, the system architecture of the mobile communication network of this embodiment of the application has been expanded, such as Figure 1a As shown, the UE in the embodiment of the present application supports one or more steering functions, such as MPTCP (MultiPath TCP) function and / or ASSSS-LL and / or MP-QUIC (Mutipath QUIC) function. According to the ATSSS rules provided by the network, each steering function in the UE supports traffic steering, switching and splitting of multi-path access. For Ethernet type MA PDU (Mutil Anchor Protocol Data Unit) sessions, the ASSSS-LL function is mandatory in the UE. Accordingly, as Figure 1a As shown, the UPF in the embodiment of the present application can support the MPTCP proxy function, which communicates with the PTCP function in the UE by using the MPTCP protocol; the UPF can also support the ATSSS-LL function, which is similar to the ATSSS-LL function in the UE.

[0035] exist Figure 1a In addition to UPF and UE, other network entities related to redundant transmission, such as AMF, SMF and PCF, are also shown. Among them, AMF is responsible for the access and mobility management functions of UE; SMF implements session management, which supports the establishment, modification and release of sessions, the allocation and management of UE IP addresses, etc.; PCF supports a unified policy framework for managing network behavior, provides policy rules for the control plane to execute, and can access subscription information related to policy formulation in the unified data repository (UDR). UPF is mainly responsible for the routing and forwarding of user plane data packets in the core network, and interacts with SMF through the N4 air interface, performs corresponding processing according to various policies issued by SMF, and serves as a session point for interconnection between the core network and the data network (DN).

[0036] In the embodiment of the present application, there are multiple access paths between the UE and the UPF, and the UE and the network entities UPF, AMF, SMF, PCF, etc. cooperate with each other to realize a redundant transmission process based on multiple paths. Figure 1aIn the embodiment, multiple access paths between the UE and the UPF, including 3GPP access paths and non-3GPP access paths, are used as an example for illustration, but the present invention is not limited thereto. With the development of communication technology, more other access paths may appear in the future, and these access paths are also applicable to the embodiments of the present application. The redundant transmission mode allows redundant transmission of data packets on multiple access paths, but does not limit the specific implementation method of redundant transmission of data packets on multiple access paths. Optionally, a specific implementation method of the redundant transmission mode is a synchronous redundant transmission mode, that is, after triggering the transmission in this mode, the same data packet is transmitted simultaneously on multiple access paths, thereby realizing redundant transmission based on multiple paths. In addition, the embodiment of the present application also provides an asynchronous redundant transmission mode (re-injection mode), which can also be called asynchronous retransmission mode or re-caching retransmission mode. It is another specific implementation method of the redundant transmission mode. It mainly refers to the case where a data packet that has been transmitted on an access path and has not received timely confirmation from the other end, and a data packet sent later on another access path arrives first, the data packet that has not been confirmed in time is asynchronously transmitted again on the other access path, thereby realizing redundant transmission based on multiple paths and solving the problem of late arrival first caused by a data packet that has been transmitted on an access path and has not received a confirmation message from the other end. Among them, Figure 1b The figure shows the transmission status diagram of the asynchronous redundant transmission mode. Figure 1b In the example, both ends adopt asynchronous redundant transmission mode, wherein data packets 1-10 are transmitted on the non-3GPP access path. Data packets 1-3 and 8-10 receive confirmation messages (ACK) from the other end, but data packet 4-7, which was sent earlier than data packet 8-10, fails to receive the confirmation message from the other end. Therefore, asynchronous redundant retransmission is performed from another access path, namely the 3GPP access path, so as to take advantage of the priority of the 3GPP access path with better QoS to ensure that the other end receives data packet 4-7 in time.

[0037] In this embodiment, the UPF can use an asynchronous redundant transmission mode to send downlink data packets to the UE. Similarly, the UE can also use the asynchronous redundant transmission mode to send uplink data packets to the UPF. The asynchronous redundant transmission process of uplink data packets is the same or similar to the asynchronous redundant transmission process of downlink data packets. In the following embodiments of this application, the multi-path redundant transmission method provided in the embodiments of this application is described in detail, focusing on the example of the UPF using the asynchronous redundant transmission mode to send downlink data packets to the UE.

[0038] Figure 2a The following is a flow chart of an interactive process of a multi-path redundant transmission method provided by an exemplary embodiment of the present application. Figure 2a As shown, the method includes:

[0039] 21a. The UE sends a first message to the first network entity. The first message includes at least first indication information that the MA PDU session requests to use the asynchronous redundant transmission mode. The asynchronous redundant transmission mode is one of the redundant transmission modes.

[0040] 22a. After receiving the first message, the first network entity determines configuration instruction information for performing asynchronous redundant transmission on unacknowledged data packets on the first access path according to the first instruction information for requesting to use the asynchronous redundant transmission mode included in the first message.

[0041] 23a. The first network entity sends a second message to the second network entity, where the second message includes at least the above configuration indication information.

[0042] 24a. After receiving the second message, the second network entity configures a first data flow for unacknowledged data packets on the first access path on the second access path according to the configuration indication information included in the second message.

[0043] 25a. The second network entity returns a third message to the first network entity to notify the first network entity that the configuration has been completed.

[0044] 26a. After receiving the third message, the first network entity sends a fourth message to the UE, where the fourth message includes at least the above configuration indication information, so that the UE understands that the asynchronous redundant transmission mode can be used.

[0045] 27a. The second network entity buffers the unacknowledged data packets on the first access path into the first data flow for asynchronous redundant transmission through the second access path.

[0046] 28a. In the asynchronous redundant transmission mode, the UE re-receives the unacknowledged data packet on the first access path on the second access path.

[0047] In this embodiment, there are multiple access paths between the UE and the second network entity. Under normal circumstances, the second network entity can transmit different data packets to the UE on the multiple access paths respectively, so as to give full play to the advantages of multiple access paths and improve the transmission efficiency of data packets. However, in order to give full play to the beneficial effects of multi-path redundant transmission, the UE can send a first message to the first network entity during the process of creating an MA PDU session or during the process of modifying an MA PDU session to request the use of the asynchronous redundant transmission mode in the redundant transmission mode for data packet transmission for the MAPDU session. The first network entity is the network entity responsible for session management, and can be, for example, but not limited to, an SMF. The second network entity is the network entity that performs user plane data packet forwarding with the UE, and can be, for example, but not limited to, a UPF.

[0048] Optionally, the first message may only include the first indication information (re-injection mode) requesting the use of the asynchronous redundant transmission mode, or may also include the second indication information (indication of support for redundant mode) that the MA PDU session supports the redundant transmission mode and the first indication information (re-injection mode) that the MA PDU session requests the use of the asynchronous redundant transmission mode, without limitation.

[0049] After receiving the first message, the first network entity determines that the UE requests to use the asynchronous redundant transmission mode based on at least the first indication information for requesting to use the asynchronous redundant transmission mode contained in the first message. Therefore, it is necessary to generate configuration indication information for asynchronous retransmission of unconfirmed data packets on the first access path for the second network entity, so that the second network entity performs relevant configuration of the asynchronous retransmission redundancy mode according to the configuration indication information, and sends the configuration indication information to the second network entity through a third message.

[0050] In this embodiment, under normal circumstances, the second network entity can transmit different data packets to the UE over multiple access paths, leveraging the advantages of multiple access paths and improving data packet transmission efficiency. However, when a last-come-first-served problem occurs—that is, a data packet transmitted on one access path but not promptly acknowledged by the UE arrives before a later data packet sent on another access path—asynchronous redundant transmission mode can be triggered. The first access path is the access path currently used by the MAPDU session and is the access path for "data packets transmitted but not promptly acknowledged by the UE" in the last-come-first-served problem. Accordingly, the second access path is another access path corresponding to the MAPDU session and is the access path for "data packets sent later arriving first" in the last-come-first-served problem. It is used for asynchronous redundant transmission of unacknowledged data packets on the first access path. In this embodiment, the first and second access paths are not limited. Relatively speaking, the QoS of the second access path is superior to that of the first access path. Optionally, the first access path can be a non-3GPP access path, while the second access path is a 3GPP access path. QoS can specifically refer to multiple indicator parameters, including but not limited to latency, jitter, packet loss rate, path load, etc.

[0051] In this embodiment, regardless of which access path the second network entity sends a data packet to the UE, the UE must return an acknowledgment message within a set timeframe. If, after sending a data packet, the second network entity fails to receive an acknowledgment message from the UE in a timely manner, the data packet is referred to as an unacknowledged data packet. Accordingly, an unacknowledged data packet on the first access path refers to a data packet that has been transmitted on the first access path but for which the UE has not received an acknowledgment message in a timely manner. Data packets for which the UE has not received an acknowledgment message in a timely manner primarily refer to first-sent data packets that are later than later-sent data packets when a first-sent-last-arrival issue occurs.

[0052] In order to use the second access path to perform asynchronous redundant transmission (asynchronous redundant transmission can also be referred to as asynchronous retransmission) of unconfirmed data packets on the first access path, the second network entity, after receiving the second message, configures a first data stream for unconfirmed data packets on the first access path on the second access path according to the configuration indication information in the second message. The first data stream is a data stream used for redundant transmission of unconfirmed data packets on the first access path. The data stream is actually a data queue for storing data packets. The data queue has a higher access channel priority. Optionally, in a 5G network, the priority can be characterized by a 5G QoS identifier (5G QoS Identifier, 5QI); accordingly, the first data stream can be a 5G QoS data stream, but is not limited to this. The 5G QoS identifier (5QI) is a reference scalar for providing specific QoS forwarding behavior (e.g., packet loss rate, packet delay budget) to the 5G QoS data stream. This can be implemented in the access network by referencing specific parameters of the 5QI node, where the specific parameters refer to parameters that control QoS forwarding processing.

[0053] After configuring the first data flow, the second network entity can, on the one hand, return a third message to the first network entity to inform the first network entity that the configuration of the asynchronous redundant transmission mode has been completed. Based on this, the first network entity sends a fourth message to the UE, carrying the aforementioned configuration indication information in the fourth message, so that the UE understands that the UPF has completed the configuration of the asynchronous redundant transmission mode and can use the asynchronous redundant transmission mode. The UE can also configure the client for the MA PDU session to receive data packets in the asynchronous redundant transmission mode. On the other hand, the second network entity can identify unacknowledged data packets on the first access path and cache the identified unacknowledged data packets in the first data flow for asynchronous redundant transmission via the second access path.

[0054] Among them, in addition to the first data stream on the second access path, there may be other data streams, and these data streams have different quality of service indications (QIs). The UPF schedules these data streams according to their quality of service indications, and the data packets in the scheduled data streams can be transmitted on the second access path. Optionally, in a 5G network, the QI of the data stream may be called 5QI (5G QoS Identifier). In this embodiment, the implementation method of the 5QI of the data stream is not limited. However, in order to ensure that the first data stream can be scheduled in time, the 5QI of the first data stream may have a higher priority. The higher the priority of the 5QI, the more priority the corresponding data stream will be scheduled.

[0055] When the first data stream is scheduled, unacknowledged data packets on the first access path that are cached in the first data stream are retransmitted on the second access path. For the UE, in asynchronous redundant transmission mode, unacknowledged data packets on the first access path can be re-received on the second access path, implementing multi-path-based asynchronous redundant transmission. This not only enriches the implementation methods of the redundant transmission mechanism, but also allows the UE to effectively solve the multi-path late-send-first-arrival problem in downlink transmission, obtain corresponding data packets as quickly as possible, and improve the user's QoE for data streams, especially those with high real-time requirements.

[0056] In the various embodiments of the present application, the manner in which the first network entity determines the configuration instruction information for asynchronous redundant transmission of unacknowledged data packets on the first access path is not limited. In an alternative embodiment, the configuration instruction information may be locally configured by the first network entity. In another alternative embodiment, the first network entity and a third network entity may interact, with the third network entity being responsible for providing the configuration instruction information. The third network entity is a network entity responsible for policy management, and may be, for example, but not limited to, a PCF.

[0057] Further, optionally, in addition to determining the aforementioned configuration indication information, the first network entity may also determine a trigger parameter corresponding to the asynchronous redundant transmission mode and provide it to the second network entity. Optionally, the first network entity may include the trigger parameter in a second message and provide it to the second network entity. The trigger parameter is used by the second network entity to identify unacknowledged data packets on the first access path, which also activates the asynchronous redundant transmission mode. Optionally, the trigger parameter may be the delay difference between the two access paths. Thus, each time the second network entity transmits a data packet on the first access path, the second network entity (e.g., the UPF) may monitor the delay difference between the two access paths. When the delay difference exceeds a threshold, the data packets transmitted during the period when the delay difference exceeded the threshold are determined to be unacknowledged data packets requiring asynchronous retransmission, and the unacknowledged data packets are buffered in the first data stream. When the delay difference again falls below the threshold, the second network entity may transmit different data packets to the UE over multiple access paths. This is equivalent to deactivating the asynchronous redundant retransmission mode. Using multiple access paths to simultaneously transmit different data packets improves data packet transmission efficiency. That is, as the delay difference changes, when the delay difference is large, the asynchronous redundant retransmission mode can be activated, and when the delay difference becomes small again, the asynchronous redundant retransmission mode can be deactivated.

[0058] In the various embodiments of the present application, the manner in which the first network entity determines the trigger parameter is not limited. In an optional embodiment, the trigger parameter may be locally configured by the first network entity. In another optional embodiment, the first network entity and a third network entity may interact, with the third network entity being responsible for providing the trigger parameter.

[0059] In an optional embodiment, after receiving the first message, the first network entity simultaneously determines configuration instruction information for performing asynchronous redundant transmission on unacknowledged data packets on the first access path and trigger parameters of the asynchronous redundant transmission mode. Figure 2b As shown, this embodiment includes the following steps:

[0060] 21b. The UE sends a first message to the first network entity. The first message includes at least first indication information that the MA PDU session requests to use the asynchronous redundant transmission mode. The asynchronous redundant transmission mode is one of the redundant transmission modes.

[0061] 22b. After receiving the first message, the first network entity determines, based on the first indication information requesting the use of the asynchronous redundant transmission mode contained in the first message, configuration indication information for performing asynchronous redundant transmission on unconfirmed data packets on the first access path, as well as trigger parameters for the asynchronous redundant transmission mode.

[0062] Optionally, the manner in which the first network entity determines the configuration indication information and the trigger parameter includes but is not limited to the following:

[0063] Method A1: After receiving the first message, the first network entity locally configures the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path and the trigger parameters of the asynchronous redundant transmission mode according to the first indication information requesting the use of the asynchronous redundant transmission mode contained in the first message.

[0064] Mode A2: After receiving the first message, the first network entity sends a fifth message to the third network entity based on the first indication information requesting the use of the asynchronous redundant transmission mode contained in the first message. The fifth message includes at least the first indication information requesting the use of the asynchronous redundant transmission mode, so that the third network entity can confirm whether the asynchronous redundant transmission mode can be used. The first network entity then receives a sixth message from the third network entity. The sixth message indicates that the asynchronous redundant transmission mode can be used and also includes configuration indication information for asynchronous redundant transmission of unacknowledged data packets on the first access path, as well as trigger parameters for the asynchronous redundant transmission mode. The first network entity parses the configuration indication information and trigger parameters from the sixth message. In Mode A2, both the configuration indication information and trigger parameters are provided by the third network entity.

[0065] Mode A3: After receiving the first message, the first network entity sends a fifth message to the third network entity based on the first indication information requesting the use of the asynchronous redundant transmission mode contained in the first message. The fifth message includes at least the first indication information requesting the use of the asynchronous redundant transmission mode, so that the third network entity can confirm whether the asynchronous redundant transmission mode can be used. The first network entity then receives a sixth message from the third network entity. The sixth message indicates that the asynchronous redundant transmission mode can be used and also includes configuration indication information for asynchronous redundant transmission of unacknowledged data packets on the first access path. The first network entity parses the configuration indication information from the sixth message and locally configures trigger parameters for the asynchronous redundant transmission mode. In Mode A3, the configuration indication information is provided by the third network entity, and the trigger parameters are locally configured by the second network entity.

[0066] Mode A4: After receiving the first message, the first network entity sends a fifth message to the third network entity based on the first indication information requesting the use of the asynchronous redundant transmission mode contained in the first message. The fifth message includes at least the first indication information requesting the use of the asynchronous redundant transmission mode, so that the third network entity can confirm whether the asynchronous redundant transmission mode can be used. The first network entity then receives a sixth message from the third network entity. The sixth message indicates that the asynchronous redundant transmission mode can be used and also includes trigger parameters for the asynchronous redundant transmission mode. The first network entity parses the trigger parameters from the sixth message and locally configures configuration indication information for asynchronous redundant transmission of unacknowledged data packets on the first access path. In Mode A4, the trigger parameters are provided by the third network entity, and the configuration indication information is locally configured by the second network entity.

[0067] 23b. The first network entity sends a second message to the second network entity, where the second message includes the above configuration indication information and trigger parameters.

[0068] 24b. After receiving the second message, the second network entity configures a first data flow for unacknowledged data packets on the first access path on the second access path according to the configuration indication information included in the second message.

[0069] 25b. The second network entity returns a third message to the first network entity to notify the first network entity that the configuration has been completed.

[0070] 26b. After receiving the third message, the first network entity sends a fourth message to the UE. The fourth message includes the above configuration indication information and trigger parameters, so that the UE knows that the asynchronous redundant transmission mode can be used.

[0071] 27b. The second network entity identifies unacknowledged data packets on the first access path according to the trigger parameter included in the second message, and caches the identified unacknowledged data packets into the first data flow for asynchronous redundant transmission through the second access path.

[0072] Specifically, the trigger parameter represents the delay difference for transmitting data packets between the two access paths. The second network entity can monitor the delay difference for transmitting data packets between the first access path and the second access path, and treat the data packets sent on the first access path during the period when the delay difference exceeds the set threshold as unconfirmed data packets that need to be asynchronously retransmitted. These data packets usually cannot receive the confirmation message returned by the UE in time due to the large delay difference.

[0073] 28b. In the asynchronous redundant transmission mode, the UE re-receives the unacknowledged data packet on the first access path on the second access path.

[0074] Furthermore, when the delay difference falls below the threshold again, the second network entity can transmit different data packets to the UE over multiple access paths. This is equivalent to deactivating the asynchronous redundant retransmission mode. Using multiple access paths to simultaneously transmit different data packets improves data packet transmission efficiency. In other words, as the delay difference changes, the asynchronous redundant retransmission mode can be activated when the delay difference is large, and deactivated when the delay difference becomes smaller again.

[0075] In the above embodiment, the trigger parameter of the asynchronous redundant transmission mode is provided by the first network entity or the third network entity as an example for explanation, but the present invention is not limited thereto. The trigger parameter required to trigger the second network entity to identify the unconfirmed data packet on the first access path may also be provided by the application layer or the application layer protocol (e.g., the MP-QUIC protocol), that is, the above configuration indication information is provided by the first network entity or the third network entity, and is provided to the second network entity and the UE respectively through the second message and the fourth message. Before identifying the unconfirmed data packet on the first access path, the second network entity may also receive the trigger parameter sent by the application layer or the application layer protocol (e.g., the MP-QUIC protocol), and identify the unconfirmed data packet on the first access path according to the trigger parameter provided by the application layer or the application layer protocol (e.g., the MP-QUIC protocol).

[0076] It should be noted that the application layer refers to an upper-layer application on the UE, such as an APP, or a transmission protocol used by the application layer, such as the MP-QUIC transmission protocol or a transmission tunnel. The upper-layer application or the transmission protocol tunnel of the application layer can configure the trigger parameters of the asynchronous redundant transmission mode by itself, or can also send a seventh message to the first network entity to request the first network entity to configure the trigger parameters required for the asynchronous redundant transmission mode; then, the eighth message returned by the first network entity is received, and the trigger parameters configured by the first network entity are parsed from the eighth message. Here, the upper-layer application (or UE) requests the first network entity to configure the trigger parameters required for the asynchronous redundant transmission mode, including: requesting the first network entity to configure the trigger parameters when there are no trigger parameters, and also including requesting the first network entity to modify or reconfigure the trigger parameters when there are trigger parameters because the trigger parameters are inappropriate. Regardless of how the trigger parameters are obtained, after obtaining the trigger parameters, a ninth message can be sent to the second network entity, and the trigger parameters can be included in the ninth message.

[0077] It should be noted that the application layer can provide a trigger parameter to the second network entity, which then activates the asynchronous redundant transmission mode based on the trigger parameter. This process involves identifying data packets sent on the first access path during the period when the delay difference indicated by the transmission parameter exceeds a set threshold as unacknowledged data packets requiring asynchronous retransmission, caching them in the first data stream for asynchronous redundant transmission over the second access path. Furthermore, the application layer can also provide a trigger indication for the asynchronous redundant transmission mode to the second network entity, which then activates the asynchronous redundant transmission mode based on the trigger indication. This means identifying unacknowledged data packets on the first access path, caching them in the first data stream for asynchronous redundant transmission over the second access path. This trigger indication also enables the second network entity to identify unacknowledged data packets on the first access path, but differs from the trigger parameter in that it enables the second network entity to treat data packets that have been transmitted on the first access path but for which no acknowledgment message has been received prior to the arrival of the trigger indication as unacknowledged data packets.

[0078] Optionally, the trigger parameter or trigger indication is provided by an upper-layer application or application-layer transport protocol. Specifically, the trigger mechanism of the application-layer transport protocol can be the QoE status signaling (QoE_STATUS_SIGNAL) in the MP-QUIC scheduling protocol. The QOE status signaling can carry the buffered packet sequence of the downlink data packets received by the UE. The UPF can trigger asynchronous redundant transmission based on the QoE status signaling.

[0079] In an optional embodiment, after receiving the first message, the first network entity determines configuration instruction information for performing asynchronous redundant transmission for unacknowledged data packets on the first access path, and provides a trigger instruction of the asynchronous redundant transmission mode to the second network entity through the application layer. Figure 2c As shown, this embodiment includes the following steps:

[0080] 21c. The UE sends a first message to the first network entity. The first message includes at least first indication information that the MA PDU session requests to use the asynchronous redundant transmission mode. The asynchronous redundant transmission mode is one of the redundant transmission modes and can also be an independent redundant transmission mode.

[0081] 22c. After receiving the first message, the first network entity determines configuration instruction information for performing asynchronous redundant transmission on unacknowledged data packets on the first access path according to the first instruction information for requesting to use the asynchronous redundant transmission mode included in the first message.

[0082] 23c. The first network entity sends a second message to the second network entity, where the second message includes at least the above configuration indication information.

[0083] 24c. After receiving the second message, the second network entity returns a third message to the first network entity to notify the first network entity that the second message has been received.

[0084] 25c. After receiving the third message, the first network entity sends a fourth message to the UE, where the fourth message includes the above configuration indication information, so that the UE understands that the asynchronous redundant transmission mode can be used.

[0085] 26c. The UE sends a trigger indication of the asynchronous redundant transmission mode to the second network entity, where the trigger indication is used for the second network entity to identify data packets that have been transmitted on the first access path but for which no confirmation message has been received before the trigger indication arrives as unconfirmed data packets.

[0086] 27c. The second network entity configures a first data stream for unconfirmed data packets on the first access path on the second access path according to the configuration indication information included in the second message, and caches the unconfirmed data packets on the first access path into the first data stream according to the above trigger indication, so as to perform asynchronous redundant transmission through the second access path.

[0087] 28c. The UE re-receives the unacknowledged data packet on the first access path on the second access path in the asynchronous redundant transmission mode.

[0088] In this embodiment, steps identical or similar to those in the previous embodiment can be found in the previous embodiment and will not be repeated here. In this embodiment, the trigger indication is used for the second network entity to activate the asynchronous redundant transmission mode, i.e., packets on the first access path for which no confirmation message has been received before the trigger indication arrives are treated as unconfirmed packets and cached in the first data stream for asynchronous redundant transmission via the second access path. After caching the unconfirmed packets in the first data stream, or after all the unconfirmed packets are asynchronously redundantly transmitted via the second access path, the second network entity can retransmit different packets to the UE over multiple access paths. This is equivalent to deactivating the asynchronous redundant retransmission mode. Using multiple access paths to simultaneously transmit different packets is beneficial for improving packet transmission efficiency. In other words, the application layer can provide a trigger indication to the second network entity on demand (e.g., when a last-come-first-served issue occurs), allowing the second network entity to dynamically activate / deactivate the asynchronous redundant retransmission mode.

[0089] It is explained here that the second network entity can identify unconfirmed data packets on the first access path based solely on the trigger parameter or the trigger indication (i.e., activate the asynchronous redundant retransmission mode), or can simultaneously identify unconfirmed data packets on the first access path (i.e., activate the asynchronous redundant retransmission mode) in combination with the trigger parameter and the trigger indication. Regarding the case of identifying unconfirmed data packets on the first access path in combination with the trigger parameter and the trigger indication, the second network entity can activate the asynchronous redundant retransmission mode when receiving the trigger indication, that is, it is necessary to treat the data packets that have been transmitted on the first access path but have not received a confirmation message before the trigger indication arrives as unconfirmed data packets. In addition, the second network entity can also treat the data packets sent on the first access path during the period when the delay difference represented by the trigger parameter exceeds the set threshold as unconfirmed data packets. Regarding the case of identifying unconfirmed data packets on the first access path in combination with the trigger parameter and the trigger indication, the trigger parameter can be provided by the upper-layer application, or by the first network entity or the third network entity, and there is no limitation on this.

[0090] In the above or following embodiments, the implementation method of the "configuration indication information" is not limited. Any implementation method of the information that can indicate the configuration of the first data flow for the unconfirmed data packets on the first access path on the second access path is applicable to the embodiments of the present application. In an optional embodiment, the configuration indication information is used to instruct the creation of a new data flow for the unconfirmed data packets on the first access path on the second access path, and indicates that the new data flow has a higher 5QI, so as to obtain priority scheduling and ensure that the UE receives the data packet in time. In this optional embodiment, the configuration indication information may include first indication information and a first 5QI. The first indication information is used to instruct the creation of a new data flow for the unconfirmed data packets on the first access path on the second access path. The first 5QI refers to the 5QI that the new data flow should have. Based on this, a method for the second network entity to configure the first data flow for the unconfirmed data packets on the first access path on the second access path according to the configuration indication information includes: creating a new data flow on the second access path for the unconfirmed data packets on the first access path according to the first indication information in the configuration indication information, and configuring the 5QI of the new data flow to be the first 5QI. In this embodiment, the new data flow is the first data flow.

[0091] In another optional embodiment, the configuration indication information is used to indicate that the unconfirmed data packets on the first access path are cached to the existing data stream with a higher priority 5QI on the second access path, so as to obtain priority scheduling and ensure that the UE receives the data packet in time. In this optional embodiment, the configuration indication information may include second indication information and a second 5QI, and the second indication information is used to indicate that the unconfirmed data packets on the first access path are cached to the existing data stream with a second 5QI on the second access path, and the priority of the second 5QI is higher, for example, higher than a set priority threshold. Based on this, a method for the second network entity to configure the first data stream for the unconfirmed data packets on the first access path on the second access path according to the configuration indication information includes: determining the existing data stream with the second 5QI on the second access path according to the second 5QI in the configuration indication information; and determining to multiplex the existing data stream with the second 5QI for the unconfirmed data packets on the first access path according to the second indication information in the configuration indication information. In this embodiment, the existing data stream with the second 5QI is the first data stream. It should be noted that the above configuration indication information may not include the second 5QI, and the second network entity may independently select an existing data flow with a higher priority on the second access path.

[0092] In the above or below embodiments, there is no limitation on how the second network entity determines the second access path. In an optional embodiment, the multiple access paths are two, denoted as the first access path and the second access path. In an optional embodiment, the multiple access paths are more than two, including the first access path and other access paths, and the second network entity may select the second access path from other access paths other than the first access path. Methods for selecting the second access path include, but are not limited to:

[0093] Method B1: randomly select one of the other access paths as the second access path.

[0094] Method B2: Measure the QoS of access paths other than the first access path, and based on the QoS of the other access paths, select an access path whose QoS meets preset conditions as the second access path. For example, an access path whose QoS is greater than a set threshold can be selected as the second access path. QoS can specifically refer to multiple indicator parameters, including but not limited to latency, jitter, packet loss rate, path load, transmission rate, etc. Specifically, an access path with a lighter path load can be selected as the second access path, or an access path with a faster transmission rate can be selected as the second access path, or an access path with a lower packet loss rate can be selected as the second access path, and so on.

[0095] In the above embodiments of the present application, the implementation forms of the first network entity, the second network entity, the third network entity and each message are not limited, and can be flexibly determined according to the standard of the mobile communication network. In the following embodiments, the 5G network will be taken as an example, and the multi-path redundant transmission method provided in the embodiments of the present application will be exemplified in combination with specific network entities and specific message formats. In the following scenario embodiment, the first network entity is SMF, the second network entity is UPF, and the third network entity is PCF. The first message is a PDU session establishment / modification request message, the second message is an N4 session establishment / modification request message, the third message is an N4 session establishment / modification response message, the fourth message is a PDU session establishment / modification response message, the fifth message is a PCF session management policy control update request message (Npcf_SMPolicyControl_Updaterequest), and the sixth message is a PCF session management policy control update response message (Npcf_SMPolicyControl_Updateresponse); the ninth message is a QoE control signal frame (QoE_STATUS_SIGNAL frame). Furthermore, in the following scenario embodiments, an example is given in which the first access path is a non-3GPP access path and the second access path is a 3GPP access path.

[0096] Figure 3a FIG. 1 is a flow chart of another interactive process of a multi-path redundant transmission method provided by an exemplary embodiment of the present application. Figure 3a As shown, the method includes:

[0097] 31a. The upper layer application in the UE establishes a communication connection with the application server (AS) and has applied to complete the establishment of the MA PDU session.

[0098] 32a. The UE sends a PDU session modification request message to the SMF, which carries the second indication information that the MA PDU session supports redundant transmission mode and the first indication information requesting the use of asynchronous redundant transmission mode.

[0099] It is noted here that, when the MA PDU session has been established, the UE can request the use of the asynchronous redundant transmission mode during the modification process of the MA PDU session. In addition, when the MA PDU session has not been established, the UE can request the use of the asynchronous redundant transmission mode during the MA PDU session establishment process. In this case, a PDU session establishment request message (PDU session establishment request) can be sent to the SMF, which carries the second indication information that the MA PDU session supports the redundant transmission mode, and the first indication information requesting the use of the asynchronous redundant transmission mode.

[0100] 33a. The SMF sends a PCF session management policy control update request message (Npcf_SMPolicyControl_Update request) to the PCF. The message includes first indication information requesting to use the asynchronous redundant transmission mode, so as to query the PCF whether the asynchronous redundant transmission mode can be executed.

[0101] 34a. Based on the policy and charging control rule, the PCF determines that the asynchronous redundant transmission mode can be implemented and returns a PCF session management policy control update response message (Npcf_SMPolicyControl_Update response) to the SMF. This message includes configuration information for asynchronous redundant transmission of unacknowledged data packets on the non-3GPP access path (configuration of unack QoS flow) and trigger parameters required for the asynchronous redundant transmission mode, such as the delay difference between the two access paths. Specifically, the policy and charging control rules in the PCF may include rules supporting multi-path synchronous redundant transmission (redundant steering mode) and rules supporting multi-path asynchronous redundant transmission (re-injection mode).

[0102] It is noted here that any one or both of the above-mentioned configuration indication information and trigger parameters can also be configured locally by the SMF. Please refer to the description in the above-mentioned embodiment and will not be repeated here.

[0103] 35a. SMF sends an N4 session establishment / modification request message (N4session establishment / modification request) to UPF. The request message includes the N4 rule and the above-mentioned configuration indication information. The N4 rule includes the above-mentioned trigger parameters, such as the delay difference between the two access paths.

[0104] Further optionally, the N4 rule also includes: path selection criteria, an identifier of the initial activation / deactivation of the redundant transmission mode, and measurement assistance information for triggering the redundant transmission mechanism.

[0105] 36a. The UPF configures a QoS data flow for unacknowledged data packets on the non-3GPP access path on the 3GPP access path according to the configuration indication information, and caches the unacknowledged data packets on the non-3GPP access path into the configured QoS data flow according to the trigger parameters for retransmission on the 3GPP access path.

[0106] Specifically, the trigger parameter represents the delay difference for transmitting data packets between the two access paths. The UPF can monitor the delay difference for transmitting data packets between the non-3GPP access path and the 3GPP access path, and treat the data packets sent on the non-3GPP access path during the period when the delay difference exceeds the set threshold as unconfirmed data packets that need to be asynchronously retransmitted. These data packets usually cannot receive the confirmation message returned by the UE in time due to the large delay difference.

[0107] 37a. UPF sends an N4 session establishment or modification response message (N4session establishment / modification response) to SMF.

[0108] 38a. SMF sends a PDU session establishment / modification response message (PDU session establishment / modification response) to the UE, which includes the N4 rule and the above-mentioned configuration indication information. The N4 rule includes the above-mentioned trigger parameters.

[0109] Optionally, the N4 rule can be configured by the SMF based on the ATSSS rule, and the ATSSS rule can be obtained by the SMF through the PCF. Specifically, the ATSSS rule can be included in the policy and charging control rules in the PCF, which can include rules supporting multi-path synchronous redundant transmission (redundant steering mode) and rules supporting multi-path asynchronous redundant transmission (re-injection mode).

[0110] 39a. After receiving the PDU session establishment / modification response message, the UE configures the tunnel client corresponding to the MA PDU session. The tunnel client corresponds to the tunnel server in the UPF, and the two work together to complete the MA PDU session process.

[0111] 40a. In the asynchronous redundant transmission mode, the UE re-receives the unacknowledged data packet on the non-3GPP access path on the 3GPP access path.

[0112] Furthermore, when the delay difference falls below the threshold again, the UPF can transmit different data packets to the UE on the non-3GPP access path and the 3GPP access path, respectively. This is equivalent to deactivating the asynchronous redundant retransmission mode. Accordingly, the UE can receive different data packets on the two access paths, improving data packet transmission efficiency. In other words, as the delay difference changes, when the delay difference is large, the UPF activates the asynchronous redundant retransmission mode. When the delay difference becomes smaller again, the UPF can deactivate the asynchronous redundant retransmission mode.

[0113] Figure 3b FIG. 1 is a flow chart of another interactive process of a multi-path redundant transmission method provided by an exemplary embodiment of the present application. Figure 3b As shown, the method includes:

[0114] 31b. The upper layer application in the UE establishes a communication connection with the application server (AS) and applies to establish an MA PDU session.

[0115] 32b. The UE sends a PDU session establishment request message (PDU session establishment request) to the SMF, which carries the second indication information that the MA PDU session supports redundant transmission mode (support for redundant mode) and the first indication information requesting the use of asynchronous redundant transmission mode (re-injection mode).

[0116] It is noted that, when the MA PDU session is not established, the UE may request the use of the asynchronous redundant transmission mode during the MA PDU session establishment process. In addition, when the MA PDU session has been established, the UE may request the use of the asynchronous redundant transmission mode during the MA PDU session modification process. In this case, a PDU session modification request message may be sent to the SMF. The message carries the second indication information that the MA PDU session supports the redundant transmission mode, and the first indication information requesting the use of the asynchronous redundant transmission mode.

[0117] 33b. The SMF determines configuration indication information (configuration of unack QoS flow) for performing asynchronous redundant transmission on unacknowledged data packets on the non-3GPP access path according to the second indication information and the first indication information requesting to use the asynchronous redundant transmission mode.

[0118] Optionally, the SMF may also send a PCF session management policy control update request message (Npcf_SMPolicyControl_Update request) to the PCF, which includes first indication information for the asynchronous redundant transmission mode, to query the PCF whether the asynchronous redundant transmission mode can be implemented. The PCF determines that the asynchronous redundant transmission mode can be implemented based on the policy and charging control rule (Policy and Charging Control Rule) and returns a PCF session management policy control update response message (Npcf_SMPolicyControl_Update response) to the SMF. In this embodiment, the Npcf_SMPolicyControl_Update response message may not include the above-mentioned configuration indication information.

[0119] 34b. SMF sends an N4 session establishment / modification request message (N4session establishment / modification request) to UPF, which includes N4 rules and the above-mentioned configuration indication information. The N4 rules include path selection rules (including selection criteria), the initial activation / or deactivation of the redundant transmission mode (initial activated / deactivated), and measurement assistance information (Measurement assistance information) for triggering the redundant transmission mechanism.

[0120] 35b. UPF sends an N4 session establishment or modification response message (N4session establishment / modification response) to SMF.

[0121] 36b. SMF sends a PDU session establishment / modification response message to the UE, which includes the N4 rule and the above configuration indication information.

[0122] 37b. After receiving the PDU session establishment / modification response message, the UE configures the tunnel client corresponding to the MA P DU session. The tunnel client corresponds to the tunnel server in the UPF, and the two work together to complete the MA P DU session process.

[0123] 38b. The UE sends an indication from the MP-QUIC / DCCP layer for triggering re-injection mode to the UPF.

[0124] 39b. The UPF configures a QoS data flow for unconfirmed data packets on the non-3GPP access path on the 3GPP access path according to the above configuration indication information, and caches the unconfirmed data packets on the non-3GPP access path into the configured QoS data flow according to the above trigger indication for retransmission on the 3GPP access path.

[0125] When the UPF receives a trigger indication provided by the application layer, it treats the data packets that have been transmitted on the non-3GPP access path and for which no confirmation message has been received before the trigger indication arrives as unconfirmed data packets that need to be asynchronously retransmitted, and caches them in the first data stream for asynchronous redundant transmission through the second access path.

[0126] 40b. In the asynchronous redundant transmission mode, the UE re-receives the unacknowledged data packet on the non-3GPP access path on the 3GPP access path.

[0127] Furthermore, after caching the unacknowledged data packet in the first data stream, or after asynchronously redundantly transmitting all the unacknowledged data packets through the 3GPP access path, the UPF can retransmit different data packets to the UE on the two access paths. This is equivalent to deactivating the asynchronous redundant retransmission mode. Using two access paths to simultaneously transmit different data packets is beneficial to improving data packet transmission efficiency. In other words, the application layer can provide a trigger indication to the UPF on demand (when a last-come-first-served problem occurs), so that the UPF dynamically activates / deactivates the asynchronous redundant retransmission mode.

[0128] In the above embodiment of the present application, during the establishment or modification of the PDU session, the UE requests asynchronous redundant transmission from the SMF. After confirmation by the PCF, the SMF configures the UPF to perform QoS data flow and trigger parameters for asynchronous redundant transmission, or the upper layer application or application layer transmission protocol provides trigger parameters or trigger indications, so that multi-path-based asynchronous redundant transmission is implemented between the UE and the UPF, which allows the UE to effectively solve the multi-path late-arrival problem in downlink transmission, obtain the corresponding data packet as soon as possible, and improve the user's QoE for data streams, especially data streams with high real-time requirements. Specifically, the trigger mechanism of the application layer transmission protocol can be the signaling QoE status signaling (QoE_STATUS_SIGNAL) in the MP-QUIC scheduling protocol. The QoE status signaling can carry the cache packet sequence status of the downlink data packet received by the UE. The UPF can trigger asynchronous redundant transmission based on the QoS status signaling.

[0129] Figure 4a A flowchart of another multi-path redundant transmission method provided by an exemplary embodiment of the present application is provided. This method is described from the perspective of the UE, such as Figure 4a As shown, the method includes:

[0130] 41a. Send a first message to a first network entity, the first message including at least first indication information of a request for an MA PDU session to use an asynchronous redundant transmission mode, so that the first network entity sends a second message to a second network entity, the asynchronous redundant transmission mode being one of the redundant transmission modes;

[0131] 42a. Receive a fourth message returned by the first network entity, where the second message and the fourth message include at least configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, so that the second network entity performs asynchronous redundant transmission of unconfirmed data packets on the first access path through the second access path according to the above configuration indication information.

[0132] In an optional embodiment, the fourth message further includes: a trigger parameter of an asynchronous redundant transmission mode, which trigger parameter is used for the second network entity to identify unconfirmed data packets on the first access path, and the unconfirmed data packets refer to data packets sent during a period when the delay difference represented by the trigger parameter exceeds a set threshold.

[0133] In an optional embodiment, the method of this embodiment further includes: sending a seventh message to the first network entity to request the first network entity to configure the trigger parameters; and receiving an eighth message returned by the first network entity, where the eighth message includes the configured trigger parameters.

[0134] In an optional embodiment, the first message further includes: second indication information that the MA PDU session supports redundant transmission mode.

[0135] In an optional embodiment, the method of this embodiment further includes: sending a trigger indication of an asynchronous redundant transmission mode to the second network entity so that the second network entity can identify unconfirmed data packets on the first access path, wherein the unconfirmed data packets refer to data packets for which no confirmation message has been received before the trigger indication arrives.

[0136] In an optional embodiment, the configuration indication information is used to instruct configuration of a first data flow for unacknowledged data packets on the first access path on the second access path.

[0137] The detailed implementation of each of the above steps can be found in the relevant description in the above embodiments and will not be repeated here.

[0138] Figure 4b A flowchart of another multi-path redundant transmission method provided by an exemplary embodiment of the present application is provided. The method is described from the perspective of the first network entity, such as Figure 4b As shown, the method includes:

[0139] 41b. Receive a first message sent by the UE, where the first message includes at least first indication information that the MA PDU session requests to use an asynchronous redundant transmission mode, where the asynchronous redundant transmission mode is one of the redundant transmission modes;

[0140] 42b. Determine, according to the first instruction information requesting to use the asynchronous redundant transmission mode, configuration instruction information for performing asynchronous redundant transmission on unacknowledged data packets on the first access path;

[0141] 43b. Send a second message to the second network entity and send a fourth message to the UE, where the second message and the fourth message include at least the above-mentioned configuration indication information, so that the second network entity performs asynchronous redundant transmission of unconfirmed data packets on the first access path through the second access path.

[0142] In an optional embodiment, the second message further includes a trigger parameter for the asynchronous redundant transmission mode. Based on this, the method of this embodiment further includes determining the trigger parameter for the asynchronous redundant transmission mode based on the first indication information requesting the use of the asynchronous redundant transmission mode, where the trigger parameter is used by the second network entity to identify unacknowledged data packets on the first access path.

[0143] In an optional embodiment, before determining the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path based on the first indication information requesting the use of the asynchronous redundant transmission mode, the method further includes: sending a fifth message to a third network entity, the fifth message including at least the first indication information requesting the use of the asynchronous redundant transmission mode, so that the third network entity confirms whether the asynchronous redundant transmission mode can be executed; and receiving a sixth message sent by the third network entity, the sixth message indicating that the asynchronous redundant transmission mode can be executed.

[0144] In an optional embodiment, the sixth message includes at least one of the configuration indication information and the trigger parameter. Based on this, determining the configuration indication information for asynchronous redundant transmission of unacknowledged data packets on the first access path and the trigger parameter for the asynchronous redundant transmission mode according to the first indication information requesting the use of the asynchronous redundant transmission mode includes: obtaining at least one of the configuration indication information and the trigger parameter from the sixth message and, if one of the information is obtained from the sixth message, locally configuring the other; or, locally configuring the configuration indication information and the trigger parameter according to the first indication information requesting the use of the asynchronous redundant transmission mode.

[0145] In an optional embodiment, the configuration indication information is used to instruct configuration of a first data flow for unacknowledged data packets on the first access path on the second access path.

[0146] The detailed implementation of each of the above steps can be found in the relevant description in the above embodiments and will not be repeated here.

[0147] Figure 4c A flowchart of another multi-path redundant transmission method provided by an exemplary embodiment of the present application is provided. The method is described from the perspective of the second network entity, such as Figure 4c As shown, the method includes:

[0148] 41c. Receive a second message sent by the first network entity, where the second message includes at least configuration instruction information for asynchronous redundant transmission of unacknowledged data packets on the first access path, and the MA PDU session corresponding to the first access path requests to use the asynchronous redundant transmission mode;

[0149] 42c. Configure, on the second access path, a first data flow for unacknowledged data packets on the first access path according to the configuration instruction information;

[0150] 43c. Buffer the unacknowledged data packets on the first access path into the first data flow for asynchronous redundant transmission through the second access path, where the second access path is another access path corresponding to the MA PDU session.

[0151] In an optional embodiment, the above-mentioned caching of unconfirmed data packets on the first access path into the first data stream for asynchronous redundant transmission through the second access path includes: identifying unconfirmed data packets on the first access path according to trigger parameters and / or trigger indications of the asynchronous redundant transmission mode; and caching the identified unconfirmed data packets into the first data stream for asynchronous redundant transmission through the second access path.

[0152] In an optional embodiment, this embodiment also includes: obtaining trigger parameters and / or trigger indications of the asynchronous redundant transmission mode, and the acquisition operation includes at least one of the following methods: obtaining trigger parameters from the second message; receiving trigger parameters sent by the application layer; receiving trigger indications sent by the application layer.

[0153] In an optional embodiment, the above-mentioned identification of unconfirmed data packets on the first access path based on trigger parameters and / or trigger indications includes: treating data packets sent on the first access path during a period when the delay difference represented by the trigger parameters exceeds a set threshold as unconfirmed data packets; and / or treating data packets on the first access path for which no confirmation message is received before the trigger indication arrives as unconfirmed data packets.

[0154] In an optional embodiment, before configuring the first data flow for the unconfirmed data packets on the first access path on the second access path, the method further includes: measuring the QoS of other access paths other than the first access path; and selecting an access path whose QoS meets preset conditions as the second access path based on the QoS of the other access paths.

[0155] The detailed implementation of each of the above steps can be found in the relevant description in the above embodiments and will not be repeated here.

[0156] It should be noted that in some of the processes described in the above embodiments and the accompanying drawings, multiple operations that appear in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this article or may be executed in parallel. The sequence numbers of the operations, such as 21a, 22a, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions of "first", "second", etc. in this article are used to distinguish different messages, devices, modules, etc., and do not represent a sequential order, nor do they limit "first" and "second" to being different types.

[0157] Figure 5a This is a structural diagram of a multi-path redundant transmission device provided by another exemplary embodiment of the present application. The device can be applied to UE, such as Figure 5aAs shown, the device includes: a sending module 51a and a receiving module 52a.

[0158] a sending module 51a, configured to send a first message to a first network entity, the first message including at least first indication information requesting the MA PDU session to use an asynchronous redundant transmission mode, so that the first network entity sends a second message to a second network entity, the asynchronous redundant transmission mode being one of the redundant transmission modes;

[0159] The receiving module 52a is used to receive a fourth message returned by the first network entity, where the second message and the fourth message include at least configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, so that the second network entity performs asynchronous redundant transmission of unconfirmed data packets on the first access path through the second access path according to the above configuration indication information.

[0160] In an optional embodiment, the fourth message further includes: a trigger parameter of an asynchronous redundant transmission mode, which trigger parameter is used for the second network entity to identify unconfirmed data packets on the first access path, and the unconfirmed data packets refer to data packets sent during a period when the delay difference represented by the trigger parameter exceeds a set threshold.

[0161] In an optional embodiment, the sending module 51a is further used to: send a seventh message to the first network entity to request the first network entity to configure the trigger parameters; the receiving module 52a is further used to: receive an eighth message returned by the first network entity, the eighth message including the configured trigger parameters.

[0162] In an optional embodiment, the first message further includes: second indication information that the MA PDU session supports redundant transmission mode.

[0163] In an optional embodiment, the sending module 51a is further used to: send a trigger indication of the asynchronous redundant transmission mode to the second network entity, so that the second network entity can identify unconfirmed data packets on the first access path, and the unconfirmed data packets refer to data packets for which no confirmation message has been received before the trigger indication arrives.

[0164] In an optional embodiment, the configuration indication information is used to instruct configuration of a first data flow for unacknowledged data packets on the first access path on the second access path.

[0165] Figure 5b This is a structural diagram of another multi-path redundant transmission device provided by an exemplary embodiment of the present application. Figure 5b As shown, the device includes: a sending module 51b, a receiving module 52b and a determining module 53b.

[0166] A receiving module 52b is configured to receive a first message sent by the UE, where the first message includes at least first indication information of a MA PDU session requesting to use an asynchronous redundant transmission mode, where the asynchronous redundant transmission mode is one of the redundant transmission modes;

[0167] The determining module 53b is configured to determine, according to the first indication information requesting to use the asynchronous redundant transmission mode, configuration indication information for performing asynchronous redundant transmission on unacknowledged data packets on the first access path;

[0168] The sending module 51b is used to send a second message to the second network entity and send a fourth message to the UE, where the second message and the fourth message include at least the above-mentioned configuration indication information, so that the second network entity performs asynchronous redundant transmission of unconfirmed data packets on the first access path through the second access path.

[0169] In an optional embodiment, the second message further includes a trigger parameter for the asynchronous redundant transmission mode. Based on this, the determination module 53b is further configured to determine the trigger parameter for the asynchronous redundant transmission mode based on the first indication information requesting the use of the asynchronous redundant transmission mode, where the trigger parameter is used by the second network entity to identify unacknowledged data packets on the first access path.

[0170] In an optional embodiment, the sending module 51b is further configured to, before determining the configuration indication information for asynchronous redundant transmission of unacknowledged data packets on the first access path, send a fifth message to the third network entity, where the fifth message includes at least the first indication information requesting the use of the asynchronous redundant transmission mode, so that the third network entity can confirm whether the asynchronous redundant transmission mode can be used. Accordingly, the receiving module 52b is further configured to receive a sixth message sent by the third network entity, where the sixth message indicates that the asynchronous redundant transmission mode can be used.

[0171] In an optional embodiment, the sixth message includes at least one of the configuration indication information and the trigger parameter. Based on this, when determining the configuration indication information for performing asynchronous redundant transmission of unacknowledged data packets on the first access path and the trigger parameter for the asynchronous redundant transmission mode, the determination module 53b is specifically configured to: obtain at least one of the configuration indication information and the trigger parameter from the sixth message, and if one of the information is obtained from the sixth message, locally configure the other; or, based on the request, locally configure the configuration indication information and the trigger parameter using the first indication information for the asynchronous redundant transmission mode.

[0172] In an optional embodiment, the configuration indication information is used to instruct configuration of a first data flow for unacknowledged data packets on the first access path on the second access path.

[0173] Figure 5cThis is a structural diagram of another multi-path redundant transmission device provided by an exemplary embodiment of the present application. Figure 5c As shown, the device includes: a sending module 51c, a receiving module 52c and a configuration module 53c.

[0174] a receiving module 52c, configured to receive a second message sent by the first network entity, the second message including at least configuration instruction information for asynchronous redundant transmission of unacknowledged data packets on the first access path, the MA PDU session corresponding to the first access path requesting the use of the asynchronous redundant transmission mode;

[0175] a configuration module 53c, configured to configure, on the second access path, a first data flow for unacknowledged data packets on the first access path according to the configuration indication information;

[0176] The sending module 51c is configured to buffer the unacknowledged data packets on the first access path into the first data flow for asynchronous redundant transmission via the second access path, where the second access path is another access path corresponding to the MA PDU session.

[0177] In an optional embodiment, the sending module 51c is specifically used to: identify unconfirmed data packets on the first access path according to the trigger parameters and / or trigger indications of the asynchronous redundant transmission mode; cache the identified unconfirmed data packets into the first data stream for asynchronous redundant transmission through the second access path.

[0178] In an optional embodiment, the receiving module 52c is further used to: obtain trigger parameters and / or trigger indications of the asynchronous redundant transmission mode, and the acquisition operation includes at least one of the following methods: obtaining trigger parameters from the second message; receiving trigger parameters sent by the application layer; receiving trigger indications sent by the application layer.

[0179] In an optional embodiment, when the sending module 51c identifies unconfirmed data packets on the first access path based on the trigger parameters and / or the trigger indication, it is specifically used to: treat the data packets sent on the first access path during the period when the delay difference represented by the trigger parameters exceeds the set threshold as unconfirmed data packets; and / or, treat the data packets on the first access path for which no confirmation message is received before the trigger indication arrives as unconfirmed data packets.

[0180] In an optional embodiment, before configuring the first data flow for the unconfirmed data packets on the first access path on the second access path, the method further includes: measuring the QoS of other access paths other than the first access path; and selecting an access path whose QoS meets preset conditions as the second access path based on the QoS of the other access paths.

[0181] Figure 6aA schematic diagram of the structure of a user equipment provided by an exemplary embodiment of the present application is shown in FIG. Figure 6a As shown, the user equipment includes: a memory 61a, a processor 62a and a communication component 63a.

[0182] The memory 61a is used to store computer programs and can be configured to store various other data to support operations on the user device. Examples of such data include instructions for any application or method operating on the user device, contact data, phone book data, messages, pictures, videos, etc.

[0183] The processor 62a is coupled to the memory 61a and is configured to execute a computer program in the memory 61a, so as to: send a first message to the first network entity through the communication component 63a, where the first message includes at least first indication information of a MA PDU session requesting use of an asynchronous redundant transmission mode, so that the first network entity sends a second message to the second network entity, where the asynchronous redundant transmission mode is one of the redundant transmission modes; and receive a fourth message returned by the first network entity through the communication component 63a, where the second message and the fourth message include at least configuration indication information for performing asynchronous redundant transmission on unconfirmed data packets on the first access path, so that the second network entity performs asynchronous redundant transmission on the unconfirmed data packets on the first access path through the second access path according to the above configuration indication information.

[0184] In an optional embodiment, the fourth message further includes: a trigger parameter of an asynchronous redundant transmission mode, which trigger parameter is used for the second network entity to identify unconfirmed data packets on the first access path, and the unconfirmed data packets refer to data packets sent during a period when the delay difference represented by the trigger parameter exceeds a set threshold.

[0185] In an optional embodiment, the processor 62a is further configured to: send a seventh message to the first network entity through the communication component 63a to request the first network entity to configure the trigger parameters; and receive an eighth message returned by the first network entity, where the eighth message includes the configured trigger parameters.

[0186] In an optional embodiment, the first message further includes: second indication information that the MA PDU session supports redundant transmission mode.

[0187] In an optional embodiment, the processor 62a is further used to: send a trigger indication of the asynchronous redundant transmission mode to the second network entity through the communication component 63a, so that the second network entity can identify unconfirmed data packets on the first access path, and the unconfirmed data packets refer to data packets for which no confirmation message has been received before the trigger indication arrives.

[0188] In an optional embodiment, the configuration indication information is used to instruct configuration of a first data flow for unacknowledged data packets on the first access path on the second access path.

[0189] The detailed implementation of the above operations can be found in the relevant descriptions in the above embodiments and will not be repeated here.

[0190] Further, if Figure 6a As shown, the user device also includes: a display 64a, a power component 65a, an audio component 66a and other components. Figure 6a Only some components are shown schematically, which does not mean that the user equipment only includes Figure 6a Components shown.

[0191] Accordingly, an embodiment of the present application also provides a computer-readable storage medium storing a computer program / instruction. When the computer program / instruction is executed by a processor, the processor is enabled to implement the steps that can be executed by the UE in the above method embodiment.

[0192] Figure 6b This is a schematic diagram of the structure of a network entity provided by an exemplary embodiment of the present application. The network entity can be implemented as the first network entity in the aforementioned embodiment, such as Figure 6b As shown, the user equipment includes: a memory 61b, a processor 62b and a communication component 63b. Figure 6b As shown, the network entity further includes a power supply component 64b.

[0193] The processor 62b is coupled to the memory 61b and is configured to execute a computer program in the memory 61b, so as to: receive, through the communication component 63b, a first message sent by the UE, where the first message includes at least first indication information requesting the use of an asynchronous redundant transmission mode for the MA PDU session, where the asynchronous redundant transmission mode is one of the redundant transmission modes; determine, based on the first indication information requesting the use of the asynchronous redundant transmission mode, configuration indication information for performing asynchronous redundant transmission on unacknowledged data packets on the first access path; and send a second message to the second network entity and a fourth message to the UE, where the second message and the fourth message include at least the above-mentioned configuration indication information, so that the second network entity performs asynchronous redundant transmission on the unacknowledged data packets on the first access path through the second access path.

[0194] In an optional embodiment, the second message further includes a trigger parameter for the asynchronous redundant transmission mode. Based on this, the processor 62b is further configured to determine the trigger parameter for the asynchronous redundant transmission mode according to the first indication information requesting the use of the asynchronous redundant transmission mode, where the trigger parameter is used by the second network entity to identify unacknowledged data packets on the first access path.

[0195] In an optional embodiment, the processor 62b is further used to: send a fifth message to the third network entity through the communication component 63b, where the fifth message includes at least first indication information requesting the use of the asynchronous redundant transmission mode, so that the third network entity confirms whether the asynchronous redundant transmission mode can be executed; and receive a sixth message sent by the third network entity, where the sixth message indicates that the asynchronous redundant transmission mode can be executed.

[0196] In an optional embodiment, the sixth message includes at least one of the configuration indication information and the trigger parameter. Based on this, when determining the configuration indication information for performing asynchronous redundant transmission of unacknowledged data packets on the first access path and the trigger parameter for the asynchronous redundant transmission mode, the processor 62b is specifically configured to: obtain at least one of the configuration indication information and the trigger parameter from the sixth message, and if one of the information is obtained from the sixth message, locally configure the other; or, based on the request, locally configure the configuration indication information and the trigger parameter using the first indication information for the asynchronous redundant transmission mode.

[0197] In an optional embodiment, the configuration indication information is used to instruct configuration of a first data flow for unacknowledged data packets on the first access path on the second access path.

[0198] The detailed implementation of the above operations can be found in the relevant descriptions in the above embodiments and will not be repeated here.

[0199] Accordingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program / instruction. When the computer program / instruction is executed by a processor, the processor is enabled to implement the steps that can be performed by the first network entity in the above method embodiment.

[0200] Figure 6c This is a schematic diagram of the structure of another network entity provided by an exemplary embodiment of the present application. The network entity can be implemented as the second network entity in the aforementioned embodiment, such as Figure 6c As shown, the user equipment includes: a memory 61c, a processor 62c and a communication component 63c. Figure 6c As shown, the network entity further includes a power supply component 64c.

[0201] The processor 62c is coupled to the memory 61c and is configured to execute a computer program in the memory 61c, so as to: receive, through the communication component 63c, a second message sent by the first network entity, where the second message includes at least configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, and the MA PDU session corresponding to the first access path requests to use the asynchronous redundant transmission mode; configure, on the second access path according to the above configuration indication information, a first data stream for the unconfirmed data packets on the first access path; and cache the unconfirmed data packets on the first access path into the first data stream for asynchronous redundant transmission through the second access path, where the second access path is another access path corresponding to the MA PDU session.

[0202] In an optional embodiment, when the processor 62c caches the unconfirmed data packets on the first access path into the first data stream for asynchronous redundant transmission through the second access path, it is specifically used to: identify the unconfirmed data packets on the first access path according to the trigger parameters and / or trigger indications of the asynchronous redundant transmission mode; and cache the identified unconfirmed data packets into the first data stream for asynchronous redundant transmission through the second access path.

[0203] In an optional embodiment, the processor 62c is further used to: obtain trigger parameters and / or trigger indications of the asynchronous redundant transmission mode, and the acquisition operation includes at least one of the following methods: obtaining trigger parameters from the second message; receiving trigger parameters sent by the application layer; receiving trigger indications sent by the application layer.

[0204] In an optional embodiment, when the processor 62c identifies unconfirmed data packets on the first access path based on the trigger parameters and / or the trigger indication, it is specifically used to: treat the data packets sent on the first access path during the period when the delay difference represented by the trigger parameters exceeds the set threshold as unconfirmed data packets; and / or, treat the data packets on the first access path for which no confirmation message is received before the trigger indication arrives as unconfirmed data packets.

[0205] In an optional embodiment, the processor 62c is further configured to: measure the QoS of other access paths except the first access path; and select, based on the QoS of other access paths, an access path whose QoS meets a preset condition as the second access path.

[0206] The detailed implementation of the above operations can be found in the relevant descriptions in the above embodiments and will not be repeated here.

[0207] Accordingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program / instruction. When the computer program / instruction is executed by a processor, the processor is enabled to implement the steps that can be performed by the second network entity in the above method embodiment.

[0208] The memory in the above embodiments can be implemented by any type of volatile or non-volatile memory device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0209] The communication component in each of the above embodiments is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0210] The display in each of the above embodiments includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0211] The power supply assembly in each of the above embodiments provides power to various components of the device in which the power supply assembly is located. The power supply assembly may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which the power supply assembly is located.

[0212] The audio components in the above embodiments may be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), and when the device where the audio component is located is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal. The received audio signal may be further stored in a memory or sent via a communication component. In some embodiments, the audio component further includes a speaker for outputting an audio signal.

[0213] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0214] The present application is described with reference to the flow chart and / or block diagram of the method, device (system), and computer program product according to the embodiment of the present application. It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processing machine or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one flow chart flow or multiple flows and / or one box or multiple boxes of the block diagram.

[0215] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0216] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0217] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0218] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0219] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0220] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0221] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A multi-path redundant transmission method, applicable to a user device, characterized in that: The method comprises: sending a first message to a first network entity, the first message including at least first indication information of a multi-anchor protocol data unit (MA PDU) session requesting use of an asynchronous redundant transmission mode, so that the first network entity sends a second message to a second network entity, the asynchronous redundant transmission mode being one of the redundant transmission modes; receiving a fourth message returned by the first network entity, where the second message and the fourth message include at least configuration instruction information for performing asynchronous redundant transmission on unacknowledged data packets on the first access path, so that the second network entity performs asynchronous redundant transmission on the unacknowledged data packets on the first access path according to the configuration instruction information through the second access path in activating the asynchronous redundant transmission mode; In which, after the second network entity caches the unconfirmed data packets on the first access path to the first data flow of the second access path, or after asynchronously redundantly transmitting all the unconfirmed data packets on the first access path through the second access path, the second network entity transmits different data packets to the user equipment on the first access path and the second access path respectively to deactivate the asynchronous redundant transmission mode.

2. The method according to claim 1, characterized in that The fourth message also includes: a trigger parameter of the asynchronous redundant transmission mode, wherein the trigger parameter is used for the second network entity to identify unconfirmed data packets on the first access path, and the unconfirmed data packets refer to data packets sent during a period when the delay difference represented by the trigger parameter exceeds a set threshold.

3. The method according to claim 2, characterized in that Also includes: sending a seventh message to the first network entity to request the first network entity to configure the trigger parameter; An eighth message returned by the first network entity is received, where the eighth message includes a configured trigger parameter.

4. The method according to any one of claims 1 to 3, characterized in that The first message also includes: second indication information that the MA PDU session supports redundant transmission mode.

5. The method according to any one of claims 1 to 3, characterized in that Also includes: A trigger indication of the asynchronous redundant transmission mode is sent to the second network entity so that the second network entity can identify unconfirmed data packets on the first access path, where the unconfirmed data packets refer to data packets for which no confirmation message has been received before the trigger indication arrives.

6. The method according to any one of claims 1 to 3, characterized in that Also includes: The configuration indication information is used to instruct configuration of a first data flow for unacknowledged data packets on the first access path on the second access path.

7. A multi-path redundant transmission method, applicable to a first network entity, characterized in that: The method comprises: receiving a first message sent by a user equipment, where the first message includes at least first indication information of a multi-anchor protocol data unit (MA PDU) session requesting use of an asynchronous redundant transmission mode, where the asynchronous redundant transmission mode is one of the redundant transmission modes; Determining, according to the first indication information, configuration indication information for performing asynchronous redundant transmission on unacknowledged data packets on the first access path; sending a second message to a second network entity and sending a fourth message to the user equipment, where the second message and the fourth message include at least the configuration indication information, so that the second network entity performs asynchronous redundant transmission of unacknowledged data packets on the first access path through a second access path in activating the asynchronous redundant transmission mode; In which, after the second network entity caches the unconfirmed data packets on the first access path to the first data flow of the second access path, or after asynchronously redundantly transmitting all the unconfirmed data packets on the first access path through the second access path, the second network entity transmits different data packets to the user equipment on the first access path and the second access path respectively to deactivate the asynchronous redundant transmission mode.

8. The method according to claim 7, characterized in that The second message further includes: a trigger parameter of the asynchronous redundant transmission mode, and the method further includes: According to the first indication information, a trigger parameter of the asynchronous redundant transmission mode is determined, where the trigger parameter is used for the second network entity to identify unconfirmed data packets on the first access path.

9. The method according to claim 8, characterized in that Before determining, according to the first indication information, configuration indication information for performing asynchronous redundant transmission on unacknowledged data packets on the first access path, the method further includes: Sending a fifth message to a third network entity, where the fifth message includes at least the first indication information, so that the third network entity confirms whether the asynchronous redundant transmission mode can be executed; and A sixth message sent by the third network entity is received, where the sixth message indicates that an asynchronous redundant transmission mode can be executed.

10. The method according to claim 9, characterized in that The sixth message includes: at least one of the configuration indication information and the trigger parameter; Determining, according to the first indication information, configuration indication information for performing asynchronous redundant transmission on unacknowledged data packets on the first access path and triggering parameters of the asynchronous redundant transmission mode, including: obtaining at least one of the configuration indication information and the trigger parameter from the sixth message, and locally configuring the other information if one of the information is obtained from the sixth message; or, According to the first indication information, the configuration indication information and the trigger parameter are locally configured.

11. The method according to any one of claims 7 to 10, characterized in that: The configuration indication information is used to instruct configuration of a first data flow for unacknowledged data packets on the first access path on the second access path.

12. A multi-path redundant transmission method, applicable to a second network entity, characterized in that: The method comprises: receiving a second message sent by the first network entity, where the second message includes at least configuration indication information for asynchronous redundant transmission of unacknowledged data packets on the first access path, and a multi-anchor protocol data unit (MA PDU) session corresponding to the first access path requests use of an asynchronous redundant transmission mode; configuring, on a second access path, a first data flow for unacknowledged data packets on the first access path according to the configuration indication information in activating the asynchronous redundant transmission mode; caching unacknowledged data packets on the first access path into the first data flow for asynchronous redundant transmission over the second access path, where the second access path is another access path corresponding to the MA PDU session; After caching the unconfirmed data packets on the first access path to the first data stream, or after all the unconfirmed data packets on the first access path are asynchronously redundantly transmitted through the second access path, different data packets are transmitted to the user equipment on the first access path and the second access path respectively to deactivate the asynchronous redundant transmission mode.

13. The method according to claim 12, characterized in that Buffering unacknowledged data packets on the first access path into the first data flow for asynchronous redundant transmission through the second access path, comprising: identifying unacknowledged data packets on the first access path according to a trigger parameter and / or a trigger indication of the asynchronous redundant transmission mode; The identified unacknowledged data packets are buffered in the first data flow for asynchronous redundant transmission via the second access path.

14. The method according to claim 13, characterized in that Also includes: Acquire the trigger parameter and / or trigger indication of the asynchronous redundant transmission mode, where the acquisition operation includes at least one of the following methods: Acquire the trigger parameter from the second message; Receiving the trigger parameter sent by the application layer; Receive the trigger indication sent by the application layer.

15. The method according to claim 13 or 14, characterized in that Identifying unacknowledged data packets on the first access path according to the trigger parameter and / or the trigger indication includes: treating data packets sent on the first access path during a period when the delay difference represented by the trigger parameter exceeds a set threshold as unacknowledged data packets; and / or The data packets on the first access path for which no confirmation message has been received before the trigger indication arrives are regarded as unconfirmed data packets.

16. The method according to any one of claims 12 to 14, characterized in that: Before configuring a first data flow for unacknowledged data packets on the first access path on the second access path, the method further includes: measuring the quality of service (QoS) of other access paths except the first access path; According to the QoS of the other access paths, an access path whose QoS meets a preset condition is selected as the second access path.

17. A user equipment, characterized in that: include: memory, processors, and communications components; The memory is used to store computer programs; The processor is configured to execute the computer program to implement the steps in the method according to any one of claims 1 to 6.

18. A network entity, implemented as a first network entity, characterized in that: include: memory, processors, and communications components; The memory is used to store computer programs; The processor is configured to execute the computer program to implement the steps in the method according to any one of claims 7 to 11.

19. A network entity implemented as a second network entity, characterized in that: include: memory, processors, and communications components; The memory is used to store computer programs; The processor is configured to execute the computer program to implement the steps of the method according to any one of claims 12 to 16.

20. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the processor is enabled to implement the steps of the method according to any one of claims 1 to 16.

Images