Inter-AP communication method, apparatus, device, medium, and program product

Abstract

The present application relates to the technical field of communications. Disclosed are an inter-AP communication method, an apparatus, a device, a medium, and a program product. The method is executed by a first AP. The method comprises: sending a first frame, the first frame being used for indicating first MAPC information related to the first AP, and the first MAPC information being used for indicating information required for MAPC data transmission. The method enables other APs to acquire the first MAPC information, thereby helping the APs coordinate data transmission.

Description

Communication methods, devices, equipment, media, and software products between APs Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, apparatus, device, medium and program product between access points (APs). Background Technology

[0002] During communication between APs, it is necessary to discover APs that support AP collaborative data transmission from among multiple APs.

[0003] In related technologies, APs that support AP cooperative data transmission can be discovered by using passive methods (e.g., using beacon frames) or active methods (e.g., using dedicated management frames). Summary of the Invention

[0004] This application provides a communication method, apparatus, device, medium, and program product between access points (APs), and the technical solution includes at least the following:

[0005] According to one aspect of the embodiments of this application, a communication method between APs is provided, the method being executed by a first AP, the method comprising:

[0006] Send the first frame, which is used to indicate the first multi-AP coordination (MAPC) information associated with the first AP;

[0007] The first MAPC information is used to indicate the information required for MAPC to transmit data.

[0008] According to one aspect of the embodiments of this application, a parameter negotiation method is provided, the method being performed by a first AP, the method comprising:

[0009] Send a first request frame, which is used to negotiate the MAPC parameters required for MAPC data transmission.

[0010] According to one aspect of the embodiments of this application, a communication method between APs is provided, the method being executed by a first AP, the method comprising:

[0011] Receive and / or send at least one frame, which is related to the MAPC discovery process.

[0012] According to one aspect of the embodiments of this application, a communication method between APs is provided, the method being executed by a first AP, the method comprising:

[0013] Receive and / or send at least one frame, which is related to the MAPC negotiation process.

[0014] According to another aspect of the embodiments of this application, a communication method between APs is provided, the method being performed by a second AP, the method comprising: receiving a first frame, the first frame being used to indicate first MAPC information associated with a first AP;

[0015] The first MAPC information is used to indicate the information required for MAPC to transmit data.

[0016] According to one aspect of the embodiments of this application, a parameter negotiation method is provided, the method being performed by a second AP, the method comprising:

[0017] Receive the first request frame, which is used to negotiate the MAPC parameters required for MAPC data transmission.

[0018] According to another aspect of the embodiments of this application, a first wireless device is provided, the first wireless device comprising:

[0019] A transmitting module is used to transmit a first frame, which is used to indicate first MAPC information related to the first wireless device;

[0020] The first MAPC information is used to indicate the information required for MAPC to transmit data.

[0021] According to another aspect of the embodiments of this application, a second wireless device is provided, the second wireless device comprising:

[0022] A receiving module is configured to receive a first frame, the first frame being used to indicate first MAPC information related to the first wireless device;

[0023] The first MAPC information is used to indicate the information required for MAPC to transmit data.

[0024] According to another aspect of the embodiments of this application, a first wireless device is provided, the first wireless device comprising:

[0025] The sending module is used to send a first request frame, which is used to negotiate the MAPC parameters required for MAPC data transmission.

[0026] According to another aspect of the embodiments of this application, a second wireless device is provided, the second wireless device comprising:

[0027] The receiving module is used to receive the first request frame, which is used to negotiate the MAPC parameters required for MAPC data transmission.

[0028] According to another aspect of the embodiments of this application, a first wireless device is provided, the first wireless device comprising:

[0029] The transceiver module is used to receive and / or send at least one frame, which is related to the MAPC discovery process.

[0030] According to another aspect of the embodiments of this application, a first wireless device is provided, the first wireless device comprising:

[0031] The transceiver module is used to receive and / or send at least one frame, which is related to the MAPC negotiation process.

[0032] According to another aspect of the embodiments of this application, a first AP is provided, the first AP comprising:

[0033] Processor; transceiver connected to the processor; memory for storing executable instructions of the processor; wherein the processor is configured to load and execute executable instructions to implement the inter-AP communication method and / or parameter negotiation method as described above.

[0034] According to another aspect of the embodiments of this application, a second AP is provided, the second AP comprising:

[0035] Processor; transceiver connected to the processor; memory for storing executable instructions of the processor; wherein the processor is configured to load and execute executable instructions to implement the inter-AP communication method and / or parameter negotiation method as described above.

[0036] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, which stores at least one program that is loaded and executed by a processor to implement the inter-AP communication method and / or parameter negotiation method as described in the various aspects above.

[0037] According to another aspect of the embodiments of this application, a chip is provided, the chip including programmable logic circuits and / or program instructions, which, when running on a first AP, are used to implement the inter-AP communication method and / or parameter negotiation method of the above-mentioned aspects; and when running on a second AP, are used to implement the inter-AP communication method and / or parameter negotiation method of the above-mentioned aspects.

[0038] According to another aspect of the embodiments of this application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium, a processor retrieving the computer instructions from the computer-readable storage medium, and the processor executing the computer instructions to implement the communication method and / or parameter negotiation method between APs as described in the various aspects above.

[0039] The technical solutions provided in this application embodiment may include the following beneficial effects:

[0040] The communication method between APs involves sending a first frame, which indicates first MAPC information associated with the first AP. The first MAPC information indicates the information required for MAPC data transmission, thereby enabling other APs to obtain the first MAPC information and helping APs to cooperate in transmitting data.

[0041] The parameter negotiation method involves sending a first request frame to negotiate the MAPC parameters required for MAPC data transmission. This enables the first AP and the second AP to conduct a MAPC negotiation process, thereby negotiating the MAPC parameters to be used during MAPC transmission so that subsequent MAPC transmissions can be performed using the MAPC parameters agreed upon by all APs. Attached Figure Description

[0042] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0043] Figure 1 shows a schematic diagram of a communication system provided in an exemplary embodiment of this application;

[0044] Figure 2 illustrates a schematic diagram of the MAPC discovery process provided by the relevant technologies;

[0045] Figure 3 shows a schematic diagram of the framework for the MAPC coordination pair / group coordination setup provided by the relevant technology;

[0046] Figure 4 shows a schematic diagram of Mode A provided by the relevant technology;

[0047] Figure 5 shows a schematic diagram of Mode B provided by the related technology;

[0048] Figure 6 shows a schematic diagram of the non-master channel access mechanism provided by the relevant technology;

[0049] Figure 7 shows a flowchart of an inter-AP communication method provided in an exemplary embodiment of this application;

[0050] Figure 8 shows a flowchart of an inter-AP communication method provided in an exemplary embodiment of this application;

[0051] Figure 9 shows a schematic diagram of an inter-AP communication method provided in an exemplary embodiment of this application;

[0052] Figure 10 shows a schematic diagram of an inter-AP communication method provided in an exemplary embodiment of this application;

[0053] Figure 11 shows a schematic diagram of the format of the aggregation control field provided in an exemplary embodiment of this application;

[0054] Figure 12 shows a schematic diagram of the format of the first or second frame provided in an exemplary embodiment of this application;

[0055] Figure 13 shows a schematic diagram of the format of the third frame provided in an exemplary embodiment of this application;

[0056] Figure 14 illustrates a schematic diagram of the MAPC discovery process provided in an exemplary embodiment of this application;

[0057] Figure 15 illustrates a schematic diagram of the MAPC discovery process provided in an exemplary embodiment of this application;

[0058] Figure 16 illustrates a schematic diagram of the MAPC discovery process provided in an exemplary embodiment of this application;

[0059] Figure 17 illustrates a schematic diagram of the MAPC negotiation process provided in an exemplary embodiment of this application;

[0060] Figure 18 illustrates a schematic diagram of the format of a first request frame or a first response frame provided in an exemplary embodiment of this application;

[0061] Figure 19 illustrates a schematic diagram of the MAPC negotiation process provided in an exemplary embodiment of this application;

[0062] Figure 20 shows a schematic diagram of the MAPC negotiation process provided in an exemplary embodiment of this application;

[0063] Figure 21 shows a flowchart of an inter-AP communication method provided in an exemplary embodiment of this application;

[0064] Figure 22 shows a flowchart of a parameter negotiation method provided in an exemplary embodiment of this application;

[0065] Figure 23 shows a flowchart of a parameter negotiation method provided in an exemplary embodiment of this application;

[0066] Figure 24 shows a flowchart of an inter-AP communication method provided in an exemplary embodiment of this application;

[0067] Figure 25 shows a flowchart of an inter-AP communication method provided in an exemplary embodiment of this application;

[0068] Figure 26 shows a block diagram of a first wireless device provided in an exemplary embodiment of this application;

[0069] Figure 27 shows a block diagram of a second wireless device provided in an exemplary embodiment of this application;

[0070] Figure 28 shows a block diagram of a first wireless device provided in an exemplary embodiment of this application;

[0071] Figure 29 shows a block diagram of a second wireless device provided in an exemplary embodiment of this application;

[0072] Figure 30 shows a block diagram of a first wireless device provided in an exemplary embodiment of this application;

[0073] Figure 31 shows a block diagram of a first wireless device provided in an exemplary embodiment of this application;

[0074] Figure 32 shows a schematic diagram of the structure of a first AP or a second AP provided in an exemplary embodiment of this application. Detailed Implementation

[0075] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail here, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0076] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms “a,” “the,” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0077] It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0078] The technical solutions described in some embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, Advanced Long Term Evolution (LTE-A) systems, New Radio (NR) systems, evolution systems of NR systems, LTE-based access to unlicensed spectrum (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, Non-Terrestrial Networks (NTN) systems, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th-Generation (5G) systems, cellular IoT systems, cellular passive IoT systems, and can also be applied to subsequent evolution systems of 5G NR systems, as well as 6G and subsequent evolution systems.

[0079] It should be understood that in some embodiments of this application, "5G" may also be referred to as "5G NR" or "NR".

[0080] It should be understood that in the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0081] In this embodiment of the application, "predefined" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0082] In this application embodiment, "protocol" may refer to standard protocols in the field of communication, such as IEEE 802.11ax protocol, IEEE 802.11be protocol, IEEE 802.11bn protocol, and related protocols applied in future communication systems. This application does not limit this.

[0083] Figure 1 shows a schematic diagram of a communication system 10 provided in an exemplary embodiment of this application. The communication system 10 includes multiple access points (APs) and non-AP stations (non-AP stations, non-AP STAs, abbreviated as STAs). In this application, the communication system 10 is described as including: a first AP 110, a second AP 120, a first STA 130, and a second STA 140.

[0084] In some embodiments, the communication system 10 may also include more second APs, such as two second APs 120. This application embodiment does not limit this, and usually one second AP 120 is used as an example for illustration.

[0085] Both AP110 and AP120 are devices deployed in a WLAN / Wi-Fi system to provide wireless communication capabilities for STAs. An AP acts as a bridge connecting wired and wireless networks, its main function being to connect various wireless network clients together and then connect the wireless network to the Ethernet. AP110 and AP120 can be terminal devices or network devices (such as routers) equipped with WLAN / Wi-Fi chips.

[0086] In some embodiments, the first AP110 and the second AP120 can be devices supporting the 802.11be standard. The first AP110 and the second AP120 can also be devices supporting various current and future 802.11 family WLAN standards, such as 802.11bn, 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. The first AP110 and the second AP120 can also be applied in network environments supporting next-generation WLAN systems / next-generation Wi-Fi communication.

[0087] In some embodiments, the first AP110 may have the same or different format as the second AP120.

[0088] A Basic Service Set (BSS) is the fundamental topology in WLAN / Wi-Fi communication. The communication devices constituting a BSS include one Access Point (AP) and several non-AP STAs (Standard Target Units). After joining the AP's radio domain, each non-AP STA establishes an association with the AP. Associated non-AP STAs and the AP can transmit data, and non-AP STAs within the same BSS can exchange data through the AP.

[0089] In some embodiments, there are one or more links between the first AP110 and the second AP120. For example, in a multi-AP coordination scenario, the link between the first AP110 and the second AP120 can meet the requirements of multi-AP coordination, thereby reducing mutual interference between BSS1 to which the first AP110 belongs and BSS2 to which the second AP120 belongs, improving spectrum utilization efficiency, throughput and transmission reliability, and the number of APs participating in multi-AP coordination can be two or more.

[0090] In this application embodiment, Multi-AP cooperation includes one or more of the following schemes: Coordinated Beamforming (Co-BF), Coordinated Spatial Reuse (Co-SR), Coordinated Time Division Multiple Access (Co-TDMA), Coordinated Orthogonal Frequency Division Multiple Access (Co-OFDMA), Coordinated Nulling, and Seamless Roaming.

[0091] In some embodiments, communication in the communication system can be between the first AP110 and the second AP120, between the first AP110 and the first STA130, or between the first STA130 and other terminal devices. Both the first STA130 and the second STA140 are non-AP STAs associated with the AP. In this embodiment, only the first STA130 is described as an example; the second STA140 will not be described further.

[0092] In this embodiment, the first STA130 can be a device with wireless transceiver capabilities, such as a device supporting the 802.11 series of protocols, or a device capable of communicating with the first AP110 or other terminal devices. For example, the first STA130 is any user communication device that allows a user to communicate with the first AP110 and thus with the WLAN. The first STA130 can be, for example, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device, etc.

[0093] The first STA130 in this embodiment can also be a device that provides voice / data / image connectivity to a user. For example, it can be a handheld device, in-vehicle device, home appliance, gaming device, etc., that has wireless connectivity or is equipped with a wireless communication module. Examples include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, drones or aerial photography equipment, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future evolved Public Land Mobile networks. Terminal devices in a network (PLMN) can also be televisions, refrigerators, washing machines, kitchen appliances, door locks, fish tanks, robot vacuum cleaners, game consoles, cameras / camcorders, etc. with wireless connectivity, but this application embodiment is not limited to these.

[0094] By way of example and not limitation, in this embodiment, the first STA130 can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Examples include smartwatches or smart glasses, as well as devices that focus on a specific type of application function and require cooperation with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0095] Furthermore, in some embodiments, the first STA130 can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical characteristic is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. In the embodiments of this application, IoT technology can achieve massive connectivity, deep coverage, and terminal power saving through technologies such as narrowband (NB).

[0096] Furthermore, in some embodiments, the first STA130 may also be an in-vehicle communication device in the vehicle-to-everything (V2X) system or the vehicle itself. The communication methods in the V2X system are collectively referred to as V2X (where X represents anything). For example, V2X communication includes: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc.

[0097] In this embodiment, the first STA130 may be a mobile phone, tablet computer, computer, virtual reality device, augmented reality device, communication device in industrial control, set-top box, communication device in autonomous driving, vehicle communication device, communication device in telemedicine, communication device in smart grid, communication device in transportation safety, communication device in smart city, or communication device in smart home, or wireless communication chip, etc., that supports WLAN / Wi-Fi technology. WLAN technology may support frequency bands including but not limited to: low frequency bands (2.4GHz, 5GHz, 6GHz) and high frequency bands (45GHz, 60GHz).

[0098] The following section describes the relevant technologies involved in the embodiments of this application:

[0099] • MAPC discovery process:

[0100] A framework for MAPC transmission has been proposed in related technologies, which is applicable to MAPC transmission under any coordination scheme. MAPC transmission includes the following stages: MAPC discovery, MAPC protocol setup, an additional stage based on the Transmission Opportunity (TXOP) protocol, and MAPC transmission initiation. In the embodiments of this application, the terms coordination, collaboration, and cooperation have the same meaning and are used to describe coordination or related meanings.

[0101] Figure 2 illustrates a schematic diagram of the MAPC discovery process provided by related technologies. In Figure 2(a), APs supporting MAPC transmission are discovered passively, for example, by using beacon frames.

[0102] In Figure 2(b), APs that support MAPC transmission are discovered actively, for example by sending request and response frames (MAPC Probe Request and MAPC Probe Response frames) between APs.

[0103] For example, AP1 sends a request frame (MAPC Probe Request frame) to AP2, and AP2 replies with a response frame (MAPC Probe Response frame) to AP1; or, AP1 sends a request frame to AP3, and AP3 replies with a response frame to AP1. Other cases will not be described in detail.

[0104] However, this MAPC discovery process is designed based on the assumption that all APs have the same main channel. In practice, the main channel of an AP may be switched, for example, switched to the NPCA main channel.

[0105] • MAPC Setup Scheme (Multi-AP Coordination Setup Scheme):

[0106] A framework for setting up MAPC coordination pairs / groups has been proposed in related technologies. This framework consists of three parts: a capability declaration / discovery process, a distributed coordination pair / group setup process, and a shared-AP AID assignment / allocation process.

[0107] Figure 3 illustrates a schematic diagram of the framework for MAPC coordination pair / group coordination setup provided by related technologies. The capability declaration / discovery process uses management frames (e.g., beacon frames) to declare its ability to support multi-AP coordination functionality (also known as MAPC functionality). APs with MAPC functionality can identify neighboring APs that also have MAPC functionality and initiate a request or response request to establish a MAP coordination pair with those neighboring APs. For example, in Figure 3(a), AP1 sends a request or response frame to at least one of APs, AP2, AP3, and AP4.

[0108] The distributed coordination pair / group setup process involves the following steps after a MAP coordination pair is successfully established: The two APs associated with the pair will add each other to their respective MAPC lists. Each MAPC list may contain one or more coordination peer APs associated with that AP. In other words, an AP and its MAPC list members constitute a MAPC group, which is maintained locally by the AP to act as a sharing AP during coordination transmissions. The MAPC list can be updated when an AP joins or leaves a MAPC group. For example, in Figure 3(a), the MAPC group established by AP1 includes AP2, AP3, and AP4.

[0109] The process of assigning / allocating shared AP identifiers is as follows: Two APs in a MAP coordination pair can mutually assign an Access Point Identifier (AID) during the distributed coordination pair / group setup process. Each AP associated with one or more MAP coordination pairs should ensure that it assigns a locally unique AID to different coordination peer APs. For example, in Figure 3(b), AP1 can assign an AID to AP2, and AP2 can also assign an AID to AP1; or, AP1 can assign an AID to AP3, and AP3 can also assign an AID to AP1. Other cases will not be elaborated further.

[0110] However, this MAPC discovery process is designed based on the assumption that all APs have the same main channel. In practice, the main channel of an AP may be switched, for example, switched to the NPCA main channel.

[0111] • Coordinated Restricted Target Wake Time (Co-RTWT) scheduling protocol:

[0112] Related technologies propose using Co-RTWT to divide communication between APs and between APs and non-AP STAs in the time domain. Communication between APs can be transmitted in a contention-based or trigger-based manner within a Service Period (SP). The process includes: establishing an R-TWT scheduling protocol among multiple APs for communication between them. Within the Service Period, communication between APs can be either contention-based or trigger-based. To ensure that latency-sensitive services between APs and non-AP STAs are processed in a timely manner, while accommodating the R-TWT scheduling protocol required for communication between APs, this proposal suggests two coordination modes for R-TWT schedules: Mode A and Mode B.

[0113] Figure 4 illustrates a schematic diagram of Mode A provided by the related technology. APs can negotiate separate R-TWT service cycles for inter-AP communication and data transmission between APs and non-AP STAs. For example, data transmission (uplink / downlink) between AP1 and STA1 is performed within R-TWT SP1; parameter exchange for Co-SR between AP1 and AP2 based on trigger frames is performed within R-TWT SP2.

[0114] Figure 5 illustrates a schematic diagram of Mode B provided by the related technology. APs can negotiate a common R-TWT service period (Common R-TWT SP) for inter-AP communication and data transmission between APs and non-AP STAs. For example, Co-SR parameter exchange based on trigger frames and R-TWT data transmission (uplink / downlink) based on trigger frames are performed within Common R-TWT SP1; Coordinated Time Division Multiple Access (Co-TDMA) parameter exchange and R-TWT data transmission (uplink / downlink) are performed within Common R-TWT SP2.

[0115] However, this method does not solve the initial configuration problem of the Co-RTWT service cycle, namely the lack of a MAPC discovery process and a process for negotiating and setting up MAPC. Only by solving these problems can a Co-RTWT scheduling protocol be established between APs.

[0116] Seamless Roaming:

