Communication method and apparatus, and storage medium

Abstract

The embodiments of the present application belong to the technical field of Wi-Fi communications. Provided are a communication method and apparatus, and a storage medium. In the method, a second device is triggered by a first device to transfer a context to a third device, wherein the first device is a non-AP STA or a non-AP MLD, the second device is the current AP STA or AP MLD, and the third device is a target AP STA or a target AP MLD. A non-AP STA or a non-AP MLD may trigger context transfer in advance, thereby reducing the service interruption duration in an FT process.

Description

Communication methods, devices and storage media

[0001] This application claims priority to Chinese Patent Application No. 202410707324.2, filed on May 31, 2024, entitled "Communication Method, Apparatus and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application belongs to the field of Wi-Fi communication technology, specifically relating to a communication method, device, and storage medium. Background Technology

[0003] Roaming refers to the ability of a non-access point station (non-AP STA) to switch from one wireless access point station (AP STA) to another in a wireless local area network (WLAN) while the WLAN continues to provide services to it.

[0004] When a non-AP STA roams from the first AP STA to the second AP STA and re-associates with it, a considerable amount of time is required for authentication and key generation, resulting in prolonged service interruption. The Institute of Electrical and Electronics Engineers (IEEE) standard 802.11r for WLAN allows non-AP STAs to pre-process a very short key generation process with the second AP STA based on current association information, reducing service interruption time to less than 100ms and enabling fast roaming.

[0005] Building upon rapid roaming, how to further reduce service interruption time to improve reliability is a pressing technical issue that needs to be addressed. Summary of the Invention

[0006] This application relates to a communication method, apparatus, and storage medium for reducing service interruption time during roaming.

[0007] In a first aspect, embodiments of this application provide a communication method applied in a first device, wherein the first device is a non-AP STA or a non-AP MLD, the method comprising:

[0008] Send a first management frame to the second device, the first management frame being used to request the second device to transfer the context to the third device;

[0009] The second device is the AP STA or AP MLD associated with the first device, and the third device is the AP STA or AP MLD to be associated with the first device.

[0010] In one possible implementation, the context includes a first Media Access Control Service Data Unit (MSDU) and / or a block acknowledgment context, wherein the first MSDU is an MSDU to be sent.

[0011] In one possible implementation, the block acknowledgment context includes at least one of the following: receive window state, first Media Access Control Protocol Data Unit (MPDU), send window state, and second MPDU;

[0012] The receiving window status is used to indicate the receiving status of the receiving window, the first MPDU is the received MPDU that is in the buffer, the sending window status is used to indicate the sending status of the sending window, and the second MPDU is the MPDU to be sent and / or the MPDU that has been sent but not acknowledged by the first device.

[0013] In one possible implementation, the first management frame includes a first field and a second field, the first field indicating the Media Access Control (MAC) address of the third device, and the second field indicating the block confirmation context for which a transfer is requested.

[0014] In one possible implementation, the first management frame includes an ultra-high reliability (UHR) behavior frame.

[0015] In one possible implementation, the first management frame is sent before the first device and the third device reassociate.

[0016] In one possible implementation, the first device, the second device, and the third device have the ability to support context switching.

[0017] In one possible implementation, the method further includes:

[0018] Send first capability information, which indicates that the first device has the capability to support context transfer, and the first capability information is carried in an association request frame and / or a reassociation request frame.

[0019] Secondly, embodiments of this application provide a communication method applied in a second device, the second device being an AP STA or AP MLD, the method comprising:

[0020] Receive a first management frame sent by the first device, the first management frame being used to request the second device to transfer the context to the third device;

[0021] The first device is a non-AP STA or non-AP MLD associated with the second device, and the third device is an AP STA or AP MLD to be associated with the first device.

[0022] In one possible implementation, the context includes a first Media Access Control Service Data Unit (MSDU) and / or a block acknowledgment context, wherein the first MSDU is an MSDU to be sent.

[0023] In one possible implementation, the block acknowledgment context includes at least one of the following: receive window state, first Media Access Control Protocol Data Unit (MPDU), send window state, and second MPDU;

