Method for establishing multi-access point coordination technology and electronic apparatus

Abstract

Embodiments of the present disclosure provide a method for establishing multi-access point coordination technology and an electronic apparatus. The method comprises: a first device sends to a second device a third message requesting to establish multi-access point coordination technology, wherein the third message comprises an establishment request for one or more multi-access point coordination technology (S702); and the first device receives a fourth message of the second device in response to the third message, wherein the fourth message comprises an establishment response for the one or more multi-access point coordination technology (S704). The present disclosure solves the problem in the related art of redundancy caused by multiple air-interface interactions for the multi-access point coordination technology.

Description

Methods and electronic devices for establishing multi-access point collaboration technology

[0001] Cross-references to related applications

[0002] This disclosure is based on and claims priority to Chinese patent application CN202411044378.1, filed on July 31, 2024, entitled “Method and Electronic Device for Establishing Multi-Access Point Collaboration Technology”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communications, and more specifically, to a method and electronic device for establishing a multi-access point cooperation technology. Background Technology

[0004] When multiple multi-AP technologies collaborate between link-level access points (APs), a separate multi-AP setup process is required, leading to air interface redundancy due to multiple frame exchanges. Multi-link devices may support the same or different multi-AP collaboration technologies on different links. When these technologies need to be used across multiple links, a specific multi-AP setup process must be performed on each link, further increasing air interface redundancy due to frame exchanges. In both single-link and multi-link scenarios, multiple multi-AP collaboration technologies may simultaneously update information; independent update processes also contribute to air interface redundancy. Summary of the Invention

[0005] This disclosure provides a method and electronic device for establishing a multi-access point collaboration technology, which at least solves the problem of redundancy caused by multiple air interface interactions in the related art.

[0006] According to one embodiment of this disclosure, a method for establishing a multi-access point collaboration technology is provided, comprising: a first device sending a third message to a second device requesting the establishment of a multi-access point collaboration technology, wherein the third message contains an establishment request for one or more multi-access point collaboration technologies; and the first device receiving a fourth message from the second device in response to the third message, wherein the fourth message contains an establishment response for one or more multi-access point collaboration technologies.

[0007] According to another embodiment of this disclosure, a method for establishing a multi-access point collaboration technology is provided, comprising: a second device receiving a third message sent by a first device requesting the establishment of a multi-access point collaboration technology, wherein the third message contains an establishment request for one or more multi-access point collaboration technologies; and the second device sending a fourth message to the first device in response to the third message, wherein the fourth message contains an establishment response for one or more multi-access point collaboration technologies.

[0008] According to yet another embodiment of this disclosure, a computer-readable storage medium is also provided, in which a computer program is stored, wherein the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0009] According to yet another embodiment of this disclosure, an electronic device is also provided, including a memory and a processor, wherein a computer program is stored in the memory and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0010] According to yet another embodiment of this disclosure, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments. Attached Figure Description

[0011] Figure 1 is a flowchart of the discovery process for MLD in the prior art;

[0012] Figure 2 shows the format of multi-link elements in the prior art;

[0013] Figure 3 shows the format of each STA configuration sub-element of a basic multi-link element in the prior art;

[0014] Figure 4 shows multiple BSSIDs under multiple links in the prior art;

[0015] Figure 5 is a flowchart of the operation of various collaborative technologies in the prior art;

[0016] Figure 6 is a hardware structure block diagram of a mobile terminal for establishing a multi-access point cooperation technology according to an embodiment of the present disclosure.

[0017] Figure 7 is a flowchart of a method for establishing a multi-access point collaboration technology according to an embodiment of the present disclosure;

[0018] Figure 8 is another flowchart of a method for establishing a multi-access point collaboration technology according to an embodiment of the present disclosure;

[0019] Figure 9 is a flowchart of a method for establishing a single-link multi-access point cooperation technology according to an embodiment of the present disclosure;

[0020] Figure 10 is a schematic diagram of the field structure of a multi-access point element according to an embodiment of the present disclosure;

[0021] Figure 11 is a schematic diagram of the field structure configured according to an embodiment of the present disclosure;

[0022] Figure 12 is another schematic diagram of the field structure of a multi-access point element according to an embodiment of the present disclosure;

[0023] Figure 13 is another schematic diagram of the field structure configured according to an embodiment of the present disclosure;

[0024] Figure 14 is a schematic diagram of the structure of the multi-access point information field of a multi-access point element according to an embodiment of the present disclosure;

[0025] Figure 15 is a flowchart of a method for establishing a multi-link multi-access point cooperation technology according to an embodiment of the present disclosure;

[0026] Figure 16 is a schematic diagram of the field structure of a multi-link element according to an embodiment of the present disclosure;

[0027] Figure 17 is a schematic diagram of the field structure of public information according to an embodiment of the present disclosure;

[0028] Figure 18 is a schematic diagram of the field structure of a configuration sub-element according to an embodiment of the present disclosure;

[0029] Figure 19 is a schematic diagram of the field structure of site control according to an embodiment of the present disclosure;

[0030] Figure 20 is a schematic diagram of the field structure of site information according to an embodiment of the present disclosure;

[0031] Figure 21 is a flowchart of the establishment, updating and teardown of the single-link multi-access point technology according to an embodiment of the present disclosure. Detailed Implementation

[0032] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings and examples.

[0033] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0034] 1.FTTR

[0035] Fiber-to-The-Room (FTTR) technology connects wireless access points (APs) in different rooms or locations in homes or small and medium-sized enterprises using fiber optic cables, thereby providing high-bandwidth and high-reliability connections between multiple APs. It can utilize point-to-multipoint optical distribution networks to achieve connections between master control APs and slave APs.

[0036] 2. MLD discovery

[0037] In 802.11be, each AP multi-link device (MLD) announces its own operation and capability information via a beacon on each link, and also carries information about other links via Radio Network Resource (RNR). After obtaining this information, a non-AP station (STA) operating on the current link can request the AP MLD to provide specific operation and capability information of other links on the current link through a multi-link probe request (specifying the link to be requested through the AP MLD ID and link ID in the multi-link probe request). Figure 1 is a flowchart of MLD discovery in the prior art.

[0038] 3. Multi-link element

[0039] 802.11be defines a multi-link element, where common info carries common information about multiple links, and link info carries information about other links. This element is used for the discovery, association, and other processes of multi-link devices. Figure 2 shows the format of a multi-link element in the prior art, including Element ID, Length, Element ID Extension, Multi-Link Control, Common Info, and Link Info. The Link Info contains information about the other links. Figure 3 shows the format of each STA configuration sub-element of a basic multi-link element in the prior art, including Subelement ID, Length, STA Control, STA Info, and STA Profile.

[0040] 4. Multi-AP (Multi-Access Point) Collaboration Technology

[0041] The multi-access point cooperation technology in the 802.11bn standard includes:

[0042] Co-OFDMA: An access point allocates a portion of its frequency domain resources to neighboring access points.

[0043] Co-TDMA: An access point allocates a portion of its time-domain resources to neighboring access points.

[0044] Co-SR: Access points and neighboring access points collaborate to use spatial reuse technology.

[0045] Co-BF: The access point and its neighboring access points cooperate to perform beamforming, which enhances the signal-to-noise ratio (SNR) and reduces interference.

[0046] Co-RTWT: The access point negotiates RTWT information with neighboring access points to reduce the interference from overlapping basic service sets (OBSS) that may affect the RTWT window time.

[0047] Seamless roaming: The collaboration between the access point and neighboring access points ensures low latency and zero packet loss for workstations during roaming.

[0048] Coordinated Non-Primary Channel Access (Co-NPCA): In a Basic Service Set (BSS), when the primary channel is interfered with by the OBSS, communication between the access point and the workstation is switched to a secondary channel. Co-NPCA is used by access points and neighboring access points to coordinate the secondary channel, and when the primary channel is interfered with by the OBSS, they uniformly switch to the secondary channel to perform other multi-access point cooperative operations.

[0049] 5. Multiple Basic Service Set Identifier (MBSSID)

[0050] Access points within the same physical entity are called co-located access points (APs).

[0051] Within the same physical entity, access points that share the same operating channel, channel access function, and transceiver antenna are called co-hosted BSSIDs.

