CN113765784B - Method and device for establishing multilink convergence data packet transmission process - Google Patents

Method and device for establishing multilink convergence data packet transmission process Download PDF

Info

Publication number
CN113765784B
CN113765784B CN202010508520.9A CN202010508520A CN113765784B CN 113765784 B CN113765784 B CN 113765784B CN 202010508520 A CN202010508520 A CN 202010508520A CN 113765784 B CN113765784 B CN 113765784B
Authority
CN
China
Prior art keywords
message
responder
logic
policy
block acknowledgement
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.)
Active
Application number
CN202010508520.9A
Other languages
Chinese (zh)
Other versions
CN113765784A (en
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.)
Chengdu Jimi Technology Co Ltd
Original Assignee
Chengdu Jimi Technology 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 Chengdu Jimi Technology Co Ltd filed Critical Chengdu Jimi Technology Co Ltd
Priority to CN202010508520.9A priority Critical patent/CN113765784B/en
Priority to PCT/CN2020/102665 priority patent/WO2021243818A1/en
Publication of CN113765784A publication Critical patent/CN113765784A/en
Application granted granted Critical
Publication of CN113765784B publication Critical patent/CN113765784B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application discloses a method and a device for establishing a multilink convergence data packet transmission process, wherein the method comprises the following steps: a first logic entity of a message initiator sends an ADDBA request message to a second logic entity of a message responder, wherein the ADDBA request message comprises a parameter STA-ML-BA Policy; a first logic entity of a message initiator receives an ADDBA response message sent by a second logic entity of a message responder, wherein the ADDBA response message comprises a parameter AP-ML-BA Policy; if the AP-ML-BA Policy in the ADDBA response message indicates agreement to use the multi-link cooperative block acknowledgement Policy, the first logical entity of the message originator indicates in the send data packet that the second logical entity of the message responder needs the feedback block acknowledgement message, and the other logical entities of the message originator indicates in the send data packet that the peer logical entity of the message responder does not need the feedback block acknowledgement message. By unified data management, the complexity of data sending and receiving management is reduced, and the network throughput rate and efficiency are improved.

Description

