CN115087043A

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

Info

Publication number: CN115087043A
Application number: CN202210489734.5A
Authority: CN
Inventors: 于小博; 邓娟; 刘大鹏
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2022-05-06
Filing date: 2022-05-06
Publication date: 2022-09-20
Also published as: WO2023213281A1

Abstract

The embodiment of the application provides a multi-path redundant transmission method, user equipment, a network entity and a storage medium. In the embodiment of the application, the user equipment and a network entity in a mobile communication network are mutually matched, and the activation and deactivation of asynchronous redundant transmission based on multiple paths are realized aiming at MA PDU conversation, so that the asynchronous redundant transmission of data packets which are transmitted on one access path but cannot be confirmed in time can be carried out on the other access path, the implementation mode of a redundant transmission mechanism is enriched, the problem that the data packets are transmitted before the multiple paths can be effectively solved by the UE in downlink transmission, the corresponding data packets are obtained as soon as possible, and the QoE of a user on data flow, especially on data flow with higher real-time requirement is improved.

Description

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

Technical Field

The present application relates to the field of communications technologies, and in particular, to a multipath redundancy transmission method, a user equipment, a network entity, and a storage medium.

Background

The 3GPP Release 16 adds the functions of Access Traffic Steering, Switching and Splitting (ATSSS). To support the ATSSS feature, the 5G system architecture is extended, and User Equipment (UE) supports one or more steering functions, each of which supports traffic steering, switching, and splitting across 3GPP and non-3GPP accesses.

At present, the ATSSS supports a redundant transmission mode, that is, the same data packet is transmitted on a 3GPP path and a non-3GPP path at the same time, and redundant transmission is performed on the 3GPP path with better Quality of Service (QoS), so that the UE is ensured to obtain the corresponding data packet as soon as possible, and Quality of Experience (QoE) of the data stream is improved.

The existing redundant transmission mode is relatively single in realization, and cannot solve the problem of multi-path forward-backward arrival (multi-path forward of line blocking), wherein the problem of forward-backward arrival refers to that under multi-path transmission, when the transmission delay of one path is obviously longer than that of the other path, a data packet transmitted first on the path is often not received when a data packet transmitted later on the other path arrives, so that the problem of data packet loss or disorder is caused. In order to solve the above problems, a new multipath redundant transmission scheme needs to be provided.

Disclosure of Invention

Aspects of the present disclosure provide a multi-path redundant transmission method, user equipment, a network entity, and a storage medium, so as to provide a new multi-path redundant transmission method, so that a UE can effectively solve a problem of multipath-first transmission in downlink transmission, obtain a corresponding data packet as soon as possible, and improve QoE of a data stream.

The embodiment of the application provides a multi-path redundant transmission method, which is suitable for user equipment, and comprises the following steps: sending a first message to a first network entity, the first message including at least first indication information that a multi-anchor protocol data unit (MA) PDU session requests 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 redundant transmission modes; receiving a fourth message returned by the first network entity, where the second message and the fourth message at least include configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on a first access path, so that the second network entity performs asynchronous redundancy transmission on the unacknowledged data packet on the first access path through a second access path according to the configuration indication information.

The embodiment of the present application further provides a multi-path redundant transmission method, which is applicable to a first network entity, and the method includes: receiving a first message sent by user equipment, wherein the first message at least comprises first indication information of a multi-anchor point protocol data unit (MA) PDU session request using an asynchronous redundancy transmission mode, and the asynchronous redundancy transmission mode is one of redundancy transmission modes; determining configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on a first access path according to the first indication information; and 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 at least include the configuration indication information, so that the second network entity performs asynchronous redundant transmission on an unacknowledged data packet on the first access path through a second access path.

The embodiment of the present application further provides a multi-path redundant transmission method, which is applicable to a second network entity, and the method includes: receiving a second message sent by a first network entity, wherein the second message at least comprises configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on a first access path, and a session request of a multi-anchor protocol data unit (MA PDU) corresponding to the first access path uses an asynchronous redundancy transmission mode; configuring a first data flow aiming at unacknowledged data packets on the first access path on a second access path according to the configuration indication information; and buffering the unacknowledged data packets on the first access path into the first data flow so as to perform asynchronous redundancy transmission through the second access path, wherein the second access path is another access path corresponding to the MA PDU session.

An embodiment of the present application further provides a user equipment, including: a memory, a processor, and a communications component; the memory for storing a computer program; the processor is configured to execute the computer program to implement the steps in the multipath redundant transmission method that can be executed by the user equipment according to the embodiment of the present application.

An embodiment of the present application further provides a network entity, which can be implemented as a first network entity, including: a memory, a processor, and a communications component; the memory for storing a computer program; the processor is configured to execute the computer program to implement the steps in the multipath redundant transmission method that can be performed by the first network entity according to the embodiment of the present application.

An embodiment of the present application further provides a network entity, which can be implemented as a second network entity, including: a memory, a processor, and a communications component; the memory for storing a computer program; the processor is configured to execute the computer program to implement the steps in the multipath redundant transmission method that can be performed by the second network entity according to the embodiment of the present application.

Embodiments of the present application further provide a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to implement the steps in the multipath redundant transmission method provided in the embodiments of the present application.

In the embodiment of the application, the user equipment and a network entity in a mobile communication network are mutually matched, and the activation and deactivation of asynchronous redundant transmission based on multiple paths are realized aiming at MA PDU conversation, so that the asynchronous redundant transmission of data packets which are transmitted on one access path but cannot be confirmed in time can be carried out on the other access path, the implementation mode of a redundant transmission mechanism is enriched, the problem that the data packets are transmitted before the multiple paths can be effectively solved by the UE in downlink transmission, the corresponding data packets are obtained as soon as possible, and the QoE of a user on data flow, especially on data flow with higher real-time requirement is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1a is a schematic diagram of a partial architecture of a mobile communication network according to an exemplary embodiment of the present application;

fig. 1b is a schematic diagram illustrating a transmission status of an asynchronous redundant transmission mode according to an exemplary embodiment of the present application;

fig. 2a is an interaction flow diagram of a multipath redundant transmission method according to an exemplary embodiment of the present application;

fig. 2b is an interaction flow diagram of another multi-path redundant transmission method according to an exemplary embodiment of the present application;

fig. 2c is an interaction flow diagram of another multipath redundant transmission method according to an exemplary embodiment of the present application;

fig. 3a is an interaction flow diagram of another multipath redundant transmission method according to an exemplary embodiment of the present application;

fig. 3b is an interaction flow diagram of another multipath redundant transmission method according to an exemplary embodiment of the present application;

fig. 4a is a schematic flowchart of another multipath redundant transmission method according to an exemplary embodiment of the present application;

fig. 4b is a schematic flowchart of another multipath redundant transmission method according to an exemplary embodiment of the present application;

fig. 4c is a schematic flowchart of another multi-path redundant transmission method according to an exemplary embodiment of the present application;

fig. 5a is a schematic structural diagram of a multipath redundant transmission apparatus according to another exemplary embodiment of the present application;

fig. 5b is a schematic structural diagram of a multipath redundant transmission apparatus according to another exemplary embodiment of the present application;

fig. 5c is a schematic structural diagram of a multipath redundant transmission apparatus according to another exemplary embodiment of the present application;

fig. 6a is a schematic structural diagram of a user equipment according to an exemplary embodiment of the present application;

fig. 6b is a schematic structural diagram of a network entity according to an exemplary embodiment of the present application;

fig. 6c is a schematic structural diagram of another network entity according to an exemplary embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the embodiment of the application, user equipment and a network entity in a mobile communication network are matched with each other, and the activation and deactivation of multi-path-based asynchronous redundant transmission are realized for an MA PDU session, so that data packets which are transmitted on one access path but cannot be confirmed in time can be subjected to asynchronous redundant transmission on the other access path, the realization mode of a redundant transmission mechanism is enriched, the problem of multi-path-based transmission can be effectively solved by UE (user equipment) in downlink transmission, corresponding data packets can be obtained as soon as possible, and the QoE (quality of experience) of a user on data streams, particularly data streams with high real-time requirements is improved.

The mobile communication network of this embodiment includes an access network and a core network, where the access network mainly includes a base station, and the access network may be multiple, and may include, for example, a 3GPP access network and a Non-3GPP (Non-3GPP) access network at the same time; the core network includes, but is not limited to, a number of network entities: authentication Server Function (AUSF), User Plane Function (UPF), Access and Mobility Management Function (AMF), Unified Data Management (UDM), Network open Function (NEF), Session Management Function (SMF), Network Slice Selection Function (NSSF), Network storage Function (NF playback Function, NRF), Policy Control Function (Policy Control Function, PCF), Application layer Function (Application Function, AF), and the like.