[0052] Based on the co-hosted BSSID, if one of the BSSIDs supports sending beacon and probe response information on behalf of other BSSIDs, then this set of BSSIDs is called MBSSID (multiple BSSID). Among them, the BSSIDs that do not send beacon and probe response are called non-transmitted BSSIDs, and the BSSIDs that send beacon and probe response are called transmitted BSSIDs.

[0053] 6. Multi-BSSID technology under multi-link conditions

[0054] Figure 4 shows multiple BSSIDs under multiple links in the prior art. As shown in Figure 4, MLD E contains BSSID-x, BSSID-p and BSSID-a, which operate on channels 1, 2 and 3 respectively. MLD F contains BSSID-q and BSSID-b, which operate on channels 2 and 3 respectively. MLD G contains BSSID-y and BSSID-r, which operate on channels 1 and 2 respectively. MLD H contains BSSID-c, which operates on channel 3.

[0055] BSSID-x and BSSID-y constitute an MBSSID, where BSSID-y is the transmitted BSSID. The beacon and probe response will carry information about BSSID-x. BSSID-p, BSSID-q, and BSSID-r constitute an MBSSID, where BSSID-q is the transmitted BSSID. The beacon and probe response will carry information about BSSID-p and BSSID-r. BSSID-a, BSSID-b, and BSSID-c constitute an MBSSID, where BSSID-a is the transmitted BSSID. The beacon and probe response will carry information about BSSID-b and BSSID-c.

[0056] 7. Problems with existing technologies

[0057] In the 802.11be, Ultra High Reliability (UHR) and current 802.11bn stages, multi-AP (access point) cooperation technology has been repeatedly discussed and studied in the standards group. The currently hotly debated sub-technologies include: Coordinated Time Division Multiple Access (co-TDMA), Coordinated Orthogonal Frequency Division Multiple Access (co-OFDMA), Coordinated Spatial Reuse (co-SR), Coordinated Beam Forming (co-BF), and Coordinated Restricted Target Wake Time (co-RTWT). The aforementioned technologies, in their specific workflow, include: multi-AP discovery, multi-AP setup, multi-AP coordinated agreement, pre-TX (transmission) (steps before multi-AP transmission), and some or all of the operations in multi-AP transmission.

[0058] Most existing technologies focus on a single technical direction. Figure 5 shows the operation flowchart of multiple collaborative technologies in existing technologies. 802.11bn devices can support more than one multi-AP (multi-access point) collaboration technology, and 802.11bn product forms can include single-link or multi-link devices. Therefore, the following problems exist:

[0059] 1) When multiple multi-AP technologies are used for collaboration between link-level APs, the multi-AP setup process needs to be performed separately. For example, if an AP supports both co-TDMA and co-RTWT, the setup process for co-TDMA and co-RTWT needs to be completed separately when APs collaborate on the above technologies. Multiple frame exchanges result in air interface redundancy.

[0060] 2) Multi-link devices (MLDs) may support the same or different multi-AP cooperation technologies on different links. When the above cooperation technologies need to be used on multiple links, a specific multi-AP setup process needs to be performed on each link. For example, if AP MLD 1 and AP MLD 2 support co-TMDA and co-SR on link 1 and co-TDMA and co-RTWT on link 2, then AP MLD 1 and AP MLD 2 need to complete the setup process for co-TDMA and co-SR on link 1 and the setup process for co-TDMA and co-RTWT on link 2 respectively. The frame interaction of multiple links further leads to air interface redundancy.

[0061] 3) In single-link and multi-link scenarios, there may be multiple multi-access point collaboration technologies that perform information updates simultaneously. For example, on link 1 of AP MLD 1, co-TDMA sleep information needs to be updated, and on link 2, co-RTWT RTWT time window needs to be updated. Independent update processes can also lead to air interface redundancy.

[0062] To address the problems existing in the prior art, this disclosure provides a method for establishing a multi-access point cooperation technology. The method embodiments provided in this disclosure can be executed in a mobile terminal, computer terminal, or similar computing device. Taking a mobile terminal as an example, FIG6 is a hardware structure block diagram of a mobile terminal using the method for establishing a multi-access point cooperation technology according to an embodiment of this disclosure. As shown in FIG6, the mobile terminal may include one or more (only one is shown in FIG6) processors 602 (processor 602 may include, but is not limited to, processing devices such as microprocessors MCUs or programmable logic devices FPGAs) and a memory 604 for storing data. The mobile terminal may also include a transmission device 606 for communication functions and an input / output device 608. Those skilled in the art will understand that the structure shown in FIG6 is merely illustrative and does not limit the structure of the mobile terminal. For example, the mobile terminal may include more or fewer components than shown in FIG6, or have a different configuration than shown in FIG6.

[0063] The memory 604 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the multi-access point cooperation technology establishment method in this embodiment of the present disclosure. The processor 602 executes various functional applications and data processing by running the computer program stored in the memory 604, thereby implementing the above-described method. The memory 604 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 604 may further include memory remotely located relative to the processor 602, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0064] The transmission device 606 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 606 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 606 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0065] This embodiment provides a method for establishing a multi-access point collaboration technology running on the aforementioned mobile terminal. Figure 7 is a flowchart of the method for establishing a multi-access point collaboration technology according to an embodiment of this disclosure. As shown in Figure 7, the process includes the following steps:

[0066] In step S702, the first device sends a third message to the second device requesting the establishment of a multi-access point cooperation technology, wherein the third message contains a request to establish one or more multi-access point cooperation technologies.

[0067] In this embodiment, the first device and the second device can be single-link devices or multi-link devices.

[0068] In this embodiment, in the case of a single link, the first device sends a third message to the second device requesting the establishment of a multi-access point cooperation technology. The third message contains a request to establish one or more multi-access point cooperation technologies, or a request to establish one or more multi-access point cooperation technologies on the same channel as other access points that are in the same multi-basic service set identifier (MBSSID) or co-hosted BSSID or co-located AP as the first device.

[0069] In a multi-link scenario, the first access point belonging to the first device sends a third message to the fourth access point belonging to the second device requesting the establishment of a multi-access point cooperation technology. The third message includes at least one of the following: a request to establish one or more multi-access point cooperation technologies on the current link; a request to establish one or more multi-access point cooperation technologies on one or more other links; a request to establish one or more multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP; or a request to establish one or more multi-access point cooperation technologies on the current link or at least one other link as the first access point belonging to the first or second access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP.

[0070] In step S704, the first device receives a fourth message from the second device in response to the third message, wherein the fourth message contains an establishment response for one or more multi-access point cooperation technologies.

[0071] In this embodiment, in the case of a single link, the first device receives a fourth message from the second device in response to the third message. The fourth message contains an establishment response of one or more multi-access point cooperation technologies, or an establishment response of one or more multi-access point cooperation technologies on the same channel as the first device, which is in the same multi-basic service set identifier (MBSSID) or co-hosted BSSID or co-located AP.

[0072] In a multi-link scenario, the first access point belonging to the first device receives a fourth message from the fourth access point belonging to the second device in response to the third message. The fourth message includes at least one of the following: a response to the establishment of one or more multi-access point cooperation technologies on the current link; a response to the establishment of one or more multi-access point cooperation technologies on one or more other links; a response to the establishment of one or more multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP; or a response to the establishment of one or more multi-access point cooperation technologies on the current link or at least one other link as the first access point belonging to the first or second access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP.

[0073] In one embodiment, the first device may send a fifth message to the second device to request an update of the multi-access point cooperation technology, or the first device may receive a fifth message from the second device requesting an update of the multi-access point cooperation technology, wherein the fifth message contains an update request for one or more multi-access point cooperation technologies.

[0074] In this embodiment, in the case of a single link, the first device sends a fifth message to the second device requesting an update of the multi-access point cooperation technology. The fifth message contains an update request for one or more multi-access point cooperation technologies, or an update request for one or more multi-access point cooperation technologies from other access points on the same channel as the first device that share the same Multiple Basic Service Set Identifier (MBSSID), Co-hosted Basic Service Set Identifier (co-hosted BSSID), or Co-located Access Point (co-located AP). Alternatively, the first device receives a fifth message from the second device requesting an update of the multi-access point cooperation technology, wherein the fifth message contains an update request for one or more multi-access point cooperation technologies, or an update request for one or more multi-access point cooperation technologies from other access points on the same channel as the first device that share the same Multiple Basic Service Set Identifier (MBSSID), Co-hosted Basic Service Set Identifier (co-hosted BSSID), or Co-located Access Point (co-located AP).

[0075] In a multi-link scenario, the first access point belonging to the first device sends a fifth message requesting an update of the multi-access point cooperation technology to the fourth access point belonging to the second device. This fifth message includes at least one of the following: an update request for one or more multi-access point cooperation technologies on the current link; an update request for one or more multi-access point cooperation technologies on one or more other links; an update request for one or more multi-access point cooperation technologies on the same channel as the first device's first access point, sharing the same MBSSID or co-hosted BSSID or co-located AP; or an update request for one or more multi-access point cooperation technologies on the same MBSSID or co-hosted BSSID or co-located AP as the first device's first or second access point. The following is a request from other access points of the AP to update one or more multi-access point cooperation technologies on the current link or at least one other link; or the first access point of the first device receives a fifth message from the fourth access point of the second device requesting an update of the multi-access point cooperation technology, wherein the fifth message includes at least one of the following: a request to update one or more multi-access point cooperation technologies on the current link; a request to update one or more multi-access point cooperation technologies on one or more other links; a request to update one or more multi-access point cooperation technologies on the same channel as the first access point of the AP with the same MBSSID or co-hosted BSSID or co-located access point; or a request to update one or more multi-access point cooperation technologies on the current link or at least one other link as the first access point of the AP with the same MBSSID or co-hosted BSSID or co-located access point.

[0076] In one embodiment, the first device may also send a sixth message to the second device to request the removal of the multi-access point cooperation technology, or the first device may receive a sixth message from the second device requesting the removal of the multi-access point cooperation technology, wherein the sixth message contains a removal request for one or more multi-access point cooperation technologies.

[0077] In this embodiment, in the case of a single link, the first device sends a sixth message to the second device requesting the removal of a multi-access point cooperation technology. The sixth message contains a removal request for one or more multi-access point cooperation technologies, or a removal request for one or more multi-access point cooperation technologies on the same channel as other access points sharing the same Multiple Basic Service Set Identifier (MBSSID), Co-hosted Basic Service Set Identifier (co-hosted BSSID), or Co-located Access Point (co-located AP). Alternatively, the first device receives a sixth message from the second device requesting the removal of a multi-access point cooperation technology, where the sixth message contains a removal request for one or more multi-access point cooperation technologies, or a removal request for one or more multi-access point cooperation technologies on the same channel as other access points sharing the same Multiple Basic Service Set Identifier (MBSSID), Co-hosted Basic Service Set Identifier (co-hosted BSSID), or Co-located Access Point (co-located AP).

[0078] In a multi-link scenario, the first access point belonging to the first device sends a sixth message requesting the removal of multi-access point cooperation technology to the fourth access point belonging to the second device. This sixth message includes at least one of the following: a request to remove one or more multi-access point cooperation technologies on the current link; a request to remove one or more multi-access point cooperation technologies on one or more other links; a request to remove one or more multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID, co-hosted BSSID, or co-located AP; or a request to remove one or more multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID, co-hosted BSSID, or co-located AP. The message indicates that the AP's other access points on the current link or at least one other link have requested the removal of one or more multi-access point cooperation technologies; or the first access point of the first device receives a sixth message from the fourth access point of the second device requesting the removal of multi-access point cooperation technologies, wherein the sixth message contains at least one of the following: a request to remove one or more multi-access point cooperation technologies on the current link; a request to remove one or more multi-access point cooperation technologies on one or more other links; a request to remove one or more multi-access point cooperation technologies on the same channel as the first access point of the first device's other access points that share the same MBSSID or co-hosted BSSID or co-located access point; or a request to remove one or more multi-access point cooperation technologies on the current link or at least one other link as the first access point of the first device's other access points that share the same MBSSID or co-hosted BSSID or co-located access point.

[0079] In one embodiment, before performing step S702, the first device may send a first message to the second device to declare its support capability for multi-access point collaboration technology, and the first device receives a second message from the second device to declare its support capability for multi-access point collaboration technology.

[0080] In this embodiment, in the single-link scenario, the first device sends a first message to the second device to declare its support for multi-access point collaboration technology. In the multi-link scenario, multiple access points belonging to the first device send first messages to multiple access points belonging to the second device on multiple links to declare their support for multi-access point collaboration technology.

[0081] In this embodiment, in the single-link scenario, the first device receives a second message from the second device declaring its support for multi-access point collaboration technology. In the multi-link scenario, multiple access points belonging to the first device receive second messages from multiple access points belonging to the second device on multiple links, declaring their support for multi-access point collaboration technology.

[0082] In this embodiment, in the case of a single link, the first message includes at least one of the following: the support capability of multi-access point cooperation technology for the current link, the support capability of multi-access point cooperation technology for at least one other link, and the support capability of multi-access point cooperation technology for other access points on the same channel as the first device that are in the same multi-basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP).

[0083] In the case of multiple links, the first message includes at least one of the following: the ability to support multi-access point cooperation technology on the current link; the ability to support multi-access point cooperation technology on at least one other link; the ability to support multi-access point cooperation technology on the same channel as other access points belonging to the first access point of the first device that share the same MBSSID or co-hosted BSSID or co-located AP; or the ability to support multi-access point cooperation technology on the current link or at least one other link as other access points belonging to the first access point or second access point of the first device that share the same MBSSID or co-hosted BSSID or co-located AP.

[0084] In the case of a single link, the second message includes at least one of the following: the ability to support multi-access point cooperation technology on the current link, the ability to support multi-access point cooperation technology on at least one other link, and the ability to support multi-access point cooperation technology on the same channel for other access points that are in the same multi-basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP) as the second device.

[0085] In the case of multiple links, the second message includes at least one of the following: the ability to support multi-access point cooperation technology on the current link; the ability to support multi-access point cooperation technology on at least one other link; the ability to support multi-access point cooperation technology on the same channel as the fourth access point to which the second device belongs, which shares the same MBSSID or co-hosted BSSID or co-located AP; or the ability to support multi-access point cooperation technology on the current link or at least one other link as the fourth or fifth access point to which the second device belongs, which shares the same MBSSID or co-hosted BSSID or co-located AP.

[0086] In one embodiment, the first, second, third, or fourth message may be a management frame, a control frame, or a data frame.

[0087] In one embodiment, in the case of a single link, the third or fourth message includes at least one of the following fields: element ID, length, multi-access point bitmap, and multi-access point information. The multi-access point bitmap field includes a correspondence between multiple bits and one or more multi-access point cooperation technologies. The multi-access point information field includes the feature configuration of one or more multi-access point cooperation technologies. The feature configuration of each multi-access point cooperation technology includes at least one of the following fields: sub-element ID, length, multi-access point status, and optional sub-element.

[0088] Alternatively, in the case of a single link, the third or fourth message shall include at least one of the following fields: element ID, length, and multi-access point information; wherein the multi-access point information field includes feature configurations of one or more multi-access point collaboration technologies, and each feature configuration of a multi-access point collaboration technology shall include at least one of the following fields: sub-element ID, length, multi-access point feature ID, multi-access point status, and optional sub-element; the multi-access point feature ID field indicates the correspondence between the multi-access point feature ID and the multi-access point collaboration technology.

[0089] Alternatively, in the case of a single link, the third or fourth message includes at least one of the following fields: element ID, length, multi-access point bitmap, and multi-access point information; wherein, the multi-access point bitmap field includes a correspondence between multiple bits and one or more multi-access point cooperation technologies; if the multi-access point bitmap field has a specific value, the multi-access point information field includes sub-elements of one or more multi-access point cooperation technologies, and the sorting order of the sub-elements of the multi-access point cooperation technologies is consistent with the sorting order of the correspondence; the sub-elements of the multi-access point cooperation technologies include other information about the multi-access point cooperation technologies.

[0090] In the third message, the multi-access point status field is a reserved field, and in the fourth message, the multi-access point status field indicates the response result of whether one or more multi-access point collaboration technologies have been successfully established; the optional sub-element fields include other information about the establishment of multi-access point collaboration technologies.