Method and device for establishing multilink convergence data packet transmission process
Technical Field
The present application relates to the field of wireless communications, and in particular, to a method and an apparatus for establishing a multilink aggregation packet transmission process.
Background
802.11be networks, also known as Extreme High Throughput (EHT) networks, are enhanced by a range of system features and a variety of mechanisms to achieve very High Throughput. As the use of Wireless Local Area Networks (WLANs) continues to grow, it becomes increasingly important to provide wireless data services in many environments, such as homes, businesses, and hot spots. In particular, video traffic will continue to be the dominant type of traffic in many WLAN deployments. With the advent of 4k and 8k video (uncompressed rate of 20 Gbps), the throughput requirements for these applications are constantly evolving. New high throughput, low latency applications such as virtual reality or augmented reality, gaming, remote office and cloud computing will proliferate (e.g., latency for real-time gaming is less than 5 milliseconds).
In view of the high throughput and stringent real-time latency requirements of these applications, users expect higher throughput, higher reliability, less latency and jitter, and higher power efficiency when supporting their applications over a WLAN. Users desire improved integration with Time Sensitive Networks (TSNs) to support applications on heterogeneous ethernet and wireless LANs. 802.11be networks aim to ensure the competitiveness of WLANs by further increasing overall throughput and reducing latency, while ensuring backward compatibility and coexistence with legacy technology standards. 802.11 compatible devices operating in the 2.4GHz,5GHz and 6GHz bands.
In the 802.11be network, in order to achieve the above-mentioned object, it is proposed that a plurality of data transmission links can be established between a terminal and an access point, and transmission is performed through the plurality of links simultaneously, so as to improve the transmission rate.
Disclosure of Invention
In an 802.11 network, in order to ensure the reliability of the network, each time a sender sends a data packet, a receiver needs to return an ACK message to the sender to tell the sender whether the data packet is correctly received. With the increase of network data rate, after a sender is allowed to send a plurality of data packets, a receiver feeds back the plurality of data packets, and a message fed back for the plurality of data packets is called a Block acknowledgement (Block ACK, BA) message.
In a multilink operation scenario, implemented according to the prior art, each link needs to feed back Block ACK, and actually there is only one physical entity for receiving and sending, that is, there is only one main distribution body of a data packet, and feeding back ACK on multiple links needs to strictly divide the data packet and then distribute the data packet to each link for sending, because a sender needs to adjust a window of the sent data packet according to the Block ACK fed back by a receiver, therefore:
firstly, the complexity of data sending and receiving management is increased, data distribution is required to be carried out according to network conditions before data distribution is carried out, and data receiving and sending management is required to be carried out by using a plurality of sets of data packet sequence numbers, so that not only is the complexity increased for a data sending party, but also the complexity is increased for a receiving party in the operation of data merging and reordering;
secondly, when the network condition is changed, the data transceiving scheme cannot be flexibly adjusted, which may cause more data cache on a link due to the deterioration of the network condition, but must comply with a strict data distribution policy, and cannot transmit using other links with good network conditions, thereby reducing the network throughput rate and efficiency.
The application provides a scheme for managing data packet receiving and sending in a multilink scene, and the problem is solved through unified data management.
In a first aspect, a method for establishing a multilink aggregated data packet transmission process is provided, including: a first logic entity of a message initiator sends an addition block acknowledgement (ADDBA) request message to a second logic entity of a message responder, wherein the ADDBA request message comprises a parameter STA-ML-BA Policy which is used for indicating whether the message initiator requests to use a multilink cooperative block acknowledgement strategy or not; a first logic entity of a message initiator receives an ADDBA response message sent by a second logic entity of a message responder, wherein the ADDBA response message comprises a parameter AP-ML-BA Policy and is used for indicating whether the message responder agrees to use a multilink cooperative block acknowledgement Policy or not; if the AP-ML-BA Policy in the ADDBA response message indicates agreement to use the multi-link cooperative block acknowledgement Policy, the first logical entity of the message initiator indicates in the send data packet that the second logical entity of the message responder needs the feedback block acknowledgement message, and the other logical entities of the message initiator indicates in the send data packet that the peer logical entities of the message responder do not need the feedback block acknowledgement message.
Optionally, the method further comprises: a plurality of logic entities of a message initiator respectively send aggregated data packets to peer logic entities of a message responder; the first logic entity of the message initiator receives a block acknowledgement message sent by the second logic entity of the message responder, wherein the block acknowledgement message comprises the data receiving state of other logic entities of the message responder.
Illustratively, a first logic entity of a message initiator indicates that a message responder needs to feed back a block acknowledgement message by using a display block acknowledgement request mode or an implicit block acknowledgement request mode, where the display block acknowledgement request mode refers to sending an individual block acknowledgement request message, and the implicit block acknowledgement request mode refers to setting in a control field of a sent data packet to indicate that block acknowledgement is requested.
Optionally, the method further comprises: a first logic entity of a message initiator sends a successfully received data packet or/and unsuccessfully received data packet information in a block acknowledgement message to a data packet transceiving management unit (PDU-TRMU) of the message initiator; the PDU-TRMU of the message initiator sets a data packet of a next aggregated data packet of a plurality of links, and respectively sends the aggregated data packet to a plurality of logic entities of the message initiator, or respectively sends the information of the data packet to the plurality of logic entities of the message initiator.
In one possible design, further comprising: a second logic entity of a message responder receives an ADDBA request message sent by a first logic entity of a message initiator and sends a multilink cooperative block acknowledgement strategy request message to a data packet transceiving management unit (PDU-TRMU) of the message responder, wherein the multilink cooperative block acknowledgement strategy request message comprises a service identifier (TID), a message initiator address (TA) and STA-ML-BA Policy in the ADDBA request message; if the PDU-TRMU agrees to use the multilink cooperative block acknowledgement strategy, the message responder sends a message containing TID, TA and AP-ML-BA Policy to all logic entities of the message responder, wherein the AP-ML-BA Policy is set to indicate that the multilink cooperative block acknowledgement strategy agrees to use; all logic entities of the message responder store the TID, the TA and the AP-ML-BA Policy in the message sent by the message responder PDU-TRMU locally; the second logical entity of the message responder sends an ADDBA response message to the first logical entity of the message initiator.
Optionally, the method further comprises: a plurality of logic entities of a message responder respectively receive converged data packets sent by a plurality of logic entities of a message initiator, and if the local AP-ML-BA Policy indicates that the use of a multilink cooperation block acknowledgement strategy is agreed, data packet information in the converged data packets is sent to a data packet transceiving management unit (PDU-TRMU) of the message responder; the PDU-TRMU of the message responder counts data packets successfully received by a plurality of logic entities of the message responder or/and data packets unsuccessfully received by the plurality of logic entities of the message responder, and feeds back the successfully received data packets or/and the unsuccessfully received data packet information to a second logic entity of the message responder; the second logic entity of the message responder confirms the content of the message according to the information construction block fed back by the PDU-TRMU of the message responder; the second logical entity of the message responder sends a block acknowledgement message to the first logical entity of the message initiator.
In another possible design, the method further includes: the second logic entity of the message responder receives the ADDBA request message sent by the first logic entity of the message initiator, and if the message responder agrees to use the multilink coordination block acknowledgement Policy, the second logic entity of the message responder sends a message containing a service identifier (TID), a message initiator address (TA) and STA-ML-BA Policy in the ADDBA request message to other logic entities of the message responder; the other logic entities of the message responder store the TID, the TA and the STA-ML-BA Policy in the message sent by the second logic entity of the message responder in local; the second logical entity of the message responder sends an ADDBA response message to the first logical entity of the message initiator.
Optionally, the method further comprises: a plurality of logic entities of a message responder respectively receive converged data packets sent by a plurality of logic entities of a message initiator, and if the local STA-ML-BA Policy indicates that a multilink cooperative block acknowledgement Policy is used, other logic entities of the message responder send data packet information in the converged data packets to a second logic entity of the message responder; the second logic entity of the message responder counts the data packets successfully received or/and the data packets unsuccessfully received by a plurality of logic entities of the message responder, and establishes a block according to the counted information to confirm the content of the message; the second logical entity of the message responder sends a block acknowledgement message to the first logical entity of the message initiator.
In a second aspect, an apparatus for establishing a multilink aggregated packet transmission process is provided, where the apparatus includes a plurality of logical entities respectively operating on different links, and when the apparatus is used as a message initiator, the logical entities are configured to: a first logic entity sends an addition block acknowledgement (ADDBA) request message, wherein the ADDBA request message comprises a parameter STA-ML-BA Policy and is used for indicating whether a message initiator requests to use a multilink cooperative block acknowledgement strategy or not; a first logic entity receives an ADDBA response message, wherein the ADDBA response message comprises a parameter AP-ML-BA Policy and is used for indicating whether a message response party agrees to use a multilink cooperative block acknowledgement Policy or not; if the AP-ML-BA Policy in the ADDBA response message indicates to agree to use the multi-link cooperative block acknowledgement Policy, the first logic entity indicates in the sending data packet that the peer-to-peer logic entity of the message responder needs to feed back the block acknowledgement message, and the other logic entities indicate in the sending data packet that the peer-to-peer logic entity of the message responder does not need to feed back the block acknowledgement message;
when the apparatus is acting as a message responder, the logical entity is configured to: the second logic entity receives the ADDBA request message; the second logical entity sends an ADDBA response message.
Optionally, when the apparatus is used as a message initiator, the logic entity is further configured to: a plurality of logic entities send aggregated data packets; the first logical entity receives a block acknowledgement message that includes the data reception status of all logical entities of the message responder.
In one possible design, the apparatus further includes a packet transmit receive management unit (PDU-TRMU), and when the apparatus is acting as a message originator, the logical entity is further configured to: the first logic entity sends the successfully received data packet or/and the unsuccessfully received data packet information in the block acknowledgement message to PDU-TRMU; the PDU-TRMU performs the following operations: setting data packets of a next aggregated data packet on a plurality of links, and respectively sending the aggregated data packets to a plurality of logic entities or respectively sending data packet information to the plurality of logic entities;
when the apparatus is acting as a message responder, the logical entity is further configured to: the second logic entity sends a multilink cooperation block acknowledgement strategy request message to the PDU-TRMU, wherein the multilink cooperation block acknowledgement strategy request message comprises a service identifier (TID), a message initiator address (TA) and a STA-ML-BA Policy in the ADDBA request message; all logic entities store TID, TA and AP-ML-BA Policy in the message sent by PDU-TRMU locally; the PDU-TRMU performs the following operations: and if the PDU-TRMU agrees to use the multilink cooperative block acknowledgement strategy, sending a message containing the TID, the TA and the AP-ML-BA Policy to all the logic entities, wherein the AP-ML-BA Policy is set to indicate that the multilink cooperative block acknowledgement strategy is agreeed to use.
Optionally, when the apparatus is acting as a message responder, the logical entity is further configured to: a plurality of logic entities receive the converged data packets; if the local AP-ML-BA Policy indicates that the multi-link cooperative block acknowledgement strategy is agreed to be used, the plurality of logic entities send the data packet information in the aggregated data packet to the PDU-TRMU; the second logic entity constructs the content of the block acknowledgement message according to the information fed back by the PDU-TRMU and sends the block acknowledgement message; the PDU-TRMU is further configured to: and counting the successfully received data packets or/and the unsuccessfully received data packets, and feeding back the successfully received data packets or/and the unsuccessfully received data packet information to the second logic entity.
In another possible design, when the apparatus is a message responder, the logic entity is further configured to: if the message responder agrees to use the multilink cooperative block acknowledgement Policy, the second logical entity sends a message containing a service identifier (TID), a message initiator address (TA) and STA-ML-BA Policy in the ADDBA request message to other logical entities; the other logical entities locally store the TID, TA and STA-ML-BA Policy in the message sent by the second logical entity.
Optionally, when the apparatus is acting as a message responder, the logical entity is further configured to: a plurality of logic entities receive the converged data packets; if the local STA-ML-BA Policy indicates that the multilink cooperative block acknowledgement strategy is used, the other logic entities send the data packet information in the converged data packet to a second logic entity; and the second logic entity counts the data packets successfully received by the plurality of logic entities or/and the data packets unsuccessfully received by the plurality of logic entities, constructs the content of the block acknowledgement message according to the counted information, and sends the block acknowledgement message.
According to the method, an ADDBA request message and an ADDBA response message are sent on a main link, a parameter ML-BA Policy is added in the ADDBA request message and the ADDBA response message to indicate whether to request and approve to use a multilink cooperation block confirmation strategy, if the multilink cooperation block confirmation strategy is used, a BAR message and a BA message are only sent on the main link, the BA message comprises data receiving states on other links, and unified data management is realized by introducing a PDU-TRMU logic unit for coordinating to receive and send data packets or introducing an interactive interface between logic entities in multilink equipment, synchronizing the information of the received data packets (a message response party), and information of successfully received data packets or/and unsuccessfully received data packets in BA (a message initiator), so that the complexity of data sending and receiving management is reduced, and the network throughput rate and efficiency are improved.
Drawings
The present application will now be described by way of example only with reference to the accompanying drawings, in which:
fig. 1 is a schematic diagram illustrating a method for establishing a multilink aggregate packet transmission process according to an embodiment of the present application;
fig. 2 is a schematic diagram illustrating a method for establishing a multilink aggregate packet transmission process according to another embodiment of the present application;
fig. 3 is a diagram illustrating a method for establishing a multilink aggregate packet transmission process according to another embodiment of the present application;
fig. 4 is a schematic diagram illustrating a method for establishing a multilink aggregate packet transmission procedure according to another embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
In the embodiments of the present application, the words "exemplary," "for example," and the like are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term using examples is intended to present concepts in a concrete fashion.
Unless defined otherwise, technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this application belongs. The use of "first," "second," and similar terms in this application do not denote any order, quantity, or importance, but rather the description is used to distinguish one element from another. The word "comprising" or "comprises", and the like, means that the element or item listed before the word covers the element or item listed after the word and its equivalents, but does not exclude other elements or items. The term "and/or" includes any and all combinations of one or more of the associated listed items.
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is further described in detail with reference to specific embodiments below. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
In this application, we refer to a Multi-link Device (MLD) initiating data transmission as a message initiator and an MLD responding to data transmission as a message responder. In the following embodiments, in order to make the scheme clearer, the present application is illustrated by taking only two links as an example, but the present application concept is not limited thereto and is also applicable to the case of more than two links.
In the following embodiments, MLD1 is a message initiator, STA1 and STA2 are logical entities within MLD1 operating on link 1 and link 2, respectively, MLD2 is a message responder, and STA3 and STA4 are logical entities within MLD2 operating on link 1 and link 2, respectively.
Multilink cooperative block acknowledgement policy: it is defined in this application that by coordination, a message responder sends a BA on only one link, and the BA includes data reception status on other links.
The method for establishing the multilink convergence data packet transmission process includes that a message initiator only sends an ADDBA request message on a main link, whether a multilink cooperative block confirmation strategy is required to be used or not is indicated by adding a parameter ML-BA Policy in the ADDBA request message, and if a message responder agrees to use the multilink cooperative block confirmation strategy, the message responder only indicates on the main link that the message responder needs to feed back a block confirmation message. The method comprises the following steps:
a first logic entity of a message initiator sends an addition block acknowledgement (ADDBA) request message to a second logic entity of a message responder, wherein the ADDBA request message comprises a parameter STA-ML-BA Policy and is used for indicating whether the message initiator requests to use a multilink cooperative block acknowledgement strategy or not; a first logic entity of a message initiator receives an ADDBA response message sent by a second logic entity of a message responder, wherein the ADDBA response message comprises a parameter AP-ML-BA Policy and is used for indicating whether the message responder agrees to use a multilink cooperative block acknowledgement Policy or not; if the AP-ML-BA Policy in the ADDBA response message indicates agreement to use the multi-link cooperative block acknowledgement Policy, the first logical entity of the message initiator indicates in the send data packet that the second logical entity of the message responder needs the feedback block acknowledgement message, and the other logical entities of the message initiator indicates in the send data packet that the peer logical entities of the message responder do not need the feedback block acknowledgement message. If a certain logical entity of the message initiator and a certain logical entity of the message responder transmit and receive data on the same link, the two logical entities are peer-to-peer, such as: STA1 sends data to STA3 through link 1, STA2 sends data to STA4 through link 2, STA3 feeds back data to STA1 through link 1, STA4 feeds back data to STA2 through link 2, then STA1 and STA3 are peer-to-peer, and STA2 and STA4 are peer-to-peer.
In some embodiments, the message initiator and the message responder may each include a packet transmit receive management unit (PDU-TRMU), which may be an internal logical unit of the message initiator and the message responder or an external logical unit of the message initiator and the message responder. The message response party sends the received ADDBA request message and corresponding information in the aggregated data packet to the PDU-TRMU of the message response party, and the PDU-TRMU of the message response party determines the setting of a parameter ML-BA Policy in the ADDBA response message and counts the receiving states of the data packets on all links of the message response party. The message initiator sends the corresponding information in the received BA message to the PDU-TRMU, and the PDU-TRMU of the message initiator sets a data packet of a next aggregated data packet of a plurality of links. Alternatively, an interactive interface between logical entities inside the multilink device is introduced, and information of the received data packets (message responder) and information of the successfully received data packets or/and the unsuccessfully received data packets (message initiator) in the BA are synchronized.
The present application does not limit the method for selecting the main link, and the inventive concept of the present application is not limited thereto. Illustratively, the main link may be set by including corresponding parameters in the interacted information, such as: the message responder includes a Primary Link parameter in the feedback connection response message or reconnection response message to indicate a Primary Link in the multilink operation, and the message initiator may also include a Primary Link parameter in the connection request message or reconnection request message to indicate a Primary Link that the message initiator desires to use.
Fig. 1 is a schematic diagram illustrating a method for establishing a multilink aggregate packet transmission process according to an embodiment of the present application. In this embodiment, the message initiator indicates that the message responder needs to feed back a block acknowledgement message by using a display block acknowledgement request manner, i.e., sends an individual BAR message to the message responder. The method for establishing the multilink convergence data packet transmission process comprises the following steps:
STA1 sends an ADDBA request (request) message to STA3, which includes, for example:
TID: the service identifier is used for identifying the service to which the current sending data belongs;
ML-BA Policy: for indicating whether the message originator requests the use of multilink cooperative block acknowledgement policy, such as:
"0": indicating that a multilink cooperative block acknowledgement policy is not used;
"1": indicating the use of a multilink cooperative block acknowledgement policy;
set to "1" in the present exemplary embodiment;
TA: the message originator address may be used to identify an MLD that sends data.
STA3 sends an ACK message to STA1 indicating that STA3 has received the ADDBA request message sent by STA1.
Sta3 sends a multilink cooperative block acknowledgement policy request message to PDU-TRMU, illustratively including:
TID: service identification;
ML-BA Policy: for indicating whether a message originator requests use of a multilink coordination block acknowledgment policy;
TA: the message originator address.
And 4. If the PDU-TRMU agrees to use the multi-link cooperative block acknowledgement strategy, sending a message to all STAs (STA 3 and STA4 in the embodiment of the application), wherein the message comprises TID, TA and ML-BA Policy, and the value of the ML-BA Policy is set to be 1, namely the multi-link cooperative block acknowledgement strategy is used. If the PDU-TRMU does not agree to use the multi-link cooperative block acknowledgement Policy, the PDU-TRMU may send a message to all STAs, or may not send a message to all STAs, if the message is sent, the value of the ML-BA Policy is set to "0", that is, the multi-link cooperative block acknowledgement Policy is not used, if the message is not sent, the multi-link cooperative block acknowledgement Policy is not used by default, and the present application does not limit this.
STA3 and STA4 store TID, TA and ML-BA Policy locally.
STA3 sends ADDBA response to STA1, which includes, for example:
ML-BA Policy: for indicating whether the message responder agrees to use a multilink cooperative block acknowledgment policy, such as:
"0": indicating that a multilink cooperative block acknowledgement policy is not used;
"1": indicating the use of a multilink cooperative block acknowledgement policy;
set to "1" in the present exemplary embodiment.
STA1 sends an ACK message to STA3 indicating that STA1 has received the ADDBA response message sent by STA3.
And 8, sending an aggregated data packet to the STA3 and the STA4 by the STA1 and the STA2 on the link 1 and the link 2 respectively, wherein the data packet comprises a TID and a TA.
9. After the data packet is sent, the STA1 sends a BA request message to the STA3.
And 10, after the STA3 and the STA4 receive the converged data packet, for example, if the ML-BA Policy corresponding to the TA and the TID in the received data packet indicates 1, transmitting the data packet information in the converged data packet to the PDU-TRMU.
And 11, counting the successfully received data packets or/and the unsuccessfully received data packets in the STA3 and the STA4 by the PDU-TRMU, and feeding back the successfully received data packets or/and the unsuccessfully received data packet information to the STA3.
And 12.STA3 constructs the content of the BA message according to the information fed back by the PDU-TRMU.
STA3 sends a BA message to STA1.
The STA1 sends the successfully received data packet in the BA message or/and the unsuccessfully received data packet information to the PDU-TRMU;
and 15, setting a data packet of a next aggregated data packet on the link 1 and the link 2 by the PDU-TRMU, and respectively sending the aggregated data packet to the STA1 and the STA2, or respectively sending data packet information to the STA1 and the STA2.
And (16) the STA1 and the STA2 send corresponding aggregated data packets according to the data packet information.
Fig. 2 is a schematic diagram illustrating a method for establishing a multilink aggregate packet transmission process according to another embodiment of the present application. In this embodiment, the message initiator also indicates that the message responder needs to feed back the block acknowledgement message in the display block acknowledgement request manner, but the MLD does not include PDU-TRMU, and synchronizes the information of the received data packet (message responder) and the information of the successfully received data packet or/and the unsuccessfully received data packet (message initiator) in the BA through an interactive interface introduced between logical entities inside the MLD. The method for establishing the multilink convergence data packet transmission process comprises the following steps:
STA1 sends ADDBA request message to STA3, illustratively including:
TID: the service identifier is used for identifying the service to which the current sending data belongs;
ML-BA Policy: for indicating whether the message originator requests the use of multilink cooperative block acknowledgement policy, such as:
"0": indicating that a multilink cooperative block acknowledgement policy is not used;
"1": indicating the use of a multilink cooperative block acknowledgement policy;
set to "1" in the exemplary embodiments of the present invention;
TA: the message originator address may be used to identify an MLD that sends data.
STA3 sends an ACK message to STA1 indicating that STA3 has received the ADDBA request message sent by STA1.
3. If the message responder agrees to use the multilink cooperative block acknowledgement policy, the STA3 sends a message to the STA4, wherein the message comprises:
TID: service identification;
ML-BA Policy: for indicating whether a message originator requests to use a multilink coordination block acknowledgement policy;
TA: the message originator address.
STA4 locally stores TID, TA and ML-BA Policy.
STA3 sends ADDBA response to STA1, illustratively, the message contains:
ML-BA Policy: for indicating whether the message responder agrees to use a multilink cooperative block acknowledgment policy, such as:
"0": indicating that a multilink cooperative block acknowledgement policy is not used;
"1": indicating the use of a multilink cooperative block acknowledgement policy;
set to "1" in the present exemplary embodiment.
STA1 sends an ACK message to STA3 indicating that STA1 has received the ADDBA response message sent by STA3.
And 7, the STA1 and the STA2 respectively send an aggregation data packet to the STA3 and the STA4 on the link 1 and the link 2, wherein the data packet comprises a TID and a TA.
8. After the data packet is sent, the STA1 sends a BA request message to the STA3.
After STA3 and STA4 receive the aggregated packet, STA4 sends the packet information in the aggregated packet to STA3, for example, if the ML-BA Policy corresponding to the TA and TID in the received packet indicates "1".
STA3 counts the successfully received packets in STA3 and STA4, or/and the unsuccessfully received packets.
STA3 constructs the content of the BA message according to the statistical information.
STA3 sends a BA message to STA1.
Fig. 3 is a schematic diagram illustrating a method for establishing a multilink aggregate packet transmission process according to another embodiment of the present application. In this embodiment, the message initiator indicates that the message responder needs to feed back a block acknowledgement message by using an implicit block acknowledgement request mode, that is, the message initiator performs setting in a control field of a transmitted data packet to indicate that block acknowledgement is requested. For example, in the QoS control field of the packet, the ACK policy field is set to "00" indicating that the message responder is required to send the BA message. The remainder of this embodiment is the same as the embodiment shown in fig. 1 and will not be described again here.
Fig. 4 is a schematic diagram illustrating a method for establishing a multilink aggregate packet transmission procedure according to another embodiment of the present application. In this embodiment, the message initiator indicates the message responder to need to feed back a block acknowledgement message by using an implicit block acknowledgement request mode, that is, the message initiator performs setting in a control field of a transmitted data packet to indicate that block acknowledgement is requested. For example, in the QoS control field of a packet, the ACK policy field is set to "00" indicating that a message responder is required to send a BA message. The remainder of this embodiment is the same as the embodiment shown in fig. 2 and will not be described again here.
The embodiment of the present application further provides a device for establishing a multilink aggregated data packet transmission process, where the device may serve as a message initiator or a message responder, and includes a plurality of logical entities (STAs) respectively operating on different links, and in some embodiments, the device may further include a data packet transceiving management unit (PDU-TRMU).
The apparatus for establishing a transmission process of a multilink aggregated data packet according to this embodiment is used to implement the method for establishing a transmission process of a multilink aggregated data packet according to the embodiment shown in fig. 1, fig. 2, fig. 3, or fig. 4.
It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, some or all of the steps may be executed in parallel or executed sequentially, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, a network device or a terminal device, etc.) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, ROM, RAM) magnetic disk or optical disk, etc. on which various types of program codes can be stored.
The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.
The words "if" or "if" as used herein may be interpreted as "at \8230; \8230whenor" when 8230; \8230, when or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrase "if determined" or "if detected (a stated condition or event)" may be interpreted as "upon determining" or "in response to determining" or "upon detecting (a stated condition or event)" or "in response to detecting (a stated condition or event)", depending on the context.
It will be understood by those skilled in the art that all or part of the steps in the method for implementing the above embodiments may be implemented by instructing the relevant hardware through a program, which may be stored in a storage medium readable by a device and includes all or part of the steps when executed, such as: FLASH, EEPROM, etc.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (11)

