WO2023213281A1 - 多路径冗余传输方法、用户设备、网络实体及存储介质 - Google Patents

多路径冗余传输方法、用户设备、网络实体及存储介质 Download PDF

Info

Publication number
WO2023213281A1
WO2023213281A1 PCT/CN2023/092141 CN2023092141W WO2023213281A1 WO 2023213281 A1 WO2023213281 A1 WO 2023213281A1 CN 2023092141 W CN2023092141 W CN 2023092141W WO 2023213281 A1 WO2023213281 A1 WO 2023213281A1
Authority
WO
WIPO (PCT)
Prior art keywords
access path
redundant transmission
message
network entity
data packets
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/092141
Other languages
English (en)
French (fr)
Inventor
于小博
邓娟
刘大鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba China Co Ltd
Original Assignee
Alibaba China Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba China Co Ltd filed Critical Alibaba China Co Ltd
Publication of WO2023213281A1 publication Critical patent/WO2023213281A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements

Definitions

  • the present application relates to the field of communication technology, and in particular, to a multi-path redundant transmission method, user equipment, network entities and storage media.
  • ATSSS Access Traffic Steering, Switching and Splitting
  • UE User Equipment
  • Each steering function supports traffic steering, handover and cross-3GPP access and non-3GPP access.
  • ATSSS supports redundant transmission mode, that is, the same data packet is transmitted on 3GPP paths and non-3GPP paths at the same time. Redundant transmission is performed on 3GPP paths with better quality of service (QoS) to ensure that the UE obtains data as soon as possible. Corresponding data packets improve the quality of experience (Quality of Experience, QoE) of the data flow.
  • QoS quality of service
  • the implementation of the existing redundant transmission mode is relatively simple and cannot solve the multi-path head of line blocking problem under multi-path.
  • the last-come first-come problem refers to the multi-path transmission when one path is transmitted. When the delay is significantly greater than that of another path, the data packets transmitted first on this path are often not received when the data packets sent later on the other path arrive, thus causing the problem of missing or out-of-order data packets.
  • a new multi-path redundant transmission scheme needs to be provided.
  • Various aspects of this application provide a multi-path redundant transmission method, user equipment, network entities and storage media to provide a new multi-path redundant transmission method so that the UE can effectively solve the multi-path problem in downlink transmission.
  • the problem of last-come-first-served is to obtain the corresponding data packet as soon as possible and improve the QoE of the data flow.
  • Embodiments of the present application provide a multi-path redundant transmission method, which is suitable for user equipment.
  • the method includes: sending a first message to a first network entity, where the first message at least includes a multi-anchor protocol data unit MA PDU session. Requesting first indication information to use an asynchronous redundant transmission mode, so that the first network entity sends a second message to the second network entity, the asynchronous redundant transmission mode being one of the redundant transmission modes; receiving the The fourth message returned by the first network entity, the second message and the fourth message at least include configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, so that the The second network entity performs asynchronous redundant transmission of unconfirmed data packets on the first access path through the second access path according to the configuration indication information.
  • An embodiment of the present application also provides a multi-path redundant transmission method, which is suitable for the first network entity.
  • the method includes: Receive the first message sent by the user equipment, the first message including at least the first indication information of the multi-anchor protocol data unit MA PDU session request to use the asynchronous redundant transmission mode, the asynchronous redundant transmission mode is redundant transmission One of the modes; according to the first indication information, determine the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path; send a second message to the second network entity, and The user equipment sends a fourth message, where the second message and the fourth message at least include the configuration indication information, so that the second network entity configures the first access path through the second access path.
  • Embodiments of the present application also provide a multi-path redundant transmission method, which is suitable for a second network entity.
  • the method includes: receiving a second message sent by the first network entity, where the second message at least includes information for the first connection. Configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the incoming path.
  • the multi-anchor protocol data unit MA PDU session request corresponding to the first access path uses the asynchronous redundant transmission mode; according to the configuration indication information , configure the first data flow for the unconfirmed data packets on the first access path on the second access path; cache the unconfirmed data packets on the first access path to the first data In the flow, asynchronous redundant transmission is performed through the second access path, and the second access path is another access path corresponding to the MA PDU session.
  • An embodiment of the present application also provides a user equipment, including: a memory, a processor and a communication component; the memory is used to store a computer program; the processor is used to execute the computer program to implement the embodiment of the present application.
  • the embodiment of the present application also provides a network entity, which can be implemented as a first network entity, including: a memory, a processor, and a communication component; the memory is used to store a computer program; the processor is used to execute the computer program, To implement the steps in the multi-path redundant transmission method provided by the embodiment of the present application and which can be executed by the first network entity.
  • a network entity which can be implemented as a first network entity, including: a memory, a processor, and a communication component; the memory is used to store a computer program; the processor is used to execute the computer program, To implement the steps in the multi-path redundant transmission method provided by the embodiment of the present application and which can be executed by the first network entity.
  • the embodiment of the present application also provides a network entity, which can be implemented as a second network entity, including: a memory, a processor, and a communication component; the memory is used to store a computer program; the processor is used to execute the computer program, To implement the steps in the multi-path redundant transmission method provided by the embodiment of the present application and which can be executed by the second network entity.
  • a network entity which can be implemented as a second network entity, including: a memory, a processor, and a communication component; the memory is used to store a computer program; the processor is used to execute the computer program, To implement the steps in the multi-path redundant transmission method provided by the embodiment of the present application and which can be executed by the second network entity.
  • Embodiments of the present application also provide a computer-readable storage medium storing a computer program.
  • the computer program When executed by a processor, the processor can implement the steps in the multi-path redundant transmission method provided by each embodiment of the present application.
  • the user equipment and the network entity in the mobile communication network cooperate with each other to realize the activation and deactivation of asynchronous redundant transmission based on multi-path for the MA PDU session.
  • data packets that cannot be confirmed in time can be asynchronously redundantly transmitted on another access path.
  • This enriches the implementation of the redundant transmission mechanism and allows the UE to effectively solve multi-path problems in downlink transmission. Solve first-come issues and obtain corresponding data packets as soon as possible to improve users' QoE for data flows, especially data flows with high real-time requirements.
  • Figure 1a is a schematic diagram of a partial architecture of a mobile communication network provided by an exemplary embodiment of the present application
  • Figure 1b is a schematic diagram of the transmission status of an asynchronous redundant transmission mode provided by an exemplary embodiment of the present application
  • Figure 2a is a schematic interactive flow diagram of a multi-path redundant transmission method provided by an exemplary embodiment of the present application
  • Figure 2b is a schematic interactive flow diagram of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application.
  • Figure 2c is a schematic interactive flow diagram of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application.
  • Figure 3a is a schematic interactive flow diagram of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application.
  • Figure 3b is a schematic interactive flow diagram of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application.
  • Figure 4a is a schematic flowchart of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application.
  • Figure 4b is a schematic flowchart of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application.
  • Figure 4c is a schematic flowchart of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application.
  • Figure 5a is a schematic structural diagram of a multi-path redundant transmission device provided by another exemplary embodiment of the present application.
  • Figure 5b is a schematic structural diagram of a multi-path redundant transmission device provided by another exemplary embodiment of the present application.
  • Figure 5c is a schematic structural diagram of a multi-path redundant transmission device provided by another exemplary embodiment of the present application.
  • Figure 6a is a schematic structural diagram of a user equipment provided by an exemplary embodiment of the present application.
  • Figure 6b is a schematic structural diagram of a network entity provided by an exemplary embodiment of the present application.
  • Figure 6c is a schematic structural diagram of another network entity provided by an exemplary embodiment of the present application.
  • the user equipment and the network entity in the mobile communication network cooperate with each other to target MA PDU
  • the session implements activation and deactivation of asynchronous redundant transmission based on multipath. In this way, for data packets that have been transmitted on one access path but cannot be acknowledged in time, these data packets can be asynchronously redundant on another access path.
  • Redundant transmission a rich implementation of redundant transmission mechanism, allows UE to effectively solve the multi-path last-come-first-served problem in downlink transmission, obtain the corresponding data packets as soon as possible, and improve users' higher requirements on data flow, especially real-time performance. QoE of the data flow.
  • the mobile communication network in this embodiment includes an access network and a core network.
  • the access network mainly includes a base station. There may be multiple access networks. For example, it may include both a 3GPP access network and a non-3GPP (Non-3GPP) access network;
  • the core network includes but is not limited to the following network entities: Authentication Server Function (AUSF), User Plane Function (UPF), Access and Mobility Management Function (AMF) ), Unified Data Management (UDM), Network Exposure Function (NEF), Session Management Function (SMF), Network Slice Selection Function (NSSF), Network Storage Function (NF Repository Function, NRF), Policy Control Function (PCF), Application Layer Function (Application Function, AF), etc.
  • AUSF Authentication Server Function
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • UDM Unified Data Management
  • NEF Network Exposure Function
  • SMF Session Management Function
  • NSSF Network Slice Selection Function
  • NRF Network Storage Function
  • PCF Policy Control Function
  • the mobile communication network of this embodiment supports the ATSSS feature, and the ATSSS supports a redundant transmission mode.
  • the redundant transmission mode may be called a redundant steering mode.
  • the redundant transmission mode is a mode that can redundantly transmit data packets on multiple paths.
  • the system architecture of the mobile communication network in the embodiment of the present application has been expanded.
  • the UE in the embodiment of the present application supports one or more steering functions, such as MPTCP (MultiPath TCP) function and/or Or ATSSS-LL and/or MP-QUIC (Mutipath QUIC) function.
  • MPTCP MultiPath TCP
  • ATSSS-LL ATSSS-LL
  • MP-QUIC Motipath QUIC
  • each steering function in the UE supports traffic steering, switching and splitting for multi-path access.
  • the ATSSS-LL function is mandatory in the UE.
  • the UPF in the embodiment of this application can support the MPTCP proxy function, which communicates with the PTCP function in the UE by using the MPTCP protocol; the UPF can also support the ATSSS-LL function, which is similar to the ATSSS-LL function in the UE.
  • AMF is responsible for the access and mobility management functions of UE
  • SMF implements session management, which supports the establishment, modification and release of sessions, the allocation and management of UE's IP address, etc.
  • PCF supports a unified policy framework for controlling network behavior, providing Policy rules are executed on the control plane and can access subscription information related to policy formulation in the Unified Data Repository (UDR) function.
  • UDR Unified Data Repository
  • UPF is mainly responsible for routing and forwarding of user plane data packets in the core network, interacting with SMF through the N4 air interface, performing corresponding processing according to various policies issued by SMF, and interconnecting the core network with the Data Network (DN). session points, etc.
  • DN Data Network
  • the cooperation between the UE and the network entities UPF, AMF, SMF, PCF, etc. can implement a multi-path-based redundant transmission process.
  • multiple access paths existing between the UE and the UPF including 3GPP access paths and non-3GPP access paths, are used as an example for illustration, but are not limited to this.
  • the redundant transmission mode allows redundant transmission of data packets on multiple access paths, but does not limit the specific implementation of redundant transmission of data packets on multiple access paths.
  • a specific implementation method of the redundant transmission mode is the synchronous redundant transmission mode, that is, after triggering the transmission mode, the same data packet is transmitted simultaneously on multiple access paths, thereby realizing multi-path-based redundancy. remaining transmission.
  • embodiments of the present application also provide an asynchronous redundant transmission mode (re-injection mode).
  • This asynchronous redundant transmission mode can also be called asynchronous retransmission mode or re-caching retransmission mode. It is a redundant transmission mode.
  • Another specific implementation method under the mode mainly refers to the situation where a data packet has been transmitted on one access path and cannot be received in time from the peer, and the later data packet on another access path arrives first.
  • Figure 1b shows a schematic diagram of the transmission status of the asynchronous redundant transmission mode.
  • both ends adopt the asynchronous redundant transmission mode, in which data packets 1-10 and data packet 1 are transmitted on the non-3GPP access path.
  • -3 and 8-10 received the peer acknowledgment message (ACK), but the data packet 4-7 sent earlier than the data packet 8-10 failed to receive the peer acknowledgment message. Therefore, from another access path, that is, 3GPP Asynchronous redundant retransmission is performed on the access path to prioritize the 3GPP access path with better QoS to ensure that the opposite end receives the data packet in time 4-7.
  • the UPF may use an asynchronous redundant transmission mode to send downlink data packets to the UE.
  • the UE can also use asynchronous redundant transmission mode to send uplink data packets to the UPF.
  • the asynchronous redundant transmission process of the uplink data packet is the same or similar to the asynchronous redundant transmission process of the downlink data packet.
  • the focus is on the UPF using the asynchronous redundant transmission mode to send the downlink data packet to the UE.
  • the multi-path redundant transmission method provided by the embodiment of the present application will be described in detail.
  • Figure 2a is a schematic interactive flow diagram of a multi-path redundant transmission method provided by an exemplary embodiment of the present application. As shown in Figure 2a, the method includes:
  • the UE sends a first message to the first network entity.
  • the first message includes at least first indication information of MA PDU session request to use asynchronous redundant transmission mode.
  • the asynchronous redundant transmission mode is one of the redundant transmission modes.
  • the first network entity After receiving the first message, the first network entity determines to perform asynchronous redundancy for the unconfirmed data packets on the first access path according to the first instruction information contained in the first message requesting to use the asynchronous redundant transmission mode. transmission configuration setting instructions.
  • the first network entity sends a second message to the second network entity, where the second message at least includes the above configuration indication information.
  • the second network entity After receiving the second message, the second network entity configures the first data flow for the unconfirmed data packet on the first access path on the second access path according to the configuration instruction information contained in the second message. .
  • the second network entity returns a third message to the first network entity to notify the first network entity that the configuration has been completed.
  • the first network entity After receiving the third message, the first network entity sends a fourth message to the UE, where the fourth message at least includes the above configuration indication information, so that the UE understands that the asynchronous redundant transmission mode can be used.
  • the second network entity caches the unconfirmed data packets on the first access path into the first data stream to perform asynchronous redundant transmission through the second access path.
  • the UE In the asynchronous redundant transmission mode, the UE re-receives the unacknowledged data packet on the first access path on the second access path.
  • the second network entity can transmit different data packets to the UE on the multiple access paths to take advantage of multiple access paths.
  • the advantages of multiple access paths improve the transmission efficiency of data packets.
  • the UE may send a first message to the first network entity during the process of creating the MA PDU session or modifying the MA PDU session to request the use of redundant transmission for the MA PDU session.
  • the asynchronous redundant transmission mode in the redundant transmission mode performs data packet transmission.
  • the first network entity is a network entity responsible for session management, which may be but is not limited to SMF, for example.
  • the second network entity is a network entity that forwards user plane data packets with the UE, and may be, for example but not limited to, UPF.
  • the first message may only include the first indication information (re-injection mode) requesting to use the asynchronous redundant transmission mode, or may also include the second indication information (re-injection mode) that the MA PDU session supports the redundant transmission mode ( Indication of support for redundant mode) and MA PDU session request use the first indication information (re-injection mode) of asynchronous redundant transmission mode, which is not limited.
  • the first network entity 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 the first indication information contained in the first message requesting to use the asynchronous redundant transmission mode. Therefore, it is necessary to provide the second network entity with Generate configuration instruction information for asynchronous retransmission of unconfirmed data packets on the first access path, so that the second network entity performs relevant configuration of the asynchronous retransmission redundancy mode according to the configuration instruction information, and transmits the asynchronous retransmission redundancy mode through the third message.
  • the configuration indication information is sent to the second network entity.
  • the second network entity can transmit different data packets to the UE on multiple access paths to take advantage of the multiple access paths and improve the transmission efficiency of data packets.
  • Asynchronous redundant transmission mode can be triggered.
  • the first access path refers to an access path currently used by the MA PDU session, which is an access path that "has been transmitted and failed to receive the data packet confirmed by the UE in time" in the last-come-first-come problem; accordingly; , the second access path is another access path corresponding to the MA PDU session. It is an access path where "later data packets arrive first" in the last-come-first-come problem. It is used to analyze the first access path.
  • the first access path and the second access path are not limited. Relatively speaking, the QoS of the second access path is better than the QoS of the first access path.
  • the first access path The incoming path may be a non-3GPP access path, and the second access path is a 3GPP access path.
  • QoS can specifically refer to multiple index parameters, including but not limited to delay, jitter, packet loss rate, path load, etc.
  • the UE is required to return a confirmation message within a set time range.
  • the data packet is called an unconfirmed data packet.
  • the unconfirmed data packet on the first access path refers to the data packet that has been transmitted on the first access path but failed to receive the confirmation message returned by the UE in time.
  • the failure to receive the data packet returned by the UE in time to confirm the message mainly refers to the first-sent data packet that is later than the later-sent data packet when the first-sent-last-arrival problem occurs.
  • the second network entity In order to use the second access path to perform asynchronous redundant transmission of unconfirmed data packets on the first access path (asynchronous redundant transmission may also be referred to as asynchronous retransmission), the second network entity after receiving the second message , according to the configuration instruction information in the second message, configure the first data flow for unconfirmed data packets on the first access path on the second access path, and the first data flow is used to configure the first access path A data stream for redundant transmission of unacknowledged data packets on a network.
  • the data stream is actually a data queue used to store data packets.
  • the data queue has a higher access channel priority.
  • the priority can be characterized by a 5G QoS Identifier (5QI); accordingly, the first data flow can be a 5G QoS data flow, but is not limited to this.
  • the 5G QoS Identity (5QI) is a reference scalar used to provide specific QoS forwarding behavior (e.g., packet loss rate, packet delay budget) to 5G QoS data flows. This can be achieved in the access network through specific parameters of the 5QI reference node, which are parameters that control the QoS forwarding process.
  • the second network entity may return a third message to the first network entity to inform the first network entity that the relevant configuration of the asynchronous redundant transmission mode has been completed. Accordingly, the first network entity sends a fourth message to the UE, and carries the above configuration indication information in the fourth message, so that the UE understands that the UPF has completed the relevant configuration of the asynchronous redundant transmission mode and can use the asynchronous redundant transmission mode.
  • the client for the MA PDU session can also be configured to receive packets in asynchronous redundant transmission mode.
  • the second network entity may identify unacknowledged data packets on the first access path and cache the identified unacknowledged data packets into the first data stream for asynchronous redundant transmission through the second access path. .
  • the UPF evaluates these data according to the quality of service indications of these data flows.
  • the flow is scheduled, and the data packets in the scheduled data flow can be transmitted on the second access path.
  • the QI of the data flow may be called 5QI (5G QoS Identifier).
  • the implementation method of the 5QI of the data flow is not limited. However, in order to ensure that the first data flow can be scheduled in time, the 5QI of the first data flow may have a higher priority. The higher the priority of the 5QI, The corresponding data flow is scheduled with higher priority.
  • unacknowledged data packets buffered on the first access path in the first data flow are retransmitted on the second access path.
  • the unconfirmed data packets on the first access path can be re-received on the second access path to achieve asynchronous redundant transmission based on multi-path.
  • it enriches the redundancy
  • the implementation of the residual transmission mechanism allows the UE to effectively solve the multi-path late-first-come problem in downlink transmission, obtain the corresponding data packets as soon as possible, and improve the user's understanding of data flows, especially data with high real-time requirements. Streaming QoE.
  • the manner in which the first network entity determines the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path is not limited. In an optional embodiment, it may be configured locally by the first network entity. In another optional embodiment, the first network entity and the third network entity may interact, and the third network entity is responsible for providing the configuration indication information.
  • the third network entity refers to the network entity responsible for policy management, for example, it can be But not limited to PCF.
  • the first network entity may also determine trigger parameters corresponding to the asynchronous redundant transmission mode and provide them to the second network entity.
  • the first network entity may carry the trigger parameter in the second message and provide it to the second network entity.
  • the trigger parameter is used for the second network entity to identify unacknowledged data packets on the first access path, which is also an activation operation for the asynchronous redundant transmission mode.
  • the trigger parameter may be the delay difference between the two access paths. In this way, each time the second network entity transmits a data packet on the first access path, the second network entity (such as UPF) can monitor the delay difference in transmitting the data packet between the two access paths.
  • the second network entity can transmit different data packets to the UE on multiple access paths. This is equivalent to deactivating the asynchronous redundant retransmission mode and utilizing multiple access paths.
  • the path transmits different data packets at the same time, which is beneficial to improving the efficiency of data packet transmission. That is to say, as the delay difference changes, when the delay difference is large, the asynchronous redundant retransmission mode can be activated, and when the delay difference becomes smaller again, the asynchronous redundant retransmission mode can be deactivated.
  • the manner in which the first network entity determines the above-mentioned triggering parameters is also not limited. In an optional embodiment, it may be configured locally by the first network entity. In another optional embodiment, the first network entity and the third network entity may interact, and the third network entity is responsible for providing the trigger parameter.
  • the first network entity after receiving the first message, the first network entity simultaneously determines the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, and the asynchronous redundant transmission mode. trigger parameters. As shown in Figure 2b, this embodiment includes the following steps:
  • the UE sends a first message to the first network entity.
  • the first message at least includes first indication information of the MA PDU session request to use the asynchronous redundant transmission mode.
  • the asynchronous redundant transmission mode is one of the redundant transmission modes.
  • the first network entity After receiving the first message, the first network entity determines to perform asynchronous redundancy for the unconfirmed data packets on the first access path according to the first instruction information contained in the first message requesting to use the asynchronous redundant transmission mode. Configuration indication information of redundant transmission, and trigger parameters of asynchronous redundant transmission mode.
  • the first network entity determines the configuration indication information and trigger parameters in a manner including but not limited to the following:
  • Method A1 After receiving the first message, the first network entity uses the first indication information of the asynchronous redundant transmission mode according to the request contained in the first message, and performs local configuration for unconfirmed data packets on the first access path. Configuration indication information of asynchronous redundant transmission, and trigger parameters of asynchronous redundant transmission mode.
  • Method A2 After receiving the first message, the first network entity uses the first instruction information of the asynchronous redundant transmission mode according to the request contained in the first message, and sends a fifth message to the third network entity.
  • the fifth message contains at least including first indication information requesting the use of the asynchronous redundant transmission mode, so that the third network entity can confirm whether the asynchronous redundant transmission mode can be executed; and receiving a sixth message sent by the third network entity, which on the one hand indicates that the asynchronous redundant transmission mode can be executed Asynchronous redundant transmission mode; on the other hand, it also includes configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, and trigger parameters of the asynchronous redundant transmission mode.
  • the first network entity parses the configuration indication information and trigger parameters from the sixth message. In this method A2, the above configuration indication information and triggering parameters are both provided by the third network entity.
  • Method A3 After receiving the first message, the first network entity uses the first instruction information of the asynchronous redundant transmission mode according to the request contained in the first message, and sends a fifth message to the third network entity.
  • the fifth message contains at least Include first indication information requesting the use of asynchronous redundant transmission mode, so that the third network entity can confirm whether it can be performed Asynchronous redundant transmission mode; and receiving a sixth message sent by the third network entity.
  • the sixth message indicates that the asynchronous redundant transmission mode can be executed; on the other hand, it also includes performing operations on unconfirmed data packets on the first access path.
  • Configuration instructions for asynchronous redundant transmission The first network entity parses the above configuration indication information from the sixth message, and locally configures the trigger parameters of the asynchronous redundant transmission mode. In this method A3, the above configuration indication information is provided by the third network entity, and the above trigger parameter is configured locally by the second network entity.
  • Method A4 After receiving the first message, the first network entity uses the first instruction information of the asynchronous redundant transmission mode according to the request contained in the first message, and sends a fifth message to the third network entity.
  • the fifth message contains at least including first indication information requesting the use of the asynchronous redundant transmission mode, so that the third network entity can confirm whether the asynchronous redundant transmission mode can be executed; and receiving a sixth message sent by the third network entity, which on the one hand indicates that the asynchronous redundant transmission mode can be executed Asynchronous redundant transmission mode; on the other hand, it also includes trigger parameters of asynchronous redundant transmission mode.
  • the first network entity parses the trigger parameter from the sixth message, and locally configures configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path.
  • the trigger parameters are provided by the third network entity, and the configuration indication information is configured locally by the second network entity.
  • the first network entity sends a second message to the second network entity, where the second message includes the above configuration indication information and trigger parameters.
  • the second network entity After receiving the second message, the second network entity configures the first data flow for the unconfirmed data packet on the first access path on the second access path according to the configuration instruction information contained in the second message. .
  • the second network entity returns a third message to the first network entity to notify the first network entity that the configuration has been completed.
  • the first network entity After receiving the third message, the first network entity sends a fourth message to the UE.
  • the fourth message includes the above configuration indication information and trigger parameters, so that the UE understands that the asynchronous redundant transmission mode can be used.
  • the second network entity identifies the unconfirmed data packets on the first access path according to the trigger parameters contained in the second message, and caches the identified unconfirmed data packets into the first data stream for use through the second access path.
  • the input path performs asynchronous redundant transmission.
  • the trigger parameter represents the delay difference in transmitting data packets between the two access paths.
  • the second network entity can monitor the delay difference in transmitting data packets between the first access path and the second access path, and Data packets sent on the first access path during the period when the delay difference exceeds the set threshold are regarded as unconfirmed data packets that need to be asynchronously retransmitted. These data packets are usually unable to be received in time due to the large delay difference. Returns a confirmation message to the UE.
  • the UE In the asynchronous redundant transmission mode, the UE re-receives the unacknowledged data packet on the first access path on the second access path.
  • the second network entity can transmit different data packets to the UE on multiple access paths. This is equivalent to deactivating the asynchronous redundant retransmission mode and utilizing multiple access paths.
  • the access path transmits different data packets at the same time, which is beneficial to improving data packet transmission efficiency. That is to say, as the delay difference changes, when the delay difference is large, the asynchronous redundant retransmission mode can be activated, and when the delay difference becomes smaller again, the asynchronous redundant retransmission mode can be deactivated.
  • the trigger parameter of the asynchronous redundant transmission mode is provided by the first network entity or the third network entity as an example for description, but it is not limited to this.
  • the triggering parameters required to trigger the second network entity to identify unconfirmed data packets on the first access path may also be provided by the application layer or an application layer protocol (such as the MP-QUIC protocol), that is, the above configuration indication information is provided by the first The network entity or the third network entity provides it and provides it to the second network entity and the UE through the second message and the fourth message respectively.
  • the second network entity Before the second network entity identifies the unconfirmed data packet on the first access path, It can also receive trigger parameters sent by the application layer or application layer protocol (such as MP-QUIC protocol), and identify unconfirmed items on the first access path according to the trigger parameters provided by the application layer or application layer protocol (such as MP-QUIC protocol). data pack.
  • the application layer or application layer protocol such as MP-QUIC protocol
  • the application layer refers to the upper-layer application on the UE, such as APP, or the transmission protocol used by the application layer, such as MP-QUIC transmission protocol or transmission tunnel.
  • the upper-layer application or the transmission protocol tunnel of the application layer can configure the triggering parameters of the asynchronous redundant transmission mode on its own, or it can also send a seventh message to the first network entity to request the first network entity to configure the asynchronous redundant transmission mode. trigger parameters; then, receive the eighth message returned by the first network entity, and parse the trigger parameters configured by the first network entity from the eighth message.
  • the upper layer application requests the first network entity to configure the trigger parameters required for the asynchronous redundant transmission mode, including: in the absence of trigger parameters, requesting the first network entity to configure trigger parameters, and also includes the situation where there are already In the case of trigger parameters, the first network entity is requested to re-modify or reconfigure the trigger parameters because the trigger parameters are inappropriate. No matter how the trigger parameter is obtained, after the trigger parameter is obtained, a ninth message can be sent to the second network entity, and the ninth message includes the trigger parameter.
  • the application layer can 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, identifying the time represented by the transmission parameter on the first access path.
  • the data packets sent during the period when the delay difference exceeds the set threshold are regarded as unconfirmed data packets that need to be asynchronously retransmitted, and are cached in the first data stream for asynchronous redundant transmission through the second access path.
  • the application layer may also provide a trigger indication of the asynchronous redundant transmission mode to the second network entity.
  • the second network entity activates the asynchronous redundant transmission mode according to the trigger indication, that is, identifies unacknowledged errors on the first access path.
  • the data packet is buffered into the first data stream for asynchronous redundant transmission through the second access path.
  • the trigger indication is also used by the second network entity to identify unacknowledged data packets on the first access path, but is different from the trigger parameters.
  • the trigger indication is used by the second network entity to identify unacknowledged data packets on the first access path. Packets that have been transmitted but have not received an acknowledgment message before this trigger indication arrives are treated as unacknowledged packets.
  • the upper layer application or application layer transmission protocol provides trigger parameters or trigger instructions.
  • the triggering mechanism of the application layer transmission protocol may be the signaling QoE status signaling (QoE_STATUS_SIGNAL) in the MP-QUIC scheduling protocol.
  • the QOE status signaling can carry the buffered packet sequence status of downlink data packets received by the UE.
  • UPF can trigger asynchronous redundant transmission based on QoE status signaling.
  • the first network entity determines the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, and sends the request to the second network entity from the application layer.
  • the network entity provides triggering indication of asynchronous redundant transmission mode. As shown in Figure 2c, this embodiment includes the following steps:
  • the UE sends a first message to the first network entity.
  • the first message at least includes first indication information of MA PDU session request to use asynchronous redundant transmission mode.
  • the asynchronous redundant transmission mode is one of the redundant transmission modes, and also Can be an independent redundant transmission mode.
  • the first network entity After receiving the first message, the first network entity determines to perform asynchronous redundancy for the unconfirmed data packets on the first access path according to the first instruction information contained in the first message requesting to use the asynchronous redundant transmission mode. Configuration instructions for transmission.
  • the first network entity sends a second message to the second network entity, where the second message at least includes the above configuration indication information.
  • the second network entity After receiving the second message, the second network entity returns a third message to the first network entity to notify the first network entity that the second message has been received.
  • the first network entity After receiving the third message, the first network entity sends a fourth message to the UE, where the fourth message includes the above configuration indication information, so that the UE understands that the asynchronous redundant transmission mode can be used.
  • the UE sends a trigger indication of the asynchronous redundant transmission mode to the second network entity.
  • the trigger indication is used by the second network entity to transmit the data that has been transmitted on the first access path but has not received an acknowledgment message before the trigger indication arrives.
  • the packet is identified as an unacknowledged packet.
  • the second network entity configures the first data flow for the unconfirmed data packets on the first access path on the second access path according to the configuration instruction information contained in the second message, and configures the first data flow according to the above trigger instruction. Unacknowledged data packets on the first access path are buffered into the first data stream for asynchronous redundant transmission through the second access path.
  • the UE In the asynchronous redundant transmission mode, the UE re-receives the unacknowledged data packet on the first access path on the second access path.
  • the above trigger indication is used for the second network entity to activate the asynchronous redundant transmission mode, that is, the data packets on the first access path that have not received the confirmation message before the trigger indication arrives are treated as unconfirmed data packets and cached. into the first data stream for asynchronous redundant transmission through the second access path. After caching this unconfirmed data packet into the first data stream, or after performing asynchronous redundant transmission of all this unconfirmed data packet through the second access path, the second network entity can re-transmit the unconfirmed data packet on multiple access paths.
  • Different data packets are transmitted to the UE on the path respectively, which is equivalent to deactivating the asynchronous redundant retransmission mode.
  • Using multiple access paths to transmit different data packets at the same time is beneficial to improving data packet transmission efficiency. That is to say, the application layer can provide a trigger instruction to the second network entity on demand (for example, when a last-come-first-served problem occurs), so that the second network entity dynamically activates/deactivates the asynchronous redundant retransmission mode.
  • the second network entity can identify unconfirmed data packets on the first access path (that is, activate the asynchronous redundant retransmission mode) based on the trigger parameters or trigger instructions alone, or it can also combine the trigger parameters and trigger instructions at the same time. Unacknowledged data packets on the first access path are identified (ie, asynchronous redundant retransmission mode is activated).
  • the second network entity can activate the asynchronous redundant retransmission mode when receiving the trigger instructions, that is, the first network entity needs to Data packets that have been transmitted on the access path but have not received an acknowledgment message before the trigger indication arrives are regarded as unconfirmed data packets.
  • the second network entity can also set the delay represented by the trigger parameter on the first access path. If the difference exceeds the set threshold, the packets are sent as unacknowledged packets.
  • the trigger parameters may be provided by the upper-layer application, or may be provided by the first network entity or the third network entity. This is not done. limited.
  • the implementation method of "configuration indication information" is not limited. Any information that can instruct the second access path to configure the first data flow for unconfirmed data packets on the first access path All information implementation methods are applicable to the embodiments of this application.
  • the configuration indication information is used to instruct a new data flow to be created on the second access path for unacknowledged data packets on the first access path, and indicates that the new data flow has a higher 5QI to facilitate priority scheduling and ensure that the UE receives data packets in time.
  • the configuration indication information may include first indication information and a first 5QI.
  • the first indication information is used to instruct the second access path to create a new data packet for unacknowledged data packets on the first access path.
  • the first 5QI refers to the 5QI that the new data stream should have.
  • a way for the second network entity to configure the first data flow for the unconfirmed data packets on the first access path on the second access path according to the configuration instruction information includes: according to the configuration instruction information According to the first instruction information in the first access path, a new data flow is created on the second access path for the unconfirmed data packets on the first access path, and the 5QI of the new data flow is configured as the first 5QI.
  • the new data stream is the first data stream.
  • the configuration indication information is used to instruct to cache unacknowledged data packets on the first access path to the existing data flow of 5QI with higher priority on the second access path, so that In order to obtain priority scheduling, it ensures that the UE receives data packets in time.
  • the configuration indication information may include second indication information and a second 5QI. The second indication information is used to indicate caching unacknowledged data packets on the first access path to the second access path. For existing data streams with the second 5QI, the second 5QI has a higher priority, for example, higher than a set priority threshold.
  • a way for the second network entity to configure the first data flow for the unconfirmed data packets on the first access path on the second access path according to the configuration instruction information includes: according to the configuration instruction information the second 5QI in the second access path, determine the existing data flow with the second 5QI on the second access path; according to the second indication information in the configuration indication information, determine the multiplexing of unconfirmed data packets on the first access path Existing data flow with second 5QI.
  • the existing data stream with the second 5QI is the first data stream. It should be noted here that the above configuration indication information may not include the second 5QI, and the second network entity may select an existing data flow with a higher priority on the second access path.
  • how the second network entity determines the second access path is not limited.
  • there are two access paths denoted as a first access path and a second access path.
  • the number of access paths is more than two, including the first access path and other access paths.
  • the second network entity can select from other access paths except the first access path. Select the second access path. Methods for selecting the second access path include but are not limited to:
  • Method B1 Randomly select one from other access paths as the second access path.
  • Method B2 Measure the QoS of other access paths except the first access path, and select an access path whose QoS meets the preset conditions as the second access path based on the QoS of the other access paths. For example, an access path with a QoS greater than a set threshold may be selected as the second access path.
  • QoS can specifically refer to multiple index parameters, including but not limited to delay, jitter, packet loss rate, path load, transmission rate, etc. Specifically, you can select an access path with a lighter path load as the second access path, or select an access path with a faster transmission rate as the second access path, or select an access path with a lower packet loss rate. As a second access path, etc.
  • the first network entity, the second network entity, the third network entity and the implementation form of each message are not limited, and can be flexibly determined according to the standard of the mobile communication network.
  • the 5G network will be taken as an example to illustrate the multi-path redundant transmission method provided by the embodiments of the present application in combination with specific network entities and specific message formats.
  • the first network entity is SMF
  • the second network entity is UPF
  • the third network entity is PCF
  • the first message is a PDU session establishment/modification request message
  • the second message is an N4 session establishment/modification request message.
  • the ninth message is the QoE control signal frame (QoE_STATUS_SIGNAL frame).
  • the first access path is a non-3GPP access path and the second access path is a 3GPP access path as an example for exemplary explanation.
  • Figure 3a is a schematic interactive flow diagram of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application. As shown in Figure 3a, the method includes:
  • the upper-layer application in the UE establishes a communication connection with the application server (AS), and has applied to complete the establishment of the MA PDU session.
  • AS application server
  • the UE sends a PDU session modification request message (PDU session modification request) to the SMF.
  • PDU session modification request The message carries the second indication information that the MA PDU session supports redundant transmission mode (support for redundant mode), and requests the use of asynchronous redundant transmission mode. (re-injection mode) first indication information.
  • the UE can request to use the asynchronous redundant transmission mode during the modification process of the MA PDU session.
  • the UE can request to use the asynchronous redundant transmission mode during the MA PDU session establishment process.
  • it can send a PDU session establishment request message (PDU session establishment request) to the SMF.
  • PDU session establishment request carries the second indication information that the MA PDU session supports the redundant transmission mode, and the first indication information requesting the use of the asynchronous redundant transmission mode.
  • the SMF sends the PCF session management policy control update request message (Npcf_SMPolicyControl_Update request) to the PCF.
  • the message includes the first instruction information requesting the use of the asynchronous redundant transmission mode to query the PCF whether the asynchronous redundant transmission mode can be executed.
  • PCF determines that the asynchronous redundant transmission mode can be implemented based on the policy and charging control rules (Policy and Charging Control Rule), and returns the PCF session management policy control update response message (Npcf_SMPolicyControl_Update response) to SMF.
  • the message includes the Configuration instructions for asynchronous redundant transmission of unacknowledged data packets on the 3GPP access path (configuration of unack Qos flow) and trigger parameters required for asynchronous redundant transmission mode, such as the delay difference between the two access paths (delay difference).
  • the policy and charging control rules in PCF may include rules supporting multi-path synchronous redundant transmission (redundant steering mode) and rules supporting multi-path asynchronous redundant transmission (re-injection mode).
  • any one or both of the above configuration indication information and trigger parameters can also be configured locally by the SMF. Please refer to the description in the foregoing embodiments, which will not be described again here.
  • SMF sends an N4 session establishment/modification request message (N4session establishment/modification request) to UPF.
  • the request message includes N4 rules and the above configuration instruction information.
  • the N4 rules include the above trigger parameters, such as between two access paths. delay difference.
  • the N4 rules also include: path selection rules (including selection criteria), identification of initial activation/deactivation of the redundant transmission mode (initial activated/deactivated), and measurement auxiliary information that triggers the redundant transmission mechanism ( Measurement assistance information).
  • UPF configures the QoS data flow for unconfirmed data packets on the non-3GPP access path on the 3GPP access path based on the above configuration instruction information, and configures the unconfirmed data on the non-3GPP access path based on the above trigger parameters. Packets are buffered into the QoS data flow configured above for retransmission on the 3GPP access path.
  • the trigger parameter represents the delay difference in transmitting data packets between the two access paths.
  • UPF can monitor the delay difference in transmitting data packets between the non-3GPP access path and the 3GPP access path, and will Data packets sent on the incoming path when the delay difference exceeds the set threshold are regarded as unconfirmed data packets that need to be asynchronously retransmitted. These data packets usually cannot receive acknowledgment from the UE in time due to the large delay difference. information.
  • UPF sends an N4 session establishment or modification response message (N4session establishment/modification response) to SMF.
  • the SMF sends a PDU session establishment/modification response message (PDU session establishment/modification response) to the UE.
  • the message includes the N4 rule and the above configuration indication information.
  • the N4 rule includes the above trigger parameter.
  • N4 rules can be configured by SMF based on ATSSS rules, and ATSSS rules can be configured by SMF. Obtained via PCF. Specifically, the ATSSS rules can be included in the policy and charging control rules in the PCF. The rules can include rules that support multi-path synchronous redundant transmission (redundant steering mode) and multi-path asynchronous redundant transmission (re-injection). mode) rules.
  • the UE After receiving the PDU session establishment/modification response message, the UE configures the tunnel client (tunnel client) corresponding to the MAP DU session.
  • the tunnel client corresponds to the tunnel server (tunnel server) in UPF, and the two cooperate. Used to complete the MA PDU session process.
  • the UE In the asynchronous redundant transmission mode, the UE re-receives unacknowledged data packets on the non-3GPP access path on the 3GPP access path.
  • UPF can transmit different data packets to the UE on the non-3GPP access path and the 3GPP access path respectively, which is equivalent to deactivating the asynchronous redundant retransmission mode; accordingly , the UE can receive different data packets on two access paths, improving data packet transmission efficiency. That is to say, as the delay difference changes, when the delay difference is large, UPF can activate the asynchronous redundant retransmission mode, and when the delay difference becomes smaller again, UPF can deactivate the asynchronous redundant retransmission mode.
  • Figure 3b is a schematic interactive flow diagram of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application. As shown in Figure 3b, the method includes:
  • the upper-layer application in the UE establishes a communication connection with the application server (AS) and applies to establish a MA PDU session.
  • AS application server
  • the UE sends a PDU session establishment request message (PDU session establishment request) to the SMF.
  • PDU session establishment request The message carries the second indication information that the MA PDU session supports redundant transmission mode (support for redundant mode), and requests the use of asynchronous redundant transmission mode. (re-injection mode) first indication information.
  • the UE can request to use the asynchronous redundant transmission mode during the MA PDU session establishment process.
  • the UE can request to use the asynchronous redundant transmission mode during the modification process of the MA PDU session.
  • it can send a PDU session modification request message (PDU session modification) to the SMF. request), this message carries the second indication information that the MA PDU session supports the redundant transmission mode, and the first indication information requesting to use the asynchronous redundant transmission mode.
  • PDU session modification PDU session modification
  • the SMF determines the configuration instruction information (configuration of unack Qos flow) for asynchronous redundant transmission of unconfirmed data packets on the non-3GPP access path. ).
  • the SMF can also send a PCF session management policy control update request message (Npcf_SMPolicyControl_Update request) to the PCF.
  • the message includes the first indication information of the asynchronous redundant transmission mode to query the PCF whether the asynchronous redundant transmission mode can be executed. .
  • PCF determines that the asynchronous redundant transmission mode can be executed based on the policy and charging control rules (Policy and Charging Control Rule), and returns the PCF session management policy control update response message (Npcf_SMPolicyControl_Update response) to SMF.
  • the Npcf_SMPolicyControl_Update response message may not include the above configuration indication information.
  • SMF sends an N4 session establishment/modification request message (N4session establishment/modification request) to UPF.
  • the message includes N4 rules and the above configuration instruction information.
  • the N4 rules include path selection rules (including selection criteria), initial activation/or The identification of deactivating the redundant transmission mode (initial activated/deactivated), and the measurement assistance information (Measurement assistance information) that triggers the redundant transmission mechanism.
  • UPF sends an N4 session establishment or modification response message (N4session establishment/modification response) to SMF.
  • the SMF sends a PDU session establishment/modification response message (PDU session establishment/modification response) to the UE.
  • the message includes the N4 rule and the above configuration indication information.
  • the UE After receiving the PDU session establishment/modification response message, the UE configures the tunnel client (tunnel client) corresponding to the MAP DU session.
  • the tunnel client corresponds to the tunnel server (tunnel server) in UPF. The two are used together. To complete the MAP DU session process.
  • the UE sends the triggering indication of the asynchronous redundant transmission mode (indication from MP-QUIC/DCCP layer for triggering re-injection mode) to the UPF.
  • UPF configures the QoS data flow for unconfirmed data packets on the non-3GPP access path on the 3GPP access path according to the above configuration instruction information, and configures the unconfirmed data flow on the non-3GPP access path according to the above trigger instruction. Packets are buffered into the QoS data flow configured above for retransmission on the 3GPP access path.
  • the data packets that have been transmitted on the non-3GPP access path and have not received the confirmation message before the trigger indication arrives are treated as unconfirmed data packets that need to be asynchronously retransmitted, and are cached in the third In one data stream, asynchronous redundant transmission is performed through the second access path.
  • the UE In the asynchronous redundant transmission mode, the UE re-receives unacknowledged data packets on the non-3GPP access path on the 3GPP access path.
  • UPF can re-transmit the data on the two access paths. Transmitting different data packets to the UE respectively is equivalent to deactivating the asynchronous redundant retransmission mode.
  • Using two access paths to transmit different data packets at the same time is beneficial to improving data packet transmission efficiency.
  • the application layer can provide trigger instructions to the UPF on demand (when a last-come-first-served problem occurs), so that the UPF dynamically activates/deactivates the asynchronous redundant retransmission mode.
  • the UE requests asynchronous redundant transmission from the SMF during the establishment or modification process of the PDU session.
  • the SMF configures the UPF to perform the QoS data flow and trigger parameters of the asynchronous redundant transmission, or the upper layer application Or the application layer transmission protocol provides trigger parameters or trigger instructions, so that multi-path-based asynchronous redundant transmission is implemented between the UE and UPF, which allows the UE to effectively solve the multi-path last-come-first-served problem in downlink transmission and obtain data as soon as possible.
  • Corresponding data packets improve users' QoE for data flows, especially data flows with high real-time requirements.
  • the triggering mechanism of the application layer transmission protocol may be the signaling QoE status signaling (QoE_STATUS_SIGNAL) in the MP-QUIC scheduling protocol.
  • the QoE status signaling can carry the buffered packet sequence status of downlink data packets received by the UE.
  • UPF can trigger asynchronous redundant transmission based on QoS status signaling.
  • Figure 4a is a schematic flowchart of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application. The method is described from the perspective of the UE, as shown in Figure 4a. The method includes:
  • the first message at least includes the first instruction information of the MA PDU session request to use the asynchronous redundant transmission mode, so that the first network entity sends the second message to the second network entity, so
  • the asynchronous redundant transmission mode is one of the redundant transmission modes
  • the second message and the fourth message at least include configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, so that the second network The entity performs asynchronous redundant transmission of unacknowledged data packets on the first access path through the second access path according to the above configuration indication information.
  • the above-mentioned fourth message also includes: a trigger parameter of the asynchronous redundant transmission mode, the trigger parameter is used for the second network entity to identify the unconfirmed data packet on the first access path, so The unacknowledged data packet refers to a data packet sent during the period when the delay difference indicated by the trigger parameter exceeds the set threshold.
  • 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; receiving an eighth message returned by the first network entity. Eight messages include configured trigger parameters.
  • the above-mentioned first message also includes: second indication information that the MA PDU session supports redundant transmission mode.
  • the method of this embodiment further includes: sending a trigger indication of the asynchronous redundant transmission mode to the second network entity so that the second network entity can identify the unconfirmed data packet on the first access path,
  • the unconfirmed data packet refers to a data packet that does not receive an acknowledgment message before the trigger indication arrives.
  • the above configuration indication information is used to instruct the second access path to configure the first data flow for unacknowledged data packets on the first access path.
  • Figure 4b is a schematic flowchart of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application. The method is described from the perspective of the first network entity, as shown in Figure 4b. The method includes:
  • the asynchronous redundant transmission mode is one of the redundant transmission modes
  • the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path determine the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path
  • the second message and the fourth message at least include the above configuration indication information, so that the second network entity uses the second access path to access the first Unacknowledged data packets on the access path are transmitted asynchronously and redundantly.
  • the above-mentioned second message further includes: trigger parameters of the asynchronous redundant transmission mode.
  • the method of this embodiment also includes: determining the trigger parameter of the asynchronous redundant transmission mode according to the first indication information requesting the use of the asynchronous redundant transmission mode.
  • the trigger parameter is used for the second network entity to identify the first access Unacknowledged packets on the path.
  • the method before determining the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path according to the first indication information requesting to use the asynchronous redundant transmission mode, the method further includes: The third network entity sends a fifth message, which at least includes first indication information requesting the use of the asynchronous redundant transmission mode, so that the third network entity confirms whether the asynchronous redundant transmission mode can be implemented; and receives the third network entity The sixth message sent indicates that the asynchronous redundant transmission mode can be performed.
  • the sixth message includes: at least one of the configuration indication information and the trigger parameter. Based on this, according to the first indication information requesting the use of asynchronous redundant transmission mode, determine the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path and the trigger parameters of the asynchronous redundant transmission mode. , including: obtaining at least one of configuration indication information and trigger parameters from the sixth message, and when one of the information is obtained from the sixth message, locally configuring the other information; or, according to the above request Using the first indication information of the asynchronous redundant transmission mode, the above configuration indication information and triggering parameters are locally configured.
  • the above configuration indication information is used to indicate that the second access path is configured for the first access The first stream of unacknowledged packets on the incoming path.
  • Figure 4c is a schematic flowchart of yet another multi-path redundant transmission method provided by an exemplary embodiment of the present application. The method is described from the perspective of the second network entity, as shown in Figure 4c. The method includes:
  • the second message at least includes configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, and the MA PDU corresponding to the first access path.
  • Session requests use asynchronous redundant transmission mode
  • the second access path is another access corresponding to the MA PDU session. path.
  • the above-mentioned buffering of unconfirmed data packets on the first access path into the first data stream for asynchronous redundant transmission through the second access path includes: according to the asynchronous redundant transmission mode trigger parameters and/or trigger instructions to identify unconfirmed data packets on the first access path; cache the identified unconfirmed data packets into the first data stream for asynchronous redundant transmission through the second access path .
  • this embodiment further includes: obtaining the trigger parameters and/or trigger instructions of the asynchronous redundant transmission mode.
  • the obtaining operation includes at least one of the following methods: obtaining the trigger parameters from the second message; receiving Trigger parameters sent by the application layer; receive trigger instructions sent by the application layer.
  • the above-mentioned identification of unconfirmed data packets on the first access path based on the trigger parameter and/or trigger indication includes: converting the delay represented by the trigger parameter on the first access path to Data packets sent within a period when the difference exceeds the set threshold are regarded as unacknowledged data packets; and/or data packets on the first access path that do not receive an acknowledgment message before the trigger indication arrives are regarded as unacknowledged data packets.
  • the method 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 other than the first access path. QoS of other access paths; according to the QoS of other access paths, select an access path whose QoS meets the preset conditions as the second access path.
  • Figure 5a is a schematic structural diagram of a multi-path redundant transmission device provided by another exemplary embodiment of the present application.
  • the device can be applied in a UE.
  • the device includes: a sending module 51a and a receiving module 52a.
  • the sending module 51a is configured to send a first message to the first network entity.
  • the first message at least includes the first indication information of the MA PDU session request to use the asynchronous redundant transmission mode, so that the first network entity sends the first message to the second network entity.
  • Two messages, the asynchronous redundant transmission mode is one of the redundant transmission modes;
  • the receiving module 52a is configured to receive a fourth message returned by the first network entity.
  • the second message and the fourth message at least include configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, to The second network entity is caused to perform asynchronous redundant transmission of unconfirmed data packets on the first access path through the second access path according to the above configuration indication information.
  • the above-mentioned fourth message also includes: a trigger parameter of the asynchronous redundant transmission mode, the trigger parameter is used for the second network entity to identify the unconfirmed data packet on the first access path, so The unacknowledged data packet refers to a data packet sent during the period when the delay difference indicated by the trigger parameter exceeds the set threshold.
  • the sending module 51a is also configured to: send a seventh message to the first network entity to request the first network entity to configure the trigger parameters; the receiving module 52a is also configured to: receive a response from the first network entity The eighth message includes configured trigger parameters.
  • the above-mentioned first message also includes: second indication information that the MA PDU session supports redundant transmission mode.
  • the sending module 51a is also configured to: send a trigger indication of the asynchronous redundant transmission mode to the second network entity, so that the second network entity can identify the unconfirmed data packet on the first access path, so
  • the above-mentioned unconfirmed data packets refer to data packets that do not receive an acknowledgment message before the trigger indication arrives.
  • the above configuration indication information is used to instruct the second access path to configure the first data flow for unacknowledged data packets on the first access path.
  • Figure 5b is a schematic structural diagram of yet another multi-path redundant transmission device provided by an exemplary embodiment of the present application. As shown in Figure 5b, the device includes: a sending module 51b, a receiving module 52b and a determining module 53b.
  • the receiving module 52b is configured to receive the first message sent by the UE.
  • the first message at least includes the first indication information of the MA PDU session request to use the asynchronous redundant transmission mode.
  • the asynchronous redundant transmission mode is the redundant transmission mode.
  • Determining module 53b configured to determine the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path according to the first indication information requesting the use of asynchronous redundant transmission mode;
  • the sending module 51b is configured to send a second message to the second network entity and a fourth message to the UE, where the second message and the fourth message at least include the above configuration indication information, so that the second network entity can access through the second The path performs asynchronous redundant transmission of unacknowledged data packets on the first access path.
  • the above-mentioned second message further includes: trigger parameters of the asynchronous redundant transmission mode.
  • the determining module 53b is also configured to: determine the trigger parameters of the asynchronous redundant transmission mode according to the first indication information requesting the use of the asynchronous redundant transmission mode. The trigger parameters are used for the second network entity to identify the first access path. unacknowledged packets on.
  • the sending module 51b is further configured to send a fifth message to the third network entity before determining the configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path.
  • the fifth message at least includes first indication information requesting the use of the asynchronous redundant transmission mode, so that the third network entity can confirm whether the asynchronous redundant transmission mode can be executed.
  • the receiving module 52b is also configured to: receive a sixth message sent by the third network entity, where the sixth message indicates that the asynchronous redundant transmission mode can be performed.
  • the sixth message includes: at least one of the configuration indication information and the trigger parameter.
  • the determining module 53b is specifically used to: from the sixth message Obtain at least one of the configuration indication information and trigger parameters from the sixth message, and when one of the information is obtained from the sixth message, configure the other information locally; or, use the asynchronous redundant transmission mode according to the above request
  • the first indication information is to configure the above configuration indication information and trigger parameters locally.
  • the above configuration indication information is used to instruct the second access path to configure the first data flow for unacknowledged data packets on the first access path.
  • Figure 5c is a schematic structural diagram of yet another multi-path redundant transmission device provided by an exemplary embodiment of the present application. As shown in Figure 5c, the device includes: a sending module 51c, a receiving module 52c and a configuration module 53c.
  • the receiving module 52c is configured to receive a second message sent by the first network entity.
  • the second message at least includes configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path.
  • the first access path The corresponding MA PDU session request uses asynchronous redundant transmission mode;
  • the configuration module 53c is configured to configure the first data flow for unconfirmed data packets on the first access path on the second access path according to the above configuration instruction information
  • the sending module 51c is used to cache unconfirmed data packets on the first access path into the first data stream for asynchronous redundant transmission through the second access path.
  • the second access path is corresponding to the MA PDU session. Another access path.
  • the sending module 51c is specifically configured to: identify unconfirmed data packets on the first access path according to the trigger parameters and/or trigger instructions of the asynchronous redundant transmission mode; and send the identified unconfirmed data to Packets are buffered into the first data stream for asynchronous redundant transmission over the second access path.
  • the receiving module 52c is also configured to: obtain the trigger parameters and/or trigger instructions of the asynchronous redundant transmission mode.
  • the obtaining operation includes at least one of the following methods: obtaining the trigger parameters from the second message; receiving Trigger parameters sent by the application layer; receive trigger instructions sent by the application layer.
  • the sending module 51c when the sending module 51c identifies the unconfirmed data packet on the first access path according to the trigger parameter and/or the trigger indication, it is specifically configured to: convert the trigger parameter on the first access path to Data packets sent within a period in which the represented delay difference exceeds the set threshold are regarded as unconfirmed data packets; and/or data packets on the first access path that do not receive a confirmation message before the trigger indication arrives are regarded as unconfirmed data packets. data pack.
  • the method 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 other than the first access path. QoS of other access paths; according to the QoS of other access paths, select an access path whose QoS meets the preset conditions as the second access path.
  • Figure 6a is a schematic structural diagram of a user equipment provided by an exemplary embodiment of the present application.
  • the user equipment includes: a memory 61a, a processor 62a and a communication component 63a.
  • the memory 61a is used to store computer programs, and may be configured to store various other data to support operations on the user device. Examples of this data include instructions for any application or method operating on the user's device, contact data, phonebook data, messages, pictures, videos, etc.
  • the processor 62a is coupled to the memory 61a and is configured to execute the computer program in the memory 61a for: sending a first message to the first network entity through the communication component 63a, the first message at least including the MA PDU session request using asynchronous redundancy.
  • the first indication information of the transmission mode, so that the first network entity sends the second message to the second network entity, the asynchronous redundant transmission mode is one of the redundant transmission modes; receiving the first network entity through the communication component 63a
  • the returned fourth message, the second message and the fourth message at least include configuration indication information for asynchronous redundant transmission of unconfirmed data packets on the first access path, so that the second network entity can pass through according to the above configuration indication information.
  • the second access path performs asynchronous redundant transmission of the unacknowledged data packets on the first access path.
  • the above-mentioned fourth message also includes: a trigger parameter of the asynchronous redundant transmission mode, the trigger parameter The number is used by the second network entity to identify unconfirmed data packets on the first access path.
  • the unconfirmed data packets refer to data sent during the period when the delay difference represented by the trigger parameter exceeds the set threshold. Bag.
  • the processor 62a is further configured to: send a seventh message to the first network entity through the communication component 63a to request the first network entity to configure the trigger parameter; receive the eighth message returned by the first network entity. message, the eighth message includes configured trigger parameters.
  • the above-mentioned first message also includes: second indication information that the MA PDU session supports redundant transmission mode.
  • the processor 62a is also configured to: send a trigger indication of the asynchronous redundant transmission mode to the second network entity through the communication component 63a, so that the second network entity can identify the unconfirmed information on the first access path.
  • Data packets, the unconfirmed data packets refer to data packets that do not receive a confirmation message before the trigger indication arrives.
  • the above configuration indication information is used to instruct the second access path to configure the first data flow for unacknowledged data packets on the first access path.
  • the user equipment also includes: a display 64a, a power component 65a, an audio component 66a and other components. Only some components are schematically shown in Figure 6a, which does not mean that the user equipment only includes the components shown in Figure 6a.
  • embodiments of the present application also provide a computer-readable storage medium storing computer programs/instructions.
  • the processor can implement each of the above method embodiments that can be executed by the UE. step.
  • Figure 6b is a schematic structural diagram of a network entity provided by an exemplary embodiment of the present application.
  • the network entity can be implemented as the first network entity in the previous embodiment.
  • the user equipment includes: a memory 61b, a processing unit 62b and communication component 63b. Further, as shown in Figure 6b, the network entity also includes a power supply component 64b.
  • the processor 62b is coupled to the memory 61b and is configured to execute the computer program 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 a MA PDU session request using asynchronous redundant transmission.
  • the first indication information of the mode, the asynchronous redundant transmission mode is one of the redundant transmission modes; according to the first indication information of the request to use the asynchronous redundant transmission mode, determine the unconfirmed data on the first access path
  • the configuration indication information for asynchronous redundant transmission of the package is sent; the second message is sent to the second network entity, and the fourth message is sent to the UE.
  • the second message and the fourth message at least include the above configuration indication information, so that the second network entity Asynchronous redundant transmission of unacknowledged data packets on the first access path is performed through the second access path.
  • the above-mentioned second message further includes: trigger parameters of the asynchronous redundant transmission mode.
  • the processor 62b is further configured to: determine the trigger parameter of the asynchronous redundant transmission mode according to the first indication information requesting the use of the asynchronous redundant transmission mode, the trigger parameter is used for the second network entity to identify the first access path unacknowledged packets on.
  • the processor 62b is further configured to: send a fifth message to the third network entity through the communication component 63b, where the fifth message at least includes 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 receives a sixth message sent by the third network entity, indicating that the asynchronous redundant transmission mode can be executed.
  • the sixth message includes: at least one of the configuration indication information and the trigger parameter.
  • the processor 62b is specifically configured to: from the sixth message Obtain at least one of configuration indication information and trigger parameters from the sixth message, and when one of the information is obtained from the sixth message, configure the other information locally; or use the asynchronous redundant transmission mode according to the above request.
  • the first indication information is to configure the above configuration indication information and trigger parameters locally.
  • the above configuration indication information is used to instruct the second access path to configure the first data flow for unacknowledged data packets on the first access path.
  • embodiments of the present application also provide a computer-readable storage medium storing computer programs/instructions.
  • the processor can implement the above method embodiments that can be performed by the first network entity. steps performed.
  • Figure 6c is a schematic structural diagram of another network entity provided by an exemplary embodiment of the present application.
  • This network entity can be implemented as the second network entity in the previous embodiment.
  • the user equipment includes: memory 61c, Processor 62c and communication component 63c.
  • the network entity also includes a power supply component 64c.
  • the processor 62c is coupled to the memory 61c, and is used to execute the computer program in the memory 61c, and is used to: receive a second message sent by the first network entity through the communication component 63c, where the second message at least includes information about the first access path.
  • the MA PDU session request corresponding to the first access path uses the asynchronous redundant transmission mode; according to the above configuration instruction information, configure on the second access path for the second access path.
  • a first data stream of unconfirmed data packets on an access path caching the unconfirmed data packets on the first access path into the first data stream for asynchronous redundant transmission through the second access path;
  • the second access path is another access path corresponding to the MA PDU session.
  • the processor 62c when buffering unacknowledged data packets on the first access path into the first data stream for asynchronous redundant transmission through the second access path, is specifically used to: Identify unconfirmed data packets on the first access path according to the trigger parameters and/or trigger instructions of the asynchronous redundant transmission mode; cache the identified unconfirmed data packets into the first data stream to pass through the second access path The path performs asynchronous redundant transmission.
  • the processor 62c is also configured to: obtain the trigger parameter and/or trigger indication of the asynchronous redundant transmission mode.
  • the obtaining operation includes at least one of the following methods: obtaining the trigger parameter from the second message; receiving Trigger parameters sent by the application layer; receive trigger instructions sent by the application layer.
  • the processor 62c when the processor 62c identifies the unacknowledged data packet on the first access path according to the trigger parameter and/or the trigger indication, the processor 62c is specifically configured to: convert the trigger parameter on the first access path to Data packets sent within a period in which the represented delay difference exceeds the set threshold are regarded as unconfirmed data packets; and/or data packets on the first access path that do not receive a confirmation message before the trigger indication arrives are regarded as unconfirmed data packets. data pack.
  • the processor 62c is also configured to: measure the QoS of other access paths except the first access path; and select the access whose QoS meets the preset conditions according to the QoS of the other access paths. path as the second access path.
  • embodiments of the present application also provide a computer-readable storage medium storing computer programs/instructions.
  • the processor can implement the above method embodiments by the second network entity. steps performed.
  • the memory in the above embodiments can be implemented by any type of volatile or non-volatile storage device or their combination, 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 disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM Erasable programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory magnetic memory
  • flash memory magnetic or optical disk.
  • the communication component in each of the above embodiments is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices.
  • the device where the communication component is located can access wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G/LTE, 5G and other mobile communication networks, or a combination thereof.
  • the communication component receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component further includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the display in the above embodiments includes a screen, and the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, swipes, 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 action.
  • the power supply component in the above embodiments provides power for various components of the device where the power supply component is located.
  • a power component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which the power component resides.
  • the audio components in the above embodiments may be configured to output and/or input audio signals.
  • the audio component includes a microphone (MIC), and when the device where the audio component is located is in an operating mode, such as call mode, recording mode, and voice recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal may be further stored in memory or sent via a communications component.
  • the audio component further includes a speaker for outputting audio signals.
  • embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines 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, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that when the computer A series of operating steps are executed on a computer or other programmable device to produce a computer-implemented process, whereby instructions executed on a computer or other programmable device provide for implementing a process or processes in a flowchart and/or a block in a block diagram or steps for a function specified in multiple boxes.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in computer-readable media, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash random access memory
  • Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information.
  • Information may be computer-readable instructions, data structures, modules of programs, 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), and read-only memory.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • read-only memory read-only memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory or other memory technology
  • compact disc read-only memory CD-ROM
  • DVD digital versatile disc
  • Magnetic tape cassettes tape disk storage or other magnetic storage devices or any other non-transmission medium can be used to store information that can be accessed by a computing device.
  • computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

Landscapes

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

Abstract

本申请实施例提供一种多路径冗余传输方法、用户设备、网络实体及存储介质。在本申请实施例中，由用户设备与移动通信网络中的网络实体相互配合，针对MA PDU会话，实现基于多路径的异步冗余传输的激活与去激活，这样针对一条接入路径上已传输但未能及时被确认的数据包，能够在另一条接入路径上对这些数据包进行异步冗余传输，丰富冗余传输机制的实现方式，可以让UE在下行传输中有效地解决多路径后发先至问题，尽快获得相应的数据包，提升用户对数据流尤其是对实时性要求较高的数据流的QoE。

Description

多路径冗余传输方法、用户设备、网络实体及存储介质
本申请要求于2022年05月06日提交中国专利局、申请号为202210489734.5、申请名称为“多路径冗余传输方法、用户设备、网络实体及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种多路径冗余传输方法、用户设备、网络实体及存储介质。
背景技术
在3GPP Release 16中增加了接入流量导向、切换和拆分(Access Traffic Steering，Switching and Splitting，ATSSS)功能。为了支持ATSSS特性，5G系统架构进行了扩展，用户设备(User Equipment，UE)支持一种或多种转向功能，每个转向功能都支持跨3GPP接入和非3GPP接入的流量转向、切换和拆分。
目前ATSSS中支持冗余传输模式，即同时在3GPP路径和非3GPP路径上传输相同的数据包，通过在服务质量(Quality of Service，QoS)较好的3GPP路径进行冗余传输，保证UE尽快获得相应的数据包，改善数据流的体验质量(Quality of Experience，QoE)。
现有冗余传输模式的实现较为单一，无法解决多路径下的后发先至(multi-path head of line blocking)问题，后发先至问题是指多路径传输下，当一条路径的传输时延明显大于另一条路径时，此路径上先传输的数据包往往在另一条路径后发的数据包到达时还没有被接收到，从而引发了数据包缺失或者乱序的问题。为了解决上述问题，需要提供新的多路径冗余传输方案。
发明内容
本申请的多个方面提供一种多路径冗余传输方法、用户设备、网络实体及存储介质，用以提供一种新的多路径冗余传输方式，使得UE在下行传输中有效地解决多路径后发先至问题，尽快获得相应的数据包，改善数据流的QoE。
本申请实施例提供一种多路径冗余传输方法，适用于用户设备，所述方法包括：向第一网络实体发送第一消息，所述第一消息至少包括多锚点协议数据单元MA PDU会话请求使用异步冗余传输模式的第一指示信息，以使所述第一网络实体向第二网络实体发送第二消息，所述异步冗余传输模式是冗余传输模式中的一种；接收所述第一网络实体返回的第四消息，所述第二消息和所述第四消息中至少包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，以使所述第二网络实体根据所述配置指示信息通过第二接入路径对所述第一接入路径上的未确认数据包进行异步冗余传输。
本申请实施例还提供一种多路径冗余传输方法，适用于第一网络实体，所述方法包括： 接收用户设备发送的第一消息，所述第一消息中至少包括多锚点协议数据单元MA PDU会话请求使用异步冗余传输模式的第一指示信息，所述异步冗余传输模式是冗余传输模式中的一种；根据所述第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息；向第二网络实体发送第二消息，并向所述用户设备发送第四消息，所述第二消息和所述第四消息中至少包括所述配置指示信息，以使所述第二网络实体通过第二接入路径对所述第一接入路径上的未确认数据包进行异步冗余传输。
本申请实施例还提供一种多路径冗余传输方法，适用于第二网络实体，所述方法包括：接收第一网络实体发送的第二消息，所述第二消息中至少包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，所述第一接入路径对应的多锚点协议数据单元MA PDU会话请求使用异步冗余传输模式；根据所述配置指示信息，在第二接入路径上配置针对所述第一接入路径上的未确认数据包的第一数据流；将所述第一接入路径上的未确认数据包缓存至所述第一数据流中，以通过所述第二接入路径进行异步冗余传输，所述第二接入路径是MA PDU会话对应的另一条接入路径。
本申请实施例还提供一种用户设备，包括：存储器、处理器和通信组件；所述存储器，用于存储计算机程序；所述处理器用于执行所述计算机程序，以用于实现本申请实施例提供的可由用户设备执行的多路径冗余传输方法中的步骤。
本申请实施例还提供一种网络实体，可作为第一网络实体实现，包括：存储器、处理器和通信组件；所述存储器，用于存储计算机程序；所述处理器用于执行所述计算机程序，以用于实现本申请实施例提供的可由第一网络实体执行的多路径冗余传输方法中的步骤。
本申请实施例还提供一种网络实体，可作为第二网络实体实现，包括：存储器、处理器和通信组件；所述存储器，用于存储计算机程序；所述处理器用于执行所述计算机程序，以用于实现本申请实施例提供的可由第二网络实体执行的多路径冗余传输方法中的步骤。
本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，当计算机程序被处理器执行时，致使处理器能够实现本申请各实施例提供的多路径冗余传输方法中的步骤。
在本申请实施例中，由用户设备与移动通信网络中的网络实体相互配合，针对MA PDU会话，实现基于多路径的异步冗余传输的激活与去激活，这样针对一条接入路径上已传输但未能及时被确认的数据包，能够在另一条接入路径上对这些数据包进行异步冗余传输，丰富冗余传输机制的实现方式，可以让UE在下行传输中有效地解决多路径后发先至问题，尽快获得相应的数据包，提升用户对数据流尤其是对实时性要求较高的数据流的QoE。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1a为本申请示例性实施例提供的一种移动通信网络的局部架构示意图；
图1b为本申请示例性实施例提供的一种异步冗余传输模式的传输状态示意图；
图2a为本申请示例性实施例提供的一种多路径冗余传输方法的交互流程示意图；
图2b为本申请示例性实施例提供的又一种多路径冗余传输方法的交互流程示意图；
图2c为本申请示例性实施例提供的又一种多路径冗余传输方法的交互流程示意图；
图3a为本申请示例性实施例提供的又一种多路径冗余传输方法的交互流程示意图；
图3b为本申请示例性实施例提供的又一种多路径冗余传输方法的交互流程示意图；
图4a为本申请示例性实施例提供的又一种多路径冗余传输方法的流程示意图；
图4b为本申请示例性实施例提供的又一种多路径冗余传输方法的流程示意图；
图4c为本申请示例性实施例提供的又一种多路径冗余传输方法的流程示意图；
图5a为本申请又一示例性实施例提供的一种多路径冗余传输装置的结构示意图；
图5b为本申请又一示例性实施例提供的一种多路径冗余传输装置的结构示意图；
图5c为本申请又一示例性实施例提供的一种多路径冗余传输装置的结构示意图；
图6a为本申请示例性实施例提供的一种用户设备的结构示意图；
图6b为本申请示例性实施例提供的一种网络实体的结构示意图；
图6c为本申请示例性实施例提供的又一种网络实体的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
针对现有冗余传输模式的实现较为单一，无法解决多路径下的后发先至的技术问题，在本申请实施例中，由用户设备与移动通信网络中的网络实体相互配合，针对MA PDU会话实现基于多路径的异步冗余传输的激活与去激活，这样针对一条接入路径上已传输但未能及时被确认的数据包，能够在另一条接入路径上对这些数据包进行异步冗余传输，丰富冗余传输机制的实现方式，可以让UE在下行传输中有效地解决多路径后发先至问题，尽快获得相应的数据包，提升用户对数据流尤其是对实时性要求较高的数据流的QoE。
本实施例的移动通信网络包括接入网和核心网，接入网主要包括基站，接入网可以是多个，例如可以同时包括3GPP接入网和非3GPP(Non-3GPP)接入网；核心网包括但不限于以下多个网络实体：鉴权服务器功能(Authentication Server Function，AUSF)、用户平面功能(User plane Function，UPF)、接入和移动性管理功能(Access and Mobility Management Function，AMF)、统一数据管理(Unified Data Management，UDM)、网络开放功能(Network Exposure Function，NEF)、会话管理功能(Session Management Function，SMF)、网络切片选择功能(Network Slice Selection Function，NSSF)、网络存储功能(NF Repository Function，NRF)、策略控制功能(Policy Control function，PCF)、应用层功能(Application Function，AF)等。
另外，本实施例的移动通信网络支持ATSSS特性，ATSSS中支持冗余传输模式，该冗余传输模式可以称为是冗余转向模式(redundant steering mode)。其中，冗余传输模式是一种可以在多条路径上对数据包进行冗余传输的模式。为了支持ATSSS特性，本申请实施例移动通信网络的系统架构做了拓展，如图1a所示，本申请实施例中的UE支持一种或多种转向功能，例如MPTCP(MultiPath TCP)功能和/或ATSSS-LL和/或MP-QUIC(Mutipath QUIC)功能。根据网络提供的ATSSS规则，UE中的每个转向功能都支持多路径(multi-path)接入的流量转向、切换和拆分。对于以太网类型的MA PDU(Mutil Anchor Protocol Data Unit，多锚点协议数据单元)会话，ATSSS-LL功能在UE中是强制性的。相应地，如图1a所示， 本申请实施例中的UPF可以支持MPTCP代理功能，它通过使用MPTCP协议与UE中的PTCP功能进行通信；UPF也可以支持ATSSS-LL功能，类似于为UE中的ATSSS-LL功能。
在图1a中，除了示出UPF和UE之外，还示出了与冗余传输相关的其它网络实体AMF、SMF和PCF。其中，AMF负责UE的接入和移动性管理功能；SMF实现会话管理，它支持会话的建立、修改和释放，UE的IP地址的分配和管理等；PCF支持管控网络行为的统一策略框架，提供策略规则给控制面执行，可以访问统一数据仓储功能(Unified Data Repository，UDR)中与策略制定相关的订阅信息。UPF主要负责核心网中用户平面数据包的路由和转发，并通过N4空中接口与SMF交互，根据SMF发布的各种策略执行相应处理，以及作为核心网与数据网络(Data Network，DN)互连的会话点等。
在本申请实施例中，UE与UPF之间存在多条接入路径，且UE与网络实体UPF、AMF、SMF、PCF等相互配合可以实现基于多路径的冗余传输过程。在图1a中，以UE与UPF之间存在的多条接入路径包括3GPP接入路径和非3GPP接入路径为例进行图示，但并不限于此。随着通信技术的发展，未来可能出现更多其它接入路径，这些接入路径同样适用于本申请实施例。冗余传输模式允许在多条接入路径上对数据包进行冗余传输，但并未限定在多条接入路径上冗余传输数据包的具体实现方式。可选地，冗余传输模式的一种具体实现方式为同步冗余传输模式，即在触发该模式传输后，在多条接入路径上同时传输相同的数据包，从而实现基于多路径的冗余传输。除此之外，本申请实施例还提供一种异步冗余传输模式(re-injection mode)，该异步冗余传输模式也可称为异步重传模式或者重新缓存重传模式，是冗余传输模式下的另一种具体实现方式，主要是指针对一条接入路径上已传输且未能及时收到对端确认的数据包，且另一条接入路径上后发的数据包先到达的情况下，重新在另一条接入路径上对这部分未能及时得到确认的数据包进行异步传输，从而实现基于多路径的冗余传输，解决一条接入路径上已传输且迟迟未收到对端返回确认消息的数据包，从而导致的后发先至问题。其中，图1b所示为异步冗余传输模式的传输状态示意图，在图1b中，两端采用异步冗余传输模式，其中，在非3GPP接入路径上传输数据包1-10，数据包1-3、8-10接收到了对端确认消息(ACK)，但早于数据包8-10发出的数据包4-7未能收到对端的确认消息，于是，从另一条接入路径即3GPP接入路径上进行异步冗余重传，以便借助于3GPP接入路径具有较好QoS的优先，确保对端及时接收到数据包4-7。
在本实施例中，UPF可以采用异步冗余传输模式向UE发送下行数据包。同理，UE也可以采用异步冗余传输模式向UPF发送上行数据包。其中，上行数据包的异步冗余传输过程与下行数据包的异步冗余传输过程相同或相似，在本申请下述实施例中，重点以UPF采用异步冗余传输模式向UE发送下行数据包为例，对本申请实施例提供的多路径冗余传输方法进行详细说明。
图2a为本申请示例性实施例提供的一种多路径冗余传输方法的交互流程示意图。如图2a所示，该方法包括：
21a、UE向第一网络实体发送第一消息，第一消息至少包括MA PDU会话请求使用异步冗余传输模式的第一指示信息，异步冗余传输模式是冗余传输模式中的一种。
22a、第一网络实体在接收到第一消息后，根据第一消息中包含的请求使用异步冗余传输模式的第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配 置指示信息。
23a、第一网络实体向第二网络实体发送第二消息，第二消息中至少包括上述配置指示信息。
24a、第二网络实体在接收到第二消息后，根据第二消息中包含的配置指示信息，在第二接入路径上配置针对第一接入路径上的未确认数据包的第一数据流。
25a、第二网络实体向第一网络实体返回第三消息，以通知第一网络实体已经完成配置。
26a、第一网络实体在接收到第三消息后，向UE发送第四消息，第四消息中至少包括上述配置指示信息，以使UE了解可以使用异步冗余传输模式。
27a、第二网络实体将第一接入路径上的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输。
28a、UE在异步冗余传输模式下，在第二接入路径上重新接收第一接入路径上的未确认数据包。
在本实施例中，UE与第二网络实体之间存在多条接入路径，在正常情况下，第二网络实体可以在多条接入路径上分别向UE传输不同的数据包，以发挥多条接入路径的优势，提高数据包的传输效率。但是，为了发挥多路径冗余传输的有益效果，UE可以在创建MA PDU会话过程中，或者在修改MA PDU会话过程中，向第一网络实体发送第一消息，以请求针对MA PDU会话使用冗余传输模式中的异步冗余传输模式进行数据包传输。第一网络实体是负责会话管理的网络实体，例如可以是但不限于SMF。第二网络实体是与UE进行用户平面数据包转发的网络实体，例如可以是但不限于UPF。
可选地，第一消息中可以仅包括请求使用异步冗余传输模式的第一指示信息(re-injection mode)，或者，也可以同时包含MA PDU会话支持冗余传输模式的第二指示信息(indication of support for redundant mode)和MA PDU会话请求使用异步冗余传输模式的第一指示信息(re-injection mode)，对此不做限定。
第一网络实体接收到第一消息之后，根据第一消息中至少包含的请求使用异步冗余传输模式的第一指示信息，确定UE请求使用异步冗余传输模式，因此，需要为第二网络实体生成针对第一接入路径上的未确认数据包进行异步重传的配置指示信息，以使第二网络实体根据该配置指示信息进行异步重传冗余模式的相关配置，并通过第三消息将该配置指示信息发送给第二网络实体。
在本实施例中，在正常情况下，第二网络实体可以在多条接入路径上向UE传输不同的数据包，以发挥多条接入路径的优势，提高数据包的传输效率。但是，当出现后发先至问题时，即其中一条接入路径上已传输且未能及时收到UE确认的数据包，而另一条接入路径上后发的数据包先到达UE的情况，可触发异步冗余传输模式。其中，第一接入路径是指MA PDU会话当前使用的一条接入路径，是后发先至问题中“已传输且未能及时收到UE确认的数据包”的一条接入路径；相应地，第二接入路径是MA PDU会话对应的另一条接入路径，是后发先至问题中“后发的数据包先到达”的一条接入路径，是用来对第一接入路径上的未确认数据包进行异步冗余传输时使用的接入路径。在本实施例中，并不限定第一接入路径和第二接入路径，相对而言，第二接入路径的QoS要优于第一接入路径的QoS，可选地，第一接入路径可以是非3GPP接入路径，而第二接入路径是3GPP接入路径。QoS可以具体指多个指标参数，包括但不限于延时，抖动，丢包率，路径负载等。
在本实施例中，第二网络实体无论在哪条接入路径上向UE发送数据包，需要UE在设定的时间范围内返回确认消息，如果针对任一数据包，在发送该数据包之后若未能及时收到UE返回的确认消息，则将该数据包称为未确认数据包。据此，第一接入路径上的未确认数据包是指已在第一接入路径上传输但未能及时收到UE返回的确认消息的数据包。其中，未能及时收到UE返回确认消息的数据包，主要是指出现先发后至问题时晚于后发数据包的先发数据包。
为了能够使用第二接入路径对第一接入路径上的未确认数据包进行异步冗余传输(异步冗余传输也可以简称为异步重传)，第二网络实体在接收到第二消息之后，根据第二消息中的配置指示信息，在第二接入路径上配置针对第一接入路径上的未确认数据包的第一数据流，第一数据流是用于对第一接入路径上的未确认数据包进行冗余传输的一条数据流，该数据流实际上是用于存储数据包的数据队列。该数据队列具有较高的接入信道优先级，可选地，在5G网络中，优先级可以用5G QoS标识(5G QoS Identifier，5QI)来表征；相应地，第一数据流可以是5G QoS数据流，但并不限于此。5G QoS标识(5QI)是用于提供给5G QoS数据流的特定QoS转发行为(例如，分组丢失率，分组延迟预算)的参考标量。这可以通过5QI引用节点的特定参数在接入网络中实现，所述特定参数是指控制QoS转发处理的参数。
在配置第一数据流之后，第二网络实体一方面可以向第一网络实体返回第三消息，以告知第一网络实体已经完成异步冗余传输模式的相关配置。第一网络实体据此向UE发送第四消息，并在第四消息中携带上述配置指示信息，以使UE了解UPF已经完成异步冗余传输模式的相关配置，可以使用异步冗余传输模式。对UE而言，还可以配置用于MA PDU会话的客户端，以在异步冗余传输模式下接收数据包。另一方面，第二网络实体可以识别第一接入路径上的未确认数据包并将识别到的未确认数据包缓存至第一数据流中，以便通过第二接入路径进行异步冗余传输。
其中，在第二接入路径上除了存在第一数据流之外，还可能存在其它数据流，这些数据流具有不同的服务质量指示(QI)，UPF根据这些数据流的服务质量指示对这些数据流进行调度，被调度到的数据流中的数据包可以在第二接入路径上进行传输。可选地，在5G网络中，数据流的QI可称为5QI(5G QoS Identifier)。在本实施例中，并不限定数据流的5QI的实现方式，但是，为了保证第一数据流能够及时得到调度，第一数据流的5QI可以具有较高优先级，5QI的优先级越高，对应数据流越优先被调度。
当第一数据流被调度时，被缓存至第一数据流中的第一接入路径上的未确认数据包在第二接入路径上被重新传输。对UE来说，在异步冗余传输模式下，可在第二接入路径上重新接收第一接入路径上的未确认数据包，实现基于多路径的异步冗余传输，一方面丰富了冗余传输机制的实现方式，另一方面可以让UE在下行传输中有效地解决多路径后发先至问题，尽快获得相应的数据包，提升用户对数据流尤其是对实时性要求较高的数据流的QoE。
在本申请各实施例中，并不限定第一网络实体确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息的方式。在一可选实施例中，可以由第一网络实体本地配置。在另一可选实施例中，可由第一网络实体和第三网络实体进行交互，由第三网络实体负责提供该配置指示信息。第三网络实体是指负责策略管理的网络实体，例如可以是 但不限于PCF。
进一步可选地，第一网络实体除了确定上述配置指示信息之外，还可以确定异步冗余传输模式对应的触发参数，并提供给第二网络实体。可选地，第一网络实体可以将该触发参数携带在第二消息中一并提供给第二网络实体。该触发参数用于供第二网络实体识别第一接入路径上的未确认数据包，这也是对异步冗余传输模式的激活操作。可选地，该触发参数可以是两条接入路径之间的延时差(delay difference)。这样，第二网络实体每次在第一接入路径上传输数据包之后，可以通过第二网络实体(如UPF)来监测两条接入路径之间传输数据包的延时差，当延时差超过一个阈值后，则确定在该延时差超过阈值的期间内传输的数据包为需要进行异步重传的未确认数据包，将该未确认数据包缓存至第一数据流中。在时延差重新低于阈值时，第二网络实体可以在多条接入路径上分别向UE传输不同的数据包，这相当于是对异步冗余重传模式的去激活，利用多条接入路径同时传输不同数据包，有利于提高数据包传输效率。也就是说，随着时延差的变化，当时延差较大时，可以激活异步冗余重传模式，在时延差重新变小时，可以去激活异步冗余重传模式。
在本申请各实施例中，也不限定第一网络实体确定上述触发参数的方式。在一可选实施例中，可以由第一网络实体本地配置。在另一可选实施例中，可由第一网络实体和第三网络实体进行交互，由第三网络实体负责提供该触发参数。
在一可选实施例中，第一网络实体在接收到第一消息后，同时确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，以及异步冗余传输模式的触发参数。如图2b所示，该实施例包括以下步骤：
21b、UE向第一网络实体发送第一消息，第一消息至少包括MA PDU会话请求使用异步冗余传输模式的第一指示信息，异步冗余传输模式是冗余传输模式中的一种。
22b、第一网络实体在接收到第一消息后，根据第一消息中包含的请求使用异步冗余传输模式的第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，以及异步冗余传输模式的触发参数。
可选地，第一网络实体确定配置指示信息和触发参数的方式包括但不限于以下几种：
方式A1：第一网络实体在接收到第一消息后，根据第一消息中包含的请求使用异步冗余传输模式的第一指示信息，本地配置针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，以及异步冗余传输模式的触发参数。
方式A2：第一网络实体在接收到第一消息后，根据第一消息中包含的请求使用异步冗余传输模式的第一指示信息，向第三网络实体发送第五消息，第五消息中至少包括请求使用异步冗余传输模式的第一指示信息，以使第三网络实体确认是否可以执行异步冗余传输模式；以及接收第三网络实体发送的第六消息，第六消息一方面指示可以执行异步冗余传输模式；另一方面还包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，以及异步冗余传输模式的触发参数。第一网络实体从第六消息中解析出上述配置指示信息和触发参数。在该方式A2中，上述配置指示信息和触发参数均由第三网络实体提供。
方式A3：第一网络实体在接收到第一消息后，根据第一消息中包含的请求使用异步冗余传输模式的第一指示信息，向第三网络实体发送第五消息，第五消息中至少包括请求使用异步冗余传输模式的第一指示信息，以使第三网络实体确认是否可以执行 异步冗余传输模式；以及接收第三网络实体发送的第六消息，第六消息一方面指示可以执行异步冗余传输模式；另一方面还包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息。第一网络实体从第六消息中解析出上述配置指示信息，并本地配置异步冗余传输模式的触发参数。在该方式A3中，上述配置指示信息由第三网络实体提供，上述触发参数由第二网络实体本地配置。
方式A4：第一网络实体在接收到第一消息后，根据第一消息中包含的请求使用异步冗余传输模式的第一指示信息，向第三网络实体发送第五消息，第五消息中至少包括请求使用异步冗余传输模式的第一指示信息，以使第三网络实体确认是否可以执行异步冗余传输模式；以及接收第三网络实体发送的第六消息，第六消息一方面指示可以执行异步冗余传输模式；另一方面还包括异步冗余传输模式的触发参数。第一网络实体从第六消息中解析出上述触发参数，并本地配置针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息。在该方式A4中，上述触发参数由第三网络实体提供，上述配置指示信息由第二网络实体本地配置。
23b、第一网络实体向第二网络实体发送第二消息，第二消息中包括上述配置指示信息和触发参数。
24b、第二网络实体在接收到第二消息后，根据第二消息中包含的配置指示信息，在第二接入路径上配置针对第一接入路径上的未确认数据包的第一数据流。
25b、第二网络实体向第一网络实体返回第三消息，以通知第一网络实体已经完成配置。
26b、第一网络实体在接收到第三消息后，向UE发送第四消息，第四消息中包括上述配置指示信息和触发参数，以使UE了解可以使用异步冗余传输模式。
27b、第二网络实体根据第二消息中包含的触发参数，识别第一接入路径上的未确认数据包，将识别到的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输。
具体地，该触发参数表示两条接入路径之间传输数据包的延时差，第二网络实体可以监测第一接入路径和第二接入路径之间传输数据包的时延差，将在第一接入路径上在该时延差超过设定阈值期间内发送的数据包作为需要进行异步重传的未确认数据包，这些数据包通常会因为时延差较大，而无法及时收到UE返回确认消息。
28b、UE在异步冗余传输模式下，在第二接入路径上重新接收第一接入路径上的未确认数据包。
进一步，在时延差重新低于阈值时，第二网络实体可以在多条接入路径上分别向UE传输不同的数据包，这相当于是对异步冗余重传模式的去激活，利用多条接入路径同时传输不同数据包，有利于提高数据包传输效率。也就是说，随着时延差的变化，当时延差较大时，可以激活异步冗余重传模式，在时延差重新变小时，可以去激活异步冗余重传模式。
在上述实施例中，以异步冗余传输模式的触发参数是由第一网络实体或第三网络实体提供为例进行说明，但并不限于此。关于触发第二网络实体识别第一接入路径上的未确认数据包所需的触发参数，也可以由应用层或者应用层协议(例如MP-QUIC协议)提供，即上述配置指示信息由第一网络实体或第三网络实体提供，并通过第二消息和第四消息分别提供给第二网络实体和UE，第二网络实体在识别第一接入路径上的未确认数据包之前， 还可以接收应用层或者应用层协议(例如MP-QUIC协议)发送的触发参数，并根据应用层或者应用层协议(例如MP-QUIC协议)提供的触发参数识别第一接入路径上的未确认数据包。
需要说明的是，应用层是指UE上的上层应用，如APP，或者是应用层所用到的传输协议，例如MP-QUIC传输协议或者传输隧道。该上层应用或者应用层的传输协议隧道可以自行配置异步冗余传输模式的触发参数，或者，也可以向第一网络实体发送第七消息，以请求第一网络实体配置异步冗余传输模式所需的触发参数；然后，接收第一网络实体返回的第八消息，从第八消息中解析出第一网络实体配置的触发参数。这里上层应用(或者UE)请求第一网络实体配置异步冗余传输模式所需的触发参数，包括：在没有触发参数的情况下，请求第一网络实体配置触发参数的情况，也包括在已有触发参数的情况下，因为触发参数不合适，请求第一网络实体重新修改或重新配置触发参数的情况。无论是以何种方式获得触发参数，在得到触发参数之后，可以向第二网络实体发送第九消息，在第九消息中包含有该触发参数。
需要说明的是，应用层可以将触发参数提供给第二网络实体，由第二网络实体根据该触发参数激活异步冗余传输模式，也就是识别第一接入路径上在该传输参数表示的时延差超过设定阈值期间内发送的数据包作为需要进行异步重传的未确认数据包，并缓存至第一数据流中，以通过第二接入路径进行异步冗余传输的过程。除此之外，应用层也可以向第二网络实体提供异步冗余传输模式的触发指示，第二网络实体根据该触发指示激活异步冗余传输模式，即识别第一接入路径上的未确认数据包，并缓存至第一数据流中，以通过第二接入路径进行异步冗余传输。该触发指示也用于供第二网络实体识别第一接入路径上的未确认数据包，但却与触发参数有所不同，该触发指示用于供第二网络实体将第一接入路径上已传输但在该触发指示到达之前未接收到确认消息的数据包作为未确认数据包。
可选地，由上层应用或者应用层传输协议来提供触发参数或触发指示，具体的，应用层传输协议的触发机制可以是MP-QUIC调度协议中的信令QoE状态信令(QoE_STATUS_SIGNAL)。QOE状态信令中可以携带UE接收到下行数据包的缓存包序列情况。UPF可以根据QoE状态信令来触发异步冗余传输。
在一可选实施例中，第一网络实体在接收到第一消息后，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，并由应用层向第二网络实体提供异步冗余传输模式的触发指示。如图2c所示，该实施例包括以下步骤：
21c、UE向第一网络实体发送第一消息，第一消息至少包括MA PDU会话请求使用异步冗余传输模式的第一指示信息，异步冗余传输模式是冗余传输模式中的一种，也可以是一种独立的冗余传输模式。
22c、第一网络实体在接收到第一消息后，根据第一消息中包含的请求使用异步冗余传输模式的第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息。
23c、第一网络实体向第二网络实体发送第二消息，第二消息中至少包括上述配置指示信息。
24c、第二网络实体在接收到第二消息后，向第一网络实体返回第三消息，以通知第一网络实体已收到第二消息。
25c、第一网络实体在接收到第三消息后，向UE发送第四消息，第四消息中包括上述配置指示信息，以使UE了解可以使用异步冗余传输模式。
26c、UE向第二网络实体发送异步冗余传输模式的触发指示，该触发指示用于供第二网络实体将第一接入路径上已传输但在该触发指示到达之前未接收到确认消息的数据包识别为未确认数据包。
27c、第二网络实体根据第二消息中包含的配置指示信息，在第二接入路径上配置针对第一接入路径上的未确认数据包的第一数据流，并根据上述触发指示，将第一接入路径上的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输。
28c、UE在异步冗余传输模式下，在第二接入路径上重新接收第一接入路径上的未确认数据包。
在本实施例中，与前述实施例相同或相似的步骤可参见前述实施例，在此不再赘述。在本实施例中，上述触发指示用于供第二网络实体激活异步冗余传输模式，即将第一接入路径上在触发指示到达之前未收到确认消息的数据包作为未确认数据包并缓存至第一数据流中，以通过第二接入路径进行异步冗余传输。在将此次未确认数据包缓存至第一数据流之后，或者通过第二接入路径将此次的未确认数据包全部进行异步冗余传输之后，第二网络实体可以重新在多条接入路径上分别向UE传输不同的数据包，这相当于是对异步冗余重传模式的去激活，利用多条接入路径同时传输不同数据包，有利于提高数据包传输效率。也就是说，应用层可以按需(例如在出现后发先至问题时)向第二网络实体提供触发指示，使得第二网络实体动态激活/去激活异步冗余重传模式。
在此说明，第二网络实体可以单独根据触发参数或触发指示来识别第一接入路径上的未确认数据包(即激活异步冗余重传模式)，也可以同时结合触发参数和触发指示来识别第一接入路径上的未确认数据包(即激活异步冗余重传模式)。关于同时结合触发参数和触发指示来识别第一接入路径上的未确认数据包的情况，第二网络实体在接收到触发指示的情况下可以激活异步冗余重传模式，即需要将第一接入路径上已传输但在该触发指示到达之前未接收到确认消息的数据包作为未确认数据包，另外，第二网络实体还可以将第一接入路径上在该触发参数表示的时延差超过设定阈值期间内发送数据包作为未确认数据包。关于同时结合触发参数和触发指示来识别第一接入路径上的未确认数据包的情况，触发参数可以由上层应用提供，也可以由第一网络实体或第三网络实体提供，对此不做限定。
在上述或下述各实施例中，并未限定“配置指示信息”的实现方式，凡是能够指示在第二接入路径配置针对第一接入路径上的未确认数据包的第一数据流的信息实现方式均适用于本申请实施例。在一可选实施例中，该配置指示信息用于指示在第二接入路径针对第一接入路径上的未确认数据包创建新的数据流，并指示该新的数据流具有较高的5QI，以便于得到优先调度，保证UE及时收到数据包。在该可选实施例中，该配置指示信息可以包括第一指示信息和第一5QI，第一指示信息用于指示在第二接入路径针对第一接入路径上的未确认数据包创建新的数据流，第一5QI是指该新的数据流应该具有的5QI。基于此，第二网络实体根据配置指示信息，在第二接入路径上配置针对所述第一接入路径上的未确认数据包的第一数据流的一种方式包括：根据该配置指示信息中的第一指示信息，针对第一接入路径上的未确认数据包在第二接入路径上创建新的数据流，并配置该新的数据流的5QI为第一5QI。在该实施例中，该新的数据流即为第一数据流。
在另一可选实施例中，该配置指示信息用于指示将第一接入路径上的未确认数据包缓存到第二接入路径上具有较高优先级的5QI的已有数据流，以便于得到优先调度，保证UE及时收到数据包。在该可选实施例中，该配置指示信息可以包括第二指示信息和第二5QI，第二指示信息用于指示将第一接入路径上的未确认数据包缓存至第二接入路径上具有第二5QI的已有数据流，第二5QI的优先级较高，例如高于设定的优先级阈值。基于此，第二网络实体根据配置指示信息，在第二接入路径上配置针对所述第一接入路径上的未确认数据包的第一数据流的一种方式包括：根据该配置指示信息中的第二5QI，确定第二接入路径上具有第二5QI的已有数据流；根据该配置指示信息中的第二指示信息，确定针对第一接入路径上的未确认数据包复用具有第二5QI的已有数据流。在该实施例中，该具有第二5QI的已有数据流即为第一数据流。在此说明，上述配置指示信息也可以不包含第二5QI，由第二网络实体自行选择第二接入路径上优先级较高的已有数据流。
在上述或下述各实施例中，并未限定第二网络实体如何确定第二接入路径。在一可选实施例中，多条接入路径为两条，记为第一接入路径和第二接入路径。在一可选实施例中，多条接入路径为两条以上，包括第一接入路径和其它接入路径，第二网络实体可以从除第一接入路径之外的其它接入路径中选择第二接入路径。关于第二接入路径的选择方式包括但不限于：
方式B1：随机从其它接入路径中选择一条作为第二接入路径。
方式B2：测量除第一接入路径之外的其它接入路径的QoS，根据其它接入路径的QoS，从中选择QoS符合预设条件的接入路径作为第二接入路径。例如，可以选择QoS大于设定阈值的接入路径作为第二接入路径。QoS可以具体指多个指标参数，包括但不限于延时，抖动，丢包率，路径负载，传输速率等。具体地，可以选择路径负载较轻的接入路径作为第二接入路径，或者，选择传输速率较快的接入路径作为第二接入路径，或者，选择丢包率较低的接入路径作为第二接入路径，等等。
在本申请上述实施例中，并未对第一网络实体、第二网络实体、第三网络实体以及各消息的实现形态进行限定，可根据移动通信网络的制式灵活而定。在下述实施例中，将以5G网络为例，结合具体网络实体以及具体消息格式对本申请实施例提供的多路径冗余传输方法进行示例性说明。在下述场景实施例中，第一网络实体为SMF，第二网络实体为UPF，第三网络实体为PCF，第一消息为PDU会话建立/修改请求消息，第二消息为N4会话建立/修改请求消息，第三消息为N4会话建立/修改响应消息，第四消息为PDU会话建立/修改响应消息，第五消息为PCF会话管理策略控制更新请求消息(Npcf_SMPolicyControl_Update request)，第六消息为PCF会话管理策略控制更新应答消息(Npcf_SMPolicyControl_Update response)；第九消息为QoE控制信号帧(QoE_STATUS_SIGNAL frame)。以及，在下述场景实施例中，以第一接入路径为非3GPP接入路径，以第二接入路径为3GPP接入路径为例进行示例性说明。
图3a为本申请示例性实施例提供的又一种多路径冗余传输方法的交互流程示意图。如图3a所示，该方法包括：
31a、UE中的上层应用与应用服务器(AS)建立通信连接，且已申请完成MA PDU会话的建立。
32a、UE向SMF发送PDU会话修改请求消息(PDU session modification request)，该消息中携带MA PDU会话支持冗余传输模式(support for redundant mode)的第二指示信息，以及请求使用异步冗余传输模式(re-injection mode)的第一指示信息。
在此说明，在MA PDU会话已建立完成的情况下，UE可以在MA PDU会话的修改过程中请求使用异步冗余传输模式。除此之外，在MA PDU会话未建立的情况下，UE可以在MA PDU会话建立过程中请求使用异步冗余传输模式，该情况下可以向SMF发送PDU会话建立请求消息(PDU session establishment request)，该消息中携带MA PDU会话支持冗余传输模式的第二指示信息，以及请求使用异步冗余传输模式的第一指示信息。
33a、SMF向PCF发送PCF会话管理策略控制更新请求消息(Npcf_SMPolicyControl_Update request)，该消息中包括请求使用异步冗余传输模式的第一指示信息，以向PCF查询是否可以执行异步冗余传输模式。
34a、PCF根据策略以及计费控制规则(Policy and Charging Control Rule)，确定可以执行异步冗余传输模式，并向SMF返回PCF会话管理策略控制更新应答消息(Npcf_SMPolicyControl_Update response)，该消息中包括针对非3GPP接入路径上的未确认数据包进行异步冗余传输的配置指示信息(configuration of unack Qos flow)和异步冗余传输模式所需的触发参数，例如两条接入路径之间的延时差(delay difference)。具体的，PCF中的策略以及计费控制规则可以包括支持多路径同步冗余传输(redundant steering mode)的规则，以及支持多路径异步冗余传输(re-injection mode)的规则。
在此说明，上述配置指示信息和触发参数中的任一种或两种也可以由SMF本地配置，可参见前述实施例中的描述，在此不再赘述。
35a、SMF向UPF发送N4会话建立/修改请求消息(N4session establishment/modification request)，该请求消息中包括N4规则和上述配置指示信息，N4规则中包含上述触发参数，如两条接入路径之间的延时差(delay difference)。
进一步可选地，N4规则中还包括：路径选择规则(including selection criteria)，初始激活/或去激活冗余传输模式的标识(initial activated/deactivated)，以及触发冗余传输机制的测量辅助信息(Measurement assistance information)。
36a、UPF根据上述配置指示信息，在3GPP接入路径上配置针对非3GPP接入路径上的未确认数据包的QoS数据流，并根据上述触发参数，将非3GPP接入路径上的未确认数据包缓存至上述配置的QoS数据流中，以在3GPP接入路径重新传输。
具体地，该触发参数表示两条接入路径之间传输数据包的延时差，UPF可以监测非3GPP接入路径和3GPP接入路之间传输数据包的时延差，将在非3GPP接入路径上在该时延差超过设定阈值期间内发送的数据包作为需要进行异步重传的未确认数据包，这些数据包通常会因为时延差较大，而无法及时收到UE返回确认消息。
37a、UPF向SMF发送N4会话建立或者修改响应消息(N4session establishment/modification response)。
38a、SMF向UE发送PDU会话建立/修改响应消息(PDU session establishment/modification response)，该消息中包括N4规则和上述配置指示信息，N4规则中包含上述触发参数。
可选地，N4规则可以是SMF可以根据ATSSS规则配置的，ATSSS规则可以由SMF 通过PCF获取。具体的，ATSSS规则可以包含在PCF中的策略以及计费控制规则中，该规则可以包括支持多路径同步冗余传输(redundant steering mode)的规则，以及支持多路径异步冗余传输(re-injection mode)的规则。
39a、UE在收到PDU会话建立/修改响应消息之后，配置MA P DU会话对应的隧道客户端(tunnel client)，该隧道客户端与UPF中的隧道服务端(tunnel server)对应，两者配合用于完成MA PDU会话过程。
40a、UE在异步冗余传输模式下，在3GPP接入路径上重新接收非3GPP接入路径上的未确认数据包。
进一步，在时延差重新低于阈值时，UPF可以在非3GPP接入路径和3GPP接入路上分别向UE传输不同的数据包，这相当于是对异步冗余重传模式的去激活；相应地，UE可以在两台条接入路径上接收不同的数据包，提高数据包传输效率。也就是说，随着时延差的变化，当时延差较大时，UPF以激活异步冗余重传模式，在时延差重新变小时，UPF可以去激活异步冗余重传模式。
图3b为本申请示例性实施例提供的又一种多路径冗余传输方法的交互流程示意图。如图3b所示，该方法包括：
31b、UE中的上层应用与应用服务器(AS)建立通信连接，并申请建立MA PDU会话。
32b、UE向SMF发送PDU会话建立请求消息(PDU session establishment request)，该消息中携带MA PDU会话支持冗余传输模式(support for redundant mode)的第二指示信息，以及请求使用异步冗余传输模式(re-injection mode)的第一指示信息。
在此说明，在MA PDU会话未建立的情况下，UE可以在MA PDU会话建立过程中请求使用异步冗余传输模式。除此之外，在MA PDU会话已建立完成的情况下，UE可以在MA PDU会话的修改过程中请求使用异步冗余传输模式，该情况下可以向SMF发送PDU会话修改请求消息(PDU session modification request)，该消息中携带MA PDU会话支持冗余传输模式的第二指示信息，以及请求使用异步冗余传输模式的第一指示信息。
33b、SMF根据第二指示信息和请求使用异步冗余传输模式的第一指示信息，确定针对非3GPP接入路径上的未确认数据包进行异步冗余传输的配置指示信息(configuration of unack Qos flow)。
可选地，SMF还可以向PCF发送PCF会话管理策略控制更新请求消息(Npcf_SMPolicyControl_Update request)，该消息中包括异步冗余传输模式的第一指示信息，以向PCF查询是否可以执行异步冗余传输模式。PCF根据策略以及计费控制规则(Policy and Charging Control Rule)，确定可以执行异步冗余传输模式，并向SMF返回PCF会话管理策略控制更新应答消息(Npcf_SMPolicyControl_Update response)。在该实施例中，Npcf_SMPolicyControl_Update response消息中可不包括上述配置指示信息。
34b、SMF向UPF发送N4会话建立/修改请求消息(N4session establishment/modification request)，该消息中包括N4规则和上述配置指示信息，N4规则中包括路径选择规则(including selection criteria)，初始激活/或去激活冗余传输模式的标识(initial activated/deactivated)，以及触发冗余传输机制的测量辅助信息(Measurement assistance information)。
35b、UPF向SMF发送N4会话建立或者修改响应消息(N4session establishment/modification response)。
36b、SMF向UE发送PDU会话建立/修改响应消息(PDU session establishment/modification response)，该消息中包括N4规则和上述配置指示信息。
37b、UE在收到PDU会话建立/修改响应消息之后，配置MA P DU会话对应的隧道客户端(tunnel client)，该tunnel client与UPF中的隧道服务端(tunnel server)对应，两者配合用于完成MA P DU会话过程。
38b、UE向UPF发送异步冗余传输模式的触发指示(indication from MP-QUIC/DCCP layer for triggering re-injection mode)。
39b、UPF根据上述配置指示信息，在3GPP接入路径上配置针对非3GPP接入路径上的未确认数据包的QoS数据流，并根据上述触发指示，将非3GPP接入路径上的未确认数据包缓存至上述配置的QoS数据流中，以在3GPP接入路径重新传输。
UPF在接收到应用层提供的触发指示时，将非3GPP接入路径上已传输且在触发指示到达之前未收到确认消息的数据包作为需要进行异步重传的未确认数据包，缓存至第一数据流中，以通过第二接入路径进行异步冗余传输。
40b、UE在异步冗余传输模式下，在3GPP接入路径上重新接收非3GPP接入路径上的未确认数据包。
进一步，在将此次未确认数据包缓存至第一数据流之后，或者通过3GPP接入路径将此次的未确认数据包全部进行异步冗余传输之后，UPF可以重新在两条接入路径上分别向UE传输不同的数据包，这相当于是对异步冗余重传模式的去激活，利用两条接入路径同时传输不同数据包，有利于提高数据包传输效率。也就是说，应用层可以按需(在出现后发先至问题时)向UPF提供触发指示，使得UPF动态激活/去激活异步冗余重传模式。
在本申请上述实施例中，UE在PDU会话建立或者修改过程中，向SMF请求异步冗余传输，SMF经过PCF确认后配置UPF进行异步冗余传输的QoS数据流以及触发参数，或由上层应用或者应用层传输协议来提供触发参数或触发指示，使得在UE和UPF之间实现基于多路径的异步冗余传输，可以让UE在下行传输中有效地解决多路径后发先至问题，尽快获得相应的数据包，提升用户对数据流尤其是对实时性要求较高的数据流的QoE。具体的，应用层传输协议的触发机制可以是MP-QUIC调度协议中的信令QoE状态信令(QoE_STATUS_SIGNAL)。QoE状态信令中可以携带UE接收到下行数据包的缓存包序列情况。UPF可以根据QoS状态信令来触发异步冗余传输。
图4a为本申请示例性实施例提供的又一种多路径冗余传输方法的流程示意图。该方法是从UE的角度进行的描述，如图4a所示，该方法包括：
41a、向第一网络实体发送第一消息，第一消息至少包括MA PDU会话请求使用异步冗余传输模式的第一指示信息，以使第一网络实体向第二网络实体发送第二消息，所述异步冗余传输模式是冗余传输模式中的一种；
42a、接收第一网络实体返回的第四消息，第二消息和第四消息中至少包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，以使第二网络实体根据上述配置指示信息通过第二接入路径对第一接入路径上的未确认数据包进行异步冗余传输。
在一可选实施例中，上述第四消息还包括：异步冗余传输模式的触发参数，该触发参数用于供第二网络实体识别所述第一接入路径上的未确认数据包，所述未确认数据包是指在所述触发参数表示的时延差超过设定阈值期间内发送的数据包。
在一可选实施例中，本实施例的方法还包括：向第一网络实体发送第七消息，以请求第一网络实体配置所述触发参数；接收第一网络实体返回的第八消息，第八消息包括配置的触发参数。
在一可选实施例中，上述第一消息还包括：MA PDU会话支持冗余传输模式的第二指示信息。
在一可选实施例中，本实施例的方法还包括：向第二网络实体发送异步冗余传输模式的触发指示，以供第二网络实体识别第一接入路径上的未确认数据包，所述未确认数据包是指在该触发指示到达之前未接收到确认消息的数据包。
在一可选实施例中，上述配置指示信息用于指示在第二接入路径配置针对第一接入路径上的未确认数据包的第一数据流。
上述各步骤的详细实现方式可参见前述实施例中的相关描述，在此不再赘述。
图4b为本申请示例性实施例提供的又一种多路径冗余传输方法的流程示意图。该方法是从第一网络实体的角度进行的描述，如图4b所示，该方法包括：
41b、接收UE发送的第一消息，第一消息中至少包括MA PDU会话请求使用异步冗余传输模式的第一指示信息，所述异步冗余传输模式是冗余传输模式中的一种；
42b、根据请求使用异步冗余传输模式的第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息；
43b、向第二网络实体发送第二消息，并向UE发送第四消息，第二消息和第四消息中至少包括上述配置指示信息，以使第二网络实体通过第二接入路径对第一接入路径上的未确认数据包进行异步冗余传输。
在一可选实施例中，上述第二消息中还包括：异步冗余传输模式的触发参数。基于此，本实施例的方法还包括：根据请求使用异步冗余传输模式的第一指示信息，确定异步冗余传输模式的触发参数，该触发参数用于供第二网络实体识别第一接入路径上的未确认数据包。
在一可选实施例中，根据请求使用异步冗余传输模式的第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息之前，还包括：向第三网络实体发送第五消息，第五消息中至少包括请求使用异步冗余传输模式的第一指示信息，以使第三网络实体确认是否可以执行异步冗余传输模式；以及接收第三网络实体发送的第六消息，第六消息指示可以执行异步冗余传输模式。
在一可选实施例中，上述第六消息中包括：上述配置指示信息和触发参数中的至少一种。基于此，根据请求使用异步冗余传输模式的第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息和所述异步冗余传输模式的触发参数，包括：从第六消息中获取配置指示信息和触发参数中的至少一种，并在从第六消息中获取到其中一种信息的情况下，本地配置另一种信息；或者，根据上述请求使用异步冗余传输模式的第一指示信息，本地配置上述配置指示信息和触发参数。
在一可选实施例中，上述配置指示信息用于指示在第二接入路径配置针对第一接 入路径上的未确认数据包的第一数据流。
上述各步骤的详细实现方式可参见前述实施例中的相关描述，在此不再赘述。
图4c为本申请示例性实施例提供的又一种多路径冗余传输方法的流程示意图。该方法是从第二网络实体的角度进行的描述，如图4c所示，该方法包括：
41c、接收第一网络实体发送的第二消息，第二消息中至少包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，第一接入路径对应的MA PDU会话请求使用异步冗余传输模式；
42c、根据上述配置指示信息，在第二接入路径上配置针对第一接入路径上的未确认数据包的第一数据流；
43c、将第一接入路径上的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输，第二接入路径是MA PDU会话对应的另一条接入路径。
在一可选实施例中，上述将第一接入路径上的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输，包括：根据异步冗余传输模式的触发参数和/或触发指示，识别第一接入路径上的未确认数据包；将识别到的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输。
在一可选实施例中，本实施例的还包括：获取异步冗余传输模式的触发参数和/或触发指示，该获取操作包括以下至少一种方式：从第二消息中获取触发参数；接收应用层发送的触发参数；接收应用层发送的触发指示。
在一可选实施例中，上述根据触发参数和/或触发指示识别第一接入路径上的未确认数据包，包括：将所述第一接入路径上在所述触发参数表示的时延差超过设定阈值期间内发送的数据包，作为未确认数据包；和/或，将第一接入路径上在触发指示到达之前未接收到确认消息的数据包，作为未确认数据包。
在一可选实施例中，在第二接入路径上配置针对所述第一接入路径上的未确认数据包的第一数据流之前，还包括：测量除所述第一接入路径之外的其它接入路径的QoS；根据其它接入路径的QoS，从中选择QoS符合预设条件的接入路径作为第二接入路径。
上述各步骤的详细实现方式可参见前述实施例中的相关描述，在此不再赘述。
需要说明的是，在上述实施例及附图中的描述的一些流程中，包含了按照特定顺序出现的多个操作，但是应该清楚了解，这些操作可以不按照其在本文中出现的顺序来执行或并行执行，操作的序号如21a、22a等，仅仅是用于区分开各个不同的操作，序号本身不代表任何的执行顺序。另外，这些流程可以包括更多或更少的操作，并且这些操作可以按顺序执行或并行执行。需要说明的是，本文中的“第一”、“第二”等描述，是用于区分不同的消息、设备、模块等，不代表先后顺序，也不限定“第一”和“第二”是不同的类型。
图5a为本申请又一示例性实施例提供的一种多路径冗余传输装置的结构示意图。该装置可应用于UE中，如图5a所示，该装置包括：发送模块51a和接收模块52a。
发送模块51a，用于向第一网络实体发送第一消息，第一消息至少包括MA PDU会话请求使用异步冗余传输模式的第一指示信息，以使第一网络实体向第二网络实体发送第二消息，所述异步冗余传输模式是冗余传输模式中的一种；
接收模块52a，用于接收第一网络实体返回的第四消息，第二消息和第四消息中至少包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，以 使第二网络实体根据上述配置指示信息通过第二接入路径对第一接入路径上的未确认数据包进行异步冗余传输。
在一可选实施例中，上述第四消息还包括：异步冗余传输模式的触发参数，该触发参数用于供第二网络实体识别所述第一接入路径上的未确认数据包，所述未确认数据包是指在所述触发参数表示的时延差超过设定阈值期间内发送的数据包。
在一可选实施例中，发送模块51a还用于：向第一网络实体发送第七消息，以请求第一网络实体配置所述触发参数；接收模块52a还用于：接收第一网络实体返回的第八消息，第八消息包括配置的触发参数。
在一可选实施例中，上述第一消息还包括：MA PDU会话支持冗余传输模式的第二指示信息。
在一可选实施例中，发送模块51a还用于：向第二网络实体发送异步冗余传输模式的触发指示，以供第二网络实体识别第一接入路径上的未确认数据包，所述未确认数据包是指在该触发指示到达之前未接收到确认消息的数据包。
在一可选实施例中，上述配置指示信息用于指示在第二接入路径配置针对第一接入路径上的未确认数据包的第一数据流。
图5b为本申请示例性实施例提供的又一种多路径冗余传输装置的结构示意图。如图5b所示，该装置包括：发送模块51b、接收模块52b和确定模块53b。
接收模块52b，用于接收UE发送的第一消息，第一消息中至少包括MA PDU会话请求使用异步冗余传输模式的第一指示信息，所述异步冗余传输模式是冗余传输模式中的一种；
确定模块53b，用于根据请求使用异步冗余传输模式的第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息；
发送模块51b，用于向第二网络实体发送第二消息，并向UE发送第四消息，第二消息和第四消息中至少包括上述配置指示信息，以使第二网络实体通过第二接入路径对第一接入路径上的未确认数据包进行异步冗余传输。
在一可选实施例中，上述第二消息中还包括：异步冗余传输模式的触发参数。基于此，确定模块53b还用于：根据请求使用异步冗余传输模式的第一指示信息，确定异步冗余传输模式的触发参数，该触发参数用于供第二网络实体识别第一接入路径上的未确认数据包。
在一可选实施例中，发送模块51b还用于在确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息之前，向第三网络实体发送第五消息，第五消息中至少包括请求使用异步冗余传输模式的第一指示信息，以使第三网络实体确认是否可以执行异步冗余传输模式。相应地，接收模块52b还用于：接收第三网络实体发送的第六消息，第六消息指示可以执行异步冗余传输模式。
在一可选实施例中，上述第六消息中包括：上述配置指示信息和触发参数中的至少一种。基于此，确定模块53b在确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息和所述异步冗余传输模式的触发参数时，具体用于：从第六消息中获取配置指示信息和触发参数中的至少一种，并在从第六消息中获取到其中一种信息的情况下，本地配置另一种信息；或者，根据上述请求使用异步冗余传输模式 的第一指示信息，本地配置上述配置指示信息和触发参数。
在一可选实施例中，上述配置指示信息用于指示在第二接入路径配置针对第一接入路径上的未确认数据包的第一数据流。
图5c为本申请示例性实施例提供的又一种多路径冗余传输装置的结构示意图。如图5c所示，该装置包括：发送模块51c、接收模块52c和配置模块53c。
接收模块52c，用于接收第一网络实体发送的第二消息，第二消息中至少包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，第一接入路径对应的MA PDU会话请求使用异步冗余传输模式；
配置模块53c，用于根据上述配置指示信息，在第二接入路径上配置针对第一接入路径上的未确认数据包的第一数据流；
发送模块51c，用于将第一接入路径上的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输，第二接入路径是MA PDU会话对应的另一条接入路径。
在一可选实施例中，发送模块51c具体用于：根据异步冗余传输模式的触发参数和/或触发指示，识别第一接入路径上的未确认数据包；将识别到的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输。
在一可选实施例中，接收模块52c还用于：获取异步冗余传输模式的触发参数和/或触发指示，该获取操作包括以下至少一种方式：从第二消息中获取触发参数；接收应用层发送的触发参数；接收应用层发送的触发指示。
在一可选实施例中，发送模块51c在根据触发参数和/或触发指示识别第一接入路径上的未确认数据包时，具体用于：将第一接入路径上在所述触发参数表示的时延差超过设定阈值期间内发送的数据包，作为未确认数据包；和/或，将第一接入路径上在触发指示到达之前未接收到确认消息的数据包，作为未确认数据包。
在一可选实施例中，在第二接入路径上配置针对所述第一接入路径上的未确认数据包的第一数据流之前，还包括：测量除所述第一接入路径之外的其它接入路径的QoS；根据其它接入路径的QoS，从中选择QoS符合预设条件的接入路径作为第二接入路径。
图6a为本申请示例性实施例提供的一种用户设备的结构示意图，如图6a所示，该用户设备包括：存储器61a、处理器62a以及通信组件63a。
存储器61a，用于存储计算机程序，并可被配置为存储其它各种数据以支持在用户设备上的操作。这些数据的示例包括用于在用户设备上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。
处理器62a，与存储器61a耦合，用于执行存储器61a中的计算机程序，以用于：通过通信组件63a向第一网络实体发送第一消息，第一消息至少包括MA PDU会话请求使用异步冗余传输模式的第一指示信息，以使第一网络实体向第二网络实体发送第二消息，所述异步冗余传输模式是冗余传输模式中的一种；通过通信组件63a接收第一网络实体返回的第四消息，第二消息和第四消息中至少包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，以使第二网络实体根据上述配置指示信息通过第二接入路径对第一接入路径上的未确认数据包进行异步冗余传输。
在一可选实施例中，上述第四消息还包括：异步冗余传输模式的触发参数，该触发参 数用于供第二网络实体识别所述第一接入路径上的未确认数据包，所述未确认数据包是指在所述触发参数表示的时延差超过设定阈值期间内发送的数据包。
在一可选实施例中，处理器62a还用于：通过通信组件63a向第一网络实体发送第七消息，以请求第一网络实体配置所述触发参数；接收第一网络实体返回的第八消息，第八消息包括配置的触发参数。
在一可选实施例中，上述第一消息还包括：MA PDU会话支持冗余传输模式的第二指示信息。
在一可选实施例中，处理器62a还用于：通过通信组件63a向第二网络实体发送异步冗余传输模式的触发指示，以供第二网络实体识别第一接入路径上的未确认数据包，所述未确认数据包是指在该触发指示到达之前未接收到确认消息的数据包。
在一可选实施例中，上述配置指示信息用于指示在第二接入路径配置针对第一接入路径上的未确认数据包的第一数据流。
上述各操作的详细实现方式可参见前述实施例中的相关描述，在此不再赘述。
进一步，如图6a所示，该用户设备还包括：显示器64a、电源组件65a、音频组件66a等其它组件。图6a中仅示意性给出部分组件，并不意味着用户设备只包括图6a所示组件。
相应地，本申请实施例还提供一种存储有计算机程序/指令的计算机可读存储介质，当计算机程序/指令被处理器执行时，致使处理器能够实现上述方法实施例中可由UE执行的各步骤。
图6b为本申请示例性实施例提供的一种网络实体的结构示意图，该网络实体可作为前述实施例中的第一网络实体实现，如图6b所示，该用户设备包括：存储器61b、处理器62b以及通信组件63b。进一步，如图6b所示，该网络实体还包括电源组件64b。
处理器62b，与存储器61b耦合，用于执行存储器61b中的计算机程序，以用于：通过通信组件63b接收UE发送的第一消息，第一消息中至少包括MA PDU会话请求使用异步冗余传输模式的第一指示信息，所述异步冗余传输模式是冗余传输模式中的一种；根据请求使用异步冗余传输模式的第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息；向第二网络实体发送第二消息，并向UE发送第四消息，第二消息和第四消息中至少包括上述配置指示信息，以使第二网络实体通过第二接入路径对第一接入路径上的未确认数据包进行异步冗余传输。
在一可选实施例中，上述第二消息中还包括：异步冗余传输模式的触发参数。基于此，处理器62b还用于：根据请求使用异步冗余传输模式的第一指示信息，确定异步冗余传输模式的触发参数，该触发参数用于供第二网络实体识别第一接入路径上的未确认数据包。
在一可选实施例中，处理器62b还用于：通过通信组件63b向第三网络实体发送第五消息，第五消息中至少包括请求使用异步冗余传输模式的第一指示信息，以使第三网络实体确认是否可以执行异步冗余传输模式；以及接收第三网络实体发送的第六消息，第六消息指示可以执行异步冗余传输模式。
在一可选实施例中，上述第六消息中包括：上述配置指示信息和触发参数中的至少一种。基于此，处理器62b在确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息和所述异步冗余传输模式的触发参数时，具体用于：从第六消 息中获取配置指示信息和触发参数中的至少一种，并在从第六消息中获取到其中一种信息的情况下，本地配置另一种信息；或者，根据上述请求使用异步冗余传输模式的第一指示信息，本地配置上述配置指示信息和触发参数。
在一可选实施例中，上述配置指示信息用于指示在第二接入路径配置针对第一接入路径上的未确认数据包的第一数据流。
上述各操作的详细实现方式可参见前述实施例中的相关描述，在此不再赘述。
相应地，本申请实施例还提供一种存储有计算机程序/指令的计算机可读存储介质，当计算机程序/指令被处理器执行时，致使处理器能够实现上述方法实施例中可由第一网络实体执行的各步骤。
图6c为本申请示例性实施例提供的又一种网络实体的结构示意图，该网络实体可作为前述实施例中的第二网络实体实现，如图6c所示，该用户设备包括：存储器61c、处理器62c以及通信组件63c。进一步，如图6c所示，该网络实体还包括电源组件64c。
处理器62c，与存储器61c耦合，用于执行存储器61c中的计算机程序，以用于：通过通信组件63c接收第一网络实体发送的第二消息，第二消息中至少包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，第一接入路径对应的MA PDU会话请求使用异步冗余传输模式；根据上述配置指示信息，在第二接入路径上配置针对第一接入路径上的未确认数据包的第一数据流；将第一接入路径上的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输，第二接入路径是MA PDU会话对应的另一条接入路径。
在一可选实施例中，处理器62c在将第一接入路径上的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输时，具体用于：根据异步冗余传输模式的触发参数和/或触发指示，识别第一接入路径上的未确认数据包；将识别到的未确认数据包缓存至第一数据流中，以通过第二接入路径进行异步冗余传输。
在一可选实施例中，处理器62c还用于：获取异步冗余传输模式的触发参数和/或触发指示，该获取操作包括以下至少一种方式：从第二消息中获取触发参数；接收应用层发送的触发参数；接收应用层发送的触发指示。
在一可选实施例中，处理器62c在根据触发参数和/或触发指示识别第一接入路径上的未确认数据包时，具体用于：将第一接入路径上在所述触发参数表示的时延差超过设定阈值期间内发送的数据包，作为未确认数据包；和/或，将第一接入路径上在触发指示到达之前未接收到确认消息的数据包，作为未确认数据包。
在一可选实施例中，处理器62c还用于：测量除第一接入路径之外的其它接入路径的QoS；根据其它接入路径的QoS，从中选择QoS符合预设条件的接入路径作为第二接入路径。
上述各操作的详细实现方式可参见前述实施例中的相关描述，在此不再赘述。
相应地，本申请实施例还提供一种存储有计算机程序/指令的计算机可读存储介质，当计算机程序/指令被处理器执行时，致使处理器能够实现上述方法实施例中可由第二网络实体执行的各步骤。
上述各实施例中的存储器可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)， 可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
上述各实施例中的通信组件被配置为便于通信组件所在设备和其他设备之间有线或无线方式的通信。通信组件所在设备可以接入基于通信标准的无线网络，如WiFi，2G、3G、4G/LTE、5G等移动通信网络，或它们的组合。在一个示例性实施例中，通信组件经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
上述各实施例中的显示器包括屏幕，其屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。
上述各实施例中的电源组件，为电源组件所在设备的各种组件提供电力。电源组件可以包括电源管理系统，一个或多个电源，及其他与为电源组件所在设备生成、管理和分配电力相关联的组件。
上述各实施例中的音频组件，可被配置为输出和/或输入音频信号。例如，音频组件包括一个麦克风(MIC)，当音频组件所在设备处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器或经由通信组件发送。在一些实施例中，音频组件还包括一个扬声器，用于输出音频信号。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (20)

  1. 一种多路径冗余传输方法，适用于用户设备，其特征在于，所述方法包括：
    向第一网络实体发送第一消息，所述第一消息至少包括多锚点协议数据单元MA PDU会话请求使用异步冗余传输模式的第一指示信息，以使所述第一网络实体向第二网络实体发送第二消息，所述异步冗余传输模式是冗余传输模式中的一种；
    接收所述第一网络实体返回的第四消息，所述第二消息和所述第四消息中至少包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，以使所述第二网络实体根据所述配置指示信息通过第二接入路径对所述第一接入路径上的未确认数据包进行异步冗余传输。
  2. 根据权利要求1所述的方法，其特征在于，所述第四消息还包括：所述异步冗余传输模式的触发参数，所述触发参数用于供所述第二网络实体识别所述第一接入路径上的未确认数据包，所述未确认数据包是指在所述触发参数表示的时延差超过设定阈值期间内发送的数据包。
  3. 根据权利要求2所述的方法，其特征在于，还包括：
    向所述第一网络实体发送第七消息，以请求所述第一网络实体配置所述触发参数；
    接收所述第一网络实体返回的第八消息，所述第八消息包括配置的触发参数。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一消息还包括：MA PDU会话支持冗余传输模式的第二指示信息。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，还包括：
    向所述第二网络实体发送所述异步冗余传输模式的触发指示，以供所述第二网络实体识别所述第一接入路径上的未确认数据包，所述未确认数据包是指在所述触发指示到达之前未接收到确认消息的数据包。
  6. 根据权利要求1-3任一项所述的方法，其特征在于，还包括：
    所述配置指示信息用于指示在第二接入路径配置针对所述第一接入路径上的未确认数据包的第一数据流。
  7. 一种多路径冗余传输方法，适用于第一网络实体，其特征在于，所述方法包括：
    接收用户设备发送的第一消息，所述第一消息中至少包括多锚点协议数据单元MA PDU会话请求使用异步冗余传输模式的第一指示信息，所述异步冗余传输模式是冗余传输模式中的一种；
    根据所述第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息；
    向第二网络实体发送第二消息，并向所述用户设备发送第四消息，所述第二消息和所述第四消息中至少包括所述配置指示信息，以使所述第二网络实体通过第二接入路径对所述第一接入路径上的未确认数据包进行异步冗余传输。
  8. 根据权利要求7所述的方法，其特征在于，所述第二消息中还包括：所述异步冗余传输模式的触发参数，所述方法还包括：
    根据所述第一指示信息，确定所述异步冗余传输模式的触发参数，所述触发参数用于供所述第二网络实体识别所述第一接入路径上的未确认数据包。
  9. 根据权利要求8所述的方法，其特征在于，根据所述第一指示信息，确定针对 第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息之前，还包括：
    向第三网络实体发送第五消息，所述第五消息中至少包括所述第一指示信息，以使所述第三网络实体确认是否可以执行异步冗余传输模式；以及
    接收所述第三网络实体发送的第六消息，所述第六消息指示可以执行异步冗余传输模式。
  10. 根据权利要求9所述的方法，其特征在于，所述第六消息中包括：所述配置指示信息和所述触发参数中的至少一种；
    根据所述第一指示信息，确定针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息和所述异步冗余传输模式的触发参数，包括：
    从所述第六消息中获取所述配置指示信息和所述触发参数中的至少一种，并在从所述第六消息中获取到其中一种信息的情况下，本地配置另一种信息；
    或者，
    根据所述第一指示信息，本地配置所述配置指示信息和所述触发参数。
  11. 根据权利要求7-10任一项所述的方法，其特征在于，所述配置指示信息用于指示在第二接入路径配置针对所述第一接入路径上的未确认数据包的第一数据流。
  12. 一种多路径冗余传输方法，适用于第二网络实体，其特征在于，所述方法包括：
    接收第一网络实体发送的第二消息，所述第二消息中至少包括针对第一接入路径上的未确认数据包进行异步冗余传输的配置指示信息，所述第一接入路径对应的多锚点协议数据单元MA PDU会话请求使用异步冗余传输模式；
    根据所述配置指示信息，在第二接入路径上配置针对所述第一接入路径上的未确认数据包的第一数据流；
    将所述第一接入路径上的未确认数据包缓存至所述第一数据流中，以通过所述第二接入路径进行异步冗余传输，所述第二接入路径是MA PDU会话对应的另一条接入路径。
  13. 根据权利要求12所述的方法，其特征在于，将所述第一接入路径上的未确认数据包缓存至所述第一数据流中，以通过所述第二接入路径进行异步冗余传输，包括：
    根据所述异步冗余传输模式的触发参数和/或触发指示，识别所述第一接入路径上的未确认数据包；
    将识别到的未确认数据包缓存至所述第一数据流中，以通过所述第二接入路径进行异步冗余传输。
  14. 根据权利要求13所述的方法，其特征在于，还包括：获取所述异步冗余传输模式的触发参数和/或触发指示，该获取操作包括以下至少一种方式：
    从所述第二消息中获取所述触发参数；
    接收应用层发送的所述触发参数；
    接收应用层发送的所述触发指示。
  15. 根据权利要求13或14所述的方法，其特征在于，根据所述触发参数和/或触发指示识别所述第一接入路径上的未确认数据包，包括：
    将所述第一接入路径上在所述触发参数表示的时延差超过设定阈值期间内发送的 数据包，作为未确认数据包；
    和/或
    将所述第一接入路径上在所述触发指示到达之前未接收到确认消息的数据包，作为未确认数据包。
  16. 根据权利要求12-14任一项所述的方法，其特征在于，在第二接入路径上配置针对所述第一接入路径上的未确认数据包的第一数据流之前，还包括：
    测量除所述第一接入路径之外的其它接入路径的服务质量QoS；
    根据所述其它接入路径的QoS，从中选择QoS符合预设条件的接入路径作为所述第二接入路径。
  17. 一种用户设备，其特征在于，包括：存储器、处理器和通信组件；所述存储器，用于存储计算机程序；所述处理器用于执行所述计算机程序，以用于实现权利要求1-6任一项所述方法中的步骤。
  18. 一种网络实体，可作为第一网络实体实现，其特征在于，包括：存储器、处理器和通信组件；所述存储器，用于存储计算机程序；所述处理器用于执行所述计算机程序，以用于实现权利要求7-11任一项所述方法中的步骤。
  19. 一种网络实体，可作为第二网络实体实现，其特征在于，包括：存储器、处理器和通信组件；所述存储器，用于存储计算机程序；所述处理器用于执行所述计算机程序，以用于实现权利要求12-16任一项所述方法中的步骤。
  20. 一种存储有计算机程序的计算机可读存储介质，其特征在于，当所述计算机程序被处理器执行时，致使所述处理器能够实现权利要求1-16任一项所述方法中的步骤。
PCT/CN2023/092141 2022-05-06 2023-05-05 多路径冗余传输方法、用户设备、网络实体及存储介质 Ceased WO2023213281A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210489734.5A CN115087043B (zh) 2022-05-06 2022-05-06 多路径冗余传输方法、用户设备、网络实体及存储介质
CN202210489734.5 2022-05-06

Publications (1)

Publication Number Publication Date
WO2023213281A1 true WO2023213281A1 (zh) 2023-11-09

Family

ID=83246862

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/092141 Ceased WO2023213281A1 (zh) 2022-05-06 2023-05-05 多路径冗余传输方法、用户设备、网络实体及存储介质

Country Status (2)

Country Link
CN (1) CN115087043B (zh)
WO (1) WO2023213281A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115087043B (zh) * 2022-05-06 2025-09-19 阿里巴巴（中国）有限公司 多路径冗余传输方法、用户设备、网络实体及存储介质
CN116436865B (zh) * 2023-03-31 2026-01-02 阿里巴巴华东有限公司 多路径传输的重注入控制方法、电子设备及存储介质
CN118785254A (zh) * 2023-04-07 2024-10-15 中国电信股份有限公司 冗余传输的控制方法、装置、电子设备及可读存储介质
CN118828101A (zh) * 2023-04-19 2024-10-22 抖音视界有限公司 数据调度方法、装置、电子设备和存储介质
CN117579544B (zh) * 2024-01-17 2024-10-22 杭州映云科技有限公司 一种多路径数据传输方法、系统、设备和存储介质
CN118101553A (zh) * 2024-02-28 2024-05-28 北京字跳网络技术有限公司 一种数据传输方法、装置、设备和存储介质
CN120786342A (zh) * 2024-04-03 2025-10-14 华为技术有限公司 一种通信方法、装置及可读存储介质
CN121645397A (zh) * 2024-09-10 2026-03-10 华为技术有限公司 一种信息处理方法及装置
CN121334038A (zh) * 2025-11-14 2026-01-13 四川迅游网络科技股份有限公司 一种基于多链接路径的网络加速优化方法及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105379342A (zh) * 2014-02-28 2016-03-02 华为技术有限公司 一种数据重传的方法和装置
WO2018006871A1 (zh) * 2016-07-08 2018-01-11 电信科学技术研究院 一种进行数据重传的方法和设备
CN110391879A (zh) * 2019-07-15 2019-10-29 湖南大学 数据传输网络的丢包恢复方法、装置和计算机设备
WO2021078232A1 (zh) * 2019-10-24 2021-04-29 北京大学 一种基于多路径调度的中继设备
CN114080767A (zh) * 2019-06-27 2022-02-22 高通股份有限公司 跨载波重传技术
CN115087043A (zh) * 2022-05-06 2022-09-20 阿里巴巴（中国）有限公司 多路径冗余传输方法、用户设备、网络实体及存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3797486A4 (en) * 2018-05-22 2021-12-29 Lenovo (Beijing) Limited Redundant transmission determination
EP3949194B1 (en) * 2019-06-12 2024-08-21 Huawei Technologies Co., Ltd. Methods and devices for establishment of redundant pdu session
CN111093288B (zh) * 2019-07-30 2024-02-06 中兴通讯股份有限公司 一种用户数据传输方法、网络设备及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105379342A (zh) * 2014-02-28 2016-03-02 华为技术有限公司 一种数据重传的方法和装置
WO2018006871A1 (zh) * 2016-07-08 2018-01-11 电信科学技术研究院 一种进行数据重传的方法和设备
CN114080767A (zh) * 2019-06-27 2022-02-22 高通股份有限公司 跨载波重传技术
CN110391879A (zh) * 2019-07-15 2019-10-29 湖南大学 数据传输网络的丢包恢复方法、装置和计算机设备
WO2021078232A1 (zh) * 2019-10-24 2021-04-29 北京大学 一种基于多路径调度的中继设备
CN115087043A (zh) * 2022-05-06 2022-09-20 阿里巴巴（中国）有限公司 多路径冗余传输方法、用户设备、网络实体及存储介质