[0117] A mechanism is defined in related technologies to enable a non-AP multi-link device (non-AP MLD) to roam from one multi-link device (AP MLD) to another AP MLD, maintaining connectivity with both the original AP MLD and the target AP MLD during and after the roaming process. During the roaming process, the context associated with the non-AP MLD is transferred to the target AP MLD. After exchanging a handover request frame or handover response frame, a distributed system (DS) mapping change notification from the current AP MLD to the target AP MLD is initiated. It is assumed that after the DS mapping change, the target AP MLD can transmit data frames to the non-AP MLD. The current AP MLD can forward downlink (DL) data to the target AP MLD. Seamless roaming requires coordination and information sharing between multiple APs. For example, when a STA moves from its original BSS to a target BSS, the original associated AP and the target AP will exchange frames (such as the STA's ID and other information), and data frames will be transmitted between the APs.

[0118] • Non-Primary Channel Access (NPCA) mechanism:

[0119] Related technologies define a maximum supported bandwidth of 320MHz, but actual bandwidth usage depends on the idle state of the 20MHz primary channel. If the primary channel is busy, nodes cannot utilize the bandwidth of the remaining secondary channels, resulting in wasted spectrum resources. The NPCA mechanism solves this problem by defining an NPCA primary channel as an auxiliary primary channel. This auxiliary primary channel serves as a backup to the primary channel, capable of carrying data transmission tasks of equal importance to the primary channel, and typically possesses similar bandwidth and transmission capabilities. When the primary channel is busy due to overlapping BSS (OBSS) interference or other conditions, the connection is made to the NPCA primary channel.

[0120] Figure 6 illustrates a schematic diagram of the non-primary channel access mechanism provided by the related technology. When the primary channel (taking the primary 20MHz channel as an example) is busy, for example due to OBSS interference, the system switches to the NPCA primary channel for channel access and frame switching. When the primary channel becomes idle again, for example when the OBSS interference disappears, frame switching is performed on the full bandwidth (the bandwidth occupied by the primary channel and the NPCA primary channel).

[0121] In wireless network environments, access points (APs) often switch their primary channel to the NPCA primary channel frequently due to OBSS interference. However, when multiple APs switch to the same primary channel, new interference problems arise. To avoid this, APs need to perform a channel discovery and negotiation process. Through this process, APs can establish communication, thereby effectively avoiding interference.

[0122] During communication between APs, it is necessary to discover APs that support AP cooperative data transmission from among multiple APs. In related technologies, APs that support AP cooperative data transmission can be discovered by using passive methods (e.g., using beacon frames) or active methods (e.g., using dedicated management frames). This application provides an AP communication method. Figure 7 shows a flowchart of an exemplary embodiment of the AP communication method provided by this application. The method is executed by a first AP 110 and a second AP 120. The method mainly includes a MAPC discovery process and a MAPC negotiation process, including at least one of the following steps.

[0123] Step 701: The first AP110 sends the first frame to the second AP120.

[0124] The first frame is used to indicate the first MAPC information associated with the first AP110, and the first MAPC information is used to indicate the information required for MAPC data transmission.

[0125] In some embodiments, the device initiating the MAPC discovery process is called the MAPC Initiator AP, and the device responding to the MAPC discovery is called the MAPC Responder AP. Both the MAPC Initiator AP and the MAPC Responder AP support MAPC transmission. The following explanation uses the example of the first AP110 as the MAPC Initiator AP and the second AP120 as the MAPC Responder AP.

[0126] The following problems exist: (a) The main channel of the MAPC response AP is the same as that of the MAPC initiating AP, but when the MAPC response AP temporarily switches to its NPCA main channel, it cannot receive beacon frames sent by the MAPC initiating AP; (b) The main channel of the MAPC response AP is different from that of the MAPC initiating AP, but the NPCA main channel of the MAPC response AP is the same as that of the MAPC initiating AP. When the MAPC response AP switches to the NPCA main channel, it cannot cooperate with the MAPC initiating AP to avoid interference. To solve the above problems, the first AP110 needs to broadcast the first MAPC information to discover the second AP120 that can perform inter-MAPC data transmission.

[0127] By way of example and not limitation, the first MAPC information includes one or more of the following: the main channel of the first AP110; the NPCA main channel of the first AP110; the MAPC transmission policy supported by the first AP110; and the disabled sub-channels of the first AP110.

[0128] In some embodiments, the first frame is also used to request the second AP120 to provide feedback on the second MAPC information related to the second AP120.

[0129] By broadcasting first MAPC information related to the first AP110 itself, and requesting second MAPC information from the second AP120, a MAPC group can be established.

[0130] Optionally, the first frame is transmitted in a non-high-throughput duplicate (non-HT duplicate) manner within the operating bandwidth of the first AP110, where the operating bandwidth is used to indicate the frequency band width used by the first AP110 during communication.

[0131] For example, the first frame is a MAPC Discovery Notification frame.

[0132] Step 702: The first AP110 receives the second frame sent by the second AP120.

[0133] The second frame is used to indicate the second MAPC information related to the second AP120. The second frame is sent when the main channel of the second AP is the same as the main channel of the first AP; or, the second frame is sent when the NPCA main channel of the second AP is the same as the main channel of the first AP; or, the second frame is sent when the main channel of the second AP is the same as the NPCA main channel of the first AP; or, the second frame is sent when the NPCA main channel of the second AP is the same as the NPCA main channel of the first AP.

[0134] In this application embodiment, the example is usually given that the main channel of the second AP or the main channel of the NPCA is the same as the main channel of the first AP.

[0135] By way of example and not limitation, the second MAPC information includes one or more of the following: the main channel of the second AP120; the NPCA main channel of the second AP120; the MAPC transmission policy supported by the second AP120; the disabled sub-channels of the second AP120; and whether the second AP120 agrees to join the MAPC group.

[0136] The MAPC group is a set of APs used for cooperative data transmission, and the MAPC group includes the first AP110. If the second AP120 agrees to join the MAPC group, the MAPC group includes both the first AP110 and the second AP120.

[0137] The second AP120 feeds back the second MAPC information through the second frame, thereby helping the first AP110 establish a MAPC group, which facilitates subsequent MAPC data transmission.

[0138] For example, the second frame is a MAPC discovery information (MAPC-Discovery Info) frame.

[0139] Step 703: The first AP110 sends the third frame to the second AP120.

[0140] The third frame is used to indicate MAPC group information related to the MAPC group, which is a set of APs used for cooperative data transmission.

[0141] After the first AP110 establishes a MAPC group with one or more second APs120, the first AP110 sends MAPC group information to the member APs of the MAPC group through the third frame.

[0142] By way of example and not limitation, the MAPC group information includes one or more of the following: the main channel of the MAPC group; the NPCA main channel of each AP in the MAPC group; the MAPC transmission policy supported by each AP in the MAPC group; the disabled sub-channels of each AP in the MAPC group; the AP ID of each AP in the MAPC group; and the MAPC Enhanced Distributed Channel Access (MAPC EDCA) parameters, wherein the main channel of the MAPC group is the same as the main channel of the first AP110.

[0143] For example, the third frame is a MAPC Group Info frame.

[0144] Steps 701 to 703 constitute the MAPC discovery process, which may also include other steps, but this embodiment does not limit these steps. The purpose of the MAPC discovery process is to establish a MAPC group, thereby obtaining information such as the main channel of the member APs in the MAPC group, the main channel of the NPCA, and the supported MAPC transmission strategies.

[0145] Step 704: The first AP110 sends the fourth frame to the second AP120.

[0146] Due to potential OBSS interference, adjacent APs need to transmit not only control signaling but also data. A link using only the 20MHz main channel cannot meet these data transmission requirements. Therefore, this application's embodiment designs a MAPC negotiation process. APs, considering data transmission needs and OBSS interference, exchange suitable subsets of channels for channel binding and perform channel binding, thereby widening the transmission link between APs.

[0147] In some embodiments, the fourth frame includes at least one of a Request to Send (RTS) frame and a Multi-User RTS (MU-RTS) frame. The following description uses an MU-RTS frame as an example.

[0148] Step 705: The first AP110 receives the fifth frame sent by the second AP120.

[0149] The fifth frame is used in response to the fourth frame; for example, the fifth frame is a Clear To Send (CTS) frame.

[0150] Step 706: The first AP110 sends a first request frame to the second AP120.

[0151] In some embodiments, the transmitting AP and the receiving AP perform a parameter negotiation process in a non-HT repetitive manner. This parameter negotiation process serves the subsequent MAPC transmission strategy, which includes, but is not limited to: Co-TDMA, Co-RTWT, Co-BF, Co-SR, and Seamless Roaming.

[0152] Because the physical distance between APs on the same main channel is relatively far in the AP channel scanning mechanism, APs need to negotiate some MAPC parameters, such as minimum or maximum transmit power, modulation and coding scheme (MCS), number of spatial streams (NSS), etc.

[0153] In some embodiments, the first AP110 sends a first request frame (e.g., a parameter request frame). The parameter command field in the first request frame indicates the parameter negotiation type, including four types: Suggest, Accept, Reject, and Alternate. In the first request frame, this field is set to Suggest to indicate the MAPC parameters suggested by the first AP110.

[0154] By way of example and not limitation, the MAPC parameters include one or more of the following parameters: the recommended set of subchannel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0155] Step 707: The first AP110 receives the first response frame sent by the second AP120.

[0156] In some embodiments, the first AP110 receives a first response frame (e.g., a parameter response frame) sent by the second AP120, the first response frame also containing a parameter command field.

[0157] Optionally, the parameter command field is set to override to indicate the MAPC parameters recommended by the second AP120, which are different from the MAPC parameters recommended by the first AP110.

[0158] Optionally, the parameter command field is set to accept to instruct the second AP120 to accept the MAPC parameters suggested by the first AP110. This application embodiment uses the parameter command field set to accept as an example for illustration.

[0159] Steps 704 to 707 constitute the MAPC negotiation process. This process may also include other steps, such as the first AP110 sending a second response frame if the parameter command field of the first response frame is set to "alternate". This embodiment of the application does not limit this. The purpose of the MAPC negotiation process is to negotiate the parameters of the communication link between MAPCs. The newly designed negotiation frames (first request frame, first response frame) carry information such as the proposed set of candidate sub-channels for binding and the minimum / maximum transmit power.

[0160] Step 708: The first AP110 and the second AP120 perform MAPC data transmission.

[0161] After the MAPC discovery process and the MAPC negotiation process, the first AP110 and the second AP120 can stably transmit MAPC data by executing the MAPC transmission strategy.

[0162] Figure 8 shows a flowchart of an inter-AP communication method provided in an exemplary embodiment of this application. The method is performed by a first AP and includes:

[0163] Step 810: Send the first frame.

[0164] The first frame is used to indicate the first MAPC information associated with the first AP, and the first MAPC information is used to indicate the information required for MAPC data transmission.

[0165] Since APs only exchange at least one of the control frames and management frames on the primary 20MHz channel, the primary 20MHz channel is referred to as the primary channel for ease of description. In this application embodiment, a primary channel bandwidth of 20MHz is typically used as an example. In other practical application scenarios, the primary channel can also be other bandwidths, such as 40MHz, and this application embodiment does not limit this.

[0166] In some embodiments, the first frame used to indicate the first MAPC information related to the first AP can be equivalently understood as at least one of the following expressions: the first frame is used to publish the first MAPC information related to the first AP; the first frame is used to discover the first MAPC information related to the first AP; the first frame is used to announce the first MAPC information related to the first AP; the first frame is used to broadcast the first MAPC information related to the first AP, and the embodiments of this application do not limit this.

[0167] In the embodiments of this application, the terms coordination, collaboration, and cooperation have the same meaning and are all used to describe coordination.

[0168] In this embodiment, it is assumed that all devices are single-link devices, each link consists of four 20MHz sub-channels, and the total operating bandwidth is 80MHz, including one main channel with a bandwidth of 20MHz. In practical applications, different numbers of channels can also be used to form channels with a total bandwidth of 160MHz, 320MHz, etc., and this embodiment does not limit this.

[0169] In some embodiments, the first frame is transmitted in a non-high-throughput duplicate manner within the operating bandwidth of the first AP; or, the first frame is transmitted in a non-high-throughput duplicate manner on at least two sub-channels of the operating bandwidth of the first AP, the operating bandwidth being used to indicate the bandwidth of the frequency band used by the first AP during communication.

[0170] For example, the operating bandwidth is the frequency band width corresponding to the four channels from channel 1 to channel 4, and the first frame is transmitted on these four channels in a non-high throughput repetitive manner; or, the first frame is transmitted on channel 1 and channel 2 in a non-high throughput repetitive manner; or, the first frame is transmitted on channel 1, channel 2 and channel 3 in a non-high throughput repetitive manner. This application embodiment does not limit this.

[0171] In some embodiments, step 810 is one of the steps included in the MAPC discovery process.

[0172] The device initiating the MAPC discovery process is called the MAPC Initiator AP, and the device responding to the MAPC discovery process is called the MAPC Responder AP. Both the MAPC Initiator AP and the MAPC Responder AP support MAPC transmission. In this embodiment, MAPC includes a first AP and a second AP. The following description uses the first AP as the MAPC Initiator AP and the second AP as the MAPC Responder AP as an example.

[0173] 1.1 First MAPC information;

[0174] The following issues are addressed: (a) The main channel of the MAPC response AP is the same as that of the MAPC initiating AP, but when the MAPC response AP temporarily switches to its NPCA main channel, it cannot receive beacon frames sent by the MAPC initiating AP; (b) The main channel of the MAPC response AP is different from that of the MAPC initiating AP, but the NPCA main channel of the MAPC response AP is the same as that of the MAPC initiating AP. When the MAPC response AP switches to the NPCA main channel, it cannot cooperate with the MAPC initiating AP to avoid interference.

[0175] The MAPC discovery process is designed as follows: the AP that initiates the MAPC broadcasts its first frame (e.g., a MAPC discovery notification frame) across the BSS in a non-HT duplicate manner within the operating bandwidth, announcing its primary channel, NPCA primary channel, supported MAPC transmission strategies, and other information.

[0176] In some embodiments, the first MAPC information includes one or more of the following: the primary channel of the first AP; the NPCA primary channel of the first AP; the MAPC Transmission Scheme supported by the first AP; and the disabled sub-channels of the first AP.

[0177] By way of example and not limitation, the MAPC transmission strategy includes at least one of the following: Co-TDMA; Co-RTWT; Co-BF; Co-SR; and seamless roaming. In the embodiments of this application, the MAPC transmission strategy may also be referred to as MAP transmission strategy (MAP Transmission Scheme), MAPC strategy, etc.

[0178] Figure 9 shows a schematic diagram of an inter-AP communication method provided in an exemplary embodiment of this application.

[0179] In Figure 9, AP1 (the first AP) is the initiating AP, broadcasting the first frame (e.g., a MAPC discovery notification frame) on channels 1 (Ch_1) to 4 (Ch_4) in a non-HT repetition manner. AP2 (the first second AP) and AP3 (the second second AP) are the responding APs, where AP2's main channel (AP2's P20 channel) is the same as AP1's main channel (AP1's P20 channel), and AP3's NPCA main channel (AP3's NPCA P20 channel) is the same as AP1's main channel.

[0180] In some embodiments, the first frame is also used to request the second AP to provide feedback on second MAPC information related to the second AP.

[0181] For example, the Channel-Info Req field in the first frame requests information such as the main channel of the second AP, the NPCA main channel, and the supported MAPC transmission strategies.

[0182] 1.2 Second MAPC information;

[0183] In some embodiments, the method further includes: receiving a second frame, the second frame being used to indicate second MAPC information associated with a second AP;

[0184] The second frame is transmitted by the second AP when it has the same main channel as the first AP. The situation of having the same main channel includes at least one of the following: the main channel of the second AP is the same as the main channel of the first AP; the NPCA main channel of the second AP is the same as the main channel of the first AP; the main channel of the second AP is the same as the NPCA main channel of the first AP; or the NPCA main channel of the second AP is the same as the NPCA main channel of the first AP.

[0185] In the counterexamples of the above scenario, the second AP will not send a second frame. For example, if the main channel of the first AP is different from the main channel of the second AP and the NPCA main channel, the second AP will not send a second frame; or, if the NPCA main channel of the first AP is different from the main channel of the second AP and the NPCA main channel, the second AP will not send a second frame.

[0186] When the first AP transmits the first frame on a single channel (e.g., the first AP's primary channel or the first AP's NPCA primary channel), the second AP can determine which of the four scenarios mentioned above applies to the case where it shares the same primary channel as the first AP. For example, if the first AP transmits the first frame on channel 1, and the first MAPC information includes information indicating that channel 1 is the primary channel, and the second AP's primary channel is also channel 1, then the second AP determines that its primary channel is the same as the first AP's primary channel.

[0187] If the first AP may switch to the first AP's NPCA main channel, then the second AP cannot determine whether the first AP is currently on the first AP's main channel or the first AP's NPCA main channel.