[0024] The receiving window status is used to indicate the receiving status of the receiving window, the first MPDU is the received MPDU that is in the buffer, the sending window status is used to indicate the sending status of the sending window, and the second MPDU is the MPDU to be sent and / or the MPDU that has been sent but not acknowledged by the first device.

[0025] In one possible implementation, the first management frame includes a first field and a second field, the first field indicating the Media Access Control (MAC) address of the third device, and the second field indicating the block confirmation context for which a transfer is requested.

[0026] In one possible implementation, the first device, the second device, and the third device have the ability to support context switching.

[0027] In one possible implementation, the method further includes:

[0028] Send second capability information, which indicates that the second device has the capability to support context transfer, and the second capability information is carried in at least one of a beacon frame, a probe response frame, an association response frame, and a reassociation response frame.

[0029] Thirdly, embodiments of this application provide a communication device applied in a first device, wherein the first device is a non-AP STA or a non-AP MLD, the device comprising:

[0030] The transceiver module is used to send a first management frame to the second device, wherein the first management frame is used to request the second device to transfer the context to the third device;

[0031] The second device is the access point site (AP STA) or access point multi-link device (AP MLD) associated with the first device, and the third device is the AP STA or AP MLD to be associated with the first device.

[0032] Fourthly, embodiments of this application provide another communication device applied in a second device, the second device being an AP STA or AP MLD, the device comprising:

[0033] The transceiver module is used to receive a first management frame sent by the first device, wherein the first management frame is used to request the second device to transfer the context to the third device;

[0034] Wherein, the first device is a non-access point site or a non-access point multi-link device associated with the second device, and the third device is an AP STA or AP MLD to be associated with the first device.

[0035] Fifthly, embodiments of this application provide a communication device, including: a processor, and a memory communicatively connected to the processor;

[0036] The memory stores computer-executed instructions;

[0037] The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in the first or second aspect.

[0038] In a sixth aspect, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method described in the first or second aspect.

[0039] In a seventh aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the method described in the first or second aspect.

[0040] Eighthly, embodiments of this application provide a chip on which a computer program is stored, and when the computer program is executed by the chip, it implements the method described in the first or second aspect.

[0041] In one possible implementation, the chip is a chip in a chip module.

[0042] This application provides a communication method, apparatus, and storage medium. In this method, a first device triggers a context transfer from a second device to a third device. The first device is a non-AP STA or non-AP MLD, the second device is the current AP STA or AP MLD, and the third device is the target AP STA or AP MLD. The non-AP STA or non-AP MLD can trigger the context transfer earlier, thereby reducing service interruption time during the FT process. Attached Figure Description

[0043] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0044] Figure 1 is a schematic diagram of an application scenario provided by an embodiment of this application;

[0045] Figure 2 is a flowchart illustrating a correlation process in related technologies;

[0046] Figure 3 is a flowchart of an FT process in related technologies;

[0047] Figure 4 is a schematic diagram of the frame structure of the block confirmation parameter set field in the related technology;

[0048] Figure 5 is a flowchart of another FT process in related technologies;

[0049] Figure 6 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0050] Figure 7A is a schematic diagram of the receiving window of the second device provided in an embodiment of this application;

[0051] Figure 7B is a schematic diagram of the sending window of the second device provided in an embodiment of this application;

[0052] Figure 8 is a schematic diagram of the frame structure of a first management frame provided in an embodiment of this application;

[0053] Figure 9 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0054] Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0055] Figure 11 is a schematic diagram of another communication device provided in an embodiment of this application;

[0056] Figure 12 is a schematic diagram of the structure of another communication device provided in an embodiment of this application.

[0057] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0058] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0059] In this application, "at least one" means one or more. "More than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0060] The use of terms like "first," "second," etc., in this application is for illustrative purposes and to distinguish the objects being described. They do not imply any order or limit on the number of objects in the embodiments of this application, and therefore do not constitute any limitation on the embodiments of this application. For example, the use of terms like "first device," "second device," etc., is merely to distinguish different devices and does not indicate a difference in priority or importance between the two devices.

[0061] In this application, terms such as "exemplary," "in some embodiments," and "in other embodiments" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the term "exemplary" is used to present the concept in a specific manner.

[0062] For ease of understanding, the application scenarios applicable to the embodiments of this application will be described below with reference to Figure 1.

[0063] Figure 1 is a schematic diagram of an application scenario provided by an embodiment of this application. Referring to Figure 1, taking a wireless local area network as an example, it includes AP STA101, AP STA102, and non-AP STA103.

[0064] Among them, the basic service set (BSS) to which AP STA101 belongs and the BSS to which AP STA102 belongs belong to the same extended service set (ESS). Non-AP STA103 can roam from AP STA101 to AP STA102.

[0065] It should be noted that the above application scenarios are merely examples. Optionally, the above AP STA can also be an AP MLD, and the non-AP STA can also be a non-AP MLD. Other numbers of devices may also be included in the scenario, but this application embodiment does not limit this.

[0066] To explain this application more clearly, the relevant technologies involved in this application will be introduced first below.

[0067] 1. Basic Service Set (BSS)

[0068] BSS is a fundamental component of an 802.11 network, used to describe a group of communicating mobile devices in an 802.11 WLAN.

[0069] There are two types of BBS: one is the infrastructure mode BBS, which includes one AP STA and several non-AP STAs; the other is the stand-alone mode BBS, which consists of several non-AP STAs.

[0070] Each BSS has a unique identifier called the Basic Service Set Identifier (BSSID).

[0071] This application primarily discusses the BSS of the infrastructure model.

[0072] 2. Extended Service Set (ESS)

[0073] It is a union of BSSs with the same identifier connected by a distribution system (DS), but ESS does not include DS.

[0074] 3. Roaming-related content

[0075] In IEEE 802.11, the association process between a non-AP STA and an ESS AP STA is relatively time-consuming, requiring complete authentication and key generation, as shown in Figure 2. On the AP STA side, a context also needs to be established based on the capabilities of the non-AP STA, involving the allocation and initialization of space for many variables, cache allocation, etc.

[0076] When a non-AP STA roams within an ESS to a new AP STA (i.e., the target AP STA), it needs to reassociate with the target AP STA. The reassociation process is similar to the associativity process, and it also involves intra-ESS routing updates (DS mapping updates), which can cause a relatively long service communication interruption (>100ms). The reassociation process also involves transferring downlink data cached in the current AP STA to the target AP STA. How the intra-ESS routing update and data transfer are performed is currently implemented by the AP STA and is independent of the standard.

[0077] IEEE 802.11r introduced Fast BSS Transition (FT), which allows a non-AP STA to pre-conduct a very short key generation process with the target AP STA before re-associating with the target AP STA, significantly reducing service communication interruptions (50ms). Figure 3 shows a flowchart of an FT process.

[0078] 4. Block Acknowledgment (BA)

[0079] In IEEE 802.11, for frames that require acknowledgment, the sending end waits for an acknowledgment after a short inter-frame space (SIFS) after sending each frame. If no acknowledgment is received, the frame is retransmitted, so that the station can sequentially submit the Media Access Control Service Data Unit (MSDU) upwards after receiving the frame.

[0080] As physical layer speeds increase, this mechanism becomes too costly. Therefore, a block acknowledgment mechanism was introduced. This involves both parties pre-negotiating a block acknowledgment protocol for data streams identified by certain traffic identifiers (TIDs). The negotiation process also involves determining how the parties allocate buffers. After establishing the block acknowledgment protocol, the sending end transmits multiple frames (typically aggregated into an aggregated Media Access Control Protocol Data Unit (MPDU) within a Physical Layer Protocol Data Unit (PPDU)) to trigger acknowledgment at the receiving end.

[0081] The parameters of the block confirmation protocol are shown in Figure 4, including the aggregated MSDU (A-MSDU) subfield, the block confirmation policy subfield, the TID subfield, and the cache size subfield. The block confirmation policy subfield is set to 1 to enable block confirmation, and the cache size subfield represents the size of the sliding window.

[0082] Both the sending and receiving ends maintain a bitmap in the block acknowledgment, indicating which MPDUs were successfully transmitted and which were not. The sending end retransmits the MPDUs that were not successfully transmitted. In a block acknowledgment, the receiving end may have preceding MPDUs that were not successfully transmitted. To ensure the sequential submission of MPDUs upwards, it needs to buffer the successfully received MPDUs and wait for the retransmission of the preceding failed MPDUs.

[0083] During the FT process, a block acknowledgment protocol can be established in advance before the non-AP STA reassociates with the target AP STA, in order to further reduce the service interruption time caused by the AP STA handover. As shown in Figure 5, the signaling required to establish the block acknowledgment protocol can be carried through a resource information container (RIC).

[0084] After a non-AP STA reassociates with the target AP STA, the sender will start transmitting from the first MPDU that failed to be transmitted.

[0085] 5. Multi-link device (MLD)

[0086] MLD is a wireless communication device that supports parallel transmission across multiple links. It includes one or more affiliated sites, which are logical sites.

[0087] IEEE 802.11be (Extremely High Throughput (EHT)) defines a Multi-Link Device (MLD), which can include up to 15 affiliated sites. An Access Point Multi-Link Device (AP MLD) can include multiple AP STAs, and a Non-Access Point Multi-Link Device (non-AP MLD) can include one or more non-AP STAs. One or more links can be established between two MLDs.

[0088] APs that support IEEE 802.11be and its subsequent protocols are all in AP MLD form.

[0089] A non-AP STA cannot be associated with an AP MLD, but it can be associated with an AP STA to which the AP MLD belongs.

[0090] When a non-AP MLD roams to an AP MLD, the non-AP MLD can initiate a reassociation process or a FT process through one of its subordinate non-AP STAs.

[0091] When the roaming target of a non-AP MLD is an AP STA, the non-AP MLD can select a non-AP STA belonging to the same frequency band as the target AP STA and initiate a reassociation process or FT process using the MLD address to ensure that the MAC address remains unchanged.

[0092] One of the goals of IEEE 802.11bn (Ultra High Reliability, UHR) is to reduce latency, and improving the roaming process to reduce latency aligns with this goal. This application triggers a context transfer from a second device to a third device via a non-AP STA or non-AP MLD. The second device is the current AP STA or AP MLD, and the third device is the target AP STA or AP MLD. The non-AP STA or non-AP MLD can trigger the context transfer in advance, allowing data transmission to continue within the same context after switching to the target AP STA or AP MLD, thereby reducing service interruption time during the FT process.

[0093] The full Chinese and English names corresponding to the English abbreviations in the accompanying drawings of this application are shown in Table 1:

[0094] Table 1

[0095] The technical solutions shown in this application will now be described in detail through specific embodiments. It should be noted that the following embodiments may exist independently or in combination with each other; identical or identical content will not be repeated in different embodiments.

[0096] Figure 6 is a flowchart illustrating a communication method provided in an embodiment of this application. Referring to Figure 6, the method includes:

[0097] S601, the first device sends a first management frame to the second device, the first management frame being used to request the second device to transfer the context to the third device.

[0098] In other words, the second device receives the first management frame sent by the first device.

[0099] The first device can be either a non-AP STA or a non-AP MLD.

[0100] The first device in this application may be an FTO.

[0101] The second device can be the AP STA or AP MLD associated with the first device, or it can be referred to as the current AP STA or the current AP MLD.

[0102] The third device can be the AP STA or AP MLD that the first device is to be associated with, or it can be called the target AP STA or target AP MLD.

[0103] To facilitate understanding, the specific content included in the context that needs to be transferred is explained in detail below.

[0104] Context transfer includes data transfer and / or block acknowledgment context transfer, meaning the context of the requested transfer may include a first MSDU and / or a block acknowledgment context. The first MSDU is the MSDU that the second device needs to send to the first device, i.e., the data to be transferred.

[0105] The block acknowledgment context may include at least one of the following: receive window state, first MPDU, send window state, and second MPDU.

[0106] The receive window status indicates the reception status of the receive window. For example, the receive window status can indicate which MPDUs have been successfully received and which MPDUs have not yet been successfully received in the second device's receive window. It should be noted that this receive window is the window used by the second device to receive data sent by the first device.

[0107] The first MPDU is the MPDU that the second device receives from the first device and is in the buffer.

[0108] For example, as shown in Figure 7A, the receiving window of the second device includes MPDU5, MPDU6, MPDU7, MPDU8, and MPDU9. MPDU6 and MPDU7 have been successfully received, while MPDU5, MPDU8, and MPDU9 have not been successfully received. Therefore, MPDU6 and MPDU7 can be used as the first MPDU and buffered in the reordering buffer.

[0109] The transmit window status is used to indicate the reception status of the transmit window. For example, the transmit window status can indicate which MPDUs in the second device's receive window have been successfully transmitted and which MPDUs have not yet been successfully transmitted. It should be noted that this transmit window is the window used by the second device to send data to the first device.

[0110] The second MPDU is an MPDU that the second device is about to send to the first device and / or an MPDU that has been sent but has been acknowledged by the first device.

[0111] For example, as shown in Figure 7B, the sending window of the second device includes MPDU1, MPDU2, MPDU3, MPDU4, and MPDU5. MPDU2 and MPDU3 have been successfully sent to the first device, MPDU1 has been sent to the first device but has not yet received confirmation from the first device, and MPDU4 and MPDU5 have not yet been sent to the first device. Therefore, MPDU1, MPDU4, and MPDU5 can all be used as the second MPDU.

[0112] To facilitate understanding, the frame structure of the first management frame will be explained in detail below.

[0113] In one possible implementation, the first management frame includes a first field and a second field, the first field being used to indicate the MAC address of the third device and the second field being used to indicate the block confirmation context for the requested transfer.

[0114] If the block confirmation context includes block confirmation context 1, block confirmation context 2, and block confirmation context 3, the second field can indicate that the block confirmation context for the requested transfer is block confirmation context 2.

[0115] For example, as shown in Figure 8, the first management frame may include a type field, a transfer context request behavior field, a first field, and a second field, wherein the first field occupies 6 octets and indicates the MAC address of the third device, and the second field occupies 1 octet and indicates the block confirmation context for requesting the transfer.

[0116] The first field, also known as the target AP field, such as the target AP STA field or the target AP MLD field, is not limited to a specific name in this application. As long as the function is the same as the first field in this application, it can be considered equivalent to the first field in this application.

[0117] The second field can use TID to indicate the block confirmation context for the requested transfer. For example, when TID is 4, if the 4th bit in the second field is set to 1, it indicates that the block confirmation context corresponding to the data with TID 4 is the block confirmation context for the requested transfer. The second field can also be called the TID bitmap field for block confirmation context request. This application does not limit the specific name of the second field. As long as the function is the same as the second field of this application, it can be equivalent to the second field of this application.

[0118] It should be noted that only block acknowledgment protocol contexts with the same block acknowledgment parameter set settings between the second and third devices can be used for transmission.

[0119] The first management frame may be called a context transfer request frame or a context transfer request frame; this application does not limit the specific name of the first management frame.

[0120] The management frame can be a behavior frame; for example, the management frame can be a UHR behavior frame.

[0121] In one possible implementation, the first management frame is sent before the first device associates or reassociates with the third device.

[0122] For example, the first device can send a first management frame to the second device before sending a reassociation request to the third device, as shown in Figure 9. Alternatively, the first management frame can be sent to the second device simultaneously with the reassociation request to the third device. For instance, a non-AP MLD might send the first management frame to the second device through one of its subordinate non-AP STAs and send a reassociation request to the second device through another subordinate non-AP STA. After receiving the first management frame, the second device can transfer the context to the third device based on the instructions in the first management frame. It should be noted that the context transfer part in Figure 9 is a specific implementation and is not limited in this application.

[0123] In one possible implementation, the first device, the second device, and the third device are capable of supporting context transfer.

[0124] The aforementioned devices can be predefined through the protocol to support context switching capabilities. For example, devices that support UHR and above can be predefined to support context switching capabilities.

[0125] Each device can also indicate its own ability to support context transfer by broadcasting or unicasting information.

[0126] In one possible implementation, the first device may send first capability information, indicating that the first device has the capability to support context transitions. In other words, the second device may receive the first capability information.

[0127] When the first device is a non-AP STA, it can carry the first capability information in the association request frame and / or reassociation request frame; when the first device is a non-AP MLD, it can carry the first capability information in the association request frame and / or reassociation request frame sent by the non-AP STA to which it belongs. Specifically, the first capability information can be carried in the UHR capability element in the association request frame and / or the UHR capability element in the reassociation request frame.

[0128] That is, the first device can send first capability information to the corresponding AP STA or AP MLD during the association process. For example, the first device can send first capability information to the second device during the association process, and the second device can receive the first capability information sent by the first device.

[0129] In one possible implementation, the second device can send second capability information, indicating that the second device has the capability to support context transitions. In other words, the first device can receive the second capability information.

[0130] The second device may transmit second capability information through at least one of beacon frames, probe response frames, association response frames, or reassociation response frames.

[0131] When the second device is an AP MLD, it can send second capability information through at least one of the beacon frames, probe response frames, association response frames, or reassociation response frames sent by its affiliated AP STA.

[0132] Specifically, the second capability information can be carried in at least one of the following: the UHR capability element of the beacon frame, the UHR capability element of the probe response frame, the UHR capability element of the association response frame, and the UHR capability element of the reassociation response frame.

[0133] In one possible implementation, the third device can send third capability information, indicating that the third device has the capability to support context transitions. In other words, the first device can receive the third capability information.

[0134] The third device can send third capability information through at least one of the following: beacon frame, probe response frame, association response frame, or reassociation response frame.

[0135] When the third device is an AP MLD, it can send third capability information through at least one of the beacon frames, probe response frames, association response frames, or reassociation response frames sent by its affiliated AP STA.

[0136] Specifically, the third capability information can be carried in at least one of the following: the UHR capability element of the beacon frame, the UHR capability element of the probe response frame, the UHR capability element of the association response frame, and the UHR capability element of the reassociation response frame.

[0137] In this embodiment, the non-AP STA or non-AP MLD can trigger context transfer in advance, so that after the non-AP STA or non-AP MLD switches to the target AP STA or AP MLD, data transmission can continue on the same context, thereby reducing the service interruption time during the FT process.

[0138] Figure 10 is a schematic diagram of a communication device provided in an embodiment of this application. The device 10 is applied to a first device, which is a non-AP STA or a non-AP MLD. Referring to Figure 10, the device 10 includes:

[0139] The transceiver module 11 is used for the second device to send a first management frame, which is used to request the second device to transfer the context to the third device; wherein the second device is the AP STA or AP MLD associated with the first device, and the third device is the AP STA or AP MLD to be associated with the first device.

[0140] In one possible implementation, the context includes a first MSDU and / or a block acknowledgment context, where the first MSDU is the MSDU to be sent.

[0141] In one possible implementation, the block acknowledgment context includes at least one of the following: receive window state, first MPDU, send window state, and second MPDU;

[0142] The receiving window status is used to indicate the receiving status of the receiving window, the first MPDU is the received MPDU that is in the buffer, the sending window status is used to indicate the sending status of the sending window, and the second MPDU is the MPDU to be sent and / or the MPDU that has been sent but not acknowledged by the first device.

[0143] In one possible implementation, the first management frame includes a first field and a second field, wherein the first field is used to indicate the MAC address of the third device and the second field is used to indicate the block confirmation context for requesting a transfer.

[0144] In one possible implementation, the first management frame includes a UHR behavior frame.

[0145] In one possible implementation, the first management frame is sent before the first device and the third device reassociate.

[0146] In one possible implementation, the first device, the second device, and the third device are capable of supporting context transfer.

[0147] In one possible implementation, the transceiver module 11 is further configured to:

[0148] Send first capability information, which indicates that the first device has the capability to support context transfer. The first capability information is carried in an association request frame and / or a reassociation request frame.

[0149] The communication device 10 can execute the steps performed by the first device in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0150] Figure 11 is a schematic diagram of another communication device provided in an embodiment of this application. This device 20 is used in a second device, which is an AP STA or AP MLD. Referring to Figure 11, the device 20 includes:

[0151] Transceiver module 21 is used to receive a first management frame sent by the first device, the first management frame being used to request the second device to transfer the context to the third device;

[0152] The first device is a non-AP STA or non-AP MLD associated with the second device, and the third device is an AP STA or AP MLD to be associated with the first device.

[0153] In one possible implementation, the context includes a first MSDU and / or a block acknowledgment context, where the first MSDU is the MSDU to be sent.

[0154] In one possible implementation, the block acknowledgment context includes at least one of the following: receive window state, first MPDU, send window state, and second MPDU;

[0155] The receiving window status is used to indicate the receiving status of the receiving window, the first MPDU is the received MPDU that is in the buffer, the sending window status is used to indicate the sending status of the sending window, and the second MPDU is the MPDU to be sent and / or the MPDU that has been sent but not acknowledged by the first device.

[0156] In one possible implementation, the first management frame includes a first field and a second field, wherein the first field is used to indicate the MAC address of the third device and the second field is used to indicate the block confirmation context for requesting a transfer.

[0157] In one possible implementation, the first device, the second device, and the third device are capable of supporting context transfer.

[0158] In one possible implementation, the transceiver module 21 is further configured to:

[0159] Send second capability information, which indicates that the second device has the capability to support context transfer. The second capability information is carried in at least one of a beacon frame, a probe response frame, an association response frame, and a reassociation response frame.

[0160] The communication device 20 can execute the steps performed by the second device in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0161] Figure 12 is a schematic diagram of another communication device provided in an embodiment of this application. Referring to Figure 12, the device 30 includes: a transceiver 31, a memory 32, and a processor 33. The transceiver 31 may include a transmitter and / or a receiver. The transmitter may also be referred to as a transmitter, transmitter, transmitting port, or transmitting interface, etc., and the receiver may also be referred to as a receiver, receiver, receiving port, or receiving interface, etc. Exemplarily, the transceiver 31, memory 32, and processor 33 are interconnected via a bus 34.

[0162] Memory 32 is used to store program instructions;

[0163] The processor 33 is used to execute the program instructions stored in the memory, so that the communication device 30 performs the steps performed by the first device or the second device in the above method embodiment.

[0164] The transceiver 31 is used to perform the transmission and reception functions of the communication device 30 in the above communication method.

[0165] The communication device 30 can be a chip, module, integrated development environment (IDE), etc.

[0166] The communication device 30 can execute the steps executed by the first device or the second device in the above method embodiments. The implementation principle and beneficial effects are similar, and will not be described again here.

[0167] This application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a computer, cause any of the aforementioned communication methods to be executed.

[0168] This application embodiment may also provide a computer program product that can be executed by a processor, such that when the computer program product is executed by a computer, the communication method described above is executed.

[0169] All or part of the steps in the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, it performs the steps of the above-described method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (ROM), random access memory (RAM), flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0170] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0171] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0172] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0173] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A communication method, characterized in that, The method is applied in a first device, which is a non-access point site or a non-access point multi-link device, and includes: Send a first management frame to the second device, the first management frame being used to request the second device to transfer the context to the third device; The second device is the access point site (AP STA) or access point multi-link device (AP MLD) associated with the first device, and the third device is the AP STA or AP MLD to be associated with the first device.

2. The method according to claim 1, characterized in that, The context includes a first Media Access Control Service Data Unit (MSDU) and / or a block acknowledgment context, wherein the first MSDU is an MSDU to be sent.

3. The method according to claim 2, characterized in that, The block confirmation context includes at least one of the following: receive window state, first Media Access Control Protocol Data Unit (MPDU), send window state, and second MPDU; The receiving window status is used to indicate the receiving status of the receiving window, the first MPDU is the received MPDU that is in the buffer, the sending window status is used to indicate the sending status of the sending window, and the second MPDU is the MPDU to be sent and / or the MPDU that has been sent but not acknowledged by the first device.

4. The method according to claim 2 or 3, characterized in that, The first management frame includes a first field and a second field. The first field is used to indicate the Media Access Control (MAC) address of the third device, and the second field is used to indicate the block confirmation context for which a transfer is requested.

5. The method according to any one of claims 1-4, characterized in that, The first management frame includes an ultra-high reliability (UHR) behavior frame.

6. The method according to any one of claims 1-5, characterized in that, The first management frame is sent before the first device and the third device reassociate.

7. The method according to any one of claims 1-6, characterized in that, The first device, the second device, and the third device are capable of supporting context transfer.

8. The method according to claim 7, characterized in that, The method further includes: Send first capability information, which indicates that the first device has the capability to support context transfer, and the first capability information is carried in an association request frame and / or a reassociation request frame.

9. A communication method, characterized in that, The method is applied to a second device, which is an access point site (AP STA) or an access point multi-link device (AP MLD), and includes: Receive a first management frame sent by the first device, the first management frame being used to request the second device to transfer the context to the third device; Wherein, the first device is a non-access point site or a non-access point multi-link device associated with the second device, and the third device is an AP STA or AP MLD to be associated with the first device.

10. The method according to claim 9, characterized in that, The context includes a first Media Access Control Service Data Unit (MSDU) and / or a block acknowledgment context, wherein the first MSDU is an MSDU to be sent.

11. The method according to claim 10, characterized in that, The block confirmation context includes at least one of the following: receive window state, first Media Access Control Protocol Data Unit (MPDU), send window state, and second MPDU; The receiving window status is used to indicate the receiving status of the receiving window, the first MPDU is the received MPDU that is in the buffer, the sending window status is used to indicate the sending status of the sending window, and the second MPDU is the MPDU to be sent and / or the MPDU that has been sent but not acknowledged by the first device.

12. The method according to claim 10 or 11, characterized in that, The first management frame includes a first field and a second field. The first field is used to indicate the Media Access Control (MAC) address of the third device, and the second field is used to indicate the block confirmation context for which a transfer is requested.

13. The method according to any one of claims 9-12, characterized in that, The first device, the second device, and the third device are capable of supporting context transfer.

14. The method according to claim 13, characterized in that, The method further includes: Send second capability information, which indicates that the second device has the capability to support context transfer, and the second capability information is carried in at least one of a beacon frame, a probe response frame, an association response frame, and a reassociation response frame.

15. A communication device, characterized in that, Applied in a first device, wherein the first device is a non-access point site or a non-access point multi-link device, the device includes: The transceiver module is used to send a first management frame to the second device, wherein the first management frame is used to request the second device to transfer the context to the third device; The second device is the access point site (AP STA) or access point multi-link device (AP MLD) associated with the first device, and the third device is the AP STA or AP MLD to be associated with the first device.

16. A communication device, characterized in that, Applied in a second device, the second device being an access point site (AP STA) or an access point multi-link device (AP MLD), the device includes: The transceiver module is used to receive a first management frame sent by the first device, wherein the first management frame is used to request the second device to transfer the context to the third device; Wherein, the first device is a non-access point site or a non-access point multi-link device associated with the second device, and the third device is an AP STA or AP MLD to be associated with the first device.

17. A communication device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-8, or the method as described in any one of claims 9-14.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when executed by a processor, are used to implement the method of any one of claims 1-8, or the method of any one of claims 9-14.

19. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-8, or the method of any one of claims 9-14.

Images