1. A method for establishing a multilink aggregate packet transmission process, comprising:
a first logic entity of a message initiator sends an addition block acknowledgement (ADDBA) request message to a second logic entity of a message responder, wherein the ADDBA request message comprises a parameter STA-ML-BA Policy which is used for indicating whether the message initiator requests to use a multilink cooperative block acknowledgement strategy or not;
a first logic entity of a message initiator receives an ADDBA response message sent by a second logic entity of a message responder, wherein the ADDBA response message comprises a parameter AP-ML-BA Policy and is used for indicating whether the message responder agrees to use a multilink cooperative block acknowledgement Policy or not;
if the AP-ML-BA Policy in the ADDBA response message indicates agreement to use the multi-link cooperative block acknowledgement Policy, the first logic entity of the message initiator indicates in the sending data packet that the second logic entity of the message responder needs to feed back the block acknowledgement message, and the other logic entities of the message initiator indicates in the sending data packet that the peer logic entities of the message responder do not need to feed back the block acknowledgement message;
a plurality of logic entities of a message initiator respectively send aggregated data packets to peer logic entities of a message responder;
a first logic entity of a message initiator receives a block acknowledgement message sent by a second logic entity of a message responder, wherein the block acknowledgement message comprises data receiving states of other logic entities of the message responder;
a first logic entity of a message initiator sends a successfully received data packet or/and unsuccessfully received data packet information in a block acknowledgement message to a data packet transceiving management unit (PDU-TRMU) of the message initiator;
the PDU-TRMU of the message initiator sets data packets of next aggregated data packets on a plurality of links, and respectively sends the aggregated data packets to a plurality of logic entities of the message initiator, or respectively sends data packet information to the plurality of logic entities of the message initiator, so that the plurality of logic entities of the message initiator send corresponding aggregated data packets according to the received aggregated data packets or data packet information.
2. The method according to claim 1, wherein a first logic entity of a message initiator indicates that a message responder needs to feed back a block ack message by using a explicit block ack request manner or an implicit block ack request manner, the explicit block ack request manner is to send an individual block ack request message, and the implicit block ack request manner is to set in a control field of a sent data packet to indicate a request block ack.
3. The method of claim 1, further comprising:
a second logic entity of a message responder receives an ADDBA request message sent by a first logic entity of a message initiator and sends a multilink cooperative block acknowledgement strategy request message to a data packet transceiving management unit (PDU-TRMU) of the message responder, wherein the multilink cooperative block acknowledgement strategy request message comprises a service identifier (TID), a message initiator address (TA) and STA-ML-BA Policy in the ADDBA request message;
if the PDU-TRMU of the message responder agrees to use the multilink cooperative block acknowledgement strategy, sending a message containing TID, TA and AP-ML-BA Policy to all logic entities of the message responder, wherein the AP-ML-BA Policy is set to indicate that the multilink cooperative block acknowledgement strategy is agreeed to use;
all logic entities of the message responder store the TID, the TA and the AP-ML-BA Policy in the message sent by the message responder PDU-TRMU in a local place;
the second logical entity of the message responder sends an ADDBA response message to the first logical entity of the message initiator.
4. The method of claim 1, further comprising:
a plurality of logic entities of a message responder respectively receive converged data packets sent by a plurality of logic entities of a message initiator, and if the local AP-ML-BA Policy indicates that the use of a multilink cooperation block confirmation strategy is agreed, data packet information in the converged data packets is sent to a data packet transceiving management unit (PDU-TRMU) of the message responder;
the PDU-TRMU of the message responder counts data packets successfully received by a plurality of logic entities of the message responder or/and data packets unsuccessfully received by the plurality of logic entities of the message responder, and feeds back the successfully received data packets or/and the unsuccessfully received data packet information to a second logic entity of the message responder;
the second logic entity of the message responder confirms the content of the message according to the information construction block fed back by the PDU-TRMU of the message responder;
the second logical entity of the message responder sends a block acknowledgement message to the first logical entity of the message initiator.
5. The method of claim 1, further comprising:
the second logic entity of the message responder receives the ADDBA request message sent by the first logic entity of the message initiator, and if the message responder agrees to use the multi-link cooperative block acknowledgement strategy, the second logic entity of the message responder sends a message containing the service identification (TID), the message initiator address (TA) and the STA-ML-BA Policy in the ADDBA request message to other logic entities of the message responder;
other logic entities of the message responder store the TID, the TA and the STA-ML-BA Policy in the message sent by the second logic entity of the message responder in a local place;
the second logical entity of the message responder sends an ADDBA response message to the first logical entity of the message initiator.
6. The method of claim 1, further comprising:
a plurality of logic entities of a message responder respectively receive converged data packets sent by a plurality of logic entities of a message initiator, and if the local STA-ML-BA Policy indicates that a multilink cooperative block acknowledgement Policy is used, other logic entities of the message responder send data packet information in the converged data packets to a second logic entity of the message responder;
the second logic entity of the message responder counts the data packets successfully received or/and the data packets unsuccessfully received by a plurality of logic entities of the message responder, and establishes a block according to the counted information to confirm the content of the message;
the second logical entity of the message responder sends a block acknowledgement message to the first logical entity of the message initiator.
7. An apparatus for establishing a multilink aggregated packet transmission process, comprising a plurality of logical entities respectively operating on different links, and a packet transmit receive management unit (PDU-TRMU),
when the apparatus is acting as a message initiator, the logical entity is configured to:
a first logic entity sends an addition block acknowledgement (ADDBA) request message, wherein the ADDBA request message comprises a parameter STA-ML-BA Policy and is used for indicating whether a message initiator requests to use a multilink cooperative block acknowledgement Policy or not; the first logic entity receives an ADDBA response message, wherein the ADDBA response message comprises a parameter AP-ML-BA Policy, and is used for indicating whether a message response party agrees to use a multilink cooperative block acknowledgement Policy or not; if the AP-ML-BA Policy in the ADDBA response message indicates to agree to use the multi-link cooperative block acknowledgement Policy, the first logic entity indicates in the sending data packet that the peer-to-peer logic entity of the message responder needs to feed back the block acknowledgement message, and the other logic entities indicate in the sending data packet that the peer-to-peer logic entity of the message responder does not need to feed back the block acknowledgement message; a plurality of logic entities send aggregated data packets; a first logic entity receives a block acknowledgement message, wherein the block acknowledgement message comprises data receiving states of all logic entities of a message responder; the first logic entity sends the successfully received data packet or/and the unsuccessfully received data packet information in the block acknowledgement message to PDU-TRMU;
the PDU-TRMU performs the following operations: setting data packets of a next aggregated data packet on a plurality of links, and respectively sending the aggregated data packets to a plurality of logic entities, or respectively sending data packet information to the plurality of logic entities, so that the plurality of logic entities send corresponding aggregated data packets according to the received aggregated data packets or data packet information;
when the apparatus is acting as a message responder, the logical entity is configured to:
the second logic entity receives the ADDBA request message; the second logical entity sends an ADDBA response message.
8. The apparatus for establishing a process of transmitting a multilink aggregate data packet according to claim 7,
when the apparatus is acting as a message responder, the logical entity is further configured to: the second logic entity sends a multilink cooperative block acknowledgement Policy request message to the PDU-TRMU, wherein the multilink cooperative block acknowledgement Policy request message comprises a service identifier (TID), a message initiator address (TA) and an STA-ML-BA Policy in the ADDBA request message; all logic entities store TID, TA and AP-ML-BA Policy in the message sent by the PDU-TRMU in local; the PDU-TRMU performs the following operations: and if the PDU-TRMU agrees to use the multilink cooperative block acknowledgement strategy, sending a message containing the TID, the TA and the AP-ML-BA Policy to all the logic entities, wherein the AP-ML-BA Policy is set to indicate that the multilink cooperative block acknowledgement strategy agrees to use.
9. The apparatus of claim 8, wherein the logic entity is further configured to perform the following operations when the apparatus is acting as a message responder: a plurality of logic entities receive the converged data packets; if the local AP-ML-BA Policy indicates that the multi-link cooperative block acknowledgement strategy is agreed to be used, the plurality of logic entities send the data packet information in the aggregated data packet to the PDU-TRMU; the second logic entity constructs the content of the block acknowledgement message according to the information fed back by the PDU-TRMU and sends the block acknowledgement message;
the PDU-TRMU is further configured to: and counting the successfully received data packets or/and the unsuccessfully received data packets, and feeding back the successfully received data packets or/and the unsuccessfully received data packet information to the second logic entity.
10. The apparatus of claim 7, wherein when the apparatus is acting as a message responder, the logic entity is further configured to:
if the message response party agrees to use the multi-link cooperative block acknowledgement Policy, the second logical entity sends a message containing the service identifier (TID), the message initiator address (TA) and the STA-ML-BA Policy in the ADDBA request message to other logical entities; the other logical entities locally store the TID, TA and STA-ML-BA Policy in the message sent by the second logical entity.
11. The apparatus of claim 7, wherein the logic entity is further configured to perform the following operations when the apparatus is acting as a message responder:
a plurality of logic entities receive the converged data packets; if the local STA-ML-BA Policy indicates that the multilink cooperative block acknowledgement strategy is used, the other logic entities send the data packet information in the converged data packet to a second logic entity;
and the second logic entity counts the data packets successfully received by the plurality of logic entities or/and the data packets unsuccessfully received by the plurality of logic entities, constructs the content of the block acknowledgement message according to the counted information, and sends the block acknowledgement message.
CN202010508520.9A 2020-06-06 2020-06-06 Method and device for establishing multilink convergence data packet transmission process Active CN113765784B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010508520.9A CN113765784B (en) 2020-06-06 2020-06-06 Method and device for establishing multilink convergence data packet transmission process
PCT/CN2020/102665 WO2021243818A1 (en) 2020-06-06 2020-07-17 Method and apparatus for establishing multi-link aggregation data packet transmission process

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010508520.9A CN113765784B (en) 2020-06-06 2020-06-06 Method and device for establishing multilink convergence data packet transmission process