[0091] In one embodiment, in the case of multiple links, the third or fourth message includes at least one of the following fields: element ID, length, element ID extension, multi-link control, public information, and link information; wherein, the multi-link control field includes at least one of the following fields: type, reserved, and exist bitmap; the public information field includes at least one of the following fields: public information length and access point multi-link device MAC address; the link information field includes the field: configuration sub-element of one or more sites of the multi-access point multi-link element; the configuration sub-element field of one or more sites includes at least one of the following fields: sub-element ID, length, site control, site information, and site configuration; the site control field includes at least one of the following fields: link ID, site MAC address exist, and reserved; and the site information field includes at least one of the following fields: site information length and site MAC address.

[0092] In this embodiment, the presence of a site MAC address indicates whether the site information contains a site MAC address.

[0093] In this embodiment, the multi-link control field also includes a type subfield value. When the type subfield value is a specific value, the multi-link element variant is named multi-access point or access point collaboration.

[0094] In this embodiment, the site configuration field includes at least one of the following fields: element ID, length, multi-access point bitmap, and multi-access point information. The multi-access point bitmap field includes the correspondence between multiple bits and one or more multi-access point collaboration technologies. The multi-access point information field includes the feature configuration of one or more multi-access point collaboration technologies. The feature configuration of each multi-access point collaboration technology includes at least one of the following fields: sub-element ID, length, multi-access point status, and optional sub-element.

[0095] Alternatively, the site configuration fields may include at least one of the following fields: element ID, length, and multi-access point information; wherein the multi-access point information field includes feature configurations for one or more multi-access point collaboration technologies, and each feature configuration for a multi-access point collaboration technology may include at least one of the following fields: sub-element ID, length, multi-access point feature ID, multi-access point status, and optional sub-element; the multi-access point feature ID field indicates the correspondence between the multi-access point feature ID and the multi-access point collaboration technology.

[0096] Alternatively, the site configuration fields may include at least one of the following fields: element ID, length, multi-access point bitmap, and multi-access point information; wherein, the multi-access point bitmap field includes the correspondence between multiple bits and one or more multi-access point collaboration technologies; when the multi-access point bitmap field has a specific value, the multi-access point information field includes sub-elements of one or more multi-access point collaboration technologies, and the sorting order of the sub-elements of the multi-access point collaboration technologies is consistent with the sorting order of the correspondence; the sub-elements of the multi-access point collaboration technologies include other information about the multi-access point collaboration technologies.

[0097] In one embodiment, in the case of a single link, the fourth message includes multiple status code fields to indicate the establishment status of the multi-access point collaboration technology for each request.

[0098] In this embodiment, when there is mutual exclusion in the multi-access point cooperation technology, the mutually exclusive multi-access point cooperation technologies in the multi-access point bitmap field are not simultaneously of the same specific value, or when there is mutual exclusion in the multi-access point cooperation technology, the mutually exclusive multi-access point cooperation technologies in the multi-access point bitmap field are simultaneously of the same specific value, and the reason for rejection is indicated in the status code field of the fourth message or in the multi-access point status field as mutual exclusion of multi-access point cooperation technologies.

[0099] Through the above steps, the first device sends a third message to the second device requesting the establishment of a multi-access point cooperation (MIPC) technology. This third message contains a request to establish one or more MIPC technologies. The first device then receives a fourth message from the second device in response to the third message, which contains a response to the establishment of one or more MIPC technologies. This solves the problem of redundancy caused by multiple air interface interactions in MIPC technologies in related technologies, thereby improving the interaction efficiency of MIPC technologies.

[0100] Figure 8 is another flowchart of a method for establishing a multi-access point cooperation technology according to an embodiment of the present disclosure. As shown in Figure 8, the process includes the following steps:

[0101] In step S802, the second device receives a third message from the first device requesting the establishment of a multi-access point cooperation technology, wherein the third message contains a request to establish one or more multi-access point cooperation technologies.

[0102] In this embodiment, the first device and the second device can be single-link devices or multi-link devices.

[0103] In step S804, the second device sends a fourth message to the first device in response to the third message, wherein the fourth message contains an establishment response for one or more multi-access point cooperation technologies.

[0104] In one embodiment, the second device may send a fifth message requesting an update to the multi-access point cooperation technology to the first device, or the second device may receive a fifth message requesting an update to the multi-access point cooperation technology sent by the first device, wherein the fifth message contains an update request for one or more multi-access point cooperation technologies.

[0105] In one embodiment, the second device may also send a sixth message requesting the removal of the multi-access point cooperation technology to the first device, or the second device may receive a sixth message requesting the removal of the multi-access point cooperation technology sent by the first device, wherein the sixth message contains a removal request for one or more multi-access point cooperation technologies.

[0106] In one embodiment, before performing step S802, the second device sends a first message to the first device to declare its support for multi-access point collaboration technology, and the second device receives a second message from the first device to declare its support for multi-access point collaboration technology.

[0107] In one embodiment, the first, second, third, or fourth message may be a management frame, a control frame, or a data frame.

[0108] Through the above steps, the second device receives a third message from the first device requesting the establishment of a multi-access point cooperation (MIPC) technology. This third message contains a request to establish one or more MIPC technologies. The second device then sends a fourth message to the first device in response to the third message, containing a response to the establishment of one or more MIPC technologies. This solves the problem of redundancy caused by multiple air interface interactions in MIPC technologies in related technologies, thereby reducing redundancy and improving the interaction efficiency of MIPC technologies.

[0109] Figure 9 is a flowchart of a method for establishing a single-link multi-access point cooperation technology according to an embodiment of the present disclosure. As shown in Figure 9, the process includes the following steps:

[0110] Step S901: The first device (AP1) sends a first message to the second device (AP2) to declare support for multi-access point collaboration technology.

[0111] The first device and the second device can be single-link devices or multi-link devices.

[0112] In step S902, the second device (AP2) sends a second message to the first device (AP1) declaring support for multi-access point collaboration technology.

[0113] The first message may include at least one of the following: the support capability of multi-access point cooperation technology for the current link, the support capability of multi-access point cooperation technology for at least one other link, and the support capability of multi-access point cooperation technology for other access points on the same channel as the first device that are in the same multi-basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP) (as shown in Figure 4, BSSID-x may carry the support capability of BSSID-y).

[0114] The second message may include at least one of the following: the support capability of multi-access point cooperation technology for the current link, the support capability of multi-access point cooperation technology for at least one other link, and the support capability of multi-access point cooperation technology for other access points on the same channel as the second device that are in the same multi-basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP) (as shown in Figure 4, BSSID-y may carry the support capability of BSSID-x).

[0115] Step S903: The first device sends a third message to the second device requesting the establishment of multi-access point cooperation technology;

[0116] The third message contains a request to establish one or more multi-access point cooperation technologies, or a request to establish one or more multi-access point cooperation technologies on the same channel as the first device, which is in the same multi-basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP). (This can be seen in Figure 4; for example, BSSID-x can carry an establishment request for BSSID-y.)

[0117] Step S904: The second device sends a fourth message to the first device in response to the establishment of the multi-access point cooperation technology;

[0118] The fourth message includes a response to the establishment of one or more multi-access point cooperation technologies, or a response to the establishment of one or more multi-access point cooperation technologies on the same channel as the first device, which is in the same multi-basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP).

[0119] Figure 10 is a schematic diagram of the field structure of a multi-access point element according to an embodiment of the present disclosure. As shown in Figure 10, it includes one of the following fields: Element ID, Length, Multi-AP bitmap, and Multi-AP Info. The Multi-AP bitmap field includes the correspondence between multiple bits and one or more multi-access point cooperation technologies, as shown in Table 1, which shows the correspondence between bits 0 to 15 of the Multi-AP bitmap and specific Multi-AP technology features. A corresponding bit position of 1 (or other specific values, which are not limited herein) indicates that the Multi-AP Info contains that technology information; otherwise, it does not.

[0120] Table 1

[0121] The multi-access point information field includes feature configurations for one or more multi-access point collaboration technologies. Figure 11 is a schematic diagram of the field structure of the feature configurations according to an embodiment of this disclosure. As shown in Figure 11, each feature configuration for a multi-access point collaboration technology includes at least one of the following fields: Subelement ID, Length, Multi-AP Status, and Optional subelements. This field is reserved when the Multi-AP status is included in a multi-access point technology establishment response message other than the one in the multi-access point technology establishment response message. When included in the multi-access point technology establishment response message, this field indicates the response result; a success value indicates successful establishment, otherwise, establishment has failed. Optional subelements contain other information used for multi-access point technology establishment. Table 2 lists the subelement IDs of the multi-access point information for the multi-access point elements.

[0122] Table 2

[0123] Figure 12 is another schematic diagram of the field structure of a multi-access point element according to an embodiment of the present disclosure. As shown in Figure 12, it includes at least one of the following fields: Element ID, Length, and Multi-AP Info, wherein the Multi-AP Info field includes feature configurations of one or more multi-access point collaboration technologies.

[0124] Figure 13 is another schematic diagram of the field structure of the feature configuration according to an embodiment of the present disclosure. As shown in Figure 13, the feature configuration of each multi-access point collaboration technology includes at least one of the following fields: Subelement ID, Length, Multi-AP feature ID, Multi-AP Status, and Optional subelements. This field is reserved when the Multi-AP status is included in the multi-access point technology establishment request message. When included in the multi-access point technology establishment response message, this field indicates the response result; a success value indicates successful establishment, otherwise, establishment has failed. Optional subelements contain other information for the multi-access point technology. The Multi-Access Point Feature ID field represents the correspondence between the Multi-Access Point Feature ID and the multi-access point collaboration technology, as shown in Table 3.

[0125] Table 3

[0126] Figure 14 is a schematic diagram of the multi-access point information field structure of a multi-access point element according to an embodiment of the present disclosure. As shown in Figure 14, when the bit position corresponding to the Multi-AP technology feature in the Multi-AP bitmap of the Multi-AP element in Figure 10 is 1 (or other specific value) (the correspondence is shown in Table 1), the Multi-AP Info contains the sub-element corresponding to that technology. Conversely, when the corresponding bit position is 0 (or other specific value), the Multi-AP Info does not contain the sub-element corresponding to that element. The sub-element in the Multi-AP Info is arranged in the same order as the Multi-AP bitmap, in ascending order of bit position. The sub-element contains other information for that multi-access point technology.

[0127] The third or fourth message may contain information as shown in Figure 10, Table 1, Table 2, or Figure 11, or may contain Figure 12, Table 2, Figure 13, or Table 3, or may contain Figure 10, Table 1, or Figure 14.

[0128] The fourth message contains multiple independent status code fields, each representing the status of the requested multi-access point technology establishment.

[0129] In the third message, some technologies in the Multi-AP bitmap are mutually exclusive and cannot be set to 1 (or other specific values) at the same time, or are allowed to be set to 1 (or other specific values) at the same time. However, in the fourth message, the reason for the rejection is indicated by the status code field or the Multi-AP Status field in Figure 11 or Figure 13, which is that the technologies are mutually exclusive.

[0130] Step S905: The first device or the second device sends a fifth message to the other party to update the established multi-access point cooperation technology;

[0131] Specifically, the first device sends a fifth message to the second device requesting an update of the multi-access point cooperation technology. This fifth message contains an update request for one or more multi-access point cooperation technologies, or an update request for one or more multi-access point cooperation technologies from other access points on the same channel as the first device that share the same multiple basic service set identifier (MBSSID), co-hosted basic service set identifier (co-hosted BSSID), or co-located access point (co-located AP). Alternatively, the first device receives a fifth message from the second device requesting an update of the multi-access point cooperation technology. This fifth message contains an update request for one or more multi-access point cooperation technologies, or an update request for one or more multi-access point cooperation technologies from other access points on the same channel as the first device that share the same multiple basic service set identifier (MBSSID), co-hosted basic service set identifier (co-hosted BSSID), or co-located access point (co-located AP) (refer to Figure 4; for example, BSSID-x may carry an update request for BSSID-y).

[0132] Step S906: The first device or the second device sends a sixth message to the other party to dismantle the established multi-access point cooperation technology;

[0133] Specifically, the first device sends a sixth message to the second device requesting the removal of a multi-access point cooperative technology (MAPT). This sixth message contains a removal request for one or more MAPTs, or a removal request for one or more MAPTs from other access points on the same channel as the first device that share the same multiple basic service set identifier (MBSSID), co-hosted basic service set identifier (co-hosted BSSID), or co-located access point (co-located AP). Alternatively, the first device receives a sixth message from the second device requesting the removal of a MAPT, containing a removal request for one or more MAPTs, or a removal request for one or more MAPTs from other access points on the same channel as the first device that share the same multiple basic service set identifier (MBSSID), co-hosted basic service set identifier (co-hosted BSSID), or co-located access point (co-located AP) (refer to Figure 4; for example, BSSID-x may carry a removal request for BSSID-y).

[0134] The third, fourth, fifth, or sixth message can be a management frame, a control frame, or a data frame. The fifth or sixth message can be sent by either the first or second device.

[0135] Figure 15 is a flowchart of a method for establishing a multi-link multi-access point cooperation technology according to an embodiment of the present disclosure. As shown in Figure 15, the process includes the following steps:

[0136] In step S1501, the first device and the second device send a first message and a second message to each other on multiple links respectively to declare support for multi-access point collaboration technology.

[0137] The first message includes at least one of the following: the support capability of multi-access point cooperation technology on the current link; the support capability of multi-access point cooperation technology on at least one other link; the support capability of multi-access point cooperation technology on the same channel as the first access point (AP1) to which the first device belongs; or the support capability of multi-access point cooperation technology on the current link or at least one other link for other access points to which the first access point (AP1) to which the first device belongs; or the support capability of multi-access point cooperation technology on the current link or at least one other link for other access points to which the first access point (AP1) to which the first device belongs or the second access point (AP2) belongs; (as shown in Figure 4, for example, BSSID-x can carry the support capability of BSSID-y, or BSSID-x can carry the support capability of BSSID-r, or BSSID-x can carry the support capability of BSSID-q, or BSSID-x can carry the support capability of BSSID-b).

[0138] The second message includes at least one of the following: the ability to support multi-access point cooperation technology on the current link; the ability to support multi-access point cooperation technology on at least one other link; the ability to support multi-access point cooperation technology on the same channel as the fourth access point (AP4) to which the second device belongs; or the ability to support multi-access point cooperation technology on the current link or at least one other link as the fourth access point (AP4) to which the second device belongs; or the ability to support multi-access point cooperation technology on the current link or at least one other link as the fourth access point (AP4) or the fifth access point (AP5) to which the second device belongs (as shown in Figure 4, for example, BSSID-y can carry the ability to support BSSID-x, or BSSID-y can carry the ability to support BSSID-p, or BSSID-y can carry the ability to support BSSID-q, or BSSID-y can carry the ability to support BSSID-b).

[0139] In step S1502, the first access point (AP1) of the first device sends a third message to the fourth access point (AP4) of the second device to request the establishment of multi-access point cooperation technology.

[0140] The third message includes at least one of the following: a request to establish one or more multi-access point cooperation technologies on the current link; a request to establish one or more multi-access point cooperation technologies on one or more other links; a request to establish one or more multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP; or a request to establish one or more multi-access point cooperation technologies on the current link or at least one other link as the first access point or belonging to the first or second access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP (as shown in Figure 4, for example, BSSID-x can carry an establishment request for BSSID-y, or BSSID-x can carry an establishment request for BSSID-r, or BSSID-x can carry an establishment request for BSSID-q, or BSSID-x can carry an establishment request for BSSID-b).

[0141] In step S1503, the fourth access point (AP4) of the second device sends a fourth message to the first access point (AP1) of the first device to respond to the establishment of the multi-access point cooperation technology.

[0142] The fourth message includes at least one of the following: a response to the establishment of one or more multi-access point cooperation technologies on the current link; a response to the establishment of one or more multi-access point cooperation technologies on another link or more links; a response to the establishment of one or more multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP; or a response to the establishment of one or more multi-access point cooperation technologies on the current link or at least another link as to the first access point or second access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP.

[0143] Figure 16 is a schematic diagram of the field structure of a multi-link element according to an embodiment of the present disclosure. As shown in Figure 16, it includes at least one of the following fields: Element ID, Length, Element ID Extension, Multi-Link Control, Common Info, and Link Info. The Multi-Link Control field includes at least one of the following fields: Type, Reserved, and Presence Bitmap.

[0144] Figure 17 is a schematic diagram of the field structure of common information according to an embodiment of the present disclosure. As shown in Figure 17, the common information field includes at least one of the following fields: Common Info Length and Access Point Multi-Link Device MAC Address.

[0145] The link information field includes the field: configuration sub-element of one or more sites of the multi-access point multi-link element. Figure 18 is a schematic diagram of the field structure of the configuration sub-element according to an embodiment of the present disclosure. As shown in Figure 18, the configuration sub-element field of one or more sites includes at least one of the following fields: Subelement ID, Length, STA Control, STA Info, and STA Profile. The site configuration may include a multi-access point element, as shown in Figure 10, Table 1, Table 2, and Figure 11, or Figure 12, Table 2, Figure 13, and Table 3, or Figure 10, Table 1, and Figure 14.

[0146] Figure 19 is a schematic diagram of the field structure of the site control according to an embodiment of the present disclosure. As shown in Figure 19, the site control field includes at least one of the following fields: Link ID, STA MAC Address present, and Reserved. STA MAC Address present indicates whether the site information (STA info) contains the STA MAC address. A value of 1 (or other specific value) indicates that the STA MAC address is present, and a value of 0 (or other specific value) indicates that the STA MAC address is not present.

[0147] Figure 20 is a schematic diagram of the field structure of site information according to an embodiment of the present disclosure. As shown in Figure 20, the site information field includes at least one of the following fields: Site Information Length (STA Info Length) and Site MAC Address (STA MAC Address). The STA MAC address represents the MAC address of the reported access point.

[0148] The multi-link control field also includes a type subfield value. When the type subfield value is a specific value, the multi-link element variant is named multi-AP or AP coordination. As shown in Table 4, when the type subfield value is set to 5 (or other specific value), the corresponding multi-link element variant can be named multi-AP or AP coordination.

[0149] Table 4

[0150] The information that the third and fourth messages can contain is shown in Figures 16-20 and Table 4.

[0151] In step S1504, the first access point (AP1) or the fourth access point (AP4) sends a fifth message to the other party to update the established multi-access point cooperation technology.

[0152] In this process, the first access point (AP1) of the first device sends a fifth message to the fourth access point (AP4) of the second device, requesting an update of the multi-access point cooperation technology. The fifth message includes at least one of the following: an update request for one or more multi-access point cooperation technologies on the current link; an update request for one or more multi-access point cooperation technologies on one or more other links; an update request for one or more multi-access point cooperation technologies on the same channel as the first access point (AP1) of the first device, sharing the same MBSSID or co-hosted BSSID or co-located AP; or an update request for one or more multi-access point cooperation technologies on the same MBSSID or co-hosted BSSID or co-located AP as the first access point (AP1) of the first device; or an update request for one or more multi-access point cooperation technologies on the same channel as the first access point (AP1) of the first device or the second access point (AP2). Other access points of the AP request an update request for one or more multi-access point cooperation technologies on the current link or at least one other link; or the first access point of the first device receives a fifth message from the fourth access point (AP4) of the second device requesting an update of the multi-access point cooperation technology, wherein the fifth message includes at least one of the following: an update request for one or more multi-access point cooperation technologies on the current link; an update request for one or more multi-access point cooperation technologies on one or more other links; an update request for one or more multi-access point cooperation technologies on the same channel as the first access point (AP1) of the first device, or an update request for one or more multi-access point cooperation technologies on the same channel as the first access point (AP1) of the first device, or an update request for one or more multi-access point cooperation technologies on the same channel as the first access point (AP1) of the first device, or an update request for one or more multi-access point cooperation technologies on the same channel as the first access point (AP1) of the first device, or an update request for one or more multi-access point cooperation technologies on the same channel as the first access point (AP1) of the first device, or an update request for one or more multi-access point cooperation technologies on the same channel as the first access point (AP2 ... Update requests from other access points of the AP on the current link or at least one other link using one or more multi-access point cooperation technologies (as shown in Figure 4, for example, BSSID-x can carry an update request for BSSID-y, or BSSID-x can carry an update request for BSSID-r, or BSSID-x can carry an update request for BSSID-q, or BSSID-x can carry an update request for BSSID-b).

[0153] Step S1505: The first access point (AP1) or the fourth access point (AP4) sends a sixth message to the other party to dismantle the establishment of the multi-access point cooperation technology.

[0154] In this process, the first access point (AP1) of the first device sends a sixth message to the fourth access point (AP4) of the second device requesting the removal of a multi-access point cooperation (MAP) technology. The sixth message includes at least one of the following: a request to remove one or more MAP technologies on the current link; a request to remove one or more MAP technologies on one or more other links; a request to remove one or more MAP technologies on the same channel as the first access point (AP1) of the first device, either using the same MBSSID or co-hosted BSSID or co-located AP; or a request to remove one or more MAP technologies on the same channel as the first access point (AP1) of the first device, using the same MBSSID or co-hosted BSSID or co-located AP. The request to remove one or more multi-access point cooperation technologies (MAPs) from other access points of the AP on the current link or at least one other link; or the first access point of the first device receiving a sixth message from the fourth access point (AP4) of the second device requesting the removal of MAPs, wherein the sixth message contains at least one of the following: a request to remove one or more MAPs on the current link; a request to remove one or more MAPs on one or more other links; a request to remove one or more MAPs on the same channel as the first access point (AP1) of the first device, or a request to remove one or more MAPs on the same channel as the first access point (AP1) of the first device, or a request to remove one or more MAPs on the same channel as the first access point (AP1) of the first device, or a request to remove one or more MAPs on the same channel as the first access point (AP1) of the first device, or a request to remove one or more MAPs on the same channel as the first access point (AP1) of the first device, or a request to remove one or more MAPs on the same channel as the first access point (AP1) of the first device, or a request to remove one or more MAPs on the same channel as the first access point (AP1) of the first device, or a request to remove one or more MAPs on the same channel as the first access point (AP2) of the first device, or a request to remove one or more MAPs on the same channel. Other access points of the AP may request the removal of one or more multi-access point cooperation technologies on the current link or at least one other link (as shown in Figure 4, for example, BSSID-x may carry a removal request for BSSID-y, or BSSID-x may carry a removal request for BSSID-r, or BSSID-x may carry a removal request for BSSID-q, or BSSID-x may carry a removal request for BSSID-b).

[0155] The third, fourth, fifth, or sixth message can be a management frame, a control frame, or a data frame. The fifth or sixth message can be sent by either the first or second device.

[0156] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solutions of this disclosure, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of this disclosure.

[0157] Example

[0158] Figure 21 is a flowchart of the establishment, updating, and teardown of the single-link multi-access point technology according to an embodiment of the present disclosure. As shown in Figure 21, it includes the following steps:

[0159] Step S2101: The multi-access point cooperative technology establishment request carries the multi-access point element shown in Figure 10, wherein bits 0, 2, 3, and 4 in the multi-access point bitmap are set to 1, and the others are set to 0, indicating a request to establish co-TDMA, co-SR, co-BF, and co-RTWT multi-access point cooperative technologies.

[0160] In step S2102, the multi-access point cooperative technology establishment response carries the multi-access point element shown in Figure 10. The multi-AP status of co-TDMA, co-SR, co-BF, and co-RTWT in the feature configuration Per-Multi-AP feature Profile format shown in Figure 11 is all 0, indicating that the establishment of co-TDMA, co-SR, co-BF, and co-RTWT is accepted.

[0161] In step S2103, the multi-access point cooperative technology update carries the multi-access point element shown in Figure 10. The feature configuration Per-Multi-AP feature Profile format shown in Figure 11 corresponding to co-RTWT and co-TDMA contains the corresponding update information, such as update information of co-RTWT service cycle and co-TDMA power saving information.

[0162] In step S2104, during the dismantling of the multi-access point cooperative technology, the multi-access point element shown in Figure 10 is carried, wherein bits 2 and 3 in the multi-access point bitmap are set to 1 and the others are set to 0, indicating the dismantling of co-SR and co-BF multi-access point cooperative technologies.

[0163] Embodiments of this disclosure also provide a computer-readable storage medium storing a computer program configured to perform the steps in any of the above method embodiments when executed.

[0164] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0165] Embodiments of this disclosure also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0166] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0167] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0168] Embodiments of this disclosure also provide a computer program product, including computer instructions that, when executed by a processor, implement the steps in any of the above method embodiments.

[0169] Embodiments of this disclosure also provide a computer program product including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the methods described in various embodiments of this disclosure.

[0170] It is obvious to those skilled in the art that the modules or steps of this disclosure described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this disclosure is not limited to any particular combination of hardware and software.

[0171] The above description is merely a preferred embodiment of this disclosure and is not intended to limit this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for establishing a multi-access point collaboration technology, comprising: The first device sends a third message to the second device requesting the establishment of a multi-access point cooperation technology, wherein the third message contains a request to establish one or more multi-access point cooperation technologies. The first device receives a fourth message from the second device in response to the third message, wherein the fourth message includes an establishment response for one or more multi-access point cooperation technologies.

2. The method according to claim 1, wherein, The method further includes: The first device sends a fifth message to the second device requesting an update to the multi-access point cooperation technology, or The first device receives the fifth message from the second device requesting an update to the multi-access point cooperation technology. The fifth message contains an update request for one or more multi-access point collaboration technologies.

3. The method according to claim 1, wherein, The method further includes: The first device sends a sixth message to the second device requesting the removal of the multi-access point cooperation technology, or The first device receives the sixth message from the second device requesting the removal of the multi-access point cooperation technology. The sixth message contains a teardown request for one or more multi-access point collaboration technologies.

4. The method according to claim 1, wherein, Before the first device sends a third message to the second device requesting the establishment of multi-access point cooperation technology, the method includes: The first device sends a first message to the second device to declare its support for the multi-access point collaboration technology; The first device receives a second message from the second device declaring its support for the multi-access point collaboration technology.

5. The method according to claim 1, wherein, In a single-link scenario, the third message sent by the first device to the second device requesting the establishment of multi-access point cooperation technology includes: The first device sends a third message to the second device requesting the establishment of a multi-access point cooperation technology, wherein the third message contains one or more requests for the establishment of a multi-access point cooperation technology, or requests for the establishment of one or more of the multi-access point cooperation technologies on the same channel as the first device, which are in the same multiple basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP).

6. The method according to claim 1, wherein, In a multi-link scenario, the third message sent by the first device to the second device requesting the establishment of multi-access point cooperation technology includes: The first access point belonging to the first device sends a third message to the fourth access point belonging to the second device requesting the establishment of a multi-access point cooperation technology. The third message includes at least one of the following: a request to establish one or more of the multi-access point cooperation technologies on the current link; a request to establish one or more of the multi-access point cooperation technologies on one or more other links; a request to establish one or more of the multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP; or a request to establish one or more of the multi-access point cooperation technologies on the current link or at least one other link as the first access point belonging to the first or second access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP.

7. The method according to claim 1, wherein, In a single-link scenario, the first device receiving a fourth message from the second device in response to the third message includes: The first device receives a fourth message from the second device in response to the third message, wherein the fourth message includes an establishment response of one or more of the multi-access point cooperation technologies, or an establishment response of one or more of the multi-access point cooperation technologies on the same channel as the first device, which are in the same multiple basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP).

8. The method according to claim 1, wherein, In a multi-link scenario, the first device receiving a fourth message from the second device in response to the third message includes: The first access point belonging to the first device receives a fourth message from the fourth access point belonging to the second device in response to the third message, wherein the fourth message includes at least one of the following: an establishment response of one or more of the multi-access point cooperation technologies on the current link; an establishment response of one or more of the multi-access point cooperation technologies on one or more other links; an establishment response of one or more of the multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP; or an establishment response of one or more of the multi-access point cooperation technologies on the current link or at least one other link as the first access point belonging to the first or second access point belonging to the first device and sharing the same MBSSID or co-hosted BSSID or co-located AP.

9. The method according to claim 3, wherein, The first device sending a sixth message requesting the removal of the multi-access point cooperation technology to the second device, or the first device receiving a sixth message requesting the removal of the multi-access point cooperation technology from the second device, includes one of the following: In a single-link scenario, the first device sends a sixth message to the second device requesting the removal of a multi-access point cooperation technology. This sixth message contains a removal request for one or more multi-access point cooperation technologies, or a removal request for one or more of the aforementioned multi-access point cooperation technologies on the same channel as the first device, sharing the same Multi-Basic Service Set Identifier (MBSSID), Co-hosted Basic Service Set Identifier (co-hosted BSSID), or Co-located Access Point (co-located AP). Alternatively, the first device receives a sixth message from the second device requesting the removal of a multi-access point cooperation technology, where the sixth message contains a removal request for one or more multi-access point cooperation technologies, or a removal request for one or more of the aforementioned multi-access point cooperation technologies on the same channel as the first device, sharing the same Multi-Basic Service Set Identifier (MBSSID), Co-hosted Basic Service Set Identifier (co-hosted BSSID), or Co-located Access Point (co-located AP). In a multi-link scenario, the first access point belonging to the first device sends a sixth message requesting the removal of multi-access point cooperation technology to the fourth access point belonging to the second device. This sixth message includes at least one of the following: a removal request for one or more of the multi-access point cooperation technologies on the current link; a removal request for one or more of the multi-access point cooperation technologies on one or more other links; a removal request for one or more of the multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID, co-hosted BSSID, or co-located AP; or a removal request for one or more of the multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID, co-hosted BSSID, or co-located AP. The request to remove one or more of the multi-access point cooperation technologies (MALT) on the current link or at least one other link by other access points of the AP; or the first access point of the first device receives a sixth message from the fourth access point of the second device requesting the removal of MALT, wherein the sixth message includes at least one of the following: a request to remove one or more of the MALT on the current link; a request to remove one or more of the MALT on one or more other links; a request to remove one or more of the MALT on the same channel as the first access point of the first device, which shares the same MBSSID or co-hosted BSSID or co-located AP; or a request to remove one or more of the MALT on the current link or at least one other link by other access points of the first device, which shares the same MBSSID or co-hosted BSSID or co-located AP.

10. The method according to claim 2, wherein, The first device sending a fifth message requesting an update to the multi-access point cooperation technology to the second device, or the first device receiving a fifth message requesting an update to the multi-access point cooperation technology from the second device, includes one of the following: In a single-link scenario, the first device sends a fifth message to the second device requesting an update of the multi-access point cooperation technology. This fifth message contains one or more update requests for multi-access point cooperation technology, or update requests for one or more of the aforementioned multi-access point cooperation technologies from other access points sharing the same multiple basic service set identifier (MBSSID), co-hosted basic service set identifier (co-hosted BSSID), or co-located access point (co-located AP) on the same channel as the first device. Alternatively, the first device receives a fifth message from the second device requesting an update of the multi-access point cooperation technology, where the fifth message contains one or more update requests for multi-access point cooperation technology, or update requests for one or more of the aforementioned multi-access point cooperation technologies from other access points sharing the same multiple basic service set identifier (MBSSID), co-hosted basic service set identifier (co-hosted BSSID), or co-located access point (co-located AP) on the same channel as the first device. In a multi-link scenario, the first access point belonging to the first device sends a fifth message requesting an update to the multi-access point cooperation technology to the fourth access point belonging to the second device. This fifth message includes at least one of the following: an update request for one or more of the multi-access point cooperation technologies on the current link; an update request for one or more of the multi-access point cooperation technologies on one or more other links; an update request for one or more of the multi-access point cooperation technologies on the same channel as the first access point belonging to the first device and sharing the same MBSSID, co-hosted BSSID, or co-located AP; or an update request for one or more of the multi-access point cooperation technologies on the same MBSSID, co-hosted BSSID, or co-located AP as the first access point belonging to the first device or the second access point. The following are possible interpretations of the following: an update request for one or more of the multi-access point cooperation technologies (MALT) from other access points of the AP on the current link or at least one other link; or a fifth message from a fourth access point of the second device to the first access point of the first device requesting an update of the MALT, wherein the fifth message includes at least one of the following: an update request for one or more of the MALT on the current link; an update request for one or more of the MALT on one or more other links; an update request for one or more of the MALT on the same channel as the first access point of the first device, which shares the same MBSSID or co-hosted BSSID or co-located AP; or an update request for one or more of the MALT on the current link or at least one other link as the first access point of the first device, which shares the same MBSSID or co-hosted BSSID or co-located AP.

11. The method according to claim 4, wherein, The first device sends a first message to the second device to declare that its support for the multi-access point collaboration technology includes one of the following: In the case of a single link, the first device sends a first message to the second device to declare its support for the multi-access point collaboration technology; In a multi-link scenario, multiple access points belonging to the first device send a first message to multiple access points belonging to the second device on multiple links to declare their support for the multi-access point collaboration technology.

12. The method according to claim 4, wherein, The first device receiving a second message from the second device declaring support for the multi-access point cooperation technology includes one of the following: In the case of a single link, the first device receives a second message from the second device declaring its support capability for the multi-access point collaboration technology; In a multi-link scenario, the first device's subordinate access points receive a second message sent by the second device's subordinate access points on multiple links, declaring support for the multi-access point collaboration technology.

13. The method according to claim 4, wherein, In the case of a single link, the first message includes at least one of the following: the support capability of the multi-access point cooperation technology for the current link, the support capability of the multi-access point cooperation technology for at least one other link, and the support capability of the multi-access point cooperation technology for other access points that are on the same channel as the first device and are in the same multi-basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP). In the case of multiple links, the first message includes at least one of the following: the support capability of the multi-access point cooperation technology on the current link; the support capability of the multi-access point cooperation technology on at least one other link; the support capability of the multi-access point cooperation technology on the same channel as the first access point belonging to the first device and sharing the same multiple basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP); or the support capability of the multi-access point cooperation technology on the current link or at least one other link as the first access point or second access point belonging to the first device and sharing the same multiple basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP). In the case of a single link, the second message includes at least one of the following: the support capability of the multi-access point cooperation technology for the current link, the support capability of the multi-access point cooperation technology for at least one other link, and the support capability of the multi-access point cooperation technology for other access points on the same channel as the second device that are in the same multiple basic service set identifier (MBSSID) or co-hosted basic service set identifier (co-hosted BSSID) or co-located access point (co-located AP). In the case of multiple links, the second message includes at least one of the following: the ability to support the multi-access point cooperation technology on the current link; the ability to support the multi-access point cooperation technology on at least one other link; the ability to support the multi-access point cooperation technology on the same channel as the fourth access point to which the second device belongs, which shares the same MBSSID or co-hosted BSSID or co-located AP; or the ability to support the multi-access point cooperation technology on the current link or at least one other link as the fourth or fifth access point to which the second device belongs, which shares the same MBSSID or co-hosted BSSID or co-located AP.

14. The method according to claim 1, wherein, In the case of a single link, the third message or the fourth message includes at least one of the following fields: The elements include an element ID, a length, a multi-access point bitmap, and multi-access point information. The multi-access point bitmap field includes a correspondence between multiple bits and one or more of the multi-access point collaboration technologies. The multi-access point information field includes feature configurations of one or more of the multi-access point collaboration technologies. Each feature configuration of the multi-access point collaboration technology includes at least one of the following fields: sub-element ID, length, multi-access point status, and optional sub-element.

15. The method according to claim 1, wherein, In the case of a single link, the third message or the fourth message includes at least one of the following fields: The multi-access point information field includes an element ID, length, and multi-access point information; wherein, the multi-access point information field includes feature configurations of one or more of the multi-access point collaboration technologies, and each feature configuration of the multi-access point collaboration technology includes at least one of the following fields: sub-element ID, length, multi-access point feature ID, multi-access point status, and optional sub-element; the multi-access point feature ID field indicates the correspondence between the multi-access point feature ID and the multi-access point collaboration technology.

16. The method according to claim 14 or 15, wherein, The multi-access point status field in the third message is a reserved field, and the multi-access point status field in the fourth message indicates the response result of whether one or more of the multi-access point cooperation technologies have been successfully established; the optional sub-element field includes other information about the establishment of the multi-access point cooperation technology.

17. The method according to claim 1, wherein, In the case of multiple links, the third message or the fourth message shall include at least one of the following fields: The elements are: Element ID, Length, Element ID Extension, Multi-link Control, Public Information, and Link Information; wherein the Multi-link Control field includes at least one of the following fields: Type, Reserved, Existing Bitmap; the Public Information field includes at least one of the following fields: Public Information Length, Access Point Multi-link Device MAC Address; the Link Information field includes the following fields: Configuration Sub-elements of one or more sites of the Multi-access Point Multi-link element; the Configuration Sub-elements of one or more sites include at least one of the following fields: Sub-element ID, Length, Site Control, Site Information, Site Configuration; the Site Control field includes at least one of the following fields: Link ID, Site MAC Address Existing, Reserved; and the Site Information field includes at least one of the following fields: Site Information Length, Site MAC Address.

18. The method according to claim 17, wherein, The site configuration fields must include at least one of the following fields: The elements include an element ID, a length, a multi-access point bitmap, and multi-access point information. The multi-access point bitmap field includes a correspondence between multiple bits and one or more of the multi-access point collaboration technologies. The multi-access point information field includes feature configurations of one or more of the multi-access point collaboration technologies. Each feature configuration of the multi-access point collaboration technology includes at least one of the following fields: sub-element ID, length, multi-access point status, and optional sub-element.

19. The method of claim 17, wherein, The site configuration fields must include at least one of the following fields: The multi-access point information field includes an element ID, length, and multi-access point information; wherein, the multi-access point information field includes feature configurations of one or more of the multi-access point collaboration technologies, and each feature configuration of the multi-access point collaboration technology includes at least one of the following fields: sub-element ID, length, multi-access point feature ID, multi-access point status, and optional sub-element; the multi-access point feature ID field indicates the correspondence between the multi-access point feature ID and the multi-access point collaboration technology.

20. The method of claim 17, wherein, The presence of a site MAC address indicates whether the site information contains a site MAC address.

21. The method according to claim 14, wherein, The fourth message includes multiple status code fields to indicate the establishment status of the multi-access point collaboration technology for each type of request.

22. The method according to claim 17, wherein, The multilink control field also includes a type subfield value, and when the type subfield value is a specific value, the multilink element variant is named multi-access point or access point collaboration.

23. The method according to claim 21, wherein, In the case where the multi-access point cooperation techniques are mutually exclusive, the mutually exclusive multi-access point cooperation techniques in the multi-access point bitmap field are not simultaneously the same specific value, or In the case where the multi-access point cooperation techniques are mutually exclusive, the mutually exclusive multi-access point cooperation techniques in the multi-access point bitmap field are simultaneously of the same specific value, and the reason for rejection is indicated in the status code field of the fourth message or in the multi-access point status field as the multi-access point cooperation techniques are mutually exclusive.

24. A method for establishing a multi-access point collaboration technology, comprising: The second device receives a third message from the first device requesting the establishment of a multi-access point cooperation technology, wherein the third message contains a request to establish one or more multi-access point cooperation technologies. The second device sends a fourth message to the first device in response to the third message, wherein the fourth message contains an establishment response for the one or more multi-access point cooperation technologies.

25. The method according to claim 24, wherein, The method further includes: The second device sends a fifth message to the first device requesting an update to the multi-access point cooperation technology, or The second device receives the fifth message from the first device requesting an update to the multi-access point cooperation technology. The fifth message contains an update request for one or more multi-access point collaboration technologies.

26. The method according to claim 24, wherein, The method further includes: The second device sends a sixth message to the first device requesting the removal of the multi-access point cooperation technology, or The second device receives the sixth message from the first device requesting the removal of the multi-access point cooperation technology. The sixth message contains a teardown request for one or more multi-access point collaboration technologies.

27. The method according to claim 24, wherein, Before the second device receives the third message from the first device requesting the establishment of multi-access point cooperation technology, the method includes: The second device sends a first message to the first device to declare its support for the multi-access point collaboration technology; The second device receives a second message from the first device declaring its support for the multi-access point collaboration technology.

28. A computer-readable storage medium storing a computer program, wherein, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 23, or the steps of the method described in any one of claims 24 to 27.

29. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of the method according to any one of claims 1 to 23, or implements the steps of the method according to any one of claims 24 to 27.

30. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 23, or implements the steps of the method according to any one of claims 24 to 27.

Images