[0188] If the second AP has one and only one channel (the second AP's primary channel or its NPCA primary channel) that is identical to the first AP's NPCA primary channel, the second AP can establish communication with the first AP, but the second AP may refuse to join the MAPC group. That is, the first AP can know the second AP's primary channel and other information, but it may not be able to form a MAPC group with the second AP. The MAPC information sent by AP2 can help establish a MAPC group, and the primary channel of the MAPC group is AP1's NPCA primary channel.

[0189] If the main channel of the first AP and the NPCA main channel of the first AP are both within the operating bandwidth of the second AP, and the main channel / NPCA main channel of the second AP is the same as the main channel / NPCA main channel of the first AP (i.e., the four same cases mentioned above), then the second AP can send the second frame on the main channel and the NPCA main channel of the first AP in a non-high throughput repetitive manner.

[0190] For example, if the main channel of the second AP is the same as the main channel of the first AP, and the NPCA main channel of the second AP is the same as the NPCA main channel of the first AP, then the second AP transmits the second frame on the main channel of the first AP and the NPCA main channel of the first AP in a non-high throughput repetition manner; or, if the main channel of the second AP is the same as the main channel of the first AP, and the NPCA main channel of the second AP is different from the NPCA main channel of the first AP (i.e., only one channel is the same), and the main channel of the first AP and the NPCA main channel of the first AP are both within the operating bandwidth of the second AP, then the second AP transmits the second frame on the main channel of the first AP and the NPCA main channel of the first AP in a non-high throughput repetition manner.

[0191] For example, if the second AP does not have the same channel as the first AP, then the second AP will not send the second frame.

[0192] For example, if the main channel of the second AP is the same as the main channel of the first AP, but the NPCA main channel of the second AP is different from that of the first AP (i.e., only one channel is the same), and the main channel of the first AP or the NPCA main channel of the first AP is within the operating bandwidth of the second AP (i.e., both channels are not within the operating bandwidth of the second AP), then the second AP will only send the second frame on the main channel.

[0193] In some embodiments, the second MAPC information includes one or more of the following: the main channel of the second AP; the NPCA main channel of the second AP; the MAPC transmission policy supported by the second AP; the disabled sub-channels of the second AP; whether the second AP agrees to join the MAPC group; wherein, the MAPC group is a set of APs used for cooperative data transmission.

[0194] The MAPC group includes the first AP. If the second AP agrees to join the MAPC group, the MAPC group includes both the first and second APs.

[0195] After receiving the first frame, the second AP sends a second frame to indicate whether it agrees to join the MAPC group, thus facilitating the first AP to determine which AP will perform subsequent data transmission.

[0196] As shown in Figure 9, after receiving the first frame, AP2 sends a second frame (e.g., a MAPC discovery information frame) to AP1 on its main channel, thereby informing AP2 of its main channel, NPCA main channel, supported MAPC transmission strategies, and whether it agrees to join the MAPC group. AP1 replies with an acknowledgment frame (ACK) on its main channel.

[0197] In some embodiments, the second frame is a MAPC discovery information frame, which is sent by the second AP when it switches to the second AP's NPCA main channel and the second AP's NPCA main channel is the same as the first AP's main channel.

[0198] As shown in Figure 9, AP3's NPCA main channel is the same as AP1's main channel. After receiving the first frame, AP3 sends a second frame (e.g., a MAPC discovery information frame) to AP1 on its NPCA main channel. The second frame is sent by AP3 when switching to AP3's NPCA main channel. AP3 can switch to the NPCA main channel actively, or it can trigger a switch when it detects OBSS interference.

[0199] Optionally, the second frame includes at least one of a MAPC discovery information frame and a MAPC discovery notification frame.

[0200] Figure 10 shows a schematic diagram of an inter-AP communication method provided in an exemplary embodiment of this application.

[0201] In Figure 10, AP2 broadcasts a second frame (MAPC discovery notification frame), which includes information such as AP2's main channel, NPCA main channel, supported MAPC transmission policies, and whether it agrees to join the MAPC group. AP1 receives the second frame broadcast by AP2.

[0202] In some embodiments, the second frame is transmitted in a non-high-throughput repetitive manner on at least two channels, the at least two channels including at least one of the primary channel of the first AP and the NPCA primary channel of the first AP.

[0203] The second AP can transmit the second frame in a non-high-throughput repetitive manner within the operating bandwidth of the second AP. At least two channels refer to all channels within the operating bandwidth of the second AP. For example, if the second AP transmits the second frame on four channels, at least two channels means four channels.

[0204] If both the primary channel and the NPCA primary channel of the first AP are within the operating bandwidth of the second AP, then the four channels include the primary channel and the NPCA primary channel of the first AP. If either the primary channel or the NPCA primary channel of the first AP is within the operating bandwidth of the second AP, then the four channels only include the channel within the operating bandwidth. For example, if the primary channel of the first AP is within the operating bandwidth of the second AP, then the four channels only include the primary channel of the first AP and do not include the NPCA primary channel of the first AP.

[0205] When the first AP transmits the first frame in a non-high-throughput repetitive manner on at least two channels, the second AP can reply by transmitting a second frame in a non-high-throughput repetitive manner on at least two channels. In this application embodiment, the transmission of the second frame on one channel is typically used as an example for illustration, and the transmission method of the second frame is not limited.

[0206] 1.3 Fields carried in the first or second frame;

[0207] In some embodiments, the first or second frame carries one or more of the following fields:

[0208] MAPC Group Field; Common Action Field; MAPC Transmission Policy Field; Main Channel Center Frequency Field; NPCA Main Channel Field; Disabled Sub-channel Bitmap Field; Channel Information Request Field; Accept or Reject Field;

[0209] The MAPC group field indicates whether MAPC is supported; the common action field indicates the frame type; the MAPC transmission policy field indicates the supported MAPC transmission policy; the channel information request field indicates the channel information requester or responder; and the accept or reject field indicates whether to agree to join the MAPC group. The MAPC group is a set of APs used for cooperative data transmission. The MAPC group includes the first AP. If the second AP agrees to join the MAPC group, the MAPC group includes the first AP and the second AP.

[0210] A High Throughput Control (HT Control) field is added to the control fields of (MU-)RTS frames, MAPC Discovery Notification frames, and MAPC Discovery Info frames. This HT Control field is of type High Efficiency variant (HE variant) and has a length of 4 bytes (32 bits), with the first two bits both being 1 to indicate that the HT Control field is of the High Efficiency variant type. The HT Control field also includes an Aggregate Control (A-Control) field. Figure 11 shows a schematic diagram of the format of the Aggregate Control field provided in an exemplary embodiment of this application. The numbers below each field indicate the number of bits it may occupy. In this embodiment, subfields may be simply referred to as fields.

[0211] The aggregated control field occupies 30 bits and includes at least one of the following fields: Control ID field and Control Information field.

[0212] The control ID field occupies 4 bits, and the control information field occupies 26 bits.

[0213] The Control ID field uses the currently reserved bits 10-14. When the Control ID field is 10, the Control Information field includes a MAPC Group field to indicate whether MAPC is supported.

[0214] The control information fields include at least one of the following fields: the MAPC Group field and the Reserved field.

[0215] The MAPC group field occupies 1 bit, and the reserved field occupies 25 bits. A value of 1 in the MAPC group field indicates that MAPC is supported, and a value of 0 indicates that MAPC is not supported. The remaining bits are reserved to meet the requirement that the HT control field occupies 4 bytes.

[0216] The format of the above-mentioned aggregation control field is an exemplary possibility. In different embodiments or different designs, it is possible that at least one of the following designs may change: the position of the above field in the frame, its arrangement order with other fields, the number of bytes occupied, the number of bits occupied, the element name, and the field name. This embodiment does not limit this.

[0217] Figure 12 illustrates a schematic diagram of the format of a first or second frame provided in an exemplary embodiment of this application. The numbers below each field indicate the number of bytes or bits it may occupy. In this embodiment, subfields may be simply referred to as fields. The first or second frame is based on a common action frame design, which supports cross-BSS communication.

[0218] The first or second frame includes at least one of the following fields: Frame Control field, Duration field, Destination Address (DA) field, Source Address (SA) field, Basic Service Set ID (BSSID) field, Sequence Control field, Frame Body field, and Frame Check Sequence (FCS) field.

[0219] The frame control field occupies 2 bytes, the duration field occupies 2 bytes, the DA field occupies 6 bytes, the SA field occupies 6 bytes, the BSSID field occupies 6 bytes, the sequence control field occupies 2 bytes, the frame body field occupies 8 or 10 bytes, and the FCS field occupies 4 bytes.

[0220] In the MAPC discovery notification frame, DA is set to the broadcast address; in the MAPC discovery information frame, DA is set to the address of the first AP (initiating AP). The BSSID field is set to the wildcard BSSID value, that is, all bits of the BSSID are set to 1.

[0221] The frame body fields include at least one of the following fields: Category field, Public Action field, Element ID field, Length field, Element ID Extension field, and Subchannel-Info field.

[0222] The category field occupies 1 byte, the public action field occupies 1 byte, the element ID field occupies 1 byte, the length field occupies 1 byte, the element ID extension field occupies 1 byte, and the sub-channel information field occupies 3 or 5 bytes.

[0223] The category field is set to 4 to indicate that the frame belongs to the common action frame category. The reserved bits for the common action field are 46–255; a value of 46 indicates that the frame is a MAPC discovery notification frame or a MAPC discovery information frame. The element ID field is set to 255, and the element ID extension field is set to 136 (or another reserved value) to indicate that the frame body field includes a sub-channel information field, which indicates relevant information about the sub-channel.

[0224] The subchannel information field includes at least one of the following fields: MAPC Transmission Scheme, Primary Channel Center Frequency (Pch CCF), NPCA Primary Channel (NPCA Pch), Disabled Subchannel Bitmap, Channel-Info Req, MAPC Accept / Reject, and Reserved.

[0225] The MAPC transmission policy field occupies 4 bits, the main channel center frequency field occupies 8 bits, the NPCA main channel field occupies 8 bits, the disabled sub-channel bitmap field occupies 0 or 16 bits, the channel information request field occupies 1 bit, the MAPC accept or reject field occupies 1 bit, and the reserved field occupies 2 bits.

[0226] The MAPC transmission policy field indicates the supported MAPC transmission policies. Examples are shown in Table 1. A bit value of 1 indicates support for the corresponding MAPC transmission policy. For example, a MAPC transmission policy field value of 1001 indicates support for Co-SR and Co-RTWT.

[0227] Table 1

[0228] Table 1 is only used as an example to indicate the MAPC transmission strategy. Other indication methods may also exist, such as B0 corresponding to Co-RTWT, B1 corresponding to Co-SR, etc.; or, the MAPC transmission strategy field occupies fewer or more bits to indicate the supported MAPC transmission strategy. This application embodiment does not limit this.

[0229] The Pch CCF field indicates the center frequency of the primary channel. The NPCA Pch field indicates the channel number corresponding to the channel performing the NPCA operation. The Disabled Subchannel Bitmap field indicates that the subchannel bitmap is disabled.

[0230] The channel information request field is used to indicate whether the party requesting or responding to channel information is doing so. In a MAPC discovery notification frame, this field has a value of 1, indicating a party requesting channel information; in a MAPC discovery information frame, this field has a value of 0, indicating a party responding to channel information. Alternatively, in a MAPC discovery notification frame, this field has a value of 0, indicating a party requesting channel information; in a MAPC discovery information frame, this field has a value of 1, indicating a party responding to channel information. This embodiment of the application does not limit this specific approach.

[0231] The MAPC Accept or Reject field is used to indicate whether to agree to join the MAPC group. This field is valid when the Channel Information Request field is 0. A value of 1 indicates agreement to join the MAPC group, and a value of 0 indicates rejection. Alternatively, a value of 0 indicates agreement to join the MAPC group, and a value of 1 indicates rejection. This application embodiment does not limit this.

[0232] The format of the first or second frame described above is an exemplary possibility. In different embodiments or designs, it is possible that at least one of the following designs may change: the position of the field in the frame, the order of arrangement with other fields, the number of bytes occupied, the number of bits occupied, the element name, and the field name. This embodiment does not limit this.

[0233] 1.4 Third frame;

[0234] In some embodiments, the method further includes: sending a third frame, the third frame being used to indicate MAPC group information associated with the MAPC group;

[0235] The MAPC group is a set of APs used for cooperative data transmission. The MAPC group includes the first AP. If the second AP agrees to join the MAPC group, the MAPC group includes both the first and second APs.

[0236] In some embodiments, the MAPC group information includes one or more of the following: the main channel of the MAPC group; the NPCA main channel of each AP included in the MAPC group; the MAPC transmission policy supported by each AP included in the MAPC group; the disabled sub-channels of each AP included in the MAPC group; the AP ID of each AP included in the MAPC group; and the MAPC EDCA parameters; wherein the main channel of the MAPC group is the same as the main channel of the first AP.

[0237] As shown in Figure 9, after AP1 establishes a MAPC group with each AP (AP2 and AP3) in a one-to-one manner, AP1 announces the group information by sending a third frame (MAPC Group Info frame) to the member APs (such as AP2 and AP3) that have joined the MAPC group. The group information includes at least one of the following: the main channel of the MAPC group; the NPCA main channel of each AP included in the MAPC group; the MAPC transmission policy supported by each AP included in the MAPC group; the disabled sub-channels of each AP included in the MAPC group; the AP ID of each AP included in the MAPC group; and the MAPC EDCA parameters. The main channel of the MAPC group is the same as the main channel of the first AP.

[0238] In some embodiments, a third frame is transmitted in a non-high-throughput repetitive manner within the operating bandwidth of the first AP.

[0239] As shown in Figure 9 or Figure 10, AP1 broadcasts the third frame in a non-HT repeat manner in channels 1 (Ch_1) to 4 (Ch_4).

[0240] In some embodiments, a third frame is transmitted on the main channel of the first AP or on the NPCA main channel of the first AP.

[0241] The embodiments of this application do not limit the specific method of sending the third frame, but usually use a non-high throughput repetition method as an example for explanation.

[0242] In some embodiments, the third frame carries one or more of the following fields: common action field; main channel center frequency field; NPCA main channel field; MAPC transmission policy field; disabled sub-channel bitmap field; AP ID field; MAPC EDCA field; wherein the common action field is used to indicate the frame type; and the AP ID field is used to indicate the AP ID of each AP in the MAPC group.

[0243] Figure 13 illustrates a schematic diagram of the format of a third frame provided in an exemplary embodiment of this application. The numbers below each field indicate the number of bytes or bits it may occupy. In this embodiment, subfields may be simply referred to as fields. The third frame is based on a common action frame design, which supports cross-BSS communication.

[0244] The third frame includes at least one of the following fields: Frame Control field, Duration field, DA field, SA field, BSSID field, Sequence Control field, Frame Body field, and FCS field.

[0245] The frame control field occupies 2 bytes, the duration field occupies 2 bytes, the DA field occupies 6 bytes, the SA field occupies 6 bytes, the BSSID field occupies 6 bytes, the sequence control field occupies 2 bytes, the frame body field occupies a variable number of bytes, and the FCS field occupies 4 bytes.

[0246] In the third frame, the DA field is set to the broadcast address, and the BSSID field is set to the wildcard BSSID value, that is, all bits of the BSSID are set to 1.

[0247] The frame body fields include at least one of the following fields: Category, Public Action, Element ID, Length, Element ID Extension, and MAPC List-Info.

[0248] The category field occupies 1 byte, the common action field occupies 1 byte, the element ID field occupies 1 byte, the length field occupies 1 byte, the element ID extension field occupies 1 byte, and the MAPC list information field occupies 5*n+1 or 7*n+1 bytes, where n is a positive integer.

[0249] The category field is set to 4 to indicate that the frame belongs to the common action frame category. The reserved bits for the common action field are 46–255; a value of 47 indicates that the frame is a MAPC group information frame. The element ID field is set to 255, and the element ID extension field is set to 137 (or another reserved value) to indicate that the frame body field includes a MAPC list information field. The MAPC list information field is used to indicate relevant information about one or more AP sub-channels.

[0250] The MAPC list information fields include at least one of the following fields: the main channel center frequency (Pch CCF) field, and n MAPC information (MAPC Info) fields (from MAPC Info 1 field to MAPC Info n field).

[0251] The main channel center frequency field occupies 1 byte, and each MAPC information field occupies 5 or 7 bytes.

[0252] Taking the MAPC Info 1 field as an example, the MAPC Info 1 field includes at least one of the following fields: BSSID field, MAC Address field, AP ID field, MAPC Transmission Scheme field, NPCA Pch field, Disabled Subchannel Bitmap field, MAPC EDCA field, and reserved field.

[0253] Among them, the BSSID field and MAC address field are optional fields, the AP ID field occupies 16 bits, the MAPC transmission policy field occupies 4 bits, the NPCA main channel field occupies 8 bits, the disabled sub-channel bitmap field occupies 0 or 16 bits, the MAPC EDCA field occupies 8 bits, and the reserved field occupies 4 bits.

[0254] The AP ID field is the AP identifier assigned to each responding AP by the first AP (initiating AP) after collecting sub-channel information from each responding AP. The BSSID of the BSS where the AP is located and the AP's MAC address are optional. The Pch CCF field indicates the center frequency of the main channel. The NPCA Pch field indicates the channel number corresponding to the channel performing the NPCA operation. The Disabled Sub-channel Bitmap field indicates that the sub-channel bitmap is disabled. The MAPC EDCA field contains the EDCA parameters reconfigured by the first AP for MAPC.

[0255] The format of the third frame described above is an exemplary possibility. In different embodiments or designs, it is possible that at least one of the following designs may change: the position of the field in the frame, the order of arrangement with other fields, the number of bytes occupied, the number of bits occupied, the element name, and the field name. This embodiment does not limit this.

[0256] By sending a third frame, which indicates MAPC group information related to the MAPC group, all APs in the MAPC group are made aware of the MAPC group information, facilitating subsequent data transmission between APs.

[0257] 1.5 Exemplary embodiments of the MAPC discovery process;

[0258] To illustrate the MAPC discovery process, this application provides the following three embodiments in conjunction with the accompanying drawings.

[0259] 1.5.1 Basic MAPC discovery process;

[0260] Figure 14 illustrates a schematic diagram of the MAPC discovery process provided in an exemplary embodiment of this application.

[0261] AP1 is the initiator AP for the MAPC discovery process, while AP2 and AP3 are the responder APs. AP2's primary channel is the same as AP1's; AP3's primary channel is different from AP1's, but its NPCA primary channel is the same as AP1's; AP4's primary channel and NPCA primary channel are both different from AP1's.

[0262] As shown in Figure 14, AP1 broadcasts its first frame (MAPC discovery notification frame) across the BSS within its operating bandwidth in a non-HT repetitive manner, announcing the first MAPC information, such as AP1's primary channel, NPCA primary channel, and supported MAPC transmission strategies. The channel information request field in the MAPC discovery notification frame requests the response AP's MAPC parameters.

[0263] AP2 sends a second frame (MAPC discovery information frame) to AP1 on the main channel to inform it of the second MAPC information, such as AP2's main channel, NPCA main channel, supported MAPC transmission strategies, and whether it agrees to join the MAPC group; AP1 replies with an acknowledgment frame.

[0264] AP3 switches to the NPCA main channel to avoid OBSS interference and sends a second frame (MAPC discovery information frame) to AP1. AP1 replies with an acknowledgment frame.

[0265] AP4's main channel and NPCA main channel are different from AP1's main channel, so it does not join the MAPC group initiated by AP1 and does not perform a response operation.

[0266] AP1 establishes a MAPC group with AP2 and AP3 in a one-to-one manner. In the third frame (MAPC group information frame), AP1 announces the MAPC group information to the member APs (AP2 and AP3) that have joined the MAPC group.

[0267] 1.5.2 MAPC discovery process based on Target Wake Time (TWT);

[0268] In some embodiments, the first frame is sent outside the first service time; wherein the first service time is indicated by a TWT schedule, which is negotiated in advance by the first AP and the associated site.

[0269] Figure 15 illustrates a schematic diagram of the MAPC discovery process provided in an exemplary embodiment of this application.

[0270] AP1 is the initiating AP of the MAPC discovery process, and AP2 is the responding AP of the MAPC discovery process. AP2's primary channel is the same as AP1's. As shown in Figure 15, AP1 negotiates the TWT schedule with its associated non-AP STA (STA1) within its BSS1, for example, through frame exchange between TWT request (TWT Req) and TWT response (TWT Resp) frames.

[0271] The TWT schedule is used to indicate the Service Period (SP). STA1 performs BSS1 transmissions within the SP; during the T1 time period, i.e., the time outside the SP, it enters a doze state.

[0272] Within time T1, AP1 broadcasts the first frame across the BSS in a non-HT repetitive manner within its operating bandwidth, announcing the first MAPC information and requesting AP2 to provide the second MAPC information. AP1 and AP2 establish a MAPC group on a one-to-one basis. In the third frame, AP1 announces the MAPC group information to the APs that have joined the MAPC group. For specific implementation details, please refer to 1.5.1, which will not be repeated here.

[0273] The negotiated TWT schedule is intended to prioritize communication between APs outside of the SP (i.e., within T1 time). STA1 enters a sleep state outside of the SP to avoid interference or invalid transmissions within the BSS due to issues such as hidden terminals.

[0274] 1.5.3 MAPC discovery process based on RTWT;

[0275] In some embodiments, the first frame carries an RTWT schedule, which is used to indicate a second service time, and receiving the second frame includes receiving the second frame within the second service time.

[0276] Figure 16 illustrates a schematic diagram of the MAPC discovery process provided in an exemplary embodiment of this application.

[0277] AP1 initiates the MAPC discovery process, and AP2 responds to the MAPC discovery process. AP2 uses the same primary channel as AP1. As shown in Figure 16, AP1 broadcasts the first frame across the BSS within its operating bandwidth in a non-HT repetitive manner, announcing the first MAPC information and requesting AP2 to provide feedback on the second MAPC information. The first frame also carries the R-TWT1 schedule, indicating priority for inter-AP communication within the R-TWT SP (Second Service Time).

[0278] AP2 broadcasts the R-TWT1 schedule on its main channel within its BSS to indicate priority for inter-AP communication within the R-TWT SP.

[0279] Within R-TWT1 SP, AP2 sends a second frame to AP1 on its primary channel to inform it of the second MAPC information; AP1 replies with an acknowledgment frame. AP1 and AP2 establish a MAPC group in a one-to-one manner. In the third frame, AP1 announces the MAPC group information to the APs that have joined the MAPC group. For specific implementation details, refer to 1.5.1, which will not be repeated here.

[0280] Regarding the R-TWT1 schedule, upon receiving the R-TWT1 schedule, each responding AP will announce this R-TWT1 schedule within its BSS. Based on the protection mechanism for the R-TWT SP in relevant standards, the purpose of establishing this R-TWT is to prioritize communication between APs within the R-TWT SP, thereby avoiding interference or invalid transmissions within the BSS caused by issues such as hidden terminals.

[0281] 1.6 Fourth frame;

[0282] In some embodiments, the method further includes sending a fourth frame, the fourth frame being used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0283] Due to potential OBSS interference, adjacent APs need to transmit not only control signaling but also data. A link using only the 20MHz main channel cannot meet these data transmission requirements. Therefore, this application's embodiment designs a MAPC negotiation process. APs, considering data transmission needs and OBSS interference, exchange suitable subsets of channels for channel binding and perform channel binding, thereby widening the transmission link between APs.

[0284] In some embodiments, the transmitting AP and the receiving AP perform the MAPC negotiation process in a non-HT repetitive manner. This MAPC negotiation process serves the subsequent MAPC transmission strategy, which includes, but is not limited to: Co-TDMA, Co-RTWT, Co-BF, Co-SR, and seamless roaming.

[0285] In some embodiments, the fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0286] Figure 17 shows a schematic diagram of the MAPC negotiation process provided in an exemplary embodiment of this application.

[0287] In Figure 17, AP1 is the transmitting AP, and AP2 is the receiving AP. The transmitting AP sends an RTS frame or MU-RTS frame to one or more receiving APs. This frame includes a MAPC group identifier field to indicate support for MAPC or to announce MAPC negotiation. Upon receiving this frame, the receiving AP replies with a CTS frame.

[0288] In some embodiments, the fourth frame includes at least one of an RTS frame and a MU-RTS frame.

[0289] If only two APs participate in the communication, AP1 can send an RTS frame or a MU-RTS frame; if multiple APs need to participate in the communication, such as in Co-TDMA where polling is required, AP1 sends a MU-RTS frame. This embodiment only illustrates the example of AP1 sending a MU-RTS frame to AP2.

[0290] The site associated with AP1 (STA1) or the site associated with AP2 (STA2) sets the local network allocation vector (NAV) based on the duration field in the MU-RTS frame or CTS frame to remain silent.

[0291] 1.7 MAPC parameter negotiation;

[0292] In some embodiments, the method further includes: sending a first request frame, the first request frame being used to negotiate MAPC parameters required for MAPC data transmission, the MAPC parameters being used to help execute the MAPC transmission strategy.

[0293] In some embodiments, the method further includes: receiving a first response frame, the first response frame being used to respond to a first request frame.

[0294] In some embodiments, the method further includes sending a second response frame, the second response frame being used in response to the first response frame.

[0295] In the aforementioned MAPC negotiation process, this application's embodiments address the issues of insufficient MAPC link bandwidth and different interference sub-channels perceived by APs in different BSSs by designing a process for negotiating a candidate set of channel binding between the two APs. Furthermore, because the physical distance between APs on the same main channel is relatively large in the AP channel scanning mechanism, the APs need to negotiate some MAPC parameters, such as minimum or maximum transmit power, MCS, NSS, etc. The MAPC negotiation process includes MAPC parameter negotiation.

[0296] In some embodiments, the first request frame carries a field indicating the MAPC parameters suggested by the first AP.

[0297] Optionally, the first request frame also carries a first parameter command field, which indicates that the type of MAPC parameter negotiation is a suggested type, and the suggested type indicates that the MAPC parameters suggested by the first AP are used.

[0298] In some embodiments, the first response frame carries a field for indicating the MAPC parameters suggested by the second AP.

[0299] Optionally, the first response frame also carries a second parameter command field, which indicates that the type of MAPC parameter negotiation is an alternative type. The alternative type indicates that the MAPC parameters suggested by the second AP are different from those suggested by the first AP.

[0300] In some embodiments, the second response frame carries a field for indicating whether the second AP suggestion is accepted or rejected.

[0301] Optionally, the second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an acceptance type or a rejection type. The acceptance type is used to indicate that the MAPC parameters proposed by the second AP are accepted, and the rejection type is used to indicate that the MAPC parameters proposed by the second AP are rejected.

[0302] As shown in Figure 17, AP1 sends a first request frame (e.g., a parameter request frame). The parameter command field (first parameter command field) in the first request frame indicates the parameter negotiation type, including four types: Suggest, Accept, Reject, and Alternate. In the first request frame, this field is set to Suggest, indicating that the MAPC parameters suggested by AP1 should be used.

[0303] AP2 responds with a first response frame (e.g., a parameter response frame), which also contains a parameter command field (a second parameter command field). The second parameter command field is set to override, indicating the use of the MAPC parameters suggested by AP2, which differ from those suggested by AP1.

[0304] AP1 responds with a second response frame, which also contains a parameter command field (third parameter command field). The third parameter command field is set to accept or reject, indicating whether to accept or reject the MAPC parameters suggested by AP2.

[0305] After completing the MAPC parameter negotiation process, AP1, AP2 and their respective associated STA1 and STA2 perform MAPC transmission, including at least one of Co-TDMA, Co-BF, Co-SR, Co-OFDMA, Joint Transmission (JTX), and seamless roaming.

[0306] In some embodiments, sending a first request frame to sending a second response frame is an optional step.

[0307] In some embodiments, in seamless roaming scenarios, the MAPC parameter negotiation process is mandatory because user data needs to be forwarded between APs.

[0308] In some embodiments, the MAPC parameters include one or more of the following parameters: the proposed set of sub-channel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the proposed set of sub-channel candidates for binding includes the primary channel of the first AP, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0309] Since a link using only the 20MHz main channel cannot meet data transmission requirements, channel binding is performed using a set of candidate sub-channels for transmission proposal binding, thereby widening the inter-AP transmission link. If the MAPC parameter includes a configuration validity period, it indicates that the MAPC parameter can be used for one or more TXOPs in inter-AP communication, and the configuration validity period is used to indicate the applicable one or more TXOPs.

[0310] In some embodiments, the first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field;

[0311] Among them, the common action field is used to indicate the frame type; the parameter request field is used to indicate the initiator or responder of MAPC parameter negotiation; the parameter command field is used to indicate the type of MAPC parameter negotiation; the MAPC session start time field is used to indicate the start time of the configuration validity period, the configuration validity period is used to indicate the validity period of the MAPC parameters; and the MAPC session duration field is used to indicate the duration of the configuration validity period.

[0312] Figure 18 illustrates a schematic diagram of the format of a first request frame or a first response frame provided in an exemplary embodiment of this application. The numbers below each field indicate the number of bytes or bits it may occupy. In this embodiment, subfields may be simply referred to as fields. The first request frame and the first response frame are based on a common action frame design, which supports cross-BSS communication.

[0313] The first request frame or the first response frame includes at least one of the following fields: Category field, Public Action field, Dialog Token field, and MAPC Parameter element field.

[0314] The category field occupies 1 byte, the common action field occupies 1 byte, the dialogue mark field occupies 1 byte, and the MAPC parameter element field occupies 13 bytes.

[0315] The category field is set to 4 to indicate that the frame belongs to the common action frame category. The reserved bits of the common action field are 46 to 255. A value of 48 indicates that the frame is either a first request frame (parameter request frame) or a first response frame (parameter response frame).

[0316] MAPC parameter element fields include at least one of the following fields: Element ID field, Length field, Element ID Extension field, and MAPC Parameter Info field.

[0317] The element ID field occupies 1 byte, the length field occupies 1 byte, the element ID extension field occupies 1 byte, and the MAPC parameter information field occupies 10 bytes.

[0318] The element ID field is set to 255, and the element ID extension field is set to 139 (or other reserved value) to indicate that the MAPC parameter element field includes the MAPC parameter information field, which is used to indicate relevant information about the MAPC parameters.

[0319] MAPC parameter information fields include at least one of the following fields: Parameter Request field, Parameter Command field, Suggest bonding subchannel Bitmap field, MAPC Channel Width field, Minimum Transmit Power field, Maximum Transmit Power field, MCS field, NSS field, MAPC Session Start Time field, Period Unit field, MAPC Session Period field, and Reserved field.

[0320] The parameter request field occupies 1 bit, the parameter command field occupies 2 bits, the suggested sub-channel bitmap field occupies 16 bits, the MAPC channel bandwidth field occupies 3 bits, the minimum transmit power field occupies 8 bits, the maximum transmit power field occupies 8 bits, the MCS field occupies 4 bits, the NSS field occupies 3 bits, the MAPC session start time field occupies 16 bits, the time unit field occupies 4 bits, the MAPC session duration field occupies 8 bits, and the reserved field occupies 7 bits.

[0321] The parameter request field is used to indicate the initiator or responder of parameter negotiation. A value of 1 indicates the initiator of parameter negotiation, and a value of 0 indicates the responder of parameter negotiation; or, a value of 0 indicates the initiator of parameter negotiation, and a value of 1 indicates the responder of parameter negotiation. This application embodiment does not limit this.

[0322] The parameter command field is used to indicate the parameter negotiation type. A value of 0 indicates that the parameter negotiation type is Suggest, a value of 1 indicates that the parameter negotiation type is Accept, a value of 2 indicates that the parameter negotiation type is Alternate, and a value of 3 indicates that the parameter negotiation type is Reject. This application embodiment does not limit the correspondence between parameter negotiation type and value, but only uses the above correspondence as an example for illustration.

[0323] The "Suggested Subchannel Bitmap" field indicates the bitmap information of the suggested subchannel set for binding. The "MAPC Channel Bandwidth" field indicates the operating bandwidth for data transmission between APs. The "Minimum Transmit Power" field indicates the minimum transmit power of the first AP. The "Maximum Transmit Power" field indicates the maximum transmit power of the first AP. The "MCS" field indicates the MCS used for data transmission between APs. The "NSS" field indicates the number of spatial streams for data transmission between APs.

[0324] The MAPC session start time field indicates the start time of the configuration validity period. The time unit field indicates the minimum time slot unit of the configuration validity period, with a value of 0 to 3. A value of 0 indicates a minimum time slot unit of 32 microseconds; other values ​​are reserved. The MAPC session duration field indicates the total duration of the configuration validity period.

[0325] The format of the first request frame or the first response frame described above is an exemplary possibility. In different embodiments or designs, it is possible that at least one of the following designs may change: the position of the above fields in the frame, the order of arrangement with other fields, the number of bytes occupied, the number of bits occupied, the element name, and the field name. This embodiment does not limit this.

[0326] 1.8 Exemplary embodiments of the MAPC negotiation process;

[0327] To illustrate the MAPC negotiation process, this application provides the following two embodiments in conjunction with the accompanying drawings.

[0328] 1.8.1 MAPC negotiation process under Co-TDMA;

[0329] Figure 19 shows a schematic diagram of the MAPC negotiation process provided in an exemplary embodiment of this application.

[0330] AP1 is the transmitting AP, AP2 and AP3 are the receiving APs, STA1 is associated with AP1, STA2 is associated with AP2, and STA3 is associated with AP3. The primary channels of AP1, AP2, and AP3 are the same. This embodiment only uses Co-TDMA as an example for illustration, and the relevant MAPC negotiation process is also applicable to other transmission strategies. The same applies to the case where AP2 or AP3 is the transmitting AP and other APs are the receiving APs, and will not be described in detail here.

[0331] During TXOP1, AP1 sends MU-RTS frames to AP2 and AP3. The MU-RTS frame includes a MAPC group field, which indicates whether MAPC is supported or declares whether MAPC negotiation is to be performed. AP2 and AP3 reply with CTS frames after receiving the MU-RTS frames.

[0332] AP1 sends a first request frame (e.g., a parameter request frame) to AP2 and AP3 to negotiate parameters. The first request frame contains the MAPC parameters proposed by AP1.

[0333] AP2 and AP3 each reply with a first response frame (e.g., a parameter response frame). The parameter command field in the first response frame can be used to indicate the parameter negotiation type. Taking the example where the parameter negotiation type indicated by the first response frames from AP2 and AP3 is both "alternate," it includes the MAPC parameters suggested by AP2 and AP3, respectively.

[0334] AP1 responds with a second response frame. The second response frame indicates that the parameter negotiation type is accept or reject, and is used to indicate whether AP1 accepts or rejects the MAPC parameters suggested by AP2 or AP3.

