Communication method and apparatus
By not clearing the buffer data of the original access point when roaming and switching between non-access points in a wireless communication device, the packet loss problem during roaming is solved and communication reliability is improved.
Patent Information
- Application Number
- PCT/CN2024/091746
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-05-08
- Publication Date
- 2024-11-21
AI Technical Summary
In wireless communication devices, packet loss problems caused by link quality reduction during roaming by non-AP MLDs affect communication reliability.
When the non-access point triggers a tentative association through the original access point (AP MLD), the data in the sending buffer is not cleared, and all the data is sent to the target access point, ensuring the integrity of data transmission and reducing the roaming switching process lost packet in.
Improves communication reliability of non-access points during roaming, reduces packet loss problems, and ensures business continuity.
Smart Images

Figure CN2024091746_21112024_PF_FP_ABST
Abstract
Description
Communication method and device
[0001] This application claims priority to the Chinese patent application with application number 202310541312.2 filed with the State Intellectual Property Office of China on May 12, 2023, and priority to the Chinese patent application with the invention name “A Communication Method and Device”, all contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art
[0003] Currently, wireless communication devices can support multi-link communication, such as communicating on multiple links in different communication frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, etc.), or communicating on different channels in the same communication frequency band. Communication devices that support multi-link communication are referred to as multi-link devices (MLDs). Multi-link devices include access point (AP) MLDs and non-access point (non-AP) MLDs.
[0004] When a non-APMLD moves, link quality can deteriorate due to factors such as increasing distance between the non-APMLD and its associated AP MLD and / or the presence of obstructions. This can trigger roaming, where the non-APMLD roams to an AP MLD that provides a higher-quality link to meet service requirements. However, roaming can lead to packet loss, which impacts communication reliability.
[0005] Summary of the Invention
[0006] The present application provides a communication method and apparatus, which reduces the packet loss problem during non-APMLD roaming switching, thereby improving the communication reliability of non-APMLD during roaming.
[0007] In a first aspect, a communication method is provided, including: an original AP MLD determining that data exists in a send buffer of the original AP MLD, the send buffer being used to cache data of the original AP MLD and a non-AP MLD, the non-AP MLD triggering a tentative association with a target AP MLD; the original AP MLD sending all data in the send buffer to the non-AP MLD or the target AP MLD, the target AP MLD being used to send data from the original AP MLD to the non-AP MLD.
[0008] In the above embodiment, the non-AP MLD triggers a tentative association with the target AP MLD, indicating that the non-AP MLD has begun roaming handover with the target AP MLD. At this point, after the original AP MLD determines that there is data in its send buffer, it can send all the data in the send buffer to the non-AP MLD. Alternatively, it can send all the data in the send buffer to the target AP MLD, allowing the target AP MLD to forward the data from the original AP MLD to the non-AP MLD. This reduces packet loss during the non-AP MLD roaming handover process and improves communication reliability for the non-AP MLD during roaming.
[0009] In conjunction with the first aspect, in one possible implementation, the protocol (pre-)defines that, when the original AP MLD determines that the non-AP MLD has triggered a tentative association with the target AP MLD, data starting from the window start position (WinStart_O) in the original AP MLD's send buffer is not cleared, such as one or more items of pending data (i.e., data not sent by the original AP MLD to the non-AP MLD) and unsuccessfully sent data (i.e., data not successfully sent by the original AP MLD to the non-AP MLD). Alternatively, the protocol (pre-)defines that a sender (e.g., the original AP MLD) is not cleared from its send buffer data starting from the window start position, such as one or more items of pending data (i.e., data not sent by the sender) and unsuccessfully sent data (i.e., data not successfully sent by the sender).
[0010] In the above embodiment, this ensures that when the non-AP MLD triggers a tentative association with the target AP MLD, the data starting from the start position of the window in the sending buffer is not cleared.
[0011] In combination with the first aspect, in a possible implementation, the method further includes: when the original AP MLD does not support the first capability, the original AP MLD clears the successfully sent data in the sending buffer; when the original AP MLD supports the first capability, the original AP MLD retains the successfully sent data in the sending buffer starting from the start position of the window; wherein the first capability is the ability of the original AP MLD to still retain the successfully sent data in the sending buffer starting from the start position of the window when it determines that the non-AP MLD has triggered a tentative association with the target AP MLD.
[0012] In the above embodiment, when the original AP MLD does not support the first capability, the original AP MLD clears the successfully sent data in the send buffer. This indicates that when the non-AP MLD roams to the target AP MLD, it is necessary to migrate the block acknowledgment (BA) session information between the original AP MLD and the non-AP MLD, i.e., perform a BA session transfer. This can reduce or avoid service interruption during the non-AP MLD roaming handover process, thereby improving the communication reliability of the non-AP MLD during the roaming process. When the original AP MLD supports the first capability, the original AP MLD retains the successfully sent data in the send buffer starting from the start position of the window. This indicates that when the non-AP MLD roams to the target AP MLD, it is not necessary to perform a BA session transfer.
[0013] In combination with the first aspect, in a possible implementation, the method further includes: when the original AP MLD supports the first capability and the original AP MLD determines that the non-AP MLD triggers a tentative association with the target AP MLD, the original AP MLD deletes the BA session information between the original AP MLD and the non-AP MLD; when the original AP MLD does not support the first capability and the original AP MLD determines that the non-AP MLD triggers a tentative association with the target AP MLD, the original AP MLD retains the BA session information between the original AP MLD and the non-AP MLD.
[0014] In the above embodiment, when the original AP MLD supports the first capability and determines that the non-AP MLD has triggered a tentative association with the target AP MLD, the original AP MLD can delete the BA session information between the original AP MLD and the non-AP MLD, thereby avoiding BA session transfer. When the original AP MLD does not support the first capability and determines that the non-AP MLD has triggered a tentative association with the target AP MLD, the original AP MLD needs to retain the BA session information between the original AP MLD and the non-AP MLD. This ensures that the BA session can be transferred when the non-AP MLD roams to the target AP MLD, thereby avoiding packet loss caused by roaming.
[0015] With reference to the first aspect, in a possible implementation manner, the method further includes: the original AP MLD sending BA session information between the original AP MLD and the non-AP MLD to the target AP MLD.
[0016] In the above embodiment, the target AP MLD needs to use the BA session information of the original AP MLD and the non-AP MLD. This can reduce or avoid service interruption during the non-AP MLD roaming handover process, thereby improving the communication reliability of the non-AP MLD during the roaming process.
[0017] In combination with the first aspect, in a possible implementation, the method further includes: the original AP MLD sends first information to the non-AP MLD, where the first information is used to indicate that data in the sending buffer is not completely transmitted.
[0018] In the above embodiment, the original AP MLD may send the first information to the non-AP MLD to prevent the non-AP MLD from triggering downlink transmission with the target AP MLD and / or deleting the key with the original AP MLD when the original AP MLD has not completely transmitted data.
[0019] Among them, the secret keys involved in this application may include at least one of the following: pairwise transient key (PTK), group transient key (GTK), integrity group transient key (IGTK), beacon integrity group transient key (BIGTK).
[0020] In combination with the first aspect, in a 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.
[0021] In combination with the first aspect, in a possible implementation, the method further includes: the original AP MLD sends second information to the non-AP MLD or the target AP MLD, where the second information is used to indicate that all data in the sending buffer has been transmitted.
[0022] In the above embodiment, the non-AP MLD can be informed of whether the original AP MLD has completed data transmission.
[0023] In combination with the first aspect, in a possible implementation, the second information is carried in a moredata field of the second frame, the moredata field of the second frame is set to 0, and the second frame is a data frame or a disassociation frame.
[0024] In conjunction with the first aspect, in a possible implementation, the method further includes: the original AP MLD receiving third information from the target AP MLD, the third information being used to request sending all data in the buffer. In other words, the third information is used to request transferring all data in the buffer.
[0025] In conjunction with the first aspect, in one possible implementation, the method further includes: the original AP MLD receiving fourth information from the target AP MLD, where the fourth information is used to request BA session information between the original AP MLD and the non-AP MLD. In other words, the fourth information is used to request transfer of the BA session information between the original AP MLD and the non-AP MLD to the target AP MLD.
[0026] With reference to the first aspect, in a possible implementation, the method further includes: the original AP MLD obtains fifth information, where the fifth information is used to indicate that the target AP MLD supports BA session migration.
[0027] In conjunction with the first aspect, in one possible implementation, the method further includes: the original AP MLD sending sixth information to the non-AP MLD, where the sixth information is used to instruct the non-AP MLD to retain the BA session information between the original AP MLD and the non-AP MLD. Optionally, the sixth information may include a service identifier, which associates the BA session information between the original AP MLD and the non-AP MLD. The service identifier referred to in this application may also be referred to as a traffic identity (TID).
[0028] In the above embodiment, this ensures that the BA session can be transferred when the non-AP MLD roams to the target AP MLD, thereby avoiding packet loss caused by roaming. At the same time, when the sixth information includes the service identifier, the non-AP MLD can retain the BA session information associated with the service identifier.
[0029] In conjunction with the first aspect, in one possible implementation, the sixth information may further instruct the non-AP MLD to retain data in the non-AP MLD's receive buffer and / or the non-AP MLD's scoreboard. The receive buffer is used to cache data received by the non-AP MLD from the original AP MLD. The scoreboard is used to record data successfully received and / or unsuccessfully received by the non-AP MLD, such as data successfully received from the original AP MLD and data unsuccessfully received from the original AP MLD.
[0030] In the above embodiment, it is ensured that the data in the receiving buffer is not cleared when the non-AP MLD roams and switches to the target AP MLD.
[0031] With reference to the first aspect, in a possible implementation manner, the method further includes: the original AP MLD sending seventh information to the non-AP MLD, where the seventh information is used to indicate that the original AP MLD supports BA session migration.
[0032] In conjunction with the first aspect, in one possible implementation, the method further includes: the original AP MLD receiving eighth information from the non-AP MLD, where the eighth information is used to instruct the original AP MLD to retain BA session information between the original AP MLD and the non-AP MLD. Optionally, the eighth information may include a service identifier, where the service identifier associates the BA session information between the original AP MLD and the non-AP MLD.
[0033] In the above embodiment, this ensures that the BA session can be transferred when the non-AP MLD roams to the target AP MLD, thereby avoiding packet loss caused by roaming. At the same time, when the eighth information includes the service identifier, the non-AP MLD can retain the BA session information associated with the service identifier.
[0034] According to a second aspect, a communication method is provided, including: a non-AP MLD receiving all data from a send buffer of an original AP MLD, where the send buffer is used to cache data of the original AP MLD and the non-AP MLD; or, the non-AP MLD receiving all data from the send buffer of the original AP MLD through a target AP MLD; wherein the non-AP MLD triggers a tentative association with the target AP MLD.
[0035] In the above embodiment, the non-AP MLD triggers a tentative association with the target AP MLD, indicating that the non-AP MLD has begun roaming handover with the target AP MLD. At this point, the non-AP MLD receives all data from the send buffer of the original AP MLD, or the non-AP MLD receives all data from the send buffer of the original AP MLD through the target AP MLD. This reduces packet loss during the non-AP MLD roaming handover process and improves communication reliability during the non-AP MLD roaming process.
[0036] In combination with the second aspect, in a possible implementation, the method further includes: the non-AP MLD receiving first information from the original AP MLD, where the first information is used to indicate that data in the sending buffer is not completely transmitted.
[0037] In the above embodiment, the original AP MLD may send the first information to the non-AP MLD to prevent the non-AP MLD from triggering downlink transmission with the target AP MLD and / or deleting the key with the original AP MLD when the original AP MLD has not completely transmitted data.
[0038] In combination with the second aspect, in a possible implementation, the first information is carried in a moredata field of a first frame, the moredata field of the first frame is set to 1, and the first frame is a data frame or a disassociation frame.
[0039] In conjunction with the second aspect, in a possible implementation, the method further includes: the non-AP MLD receiving second information from the original AP MLD, where the second information is used to indicate that all data in the sending buffer has been transmitted.
[0040] In the above embodiment, the non-AP MLD can be informed of whether the original AP MLD has completed data transmission.
[0041] In combination with the second aspect, in a possible implementation, the second information is carried in a moredata field of the second frame, the moredata field of the second frame is set to 0, and the second frame is a data frame or a disassociation frame.
[0042] In combination with the second aspect, in one possible implementation, the protocol predefines that when a non-AP MLD triggers a tentative association with a target AP MLD, at least one of the following items is retained: the secret key between the original AP MLD and the non-AP MLD, the BA session information between the original AP MLD and the non-AP MLD, the secret key between the target AP MLD and the non-AP MLD, and the BA session information between the target AP MLD and the non-AP MLD.
[0043] In the above embodiment, it is ensured that the communication between the original AP MLD, the non-AP MLD, the target AP MLD, etc. is not disturbed during the non-APMLD roaming handover process.
[0044] In conjunction with the second aspect, in one possible implementation, the method further includes: the non-AP MLD sending ninth information to the target AP MLD, the ninth information being used to instruct the target AP MLD to obtain BA session information between the original AP MLD and the non-AP MLD. Optionally, the ninth information also includes a service identifier, which associates the BA session information between the original AP MLD and the non-AP MLD.
[0045] In the above embodiment, the target AP MLD needs to obtain the BA session information of the original AP MLD and the non-AP MLD, so that the BA session information of the original AP MLD and the non-AP MLD can be used. This can reduce or avoid service interruption during the non-AP MLD roaming handover process, thereby improving the communication reliability of the non-AP MLD during the roaming process. It can also enable the target AP MLD to know which BA session information needs to be transferred from the original AP MLD to the target AP MLD.
[0046] In conjunction with the second aspect, in one possible implementation, the method further includes: the non-AP MLD receiving sixth information from the original AP MLD, where the sixth information is used to instruct the non-AP MLD to retain BA session information between the original AP MLD and the non-AP MLD. Optionally, the sixth information may include a service identifier, where the service identifier associates the BA session information between the original AP MLD and the non-AP MLD.
[0047] In the above embodiment, this ensures that the BA session can be transferred when the non-AP MLD roams to the target AP MLD, thereby avoiding packet loss caused by roaming. At the same time, when the sixth information includes the service identifier, the non-AP MLD can retain the BA session information associated with the service identifier.
[0048] In conjunction with the second aspect, in one possible implementation, the sixth information may further instruct the non-AP MLD to retain data in a non-AP MLD receive buffer and / or a non-AP MLD scoreboard. The receive buffer is used to cache data received by the non-AP MLD from the original AP MLD.
[0049] In the above embodiment, it is ensured that the data in the receiving buffer is not cleared when the non-AP MLD roams and switches to the target AP MLD.
[0050] With reference to the second aspect, in a possible implementation manner, the method further includes: the non-AP MLD receiving seventh information from the original AP MLD, where the seventh information is used to indicate that the original AP MLD supports BA session migration.
[0051] In conjunction with the second aspect, in one possible implementation, the method further includes: the non-AP MLD sending eighth information to the original AP MLD, where the eighth information is used to instruct the original AP MLD to retain BA session information between the original AP MLD and the non-AP MLD. Optionally, the eighth information may include a service identifier, where the service identifier associates the BA session information between the original AP MLD and the non-AP MLD.
[0052] In the above embodiment, this ensures that the BA session can be transferred when the non-AP MLD roams to the target AP MLD, thereby avoiding packet loss caused by roaming. At the same time, when the eighth information includes the service identifier, the non-AP MLD can retain the BA session information associated with the service identifier.
[0053] According to a third aspect, a communication method is provided, including: a target AP MLD receiving all data from a send buffer of an original AP MLD, where the send buffer is used to cache data of the original AP MLD and a non-AP MLD, and the non-AP MLD triggers a tentative association with the target AP MLD; when the tentative association between the target AP MLD and the non-AP MLD is activated, the target AP MLD sends the data from the original AP MLD to the non-AP MLD.
[0054] In the above embodiment, the non-AP MLD triggers a tentative association with the target AP MLD, indicating that the non-AP MLD begins roaming handover with the target AP MLD. At this point, the target AP MLD sends data from the original AP MLD to the non-AP MLD. This reduces packet loss during the non-AP MLD roaming handover process and improves communication reliability during the non-AP MLD roaming process.
[0055] In combination with the third aspect, in a possible implementation, the method further includes: the target AP MLD receives BA session information of the original AP MLD and the non-AP MLD from the original AP MLD; the target AP MLD sends data from the original AP MLD to the non-AP MLD, including: the target AP MLD sends the data from the original AP MLD to the non-AP MLD based on the BA session information.
[0056] In the above embodiment, it can be shown that the target AP MLD uses the BA session information of the original AP MLD and non-AP MLD, which can reduce or avoid the service interruption problem during the non-APMLD roaming switching process, and further improve the communication reliability of the non-APMLD during the roaming process.
[0057] In combination with the third aspect, in one possible implementation, the method further includes: the target AP MLD receiving address information of the original AP MLD from the non-AP MLD; when the non-AP MLD associated with the original AP MLD tentatively associates with the target AP MLD, the target AP MLD sends third information to the original AP MLD based on the address information of the original AP MLD, where the third information is used to request sending all data in the buffer.
[0058] In combination with the third aspect, in a possible implementation, the method further includes: the target AP MLD sending fourth information to the original AP MLD according to the address information of the original AP MLD, where the fourth information is used to request BA session information between the original AP MLD and the non-AP MLD.
[0059] In combination with the third aspect, in a possible implementation, the method further includes: the target AP MLD broadcasting fifth information, where the fifth information is used to indicate that the target AP MLD supports BA session migration.
[0060] In combination with the third aspect, in a possible implementation, the method further includes: the target AP MLD receiving ninth information from the non-AP MLD, where the ninth information is used to instruct the target AP MLD to obtain BA session information between the original AP MLD and the non-AP MLD.
[0061] In the above embodiment, the target AP MLD needs to obtain the BA session information of the original AP MLD and the non-AP MLD, so that the BA session information of the original AP MLD and the non-AP MLD can be used. This can reduce or avoid service interruption during the non-AP MLD roaming handover process, thereby improving the communication reliability of the non-AP MLD during the roaming process. It can also enable the target AP MLD to know which BA session information needs to be transferred from the original AP MLD to the target AP MLD.
[0062] In conjunction with the third aspect, in one possible implementation, the ninth information further includes a service identifier corresponding to the data in the send buffer, and the ninth information is further used to instruct the target AP MLD to obtain BA session information between the original AP MLD and the non-AP MLD. Optionally, the ninth information further includes a service identifier, and the service identifier is associated with the BA session information between the original AP MLD and the non-AP MLD.
[0063] In the above embodiment, the target AP MLD needs to obtain the BA session information of the original AP MLD and the non-AP MLD, so that the BA session information of the original AP MLD and the non-AP MLD can be used. This can reduce or avoid service interruption during the non-AP MLD roaming handover process, thereby improving the communication reliability of the non-AP MLD during the roaming process. It can also enable the target AP MLD to know which BA session information needs to be transferred from the original AP MLD to the target AP MLD.
[0064] In a fourth aspect, a communication method is provided, including: a gateway device receives first information from an original AP MLD, the first information indicating that a non-AP MLD associated with the original AP MLD triggers a tentative association with a target AP MLD; the gateway device sends one or more first data to the original AP MLD and the target AP MLD respectively.
[0065] In the above embodiment, the gateway device can learn from the original AP MLD that the non-AP MLD associated with the original AP MLD has triggered a tentative association with the target AP MLD, indicating that the non-AP MLD has begun roaming handover with the target AP MLD. At this point, the gateway device can send the same data to both the original AP MLD and the target AP MLD. This allows the original AP MLD to inform the target AP MLD which data to send to the non-AP MLD when the non-AP MLD switches data from the original AP MLD to the target AP MLD. This allows the target AP MLD to send data that the original AP MLD failed to send to the non-AP MLD, even if the original AP MLD does not migrate data to the target AP MLD. This avoids delays caused by data migration, reduces packet loss during the non-AP MLD roaming handover process, and improves communication reliability for the non-AP MLD during roaming.
[0066] In combination with the fourth aspect, in a possible implementation, the method further includes: the gateway device sending one or more numbers corresponding to the first data to the original AP MLD and the target AP MLD respectively.
[0067] In combination with the fourth aspect, in a possible implementation, the method also includes: the gateway device receives the data aggregation capability from the target AP MLD; the gateway device receives the data aggregation capability from the original AP MLD; the gateway device generates one or more first data based on the data aggregation capability of the target AP MLD and the data aggregation capability of the original AP MLD.
[0068] In the above embodiment, the first data is generated according to the data aggregation capability of the target AP MLD and the data aggregation capability of the original AP MLD, which can reduce the number of data transmissions and thus improve the data transmission rate.
[0069] In a fifth aspect, a communication method is provided, including: a target AP MLD receiving one or more first data from a gateway device, where the one or more first data are data sent when the gateway device determines that a non-AP MLD associated with an original AP MLD triggers a tentative association with the target AP MLD; the target AP MLD receiving second information from the original AP MLD, where the second information is used by the target AP MLD to determine data to be sent from the one or more first data; and when the tentative association between the target AP MLD and the non-AP MLD is activated, the target AP MLD sends the data to be sent to the non-AP MLD.
[0070] In the above embodiment, the gateway device can learn from the original AP MLD that the non-AP MLD associated with the original AP MLD has triggered a tentative association with the target AP MLD, indicating that the non-AP MLD has begun roaming handover with the target AP MLD. At this point, the gateway device can send the same data to both the original AP MLD and the target AP MLD. This allows the original AP MLD to inform the target AP MLD which data to send to the non-AP MLD when the non-AP MLD switches data from the original AP MLD to the target AP MLD. This allows the target AP MLD to send data that the original AP MLD failed to send to the non-AP MLD, even if the original AP MLD does not migrate data to the target AP MLD. This avoids delays caused by data migration, reduces packet loss during the non-AP MLD roaming handover process, and improves communication reliability for the non-AP MLD during roaming.
[0071] In combination with the fifth aspect, in a possible implementation, the second information includes the sending status corresponding to one or more first data, the sending status includes success or failure, and the data to be sent includes one or more first data whose sending status is failure.
[0072] In combination with the fifth aspect, in a possible implementation, the second information also includes the retransmission status corresponding to one or more first data, the retransmission status includes retransmission success or retransmission failure, and the data to be sent also includes one or more first data whose retransmission status is retransmission failure.
[0073] In combination with the fifth aspect, in a possible implementation, the second information is used to indicate a starting number corresponding to the data to be sent, and the data to be sent is data with a number greater than or equal to the starting number in one or more first data.
[0074] In combination with the fifth aspect, in a possible implementation, the method further includes: the target AP MLD receives a number corresponding to one or more first data from a gateway device.
[0075] In combination with the fifth aspect, in a possible implementation, the method further includes: the target AP MLD sending the data aggregation capability of the target AP MLD to the gateway device.
[0076] In a sixth aspect, a communication method is provided, including: an original AP MLD receives one or more first data from a gateway device, where the one or more first data are data sent when the gateway device determines that a non-AP MLD associated with the original AP MLD triggers a tentative association with a target AP MLD; the original AP MLD sends second information to the target AP MLD, where the second information is used by the target AP MLD to determine data to be sent from the one or more first data.
[0077] In the above embodiment, the gateway device can learn from the original AP MLD that the non-AP MLD associated with the original AP MLD has triggered a tentative association with the target AP MLD, indicating that the non-AP MLD has begun roaming handover with the target AP MLD. At this point, the gateway device can send the same data to both the original AP MLD and the target AP MLD. This allows the original AP MLD to inform the target AP MLD which data to send to the non-AP MLD when the non-AP MLD switches data from the original AP MLD to the target AP MLD. This allows the target AP MLD to send data that the original AP MLD failed to send to the non-AP MLD, even if the original AP MLD does not migrate data to the target AP MLD. This avoids delays caused by data migration, reduces packet loss during the non-AP MLD roaming handover process, and improves communication reliability for the non-AP MLD during roaming.
[0078] In combination with the sixth aspect, in a possible implementation, the second information includes a sending status corresponding to one or more first data, the sending status includes success or failure, and the data to be sent includes one or more first data whose sending status is failure.
[0079] In combination with the sixth aspect, in a possible implementation, the second information also includes the retransmission status corresponding to one or more first data, the retransmission status includes retransmission success or retransmission failure, and the data to be sent also includes one or more first data whose retransmission status is retransmission failure.
[0080] In combination with the sixth aspect, in a possible implementation, the second information is used to indicate a starting number corresponding to the data to be sent, and the data to be sent is data in one or more first data whose number is greater than or equal to the starting number.
[0081] In combination with the sixth aspect, in a possible implementation, the method further includes: the target AP MLD receives a number corresponding to one or more first data from a gateway device.
[0082] With reference to the sixth aspect, in a possible implementation manner, the method further includes: the target AP MLD sending the data aggregation capability of the target AP MLD to the gateway device.
[0083] In a seventh aspect, a communication device is provided, comprising a unit or module for implementing the method as described in any one of the first to sixth aspects.
[0084] In an eighth aspect, a communication device is provided, comprising at least one processor and a memory; wherein the memory is used to store computer programs or instructions; and at least one processor is used to execute the computer programs or instructions in the memory, so that any one of the methods described in any one of the first to sixth aspects is executed.
[0085] In a ninth aspect, a communication system is provided, comprising an original access point multi-link device and a non-access point multi-link device; the original access point multi-link device is configured to execute the method as described in any one of the first aspects; and the non-access point multi-link device is configured to execute the method as described in any one of the second aspects.
[0086] In a tenth aspect, a communication system is provided, comprising an original access point multi-link device, a non-access point multi-link device, and a target access point multi-link device; the original access point multi-link device is configured to execute the method described in any one of the first aspects; the non-access point multi-link device is configured to execute the method described in any one of the second aspects; and the target access point multi-link device is configured to execute the method described in any one of the third aspects.
[0087] In the eleventh aspect, a communication system is provided, the communication system including a gateway device, an original access point multi-link device, a non-access point multi-link device and a target access point multi-link device; the gateway device is used to execute the method as described in any one of the fourth aspects; the target access point multi-link device is used to execute the method as described in any one of the fifth aspects; the original access point multi-link device is used to execute the method as described in any one of the sixth aspects.
[0088] In a twelfth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed, the computer executes the method as described in any one of the first to sixth aspects.
[0089] In a thirteenth aspect, a computer program product is provided, the computer program product comprising: a computer program code, and when the computer program code is executed by a computer, the computer executes the method as described in any one of the first to sixth aspects.
[0090] In the fourteenth aspect, a chip is provided, which includes at least one processor and an interface, the processor is used to read and execute instructions stored in a memory, and when the instructions are executed, the chip executes the method described in any one of the first to sixth aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0091] FIG1 is a basic architecture of a communication system provided in an embodiment of the present application;
[0092] FIG2 is a flow chart of a communication method provided in an embodiment of the present application;
[0093] FIG3 is a flow chart of another communication method provided in an embodiment of the present application;
[0094] FIG4 is a schematic diagram of a queue to be sent provided in an embodiment of the present application;
[0095] FIG5 is a flow chart of another communication method provided in an embodiment of the present application;
[0096] FIG6 is a schematic diagram of the numbering and sequence number of first data provided in an embodiment of the present application;
[0097] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0098] FIG8 is a schematic structural diagram of another communication device provided in an embodiment of the present application;
[0099] FIG9 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0100] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the embodiments of the present application, the terms "system" and "network" can be used interchangeably. Unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural. In addition, in the description of this application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be one or more. In addition, to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish between network elements and identical or similar items with substantially the same functions. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and terms such as "first" and "second" do not necessarily limit differences.
[0101] References to "one embodiment" or "some embodiments" in the embodiments of the present application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.
[0102] The following specific implementation methods further describe in detail the objectives, technical solutions and beneficial effects of the present application. It should be understood that the following are only specific implementation methods of the present application and are not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application.
[0103] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
[0104] First, the communication scenarios to which the embodiments of the present application are applicable are introduced. It should be understood that the embodiments of the present application can be applicable to wireless local area network (WLAN) scenarios, and can be applicable to IEEE 802.11 system standards, such as 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, or their successors, such as 802.11be or later generations. For example, the communication method provided by the embodiments of the present application can be applied to MLD roaming scenarios in wireless communication systems, such as scenarios where a non-AP MLD roams between at least two AP MLDs, or scenarios where a non-AP MLD switches from a basic service set (BSS) in the same extended service set (ESS) to another BSS. Alternatively, the embodiments of the present application can also be applied to wireless local area network systems such as Internet of Things (IoT) networks or Vehicle to X (V2X) networks. Of course, the embodiments of the present application can also be applied to other possible communication systems, such as long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), world-wide interoperability for microwave access (WiMAX) communication system, and future 6G communication system.
[0105] WLAN evolved from the 802.11a / g standard to 802.11n, 802.11ac, 802.11ax, and the currently under discussion 802.11be and Wi-Fi 8. 802.11n is also known as high throughput (HT); 802.11ac is also known as very high throughput (VHT); 802.11ax is also known as high efficiency (HE) or Wi-Fi 6; 802.11be is also known as extremely high throughput (EHT) or Wi-Fi 7. Standards prior to HT, such as 802.11a / b / g, are collectively referred to as non-HT.
[0106] The following uses the scenario in which the embodiment of the present application is applicable to WLAN as an example to introduce the basic architecture of the communication system to which the embodiment of the present application is applicable.
[0107] Refer to Figure 1, which shows the basic architecture of a communication system provided in an embodiment of the present application.
[0108] FIG1 includes AP MLD1, AP MLD2, and non-AP MLD. AP MLD1 and AP MLD2 each include at least one AP (FIG1 illustrates AP MLD1 includes AP1 and AP2, and AP MLD2 includes AP3 and AP4). A non-AP MLD may include at least one STA (FIG1 illustrates non-AP MLD includes STA1 and STA2). AP MLD1 can communicate with AP MLD2 and non-AP MLD, respectively, and AP MLD2 can communicate with non-AP MLD. That is, during roaming from AP MLD1 to AP MLD2, the non-AP MLD can communicate with AP MLD1 via a link operated by some STAs in the non-AP MLD (e.g., STA1), and the non-AP MLD can communicate with AP MLD2 via a link operated by another STA in the non-AP MLD (e.g., STA2). Optionally, FIG1 may also include a gateway device and a server. For example, a server can send downlink data to a gateway device, and the gateway device can send the downlink data to AP MLD1 and / or AP MLD2. Another example is that AP MLD1 and / or AP MLD2 can send uplink data from a non-AP MLD to the gateway device, and the gateway device can send the uplink data to the server. Furthermore, AP MLD1 and AP MLD2 are referred to as the source AP MLD and target AP MLD, respectively.
[0109] It should be noted that FIG1 is only an example and should not be considered as a specific limitation of the present application.
[0110] 1. STA
[0111] The STA involved in the embodiments of the present application may be a STA applicable to the IEEE 802.11 system standard, and may be various user terminals, user devices, access devices, subscriber stations, subscriber units, mobile stations, user agents, user equipment, or other names with wireless communication capabilities. Among them, user terminals may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities, as well as various forms of user equipment (UE), mobile stations (MS), terminals, terminal equipment, portable communication devices, handheld devices, portable computing devices, entertainment devices, gaming devices or systems, global positioning system devices, or any other suitable devices configured to communicate over a wireless medium. For example, a STA may be a router, a switch, a bridge, etc. Here, for the convenience of description, the above-mentioned devices are collectively referred to as stations or STAs.
[0112] Optionally, the STA may be a terminal product that supports the media access control (MAC) and physical layer (PHY) of the 802.11 system standard, such as a mobile phone, a notebook computer, etc.
[0113] 2. AP
[0114] The AP involved in the embodiments of the present application may be an AP applicable to the IEEE 802.11 system standard, and may be a device deployed in a wireless communication network to provide wireless communication functions for its associated STAs. The AP may serve as the hub of the communication system and is typically a network-side product that supports the MAC and PHY of the 802.11 system standard, 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. Here, for the convenience of description, the above-mentioned devices are collectively referred to as APs.
[0115] 3. MLD
[0116] An MLD is a wireless communication device that supports parallel transmission over multiple links. It can also be referred to as a multi-band device. Compared to devices that only support transmission over a single link, an MLD has higher transmission efficiency and higher throughput. The frequency bands in which an MLD operates may include one or more of the following: sub-1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz. An MLD includes one or more affiliated STAs (STAs). An affiliated STA is a logical station that can operate on a link. An affiliated station can be an AP or a non-AP STA. For ease of description, this application refers to an MLD whose affiliated station is an AP as a multi-link AP, a multi-link AP device, or an AP MLD, and an MLD whose affiliated station is a non-AP STA as a multi-link STA, a multi-link STA device, a STA MLD, or a non-AP MLD. It should be understood that each station in an MLD can operate on a link, but multiple stations are allowed to operate on the same link.
[0117] 4. Gateway Device
[0118] The gateway device involved in this application can transmit downlink data from the server to the original AP MLD and / or the target AP MLD, and can also transmit uplink data from the non-AP MLD to the server.
[0119] 5. Server
[0120] The server involved in this application can send downlink data to the gateway device and can also receive uplink data from the gateway device. The number of servers can be one or more.
[0121] The server mentioned in each embodiment of the present application can be a single server or a server cluster consisting of multiple servers, which is not limited here.
[0122] The communication method provided in the embodiment of the present application is described in detail below with reference to FIG1 .
[0123] For ease of understanding, the following examples provide some explanations of concepts related to the embodiments of the present application for reference.
[0124] 1. Send buffer
[0125] The sending buffer of the AP MLD (such as the original AP MLD or the target AP MLD) can be used to cache AP MLD and non-AP MLD data.
[0126] The data mentioned in this application may be a medium access control (MAC) service data unit (MSDU) or an aggregation MSDU (A-MSDU). An A-MSDU may include one or more MSDUs.
[0127] In this application, the protocol (pre-)defines that, when the original AP MLD determines that a non-AP MLD has triggered a tentative association with a target AP MLD, it does not clear or does not allow the clearing of data starting from the window start position in the original AP MLD's send buffer, such as one or more items of pending data (i.e., data not sent by the original AP MLD to the non-AP MLD) and unsuccessfully sent data (i.e., data not successfully sent by the original AP MLD to the non-AP MLD). Optionally, the protocol may also (pre-)define that, when the original AP MLD determines that a non-AP MLD has triggered a tentative association with a target AP MLD, it is allowed to clear one or more items of pending data and unsuccessfully sent data before the window start position in the send buffer. Optionally, this can also be understood as the protocol (pre-)defining that a sender (e.g., the original AP MLD) does not clear data starting from the window start position in its send buffer, such as one or more items of pending data and unsuccessfully sent data (i.e., data not successfully sent by the sender). Of course, the protocol may also (pre)define that the sending end is allowed to clear one or more items of the data to be sent and the data not successfully sent before the start position of the window in the sending buffer.
[0128] Optionally, the original AP MLD can determine that the non-AP MLD has triggered a tentative association with the target AP MLD by receiving first indication information from the non-AP MLD. That is, the first indication information can be used to indicate that the non-AP MLD has triggered a tentative association with the target AP MLD. The first indication information can, for example, 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 also include other fields, which are not limited in this application.
[0129] In this application, "a non-AP MLD triggering a tentative association with a target AP MLD" can be understood as at least one of the following: the non-AP MLD preparing for roaming handover to the target AP MLD, the non-AP MLD initiating roaming handover with the target AP MLD, etc. The following example uses the non-AP MLD triggering a tentative association with the target AP MLD as an example. Furthermore, the tentative association in this application can be replaced with tentative reassociation.
[0130] Optionally, the non-AP MLD triggers a tentative association with the target AP MLD, which can be understood as follows: when the status of some links between the original AP MLD and the non-AP MLD is disconnected (or disabled), the first STA in the non-AP MLD sends a multi-link association request frame to the target AP MLD, and the multi-link association request frame is used to request the target AP MLD to perform a multi-link tentative association with the non-AP MLD. This application does not limit the specific process of the target AP MLD and the non-AP MLD performing a tentative association. Among them, the link status between the first STA and the original AP MLD is disconnected (or disabled), and the link status between the first STA and the target AP MLD is connected (or enabled), but the tentative association between the target AP MLD and the non-AP MLD is not activated, that is, the gateway device can still deliver data sent to the non-AP MLD to the original AP MLD. The link status between the second STA of the non-AP MLD and the original AP MLD is connected (or enabled). Optionally, the number of second STAs can be one or more. Therefore, the original AP MLD can communicate with the non-AP MLD through the link where the second STA works. In general, the non-AP MLD is associated with the original AP MLD and tentatively associated with the target AP MLD, but the tentative association between the target AP MLD and the non-AP MLD is not activated.
[0131] 2. BA session information
[0132] The BA session information involved in this application is used to establish a BA session, and the specific process of establishing a BA session is not limited here.
[0133] The BA session information involved in this application may include at least one of the following: a service identifier, a sequence number (SN) assigned to each data item, a confirmation policy, whether data aggregation is allowed, a window starting position of a send buffer of an AP MLD (such as an original AP MLD or a target AP MLD), a window size (WinSize_O) of the send buffer, a send status (including success or failure) of each data item in the window, a number of retransmissions of each data item in the window, a window starting position (WinStart_R) of a scoreboard of a non-AP MLD, a window size of the scoreboard, a window starting position (WinStart_B) of a receive reordering buffer of a non-AP MLD, and a window size of the receive reordering buffer. The scoreboard is used to record data successfully received and / or unsuccessfully received by the non-AP MLD, such as data successfully received from an AP MLD (such as the original AP MLD or the target AP MLD) and data unsuccessfully received from an AP MLD (such as the original AP MLD or the target AP MLD). The receive reordering buffer is used by the non-AP MLD to cache data from an AP MLD (such as the original AP MLD or the target AP MLD). The service identifier is also called a TID. For details on the various parameters included in BA session information, please refer to IEEE 802.11 and are not detailed here.
[0134] The present application may divide the BA session information into two types: one is the BA session information between the original AP MLD and the non-AP MLD, and the other is the BA session information between the target AP MLD and the non-AP MLD.
[0135] The present application provides the embodiments shown in Figures 2, 3, or 8 to solve the packet loss problem during non-APMLD roaming handover.
[0136] As shown in FIG2 , a communication method is provided in an embodiment of the present application, which includes but is not limited to the following steps:
[0137] 201. The original AP MLD determines that data exists in a sending buffer of the original AP MLD. The sending buffer is used to cache data of the original AP MLD and a non-AP MLD. The non-AP MLD triggers a tentative association with a target AP MLD.
[0138] In one possible implementation, step 201 can be understood as: the original AP MLD determines that data exists in the send buffer starting from the window start position. For example, data exists, such as one or more of data to be sent (i.e., data that the original AP MLD has not sent to the non-AP MLD) and data that has not been successfully sent (i.e., data that the original AP MLD has not successfully sent to the non-AP MLD). Optionally, the send buffer may also contain successfully sent data starting from the window start position (i.e., data that the original AP MLD has successfully sent to the non-AP MLD). For example, if the protocol (pre-)defines that the original AP MLD determines that the non-AP MLD has triggered a tentative association with the target AP MLD, it is not allowed to clear the successfully sent data in the send buffer starting from the window start position. Optionally, the protocol may also (pre-)define that the original AP MLD determines that the non-AP MLD has triggered a tentative association with the target AP MLD, it is allowed to clear the successfully sent data before the window start position in the send buffer. For another example, the protocol (pre-)defines that the sender (e.g., the original AP MLD, etc.) does not clear the successfully sent data in its send buffer starting from the window start position. Optionally, the protocol may also (pre)define that the sending end is allowed to clear the successfully sent data before the start position of the window in the sending buffer.
[0139] 202. The original AP MLD sends all data in the send buffer to the non-AP MLD.
[0140] Correspondingly, the non-AP MLD receives all the data in the send buffer of the original AP MLD.
[0141] In one possible implementation, step 202 can be understood as: the original AP MLD sends all data in the send buffer to the non-AP MLD based on the BA session information between the original AP MLD and the non-AP MLD. Optionally, the original AP MLD can send all data in the send buffer to the non-AP MLD in one or more transmissions. For example, the original AP MLD can send a data frame to the non-AP MLD based on the BA session information, and the data frame can include all the data. For another example, the original AP MLD can send multiple data frames to the non-AP MLD based on the BA session information, and one of the multiple data frames can include one or more data items from the total data. This application does not limit the frame structure of the data frame.
[0142] Optionally, the original AP MLD sends all data in the send buffer to the non-AP MLD based on the BA session information. This can also be understood as: the original AP MLD sends all data in the send buffer to the non-AP MLD over the BA session between the original AP MLD and the non-AP MLD.
[0143] In one possible implementation, all data in the send buffer of the original AP MLD includes one or more items of data to be sent and unsuccessfully sent data in the send buffer starting from the start position of the window. That is, when the original AP MLD determines that one or more items of data to be sent and unsuccessfully sent data exist in the send buffer starting from the start position of the window, all data in the send buffer includes one or more items of the data to be sent and the unsuccessfully sent data. Optionally, all data in the send buffer may also include data that has been successfully sent in the send buffer starting from the start position of the window. That is, when the original AP MLD determines that data that has been successfully sent exists in the send buffer starting from the start position of the window, all data in the send buffer may also include the successfully sent data.
[0144] Optionally, the method may further include step 203 of method 1 in FIG. 2 ; or, the method may further include step 204 and step 205 of method 2 in FIG. 2 .
[0145] Method 1:
[0146] 203. The target AP MLD receives second information from the original AP MLD, where the second information is used to indicate that all data in the sending buffer has been transmitted.
[0147] Correspondingly, the original AP MLD sends the second information to the target AP MLD.
[0148] Optionally, when the target AP MLD receives the second information from the original AP MLD, the second information is used to indicate that all data in the sending buffer has been transmitted. This can also be understood as: the second information is used to indicate that the target AP MLD is allowed to send downlink data.
[0149] Method 2:
[0150] 204. The non-AP MLD receives second information from the original AP MLD, where the second information is used to indicate that all data in the sending buffer has been transmitted.
[0151] Correspondingly, the original AP MLD sends the second information to the non-AP MLD.
[0152] In one possible implementation, when the non-AP MLD receives the second information from the original AP MLD, the second information may be carried in the moredata field of the second frame, the moredata field of the second frame is set to 0, and the second frame is a data frame or a disassociation frame. This application does not limit the frame structure of the disassociation frame.
[0153] Optionally, the second frame is the last data frame sent, and the second frame also includes the remaining data in the send buffer starting from the start of the window. For example, if the original AP MLD can send all the data in the send buffer to the non-AP MLD in one transmission (i.e., the original AP MLD sends a data frame to the non-AP MLD, and the data frame includes all the data), the remaining data here refers to all the data. For another example, if the original AP MLD can send all the data in the send buffer to the non-AP MLD in multiple transmissions (i.e., the original AP MLD can send multiple data frames to the non-AP MLD, and the multiple data frames include the last transmitted data frame as well as other data frames), the remaining data here refers to one or more data in the total data, excluding data carried by other data frames (the data carried by other data frames refers to one or more data in the send buffer starting from the start of the window). Optionally, the MoreData field of the other data frames can be set to 1, indicating that the data in the send buffer has not been fully transmitted.
[0154] 205. The target AP MLD receives the tenth information from the non-AP MLD. The tenth information is used to indicate that the target AP MLD is allowed to send downlink data.
[0155] Correspondingly, the non-AP MLD sends the tenth information to the target AP MLD.
[0156] Optionally, the method may further include step 206 .
[0157] 206. When the gateway device determines that the non-AP MLD associated with the original AP MLD triggers a tentative association with the target AP MLD, the gateway device sends one or more data to the target AP MLD.
[0158] Correspondingly, the target AP MLD receives one or more data from the gateway device.
[0159] In one possible implementation, before step 206, the method may further include: the gateway device receiving eleventh information from the non-AP MLD via the target AP MLD, where the eleventh information includes address information of the non-AP MLD, such as a MAC address. Because the address information of the non-AP MLD is sent to the gateway device via the target AP MLD, the gateway device can determine that the non-AP MLD associated with the original AP MLD has triggered a tentative association with the target AP MLD.
[0160] Optionally, when the non-AP MLD receives the second information from the original AP MLD, the eleventh information can also be used to instruct the first STA in the non-AP MLD to enter the energy-saving mode, and the first STA tentatively associates with the access point in the target AP MLD. This allows the target AP MLD to wait for the first STA of the non-AP MLD to trigger before sending downlink data. In addition, in this case, the tenth information in step 205 is used to indicate that the target AP MLD is allowed to send downlink data, which can be understood as: the tenth information is used to instruct the first STA to switch from the energy-saving mode to the active mode. Optionally, the tenth information can be carried in a data frame, a power saving polling (PS-POLL) frame, or a newly defined protected management frame (Protect Management Frame).
[0161] In a possible implementation, the eleventh information may be carried in a power management (power management) field of a data frame, and the power management field may be set to 1.
[0162] There is no required order in which step 206 is performed compared to steps 201 through 203. For example, step 206 can be performed before or after any one of steps 201 through 203. Alternatively, step 203 can be performed simultaneously with any one of steps 201 through 203. Similarly, there is no required order in which step 206 is performed compared to steps 201, 202, 204, and 205. For example, step 206 can be performed before or after any one of steps 201, 202, 204, and 205. Alternatively, step 206 can be performed simultaneously with any one of steps 201, 202, 204, and 205.
[0163] Optionally, the method may further include step 207 .
[0164] 207. The target AP MLD sends one or more data to the non-AP MLD.
[0165] Correspondingly, the non-AP MLD receives one or more data from the target AP MLD.
[0166] 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 the one or more data to the non-AP MLD via the first STA based on the BA session information between the target AP MLD and the non-AP MLD. Alternatively, it may be understood that the target AP MLD sends the one or more data to the non-AP MLD via the first STA over the BA session between the target AP MLD and the non-AP MLD.
[0167] In the above embodiment, the non-AP MLD triggers a tentative association with the target AP MLD, indicating that the non-AP MLD has begun roaming handover with the target AP MLD. At this point, the original AP MLD, after confirming that there is data in its send buffer, can send all the data in the buffer to the non-AP MLD. This reduces packet loss during the non-AP MLD roaming handover process and improves communication reliability for the non-AP MLD during roaming.
[0168] Optionally, in the embodiment shown in Figure 2 , when the protocol predefines that a non-AP MLD triggers a tentative association with a target AP MLD, at least one of the following items is retained: the key between the original AP MLD and the non-AP MLD, the BA session information between the original AP MLD and the non-AP MLD, the key between the target AP MLD and the non-AP MLD, and the BA session information between the target AP MLD and the non-AP MLD. Alternatively, it can be understood that when the protocol predefines that a non-AP MLD triggers a tentative association with a target AP MLD, it can operate in dual-channel mode: one channel maintains one or more of the key between the original AP MLD and the non-AP MLD, the BA session information between the original AP MLD and the non-AP MLD, and the other channel maintains one or more of the key between the target AP MLD and the non-AP MLD, the BA session information between the target AP MLD and the non-AP MLD, and the like. This ensures that communication between the original AP MLD, the non-AP MLD, and the target AP MLD is not disrupted during non-AP MLD roaming.
[0169] Among them, the secret keys involved in this application may include at least one of the following: PTK, GTK, IGTK, BIGTK.
[0170] As shown in FIG3 , another communication method provided in an embodiment of the present application includes but is not limited to the following steps:
[0171] 301. The original AP MLD determines that data exists in a sending buffer of the original AP MLD. The sending buffer is used to cache data of the original AP MLD and a non-AP MLD. The non-AP MLD triggers a tentative association with a target AP MLD.
[0172] There are at least three implementations of step 301, specifically:
[0173] Method 1.1 is similar to step 201 in FIG2 and will not be described in detail here.
[0174] Method 1.2: When the original AP MLD does not support the first capability, the original AP MLD determines that one or more of data to be sent and data not successfully sent exists in the send buffer starting from the window start position. The first capability is the ability of the original AP MLD to retain successfully sent data in the send buffer starting from the window start position when it determines that a non-AP MLD has triggered a tentative association with a target AP MLD. In other words, the first capability is the ability of the original AP MLD to clear data before the window start position in the send buffer and retain successfully sent data in the send buffer starting from the window start position when it determines that a non-AP MLD has triggered a tentative association with a target AP MLD. Therefore, when the original AP MLD does not support the first capability, the original AP MLD can clear the successfully sent data in the send buffer.
[0175] In mode 1.3, when the original AP MLD supports the first capability, the original AP MLD determines whether one or more of the following exists in the send buffer starting from the start of the window: data to be sent, data that has not been successfully sent, and data that has been successfully sent. This indicates that when the original AP MLD supports the first capability, the original AP MLD may retain the successfully sent data in the send buffer starting from the start of the window.
[0176] 302. The original AP MLD sends all data in the send buffer to the target AP MLD.
[0177] Accordingly, the target AP MLD receives all data in the send buffer from the original AP MLD. Optionally, the method further includes: the target AP MLD receiving address information (such as the MAC address of the original AP MLD) of the original AP MLD from the non-AP MLD; when the non-AP MLD associated with the original AP MLD tentatively associates with the target AP MLD, the target AP MLD sends third information to the original AP MLD based on the address information of the original AP MLD, where the third information is used to request that all data in the send buffer be sent.
[0178] In a possible implementation manner, the original AP MLD may send all the data in the sending buffer to the target AP MLD in one or more times.
[0179] For mode 1.1, if the original AP MLD determines that one or more items of data to be sent or unsuccessfully sent exist in the send buffer starting from the window start position, the total data in the send buffer may include one or more items of data to be sent or unsuccessfully sent in the send buffer starting from the window start position. If the original AP MLD also determines that successfully sent data exists in the send buffer starting from the window start position, the total data also includes the successfully sent data.
[0180] For mode 1.2, all data in the sending buffer may include one or more items of data to be sent starting from the start position of the window in the sending buffer and data that has not been successfully sent.
[0181] For mode 1.3, all data in the sending buffer may include one or more of data to be sent starting from the start position of the window in the sending buffer, data that has not been successfully sent, and data that has been successfully sent.
[0182] 303. When the tentative association between the target AP MLD and the non-AP MLD is activated, the target AP MLD sends data from the original AP MLD to the non-AP MLD.
[0183] Correspondingly, the non-AP MLD receives all the data in the send buffer of the original AP MLD through the target AP MLD.
[0184] There are at least two implementations of step 303, specifically:
[0185] In method 2.1, the target AP MLD receives, from the original AP MLD, BA session information between the original AP MLD and the non-AP MLD; and based on the BA session information, the target AP MLD sends data from the original AP MLD to the non-AP MLD. Optionally, the method further includes: the target AP MLD sending, based on the address information of the original AP MLD, fourth information to the original AP MLD, where the fourth information is used to request the BA session information. Optionally, the target AP MLD sends the data from the original AP MLD to the non-AP MLD based on the BA session information between the original AP MLD and the non-AP MLD. This can also be understood as: the target AP MLD sends the data from the original AP MLD to the non-AP MLD over the BA session between the original AP MLD and the non-AP MLD. In one possible implementation, the target AP MLD may send the data from the original AP MLD to the non-AP MLD in one or more instances. For example, the target AP MLD may send a data frame to the non-AP MLD based on the BA session information, where the data frame may include the data. For example, the target AP MLD can send multiple data frames to the non-AP MLD based on the BA session information. One of the multiple data frames can include one or more data items in the data. This indicates that the target AP MLD needs to use the BA session information between the original AP MLD and the non-AP MLD. This can reduce or avoid service interruption during the non-AP MLD roaming handover process, thereby improving the communication reliability of the non-AP MLD during the roaming process.
[0186] Mode 2.2: The target AP MLD sends the data from the original AP MLD to the non-AP MLD based on the BA session information between the target AP MLD and the non-AP MLD. The BA session information can be obtained through negotiation between the target AP MLD and the non-AP MLD, and the specific negotiation process is not limited here. Optionally, the target AP MLD sends the data from the original AP MLD to the non-AP MLD based on the BA session information. This can also be understood as the target AP MLD sending the data to the non-AP MLD over the BA session between the target AP MLD and the non-AP MLD. In one possible implementation, the target AP MLD may send the data to the non-AP MLD in one or more batches. For example, the target AP MLD may send a data frame to the non-AP MLD based on the BA session information, and the data frame may include the data. In another example, the target AP MLD may send multiple data frames to the non-AP MLD based on the BA session information, and one of the multiple data frames may include one or more data items in the data. This indicates that the target AP MLD sends data from the original AP MLD to the non-AP MLD without using the BA session information between the original AP MLD and the non-AP MLD, thus avoiding BA session transfer.
[0187] It can be understood that there is a correspondence between the methods 1.1 to 1.3 in step 301 and the methods 2.1 to 2.2 in step 303.
[0188] Specifically:
[0189] When step 301 adopts method 1.1, step 303 can be implemented by method 2.1 or method 2.2.
[0190] When step 301 adopts method 1.2, step 303 can be implemented using method 2.1. That is, when the original AP MLD does not support the first capability and the original AP MLD determines that the non-AP MLD has triggered a tentative association with the target AP MLD, the original AP MLD retains the BA session information between the original AP MLD and the non-AP MLD and sends the BA session information to the target AP MLD. The target AP MLD can then send data from the original AP MLD to the non-AP MLD based on the BA session information.
[0191] When step 301 adopts method 1.3, step 303 can be implemented using method 2.2. That is, when the original AP MLD supports the first capability and determines that the non-AP MLD has triggered a tentative association with the target AP MLD, the original AP MLD deletes the BA session information between the original AP MLD and the non-AP MLD. Therefore, the target AP MLD can send data from the original AP MLD to the non-AP MLD based on the BA session information between the target AP MLD and the non-AP MLD.
[0192] The tentative association between the target AP MLD and the non-AP MLD can be activated in at least two ways:
[0193] Mode 3.1: The target AP MLD receives the second information from the original AP MLD. The second information indicates that all data in the send buffer (i.e., the send buffer in the original AP MLD and the non-AP MLD) has been transmitted. This is similar to step 203 in Figure 2 and is not described here in detail.
[0194] Mode 3.2: The target AP MLD receives the tenth message from the non-AP MLD, where the tenth message is used to indicate that the target AP MLD is allowed to send downlink data. This is similar to step 205 in FIG2 and will not be described in detail here.
[0195] The “tentative association between the target AP MLD and the non-AP MLD is activated” involved in this application can be understood as at least one of the following: the non-AP MLD has roamed and switched to the target AP MLD, etc.
[0196] Optionally, data from the original AP MLD can be included in the target AP MLD's to-be-sent queue. The to-be-sent queue is used to buffer data to be sent by the target AP MLD to the non-AP MLD. When the to-be-sent queue also includes one or more data from a gateway device, the data from the original AP MLD precedes the one or more data in the to-be-sent queue. The target AP MLD will first send the data at the front of the to-be-sent queue. As shown in Figure 4, the data from the original AP MLD includes data with SNs 6 to 9, and the data from the network device includes data with SNs 10 to 13. In the to-be-sent queue, data with SNs 6 to 9 precedes data with SNs 10 to 13. Therefore, the target AP MLD can first send data with SN 6, then data with SN 7, and so on.
[0197] In the above embodiment, the non-AP MLD triggers a tentative association with the target AP MLD, indicating that the non-AP MLD has begun roaming handover with the target AP MLD. At this point, the original AP MLD can send all data in its send buffer to the target AP MLD, allowing the target AP MLD to forward data from the original AP MLD to the non-AP MLD. This reduces packet loss during the non-AP MLD roaming handover process and improves communication reliability for the non-AP MLD during roaming.
[0198] Optionally, some detailed solutions are described in detail below in conjunction with the methods 1.1 to 1.3 of step 301 in the embodiment shown in FIG. 3 , and can be referred to the following examples 1 to 3 respectively.
[0199] Example 1:
[0200] In one possible implementation, the method further includes: the original AP MLD sending sixth information to the non-AP MLD, the sixth information being used to instruct the non-AP MLD to retain the BA session information between the original AP MLD and the non-AP MLD. Optionally, the sixth information may include a service identifier, which associates the BA session information between the original AP MLD and the non-AP MLD. This ensures that the BA session can be transferred when the non-AP MLD roams to the target AP MLD, thereby avoiding packet loss caused by roaming. Furthermore, when the sixth information includes the service identifier, the non-AP MLD can retain the BA session information associated with the service identifier.
[0201] Optionally, the sixth information may further instruct the non-AP MLD to retain data in its receive buffer and / or its scoreboard. The receive buffer is used to cache data received by the non-AP MLD from the original AP MLD. This ensures that data in the receive buffer is not cleared when the non-AP MLD roams to the target AP MLD.
[0202] The sixth information may be carried in a request mode field, for example, where the sixth information is a 1-bit reserved field in the request mode field. Alternatively, the request mode field may be located in a BTM request frame. The BTM request frame may also include other fields, which are not described in detail here.
[0203] In one possible implementation, the method further includes: the original AP MLD sending seventh information to the non-AP MLD, where the seventh information is used to indicate that the original AP MLD supports BA session transfer (BA session transfer supported). Optionally, the seventh information can be carried in a neighbor report element field. This application does not limit the wireless frame in which the neighbor report element field is located.
[0204] In one possible implementation, the method further includes: the original AP MLD receiving eighth information from the non-AP MLD, the eighth information being used to instruct the original AP MLD to retain the BA session information between the original AP MLD and the non-AP MLD. Optionally, the eighth information may include a service identifier, which associates the BA session information between the original AP MLD and the non-AP MLD. This ensures that the BA session can be transferred when the non-AP MLD roams to the target AP MLD, thereby avoiding packet loss caused by roaming. Furthermore, when the eighth information includes the service identifier, the non-AP MLD can retain the BA session information associated with the service identifier.
[0205] Optionally, the eighth information may be carried in a status code field. Optionally, the status code field may be located in a BTM response frame or a newly defined frame. When the status code field is located in a BTM response frame, the status code field may also be used to indicate acceptance due to no MSDU loss (ACCEPT with NO MSDU LOST).
[0206] Example 2:
[0207] In one possible implementation, the method further includes: the non-AP MLD deleting a secret key between the original AP MLD and the non-AP MLD. If the non-AP MLD receives a disassociation frame, the non-AP MLD deletes the secret key between the original AP MLD and the non-AP MLD.
[0208] In one possible implementation, the method further includes: the non-AP MLD receiving second indication information from the original AP MLD, the second indication information being used to instruct the non-AP MLD to delete BA session information between the original AP MLD and the non-AP MLD, or the second indication information being used to indicate that the original AP MLD supports the first capability; and the non-AP MLD deleting the BA session information. This avoids BA session transfer.
[0209] In one possible implementation, the method further includes: the original AP MLD deleting a secret key between the original AP MLD and the non-AP MLD. For example, when the original AP MLD supports the first capability and the original AP MLD determines that the non-AP MLD has triggered a tentative association with the target AP MLD, the original AP MLD deleting the secret key between the original AP MLD and the non-AP MLD.
[0210] Example 3:
[0211] In one possible implementation, the method further includes: the original AP MLD sending first information to the non-AP MLD, where the first information indicates that data in a send buffer (i.e., the send buffer of the original AP MLD) has not been completely transmitted. This prevents the non-AP MLD from triggering downlink transmission with the target AP MLD and / or deleting a key with the original AP MLD if the original AP MLD has not completely transmitted data.
[0212] Optionally, the first information is carried in a moredata field of the first frame, the moredata field of the first frame is set to 1, and the first frame is a data frame or a disassociation frame. It should be understood that when the first frame is a disassociation frame, the non-AP MLD can delete the secret key between the original AP MLD and the non-AP MLD.
[0213] Optionally, the above example 1 and example 3 may further include the following detailed solutions, specifically:
[0214] In a possible implementation manner, the method further includes: the target AP MLD broadcasting fifth information, where the fifth information is used to indicate that the target AP MLD supports BA session migration.
[0215] The fifth information may be carried in a neighbor report element field, for example.
[0216] In one possible implementation, the method further includes: the target AP MLD receiving ninth information from the non-AP MLD, the ninth information being used to instruct the target AP MLD to obtain BA session information between the original AP MLD and the non-AP MLD. Optionally, the ninth information also includes a service identifier, which associates the BA session information between the original AP MLD and the non-AP MLD. This indicates that the target AP MLD needs to obtain the BA session information between the original AP MLD and the non-AP MLD, so that the BA session information between the original AP MLD and the non-AP MLD can be used. This can reduce or avoid service interruption during non-AP MLD roaming and switching, thereby improving the communication reliability of the non-AP MLD during roaming. It can also enable the target AP MLD to know which BA session information needs to be transferred from the original AP MLD to the target AP MLD.
[0217] The ninth information may be carried in a reassociation request frame.
[0218] As shown in FIG5 , another communication method provided in an embodiment of the present application includes but is not limited to the following steps:
[0219] 501. A gateway device receives first information from an original AP MLD, where the first information indicates that a non-AP MLD associated with the original AP MLD triggers a tentative association with a target AP MLD.
[0220] Correspondingly, the original AP MLD sends the first information to the gateway device. For example, when the original AP MLD determines that the non-AP MLD associated with the original AP MLD triggers a tentative association with the target AP MLD, the original AP MLD sends the first information to the gateway device.
[0221] 502. The gateway device sends one or more first data to the original AP MLD and the target AP MLD respectively.
[0222] Correspondingly, the original AP MLD and the target AP MLD respectively receive one or more first data from the gateway device.
[0223] The first data may be an MSDU or an A-MSDU.
[0224] Optionally, the method further includes: the gateway device receiving data aggregation capabilities from the target AP MLD; the gateway device receiving data aggregation capabilities from the original AP MLD; and the gateway device generating one or more first data based on the data aggregation capabilities of the target AP MLD and the original AP MLD. For example, the gateway device aggregates one or more second data from the server based on the data aggregation capabilities of the target AP MLD and the original AP MLD to obtain one or more first data. Optionally, one first data item can be aggregated from one or more second data items. Therefore, the first data item here can be an A-MSDU and the second data item can be an MSDU. This can increase the data transmission rate.
[0225] The data aggregation capability involved in this application is used to indicate the data aggregation capability supported by a certain device (such as the original AP MLD or the target AP MLD).
[0226] Optionally, the method further includes: the gateway device assigning an SN to one or more first data; and the gateway device sending the SN of the one or more first data to the original AP MLD and the target AP MLD, respectively. One first data item corresponds to one SN. The one or more SNs of the first data items can be used by the original AP MLD to place the one or more first data items into a queue to be sent by the original AP MLD. The queue to be sent by the original AP MLD is used to cache data to be sent by the original AP MLD to the non-AP MLD. The one or more SNs of the first data items can also be used by the target AP MLD to place the one or more first data items into a queue to be sent by the target AP MLD. The queue to be sent by the target AP MLD is used to cache data to be sent by the target AP MLD to the non-AP MLD.
[0227] 503. The original AP MLD sends second information to the target AP MLD. The second information is used by the target AP MLD to determine data to be sent from one or more first data.
[0228] Correspondingly, the target AP MLD receives the second information from the original AP MLD.
[0229] In one possible implementation, the second information includes the transmission status corresponding to one or more pieces of first data, where the transmission status includes success or failure, and the data to be transmitted is the data in the one or more pieces of first data with a transmission status of failure. Optionally, the second information also includes the retransmission status corresponding to one or more pieces of first data, where the retransmission status includes retransmission success or retransmission failure, and the data to be transmitted also includes the data in the one or more pieces of first data with a retransmission status of retransmission failure. Optionally, the second information may be included in the BA session information between the original AP MLD and the non-AP MLD.
[0230] In another possible embodiment, the second information is used to indicate the starting number corresponding to the data to be sent, and the data to be sent is data with a number greater than or equal to the starting number among one or more first data. It should be understood that in this case, the method also includes: the original AP MLD receives the numbers corresponding to one or more first data from the gateway device. One first data can correspond to one or more numbers, such as the gateway device can number one or more second data in the order in which they arrive at the gateway device, and one first data can be aggregated from one or more second data, so one first data can correspond to one or more numbers. For example, as shown in Figure 6, the first data with an SN of 6 has corresponding numbers 11 and 12; the first data with an SN of 7 has corresponding numbers 13 and 14; the first data with an SN of 5 has a corresponding number 15, and the rest are similar and will not be elaborated here.
[0231] 504. When the tentative association between the target AP MLD and the non-AP MLD is activated, the target AP MLD sends the data to be sent to the non-AP MLD.
[0232] Correspondingly, the non-AP MLD receives the data to be sent from the target AP MLD.
[0233] Optionally, the second information is further used to indicate that the target AP MLD is allowed to send downlink data, so that the target AP MLD can determine that the tentative association with the non-AP MLD is activated.
[0234] If the second information is included in the BA session information between the original AP MLD and the non-AP MLD, step 504 may include: the target AP MLD sending the data to be sent to the non-AP MLD based on the BA session information. Optionally, the target AP MLD sending the data to be sent to the non-AP MLD based on the BA session information can also be understood as: the target AP MLD sending the data from the original AP MLD to the non-AP MLD over the BA session between the original AP MLD and the non-AP MLD. This indicates that the target AP MLD can continue to use the BA session information between the original AP MLD and the non-AP MLD, reducing or avoiding service interruption during non-AP MLD roaming handover, thereby improving communication reliability of the non-AP MLD during roaming.
[0235] Optionally, the method further includes: the target AP MLD receives address information of the original AP MLD from the non-AP MLD (such as the MAC address of the original AP MLD); when the non-AP MLD associated with the original AP MLD tentatively associates with the target AP MLD, the target AP MLD sends third information to the original AP MLD based on the address information of the original AP MLD, where the third information is used to request the BA session information.
[0236] Optionally, the number of data to be sent may be one or more, and the target AP MLD may send the multiple data to be sent to the non-AP MLD in one or more batches. For example, the target AP MLD may send a data frame to the non-AP MLD based on the BA session information, where the data frame may include the multiple data to be sent. For another example, the target AP MLD may send multiple data frames to the non-AP MLD based on the BA session information, where one of the multiple data frames may include one or more data among the multiple data to be sent.
[0237] When the second information indicates the starting number corresponding to the data to be sent, step 504 may include: the target AP MLD sending the data to be sent to the non-AP MLD based on the 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, and the specific negotiation process is not limited herein. Optionally, the target AP MLD sending the data to be sent to the non-AP MLD based on the BA session information between the target AP MLD and the non-AP MLD can also be understood as: the target AP MLD sending the data to be sent to the non-AP MLD based on the BA session between the target AP MLD and the non-AP MLD.
[0238] Optionally, the number of data to be sent may be one or more, and the target AP MLD may send the multiple data to be sent to the non-AP MLD in one or more batches. For example, the target AP MLD may send a data frame to the non-AP MLD based on the BA session information, and the data frame may include multiple data to be sent. In another example, the target AP MLD may send multiple data frames to the non-AP MLD based on the BA session information, and one of the multiple data frames may include one or more data among the multiple data to be sent. This indicates that the target AP MLD sends the data to be sent to the non-AP MLD without using the BA session information between the original AP MLD and the non-AP MLD, thereby avoiding BA session transfer.
[0239] In the above embodiment, the gateway device can learn from the original AP MLD that the non-AP MLD associated with the original AP MLD has triggered a tentative association with the target AP MLD, indicating that the non-AP MLD has begun roaming handover with the target AP MLD. At this point, the gateway device can send the same data to both the original AP MLD and the target AP MLD. This allows the original AP MLD to inform the target AP MLD which data to send to the non-AP MLD when the non-AP MLD switches data from the original AP MLD to the target AP MLD. This allows the target AP MLD to send data that the original AP MLD failed to send to the non-AP MLD, even if the original AP MLD does not migrate data to the target AP MLD. This avoids delays caused by data migration, reduces packet loss during the non-AP MLD roaming handover process, and improves communication reliability for the non-AP MLD during roaming.
[0240] The above mainly introduces the solution provided by the present application from the perspective of the interaction between various devices. It is understandable that, in order to realize the above functions, the above-mentioned implementation devices include hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0241] In the embodiments of the present application, the functional modules of an AP MLD (such as the original AP MLD or the target AP MLD), a non-AP MLD, or a gateway device can be divided according to the above-described method examples. For example, each functional module can be divided according to each function, or two or more functions can be integrated into a single processing module. The integrated module can be implemented in the form of hardware or software functional modules. It should be noted that the module division in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used.
[0242] Referring to Figure 7 , Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 700 can be applied to the methods shown in any 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 can be one or more processors, and the transceiver module 702 can be a transceiver or a communication interface. The communication device can be used to implement the AP MLD (such as the original AP MLD or the target AP MLD), non-AP MLD, or gateway device involved in any of the above-mentioned method embodiments, or to implement the network element functions involved in any of the above-mentioned method embodiments. The network element or network function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the communication device 700 can also include a storage module 703 for storing program code and data of the communication device 700.
[0243] In one embodiment, when the communication device functions as an AP MLD (e.g., an original AP MLD or a target AP MLD) or as a chip implemented in an AP MLD (e.g., an original AP MLD or a target AP MLD), and executes the steps performed by the AP MLD (e.g., an original AP MLD or a target AP MLD) in the above-described method embodiments, the transceiver module 702 is configured to specifically execute the sending and / or receiving actions performed by the AP MLD (e.g., an original AP MLD or a target AP MLD) in any one or more of the embodiments in FIG. 2 , FIG. 3 , or FIG. 5 , for example, supporting the AP MLD (e.g., an original AP MLD or a target AP MLD) in executing other processes described herein. The processing module 701 is configured to support the communication device 700 in executing the processing actions in the above-described method embodiments, for example, supporting the AP MLD (e.g., an original AP MLD or a target AP MLD) in executing other processes described herein.
[0244] In another example, when the communication device functions as a non-AP MLD or a chip used in a non-AP MLD, and executes the steps performed by the non-AP MLD in the aforementioned method embodiments, the transceiver module 702 is configured to specifically execute the sending and / or receiving actions performed by the non-AP MLD in any one or more of the embodiments in Figures 2, 3, or 5, such as supporting the non-AP MLD in executing other processes described herein. The processing module 701 is configured to support the communication device 700 in executing the processing actions in the aforementioned method embodiments, such as supporting the non-AP MLD in executing other processes described herein.
[0245] In another example, when the communication device serves as a gateway device or a chip used in a gateway device, and executes the steps performed by the gateway device in the above-mentioned method embodiments, the transceiver module 702 is used to specifically execute the sending and / or receiving actions performed by the gateway device in any one or more of the embodiments in Figures 2, 3, or 5, such as supporting the gateway device to execute other processes of the technology described herein. The processing module 701 can be used to support the communication device 700 in executing the processing actions in the above-mentioned method embodiments, such as supporting the gateway device to execute other processes of the technology described herein.
[0246] Optionally, when the AP MLD (such as the original AP MLD or the target AP MLD), non-AP MLD, or gateway device is a chip, processing module 701 may be one or more processors, and transceiver module 702 may be a transceiver. Alternatively, transceiver module 702 may be a transmitting module and a receiving module, where the transmitting module may be a transmitter and the receiving module may be a receiver, with the transmitting module and receiving module integrated into a single device, such as a transceiver. In embodiments of the present application, the processor and transceiver may be coupled, and the connection method between the processor and transceiver is not limited in embodiments of the present application. During the execution of the above method, the process of sending information in the above method can be understood as the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver for transmission by the transceiver. After being output by the processor, the above information may undergo further processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be understood as the process of the processor receiving the input information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to be processed further before being input into the processor.
[0247] The above description is for possible product forms of the communication device shown in FIG7 . It should be understood that any product having the functions of the communication device described in FIG7 falls within the scope of protection of the embodiments of this application. It should also be understood that the above description is for illustrative purposes only and does not limit the product form of the communication device of the embodiments of this application.
[0248] Referring to Figure 8 , Figure 8 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. The communication device may be an AP MLD (such as an original AP MLD or a target AP MLD), a non-AP MLD, or a gateway device, or a chip therein. Figure 8 only illustrates the main components of the communication device. In addition to a processor 801 and a transceiver 802, the communication device may further include a memory 803 and input / output devices (not shown). The processor 801 is primarily used to process communication protocols and communication data, as well as to control the entire communication device, execute software programs, and process software program data. The memory 803 is primarily used to store software programs and data. The transceiver 802 may include a control circuit and an antenna. The control circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as a touch screen, display, and keyboard, are primarily used to receive data input by the user and output data to the user.
[0249] When the communication device is turned on, the processor 801 can read the software program in the memory 803, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 801 performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 801. The processor 801 converts the baseband signal into data and processes the data. In another implementation, the radio frequency circuit and antenna can be set independently of the processor that performs baseband processing. For example, in a distributed scenario, the radio frequency circuit and antenna can be arranged independently of the communication device in a remote manner.
[0250] The processor 801 , the transceiver 802 , and the memory 803 may be connected via a communication bus.
[0251] Illustratively, when the communication device is used to execute the steps, methods, or functions performed by the AP MLD (such as the original AP MLD or the target AP MLD, etc.) in the above method embodiment, the processor 801 can be used to execute other processes of the technology described in this document; the transceiver 802 can be used to execute step 202 in Figure 2, and / or other processes of the technology described in this document.
[0252] As another example, when the communication device is used to execute the steps, methods, or functions performed by the non-AP MLD in the above-mentioned method embodiment, the processor 801 can be used to execute other processes of the technology described in this document; the transceiver 802 can be used to execute step 205 in Figure 2, and / or other processes of the technology described in this document.
[0253] Also exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the gateway device in the above method embodiment, the processor 801 can be used to execute other processes of the technology described in this document; the transceiver 802 can be used to execute step 206 in Figure 2, and / or other processes of the technology described in this document.
[0254] In one implementation, the processor 801 may store instructions, which may be computer programs. The computer programs, when executed on the processor 801, may cause the communication device to perform the methods described in the above method embodiments. The computer programs may be embedded in the processor 801, in which case the processor 801 may be implemented by hardware.
[0255] In one implementation, the communication device may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiment. The processor and transceiver described in this application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFIC), a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
[0256] It is understood that the communication device shown in the embodiment of the present application may also have more components than those in Figure 8, and the embodiment of the present application is not limited to this. The method performed by the processor and transceiver shown above is only an example. For the specific steps performed by the processor and transceiver, please refer to the description of the method embodiment above.
[0257] In another possible implementation, in the communication device shown in FIG7 , the processing module 701 may be one or more logic circuits, and the transceiver module 702 may be an input / output interface, also referred to as a communication interface, an interface circuit, an interface, etc. Alternatively, the transceiver module 702 may be a transmitting module and a receiving module, the transmitting module may be an output interface, the receiving module may be an input interface, and the transmitting module and the receiving module may be integrated into one unit, such as an input / output interface.
[0258] Referring to Figure 9, Figure 9 is a schematic diagram of the structure of another communication device provided in an embodiment of the present 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 above-mentioned processing module 701 can be implemented with a logic circuit 901, and the transceiver module 702 can be implemented with an interface 902. Among them, the logic circuit 901 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface 902 can be a communication interface, an input and output interface, a pin, etc. Exemplarily, Figure 9 is shown as an example of the above-mentioned communication device being a chip, and the chip includes a logic circuit 901 and an interface 902. Optionally, the logic circuit and the interface can also be coupled to each other. The specific connection method of the logic circuit and the interface is not limited in the embodiment of the present application.
[0259] Illustratively, when the communication device is used to execute the steps, methods, or functions executed by the original AP MLD in the above-mentioned method embodiment, logic circuit 901 is used to: determine whether data exists in a send buffer of the original AP MLD, where the send buffer is used to cache data of the original AP MLD and a non-AP MLD, and the non-AP MLD triggers a tentative association with a target AP MLD; and interface 902 is used to: send all data in the send buffer to the non-AP MLD or the target AP MLD, where the target AP MLD is used to send data from the original AP MLD to the non-AP MLD.
[0260] As another example, when the communication device is used to execute the steps, methods, or functions executed by the non-AP MLD in the above-mentioned method embodiment, interface 902 is used to: receive all data from a sending buffer of an original AP MLD, where the sending buffer is used to cache data of the original AP MLD and the non-AP MLD; or, receive all data from the sending buffer of the original AP MLD through a target AP MLD; wherein the non-AP MLD triggers a tentative association with the target AP MLD.
[0261] As another example, when the communication device is used to execute the steps, methods, or functions executed by the target AP MLD in the above-mentioned method embodiment, interface 902 is used to: receive all data from a sending buffer of the original AP MLD, where the sending buffer is used to cache data of the original AP MLD and a non-AP MLD, and the non-AP MLD triggers a tentative association with the target AP MLD; and when the tentative association between the target AP MLD and the non-AP MLD is activated, send data from the original AP MLD to the non-AP MLD.
[0262] Also exemplarily, when the communication device is used to execute the steps, methods, or functions performed by the gateway device in the above-mentioned method embodiment, interface 902 is used to: receive first information from the original AP MLD, the first information indicating that the non-AP MLD associated with the original AP MLD triggered a tentative association with the target AP MLD; and send one or more first data to the original AP MLD and the target AP MLD, respectively.
[0263] It is understood that the communication device shown in the embodiment of the present application can implement the method provided in the embodiment of the present application in the form of hardware, or can implement the method provided in the embodiment of the present application in the form of software, etc., and the embodiment of the present application is not limited to this. For the specific implementation of the embodiment shown in Figure 9, reference can also be made to the above-mentioned embodiments, which will not be described in detail here.
[0264] An embodiment of the present application also provides a communication device, which includes at least one processor and a memory; wherein the memory is used to store computer programs or instructions; and at least one processor is used to execute the computer programs or instructions in the memory, so that the method described in any one or more embodiments of Figures 2, 3, and 5 is executed.
[0265] An embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed, the computer executes any one of the methods described in any one or more embodiments of FIG. 2 , FIG. 3 , and FIG. 5 .
[0266] An embodiment of the present application further provides a computer program product, which includes: computer program code, and when the computer program code is executed by a computer, causes the computer to execute any one of the methods described in any one or more embodiments of FIG. 2 , FIG. 3 , and FIG. 5 .
[0267] An embodiment of the present application also provides a chip, which includes at least one processor and an interface. The processor is used to read and execute instructions stored in a memory. When the instructions are executed, the chip executes any method described in any one or more embodiments of Figures 2, 3, and 5.
[0268] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present application. In addition, the network element units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware or in the form of software network element units.
[0269] If the above-mentioned integrated unit is implemented in the form of a software network element unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the part that essentially contributes to the technical solution of the present application, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, terminal device, cloud server, or network device, etc.) to perform all or part of the steps of the above-mentioned methods in each embodiment of the present application. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk. The above is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection of the claims.
Claims
1. A communication method, characterized in that: include: The original access point multi-link device determines that there is data in a sending buffer of the original access point multi-link device, the sending buffer is used to cache data between the original access point multi-link device and a non-access point multi-link device, and the non-access point multi-link device triggers a tentative association with a target access point multi-link device; The original access point multi-link device sends all the data in the sending buffer to the non-access point multi-link device or the target access point multi-link device, and the target access point multi-link device is used to send the data from the original access point multi-link device to the non-access point multi-link device.
2. The method according to claim 1, characterized in that The protocol predefines that the original access point multi-link device does not clear the data starting from the window start position in the sending buffer when determining that the non-access point multi-link device triggers a tentative association with the target access point multi-link device.
3. The method according to claim 1 or 2, characterized in that: The method further comprises: When the original access point multi-link device does not support the first capability, the original access point multi-link device clears the successfully sent data in the sending buffer; When the original access point multi-link device supports the first capability, the original access point multi-link device retains the successfully sent data in the sending buffer starting from the start position of the window; The first capability is the capability of retaining successfully sent data in the sending buffer starting from the start position of the window when the original access point multi-link device determines that the non-access point multi-link device has triggered a tentative association with the target access point multi-link device.
4. The method according to claim 3, characterized in that The method further comprises: When the original access point multi-link device supports the first capability and the original access point multi-link device determines that the non-access point multi-link device triggers a tentative association with the target access point multi-link device, the original access point multi-link device deletes the block confirmation session information between the original access point multi-link device and the non-access point multi-link device; When the original access point multi-link device does not support the first capability and the original access point multi-link device determines that the non-access point multi-link device triggers a tentative association with the target access point multi-link device, the original access point multi-link device retains block confirmation session information between the original access point multi-link device and the non-access point multi-link device.
5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The original access point multi-link device sends block confirmation session information between the original access point multi-link device and the non-access point multi-link device to the target access point multi-link device.
6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The original access point multi-link device sends first information to the non-access point multi-link device, where the first information is used to indicate that the data in the sending buffer has not been completely transmitted.
7. The method according to claim 6, characterized in that 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 de-association frame.
8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: The original access point multi-link device sends second information to the non-access point multi-link device, where the second information is used to indicate that all data in the sending buffer has been transmitted.
9. The method according to claim 8, characterized in that 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 disassociated frame.
10. A communication method, characterized in that: include: The non-access point multi-link device receives all data from a sending buffer of the original access point multi-link device, where the sending buffer is used to cache data between the original access point multi-link device and the non-access point multi-link device; or, The non-access point multi-link device receives all data from the sending buffer of the original access point multi-link device through the target access point multi-link device; The non-access point multi-link device triggers a tentative association with the target access point multi-link device.
11. The method according to claim 10, characterized in that The method further comprises: The non-access point multi-link device receives first information from the original access point multi-link device, where the first information is used to indicate that the data in the sending buffer is not completely transmitted.
12. The method according to claim 11, characterized in that 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 de-association frame.
13. The method according to any one of claims 10 to 12, characterized in that: The method further comprises: The non-access point multi-link device receives second information from the original access point multi-link device, where the second information is used to indicate that all data in the sending buffer has been transmitted.
14. The method according to claim 13, characterized in that 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 disassociated frame.
15. The method according to any one of claims 10 to 14, characterized in that: The protocol predefines that when the non-access point multi-link device triggers a tentative association with a target access point multi-link device, at least one of the following items is retained: a secret key between the original access point multi-link device and the non-access point multi-link device, block confirmation session information between the original access point multi-link device and the non-access point multi-link device, a secret key between the target access point multi-link device and the non-access point multi-link device, and block confirmation session information between the target access point multi-link device and the non-access point multi-link device.
16. A communication method, characterized in that: include: The target access point multi-link device receives all data from a sending buffer of the original access point multi-link device, the sending buffer being used to cache data of the original access point multi-link device and a non-access point multi-link device, the non-access point multi-link device triggering a tentative association with the target access point multi-link device; When the tentative association between the non-access point multi-link device and the target access point multi-link device is activated, the target access point multi-link device sends data from the original access point multi-link device to the non-access point multi-link device.
17. The method according to claim 16, characterized in that The method further comprises: The target access point multi-link device receives block confirmation session information between the original access point multi-link device and the non-access point multi-link device from the original access point multi-link device; The target access point multi-link device sends data from the original access point multi-link device to the non-access point multi-link device, including: The target access point multi-link device sends the data from the original access point multi-link device to the non-access point multi-link device according to the block confirmation session information.
18. A communication device, characterized in that: The method comprises a unit or a module for implementing the method according to any one of claims 1 to 17.
19. A communication device, characterized in that: The communication device includes at least one processor and a memory; The memory is used to store computer programs or instructions; and the at least one processor is used to execute the computer programs or instructions in the memory, so that the method described in any one of claims 1 to 17 is executed.
20. A communication system, characterized in that: The communication system includes an original access point multi-link device and a non-access point multi-link device; The original access point multi-link device is used to perform the method according to any one of claims 1 to 9; The non-access point multi-link device is configured to perform the method according to any one of claims 10 to 15.
21. A communication system, characterized in that: The communication system includes an original access point multi-link device, a non-access point multi-link device and a target access point multi-link device; The original access point multi-link device is used to perform the method according to any one of claims 1 to 9; The non-access point multi-link device is used to perform the method according to any one of claims 10 to 15; The target access point multi-link device is configured to perform the method according to any one of claims 16 to 17.
22. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, which, when executed, cause the computer to perform the method according to any one of claims 1 to 17.
23. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is executed by a computer, the computer is caused to perform the method according to any one of claims 1 to 17.
24. A chip, characterized in that: The chip includes at least one processor and an interface, wherein the processor is used to read and execute instructions stored in a memory, and when the instructions are executed, the chip executes the method according to any one of claims 1 to 17.
Citation Information
Patent Citations
Communication method and device
CN118945745A
Roaming method in multi-link scene, multi-link equipment and storage medium
CN111741500A
Control link switch method employed by wireless fidelity multi-link device
CN112449391A
Multi-link trial association method and related device
CN113747502A
Enhanced wi-fi fast roaming transition for mobile devices
US20220116833A1