In addition, the mobile communication network of the embodiment supports the ATSSS feature, and the ATSSS supports a redundant transmission mode, which may be referred to as a redundant steering mode (redundant steering mode). The redundant transmission mode is a mode in which a packet can be transmitted redundantly over multiple paths. In order to support the sss feature, the system architecture of the mobile communication network according to the embodiment of the present invention is expanded, and as shown in fig. 1a, the UE according to the embodiment of the present invention supports one or more steering functions, such as mptcp (multiproath tcp) function and/or sss-LL and/or MP-quic (multiproath quic) function. Each steering function in the UE supports traffic steering, handover and splitting for multi-path (multi-path) access according to the ATSSS rules provided by the network. For an ethernet-type MA PDU (multi Anchor Protocol Data Unit) session, the ATSSS-LL function is mandatory in the UE. Accordingly, as shown in fig. 1a, the UPF in the embodiment of the present application may support an MPTCP proxy function, which communicates with a PTCP function in the UE by using an MPTCP protocol; the UPF may also support the ATSSS-LL function, similar to the ATSSS-LL function in the UE.

In fig. 1a, in addition to the UPF and the UE, other network entities AMF, SMF and PCF related to redundant transmission are shown. The AMF is responsible for access and mobility management functions of the UE; SMF realizes session management, which supports establishment, modification and release of session, allocation and management of IP address of UE, etc.; the PCF supports a Unified policy framework that governs network behavior, provides policy rules to the control plane for execution, and can access subscription information related to policy formulation in a Unified Data Repository (UDR) function. The UPF is mainly responsible for routing and forwarding user plane Data packets in the core Network, interacts with the SMF through an N4 air interface, executes corresponding processing according to various strategies issued by the SMF, and is used as a session point for interconnecting the core Network and a Data Network (DN).

In the embodiment of the application, a plurality of access paths exist between the UE and the UPF, and the UE and the network entities UPF, AMF, SMF, PCF and the like are mutually matched to realize a multi-path-based redundant transmission process. In fig. 1a, the multiple access paths existing between the UE and the UPF include a 3GPP access path and a non-3GPP access path, which is taken as an example for illustration, but not limited thereto. As communication technology develops, 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 over multiple access paths, but does not limit the specific implementation of redundant transmission of data packets over multiple access paths. Optionally, a specific implementation manner of the redundant transmission mode is a synchronous redundant transmission mode, that is, after the mode is triggered to transmit, the same data packet is transmitted on multiple access paths simultaneously, so as to implement the multipath-based redundant transmission. In addition, an embodiment of the present application further provides an asynchronous-redundancy transmission mode (re-injection mode), which may also be referred to as an asynchronous retransmission mode or a re-caching retransmission mode, and is another specific implementation manner in the redundancy transmission mode, and mainly means that when a data packet transmitted on one access path and failed to receive an acknowledgement from an opposite end in time arrives first, the asynchronous transmission is performed on the data packet that failed to obtain an acknowledgement in time on another access path again on the condition that a data packet transmitted on another access path arrives first, so as to implement multi-path-based redundancy transmission, and a problem of late arrival caused by a data packet transmitted on one access path and not receiving an acknowledgement message returned by the opposite end later is solved. Fig. 1b is a schematic diagram illustrating a transmission state of an asynchronous redundancy transmission mode, in fig. 1b, two ends use the asynchronous redundancy transmission mode, wherein, data packets 1 to 10 are transmitted on a non-3GPP access path, the data packets 1 to 3 and 8 to 10 receive an Acknowledgement (ACK) of an opposite end, but the data packets 4 to 7 sent earlier than the data packets 8 to 10 fail to receive the acknowledgement of the opposite end, and then, asynchronous redundancy retransmission is performed on the other access path, i.e., the 3GPP access path, so as to ensure that the opposite end receives the data packets 4 to 7 in time by virtue of the 3GPP access path having a higher QoS priority.

In this embodiment, the UPF may send a downlink data packet to the UE by using an asynchronous redundancy transfer mode. Similarly, the UE may also send the uplink data packet to the UPF using an asynchronous redundancy transfer mode. In the following embodiments of the present application, an example is mainly taken in which a UPF sends a downlink data packet to a UE in an asynchronous redundancy transmission mode, and the multipath redundancy transmission method provided in the embodiments of the present application is described in detail.

Fig. 2a is an interaction flow diagram of a multipath redundant transmission method according to an exemplary embodiment of the present application. As shown in fig. 2a, the method comprises:

21a, the UE sends a first message to the first network entity, the first message including at least first indication information that the MA PDU session requests to use an asynchronous redundant transport mode, the asynchronous redundant transport mode being one of the redundant transport modes.

22a, after receiving the first message, the first network entity determines configuration indication information for performing asynchronous redundant transmission on an unacknowledged data packet on the first access path according to first indication information requesting to use an asynchronous redundant transmission mode included in the first message.

23a, the first network entity sends a second message to the second network entity, and the second message at least includes the configuration indication information.

24a, after receiving the second message, the second network entity configures, according to the configuration indication information included in the second message, a first data flow for the unacknowledged data packet on the first access path on the second access path.

25a, the second network entity returns a third message to the first network entity to inform the first network entity that the configuration has been completed.

26a, after receiving the third message, the first network entity sends a fourth message to the UE, where the fourth message at least includes the configuration indication information, so that the UE knows that the asynchronous redundancy transmission mode can be used.

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.

28a, the UE re-receives the unacknowledged data packet on the first access path on the second access path in the asynchronous redundancy transfer mode.

In this embodiment, a plurality of access paths exist between the UE and the second network entity, and under a normal condition, the second network entity may transmit different data packets to the UE on the plurality of access paths, so as to exert advantages of the plurality of access paths and improve transmission efficiency of the data packets. However, to exploit the benefits of multi-path redundant transport, the UE may send a first message to the first network entity during creation of a MA PDU session or during modification of a MA PDU session to request packet transmission using asynchronous redundant transport mode of redundant transport modes for the MA PDU session. The first network entity is a network entity responsible for session management, which may be, for example, but not limited to, SMF. The second network entity is a network entity that performs user plane packet forwarding with the UE, and may be, for example and without limitation, a UPF.

Optionally, the first message may only include the first indication information (re-indication mode) requesting to use the asynchronous redundant transmission mode, or may also include the second indication information (indication of support for redundant mode) of the MA PDU session and the first indication information (re-indication mode) requesting to use the asynchronous redundant transmission mode of the MA PDU session, which is not limited herein.

After receiving the first message, the first network entity determines that the UE requests to use the asynchronous redundant transmission mode according to at least first indication information, which is included in the first message and requests to use the asynchronous redundant transmission mode, so that configuration indication information for performing asynchronous retransmission on an unacknowledged data packet on the first access path needs to be generated for the second network entity, so that the second network entity performs related configuration of the asynchronous redundant transmission mode according to the configuration indication information, and sends the configuration indication information to the second network entity through a third message.

In this embodiment, under a normal condition, the second network entity may transmit different data packets to the UE on multiple access paths, so as to exert advantages of the multiple access paths and improve transmission efficiency of the data packets. However, when the problem of forward-backward arrival occurs, that is, when a data packet transmitted on one access path fails to be received in time by the UE, and a data packet forward-backward arrival on the other access path arrives at the UE first, the asynchronous redundancy transmission mode may be triggered. The first access path is an access path currently used by the MA PDU session, and is an access path which is sent to the problem later and is firstly sent to the data packet which is transmitted and cannot be confirmed by the UE in time; correspondingly, the second access path is another access path corresponding to the MA PDU session, is an access path that is sent later and arrives first in the problem, and is used for performing asynchronous redundancy transmission on unacknowledged data packets on the first access path. In this embodiment, the first access path and the second access path are not limited, and the QoS of the second access path is relatively better than that of the first access path, and optionally, the first access path may be a non-3GPP access path, and the second access path is a 3GPP access path. QoS may specifically refer to a plurality of index parameters, including but not limited to delay, jitter, packet loss rate, path load, and the like.

In this embodiment, no matter which access path the second network entity sends the data packet to the UE, the UE needs to return an acknowledgement message within a set time range, and if the acknowledgement message returned by the UE cannot be received in time after sending the data packet for any data packet, the data packet is called an unacknowledged data packet. Accordingly, the unacknowledged data packet on the first access path refers to a data packet which has been transmitted on the first access path but fails to receive an acknowledgement message returned by the UE in time. The data packet which fails to receive the acknowledgement message returned by the UE in time mainly refers to a first-sent data packet which is sent first and then later than a second-sent data packet when a problem occurs.

In order to enable asynchronous redundant transmission (asynchronous redundant transmission may also be referred to as asynchronous retransmission) of an unacknowledged data packet on the first access path using the second access path, after receiving the second message, the second network entity configures, according to the configuration indication information in the second message, a first data flow for the unacknowledged data packet on the first access path on the second access path, where the first data flow is a data flow for performing redundant transmission on the unacknowledged data packet on the first access path, and the data flow is actually a data queue for storing the data packet. The data queue has a higher priority of an access channel, and optionally, in a 5G network, the priority may be characterized by a 5G QoS Identifier (5G QoS Identifier, 5 QI); accordingly, the first data flow may be a 5G QoS data flow, but is not limited thereto. The 5G QoS tag (5QI) is a reference scalar for the specific QoS forwarding behavior (e.g., packet loss rate, packet delay budget) provided to the 5G QoS data flow. This may be achieved in the access network by 5QI referencing the specific parameters of the node, which refer to the parameters that control the QoS forwarding process.

After configuring the first data stream, the second network entity may on the one hand return a third message to the first network entity to inform the first network entity that the asynchronous redundant transmission mode related configuration has been completed. The first network entity sends a fourth message to the UE accordingly, and carries the configuration indication information in the fourth message, so that the UE knows that the UPF has completed the relevant configuration of the asynchronous redundancy transfer mode, and can use the asynchronous redundancy transfer mode. The UE may also be configured with a client for MA PDU sessions to receive packets in asynchronous redundant transmission mode. In another aspect, the second network entity may identify an unacknowledged packet on the first access path and buffer the identified unacknowledged packet into the first data flow for asynchronous redundant transmission over the second access path.

Besides the first data flow, other data flows may exist on the second access path, the data flows have different quality of service indicators (QI), the UPF schedules the data flows according to the quality of service indicators of the data flows, and the data packets in the scheduled data flows can be transmitted on the second access path. Alternatively, in a 5G network, the QI of a data flow may be referred to as a 5QI (5G QoS Identifier). In this embodiment, the implementation manner of the 5QI of the data stream is not limited, but 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, and the higher the priority of the 5QI is, the higher the priority of the corresponding data stream is.

When the first data flow is scheduled, unacknowledged packets on the first access path buffered into the first data flow are retransmitted on the second access path. For the UE, in the asynchronous redundant transmission mode, the unacknowledged data packet on the first access path may be received again on the second access path, so as to implement the asynchronous redundant transmission based on multiple paths, on one hand, the implementation manner of the redundant transmission mechanism is enriched, on the other hand, the UE may effectively solve the problem of multipath late arrival in the downlink transmission, obtain the corresponding data packet as soon as possible, and improve the QoE of the user on the data stream, especially on the data stream with high real-time requirement.

In the embodiments of the present application, the manner in which the first network entity determines the configuration indication information for the asynchronous redundant transmission of the unacknowledged data packet on the first access path is not limited. In an alternative embodiment, the configuration may be local to the first network entity. In another alternative embodiment, the interaction may be performed by the first network entity and a third network entity, the third network entity being responsible for providing the configuration indication information. The third network entity refers to a network entity responsible for policy management, which may be, for example, but not limited to, a PCF.

Further optionally, the first network entity may determine, in addition to the configuration indication information, a trigger parameter corresponding to an asynchronous redundant transmission mode, and provide the trigger parameter to the second network entity. Optionally, the first network entity may carry the trigger parameter in the second message and provide the second message to the second network entity. The trigger parameter is used for the second network entity to identify the unacknowledged data packet on the first access path, which is also an active operation for the asynchronous redundant transmission mode. Alternatively, the triggering parameter may be a delay difference (delay difference) between the two access paths. In this way, after the second network entity transmits the data packet on the first access path each time, the delay difference of transmitting the data packet between the two access paths may be monitored by the second network entity (e.g., UPF), and when the delay difference exceeds a threshold, the data packet transmitted during the period when the delay difference exceeds the threshold is determined to be an unacknowledged data packet that needs to be asynchronously retransmitted, and the unacknowledged data packet is buffered in the first data stream. When the delay difference is lower than the threshold again, the second network entity may transmit different data packets to the UE on the multiple access paths, which is equivalent to deactivating the asynchronous redundancy retransmission mode, and the multiple access paths are used to transmit different data packets at the same time, which is beneficial to improving the data packet transmission efficiency. That is, with the change of the delay difference, when the delay difference is large, the asynchronous redundancy retransmission mode may be activated, and when the delay difference becomes small again, the asynchronous redundancy retransmission mode may be deactivated.

In the embodiments of the present application, a manner in which the first network entity determines the trigger parameter is not limited. In an alternative embodiment, the configuration may be local to the first network entity. In another alternative embodiment, the interaction may be performed by the first network entity and a third network entity, the third network entity being responsible for providing the trigger parameter.

In an optional embodiment, after receiving the first message, the first network entity determines configuration indication information for performing asynchronous redundancy transmission for an unacknowledged data packet on the first access path and a trigger parameter of an asynchronous redundancy transmission mode at the same time. As shown in fig. 2b, this embodiment comprises the following steps:

21b, the UE sends a first message to the first network entity, the first message comprising at least first indication information that the MA PDU session requests to use an asynchronous redundant transport mode, the asynchronous redundant transport mode being one of the redundant transport modes.

22b, after receiving the first message, the first network entity determines configuration indication information for performing asynchronous redundant transmission on an unacknowledged data packet on the first access path and a trigger parameter of the asynchronous redundant transmission mode according to first indication information of a request using an asynchronous redundant transmission mode included in the first message.

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:

mode a 1: after receiving the first message, the first network entity locally configures configuration indication information for performing asynchronous redundant transmission on an unacknowledged data packet on the first access path and trigger parameters of the asynchronous redundant transmission mode according to first indication information requesting to use the asynchronous redundant transmission mode included in the first message.

Mode a 2: after receiving the first message, the first network entity sends a fifth message to the third network entity according to first indication information which is contained in the first message and requests to use an asynchronous redundant transmission mode, wherein the fifth message at least comprises the first indication information which requests to use the asynchronous redundant transmission mode, so that the third network entity confirms whether the asynchronous redundant transmission mode can be executed or not; and receiving a sixth message sent by the third network entity, wherein the sixth message indicates that the asynchronous redundancy transmission mode can be executed; in another aspect, the configuration indication information of the asynchronous redundancy transmission for the unacknowledged data packet on the first access path and the triggering parameter of the asynchronous redundancy transmission mode are also included. And the first network entity analyzes the configuration indication information and the trigger parameter from the sixth message. In the method a2, the configuration indication information and the trigger parameter are both provided by the third network entity.

Mode a 3: after receiving the first message, the first network entity sends a fifth message to the third network entity according to first indication information which is contained in the first message and requests to use an asynchronous redundant transmission mode, wherein the fifth message at least comprises the first indication information which requests to use the asynchronous redundant transmission mode, so that the third network entity confirms whether the asynchronous redundant transmission mode can be executed or not; and receiving a sixth message sent by the third network entity, wherein the sixth message indicates that the asynchronous redundancy transmission mode can be executed; another aspect further includes configuration indication information for asynchronous redundant transmission of unacknowledged data packets on the first access path. The first network entity analyzes the configuration indication information from the sixth message and locally configures the trigger parameter of the asynchronous redundant transmission mode. In the method a3, the configuration indication information is provided by a third network entity, and the trigger parameter is configured locally by the second network entity.

Mode a 4: after receiving the first message, the first network entity sends a fifth message to the third network entity according to first indication information which is contained in the first message and requests to use an asynchronous redundant transmission mode, wherein the fifth message at least comprises the first indication information which requests to use the asynchronous redundant transmission mode, so that the third network entity confirms whether the asynchronous redundant transmission mode can be executed or not; and receiving a sixth message sent by the third network entity, wherein the sixth message indicates that the asynchronous redundancy transmission mode can be executed; another aspect further comprises a triggering parameter for asynchronous redundant transmission mode. The first network entity analyzes the trigger parameter from the sixth message, and locally configures configuration indication information for performing asynchronous redundancy transmission on the unacknowledged data packet on the first access path. In the method a4, the trigger parameter is provided by a third network entity, and the configuration indication information is configured locally by the second network entity.

23b, the first network entity sends a second message to the second network entity, wherein the second message comprises the configuration indication information and the trigger parameter.

And 24b, after receiving the second message, the second network entity configures the first data flow aiming at the unacknowledged data packet on the first access path on the second access path according to the configuration indication information contained in the second message.

25b, the second network entity returns a third message to the first network entity to inform the first network entity that the configuration has been completed.

26b, after receiving the third message, the first network entity sends a fourth message to the UE, where the fourth message includes the configuration indication information and the trigger parameter, so that the UE knows that the asynchronous redundancy transmission mode can be used.

27b, the second network entity identifies an unacknowledged data packet on the first access path according to the trigger parameter contained in the second message, and buffers the identified unacknowledged data packet into the first data stream, so as to perform asynchronous redundancy transmission through the second access path.

Specifically, the trigger parameter indicates a delay difference between two access paths for transmitting a data packet, and the second network entity may monitor the delay difference between the first access path and the second access path for transmitting the data packet, and use a data packet sent on the first access path within a period in which the delay difference exceeds a set threshold as an unacknowledged data packet that needs to be asynchronously retransmitted, where the data packets generally cannot receive an acknowledgement message returned by the UE in time because of a large delay difference.

28b, the UE re-receives the unacknowledged data packet on the first access path on the second access path under the asynchronous redundancy transmission mode.

Further, when the delay difference is lower than the threshold again, the second network entity may transmit different data packets to the UE on the multiple access paths, which is equivalent to deactivating the asynchronous redundancy retransmission mode, and the multiple access paths are used to transmit different data packets at the same time, which is beneficial to improving the data packet transmission efficiency. That is, with the change of the delay difference, when the delay difference is large, the asynchronous redundancy retransmission mode may be activated, and when the delay difference becomes small again, the asynchronous redundancy retransmission mode may be deactivated.

In the above embodiments, the triggering parameter of the asynchronous redundancy transmission mode is provided by the first network entity or the third network entity for illustration, but not limited thereto. The trigger parameter required for triggering the second network entity to identify the unacknowledged data packet on the first access path may also be provided by an application layer or application layer protocol (e.g., MP-QUIC protocol), i.e., the above configuration indication information is provided by the first network entity or the third network entity and provided to the second network entity and the UE respectively through a second message and a fourth message, and the second network entity may further receive the trigger parameter sent by the application layer or application layer protocol (e.g., MP-QUIC protocol) before identifying the unacknowledged data packet on the first access path, and identify the unacknowledged data packet on the first access path according to the trigger parameter provided by the application layer or application layer protocol (e.g., MP-QUIC protocol).

It should be noted that the application layer refers to an upper layer application on the UE, such as APP, or a transport protocol used by the application layer, such as MP-QUIC transport protocol or transport tunnel. The transmission protocol tunnel of the upper application or application layer may configure the trigger parameter of the asynchronous redundant transmission mode by itself, or may send a seventh message to the first network entity to request the first network entity to configure the trigger parameter required by the asynchronous redundant transmission mode; and then, receiving an eighth message returned by the first network entity, and analyzing the trigger parameter configured by the first network entity from the eighth message. Here, the upper layer application (or UE) requests the first network entity to configure trigger parameters required for the asynchronous redundant transmission mode, including: the case where the first network entity is requested to configure the trigger parameter without the trigger parameter also includes the case where the first network entity is requested to modify or reconfigure the trigger parameter again because the trigger parameter is not appropriate in the case where the trigger parameter is already present. Regardless of the manner in which the trigger parameter is obtained, after obtaining the trigger parameter, a ninth message may be sent to the second network entity, the trigger parameter being included in the ninth message.

It should be noted that, the application layer may provide the trigger parameter to the second network entity, and the second network entity activates the asynchronous redundant transmission mode according to the trigger parameter, that is, identifies a data packet sent on the first access path during a period in which the delay difference indicated by the transmission parameter exceeds a set threshold as an unacknowledged data packet that needs to be asynchronously retransmitted, and buffers the unacknowledged data packet into the first data stream, so as to perform the asynchronous redundant transmission process through the second access path. In addition, the application layer may also provide a trigger indication of the asynchronous redundancy transfer mode to the second network entity, and the second network entity activates the asynchronous redundancy transfer mode according to the trigger indication, that is, identifies an unacknowledged packet on the first access path and buffers the unacknowledged packet into the first data stream to perform asynchronous redundancy transfer through the second access path. The trigger indication is also used for the second network entity to identify unacknowledged data packets on the first access path, but is different from the trigger parameter, and the trigger indication is used for the second network entity to treat data packets which are transmitted on the first access path but have not received the acknowledgement message before the trigger indication arrives as unacknowledged data packets.

Optionally, the trigger parameter or trigger indication is provided by an upper layer application or an application layer transport protocol, and specifically, the trigger mechanism of the application layer transport protocol may be signaling QoE STATUS signaling (QoE _ STATUS _ SIGNAL) in the MP-QUIC scheduling protocol. The QOE status signaling may carry the buffer packet sequence condition of the downlink data packet received by the UE. The UPF may trigger asynchronous redundancy transfer based on QoE status signaling.

In an optional embodiment, the first network entity determines configuration indication information for performing asynchronous redundancy transmission for unacknowledged data packets on the first access path after receiving the first message, and provides a trigger indication of an asynchronous redundancy transmission mode to the second network entity by the application layer. As shown in fig. 2c, this embodiment comprises the following steps:

21c, the UE sends a first message to the first network entity, where the first message at least includes first indication information that the MA PDU session request uses an asynchronous redundancy transfer mode, and the asynchronous redundancy transfer mode is one of redundancy transfer modes or may be an independent redundancy transfer mode.

22c, after receiving the first message, the first network entity determines configuration indication information for performing asynchronous redundant transmission on an unacknowledged data packet on the first access path according to first indication information, included in the first message, that requests to use an asynchronous redundant transmission mode.

23c, the first network entity sends a second message to the second network entity, wherein the second message at least comprises the configuration indication information.

And 24c, after receiving the second message, the second network entity returns a third message to the first network entity so as to inform the first network entity that the second message is received.

25c, after receiving the third message, the first network entity sends a fourth message to the UE, where the fourth message includes the configuration indication information, so that the UE knows that the asynchronous redundancy transmission mode can be used.

26c, the UE sends a trigger indication of the asynchronous redundant transmission mode to the second network entity, the trigger indication being used for the second network entity to identify as unacknowledged data packets that have been transmitted on the first access path but for which no acknowledgement message has been received before the trigger indication arrives.

27c, the second network entity configures, according to the configuration indication information included in the second message, a first data flow for the unacknowledged data packets on the first access path on the second access path, and buffers the unacknowledged data packets on the first access path into the first data flow according to the trigger indication, so as to perform asynchronous redundancy transmission through the second access path.

28c, the UE re-receives the unacknowledged data packet on the first access path on the second access path under the asynchronous redundancy transmission mode.

In this embodiment, the same or similar steps as those in the previous embodiment can be referred to in the previous embodiment, and are not repeated herein. In this embodiment, the trigger indication is used for the second network entity to activate the asynchronous redundancy transmission mode, that is, a data packet on the first access path that does not receive the acknowledgement message before the trigger indication arrives is taken as an unacknowledged data packet and buffered in the first data stream, so as to perform asynchronous redundancy transmission through the second access path. After the unacknowledged data packet is cached to the first data stream, or after the unacknowledged data packet is subjected to asynchronous redundancy transmission through the second access path, the second network entity can transmit different data packets to the UE on the multiple access paths again, which is equivalent to deactivation of an asynchronous redundancy retransmission mode, and the multiple access paths are used for transmitting different data packets at the same time, so that the transmission efficiency of the data packets is improved. That is, the application layer may provide a trigger indication to the second network entity on demand (e.g., upon occurrence of a late-transmission first-arrival problem) such that the second network entity dynamically activates/deactivates the asynchronous redundancy retransmission mode.

It is noted that the second network entity may identify the unacknowledged data packets on the first access path (i.e. activate the asynchronous redundancy retransmission mode) based on the trigger parameter or the trigger indication alone, or may identify the unacknowledged data packets on the first access path (i.e. activate the asynchronous redundancy retransmission mode) by combining the trigger parameter and the trigger indication. Regarding the case of identifying an unacknowledged packet on the first access path by combining the trigger parameter and the trigger indication at the same time, the second network entity may activate the asynchronous redundancy retransmission mode when receiving the trigger indication, that is, a packet transmitted on the first access path but not receiving an acknowledgement message before the trigger indication arrives is required to be regarded as an unacknowledged packet, and in addition, the second network entity may also send a packet as an unacknowledged packet on the first access path within a period that the delay difference represented by the trigger parameter exceeds a set threshold. In regard to the case of identifying the unacknowledged data packet on the first access path by combining the trigger parameter and the trigger indication, the trigger parameter may be provided by the upper layer application, or may be provided by the first network entity or the third network entity, which is not limited thereto.

In the above or below embodiments, the implementation manner of the "configuration indication information" is not limited, and any implementation manner of the information that can indicate that the first data flow for the unacknowledged data packet on the first access path is configured 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 indicate that a new data flow is created on the second access path for the unacknowledged data packets on the first access path, and indicate that the new data flow has a higher 5QI, so as to obtain preferential scheduling, and ensure that the UE receives the data packets in time. In this alternative embodiment, the configuration indication information may include first indication information and a first 5QI, where the first indication information is used to indicate that a new data flow is created on the second access path for unacknowledged data packets on the first access path, and the first 5QI refers to a 5QI that the new data flow should have. Based on this, one way for the second network entity to configure the first data flow for the unacknowledged data packet on the first access path on the second access path according to the configuration indication information includes: and according to the first indication information in the configuration indication information, creating a new data flow on the second access path aiming at the unacknowledged data packets on the first access path, and configuring the 5QI of the new data flow as the first 5 QI. In this embodiment, the new data stream is the first data stream.

In another optional embodiment, the configuration indication information is used to indicate that the unacknowledged data packets on the first access path are cached to the existing 5QI data stream with higher priority on the second access path, so as to obtain priority scheduling, and ensure that the UE receives the data packets in time. In this alternative embodiment, the configuration indication information may include second indication information and a second 5QI, where the second indication information is used to indicate that the unacknowledged data packet on the first access path is buffered to an existing data flow with the second 5QI on the second access path, and the priority of the second 5QI is higher, for example, higher than the set priority threshold. Based on this, one way for the second network entity to configure the first data flow for the unacknowledged data packet 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 according to the second indication information in the configuration indication information, determining that the existing data stream with the second 5QI is multiplexed for the unacknowledged data packets on the first access path. In this embodiment, the existing data stream with the second 5QI is the first data stream. It should be noted that the configuration indication information may not include the second 5QI, and the second network entity may select the existing data flow with higher priority on the second access path.

In each of the above or below embodiments, it is not limited how the second network entity determines the second access path. In an optional embodiment, two access paths are provided, and are denoted as a first access path and a second access path. In an optional embodiment, the plurality of access paths is two or more, and includes the first access path and other access paths, and the second network entity may select the second access path from the other access paths except the first access path. The selection method of the second access path includes but is not limited to:

mode B1: one of the other access paths is randomly selected as the second access path.

Mode B2: and measuring the QoS of other access paths except the first access path, and selecting the access path with the QoS meeting the preset condition as a second access path according to the QoS of the other access paths. For example, an access path having a QoS greater than a set threshold may be selected as the second access path. QoS may specifically refer to a plurality of index parameters, including but not limited to delay, jitter, packet loss rate, path load, transmission rate, and the like. Specifically, an access path with a lighter path load may be selected as the second access path, or an access path with a faster transmission rate may be selected as the second access path, or an access path with a lower packet loss rate may be selected as the second access path, and so on.

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 may be flexibly determined according to the standard of the mobile communication network. In the following embodiments, a 5G network is taken as an example, and a multipath redundant transmission method provided by the embodiments of the present application is exemplarily described in combination with a specific network entity and a specific message format. In the following scenario embodiment, the first network entity is an SMF, the second network entity is an UPF, the third network entity is a PCF, the first message is a PDU session establishment/modification request message, the second message is an N4session establishment/modification request message, the third message is an N4session 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 _ Update request), and the sixth message is a PCF session management policy control Update response message (Npcf _ SMPolicyControl _ Update response); the ninth message is a QoE control SIGNAL frame (QoE _ STATUS _ SIGNAL frame). In the following scenario embodiments, the first access path is taken as a non-3GPP access path, and the second access path is taken as a 3GPP access path for example.

Fig. 3a is an interaction flow diagram of another multipath redundant transmission method according to an exemplary embodiment of the present application. As shown in fig. 3a, the method comprises:

31a, the upper layer application in the UE establishes a communication connection with an Application Server (AS), and applies to complete the establishment of the MA PDU session.

32a, the UE sends a PDU session modification request message (PDU session modification request) to the SMF, where the PDU session modification request message carries second indication information that the MA PDU session supports a redundant transmission mode (supported for redundant mode), and first indication information that an asynchronous redundant transmission mode (re-indication mode) is requested to be used.

It is explained here that in case the MA PDU session has been established completed, the UE may request the use of asynchronous redundant transport mode during the modification of the MA PDU session. In addition, under the condition that the MA PDU session is not established, the UE may request to use the asynchronous redundant transmission mode in the MA PDU session establishment process, and in this case, may send a PDU session establishment request message (PDU session redundancy request) to the SMF, where the message carries the second indication information that the MA PDU session supports the redundant transmission mode, and the first indication information that the asynchronous redundant transmission mode is requested to use.

33a, SMF sends PCF session management policy control Update request message (Npcf _ SMPolicyControl _ Update request) to PCF, which includes first indication information requesting use of asynchronous redundancy transfer mode to inquire to PCF whether it is possible to execute asynchronous redundancy transfer mode.

34a, PCF determines that the asynchronous redundant transmission mode can be executed according to Policy and Charging Control Rule (Policy and Charging Control Rule), and returns PCF session management Policy Control Update response message (Npcf _ SMPolicyControl _ Update response) to SMF, where the message includes configuration indication information (configuration of non-ack Qos flow) for asynchronous redundant transmission of unacknowledged data packets on the non-3GPP access path and trigger parameters required by the asynchronous redundant transmission mode, such as delay difference (delay difference) between two access paths. Specifically, the policy and charging control rules in the PCF may include rules supporting multipath synchronous redundant transmission (redundant transmission mode) and rules supporting multipath asynchronous redundant transmission (re-injection mode).

For a description herein, either or both of the configuration indication information and the trigger parameter may also be configured locally by the SMF, which is described in the foregoing embodiments and is not described herein again.

35a, the SMF sends an N4session establishment/modification request message (N4session establishment/modification request) to the UPF, where the request message includes an N4 rule and the configuration indication information, and the N4 rule includes the trigger parameter, such as a delay difference (delay difference) between two access paths.

Further optionally, the N4 rule further includes: a path selection rule (including selection criterion), an identifier for initially activating/deactivating a redundant transmission mode (initial activated/deactivated), and Measurement assistance information (Measurement assistance information) for triggering a redundant transmission mechanism.

36a, the UPF configures a QoS data flow for an unacknowledged data packet on the non-3GPP access path on the 3GPP access path according to the configuration indication information, and buffers the unacknowledged data packet on the non-3GPP access path into the configured QoS data flow according to the trigger parameter, so as to retransmit the data flow on the 3GPP access path.

Specifically, the trigger parameter indicates a delay difference for transmitting a data packet between two access paths, the UPF may monitor a delay difference for transmitting a data packet between a non-3GPP access path and a 3GPP access path, and use a data packet sent on the non-3GPP access path within a period in which the delay difference exceeds a set threshold as an unacknowledged data packet that needs to be asynchronously retransmitted, where the data packets generally cannot receive an acknowledgement message returned by the UE in time due to a large delay difference.

37a, the UPF sends an N4session setup or modification response message (N4session establishment/modification response) to the SMF.

38a, the SMF sends a PDU session establishment/modification response message (PDU session establishment/modification response) to the UE, where the message includes an N4 rule and the configuration indication information, and the N4 rule includes the trigger parameter.

Alternatively, the N4 rule may be configurable by the SMF according to the sss rule, which may be obtained by the SMF via the PCF. Specifically, the ssss rule may be included in policy and charging control rules in the PCF, and the rules may include a rule supporting a multipath synchronous redundant transmission (redundant transmission mode) and a rule supporting a multipath asynchronous redundant transmission (re-injection mode).

39a, after receiving the PDU session establishment/modification response message, the UE configures a tunnel client (tunnel client) corresponding to the MA P DU session, where the tunnel client corresponds to a tunnel server (tunnel server) in the UPF, and the tunnel client and the tunnel server cooperate to complete the MA PDU session process.

40a, the UE receives the unacknowledged data packet on the non-3GPP access path again on the 3GPP access path under the asynchronous redundancy transmission mode.

Further, when the delay difference is lower than the threshold again, the UPF may transmit different data packets to the UE on the non-3GPP access path and the 3GPP access path, which is equivalent to deactivation of the asynchronous redundancy retransmission mode; accordingly, the UE can receive different data packets on two access paths, thereby improving the transmission efficiency of the data packets. That is, as the delay difference changes, when the delay difference is large, the UPF activates the asynchronous redundancy retransmission mode, and when the delay difference becomes small again, the UPF may deactivate the asynchronous redundancy retransmission mode.

Fig. 3b is an interaction flow diagram of another multipath redundant transmission method according to an exemplary embodiment of the present application. As shown in fig. 3b, the method comprises:

31b, the upper layer application in the UE establishes communication connection with an Application Server (AS) and applies for establishing the MA PDU session.

32b, the UE sends a PDU session establishment request message (PDU session establishment request) to the SMF, wherein the message carries second indication information that the MA PDU session supports a redundant transmission mode (support for redundant mode) and first indication information that the asynchronous redundant transmission mode (re-injection mode) is requested to be used.

It is explained herein that in case the MA PDU session is not established, the UE may request to use asynchronous redundant transport mode during the MA PDU session establishment procedure. In addition, in the case that the MA PDU session is established, the UE may request to use the asynchronous redundant transmission mode in the modification process of the MA PDU session, and in this case, may send a PDU session modification request message (PDU session modification request) to the SMF, where the PDU session modification request message carries second indication information that the MA PDU session supports the redundant transmission mode, and first indication information that the asynchronous redundant transmission mode is requested to be used.

33b, the SMF determines configuration indication information (configuration of non-ack Qos flow) for performing asynchronous redundant transmission for unacknowledged 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.

Optionally, the SMF may further send a PCF session management policy control Update request message (Npcf _ SMPolicyControl _ Update request) to the PCF, where the message includes first indication information of the asynchronous redundancy transfer mode, so as to query the PCF whether the asynchronous redundancy transfer mode can be executed. The PCF determines that the asynchronous redundant transmission mode can be executed according to 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 above configuration indication information may not be included in the Npcf _ SMPolicyControl _ Update response message.

34b, the SMF sends a N4session establishment/modification request message (N4session establishment/modification request) to the UPF, where the message includes an N4 rule and the above configuration indication information, and the N4 rule includes a routing rule (including selection criterion), an identifier for initially activating/deactivating a redundant transmission mode (initial activated/deactivated), and Measurement assistance information (Measurement auxiliary information) for triggering a redundant transmission mechanism.

35b, the UPF sends an N4session setup or modification response message (N4session authorization/modification response) to the SMF.

36b, the SMF sends a PDU session establishment/modification response message (PDU session establishment/modification response) to the UE, where the message includes the N4 rule and the above configuration indication information.

37b, after receiving the PDU session establishment/modification response message, the UE configures a tunnel client (tunnel client) corresponding to the MA P DU session, where the tunnel client corresponds to a tunnel server (tunnel server) in the UPF, and the tunnel client and the tunnel server cooperate to complete the MA P DU session process.

38b, the UE sends an indication of triggering of asynchronous redundant transmission mode (indication from MP-QUIC/DCCP layer for triggering-injection mode) to the UPF.

39b, the UPF configures a QoS data flow for an unacknowledged data packet on the non-3GPP access path on the 3GPP access path according to the configuration indication information, and buffers the unacknowledged data packet on the non-3GPP access path into the configured QoS data flow according to the trigger indication, so as to retransmit the data flow on the 3GPP access path.

When receiving a trigger instruction provided by an application layer, the UPF caches a data packet which is transmitted on a non-3GPP access path and does not receive an acknowledgement message before the trigger instruction arrives as an unacknowledged data packet needing asynchronous retransmission to a first data stream so as to carry out asynchronous redundant transmission through a second access path.

40b, the UE receives the unacknowledged data packet on the non-3GPP access path again on the 3GPP access path under the asynchronous redundancy transmission mode.

Further, after the unacknowledged data packet is cached to the first data stream, or after all the unacknowledged data packets are subjected to asynchronous redundancy transmission through the 3GPP access path, the UPF may retransmit different data packets to the UE on the two access paths, which is equivalent to deactivation of an asynchronous redundancy retransmission mode, and the two access paths are used to transmit different data packets at the same time, which is beneficial to improving the data packet transmission efficiency. That is, the application layer may provide a trigger indication to the UPF on demand (when a late-transmission early-arrival problem occurs) so that the UPF dynamically activates/deactivates the asynchronous redundancy retransmission mode.

In the above embodiment of the present application, in the PDU session establishment or modification process, the UE requests asynchronous redundant transmission to the SMF, and the SMF configures a QoS data stream and a trigger parameter for asynchronous redundant transmission by the UPF after being confirmed by the PCF, or provides the trigger parameter or a trigger indication by an upper application or application layer transport protocol, so that asynchronous redundant transmission based on multiple paths is implemented between the UE and the UPF, which can effectively solve the problem of sending before after multiple paths in downlink transmission, obtain a corresponding data packet as soon as possible, and improve the QoE of the user on the data stream, especially on the data stream with a high real-time requirement. Specifically, the trigger mechanism of the application layer transport protocol may be signaling QoE STATUS signaling (QoE _ STATUS _ SIGNAL) in the MP-QUIC scheduling protocol. The QoE status signaling may carry a sequence condition of a buffer packet of the downlink data packet received by the UE. The UPF may trigger asynchronous redundant transmissions based on QoS status signaling.

Fig. 4a is a schematic flowchart of another multi-path redundant transmission method according to an exemplary embodiment of the present application. The method is described from the perspective of a UE, and as shown in fig. 4a, the method includes:

41a, sending a first message to a first network entity, the first message including at least first indication information that an MA PDU session requests to use an asynchronous redundant transmission mode, so that the first network entity sends a second message to a second network entity, wherein the asynchronous redundant transmission mode is one of redundant transmission modes;

42a, receiving a fourth message returned by the first network entity, where the second message and the fourth message at least include configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on the first access path, so that the second network entity performs asynchronous redundancy transmission on the unacknowledged data packet on the first access path through the second access path according to the configuration indication information.

In an optional embodiment, the fourth message further includes: and the triggering parameter is used for a second network entity to identify an unacknowledged data packet on the first access path, wherein the unacknowledged data packet refers to a data packet which is sent within a period that the delay difference represented by the triggering parameter exceeds a set threshold value.

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 parameter; and receiving an eighth message returned by the first network entity, wherein the eighth message comprises the configured trigger parameter.

In an optional embodiment, the first message further includes: the MA PDU session supports the second indication of the redundant transmission mode.

In an optional embodiment, the method of this embodiment further includes: and sending a trigger indication of the asynchronous redundancy transmission mode to the second network entity so that the second network entity can identify an unacknowledged data packet on the first access path, wherein the unacknowledged data packet refers to a data packet which does not receive an acknowledgement message before the trigger indication arrives.

In an optional embodiment, the configuration indication information is used to indicate that the first data flow for unacknowledged data packets on the first access path is configured on the second access path.

For detailed implementation of the above steps, reference may be made to the related description in the foregoing embodiments, and details are not described herein.

Fig. 4b is a flowchart illustrating another multipath redundant transmission method according to an exemplary embodiment of the present application. The method is described from the perspective of a first network entity, as shown in fig. 4b, and comprises:

41b, receiving a first message sent by the UE, where the first message at least includes first indication information that an MA PDU session request uses an asynchronous redundant transmission mode, where the asynchronous redundant transmission mode is one of redundant transmission modes;

42b, according to the first indication information of the asynchronous redundancy transmission mode, determining configuration indication information for carrying out asynchronous redundancy transmission on the unacknowledged data packet on the first access path;

43b, sending a second message to the second network entity, and sending a fourth message to the UE, where the second message and the fourth message at least include the configuration indication information, so that the second network entity performs asynchronous redundant transmission on the unacknowledged data packet on the first access path through the second access path.

In an optional embodiment, the second message further includes: triggering parameters of asynchronous redundant transmission mode. Based on this, the method of this embodiment further includes: and determining a trigger parameter of the asynchronous redundancy transmission mode according to the first indication information requesting to use the asynchronous redundancy transmission mode, wherein the trigger parameter is used for identifying the unacknowledged data packet on the first access path by the second network entity.

In an optional embodiment, before determining the configuration indication information for performing the asynchronous redundancy transmission for the unacknowledged data packet on the first access path according to the first indication information requesting to use the asynchronous redundancy transmission mode, the method further includes: sending a fifth message to the third network entity, wherein the fifth message at least comprises first indication information requesting to use the asynchronous redundant transmission mode, so that the third network entity confirms whether the asynchronous redundant transmission mode can be executed or not; and receiving a sixth message sent by the third network entity, the sixth message indicating that asynchronous redundant transmission mode can be performed.

In an optional embodiment, the sixth message includes: at least one of the configuration indication information and the trigger parameter. Based on this, determining configuration indication information for performing asynchronous redundancy transmission for unacknowledged data packets on a first access path and a trigger parameter of an asynchronous redundancy transmission mode according to first indication information requesting to use the asynchronous redundancy transmission mode, includes: acquiring at least one of configuration indication information and a trigger parameter from the sixth message, and locally configuring another information under the condition of acquiring one of the information from the sixth message; or, according to the first indication information of the asynchronous redundancy transmission mode used by the request, the configuration indication information and the trigger parameter are configured locally.

Fig. 4c is a flowchart illustrating another multipath redundant transmission method according to an exemplary embodiment of the present application. The method is described from the perspective of a second network entity, as shown in fig. 4c, and comprises:

41c, receiving a second message sent by the first network entity, where the second message at least includes configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on the first access path, and an MA PDU session request corresponding to the first access path uses an asynchronous redundancy transmission mode;

42c, configuring a first data flow aiming at the unacknowledged data packet on the first access path on the second access path according to the configuration indication information;

43c, buffering the unacknowledged data packet on the first access path into the first data flow so as to perform asynchronous redundancy transmission through a second access path, wherein the second access path is another access path corresponding to the MA PDU session.

In an optional embodiment, the buffering the unacknowledged data packets on the first access path into the first data stream for asynchronous redundancy transmission through the second access path includes: identifying an unacknowledged data packet on the first access path according to the trigger parameters and/or the trigger indication of the asynchronous redundancy transmission mode; and buffering the identified unacknowledged data packets into the first data flow so as to carry out asynchronous redundancy transmission through the second access path.

In an optional embodiment, the present embodiment further includes: acquiring a trigger parameter and/or a trigger indication of an asynchronous redundant transmission mode, wherein the acquiring operation comprises at least one of the following modes: acquiring a trigger parameter from the second message; receiving a trigger parameter sent by an application layer; and receiving a trigger indication sent by an application layer.

In an optional embodiment, the identifying the unacknowledged data packet on the first access path according to the trigger parameter and/or the trigger indication includes: taking a data packet sent in a period that the delay difference represented by the trigger parameter on the first access path exceeds a set threshold value as an unacknowledged data packet; and/or taking a data packet which does not receive the confirmation message before the trigger indication arrives on the first access path as an unacknowledged data packet.

In an optional embodiment, before configuring the first data flow for unacknowledged data packets on the first access path on the second access path, the method further includes: measuring the QoS of other access paths except the first access path; and according to the QoS of other access paths, selecting an access path with the QoS meeting the preset condition as a second access path.

It should be noted that in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 21a, 22a, etc., are merely used for distinguishing different operations, and the sequence numbers themselves do not represent any execution order. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

Fig. 5a is a schematic structural diagram of a multipath redundant transmission apparatus according to another exemplary embodiment of the present application. The apparatus can be applied to a UE, and as shown in fig. 5a, the apparatus includes: a transmitting module 51a and a receiving module 52 a.

A sending module 51a, configured to send a first message to a first network entity, where the first message includes at least first indication information that an MA PDU session requests to use an asynchronous redundant transmission mode, so that the first network entity sends a second message to a second network entity, where the asynchronous redundant transmission mode is one of redundant transmission modes;

the receiving module 52a is configured to receive a fourth message returned by the first network entity, where the second message and the fourth message at least include configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on the first access path, so that the second network entity performs asynchronous redundancy transmission on the unacknowledged data packet on the first access path through the second access path according to the configuration indication information.

In an optional embodiment, the sending module 51a is further configured to: sending a seventh message to the first network entity to request the first network entity to configure the trigger parameter; the receiving module 52a is further configured to: and receiving an eighth message returned by the first network entity, wherein the eighth message comprises the configured trigger parameter.

In an optional embodiment, the sending module 51a is further configured to: and sending a trigger indication of the asynchronous redundancy transmission mode to the second network entity so that the second network entity can identify an unacknowledged data packet on the first access path, wherein the unacknowledged data packet refers to a data packet which does not receive an acknowledgement message before the trigger indication arrives.

Fig. 5b is a schematic structural diagram of another multipath redundant transmission apparatus according to an exemplary embodiment of the present application. As shown in fig. 5b, the apparatus comprises: a sending module 51b, a receiving module 52b and a determining module 53 b.

A receiving module 52b, configured to receive a first message sent by the UE, where the first message includes at least first indication information that an MA PDU session requests to use an asynchronous redundancy transport mode, where the asynchronous redundancy transport mode is one of redundancy transport modes;

a determining module 53b, configured to determine configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on the first access path according to the first indication information requesting to use the asynchronous redundancy transmission mode;

the sending module 51b is configured 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 at least include the configuration indication information, so that the second network entity performs asynchronous redundant transmission on the unacknowledged data packet on the first access path through the second access path.

In an optional embodiment, the second message further includes: triggering parameters of asynchronous redundant transmission mode. Based on this, the determining module 53b is further configured to: and determining a trigger parameter of the asynchronous redundancy transmission mode according to the first indication information of requesting to use the asynchronous redundancy transmission mode, wherein the trigger parameter is used for identifying the unacknowledged data packet on the first access path by the second network entity.

In an optional embodiment, the sending module 51b is further configured to send a fifth message to the third network entity before determining the configuration indication information for performing asynchronous redundant transmission on the unacknowledged data packet on the first access path, where the fifth message includes at least the first indication information requesting to use the asynchronous redundant transmission mode, so that the third network entity confirms whether the asynchronous redundant transmission mode can be performed. Accordingly, the receiving module 52b is further configured to: and receiving a sixth message sent by the third network entity, wherein the sixth message indicates that the asynchronous redundancy transmission mode can be executed.

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 the asynchronous redundant transmission on the unacknowledged data packet on the first access path and the trigger parameter of the asynchronous redundant transmission mode, the determining module 53b is specifically configured to: acquiring at least one of configuration indication information and a trigger parameter from the sixth message, and locally configuring another information under the condition of acquiring one of the information from the sixth message; or, according to the first indication information of the asynchronous redundancy transmission mode used by the request, the configuration indication information and the trigger parameter are configured locally.

Fig. 5c is a schematic structural diagram of another multipath redundant transmission apparatus according to an exemplary embodiment of the present application. As shown in fig. 5c, the apparatus comprises: a sending module 51c, a receiving module 52c and a configuration module 53 c.

A receiving module 52c, configured to receive a second message sent by the first network entity, where the second message at least includes configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on the first access path, and an MA PDU session request corresponding to the first access path uses an asynchronous redundancy transmission mode;

a configuration module 53c, configured to configure a first data flow for an unacknowledged data packet on the first access path on the second access path according to the configuration indication information;

the sending module 51c is configured to buffer the unacknowledged data packet on the first access path into the first data flow, so as to perform asynchronous redundancy transmission through a second access path, where the second access path is another access path corresponding to the MA PDU session.

In an optional embodiment, the sending module 51c is specifically configured to: identifying an unacknowledged data packet on the first access path according to the trigger parameters and/or the trigger indication of the asynchronous redundancy transmission mode; and buffering the identified unacknowledged data packets into the first data flow so as to carry out asynchronous redundancy transmission through the second access path.

In an alternative embodiment, the receiving module 52c is further configured to: acquiring a trigger parameter and/or a trigger indication of an asynchronous redundant transmission mode, wherein the acquiring operation comprises at least one of the following modes: acquiring a trigger parameter from the second message; receiving a trigger parameter sent by an application layer; and receiving a trigger indication sent by an application layer.

In an optional embodiment, when the sending module 51c identifies an unacknowledged packet on the first access path according to the trigger parameter and/or the trigger indication, the sending module is specifically configured to: taking a data packet sent in a period that the time delay difference represented by the trigger parameter on the first access path exceeds a set threshold value as an unacknowledged data packet; and/or taking a data packet which does not receive the confirmation message before the trigger indication arrives on the first access path as an unacknowledged data packet.

Fig. 6a is a schematic structural diagram of a user equipment according to an exemplary embodiment of the present application, and as shown in fig. 6a, the user equipment includes: memory 61a, processor 62a and communication component 63 a.

The memory 61a is used for storing computer programs and may be configured to store other various data to support operations on the user equipment. Examples of such data include instructions for any application or method operating on the user device, contact data, phonebook data, messages, pictures, videos, and so forth.

A processor 62a, coupled to the memory 61a, for executing computer programs in the memory 61a for: sending a first message to the first network entity through the communication component 63a, the first message comprising at least first indication information that the MA PDU session requests to use an asynchronous redundant transport mode, the asynchronous redundant transport mode being one of the redundant transport modes, to cause the first network entity to send a second message to the second network entity; and receiving a fourth message returned by the first network entity through the communication component 63a, where the second message and the fourth message at least include configuration indication information for performing asynchronous redundant transmission on the unacknowledged data packet on the first access path, so that the second network entity performs asynchronous redundant transmission on the unacknowledged data packet on the first access path through the second access path according to the configuration indication information.

In an alternative embodiment, the processor 62a is further configured to: sending a seventh message to the first network entity through the communication component 63a to request the first network entity to configure the triggering parameter; and receiving an eighth message returned by the first network entity, wherein the eighth message comprises the configured trigger parameter.

In an alternative embodiment, the processor 62a is further configured to: a trigger indication of the asynchronous redundant transmission mode is sent to the second network entity through the communication component 63a, so that the second network entity can identify an unacknowledged data packet on the first access path, where the unacknowledged data packet refers to a data packet for which an acknowledgement message is not received before the trigger indication arrives.

For detailed implementation of the above operations, reference may be made to the related description in the foregoing embodiments, and details are not described herein.

Further, as shown in fig. 6a, the user equipment further includes: display 64a, power supply components 65a, audio components 66a, and the like. Only some of the components are schematically shown in fig. 6a, and the user equipment is not meant to comprise only the components shown in fig. 6 a.

Accordingly, the present application also provides a computer readable storage medium storing a computer program/instruction, which when executed by a processor, causes the processor to implement the steps executable by the UE in the above method embodiments.

Fig. 6b is a schematic structural diagram of a network entity according to an exemplary embodiment of the present application, where the network entity may be implemented as a first network entity in the foregoing embodiments, as shown in fig. 6b, the user equipment includes: a memory 61b, a processor 62b and a communication component 63 b. Further, as shown in fig. 6b, the network entity also includes a power component 64 b.

A processor 62b, coupled to the memory 61b, for executing computer programs in the memory 61b for: receiving a first message sent by the UE through the communication component 63b, where the first message at least includes 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 redundant transmission modes; determining configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on a first access path according to first indication information requesting to use an asynchronous redundancy transmission mode; and sending a second message to a second network entity, and sending a fourth message to the UE, wherein the second message and the fourth message at least comprise the configuration indication information, so that the second network entity performs asynchronous redundant transmission on the unacknowledged data packet on the first access path through a second access path.

In an optional embodiment, the second message further includes: triggering parameters of asynchronous redundant transmission mode. Based on this, the processor 62b is further configured to: and determining a trigger parameter of the asynchronous redundancy transmission mode according to the first indication information requesting to use the asynchronous redundancy transmission mode, wherein the trigger parameter is used for identifying the unacknowledged data packet on the first access path by the second network entity.

In an alternative embodiment, the processor 62b is further configured to: sending a fifth message to the third network entity through the communication component 63b, the fifth message including at least the first indication information requesting to use 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 asynchronous redundant transmission mode can be performed.

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 the asynchronous redundant transmission on the unacknowledged data packet on the first access path and the trigger parameter of the asynchronous redundant transmission mode, the processor 62b is specifically configured to: acquiring at least one of configuration indication information and a trigger parameter from the sixth message, and locally configuring another information under the condition of acquiring one of the information from the sixth message; or, according to the first indication information of the asynchronous redundancy transmission mode used by the request, the configuration indication information and the trigger parameter are configured locally.

Accordingly, the present application also provides a computer readable storage medium storing a computer program/instructions, which when executed by a processor, causes the processor to implement the steps of the above method embodiments, which are executable by the first network entity.

Fig. 6c is a schematic structural diagram of another network entity provided in an exemplary embodiment of the present application, where the network entity may be implemented as a second network entity in the foregoing embodiments, as shown in fig. 6c, the user equipment includes: a memory 61c, a processor 62c and a communication component 63 c. Further, as shown in fig. 6c, the network entity also includes a power component 64 c.

A processor 62c, coupled to the memory 61c, for executing computer programs in the memory 61c for: receiving, by the communication component 63c, a second message sent by the first network entity, where the second message at least includes configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on the first access path, and an MA PDU session request corresponding to the first access path uses an asynchronous redundancy transmission mode; according to the configuration indication information, configuring a first data flow aiming at an unacknowledged data packet on a first access path on a second access path; and caching the unacknowledged data packets on the first access path into the first data flow so as to carry out asynchronous redundancy transmission through a second access path, wherein the second access path is another access path corresponding to the MA PDU session.

In an optional embodiment, when buffering the unacknowledged data packet on the first access path into the first data stream for asynchronous redundancy transmission via the second access path, the processor 62c is specifically configured to: identifying an unacknowledged data packet on the first access path according to the trigger parameters and/or the trigger indication of the asynchronous redundancy transmission mode; and buffering the identified unacknowledged data packets into the first data flow so as to carry out asynchronous redundancy transmission through the second access path.

In an alternative embodiment, the processor 62c is further configured to: acquiring a trigger parameter and/or a trigger indication of an asynchronous redundant transmission mode, wherein the acquiring operation comprises at least one of the following modes: acquiring a trigger parameter from the second message; receiving a trigger parameter sent by an application layer; and receiving a trigger indication sent by an application layer.

In an alternative embodiment, the processor 62c, when identifying the unacknowledged data packet on the first access path according to the trigger parameter and/or the trigger indication, is specifically configured to: taking a data packet sent in a period that the time delay difference represented by the trigger parameter on the first access path exceeds a set threshold value as an unacknowledged data packet; and/or taking a data packet which does not receive the confirmation message before the trigger indication arrives on the first access path as an unacknowledged data packet.

In an alternative embodiment, the processor 62c is further configured to: measuring the QoS of other access paths except the first access path; and according to the QoS of other access paths, selecting an access path with the QoS meeting the preset condition as a second access path.

Accordingly, the present application also provides a computer readable storage medium storing a computer program/instructions, which when executed by a processor, causes the processor to implement the steps of the above method embodiments, which can be performed by the second network entity.

The memory in the above embodiments may be implemented by any type or combination of volatile or non-volatile memory devices, 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 or optical disks.

The communication component in the above embodiments is configured to facilitate communication between the device in which the communication component is located and other devices in a wired or wireless manner. The device where the communication component is located can access a wireless network based on a communication standard, such as a WiFi, a 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 one exemplary embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

The display in 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 an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

The power supply components in the embodiments described above provide power to the various components of the device in which the power supply components are located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.

The audio component in the above embodiments may be configured to output and/or input an audio signal. For example, the audio component includes a Microphone (MIC) configured to receive an external audio signal when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A multi-path redundant transmission method applied to User Equipment (UE), the method comprising:

sending a first message to a first network entity, the first message including at least first indication information that a multi-anchor protocol data unit (MA) PDU session requests 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 redundant transmission modes;

receiving a fourth message returned by the first network entity, where the second message and the fourth message at least include configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on a first access path, so that the second network entity performs asynchronous redundancy transmission on the unacknowledged data packet on the first access path through a second access path according to the configuration indication information.

2. The method of claim 1, wherein the fourth message further comprises: and the triggering parameter is used for the second network entity to identify an unacknowledged data packet on the first access path, where the unacknowledged data packet is a data packet sent within a period in which the delay difference represented by the triggering parameter exceeds a set threshold.

3. The method of claim 2, further comprising:

sending a seventh message to the first network entity to request the first network entity to configure the trigger parameter;

and receiving an eighth message returned by the first network entity, wherein the eighth message comprises the configured trigger parameter.

4. The method of any of claims 1-3, wherein the first message further comprises: the MA PDU session supports the second indication of the redundant transmission mode.

5. The method of any one of claims 1-3, further comprising:

sending a trigger indication of the asynchronous redundant transmission mode to the second network entity so that the second network entity can identify an unacknowledged data packet on the first access path, wherein the unacknowledged data packet refers to a data packet which does not receive an acknowledgement message before the trigger indication arrives.

6. The method according to any one of claims 1-3, further comprising:

the configuration indication information is used for indicating that a first data flow of unacknowledged data packets on the first access path is configured on a second access path.

7. A multi-path redundant transmission method for a first network entity, the method comprising:

receiving a first message sent by user equipment, wherein the first message at least comprises first indication information of a multi-anchor point protocol data unit (MA) PDU session request using an asynchronous redundancy transmission mode, and the asynchronous redundancy transmission mode is one of redundancy transmission modes;

determining configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on a first access path according to the first indication information;

and 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 at least include the configuration indication information, so that the second network entity performs asynchronous redundant transmission on an unacknowledged data packet on the first access path through a second access path.

8. The method of claim 7, wherein the second message further comprises: the triggering parameter of the asynchronous redundant transmission mode, the method further comprising:

and determining a trigger parameter of the asynchronous redundancy transmission mode according to the first indication information, wherein the trigger parameter is used for the second network entity to identify the unacknowledged data packet on the first access path.

9. The method of claim 8, wherein before determining the configuration indication information for the asynchronous redundant transmission of unacknowledged data packets over the first access path according to the first indication information, the method further comprises:

sending a fifth message to a third network entity, wherein the fifth message at least comprises the first indication information so that the third network entity confirms whether the asynchronous redundancy transmission mode can be executed or not; and

receiving a sixth message sent by the third network entity, the sixth message indicating that asynchronous redundant transmission mode may be performed.

10. The method of claim 9, wherein the sixth message comprises: at least one of the configuration indication information and the trigger parameter;

determining configuration indication information for performing asynchronous redundant transmission on an unacknowledged data packet on a first access path and a trigger parameter of the asynchronous redundant transmission mode according to the first indication information, wherein the configuration indication information comprises:

acquiring at least one of the configuration indication information and the trigger parameter from the sixth message, and locally configuring another information when one information is acquired from the sixth message;

or,

and locally configuring the configuration indication information and the trigger parameter according to the first indication information.

11. The method according to any of claims 7-10, wherein the configuration indication information is used to indicate that the first data flow for unacknowledged data packets on the first access path is configured on the second access path.

12. A multi-path redundant transmission method for a second network entity, the method comprising:

receiving a second message sent by a first network entity, wherein the second message at least comprises configuration indication information for performing asynchronous redundancy transmission on an unacknowledged data packet on a first access path, and a session request of a multi-anchor protocol data unit (MA PDU) corresponding to the first access path uses an asynchronous redundancy transmission mode;

according to the configuration indication information, configuring a first data flow aiming at an unacknowledged data packet on the first access path on a second access path;

and buffering the unacknowledged data packets on the first access path into the first data flow so as to perform asynchronous redundancy transmission through the second access path, wherein the second access path is another access path corresponding to the MA PDU session.

13. The method of claim 12, wherein buffering unacknowledged packets on the first access path into the first data stream for asynchronous redundant transmission via the second access path comprises:

according to the triggering parameters and/or triggering indications of the asynchronous redundancy transmission mode, identifying unacknowledged data packets on the first access path;

and buffering the identified unacknowledged data packets into the first data stream for asynchronous redundant transmission through the second access path.

14. The method of claim 13, further comprising: acquiring a trigger parameter and/or a trigger indication of the asynchronous redundancy transmission mode, wherein the acquiring operation comprises at least one of the following modes:

acquiring the trigger parameter from the second message;

receiving the trigger parameters sent by an application layer;

and receiving the trigger indication sent by an application layer.

15. The method according to claim 13 or 14, wherein identifying unacknowledged data packets on the first access path according to the trigger parameter and/or trigger indication comprises:

taking a data packet sent in a period that the delay difference represented by the trigger parameter on the first access path exceeds a set threshold value as an unacknowledged data packet;

and/or

And taking a data packet which does not receive the confirmation message before the trigger indication arrives on the first access path as an unacknowledged data packet.

16. The method according to any of claims 12-14, further comprising, before configuring the first data flow for unacknowledged data packets on the first access path on the second access path:

measuring the QoS of other access paths except the first access path;

and selecting an access path with QoS meeting preset conditions as the second access path according to the QoS of the other access paths.

17. A user device, comprising: a memory, a processor, and a communications component; the memory for storing a computer program; the processor is adapted to execute the computer program for implementing the steps in the method of any of claims 1-6.

18. A network entity, implementable as a first network entity, comprising: a memory, a processor, and a communications component; the memory for storing a computer program; the processor is adapted to execute the computer program for implementing the steps of the method of any one of claims 7-11.

19. A network entity, implementable as a second network entity, comprising: a memory, a processor, and a communications component; the memory for storing a computer program; the processor is adapted to execute the computer program for implementing the steps in the method of any of claims 12-16.

20. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 16.