Publications (2)

Publication Number Publication Date
CN113765784A CN113765784A (en) 2021-12-07
CN113765784B true CN113765784B (en) 2022-11-18

Family

ID=78785322

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010508520.9A Active CN113765784B (en) 2020-06-06 2020-06-06 Method and device for establishing multilink convergence data packet transmission process

Country Status (2)

Country Link
CN (1) CN113765784B (en)
WO (1) WO2021243818A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101124762A (en) * 2004-07-30 2008-02-13 诺基亚公司 System and method for variable length acknowledgements in a shared resource network
CN104540226A (en) * 2009-12-20 2015-04-22 英特尔公司 Device, system and method of simultaneously communicating with a group of wireless communication devices
CN106161583A (en) * 2015-05-12 2016-11-23 华为技术有限公司 The transmission method of a kind of piece of acknowledgement frame and equipment
CN111066271A (en) * 2017-09-11 2020-04-24 高通股份有限公司 Techniques for multilink aggregated signaling

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170055255A1 (en) * 2015-08-18 2017-02-23 Qualcomm Incorporated Techniques for response frames in cooperative reception
US11558777B2 (en) * 2018-12-28 2023-01-17 Intel Corporation Methods of multi-link buffer management without block acknowledgement (BA) negotiation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101124762A (en) * 2004-07-30 2008-02-13 诺基亚公司 System and method for variable length acknowledgements in a shared resource network
CN104540226A (en) * 2009-12-20 2015-04-22 英特尔公司 Device, system and method of simultaneously communicating with a group of wireless communication devices
CN106161583A (en) * 2015-05-12 2016-11-23 华为技术有限公司 The transmission method of a kind of piece of acknowledgement frame and equipment
CN111066271A (en) * 2017-09-11 2020-04-24 高通股份有限公司 Techniques for multilink aggregated signaling