[0335] In some embodiments, if the parameter negotiation type indicated by the first response frame replied by AP2 and AP3 is "accept", then AP1 does not need to reply with a second response frame.

[0336] In some embodiments, the method further includes: sending an Initial Control Frame (ICF), which polls the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; wherein the MAPC group is a set of APs used for cooperative data transmission, and the MAPC group includes a first AP. If a second AP agrees to join the MAPC group, the MAPC group includes both the first and second APs.

[0337] In some embodiments, the method further includes receiving an Initial Control Response (ICR) frame, the ICR frame being used to determine the APs participating in the MAPC transmission strategy.

[0338] In some embodiments, the method further includes: sending a MU-RTS frame to the target AP;

[0339] The target AP is the AP participating in the MAPC transmission strategy determined based on the ICR frame, and the MU-RTS frame is used to instruct the target AP to transmit data during the Transmission Opportunity Sharing (TXS) period.

[0340] As shown in Figure 19, following the MAPC parameter negotiation results (e.g., the transmit power obtained through negotiation), during TXOP2, AP1 sends an ICF to poll the member APs (AP2 and AP3) of the MAPC group to determine which APs will participate in Co-TDMA. In this embodiment, AP3 is a member AP and has sent an ICR frame to confirm its participation in Co-TDMA.

[0341] After completing the BSS1 transmission, AP1 sends a MU-RTS frame to AP3, sharing the TXOP with AP3. Upon receiving the MU-RTS frame, AP3 sends a CTS frame to AP1 and completes the BSS3 transmission within the TXS period. After completing the BSS3 transmission, AP3 returns the TXOP to AP1.

[0342] 1.8.2 MAPC Negotiation Process under Seamless Roaming;

[0343] Figure 20 shows a schematic diagram of the MAPC negotiation process provided in an exemplary embodiment of this application.

[0344] In some embodiments, the method further includes: receiving a seamless roaming request frame, the seamless roaming request frame being used to indicate that a first site requests roaming to a second AP, the first site being an associated site of the first AP.

[0345] When STA1 (the first site) moves from its original BSS to the target BSS to achieve seamless roaming, the original associated AP (AP1, the first AP) and the target AP (AP2, the second AP) need to exchange frames, such as transmitting STA ID information. AP1 also needs to forward STA1's downlink data to AP2 and negotiate to extend the inter-MAPC link bandwidth. AP1 is the transmitting AP, and AP2 is the receiving AP; AP1 and AP2 share the same primary channel. Figure 20 only shows the air interface frame exchange process during seamless roaming.

[0346] STA1 sends a Seamless Roaming Request frame to AP1, and AP1 replies with an acknowledgment frame.

[0347] AP1 sends a MU-RTS frame to AP2. The MU-RTS frame includes a MAPC group field, which indicates whether MAPC is supported or declares whether MAPC negotiation is to be performed. AP2 replies with a CTS frame after receiving the MU-RTS frame.

[0348] Since signaling interaction and context transfer are required between APs during roaming, and considering the potential insufficient bandwidth of the MAPC link, AP1 sends a first request frame (e.g., a parameter request frame) to AP2 to negotiate parameters based on the interference sub-channels sensed by AP1 and AP2. The first request frame contains MAPC parameters. AP2 replies with a first response frame (e.g., a parameter response frame) to negotiate parameters. For specific implementation details, please refer to the embodiment in Figure 17, which will not be repeated here.

[0349] Once the parameter negotiation is complete, AP1 and AP2 will transmit data in the negotiated bound sub-channels, such as context transfer and data frame transmission on channel 1 (Ch_1) to channel 3 (Ch_3).

[0350] In some embodiments, the method further includes sending a seamless roaming response frame, the seamless roaming response frame being used to indicate that seamless roaming has been completed.

[0351] After the data transmission is completed, AP1 sends a Seamless Roaming Response frame to STA1, and STA1 replies with an acknowledgment frame, thus completing the seamless roaming.

[0352] In summary, the method provided in this embodiment sends a first frame, which is used to indicate first MAPC information related to the first AP. The first MAPC information is used to indicate the information required for MAPC data transmission, thereby enabling other APs to obtain the first MAPC information and helping APs to cooperate in transmitting data.

[0353] The method provided in this embodiment also receives a second frame, which is used to indicate the second MAPC information related to the second AP, so that the first AP can determine whether the second AP agrees to join the MAPC group, thereby facilitating the first AP to determine the AP that will subsequently perform data transmission.

[0354] The method provided in this embodiment also sends a third frame, which is used to indicate the MAPC group information related to the MAPC group, so that the member APs of the MAPC group are uniformly aware of the MAPC group information, which facilitates subsequent data transmission between APs.

[0355] The method provided in this embodiment also negotiates the MAPC parameters to be used during MAPC transmission, such as minimum or maximum transmit power, MCS, and the proposed set of candidate sub-channels to be bound, by conducting a MAPC negotiation process with the second AP, such as exchanging first request frames and first response frames.

[0356] Figure 21 shows a flowchart of an inter-AP communication method provided in an exemplary embodiment of this application. The method is performed by a second AP and includes:

[0357] Step 2110: Receive the first frame.

[0358] The first frame is used to indicate the first MAPC information associated with the first AP, and the first MAPC information is used to indicate the information required for MAPC data transmission.

[0359] In some embodiments, a first frame is received; wherein the first frame is transmitted by the first AP in a non-high throughput repetitive manner within the operating bandwidth of the first AP; or, the first frame is transmitted by the first AP in a non-high throughput repetitive manner on at least two sub-channels of the operating bandwidth of the first AP.

[0360] In some embodiments, the first frame is received in a non-high-throughput duplicate manner within the operating bandwidth of the first AP; or, the first frame is received in a non-high-throughput duplicate manner on at least two sub-channels of the operating bandwidth of the first AP; or, the first frame is received on a single channel, the single channel being the same as the main channel of the first AP or the main channel of the NPCA, for example, the main channel of the second AP is the same as the main channel of the first AP.

[0361] In some embodiments, step 2110 is one of the steps included in the MAPC discovery process.

[0362] The device that initiates the MAPC discovery process is called the MAPC Initiator AP, and the device that responds to the MAPC discovery process is called the MAPC Responder AP. Both the MAPC Initiator AP and the MAPC Responder AP support MAPC transmission. The following explanation uses an example where the first AP is the MAPC Initiator AP and the second AP is the MAPC Responder AP.

[0363] For specific implementation details, please refer to the embodiment in Figure 8, which will not be repeated here.

[0364] 2.1 First MAPC information;

[0365] In some embodiments, the first MAPC information includes one or more of the following: the main channel of the first AP; the NPCA main channel of the first AP; the MAPC transmission policy supported by the first AP; and the disabled sub-channels of the first AP.

[0366] By way of example and not limitation, the MAPC transmission strategy includes at least one of the following: Co-TDMA; Co-RTWT; Co-BF; Co-SR; Seamless roaming.

[0367] In some embodiments, the first frame is also used to request the second AP to provide feedback on second MAPC information related to the second AP.

[0368] For specific implementation details, please refer to section 1.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0369] 2.2 Second MAPC information;

[0370] In some embodiments, the method further includes: sending a second frame, the second frame being used to indicate second MAPC information associated with a second AP;

[0371] The second frame is sent when the main channel of the second AP is the same as the main channel of the first AP; or, the second frame is sent when the NPCA main channel of the second AP is the same as the main channel of the first AP; or, the second frame is sent when the main channel of the second AP is the same as the NPCA main channel of the first AP; or, the second frame is sent when the NPCA main channel of the second AP is the same as the NPCA main channel of the first AP.

[0372] In some embodiments, the second MAPC information includes one or more of the following: the main channel of the second AP; the NPCA main channel of the second AP; the MAPC transmission policy supported by the second AP; the disabled sub-channels of the second AP; whether the second AP agrees to join the MAPC group; wherein, the MAPC group is a set of APs used for cooperative data transmission.

[0373] In some embodiments, the second frame is a MAPC discovery information frame, which is sent by the second AP when it switches to the second AP's NPCA main channel and the second AP's NPCA main channel is the same as the first AP's main channel.

[0374] Optionally, the second frame includes at least one of a MAPC discovery information frame and a MAPC discovery notification frame.

[0375] In some embodiments, the second frame is transmitted in a non-high-throughput repetitive manner on at least two channels, the at least two channels including at least one of the primary channel of the first AP and the NPCA primary channel of the first AP.

[0376] For specific implementation details, please refer to section 1.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0377] 2.3 Fields carried in the first or second frame;

[0378] In some embodiments, the first or second frame carries one or more of the following fields:

[0379] MAPC Group Field; Common Action Field; MAPC Transmission Policy Field; Main Channel Center Frequency Field; NPCA Main Channel Field; Disabled Sub-channel Bitmap Field; Channel Information Request Field; Accept or Reject Field;

[0380] Among them, the MAPC group field is used to indicate whether MAPC is supported; the common action field is used to indicate the frame type; the MAPC transmission policy field is used to indicate the supported MAPC transmission policy; the channel information request field is used to indicate the channel information requester or responder; and the accept or reject field is used to indicate whether to agree to join the MAPC group, which is a set of APs used for cooperative data transmission.

[0381] For specific implementation details, please refer to section 1.3 of the embodiment shown in Figure 8, which will not be repeated here.

[0382] 2.4 Third frame;

[0383] In some embodiments, the method further includes: receiving a third frame, the third frame being used to indicate MAPC group information associated with a MAPC group;

[0384] Among them, the MAPC group is a set of APs used for cooperative data transmission.

[0385] In some embodiments, the MAPC group information includes one or more of the following: the main channel of the MAPC group; the NPCA main channel of each AP included in the MAPC group; the MAPC transmission policy supported by each AP included in the MAPC group; the disabled sub-channels of each AP included in the MAPC group; the AP ID of each AP included in the MAPC group; and the MAPC EDCA parameters; wherein the main channel of the MAPC group is the same as the main channel of the first AP.

[0386] In some embodiments, a third frame is received, which is transmitted by the first AP in a non-high-throughput repetitive manner within the operating bandwidth of the first AP.

[0387] In some embodiments, a third frame is received in a non-high-throughput repetitive manner within the operating bandwidth of the first AP.

[0388] In some embodiments, a third frame is received on a single channel, which is the same channel as the primary channel of the first AP or the primary channel of the NPCA, for example, the primary channel of the second AP is the same as the primary channel of the first AP.

[0389] In some embodiments, the third frame carries one or more of the following fields: common action field; main channel center frequency field; NPCA main channel field; MAPC transmission policy field; disabled sub-channel bitmap field; AP ID field; MAPC EDCA field; wherein the common action field is used to indicate the frame type; and the AP ID field is used to indicate the AP ID of each AP in the MAPC group.

[0390] For specific implementation details, please refer to section 1.4 of the embodiment shown in Figure 8, which will not be repeated here.

[0391] 2.5 Exemplary embodiments of the MAPC discovery process;

[0392] To illustrate the MAPC discovery process, this application provides the following three embodiments in conjunction with the accompanying drawings.

[0393] 2.5.1 Basic MAPC discovery process;

[0394] Figure 14 illustrates a schematic diagram of the basic MAPC discovery process provided in an exemplary embodiment of this application.

[0395] AP1 is the initiator AP for the MAPC discovery process, while AP2 and AP3 are the responder APs for the MAPC discovery process. AP2's primary channel is the same as AP1's; AP3's primary channel is different from AP1's, but its NPCA primary channel is the same as AP1's; AP4's primary channel and NPCA primary channel are both different from AP1's primary channel.

[0396] For specific implementation details, please refer to section 1.5.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0397] 2.5.2 MAPC discovery process based on TWT;

[0398] In some embodiments, the first frame is received outside of the first service time; wherein the first service time is indicated by a TWT schedule, which is negotiated in advance by the first AP and the associated site.

[0399] For specific implementation details, please refer to section 1.5.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0400] 2.5.3 MAPC discovery process based on RTWT;

[0401] In some embodiments, the first frame carries an RTWT schedule, which is used to indicate a second service time, and sending the second frame includes sending the second frame within the second service time.

[0402] For specific implementation details, please refer to section 1.5.3 of the embodiment shown in Figure 8, which will not be repeated here.

[0403] 2.6 Fourth frame;

[0404] In some embodiments, the method further includes receiving a fourth frame, the fourth frame being used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0405] In some embodiments, the fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0406] In some embodiments, the fourth frame includes at least one of an RTS frame and a MU-RTS frame.

[0407] For specific implementation details, please refer to section 1.6 of the embodiment shown in Figure 8, which will not be repeated here.

[0408] 2.7 MAPC parameter negotiation;

[0409] In some embodiments, the method further includes: receiving a first request frame, the first request frame being used to negotiate MAPC parameters required for MAPC data transmission, the MAPC parameters being used to help execute the MAPC transmission strategy.

[0410] In some embodiments, the first request frame carries a field indicating the MAPC parameters suggested by the first AP.

[0411] Optionally, the first request frame also carries a first parameter command field, which indicates that the type of MAPC parameter negotiation is a suggestion type.

[0412] In some embodiments, the method further includes: sending a first response frame, the first response frame being used to respond to a first request frame.

[0413] In some embodiments, the first response frame carries a field for indicating the MAPC parameters suggested by the second AP.

[0414] Optionally, the first response frame also carries a second parameter command field, which is used to indicate that the type of MAPC parameter negotiation is an alternative type.

[0415] In some embodiments, the method further includes: receiving a second response frame, the second response frame being used in response to the first response frame.

[0416] In some embodiments, the second response frame carries a field for indicating whether the second AP suggestion is accepted or rejected.

[0417] Optionally, the second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type.

[0418] In some embodiments, the MAPC parameters include one or more of the following parameters: the proposed set of sub-channel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the proposed set of sub-channel candidates for binding includes the primary channel of the first AP, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0419] In some embodiments, the first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field;

[0420] Among them, the common action field is used to indicate the frame type; the parameter request field is used to indicate the initiator or responder of MAPC parameter negotiation; the parameter command field is used to indicate the type of MAPC parameter negotiation; the MAPC session start time field is used to indicate the start time of the configuration validity period, the configuration validity period is used to indicate the validity period of the MAPC parameters; and the MAPC session duration field is used to indicate the duration of the configuration validity period.

[0421] For specific implementation details, please refer to section 1.7 of the embodiment shown in Figure 8, which will not be repeated here.

[0422] 2.8 Exemplary embodiments of the MAPC negotiation process;

[0423] To illustrate the MAPC negotiation process, this application provides the following two embodiments in conjunction with the accompanying drawings.

[0424] 2.8.1 MAPC negotiation process under Co-TDMA;

[0425] In some embodiments, the method further includes: receiving an ICF, which is used to poll APs in a MAPC group to determine APs participating in the MAPC transmission strategy; wherein, a MAPC group is a set of APs used for cooperative data transmission.

[0426] In some embodiments, the method further includes: sending an ICR frame, the ICR frame being used to determine the APs participating in the MAPC transmission strategy.

[0427] In some embodiments, the second AP is a target AP, which is an AP participating in the MAPC transmission strategy determined based on the ICR frame. The method further includes: receiving a MU-RTS frame; wherein the MU-RTS frame is used to instruct the target AP to transmit data during the TXS time period.

[0428] For specific implementation details, please refer to section 1.8.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0429] 2.8.2 MAPC Negotiation Process under Seamless Roaming;

[0430] Figure 20 shows a schematic diagram of the MAPC negotiation process provided in an exemplary embodiment of this application.

[0431] When STA1 (the first site) moves from its original BSS to the target BSS to achieve seamless roaming, the original associated AP (AP1, the first AP) and the target AP (AP2, the second AP) need to exchange frames, such as transmitting STA ID information. AP1 also needs to forward STA1's downlink data to AP2 and negotiate to extend the inter-MAPC link bandwidth. AP1 is the transmitting AP, and AP2 is the receiving AP; AP1 and AP2 share the same primary channel. Figure 20 only shows the air interface frame exchange process during seamless roaming.

[0432] For specific implementation details, please refer to section 1.8.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0433] In summary, the method provided in this embodiment enables the second AP to obtain the first MAPC information by receiving a first frame, which is used to indicate first MAPC information related to the first AP and the first MAPC information is used to indicate the information required for MAPC data transmission.

[0434] The method provided in this embodiment also sends a second frame, which is used to indicate the second MAPC information related to the second AP, so that the first AP can determine whether the second AP agrees to join the MAPC group, thereby facilitating the first AP to determine the AP that will subsequently perform data transmission.

[0435] The method provided in this embodiment also receives a third frame, which is used to indicate MAPC group information related to the MAPC group, so that the member APs of the MAPC group are uniformly aware of the MAPC group information, which facilitates subsequent data transmission between APs.

[0436] The method provided in this embodiment also negotiates the MAPC parameters to be used during MAPC transmission, such as minimum or maximum transmit power, MCS, and the proposed set of candidate sub-channels to be bound, by conducting a MAPC negotiation process with the first AP, such as exchanging first request frames and first response frames.

[0437] Figure 22 shows a flowchart of a parameter negotiation method provided in an exemplary embodiment of this application. The method is executed by a first AP and includes:

[0438] Step 2210: Send the first request frame.

[0439] The first request frame is used to negotiate the MAPC parameters required for MAPC data transmission.

[0440] MAPC includes a first AP and a second AP. MAPC parameters are used to help execute the MAPC transmission strategy. Step 2210 is a step in the MAPC negotiation process. The MAPC negotiation process is decoupled from the MAPC discovery process in the embodiment of Figure 8. That is, the embodiment of Figure 22 can be implemented independently of the embodiment of Figure 8, and does not necessarily need to be implemented in combination with the embodiment of Figure 8.

[0441] 3.1 MAPC parameter negotiation;

[0442] In some embodiments, the method further includes: receiving a first response frame, the first response frame being used to respond to a first request frame.

[0443] In some embodiments, the method further includes sending a second response frame, the second response frame being used in response to the first response frame.

[0444] In some embodiments, the first request frame carries a field indicating the MAPC parameters suggested by the first AP.

[0445] Optionally, the first request frame also carries a first parameter command field, which indicates that the type of MAPC parameter negotiation is a suggested type, and the suggested type indicates that the MAPC parameters suggested by the first AP are used.

[0446] In some embodiments, the first response frame carries a field for indicating the MAPC parameters suggested by the second AP.

[0447] Optionally, the first response frame also carries a second parameter command field, which indicates that the type of MAPC parameter negotiation is an alternative type. The alternative type indicates that the MAPC parameters suggested by the second AP are different from those suggested by the first AP.

[0448] In some embodiments, the second response frame carries a field for indicating whether the second AP suggestion is accepted or rejected.

[0449] Optionally, the second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an acceptance type or a rejection type. The acceptance type is used to indicate that the MAPC parameters proposed by the second AP are accepted, and the rejection type is used to indicate that the MAPC parameters proposed by the second AP are rejected.

[0450] In some embodiments, the MAPC parameters include one or more of the following parameters: the proposed set of sub-channel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the proposed set of sub-channel candidates for binding includes the primary channel of the first AP, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0451] In some embodiments, the first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field;

[0452] Among them, the common action field is used to indicate the frame type; the parameter request field is used to indicate the initiator or responder of MAPC parameter negotiation; the parameter command field is used to indicate the type of MAPC parameter negotiation; the MAPC session start time field is used to indicate the start time of the configuration validity period, the configuration validity period is used to indicate the validity period of the MAPC parameters; and the MAPC session duration field is used to indicate the duration of the configuration validity period.

[0453] For specific implementation details, please refer to section 1.7 of the embodiment shown in Figure 8, which will not be repeated here.

[0454] 3.2 Fourth frame;

[0455] In some embodiments, the method further includes sending a fourth frame, the fourth frame being used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0456] In some embodiments, the fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0457] In some embodiments, the fourth frame includes at least one of an RTS frame and a MU-RTS frame.

[0458] For specific implementation details, please refer to section 1.6 of the embodiment shown in Figure 8, which will not be repeated here.

[0459] 3.3 Exemplary embodiments of the MAPC negotiation process;

[0460] To illustrate the MAPC negotiation process, this application provides the following two embodiments in conjunction with the accompanying drawings.

[0461] 3.3.1 MAPC negotiation process under Co-TDMA;

[0462] In some embodiments, the method further includes: sending an ICF (Information Council Form) to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; wherein the MAPC group is a set of APs used for cooperative data transmission, and the MAPC group includes a first AP. If a second AP agrees to join the MAPC group, the MAPC group includes both the first and second APs.

[0463] In some embodiments, the method further includes: receiving an ICR frame, the ICR frame being used to determine the APs participating in the MAPC transmission strategy.

[0464] In some embodiments, the method further includes: sending a MU-RTS frame to the target AP;

[0465] The target AP is determined based on the ICR frame and is an AP participating in the MAPC transmission strategy. The MU-RTS frame is used to indicate that the target AP will transmit data during the TXS time period.

[0466] For specific implementation details, please refer to section 1.8.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0467] 3.3.2 MAPC Negotiation Process under Seamless Roaming;

[0468] In some embodiments, the method further includes: receiving a seamless roaming request frame, the seamless roaming request frame being used to indicate that a first site requests roaming to a second AP, the first site being an associated site of the first AP.

[0469] In some embodiments, the method further includes sending a seamless roaming response frame, the seamless roaming response frame being used to indicate that seamless roaming has been completed.

[0470] For specific implementation details, please refer to section 1.8.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0471] In summary, the method provided in this embodiment negotiates the MAPC parameters to be used during MAPC transmission, such as minimum or maximum transmit power, MCS, and the proposed set of candidate sub-channels, by conducting a MAPC negotiation process with the second AP, such as exchanging first request frames and first response frames.

[0472] Figure 23 shows a flowchart of a parameter negotiation method provided in an exemplary embodiment of this application, which is executed by a second AP and includes:

[0473] Step 2310: Receive the first request frame.

[0474] The first request frame is used to negotiate the MAPC parameters required for MAPC data transmission.

[0475] MAPC includes a first AP and a second AP. The MAPC parameters are used to help implement the MAPC transmission strategy.

[0476] 4.1 MAPC parameter negotiation;

[0477] In some embodiments, the first request frame carries a field indicating the MAPC parameters suggested by the first AP.

[0478] Optionally, the first request frame also carries a first parameter command field, which indicates that the type of MAPC parameter negotiation is a suggestion type.

[0479] In some embodiments, the method further includes: sending a first response frame, the first response frame being used to respond to a first request frame.

[0480] In some embodiments, the first response frame carries a field for indicating the MAPC parameters suggested by the second AP.

[0481] Optionally, the first response frame also carries a second parameter command field, which is used to indicate that the type of MAPC parameter negotiation is an alternative type.

[0482] In some embodiments, the method further includes: receiving a second response frame, the second response frame being used in response to the first response frame.

[0483] In some embodiments, the second response frame carries a field for indicating whether the second AP suggestion is accepted or rejected.

[0484] Optionally, the second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type.

[0485] In some embodiments, the MAPC parameters include one or more of the following parameters: the proposed set of sub-channel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the proposed set of sub-channel candidates for binding includes the primary channel of the first AP, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0486] In some embodiments, the first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field;

[0487] Among them, the common action field is used to indicate the frame type; the parameter request field is used to indicate the initiator or responder of MAPC parameter negotiation; the parameter command field is used to indicate the type of MAPC parameter negotiation; the MAPC session start time field is used to indicate the start time of the configuration validity period, the configuration validity period is used to indicate the validity period of the MAPC parameters; and the MAPC session duration field is used to indicate the duration of the configuration validity period.

[0488] For specific implementation details, please refer to section 1.7 of the embodiment shown in Figure 8, which will not be repeated here.

[0489] 4.2 Fourth frame;

[0490] In some embodiments, the method further includes receiving a fourth frame, the fourth frame being used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0491] In some embodiments, the fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0492] In some embodiments, the fourth frame includes at least one of an RTS frame and a MU-RTS frame.

[0493] For specific implementation details, please refer to section 1.6 of the embodiment shown in Figure 8, which will not be repeated here.

[0494] 4.3 Exemplary embodiments of the MAPC negotiation process;

[0495] To illustrate the MAPC negotiation process, this application provides the following two embodiments in conjunction with the accompanying drawings.

[0496] 4.3.1 MAPC negotiation process under Co-TDMA;

[0497] In some embodiments, the method further includes: receiving an ICF, which is used to poll APs in a MAPC group to determine APs participating in the MAPC transmission strategy; wherein, a MAPC group is a set of APs used for cooperative data transmission.

[0498] In some embodiments, the method further includes: sending an ICR frame, the ICR frame being used to determine the APs participating in the MAPC transmission strategy.

[0499] In some embodiments, the second AP is a target AP, which is an AP participating in the MAPC transmission strategy determined based on the ICR frame. The method further includes: receiving a MU-RTS frame; wherein the MU-RTS frame is used to instruct the target AP to transmit data during the TXS time period.

[0500] For specific implementation details, please refer to section 1.8.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0501] 4.3.2 MAPC Negotiation Process under Seamless Roaming;

[0502] Figure 20 shows a schematic diagram of the MAPC negotiation process provided in an exemplary embodiment of this application.

[0503] When STA1 (the first site) moves from its original BSS to the target BSS to achieve seamless roaming, the original associated AP (AP1, the first AP) and the target AP (AP2, the second AP) need to exchange frames, such as transmitting STA ID information. AP1 also needs to forward STA1's downlink data to AP2 and negotiate to extend the inter-MAPC link bandwidth. AP1 is the transmitting AP, and AP2 is the receiving AP; AP1 and AP2 share the same primary channel. Figure 20 only shows the air interface frame exchange process during seamless roaming.

[0504] For specific implementation details, please refer to section 1.8.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0505] In summary, the method provided in this embodiment negotiates the MAPC parameters to be used during MAPC transmission, such as minimum or maximum transmit power, MCS, and the proposed set of candidate sub-channels to be bound, by conducting a MAPC negotiation process with the first AP, such as exchanging first request frames and first response frames.

[0506] Figure 24 shows a flowchart of an inter-AP communication method provided in an exemplary embodiment of this application. The method is performed by a first AP and includes:

[0507] Step 2410: Receive and / or send at least one frame.

[0508] At least one frame is associated with the MAPC discovery process, which is used to help MAPC transmit data.

[0509] In some embodiments, at least one frame includes at least one of a first frame, a second frame, and a third frame;

[0510] The first frame indicates the first MAPC information associated with the first AP, which indicates the information required for MAPC data transmission; the second frame indicates the second MAPC information associated with the second AP; and the third frame indicates the MAPC group information associated with the MAPC group, which is a set of APs used for cooperative data transmission.

[0511] In some embodiments, at least one frame includes a first frame and a second frame. The first AP transmits the first frame in a non-high-throughput repetitive manner within its operating bandwidth. The first AP receives the second frame, which is transmitted in a non-high-throughput repetitive manner on at least two channels, including at least one of the first AP's primary channel and the first AP's NPCA primary channel.

[0512] In some embodiments, at least one frame includes a first frame, a second frame, and a third frame. The first AP transmits the first frame in a non-high-throughput repetitive manner within its operating bandwidth. The first AP receives the second frame, which is transmitted in a non-high-throughput repetitive manner on at least two channels, including at least one of the first AP's primary channel and the first AP's NPCA primary channel. The first AP transmits the third frame in a non-high-throughput repetitive manner within its operating bandwidth.

[0513] 5.1 First frame;

[0514] In some embodiments, the first frame is transmitted in a non-high-throughput duplicate manner within the operating bandwidth of the first AP; or, the first frame is transmitted in a non-high-throughput duplicate manner on at least two sub-channels of the operating bandwidth of the first AP.

[0515] The device initiating the MAPC discovery process is called the MAPC Initiator AP, and the device responding to the MAPC discovery process is called the MAPC Responder AP. Both the MAPC Initiator AP and the MAPC Responder AP support MAPC transmission. In this embodiment, MAPC includes a first AP and a second AP. The following description uses the first AP as the MAPC Initiator AP and the second AP as the MAPC Responder AP as an example.

[0516] The following issues are addressed: (a) The main channel of the MAPC response AP is the same as that of the MAPC initiating AP, but when the MAPC response AP temporarily switches to its NPCA main channel, it cannot receive beacon frames sent by the MAPC initiating AP; (b) The main channel of the MAPC response AP is different from that of the MAPC initiating AP, but the NPCA main channel of the MAPC response AP is the same as that of the MAPC initiating AP. When the MAPC response AP switches to the NPCA main channel, it cannot cooperate with the MAPC initiating AP to avoid interference.

[0517] The MAPC discovery process is designed as follows: the AP that initiates the MAPC broadcasts its first frame (e.g., a MAPC discovery notification frame) across the BSS in a non-HT duplicate manner within the operating bandwidth, announcing its primary channel, NPCA primary channel, supported MAPC transmission strategies, and other information.

[0518] In some embodiments, the first MAPC information includes one or more of the following: the primary channel of the first AP; the NPCA primary channel of the first AP; the MAPC coordination Transmission Scheme supported by the first AP; and the disabled sub-channels of the first AP.

[0519] By way of example and not limitation, the MAPC transmission strategy includes at least one of the following: Co-TDMA; Co-RTWT; Co-BF; Co-SR; and seamless roaming. In the embodiments of this application, the MAPC transmission strategy may also be referred to as the MAPC Transmission Scheme, MAPC strategy, etc.

[0520] In some embodiments, the first frame is also used to request the second AP to provide feedback on second MAPC information related to the second AP.

[0521] For specific implementation details, please refer to section 1.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0522] 5.2 Second frame;

[0523] In some embodiments, the second frame is used to indicate second MAPC information associated with the second AP;

[0524] The second frame is sent when the main channel of the second AP is the same as the main channel of the first AP; or, the second frame is sent when the NPCA main channel of the second AP is the same as the main channel of the first AP; or, the second frame is sent when the main channel of the second AP is the same as the NPCA main channel of the first AP; or, the second frame is sent when the NPCA main channel of the second AP is the same as the NPCA main channel of the first AP.

[0525] In some embodiments, the second MAPC information includes one or more of the following: the main channel of the second AP; the NPCA main channel of the second AP; the MAPC transmission policy supported by the second AP; the disabled sub-channels of the second AP; whether the second AP agrees to join the MAPC group; wherein, the MAPC group is a set of APs used for cooperative data transmission.

[0526] In some embodiments, the second frame is a MAPC discovery information frame, which is sent by the second AP when it switches to the second AP's NPCA main channel and the second AP's NPCA main channel is the same as the first AP's main channel.

[0527] Optionally, the second frame includes at least one of a MAPC discovery information frame and a MAPC discovery notification frame.

[0528] In some embodiments, the second frame is transmitted in a non-high-throughput repetitive manner on at least two channels, the at least two channels including at least one of the primary channel of the first AP and the NPCA primary channel of the first AP.

[0529] For specific implementation details, please refer to section 1.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0530] 5.3 Fields carried in the first or second frame;

[0531] In some embodiments, the first or second frame carries one or more of the following fields:

[0532] MAPC Group Field; Common Action Field; MAPC Transmission Policy Field; Main Channel Center Frequency Field; NPCA Main Channel Field; Disabled Sub-channel Bitmap Field; Channel Information Request Field; Accept or Reject Field;

[0533] The MAPC group field indicates whether MAPC is supported; the common action field indicates the frame type; the MAPC transmission policy field indicates the supported MAPC transmission policy; the channel information request field indicates the channel information requester or responder; and the accept or reject field indicates whether to agree to join the MAPC group. The MAPC group is a set of APs used for cooperative data transmission. The MAPC group includes the first AP. If the second AP agrees to join the MAPC group, the MAPC group includes the first AP and the second AP.

[0534] For specific implementation details, please refer to section 1.3 of the embodiment shown in Figure 8, which will not be repeated here.

[0535] 5.4 Third frame;

[0536] In some embodiments, the third frame is used to indicate MAPC group information associated with the MAPC group;

[0537] The MAPC group is a set of APs used for cooperative data transmission. The MAPC group includes the first AP. If the second AP agrees to join the MAPC group, the MAPC group includes both the first and second APs.

[0538] In some embodiments, the MAPC group information includes one or more of the following: the main channel of the MAPC group; the NPCA main channel of each AP included in the MAPC group; the MAPC transmission policy supported by each AP included in the MAPC group; the disabled sub-channels of each AP included in the MAPC group; the AP ID of each AP included in the MAPC group; and the MAPC EDCA parameters; wherein the main channel of the MAPC group is the same as the main channel of the first AP.

[0539] In some embodiments, a third frame is transmitted in a non-high-throughput repetitive manner within the operating bandwidth of the first AP.

[0540] In some embodiments, the third frame carries one or more of the following fields: common action field; main channel center frequency field; NPCA main channel field; MAPC transmission policy field; disabled sub-channel bitmap field; AP ID field; MAPC EDCA field; wherein the common action field is used to indicate the frame type; and the AP ID field is used to indicate the AP ID of each AP in the MAPC group.

[0541] For specific implementation details, please refer to section 1.4 of the embodiment shown in Figure 8, which will not be repeated here.

[0542] 5.5 Exemplary embodiments of the MAPC discovery process;

[0543] To illustrate the MAPC discovery process, this application provides the following three embodiments in conjunction with the accompanying drawings.

[0544] 5.5.1 Basic MAPC discovery process;

[0545] Figure 14 illustrates a schematic diagram of the MAPC discovery process provided in an exemplary embodiment of this application.

[0546] AP1 is the initiator AP for the MAPC discovery process, while AP2 and AP3 are the responder APs for the MAPC discovery process. AP2's primary channel is the same as AP1's; AP3's primary channel is different from AP1's, but its NPCA primary channel is the same as AP1's; AP4's primary channel and NPCA primary channel are both different from AP1's primary channel.

[0547] For specific implementation details, please refer to section 1.5.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0548] 5.5.2 MAPC discovery process based on TWT;

[0549] In some embodiments, the first frame is sent outside the first service time; wherein the first service time is indicated by a TWT schedule, which is negotiated in advance by the first AP and the associated site.

[0550] For specific implementation details, please refer to section 1.5.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0551] 5.5.3 MAPC discovery process based on RTWT;

[0552] In some embodiments, the first frame carries an RTWT schedule, which is used to indicate a second service time, and receiving the second frame includes receiving the second frame within the second service time.

[0553] For specific implementation details, please refer to section 1.5.3 of the embodiment shown in Figure 8, which will not be repeated here.

[0554] In summary, the method provided in this embodiment executes the MAPC discovery process by receiving and / or sending at least one frame, which is related to the MAPC discovery process. The MAPC discovery process enables a first AP to discover other APs, thereby facilitating collaborative data transmission between APs.

[0555] Figure 25 shows a flowchart of an inter-AP communication method provided in an exemplary embodiment of this application. The method is performed by a first AP and includes:

[0556] Step 2510: Receive and / or send at least one frame.

[0557] At least one frame is associated with the MAPC negotiation process, which is used to help MAPC transmit data.

[0558] In some embodiments, at least one frame includes at least one of a fourth frame, a first request frame, a first response frame, a second response frame, an ICF, an ICR frame, a MU-RTS frame, a seamless roaming request frame, and a seamless roaming response frame;

[0559] The fourth frame indicates support for MAPC or indicates the execution of MAPC negotiation; the first request frame negotiates the MAPC parameters required for MAPC data transmission, which help execute the MAPC transmission strategy; the first response frame responds to the first request frame; the second response frame responds to the first response frame; the ICF polls the APs in the MAPC group to determine which APs participate in the MAPC transmission strategy, where the MAPC group is a set of APs used for cooperative data transmission; the ICR frame determines which APs participate in the MAPC transmission strategy; the MU-RTS frame instructs the target AP to transmit data during the TXS time period, where the target AP is an AP participating in the MAPC transmission strategy determined based on the ICR frame; the seamless roaming request frame instructs the first site to request roaming to the second AP, where the first site is the associated site of the first AP; and the seamless roaming response frame indicates the completion of seamless roaming.

[0560] In some embodiments, at least one frame includes a fourth frame, a first request frame, and a first response frame. The first AP sends the fourth frame to the second AP, and the second AP replies with a CTS frame after receiving the fourth frame. The first AP sends the first request frame to the second AP, and the second AP replies with a first response frame after receiving the first request frame.

[0561] In some embodiments, at least one frame includes a fourth frame, a first request frame, a first response frame, and a second response frame. The first AP sends the fourth frame to the second AP, and the second AP replies with a CTS frame after receiving the fourth frame. The first AP sends the first request frame to the second AP, and the second AP replies with a first response frame after receiving the first request frame. The first AP then sends the second response frame after receiving the first response frame.

[0562] In some embodiments, at least one frame includes a fourth frame, a first request frame, a first response frame (or a first response frame and a second response frame), an ICF, an ICR frame, and a MU-RTS frame. The first AP sends the fourth frame to the second AP, and the second AP replies with a CTS frame after receiving the fourth frame. The first AP sends the first request frame to the second AP, and the second AP replies with a first response frame after receiving the first request frame. The first AP sends an ICF, the target AP replies with an ICR frame after receiving the ICF, and the first AP sends a MU-RTS frame to the target AP.

[0563] In some embodiments, at least one frame includes a fourth frame, a first request frame, a first response frame (or a first response frame and a second response frame), a seamless roaming request frame, and a seamless roaming response frame. The first AP receives a seamless roaming request frame sent by a first site. The first AP sends a fourth frame to a second AP, and the second AP replies with a CTS frame after receiving the fourth frame. The first AP sends a first request frame to the second AP, and the second AP replies with a first response frame after receiving the first request frame. After seamless roaming is completed, the second AP sends a seamless roaming response frame to the first AP.

[0564] 6.1 MAPC parameter negotiation;

[0565] In some embodiments, the first request frame carries a field indicating the MAPC parameters suggested by the first AP.

[0566] Optionally, the first request frame also carries a first parameter command field, which indicates that the type of MAPC parameter negotiation is a suggested type, and the suggested type indicates that the MAPC parameters suggested by the first AP are used.

[0567] In some embodiments, the first response frame carries a field for indicating the MAPC parameters suggested by the second AP.

[0568] Optionally, the first response frame also carries a second parameter command field, which indicates that the type of MAPC parameter negotiation is an alternative type. The alternative type indicates that the MAPC parameters suggested by the second AP are different from those suggested by the first AP.

[0569] In some embodiments, the second response frame carries a field for indicating whether the second AP suggestion is accepted or rejected.

[0570] Optionally, the second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an acceptance type or a rejection type. The acceptance type is used to indicate that the MAPC parameters proposed by the second AP are accepted, and the rejection type is used to indicate that the MAPC parameters proposed by the second AP are rejected.

[0571] In some embodiments, the MAPC parameters include one or more of the following parameters: the proposed set of sub-channel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the proposed set of sub-channel candidates for binding includes the primary channel of the first AP, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0572] In some embodiments, the first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field;

[0573] Among them, the common action field is used to indicate the frame type; the parameter request field is used to indicate the initiator or responder of MAPC parameter negotiation; the parameter command field is used to indicate the type of MAPC parameter negotiation; the MAPC session start time field is used to indicate the start time of the configuration validity period, the configuration validity period is used to indicate the validity period of the MAPC parameters; and the MAPC session duration field is used to indicate the duration of the configuration validity period.

[0574] For specific implementation details, please refer to section 1.7 of the embodiment shown in Figure 8, which will not be repeated here.

[0575] 6.2 Fourth frame;

[0576] In some embodiments, the fourth frame is used to indicate support for MAPC, or to indicate the performance of MAPC negotiation.

[0577] In some embodiments, the fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0578] In some embodiments, the fourth frame includes at least one of an RTS frame and a MU-RTS frame.

[0579] For specific implementation details, please refer to section 1.6 of the embodiment shown in Figure 8, which will not be repeated here.

[0580] 6.3 Exemplary embodiments of the MAPC negotiation process;

[0581] To illustrate the MAPC negotiation process, this application provides the following two embodiments in conjunction with the accompanying drawings.

[0582] 6.3.1 MAPC negotiation process under Co-TDMA;

[0583] In some embodiments, the ICF polls the APs in the MAPC group to determine which APs participate in the MAPC transmission strategy; wherein, the MAPC group is a set of APs used for cooperative data transmission, and the MAPC group includes a first AP. If a second AP agrees to join the MAPC group, the MAPC group includes both the first and second APs.

[0584] In some embodiments, the ICR frame is used to determine the APs participating in the MAPC transmission strategy.

[0585] In some embodiments, the target AP is an AP participating in the MAPC transmission strategy determined based on the ICR frame, and the MU-RTS frame is used to instruct the target AP to transmit data during the TXS time period.

[0586] For specific implementation details, please refer to section 1.8.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0587] 6.3.2 MAPC Negotiation Process under Seamless Roaming;

[0588] In some embodiments, a seamless roaming request frame is used to instruct a first site to roam to a second AP, the first site being an associated site of the first AP.

[0589] In some embodiments, a seamless roaming response frame is used to indicate that seamless roaming has been completed.

[0590] For specific implementation details, please refer to section 1.8.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0591] In summary, the method provided in this embodiment executes the MAPC negotiation process by receiving and / or sending at least one frame, which is related to the MAPC negotiation process. The MAPC negotiation process enables the first AP to negotiate MAPC parameters with other APs, thereby facilitating collaborative data transmission between APs.

[0592] In the above embodiments, the embodiments corresponding to FIG8, FIG21, FIG22, FIG23, FIG24, and FIG25 can be implemented individually or in combination. For example, the embodiments corresponding to FIG8 and FIG21 can be implemented in combination, the embodiments corresponding to FIG22 and FIG23 can be implemented in combination, and the embodiments corresponding to FIG24 and FIG25 can be implemented in combination. This application does not limit this.

[0593] Figure 26 shows a block diagram of a first wireless device provided in an exemplary embodiment of this application. The device can be implemented as a first access point (AP) or as part of a first AP via software, hardware, or a combination of both. The device includes:

[0594] Transmitting module 2610 is used to transmit a first frame, the first frame being used to indicate first MAPC information related to the first wireless device;

[0595] The first MAPC information is used to indicate the information required for MAPC to transmit data.

[0596] In one possible design of this embodiment, the transmitting module 2610 is configured to transmit the first frame in a non-high-throughput duplicate (non-HT duplicate) manner within the operating bandwidth of the first wireless device; or, transmit the first frame in a non-high-throughput duplicate manner on at least two sub-channels of the operating bandwidth of the first wireless device.

[0597] For specific implementation details, please refer to the embodiment in Figure 8, which will not be repeated here.

[0598] 7.1 First MAPC information;

[0599] In one possible design of this embodiment, the first MAPC information includes one or more of the following: the main channel of the first wireless device; the NPCA main channel of the first wireless device; the MAPC transmission strategy supported by the first wireless device; and the disabled sub-channels of the first wireless device.

[0600] By way of example and not limitation, the MAPC transmission strategy includes at least one of the following: Co-TDMA; Co-RTWT; Co-BF; Co-SR; seamless roaming. In the embodiments of this application, the MAPC transmission strategy may also be referred to simply as the MAPC transmission strategy.

[0601] In one possible design of this embodiment, the first frame is also used to request the second wireless device to provide feedback on the second MAPC information related to the second wireless device.

[0602] For specific implementation details, please refer to section 1.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0603] 7.2 Second MAPC Information;

[0604] In one possible design of this embodiment, the receiving module 2620 is used to receive a second frame, which is used to indicate second MAPC information related to the second wireless device; wherein, the second frame is sent when the main channel of the second wireless device is the same as the main channel of the first wireless device; or, the second frame is sent when the main channel of the second wireless device is the same as the main channel of the first wireless device; or, the second frame is sent when the main channel of the second wireless device is the same as the main channel of the first wireless device; or, the second frame is sent when the main channel of the second wireless device is the same as the main channel of the first wireless device.

[0605] In one possible design of this embodiment, the second MAPC information includes one or more of the following: the main channel of the second wireless device; the NPCA main channel of the second wireless device; the MAPC transmission policy supported by the second wireless device; the disabled sub-channels of the second wireless device; whether the second wireless device agrees to join the MAPC group; wherein, the MAPC group is a set of APs used for cooperative data transmission, and the MAPC group includes the first wireless device and the second wireless device.

[0606] In one possible design of this embodiment, the second frame is a MAPC discovery information frame, which is sent by the second wireless device when it switches to the second wireless device's NPCA main channel and the second wireless device's NPCA main channel is the same as the first wireless device's main channel.

[0607] Optionally, the second frame includes at least one of a MAPC discovery information frame and a MAPC discovery notification frame.

[0608] In one possible design of this embodiment, the second frame is transmitted in a non-high-throughput repetitive manner on at least two channels, the at least two channels including at least one of the main channel of the first wireless device and the NPCA main channel of the first wireless device.

[0609] For specific implementation details, please refer to section 1.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0610] 7.3 Fields carried in the first or second frame;

[0611] In one possible design of this embodiment, the first frame or the second frame carries one or more of the following fields:

[0612] MAPC Group Field; Common Action Field; MAPC Transmission Policy Field; Main Channel Center Frequency Field; NPCA Main Channel Field; Disabled Sub-channel Bitmap Field; Channel Information Request Field; Accept or Reject Field;

[0613] Among them, the MAPC group field is used to indicate whether MAPC is supported; the common action field is used to indicate the frame type; the MAPC transmission policy field is used to indicate the supported MAPC transmission policy; the channel information request field is used to indicate the channel information requester or responder; and the accept or reject field is used to indicate whether to agree to join the MAPC group. The MAPC group is a set of APs used for cooperative data transmission. The MAPC group includes a first wireless device and a second wireless device.

[0614] For specific implementation details, please refer to section 1.3 of the embodiment shown in Figure 8, which will not be repeated here.

[0615] 7.4 Third frame;

[0616] In one possible design of this embodiment, the sending module 2610 is further configured to send a third frame, which is used to indicate MAPC group information related to the MAPC group.

[0617] The MAPC group is a set of APs used for cooperative data transmission, and the MAPC group includes a first wireless device and a second wireless device.

[0618] In one possible design of this embodiment, the MAPC group information includes one or more of the following: the main channel of the MAPC group; the NPCA main channel of each AP included in the MAPC group; the MAPC transmission policy supported by each AP included in the MAPC group; the disabled sub-channels of each AP included in the MAPC group; the AP ID of each AP included in the MAPC group; and the MAPC EDCA parameters; wherein the main channel of the MAPC group is the same as the main channel of the first wireless device.

[0619] In one possible design of this embodiment, the transmitting module 2610 is configured to transmit the third frame in a non-high-throughput repetitive manner within the operating bandwidth of the first wireless device.

[0620] In one possible design of this embodiment, the third frame carries one or more of the following fields: common action field; main channel center frequency field; NPCA main channel field; MAPC transmission policy field; disabled sub-channel bitmap field; AP ID field; MAPC EDCA field; wherein, the common action field is used to indicate the frame type; the AP ID field is used to indicate the AP ID of each AP in the MAPC group.

[0621] For specific implementation details, please refer to section 1.4 of the embodiment shown in Figure 8, which will not be repeated here.

[0622] 7.5 Exemplary embodiments of the MAPC discovery process;

[0623] To illustrate the MAPC discovery process, this application provides the following three embodiments in conjunction with the accompanying drawings.

[0624] 7.5.1 Basic MAPC discovery process;

[0625] Figure 14 illustrates a schematic diagram of the basic MAPC discovery process provided in an exemplary embodiment of this application.

[0626] AP1 is the initiator AP for the MAPC discovery process, while AP2 and AP3 are the responder APs for the MAPC discovery process. AP2's primary channel is the same as AP1's; AP3's primary channel is different from AP1's, but its NPCA primary channel is the same as AP1's; AP4's primary channel and NPCA primary channel are both different from AP1's primary channel.

[0627] For specific implementation details, please refer to section 1.5.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0628] 7.5.2 MAPC discovery process based on TWT;

[0629] In one possible design of this embodiment, the transmitting module 2610 is used to transmit the first frame outside the first service time; wherein the first service time is indicated by the TWT schedule, and the TWT schedule is obtained in advance by the first wireless device and the associated site.

[0630] For specific implementation details, please refer to section 1.5.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0631] 7.5.3 MAPC discovery process based on RTWT;

[0632] In one possible design of this embodiment, the first frame carries an RTWT schedule, which is used to indicate a second service time. The receiving module 2620 is used to receive the second frame within the second service time.

[0633] For specific implementation details, please refer to section 1.5.3 of the embodiment shown in Figure 8, which will not be repeated here.

[0634] 7.6 Fourth frame;

[0635] In one possible design of this embodiment, the sending module 2610 is further configured to send a fourth frame, which is used to indicate support for MAPC or to indicate the execution of MAPC negotiation.

[0636] In one possible design of this embodiment, the fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0637] In one possible design of this embodiment, the fourth frame includes at least one of an RTS frame and a MU-RTS frame.

[0638] For specific implementation details, please refer to section 1.6 of the embodiment shown in Figure 8, which will not be repeated here.

[0639] 7.7 MAPC parameter negotiation;

[0640] In one possible design of this embodiment, the sending module 2610 is further configured to send a first request frame, which is used to negotiate the MAPC parameters required for cooperative data transmission between MAPCs. The MAPC parameters are used to help execute the MAPC transmission strategy.

[0641] In one possible design of this embodiment, the receiving module 2620 is further configured to receive a first response frame, which is used to respond to the first request frame.

[0642] In one possible design of this embodiment, the sending module 2610 is further configured to send a second response frame, which is used to respond to the first response frame.

[0643] In one possible design of this embodiment, the first request frame carries a field for indicating the MAPC parameters suggested by the first wireless device.

[0644] Optionally, the first request frame also carries a first parameter command field, which is used to indicate that the type of MAPC parameter negotiation is a suggestion type.

[0645] In one possible design of this embodiment, the first response frame has a field for indicating the MAPC parameters suggested by the second wireless device.

[0646] Optionally, the first response frame also carries a second parameter command field, which is used to indicate that the type of MAPC parameter negotiation is an alternative type.

[0647] In one possible design of this embodiment, the second response frame carries a field for indicating whether to accept or reject the MAPC parameters suggested by the second wireless device.

[0648] Optionally, the second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type.

[0649] In one possible design of this embodiment, the MAPC parameters include one or more of the following parameters: the proposed set of sub-channel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the proposed set of sub-channel candidates for binding includes the primary channel of the first wireless device, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0650] In one possible design of this embodiment, the first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field;

[0651] Among them, the common action field is used to indicate the frame type; the parameter request field is used to indicate the initiator or responder of MAPC parameter negotiation; the parameter command field is used to indicate the type of MAPC parameter negotiation; the MAPC session start time field is used to indicate the start time of the configuration validity period, the configuration validity period is used to indicate the validity period of the MAPC parameters; and the MAPC session duration field is used to indicate the duration of the configuration validity period.

[0652] For specific implementation details, please refer to section 1.7 of the embodiment shown in Figure 8, which will not be repeated here.

[0653] 7.8 Exemplary embodiments of the MAPC negotiation process;

[0654] To illustrate the MAPC negotiation process, this application provides the following two embodiments in conjunction with the accompanying drawings.

[0655] 7.8.1 MAPC negotiation process under Co-TDMA;

[0656] In one possible design of this embodiment, the transmitting module 2610 is further configured to transmit an ICF, which is used to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; wherein, the MAPC group is a set of APs used for cooperative data transmission, and the MAPC group includes a first wireless device and a second wireless device.

[0657] In one possible design of this embodiment, the receiving module 2620 is also used to receive ICR frames, which are used to determine the APs participating in the MAPC transmission strategy.

[0658] In one possible design of this embodiment, the sending module 2610 is further configured to send a MU-RTS frame to the target AP;

[0659] The target AP is determined based on the ICR frame and is an AP participating in the MAPC transmission strategy. The MU-RTS frame is used to indicate that the target AP will transmit data during the TXS time period.

[0660] For specific implementation details, please refer to section 1.8.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0661] 7.8.2 MAPC Negotiation Process under Seamless Roaming;

[0662] In one possible design of this embodiment, the receiving module 2620 is further configured to receive a seamless roaming request frame, which is used to indicate that the first station requests to roam to the second wireless device, and the first station is the associated station of the first wireless device.

[0663] In one possible design of this embodiment, the sending module 2610 is further configured to send a seamless roaming response frame, which is used to indicate the completion of seamless roaming.

[0664] For specific implementation details, please refer to section 1.8.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0665] This embodiment uses one transmitting module 2610 and one receiving module 2620 as an example for illustration, and the number of transmitting modules 2610 and receiving modules 2620 is not limited.

[0666] For a description of the function of the sending module 2610, please refer to step 810 in the embodiment shown in Figure 8. For a description of the function of the receiving module 2620, please refer to step 810 in the embodiment shown in Figure 8.

[0667] Figure 27 shows a block diagram of a second wireless device provided in an exemplary embodiment of this application. This device can be implemented as a second access point (AP) or as part of a second AP via software, hardware, or a combination of both. The device includes:

[0668] The receiving module 2710 is used to receive a first frame, which is used to indicate first MAPC information related to the first wireless device;

[0669] The first MAPC information is used to indicate the information required for MAPC to transmit data.

[0670] In one possible design of this embodiment, the receiving module 2710 is used to receive a first frame; wherein the first frame is transmitted by the first wireless device in a non-high throughput repetitive manner within the operating bandwidth of the first wireless device; or, the first frame is transmitted by the first wireless device in a non-high throughput repetitive manner on at least two sub-channels of the operating bandwidth of the first wireless device.

[0671] For specific implementation details, please refer to the embodiment in Figure 8, which will not be repeated here.

[0672] 8.1 First MAPC information;

[0673] In one possible design of this embodiment, the first MAPC information includes one or more of the following: the main channel of the first wireless device; the NPCA main channel of the first wireless device; the MAPC transmission strategy supported by the first wireless device; and the disabled sub-channels of the first wireless device.

[0674] By way of example and not limitation, the MAPC transmission strategy includes at least one of the following: Co-TDMA; Co-RTWT; Co-BF; Co-SR; seamless roaming. In the embodiments of this application, the MAPC transmission strategy may also be referred to simply as the MAPC transmission strategy.

[0675] In one possible design of this embodiment, the first frame is also used to request the second wireless device to provide feedback on the second MAPC information related to the second wireless device.

[0676] For specific implementation details, please refer to section 1.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0677] 8.2 Second MAPC Information;

[0678] In one possible design of this embodiment, the transmitting module 2720 is used to transmit a second frame, which is used to indicate second MAPC information related to the second wireless device; wherein, the second frame is transmitted when the main channel of the second wireless device is the same as the main channel of the first wireless device; or, the second frame is transmitted when the main channel of the second wireless device is the same as the main channel of the first wireless device; or, the second frame is transmitted when the main channel of the second wireless device is the same as the main channel of the first wireless device; or, the second frame is transmitted when the main channel of the second wireless device is the same as the main channel of the first wireless device.

[0679] In one possible design of this embodiment, the second MAPC information includes one or more of the following: the main channel of the second wireless device; the NPCA main channel of the second wireless device; the MAPC transmission policy supported by the second wireless device; the disabled sub-channels of the second wireless device; whether the second wireless device agrees to join the MAPC group; wherein, the MAPC group is a set of APs used for cooperative data transmission.

[0680] In one possible design of this embodiment, the NPCA main channel of the second wireless device is the same as the main channel of the first wireless device, and the second frame is a MAPC discovery information frame, which is sent by the second wireless device when switching to the NPCA main channel of the second wireless device.

[0681] Optionally, the second frame includes at least one of a MAPC discovery information frame and a MAPC discovery notification frame.

[0682] In one possible design of this embodiment, the transmitting module 2720 is configured to transmit the second frame in a non-high-throughput repetitive manner on at least two channels, the at least two channels including at least one of the main channel of the first wireless device and the NPCA main channel of the first wireless device.

[0683] For specific implementation details, please refer to section 1.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0684] 8.3 Fields carried in the first or second frame;

[0685] In one possible design of this embodiment, the first frame or the second frame carries one or more of the following fields:

[0686] MAPC Group Field; Common Action Field; MAPC Transmission Policy Field; Main Channel Center Frequency Field; NPCA Main Channel Field; Disabled Sub-channel Bitmap Field; Channel Information Request Field; Accept or Reject Field;

[0687] Among them, the MAPC group field is used to indicate whether MAPC is supported; the common action field is used to indicate the frame type; the MAPC transmission policy field is used to indicate the supported MAPC transmission policy; the channel information request field is used to indicate the channel information requester or responder; and the accept or reject field is used to indicate whether to agree to join the MAPC group, which is a set of APs used for cooperative data transmission.

[0688] For specific implementation details, please refer to section 1.3 of the embodiment shown in Figure 8, which will not be repeated here.

[0689] 8.4 Third frame;

[0690] In one possible design of this embodiment, the receiving module 2710 is further configured to receive a third frame, which is used to indicate MAPC group information related to the MAPC group; wherein, the MAPC group is a set of APs used for cooperative data transmission.

[0691] In one possible design of this embodiment, the MAPC group information includes one or more of the following: the main channel of the MAPC group; the NPCA main channel of each AP included in the MAPC group; the MAPC transmission policy supported by each AP included in the MAPC group; the disabled sub-channels of each AP included in the MAPC group; the AP ID of each AP included in the MAPC group; and the MAPC EDCA parameters; wherein the main channel of the MAPC group is the same as the main channel of the first wireless device.

[0692] In one possible design of this embodiment, the receiving module 2710 is used to receive a third frame, which is transmitted by the first wireless device in a non-high throughput repetitive manner within the operating bandwidth of the first wireless device.

[0693] In one possible design of this embodiment, the third frame carries one or more of the following fields: common action field; main channel center frequency field; NPCA main channel field; MAPC transmission policy field; disabled sub-channel bitmap field; AP ID field; MAPC EDCA field; wherein, the common action field is used to indicate the frame type; the AP ID field is used to indicate the AP ID of each AP in the MAPC group.

[0694] For specific implementation details, please refer to section 1.4 of the embodiment shown in Figure 8, which will not be repeated here.

[0695] 8.5 Exemplary embodiments of the MAPC discovery process;

[0696] To illustrate the MAPC discovery process, this application provides the following three embodiments in conjunction with the accompanying drawings.

[0697] 8.5.1 Basic MAPC discovery process;

[0698] Figure 14 illustrates a schematic diagram of the basic MAPC discovery process provided in an exemplary embodiment of this application.

[0699] AP1 is the initiator AP for the MAPC discovery process, while AP2 and AP3 are the responder APs for the MAPC discovery process. AP2's primary channel is the same as AP1's; AP3's primary channel is different from AP1's, but its NPCA primary channel is the same as AP1's; AP4's primary channel and NPCA primary channel are both different from AP1's primary channel.

[0700] For specific implementation details, please refer to section 1.5.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0701] 8.5.2 MAPC discovery process based on TWT;

[0702] In one possible design of this embodiment, the receiving module 2710 is used to receive the first frame outside the first service time; wherein the first service time is indicated by the TWT schedule, and the TWT schedule is obtained in advance by the first wireless device and the associated site.

[0703] For specific implementation details, please refer to section 1.5.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0704] 8.5.3 MAPC discovery process based on RTWT;

[0705] In one possible design of this embodiment, the first frame carries an RTWT schedule, which is used to indicate a second service time. The sending module 2720 is used to send the second frame within the second service time.

[0706] For specific implementation details, please refer to section 1.5.3 of the embodiment shown in Figure 8, which will not be repeated here.

[0707] 8.6 Fourth frame;

[0708] In one possible design of this embodiment, the receiving module 2710 is further configured to receive a fourth frame, which is used to indicate support for MAPC or to indicate the execution of MAPC negotiation.

[0709] In one possible design of this embodiment, the fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0710] In one possible design of this embodiment, the fourth frame includes at least one of an RTS frame and a MU-RTS frame.

[0711] For specific implementation details, please refer to section 1.6 of the embodiment shown in Figure 8, which will not be repeated here.

[0712] 8.7 MAPC parameter negotiation;

[0713] In one possible design of this embodiment, the receiving module 2710 is further configured to receive a first request frame, which is used to negotiate the MAPC parameters required for MAPC data transmission, and the MAPC parameters are used to help execute the MAPC transmission strategy.

[0714] In one possible design of this embodiment, the first request frame carries a field for indicating the MAPC parameters suggested by the first wireless device.

[0715] Optionally, the first request frame also carries a first parameter command field, which is used to indicate that the type of MAPC parameter negotiation is a suggestion type.

[0716] In one possible design of this embodiment, the sending module 2720 is further configured to send a first response frame, which is used to respond to the first request frame.

[0717] In one possible design of this embodiment, the first response frame carries a field for indicating the MAPC parameters suggested by the second wireless device.

[0718] Optionally, the first response frame also carries a second parameter command field, which is used to indicate that the type of MAPC parameter negotiation is an alternative type.

[0719] In one possible design of this embodiment, the receiving module 2710 is further configured to receive a second response frame, which is used to respond to the first response frame.

[0720] In one possible design of this embodiment, the second response frame carries a field for indicating whether to accept or reject the MAPC parameters suggested by the second wireless device.

[0721] Optionally, the second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type.

[0722] In one possible design of this embodiment, the MAPC parameters include one or more of the following parameters: the proposed set of sub-channel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the proposed set of sub-channel candidates for binding includes the primary channel of the first wireless device, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0723] In one possible design of this embodiment, the first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field;

[0724] Among them, the common action field is used to indicate the frame type; the parameter request field is used to indicate the initiator or responder of MAPC parameter negotiation; the parameter command field is used to indicate the type of MAPC parameter negotiation; the MAPC session start time field is used to indicate the start time of the configuration validity period, the configuration validity period is used to indicate the validity period of the MAPC parameters; and the MAPC session duration field is used to indicate the duration of the configuration validity period.

[0725] For specific implementation details, please refer to section 1.7 of the embodiment shown in Figure 8, which will not be repeated here.

[0726] 8.8 Exemplary embodiments of the MAPC negotiation process;

[0727] To illustrate the MAPC negotiation process, this application provides the following two embodiments in conjunction with the accompanying drawings.

[0728] 8.8.1 MAPC negotiation process under Co-TDMA;

[0729] In one possible design of this embodiment, the receiving module 2710 is further configured to receive an ICF, which is used to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; wherein, the MAPC group is a set of APs used for cooperative data transmission.

[0730] In one possible design of this embodiment, the sending module 2720 is also used to send an ICR frame, which is used to determine the APs participating in the MAPC transmission strategy.

[0731] In one possible design of this embodiment, the second wireless device is a target AP, which is an AP participating in the MAPC transmission strategy determined based on the ICR frame. The receiving module 2710 is also used to receive MU-RTS frames; wherein, the MU-RTS frame is used to indicate that the target AP transmits data during the TXS time period.

[0732] For specific implementation details, please refer to section 1.8.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0733] 8.8.2 MAPC Negotiation Process under Seamless Roaming;

[0734] Figure 20 shows a schematic diagram of the MAPC negotiation process provided in an exemplary embodiment of this application.

[0735] When STA1 (the first site) moves from its original BSS to the target BSS to achieve seamless roaming, the original associated AP (AP1, the first radio device) and the target AP (AP2, the second radio device) need to exchange frames, such as transmitting STA ID information. AP1 also needs to forward STA1's downlink data to AP2 and negotiate to extend the inter-MAPC link bandwidth. AP1 is the transmitting AP, and AP2 is the receiving AP; AP1 and AP2 share the same primary channel. Figure 20 only shows the air interface frame exchange process during seamless roaming.

[0736] For specific implementation details, please refer to section 1.8.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0737] This embodiment uses one receiving module 2710 and one transmitting module 2720 as an example for illustration, and the number of receiving modules 2710 and transmitting modules 2720 is not limited.

[0738] For a description of the function of the receiving module 2710, please refer to step 2110 in the embodiment shown in Figure 21. For a description of the function of the sending module 2720, please refer to step 2110 in the embodiment shown in Figure 21.

[0739] Figure 28 shows a block diagram of a first wireless device provided in an exemplary embodiment of this application. The device can be implemented as a first access point (AP) or as part of a first AP via software, hardware, or a combination of both. The device includes:

[0740] The sending module 2810 is used to send a first request frame, which is used to negotiate the MAPC parameters required for MAPC data transmission.

[0741] 9.1 MAPC parameter negotiation;

[0742] In one possible design of this embodiment, the receiving module 2820 is used to receive a first response frame, which is used to respond to a first request frame.

[0743] In one possible design of this embodiment, the sending module 2810 is used to send a second response frame, which is used to respond to the first response frame.

[0744] In one possible design of this embodiment, the first request frame carries a field for indicating the MAPC parameters suggested by the first wireless device.

[0745] Optionally, the first request frame also carries a first parameter command field, which indicates that the type of MAPC parameter negotiation is a suggestion type, and the suggestion type indicates that the MAPC parameters suggested by the first wireless device are used.

[0746] In one possible design of this embodiment, the first response frame carries a field for indicating the MAPC parameters suggested by the second wireless device.

[0747] Optionally, the first response frame also carries a second parameter command field, which indicates that the type of MAPC parameter negotiation is an alternative type. The alternative type indicates that the MAPC parameters suggested by the second wireless device are different from the MAPC parameters suggested by the first wireless device.

[0748] In one possible design of this embodiment, the second response frame carries a field for indicating whether to accept or reject the MAPC parameters suggested by the second wireless device.

[0749] Optionally, the second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type. The accept type is used to indicate that the MAPC parameters suggested by the second wireless device are accepted, and the reject type is used to indicate that the MAPC parameters suggested by the second wireless device are rejected.

[0750] In one possible design of this embodiment, the MAPC parameters include one or more of the following parameters: the proposed set of sub-channel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the proposed set of sub-channel candidates for binding includes the primary channel of the first wireless device, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0751] In one possible design of this embodiment, the first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field;

[0752] Among them, the common action field is used to indicate the frame type; the parameter request field is used to indicate the initiator or responder of MAPC parameter negotiation; the parameter command field is used to indicate the type of MAPC parameter negotiation; the MAPC session start time field is used to indicate the start time of the configuration validity period, the configuration validity period is used to indicate the validity period of the MAPC parameters; and the MAPC session duration field is used to indicate the duration of the configuration validity period.

[0753] For specific implementation details, please refer to section 1.7 of the embodiment shown in Figure 8, which will not be repeated here.

[0754] 9.2 Fourth frame;

[0755] In one possible design of this embodiment, the sending module 2810 is used to send a fourth frame, which is used to indicate support for MAPC or to indicate the execution of MAPC negotiation.

[0756] In one possible design of this embodiment, the fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0757] In one possible design of this embodiment, the fourth frame includes at least one of an RTS frame and a MU-RTS frame.

[0758] For specific implementation details, please refer to section 1.6 of the embodiment shown in Figure 8, which will not be repeated here.

[0759] 9.3 Exemplary embodiments of the MAPC negotiation process;

[0760] To illustrate the MAPC negotiation process, this application provides the following two embodiments in conjunction with the accompanying drawings.

[0761] 9.3.1 MAPC negotiation process under Co-TDMA;

[0762] In one possible design of this embodiment, the transmitting module 2810 is used to transmit an ICF (Information Function Request), which is used to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; wherein, the MAPC group is a set of APs used for cooperative data transmission, and the MAPC group includes a first wireless device. If a second wireless device agrees to join the MAPC group, the MAPC group includes both the first and second wireless devices.

[0763] In one possible design of this embodiment, the receiving module 2820 is used to receive ICR frames, which are used to determine the APs participating in the MAPC transmission strategy.

[0764] In one possible design of this embodiment, the sending module 2810 is used to send MU-RTS frames to the target AP;

[0765] The target AP is determined based on the ICR frame and is an AP participating in the MAPC transmission strategy. The MU-RTS frame is used to indicate that the target AP will transmit data during the TXS time period.

[0766] For specific implementation details, please refer to section 1.8.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0767] 9.3.2 MAPC Negotiation Process under Seamless Roaming;

[0768] In one possible design of this embodiment, the receiving module 2820 is used to receive a seamless roaming request frame, which is used to indicate that a first station requests to roam to a second wireless device, and the first station is an associated station of the first wireless device.

[0769] In one possible design of this embodiment, the sending module 2810 is used to send a seamless roaming response frame, which is used to indicate that seamless roaming has been completed.

[0770] For specific implementation details, please refer to section 1.8.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0771] For a description of the function of the sending module 2810, please refer to step 2210 in the embodiment shown in Figure 22. For a description of the function of the receiving module 2820, please refer to step 2210 in the embodiment shown in Figure 22.

[0772] Figure 29 shows a block diagram of a second wireless device provided in an exemplary embodiment of this application. The device can be implemented as a second access point (AP) or as part of a second AP via software, hardware, or a combination of both. The device includes:

[0773] The receiving module 2910 is used to receive a first request frame, which is used to negotiate the MAPC parameters required for MAPC data transmission.

[0774] 10.1 MAPC parameter negotiation;

[0775] In one possible design of this embodiment, the first request frame carries a field for indicating the MAPC parameters suggested by the first wireless device.

[0776] Optionally, the first request frame also carries a first parameter command field, which indicates that the type of MAPC parameter negotiation is a suggestion type.

[0777] In one possible design of this embodiment, the sending module 2920 is used to send a first response frame, which is used to respond to the first request frame.

[0778] In one possible design of this embodiment, the first response frame carries a field for indicating the MAPC parameters suggested by the second wireless device.

[0779] Optionally, the first response frame also carries a second parameter command field, which is used to indicate that the type of MAPC parameter negotiation is an alternative type.

[0780] In one possible design of this embodiment, the receiving module 2910 is used to receive a second response frame, which is used to respond to the first response frame.

[0781] In one possible design of this embodiment, the second response frame carries a field for indicating whether to accept or reject the MAPC parameters suggested by the second wireless device.

[0782] Optionally, the second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type.

[0783] In one possible design of this embodiment, the MAPC parameters include one or more of the following parameters: the proposed set of sub-channel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the proposed set of sub-channel candidates for binding includes the primary channel of the first wireless device, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0784] In one possible design of this embodiment, the first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field;

[0785] Among them, the common action field is used to indicate the frame type; the parameter request field is used to indicate the initiator or responder of MAPC parameter negotiation; the parameter command field is used to indicate the type of MAPC parameter negotiation; the MAPC session start time field is used to indicate the start time of the configuration validity period, the configuration validity period is used to indicate the validity period of the MAPC parameters; and the MAPC session duration field is used to indicate the duration of the configuration validity period.

[0786] For specific implementation details, please refer to section 1.7 of the embodiment shown in Figure 8, which will not be repeated here.

[0787] 10.2 Fourth frame;

[0788] In one possible design of this embodiment, the receiving module 2910 is used to receive a fourth frame, which is used to indicate support for MAPC or to indicate the execution of MAPC negotiation.

[0789] In one possible design of this embodiment, the fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0790] In one possible design of this embodiment, the fourth frame includes at least one of an RTS frame and a MU-RTS frame.

[0791] For specific implementation details, please refer to section 1.6 of the embodiment shown in Figure 8, which will not be repeated here.

[0792] 10.3 Exemplary embodiments of the MAPC negotiation process;

[0793] To illustrate the MAPC negotiation process, this application provides the following two embodiments in conjunction with the accompanying drawings.

[0794] 10.3.1 MAPC negotiation process under Co-TDMA;

[0795] In one possible design of this embodiment, the receiving module 2910 is used to receive an ICF, which is used to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; wherein, the MAPC group is a set of APs used for cooperative data transmission.

[0796] In one possible design of this embodiment, the sending module 2920 is used to send ICR frames, which are used to determine the APs participating in the MAPC transmission strategy.

[0797] In one possible design of this embodiment, the second wireless device is a target AP, which is an AP participating in the MAPC transmission strategy determined based on the ICR frame. The receiving module 2910 is used to receive MU-RTS frames; wherein, the MU-RTS frame is used to indicate that the target AP transmits data during the TXS time period.

[0798] For specific implementation details, please refer to section 1.8.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0799] 10.3.2 MAPC Negotiation Process under Seamless Roaming;

[0800] Figure 20 shows a schematic diagram of the MAPC negotiation process provided in an exemplary embodiment of this application.

[0801] When STA1 (the first site) moves from its original BSS to the target BSS to achieve seamless roaming, the original associated AP (AP1, the first radio device) and the target AP (AP2, the second radio device) need to exchange frames, such as transmitting STA ID information. AP1 also needs to forward STA1's downlink data to AP2 and negotiate to extend the inter-MAPC link bandwidth. AP1 is the transmitting AP, and AP2 is the receiving AP; AP1 and AP2 share the same primary channel. Figure 20 only shows the air interface frame exchange process during seamless roaming.

[0802] For specific implementation details, please refer to section 1.8.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0803] For a description of the function of the receiving module 2910, please refer to step 2310 in the embodiment shown in Figure 23. For a description of the function of the sending module 2920, please refer to step 2310 in the embodiment shown in Figure 23.

[0804] Figure 30 shows a block diagram of a first wireless device provided in an exemplary embodiment of this application. The device can be implemented as a first access point (AP) or as part of a first AP via software, hardware, or a combination of both. The device includes:

[0805] The transceiver module 3010 is used to receive and / or send at least one frame, which is related to the MAPC discovery process.

[0806] In one possible design of this embodiment, at least one frame includes at least one of a first frame, a second frame, and a third frame;

[0807] The first frame indicates first MAPC information associated with the first wireless device, which indicates the information required for MAPC data transmission; the second frame indicates second MAPC information associated with the second wireless device; and the third frame indicates MAPC group information associated with the MAPC group, which is a set of APs used for cooperative data transmission.

[0808] For specific implementation details, please refer to the embodiment shown in Figure 24, which will not be repeated here.

[0809] 11.1 First frame;

[0810] In one possible design of this embodiment, the transceiver module 3010 is configured to transmit the first frame in a non-high-throughput duplicate manner within the operating bandwidth of the first wireless device; or, transmit the first frame in a non-high-throughput duplicate manner on at least two sub-channels of the operating bandwidth of the first wireless device.

[0811] In one possible design of this embodiment, the first MAPC information includes one or more of the following: the main channel of the first wireless device; the NPCA main channel of the first wireless device; the MAPC transmission strategy supported by the first wireless device; and the disabled sub-channels of the first wireless device.

[0812] By way of example and not limitation, the MAPC transmission strategy includes at least one of the following: Co-TDMA; Co-RTWT; Co-BF; Co-SR; seamless roaming. In the embodiments of this application, the MAPC transmission strategy may also be referred to as MAPC transmission strategy, MAPC strategy, etc.

[0813] In one possible design of this embodiment, the first frame is also used to request the second wireless device to provide feedback on the second MAPC information related to the second wireless device.

[0814] For specific implementation details, please refer to section 1.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0815] 11.2 Second frame;

[0816] In one possible design of this embodiment, the second frame is used to indicate second MAPC information associated with the second wireless device;

[0817] The second frame is transmitted when the main channel of the second wireless device is the same as the main channel of the first wireless device; or, the second frame is transmitted when the NPCA main channel of the second wireless device is the same as the main channel of the first wireless device; or, the second frame is transmitted when the main channel of the second wireless device is the same as the NPCA main channel of the first wireless device; or, the second frame is transmitted when the NPCA main channel of the second wireless device is the same as the NPCA main channel of the first wireless device.

[0818] In one possible design of this embodiment, the second MAPC information includes one or more of the following: the main channel of the second wireless device; the NPCA main channel of the second wireless device; the MAPC transmission policy supported by the second wireless device; the disabled sub-channels of the second wireless device; whether the second wireless device agrees to join the MAPC group; wherein, the MAPC group is a set of APs used for cooperative data transmission.

[0819] In one possible design of this embodiment, the second frame is a MAPC discovery information frame, which is sent by the second wireless device when it switches to the second wireless device's NPCA main channel and the second wireless device's NPCA main channel is the same as the first wireless device's main channel.

[0820] Optionally, the second frame includes at least one of a MAPC discovery information frame and a MAPC discovery notification frame.

[0821] In one possible design of this embodiment, the second frame is transmitted in a non-high-throughput repetitive manner on at least two channels, the at least two channels including at least one of the main channel of the first wireless device and the NPCA main channel of the first wireless device.

[0822] For specific implementation details, please refer to section 1.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0823] 11.3 Fields carried in the first or second frame;

[0824] In one possible design of this embodiment, the first frame or the second frame carries one or more of the following fields:

[0825] MAPC Group Field; Common Action Field; MAPC Transmission Policy Field; Main Channel Center Frequency Field; NPCA Main Channel Field; Disabled Sub-channel Bitmap Field; Channel Information Request Field; Accept or Reject Field;

[0826] The MAPC group field indicates whether MAPC is supported; the common action field indicates the frame type; the MAPC transmission policy field indicates the supported MAPC transmission policy; the channel information request field indicates the channel information requester or responder; and the accept or reject field indicates whether to agree to join the MAPC group. The MAPC group is a set of APs used for cooperative data transmission. The MAPC group includes a first wireless device. If a second wireless device agrees to join the MAPC group, the MAPC group includes both the first and second wireless devices.

[0827] For specific implementation details, please refer to section 1.3 of the embodiment shown in Figure 8, which will not be repeated here.

[0828] 11.4 Third frame;

[0829] In one possible design of this embodiment, the third frame is used to indicate MAPC group information associated with the MAPC group;

[0830] In this context, a MAPC group is a set of Access Points (APs) used for cooperative data transmission, and the MAPC group includes a first wireless device. If a second wireless device agrees to join the MAPC group, the MAPC group includes both the first and second wireless devices.

[0831] In one possible design of this embodiment, the MAPC group information includes one or more of the following: the main channel of the MAPC group; the NPCA main channel of each AP included in the MAPC group; the MAPC transmission policy supported by each AP included in the MAPC group; the disabled sub-channels of each AP included in the MAPC group; the AP ID of each AP included in the MAPC group; and the MAPC EDCA parameters; wherein the main channel of the MAPC group is the same as the main channel of the first wireless device.

[0832] In one possible design of this embodiment, the transceiver module 3010 is used to transmit the third frame in a non-high throughput repetitive manner within the operating bandwidth of the first wireless device.

[0833] In one possible design of this embodiment, the third frame carries one or more of the following fields: common action field; main channel center frequency field; NPCA main channel field; MAPC transmission policy field; disabled sub-channel bitmap field; AP ID field; MAPC EDCA field; wherein, the common action field is used to indicate the frame type; the AP ID field is used to indicate the AP ID of each AP in the MAPC group.

[0834] For specific implementation details, please refer to section 1.4 of the embodiment shown in Figure 8, which will not be repeated here.

[0835] 11.5 Exemplary embodiments of the MAPC discovery process;

[0836] To illustrate the MAPC discovery process, this application provides the following three embodiments in conjunction with the accompanying drawings.

[0837] 11.5.1 Basic MAPC discovery process;

[0838] Figure 14 illustrates a schematic diagram of the MAPC discovery process provided in an exemplary embodiment of this application.

[0839] AP1 is the initiator AP for the MAPC discovery process, while AP2 and AP3 are the responder APs for the MAPC discovery process. AP2's primary channel is the same as AP1's; AP3's primary channel is different from AP1's, but its NPCA primary channel is the same as AP1's; AP4's primary channel and NPCA primary channel are both different from AP1's primary channel.

[0840] For specific implementation details, please refer to section 1.5.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0841] 11.5.2 MAPC discovery process based on TWT;

[0842] In one possible design of this embodiment, the transceiver module 3010 is used to send the first frame outside the first service time; wherein the first service time is indicated by the TWT schedule, and the TWT schedule is obtained in advance by the first wireless device and the associated site.

[0843] For specific implementation details, please refer to section 1.5.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0844] 11.5.3 MAPC discovery process based on RTWT;

[0845] In one possible design of this embodiment, the first frame carries an RTWT schedule, which is used to indicate a second service time. The transceiver module 3010 is used to receive the second frame within the second service time.

[0846] For specific implementation details, please refer to section 1.5.3 of the embodiment shown in Figure 8, which will not be repeated here.

[0847] For a description of the functions of the transceiver module 3010, please refer to step 2410 in the embodiment shown in Figure 24.

[0848] Figure 31 shows a block diagram of a first wireless device provided in an exemplary embodiment of this application. The device can be implemented as a first access point (AP) or as part of a first AP by software or hardware or a combination of both. The device includes:

[0849] The transceiver module 3110 is used to receive and / or send at least one frame, which is related to the MAPC negotiation process.

[0850] In one possible design of this embodiment, at least one frame includes at least one of the following: a fourth frame, a first request frame, a first response frame, a second response frame, an ICF, an ICR frame, a MU-RTS frame, a seamless roaming request frame, and a seamless roaming response frame;

[0851] The fourth frame indicates support for MAPC or indicates the execution of MAPC negotiation; the first request frame negotiates the MAPC parameters required for MAPC data transmission, which help execute the MAPC transmission strategy; the first response frame responds to the first request frame; the second response frame responds to the first response frame; the ICF polls the APs in the MAPC group to determine which APs participate in the MAPC transmission strategy, where the MAPC group is a set of APs used for cooperative data transmission; the ICR frame determines which APs participate in the MAPC transmission strategy; the MU-RTS frame instructs the target AP to transmit data during the TXS time period, where the target AP is an AP participating in the MAPC transmission strategy determined based on the ICR frame; the seamless roaming request frame instructs the first site to request roaming to the second radio device, where the first site is the associated site of the first radio device; and the seamless roaming response frame indicates the completion of seamless roaming.

[0852] For specific implementation details, please refer to the embodiment shown in Figure 25, which will not be repeated here.

[0853] 12.1 MAPC parameter negotiation;

[0854] In one possible design of this embodiment, the first request frame carries a field for indicating the MAPC parameters suggested by the first wireless device.

[0855] Optionally, the first request frame also carries a first parameter command field, which indicates that the type of MAPC parameter negotiation is a suggestion type, and the suggestion type indicates that the MAPC parameters suggested by the first wireless device are used.

[0856] In one possible design of this embodiment, the first response frame carries a field for indicating the MAPC parameters suggested by the second wireless device.

[0857] Optionally, the first response frame also carries a second parameter command field, which indicates that the type of MAPC parameter negotiation is an alternative type. The alternative type indicates that the MAPC parameters suggested by the second wireless device are different from the MAPC parameters suggested by the first wireless device.

[0858] In one possible design of this embodiment, the second response frame carries a field for indicating whether to accept or reject the MAPC parameters suggested by the second wireless device.

[0859] Optionally, the second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type. The accept type is used to indicate that the MAPC parameters suggested by the second wireless device are accepted, and the reject type is used to indicate that the MAPC parameters suggested by the second wireless device are rejected.

[0860] In one possible design of this embodiment, the MAPC parameters include one or more of the following parameters: the proposed set of sub-channel candidates for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; MCS; NSS; configuration validity period; wherein the proposed set of sub-channel candidates for binding includes the primary channel of the first wireless device, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

[0861] In one possible design of this embodiment, the first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field;

[0862] Among them, the common action field is used to indicate the frame type; the parameter request field is used to indicate the initiator or responder of MAPC parameter negotiation; the parameter command field is used to indicate the type of MAPC parameter negotiation; the MAPC session start time field is used to indicate the start time of the configuration validity period, the configuration validity period is used to indicate the validity period of the MAPC parameters; and the MAPC session duration field is used to indicate the duration of the configuration validity period.

[0863] For specific implementation details, please refer to section 1.7 of the embodiment shown in Figure 8, which will not be repeated here.

[0864] 12.2 Fourth frame;

[0865] In one possible design of this embodiment, the fourth frame is used to indicate support for MAPC or to indicate the execution of MAPC negotiation.

[0866] In one possible design of this embodiment, the fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the performance of MAPC negotiation.

[0867] In one possible design of this embodiment, the fourth frame includes at least one of an RTS frame and a MU-RTS frame.

[0868] For specific implementation details, please refer to section 1.6 of the embodiment shown in Figure 8, which will not be repeated here.

[0869] 12.3 Exemplary embodiments of the MAPC negotiation process;

[0870] To illustrate the MAPC negotiation process, this application provides the following two embodiments in conjunction with the accompanying drawings.

[0871] 12.3.1 MAPC negotiation process under Co-TDMA;

[0872] In one possible design of this embodiment, the ICF is used to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; wherein, the MAPC group is a set of APs used for cooperative data transmission, and the MAPC group includes a first wireless device. If a second wireless device agrees to join the MAPC group, the MAPC group includes both the first and second wireless devices.

[0873] In one possible design of this embodiment, the ICR frame is used to determine the APs participating in the MAPC transmission strategy.

[0874] In one possible design of this embodiment, the target AP is an AP participating in the MAPC transmission strategy determined based on the ICR frame, and the MU-RTS frame is used to indicate that the target AP transmits data during the TXS time period.

[0875] For specific implementation details, please refer to section 1.8.1 of the embodiment shown in Figure 8, which will not be repeated here.

[0876] 12.3.2 MAPC Negotiation Process under Seamless Roaming;

[0877] In one possible design of this embodiment, the seamless roaming request frame is used to instruct a first site to request roaming to a second wireless device, where the first site is an associated site of the first wireless device.

[0878] In one possible design of this embodiment, the seamless roaming response frame is used to indicate that seamless roaming is complete.

[0879] For specific implementation details, please refer to section 1.8.2 of the embodiment shown in Figure 8, which will not be repeated here.

[0880] For a description of the functions of the transceiver module 3110, please refer to step 2510 in the embodiment shown in Figure 25.

[0881] Figure 32 shows a schematic diagram of the structure of a first AP or a second AP provided in an exemplary embodiment of this application. The first AP or second AP 3200 may include a processor 3201, a transceiver 3202, and a memory 3203. The processor 3201 can be used to control transmission and / or reception. The transceiver 3202 can be used to implement transmission and / or reception functions, such as implementing the functions of at least one of the following modules: transmission module 2610, reception module 2620, reception module 2710, transmission module 2720, transmission module 2810, reception module 2820, reception module 2910, transmission module 2920, transceiver module 3010, and transceiver module 3110.

[0882] The processor 3201 includes one or more processing cores, and the processor 3201 executes various functional applications and information processing by running software programs and modules.

[0883] Transceiver 3202 may include a receiver and a transmitter. For example, transceiver 3202 may include a wired communication component, which may include a wired communication chip and a wired interface (such as a fiber optic interface). Optionally, transceiver 3202 may also include a wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0884] Transceiver 3202 is used to send a first frame, which is used to indicate first MAPC information related to the first AP; wherein, the first MAPC information is used to indicate information required for MAPC to transmit data.

[0885] Alternatively, transceiver 3202 is used to receive a first frame, the first frame being used to indicate first MAPC information associated with the first AP; wherein the first MAPC information is used to indicate information required for MAPC data transmission.

[0886] Alternatively, transceiver 3202 is used to send a first request frame, which is used to negotiate the MAPC parameters required for MAPC data transmission.

[0887] Alternatively, transceiver 3202 is used to receive a first request frame, which is used to negotiate the MAPC parameters required for MAPC data transmission.

[0888] Alternatively, transceiver 3202 is used to receive and / or transmit at least one frame, which is related to the MAPC discovery process.

[0889] Alternatively, transceiver 3202 is used to receive and / or transmit at least one frame, the at least one frame being associated with the MAPC negotiation process.

[0890] The memory 3203 can be connected to the processor 3201 and the transceiver 3202.

[0891] The memory 3203 can be used to store a computer program executed by the processor, and the processor 3201 is used to execute the computer program to implement the various steps in the above method embodiments.

[0892] Furthermore, memory 3203 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static on-demand memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0893] For details not described in this embodiment, please refer to the method-side embodiment above, which will not be repeated here.

[0894] This application also provides a computer-readable storage medium storing a computer program for execution by a processor to implement the aforementioned communication method and / or parameter negotiation method between APs. In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0895] This application also provides a chip, which includes programmable logic circuits and / or program instructions. When the chip runs on a first AP, it is used to implement the above-mentioned communication method and / or parameter negotiation method between APs on the first AP side.

[0896] This application also provides a chip, which includes programmable logic circuits and / or program instructions. When the chip runs on a second AP, it is used to implement the above-mentioned communication method and / or parameter negotiation method between APs on the second AP side.

[0897] This application embodiment also provides a first chip, the first chip including programmable logic circuits and / or program instructions, which, when the first chip is running on a first AP, are used to "send a first frame, the first frame being used to indicate first MAPC information related to the first AP; wherein the first MAPC information is used to indicate information required for MAPC data transmission", and / or "send a first request frame, the first request frame being used to negotiate MAPC parameters required for MAPC data transmission", and / or "receive and / or send at least one frame, the at least one frame being related to the MAPC discovery process", and / or "receive and / or send at least one frame, the at least one frame being related to the MAPC negotiation process".

[0898] This application embodiment also provides a second chip, which includes programmable logic circuits and / or program instructions. When the second chip is running on the second AP, it is used to "receive a first frame, the first frame being used to indicate first MAPC information related to the first AP; wherein the first MAPC information is used to indicate information required for MAPC data transmission", and / or "receive a first request frame, the first request frame being used to negotiate MAPC parameters required for MAPC data transmission".

[0899] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. The processor reads and executes the computer program from the computer-readable storage medium to implement the above-mentioned communication method and / or parameter negotiation method between APs.

[0900] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0901] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0902] In some embodiments of this application, "predefined" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device, and this application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0903] In some embodiments of this application, "protocol" may refer to standard protocols in the field of communications, such as LTE protocol, NR protocol and related protocols applied to future communication systems, and this application does not limit it.

[0904] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0905] In this article, "greater than or equal to" can mean greater than or equal to, and "less than or equal to" can mean less than or equal to.

[0906] Furthermore, the step numbers described herein are merely illustrative of one possible execution order between steps. In some other embodiments, the steps may not be executed in the order of their numbers, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.

[0907] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0908] The above are merely exemplary embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application shall be included within the protection scope of this application.

Claims

1. A communication method between access points (APs), characterized in that, The method is performed by a first AP, and the method includes: Send a first frame, which is used to indicate first multi-access point cooperation (MAPC) information associated with the first AP; The first MAPC information is used to indicate the information required for MAPC to transmit data.

2. The method according to claim 1, characterized in that, The first MAPC information includes one or more of the following: The primary channel of the first AP; the non-primary channel of the first AP accessing the NPCA primary channel; the MAPC transmission strategy supported by the first AP; and the disabled sub-channels of the first AP.

3. The method according to claim 1 or 2, characterized in that, The first frame is also used to request the second AP to provide feedback on the second MAPC information related to the second AP.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Receive a second frame, which is used to indicate second MAPC information related to the second AP; Wherein, the second frame is transmitted by the second AP when it has the same main channel as the first AP. The situation of having the same main channel includes at least one of the following: the main channel of the second AP is the same as the main channel of the first AP; the NPCA main channel of the second AP is the same as the main channel of the first AP; the main channel of the second AP is the same as the NPCA main channel of the first AP; the NPCA main channel of the second AP is the same as the NPCA main channel of the first AP.

5. The method according to claim 4, characterized in that, The second MAPC information includes one or more of the following: The main channel of the second AP; the NPCA main channel of the second AP; the MAPC transmission policy supported by the second AP; the disabled sub-channels of the second AP; whether the second AP agrees to join the MAPC group; wherein, the MAPC group is a set of APs used for cooperative data transmission.

6. The method according to claim 4 or 5, characterized in that, The second frame includes at least one of a MAPC discovery information frame and a MAPC discovery notification frame.

7. The method according to claim 6, characterized in that, The second frame is the MAPC discovery information frame, which is sent by the second AP when it switches to the second AP's NPCA main channel and the second AP's NPCA main channel is the same as the first AP's main channel.

8. The method according to any one of claims 4 to 7, characterized in that, The first frame or the second frame carries one or more of the following fields: MAPC group field; common action field; MAPC transmission policy field; main channel center frequency field; NPCA main channel field; disabled sub-channel bitmap field; channel information request field; accept or reject field; The MAPC group field indicates whether MAPC is supported; the common action field indicates the frame type; the MAPC transmission policy field indicates the supported MAPC transmission policy; the channel information request field indicates the channel information requester or responder; and the accept or reject field indicates whether to agree to join the MAPC group, which is a set of APs used for cooperative data transmission.

9. The method according to any one of claims 4 to 8, characterized in that, The second frame is transmitted in a non-high-throughput repetitive manner on at least two channels, the at least two channels including at least one of the first AP's main channel and the first AP's NPCA main channel.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: Send a third frame, which is used to indicate MAPC group information related to the MAPC group; The MAPC group is a set of APs used for cooperative data transmission.

11. The method according to claim 10, characterized in that, The MAPC group information includes one or more of the following: The main channel of the MAPC group; the NPCA main channel of each AP included in the MAPC group; the MAPC transmission policy supported by each AP included in the MAPC group; the disabled sub-channels of each AP included in the MAPC group; the AP identifier ID of each AP included in the MAPC group; the MAPC EDCA parameters for Multi-Access Point Cooperation Enhanced Distributed Coordinated Access; wherein, the main channel of the MAPC group is the same as the main channel of the first AP.

12. The method according to claim 10 or 11, characterized in that, The third frame carries one or more of the following fields: The common action field; the main channel center frequency field; the NPCA main channel field; the MAPC transmission policy field; the disabled sub-channel bitmap field; the AP ID field; and the MAPC EDCA field; wherein the common action field is used to indicate the frame type; and the AP ID field is used to indicate the AP ID of each AP in the MAPC group.

13. The method according to any one of claims 10 to 12, characterized in that, The sending of the third frame includes: The third frame is transmitted in a non-high-throughput repetitive manner within the operating bandwidth of the first AP.

14. The method according to any one of claims 1 to 13, characterized in that, Sending the first frame includes: The first frame is sent outside of the first service time; The first service time is indicated by the Target Wake-up Time (TWT) schedule, which is obtained in advance by the first AP and the associated site.

15. The method according to any one of claims 4 to 9, characterized in that, The first frame carries a Restricted Target Wake-Up Time (RTWT) schedule, the RTWT schedule being used to indicate a second service time. Receiving the second frame includes: The second frame is received within the second service time.

16. The method according to any one of claims 1 to 13, characterized in that, Sending the first frame includes: The first frame is transmitted in a non-high throughput repetitive manner within the operating bandwidth of the first AP; or, the first frame is transmitted in the non-high throughput repetitive manner on at least two sub-channels of the operating bandwidth of the first AP.

17. The method according to any one of claims 1 to 16, characterized in that, The method further includes: A fourth frame is sent, which indicates support for MAPC or indicates that MAPC negotiation is to be performed.

18. The method according to claim 17, characterized in that, The fourth frame includes at least one of a request to send an RTS frame and a multi-user request to send a MU-RTS frame.

19. The method according to claim 17 or 18, characterized in that, The fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the execution of MAPC negotiation.

20. The method according to any one of claims 1 to 19, characterized in that, The method further includes: Send a first request frame, which is used to negotiate the MAPC parameters required for MAPC data transmission. The MAPC parameters are used to help execute the MAPC transmission strategy.

21. The method according to claim 2, 5, 8, 11, or 20, characterized in that, The MAPC transmission strategy includes at least one of the following: Cooperative Time Division Multiple Access (Co-TDMA); Cooperative Limited Target Wake-up Time (Co-RTWT); Cooperative Beamforming (Co-BF); Cooperative Spatial Reuse (Co-SR); Seamless Roaming.

22. The method according to claim 20 or 21, characterized in that, The first request frame carries a field indicating the MAPC parameters suggested by the first AP.

23. The method according to claim 22, characterized in that, The first request frame also carries a first parameter command field, which is used to indicate that the type of MAPC parameter negotiation is a suggestion type.

24. The method according to any one of claims 20 to 23, characterized in that, The method further includes: Receive a first response frame, which is used to respond to the first request frame.

25. The method according to claim 24, characterized in that, The first response frame carries a field indicating the MAPC parameters suggested by the second AP.

26. The method according to claim 25, characterized in that, The first response frame also carries a second parameter command field, which is used to indicate that the type of MAPC parameter negotiation is an alternative type.

27. The method according to any one of claims 24 to 26, characterized in that, The method further includes: Send a second response frame, which is used to respond to the first response frame.

28. The method according to claim 27, characterized in that, The second response frame carries a field indicating whether the MAPC parameters suggested by the second AP are accepted or rejected.

29. The method according to claim 28, characterized in that, The second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type.

30. The method according to any one of claims 19 to 29, characterized in that, The MAPC parameters include one or more of the following: the proposed set of candidate sub-channels for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; modulation and coding scheme (MCS); number of spatial streams (NSS); and configuration validity period. The proposed set of candidate sub-channels for binding includes the primary channel of the first AP, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

31. The method according to any one of claims 20 to 29, characterized in that, The first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; Maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field; The common action field indicates the frame type; the parameter request field indicates the initiator or responder of the MAPC parameter negotiation; the parameter command field indicates the type of MAPC parameter negotiation; the MAPC session start time field indicates the start time of the configuration validity period, and the configuration validity period indicates the validity period of the MAPC parameters; the MAPC session duration field indicates the duration of the configuration validity period.

32. The method according to any one of claims 20 to 31, characterized in that, The method further includes: Send an initial control frame (ICF), which is used to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; The MAPC group is a set of APs used for cooperative data transmission.

33. The method according to claim 32, characterized in that, The method further includes: Receive an Initial Control Response (ICR) frame, which is used to determine the APs participating in the MAPC transmission strategy.

34. The method according to claim 33, characterized in that, The method further includes: Send a MU-RTS frame to the target AP; The target AP is an AP that participates in the MAPC transmission strategy, determined based on the ICR frame, and the MU-RTS frame is used to instruct the target AP to transmit data during the Transmission Opportunity Sharing (TXS) time period.

35. The method according to any one of claims 20 to 31, characterized in that, The method further includes: A seamless roaming request frame is received, which is used to instruct a first site to roam to a second AP, wherein the first site is an associated site of the first AP.

36. The method according to claim 35, characterized in that, The method further includes: Send a seamless roaming response frame, which indicates that seamless roaming has been completed.

37. A parameter negotiation method, characterized in that, The method is performed by a first access point (AP), and the method includes: Send a first request frame, which is used to negotiate the MAPC parameters required for multi-access point cooperative MAPC data transmission.

38. The method according to claim 37, characterized in that, The first request frame carries a field indicating the MAPC parameters suggested by the first AP.

39. The method according to claim 38, characterized in that, The first request frame also carries a first parameter command field, which is used to indicate that the type of MAPC parameter negotiation is a suggestion type.

40. The method according to any one of claims 37 to 39, characterized in that, The method further includes: Receive a first response frame, which is used to respond to the first request frame.

41. The method according to claim 40, characterized in that, The first response frame carries a field indicating the MAPC parameters suggested by the second AP.

42. The method according to claim 41, characterized in that, The first response frame also carries a second parameter command field, which is used to indicate that the type of MAPC parameter negotiation is an alternative type.

43. The method according to any one of claims 40 to 42, characterized in that, The method further includes: Send a second response frame, which is used to respond to the first response frame.

44. The method according to claim 43, characterized in that, The second response frame carries a field indicating whether the MAPC parameters suggested by the second AP are accepted or rejected.

45. The method according to claim 44, characterized in that, The second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type.

46. ​​The method according to any one of claims 37 to 45, characterized in that, The MAPC parameters include one or more of the following: the proposed set of candidate sub-channels for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; modulation and coding scheme (MCS); number of spatial streams (NSS); and configuration validity period. The proposed set of candidate sub-channels for binding includes the primary channel of the first AP, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

47. The method according to any one of claims 37 to 45, characterized in that, The first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; Maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field; The common action field indicates the frame type; the parameter request field indicates the initiator or responder of the MAPC parameter negotiation; the parameter command field indicates the type of MAPC parameter negotiation; the MAPC session start time field indicates the start time of the configuration validity period, and the configuration validity period indicates the validity period of the MAPC parameters; the MAPC session duration field indicates the duration of the configuration validity period.

48. The method according to any one of claims 37 to 47, characterized in that, The method further includes: A fourth frame is sent, which indicates support for MAPC or indicates that MAPC negotiation is to be performed.

49. The method according to claim 48, characterized in that, The fourth frame includes at least one of a request to send an RTS frame and a multi-user request to send a MU-RTS frame.

50. The method according to claim 48 or 49, characterized in that, The fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the execution of MAPC negotiation.

51. The method according to any one of claims 37 to 50, characterized in that, The MAPC parameters are used to help execute the MAPC transmission strategy, and the method further includes: Send an initial control frame (ICF), which is used to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; The MAPC group is a set of APs used for cooperative data transmission.

52. The method according to claim 51, characterized in that, The method further includes: Receive an Initial Control Response (ICR) frame, which is used to determine the APs participating in the MAPC transmission strategy.

53. The method according to claim 52, characterized in that, The method further includes: Send a MU-RTS frame to the target AP; The target AP is an AP that participates in the MAPC transmission strategy, determined based on the ICR frame, and the MU-RTS frame is used to instruct the target AP to transmit data during the Transmission Opportunity Sharing (TXS) time period.

54. The method according to any one of claims 37 to 50, characterized in that, The method further includes: A seamless roaming request frame is received, which is used to instruct a first site to roam to a second AP, wherein the first site is an associated site of the first AP.

55. The method according to claim 54, characterized in that, The method further includes: Send a seamless roaming response frame, which indicates that seamless roaming has been completed.

56. The method according to any one of claims 37 to 55, characterized in that, The MAPC parameters are used to help execute the MAPC transmission strategy, which includes at least one of the following: Cooperative Time Division Multiple Access (Co-TDMA); Cooperative Limited Target Wake-up Time (Co-RTWT); Cooperative Beamforming (Co-BF); Cooperative Spatial Reuse (Co-SR); Seamless Roaming.

57. A communication method between access points (APs), characterized in that, The method is performed by a first AP, and the method includes: Receive and / or transmit at least one frame, said at least one frame being associated with the Multi-Access Point Cooperative (MAPC) discovery process.

58. The method according to claim 57, characterized in that, The at least one frame includes at least one of a first frame, a second frame, and a third frame; The first frame is used to indicate first MAPC information related to the first AP, and the first MAPC information is used to indicate information required for MAPC data transmission; the second frame is used to indicate second MAPC information related to the second AP; the third frame is used to indicate MAPC group information related to the MAPC group, and the MAPC group is a set of APs used for cooperative data transmission.

59. A communication method between access points (APs), characterized in that, The method is performed by a first AP, and the method includes: Receive and / or transmit at least one frame, said at least one frame being associated with the Multi-Access Point Cooperative (MAPC) negotiation process.

60. The method according to claim 59, characterized in that, The at least one frame includes at least one of the following: a fourth frame, a first request frame, a first response frame, a second response frame, an initial control frame (ICF), an initial control response (ICR) frame, a multi-user request to send (MU-RTS) frame, a seamless roaming request frame, and a seamless roaming response frame; The fourth frame is used to indicate support for MAPC or to indicate the execution of MAPC negotiation; the first request frame is used to negotiate the MAPC parameters required for MAPC data transmission, and the MAPC parameters are used to help execute the MAPC transmission strategy; the first response frame is used to respond to the first request frame; the second response frame is used to respond to the first response frame; the ICF is used to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy, and the MAPC group is a set of APs used for cooperative data transmission; the ICR frame is used to determine the APs participating in the MAPC transmission strategy; the MU-RTS frame is used to instruct the target AP to transmit data during the Transmission Opportunity Sharing (TXS) time period, and the target AP is an AP participating in the MAPC transmission strategy determined based on the ICR frame; the seamless roaming request frame is used to instruct the first site to request roaming to the second AP, and the first site is an associated site of the first AP; the seamless roaming response frame is used to indicate the completion of seamless roaming.

61. A communication method between access points (APs), characterized in that, The method is performed by the second AP, and the method includes: Receive a first frame, which is used to indicate first multi-access point cooperation (MAPC) information associated with the first AP; The first MAPC information is used to indicate the information required for MAPC to transmit data.

62. The method according to claim 61, characterized in that, The first MAPC information includes one or more of the following: The primary channel of the first AP; the non-primary channel of the first AP accessing the NPCA primary channel; the MAPC transmission strategy supported by the first AP; and the disabled sub-channels of the first AP.

63. The method according to claim 61 or 62, characterized in that, The first frame is also used to request the second AP to provide feedback on the second MAPC information related to the second AP.

64. The method according to any one of claims 61 to 63, characterized in that, The method further includes: Send a second frame, which is used to indicate second MAPC information related to the second AP; Wherein, the second frame is sent when the main channel of the second AP is the same as the main channel of the first AP; or, the second frame is sent when the NPCA main channel of the second AP is the same as the main channel of the first AP; or, the second frame is sent when the main channel of the second AP is the same as the NPCA main channel of the first AP; or, the second frame is sent when the NPCA main channel of the second AP is the same as the NPCA main channel of the first AP.

65. The method according to claim 64, characterized in that, The second MAPC information includes one or more of the following: The main channel of the second AP; the NPCA main channel of the second AP; the MAPC transmission policies supported by the second AP; the disabled sub-channels of the second AP; whether the second AP agrees to join the MAPC group; The MAPC group is a set of APs used for cooperative data transmission.

66. The method according to claim 64 or 65, characterized in that, The second frame includes at least one of a MAPC discovery information frame and a MAPC discovery notification frame.

67. The method according to claim 66, characterized in that, The second frame is the MAPC discovery information frame, which is sent by the second AP when it switches to the second AP's NPCA main channel and the second AP's NPCA main channel is the same as the first AP's main channel.

68. The method according to any one of claims 64 to 67, characterized in that, The first frame or the second frame carries one or more of the following fields: MAPC group field; common action field; MAPC transmission policy field; main channel center frequency field; NPCA main channel field; disabled sub-channel bitmap field; channel information request field; accept or reject field; The MAPC group field indicates whether MAPC is supported; the common action field indicates the frame type; the MAPC transmission policy field indicates the supported MAPC transmission policy; the channel information request field indicates the channel information requester or responder; and the accept or reject field indicates whether to agree to join the MAPC group, which is a set of APs used for cooperative data transmission.

69. The method according to any one of claims 61 to 68, characterized in that, Sending the second frame includes: The second frame is transmitted in a non-high-throughput repetitive manner on at least two channels, said at least one of the first AP's main channel and the first AP's NPCA main channel.

70. The method according to any one of claims 61 to 69, characterized in that, The method further includes: Receive a third frame, the third frame being used to indicate MAPC group information related to the MAPC group; The MAPC group is a set of APs used for cooperative data transmission.

71. The method according to claim 70, characterized in that, The MAPC group information includes one or more of the following: The main channel of the MAPC group; the NPCA main channel of each AP in the MAPC group; the MAPC transmission policy supported by each AP in the MAPC group; the disabled sub-channels of each AP in the MAPC group; the AP identifier ID of each AP in the MAPC group; and the MAPC EDCA parameters for enhanced distributed coordinated access (EDCA) of multiple access points. The main channel of the MAPC group is the same as the main channel of the first AP.

72. The method according to claim 70 or 71, characterized in that, The third frame carries one or more of the following fields: Common Action Field; Main Channel Center Frequency Field; NPCA Main Channel Field; MAPC Transmission Policy Field; Disabled Sub-channel Bitmap Field; AP ID Field; MAPC EDCA Field; The common action field is used to indicate the frame type; the AP ID field is used to indicate the AP ID of each AP in the MAPC group.

73. The method according to any one of claims 70 to 72, characterized in that, The receiving of the third frame includes: The third frame is received, which is sent by the first AP in a non-high-throughput repetitive manner within the operating bandwidth of the first AP.

74. The method according to any one of claims 61 to 73, characterized in that, Receiving the first frame includes: The first frame is received outside of the first service time. The first service time is indicated by the Target Wake-up Time (TWT) schedule, which is obtained in advance by the first AP and the associated site.

75. The method according to any one of claims 64 to 69, characterized in that, The first frame carries a Restricted Target Wake-Up Time (RTWT) schedule, the RTWT schedule being used to indicate a second service time. Sending the second frame includes: The second frame is sent within the second service time.

76. The method according to any one of claims 61 to 73, characterized in that, Receiving the first frame includes: Receive the first frame; Wherein, the first frame is transmitted by the first AP in a non-high-throughput repetitive manner within the operating bandwidth of the first AP; or, the first frame is transmitted by the first AP in the non-high-throughput repetitive manner on at least two sub-channels of the operating bandwidth of the first AP.

77. The method according to any one of claims 61 to 76, characterized in that, The method further includes: Receive a fourth frame, which indicates support for MAPC or indicates the execution of MAPC negotiation.

78. The method according to claim 77, characterized in that, The fourth frame includes at least one of a request to send an RTS frame and a multi-user request to send a MU-RTS frame.

79. The method according to claim 77 or 78, characterized in that, The fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the execution of MAPC negotiation.

80. The method according to any one of claims 61 to 79, characterized in that, The method further includes: A first request frame is received. The first request frame is used to negotiate the MAPC parameters required for MAPC data transmission. The MAPC parameters are used to help execute the MAPC transmission strategy.

81. The method according to claim 62, 65, 68, 71, or 80, characterized in that, The MAPC transmission strategy includes at least one of the following: Cooperative Time Division Multiple Access (Co-TDMA); Cooperative Limited Target Wake-up Time (Co-RTWT); Cooperative Beamforming (Co-BF); Cooperative Spatial Reuse (Co-SR); Seamless Roaming.

82. The method according to claim 80 or 81, characterized in that, The first request frame carries a field indicating the MAPC parameters suggested by the first AP.

83. The method according to claim 82, characterized in that, The first request frame also carries a first parameter command field, which is used to indicate that the type of MAPC parameter negotiation is a suggestion type.

84. The method according to any one of claims 80 to 83, characterized in that, The method further includes: Send a first response frame, which is used to respond to the first request frame.

85. The method according to claim 84, characterized in that, The first response frame carries a field indicating the MAPC parameters suggested by the second AP.

86. The method according to claim 85, characterized in that, The first response frame also carries a second parameter command field, which is used to indicate that the type of MAPC parameter negotiation is an alternative type.

87. The method according to any one of claims 84 to 86, characterized in that, The method further includes: Receive a second response frame, which is used to respond to the first response frame.

88. The method according to claim 87, characterized in that, The second response frame carries a field indicating whether the MAPC parameters suggested by the second AP are accepted or rejected.

89. The method according to claim 88, characterized in that, The second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type.

90. The method according to any one of claims 82 to 89, characterized in that, The MAPC parameters include one or more of the following: the proposed set of candidate sub-channels for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; modulation and coding scheme (MCS); number of spatial streams (NSS); and configuration validity period. The proposed set of candidate sub-channels for binding includes the primary channel of the first AP, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

91. The method according to any one of claims 80 to 90, characterized in that, The first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; Maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field; The common action field indicates the frame type; the parameter request field indicates the initiator or responder of the MAPC parameter negotiation; the parameter command field indicates the type of MAPC parameter negotiation; the MAPC session start time field indicates the start time of the configuration validity period, and the configuration validity period indicates the validity period of the MAPC parameters; the MAPC session duration field indicates the duration of the configuration validity period.

92. The method according to any one of claims 80 to 91, characterized in that, The method further includes: Receive an initial control frame (ICF), which is used to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; The MAPC group is a set of APs used for cooperative data transmission.

93. The method according to claim 92, characterized in that, The method further includes: Send an Initial Control Response (ICR) frame, which is used to determine the APs participating in the MAPC transmission strategy.

94. The method according to claim 93, characterized in that, The second AP is the target AP, which is an AP participating in the MAPC transmission strategy determined based on the ICR frame. The method further includes: Receive MU-RTS frames; The MU-RTS frame is used to instruct the target AP to transmit data during the Transmission Opportunity Sharing (TXS) time period.

95. A parameter negotiation method, characterized in that, The method is performed by the second access point (AP), and the method includes: Receive a first request frame, which is used to negotiate the MAPC parameters required for multi-access point cooperative MAPC data transmission.

96. The method according to claim 95, characterized in that, The first request frame carries a field indicating the MAPC parameters suggested by the first AP.

97. The method according to claim 96, characterized in that, The first request frame also carries a first parameter command field, which is used to indicate that the type of MAPC parameter negotiation is a suggestion type.

98. The method according to any one of claims 95 to 97, characterized in that, The method further includes: Send a first response frame, which is used to respond to the first request frame.

99. The method according to claim 98, characterized in that, The first response frame carries a field indicating the MAPC parameters suggested by the second AP.

100. The method according to claim 99, characterized in that, The first response frame also carries a second parameter command field, which is used to indicate that the type of MAPC parameter negotiation is an alternative type.

101. The method according to any one of claims 98 to 100, characterized in that, The method further includes: Receive a second response frame, which is used to respond to the first response frame.

102. The method according to claim 101, characterized in that, The second response frame carries a field indicating whether the MAPC parameters suggested by the second AP are accepted or rejected.

103. The method according to claim 102, characterized in that, The second response frame also carries a third parameter command field, which is used to indicate whether the type of MAPC parameter negotiation is an accept type or a reject type.

104. The method according to any one of claims 96 to 103, characterized in that, The MAPC parameters include one or more of the following: the proposed set of candidate sub-channels for binding; channel bandwidth; buffer queue; minimum transmit power; maximum transmit power; modulation and coding scheme (MCS); number of spatial streams (NSS); and configuration validity period. The proposed set of candidate sub-channels for binding includes the primary channel of the first AP, and the configuration validity period is used to indicate the validity period of the MAPC parameters.

105. The method according to any one of claims 95 to 104, characterized in that, The first request frame, the first response frame, or the second response frame carries one or more of the following fields: common action field; parameter request field; parameter command field; suggested binding subchannel bitmap field; channel bandwidth field; minimum transmit power field; Maximum transmit power field; MCS field; NSS field; MAPC session start time field; MAPC session duration field; The common action field indicates the frame type; the parameter request field indicates the initiator or responder of the MAPC parameter negotiation; the parameter command field indicates the type of MAPC parameter negotiation; the MAPC session start time field indicates the start time of the configuration validity period, and the configuration validity period indicates the validity period of the MAPC parameters; the MAPC session duration field indicates the duration of the configuration validity period.

106. The method according to any one of claims 95 to 105, characterized in that, The method further includes: Receive a fourth frame, which indicates support for MAPC or indicates the execution of MAPC negotiation.

107. The method according to claim 106, characterized in that, The fourth frame includes at least one of a request to send an RTS frame and a multi-user request to send a MU-RTS frame.

108. The method according to claim 106 or 107, characterized in that, The fourth frame carries a MAPC group identifier field, which is used to indicate support for MAPC or to indicate the execution of MAPC negotiation.

109. The method according to any one of claims 95 to 108, characterized in that, The MAPC parameters are used to help execute the MAPC transmission strategy, and the method further includes: Receive an initial control frame (ICF), which is used to poll the APs in the MAPC group to determine the APs participating in the MAPC transmission strategy; The MAPC group is a set of APs used for cooperative data transmission.

110. The method according to claim 109, characterized in that, The method further includes: Send an Initial Control Response (ICR) frame, which is used to determine the APs participating in the MAPC transmission strategy.

111. The method according to claim 110, characterized in that, The second AP is the target AP, which is an AP that participates in the MAPC transmission strategy based on the ICR frame. The method further includes: receiving MU-RTS frames. The MU-RTS frame is used to instruct the target AP to transmit data during the Transmission Opportunity Sharing (TXS) time period.

112. The method according to any one of claims 95 to 111, characterized in that, The MAPC parameters are used to help execute the MAPC transmission strategy, which includes at least one of the following: Cooperative Time Division Multiple Access (Co-TDMA); Cooperative Limited Target Wake-up Time (Co-RTWT); Cooperative Beamforming (Co-BF); Cooperative Spatial Reuse (Co-SR); Seamless Roaming.

113. A first wireless device, characterized in that, The first wireless device includes: A transmitting module is configured to transmit a first frame, the first frame being used to indicate first multiple access point cooperation (MAPC) information associated with the first wireless device; The first MAPC information is used to indicate the information required for MAPC to transmit data.

114. A second wireless device, characterized in that, The second wireless device includes: A receiving module is configured to receive a first frame, wherein the first frame is used to indicate first multiple access point cooperation (MAPC) information associated with the first wireless device. The first MAPC information is used to indicate the information required for MAPC to transmit data.

115. A first wireless device, characterized in that, The first wireless device includes: The sending module is used to send a first request frame, which is used to negotiate the MAPC parameters required for multi-access point cooperative MAPC data transmission.

116. A second wireless device, characterized in that, The second wireless device includes: The receiving module is used to receive a first request frame, which is used to negotiate the MAPC parameters required for multi-access point cooperative MAPC data transmission.

117. A first wireless device, characterized in that, The first wireless device includes: A transceiver module is used to receive and / or send at least one frame, said at least one frame being associated with the Multi-Access Point Cooperative (MAPC) discovery process.

118. A first wireless device, characterized in that, The first wireless device includes: A transceiver module is used to receive and / or send at least one frame, said at least one frame being associated with the Multi-Access Point Cooperative (MAPC) negotiation process.

119. A first AP, characterized in that, The first AP includes: A processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the communication method between access points (APs) as described in any one of claims 1 to 36; and / or, the parameter negotiation method as described in any one of claims 37 to 56; and / or, the communication method between APs as described in claim 57 or 58; and / or, the communication method between APs as described in claim 59 or 60.

120. A second AP, characterized in that, The second AP includes: A processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the communication method between access points (APs) as described in any one of claims 61 to 94; and / or, the parameter negotiation method as described in any one of claims 95 to 112.

121. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one program, which is loaded and executed by a processor to implement the communication method between access points (APs) as described in any one of claims 1 to 36; and / or the parameter negotiation method as described in any one of claims 37 to 56. And / or, the inter-AP communication method of claim 57 or 58; and / or, the inter-AP communication method of claim 59 or 60; and / or, the inter-AP communication method of any one of claims 61 to 94; and / or, the parameter negotiation method of any one of claims 95 to 112.

122. A chip, characterized in that, The chip includes programmable logic circuits and / or program instructions, which, when running on the first AP, are used to implement the communication method between access points (APs) as described in any one of claims 1 to 36; and / or the parameter negotiation method as described in any one of claims 37 to 56. And / or, the inter-AP communication method of claim 57 or 58; and / or, the inter-AP communication method of claim 59 or 60; when the chip is running on the second AP, it is used to implement the inter-AP communication method of any one of claims 61 to 94; and / or, the parameter negotiation method of any one of claims 95 to 112.

123. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, a processor retrieving the computer instructions from the computer-readable storage medium, and the processor executing the computer instructions to implement the communication method between access points (APs) as described in any one of claims 1 to 36; and / or, the parameter negotiation method as described in any one of claims 37 to 56. And / or, the inter-AP communication method of claim 57 or 58; and / or, the inter-AP communication method of claim 59 or 60; and / or, the inter-AP communication method of any one of claims 61 to 94; and / or, the parameter negotiation method of any one of claims 95 to 112.

Images