Communication method and communication apparatus
By determining the preamble puncturing information through collaborative negotiation among APs, the channel conflict problem in multi-AP collaborative frequency band puncturing is solved, thereby improving spectrum utilization and transmission efficiency.
Patent Information
- Application Number
- PCT/CN2026/093579
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-05
- Filing Date
- 2026-04-28
- Publication Date
- 2026-11-12
AI Technical Summary
In existing technologies, in multi-AP collaborative frequency band punching schemes, APs that send messages later cannot actively avoid frequency band conflicts with APs that send messages earlier, resulting in low spectrum utilization.
By coordinating between the first and second devices, the preamble punching information is determined, channel conflicts are avoided, and spectrum utilization is improved.
It effectively avoids channel conflicts, improves the utilization rate of spectrum resources, and meets the transmission needs of various devices.
Smart Images

Figure CN2026093579_12112026_PF_FP_ABST
Abstract
Description
A communication method and a communication device
[0001] Cross-reference to related applications
[0002] This application claims priority to Chinese Patent Application No. 202510575148.6, filed on May 5, 2025, entitled "A Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to the field of wireless communication technology, and in particular to a communication method and a communication device. Background Technology
[0004] Currently, multi-AP collaborative technologies include Coordinated Time Division Multiple Access (Co-TDMA), Coordinated Spatial Reuse (Co-SR), and Coordinated Beamforming (Co-BF). From a frequency domain perspective, these technologies allow access points (APs) to coordinate and avoid mutual interference (e.g., when the operating frequency bands of two APs partially or completely overlap). To address this, Wi-Fi technologies have defined frequency band puncturing. The applicable scenario for frequency band puncturing is: if a Wi-Fi device detects that the primary 20MHz channel is idle but some secondary 20MHz bands are busy (already occupied by other Wi-Fi devices), then the Wi-Fi device can choose not to transmit on these secondary 20MHz bands, but only on the remaining idle bands, thereby improving channel access capability and fully utilizing the spectrum.
[0005] However, in current frequency band puncturing schemes, multiple access points (APs) can only passively puncture the frequency band occupied by the AP that sent the message first, resulting in the AP being unable to send its message later and thus affecting spectrum utilization. For example, if AP1 sends a message first, and the operating frequency band of this message occupies 20MHz of AP2's main frequency band, AP2 cannot send its message through this 20MHz main frequency band and must wait until AP1 finishes sending its message. This results in wasted spectrum resources for AP2, leading to low spectrum utilization and other problems.
[0006] Therefore, how to improve spectrum utilization by coordinating among APs to perform frequency band puncturing is a problem that needs to be solved. Summary of the Invention
[0007] This application proposes a communication method and communication device for improving spectrum utilization by coordinating between APs to perform frequency band puncturing (or preamble puncturing).
[0008] In a first aspect, this application provides a communication method that can be applied to a first device, or a component of the first device (e.g., a processor, chip, or chip system), or a logic node, logic module, or software capable of implementing all or part of the functions of the first device, or a device compatible with the first device. Taking the application of this method to a first device as an example, the method includes: the first device sending first information to a second device, the first information being used to instruct cooperative execution of preamble puncturing transmission; the first device receiving second information from the second device, the second information being used to instruct the second device to support cooperative execution of preamble puncturing transmission, the second information including the main channel information of the second device, wherein the main channel of the second device and the main channel of the first device do not overlap, and the channels of the second device and the first device overlap; and the first device determining preamble puncturing information based on the main channel information of the second device.
[0009] In the above description, the method of this application is illustrated by taking the first device as the sharer of a transmission opportunity (TXOP) and the second device as the recipient of the TXOP. The first device and the second device are different devices or apparatuses. For example, if the above method is applied to a wireless local area network (WLAN), the first device can be an access point device, such as AP1 or AP multi-link device (MLD) 1; the second device can be another access point device, such as AP2 or AP multi-link device (MLD) 2. If the above method is applied to a Starflash system, the first device can be a grant (G) node or management device, such as management device 1, and the second device can be another G node or management device, such as management device 2. If the above method is applied to a wireless wide area network, the first device can be a base station, such as base station 1; the second device can be another base station, such as base station 2. In this application, the second device does not necessarily represent a single device, but can represent one or more devices other than the first device; in other words, the number of second devices in this application is one or more.
[0010] In the embodiments of this application, preamble puncturing transmission can refer to: during the transmission of physical layer protocol data unit (PPDU), puncturing and transmission are performed when there is no signal in at least one 20MHz sub-channel within the PPDU bandwidth. Preamble puncturing transmission can also refer to: channels occupied by other devices need to be transmitted by puncturing in order to avoid interference.
[0011] In the above method, the first device sends first information to the second device, which instructs the cooperative execution of preamble puncturing transmission. The first device then receives second information from the second device, which instructs the second device to support the cooperative execution of preamble puncturing transmission. The second information includes the second device's main channel information. While the second device's main channel and the first device's main channel do not overlap, their channels do overlap. Based on this, the first device determines the preamble puncturing information according to the second device's main channel information. Therefore, the first device can coordinate with the second device to determine the preamble puncturing information in advance, avoiding channel conflicts during subsequent concurrent transmissions. This effectively prevents the waste of spectrum resources and improves spectrum resource utilization.
[0012] In one possible implementation, the preamble punch information includes at least one of the following:
[0013] (1) Preamble punching information of the first device; (2) Preamble punching information of the second device.
[0014] Through this implementation, the first device determines the preamble punching information of the first device and the preamble punching information of the second device, so that the first device side and the second device side can respectively perform the corresponding preamble punching and transmission.
[0015] In one possible implementation, the first device determines the preamble puncturing information based on the master channel information of the second device. This includes: the first device determining the preamble puncturing information based on its own channel information, master channel information, and the master channel information of the second device. With this implementation, when the first device participates in concurrent transmission with the second device, the first device negotiates and determines the preamble puncturing information based on its own channel information, master channel information, and the master channel information of the second device. This effectively avoids channel conflicts during concurrent transmission between the first and second devices, thus preventing the waste of frequency resources for both devices.
[0016] In one possible implementation, the first device determines the preamble puncture information based on its own channel information and main channel information, as well as the main channel information of the second device. This includes: the first device determining the preamble puncture information based on its own channel information and main channel information, as well as the main channel information of the second device; wherein the channel information of the second device is carried in second information. This implementation improves the accuracy of the preamble puncture information, thereby effectively avoiding channel conflicts in subsequent concurrent transmissions.
[0017] In one possible implementation, the second information also includes transmission requirement information of the second device, which includes at least one of the following:
[0018] (1) The amount of data buffered by the second device; (2) The transmission rate of the second device; (3) The transmission bandwidth (or transmission frequency) of the second device.
[0019] Through this implementation method, the first device can effectively obtain the transmission requirement information of the second device.
[0020] In one possible implementation, the first device determines the preamble puncturing information based on its own channel information and primary channel information, as well as the channel information and primary channel information of the second device. This includes: the first device determining the preamble puncturing information based on its own channel information and primary channel information, the channel information and primary channel information of the second device, its own transmission requirement information, and the transmission requirement information of the second device. Through this implementation, the first device negotiates and determines the preamble puncturing information based on the channel information and primary channel information of multiple devices, as well as the transmission requirement information of those devices. This not only effectively avoids channel conflicts during concurrent transmission by multiple devices and improves spectrum utilization, but also meets the transmission requirements of each device.
[0021] In one possible implementation, the method further includes: the first device sending preamble punching information to the second device. This implementation enables the second device to also obtain the preamble punching information, allowing it to subsequently use this information for punched transmission.
[0022] In one possible implementation, the method further includes: the first device sending third information to a third device associated with the first device, the third information including the preamble punching information of the first device. In this embodiment, the third device may refer to one or more non-access point sites (e.g., STA or STA MLD) or terminal devices associated with the first device. This implementation allows each device associated with the first device to obtain the preamble punching information of the first device, facilitating subsequent punching and transmission.
[0023] In one possible implementation, the preamble punching information of the first device includes the punching channel information and the punching time information of the first device, and the preamble punching information of the second device includes the punching channel information and the punching time information of the second device.
[0024] With this implementation, the preamble punching information corresponding to the first and second devices respectively includes not only punching channel information but also punching time information. This allows the devices to perform channel punching and transmission at the precise time, thereby ensuring the effectiveness of channel punching.
[0025] In one possible implementation, the unpunctured channels of the first device and the second device do not overlap. This implementation ensures that the first device and the second device do not collide when transmitting through their respective unpunctured channels.
[0026] In one possible implementation, the unpunctured channels of the first device and the second device partially overlap, and the unpunctured channels of the first device do not include the main channel of the second device, and vice versa. With this implementation, the first and second devices can transmit promptly through their respective main channels without conflict. Furthermore, the first and second devices can flexibly occupy their corresponding unpunctured channels.
[0027] In one possible implementation, the method further includes: a first device determining the channel occupied by the second device; the unpunctured channel of the first device overlapping with the channel occupied by the second device; and the first device puncturing the unpunctured channel of the first device according to the channel occupied by the second device. Through this implementation, the first device detects the channel occupied by the second device and promptly punctures its own unpunctured channel to avoid channel conflicts during concurrent transmission with the second device.
[0028] In one possible implementation, the channels of the first device and the second device completely overlap, or partially overlap. With this implementation, regardless of whether the channels of the first and second devices completely or partially overlap, the preamble puncturing information can be pre-negotiated to avoid channel conflicts in subsequent transmissions.
[0029] In one possible implementation, the preamble punching information is carried in the initial control frame, which also includes the address information and / or identification information of the second device. With this implementation, the first device can accurately send the preamble punching information to the corresponding second device.
[0030] In one possible implementation, the first information is a poll frame. With this implementation, the first device sends poll frames so that each second device in the system can respond promptly to whether to participate in the coordinated execution of preamble puncturing transmission, thereby effectively ensuring that subsequent concurrent transmissions within the system will not experience channel conflicts.
[0031] Secondly, this application provides a communication method that can be applied to a second device, or a component of the second device (e.g., a processor, chip, or chip system), or a logic node, logic module, or software capable of implementing all or part of the functions of the second device, or a device used in conjunction with the second device. Taking the application of this method to a second device as an example, the method includes: the second device receiving first information from a first device, the first information being used to instruct cooperative execution of preamble puncturing transmission; the second device sending second information to the first device, the second information being used to instruct the second device to support cooperative execution of preamble puncturing transmission, the second information including the main channel information of the second device, the main channel of the second device and the main channel of the first device not overlapping, and the channels of the second device and the first device overlapping; the main channel information of the second device being used to determine preamble puncturing information.
[0032] In the above description, the method of this application is illustrated by taking the first device as the sharer of the TXOP and the second device as the sharer of the TXOP. The first device and the second device are different devices or apparatuses. For example, if the above method is applied to a wireless local area network (WLAN), the first device can be an access point device, such as AP1 or AP MLD 1; the second device can be another access point device, such as AP2 or AP MLD 2. If the above method is applied to a StarSpark system, the first device can be a management G node or management device, such as management device 1, and the second device can be another G node or management device, such as management device 2. If the above method is applied to a wireless wide area network (WAN), the first device can be a base station, such as base station 1; the second device can be another base station, such as base station 2. In this application, the second device does not simply represent one device, but rather one or more access point devices other than the first device; in other words, the number of second devices in this application is one or more.
[0033] In the above method, the second device receives first information from the first device, which instructs for coordinated preamble puncturing transmission. If the second device supports coordinated preamble puncturing transmission, it responds by sending second information to the first device. This second information includes the second device's main channel information, where the second device's main channel and the first device's main channel do not overlap, but their channels do overlap. Based on this, the first device can obtain the second device's main channel information and then determine the preamble puncturing information accordingly. Therefore, this method allows the first device to coordinate with the second device to determine the preamble puncturing information in advance, avoiding channel conflicts during subsequent concurrent transmissions. This effectively prevents the waste of spectrum resources and improves spectrum resource utilization.
[0034] In one possible implementation, the method further includes: a second device receiving preamble punching information from a first device. With this implementation, the second device can obtain the preamble punching information and then use it for punching and transmission.
[0035] In one possible implementation, the preamble punch information includes at least one of the following:
[0036] (1) Preamble punching information of the first device; (2) Preamble punching information of the second device.
[0037] In one possible implementation, the second information also includes transmission requirement information of the second device, which includes at least one of the following:
[0038] (1) The amount of data buffered by the second device; (2) The transmission rate of the second device; (3) The transmission bandwidth (or transmission frequency) of the second device. This implementation method enables the first device to effectively obtain the transmission requirement information of the second device.
[0039] In one possible implementation, the method further includes: the second device sending fourth information to a fourth device associated with the second device, the fourth information including the preamble punching information of the second device. In this embodiment, the fourth device may refer to one or more non-access point sites (e.g., STA or STA MLD) or terminal devices associated with the second device. This implementation allows each device associated with the second device to obtain the preamble punching information of the second device, facilitating subsequent punching and transmission.
[0040] In one possible implementation, the preamble puncturing information of the first device includes the puncturing channel information and the puncturing time information of the first device, and the preamble puncturing information of the second device includes the puncturing channel information and the puncturing time information of the second device. Through this implementation, the preamble puncturing information corresponding to the first and second devices respectively includes not only the puncturing channel information but also the puncturing time information. This allows the devices to perform channel puncturing and transmission at precise times, thereby ensuring the effectiveness of channel puncturing.
[0041] In one possible implementation, the unpunctured channels of the first device and the second device do not overlap. This implementation ensures that the first device and the second device do not collide when transmitting through their respective unpunctured channels.
[0042] In one possible implementation, the unpunctured channels of the first device and the second device partially overlap, and the unpunctured channels of the first device do not include the main channel of the second device, and vice versa. With this implementation, the first and second devices can transmit promptly through their respective main channels without conflict. Furthermore, the first and second devices can flexibly occupy their corresponding unpunctured channels.
[0043] In one possible implementation, the method further includes: a second device determining the channel occupied by the first device; the unpunctured channel of the second device overlapping with the channel occupied by the first device; and the second device puncturing the unpunctured channel of the second device according to the channel occupied by the first device. Through this implementation, the second device detects the channel occupied by the first device and promptly punctures its own unpunctured channel to avoid channel conflicts during concurrent transmission with the first device.
[0044] In one possible implementation, the channels of the first device and the second device completely overlap, or partially overlap. With this implementation, regardless of whether the channels of the first and second devices completely or partially overlap, the preamble puncturing information can be pre-negotiated to avoid channel conflicts in subsequent transmissions.
[0045] In one possible implementation, the preamble punching information is carried in the initial control frame, which also includes the address information and / or identification information of the second device. With this implementation, the first device can accurately send the preamble punching information to the corresponding second device.
[0046] In one possible implementation, the first information is a poll frame. With this implementation, the first device sends poll frames so that each second device in the system can respond promptly to whether to participate in the coordinated execution of preamble puncturing transmission, thereby effectively ensuring that subsequent concurrent transmissions within the system will not experience channel conflicts.
[0047] In the embodiments of this application, the number of second devices may be one or more. When there are multiple second devices, each second device is implemented with reference to the method described in the first aspect above and any possible implementation thereof.
[0048] Thirdly, this application provides a communication device, which is a first device or a chip corresponding to the first device. The communication device has the function of implementing the first aspect and any of its possible embodiments, or the communication device has the function of implementing the third aspect and any of its possible embodiments. The communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.
[0049] In one possible design, the communication device includes a processor configured to support the communication device in performing corresponding functions of the first device in the method described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. The number of processors and / or memories mentioned above may be one or more.
[0050] Optionally, the communication device further includes an interface circuit for supporting communication between the communication device and other communication devices, such as the transmission and reception of data or signals. For example, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
[0051] In one possible design, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.
[0052] In one possible design, the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples, as described in the method provided in the first aspect, and will not be repeated here.
[0053] Fourthly, this application provides a communication device, which is a second device or a chip corresponding to a second device. The communication device has the functions to implement the second aspect described above and any of the possible embodiments therein. The communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.
[0054] In one possible design, the communication device includes a processor configured to support the communication device in performing the corresponding functions of the second device in the method described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. The number of processors and / or memories mentioned above can be one or more.
[0055] Optionally, the communication device further includes an interface circuit for supporting communication between the communication device and other communication devices, such as the transmission and reception of data or signals. For example, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
[0056] In one possible design, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.
[0057] In one possible design, the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples, as described in the method provided in the second aspect, and will not be repeated here.
[0058] Fifthly, this application provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor implements the methods in the first aspect and any possible implementation thereof through logic circuits or execution code instructions. The number of processors described in the fifth aspect may be one or more.
[0059] In a sixth aspect, this application provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor implements the methods in the second aspect and any of the possible implementations thereof through logic circuits or execution code instructions. The number of processors described in the sixth aspect may be one or more.
[0060] In a seventh aspect, this application provides a communication system including a first device and a second device, wherein the first device is used to implement the method described in the first aspect and any possible implementation thereof, and the second device is used to implement the method described in the second aspect and any possible implementation thereof.
[0061] Eighthly, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed by a processor, implement the methods of any one of the first and second aspects and any possible implementation thereof.
[0062] Ninthly, this application provides a computer program product storing instructions that, when executed by a processor, implement the methods of any one of the first and second aspects and any possible implementation thereof.
[0063] In a tenth aspect, this application provides a chip system including a processor and potentially a memory, for implementing the methods of any one of the first and second aspects and any possible implementation thereof. The chip system may be composed of chips or may include chips and other discrete devices.
[0064] It should be noted that the technical effects that can be achieved by any of the third to tenth aspects or any of the third to tenth aspects can be referred to the description of the technical effects that can be achieved by any of the first and second aspects or any of the first and second aspects, which will not be repeated here. Attached Figure Description
[0065] Figure 1A is a schematic diagram showing the locations of multiple pairs of transceivers in the same space and channel;
[0066] Figure 1B is a schematic diagram of multiple pairs of transceivers using the channel for communication according to TDMA time-sharing.
[0067] Figure 2 is a logical diagram of three basic BSS accessing DS;
[0068] Figure 3 is a schematic diagram of a TXOP;
[0069] Figure 4A is a schematic diagram of a Co-TDMA TXOP;
[0070] Figure 4B is a schematic diagram of Co-TDMA interaction among multiple APs;
[0071] Figure 5 is a schematic diagram of a bandwidth punched transmission;
[0072] Figure 6 is a schematic diagram of a WLAN network architecture applicable to an embodiment of this application;
[0073] Figure 7 is a flowchart illustrating a communication method provided in an embodiment of this application;
[0074] Figure 8 is a schematic flowchart of a method according to one embodiment of this application;
[0075] Figure 9A is a schematic diagram of cooperative frequency band punching transmission under the condition of complete overlap of multiple AP working frequency bands provided in the embodiment of this application;
[0076] Figure 9B is a schematic diagram of cooperative frequency band puncturing transmission under partial overlap of multiple AP operating frequency bands provided in the embodiments of this application;
[0077] Figure 9C is a schematic diagram of cooperative frequency band puncturing transmission under the overlapping of multiple AP working frequency bands provided in the embodiments of this application;
[0078] Figure 10A is a schematic diagram of synchronous concurrent transmission of static punching in an embodiment of this application;
[0079] Figure 10B is a schematic diagram of asynchronous concurrent transmission of static punching in an embodiment of this application;
[0080] Figure 11 is a schematic flowchart of another embodiment of the method provided in this application;
[0081] Figure 12A is a schematic diagram of a static punching frequency band provided in an embodiment of this application;
[0082] Figure 12B is a schematic diagram of a dynamic punching frequency band provided in an embodiment of this application;
[0083] Figure 12C is a schematic diagram of another dynamic punching frequency band provided in the embodiments of this application;
[0084] Figure 13 is a schematic diagram of asynchronous concurrent transmission of static and dynamic punching in an embodiment of this application;
[0085] Figure 14 is a schematic flowchart of another embodiment of the method provided in this application;
[0086] Figure 15A is a schematic diagram of cooperative frequency band punching transmission under the condition of complete overlap of working frequency bands among multiple APs provided in the embodiments of this application;
[0087] Figure 15B is a schematic diagram of cooperative frequency band punching transmission under partial overlap of working frequency bands among multiple APs provided in the embodiments of this application;
[0088] Figure 16 is a schematic flowchart of another embodiment of the method provided in this application;
[0089] Figure 17 is a schematic diagram of collaborative punch-through transmission between shared APs provided in this application;
[0090] Figure 18 is a schematic diagram of the structure of a communication device according to an embodiment of this application;
[0091] Figure 19 is a schematic diagram of another communication device according to an embodiment of this application;
[0092] Figure 20 is a schematic diagram of a chip device structure according to an embodiment of this application. Detailed Implementation
[0093] The scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0094] To better understand the solutions provided in the embodiments of this application, some terms, concepts, and related technologies involved in the embodiments of this application will be explained below. These explanations are intended to make the embodiments of this application easier to understand and should not be regarded as limiting the scope of protection claimed in this application.
[0095] (1) Time Division Multiple Access (TDMA):
[0096] TDMA technology allows multiple users to use the same frequency resources in different time periods. When there are multiple pairs of transceivers in the same space, such as the two pairs shown in Figure 1A (STA1-1 and STA1-2, and STA2-1 and STA2-2), and these transceivers overlap, they can communicate using the channel according to TDMA time-sharing (as shown in Figure 1B). As shown in Figure 1B, during T0 to T1, STA1-1 and STA1-2 communicate, while STA2-1 and STA2-2 do not. During T1 to T2, STA2-1 and STA2-2 communicate, while STA1-1 and STA1-2 do not communicate. This effectively avoids interference.
[0097] (2) Infrastructure-based BSS:
[0098] A Basic Service Set (BSS) is a fundamental module of IEEE 802.11 local area networks, consisting of several Standalone (STAs). Different types of BSSs have different topologies formed by their member STAs. Based on their topology, functions, and other characteristics, BSSs can be categorized into basic infrastructure BSSs, independent basic service sets (IBSSs), and others.
[0099] In an infrastructure-type BSS, a special site acts as the access distribution system (DS), called the Access Point (AP). Other sites are called non-AP STAs. All non-AP STAs must access the DS through an AP, meaning they need to be associated with an AP, and by default, they cannot communicate directly with each other. For example, Figure 2 shows a logical diagram of three infrastructure-type BSSs accessing the DS. In each infrastructure-type BSS, each non-AP STA can access the DS through its corresponding associated AP.
[0100] Note that the term "site in an infrastructure-type BSS" is used in this application. This site can be an AP or a non-AP STA.
[0101] (3) Channel:
[0102] A channel refers to a segment of spectrum resources. The concept of a channel is often used in spectrum resource allocation, and one channel is typically 20MHz. For example, in the unlicensed spectrum of 5.1 and 5.8 GHz, a segment of spectrum resources is divided into multiple channels, each with a number, such as channel numbers 149, 153, 157, 161, 165, etc., and each channel has a bandwidth of 20MHz.
[0103] For example, if the bandwidth of each channel in the system is defined as 20MHz, then a 20MHz band and a channel can be understood as equivalent.
[0104] (4) Preamble puncturing transmission:
[0105] In this application, preamble puncturing transmission can refer to: during the transmission of Physical Layer Protocol Data Units (PPDUs), puncturing and transmitting data when there is no signal in at least one 20MHz sub-channel within the PPDU bandwidth. Preamble puncturing transmission can also refer to: transmitting data through puncturing channels occupied by other devices to avoid interference.
[0106] For example, this technology is applicable to Wi-Fi networks, where channel bonding in discontinuous or interfering conditions can effectively avoid the waste of overall channel resources caused by interference from a single 20MHz channel.
[0107] In the embodiments of this application, "preamble puncturing transmission" can be replaced by "band puncturing transmission", "band puncturing transmission", or "subchannel puncturing transmission", etc.
[0108] (5) Transmission opportunity (TXOP):
[0109] The IEEE 802.11 protocol stipulates that before transmitting data, stations must compete for the channel using the carrier sense multiple access with collision avoidance (CSMA / CA) mechanism. This means that stations must listen for available media, and only when the media is idle for a certain duration can a station transmit. As shown in Figure 3, when STA1 successfully acquires the channel after the required channel idle time (i.e., STA1 has successfully acquired the channel), it is considered to have obtained a TXOP (Transmission Request Opportunity). STA1 can then use this channel for transmission for a period of time. Other stations will not actively attempt to transmit when they detect STA1's TXOP, allowing STA1 to transmit efficiently and without interference during this period. After the TXOP period ends, all stations can continue to compete for the channel.
[0110] (6) Coordinated Time Division Multiple Access (Co-TDMA) technology:
[0111] Co-TDMA technology is a technique used in multi-access point (AP) collaboration in Wi-Fi (such as Wi-Fi 8). As shown in Figure 4A, after AP1 obtains the TXOP, AP1 and AP2 can establish a Co-TDMA TXOP. Based on this, AP1 can transmit within its BSS. AP1 can also share part of the TXOP duration with AP2 participating in Co-TDMA. During this part of the TXOP duration, AP2 can transmit within its BSS. After sharing, AP2, whose TXOP was shared, can return the TXOP to AP1. For example, if AP2 did not use up the portion of the TXOP duration allocated to it, it will return the remaining duration to AP1. If there is still TXOP duration remaining after AP1 shares the TXOP with AP2, or after AP2 returns the TXOP, AP1 can continue to process the remaining TXOP duration. For example, AP1 can share the remaining TXOP duration with other APs participating in Co-TDMA, use the remaining TXOP duration for transmission within its BSS, or terminate the TXOP early.
[0112] For example, Figure 4B illustrates a specific transmission process for Co-TDMA:
[0113] Referring to Figure 4B, AP1 is the Co-TDMA sharer. At the start of the TXOP, AP1 sends an initial control frame (ICF). The ICF informs AP1 that it will share a portion of the TXOP time with AP2 and AP3 for transmission and inquires about their willingness. After receiving the ICF, AP2 and AP3 each send a response frame to AP1. The response frame indicates whether they accept the time allocation from AP1 within the current TXOP. This can be considered the polling phase. Next, AP1 can transmit with one or more associated STAs. After the short interframe space (SIFS), i.e., during the TXOP allocation phase, AP1 can send a MU-RTS TXS trigger frame to AP2. The MU-RTS TXS trigger frame instructs AP2 to transmit one or more PPDUs within the allocated TXOP portion of the duration. After receiving the MU-RTS TXS trigger frame from AP1, AP2 sends a clear to send (CTS) frame back to AP1. The CTS frame is used to respond to AP1 in response to AP2's acceptance of the allocation. Furthermore, AP2 can transmit with one or more associated STAs within the allocated TXOP portion of the duration. After AP2 completes its transmission within the allocated TXOP portion of the duration, if there is any remaining time in the allocated TXOP portion, AP2 returns that remaining time to AP1. Alternatively, AP2 returns the TXOP to AP1 at the end of the allocated TXOP portion of the duration; this phase can be considered the phase where AP2 returns the TXOP.
[0114] In this application, no specific restrictions are placed on the conditions for AP2 to return TXOP to AP1, or on the signaling used when AP2 returns TXOP to AP1.
[0115] After AP2 returns the TXOP to AP1, AP1 can continue to use the TXOP for transmission, or AP1 can continue to share the TXOP with other devices, such as AP3. The process of AP1 sharing the TXOP with AP3 (including the TXOP allocation phase for AP3, the transmission within AP3's BSS, and the phase of AP3 returning the TXOP) can be referred to the process of AP1 sharing the TXOP with AP2 (including the TXOP allocation phase for AP2, the transmission within AP2's BSS, and the phase of AP2 returning the TXOP) mentioned above, which will not be detailed here. Alternatively, AP1 can terminate the TXOP early, etc.
[0116] In the embodiments of this application, "at least one" refers to one or more, and "more than one" 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, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.
[0117] Furthermore, unless otherwise stated, the ordinal numbers such as "first," "second," or "1," "2," etc. (except in special cases indicating numerical values) mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, "first information" and "second information" are only used to distinguish different information, and do not indicate a difference in the size, priority, or importance of these two pieces of information. Similarly, "AP1" and "AP2" are only used to distinguish different APs, and do not indicate a difference in the size, priority, or importance of these two APs.
[0118] It should be noted that in this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner. In the embodiments of this application, "of," "relevant," and "corresponding" may sometimes be used interchangeably, and it should be pointed out that their intended meanings are consistent unless their distinction is emphasized.
[0119] The terms "comprising" and "having," and any variations thereof, used in the following description of embodiments of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. Furthermore, the term "for indicating" used in the description of embodiments of this application can include both direct and indirect indication. When describing an indication message for indicating A, it may include whether the indication message directly indicates A or indirectly indicates A, but does not necessarily mean that the indication message carries A.
[0120] The foregoing section introduced some terms, concepts, and related technologies involved in the embodiments of this application. The following section introduces the technical problems, solutions, and devices involved in the embodiments of this application.
[0121] Currently, multi-AP collaborative technologies include Coordinated Time Division Multiple Access (Co-TDMA), Coordinated Spatial Reuse (Co-SR), and Coordinated Beamforming (Co-BF). From a frequency domain perspective, these technologies allow access points (APs) to coordinate and avoid mutual interference (e.g., when the operating frequency bands of two APs partially or completely overlap). To address this, Wi-Fi technologies have defined frequency band puncturing. The applicable scenario for frequency band puncturing is: if a Wi-Fi device detects that the primary 20MHz channel is idle but some secondary 20MHz bands are busy (already occupied by other Wi-Fi devices), then the Wi-Fi device can choose not to transmit on these secondary 20MHz bands, but only on the remaining idle bands, thereby improving channel access capability and fully utilizing the spectrum.
[0122] However, in current frequency band puncturing schemes, multiple APs can only passively puncture the frequency band occupied by the AP that sends the message first, resulting in the AP being unable to send messages and thus affecting spectrum utilization. For example, as shown in Figure 5, from the time and frequency axis perspective, AP1 sends a message first, which occupies 20MHz of AP2's main frequency band. This prevents AP1 from sending messages in its own 20MHz main frequency band and requires it to wait until AP1 finishes sending its message before sending its own. This results in a waste of spectrum resources (AP2's operating bandwidth is greater than AP1's operating bandwidth; generally, if the union of the operating frequency bands of AP1 and AP2 is greater than the maximum of the operating bandwidths of AP1 and AP2, there may be a waste of spectrum resources), leading to low spectrum utilization.
[0123] To address the aforementioned problems, embodiments of this application provide a communication method and a communication device for improving spectrum utilization by collaboratively performing frequency band puncturing (or preamble puncturing) between access points. The method and device are based on the same inventive concept. Since the principles underlying the problems solved by the method and device are similar, their implementations can be mutually referenced, and repeated details will not be elaborated further.
[0124] This application's embodiments can be applied to wireless local area network (WLAN) scenarios. For example, they can be applied to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 system standards, such as 802.11be, Wi-Fi 7, or Extremely High Throughput (EHT), 802.11bf, and next-generation standards like Wi-Fi 8 or even later. Alternatively, this application's embodiments can also be applied to WLAN systems such as Internet of Things (IoT) networks or Vehicle-to-X (V2X) networks. Of course, this application's embodiments can also be applied to StarFlash communication systems, as well as other possible communication systems, such as 5th generation (5G) systems, new radio (NR) systems, or future communication systems.
[0125] This application can support the Spark Link / NearLink standard protocol. It can also support IEEE protocols, such as IEEE 802.11be / Wi-Fi 7 / EHT protocol, IEEE 802.11bn / UHR / Wi-Fi 8 protocol, IEEE Integrated mmWave / IMMW protocol, IEEE 802.15 / UWB protocol, or IEEE 802.11bf / sensing protocol.
[0126] The following examples illustrate how the embodiments of this application can be applied to WLAN scenarios. It should be understood that WLAN standards, starting with 802.11a / g, have evolved through 802.11n, 802.11ac, 802.11ax, and the currently discussed 802.11be. 802.11n can also be called high throughput (HT); 802.11ac can also be called very high throughput (VHT); 802.11ax can also be called high efficiency (HE) or Wi-Fi 6; 802.11be can also be called EHT or Wi-Fi 7. Standards prior to HT, such as 802.11a / b / g, can be collectively referred to as non-high throughput (Non-HT).
[0127] The communication systems described above are merely illustrative examples, and the communication systems applicable to this application are not limited thereto. The communication systems provided in this application do not impose any limitations on the solutions of this application. This will be explained uniformly here and will not be repeated below.
[0128] For example, Figure 6 illustrates a network architecture diagram of a WLAN applicable to an embodiment of this application. Referring to Figure 6, this network architecture is based on a WLAN comprising two access points (AP1 and AP2) and four non-AP STAs (STA1-1, STA1-2, STA2-1, and STA2-2). STA1-1 and STA1-2 are associated with AP1, and STA2-1 and STA2-2 are associated with AP2. An association between a STA and an AP means that the STA accesses the basic service set (BSS) of the AP. The AP can configure and manage the STA's network, enabling it to communicate through the AP's network access and / or communicate with other STAs within the BSS. Conversely, if a STA is not associated with an AP, it cannot use the network services provided by the AP, nor can it communicate with the AP or other STAs within its BSS. As shown in Figure 6, AP1 is associated with STA1-1 and STA1-2, but not with STA2-1 and STA2-2. AP2 is associated with STA2-1 and STA2-2, but not with STA1-1 and STA1-2. To distinguish them, in Figure 6, solid lines are used to indicate the association between AP1 and STA1-1 and STA1-2, and solid lines are used to indicate the association between AP2 and STA2-1 and STA2-2. Unassociated APs are not connected to STAs by solid lines.
[0129] It should be noted that the number of APs and STAs in Figure 6 is only an example, and there can be more or fewer. For example, AP1 may be associated with other STAs besides STA1-1 and STA1-2, and AP2 may be associated with other STAs besides STA2-1 and STA2-2. Alternatively, AP1 may be associated with STA1-1 or STA1-2, and AP2 may be associated with STA2-1 or STA2-2. Furthermore, the WLAN network architecture shown in Figure 6 may include even more APs. This embodiment can also be applied to communication between APs. For example, APs can communicate with each other through a distributed system (DS). The dashed lines in Figure 6 represent the connection and communication between AP1 and AP2. Through the DS, an AP can communicate with its associated STAs and / or unassociated STAs. This embodiment can also be applied to communication between STAs.
[0130] The WLAN network architecture diagram shown in Figure 6 above does not constitute a limitation on the network architecture to which the embodiments of this application can be applied. Therefore, the method provided in the embodiments of this application is applicable to various wireless network architectures or wireless communication systems, such as Wi-Fi systems, 5G communication systems, or various future mobile communication systems, and this application does not limit it.
[0131] Access points, which are the points through which terminal devices (such as mobile phones) access wired (or wireless) networks, are primarily deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters. They can also be deployed outdoors. An access point 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. Specifically, access points can be terminal devices (such as mobile phones) or network devices (such as routers) with Wi-Fi chips, or wireless communication chips, wireless sensors, or wireless communication terminals with access point functionality. Access points can be devices that support the 802.11be standard. Access points can also be devices that support various WLAN standards within the 802.11 family, such as 802.11be next-generation standards.
[0132] The site can be a wireless communication chip, wireless sensor, or wireless communication terminal, and can also be referred to as a user. For example, the site can be a mobile phone supporting Wi-Fi communication, a tablet computer supporting Wi-Fi communication, a set-top box supporting Wi-Fi communication, a smart TV supporting Wi-Fi communication, a smart wearable device supporting Wi-Fi communication, an in-vehicle communication device supporting Wi-Fi communication, and a computer supporting Wi-Fi communication, etc. Optionally, the site can support the 802.11be standard. The site can also support various WLAN standards of the 802.11 family, such as 802.11be next-generation.
[0133] For example, access points and sites can be devices used in the Internet of Vehicles, IoT nodes and sensors in the Internet of Things, smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.
[0134] The AP and STA involved in the embodiments of this application can be APs and STAs that comply with the IEEE 802.11 system standard. An AP is a device deployed in a wireless communication network to provide wireless communication functions for its associated STA. The AP can serve as the hub of the communication system and is typically a network-side product supporting the media access control (MAC) layer and physical (PHY) layer of the 802.11 system standard. Examples include base stations, routers, gateways, repeaters, communication servers, switches, or bridges. The base station can include various forms of macro base stations, micro base stations, repeater stations, etc. For ease of description, the devices mentioned above are collectively referred to as APs. STAs are typically terminal products that support the MAC and PHY layers of the 802.11 system standard, such as mobile phones and laptops.
[0135] The communication system architecture or network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of communication system or network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application can also be applied to similar technical problems.
[0136] Unless otherwise specified in this document, the terms "first device" and "second device" are used to describe the implementing entities.
[0137] "First device" can be a network device, a device with network device functions, or a device that implements network device functions. For example, "first device" is an access network device (e.g., AP or AP MLD), or "first device" can be a module (e.g., chip or circuit) in the access network device, or it can be a module or unit (e.g., CU, DU, or RU), logic module, or software that fully or partially implements the access network device. "First device" can also be a core network device, or a server, such as a cloud server. Alternatively, "first device" can also be a device or apparatus with sensing and / or positioning capabilities, or a device or apparatus capable of performing artificial intelligence tasks. Among these, a device capable of performing artificial intelligence tasks can be called an artificial intelligence task execution device.
[0138] "Second device" and "first device" are different devices or apparatuses. "Second device" can also be a network device, an apparatus with network device functions, or an apparatus that implements network device functions. For example, "second device" is an access network device (e.g., AP or AP MLD), or it can be a module (e.g., chip or circuit) within that access network device, or it can be a module or unit (e.g., CU, DU, or RU), logic module, or software that fully or partially implements that access network device. "Second device" can also be a core network device, or a server, such as a cloud server. Alternatively, "second device" can also be a device or apparatus with sensing and / or positioning capabilities, or a device or apparatus capable of performing artificial intelligence tasks. Among these, a device capable of performing artificial intelligence tasks can be called an artificial intelligence task execution device.
[0139] In some embodiments, the first device (or the second device) may also be a terminal, or a device having terminal functionality, or a device implementing terminal functionality. For example, the first device (or the second device) may be a terminal (such as a Non-AP STA or Non-AP MLD), or a module (e.g., a chip or circuit) in a terminal (e.g., a Non-AP STA or Non-AP MLD), or a module or unit that fully or partially implements a terminal (e.g., a Non-AP STA or Non-AP MLD), or a logic module or software, etc.
[0140] In a Co-TDMA TXOP scenario, the "first device" can be either the recipient or sharer of a TXOP, or the recipient of a TXOP. The "first device" can also be either the recipient or sharer of a TXOP, or the recipient of a TXOP. If the "first device" receives a TXOP and shares it with a second device, then the "first device" is the sharer of the TXOP, and the second device is the recipient of the TXOP. If the "second device" receives a TXOP and shares it with the "first device," then the "second device" is the sharer of the TXOP, and the "first device" is the recipient of the TXOP.
[0141] In this document, the scheme of the embodiments of this application is described using the example of "first device" as the sharer of TXOP and "second device" as the sharer of TXOP. In addition, "first device" can be replaced by "first apparatus" or "first communication apparatus", etc., and "second device" can be replaced by "second apparatus" or "second communication apparatus", etc.
[0142] In this application, "send" and "receive" refer to the direction of information / data / signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, and "send information" can include direct transmission or indirect transmission through other units or modules. "Receive information from YY" can be understood as the source of the information being YY, and "receive information" can include direct reception from YY or indirect reception from YY through other units or modules. Furthermore, "send" can also be understood as the "output" of a chip interface, and "receive" can be understood as the "input" of a chip interface. In other words, "send" or "receive" can occur between nodes / devices, such as a base station and a terminal transmitting or receiving data via an air interface. "Send" or "receive" can also occur within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.
[0143] It should be understood that the names of the messages (or information) in the following processes in this application are merely examples. As communication technology evolves, the names of the messages (or information, etc.) in the following processes may change. However, regardless of how their names change, as long as their meaning is the same as the function or meaning of the messages (or information, etc.) in this application, they all fall within the protection scope of this application. For example, the first information can be replaced with the first frame.
[0144] The solutions of the embodiments of this application will be described below.
[0145] This application provides a communication method that can be applied to, but is not limited to, the network architecture shown in Figure 6. The method can be executed by a first device, a second device, or by modules (e.g., processors, chips, or chip systems) corresponding to the first and second devices, respectively. It can also be executed by logical nodes, logical modules, or software that implement all or part of the functions of the first device and all or part of the functions of the second device, respectively. Furthermore, this application does not specifically limit the structure and number of the execution entities (e.g., the first and second devices) of the method provided in this application, as long as communication can be performed by running a program that records the code of the method provided in this application. For ease of description, the interaction between the first and second devices is used as an example in the following description. The order of steps in the following processes is merely an example; in actual applications, the execution order of steps in each process can be adjusted, and all or part of the following steps can be executed adaptively.
[0146] Referring to Figure 7, the method provided in this application embodiment includes the following steps:
[0147] S701: The first device sends first information to the second device; correspondingly, the second device receives the first information.
[0148] The first piece of information is used to instruct the coordinated execution of preamble punch transmission.
[0149] In this embodiment, preamble puncturing transmission can refer to: during the transmission of Physical Layer Protocol Data Units (PPDUs), puncturing and transmitting data when there is no signal in at least one 20MHz sub-channel within the PPDU bandwidth. Preamble puncturing transmission can also refer to: transmitting data through puncturing channels occupied by other devices to avoid interference.
[0150] In one possible implementation, the first information is a poll frame.
[0151] S702: The second device sends second information to the first device; correspondingly, the first device receives the second information.
[0152] The second information is used to instruct the second device to support the cooperative execution of preamble puncturing transmission. The second information includes the main channel information of the second device. The main channel of the second device and the main channel of the first device do not overlap, but the channels of the second device and the first device overlap.
[0153] For example, the second information could be a response frame.
[0154] In the embodiments of this application, the second device represents one or more devices other than the first device. Therefore, the number of second devices can be one or more. In the case of multiple second devices, the transmission between the first device and each second device can be performed with reference to S701 and S702, which will not be described in detail here.
[0155] In this embodiment, a device channel can refer to a specific frequency range used by the device for sending and receiving data or information. The device's primary channel can refer to the core frequency range used for basic communication, such as control and management frames, which are transmitted via the primary channel. The device's secondary channel (or extended channel) refers to the remaining channels in the bandwidth occupied by the device besides the primary channel, used to improve data transmission rates. For example, a Wi-Fi device uses a total bandwidth of 80MHz, with the primary channel comprising the basic 20MHz, and the remainder referred to as the secondary channel.
[0156] Typically, protocols divide multiple channels according to specific frequency bands (such as the 2.4GHz or 5GHz band of the Wi-Fi protocol) to avoid interference between devices. Different channels correspond to different center frequencies, and each channel occupies a frequency range, which can be referred to as a frequency band. Therefore, in the embodiments of this application, the "channel" used by the device for transmission can also be referred to as the "frequency band" used by the device for transmission. Correspondingly, the device's "primary channel" can be referred to as the device's "primary frequency band," and the device's "secondary channel" can be referred to as the device's "secondary frequency band."
[0157] Furthermore, the device (such as the first device or the second device) may have one or more channels, and each channel may refer to a sub-channel with a preset size (e.g., 20MHz) as the granularity or unit. The device (such as the first device or the second device) may also have one or more main channels, and the size of the main channel may be equal to the channel size.
[0158] S703: The first device determines the preamble punching information based on the main channel information of the second device.
[0159] In one possible implementation, when executing S703, the following steps are included: the first device determines the preamble punching information based on the channel information and main channel information of the first device and the main channel information of the second device.
[0160] In one possible implementation, the first device determines the preamble puncture information based on the channel information and main channel information of the first device and the main channel information of the second device (or when executing S703), including: the first device determines the preamble puncture information based on at least one of the channel information and main channel information of the first device, the channel information and main channel information of the second device; wherein the channel information of the second device is carried in the second information.
[0161] In one possible implementation, the second information also includes transmission requirement information of the second device, which includes, but is not limited to, at least one of the following:
[0162] (1) The amount of data cached by the second device.
[0163] (2) Transmission rate of the second device; The transmission rate of the second device may refer to the rate at which the second device transmits messages (or data) on its own operating frequency band.
[0164] (3) Transmission bandwidth of the second device; the transmission bandwidth of the second device may refer to the transmission frequency band occupied by the second device for transmitting data.
[0165] In one possible implementation, the first device determines the preamble puncturing information based on the channel information and main channel information of the first device, and the channel information and main channel information of the second device (or when executing S703), including: the first device determines the preamble puncturing information based on at least one of the channel information and main channel information of the first device, the channel information and main channel information of the second device, the transmission requirement information of the first device, and the transmission requirement information of the second device.
[0166] In one possible implementation, the aforementioned preamble punch information includes at least one of the following:
[0167] (1) The punching information of the preamble of the first device.
[0168] For example, the preamble punching information of the first device includes the punching channel information and / or the punching time information of the first device.
[0169] (2) The punching information of the preamble of the second device.
[0170] For example, the preamble punching information of the second device includes the punching channel information and / or the punching time information of the second device.
[0171] In one possible implementation, the method of this application embodiment further includes: the first device sending the preamble punching information to the second device; correspondingly, the second device receiving the preamble punching information. Optionally, this implementation can be performed after S703.
[0172] In one possible implementation, the method of this application embodiment further includes: a first device sending third information to a third device associated with the first device, the third information including preamble punching information of the first device; correspondingly, the third device receiving the preamble punching information of the first device. Optionally, this implementation can be performed after S703. In this application embodiment, if the first device is an access point site, the third device may refer to one or more non-access point sites (e.g., STA or STA MLD) or terminal devices associated with the first device.
[0173] In one possible implementation, the method of this application embodiment further includes: the second device sending fourth information to a fourth device associated with the second device, the fourth information including the preamble punching information of the second device; correspondingly, the fourth device receiving the preamble punching information of the second device. Optionally, this implementation can be performed after the second device receives the preamble punching information. In this application embodiment, if the second device is an access point site, the fourth device may refer to one or more non-access point sites (e.g., STA or STA MLD) or terminal devices associated with the second device.
[0174] In one possible implementation, the unpunctured channels of the first device and the second device do not overlap. This implementation effectively avoids channel conflicts that may occur during concurrent transmission of preambles by the first and second devices in coordinated operation.
[0175] In another possible implementation, the unpunctured channels of the first device and the second device partially overlap, and the unpunctured channels of the first device do not include the main channel of the second device, and the unpunctured channels of the second device do not include the main channel of the first device.
[0176] In the above, the unpunctured channel of the first device can refer to the channel of the first device other than the punctured channel of the first device determined by the cooperation, and the unpunctured channel of the second device can refer to the channel of the second device other than the punctured channel of the second device determined by the cooperation.
[0177] In response to the situation where the un-punctured channels of the first device and the second device partially overlap, and the un-punctured channels of the first device do not include the main channel of the second device, and the un-punctured channels of the second device do not include the main channel of the first device, in one possible implementation, the method of this application embodiment further includes: the first device determining the channel occupied by the second device; the un-punctured channels of the first device and the channel occupied by the second device overlap; and the first device punching a hole in the un-punctured channel of the first device according to the channel occupied by the second device.
[0178] For example, the second device sends a message first, the first device receives the message from the second device and determines that the second device uses channel 1 to send the message. Channel 1 is included in the un-punctured channel of the first device. Based on this, the first device determines to puncture channel 1, that is, the first device does not use channel 1 when sending the message.
[0179] In one possible implementation, the method of this application embodiment further includes: a second device determining the channel occupied by the first device; the un-punctured channel of the second device overlapping with the channel occupied by the first device; and the second device puncturing the un-punctured channel of the second device according to the channel occupied by the first device. Optionally, this implementation can be performed after the second device receives the preamble puncturing information.
[0180] For example, the first device sends a message first, the second device receives the message from the first device and determines that the first device uses channel 2 to send the message. Channel 2 is included in the un-punctured channel of the second device. Based on this, the second device determines to puncture channel 2, that is, the second device does not use channel 2 when sending the message.
[0181] In one possible implementation, the channels of the first device and the second device completely overlap, or the channels of the first device and the second device partially overlap.
[0182] In one possible implementation, the preamble punching information is carried in the initial control frame (ICF), which also includes the address information and / or identification information of the second device. For example, the address information of the second device is its MAC address, and the identification information is its association identifier (AID). With this implementation, the first device can accurately send the preamble punching information to the corresponding second device.
[0183] In S701 to S703 above, the interaction and negotiation between the first device and the second device are used as examples to illustrate the solution of the embodiments of this application. In actual practice, there may be one or more second devices. When there are multiple second devices, the first device can negotiate with multiple second devices to determine the preamble punching information, which can be implemented with reference to the above steps.
[0184] In the above method, the first device sends first information to the second device, which instructs for coordinated execution of preamble puncturing transmission. The first device then receives second information from the second device, which instructs the second device to support coordinated preamble puncturing transmission. The second information includes the second device's main channel information. While the second device's main channel and the first device's main channel do not overlap, their channels do overlap. Based on this, the first device determines the preamble puncturing information according to the second device's main channel information. Therefore, the first device can cooperate with the second device in advance to determine the preamble puncturing information, avoiding channel conflicts during concurrent transmission of preamble puncturing. This improves multi-device concurrency capabilities while effectively preventing the waste of spectrum resources, thereby increasing spectrum resource utilization.
[0185] The following section uses the scheme shown in Figure 7 as an example applied to a WLAN network architecture, and provides a detailed introduction to the scheme shown in Figure 7 through several specific implementation methods.
[0186] Implementation Method 1:
[0187] In Embodiment 1, based on the scheme shown in FIG7 above, taking AP1 as the first device and AP2 as the second device as an example, the scheme of this application embodiment will be described in detail. Referring to FIG8, the method flow of Embodiment 1 includes the following steps:
[0188] S801: AP1 sends a poll frame to AP2 (i.e., an example of the first information in the scheme shown in Figure 7 above); correspondingly, AP2 receives the poll frame.
[0189] The polling frame is used to instruct the coordinated execution of preamble puncturing transmission (or coordinated execution of frequency band puncturing transmission).
[0190] Prior to S801, AP1 could acquire the TXOP through channel contention. How AP1 acquires the TXOP through channel contention can be found in current related technologies and will not be detailed here. Therefore, in the following text, AP1 acts as the sharer of the TXOP. AP1 can share the TXOP with other APs, such as AP2, in which case AP2 becomes the recipient of the shared TXOP.
[0191] S802: AP2 sends a response frame to AP1 (i.e., an example of the second information in the scheme shown in Figure 7 above); correspondingly, AP1 receives the response frame.
[0192] The response frame is used to indicate whether AP2 supports or accepts cooperative preamble punch transmission.
[0193] For example, the response frame includes 1 bit of information. If the value of the 1 bit is 0, it indicates that cooperative preamble puncturing transmission is not supported or accepted; if the value of the 1 bit is 1, it indicates that cooperative preamble puncturing transmission is supported or accepted.
[0194] If AP2 supports or accepts cooperative preamble punch transmission, the response frame includes AP2's operating frequency band information and main frequency band information. AP2's operating frequency band information is used to indicate AP2's operating frequency band, and AP2's main frequency band information is used to indicate AP2's main frequency band.
[0195] In the embodiments of this application, the operating frequency band of an AP (such as AP1 or AP2) may refer to at least one frequency band allocated to the AP (such as AP1 or AP2) or at least one frequency band supported by the AP (such as AP1 or AP2).
[0196] Based on this, the operating frequency band of AP1 includes the primary frequency band of AP1, and optionally, at least one secondary frequency band of AP1. The operating frequency band of AP2 includes the primary frequency band of AP2, and optionally, at least one secondary frequency band of AP2. The primary frequency bands of AP1 and AP2 do not overlap, but at least one secondary frequency band of AP1 and at least one secondary frequency band of AP2 overlap.
[0197] In this embodiment of the application, each frequency band of the AP is 20MHz as an example, so each frequency band of the AP can also be referred to as a sub-channel.
[0198] The above S801 and S802 are examples of AP2 being the recipient of AP1's TXOP. In practice, AP1 can also share the TXOP with one or more other APs. For example, AP1 can also share the TXOP with AP3. Similarly, after receiving the polling frame from AP1, AP3 can send a response frame to AP1 following the steps of AP2. AP3's response frame includes AP3's operating frequency band information and primary frequency band information. For details, please refer to the relevant introduction of AP2's operating frequency band information and primary frequency band information above, which will not be elaborated here.
[0199] S803: AP1 sends an ICF to AP2; correspondingly, AP2 receives the ICF.
[0200] In one possible implementation, the method further includes: AP1 determining the preamble puncturing information of AP1 (i.e., an example of the preamble puncturing information of the first device in the scheme shown in Figure 7) and the preamble puncturing information of AP2 (i.e., an example of the preamble puncturing information of the second device in the scheme shown in Figure 7) based on the operating frequency band of AP1 (including the main frequency band of AP1) and the operating frequency band of AP2 (including the main frequency band of AP2). Optionally, this implementation is performed after S802 and before S803.
[0201] In the above, the ICF includes the preamble puncturing information of AP2, which includes the puncturing frequency band information and the puncturing time information of AP2. Optionally, the ICF may also include the preamble puncturing information of AP1, which includes the puncturing frequency band information and the puncturing time information of AP1.
[0202] In one possible implementation, the punched frequency band information of AP2 (or AP1) is indicated in the form of a bitmap.
[0203] For example, AP1 operates in the following frequency bands: Band 1 (secondary band 20MHz), Band 2 (secondary band 20MHz), Band 3 (primary band 20MHz), and Band 4 (secondary band 20MHz). AP2 operates in the following frequency bands: Band 1 (secondary band 20MHz), Band 2 (primary band 20MHz), Band 3 (secondary band 20MHz), and Band 4 (secondary band 20MHz). The terms "secondary frequency" and "primary frequency" refer to the individual APs. The four operating frequency bands of AP1 and AP2 completely overlap (or are the same), but the primary frequency bands of AP1 and AP2 are different. As shown in Figure 9A, if AP1, based on its operating frequency bands (including its primary band) and AP2's operating frequency bands (including its primary band), collaboratively determines that AP1's punched frequency bands are Band 1 and Band 2, and AP2's punched frequency bands are Band 3 and Band 4...
[0204] Based on this, for example, AP2 uses 4 bits to indicate the punched frequency band information. The value of these 4 bits is set to 1100. Each bit corresponds to one frequency band of AP2. Here, 0 indicates that the frequency band is a punched frequency band (that is, AP2 will not use the frequency band for transmission), and 1 indicates that the frequency band is a non-punched frequency band (that is, AP2 can use the frequency band for transmission).
[0205] For example, AP1 operates in frequency bands 1 (secondary band 20MHz), 2 (secondary band 20MHz), 3 (primary band 20MHz), and 4 (secondary band 20MHz). AP2 operates in frequency bands 1 (secondary band 20MHz), 2 (primary band 20MHz), 3 (secondary band 20MHz), and 4 (secondary band 20MHz). There is partial overlap (or same) between the operating frequency bands of AP1 and AP2. For instance, AP1's frequency bands 1 and 2 correspond one-to-one with AP2's frequency bands 3 and 4. As shown in Figure 9B, AP1 negotiates and determines the punched frequency bands for each AP based on the partially overlapping frequency bands of AP1 (including AP1's primary band) and AP2 (including AP2's primary band). If AP1 negotiates and determines that AP1's punched frequency band is frequency band 1, and AP2's punched frequency band is frequency band 4...
[0206] Based on this, for example, the punched frequency band information of AP2 is indicated by 4 bits, and the value of these 4 bits is set to 1110. Each bit corresponds to one frequency band of AP2. Among them, 0 indicates that the frequency band is a punched frequency band (that is, AP2 will not use the frequency band), and 1 indicates that the frequency band is a non-punched frequency band (that is, AP2 can use the frequency band).
[0207] In Figures 9A and 9B, the collaboratively determined "punched frequency bands" are represented by dashed lines, and the collaboratively determined "non-punched frequency bands" are represented by solid lines.
[0208] In this embodiment, AP1 may also indicate its punctured frequency band and / or AP2's punctured frequency band to AP2 in other ways, without limitation. For example, the punctured frequency band information of AP2 may be an identifier or index of AP2's punctured frequency band. Furthermore, AP1 may also send the corresponding unpunctured frequency band information to the shared users of TXOP (such as AP2 and AP3), so that the shared users of TXOP (such as AP2 and AP3) can also determine the punctured frequency band information based on the unpunctured frequency band information. For example, AP1 sends the identifier or index of AP2's unpunctured frequency band to AP2, and AP2 can determine AP2's punctured frequency band from AP2's operating frequency band based on the identifier or index of AP2's unpunctured frequency band.
[0209] In the embodiments of this application, "punch band" can be understood as the frequency band that needs to be punched, which is determined through negotiation.
[0210] In the above, the puncturing time information of AP1 is used to indicate the time when AP1 collaboratively performs preamble puncturing transmission, and the puncturing time information of AP2 is used to indicate the time when AP2 collaboratively performs preamble puncturing transmission.
[0211] The time for AP1 to collaboratively perform preamble puncturing transmission and the time for AP2 to collaboratively perform preamble puncturing transmission can be the same, meaning multiple APs (including AP1 and AP2) can collaboratively perform preamble puncturing transmission within the same preset time period. Alternatively, the time for AP1 to collaboratively perform preamble puncturing transmission and the time for AP2 to collaboratively perform preamble puncturing transmission can be different, meaning multiple APs (including AP1 and AP2) can collaboratively perform preamble puncturing transmission within different preset time periods, but these different preset time periods overlap.
[0212] In this first implementation, AP2 is used as an example to describe the shared TXOP. In reality, the shared TXOP is not limited to AP2, but may also include other APs, such as AP3. Then, AP1 can negotiate and determine the preamble punch information of AP1, AP2 and AP3 based on the operating frequency band of AP1 (including the main frequency band of AP1), the operating frequency band of AP2 (including the main frequency band of AP2) and the operating frequency band of AP3 (including the main frequency band of AP3).
[0213] Based on this, the ICF sent by AP1 also includes the preamble puncturing information of AP3. The preamble puncturing information of AP3 includes the puncturing frequency band information and puncturing time information of AP3. The specific puncturing frequency band information and puncturing time information of AP3 can be designed and implemented with reference to the puncturing frequency band information and puncturing time information of AP2 mentioned above.
[0214] For example, the operating frequency bands of AP1 are: band 1 (secondary band 20MHz), band 2 (secondary band 20MHz), band 3 (secondary band 20MHz), band 4 (secondary band 20MHz), band 5 (primary band 20MHz), and band 6 (secondary band 20MHz).
[0215] The operating frequency bands of AP2 are: band 1 (secondary band 20MHz), band 2 (secondary band 20MHz), band 3 (secondary band 20MHz), band 4 (main band 20MHz), band 5 (secondary band 20MHz), and band 6 (secondary band 20MHz).
[0216] The AP3 operates in the following frequency bands: Band 1 (secondary band 20MHz), Band 2 (secondary band 20MHz), Band 3 (secondary band 20MHz), Band 4 (secondary band 20MHz), Band 5 (secondary band 20MHz), and Band 6 (main band 20MHz).
[0217] The operating frequency bands of AP1, AP2, and AP3 completely overlap.
[0218] Referring to Figure 9C, AP1 negotiates and determines the punched frequency bands of AP1 as band 2, band 3, band 4 and band 6, the punched frequency bands of AP2 as band 1, band 3, band 5 and band 6, and the punched frequency bands of AP3 as band 1, band 2, band 4 and band 5, based on the operating frequency bands of AP1 (including the main frequency band of AP1), AP2 (including the main frequency band of AP2), and AP3 (including the main frequency band of AP3).
[0219] As can be seen from the above, the un-punched frequency bands of AP1 are band 1 and band 5 (the main frequency band of AP1), the un-punched frequency bands of AP2 are band 2 and band 4 (the main frequency band of AP2), and the un-punched frequency bands of AP3 are band 3 and band 6 (the main frequency band of AP3). The un-punched frequency bands of AP1, AP2, and AP3 do not overlap.
[0220] In this first implementation, AP1 can send the preamble punch information of each AP to the shared users of TXOP (such as AP2 and AP3) using unicast, multicast, or broadcast methods. There are no restrictions here, and the design can be made according to the actual situation or requirements.
[0221] S804: AP1 sends beacon frame 1 (an example of third information in the scheme shown in Figure 7) to STA1 associated with AP1 (i.e., an example of the third device in the scheme shown in Figure 7 above); accordingly, STA1 receives the beacon frame 1.
[0222] In this embodiment of the application, AP1 may be associated with one or more STA1s. AP1 may send beacon frame 1 to one or more of its associated STA1s via broadcast (or unicast or multicast).
[0223] In the above, beacon frame 1 includes the punching frequency band information of AP1 and the punching time information of AP1 (or effective time information 1).
[0224] Since the operating frequency band of AP1 can also be the frequency band used for transmission by its associated STA1, the punched frequency band information of AP1 is also applicable to STA1.
[0225] If beacon frame 1 includes AP1's puncturing frequency band information and AP1's puncturing time information, AP1's puncturing time information is used to indicate the time when AP1 collaboratively performs preamble puncturing transmission.
[0226] For example, the punching time information of AP1 includes the start time and end time of punching, or the start time and duration of punching, or the end time and duration of punching.
[0227] If beacon frame 1 includes AP1's punched frequency band information and effective time information 1, the effective time information 1 is used to indicate the effective time period corresponding to AP1's punched frequency band information.
[0228] Example 1: Effective time information 1 is used to indicate that the punched frequency band information of AP1 is valid after STA1 receives beacon frame 1 and before STA1 receives the next beacon frame of AP1.
[0229] Example 2: Effective time information 1 includes the start time and duration of effectiveness, or the start time and end time of effectiveness, or the end time and duration of effectiveness of AP1's punched frequency band information.
[0230] S805: AP2 sends beacon frame 2 (an example of the fourth information in the scheme shown in Figure 7) to STA2 associated with AP2 (i.e., the fourth device in the scheme shown in Figure 7 above); accordingly, STA2 receives the beacon frame 2.
[0231] In this embodiment of the application, AP2 may be associated with one or more STA2s. AP2 may send beacon frames 2 to one or more of its associated STA2s via broadcast (or unicast or multicast).
[0232] In the above, beacon frame 2 includes AP2's punching frequency band information and AP2's punching time information (or effective time information 2).
[0233] Since the operating frequency band of AP2 can also be the same frequency band used for transmission by its associated STA2, the punched frequency band information of AP2 is also applicable to STA2.
[0234] If beacon frame 2 includes AP2's puncturing frequency band information and AP2's puncturing time information, AP2's puncturing time information is used to indicate the time when AP2 collaboratively performs preamble puncturing transmission.
[0235] For example, the punching time information of AP2 includes the start time and end time of punching, or the start time and duration of punching, or the end time and duration of punching.
[0236] If beacon frame 2 includes AP2's punched frequency band information and effective time information 2, the effective time information 2 is used to indicate the effective time period of AP2's punched frequency band information.
[0237] Example 1: Effective time information 2 is used to indicate that the punched frequency band information of AP2 is valid after STA2 receives beacon frame 1 and before STA2 receives the next beacon frame of AP2.
[0238] Example 2: Effective time information 2 includes the start time and duration of the effective period, or the start time and end time of the effective period, or the end time and duration of the effective period.
[0239] The above S804 and S805 may be executed synchronously or asynchronously, and there is no restriction on the order of execution. The execution order can be adjusted according to the actual situation or needs.
[0240] In the above, AP2 is used as an example to illustrate the sharing of TXOP. In reality, the sharing of TXOP is not limited to AP2, but may also include other APs, such as AP3, AP4, etc. After obtaining its own preamble punching information, each of these APs can refer to the steps of AP2 to send the corresponding punching frequency band information and punching time information to the corresponding associated STA.
[0241] S806: AP1 and / or its associated STA1 perform static punching and transmission within the corresponding punching time.
[0242] That is, in downlink transmission, AP1 performs static puncturing of the puncturing frequency band according to AP1's puncturing frequency band information within the corresponding time period for coordinated execution of preamble puncturing transmission, and sends a downlink message to STA1; correspondingly, STA1 receives the downlink message according to AP1's puncturing frequency band information and AP1's puncturing time information (or effective time 1). In uplink transmission, STA1 performs static puncturing of the puncturing frequency band according to AP1's puncturing time information (or effective time 1) within the corresponding time period, and sends an uplink message to AP1; correspondingly, AP1 receives the uplink message according to AP1's puncturing frequency band information and AP1's puncturing time information (or effective time 1).
[0243] In this first implementation, the punching frequency band determined through prior negotiation can be referred to as the "static punching frequency band". The act of AP1 (or STA1) punching in the pre-negotiated punching frequency band can be referred to as "static punching".
[0244] S807: AP2 and / or its associated STA2 perform static punching and transmission within the corresponding punching time.
[0245] In downlink transmission, AP2 performs static puncturing of the puncturing frequency band according to its puncturing frequency band information within the corresponding time period for coordinated preamble puncturing transmission, and sends a downlink message to STA2. Correspondingly, STA2 receives the downlink message based on AP2's puncturing frequency band information and AP2's puncturing time information (or effective time 2). In uplink transmission, STA2 performs static puncturing of the puncturing frequency band according to AP2's puncturing time information (or effective time 2) within the corresponding time period, and sends an uplink message to AP2. Correspondingly, AP2 receives the uplink message based on AP2's puncturing frequency band information and AP2's puncturing time information (or effective time 2).
[0246] In this first implementation, the behavior of AP2 (or STA2) punching holes in the pre-negotiated punching frequency band can be referred to as "static punching".
[0247] For example, based on S801 to S807 above, Figure 10A shows a schematic diagram of the interaction between AP1, the sharer of TXOP, and AP2, the sharer of TXOP. Referring to Figure 10A, AP1 sends a polling frame, which AP2 receives. This polling frame is used to request cooperative execution of preamble puncturing transmission (see the description in S801 above). Then, AP2 sends a response frame to AP1, which AP1 receives. This response frame indicates whether AP2 supports or accepts cooperative execution of preamble puncturing transmission. Optionally, the response frame also includes AP2's operating frequency band information and main frequency band information (see the description in S802 above). AP1 negotiates and determines the puncturing frequency band for each AP based on its operating frequency band (including AP1's main frequency band) and AP2's operating frequency band (including AP2's main frequency band). After this, AP1 sends an ICF, which AP2 receives. The ICF includes AP2's puncturing frequency band information and puncturing time information (see the description in S803 above); further, AP1 can send beacon frame 1 to its associated STA1, and the corresponding STA1 receives beacon frame 1, which includes AP1's puncturing frequency band information and puncturing time information (or effective time 1) (see the description in S804 above). Similarly, AP2 can also send beacon frame 2 to its associated STA2, which includes AP2's puncturing frequency band information and puncturing time information (or effective time 2) (see the description in S805 above); during the cooperative execution of puncturing transmission time, AP1 and its associated STA1 puncture the puncturing frequency band according to AP1's puncturing frequency band information and perform transmission (see the description in S806 above), and AP2 and its associated STA2 puncture the puncturing frequency band according to AP2's puncturing frequency band information and perform transmission (see the description in S807 above).
[0248] In Figure 10A, during the preamble puncturing transmission time of multiple APs (including AP1 and AP2), AP1 and AP2 each perform two transmissions. AP1 and AP2 perform static puncturing and synchronous concurrent transmission, meaning that AP1 and AP2 perform synchronous concurrent transmission in each transmission. For any given transmission, considering the frequency bands of AP1 and AP2 after puncturing, the original operating frequency bands of AP1 and AP2 are the same. Specifically, frequency bands 1 and 2 of AP1 are punctured (i.e., AP1 does not use frequency bands 1 and 2), while frequency bands 3 and 4 of AP1 are not punctured (i.e., AP1 uses frequency bands 3 and 4). Similarly, frequency bands 1 and 2 of AP2 are not punctured (i.e., AP2 uses frequency bands 1 and 2), while frequency bands 3 and 4 of AP2 are punctured (i.e., AP2 does not use frequency bands 3 and 4). Therefore, the frequency bands of AP1 and AP2 after the puncturing process do not overlap, which can effectively avoid conflicts when AP1 and AP2 transmit concurrently.
[0249] Unlike Figure 10A, Figure 10B shows that during the preamble puncturing transmission time of multiple APs (including AP1 and AP2), AP1 and AP2 each perform two transmissions. AP1 and AP2 perform static puncturing and asynchronous concurrent transmission, meaning that in each transmission, AP1 and AP2 do not transmit synchronously but with a certain time difference. Referring to Figure 10B, for the first transmission, AP1's transmission time is slightly earlier than AP2's transmission time; for the second transmission, AP2's transmission time is slightly earlier than AP1's transmission time. Similarly, since the frequency bands of AP1 and AP2 after puncturing do not overlap, conflicts can be effectively avoided when AP1 and AP2 transmit concurrently in this scenario.
[0250] In the above content, AP2 is used as an example to describe the shared TXOP in detail. In actual practice, the shared TXOP is not limited to AP2, but may also include other APs, such as AP3, AP4, etc. Any AP can refer to the steps and methods corresponding to AP2 to implement the concurrent transmission of collaborative punching. They will not be listed one by one here.
[0251] In this first implementation, AP1, the sharer of the TXOP, can negotiate and determine the preamble puncturing information for each AP based on the operating frequency band of the sharer and the operating frequency band of the shared AP (such as AP2). The preamble puncturing information includes puncturing frequency band information and puncturing time information. AP1 then sends the negotiated preamble puncturing information of each AP to the corresponding AP, so that each AP and its associated STA can collaboratively perform preamble puncturing transmission according to the negotiated puncturing frequency band information and puncturing time information. In this way, when performing concurrent transmission, it can effectively avoid conflicts between multiple APs and the resulting waste of spectrum resources, thereby improving the utilization rate of spectrum resources.
[0252] Implementation Method Two:
[0253] Compared to Implementation Method 1, the main difference in Implementation Method 2 is that during the multi-AP collaborative preamble puncturing transmission time, when APs perform asynchronous concurrent transmission, each AP and its associated STA can also perform dynamic puncturing. Referring to Figure 11, the method flow of Implementation Method 2 includes the following steps:
[0254] S1101: AP1 sends a polling frame to AP2; correspondingly, AP2 receives the polling frame.
[0255] S1102: AP2 sends a response frame to AP1; correspondingly, AP1 receives the response frame.
[0256] S1103: AP1 sends an ICF to AP2; correspondingly, AP2 receives the ICF.
[0257] S1104: AP1 sends beacon frame 1 to STA1 associated with AP1; correspondingly, STA1 receives beacon frame 1.
[0258] S1105: AP2 sends beacon frame 2 to STA2 associated with AP2; correspondingly, STA2 receives beacon frame 2.
[0259] The specific implementation methods of S1101 to S1105 can be referred to one by one with the relevant descriptions of S801 to S805 in the first embodiment above, and will not be repeated here.
[0260] S1106a: AP1 and / or its associated STA1 perform static punching and transmission within the corresponding punching time.
[0261] The specific implementation of S1106a can be referred to the relevant description in S806 of the above-mentioned implementation method, and will not be described in detail here.
[0262] S1106b: AP1 and / or associated STA1 perform dynamic punching and transmission within the corresponding punching time.
[0263] In one possible implementation, during the preamble puncturing transmission time when multiple APs (including AP1 and AP2) are cooperating, AP1 detects the frequency band where other APs and / or STAs send messages. Then, AP1 punctures the frequency band in its unpunctured frequency band that overlaps with the frequency band where the message is located, based on the detected frequency band.
[0264] For example, AP1 operates in four frequency bands: band 1 (secondary band 20MHz), band 2 (secondary band 20MHz), band 3 (primary band 20MHz), and band 4 (secondary band 20MHz). AP2 operates in four frequency bands: band 1 (secondary band 20MHz), band 2 (primary band 20MHz), band 3 (secondary band 20MHz), and band 4 (secondary band 20MHz). The four frequency bands of AP1 and AP2 completely overlap.
[0265] The punch-hole frequency bands for AP1 and AP2 are determined through negotiation as follows:
[0266] Referring to Figure 12A, AP1 negotiates and determines that its punched frequency band (i.e., static punched frequency band) is frequency band 2, and determines that AP2's punched frequency band (i.e., static punched frequency band) is frequency band 3. It can be seen that the punched frequency bands of AP1 and AP2 still have some overlap; that is, AP1's frequency band 1 (sub-band 20MHz) overlaps with AP2's frequency band 1 (sub-band 20MHz), and AP2's frequency band 4 (sub-band 20MHz) overlaps with AP2's frequency band 4 (sub-band 20MHz).
[0267] Based on the collaborative determination of the frequency bands of AP1 and AP2 after puncturing, as shown in Figure 12A, AP1 is further dynamically punctured as follows:
[0268] For example, referring to Figure 12B, if AP2 transmits first and AP1 transmits later, AP2 will first use frequency bands 1, 2, and 4 to send reports. Correspondingly, AP1 will receive AP2's reports on frequency band 1 and frequency band 4. Based on this, AP1 can confirm that frequency bands 1 and 4 are already occupied. Therefore, AP1 will dynamically puncture frequency bands 1 and 4. That is, during transmission, AP1 will only use frequency band 3 (main frequency band 20MHz) to send reports, and will not use the statically punctured frequency band 2 to send messages, nor will it use the dynamically punctured frequency bands 1 and 4 to send reports.
[0269] The dynamic punching transmission method of STA1 associated with AP1 can be referred to the above implementation of the dynamic punching transmission method of AP1, and will not be described in detail here.
[0270] The above S1106a and S1106b can be executed synchronously.
[0271] S1107a: AP2 and / or its associated STA2 perform static punching and transmission according to the punching frequency band information of AP2 during the corresponding punching time.
[0272] The specific implementation of S1107a can be referred to the description in S807 of the above-mentioned implementation method, and will not be described in detail here.
[0273] S1107b: AP2 and / or associated STA2 perform dynamic punching and transmission within the corresponding punching time.
[0274] In one possible implementation, AP2 (or associated STA2) detects the frequency band in which other APs and / or STAs send messages, and then AP2 (or associated STA2) punches the frequency bands in its unpunched frequency bands that overlap with the frequency band in which the report is located, based on the frequency band in which the detected message is located.
[0275] Based on the collaborative determination of the frequency bands of AP1 and AP2 after puncturing, as shown in Figure 12A, AP2 is further dynamically punctured as follows:
[0276] For example, referring to Figure 12C, if AP1 transmits first and AP2 transmits later, AP1 will first use frequency bands 1, 3, and 4 to send reports. Correspondingly, AP2 can receive AP1's reports on frequency band 1 and frequency band 4. Based on this, AP2 can confirm that frequency bands 1 and 4 are already occupied. Therefore, AP2 performs dynamic puncturing on frequency bands 1 and 4. That is, when sending messages, AP2 only uses frequency band 2 (main frequency band 20MHz) to send reports, and does not use the statically punctured frequency band 3 to send messages, nor does it use the dynamically punctured frequency bands 1 and 4 to send reports.
[0277] The dynamic punching transmission method for AP2 associated with STA2 can be referred to the above implementation of the dynamic punching transmission method for AP2, and will not be detailed here.
[0278] The above S1107a and S1107b can be executed simultaneously.
[0279] For example, based on the method steps shown in Embodiment 2 above, Figure 13 illustrates the interaction diagram of concurrent transmission of static puncturing and dynamic puncturing. Referring to Figure 13, AP1 sends a polling frame, and AP2 receives the polling frame accordingly. This polling frame is used to indicate cooperative execution of preamble puncturing transmission (see the relevant description in S1101 above). Then, AP2 sends a response frame to AP1, and AP1 receives the response frame accordingly. This response frame is used to indicate whether AP2 supports or accepts cooperative execution of preamble puncturing transmission. The response frame may also include AP2's operating frequency band information and main frequency band information (see the relevant description in S1102 above). AP1 negotiates and determines the puncturing frequency band information of each AP based on AP1's operating frequency band (including AP1's main frequency band) and AP2's operating frequency band (including AP2's main frequency band). After this, AP1 sends an ICF, and AP2 receives the ICF accordingly. The ICF includes AP2's preamble puncturing information (see the relevant description in S1103 above). Further, AP... AP1 can send beacon frame 1 to its associated STA1, and the corresponding STA1 receives beacon frame 1. Beacon frame 1 includes AP1's puncturing frequency band information and puncturing time information (or effective time information 1) (see the relevant description in S1104 above). Similarly, AP2 can also send beacon frame 2 to its associated STA2. Beacon frame 2 includes AP2's puncturing frequency band information and puncturing time information (or effective time information 2) (see the relevant description in S1105 above). During the cooperative execution of preamble puncturing transmission time, AP1 and its associated STA1 perform static puncturing and dynamic puncturing transmission according to AP1's puncturing frequency band information (see the relevant descriptions in S1106a and S1106b above), and AP2 and its associated STA2 perform static puncturing and dynamic puncturing transmission according to AP2's puncturing frequency band information (see the relevant descriptions in S1107a and S1107b above).
[0280] In the above content, AP2 is used as an example to describe the shared TXOP in detail. In actual practice, the shared TXOP is not limited to AP2. There may be other APs, such as AP3, AP4, etc. Any AP can refer to the steps and methods corresponding to AP2 to implement the concurrent transmission of static punching and dynamic punching. They will not be listed one by one here.
[0281] Compared to Implementation Method 1, in Implementation Method 2, the sharing party AP1 and the shared party (such as AP2) of TXOP can not only negotiate and determine the punching frequency band information, but also, in asynchronous concurrent transmission scenarios, each AP and / or associated STA can not only perform static punching transmission according to the negotiated punching frequency band information during the collaborative execution of punching transmission, but also perform dynamic punching transmission according to the actual transmission situation (such as dynamically punching the corresponding overlapping frequency band according to the frequency band where the packets sent by other APs and / or STAs are detected). This allows each AP (or STA) to flexibly occupy the secondary frequency band to send packets without conflict.
[0282] In the above-described embodiments one and two, AP1, in collaboration with at least one shared AP of TXOP (including AP2 mentioned above), determines that the puncturing frequency band information of each AP can be continuously used or effective during the multi-AP collaborative execution of preamble puncturing transmission. During this time, each AP and its associated STA can perform one or more transmissions (interactions).
[0283] Implementation Method 3:
[0284] Compared to the above implementation methods one and two, the main difference of implementation method three is that AP1 determines the preamble puncturing information of each AP based on the situation where AP1, the sharer of TXOP, and the shared party (such as AP2) jointly perform a preamble puncturing transmission (or any preamble puncturing transmission) to meet the transmission requirements.
[0285] Referring to Figure 14, the method flow of Implementation Method 3 includes the following steps:
[0286] S1401: AP1 sends a polling frame to AP2 (i.e., an example of the first information in the scheme shown in Figure 7 above); correspondingly, AP2 receives the polling frame.
[0287] The polling frame is used to instruct the coordinated execution of preamble punch transmission.
[0288] S1401 can be referred to in the relevant introduction in S801 above, and will not be repeated here.
[0289] S1402: AP2 sends a response frame to AP1 (i.e., an example of the second information in the scheme shown in Figure 7 above); correspondingly, AP1 receives the response frame.
[0290] This response frame indicates whether AP2 supports or accepts cooperative preamble puncturing transmission. If AP2 supports or accepts cooperative preamble puncturing transmission, the response frame includes AP2's operating frequency band information and AP2's primary frequency band information.
[0291] The operating frequency band of AP1 includes the primary frequency band of AP1, and optionally, at least one secondary frequency band of AP1. The operating frequency band of AP2 includes the primary frequency band of AP2, and optionally, at least one secondary frequency band of AP2. The primary frequency bands of AP1 and AP2 do not overlap, but at least one secondary frequency band of AP1 and at least one secondary frequency band of AP2 overlap. In this embodiment, an example is taken where each frequency band of the AP is 20MHz.
[0292] In one possible implementation, the response frame also includes AP2's transmission requirement information. For example, AP2's transmission requirement information may include at least one of the following: the amount of data buffered by AP2, AP2's transmission rate on its own operating frequency band, or AP2's transmission bandwidth.
[0293] In another possible implementation, prior to S1401, AP1 requests AP2 to report its transmission request information, and then AP2 sends its transmission request information to AP1.
[0294] For example, before S1401, AP1 sends a capability request message to AP2. After receiving the capability request message, AP2 sends its capability information to AP1. AP2's capability information includes at least one of the following: the amount of data buffered by AP2, the transmission rate of AP2 on its own operating frequency band, or the transmission bandwidth of AP2.
[0295] In one possible implementation, the method further includes: AP1 determining the preamble puncturing information of AP1 and AP2 based on the operating frequency band of AP1 (including the main frequency band of AP1), the operating frequency band of AP2 (including the main frequency band of AP2), the transmission requirement information of AP1, and the transmission requirement information of AP2. Optionally, this implementation can be performed after S1402 and before S1403.
[0296] The AP1 preamble puncturing information includes the AP1 puncturing frequency band information and puncturing time information 1, and the AP2 preamble puncturing information includes the AP2 puncturing frequency band information and puncturing time information 2. The AP1 transmission requirement information includes at least one of the following: the amount of data buffered by AP1, the AP1 transmission rate on its own operating frequency band, and the AP1 transmission bandwidth.
[0297] In the above, the puncturing time information 1 of AP1 can be used to indicate the time 1 during which AP1 collaboratively performs preamble puncturing transmission. Similarly, the puncturing time information 2 of AP2 can be used to indicate the time 2 during which AP2 collaboratively performs preamble puncturing transmission.
[0298] The above S1401 and S1402 are examples of AP2 being the shared recipient of AP1's TXOP. In practice, AP1 can also share this TXOP with other APs, such as AP3. Similarly, after receiving the polling frame from AP1, AP3 can also send a response frame to AP1 following the steps of AP2. The function and information carried by AP3's response frame can be found in the relevant description of AP2's response frame, which will be detailed here. Based on this, AP1 can determine the preamble puncturing information of AP1, AP2, and AP3 according to AP1's operating frequency band (including AP1's main frequency band), AP2's operating frequency band (including AP2's main frequency band), AP3's operating frequency band (including AP3's main frequency band), AP1's transmission requirement information, AP2's transmission requirement information, and AP3's transmission requirement information. Among them, AP3's transmission requirement information includes at least one of the following: the amount of data buffered by AP3, AP3's transmission rate on its own operating frequency band, or AP3's transmission bandwidth. The AP3 preamble punch information includes the AP3 punch frequency band information and the AP3 punch time information.
[0299] At a certain moment a, if AP1 determines to share TXOP with other APs (such as AP2) for transmission, then the following steps are performed:
[0300] S1403: AP1 sends an ICF to AP2; correspondingly, AP2 receives the ICF.
[0301] The ICF includes the preamble puncturing information for AP2, namely the puncturing frequency band information and puncturing time information for AP2. The puncturing frequency band information for AP2 indicates the puncturing frequency band within AP2's operating frequency band.
[0302] In one possible implementation, the punched frequency band information of AP2 can be in the form of a bitmap. For details, please refer to the example of the punched frequency band information of AP2 described in S803 of the above implementation method, which will not be repeated here.
[0303] In the above, the time during which APs (such as AP1 or AP2) collaboratively perform preamble puncturing transmission can refer to the time period during which APs collaboratively perform preamble puncturing transmission (or the effective time period of the AP's puncturing frequency band information).
[0304] For example, the punching time information 1 of AP2 includes start time information and duration information, or it includes start time information and end time information, or it includes end time information and duration information.
[0305] In the above, AP2 is used as an example to illustrate the sharing of TXOP. In reality, other APs may also be sharing TXOP, such as AP3, AP4, etc. Each AP can obtain the negotiated puncturing frequency band information and puncturing time information by referring to the method and steps of AP2. These will not be detailed here. For example, the above ICF may also include preamble puncturing information from other APs.
[0306] S1404: During the time 1 of AP1's collaborative execution of preamble puncturing transmission, AP1 performs puncturing and transmission according to AP1's puncturing frequency band information.
[0307] That is, during the time 1 of AP1's collaborative preamble puncturing, AP1 punctures the puncturing frequency band according to AP1's puncturing frequency band information and sends message 1 to the associated STA1. Correspondingly, the associated STA1 receives message 1.
[0308] The number of STA1s associated with AP1 can be one or more.
[0309] S1405: During the time 2 when AP2 is cooperating in executing preamble puncturing transmission, AP2 performs puncturing and transmission according to the puncturing frequency band information of AP2.
[0310] That is, during the time 2 when AP2 is cooperating in performing preamble puncturing, AP2 punctures the puncturing frequency band according to AP2's puncturing frequency band information and sends message 2 to the associated STA2. Correspondingly, the associated STA2 receives message 2.
[0311] The number of STA2s associated with AP2 can be one or more.
[0312] For example, based on S1401 to S1405 above, in the case where the operating frequency bands of AP1 and AP2 completely overlap, Figure 15A shows a schematic diagram of the interaction between AP1, the sharer of TXOP, and AP2, the sharer of TXOP. Referring to Figure 15A, AP1 sends a polling frame to AP2, and AP2 receives the polling frame, which is used to indicate the cooperative execution of preamble puncturing transmission (see the description in S1401 above). Then, AP2 returns a response frame to AP1, and AP2 receives the response frame, which is used to indicate whether AP2 supports or accepts the cooperative execution of preamble puncturing transmission. The response frame includes AP2's operating frequency band information and transmission requirement information (see the description in S1402 above). In this way, AP1 can negotiate and determine the puncturing frequency band and puncturing time (i.e., the effective time) of each AP based on the operating frequency band information and transmission requirement information of multiple APs (including AP1 and AP2). Furthermore, at a certain moment 'a', if the AP determines that each AP needs to transmit messages, AP1 sends an ICF to AP2. AP2 receives this ICF, which includes AP2's puncturing frequency band information and puncturing time information (see the description in S1403 above). Afterwards, AP1 and AP2, within their respective puncturing times, puncture the frequency bands according to the puncturing frequency band information and perform concurrent transmission (see the descriptions in S1404 and S1405 above).
[0313] As can be seen from Figure 15A, the unpunctured frequency bands of AP1 and AP2 do not overlap. Therefore, AP1 and AP2 will not conflict when performing concurrent transmission, which can improve spectrum utilization and meet transmission requirements (such as low latency transmission requirements).
[0314] For example, in the case where the operating frequency bands of AP1 and AP2 partially overlap, Figure 15B illustrates the interaction between the sharing provider AP1 and the shared provider (such as AP2). The main difference between Figure 15B and Figure 15A is that while there are two overlapping original operating frequency bands between AP1 and AP2, inter-AP negotiation via puncturing prevents conflicts during concurrent transmission, avoiding wasted spectrum resources and thus improving spectrum utilization.
[0315] In the above content, AP2 is used as an example to describe the shared TXOP in detail. In actual practice, the shared TXOP is not limited to AP2, but may also include other APs, such as AP3, AP4, etc. Any AP can refer to the steps and methods corresponding to AP2 to implement collaborative punching and concurrent transmission. They will not be listed one by one here.
[0316] In implementation method three, AP1, the sharer of TXOP, can negotiate and determine the puncturing frequency band information and corresponding puncturing time information (or effective time information) of each AP based on the operating frequency band and transmission requirements of multiple APs (including AP1 and the APs shared by TXOP). The negotiated puncturing frequency band information and corresponding puncturing time information (or effective time information) are then sent to each AP shared by TXOP. In this way, each AP shared by TXOP can perform puncturing and concurrent transmission according to its negotiated puncturing frequency band information within the corresponding puncturing time (or effective time). This can not only effectively avoid conflicts under concurrent transmission to improve spectrum utilization, but also meet transmission requirements (such as low latency transmission requirements).
[0317] Implementation Method Four:
[0318] Compared to the above implementation method three, the main difference of implementation method four is that: when AP1 does not perform concurrent transmission with the AP that shares the TXOP, AP1 can collaboratively determine the punching frequency band and the corresponding punching time (or effective time) for the AP that shares the TXOP (hereinafter, AP2 and AP3 are examples).
[0319] Referring to Figure 16, the method flow of Implementation Method 4 includes the following steps:
[0320] S1601: AP1 sends a polling frame; correspondingly, AP2 and AP3 receive the polling frame.
[0321] The polling frame is used to instruct the coordinated execution of preamble punch transmission.
[0322] S1601 can be referred to in the relevant introduction in S1401 above, and will not be repeated here.
[0323] S1602a: AP2 sends response frame 1 to AP1; correspondingly, AP1 receives response frame 1.
[0324] S1602a can be referred to in the relevant introduction in S1402 above, and will not be repeated here.
[0325] S1602b: AP3 sends response frame 2 to AP1; correspondingly, AP1 receives the response frame 2.
[0326] The response frame 2 is used to indicate whether AP3 supports or accepts cooperative preamble puncturing transmission. If AP3 supports or accepts cooperative preamble puncturing transmission, the response frame 2 includes AP3's operating frequency band information and AP3's primary frequency band information.
[0327] The operating frequency band of AP3 includes the main frequency band of AP3, and optionally, at least one secondary frequency band of AP3. The main frequency bands of AP1, AP2, and AP3 do not overlap, but at least one secondary frequency band of AP2 and at least one secondary frequency band of AP3 overlap. In this embodiment, each frequency band of AP is 20MHz as an example.
[0328] In one possible implementation, the response frame 2 also includes transmission request information for AP3. For example, the transmission request information for AP3 may include at least one of the following: the amount of data buffered by AP3, the transmission rate of AP3 on its own operating frequency band, or the transmission bandwidth of AP3.
[0329] In another possible implementation, AP1 requests AP3 to report its transmission request information, and then AP3 sends AP2's transmission request information back to AP1. Optionally, this implementation can be performed before S1601.
[0330] For example, before S1601, AP1 sends a capability request message to AP3. After receiving the capability request message, AP3 sends its capability information to AP1, which includes AP3's transmission requirement information.
[0331] The above S1602a and S1602b can be executed synchronously or asynchronously, and there is no specific restriction on the order of execution. The execution order can be adjusted according to the actual situation or needs.
[0332] In one possible implementation, the method further includes: AP1 determining the preamble puncturing information of AP2 and AP3 based on the operating frequency band of AP2 (including the main frequency band of AP2), the operating frequency band of AP3 (including the main frequency band of AP3), the transmission requirement information of AP2, and the transmission requirement information of AP3; the preamble puncturing information of AP2 includes the puncturing frequency band information and the puncturing time information of AP2 2, and the preamble puncturing information of AP3 includes the puncturing frequency band information and the puncturing time information of AP3 3. Optionally, this implementation can be performed after S1602a and S1602b and before S1604 below.
[0333] In the above, the puncturing time information 2 of AP2 can be used to indicate the time 2 during which AP2 collaboratively performs preamble puncturing transmission. Similarly, the puncturing time information 3 of AP3 can be used to indicate the time 3 during which AP3 collaboratively performs preamble puncturing transmission.
[0334] S1603: AP1 transmits message 1 on its own operating frequency band.
[0335] AP1 obtains TXOP and can first send message 1 across the entire frequency band.
[0336] At some later time a, if AP1 determines to share TXOP with AP2 and AP3 for transmission, then the following steps are performed:
[0337] S1604: AP1 sends an ICF; correspondingly, AP2 and AP3 receive the ICF.
[0338] In the above, the ICF includes the preamble puncturing information of AP2, namely the puncturing frequency band information and the puncturing time information of AP2. The ICF also includes the preamble puncturing information of AP3, namely the puncturing frequency band information and the puncturing time information of AP3. For example, this ICF is a Multi-STA Block Ack frame.
[0339] In one possible implementation, the punched frequency band information of AP2 (or AP3) can be indicated using a bitmap method. For details, please refer to the example of the punched frequency band information of AP2 described in S803 of the above implementation method, which will not be repeated here.
[0340] In the above, the time 2 for AP2 to collaboratively perform preamble puncturing transmission and the time 3 for AP3 to collaboratively perform preamble puncturing transmission can refer to time periods.
[0341] Optionally, the ICF may also include the address information of AP2 and AP3. For example, the address information of AP2 may be the MAC address of AP2, and the address information of AP3 may be the MAC address of AP3.
[0342] In this implementation, AP1 can send ICFs to AP2 and AP3 via broadcast (or unicast or multicast). If AP1 uses broadcast or multicast, the puncturing frequency band information, puncturing time information, and address information of these APs can be carried in the same ICF (e.g., a multi-user block acknowledgment frame). If AP1 uses unicast, the puncturing frequency band information, puncturing time information, and address information of each AP can be carried in different ICFs.
[0343] S1605: During the time 2 when AP2 is cooperating in executing preamble puncturing transmission, AP2 performs puncturing and transmission according to the puncturing frequency band information of AP2.
[0344] That is, during the time 2 when AP2 is cooperating in the preamble punching transmission, AP2 punches according to the punching frequency band information of AP2 and sends a report to the associated STA2; accordingly, the associated STA2 of AP2 receives the message 3.
[0345] In the embodiments of this application, the number of STA2 associated with AP2 can be one or more, and there is no limitation thereto.
[0346] S1606: During the time 3 when AP3 is cooperating in the preamble punching transmission, AP3 performs punching and transmission according to the punching frequency band information of AP3.
[0347] That is, during the time 3 when AP3 is cooperating in the preamble puncturing transmission, AP3 performs puncturing according to the puncturing frequency band information of AP3 and sends a report to the associated STA2; accordingly, the associated STA3 of AP3 receives the message 3.
[0348] In the embodiments of this application, the number of STA3 associated with AP3 can be one or more, and there is no limitation thereto.
[0349] For example, based on S1601 to S1606 above, Figure 17 shows a schematic diagram of the interaction between AP1, the sharer of TXOP, and the sharers of TXOP (such as AP2 and AP3). Referring to Figure 17, AP1 sends a polling frame, and correspondingly, AP2 and AP3 receive a polling frame, which is used to instruct the cooperative execution of preamble puncturing transmission (see the relevant description in S1601 above); then, AP2 and AP3 return response frames (i.e., response frame 1 and response frame 2) to AP1 respectively (see the relevant description in S1602a and S1602b above). AP1 can first transmit messages across the entire frequency band (see the relevant description in S1603 above). At a certain moment a, if AP1 shares its TXOP with AP2 and AP3 for message transmission, AP1 sends an ICF. Correspondingly, AP2 and AP3 receive this ICF, which includes AP2's puncturing frequency band information and puncturing time information 2, as well as AP3's puncturing frequency band information and puncturing time information 3 (see the relevant description in S1604 above). During Co-TDMA, AP2 and AP3, within their respective puncturing times, perform puncturing according to the negotiated puncturing frequency band information and execute concurrent transmission (i.e., AP2 and AP3 concurrently send messages) (see the relevant descriptions in S1605 and S1606 above).
[0350] As shown in Figure 17, the frequency bands of AP2 and AP3 do not overlap after co-punching during Co-TDMA. There will be no conflict when AP2 and AP3 transmit concurrently. This can not only improve the concurrent capability of multiple APs and improve spectrum utilization, but also meet the transmission needs of each shared AP.
[0351] In implementation method four, AP1, the sharer of TXOP, can first send messages on all its own operating frequency bands. Then, it shares the air interface transmission opportunity (TOXP opportunity) with other APs (such as AP2 and AP3), and negotiates and determines the puncturing frequency band information and corresponding puncturing time for these shared APs. The negotiated puncturing frequency band information and corresponding puncturing time are then sent to each shared AP. In this way, each shared AP can perform puncturing and concurrent transmission according to its negotiated puncturing frequency band information within the corresponding puncturing time. This can effectively avoid conflicts under concurrent transmission, thereby effectively improving spectrum utilization and ensuring and meeting the transmission needs of the shared APs of TXOP (such as low latency transmission requirements).
[0352] It should be understood that the above embodiments may change as the technical solutions evolve, and this application is not limited to the contents shown in the above embodiments.
[0353] It should be noted that different embodiments or some steps (e.g., any one or more steps) in different embodiments of this application can be combined with each other to form new embodiments. Furthermore, this application does not limit the inclusion of any one or more steps in different embodiments as including optional steps in a certain embodiment, mandatory steps in a certain embodiment, or both optional and mandatory steps in a certain embodiment.
[0354] It should be noted that, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different implementation methods are consistent and can be referenced from each other.
[0355] It should be noted that the order of the steps in the embodiments of this application is determined by the logic of the scheme, and this application does not limit it.
[0356] It should be noted that the order in which different conditions are judged in the embodiments of this application is not limited by this application.
[0357] It should be noted that the terms "after" and "time" in this application do not strictly limit the specific point in time.
[0358] It should be noted that the nouns and terms used in this application are merely examples and may be other names, which are not limited in this application.
[0359] In the embodiments provided above, the methods provided by the embodiments of this application are described from the perspective of interaction between various devices. To implement the functions of the methods provided in the embodiments or implementations of this application above, the first device or the second device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.
[0360] The module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments or implementations of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.
[0361] Based on the above method embodiments, as shown in FIG18, this application embodiment also provides a communication device 1800 for implementing the functions of the first device or the second device in the above method. For example, the communication device 1800 can be a software module or a chip system. In this application embodiment, the chip system can be composed of chips or can include chips and other discrete devices. The communication device 1800 may include: a communication unit 1801 and a processing unit 1802.
[0362] In this embodiment, the communication unit 1801, also known as the transceiver unit, may include a sending unit and / or a receiving unit, respectively used to execute the sending and receiving steps of the first device or the second device in the above method embodiments. The processing unit 1802 may be used to read instructions and / or data from the storage module so that the communication device 1800 implements the aforementioned method embodiments.
[0363] For example, the communication device 1800 may also include a storage unit 1803, which is equivalent to a storage module and can be used to store instructions and / or data.
[0364] The communication device provided in the embodiments of this application is described in detail below with reference to Figures 18 and 19. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, the contents not described in detail can be implemented by referring to the manner shown in Figures 7, 8, 11, 14 and 16 above. For the sake of brevity, they will not be repeated here.
[0365] The communication unit 1801 can also be referred to as a transceiver, transceiver, or transceiver device. The processing unit 1802 can also be referred to as a processor, processing board, processing module, or processing device. Optionally, the device in the communication unit 1801 used to implement the receiving function can be considered as a receiving unit, and the device in the communication unit 1801 used to implement the transmitting function can be considered as a transmitting unit; that is, the communication unit 1801 includes a receiving unit and a transmitting unit. The communication unit 1801 can sometimes also be referred to as a transceiver, transceiver circuit, or transceiver circuit. The receiving unit can sometimes be referred to as a receiver, receiver, or receiving circuit. The transmitting unit can sometimes be referred to as a transmitter, transmitter, or transmitting circuit.
[0366] When the communication device 1800 is applied to the first device in the process shown in Figure 7 of the above embodiment:
[0367] The communication unit 1801 is used to send first information, which is used to instruct the cooperative execution of preamble punch transmission;
[0368] The communication unit 1801 is further configured to receive second information from the second device, the second information being configured to instruct the second device to support cooperative execution of preamble punch transmission, the second information including the main channel information of the second device, the main channel of the second device and the main channel of the first device not overlapping, and the channel of the second device and the channel of the first device overlapping;
[0369] The processing unit 1802 is used to determine the preamble punching information based on the main channel information of the second device.
[0370] When the communication device 1800 is applied to the second device in the process shown in Figure 7 of the above embodiment:
[0371] The communication unit 1801 is used to receive first information from the first device, the first information being used to instruct the cooperative execution of preamble punch transmission;
[0372] The communication unit 1801 is further configured to send second information, which is used to instruct the second device to support cooperative execution of preamble puncturing transmission. The second information includes the main channel information of the second device. The main channel of the second device and the main channel of the first device do not overlap, but the channels of the second device and the first device overlap. The main channel information of the second device is used to determine the preamble puncturing information.
[0373] The processing unit 1802 is used to process information and / or data, etc.
[0374] The above are just examples. Processing unit 1802 and communication unit 1801 can also perform other functions. For a more detailed description, please refer to the relevant descriptions in the method embodiments shown in Figures 7, 8, 11, 14 and 16 above. They will not be repeated here.
[0375] Figure 19 shows a communication device 1900 provided in an embodiment of this application. The communication device shown in Figure 19 can be a hardware circuit implementation of the communication device shown in Figure 18. This communication device 1900 can be applied to the flowcharts shown above to perform the functions of the first device or the second device in the above method embodiments. For ease of explanation, Figure 19 only shows the main components of the communication device.
[0376] As shown in Figure 19, the communication device 1900 includes a communication interface 1901 and a processor 1902. The communication interface 1901 and the processor 1902 are coupled to each other. It is understood that the communication interface 1901 can be a transceiver or an input / output interface, or an interface circuit such as a transceiver circuit. Optionally, the communication device 1900 may further include a memory 1903 for storing instructions executed by the processor 1902, or storing input data required by the processor 1902 to execute instructions, or storing data generated after the processor 1902 executes instructions.
[0377] When the communication device 1900 is used to implement the methods shown in Figures 7, 8, 11, 14 and 16, the communication interface 1901 is used to implement the functions of the communication unit 1801, and the processor 1902 is used to implement the functions of the processing unit 1802.
[0378] This embodiment does not limit the specific connection medium between the communication interface 1901, processor 1902, and memory 1903. In Figure 19, the memory 1903, processor 1902, and communication interface 1901 are connected via a communication bus 1904, which is represented by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The communication bus 1904 can be divided into an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 19, but this does not indicate that there is only one bus or one type of bus.
[0379] When the aforementioned communication device is a chip, Figure 20 shows a simplified schematic diagram of the chip's device structure. The chip 2000 includes an interface circuit 2001 and one or more processors 2002. Optionally, the chip 2000 may also include a bus. Wherein:
[0380] The processor 2002 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the aforementioned communication method can be completed through integrated logic circuits in the hardware of the processor 2002 or through software instructions. The processor 2002 may be a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods and steps disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor.
[0381] The interface circuit 2001 can be used to send or receive data, instructions or information. The processor 2002 can use the data, instructions or other information received by the interface circuit 2001 to process the data, instructions or other information, and can send the processed information out through the interface circuit 2001.
[0382] Optionally, chip 2000 also includes memory 2003, which may include read-only memory and random access memory, and provides operation instructions and data to the processor. A portion of memory 2003 may also include non-volatile random access memory (NVRAM).
[0383] Optionally, the memory stores executable software modules or data structures, and the processor can execute corresponding operations by calling the operation instructions stored in the memory (which may be stored in the operating system).
[0384] Optionally, the chip can be used in the first or second device involved in the embodiments of this application. Optionally, the interface circuit 2001 can be used to output the execution result of the processor 2002. For the communication methods provided by one or more embodiments of this application, please refer to the foregoing embodiments and implementation methods, which will not be repeated here.
[0385] It should be noted that the functions of the interface circuit 2001 and the processor 2002 can be implemented through hardware design, software design, or a combination of hardware and software; no restrictions are imposed here.
[0386] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the first device or the second device in the above method embodiments.
[0387] For example, when the computer program is executed by a computer, it enables the computer to implement the method performed by the first device or the second device in the above method embodiments.
[0388] This application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to perform the method described in the above method embodiments, executed by the first device or the second device.
[0389] This application embodiment also provides a chip, including a processor, for calling computer programs or computer instructions stored in the memory, so that the processor executes the methods of the implementation shown in Figures 7, 8, 11, 14 and 16.
[0390] In one possible implementation, the input of the chip corresponds to the receiving operation in the implementations shown in Figures 7, 8, 11, 14 and 16, and the output of the chip corresponds to the transmitting operation in the implementations shown in Figures 7, 8, 11, 14 and 16.
[0391] Optionally, the processor is coupled to the memory via an interface.
[0392] Optionally, the chip also includes a memory that stores computer programs or computer instructions.
[0393] The processor mentioned above can be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of a program through a communication method for the implementations shown in Figures 7, 8, 11, 14, and 16. The memory mentioned above can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, such as random access memory (RAM).
[0394] It should be noted that, for the sake of convenience and brevity, the explanations and beneficial effects of the relevant contents in any of the communication devices provided above can be referred to the corresponding communication method embodiments provided above, and will not be repeated here.
[0395] The module division in this embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in each embodiment of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.
[0396] Through the above description of the embodiments, those skilled in the art will clearly understand that the embodiments of this application can be implemented in hardware, firmware, or a combination thereof. When implemented in software, the above 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 accessible to a computer. For example, but not limited to, computer-readable media can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible to a computer. Furthermore, any connection can suitably be a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used in embodiments of this application, disks and discs include compact discs (CDs), laser discs, optical discs, digital video discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically copy data, while discs optically copy data using lasers. The combinations above should also be included within the scope of protection for computer-readable media.
Claims
1. A communication method, characterized in that, A chip used in a first device or a first device, including: Send a first message, which is used to instruct the cooperative execution of preamble punch transmission; Receive second information from the second device, the second information being used to indicate that the second device supports cooperative execution of preamble punch transmission, the second information including the main channel information of the second device, the main channel of the second device and the main channel of the first device not overlapping, the channel of the second device and the channel of the first device overlapping; Based on the main channel information of the second device, the preamble punching information is determined.
2. The method according to claim 1, characterized in that, The preamble punch information includes at least one of the following: The punched information of the preamble of the first device and the punched information of the preamble of the second device.
3. The method according to claim 1 or 2, characterized in that, The step of determining the preamble puncture information based on the main channel information of the second device includes: The preamble punching information is determined based on the channel information and main channel information of the first device and the main channel information of the second device.
4. The method according to claim 3, characterized in that, Determining the preamble puncture information based on the channel information and main channel information of the first device and the main channel information of the second device includes: The preamble punching information is determined based on the channel information and main channel information of the first device, and the channel information and main channel information of the second device; wherein the channel information of the second device is carried in the second information.
5. The method according to claim 4, characterized in that, The second information also includes transmission requirement information of the second device, which includes at least one of the following: The amount of data cached by the second device, the transmission rate of the second device, or the transmission bandwidth of the second device.
6. The method according to claim 5, characterized in that, Determining the preamble puncture information based on the channel information and main channel information of the first device, and the channel information and main channel information of the second device, includes: The preamble punching information is determined based on the channel information and main channel information of the first device, the channel information and main channel information of the second device, the transmission requirement information of the first device, and the transmission requirement information of the second device.
7. The method according to any one of claims 1-6, characterized in that, The method further includes: Send the preamble punching information to the second device.
8. The method according to any one of claims 2-6, characterized in that, The method further includes: Send third information to a third device associated with the first device, the third information including the preamble punching information of the first device.
9. The method according to any one of claims 2-8, characterized in that, The preamble punching information of the first device includes the punching channel information and the punching time information of the first device, and the preamble punching information of the second device includes the punching channel information and the punching time information of the second device.
10. The method according to any one of claims 1-9, characterized in that, The unpunctured channels of the first device and the unpunctured channels of the second device do not overlap.
11. The method according to any one of claims 1-9, characterized in that, The un-punched channels of the first device and the second device partially overlap, and the un-punched channels of the first device do not include the main channel of the second device, and the un-punched channels of the second device do not include the main channel of the first device.
12. The method according to claim 11, characterized in that, The method further includes: The channel occupied by the second device is determined; the un-punctured channel of the first device overlaps with the channel occupied by the second device; The un-drilled channel of the first device is punched according to the channel occupied by the second device.
13. The method according to any one of claims 1-12, characterized in that, The channels of the first device and the second device completely overlap, or the channels of the first device and the second device partially overlap.
14. The method according to claim 7, characterized in that, The preamble punch information is carried in the initial control frame, which also includes the address information and / or identification information of the second device.
15. The method according to any one of claims 1-14, characterized in that, The first information is a poll frame.
16. A communication method, characterized in that, Chips used in a second device or a second device include: Receive first information from a first device, the first information being used to instruct collaborative execution of preamble punch transmission; Send a second message, which is used to instruct the second device to support cooperative execution of preamble puncturing transmission. The second message includes the main channel information of the second device. The main channel of the second device and the main channel of the first device do not overlap. However, the channels of the second device and the first device overlap. The main channel information of the second device is used to determine the preamble puncturing information.
17. The method according to claim 16, characterized in that, The method further includes: Receive the preamble punching information from the first device.
18. The method according to claim 16 or 17, characterized in that, The preamble punch information includes at least one of the following: The punched information of the preamble of the first device and the punched information of the preamble of the second device.
19. The method according to any one of claims 16-18, characterized in that, The second information also includes transmission requirement information of the second device, which includes at least one of the following: The amount of data cached by the second device, the transmission rate of the second device, or the transmission bandwidth of the second device.
20. The method according to claim 18 or 19, characterized in that, The method further includes: Send a fourth message to a fourth device associated with the second device, the fourth message including the preamble punching information of the second device.
21. The method according to any one of claims 18-20, characterized in that, The preamble punching information of the first device includes the punching channel information and the punching time information of the first device, and the preamble punching information of the second device includes the punching channel information and the punching time information of the second device.
22. The method according to any one of claims 16-21, characterized in that, The unpunctured channels of the first device and the unpunctured channels of the second device do not overlap.
23. The method according to any one of claims 16-21, characterized in that, The un-punched channels of the first device and the second device partially overlap, and the un-punched channels of the first device do not include the main channel of the second device, and the un-punched channels of the second device do not include the main channel of the first device.
24. The method according to claim 23, characterized in that, The method further includes: The channel occupied by the first device is determined; the un-punctured channel of the second device overlaps with the channel occupied by the first device; The un-drilled channel of the second device is punched according to the channel occupied by the first device.
25. The method according to any one of claims 16-24, characterized in that, The channels of the first device and the second device completely overlap, or the channels of the first device and the second device partially overlap.
26. The method according to claim 17, characterized in that, The preamble punch information is carried in the initial control frame, which also includes the address information and / or identification information of the second device.
27. The method according to any one of claims 16-26, characterized in that, The first information is a poll frame.
28. A communication device, characterized in that, It includes units or modules for performing the method as described in any one of claims 1-15, or units or modules for performing the method as described in any one of claims 16-27.
29. A communication device, characterized in that, It includes at least one processor and a memory for storing program instructions, wherein the at least one processor, when executing the program instructions, causes the method as described in any one of claims 1-15 to be executed, or causes the method as described in any one of claims 16-27 to be executed.
30. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer-readable program or instructions that, when executed on a communication device, cause the method as described in any one of claims 1-15 to be performed, or the method as described in any one of claims 16-27 to be performed.
31. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when run on a computer, cause the method as described in any one of claims 1-15 to be performed, or the method as described in any one of claims 16-27 to be performed.