Also Published As

Publication number Publication date
CN113765784A (en) 2021-12-07
WO2021243818A1 (en) 2021-12-09

Similar Documents

Publication Publication Date Title
CN111405684B (en) Method for connecting to network access device, terminal and computer readable storage medium
US10681773B2 (en) Real-time relay of wireless communications
EP3968731B1 (en) Communication method applicable to multiple links, and related devices
WO2021232568A1 (en) Method, terminal and system for transceiving data over wireless local area network, and network access device
CN110506403B (en) Method and apparatus for flow control of wireless devices
US7339892B1 (en) System and method for dynamic control of data packet fragmentation threshold in a wireless network
CN112911729B (en) Method, terminal and storage medium for establishing tunnel direct link
CN110999467A (en) Aggregated media access control protocol data unit transmission of multi-service identifiers
CN115442921B (en) Method, device, system, equipment and storage medium for reconfiguring link
CN115209568B (en) Management method, device and storage medium for service flow data transmission of multi-link system
CN113765627B (en) Method and device for responding to multilink received data
CN113765784B (en) Method and device for establishing multilink convergence data packet transmission process
CN113938490A (en) Method, device and storage medium for establishing point-to-point communication connection
CN114095504B (en) Method, apparatus and storage medium for peer-to-peer communication using multilink
CN113141631B (en) Dual-connection data distribution method, device, equipment and storage medium
CN115150028B (en) Method, device and medium for establishing block acknowledgement protocol between multi-link devices
CN115150027B (en) Multilink block acknowledgement method, device and storage medium
CN115150037B (en) Method, device, system and storage medium for establishing multi-link block acknowledgement protocol
US9479351B2 (en) Method and apparatus for providing voice service in communication system
CN114630368B (en) Method, apparatus, device and medium for controlling data transmission on multilink
CN114257602B (en) Method, device and storage medium for triggering terminal to execute point-to-point service
EP4117252A1 (en) Traffic control method and apparatus
EP4228372A1 (en) Triggered multi-link access coordination
KR100725419B1 (en) Method for useful managing receive buffer on wlan devices and apparatus for employing the method
CN115695895A (en) Method, device, equipment and storage medium for improving data transmission rate

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant