Communication method and device

Abstract

A communication method and apparatus are provided relating to the field of communication technology. The method includes the following: when a non-AP MLD roams from the current AP MLD to a target AP MLD, and the current AP MLD determines that data exists in the current AP MLD's transmit buffer (the transmit buffer is used to buffer data for the current AP MLD and data for the non-AP MLD), the current AP MLD may transmit all the data in its transmit buffer to the non-AP MLD, or the current AP MLD may transmit all the data in its transmit buffer to the target AP MLD, and as a result, the non-AP MLD may receive the data from the current AP MLD from the target AP MLD. This reduces packet loss in the roaming handover process of the non-AP MLD and further improves the communication reliability of the non-AP MLD in the roaming process.

Description

Technical Field

[0001] This application claims the priority of Chinese Patent Application No. 202310541312.2, entitled "Communication Method and Device", filed with the China National Intellectual Property Administration on May 12, 2023, the entire content of which is incorporated herein by reference.

[0002] This application relates to the field of communication technologies, and more particularly, to communication methods and devices.

Background Art

[0003] Currently, wireless communication devices support multi-link communication. For example, they can communicate on multiple links in different communication frequency bands (such as 2.4 GHz, 5 GHz, 6 GHz), or communicate on different channels in the same communication frequency band. A communication device that supports multi-link communication can be called a multi-link device (MLD). Multi-link devices include access point (AP) MLDs and non-access point (non-AP) MLDs.

[0004] When a non-AP MLD moves, as the distance between the non-AP MLD and the associated AP MLD increases and / or obstacles appear, the link quality deteriorates. In this case, roaming of the non-AP MLD may be triggered. The non-AP MLD roams to an AP MLD that provides a higher-quality link in order to meet the service requirements for communication quality. However, when the non-AP MLD roams, packet loss may occur, which may affect the communication reliability of the non-AP MLD in the roaming process.

Summary of the Invention

Means for Solving the Problems

[0005] This application provides a communication method and apparatus for reducing packet loss in roaming handover processing of non-AP MLDs and further improving the communication reliability of non-AP MLDs in roaming processing.

[0006] According to a first aspect, a communication method is provided, namely, that the current AP MLD determines that data exists in the current AP MLD's transmit buffer, the transmit buffer is used to buffer data for the current AP MLD and data for the non-AP MLD, the non-AP MLD triggers a temporary association with the target AP MLD, the current AP MLD transmits all data in its transmit buffer to the non-AP MLD or the target AP MLD, and the target AP MLD is configured to transmit data from the current AP MLD to the non-AP MLD.

[0007] In the embodiments described above, the triggering of a temporary association between the non-AP MLD and the target AP MLD indicates that the non-AP MLD is beginning to roam to the target AP MLD. In this case, after determining that data is present in the current AP MLD's transmit buffer, the current AP MLD may either send all the data in its transmit buffer to the non-AP MLD or send all the data in its transmit buffer to the target AP MLD, thereby enabling the target AP MLD to forward the data from the current AP MLD to the non-AP MLD. This reduces packet loss during the non-AP MLD's roaming handover process and further improves the communication reliability of the non-AP MLD during roaming.

[0008] With respect to the first aspect, in one possible implementation, if the current AP MLD determines that a non-AP MLD has triggered a temporary association with a target AP MLD, the protocol (pre-defined) is that, starting from the window start position (WinStart_O), one or more of the data in the current AP MLD's send buffer, such as data to be sent (i.e., data not sent by the current AP MLD to the non-AP MLD) and data that failed to be sent (i.e., data not successfully sent by the current AP MLD to the non-AP MLD), will not be cleared. Alternatively, the protocol (pre-defined) is that the transmitter (e.g., the current AP MLD) will not clear one or more of the data in the transmitter's send buffer, starting from the window start position, such as data to be sent (i.e., data not sent by the transmitter) and data that failed to be sent (i.e., data not successfully sent by the transmitter).

[0009] In the embodiment described above, if a non-AP MLD triggers a temporary association with a target AP MLD, it can be guaranteed that data in the transmit buffer will not be cleared, starting from the window start position.

[0010] With respect to the first aspect, in one possible implementation, the method further includes, if the current AP MLD does not support the first capability, the current AP MLD clears the successfully transmitted data in the transmit buffer, or, if the current AP MLD supports the first capability, the current AP MLD retains the successfully transmitted data that starts from the window start position and is in the transmit buffer, wherein the first capability is the current AP MLD's ability to still retain the successfully transmitted data that starts from the window start position and is in the transmit buffer if the current AP MLD determines that a non-AP MLD has triggered a temporary association with a target AP MLD.

[0011] In the embodiments described above, if the current AP MLD does not support the first capability, the current AP MLD clears the successfully transmitted data in the transmit buffer. This indicates that when a non-AP MLD roams to a target AP MLD, block acknowledgement (BA) session information between the current AP MLD and the non-AP MLD needs to be transferred, i.e., a BA session transfer needs to be performed. This reduces or avoids service interruptions in the roaming handover process of the non-AP MLD and further improves the communication reliability of the non-AP MLD in the roaming process. If the current AP MLD supports the first capability, the current AP MLD retains the successfully transmitted data in the transmit buffer, starting from the window start position. This indicates that a BA session transfer may not be performed when a non-AP MLD roams to a target AP MLD.

[0012] With respect to the first aspect, in one possible implementation, the method further includes, if the current AP MLD supports the first capability and the current AP MLD determines that a non-AP MLD has triggered a temporary association with a target AP MLD, the current AP MLD deletes the BA session information between the current AP MLD and the non-AP MLD, or if the current AP MLD does not support the first capability and the current AP MLD determines that a non-AP MLD has triggered a temporary association with a target AP MLD, the current AP MLD retains the BA session information between the current AP MLD and the non-AP MLD.

[0013] In the embodiments described above, if the current AP MLD supports the first capability and the current AP MLD determines that the non-AP MLD has triggered a temporary association with the target AP MLD, the current AP MLD may delete the BA session information between the current AP MLD and the non-AP MLD in order to avoid BA session forwarding. If the current AP MLD does not support the first capability and the current AP MLD determines that the non-AP MLD has triggered a temporary association with the target AP MLD, the current AP MLD must retain the BA session information between the current AP MLD and the non-AP MLD. This ensures that BA session forwarding can be performed when the non-AP MLD roams to the target AP MLD in order to avoid packet loss caused by roaming handover.

[0014] With respect to the first aspect, in one possible implementation, the method further includes the current AP MLD transmitting BA session information between the current AP MLD and a non-AP MLD to a target AP MLD.

[0015] In the embodiments described above, the target AP MLD needs to use BA session information between the current AP MLD and the non-AP MLD. This reduces or avoids service interruptions during roaming handover processing for the non-AP MLD and further improves the communication reliability of the non-AP MLD during roaming.

[0016] With respect to the first aspect, in one possible implementation, the method further includes the current AP MLD sending first information to a non-AP MLD, the first information indicating that the data in the transmit buffer has not been fully transmitted.

[0017] In the embodiments described above, if the current AP MLD fails to complete the data transmission, the current AP MLD may send first information to the non-AP MLD to prevent the non-AP MLD from triggering a downlink transmission with the target AP MLD and / or the non-AP MLD from deleting the key in the current AP MLD.

[0018] The key in this application may include at least one of the following: a pairwise transient key (PTK), a group transient key (GTK), an integrity group transient key (IGTK), and a beacon integrity group transient key (BIGTK).

[0019] With respect to the first aspect, in one possible implementation, the first information is carried in a more data field of the first frame, the more data field of the first frame is set to 1, and the first frame is a data frame or a disassociation frame.

[0020] With respect to the first aspect, in one possible implementation, the method further includes the current AP MLD transmitting second information to a non-AP MLD or target AP MLD, the second information indicating that all data in the transmit buffer has been transmitted.

[0021] In the embodiment described above, the non-AP MLD can know whether the current AP MLD has completed data transmission.

[0022] With respect to the first aspect, in one possible implementation, the second information is carried in the more data field of the second frame, the more data field of the second frame is set to 0, and the second frame is a data frame or a disassociation frame.

[0023] With respect to the first aspect, in one possible implementation, the method further includes the current AP MLD receiving third information from a target AP MLD, and the third information being used to request all data in the transmit buffer. In other words, the third information is used to request that all data in the transmit buffer be transferred.

[0024] With respect to the first aspect, in one possible implementation, the method further includes the current AP MLD receiving fourth information from a target AP MLD, the fourth information being used to request BA session information between the current AP MLD and a non-AP MLD. In other words, the fourth information is used to request that the BA session information between the current AP MLD and a non-AP MLD be transferred to the target AP MLD.

[0025] With respect to the first aspect, in one possible implementation, the method further includes the current AP MLD obtaining fifth information, the fifth information indicating that the target AP MLD supports BA session forwarding.

[0026] Regarding the first aspect, in one possible implementation, the method further includes that the current AP MLD sends the sixth information to the non-AP MLD, and the sixth information indicates to the non-AP MLD to hold the BA session information between the current AP MLD and the non-AP MLD. Optionally, the sixth information may include a service identifier, and the service identifier is associated with the BA session information between the current AP MLD and the non-AP MLD. The service identifier in this application may be referred to as a traffic identifier (TID).

[0027] In the foregoing embodiments, to avoid packet loss caused by roaming handover, it is guaranteed that BA session transfer can be performed when the non-AP MLD roams to the target AP MLD. In addition, when the sixth information includes a service identifier, the non-AP MLD may hold the BA session information associated with the service identifier.

[0028] Regarding the first aspect, in one possible implementation, the sixth information may further indicate to the non-AP MLD to hold data in the receive buffer of the non-AP MLD and / or the scoreboard of the non-AP MLD. The receive buffer is configured to buffer data received by the non-AP MLD from the current AP MLD. The scoreboard is used to record data that has been successfully received by the non-AP MLD and / or data that has not been successfully received by the non-AP MLD, for example, data successfully received from the current AP MLD or data not successfully received from the current AP MLD.

[0029] In the foregoing embodiments, it is guaranteed that the data in the receive buffer is not cleared when the non-AP MLD roams to the target AP MLD.

[0030] With respect to the first aspect, in one possible implementation, the method further includes the current AP MLD transmitting seventh information to a non-AP MLD, the seventh information indicating that the current AP MLD supports BA session forwarding.

[0031] With respect to the first aspect, in one possible implementation, the method further includes the current AP MLD receiving eighth information from a non-AP MLD, and indicating to the current AP MLD that the eighth information holds BA session information between the current AP MLD and the non-AP MLD. Optionally, the eighth information may include a service identifier, which is associated with the BA session information between the current AP MLD and the non-AP MLD.

[0032] In the embodiments described above, it is ensured that BA session forwarding can be performed when the non-AP MLD roams to the target AP MLD in order to avoid packet loss caused by roaming handover. In addition, if the eighth piece of information includes a service identifier, the non-AP MLD may retain BA session information associated with the service identifier.

[0033] According to a second aspect, a communication method is provided, which includes: a non-AP MLD receiving all data from the transmit buffer of the current AP MLD, the transmit buffer being used to buffer the data of the current AP MLD and the data of the non-AP MLD; or a non-AP MLD receiving all data from the transmit buffer of the current AP MLD via a target AP MLD, and the non-AP MLD triggering a temporary association with the target AP MLD.

[0034] In the embodiments described above, the triggering of a temporary association between a non-AP MLD and a target AP MLD indicates that the non-AP MLD is beginning to roam to the target AP MLD. In this case, the non-AP MLD receives all data from the current AP MLD's transmit buffer, or the non-AP MLD receives all data from the current AP MLD's transmit buffer via the target AP MLD. This reduces packet loss during the non-AP MLD's roaming handover process and further improves the non-AP MLD's communication reliability during roaming.

[0035] With respect to a second aspect, in one possible implementation, the method further includes the non-AP MLD receiving first information from the current AP MLD, the first information indicating that the data in the transmit buffer has not been fully transmitted.

[0036] In the embodiments described above, in order to prevent the non-AP MLD from triggering a downlink transmission to the target AP MLD and / or deleting the key in the current AP MLD if the current AP MLD fails to complete the data transmission, the current AP MLD may send first information to the non-AP MLD.

[0037] With respect to the second aspect, in one possible implementation, the first information is carried in the more data field of the first frame, the more data field of the first frame is set to 1, and the first frame is a data frame or a disassociation frame.

[0038] With respect to the second aspect, in one possible implementation, the method further includes the non-AP MLD receiving second information from the current AP MLD, the second information indicating that all data in the transmit buffer has been transmitted.

[0039] In the embodiment described above, the non-AP MLD can know whether the current AP MLD has completed data transmission.

[0040] With respect to the second aspect, in one possible implementation, the second information is carried in the more data field of the second frame, the more data field of the second frame is set to 0, and the second frame is a data frame or a disassociation frame.

[0041] With respect to the second aspect, in one possible implementation, when a non-AP MLD triggers a temporary association with a target AP MLD, the protocol predefined that at least one of the following is maintained: a key between the current AP MLD and the non-AP MLD, BA session information between the current AP MLD and the non-AP MLD, a key between the target AP MLD and the non-AP MLD, and BA session information between the target AP MLD and the non-AP MLD.

[0042] In the above-described embodiment, it is guaranteed that communication between the current AP MLD and the non-AP MLD, and communication between the current AP MLD and the target AP MLD, etc., will not be interfered with during the roaming handover process of the non-AP MLD.

[0043] With respect to the second aspect, in one possible implementation, the method further includes the non-AP MLD transmitting the 9th information to a target AP MLD, which instructs the target AP MLD to obtain BA session information between the current AP MLD and the non-AP MLD. Optionally, the 9th information further includes a service identifier, the service identifier being associated with BA session information between the current AP MLD and the non-AP MLD.

[0044] The above embodiment demonstrates that the target AP MLD needs to obtain BA session information between the current AP MLD and the non-AP MLD, and as a result, the BA session information between the current AP MLD and the non-AP MLD can still be used. This reduces or avoids service interruptions in the roaming handover process of the non-AP MLD and further improves the communication reliability of the non-AP MLD in roaming. In addition, the target AP MLD can know the BA session information that needs to be transferred from the current AP MLD to the target AP MLD.

[0045] With respect to the second aspect, in one possible implementation, the method further includes the non-AP MLD receiving sixth information from the current AP MLD and indicating to the non-AP MLD that the sixth information holds BA session information between the current AP MLD and the non-AP MLD. Optionally, the sixth information may include a service identifier associated with the BA session information between the current AP MLD and the non-AP MLD.

[0046] In the embodiments described above, it is ensured that BA session forwarding can be performed when the non-AP MLD roams to the target AP MLD in order to avoid packet loss caused by roaming handover. In addition, if the sixth information includes a service identifier, the non-AP MLD may retain BA session information associated with the service identifier.

[0047] With respect to the second aspect, in one possible implementation, the sixth information may be further indicated to the non-AP MLD to hold data in the non-AP MLD's receive buffer and / or scoreboard. The receive buffer is configured to buffer data received by the non-AP MLD from the current AP MLD.

[0048] In the above-described embodiment, it is guaranteed that data in the receive buffer is not cleared when a non-AP MLD roams to a target AP MLD.

[0049] With respect to the second aspect, in one possible implementation, the method further includes the non-AP MLD receiving seventh information from the current AP MLD, the seventh information indicating that the current AP MLD supports BA session forwarding.

[0050] With respect to the second aspect, in one possible implementation, the method further includes the non-AP MLD transmitting eighth information to the current AP MLD, indicating to the current AP MLD that the eighth information holds BA session information between the current AP MLD and the non-AP MLD. Optionally, the eighth information may include a service identifier, which is associated with BA session information between the current AP MLD and the non-AP MLD.

[0051] In the embodiments described above, to avoid packet loss caused by roaming handover, it is guaranteed that BA session forwarding can be performed when a non-AP MLD roams to a target AP MLD. In addition, if the eighth piece of information includes a service identifier, the non-AP MLD may retain BA session information associated with the service identifier.

[0052] According to a third aspect, a communication method is provided, which includes: a target AP MLD receiving all data from the current AP MLD's transmit buffer, the transmit buffer being used to buffer the current AP MLD's data and the non-AP MLD's data; the non-AP MLD triggering a temporary association with the target AP MLD; and, if the temporary association between the target AP MLD and the non-AP MLD is activated, the target AP MLD transmitting data from the current AP MLD to the non-AP MLD.

[0053] In the embodiments described above, the non-AP MLD triggering a temporary association with the target AP MLD indicates that the non-AP MLD is beginning to roam to the target AP MLD. In this case, the target AP MLD sends data from the current AP MLD to the non-AP MLD. This reduces packet loss during the non-AP MLD's roaming handover process and further improves the non-AP MLD's communication reliability during roaming.

[0054] With respect to a third aspect, in one possible implementation, the method further includes the target AP MLD receiving BA session information between the current AP MLD and a non-AP MLD from the current AP MLD, and the target AP MLD transmitting data from the current AP MLD to the non-AP MLD, which includes the target AP MLD transmitting data from the current AP MLD to the non-AP MLD based on the BA session information.

[0055] In the embodiments described above, it may be indicated that the target AP MLD still uses the BA session information between the current AP MLD and the non-AP MLD. This reduces or avoids service interruptions during roaming handover processing for the non-AP MLD and further improves the communication reliability of the non-AP MLD during roaming.

[0056] With respect to a third aspect, in one possible implementation, the method further includes: a target AP MLD receiving address information of the current AP MLD from a non-AP MLD; if a non-AP MLD associated with the current AP MLD is temporarily associated with the target AP MLD, the target AP MLD sending third information to the current AP MLD based on the address information of the current AP MLD, the third information being used to request all data in the transmit buffer.

[0057] With respect to a third aspect, in one possible implementation, the method further includes the target AP MLD sending fourth information to the current AP MLD based on the address information of the current AP MLD, the fourth information being used to request BA session information between the current AP MLD and the non-AP MLD.

[0058] With respect to the third aspect, in one possible implementation, the method further includes the target AP MLD broadcasting fifth information, the fifth information indicating that the target AP MLD supports BA session forwarding.

[0059] With respect to a third aspect, in one possible implementation, the method further includes the target AP MLD receiving ninth information from a non-AP MLD, and the ninth information instructing the target AP MLD to obtain BA session information between the current AP MLD and the non-AP MLD.

[0060] The above embodiment demonstrates that the target AP MLD needs to obtain BA session information between the current AP MLD and the non-AP MLD, and as a result, the BA session information between the current AP MLD and the non-AP MLD can still be used. This reduces or avoids service interruptions in the roaming handover process of the non-AP MLD and further improves the communication reliability of the non-AP MLD in roaming. In addition, the target AP MLD can know the BA session information that needs to be transferred from the current AP MLD to the target AP MLD.

[0061] With respect to the third aspect, in one possible implementation, the ninth information further includes a service identifier corresponding to the data in the transmit buffer, and the ninth information further indicates to the target AP MLD to obtain BA session information between the current AP MLD and the non-AP MLD. Optionally, the ninth information further includes a service identifier associated with the BA session information between the current AP MLD and the non-AP MLD.

[0062] The above embodiment demonstrates that the target AP MLD needs to obtain BA session information between the current AP MLD and the non-AP MLD, and as a result, the BA session information between the current AP MLD and the non-AP MLD can still be used. This reduces or avoids service interruptions in the roaming handover process of the non-AP MLD and further improves the communication reliability of the non-AP MLD in roaming. In addition, the target AP MLD can know the BA session information that needs to be transferred from the current AP MLD to the target AP MLD.

[0063] According to a fourth aspect, a communication method is provided, which includes a gateway device receiving first information from the current AP MLD, the first information indicating that a non-AP MLD associated with the current AP MLD has triggered a temporary association with a target AP MLD, and the gateway device separately transmitting one or more first data to the current AP MLD and the target AP MLD.

[0064] In the embodiments described above, the gateway device can know from the current AP MLD that a non-AP MLD associated with the current AP MLD triggers a temporary association with the target AP MLD. This indicates that the non-AP MLD is beginning to roam to the target AP MLD. In this case, the gateway device may send the same data separately to the current AP MLD and the target AP MLD, and as a result, if the non-AP MLD hands over data transmission from the current AP MLD to the target AP MLD, the current AP MLD may notify the target AP MLD of the data that needs to be sent to the non-AP MLD. In this way, if the current AP MLD does not migrate the data to the target AP MLD, the target AP MLD can send the data that was not successfully sent to the non-AP MLD by the current AP MLD to the non-AP MLD. Thus, delays caused by data migration can be avoided, packet loss in the roaming handover process of the non-AP MLD can be reduced, and the communication reliability of the non-AP MLD in the roaming process can be further improved.

[0065] With respect to a fourth aspect, in one possible implementation, the method further includes the gateway device separately transmitting numbers corresponding to one or more first data to the current AP MLD and the target AP MLD.

[0066] With respect to a fourth aspect, in one possible implementation, the method further includes the gateway device receiving data aggregation capability from a target AP MLD, the gateway device receiving data aggregation capability from a current AP MLD, and the gateway device generating one or more first data based on the data aggregation capability of the target AP MLD and the data aggregation capability of the current AP MLD.

[0067] In the embodiment described above, the first data is generated based on the data aggregation capacity of the target AP MLD and the current data aggregation capacity of the AP MLD. In this way, the amount of data transmitted can be reduced and the data transmission speed can be improved.

[0068] According to a fifth aspect, a communication method is provided, the communication method comprising: a target AP MLD receiving one or more first data from a gateway device, wherein if the gateway device determines that a non-AP MLD associated with the current AP MLD has triggered a temporary association with the target AP MLD, the one or more first data are data transmitted by the gateway device; the target AP MLD receiving second information from the current AP MLD, the second information being used by the target AP MLD to determine which data should be transmitted from the one or more first data; and, if a temporary association between the target AP MLD and the non-AP MLD is activated, the target AP MLD transmitting the data to be transmitted to the non-AP MLD.

[0069] In the embodiments described above, the gateway device can know from the current AP MLD that a non-AP MLD associated with the current AP MLD triggers a temporary association with the target AP MLD. This indicates that the non-AP MLD is beginning to roam to the target AP MLD. In this case, the gateway device may send the same data separately to the current AP MLD and the target AP MLD, and as a result, if the non-AP MLD hands over data transmission from the current AP MLD to the target AP MLD, the current AP MLD may notify the target AP MLD of the data that needs to be sent to the non-AP MLD. In this way, if the current AP MLD does not migrate the data to the target AP MLD, the target AP MLD may send the data that was not successfully sent to the non-AP MLD by the current AP MLD to the non-AP MLD. Thus, delays caused by data migration can be avoided, packet loss in the roaming handover process of the non-AP MLD can be reduced, and the communication reliability of the non-AP MLD in the roaming process can be further improved.

[0070] With respect to the fifth aspect, in one possible implementation, the second information includes a transmission status corresponding to one or more first data, the transmission status includes success or failure, and the data to be transmitted includes data from one or more first data for which the transmission status is failure.

[0071] With respect to the fifth aspect, in one possible implementation, the second information further includes a retransmission status corresponding to one or more first data, the retransmission status including retransmission success or retransmission failure, and the data to be transmitted further includes data from one or more first data whose retransmission status is retransmission failure.

[0072] With respect to the fifth aspect, in one possible implementation, the second information indicates a starting number corresponding to the data to be transmitted, and the data to be transmitted is one or more of the first data whose number is greater than or equal to the starting number.

[0073] With respect to the fifth aspect, in one possible implementation, the method further includes the target AP MLD receiving a number from the gateway device corresponding to one or more first data items.

[0074] With respect to a fifth aspect, in one possible implementation, the method further includes the target AP MLD transmitting the data aggregation capabilities of the target AP MLD to the gateway device.

[0075] According to the sixth aspect, a communication method is provided, the communication method comprising: the current AP MLD receiving one or more first data from a gateway device, wherein the one or more first data are data transmitted by the gateway device if the gateway device determines that a non-AP MLD associated with the current AP MLD has triggered a temporary association with a target AP MLD; and the current AP MLD transmitting second information to the target AP MLD, the second information being used by the target AP MLD to determine which data should be transmitted from the one or more first data.

[0076] In the embodiments described above, the gateway device can know from the current AP MLD that a non-AP MLD associated with the current AP MLD triggers a temporary association with the target AP MLD. This indicates that the non-AP MLD is beginning to roam to the target AP MLD. In this case, the gateway device may send the same data separately to the current AP MLD and the target AP MLD, and as a result, if the non-AP MLD hands over data transmission from the current AP MLD to the target AP MLD, the current AP MLD may notify the target AP MLD of the data that needs to be sent to the non-AP MLD. In this way, if the current AP MLD does not migrate the data to the target AP MLD, the target AP MLD may send the data that was not successfully sent to the non-AP MLD by the current AP MLD to the non-AP MLD. Thus, delays caused by data migration can be avoided, packet loss in the roaming handover process of the non-AP MLD can be reduced, and the communication reliability of the non-AP MLD in the roaming process can be further improved.

[0077] With respect to the sixth aspect, in one possible implementation, the second information includes a transmission status corresponding to one or more first data, the transmission status includes success or failure, and the data to be transmitted includes data from one or more first data for which the transmission status is failure.

[0078] With respect to the sixth aspect, in one possible implementation, the second information further includes a retransmission status corresponding to one or more first data, the retransmission status including retransmission success or retransmission failure, and the data to be transmitted further includes data from one or more first data whose retransmission status is retransmission failure.

[0079] With respect to the sixth aspect, in one possible implementation, the second information indicates a starting number corresponding to the data to be transmitted, and the data to be transmitted is one or more of the first data whose number is greater than or equal to the starting number.

[0080] With respect to the sixth aspect, in one possible implementation, the method further includes the target AP MLD receiving a number from the gateway device corresponding to one or more first data items.

[0081] With respect to the sixth aspect, in one possible implementation, the method further includes the target AP MLD transmitting the data aggregation capabilities of the target AP MLD to the gateway device.

[0082] According to the seventh aspect, a communication device is provided, which includes a unit or module configured to perform a method according to any one of the first to sixth aspects.

[0083] According to the eighth aspect, a communication device is provided. The communication device includes at least one processor and memory. The memory is configured to store computer programs or instructions. The at least one processor is configured to execute computer programs or instructions in the memory, thereby performing a method according to any one of the first to sixth aspects.

[0084] According to the ninth aspect, a communication system is provided. The communication system includes a current access point multilink device and a non-access point multilink device. The current access point multilink device is configured to perform a method according to any implementation of the first aspect. The non-access point multilink device is configured to perform a method according to any implementation of the second aspect.

[0085] According to the tenth aspect, a communication system is provided. The communication system includes a current access point multilink device, a non-access point multilink device, and a target access point multilink device. The current access point multilink device is configured to perform a method according to any implementation of the first aspect. The non-access point multilink device is configured to perform a method according to any implementation of the second aspect. The target access point multilink device is configured to perform a method according to any implementation of the third aspect.

[0086] According to the eleventh aspect, a communication system is provided. The communication system includes a gateway device, a current access point multilink device, a non-access point multilink device, and a target access point multilink device. The gateway device is configured to perform a method according to any implementation of the fourth aspect. The target access point multilink device is configured to perform a method according to any implementation of the fifth aspect. The current access point multilink device is configured to perform a method according to any implementation of the sixth aspect.

[0087] According to the twelfth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions, and when a computer instruction is executed, the computer is able to perform a method according to any one of the first to sixth aspects.

[0088] According to the 13th aspect, a computer program product including computer program code is provided. When the computer program code is executed by a computer, the computer becomes capable of performing any one of the methods according to the first to sixth aspects.

[0089] According to the fourteenth aspect, a chip is provided. The chip includes at least one processor and an interface. The processor is configured to read and execute instructions stored in memory. Once an instruction is executed, the chip becomes capable of performing a method according to any one of the first to sixth aspects. [Brief explanation of the drawing]

[0090] [Figure 1] This is the basic architecture of a communication system according to one embodiment of this application. [Figure 2] This is a schematic flowchart of a communication method according to one embodiment of this application. [Figure 3] This is a schematic flowchart of another communication method according to one embodiment of this application. [Figure 4] This is a diagram of a transmission queue according to one embodiment of the present application. [Figure 5] This is a schematic flowchart of yet another communication method according to one embodiment of this application. [Figure 6] This is a diagram of the first data number and sequence number according to one embodiment of the present application. [Figure 7] This is a diagram showing the structure of a communication device according to one embodiment of this application. [Figure 8] This is a diagram showing the structure of another communication device according to one embodiment of this application. [Figure 9] This is a diagram showing the structure of yet another communication device according to one embodiment of this application. [Modes for carrying out the invention]

[0091] The following describes the technical solutions of embodiments of this application with reference to the accompanying drawings of embodiments of this application. In embodiments of this application, the terms “system” and “network” may be used interchangeably. Unless otherwise stated, “ / ” indicates an “or” relationship between related things. For example, A / B can mean A or B. The term “and / or” in this application simply describes a relationship of association for describing related objects, and indicates that three relationships may exist. For example, A and / or B can mean the following three cases: A only exists, A and B both exist, and B only exists, where A and B may each be singular or plural. Also in the description of this application, “plural” means two or more unless otherwise specified. “At least one of the following items (elements)” or similar expressions mean any combination of these items, including any combination of singular items (elements) or plural items (elements). For example, at least one item (element) among a, b, or c can represent a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural. In addition, in order to clearly illustrate the technical solutions in the embodiments of this application, terms such as “first” and “second” are used in the embodiments of this application to distinguish the same or similar items having essentially the same network element or purpose. Those skilled in the art will understand that terms such as “first” and “second” do not limit the quantity or order of execution, nor do they limit the distinct differences.

[0092] Whenever "one embodiment," "some embodiments," etc., are used in the embodiments of this application, it means that one or more embodiments of this application include certain features, structures, or characteristics described with reference to the embodiments. Therefore, phrases such as "in one embodiment," "in some embodiments," "in some other embodiments," or "in other embodiments" appearing elsewhere in this specification do not necessarily refer to the same embodiment. Instead, these phrases mean "one or more embodiments, but not all," unless specifically emphasized in a different way. The terms "include," "contain," "have," and variations thereof all mean "include, but not limited to," unless specifically emphasized in a different way.

[0093] The purpose, technical solution, and beneficial effects of this application are described in more detail in the following specific implementations. It should be understood that the following descriptions represent only specific implementations of this application and are not intended to limit the scope of protection. Modifications, equivalent substitutions, improvements, etc., made based on the technical solution of this application shall fall within the scope of protection.

[0094] In the embodiments of this application, unless otherwise specified or unless there is a logical inconsistency, the terminology and / or descriptions of different embodiments are consistent, mutually referential, and the technical features of different embodiments can be combined on the basis of their internal logical relationships to form new embodiments.

[0095] First, we will describe the communication scenarios to which the embodiments of this application may be applicable. It should be understood that the embodiments of this application may be applicable to wireless local area network (WLAN) scenarios and may be applicable to IEEE 802.11 system standards, e.g., 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, or the next generation of 802.11ax, e.g., 802.11be or further next generations. For example, the communication method provided in the embodiments of this application may be applicable to MLD roaming scenarios of wireless communication systems, e.g., a scenario in which a non-AP MLD roams between at least two AP MLDs, or a scenario in which a non-AP MLD transitions from a basic service set (BSS) to another BSS within the same extended service set (ESS). Alternatively, embodiments of this application may be applicable to wireless local area network systems, such as Internet of Things (IoT) networks or Vehicle to X (V2X) networks. Indeed, embodiments of this application may be further applicable to other possible communication systems, such as long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication systems (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, and future 6G communication systems.

[0096] WLAN started with the 802.11a / g standard, progressed through 802.11n, 802.11ac, and 802.11ax, and is currently being discussed as 802.11be and Wi-Fi 8. 802.11n is also called high throughput (HT), 802.11ac is also called very high throughput (VHT), 802.11ax is also called high efficiency (HE) or Wi-Fi 6, and 802.11be is also called extremely high throughput (EHT) or Wi-Fi 7. Pre-HT standards like 802.11a / b / g may be collectively referred to as non-HT.

[0097] The following describes the basic architecture of a communication system to which the embodiments of this application can be applied, using an example where the embodiments of this application are applicable to a WLAN scenario.

[0098] Figure 1 shows the basic architecture of a communication system according to one embodiment of this application.

[0099] Figure 1 may include AP MLD 1, AP MLD 2, and a non-AP MLD. AP MLD 1 and AP MLD 2 may each include at least one AP (Figure 1 shows that AP MLD 1 includes AP 1 and AP 2, and AP MLD 2 includes AP 3 and AP 4). The non-AP MLD may include at least one STA (Figure 1 shows that the non-AP MLD includes STA 1 and STA 2). AP MLD 1 may communicate separately with AP MLD 2 and the non-AP MLD, and AP MLD 2 may communicate with the non-AP MLD. In other words, in the process of a non-AP MLD roaming from AP MLD 1 to AP MLD 2, the non-AP MLD may communicate with AP MLD 1 via a link on which several STAs (e.g., STA 1) within the non-AP MLD operate, and the non-AP MLD may communicate with AP MLD 2 via a link on which another part of STA (e.g., STA 2) within the non-AP MLD operates. Optionally, Figure 1 may further include a gateway device and a server. For example, the server may send downlink data to the gateway device, and the gateway device may send downlink data to AP MLD 1 and / or AP MLD 2. In another example, AP MLD 1 and / or AP MLD 2 may send uplink data from the non-AP MLD to the gateway device, and the gateway device may send uplink data to the server. In addition, as used herein, AP MLD 1 and AP MLD 2 may be referred to as the current AP MLD and the target AP MLD, respectively.

[0100] Please note that Figure 1 is merely an example and should not be considered a specific limitation to this application. The devices in the communication system shown in Figure 1 will be described in detail below.

[0101] 1.STA In embodiments of this application, the STA may be an STA applicable to the IEEE 802.11 system standard and may be various user terminals, user equipment, access devices, subscriber stations, subscriber units, mobile stations, user agents, user devices, or other devices having wireless communication capabilities. User terminals may include various handheld devices, in-vehicle devices, wearable devices, or computing devices having wireless communication capabilities, or other processing devices connected to wireless modems, and may include various forms of user equipment (UE), mobile stations (MS), terminals, terminal equipment, mobile communication devices, handheld devices, portable computing devices, entertainment devices, game devices or systems, global positioning system devices, or any other suitable devices configured to perform network communication over a wireless medium. For example, the STA may be a router, switch, bridge, etc. For ease of explanation, the devices described herein will be collectively referred to as stations or STAs.

[0102] Optionally, the STA may be a terminal product that supports media access control (MAC) and the physical layer (PHY) of the 802.11 system standard, such as a mobile phone or notebook computer.

[0103] 2. AP The AP in the embodiments of this application may be an AP applicable to the IEEE 802.11 system standard, or a device deployed in a wireless communication network that provides wireless communication functionality to STAs associated with the AP. The AP may be used as a hub in a communication system and is typically a network-side product that supports the MAC and PHY of the 802.11 system standard, and may be a communication device such as a base station, router, gateway, repeater, communication server, switch, or bridge. The base station may include various forms of macro base stations, micro base stations, relay stations, etc. For the sake of simplicity, the aforementioned devices are collectively referred to as APs in this specification.

[0104] 3. MLD A Multi-Link Device (MLD) is a wireless communication device that supports parallel transmission over multiple links and may also be called a multi-band device. Compared to devices that support only single-link transmission, MLDs have higher transmission efficiency and higher throughput. The frequency bands in which an MLD operates may include one or more of the following frequency bands: sub-1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz. An MLD includes one or more affiliated stations (STAs), each of which is a logical station and may operate on a single link. An affiliated station may be an AP or a non-AP STA. For simplicity of explanation, in this application, an MLD where the affiliated station is an AP may be referred to as a multi-link AP, multi-link AP device, or AP MLD, and an MLD where the affiliated station is a non-AP STA may be referred to as a multi-link STA, multi-link STA device, STA MLD, or non-AP MLD. It should be understood that each station in an MLD may operate separately on a single link, but multiple stations are permitted to operate on the same link.

[0105] 4. Gateway device The gateway device of this application may transmit downlink data from the server to the current AP MLD and / or target AP MLD, and may further transmit uplink data from the non-AP MLD to the server.

[0106] 5. Server The server in this application may transmit downlink data to the gateway device or receive uplink data from the gateway device. There may be one or more servers.

[0107] The servers referred to in the embodiments of this application may be a single server or a server cluster comprising multiple servers, but are not limited thereto.

[0108] The communication method provided in the embodiment of this application will be described in detail below with reference to Figure 1.

[0109] To facilitate understanding, several concepts related to the embodiments of this application are described below for reference with examples. These are as follows:

[0110] 1. Transmit buffer The AP MLD's transmit buffer (e.g., the current AP MLD or the target AP MLD) may be used to buffer data for both the AP MLD and non-AP MLDs.

[0111] Some of the data referred to in this application may be medium access control (MAC) service data units (MSDUs) or aggregate MSDUs (A-MSDUs). An A-MSDU may contain one or more MSDUs.

[0112] In this application, the protocol (pre-defined) is that if the current AP MLD determines that a non-AP MLD has triggered a temporary association with a target AP MLD, then one or more of the data in the current AP MLD's transmit buffer, starting from the window start position, including data to be transmitted (i.e., data not yet transmitted by the current AP MLD to the non-AP MLD) and data that failed to be transmitted (i.e., data not successfully transmitted by the current AP MLD to the non-AP MLD), will not be cleared, or will not be permitted to be cleared. Optionally, the protocol may further (pre-defined) be permitted to clear one or more of the data to be transmitted and data that failed to be transmitted, located before the window start position and in the transmit buffer, if the current AP MLD determines that a non-AP MLD has triggered a temporary association with a target AP MLD. It should also be understood that, at its discretion, the protocol (pre-defined) may not allow the transmitter (e.g., the current AP MLD) to clear one or more of the data in the transmitter's transmit buffer, starting from the window start position, including data that should be transmitted and data that failed to transmit (i.e., data that was not successfully transmitted by the transmitter). Indeed, the protocol may further (pre-defined) allow the transmitter to clear one or more of the data that should be transmitted and data that failed to transmit, which are in the transmit buffer, before the window start position.

[0113] Optionally, the current AP MLD may determine that the non-AP MLD is triggering a temporary association with the target AP MLD by receiving first instruction information from the non-AP MLD. In other words, the first instruction information may indicate that the non-AP MLD is triggering a temporary association with the target AP MLD. For example, the first instruction information may be carried in the target basic service set identifier (BSS identifier, BSSID) field of a basic service set transition management (BTM) response frame. The BTM response frame may further include other fields, which are not limited to this application.

[0114] In this application, "a non-AP MLD triggers a temporary association with a target AP MLD" may be understood as at least one of the following: the non-AP MLD prepares to roam to the target AP MLD, or the non-AP MLD begins roaming to the target AP MLD. For illustrative purposes, an example of a non-AP MLD triggering a temporary association with a target AP MLD will be used below. In addition, the temporary association in this application may be replaced with a temporary re-association.

[0115] Optionally, the triggering of a temporary association between a non-AP MLD and a target AP MLD may be understood as follows: if several links between the current AP MLD and the non-AP MLD are disconnected (or disabled), a first STA in the non-AP MLD sends a multilink association request frame to the target AP MLD, which then uses the multilink association request frame to perform a temporary multilink association with the non-AP MLD. The specific process by which the target AP MLD performs a temporary association with the non-AP MLD is not limited in this application. The link between the first STA and the current AP MLD is disconnected (or disabled), and the link between the first STA and the target AP MLD is connected (or enabled), but the temporary association between the target AP MLD and the non-AP MLD is not activated. In other words, the gateway device may still deliver data destined for the non-AP MLD to the current AP MLD. The link between the non-AP MLD's second STA and the current AP MLD is in a connected (or enabled) state. Optionally, one or more second STAs may exist. Therefore, the current AP MLD may communicate with the non-AP MLD via the link on which the second STA operates. Generally, the non-AP MLD is associated with the current AP MLD and then temporarily associated with the target AP MLD, but the temporary association between the target AP MLD and the non-AP MLD is not activated.

[0116] 2. BA Session Information The BA session information in this application is used to establish a BA session. The specific process for establishing a BA session is not limited herein.

[0117] The BA session information in this application may include at least one of the following: a service identifier, a sequence number (SN) assigned to each data, an acknowledgment policy, whether data aggregation is permitted, the window start position of the transmit buffer of the AP MLD (e.g., the current AP MLD or the target AP MLD), the window size of the transmit buffer (WinSize_O), the transmission status of each data in the window (including success or failure), the retransmission amount of each data in the window, the window start position of the scoreboard of the non-AP MLD (WinStart_R), the window size of the scoreboard, the window start position of the receive sort buffer of the non-AP MLD (WinStart_B), and the window size of the receive sort buffer. The scoreboard is used to record data successfully received by the non-AP MLD and / or data not successfully received by the non-AP MLD, for example, data successfully received from the AP MLD (e.g., the current AP MLD or the target AP MLD), or data not successfully received from the AP MLD (e.g., the current AP MLD or the target AP MLD). The receive sort buffer is used by non-AP MLDs to buffer data from AP MLDs (e.g., the current AP MLD or the target AP MLD). The service identifier may also be called the TID. For details on the parameters included in the BA session information, see IEEE 802.11. Details are not provided here.

[0118] In this application, BA session information may be classified into two types: BA session information between the current AP MLD and non-AP MLD, and BA session information between the target AP MLD and non-AP MLD.

[0119] This application provides embodiments shown in Figures 2, 3, or 8 to solve packet loss in roaming handover processing of non-AP MLD. The embodiments will be described in detail below.

[0120] Figure 2 shows a communication method according to one embodiment of the present application. The communication method includes, but is not limited to, the following steps.

[0121] 201: The current AP MLD determines that data exists in its transmit buffer, and the transmit buffer is used to buffer the data of the current AP MLD and the non-AP MLD, and the non-AP MLD triggers a temporary association with the target AP MLD.

[0122] In one possible implementation, step 201 may be understood as follows: the current AP MLD determines that there is data in the send buffer starting from the window start position. For example, there may be one or more of the following: data that should be sent (i.e., data not sent by the current AP MLD to the non-AP MLD) and data that failed to be sent (i.e., data that was not successfully sent by the current AP MLD to the non-AP MLD). Optionally, there may be further data that was successfully sent (i.e., data successfully sent by the current AP MLD to the non-AP MLD) in the send buffer starting from the window start position. For example, if the current AP MLD determines that the non-AP MLD has triggered a temporary association with the target AP MLD, The protocol pre-defines that successfully transmitted data, starting from the window start position and located in the transmit buffer, is not permitted to be cleared. Optionally, the protocol may further pre-define that successfully transmitted data, prior to the window start position and located in the transmit buffer, may be permitted to be cleared if the current AP MLD determines that a non-AP MLD has triggered a temporary association with a target AP MLD. In another example, the protocol pre-defines that the transmitter (e.g., the current AP MLD) does not clear successfully transmitted data, starting from the window start position and located in the transmitter's transmit buffer. Optionally, the protocol may further pre-define that the transmitter may be permitted to clear successfully transmitted data, prior to the window start position and located in the transmit buffer.

[0123] 202: The current AP MLD sends all data in the transmit buffer to the non-AP MLD.

[0124] In response, the non-AP MLD receives all data from the current AP MLD's transmit buffer.

[0125] In one possible implementation, step 202 may be understood as follows: based on BA session information between the current AP MLD and the non-AP MLD, all data in the transmit buffer is transmitted to the non-AP MLD. Optionally, the current AP MLD may transmit all data in the transmit buffer to the non-AP MLD in a single transmit or multiple transmits. For example, the current AP MLD may transmit one data frame to the non-AP MLD based on the BA session information, and the data frame may contain all the data. As another example, the current AP MLD may transmit multiple data frames to the non-AP MLD based on the BA session information, and one of the multiple data frames may contain one or more of all the data. The frame structure of the data frame is not limited herein.

[0126] The optional choice by which the current AP MLD sends all data in its transmit buffer to the non-AP MLD based on BA session information can also be understood as follows: the current AP MLD sends all data in its transmit buffer to the non-AP MLD in the BA session between the current AP MLD and the non-AP MLD.

[0127] In one possible implementation, all data in the current AP MLD's send buffer includes one or more of the data that should be sent and the data that failed to be sent, starting from the window start position and located within the send buffer. Specifically, if the current AP MLD determines that one or more of the data that should be sent and the data that failed to be sent are present in the send buffer starting from the window start position, all data in the send buffer includes one or more of the data that should be sent and the data that failed to be sent. Optionally, all data in the send buffer may also include any successfully sent data, starting from the window start position and located within the send buffer. Specifically, if the current AP MLD determines that there is successfully sent data in the send buffer starting from the window start position, all data in the send buffer may also include any successfully sent data.

[0128] Optionally, this method may further include step 203 of Method 1 in Figure 2, or this method may further include steps 204 and 205 of Method 2 in Figure 2.

[0129] Method 1 203: The target AP MLD receives a second piece of information from the current AP MLD, which indicates that all data in the transmit buffer has been transmitted.

[0130] In response, the current AP MLD sends the second piece of information to the target AP MLD.

[0131] If the target AP MLD optionally receives second information from the current AP MLD, the second information indicating that all data in the transmit buffer has been transmitted can also be understood as follows: the second information indicates that the target AP MLD is permitted to transmit downlink data.

[0132] Method 2 204: The non-AP MLD receives a second piece of information from the current AP MLD, which indicates that all data in the transmit buffer has been transmitted.

[0133] In response to this, the current AP MLD sends the second piece of information to the non-AP MLD.

[0134] In one possible implementation, when a non-AP MLD receives second information from the current AP MLD, the second information may be carried in the more data field of a second frame, where the more data field of the second frame is set to 0, and the second frame is either a data frame or a disassociation frame. The frame structure of the disassociation frame is not limited in this application.

[0135] Optionally, the second frame is the last transmitted data frame, and the second frame further includes any remaining data in the transmit buffer starting from the window start position. For example, if the current AP MLD could transmit all the data in its transmit buffer to the non-AP MLD in a single transmit (i.e., the current AP MLD transmits one data frame to the non-AP MLD, and the data frame may contain all the data), then the remaining data here is all the data. As another example, if the current AP MLD could transmit all the data in its transmit buffer to the non-AP MLD in multiple transmits (i.e., the current AP MLD could transmit multiple data frames to the non-AP MLD, and the multiple data frames may include the last transmitted data frame and other data frames), then the remaining data here is one or more pieces of data from all the data other than the data carried in the other data frame (the data carried in the other data frame is one or more pieces of data in the transmit buffer starting from the window start position). Optionally, the more data field of the other data frame may be set to 1 to indicate that the data in the transmit buffer has not been fully transmitted.

[0136] 205: The target AP MLD receives information 10 from the non-AP MLD, and information 10 indicates that the target AP MLD is permitted to transmit downlink data.

[0137] In response, the non-AP MLD sends the tenth piece of information to the target AP MLD.

[0138] Optionally, this method may further include step 206.

[0139] 206: If the gateway device determines that a non-AP MLD currently associated with the AP MLD has triggered a temporary association with the target AP MLD, it sends one or more data to the target AP MLD.

[0140] In response, the target AP MLD receives one or more data from the gateway device.

[0141] In one possible implementation, prior to step 206, the method may further include the gateway device receiving 11th information from a non-AP MLD via a target AP MLD, wherein the 11th information includes address information of the non-AP MLD, such as a MAC address. Since the address information of the non-AP MLD is transmitted to the gateway device via the target AP MLD, the gateway device may determine that the non-AP MLD currently associated with the AP MLD has triggered a temporary association with the target AP MLD.

[0142] Optionally, if the non-AP MLD receives the second piece of information from the current AP MLD, the eleventh piece of information may further indicate that the first STA in the non-AP MLD enters power-saving mode, and the first STA is temporarily associated with the access point in the target AP MLD. In this way, the target AP MLD needs to wait for the trigger of the first STA in the non-AP MLD to transmit downlink data. In addition, in this case, the tenth piece of information in step 205 indicating that the target AP MLD is permitted to transmit downlink data may be understood as follows: the tenth piece of information indicates that the first STA is handing over from power-saving mode to active mode. Optionally, the tenth piece of information may be carried in a data frame, a power-saving polling (PS-POLL) frame, or a newly defined protect management frame.

[0143] In one possible implementation, the 11th piece of information may be carried in a power management field of the data frame, and the power management field may be set to 1.

[0144] There is no required execution order between step 206 and steps 201 through 203. For example, step 206 may be executed before or after any one of steps 201 through 203. Alternatively, step 206 may be executed simultaneously with any one of steps 201 through 203. Similarly, there is no required execution order between step 206 and steps 201, 202, 204, and 205. For example, step 206 may be executed before or after any one of steps 201, 202, 204, and 205. Alternatively, step 206 may be executed simultaneously with any one of steps 201, 202, 204, and 205.

[0145] Optionally, this method may further include step 207.

[0146] 207: The target AP MLD sends one or more data to the non-AP MLD.

[0147] In response, the non-AP MLD receives one or more data from the target AP MLD.

[0148] Optionally, step 207 may include the target AP MLD sending one or more data to the non-AP MLD via the first STA. For example, the target AP MLD sends one or more data to the non-AP MLD via the first STA based on BA session information between the target AP MLD and the non-AP MLD. It will also be understood that the target AP MLD sends one or more data to the non-AP MLD via the first STA in a BA session between the target AP MLD and the non-AP MLD.

[0149] In the embodiments described above, the non-AP MLD triggering a temporary association with the target AP MLD indicates that the non-AP MLD is beginning to roam to the target AP MLD. In this case, after determining that the data is present in the current AP MLD's transmit buffer, the current AP MLD may send all the data in the transmit buffer to the non-AP MLD. This reduces packet loss during the non-AP MLD's roaming handover process and further improves the non-AP MLD's communication reliability during roaming.

[0150] Optionally, in the embodiment shown in Figure 2, when a non-AP MLD triggers a temporary association with a target AP MLD, the protocol predefined that at least one of the following will be maintained: the key between the current AP MLD and the non-AP MLD, BA session information between the current AP MLD and the non-AP MLD, the key between the target AP MLD and the non-AP MLD, and BA session information between the target AP MLD and the non-AP MLD. It will also be understood that, when a non-AP MLD triggers a temporary association with a target AP MLD, and one channel maintains one or more of the following: the key between the current AP MLD and the non-AP MLD, BA session information between the current AP MLD and the non-AP MLD, etc., and the other channel maintains one or more of the following: the key between the target AP MLD and the non-AP MLD, and BA session information between the target AP MLD and the non-AP MLD, etc., the protocol predefined that the non-AP MLD will operate in dual-channel mode. In this way, it is possible to ensure that communication between the current AP MLD and the non-AP MLD, and communication between the current AP MLD and the target AP MLD, are not interfered with during the roaming handover process of the non-AP MLD.

[0151] The key in this application may include at least one of PTK, GTK, IGTK, and BIGTK.

[0152] Figure 3 shows another communication method according to one embodiment of this application. The communication method includes, but is not limited to, the following steps.

[0153] 301: The current AP MLD determines that data exists in its transmit buffer, and the transmit buffer is used to buffer the data of the current AP MLD and the non-AP MLD, and the non-AP MLD triggers a temporary association with the target AP MLD.

[0154] Step 301 may be carried out in at least three ways. Details are as follows:

[0155] Method 1.1 is similar to step 201 in Figure 2, and the details will not be repeated here.

[0156] Method 1.2: If the current AP MLD does not support the first capability, the current AP MLD determines that one or more of the data to be transmitted and the data that failed to be transmitted are present in the transmit buffer starting from the window start position. The first capability is the current AP MLD's ability to still retain successfully transmitted data in the transmit buffer, starting from the window start position, if the current AP MLD determines that a non-AP MLD has triggered a temporary association with the target AP MLD. In other words, the first capability is the ability to clear data that is before the window start position and is present in the transmit buffer, and to still retain successfully transmitted data in the transmit buffer, starting from the window start position, if the current AP MLD determines that a non-AP MLD has triggered a temporary association with the target AP MLD. Therefore, if the current AP MLD does not support the first capability, the current AP MLD may clear the successfully transmitted data in the transmit buffer.

[0157] Method 1.3: If the current AP MLD supports the first capability, the current AP MLD determines that one or more of the data to be sent, the data that failed to be sent, and the data that was successfully sent are present in the send buffer starting from the window start position. This indicates that, if the current AP MLD supports the first capability, the current AP MLD can hold the successfully sent data that is present in the send buffer starting from the window start position.

[0158] 302: The current AP MLD sends all data in the transmit buffer to the target AP MLD.

[0159] In response, the target AP MLD receives all data from the current AP MLD's transmit buffer. Optionally, this method further includes the target AP MLD receiving the current AP MLD's address information (e.g., the current AP MLD's MAC address) from a non-AP MLD, and, if a non-AP MLD associated with the current AP MLD is temporarily associated with the target AP MLD, the target AP MLD sending a third piece of information to the current AP MLD based on the current AP MLD's address information, which is used to request all data in the transmit buffer.

[0160] In one possible implementation, the current AP MLD may send all data in the send buffer to the target AP MLD via a single or multiple transmit.

[0161] In Method 1.1, if the current AP MLD determines that there is one or more data that should be sent and data that failed to be sent in the send buffer starting from the window start position, then all data in the send buffer may include one or more data that should be sent and data that failed to be sent, starting from the window start position. If the current AP MLD further determines that there is data that was successfully sent in the send buffer starting from the window start position, then all data further includes the successfully sent data.

[0162] In method 1.2, all data in the send buffer starts from the window start position and may include one or more of the data that should be sent and the data that failed to be sent within the send buffer.

[0163] In method 1.3, all data in the send buffer may start from the window start position and include one or more of the following: data to be sent, data that failed to be sent, and data that was successfully sent.

[0164] 303: When a temporary association between the target AP MLD and the non-AP MLD is activated, the target AP MLD sends data from the current AP MLD to the non-AP MLD.

[0165] In response, the non-AP MLD receives all data from the current AP MLD's transmit buffer via the target AP MLD.

[0166] Step 303 may be carried out in at least two ways. Details are as follows:

[0167] Method 2.1: The target AP MLD receives BA session information between the current AP MLD and the non-AP MLD from the current AP MLD, and the target AP MLD transmits data from the current AP MLD to the non-AP MLD based on the BA session information. Optionally, this method further includes the target AP MLD transmitting a fourth piece of information to the current AP MLD based on the current AP MLD's address information, which is used to request the BA session information. Optionally, the target AP MLD transmitting data from the current AP MLD to the non-AP MLD based on the BA session information between the current AP MLD and the non-AP MLD may also be understood as the target AP MLD transmitting data from the current AP MLD to the non-AP MLD in a BA session between the current AP MLD and the non-AP MLD. In one possible implementation, the target AP MLD may transmit data from the current AP MLD to the non-AP MLD via a single or multiple transmissions. For example, a target AP MLD may send a single data frame to a non-AP MLD based on BA session information, and the data frame may contain data. As another example, a target AP MLD may send multiple data frames to a non-AP MLD based on BA session information, and one of the multiple data frames may contain one or more pieces of data. This indicates that the target AP MLD needs to use the BA session information between the current AP MLD and the non-AP MLD. This reduces or avoids service interruptions in the non-AP MLD's roaming handover process and further improves the communication reliability of the non-AP MLD in roaming operations.

[0168] Method 2.2: The target AP MLD transmits data from the current AP MLD to the non-AP MLD based on BA session information between the target AP MLD and the non-AP MLD. BA session information may be obtained through negotiation between the target AP MLD and the non-AP MLD. Specific negotiation processes are not limited herein. Optionally, the transmission of data from the current AP MLD to the non-AP MLD based on BA session information by the target AP MLD may also be understood as the target AP MLD transmitting data to the non-AP MLD in a BA session between the target AP MLD and the non-AP MLD. In one possible implementation, the target AP MLD may transmit data to the non-AP MLD via a single transmission or multiple transmissions. For example, the target AP MLD may transmit a single data frame to the non-AP MLD based on BA session information, and the data frame may contain data. As another example, a target AP MLD may send multiple dataframes to a non-AP MLD based on BA session information, one of which may contain one or more data. This illustrates that the target AP MLD sends data from the current AP MLD to the non-AP MLD without using BA session information between the current AP MLD and the non-AP MLD, thereby avoiding BA session transfer.

[0169] It should be understood that there is a correspondence between methods 1.1 to 1.3 in Step 301 and methods 2.1 and 2.2 in Step 303. Details are as follows.

[0170] If method 1.1 is used in step 301, step 303 may be carried out using method 2.1 or method 2.2.

[0171] If method 1.2 is used in step 301, step 303 may be performed using method 2.1. In other words, if the current AP MLD does not support the first capability and the current AP MLD determines that the non-AP MLD has triggered a temporary association with the target AP MLD, the current AP MLD may retain BA session information between the current AP MLD and the non-AP MLD, send the BA session information to the target AP MLD, and as a result, the target AP MLD may send data from the current AP MLD to the non-AP MLD based on the BA session information.

[0172] If method 1.3 is used in step 301, step 303 may be performed using method 2.2. In other words, if the current AP MLD supports the first capability and the current AP MLD determines that the non-AP MLD has triggered a temporary association with the target AP MLD, the current AP MLD may delete the BA session information between the current AP MLD and the non-AP MLD, and as a result, the target AP MLD may send data from the current AP MLD to the non-AP MLD based on the BA session information between the target AP MLD and the non-AP MLD.

[0173] The temporary association between the target AP MLD and the non-AP MLD may be activated in at least two of the following implementation forms. Details are as follows:

[0174] Method 3.1: The target AP MLD receives second information from the current AP MLD, which indicates that all data in the transmit buffer (i.e., the transmit buffer of the current AP MLD and the transmit buffer of the non-AP MLD) has been transmitted. This is similar to step 203 in Figure 2. Details will not be repeated here.

[0175] Method 3.2: The target AP MLD receives the tenth piece of information from the non-AP MLD, which indicates that the target AP MLD is permitted to transmit downlink data. This is similar to step 205 in Figure 2. Details will not be repeated here.

[0176] In this application, "a temporary association between the target AP MLD and the non-AP MLD is activated" may be understood as at least one of the following: the non-AP MLD roaming to the target AP MLD.

[0177] Optionally, data from the current AP MLD may be included in the target AP MLD's target queue, which is used to buffer data sent by the target AP MLD to non-AP MLDs. If the target queue further includes one or more data from the gateway device, the data from the current AP MLD will precede one or more data in the target queue. The target AP MLD first sends data at the top of the target queue. As shown in Figure 4, the data from the current AP MLD includes data with SNs 6 through 9, and the data from the gateway device includes data with SNs 10 through 13, with the data with SNs 6 through 9 preceding the data with SNs 10 through 13 in the target queue. Therefore, the target AP MLD may first send the data with SN 6, then the data with SN 7, and the rest may be inferred by analogy.

[0178] In the embodiments described above, the triggering of a temporary association between a non-AP MLD and a target AP MLD indicates that the non-AP MLD is beginning to roam to the target AP MLD. In this case, the current AP MLD may send all data in its transmit buffer to the target AP MLD, and as a result, the target AP MLD can forward the data from the current AP MLD to the non-AP MLD. This reduces packet loss in the roaming handover process of the non-AP MLD and further improves the communication reliability of the non-AP MLD in the roaming process.

[0179] Optionally, several detailed solutions will be described individually below with reference to methods 1.1 to 1.3 of step 301 of the embodiment shown in Figure 3. For further details, please refer to Examples 1 to 3 below.

[0180] Example 1 In one possible implementation, the method further includes the current AP MLD sending a sixth piece of information to a non-AP MLD, which instructs the non-AP MLD to maintain BA session information between the current AP MLD and the non-AP MLD. Optionally, the sixth piece of information may include a service identifier associated with the BA session information between the current AP MLD and the non-AP MLD. This ensures that BA session forwarding can be performed when the non-AP MLD roams to the target AP MLD to avoid packet loss caused by roaming handover. In addition, if the sixth piece of information includes a service identifier, the non-AP MLD may maintain BA session information associated with the service identifier.

[0181] Optionally, the sixth piece of information may further indicate to the non-AP MLD that it should retain data in the non-AP MLD's receive buffer and / or scoreboard. The receive buffer is configured to buffer data received by the non-AP MLD from the current AP MLD. This ensures that the data in the receive buffer is not cleared when the non-AP MLD roams to a target AP MLD.

[0182] For example, the sixth piece of information may be carried in the request mode field. For example, the sixth piece of information may be one bit in the reserved field within the request mode field. Optionally, the request mode field may be placed within the BTM request frame. The BTM request frame may contain other fields, which are not described in detail here.

[0183] In one possible implementation, the method further includes the current AP MLD transmitting seventh information to a non-AP MLD, the seventh information indicating that the current AP MLD supports BA session transfer (BA session transfer supported). Optionally, the seventh information may be carried in a neighbor report element field. The wireless frame in which the neighbor report element field is located is not limited in this application.

[0184] In one possible implementation, the method further includes the current AP MLD receiving eighth information from a non-AP MLD, and the eighth information instructing the current AP MLD to hold BA session information between the current AP MLD and the non-AP MLD. Optionally, the eighth information may include a service identifier associated with the BA session information between the current AP MLD and the non-AP MLD. This ensures that the non-AP MLD can perform BA session forwarding when roaming to the target AP MLD to avoid packet loss caused by roaming handover. In addition, if the eighth information includes a service identifier, the non-AP MLD may hold BA session information associated with the service identifier.

[0185] Optionally, the eighth piece of information may be carried in a statuscode field. Optionally, the statuscode field may be placed in a BTM response frame or a newly defined frame. If the statuscode field is located in a BTM response frame, it may further indicate an acceptance with no MSDU loss.

[0186] Example 2 In one possible implementation, the method further includes the non-AP MLD deleting the key between the current AP MLD and the non-AP MLD. For example, when the non-AP MLD receives a disassociation frame, the non-AP MLD deletes the key between the current AP MLD and the non-AP MLD.

[0187] In one possible implementation, the method includes a non-AP MLD receiving a second instruction from the current AP MLD, which instructs the non-AP MLD to delete the BA session information between the current AP MLD and the non-AP MLD, or the second instruction indicating that the current AP MLD supports the first capability, causing the non-AP MLD to delete the BA session information. This avoids BA session transfer.

[0188] In one possible implementation, the method further includes the current AP MLD deleting the key between the current AP MLD and the non-AP MLD. For example, if the current AP MLD supports the first capability and the current AP MLD determines that the non-AP MLD has triggered a temporary association with the target AP MLD, the current AP MLD deletes the key between the current AP MLD and the non-AP MLD.

[0189] Example 3 In one possible implementation, the method further includes the current AP MLD sending first information to the non-AP MLD, where the first information indicates that the data in the transmit buffer (i.e., the current AP MLD's transmit buffer) has not been fully transmitted. This prevents the non-AP MLD from triggering a downlink transmit with the target AP MLD and / or the non-AP MLD from deleting the key in the current AP MLD if the current AP MLD has not completed the data transmission.

[0190] Optionally, the first information is carried in the more data field of the first frame, the more data field of the first frame is set to 1, and the first frame is either a data frame or a disassociation frame. If the first frame is a disassociation frame, it should be understood that the non-AP MLD may delete the key between the current AP MLD and the non-AP MLD.

[0191] Optionally, Examples 1 and 3 may further include the following detailed solutions. Details are as follows:

[0192] In one possible implementation, the method further includes the target AP MLD broadcasting a fifth piece of information indicating that the target AP MLD supports BA session forwarding.

[0193] For example, the fifth piece of information may be conveyed in the neighbor report element field.

[0194] In one possible implementation, the method further includes the target AP MLD receiving information 9 from the non-AP MLD, and the information 9 instructing the target AP MLD to obtain BA session information between the current AP MLD and the non-AP MLD. Optionally, the information 9 further includes a service identifier, which is associated with the BA session information between the current AP MLD and the non-AP MLD. This indicates that the target AP MLD needs to obtain the BA session information between the current AP MLD and the non-AP MLD in order to use the BA session information between the current AP MLD and the non-AP MLD. This reduces or avoids service interruptions in the non-AP MLD's roaming handover process and further improves the communication reliability of the non-AP MLD in roaming. In addition, the target AP MLD can know the BA session information that needs to be forwarded from the current AP MLD to the target AP MLD.

[0195] The ninth piece of information may be carried in a reassociation request frame.

[0196] Figure 5 shows yet another communication method according to one embodiment of the present application. The communication method includes, but is not limited to, the following steps.

[0197] 501: The gateway device receives a first piece of information from the current AP MLD, which indicates that a non-AP MLD associated with the current AP MLD will trigger a temporary association with the target AP MLD.

[0198] In response to this, the current AP MLD sends the first piece of information to the gateway device. For example, if the current AP MLD determines that a non-AP MLD associated with it has triggered a temporary association with the target AP MLD, the current AP MLD sends the first piece of information to the gateway device.

[0199] 502: The gateway device sends one or more first data packets separately to the current AP MLD and the target AP MLD.

[0200] In response to this, the current AP MLD and the target AP MLD receive one or more initial data packets separately from the gateway device.

[0201] The first data may be MSDU or A-MSDU.

[0202] Optionally, the method further includes the gateway device receiving data aggregation capability from a target AP MLD, the gateway device receiving data aggregation capability from the current AP MLD, and the gateway device generating one or more first data based on the data aggregation capability of the target AP MLD and the data aggregation capability of the current AP MLD. For example, the gateway device performs data aggregation on one or more second data from the server based on the data aggregation capability of the target AP MLD and the data aggregation capability of the current AP MLD to obtain one or more first data. Optionally, one first data may be obtained by aggregating one or more second data. Thus, the first data in this specification may be an A-MSDU, and the second data may be an MSDU. In this way, the data transmission rate can be improved.

[0203] In this application, data aggregation capability refers to the data aggregation capability supported by the device (e.g., the current AP MLD or the target AP MLD).

[0204] Optionally, the method further includes the gateway device assigning SNs to one or more first data items, and the gateway device separately transmitting the SNs of one or more first data items to the current AP MLD and the target AP MLD. One first data item corresponds to one SN. The SNs of one or more first data items may be used by the current AP MLD to place one or more first data items into the current AP MLD's send queue, which is used to buffer data sent by the current AP MLD to non-AP MLDs. The SNs of one or more first data items may further be used by the target AP MLD to place one or more first data items into the target AP MLD's send queue, which is used to buffer data sent by the target AP MLD to non-AP MLDs.

[0205] 503: The current AP MLD sends second information to the target AP MLD, which the target AP MLD uses to determine which data should be sent from one or more first data items.

[0206] In response, the target AP MLD receives second information from the current AP MLD.

[0207] In one possible implementation, the second information includes a transmission status corresponding to one or more first data items, where the transmission status includes success or failure, and the data to be transmitted is one of the one or more first data items whose transmission status is failure. Optionally, the second information further includes a retransmission status corresponding to one or more first data items, where the retransmission status includes retransmission success or retransmission failure, and the data to be transmitted further includes one or more first data items whose retransmission status is retransmission failure. Optionally, the second information may be included in the BA session information between the current AP MLD and non-AP MLD.

[0208] In another possible implementation, the second piece of information indicates a starting number corresponding to the data to be transmitted, and the data to be transmitted is one or more first pieces of data whose number is greater than or equal to the starting number. In this case, it should be understood that the method further includes the current AP MLD receiving numbers corresponding to one or more first pieces of data from the gateway device. One first piece of data may correspond to one or more numbers. For example, the gateway device may number one or more second pieces of data in the order in which they arrive at the gateway device, and one first piece of data may be obtained by aggregating one or more second pieces of data. Thus, one first piece of data may correspond to one or more numbers. For example, as shown in Figure 6, the numbers corresponding to the first piece of data with SN 6 are 11 and 12, the numbers corresponding to the first piece of data with SN 7 are 13 and 14, and the number corresponding to the first piece of data with SN 8 is 15. The rest are similar and will not be repeated in detail here.

[0209] 504: When a temporary association is activated between the target AP MLD and the non-AP MLD, the target AP MLD sends the data to be sent to the non-AP MLD.

[0210] In response, the non-AP MLD receives the data that should be sent from the target AP MLD.

[0211] Optionally, the second piece of information further indicates that the target AP MLD is permitted to transmit downlink data. In this way, the target AP MLD may determine that a temporary association with the non-AP MLD has been activated.

[0212] If the second information is included in the BA session information between the current AP MLD and the non-AP MLD, step 504 may also include the target AP MLD sending data that should be sent to the non-AP MLD based on the BA session information. Optionally, the target AP MLD sending data that should be sent to the non-AP MLD based on the BA session information may also be understood as the target AP MLD sending data from the current AP MLD to the non-AP MLD in the BA session between the current AP MLD and the non-AP MLD. This indicates that the target AP MLD may still use the BA session information between the current AP MLD and the non-AP MLD, thereby reducing or avoiding service interruptions in the non-AP MLD's roaming handover process and further improving the non-AP MLD's communication reliability in the roaming process.

[0213] Optionally, this method further includes the target AP MLD receiving the address information of the current AP MLD (e.g., the MAC address of the current AP MLD) from a non-AP MLD, and, if a non-AP MLD associated with the current AP MLD is temporarily associated with the target AP MLD, the target AP MLD sending a third piece of information to the current AP MLD based on the address information of the current AP MLD, and the third piece of information being used to request BA session information.

[0214] Optionally, there may be one or more data items to be sent, and the target AP MLD may send multiple data items to be sent to the non-AP MLD via a single or multiple transmissions. For example, the target AP MLD may send one data frame to the non-AP MLD based on BA session information, and the data frame may contain multiple data items to be sent. As another example, the target AP MLD may send multiple data frames to the non-AP MLD based on BA session information, and one of the multiple data frames may contain one or more of the multiple data items to be sent.

[0215] If the second piece of information indicates a starting number corresponding to the data to be transmitted, step 504 may also include the target AP MLD transmitting the data to be transmitted to the non-AP MLD based on BA session information between the target AP MLD and the non-AP MLD. The BA session information may be obtained through negotiation between the target AP MLD and the non-AP MLD. Specific negotiation processes are not limited herein. Optionally, the target AP MLD transmitting the data to be transmitted to the non-AP MLD based on BA session information between the target AP MLD and the non-AP MLD may also be understood as the target AP MLD transmitting the data to be transmitted in the BA session between the target AP MLD and the non-AP MLD to the non-AP MLD.

[0216] Optionally, there may be one or more data items to be sent, and the target AP MLD may send multiple data items to be sent to the non-AP MLD via a single or multiple transmissions. For example, the target AP MLD may send one data frame to the non-AP MLD based on BA session information, and the data frame may contain multiple data items to be sent. As another example, the target AP MLD may send multiple data frames to the non-AP MLD based on BA session information, and one of the multiple data frames may contain one or more of the multiple data items to be sent. This indicates that the target AP MLD sends data to be sent to the non-AP MLD without using the BA session information between the current AP MLD and the non-AP MLD, thereby avoiding BA session transfer.

[0217] In the embodiments described above, the gateway device can know from the current AP MLD that a non-AP MLD associated with the current AP MLD triggers a temporary association with the target AP MLD. This indicates that the non-AP MLD is beginning to roam to the target AP MLD. In this case, the gateway device may send the same data separately to the current AP MLD and the target AP MLD, and as a result, if the non-AP MLD hands over data transmission from the current AP MLD to the target AP MLD, the current AP MLD may notify the target AP MLD of the data that needs to be sent to the non-AP MLD. In this way, if the current AP MLD does not migrate the data to the target AP MLD, the target AP MLD may send the data that was not successfully sent to the non-AP MLD by the current AP MLD to the non-AP MLD. Thus, delays due to data migration can be avoided, packet loss in the roaming handover process of the non-AP MLD can be reduced, and the communication reliability of the non-AP MLD in the roaming process can be further improved.

[0218] The above describes the solution provided in this application from the perspective of inter-device interaction. In the aforementioned implementations, it will be understood that each device includes a corresponding hardware structure and / or software module for performing each function in order to realize the aforementioned functions. Those skilled in the art will readily understand that this application can be realized by hardware, or by a combination of hardware and computer software, in combination with the example parts and algorithmic steps described in the embodiments disclosed herein. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and the design constraints of the technical solution. Those skilled in the art may realize the functions described using various methods for each specific application, but such implementations should not be considered to exceed the scope of this application.

[0219] In embodiments of this application, an AP MLD (e.g., a current AP MLD or a target AP MLD), a non-AP MLD, or a gateway device may be divided into functional modules based on the examples of the methods described above. For example, each functional module may be obtained through a division corresponding to each function, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in hardware form or in the form of a software functional module. Note that in embodiments of this application, the division into modules is an example and is merely a logical functional division. In actual implementations, other division methods may be used.

[0220] Figure 7 is a diagram of the structure of a communication device according to one embodiment of the present application. The communication device 700 may be applied to one or more of the embodiments shown in Figures 2, 3, or 5. As shown in Figure 7, the communication device 700 includes a processing module 701 and a transceiver module 702. The processing module 701 may be one or more processors, and the transceiver module 702 may be a transceiver or a communication interface. The communication device may be configured to implement the functions of an AP MLD (e.g., a current AP MLD or a target AP MLD), a non-AP MLD, or a gateway device in any one of the embodiments of the above-described method, or it may be configured to implement the functions of a network element in any one of the embodiments of the above-described method. The network element or network function may be a network element of a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). Optionally, the communication device 700 may further include a storage module 703 configured to store the program code and data of the communication device 700.

[0221] In one example, when the communication device is used as an AP MLD (e.g., a current AP MLD or a target AP MLD) or a chip used in an AP MLD (e.g., a current AP MLD or a target AP MLD), the communication device performs the steps performed by the AP MLD (e.g., a current AP MLD or a target AP MLD) in the embodiments of the method described above. The transceiver module 702 is configured to specifically perform the transmit and / or receive operations performed by the AP MLD (e.g., a current AP MLD or a target AP MLD) in one or more embodiments of Figure 2, Figure 3, or Figure 5, and supports the AP MLD (e.g., a current AP MLD or a target AP MLD) when performing another processing of the technology described herein. The processing module 701 may be configured to support the communication device 700 when performing the processing operations in the embodiments of the method described above, and to support the AP MLD (e.g., a current AP MLD or a target AP MLD) when performing another processing of the technology described herein.

[0222] In yet another example, if the communication device is used as a non-AP MLD or a chip used with a non-AP MLD, the communication device performs the steps performed by the non-AP MLD in the embodiments of the method described above. The transceiver module 702 is configured to specifically perform the transmit and / or receive operations performed by the non-AP MLD in one or more embodiments of Figure 2, Figure 3, or Figure 5, and supports the non-AP MLD, for example, when performing another processing of the technology described herein. The processing module 701 may be configured to support the communication device 700 when performing the processing operations in the embodiments of the method described above, for example, when supporting the non-AP MLD when performing another processing of the technology described herein.

[0223] In another example, if the communication device is used as a gateway device or a chip used in a gateway device, the communication device performs steps performed by the gateway device in embodiments of the method described above. The transceiver module 702 is configured to specifically perform transmit and / or receive operations performed by the gateway device in one or more embodiments of Figure 2, Figure 3, or Figure 5, and supports the gateway device, for example, when performing another processing of the technology described herein. The processing module 701 may be configured to support the communication device 700 when performing processing operations in embodiments of the method described above, for example, when performing another processing of the technology described herein.

[0224] Optionally, if the AP MLD (e.g., current AP MLD or target AP MLD), non-AP MLD, or gateway device is a chip, the processing module 701 may be one or more processors, the transceiver module 702 may be a transceiver, and the transceiver module 702 may be a transmit module and a receive module. The transmit module may be a transmitter, and the receive module may be a receiver. The transmit module and the receive module are integrated into a single component, for example, a transceiver. In these embodiments of the application, the processor and the transceiver may be coupled or similar. The connection method between the processor and the transceiver is not limited to these embodiments of the application. In the process performing the method described above, the process of transmitting information in the method described above may be understood as the process of outputting information by the processor. When outputting information, the processor outputs the information to the transceiver, and as a result the transceiver transmits the information. After the information has been output by the processor, further processing of the information may need to be performed on the information before the information arrives at the transceiver. Similarly, the process of receiving information in the method described above may be understood as the process of receiving input information by the processor. When a processor receives input information, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, other processing may need to be performed on the information before it is input to the processor.

[0225] The above description represents possible product forms of the communication device shown in Figure 7. It should be understood that any form of product having the functionality of the communication device shown in Figure 7 falls within the scope of protection of the embodiments of this application. Furthermore, it should be understood that the above description is merely an example, and the product forms of the communication device in these embodiments of this application are not limited thereto.

[0226] Figure 8 is a diagram of the structure of another communication device according to one embodiment of the present application. The communication device may be an AP MLD (e.g., a current AP MLD or a target AP MLD), a non-AP MLD, a gateway device, or a chip in an AP MLD, a chip in a non-AP MLD, or a chip in a gateway device. Figure 8 shows only the main components of the communication device. In addition to the processor 801 and the transceiver 802, the communication device may further include a memory 803 and an input / output device (not shown). The processor 801 is mainly configured to process communication protocols and communication data, control the entire communication device, execute software programs, and process data for the software programs. The memory 803 is mainly configured to store software programs and data. The transceiver 802 may include a control circuit and an antenna. The control circuit is mainly configured to perform conversions between baseband signals and radio frequency signals and to process radio frequency signals. The antenna is mainly configured to receive / transmit radio frequency signals in the form of electromagnetic waves. Input / output devices such as touchscreens, displays, or keyboards are primarily configured to receive data entered by the user and output data to the user.

[0227] After the communication device is powered on, the processor 801 can read the software program in memory 803, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 801 performs baseband processing on the data to be transmitted, and then outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal in electromagnetic wave form via the antenna. When the data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal via the antenna, converts the radio frequency signal back to a baseband signal, and outputs the baseband signal back to the processor 801. The processor 801 converts the baseband signal back to data and processes the data. In other implementations, the radio frequency circuit and antenna may be located independently of the processor that performs the baseband processing. For example, in a distributed scenario, the radio frequency circuit and antenna may be located remotely, independently of the communication device.

[0228] The processor 801, the transceiver 802, and the memory 803 may be connected via a communication bus.

[0229] For example, if the communication device is configured to perform a step, method, or function performed by the AP MLD (e.g., the current AP MLD or the target AP MLD) in the embodiment of the method described above, the processor 801 may be configured to perform another processing of the technology described herein, and the transceiver 802 may be configured to perform step 202 in Figure 2 and / or another processing of the technology described herein.

[0230] As another example, if the communication device is configured to perform steps, methods, or functions performed by the non-AP MLD in the embodiments of the method described above, the processor 801 may be configured to perform other processing of the technology described herein, and the transceiver 802 may be configured to perform step 205 in Figure 2 and / or other processing of the technology described herein.

[0231] As another example, if the communication device is configured to perform a step, method, or function performed by the gateway device in the embodiment of the method described above, the processor 801 may be configured to perform another processing of the technology described herein, and the transceiver 802 may be configured to perform step 206 in Figure 2 and / or another processing of the technology described herein.

[0232] In one implementation, the processor 801 may store instructions. These instructions may be computer programs. The computer programs are executed in the processor 801 to enable the communication device to perform the method described in the embodiments of the above-described method. The computer programs may be incorporated into the processor 801. In this case, the processor 801 may be implemented in hardware.

[0233] In one implementation, the communication device may include a circuit. The circuit may implement the transmit, receive, or communicate functions in the embodiments of the method described above. The processors and transceivers described in this application may be mounted on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processors and transceivers may be alternatively manufactured using various IC technologies, such as complementary metal oxide semiconductors (CMOS), n-metal oxide semiconductors (NMOS), positive-channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), and gallium arsenide (GaAs).

[0234] It will be understood that the communication device shown in this embodiment of the application may further include more components than those shown in Figure 8. This is not limited to this embodiment of the application. The aforementioned method performed by the processor and transceiver is merely an example. For specific steps performed by the processor and transceiver, please refer to the description of the embodiments of the method described above.

[0235] In another possible implementation, in the communication device shown in Figure 7, the processing module 701 may be one or more logic circuits, and the transceiver module 702 may be an input / output interface, or may be called a communication interface, interface circuit, interface, etc. Alternatively, the transceiver module 702 may be a transmit module and a receive module. The transmit module may be an output interface, and the receive module may be an input interface. The transmit module and the receive module are integrated into a single unit, for example, an input / output interface.

[0236] Figure 9 shows the structure of yet another communication device according to this application. As shown in Figure 9, the communication device shown in Figure 9 includes a logic circuit 901 and an interface 902. That is, the processing module 701 may be implemented using the logic circuit 901, and the transceiver module 702 may be implemented using the interface 902. The logic circuit 901 may be a chip, a processing circuit, an integrated circuit, a system on a chip (SoC), etc. The interface 902 may be a communication interface, an input / output interface, a pin, etc. For example, Figure 9 shows an example where the communication device is a chip, and the chip includes the logic circuit 901 and the interface 902. Optionally, the logic circuit and the interface may be further coupled to each other. The specific connection method between the logic circuit and the interface is not limited to this embodiment of this application.

[0237] For example, if a communication device is configured to perform a step, method, or function performed by the current AP MLD in an embodiment of the method described above, the logic circuit 901 is configured to determine that data exists in the current AP MLD's transmit buffer, the transmit buffer is used to buffer data for the current AP MLD and data for the non-AP MLD, the non-AP MLD triggers a temporary association with the target AP MLD, the interface 902 is configured to transmit all data in the transmit buffer to the non-AP MLD or the target AP MLD, and the target AP MLD is configured to transmit data from the current AP MLD to the non-AP MLD.

[0238] As another example, if the communication device is configured to perform a step, method, or function performed by a non-AP MLD in an embodiment of the method described above, the interface 902 is configured to receive all data from the transmit buffer of the current AP MLD, the transmit buffer being used to buffer data for the current AP MLD and data for the non-AP MLD, or to receive all data from the transmit buffer of the current AP MLD via a target AP MLD, the non-AP MLD triggering a temporary association with the target AP MLD.

[0239] As another example, if the communication device is configured to perform a step, method, or function performed by the target AP MLD in the embodiment of the method described above, the interface 902 is configured to receive all data from the transmit buffer of the current AP MLD, the transmit buffer is used to buffer data for the current AP MLD and data for the non-AP MLD, and the non-AP MLD is configured to receive, trigger a temporary association with the target AP MLD, and, if the temporary association between the target AP MLD and the non-AP MLD is activated, to transmit data from the current AP MLD to the non-AP MLD.

[0240] As another example, if the communication device is configured to implement steps, methods, or functions performed by the gateway device in the embodiments of the method described above, the interface 902 is configured to receive first information from the current AP MLD, the first information indicating that a non-AP MLD associated with the current AP MLD triggers a temporary association with a target AP MLD, and to transmit one or more first data separately to the current AP MLD and the target AP MLD.

[0241] It will be understood that the communication device shown in this embodiment of the present application may implement the method provided in this embodiment in hardware form, or the method provided in this embodiment in software form. This is not limited to this embodiment of the present application. For specific implementations of the embodiment shown in Figure 9, please refer to the embodiments described above. Details will not be repeated here.

[0242] One embodiment of this application further provides a communication device, which includes at least one processor and memory. The memory is configured to store computer programs or instructions. The at least one processor is configured to execute the computer programs or instructions in the memory, thereby performing one or more of the methods shown in the embodiments of Figures 2, 3, and 5.

[0243] One embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores computer instructions. When a computer instruction is executed, the computer can perform one or more of the methods shown in the embodiments of Figures 2, 3, and 5.

[0244] One embodiment of this application further provides a computer program product, which includes computer program code. When the computer program code is executed by a computer, the computer is able to perform one or more of the methods shown in the embodiments of Figures 2, 3, and 5.

[0245] One embodiment of this application further provides a chip, which includes at least one processor and an interface, the processor being configured to read and execute instructions stored in memory, and once the instructions are executed, the chip is capable of performing one or more of the methods shown in the embodiments of Figures 2, 3, and 5.

[0246] The aforementioned units described as separate parts may or may not be physically separate, and the parts presented as units may or may not be physical units, may be located in one location, or may be distributed across multiple network units. Some or all of the units may be selected based on actual requirements in order to achieve the objectives of the solutions of the embodiments of this application. Furthermore, the network element units of the embodiments of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit. The integrated unit may be implemented in hardware form or in the form of a software network element unit.

[0247] If the integrated unit is implemented in the form of a software network element unit and sold or used as an independent product, the integrated unit may be stored on a computer-readable storage medium. Based on such understanding, an essentially contributing portion of the technical solution of this application, or all or part of the technical solution, may be embodied in the form of a software product. The computer software product is stored on a storage medium and includes instructions for instructing a computer device (which may be a personal computer, terminal equipment, cloud server, network equipment, etc.) to perform all or part of the steps of the method in the embodiments of this application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, optical disk, etc. The foregoing description is merely a specific implementation of this application and is not intended to limit the scope of protection of this application. Any modifications or substitutions that are readily conceivable by a person skilled in the art within the scope of the technical scope disclosed in this application shall fall within the scope of protection of this application. Accordingly, the scope of protection of this application shall be subject to the scope of protection of the claims. [Explanation of symbols]

[0248] 700 Communication equipment 701 Processing Module 702 Transmitter / Receiver Module 703 Memory Module 801 Processor 802 Transmitter / Receiver 803 memory 901 Logic Circuits 902 Interface

Claims

1. A method of communication, A step of determining that data exists in the transmit buffer of the current access point multilink device, wherein the transmit buffer is used to buffer data from the current access point multilink device and data from a non-access point multilink device, and the non-access point multilink device triggers a temporary association with a target access point multilink device. A step of transmitting all data in the transmit buffer to the non-access point multilink device or the target access point multilink device by the current access point multilink device, wherein the target access point multilink device is configured to transmit data from the current access point multilink device to the non-access point multilink device. Methods that include...

2. The method according to claim 1, wherein if the current access point multilink device determines that the non-access point multilink device has triggered the temporary association with the target access point multilink device, the protocol predefined that data in the transmit buffer, starting from the window start position, is not cleared.

3. The method described above is If the current access point multilink device does not support the first capability, the current access point multilink device clears the successfully transmitted data in the transmit buffer, or If the current access point multilink device supports the first capability, the current access point multilink device holds the successfully transmitted data in the transmit buffer, starting from the window start position. It further includes, The method according to claim 1 or 2, wherein the first capability is the ability of the current access point multilink device to hold the successfully transmitted data in the transmit buffer, starting from the window start position, when the current access point multilink device determines that the non-access point multilink device has triggered the temporary association with the target access point multilink device.

4. The method described above is If the current access point multilink device supports the first capability and the current access point multilink device determines that the non-access point multilink device has triggered the temporary association with the target access point multilink device, the current access point multilink device may delete the block acknowledgment session information between the current access point multilink device and the non-access point multilink device, or If the current access point multilink device does not support the first capability and the current access point multilink device determines that the non-access point multilink device has triggered the temporary association with the target access point multilink device, the current access point multilink device maintains block acknowledgment session information between the current access point multilink device and the non-access point multilink device. The method according to claim 3, further comprising:

5. The method described above is The method according to any one of claims 1 to 4, further comprising the step of transmitting the block acknowledgment session information between the current access point multilink device and the non-access point multilink device to the target access point multilink device by the current access point multilink device.

6. The method described above is The method according to any one of claims 1 to 5, further comprising the step of transmitting first information to a non-access point multilink device by the current access point multilink device, wherein the first information indicates that the data in the transmit buffer has not been fully transmitted.

7. The method according to claim 6, wherein the first information is carried in a more data field of a first frame, the more data field of the first frame is set to 1, and the first frame is a data frame or a disassociation frame.

8. The method described above is The method according to any one of claims 1 to 7, further comprising the step of transmitting second information to the non-access point multilink device by the current access point multilink device, wherein the second information indicates that all data in the transmit buffer has been transmitted.

9. The method according to claim 8, wherein the second information is carried in a more data field of a second frame, the more data field of the second frame is set to 0, and the second frame is a data frame or a disassociation frame.

10. A method of communication, A step of receiving all data from the transmit buffer of the current access point multilink device by a non-access point multilink device, wherein the transmit buffer is used to buffer the data of the current access point multilink device and the data of the non-access point multilink device, or The non-access point multilink device receives all data from the transmit buffer of the current access point multilink device via the target access point multilink device. Includes, A method for the non-access point multilink device to trigger a temporary association with the target access point multilink device.

11. The method described above is The method according to claim 10, further comprising the step of receiving first information from the current access point multilink device by the non-access point multilink device, wherein the first information indicates that the data in the transmit buffer has not been fully transmitted.

12. The method according to claim 11, wherein the first information is carried in a more data field of a first frame, the more data field of the first frame is set to 1, and the first frame is a data frame or a disassociation frame.

13. The method described above is The method according to any one of claims 10 to 12, further comprising the step of receiving second information from the current access point multilink device by the non-access point multilink device, wherein the second information indicates that all data in the transmit buffer has been transmitted.

14. The method according to claim 13, wherein the second information is carried in a more data field of a second frame, the more data field of the second frame is set to 0, and the second frame is a data frame or a disassociation frame.

15. The method according to any one of claims 10 to 14, wherein the protocol predefined that when the non-access point multilink device triggers the temporary association with the target access point multilink device, at least one of the following is maintained: a key between the current access point multilink device and the non-access point multilink device, block acknowledgment session information between the current access point multilink device and the non-access point multilink device, a key between the target access point multilink device and the non-access point multilink device, or block acknowledgment session information between the target access point multilink device and the non-access point multilink device.

16. A method of communication, A step of receiving all data from the transmit buffer of the current access point multilink device by a target access point multilink device, wherein the transmit buffer is used to buffer data from the current access point multilink device and data from a non-access point multilink device, and the non-access point multilink device triggers a temporary association with the target access point multilink device. When the temporary association between the non-access point multilink device and the target access point multilink device is activated, the target access point multilink device transmits data from the current access point multilink device to the non-access point multilink device. Includes, method.

17. The method described above is The step further includes the target access point multilink device receiving block acknowledgment session information between the current access point multilink device and the non-access point multilink device from the current access point multilink device, The step of the target access point multilink device transmitting data from the current access point multilink device to the non-access point multilink device is: The method according to claim 16, further comprising the step of the target access point multilink device transmitting data from the current access point multilink device to the non-access point multilink device based on the block acknowledgment session information.

18. A communication device comprising a unit or module configured to perform the method described in any one of claims 1 to 17.

19. A communication device comprising at least one processor and memory, A communication device wherein the memory is configured to store computer programs or instructions, and the at least one processor is configured to execute the computer programs or instructions in the memory, thereby performing the method according to any one of claims 1 to 17.

20. A communication system comprising current access point multilink devices and non-access point multilink devices, The current access point multilink device is configured to perform the method described in any one of claims 1 to 9, A communication system in which the non-access point multilink device is configured to perform the method described in any one of claims 10 to 15.

21. A communication system comprising a current access point multilink device, a non-access point multilink device, and a target access point multilink device, The current access point multilink device is configured to perform the method described in any one of claims 1 to 9, The non-access point multilink device is configured to perform the method described in any one of claims 10 to 15, A communication system in which the target access point multilink device is configured to perform the method according to either claim 16 or 17.

22. A computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed, a computer is enabled to perform the method according to any one of claims 1 to 17.

23. A computer program product comprising computer program code, wherein when the computer program code is executed by a computer, the computer is enabled to perform the method according to any one of claims 1 to 17.

24. A chip comprising at least one processor and interface, wherein the processor is configured to read and execute instructions stored in memory, and when the instructions are executed, the chip is enabled to perform the method according to any one of claims 1 to 17.

Images