Communication methods, access point multilink devices and non-access point multilink devices
By improving the link reconfiguration request to support seamless roaming, the issues of latency and packet loss during Wi-Fi roaming were resolved, enabling rapid recovery and improved stability of data transmission during seamless roaming.
Patent Information
- Application Number
- CN202510604906.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-10
- Publication Date
- 2026-11-17
AI Technical Summary
In Wi-Fi 7 and earlier technologies, during roaming, when a non-access point AP multi-link device (MLD) establishes a new link after disconnecting from the current AP MLD, it can cause latency and packet loss issues. Existing link reconfiguration requests cannot be directly applied to seamless roaming.
Improve the link reconfiguration request so that it can configure the link for the current AP MLD or the target AP MLD for seamless roaming, and include the address information of the target AP MLD. Support seamless roaming, while also being compatible with link reconfiguration for the current AP MLD.
It enables rapid recovery of data transmission during seamless roaming, reduces latency and packet loss, and improves the stability and efficiency of the communication system.
Smart Images

Figure CN123124141A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of communications, and more specifically, to a communication method, an access point multilink device, a non-access point multilink device, and a storage medium and computer program product for the communication method. Background Technology
[0002] In Wi-Fi 7 and earlier technologies, the roaming process involved a non-access point (AP) multi-link device (MLD) first disconnecting from the currently serving AP MLD (the current AP MLD) before establishing a link with another AP MLD (the target AP MLD). This method resulted in significant latency and even packet loss for non-AP MLDs during roaming. To address this, seamless roaming was proposed. Seamless roaming provides a make-before-break seamless roaming method between AP MLDs within the same Seamless Roaming Domain (SMD). This method allows a non-AP MLD to maintain its link with the current AP MLD while simultaneously establishing a link with the target AP MLD, and then disconnecting its link with the current AP MLD only after the seamless roaming process is complete.
[0003] Seamless roaming can include a preparation phase and an execution phase. The preparation phase performs link configuration and partial context transfer, while the execution phase performs the remaining context transfer and notifies the distributed system (DS) to switch to the AP MLD that is not providing services to the AP MLD. The preparation phase is optional. If the link configuration or context transfer is not completed during the preparation phase, these processes will be performed during the execution phase. Summary of the Invention
[0004] Based on the above, this disclosure provides a communication method, an AP MLD, a non-AP MLD, and a storage medium and computer program product for the communication method, which improves existing link reconfiguration requests to achieve seamless roaming, while being compatible with link reconfiguration requests for link reconfiguration of the current AP MLD.
[0005] In one aspect, this disclosure provides a communication method performed by a first AP MLD that provides services to a non-AP MLD, the method comprising: receiving a link reconfiguration request from the non-AP MLD; and in response to the link reconfiguration request including address information of a second AP MLD to which the non-AP MLD wishes to roam seamlessly, sending link configuration information and one or more contexts associated with the non-AP MLD to the second AP MLD.
[0006] In one aspect, this disclosure provides a method performed by a non-AP MLD, which is served by a first AP MLD, the method comprising: in response to the non-AP MLD wanting to seamlessly roam to a second AP MLD, generating a link reconfiguration request including link configuration information and address information of the second AP MLD; and sending the link reconfiguration request to the first AP MLD.
[0007] In one aspect, this disclosure provides a communication method performed by a second AP MLD, comprising: receiving link configuration information and one or more contexts associated with a non-AP MLD from a first AP MLD; and configuring a link with the non-AP MLD based on the link configuration information.
[0008] In one aspect, this disclosure provides an AP MLD, comprising: a processor; and a memory having instructions stored thereon, the processor being configured to implement the instructions to perform a communication method executed by an AP MLD (e.g., a first AP MLD or a second AP MLD) according to embodiments of this disclosure.
[0009] In one aspect, this disclosure provides a non-AP MLD, comprising: a processor; and a memory having instructions stored thereon, the processor being configured to implement the instructions to implement a communication method executed by the non-AP MLD according to embodiments of this disclosure.
[0010] In one aspect, this disclosure provides an AP MLD, comprising: components for implementing steps of a communication method performed by an AP MLD (e.g., a first AP MLD or a second AP MLD) according to embodiments of this disclosure.
[0011] In one aspect, this disclosure provides a non-AP MLD, comprising: components for implementing steps of a communication method performed by the non-AP MLD according to embodiments of this disclosure.
[0012] In one aspect, this disclosure provides a computer-readable storage medium having instructions stored thereon that, when executed by a processor, implement a communication method according to embodiments of this disclosure.
[0013] In one aspect, this disclosure provides a computer program product including instructions that, when executed by a processor, implement a communication method according to embodiments of this disclosure.
[0014] The technical solution of the embodiments of this disclosure improves the existing link reconfiguration request so that the target of the link configuration can be either the current AP MLD or the seamless roaming target AP MLD, and can include the address information of the seamless roaming target AP MLD, thereby supporting link configuration for the seamless roaming target AP MLD. This enables seamless roaming to be achieved using the link reconfiguration request, while also being compatible with link reconfiguration of the current AP MLD by the link reconfiguration request. Furthermore, by sending the context related to the non-AP MLD to the seamless roaming target AP MLD through the current AP MLD, after seamless roaming is completed, the non-AP MLD and the seamless roaming target AP MLD do not need to negotiate the context related to the non-AP MLD that the seamless roaming target AP MLD has already received, thereby allowing data transmission between the non-AP MLD and the seamless roaming target AP MLD to start more quickly. Attached Figure Description
[0015] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings of the embodiments will be briefly described below. Obviously, the drawings described below only relate to some embodiments of this disclosure and are not intended to limit this disclosure.
[0016] Figure 1 An example communication system to which the communication methods according to embodiments of this disclosure can be applied is shown.
[0017] Figure 2A This is an example flowchart of a communication method performed by a first AP MLD according to an embodiment of the present disclosure.
[0018] Figure 2B This is an example flowchart of a communication method performed by a non-AP MLD according to an embodiment of the present disclosure.
[0019] Figure 2C This is an example flowchart of a communication method performed by a second AP MLD according to an embodiment of the present disclosure.
[0020] Figure 3 An example of a reconfiguration of a multi-link element in a link reconfiguration request according to an embodiment of this disclosure is shown.
[0021] Figure 4 An example of a seamless roaming request element according to an embodiment of this disclosure is shown.
[0022] Figure 5 An example of a seamless roaming responsive element according to an embodiment of this disclosure is shown.
[0023] Figure 6 Another example of a reconfiguration of a multi-link element in a link reconfiguration request according to an embodiment of this disclosure is shown.
[0024] Figure 7 Another example of a reconfiguration of a multi-link element in a link reconfiguration request according to an embodiment of this disclosure is shown.
[0025] Figure 8 Another example of a reconfiguration of a multi-link element in a link reconfiguration request according to an embodiment of this disclosure is shown.
[0026] Figure 9 Another example of a seamless roaming request element according to an embodiment of this disclosure is shown.
[0027] Figure 10 Another example of a seamless roaming request element according to an embodiment of this disclosure is shown.
[0028] Figure 11 Another example of a seamless roaming response element according to an embodiment of this disclosure is shown.
[0029] Figure 12 Another example of a seamless roaming request element according to an embodiment of this disclosure is shown.
[0030] Figure 13 Another example of a reconfiguration of a multi-link element in a link reconfiguration request according to an embodiment of this disclosure is shown.
[0031] Figure 14 An example signaling interaction between a non-AP MLD, a first AP MLD, and a second APMLD during seamless roaming according to an embodiment of this disclosure is illustrated.
[0032] Figure 15 Another example configuration of a communication device (e.g., an AP MLD or a non-AP MLD) according to an embodiment of this disclosure is shown. Detailed Implementation
[0033] The technical solutions of this disclosure will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are part of, but not all of, the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without any creative effort are within the protection scope of this disclosure.
[0034] In the description of this disclosure, it should be noted that the directions or positional relationships indicated by terms such as “center,” “upper,” “lower,” “left,” “right,” “vertical,” “horizontal,” “inner,” and “outer” are based on the directions or positional relationships shown in the figures and are used only for convenience and simplification of the description of this disclosure, and do not indicate or imply that the indicated device or element must have a specific orientation. Furthermore, terms such as “first,” “second,” and “third” are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Similarly, words such as “a,” “an,” or “the” do not represent a limitation of quantity but rather indicate the presence of at least one. Words such as “comprising” or “including” mean that the element or object preceding the word includes those elements or objects listed after the word and their equivalents, without excluding other elements or objects. Words such as “connected” or “linked” are not limited to physical or mechanical connections but can include direct or indirect electrical connections.
[0035] In the description of this disclosure, it should be noted that, unless otherwise expressly specified and limited, terms such as “installation,” “link,” and “connection” should be interpreted broadly. For example, these terms may refer to a fixed connection, a detachable connection, or an integral connection; they may refer to a mechanical connection or an electrical connection; they may refer to a direct connection, an indirect connection via an intermediate medium, or a connection within two components. For those skilled in the art, the specific meaning of the above terms in this disclosure can be understood according to the specific circumstances.
[0036] Furthermore, the technical features described in the different embodiments of this disclosure can be combined with each other, provided that they do not conflict with each other. Additionally, the accompanying drawings are for illustrative purposes only and are simplified for brevity, and therefore may not be exactly the same as actual implementations. For example, device processing delays may be omitted in the figures.
[0037] In this disclosure, an AP, interchangeably referred to as a Wireless Access Point (WAP), is a communication device that communicates with non-APs (e.g., STAs) in a WLAN via one or more links, and allows non-APs to connect to a wired network. An AP is typically connected to a router as a standalone device (e.g., via a wired network), but can also be integrated into or used within a router. An AP MLD may include multiple affiliated APs, and a non-AP MLD may include multiple affiliated non-APs. Multiple affiliated APs and multiple affiliated non-APs may operate in frequency bands such as 2.4 GHz, 5 GHz, or 6 GHz. Each affiliated AP of an AP MLD may simultaneously communicate with each affiliated non-AP of a non-AP MLD via a separate link. Similarly, in this disclosure, a non-AP (e.g., a station or terminal, interchangeably referred to as a STA) is a communication device that communicates with an AP via one or more links. An STA can be any device that includes a Media Access Control (MAC) compliant with IEEE 802.11 and a Physical Layer (PHY) interface to the Wireless Media (WM). For example, an STA can be a laptop, desktop personal computer (PC), personal digital assistant (PDA), access point, or Wi-Fi phone in a WLAN environment. STAs can be fixed or mobile. In a WLAN environment, the terms "STA," "terminal," "wireless terminal," "user," "user equipment," and "node" are often used interchangeably.
[0038] In this disclosure, a STA in a WLAN can function as an AP in different scenarios, and vice versa. This is because communication devices in an IEEE 802.11 (Wi-Fi) technology environment can include both STA and AP hardware components. In this way, based on the actual WLAN conditions and / or requirements, the communication device can switch between STA mode and AP mode or operate simultaneously in both STA and AP modes.
[0039] As mentioned above, seamless roaming can include a preparation phase and an execution phase. Currently, the link reconfiguration request and response (hereinafter referred to as existing link reconfiguration request / response) introduced in the IEEE 802.11be standard are being considered as the request / response used in both the preparation and execution phases. However, since the link identifier (ID) in the existing link reconfiguration request sent by a non-AP MLD indicates the link of the current AP MLD, the existing link reconfiguration request / response cannot be directly applied to seamless roaming. Therefore, it is necessary to improve the existing link reconfiguration request / response to achieve seamless roaming.
[0040] Based on the above, this disclosure proposes a communication method, an AP MLD, a non-AP MLD, and a storage medium and computer program product for the communication method. The technical solution of the embodiments of this disclosure improves existing link reconfiguration requests so that the target of link configuration can be the current AP MLD or a seamless roaming target AP MLD, and can include the address information of the seamless roaming target AP MLD, thereby supporting link configuration for the seamless roaming target AP MLD. This enables seamless roaming to be achieved using link reconfiguration requests, while also being compatible with link reconfiguration requests for the current AP MLD.
[0041] To better understand this disclosure, the data structure of a message (or frame) according to embodiments of this disclosure is described herein. In this disclosure, a message (e.g., a link reconfiguration request / response) may include one or more fields and / or one or more elements. Each element may include one or more fields, such as an element ID field, an element length field, an element ID extension field, etc. Each element may also include one or more sub-elements, each sub-element being an element embedded within another element, which may also include one or more fields, such as a sub-element ID field, a sub-element length field, a sub-element ID extension field, etc. Each field may also consist of one or more sub-fields. Each sub-field may in turn consist of one or more sub-sub-fields, and so on. In this disclosure, elements with the same format can be represented by the same element ID.
[0042] Figure 1 An example communication system 100 to which communication methods according to embodiments of the present disclosure can be applied is shown. Figure 1 As shown, the communication system 100 may include an SMD management entity (SMD-ME) (not shown), multiple AP MLDs located in the SMD, namely AP MLDs 110a, 110b, and 110c, and non-AP MLDs connected to the AP MLDs, namely non-AP MLDs 120a and 120b. AP MLDs 110a, 110b, and 110c can be connected via wired links, wireless links (e.g., ...), Figure 1 The interconnection is achieved through a combination of wired and wireless links (links 130a and 130b shown). When a non-AP MLD enters the coverage area of the SMD, it can associate with the SMD-ME. After association, an AP MLD in the SMD can provide service to a non-AP MLD. For example, AP MLD 110a in the SMD provides service to non-AP MLD 120a via link 140a. AP MLD 110c in the SMD provides service to non-AP MLD 120b via two links 140b and 140c. Each AP MLD can be directly or indirectly connected to an external network (e.g., the Internet). Figure 1 In the example communication system 100 shown, a non-AP MLD 120a can seamlessly roam from the current AP MLD 110a to AP MLD 110b using a communication method according to an embodiment of the present disclosure, that is, establishing a link 140c and disconnecting the link 140a with AP MLD 110a after establishing the link 140c.
[0043] It should be understood that Figure 1 The communication system 100 described is merely an example and not a limitation of this disclosure. For example, although Figure 1 Three AP MLDs are shown, but a communication system to which the communication method according to embodiments of this disclosure can be applied may include more or fewer AP MLDs, or even APs that are not multi-link devices. For example, although... Figure 1 AP MLD 110a provides services to non-AP MLD 120a via one link 140a, but AP MLD 110a can provide services to non-AP MLD 120a via multiple links.
[0044] Figure 2A This is an example flowchart of a communication method 200A performed by a first AP MLD (i.e., the current AP MLD) according to an embodiment of the present disclosure. Method 200A may begin at step S210a. At step S210a, a link reconfiguration request is received from a non-AP MLD. The first AP MLD (current) provides services to the non-AP MLD. The non-AP MLD may send a link reconfiguration request when it determines, due to reasons such as mobility, that it needs to seamlessly roam from the first AP MLD providing services to it to a second AP MLD (i.e., the seamless roaming target AP MLD) (in the SMD).
[0045] At step S220a, in response to the link reconfiguration request including the address information of the second APMLD to which the non-AP MLD wants to roam seamlessly, link configuration information and one or more contexts associated with the non-AP MLD are sent to the second AP MLD. The second AP MLD can use the link configuration information to configure a link for providing services to the non-AP MLD. The link configuration information may correspond to the link information included in the link reconfiguration request. The address information may be any address information that identifies the second AP MLD, such as the MAC address of the second AP MLD. Exemplarily, the link reconfiguration request may include presence information (which may be referred to as first presence information in this disclosure) indicating whether the address information exists and the address information. The first presence information may also be considered as indication information indicating whether the link configuration targeted by the link reconfiguration request is for the first AP MLD or the second APMLD, i.e., whether it is for regular link reconfiguration or for link configuration for seamless roaming. Exemplarily, the first presence information may be indicated by a reserved bit of the presence bit subfield of the multi-link control field of the reconfiguration multi-link element of an existing link reconfiguration request, or by using a reserved subfield of the multi-link control field. In this scenario, address information can be indicated using a subfield in the common information field of the reconfiguration multi-link element of the link reconfiguration request (which is a newly added subfield in the common information field of the existing link reconfiguration request), or a field in a newly added element of the existing link reconfiguration request (e.g., named the Seamless Roaming Request element). In this case, the link reconfiguration request can be indicated to include address information based on the first presence information; for example, when the value of the first presence information is 1, the first AP MLD determines that the link reconfiguration request includes address information and sends one or more contexts to the second AP MLD indicating the address information. Using a reserved subfield of the multi-link control field to indicate the first presence information more clearly indicates whether the link reconfiguration request is for regular link reconfiguration or for seamless roaming link configuration. Furthermore, using a reserved subfield to indicate the first presence information and using a newly added Seamless Roaming Request element to indicate address information and other seamless roaming-related information allows for seamless roaming with minimal changes to existing elements of the existing link reconfiguration request.
[0046] In embodiments where address information is indicated by fields in a newly added Seamless Roaming Request element, a first presence information specifically indicating the existence of address information may not be necessary. In this case, the first AP MLD may, in response to a link reconfiguration request including a Seamless Roaming Request element, determine that the link reconfiguration request includes address information and send one or more contexts to the second AP MLD indicated by that address information.
[0047] Regarding one or more contexts sent from the first AP MLD to the second AP MLD, in one embodiment, these one or more contexts may be defaulted without requiring an indication from a link reconfiguration request. For example, these one or more contexts may be all contexts associated with non-AP MLDs. As another example, these one or more contexts may be the contexts required by the second AP MLD to maintain block acknowledgment (BA) operations between the first AP MLD and non-AP MLDs.
[0048] In another embodiment, the one or more contexts can be indicated in the link reconfiguration request. In this case, the link reconfiguration request may include context indication information that indicates the one or more contexts. Exemplarily, the context indication information may be indicated in a newly added seamless roaming request element. Additionally, the seamless roaming request element may also include presence information indicating the presence of context indication information (which may be referred to as third presence information in this disclosure). In this case, the seamless roaming request element includes context indication information in response to the third presence information indicating the presence of context indication information.
[0049] In one embodiment, context indication information can be used to indicate one or more contexts from optional contexts via a bitmap. For example, optional contexts could be all contexts associated with the non-AP MLD. As another example, optional contexts could be the set of contexts required by the second AP MLD to maintain block acknowledgment (BA) operations between the first AP MLD and the non-AP MLD (referred to in this disclosure as the first context set). That is, the set of contexts that, after seamless roaming is completed, enable the non-AP MLD and the second AP MLD to begin data transmission with a sequence number (SN) consecutive to the data transmission between the non-AP MLD and the first AP MLD. More specifically, the set of contexts that, after seamless roaming is completed, enable data transmission between the non-AP MLD and the second AP MLD such that, for both uplink (UL) and downlink (DL), data with a first SN is transmitted between the non-AP MLD and the second AP MLD, and the non-AP MLD and the second AP MLD use a first reordering buffer window for data transmission. This first SN is consecutive to the SN of the data transmitted between the non-AP MLD and the first AP MLD. The initial value of the first reordering buffer window is consecutive to the last value of the reordering buffer window used by the non-AP MLD and the first AP MLD. For example, the first context set may include the following contexts:
[0050] The non-AP MLD is the block acknowledgment parameters and block acknowledgment timeout value indicated by the existing block acknowledgment protocol of the service identifier TID.
[0051] The next sequence number (SN) to be assigned to the data frame addressed individually by the DL for each TID.
[0052] Latest duplicate receiver cache for TID without BA protocol
[0053] The latest SN of the data delivered to the upper layer by the first AP MLD
[0054] The second AP MLD assigns the start packet number PN to the frame individually addressed by the DL for each TID.
[0055] For UL-addressed frames, the initial value used by the replay counter for each TID of the second AP MLD, and
[0056] The starting value of the reordering buffer window for each TID (i.e., WinStartO of the existing DL BA protocol, such that the second AP MLD does not exceed the reordering buffer window of the non-AP MLD).
[0057] In another embodiment, the context indication information can indicate different context sets as the one or more contexts by indicating different values (i.e., patterns). Indicating different context sets by indicating patterns can reduce the number of bits required for the context indication information, thereby reducing signaling load. For example, when the context indication information indicates a first value, the context set can be the first context set described above. When the context indication information indicates a second value, the context set can be: the second context set required for the second AP MLD to reset the BA operation. That is, the second context set that enables the non-AP MLD and the second AP MLD to start data transmission with a reset SN after seamless roaming is completed. More specifically, the second context set that enables data transmission between the non-AP MLD and the second AP MLD after seamless roaming is completed as follows: for both UL and DL, data with SN 0 is transmitted between the non-AP MLD and the second AP MLD, and the non-AP MLD and the second AP MLD use a reordering buffer window with an initial value of 0. For example, the second context set can include contexts other than the first context set described above.
[0058] The next sequence number (SN) to be assigned to the data frame addressed individually by the DL for each TID.
[0059] The latest SN of the data delivered to the upper layer by the first AP MLD, and
[0060] The starting value of the reordering buffer window for each TID.
[0061] When the context indication information indicates a third value, the context set can be: the third context set required for the second AP MLD to reset the DL BA operation between the first AP MLD and the non-AP MLD. That is, a third context set that, after seamless roaming is completed, the non-AP MLD and the second AP MLD begin UL data transmission with a SN consecutive to the UL data transmission between the non-AP MLD and the first AP MLD, and begin DL data transmission with a reset SN. More specifically, a third context set that, after seamless roaming is completed, performs the following data transmission between the non-AP MLD and the second AP MLD: for UL, data with a first SN is transmitted between the non-AP MLD and the second AP MLD, and the non-AP MLD and the second AP MLD use a first reordering buffer window for data transmission; for DL, data with a SN of 0 is transmitted between the non-AP MLD and the second AP MLD, and the non-AP MLD and the second AP MLD use a reordering buffer window with an initial value of 0. Exemplarily, the third context set includes the contexts other than the above-described first context set:
[0062] The next sequence number SN to be assigned to the data frame addressed individually by DL for each TID, and
[0063] The starting value of the reordering buffer window for each TID.
[0064] When the context indication information indicates a fourth value, the context set can be: the fourth context set required for the second AP MLD to reset the UL BA operation between the first AP MLD and the non-AP MLD. That is, a fourth context set that, after seamless roaming is completed, the non-AP MLD and the second AP MLD begin DL data transmission with a SN consecutive to the downlink data transmission between the non-AP MLD and the first AP MLD, and begin UL data transmission with a reset SN. More specifically, a fourth context set that, after seamless roaming is completed, performs the following data transmission between the non-AP MLD and the second AP MLD: for UL, data with SN 0 is transmitted between the non-AP MLD and the second AP MLD, and the non-AP MLD and the second AP MLD use a reordering buffer window with an initial value of 0; for DL, data with a first SN is transmitted between the non-AP MLD and the second AP MLD, and the non-AP MLD and the second AP MLD use a first reordering buffer window for data transmission. Exemplarily, the fourth context set may include contexts other than the above-described first context set:
[0065] The latest SN of the data that has been delivered to the upper layer by the first AP MLD.
[0066] In another embodiment, context indication information can be implemented through a combination of bitmaps and indication patterns. Exemplarily, in the case where seamless roaming includes a preparation phase and an execution phase (i.e., link reconfiguration includes a preparation phase and an execution phase), a link reconfiguration request sent during the preparation phase (which may be called a link reconfiguration preparation request) can indicate the context that the first AP MLD will send during the preparation phase through an indication pattern. A link reconfiguration request sent during the execution phase (which may be called a link reconfiguration execution request) can indicate the context that the first AP MLD will send during the execution phase through a bitmap, which may be the context that the first AP MLD failed to send to the second AP MLD during the preparation phase. In this way, the context that the first AP MLD will send to the second AP MLD can be indicated more precisely while reducing signaling load. Optionally, the above communication method 200A may further include sending monitoring interval information to the second AP MLD in response to the link reconfiguration request. The monitoring interval information may indicate the time interval for non-AP MLDs to perform information monitoring. In other words, the monitoring interval information can instruct the second AP MLD on the frequency at which the non-AP MLD, which is in power-saving mode, wakes up to monitor information (e.g., beacon frames). After receiving the monitoring interval information, the second AP MLD can transmit information based on the monitoring interval indicated by the monitoring interval information through a link configured for communication with the non-AP MLD, while the link can enter a sleep state when no information transmission is required.
[0067] The link reconfiguration request may further include presence information (which may be referred to as second presence information in this disclosure) indicating the presence of monitoring interval information, and includes monitoring interval information when the second presence information indicates the presence of monitoring interval information. Exemplarily, the second presence information may be indicated using a reserved bit of the presence bit subfield of the multi-link control field of the reconfiguration multi-link element in an existing link reconfiguration request. In this case, the first presence information and the second presence information may be jointly indicated (e.g., using 1 bit); or the first presence information and the second presence information may be indicated separately (e.g., using 2 bits). Separate indication can decouple the first presence information and the second presence information, such that in embodiments where seamless roaming includes a preparation phase and an execution phase, if the link reconfiguration preparation request already carries monitoring interval information, the monitoring interval information may not need to be carried in the link reconfiguration execution request. Alternatively, the second presence information may be indicated using a reserved subfield of the multi-link control field of the reconfiguration multi-link element in an existing link reconfiguration request. In this case, the first presence information and the second presence information are jointly indicated by the reserved subfield.
[0068] When the link reconfiguration request includes second presence information, the first AP MLD can, in response to the second presence information indicating that the link reconfiguration request includes monitoring interval information (e.g., when the value of the second presence information is 1), determine that the link reconfiguration request includes monitoring interval information and send the monitoring interval information to the second AP MLD. In another embodiment, the monitoring interval information can be indicated by a new element in an existing link reconfiguration request. In this case, the first AP MLD can, in response to the link reconfiguration request including this new element, determine that the link reconfiguration request includes monitoring interval information and send the monitoring interval information to the second AP MLD.
[0069] Optionally, the communication method 200A described above may further include sending cached DL data to be sent to non-AP MLDs to the second AP MLD. In one embodiment, the DL data may be default and not required to be indicated by a link reconfiguration request. For example, the DL data may be all DL data cached by the first AP MLD that is not expected to be sent to the non-AP MLD after seamless roaming to the second AP MLD. In another embodiment, the DL data may be indicated in the link reconfiguration request. In this case, the link reconfiguration request may include data transmission information indicating the DL data. Exemplarily, the data transmission information may be indicated in a newly added seamless roaming request element. Additionally, the seamless roaming request element may also indicate the presence of data transmission information (which may be referred to as fourth presence information in this disclosure). In this case, the seamless roaming request element includes the data transmission information when the fourth presence information indicates the presence of data transmission information.
[0070] Data transmission information can indicate DL data based on a Service Identifier (TID). For example, assuming the DL data includes DL data with TIDs from 0 to N, where N is a positive integer (e.g., 7), then in one embodiment, the data transmission information can indicate the DL data by indicating the TID. In another embodiment, a bitmap can be used to indicate the DL data that the first AP MLD wants to send to the second AP MLD from optional DL data, such as DL data with TIDs from 0 to N.
[0071] In embodiments where the seamless roaming request element includes context indication information and data transmission information, the context indication information and data transmission information can be indicated separately through fields within the seamless roaming request element. Alternatively, the context indication information and data transmission information can be indicated separately through sub-elements within the seamless roaming request element. Using sub-elements to indicate seamless roaming-related information, such as context indication information and data transmission information, increases the flexibility of the seamless roaming request element. For example, when new seamless roaming-related information needs to be added, only a new sub-element needs to be added to indicate that new seamless roaming-related information, without modifying other fields or sub-elements.
[0072] Optionally, when the link reconfiguration request includes address information, the communication method 200A may further include: receiving a link configuration result from the second AP MLD, i.e., whether the second AP MLD establishes a link with a non-AP MLD; and sending a link reconfiguration response to the non-AP MLD to indicate the link configuration result. In this case, a reserved subfield of the multi-link control field in the basic multi-link element of an existing link reconfiguration response can be used to indicate whether the link reconfiguration response is for regular link reconfiguration or for seamless roaming link configuration. In embodiments where seamless roaming includes a preparation phase and an execution phase, the link reconfiguration request / response may be indicated in the seamless roaming request / response element of the link reconfiguration request / response (e.g., via a field) for the preparation phase or the execution phase. Alternatively, the link reconfiguration request / response may be indicated in the reconfiguration multi-link element of the link reconfiguration request or the basic multi-link element of the link reconfiguration response for the preparation phase or the execution phase. By indicating whether the link reconfiguration request / response is for the preparation or execution phase in the reconfiguration multilink element / basic multilink element rather than in the seamless roaming request / response element, the structure and control of the seamless roaming request / response element can be simplified. This allows the receiving device (e.g., the first AP MLD or a non-AP MLD) to determine whether the link reconfiguration request / response is for the preparation or execution phase without parsing the seamless roaming request / response element. This facilitates earlier preparation for subsequent seamless roaming processing by the receiving device, enabling faster completion of seamless roaming.
[0073] Furthermore, the link reconfiguration response may also include a seamless roaming response element. The seamless roaming response element may include context transmission status information indicating whether the first AP MLD successfully transmitted one or more contexts to the second AP MLD. Optionally, the seamless roaming response element may also include presence information indicating the presence of context transmission status information (which may be referred to in this disclosure as fifth presence information). In this case, when the seamless roaming response element includes context transmission status information, the fifth presence information may be set to indicate the presence of context transmission status information (e.g., the fifth presence information may be set to a value of 1), that is, the seamless roaming response element may include context transmission status information in response to the fifth presence information indicating the presence of context transmission status information.
[0074] Additionally, the seamless roaming response element may further include data reception period information, indicating the time period during which the non-AP MLD receives data from the first AP MLD after receiving the link reconfiguration response. Optionally, the seamless roaming response element may further include presence information (which may be referred to as sixth presence information in this disclosure) indicating the presence of the data reception period information. In this case, when the seamless roaming response element includes data reception period information, the sixth presence information may be set to indicate the presence of the data reception period information (e.g., the sixth presence information may be set to a value of 1). In embodiments where seamless roaming includes a preparation phase and an execution phase, the seamless roaming response element of a link reconfiguration response (which may be referred to as a link reconfiguration execution response in this disclosure) sent during the execution phase may include data reception period information, while the seamless roaming response element of a link reconfiguration response (which may be referred to as a link reconfiguration preparation response in this disclosure) sent during the preparation phase may not include data reception period information.
[0075] Optionally, in embodiments where seamless roaming includes a preparation phase and an execution phase, the seamless roaming response element may further include timeout information indicating a time period during which link reconfiguration execution requests sent by non-AP MLDs are valid. Optionally, the seamless roaming response element may further include presence information indicating the presence of timeout information (which may be referred to as seventh presence information in this disclosure). In this case, when the seamless roaming response element includes timeout information, the seventh presence information may be set to indicate the presence of timeout information (e.g., the seventh presence information may be set to a value of 1).
[0076] Additionally, the seamless roaming response element may also include an association identifier (AID). After seamless roaming is completed, the second AP MLD can use this AID to identify the non-AP MLD when communicating with it. In embodiments where seamless roaming includes a preparation phase and an execution phase, the AID may be included in the link reconfiguration preparation response or the link reconfiguration execution response. If the AID is included in the link reconfiguration preparation response, the link reconfiguration execution response may not include the AID. Optionally, the seamless roaming response element may also include presence information indicating the presence of the AID (which may be referred to as eighth presence information in this disclosure). In this case, when the seamless roaming response element includes the AID, the eighth presence information may be set to indicate the presence of the AID (e.g., the eighth presence information may be set to the value 1).
[0077] In one embodiment, fields of the Seamless Roaming Response element can be used to indicate context sending status information, data reception period information, timeout information and / or AID, as well as fifth to eighth presence information.
[0078] In another embodiment, sub-elements of the seamless roaming response element can be used to indicate context sending status information, data reception period information, timeout information, and / or AID. Exemplarily, the seamless roaming response element may include at least one of the following: sub-elements indicating context sending status information, timeout information, and / or AID, and sub-elements indicating data reception period information. In this case, the seamless roaming response element for a link reconfiguration preparation response may include sub-elements indicating context sending status information, timeout information, and AID. The seamless roaming response element for a link reconfiguration execution response may include sub-elements indicating context sending status information and sub-elements indicating data reception period information, or only sub-elements indicating data reception period information, depending on whether the first AP MLD needs to send context to the second AP MLD during the execution phase.
[0079] In another embodiment, seamless roaming response elements in different formats can be used to indicate context transmission status information, data reception period information, timeout information, and / or AID. For example, a first format of seamless roaming response elements can be used to indicate context transmission status information and / or AID, while a second format of seamless roaming response elements can be used to indicate data reception period information and / or timeout information. For example, a newly added seamless roaming response element can be used to indicate context transmission status information and / or AID. For data reception period information or timeout information, it can be indicated by improving the Timeout Interval Element (TIE) in the IEEE 802.11be standard (which may be referred to herein as the Existing TIE). Specifically, a reserved value of the Timeout Interval Type field of the Existing TIE can be used to indicate whether the Timeout Interval Value field of the TIE indicates data reception period information or timeout information. For example, a reserved value 6 of the Timeout Interval Type field can be used to indicate that the Timeout Interval Value field indicates timeout information, and a reserved value 7 of the Timeout Interval Type field can be used to indicate that the Timeout Interval Value field indicates data reception period information. In this scenario, the link reconfiguration preparation response may include a seamless roaming response element in a first format indicating context transmission status information and AID, and an improved TIE indicating timeout information. The link reconfiguration execution response may include a seamless roaming response element in a first format indicating context transmission status information and an improved TIE indicating data reception period information, or may only include an improved TIE indicating data reception period information. This simplifies the length of the link reconfiguration response, thereby reducing signaling load and simplifying the structure of the newly added seamless roaming response element. Optionally, the improved TIE may be included in the response message when a non-AP MLD initially associates with the SMD-ME, but not in subsequent link reconfiguration responses. In this case, the information in the TIE applies to the entire period during which the non-AP MLD is associated with the SMD-ME. Regarding the aforementioned seamless roaming request element and seamless roaming response element, in one embodiment, they may be elements of the same format. In this case, an element can be distinguished as a seamless roaming request element or a seamless roaming response element by a field in this element of the same format (which may be referred to in this disclosure as the seamless roaming process type field). Optionally, in embodiments where seamless roaming includes a preparation phase and an execution phase, the seamless roaming process type field may also indicate whether the element is used for the preparation phase or the execution phase. In another embodiment, the seamless roaming request element and the seamless roaming response element may be elements of different formats. Using elements of different formats as seamless roaming request elements and seamless roaming response elements respectively can simplify the element structure, for example, by eliminating the need for information indicating whether an element is a seamless roaming request element or a seamless roaming response element.
[0080] The above text combined Figure 2AThe described communication method improves upon existing link reconfiguration requests by allowing the target link configuration to be either the current AP MLD or the seamless roaming target AP MLD, and includes the address information of the seamless roaming target AP MLD. This supports link configuration for the seamless roaming target AP MLD, enabling seamless roaming to be achieved using link reconfiguration requests while maintaining compatibility with link reconfiguration requests for the current AP MLD. Furthermore, by sending context related to the non-AP MLD to the seamless roaming target AP MLD from the current AP MLD, once seamless roaming is complete, the non-AP MLD and the seamless roaming target AP MLD do not need to negotiate the context already received by the seamless roaming target AP MLD, allowing data transmission between the non-AP MLD and the seamless roaming target AP MLD to begin more quickly. Furthermore, by adding elements to existing link reconfiguration requests to indicate context information and / or data transmission information, and by adding elements to link reconfiguration responses to indicate context transmission status information, timeout information, and / or data reception period information, other functions of seamless roaming can be supported, making link reconfiguration requests / responses more adaptable to various functions of seamless roaming.
[0081] Figure 2B This is an example flowchart of a communication method 200B performed by a non-AP MLD according to an embodiment of the present disclosure. Communication method 200B may include: generating a link reconfiguration request (S210b) including link configuration information and address information of the second AP MLD in response to the non-AP MLD requesting seamless roaming to a second AP MLD; and sending the link reconfiguration request to a first AP MLD (S220b). As described above, the first AP MLD provides services to the non-AP MLD. Additionally, communication method 200B may also include receiving a link reconfiguration response indicating a link configuration result and may include the seamless roaming response elements described above. The non-AP MLD may perform step S210b, i.e., generating and sending a link reconfiguration request for each of the one or more second AP MLDs, upon determining that there is one or more second AP MLDs with better signal quality than the first AP MLD. The link reconfiguration request and link reconfiguration response may be a combination of the above. Figure 2A For the sake of brevity, the link reconfiguration request and link reconfiguration response will not be described in detail here.
[0082] Figure 2CThis is an example flowchart of a communication method 200C performed by a second AP MLD according to an embodiment of this disclosure. The communication method 200C may include: receiving link configuration information and one or more contexts associated with a non-AP MLD from a first AP MLD (S210c), and configuring (i.e., establishing) a link with the non-AP MLD based on the link configuration information (S220c). As described above, the first AP MLD provides services to the non-AP MLD, and the second AP MLD is the AP MLD to which the non-AP MLD will seamlessly roam. The one or more contexts are sent by the first AP MLD in response to a link reconfiguration request received from the non-AP MLD, including the address information of the second AP MLD. The one or more contexts may be the contexts described above, and for brevity, will not be repeated here. After receiving one or more contexts associated with a non-AP MLD, the second AP MLD may configure a link with the non-AP MLD based on the one or more contexts using existing methods or methods developed in the future.
[0083] Additionally, the communication method 200C may further include sending a link reconfiguration response to a non-AP MLD to indicate the link configuration result. The link reconfiguration response may be the link reconfiguration response described above, and for simplicity, will not be repeated here. Alternatively, the communication method 200C may further include sending a link configuration result to a first AP MLD, enabling the first AP MLD to indicate the link configuration result to the non-AP MLD.
[0084] In the foregoing, this disclosure combines Figures 2A to 2C A communication method for seamless roaming according to embodiments of the present disclosure is described. Note that although the above description pertains to seamless roaming of a non-AP MLD from a first AP MLD to a second AP MLD, the principles of the communication method for seamless roaming according to embodiments of the present disclosure can also be applied to any non-AP seamlessly roaming from any first AP to any second AP, even if some or all of these devices are not multi-link devices.
[0085] In the following text, for a better understanding of this disclosure, it will be combined with Figures 3-13 Examples of link reconfiguration requests and link reconfiguration responses according to embodiments of this disclosure are described.
[0086] The link reconfiguration request according to embodiments of this disclosure improves the reconfiguration multi-link element in existing link reconfiguration requests by adding a seamless roaming request element, and improves the basic multi-link element in existing link reconfiguration responses by adding a seamless roaming response element. This allows for the implementation of a link reconfiguration request / response for seamless roaming while maintaining compatibility with link reconfiguration requests / responses for the current AP MLD. The link reconfiguration request according to embodiments of this disclosure may include the entries shown in Table 1 below.
[0087]
[0088]
[0089] Table 1
[0090] The link reconfiguration response according to embodiments of this disclosure may include the entries shown in Table 2 below.
[0091] order meaning 1 category 2 Protected EHT Actions 3 Dialogue token 4 count 5 Reconfiguration status list 6 Group key data (optional) 7 OCI element (optional) 8 Basic multi-link elements (optional) 9 Seamless roaming responsive elements (optional)
[0092] Table 2
[0093] Figure 3 An example of a link reconfiguration request for reconfiguring multiple link elements according to an embodiment of this disclosure is shown. Figure 3 As shown, the reconfiguration of multi-link element 300 may include an element ID field 310, a length field 320, an extended element ID field 330, a multi-link control field 340, a public information field 350, and a link information field 360. The 5th bit B4 in the presence bitmap subfield 343 of the multi-link control field 340 can be used as the SMD seamless roaming information presence sub-subfield 343-5, indicating whether the link reconfiguration request is for regular link reconfiguration or for seamless roaming link configuration, i.e., whether the link reconfiguration request includes address information. This 5th bit is a reserved bit in existing link reconfiguration requests. When the SMD seamless roaming information presence sub-subfield 343-5 indicates that the link reconfiguration request is for seamless roaming link configuration, an SMD seamless roaming information subfield 356 can be added to the public information field 350, which may include address information sub-subfield 356-1, monitoring interval information sub-subfield 356-2, and reserved sub-subfield 356-3. Address Information sub-field 356-1 indicates the address information of the AP MLD to which the non-AP MLD should seamlessly roam. Monitoring Interval Information sub-field 356-2 indicates the monitoring interval information.
[0094] Optionally, if the seamless roaming information contains a sub-subfield 343-5 indicating that the link reconfiguration request is for a link configuration for seamless roaming, the link reconfiguration request may also include a seamless roaming request element. Figure 4 An example of a seamless roaming request element according to an embodiment of this disclosure is shown. More specifically, Figure 4 The element 400 shown illustrates the fields that a seamless roaming request element may include when a field in element 400 (e.g., seamless roaming control field 440, more specifically, seamless roaming process type subfield 441 in seamless roaming control field 440) indicates that the element is a seamless roaming request element, provided that the seamless roaming request element and the seamless roaming response element have the same format.
[0095] like Figure 4 As shown, the seamless roaming request element 400 may include an element ID field 410, a length field 420, an extended element ID field 430, a seamless roaming control field 440, and a seamless roaming operation field 450. The seamless roaming control field 440 may include a seamless roaming process type subfield 441, an existence bitmap subfield 442, and a reserved subfield 443.
[0096] When the seamless roaming request element and the seamless roaming response element have the same format, the seamless roaming process type subfield 441 can be used to indicate whether the element is a seamless roaming request element or a seamless roaming response element. Furthermore, when seamless roaming includes a preparation phase and an execution phase, the seamless roaming process type subfield 441 can also be used to indicate whether it is the preparation phase or the response phase. For example, the seamless roaming process type subfield 441 may include 2 bits, and the seamless roaming process type is indicated as shown in Table 3 below.
[0097] B0 B1 Frames including elements meaning 0 0 Link reconfiguration request frame Seamless roaming request element during the preparation phase 0 1 Link reconfiguration request frame Seamless roaming request element during the execution phase 1 0 Link reconfiguration response frame Seamless roaming responsive elements during the preparation phase 1 1 Link reconfiguration response frame Seamless roaming responsive elements during the execution phase
[0098] Table 3
[0099] The existence of bitmap subfield 442 can indicate the subfields to be included in the seamless roaming operation field 450. For example... Figure 4 As shown, the bitmap existence subfield 442 may include a context indication information existence sub-subfield 442-1, a data transmission information existence sub-subfield 442-2, and a reserved sub-subfield 442-3. In response to the context indication information existence sub-subfield 442-1 indicating the existence of context indication information, a context indication information subfield 451 indicating the aforementioned context indication information may be included in the seamless roaming operation field 450. In response to the data transmission information existence sub-subfield 442-2 indicating the existence of data transmission information, a data transmission information subfield 452 indicating the aforementioned data transmission information may be included in the seamless roaming operation field 450. The seamless roaming operation field 450 may also include a reserved subfield 453.
[0100] Figure 5An example of a seamless roaming responsive element according to an embodiment of this disclosure is shown. More specifically, Figure 5 Element 500a, shown in Figure A, illustrates the fields that a seamless roaming response element may include when a field in element 500a (e.g., seamless roaming control field 440, more specifically, seamless roaming procedure type subfield 441 within seamless roaming control field 440) indicates that the element is a seamless roaming response element, provided that the seamless roaming request element and the seamless roaming response element have the same format. Additionally, reserved bits from existing link reconfiguration responses, such as reserved subfields in basic multilink elements, may be used to indicate whether a seamless roaming response element is included in the link reconfiguration response.
[0101] Unlike Figure 4 ,exist Figure 5In the seamless roaming operation field 450, the bitmap subfield 442 may include an association identifier (AID) presence subfield 444-4, a timeout information presence subfield 442-5, a context transmission status information presence subfield 442-6, a data reception period information presence subfield 442-7, and a reserved subfield 442-8. In response to the AID presence subfield 442-4 indicating the presence of an AID, an AID subfield 454 may be included in the seamless roaming operation field 450, indicating that the seamless roaming target AP MLD has assigned an association identifier to a non-AP MLD. In response to the timeout information presence subfield 442-5 indicating the presence of timeout information, a timeout information subfield 455 may be included in the seamless roaming operation field 450, indicating the timeout information described above. In response to the presence of context transmission status information indicated by sub-subfield 442-2, a context transmission status information subfield 456 may be included in the seamless roaming operation field 450, indicating the context transmission status information described above. In response to the presence of data reception period information indicated by sub-subfield 442-2, a data reception period information subfield 457 may be included in the seamless roaming operation field 450, indicating the data reception period information described above. The context transmission status information subfield 456 may include a quantity sub-subfield 456-1 and a context transmission status information list sub-subfield 456-2. The quantity sub-subfield 456-1 indicates the number of context information entries indicated by the context transmission status information list sub-subfield 456-2. The context transmission status information list sub-subfield 456-2 may include N entries, where N is a positive integer. Each entry consists of a context information sub-sub-subfield (e.g., context information sub-sub-subfield 456-2-1a) and a status code sub-sub-subfield (e.g., status code sub-sub-subfield 456-2-1b). The status code sub-sub-subfield can indicate the sending status (e.g., success or failure) of the context indicated by each context information sub-sub-subfield.
[0102] Information regarding data reception time periods and / or timeouts can also be indicated by improving existing TIEs. Figure 5 Illustration B in the figure illustrates this situation. Figure 5Element 500b shown in Figure B may include an element ID field 510b, a length field 520b, a timeout interval type field 530b, and a timeout interval value field 540b. The timeout interval type field 530b indicates the type of information indicated by the timeout interval value field 540b. As shown in Table 5 below, a value of 6 for the timeout interval type field 530b indicates that the timeout interval value field 540b indicates data reception period information, and a value of 7 for the timeout interval type field 530b indicates that the timeout interval value field 540b indicates timeout information. Values 6 and 7 for the timeout interval type field 530b are reserved values in existing TIEs.
[0103] Value of timeout interval type field meaning unit 0 reserve 1 Reassociation cutoff interval Time Unit (TU) 2 Key life interval Second 3 Related recovery time Time Unit (TU) 4 Start time Time Unit (TU) 5 Peer-to-peer TWT protocol lifecycle Time Unit (TU) 6 Data reception period information For example, a unit of time (TU) or a second. 7 Timeout information For example, a unit of time (TU) or a second. 8-255 reserve
[0104] Table 5
[0105] In embodiments that indicate data reception period information and / or timeout information by modifying existing TIE elements, the newly added roaming response element described above, such as element 500a, may not include data reception period information and / or timeout information.
[0106] Figure 6 Another example of a reconfiguration of a multi-link element in a link reconfiguration request according to an embodiment of this disclosure is shown. Figure 6 The reconfiguration of multi-link element 600 and Figure 3 The difference between the reconfiguration multi-link element 300 and the reconfiguration multi-link element 600 is that the reconfiguration multi-link element 600 uses two reserved bits B4 and B5 of the existence bitmap subfield 343 of the existing reconfiguration multi-link element as the address information existence sub-subfield 343-7 and the monitoring interval information existence sub-subfield 343-8, respectively, to indicate the existence of the address information sub-subfield 356-1 and the monitoring interval information sub-subfield 356-2, while the reconfiguration multi-link element 300 uses one reserved bit B4 of the existence bitmap subfield 343 to jointly indicate the existence of the address information sub-subfield 356-1 and the monitoring interval information sub-subfield 356-2. Figure 3 Compared to the reconfigured multi-link element 300 shown, Figure 6 The reconfigurable multi-link element 600 shown can debind the address information existence information and the monitoring interval information existence information, so that if the link reconfiguration request in the preparation phase already carries the monitoring interval information, the link reconfiguration request in the execution phase does not need to carry the monitoring interval information again.
[0107] Figure 7 Another example of a reconfiguration of a multi-link element in a link reconfiguration request according to an embodiment of this disclosure is shown. Figure 7 The reconfiguration of multi-link element 700 and shown Figure 3The difference between the reconfiguration multilink element 300 and the reconfiguration multilink element 700 is that the reconfiguration multilink element 700 uses the reserved fields of the existing reconfiguration multilink element. Figure 7 The subtype subfield 344 indicates whether the link reconfiguration request is for regular link reconfiguration or for seamless roaming link configuration, specifically whether the link reconfiguration request includes the address information sub-subfield 356-1. The reconfiguration multi-link element 300 uses a reserved bit B4 from the presence bitmap subfield 343 to indicate the presence of the address information sub-subfield 356-1. For example, it can be assumed that a value of 1 for the subtype subfield 344 indicates that the link reconfiguration request includes the address information sub-subfield 356-1; and a value of 0 indicates that the link reconfiguration request does not include the address information sub-subfield 356-1. Directly indicating whether the link reconfiguration request is for regular link reconfiguration or for seamless roaming link configuration based on the subtype subfield 344 is clearer and more straightforward.
[0108] Figure 8 Another example of a reconfiguration of a multi-link element in a link reconfiguration request according to an embodiment of this disclosure is shown. Figure 8 The reconfiguration of multi-link element 800 and shown Figure 3 The difference between the reconfiguration multilink element 300 and the reconfiguration multilink element 800 is that the reconfiguration multilink element 800 only uses the reserved subfields of the existing reconfiguration multilink element. Figure 8 The subtype subfield 344 in the `<link>` element indicates whether the link reconfiguration request is for regular link reconfiguration or for seamless roaming link configuration, excluding address information and monitoring interval information. Address information and monitoring interval information can be indicated through the seamless roaming request element. Figure 9 This situation is illustrated. For example... Figure 9 As shown, the address information and monitoring interval information are indicated by the address information subfield 454 and the monitoring interval information subfield 455 in the seamless roaming request element 900. The seamless roaming request element 900 may also include a monitoring interval information presence subfield 442-4, which indicates whether the monitoring interval information subfield 455 exists. The seamless roaming request element 900 does not need to include information indicating the existence of the address information field 454 because... Figure 9 In the example shown, if the link reconfiguration request includes a seamless roaming request element, then the seamless roaming request element must include the address information subfield 454.
[0109] pass Figure 8 The reconfiguration of multi-link element 800 and shown Figure 9 The seamless roaming request element 900 shown implements a link reconfiguration request according to an embodiment of this disclosure, which may require only a change to one bit in an existing link reconfiguration request.
[0110] Figure 10 and Figure 11 This illustrates seamless roaming request and response elements according to embodiments of the present disclosure when the seamless roaming request and response elements are in different formats. Figure 10 As shown, Figure 10 The seamless roaming request element 1000 shown may include an element ID field 1010, a length field 1020, an element ID extension field 1030, a seamless roaming control field 1040, and a seamless roaming operation field 1050. The seamless roaming control field 1040 may include an existence bitmap subfield 1041 and a reserved subfield 1042. The existence bitmap subfield 1042 may include a context indication information existence sub-subfield 1041-1, a data transmission information existence sub-subfield 1041-2, and a reserved sub-subfield 1041-3. In response to the context indication information existence sub-subfield 1041-1 indicating the existence of context indication information, the seamless roaming operation field 1050 may include a context indication information subfield 1051 to indicate the aforementioned context indication information. In response to the data transmission information existence sub-subfield 1041-2 indicating the existence of data transmission information, the seamless roaming operation field 1050 may include a data transmission information subfield 1052 to indicate the aforementioned data transmission information.
[0111] like Figure 11 As shown, Figure 11The seamless roaming response element 1100 shown may include an element ID field 1110, a length field 1120, an element ID extension field 1130, a seamless roaming control field 1140, and a seamless roaming operation field 1150. The seamless roaming control field 1140 may include an existence bitmap subfield 1141 and a reserved subfield 1142. The existence bitmap subfield 1142 may include an AID existence sub-subfield 1141-1, a timeout information existence sub-subfield 1141-2, a context transmission status information existence sub-subfield 1141-3, a data reception period information existence sub-subfield 1141-4, and a reserved sub-subfield 1141-5. In response to the AID existence sub-subfield 1141-1 indicating the existence of an AID, the seamless roaming operation field 1150 may include an AID subfield 1151 to indicate the AID described above. In response to the presence of timeout information in sub-subfield 1141-2, indicating the existence of timeout information, the Seamless Roaming Operation field 1150 may include a timeout information subfield 1152 to indicate the timeout information described above. In response to the presence of context transmission status information in sub-subfield 1141-3, indicating the existence of context transmission status information, the Seamless Roaming Operation field 1150 may include a context transmission status information subfield 1153 to indicate the context transmission status information described above. In response to the presence of data reception period information in sub-subfield 1141-4, indicating the existence of data reception period information, the Seamless Roaming Operation field 1150 may include a data reception period information subfield 1154 to indicate the data reception period information described above. The context transmission status information subfield 1153 may have and Figure 5 The context sending status information subfield 456 shown has the same structure, and for the sake of simplicity, it will not be described again here. Figure 4 and Figure 5 Seamless roaming request elements and seamless roaming response elements with the same format described require the Seamless Roaming Control Field 440 to control whether the element is used for a seamless roaming request or a seamless roaming response. Using seamless roaming request elements and seamless roaming response elements with different formats can reduce the complexity of the Seamless Roaming Control Field 440.
[0112] Figure 12 Another example of a seamless roaming request element according to an embodiment of this disclosure is shown. Figure 12The seamless roaming request element 1200 shown may include an element ID field 1210, a length field 1220, an element ID extension field 1230, and a seamless roaming sub-element 1240. The seamless roaming sub-element may include sub-elements 1240a and 1240b. Sub-element 1240a is used to indicate context sending information. Sub-element 1240b is used to indicate data sending information. Specifically, sub-element 1240a may include a sub-element ID field 1241a, a length field 1242a, an element ID extension field 1243a, and a context sending information field 1244a. Sub-element 1240b may include a sub-element ID field 1241b, a length field 1242b, an element ID extension field 1243b, and a data sending information field 1244b. Using sub-elements to indicate information related to seamless roaming increases the flexibility of the seamless roaming request element. Figure 13 Another example of a reconfiguration of a multi-link element in a link reconfiguration request according to an embodiment of this disclosure is shown. Figure 13 The reconfiguration of multi-link element 1300 and shown Figure 3 The difference between the reconfigurable multi-link element 300 and the reconfigurable multi-link element 1300 is that the common information field 350 of the reconfigurable multi-link element 1300 may include a link reconfiguration type subfield 357, and can use the reserved bit B4 of the existence bitmap subfield 343 of the existing reconfigurable multi-link element as the link reconfiguration type existence sub-subfield 343-7 indicating the existence of the link reconfiguration type subfield 357. The reconfigurable multi-link element 300 does not include the link reconfiguration type subfield 357, and therefore does not include the link reconfiguration type existence sub-subfield 343-7. The link reconfiguration type subfield 357 can indicate the link reconfiguration type as shown in Table 6 below.
[0113] The value of the link reconfiguration type subfield meaning 0 Existing link reconfiguration 1 Seamless roaming preparation phase 2 Seamless roaming execution phase reserve reserve
[0114] Figure 6
[0115] It should be understood that the above text, in combination with... Figures 3-13 The described link reconfiguration request / element is merely an example and not a limitation of this disclosure.
[0116] Figure 14 An example signaling interaction between a non-AP MLD, a first AP MLD, and a second AP MLD is illustrated in seamless roaming according to an embodiment of this disclosure. The non-AP MLD 1410 is currently serviced by the first AP MLD 1420, and the first AP MLD 1420 and the second AP MLD 1430 are in the same SMD. Figure 14As shown, at S1440, non-AP MLD 1410 can transmit data (i.e., UL / DL data frames) with the first AP MLD 1420. At S1450, non-AP MLD 1410 can determine to perform seamless roaming. Then, seamless roaming can be performed, including a preparation phase S1460 and an execution phase S1470, to seamlessly roam from the first AP MLD 1420 to the second AP MLD 1430. At S1461, non-AP MLD 1410 can send a link reconfiguration request of type preparation (i.e., a link reconfiguration preparation request). The first AP MLD 1420, receiving the link reconfiguration request, can perform a context transfer during the preparation phase, i.e., send one or more contexts related to non-AP MLD 1410 to the second AP MLD 1430 (S1462). At S1463... The second AP MLD 1430 adds (i.e., configures) a link with the non-AP MLD 1410 based on one or more received contexts. The second AP MLD 1430 can also perform optional step S1464, sending the link configuration result to the first AP MLD 1420. Step S1464 can be performed if the first AP MLD 1420 needs to indicate to the non-AP MLD 1410 whether the link configuration of the second AP MLD 1430 was successful. Step S1464 can be omitted if the second AP MLD 1430 indicates to the non-AP MLD 1410 whether the link configuration of the second AP MLD 1430 was successful. At S1465, the first AP MLD 1420 can send a link reconfiguration response of type "ready" (i.e., a link reconfiguration ready response) to the non-AP MLD. At S1471, the non-AP MLD 1410 can send a link reconfiguration request of type "ready" (i.e., a link reconfiguration ready request). The first AP MLD 1420, receiving the link reconfiguration request, can perform a context transfer in the response phase, i.e., send one or more contexts related to the non-AP MLD 1410 to the second AP MLD 1430 (S1472), which may be the contexts that were not successfully sent to the second AP MLD 1430 at S1462. The second AP MLD 1430 can perform the optional step S1473, sending the link configuration result to the first AP MLD. Step S1473 can be performed when the first AP MLD 1420 wants to indicate to the non-AP MLD 1410 whether the link configuration of the second AP MLD 1430 was successful and the second AP MLD 1430 has not performed step S1464. At S1474, the first AP MLD 1420 can send a link reconfiguration response of type response (i.e., a link reconfiguration execution response) to the non-AP MLD 1410.At step S1481, the first AP MLD 1420 can send DL data frames to the non-AP MLD 1410. At step S1482, the non-AP MLD can send UL data frames to the second AP MLD 1430. At step S1483, the non-AP MLD 1410 can transmit data (i.e., UL / DL data frames) with the second AP MLD 1430. More details regarding the signaling interactions between the non-AP MLD, the first AP MLD, and the second AP MLD during seamless roaming, such as the format of link reconfiguration request / response, can be found above and will not be repeated here.
[0117] In the foregoing, this disclosure combines Figures 1-14 A communication method for seamless roaming according to embodiments of the present disclosure is described, along with the link reconfiguration request / response to be used therein. Hereinafter, the present disclosure will be combined with... Figure 15 This disclosure describes devices (e.g., AP MLDs or non-AP MLDs), apparatuses, computer-readable storage media, and computer program products for seamless roaming according to embodiments of the present disclosure.
[0118] Figure 15 An example configuration of a communication device 1500 (e.g., an AP MLD or a non-AP MLD) according to an embodiment of the present disclosure is shown. The communication device 1500 may be a first AP MLD, a second AP MLD, or a non-AP MLD as described above. The communication device 1500 may include a processor, i.e., a central processing unit (CPU) 1530, and at least one memory 1540. Additionally, the communication device 1500 may also include a transceiver 1510 and at least one antenna 1520 (for simplicity, in...). Figure 15(Only one antenna is shown in the diagram). Memory 1540 can store instructions. Transceiver 1510 can transmit / receive signals on the channel via antenna 1520. Processor 1530 can be configured to execute the instructions stored in memory 1540 to perform the methods described in this disclosure (e.g., methods 200A-200C). For example, in the case where communication device 1500 is a first AP MLD, processor 1530 can be configured to: receive a link reconfiguration request from a non-AP MLD; and in response to the link reconfiguration request, including address information of a second AP MLD to which the non-AP MLD wants to roam seamlessly, send link configuration information and one or more contexts associated with the non-AP MLD to the second AP MLD, wherein the first AP MLD provides services to the non-AP MLD. When the communication device 1500 is a non-AP MLD, the processor 1530 can be configured to: generate a link reconfiguration request including link configuration information and address information of the second AP MLD in response to seamless roaming to the second AP MLD; and send the link reconfiguration request to the first AP MLD, wherein the first AP MLD provides services to the non-AP MLD. When the communication device 1500 is the second AP MLD, the processor 1530 can be configured to: receive link configuration information and one or more contexts associated with the non-AP MLD; and configure a link with the non-AP MLD based on the link configuration information, wherein the first AP MLD provides services to the non-AP MLD. Furthermore, the processor 1530 can also be configured to execute the above-mentioned references. Figures 2A-2C Other operations described are acceptable as long as there are no contradictions between them.
[0119] It should be understood that Figure 15 The configuration of the communication device described herein is merely an example and not a limitation. The configuration of the communication device in this disclosure may include, but is not limited to, [other configurations]. Figure 15 The number of components in the component may be more or less.
[0120] Furthermore, this disclosure also provides a communication apparatus including components for implementing a communication method (e.g., method 200A-200C) for seamless roaming according to any embodiment of this disclosure. Exemplarily, the communication apparatus may serve as a first AP MLD and include: components for receiving a link reconfiguration request from a non-AP MLD; and components for sending link configuration information and one or more contexts associated with the non-AP MLD to the second AP MLD in response to the link reconfiguration request, including address information of a second AP MLD to which the non-AP MLD wishes to roam seamlessly, wherein the first AP MLD provides services to the non-AP MLD. Alternatively, the communication apparatus may serve as a non-AP MLD and include: components for generating a link reconfiguration request including link configuration information and address information of the second AP MLD in response to the component wishing to roam seamlessly to the second AP MLD; and components for sending the link reconfiguration request to the first AP MLD, wherein the first AP MLD provides services to the non-AP MLD. Alternatively, the communication device may serve as a second AP MLD and include: components for receiving link configuration information and one or more contexts associated with a non-AP MLD; and components for configuring a link with a non-AP MLD based on the link configuration information, wherein the first AP MLD provides services to the non-AP MLD.
[0121] In addition, this disclosure provides a non-transitory computer-readable storage medium having a computer program stored thereon that, when executed by a processor, can implement a communication method for seamless roaming according to any embodiment of this disclosure (e.g., method 200A-200C).
[0122] In addition, this disclosure provides a computer program product containing stored instructions that, when executed by a processor, can implement a communication method for seamless roaming according to any embodiment of this disclosure (e.g., method 200A-200C).
[0123] This disclosure has now been combined with Figures 1-15This disclosure describes a communication method, apparatus, device, computer-readable storage medium, and computer program product for seamless roaming according to embodiments of the present disclosure. The technical solutions of the embodiments of the present disclosure improve existing link reconfiguration requests so that the target of link configuration can be either the current AP MLD or the seamless roaming target AP MLD, and can include the address information of the seamless roaming target AP MLD, thereby supporting link configuration for the seamless roaming target AP MLD. This enables seamless roaming to be achieved using link reconfiguration requests while maintaining compatibility with link reconfiguration requests for the current AP MLD. Furthermore, by sending context related to a non-AP MLD to the seamless roaming target AP MLD through the current AP MLD, after seamless roaming is completed, the non-AP MLD and the seamless roaming target AP MLD do not need to negotiate the context related to the non-AP MLD already received by the seamless roaming target AP MLD, thus allowing data transmission between the non-AP MLD and the seamless roaming target AP MLD to begin more quickly. Furthermore, by adding elements to existing link reconfiguration requests to indicate context information and / or data transmission information, and by adding elements to link reconfiguration responses to indicate context transmission status information, timeout information, and / or data reception period information, other functions of seamless roaming can be supported, making link reconfiguration requests / responses more adaptable to various functions of seamless roaming. Furthermore, this disclosure also provides a specific format for link reconfiguration requests / responses supporting seamless roaming, promoting the implementation and standardization of seamless roaming.
[0124] It should be noted that the above description is merely some embodiments of this disclosure and an explanation of the technical principles used. For example, the equations involved in this disclosure are merely examples and not limitations. Those skilled in the art should understand that the scope of disclosure involved in this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalent features without departing from the above-described disclosure concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this disclosure.
[0125] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.
[0126] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.
Claims
1. A communication method executed by a first access point (AP) multi-link device (MLD), wherein the first AP MLD provides services to non-AP MLDs, the method comprising: Receive a link reconfiguration request from the non-AP MLD; as well as In response to the link reconfiguration request, which includes the address information of the second AP MLD to which the non-AP MLD should roam seamlessly, link configuration information and one or more contexts associated with the non-AP MLD are sent to the second AP MLD.
2. The method according to claim 1, wherein, The link reconfiguration request also includes first existence information indicating whether the address information exists.
3. The method according to claim 1, further comprising: In response to the link reconfiguration request including monitoring interval information, the monitoring interval information is sent to the second AP MLD, wherein the monitoring interval information indicates the time interval for the non-AP MLD to perform information monitoring.
4. The method according to claim 3, wherein, The link reconfiguration request also includes a second presence information indicating whether the monitoring interval information exists.
5. The method according to claim 4, wherein, The first existence information and the second existence information are jointly indicated; or The first existence information and the second existence information are respectively indicated.
6. The method according to claim 4, wherein, The presence bit subfield of the multilink control field of the reconfiguration multilink element of the link reconfiguration request is reserved to indicate the first presence information and the second presence information; or The reserved subfields of the multi-link control field of the reconfiguration multi-link element of the link reconfiguration request jointly indicate the first existence information and the second existence information.
7. The method according to claim 3, wherein, The address information and the monitoring interval information are respectively indicated by subfields in the common information field of the reconfiguration multi-link element of the link reconfiguration request.
8. The method according to claim 1, wherein, In response to the link reconfiguration request including the address information, the link reconfiguration request further includes a seamless roaming request element, which includes: Contextual indication information, indicating one or more contexts; and / or Data transmission information indicates the downlink DL data that the first AP MLD wants to send to the second AP MLD.
9. The method according to claim 1, wherein, In response to the link reconfiguration request including the address information, the link reconfiguration request further includes a seamless roaming request element, which includes: A third presence information indicating the existence of context indication information, wherein the context indication information indicates the one or more contexts; and / or A fourth presence information indicating whether data transmission information exists, wherein the data transmission information indicates that the first AP MLD is to send downlink DL data to the second AP MLD; And among them, In response to the third presence information indicating the presence of the context indication information, the seamless roaming request element further includes the context indication information; and In response to the fourth presence information indicating the presence of the data transmission information, the seamless roaming request element further includes the data transmission information.
10. The method according to claim 8 or 9, wherein, Use the fields in the Seamless Roaming Request element of the Link Reconfiguration Request to indicate the address information and monitoring interval information, respectively.
11. The method according to claim 8, wherein, The seamless roaming request element includes a first sub-element and / or a second sub-element, wherein the first sub-element is used to indicate the context indication information and the second sub-element is used to indicate the data transmission information.
12. The method according to claim 8 or 9, wherein, The context indication information is used to indicate one or more contexts from an optional context through a bitmap.
13. The method according to claim 8 or 9, wherein, The context indication information indicates different sets of contexts as one or more contexts by indicating different values.
14. The method according to claim 13, wherein, In response to the context indication information indicating a first value, the context set is a first context set such that after seamless roaming is completed, the non-AP MLD and the second AP MLD begin data transmission with a sequence number SN that is consecutive to the data transmission between the non-AP MLD and the first AP MLD; In response to the context indication information indicating a second value, the context set is a second context set that enables the non-AP MLD and the second AP MLD to begin data transmission with a reset SN after seamless roaming is completed; In response to the context indication information indicating a third value, the context set is a third context set that, after seamless roaming is completed, the non-AP MLD and the second AP MLD begin UL data transmission with a SN that is continuous with the uplink UL data transmission between the non-AP MLD and the first AP MLD, while the downlink DL data transmission begins with a reset SN. as well as In response to the context indication information indicating a fourth value, the context set is a fourth context set that includes the non-AP MLD and the second AP MLD starting DL data transmission with a SN that is continuous with the DL data transmission between the non-AP MLD and the first AP MLD, and starting UL data transmission with a reset SN.
15. The method according to claim 14, wherein, The first context set includes: The non-AP MLD is the block acknowledgment parameters and block acknowledgment timeout value indicated by the existing block acknowledgment protocol of the service identifier TID. The next sequence number (SN) to be assigned to the data frame addressed individually by the DL for each TID. Latest duplicate receiver cache for TID without BA protocol The latest SN of the data delivered to the upper layer by the first AP MLD The second AP MLD assigns the start packet number PN to the frame individually addressed by the DL for each TID. For UL-addressed frames, the initial value used by the replay counter for each TID of the second AP MLD, and The starting value of the reordering buffer window for each TID; The second context set includes the contexts in the first context set except for the following: The next sequence number (SN) to be assigned to the data frame addressed individually by the DL for each TID. The latest SN of the data delivered to the upper layer by the first AP MLD, and The starting value of the reordering buffer window for each TID; The third context set includes the contexts in the first context set other than the following: The next sequence number SN to be assigned to the data frame addressed individually by DL for each TID, and The starting value of the reordering buffer window for each TID; The fourth context set includes the contexts in the first context set other than the following: The latest SN of the data that has been delivered to the upper layer by the first AP MLD.
16. The method according to claim 1, further comprising: In response to the link reconfiguration request including the address information, the link configuration result is received from the second AP MLD; as well as Send a link reconfiguration response to the non-AP MLD to indicate the link configuration result.
17. The method according to claim 16, wherein, The link reconfiguration request is either a link reconfiguration preparation request sent during the seamless roaming preparation phase or a link reconfiguration execution request sent during the seamless roaming execution phase; and wherein, In response to the link reconfiguration request including the address information, the link reconfiguration request including a seamless roaming request element, and the link reconfiguration response including a seamless roaming response element, the seamless roaming response element including at least one of the following: A fifth presence information indicating the existence of context transmission status information, wherein the context transmission status information indicates whether the first AP MLD successfully transmitted the one or more contexts to the second AP MLD. A sixth presence information indicating the existence of data reception period information, wherein the data reception period information indicates the time period during which the non-AP MLD receives data from the first AP MLD after the non-AP MLD receives the link reconfiguration response; and A seventh presence information indicating the existence of timeout information, wherein the timeout information indicates a time period during which the link reconfiguration execution request sent by the non-AP MLD is valid; and In response to the fifth presence information indicating the presence of the context transmission status information, the seamless roaming response element includes the context transmission status information; In response to the sixth presence information indicating the existence of the data reception period information, the seamless roaming response element includes the data reception period information; and In response to the seventh existence information indicating the existence of the timeout information, the seamless roaming response element includes the timeout information.
18. The method according to claim 17, wherein, The seamless roaming request element and the seamless roaming response element are elements of the same format, and a field in the elements of the same format indicates whether the elements of the same format are the seamless roaming request element or the seamless roaming response element; or The seamless roaming request element and the seamless roaming response element are elements with different formats.
19. The method according to claim 1, wherein, Seamless roaming includes a preparation phase and an execution phase, wherein the address information is included in response to the link reconfiguration request. The reconfiguration multi-link elements of the link reconfiguration request and / or the basic multi-link elements of the link reconfiguration response in response to the link reconfiguration request include information indicating whether the link reconfiguration request and / or the link reconfiguration response are for the preparation phase or the execution phase; or The seamless roaming request element of the link reconfiguration request and / or the seamless roaming response element in response to the link reconfiguration request include information indicating whether the link reconfiguration request and / or the link reconfiguration response is for the preparation phase or the execution phase.
20. A method performed by a non-access point (AP) multi-link device (MLD), wherein the non-AP MLD is serviced by a first AP MLD, the method comprising: In response to the need for seamless roaming to the second AP MLD, a link reconfiguration request is generated, including link configuration information and the address information of the second AP MLD. as well as Send the link reconfiguration request to the first AP MLD.
21. The method according to claim 20, wherein, The link reconfiguration request also includes first existence information indicating whether the address information exists, wherein the first existence information indicates that the address information exists.
22. The method according to claim 20, wherein, The link reconfiguration request also includes a seamless roaming request element, which includes: Context indication information, indicating one or more contexts to be sent from the first AP MLD to the second AP MLD; and / or Data transmission information indicates that the first AP MLD wants to send downlink data to the second AP MLD.
23. The method according to claim 22, wherein, The context indication information indicates different sets of contexts as one or more contexts by indicating different values.
24. The method of claim 20, further comprising: Receive a link reconfiguration response, the link reconfiguration response indicating the link configuration result and including context transmission status information, the context transmission status information indicating whether the first AP MLD successfully sent one or more contexts to the second AP MLD.
25. An access point (AP) multi-link device (MLD), comprising: processor; as well as The memory, on which instructions are stored, The processor is configured to execute the instructions to implement the method according to any one of claims 1-19.
26. A non-access point AP multi-link device (MLD), comprising: processor; as well as The memory, on which instructions are stored, The processor is configured to execute the instructions to implement the method according to any one of claims 20-24.