Also Published As

Publication number Publication date
CN115087043A (zh) 2022-09-20
CN115087043B (zh) 2025-09-19

Similar Documents

Publication Publication Date Title
WO2023213281A1 (zh) 多路径冗余传输方法、用户设备、网络实体及存储介质
JP6618552B2 (ja) 多重経路メディア伝達のための方法及び装置
KR20220148316A (ko) 서비스 품질 모니터링 방법 및 시스템, 및 디바이스
WO2022143468A1 (zh) 数据传输方法、装置、系统及存储介质
US9866495B2 (en) Method and apparatus for buffering data
US10687341B2 (en) Systems, methods, and media for scheduling traffic of a communication session between an application on a WiFi network and another device
US10645003B2 (en) Data packet transmission method, network side device, and user equipment
EP3316600A1 (en) Video distribution method and device
WO2022228006A1 (zh) 一种业务流识别方法及装置
JP4974652B2 (ja) ストリーミング通信システム
US20180279322A1 (en) Service Data Packet Processing Method And Apparatus
EP3607708B1 (en) Congestion control in a dual-link arrangement
WO2020152954A1 (ja) ネットワーク配置制御装置、通信システム、および、その制御方法
WO2019015111A1 (zh) 一种数据传输方法和装置
CN116436865B (zh) 多路径传输的重注入控制方法、电子设备及存储介质
WO2026040824A1 (zh) 一种通信方法及装置
KR20250007622A (ko) 무선 통신 네트워크에서 결정론적 네트워크들을 지원하기 위한 방법
US11297634B2 (en) Systems, methods, and media for scheduling traffic of a communication session between an application on a WiFi network and another device
WO2025091244A1 (en) Device and method for application triggered dynamic traffic handling
US20230117868A1 (en) Media packet transmission method, apparatus, and system
WO2025036131A1 (zh) 一种拥塞控制方法及装置
TW202508356A (zh) 通信方法及裝置
JP5296235B2 (ja) ストリーミング通信システムおよび通信中継装置
GB2632432A (en) Method for buffer status reporting in a communication network
WO2025073256A1 (zh) 数据传输的方法和通信装置

Legal Events

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

Ref document number: 23799267

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23799267

Country of ref document: EP

Kind code of ref document: A1