Communication method and apparatus

Abstract

The present application relates to the technical field of communication, and particularly relates to a communication method and device. The present application can be applied to IEEE 802.11ax standard, 802.11be standard, 802.11bn standard and other standards of IEEE 802.11 series, such as 802.15 standard, 802.11bf standard or IMMW standard or star flash standard. The method comprises the following steps: a first AP and a second AP have established Co-RTWT, before the starting time of a second SP of the second AP, the first AP can not end a TXOP under the condition of meeting a condition; or the first AP can not end the TXOP under the condition of meeting the condition, and share a remaining time length or a part of the time length of the TXOP with the second AP after the starting time of the second SP. Therefore, the channel utilization is effectively improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] Wireless local area network (WLAN) is a general term for wireless networks covering a local area, with Wi-Fi being a typical example. Due to its high transmission speed, low cost, and open accessibility, WLAN has received widespread attention from industry and academia. WLAN operates in unlicensed spectrum, and WLAN system standards are primarily discussed within the IEEE 802.11 standards group. Since its first version was released in 1997, IEEE 802.11 has undergone several major standard evolutions, including 802.11, 802.11a and 802.11b, 802.11g, 802.1n, 802.11ac, 802.11ax (considered the sixth generation of Wi-Fi, i.e., Wi-Fi 6, also known as high-throughput (HE)), and IEEE 802.11be (considered the seventh generation of Wi-Fi, i.e., Wi-Fi 7). The next-generation WLAN standard, IEEE 802.11bn (considered the eighth generation of Wi-Fi, or Wi-Fi 8), has also begun research and is planned for release in 2028. WLAN carries more than 50% of the world's Internet Protocol (IP) traffic and has become, along with cellular networks, the main wireless networks now and in the future.

[0003] Currently, the next-generation WLAN standard IEEE 802.11bn, or Ultra High Reliability (UHR), is under research. Transmission reliability is a key focus of UHR. The IEEE 802.11bn standard introduces several reliability-related technical features, such as the Coordinated Restricted Target Wakeup Time (Co-RTWT) mechanism. The Co-RTWT mechanism effectively improves the protection of participating basic service sets (BSS) against each other's restricted target wakeup time (R-TWT), as well as the efficiency of the R-TWT mechanism itself. For example, if AP1 and AP2 establish a Co-RTWT mechanism, AP1 will provide channel access protection for the start time of AP2's R-TWT SP, ensuring that AP2 has a higher probability of competing for the channel.

[0004] Therefore, how to further improve channel utilization based on the Co-RTWT mechanism is an urgent issue to be addressed. Summary of the Invention

[0005] This application provides a communication method and apparatus that can effectively improve channel utilization.

[0006] In a first aspect, embodiments of this application provide a communication method applied to a first access point (AP). This method can be implemented by the first AP or by components on the first AP side (such as chips, functional modules, or processing systems within the first AP). The method includes:

[0007] If the first condition is met, the first AP does not terminate the transmission opportunity (TXOP) before the start time of the second service period (SP) of the second AP, and the first AP and the second AP have established a Co-RTWT; the first condition includes: the start time of the second SP is later than the start time of the first SP of the first AP, and the start time of the second SP is earlier than the end time of the first SP.

[0008] The establishment of Co-RTWT between the first AP and the second AP can also be referred to as: the first AP and the second AP have established a Co-RTWT cooperative relationship, or the first AP and the second AP have established a Co-RTWT mechanism, or the first AP protects the second AP's R-TWT mechanism (or the first AP respects the second AP's R-TWT SP), and the second AP protects the first AP's R-TWT mechanism (or the second AP respects the first AP's R-TWT SP). The first AP not ending TXOP can also be referred to as: the first AP continuing TXOP, that is, the first AP continues TXOP at and after the start time of the second SP.

[0009] If the first AP does not terminate the TXOP before the start time of the second SP, it can also mean that the end time of the TXOP is later than the start time of the second SP, and the start time of the TXOP is earlier than the start time of the second SP. This improves the efficiency of the first AP in utilizing the channel after acquiring the TXOP, thus increasing channel utilization.

[0010] In this embodiment, even if the first AP and the second AP establish a Co-RTWT, the first AP may not terminate the TXOP before the start time of the second SP. This effectively ensures that the first AP has sufficient time to transmit data, improving channel utilization.

[0011] If, under the first condition, the first AP still performs the following operation, it will result in a shorter data transmission time for the first AP, and may even affect the transmission of low-latency service data by the first AP. This would prevent the first AP from effectively transmitting the low-latency service data, thereby increasing the data transmission latency of the first AP, causing low channel utilization due to channel resource fragmentation, and introducing additional contention overhead. This operation includes: before the start time of the second SP, the first AP ending its TXOP; or, if the time between the backoff time to 0 (which is earlier than the start time of the second SP) and the start time of the second SP is insufficient to complete frame interaction, the first AP abandons the current transmission (or delays the current transmission) and backs off again. However, in this embodiment, under the first condition, the first AP may not perform the above operation, such as not ending its TXOP, or continuing transmission from the backoff time to 0 (which is earlier than the start time of the second SP) to the start time of the second SP (i.e., not abandoning the current transmission, or not delaying the transmission, without needing to back off again).

[0012] In one possible implementation, the first condition further includes at least one of the following: before the start time of the second SP, the first AP has data to be transmitted; before the start time of the second SP, the data transmission of the first AP has not ended; or, before the start time of the second SP, the priority of the low-latency service of the first AP is not lower than the priority of the low-latency service of the second AP.

[0013] The priority of low-latency services in the first AP can be the service priority associated with the first SP. For example, the R-TWT service information field in the TWT element carrying relevant information about the first SP can indicate uplink / downlink services. The priority of low-latency services in the second AP can be the service priority associated with the second SP. For example, the R-TWT service information field in the TWT element carrying relevant information about the second SP can indicate uplink / downlink services.

[0014] In this embodiment of the application, by including the above content, the first condition can further avoid the impact on the transmission of data of the first AP and improve the ability of the first AP to carry services (such as low-latency services).

[0015] In one possible implementation, the first condition further includes: the duration between the start time of the first SP and the start time of the second SP is less than or equal to a first threshold.

[0016] If the duration between the start time of the first SP and the start time of the second SP is less than or equal to the first threshold, it means that the first AP has a relatively short data transmission time after obtaining the TXOP. Therefore, the first AP does not end the TXOP, thus giving the first AP enough time to transmit data and improve channel utilization.

[0017] In one possible implementation, the method further includes: at or after the start time of the second SP, the first AP continues transmission. Optionally, the first AP continuing transmission includes: the first AP continuing to transmit data for low-latency services. This not only ensures that the first AP can transmit data (such as data for low-latency services) in a timely manner, improving the first AP's ability to carry services (such as low-latency services), but also improves channel utilization.

[0018] In one possible implementation, the method further includes: within the TXOP, the first AP transmits data for low-latency services.

[0019] In one possible implementation, within the TXOP, the first AP transmits low-latency service data, including: within the TXOP and before the start time of the second SP, the first AP transmits low-latency service data. This not only ensures that the first AP can transmit low-latency services in a timely manner but also improves channel utilization.

[0020] In one possible implementation, within the TXOP, the first AP transmits low-latency service data, including: within the TXOP, either at the start time of the second SP or after the start time of the second SP. This ensures the smooth operation of the first AP's low-latency services and improves channel utilization.

[0021] In one possible implementation, the method further includes: the first AP sharing a first duration with the second AP, the first duration being the remaining duration of TXOP, or a portion of the remaining duration.

[0022] In this embodiment, the first AP can share its TXOP, enabling the second AP to transmit data within that TXOP, thus improving the channel access efficiency of the second AP. This is because when the first AP shares its TXOP with the second AP, the second AP can immediately use the allocated TXOP to transmit data without needing to compete for channel access, reducing free competition conflicts and collisions, thereby improving the channel access efficiency of the second AP and enhancing the overall channel utilization of the network.

[0023] In one possible implementation, the first AP shares a first duration with the second AP, including: the first AP shares the first duration with the second AP if a second condition is met; the second condition includes at least one of the following: the duration between the start time of the second SP and the start time of the first duration is less than or equal to a second threshold; or, the first duration is greater than or equal to a third threshold.

[0024] In this embodiment, the first AP does not terminate the TXOP and shares the TXOP, which can ensure that the first AP has enough time to transmit data and improve channel utilization, and also enable the second AP to transmit data, thereby improving the efficiency of the second AP accessing the channel.

[0025] In one possible implementation, the second condition further includes: after the start time of the first duration, the low-latency service of the first AP has a lower priority than the low-latency service of the second AP. This ensures that data with higher priority is transmitted smoothly.

[0026] In one possible implementation, the method further includes: a first AP receiving RTWT information from a second AP, the RTWT information being used to indicate a second SP. For ease of distinction, the RTWT information of the second AP can be referred to as second RTWT information. Optionally, the second RTWT information includes at least one of the following: the start time of the second SP, the duration of the second SP, or the period of the second SP. Thus, the first AP can determine the overlap between the second SP and the first SP based on the second RTWT information, thereby determining whether to terminate the TXOP.

[0027] In one possible implementation, the method further includes: a first AP sending RTWT information to a second AP, the RTWT information being used to indicate a first SP. For ease of distinction, the RTWT information of the first AP is referred to as first RTWT information. Optionally, the first RTWT information includes at least one of the following: the start time of the first SP, the duration of the first SP, or the period of the first SP.

[0028] Secondly, embodiments of this application provide a communication method applied to an associated site of a first AP. This method can be implemented by the associated site itself, or by components on the associated site side (such as chips, functional modules, or processing systems within the associated site). The method includes:

[0029] Under the condition that the first condition is met, the associated site of the first AP does not end TXOP before the start time of the second SP, and the site corresponding to the first AP and the second SP (such as the second AP) has established Co-RTWT; the first condition includes: the start time of the second SP is later than the start time of the first SP of the first AP, and the start time of the second SP is earlier than the end time of the first SP.

[0030] The associated sites of the first AP are those sites within the BSS where the first AP is located that have established an association with the first AP. Alternatively, the associated sites of the first AP are sites belonging to the R-TWT group and associated with the first AP.

[0031] The beneficial effects of the second aspect are explained in the same way as those of the first aspect, and the details are similar, so they will not be repeated here.

[0032] In one possible implementation, the first condition further includes at least one of the following: before the start time of the second SP, the associated site has data to be transmitted; before the start time of the second SP, the data transmission of the associated site has not been completed; or, before the start time of the second SP, the priority of the low-latency service of the associated site is not lower than the priority of the low-latency service of the site corresponding to the second SP.

[0033] In one possible implementation, the first condition further includes: the duration between the start time of the first SP and the start time of the second SP is less than or equal to a first threshold.

[0034] In one possible implementation, the method further includes: before or after the start time of the second SP, the associated site continues transmission. Optionally, the associated site continuing transmission includes: the associated site continuing to transmit data for low-latency services.

[0035] In one possible implementation, the method further includes: within the TXOP, the associated site transmits data for low-latency services.

[0036] In one possible implementation, within the TXOP, the associated site transmits low-latency service data, including: within the TXOP and before the start time of the second SP, the first AP transmits low-latency service data.

[0037] In one possible implementation, within the TXOP, the associated site transmits low-latency service data, including: within the TXOP, and at or after the start time of the second SP, the associated site transmits low-latency service data.

[0038] For explanations regarding the various implementation methods involved in the second aspect, please refer to the first aspect; the details are similar and will not be repeated here.

[0039] Thirdly, embodiments of this application provide a communication method applied to a second access point (AP). This method can be implemented by the second AP itself, or by components on the second AP side (such as chips, functional modules, or processing systems within the second AP). The method includes:

[0040] The second AP receives sharing information from the first AP, which indicates a first duration, which is the remaining duration of the first AP's TXOP, or a portion of the remaining duration, and the first duration is included in the first AP's first SP; the second AP transmits data within the first duration.

[0041] Wherein, the first SP satisfies the first condition, which includes: the start time of the second SP of the second AP is later than the start time of the first SP, and the start time of the second SP is earlier than the end time of the first SP.

[0042] In one possible implementation, the second AP transmits data within a first duration, including: the second AP transmits data for low-latency services within the first duration.

[0043] In one possible implementation, the first condition further includes: the duration between the start time of the first SP and the start time of the second SP is less than or equal to a first threshold.

[0044] In one possible implementation, the first duration satisfies a second condition, which includes at least one of the following: the duration between the start time of the second SP and the start time of the first duration is less than or equal to a second threshold; or, the first duration is greater than or equal to a third threshold.

[0045] In one possible implementation, the second condition also includes: after the start time of the first duration, the low-latency service of the second AP has a higher priority than the low-latency service of the first AP.

[0046] For explanations regarding the third aspect, such as beneficial effects, please refer to the first or second aspect; they will not be elaborated upon here.

[0047] Fourthly, embodiments of this application provide a communication method applied to a site. This method can be implemented by the site itself (e.g., a first AP or associated site) or by components on the site side (e.g., chips, functional modules, or processing systems within the site). The method includes:

[0048] Before the start time of the second SP, determine whether the first condition is met; if the first condition is met, do not terminate the TXOP; or, if the first condition is not met, terminate the TXOP. The first SP is the SP of the first AP, and the second SP is the SP of the second AP, which has established a Co-RTWT.

[0049] In one possible implementation, not terminating the TXOP includes: not terminating the TXOP and sharing the remaining duration of the TXOP or a portion of the remaining duration.

[0050] In one possible implementation, the method further includes: determining whether a second condition is met; if the second condition is met, sharing the remaining duration of the TXOP or a portion thereof; if the second condition is not met, not sharing the TXOP.

[0051] For an explanation of the fourth aspect, please refer to the first or second aspect; it will not be elaborated here.

[0052] Fifthly, embodiments of this application provide a communication device for performing the methods in the first aspect, the fourth aspect, or any possible implementation. The communication device includes a module for performing the methods in the first aspect, the fourth aspect, or any possible implementation.

[0053] The communication device includes a processing module and a transceiver module. The transceiver module performs the sending or receiving actions as described in the first aspect, the fourth aspect, or any possible implementation thereof, while the processing module performs the processing actions as described in the first aspect, the fourth aspect, or any possible implementation thereof. The communication device is a first access point (AP), or a chip or circuit within a first AP, or a functional module within a first AP, etc.

[0054] Sixthly, embodiments of this application provide a communication device for performing the methods in the second aspect, the fourth aspect, or any possible implementation. The communication device includes a module for performing the methods in the second aspect, the fourth aspect, or any possible implementation.

[0055] The communication device includes a processing module and a transceiver module. The transceiver module performs the sending or receiving actions as described in the second aspect, the fourth aspect, or any possible implementation. The processing module performs the processing actions as described in the second aspect, the fourth aspect, or any possible implementation. The communication device is an associated station, or a chip or circuit within an associated station, or a functional module within an associated station, etc.

[0056] In a seventh aspect, embodiments of this application provide a communication device for executing the method in the third aspect or any possible implementation. The communication device includes a module for executing the method in the third aspect or any possible implementation.

[0057] The communication device includes a processing module and a transceiver module. The transceiver module performs the sending or receiving actions as described in the third aspect or any possible implementation, while the processing module performs the processing actions as described in the third aspect or any possible implementation. This communication device is a second access point (AP), or a chip or circuit within a second AP, or a functional module within a second AP, etc.

[0058] The modules in aspects five through seven can also be replaced with units or means, etc. These modules can be implemented in software, hardware, or a combination of both.

[0059] Eighthly, embodiments of this application provide a communication device including at least one processor; wherein the processor is configured to not terminate the TXOP before the start time of a second SP, provided that a first condition is met. For example, the processor may be configured to determine whether the first condition is met. Alternatively, the processor may be configured to determine whether the condition for not terminating the TXOP is met.

[0060] In one possible implementation, the communication device further includes a transceiver for transmitting data.

[0061] In one possible implementation, the processor is also used to share the initial duration. For example, the processor could be used to control the transceiver to send the shared information.

[0062] In one possible implementation, the transceiver is also used to receive second RTWT information.

[0063] In a ninth aspect, embodiments of this application provide a communication device including at least one processor; wherein the processor is configured to not terminate the TXOP before the start time of a second SP, provided that a first condition is met. For example, the processor may be configured to determine whether the first condition is met. Alternatively, the processor may be configured to determine whether the condition for not terminating the TXOP is met.

[0064] In one possible implementation, the communication device further includes a transceiver for transmitting data.

[0065] In one possible implementation, the transceiver is also used to receive third RTWT information and fourth RTWT information.

[0066] In a tenth aspect, embodiments of this application provide a communication device including at least one processor and a transceiver; wherein the transceiver is used to receive shared information; and the processor is used to transmit data within a first duration. For example, the processor can be used to control the transceiver to transmit data within the first duration.

[0067] In one possible implementation, the transceiver is also used to send a second RTWT message.

[0068] In one possible implementation, the transceiver is also used to receive the first RTWT information.

[0069] For explanations of the terms involved in aspects eight through ten, please refer to aspects one through four; they will not be elaborated upon here.

[0070] Eleventhly, embodiments of this application provide a chip including logic circuitry; wherein the logic circuitry is configured to not terminate TXOP before the start time of a second SP, provided that a first condition is met. For example, the logic circuitry can be used to determine whether the first condition is met. Furthermore, the logic circuitry can be used to determine whether the condition for not terminating TXOP is met.

[0071] In one possible implementation, the communication device further includes an interface for transmitting data.

[0072] In one possible implementation, the logic circuitry is also used to share the initial duration. This logic circuitry can be used to control the interface output of shared information.

[0073] In one possible implementation, the interface is also used to input second RTWT information.

[0074] In a twelfth aspect, embodiments of this application provide a chip including logic circuitry; wherein the logic circuitry is configured to not terminate TXOP before the start time of a second SP, provided that a first condition is met. For example, the logic circuitry can be used to determine whether the first condition is met. Furthermore, the logic circuitry can be used to determine whether the condition for not terminating TXOP is met.

[0075] In one possible implementation, the communication device further includes an interface for transmitting data.

[0076] In one possible implementation, an interface is provided for inputting third RTWT information and fourth RTWT information.

[0077] In a thirteenth aspect, embodiments of this application provide a chip including logic circuitry and an interface; wherein the interface is used for inputting shared information; and the logic circuitry is used for transmitting data within a first duration. For example, the logic circuitry can be used to control the interface to transmit data within the first duration.

[0078] In one possible implementation, the interface is also used to output a second RTWT message.

[0079] In one possible implementation, the interface is also used to input the first RTWT information.

[0080] For explanations of the terms involved in aspects eleven through thirteen, please refer to aspects one through four; they will not be elaborated upon here.

[0081] In a fourteenth aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer, causes the methods shown in any of the first to fourth aspects or any possible implementation thereof to be executed.

[0082] This computer program can also be called an instruction, or computer instruction, etc. That is, a computer program can be replaced by an instruction or computer instruction.

[0083] In a fifteenth aspect, embodiments of this application provide a computer program product that, when run on a computer, causes the methods in any of the first to fourth aspects or any possible implementations described above to be executed.

[0084] In a sixteenth aspect, embodiments of this application provide a communication system comprising at least two of a first AP, a second AP, and a non-AP STA. The first AP may be an apparatus as provided in the fifth, eighth, or eleventh aspects; the non-AP STA may be an apparatus as provided in the sixth, ninth, or twelfth aspects; and the second AP may be an apparatus as provided in the seventh, tenth, or thirteenth aspects. The first AP may be used to implement the methods in the first or fourth aspects or any possible implementations described above; the non-AP STA may be used to implement the methods in the second or fourth aspects or any possible implementations described above; and the second AP may be used to implement the methods in the third aspect or any possible implementations described above. Attached Figure Description

[0085] Figure 1a This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0086] Figure 1b This is a schematic diagram of another architecture of the communication system provided in the embodiments of this application;

[0087] Figure 2 This is a schematic diagram of the main channel and non-main channel provided in the embodiments of this application;

[0088] Figure 3 This is a schematic diagram of the R-TWT mechanism provided in the embodiments of this application;

[0089] Figure 4 This is a schematic diagram of the format of a TWT element provided in an embodiment of this application;

[0090] Figure 5 This is a schematic diagram of the coordinated time division multiple access (Co-TDMA) mechanism provided in the embodiments of this application;

[0091] Figure 6 This is a schematic diagram of the format of the multi-user request to send (MU-RTS) transmission opportunity sharing (TXOP) trigger frame provided in the embodiments of this application;

[0092] Figure 7 This is a schematic diagram of the Co-RTWT SP overlap provided in the embodiments of this application;

[0093] Figure 8 This is a flowchart illustrating the communication method provided in an embodiment of this application;

[0094] Figure 9 This is a schematic diagram of R-TWT SP overlap provided in an embodiment of this application;

[0095] Figure 10 This is a flowchart illustrating the communication method provided in an embodiment of this application;

[0096] Figure 11 This is a flowchart illustrating the communication method provided in an embodiment of this application;

[0097] Figure 12a and Figure 12b This is a schematic diagram of the first AP sharing TXOP when Co-RTWT SPs overlap, provided in an embodiment of this application;

[0098] Figure 13 This is a schematic diagram of a communication device provided in an embodiment of this application;

[0099] Figure 14 This is another schematic diagram of the communication device provided in the embodiments of this application;

[0100] Figure 15 This is a schematic diagram of the chip provided in an embodiment of this application. Detailed Implementation

[0101] To facilitate understanding of the technical solution of this application, the application will be further described below with reference to the accompanying drawings.

[0102] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are used only to distinguish different objects and not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0103] In this application, "at least one (item)" means one or more, "more than" means two or more, and "at least two (items)" means two or three or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. "Or" indicates that two relationships can exist, such as only A or only B exists; when A and B are not mutually exclusive, it can also represent three relationships, such as only A, only B, or both A and B exist simultaneously. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these 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".

[0104] In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which can include direct transmission via the air interface or indirect transmission via the air interface from other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which can include direct reception from YY via the air interface or indirect reception from YY via the air interface from other units or modules. "Send" can also be understood as the "output" of a chip interface, and "receive" can also be understood as the "input" of a chip interface. In other words, sending and receiving can occur between devices, such as between devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within a device via a bus, trace, or interface.

[0105] The following describes the communication system involved in this application.

[0106] The technical solutions provided in this application can be applied to wireless local area network (WLAN) systems. For example, the methods provided in this application can be applied to the IEEE 802.11 series standards, such as 802.11a / b / g, 802.11bf, 802.11az, 802.11bk, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn, or next-generation standards. Other examples include 802.11ad, 802.11ay, 802.11bq, or next-generation standards, which will not be listed here. The technical solutions provided in this application can also be applied to wireless personal area networks (WPANs) based on ultra-wideband (UWB) technology. The technical solutions provided in this application can also be applied to integrated millimeter wave (IMMW) technology. The method provided in this application embodiment can also be applied to the IEEE 802.15 series standards, such as the 802.15.4a, 802.15.4z, or 802.15.4ab standards, or a future generation of UWB WPAN standards. The method provided in this application embodiment can also be applied to the StarFlash standard. The technical solution provided in this application embodiment can also be applied to the following communication systems, for example, Internet of Things (IoT) systems, Vehicle-to-X (V2X) systems (where X can represent anything), Device-to-Device (D2D) systems, Narrowband Internet of Things (NB-IoT) systems, Long Term Evolution (LTE) systems, 5th Generation (5G) communication systems, or next-generation communication systems, etc. V2X can include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-network (V2N) communication.

[0107] WLAN systems can provide high-speed, low-latency transmission. As WLAN application scenarios continue to evolve, WLAN systems will be applied to more scenarios or industries, such as the Internet of Things industry, the Internet of Vehicles industry, the banking industry, enterprise offices, stadiums and exhibition halls, concert halls, hotel rooms, dormitories, hospital wards, classrooms, shopping malls, squares, streets, production workshops and warehouses, etc. Of course, devices that support WLAN communication or sensing (such as access points or sites) can be sensor nodes in smart cities (such as smart water meters, smart electricity meters, and smart air monitoring nodes), smart devices in smart homes (such as smart cameras, projectors, displays, televisions, speakers, refrigerators, and washing machines), nodes in the Internet of Things (IoT), entertainment terminals (such as wearable devices for augmented reality (AR) and virtual reality (VR), smart devices in smart offices (such as printers, projectors, loudspeakers, and speakers), vehicle-to-everything (V2X) devices, infrastructure in daily life scenarios (such as vending machines, self-service navigation kiosks in supermarkets, self-service checkout machines, and self-service ordering machines), and equipment in large sports and music venues.

[0108] Although the embodiments of this application primarily use WLAN as an example, especially networks applied to the IEEE 802.11 series of standards, the various aspects involved in the embodiments of this application can be extended to other networks employing various standards or protocols. For example, Bluetooth, high-performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, mainly used in Europe), and wide area networks (WANs) or other networks now known or to be developed in the future.

[0109] In one possible implementation, the method provided in this application embodiment can be implemented by a communication device in a communication system. For example, the communication device can be an access point (AP) or a non-access point station (non-AP STA). Alternatively, the communication device can be a chip or circuit in the AP, or a functional module within the AP. Another example is that the communication device is a chip or circuit in a non-AP STA, or a functional module within a non-AP STA. The method provided in this application embodiment can be applied to, but is not limited to, single-user uplink / downlink transmission and multi-user uplink / downlink transmission.

[0110] An access point is a device with wireless communication capabilities, supporting communication or sensing using WLAN protocols. It has the function of communicating or sensing with other devices in the WLAN network (such as non-AP STAs or other access points), and can also have the function of communicating or sensing with other devices. Alternatively, 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. In a WLAN system, an access point can be called an access point site (AP STA). In the embodiments of this application, the AP is a device that provides services to non-AP STAs and can support 802.11 series protocols or subsequent protocols. For example, an access point can be an access point for terminals (such as mobile phones) to enter a wired (or wireless) network, mainly deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters; it can also be deployed outdoors. Another example is that an AP can be a communication server, router, switch, bridge, or other communication entity; an AP can include various forms of macro base stations, micro base stations, repeaters, etc. Yet another example is that an AP can belong to a multi-link device (MLD) or a co-located AP, etc.

[0111] A non-AP STA is a device with wireless communication capabilities that supports communication or sensing using WLAN protocols. It has the ability to communicate or sense other non-AP STAs or access points within a WLAN network. For example, a non-AP STA is any user communication device that allows a user to communicate or sense with an AP and thus with the WLAN. For instance, a non-AP STA can be a wireless communication chip, a wireless sensor, or a wireless communication terminal, and can also be referred to as a user. Furthermore, a non-AP STA 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, or a computer supporting Wi-Fi communication. Additionally, a non-AP STA can also be a non-AP STA belonging to an MLD (Multi-Level Display) or a co-located STA.

[0112] A multi-link device comprises multiple affiliated sites, which can be physical or logical sites. Each site can operate on a link, a frequency band, or a channel, etc. The affiliated sites shown here can be APs or non-AP STAs.

[0113] In the embodiments of this application, STA includes at least one of AP or non-AP STA. That is, both AP and non-AP STA can be referred to as STA. For example, the associated site of AP can be a non-AP STA, and the associated site of non-AP STA can be AP. The following description of STA also applies to at least one of AP or non-AP STA.

[0114] The communication system provided in this application includes at least one AP / AP MLD and at least one non-AP STA / non-AP MLD.

[0115] Figure 1a This is a schematic diagram of an architecture of a communication system provided in an embodiment of this application. The communication system includes one or more access points (APs) and one or more non-AP STAs. Figure 1a The diagram illustrates an access point such as an AP, and two sites such as non-AP STA1 and non-AP STA2. Exemplarily, the method provided in this application embodiment can be applied to data communication between an AP and one or more non-AP STAs (e.g.,...). Figure 1a The communication shown is between the AP and non-AP STA1, or between AP1 and non-AP STA1, non-AP STA2, or between APs, or between non-AP STAs.

[0116] Figure 1a The example of a non-AP STA (phone) and an AP (router) is provided and is not intended to limit the types of APs and non-AP STAs in this application. Furthermore, Figure 1a Only one AP and two non-APSTAs are shown as an example, but the number of APs or non-APSTAs may be more or less, and this application embodiment does not limit this.

[0117] A WLAN consists of one or more Basic Service Sets (BSSs). The concept of a BSS is similar to that of a cell, therefore BSS and cell can be used interchangeably. Each BSS typically consists of one Access Point (AP) and one or more non-AP STAs. Sites located within the same BSS are called local BSSs (or local cells), while sites located in different BSSs are called external BSSs (or external cells). An AP located within the same BSS as any non-AP STA can be called an associated AP of that non-AP STA, and the non-AP STA is called an associated STA of that AP. Optionally, non-AP STAs are allowed to communicate with each other, such as point-to-point (P2P) communication. Generally, all uplink traffic is sent from non-AP STAs to the AP, and all downlink traffic is sent from the AP to non-AP STAs.

[0118] Figure 1b This is a schematic diagram of another architecture of the communication system provided in the embodiments of this application. For example... Figure 1b As shown, the communication system includes two BSSs, namely BSS1 and BSS2. In BSS1, non-AP STA1 is associated with AP1, and in BSS2, non-AP STA2 is associated with AP2. Non-AP STA1 in BSS1 is within the coverage area of ​​BSS2, thus overlapping with BSS2. Non-AP STA2 in BSS2 is within the coverage area of ​​BSS1, thus overlapping with BSS1.

[0119] For ease of description, the following explanation will use the data transmission process between AP1 and AP2, as well as the data transmission process between AP1 and non-AP STA1, as examples.

[0120] In this application, AP1 can also be referred to as the first AP, AP2 as the second AP, non-AP STA1 as the first non-AP STA, and non-AP STA2 as the second non-AP STA.

[0121] The following describes the terms used in the embodiments of this application.

[0122] 1. Main channel and non-main channel

[0123] The primary channel (PC) is the common channel of operation for all stations that members of the BSS. Optionally, the primary channel is a 20 MHz channel. The maximum bandwidth that a station in the BSS can transmit and receive with can be called the primary operating bandwidth of that station, and the primary operating channel is the operating channel that can accommodate the primary operating bandwidth. For example, assuming the total bandwidth of the BSS is 160 MHz, and the primary operating bandwidth of a non-AP within the BSS is also 160 MHz (i.e., the total bandwidth of the BSS), then the primary operating channel of that non-AP is the operating channel that can accommodate the primary operating bandwidth (i.e., 160 MHz, the total bandwidth of the BSS). Optionally, the bandwidth of the primary operating channel covers the bandwidth of the primary channel.

[0124] Non-primary channels refer to channels other than primary channels that can be operated by stations in a BSS. In this application embodiment, a channel can also be referred to as a medium, and this application embodiment does not limit this terminology.

[0125] Figure 2 This is a schematic diagram of the main channel and non-main channel provided in the embodiments of this application. For example... Figure 2 As shown, taking the maximum bandwidth used by a site in the BSS as an example of 160MHz, the 160MHz can be divided into 8 sub-channels of 20MHz each.

[0126] Optionally, the AP determines which sub-channel is the primary channel based on the BSS configuration information, and the remaining sub-channels are non-primary channels. For example, Figure 2 The third sub-channel is the primary channel, while the other sub-channels are non-primary channels 1 to 7. Optionally, a channel can also be understood as its corresponding bandwidth.

[0127] 2. Principle of Network Allocation Vector (NAV)

[0128] The physical layer packets transmitted by a station (such as an AP or non-AP STA) over the air interface are called Physical Layer Protocol Data Units (PPDUs). A PPDU can be considered as a packet sent by each station through the physical layer to the air interface. A PPDU can be an air interface data packet. A PPDU includes a preamble and a payload. The preamble or payload of the PPDU may contain NAV indication information or the NAV itself. NAV is a time length (or countdown duration) indicating the remaining time the sending station needs to occupy the channel from the end of the PPDU. Optionally, the NAV timer is a countdown timer. When the NAV timer value is greater than 0, it indicates that the virtual carrier sensing result of the channel is busy. When the NAV timer value is equal to 0, it indicates that the virtual carrier sensing result of the channel is idle.

[0129] 3. Principles of WLAN channel access

[0130] Channel access refers to the process by which a station in a network accesses the main channel and obtains the right to use it. Since WLANs operate in unlicensed spectrum, various wireless systems can use this spectrum resource openly and free of charge, thus requiring contention-based channel access. IEEE 802.11 specifies that stations in WLANs should use a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism. The CSMA / CA mechanism uses a listen-before-talk (LBT) approach to access the channel; that is, a station wishing to acquire the right to use the channel for frame exchange must first listen to the channel's availability level. Only when the channel is idle and certain conditions are met can the station acquire the right to use it. When access is successful, the station obtains a transmission opportunity (TXOP), and this station is called the holder of the acquired TXOP.

[0131] 4. The principle of transmission opportunity (TXOP)

[0132] For WLAN systems, stations can transmit data in units of PPDUs. A station may need to transmit multiple PPDUs to complete a single service interaction. Before the introduction of TXOP, stations had to back off before each PPDU transmission, resulting in low transmission efficiency. The introduction of TXOP allows stations that have completed backoff to efficiently transmit multiple PPDUs.

[0133] The period of time gained after a station completes its backoff is called the TXOP (Turn-Off Period). During the TXOP, adjacent PPDUs (PPDUs received and transmitted by the station, or PPDUs transmitted and received by the station) can be spaced apart for a certain duration; no backoff is required between adjacent PPDUs. This interval between adjacent PPDUs can include, but is not limited to, the short interframe space (SIFS). A station can declare the length of the TXOP at the beginning so that other stations can resolve this length and avoid competing for the channel during that period.

[0134] The station that acquires a TXOP by avoiding contention is called the TXOP holder (i.e., the station that sends the first frame of the TXOP). The station that communicates with the TXOP holder within the TXOP is called the TXOP responder (i.e., the station other than the TXOP holder that participates in the transmission within the TXOP). Both the TXOP holder and the TXOP responder are participants in the TXOP.

[0135] The mechanisms involved in the embodiments of this application are described below. The R-TWT mechanism shown below can also be referred to as R-TWT operation, and the Co-RTWT mechanism can also be referred to as Co-RTWT operation.

[0136] 5. Restricted target wakeup time (R-TWT) mechanism

[0137] The TWT mechanism refers to limiting the time a station is in the wake-up state through TWT. In other words, it schedules multiple stations to be woken up from the energy-saving state at different times to work, in order to reduce conflicts between nodes and reduce the wake-up time of energy-saving nodes.

[0138] After two sites successfully negotiate a TWT (Trusted WT) mechanism, a TWT operation is established, including individual TWTs and broadcast TWTs (B-TWTs). For example, the TWT requester sends a request to the TWT responder to establish a TWT. Optionally, the TWT requester suggests parameters related to the TWT operation, and the TWT responder determines these parameters. These parameters include, but are not limited to, at least one of the following: whether the TWT operation was successfully established, the number of Service Periods (SPs) included in the TWT, the start time of the first TWT service period (SP), and the period of the TWT SP. After both parties successfully establish the TWT, the TWT requester can enter a power-saving mode (doze state) until the first TWT SP begins. Within the TWT SP, the TWT requester and TWT responder interact with data. That is, the TWT requester and TWT responder negotiate a time for data transmission within that agreed time frame; thus, the TWT requester can enter a doze state outside the negotiated time frame to save energy.

[0139] A site where a TWT operation has been established is called an associated site of that TWT. A B-TWT is also called a B-TWT schedule, and multiple associated sites of the same B-TWT constitute a B-TWT group. A B-TWT group contains one TWT scheduling AP and several TWT scheduled STAs.

[0140] R-TWT is a new mechanism for ensuring low-latency services, derived from the existing broadcast TWT in IEEE 802.11ax. In the IEEE 802.11be standard, many real-time applications exist in non-AP EHT STAs, and these applications have very strict latency requirements. The R-TWT mechanism was proposed based on this requirement.

[0141] An Access Point (AP) broadcasts one or more R-TWT SPs (e.g., indicated by R-TWT information) via beacon frames or probe response frames. STAs within the BSS containing the AP receive these beacon frames or probe response frames. When a STA within the BSS receives the "active" R-TWT SP information broadcast by the AP, if the STA's R-TWT support parameter (e.g., dot11RestrictedTWTPtionImplemented) is set to true, then the STA must end its TXOP before the R-TWT SP start time. If the STA backs off to 0 at time t0 before the R-TWT SP start time, and the time between t0 and the R-TWT SP start time is insufficient to complete a frame exchange, then the STA abandons (or delays) this transmission, and can back off again if possible. The STA's actions can be considered as protecting the R-TWT SP, protecting R-TWT scheduling, protecting R-TWT information, or respecting the R-TWT information. Alternatively, the above operation is considered to be the STA completing the TXOP truncation protection operation.

[0142] The beacon frame or probe response frame may also include a quiet interval indication, the start time of which is the same as the R-TWT SP start time. Alternatively, the AP can set a quiet interval in the beacon frame or probe response frame that is aligned with the R-TWT SP start time. Optionally, the duration of the quiet interval is a time unit (TU) or milliseconds (ms). 1 TU = 1024 microseconds (µs). For example, the duration of the quiet interval is 1 millisecond (ms). STAs belonging to this R-TWT group (grouped by broadcast TWT ID) can ignore the aforementioned quiet interval and thus compete for the channel after the R-TWT SP starts. STAs not belonging to this R-TWT group can ignore or not ignore the aforementioned quiet interval, the purpose of which is to reduce the number of stations competing for the channel within the BSS, thereby increasing the probability of STAs with low-latency service requirements winning the channel.

[0143] Figure 3 This is a schematic diagram of the R-TWT mechanism provided in the embodiments of this application. For example... Figure 3 As shown, the AP broadcasts the R-TWT SP via a beacon frame. If the beacon frame includes R-TWT information, and if this R-TWT information can indicate the R-TWT SP start time, and other information indicated by this R-TWT information, please refer to [reference needed]. Figure 4Non-AP STA 1, belonging to the R-TWT group, can compete for the channel at the start time of R-TWT SP and thereafter, thereby accessing the channel and transmitting data frames. Non-AP STA 2, not belonging to the R-TWT group, remains silent for a period of time (e.g., 1ms) at the start time of R-TWT SP, thus ensuring that non-AP STA 1 can compete for the channel first. Optionally, traditional sites may remain silent for a period of time at the start time of R-TWT SP.

[0144] Figure 4 This is a schematic diagram of the format of a TWT element provided in an embodiment of this application. For example... Figure 4 As shown, the TWT element includes at least one of the following: element identifier (element ID), length, and control or TWT parameter information field. The control field includes at least one of the following: No Data Frame Paging Indicator (NDPpaging indicator), Responder PM Mode, Negotiation Type, TWT InformationFrame Disabled, Wake-up Duration Unit, Link ID Bitmap Present, or Aligned. For a broadcast TWT, the TWT parameter information field includes one or more broadcast TWT parameter sets. Figure 4 The format of broadcast TWT parameter set 1 is shown as an example. Figure 4 The order or length of the fields shown are merely examples and are not intended to limit the embodiments of this application.

[0145] like Figure 4As shown, the broadcast TWT parameter set fields include at least one of the following: request type, target waketime (TWT), nominal minimum TWT wake-up duration, TWT wakeinterval mantissa, broadcast TWT info, or restricted TWT traffic info (optional). The request type field includes at least one of the following: TWT request, TWT setup command, trigger, last broadcast parameter set, flow type, broadcast TWT recommendation, TWT wakeinterval exponent, or aligned. The broadcast TWT information field includes at least one of the following: limiting TWT service information presence (R-TWT trafficinfopresent), limiting TWT scheduling information (R-TWT scheduleinfo), broadcast TWT ID, or broadcast TWT persistence. The R-TWT service information field includes at least one of the following: service information control (trafficinfocontrol), R-TWT downlink traffic ID bitmap (R-TWT DL TID bitmap), or R-TWT uplink traffic ID bitmap (R-TWT uplink traffic ID bitmap, R-TWT UL TID bitmap). The service information control field includes at least one of the following: downlink TID bitmap valid (DL TID bitmapvalid) or uplink TID bitmap valid (UL TID bitmapvalid).

[0146] The R-TWT information may be carried in the TWT element. The TWT parameter information includes one or more broadcast TWT parameter sets. The broadcast TWT recommendation field in the request type field of the broadcast TWT parameter set field may be used to indicate the TWT type specified by the broadcast TWT parameter set. For example, a value of 4 for the broadcast TWT setup field indicates that the broadcast TWT parameter set corresponds to an R-TWT. This type of request is introduced in IEEE 802.11be, and thus cannot be understood by legacy stations (legacy STAs).

[0147] If a broadcast TWT parameter set corresponds to an R-TWT, a restricted TWT traffic info present field may be included in the broadcast TWT info field in the TWT element. Optionally, the restricted TWT traffic info present field occupies 1 bit, a value of 1 for the bit indicates that the R-TWT traffic information field is included in the TWT element, and a value of 0 for the bit indicates that the R-TWT traffic information field is not included in the TWT element. The R-TWT traffic information field is used by non-AP STAs and APs to negotiate uplink / downlink R-TWT TIDs and non-R-TWT TIDs.

[0148] The restricted TWT schedule info field indicates scheduling information of the R-TWT group. Different values of the restricted TWT schedule info field may respectively indicate the status (idle or active) of the R-TWT scheduling information, whether new members are admitted, whether it belongs to the local BSS, and the like. Table 1 exemplarily shows the values of the restricted TWT schedule info field and their meanings, and the relationship between each value and the meaning shown in Table 1 is only an example, and is not intended to limit the embodiments of this application.

[0149] The broadcast TWT ID field indicates the identification number of the TWT group, and a binary tuple <B-TWT ID, MAC address> is used to uniquely identify one R-TWT schedule, where the MAC address is the MAC address of the station transmitting the TWT information. R-TWT is a subtype of B-TWT.

[0150] Table 1 Values of the restricted TWT schedule info field and their meanings

[0151]

[0152]

[0153] As shown in Table 1, a value greater than 0 in the R-TWT scheduling information field indicates an active R-TWT schedule. An active R-TWT schedule can also indicate an active R-TWT SP. An idle R-TWT schedule can also indicate an idle R-TWT SP.

[0154] It is understood that the embodiments of this application are illustrated using "elements" and "fields" as examples, without specifically distinguishing between "fields" or "subfields". Therefore, this should not be construed as a limitation on the embodiments of this application.

[0155] 6. Cooperatively Limited Target Wake-up Time (Co-RTWT)

[0156] In multi-AP network scenarios, each BSS has multiple neighboring BSSs. The coverage areas (e.g., transmission coverage) of these neighboring BSSs overlap with the coverage area of ​​the local BSS; therefore, these neighboring BSSs are also called OBSSs. Before the Co-RTWT mechanism was proposed, the R-TWT information broadcast by each BSS was only received and followed by the stations within that BSS. Even if stations in other OBSSs could listen for or detect it, they might not receive or follow it. This could result in OBSS stations failing to end their transmissions (i.e., end their TXOPs) before the R-TWT SP start time broadcast by their local BSS, leading to low efficiency of the R-TWT mechanism and difficulty in improving network performance. To address these issues, the Co-RTWT mechanism was proposed, effectively improving the protection of each other's R-TWT by participating BSSs and the efficiency of the R-TWT mechanism itself.

[0157] The Co-RTWT mechanism is based on the R-TWT mechanism. The difference between Co-RTWT and R-TWT is that Co-RTWT aims to help OBSS sites compete for channels more quickly, facilitating the transmission of service data corresponding to the R-TWT. For example, in Co-RTWT, an AP within each of multiple BSSs that are each other's OBSSs will receive R-TWT information broadcast by APs in other OBSSs and then broadcast this R-TWT information to its own BSS sites. Non-AP STAs receiving R-TWT information can follow the operating rules of the R-TWT mechanism, such as needing to close their TXOPs before the start time of an "active" R-TWT SP (but not necessarily before the start time of an idle R-TWT SP).

[0158] For example, in a Co-RTWT mechanism, BSS1 refers to a BSS participating in the Co-RTWT mechanism, and a Co-BSS (CoBSS) refers to another BSS participating in the Co-RTWT mechanism. The AP in the Co BSS can send the R-TWT information of the Co BSS to the AP in BSS1, requesting BSS1 to respect the Co-RTWT information. The AP in BSS1 receives the R-TWT information from other Co-BSSs (i.e., Co BSSs), broadcasts the R-TWT information within its own BSS, and requests stations within its BSS to respect (or protect) the R-TWT information. Stations in BSS1 configure higher priority for the specified service transmission corresponding to the R-TWT of the Co BSS within the R-TWT SP. For example, stations in BSS1 complete the TXOP truncation protection operation at the start time of the R-TWT SP.

[0159] The APs of BSS1 and Co BSS can establish a cooperative relationship through processes such as neighbor node discovery, operational capabilities, and operational parameter negotiation to establish a Co-RTWT cooperative relationship. This facilitates subsequent channel access protection for the R-TWT scheduling by coordinating R-TWT scheduling information. The specific method by which BSS1 and Co BSS establish Co-RTWT is not limited in the embodiments of this application.

[0160] Optionally, an AP that implements Co-RTWT operations (e.g., the parameter dot11CoRTwtOptionImplemented is true) can broadcast a Co-RTWT negotiation frame and its associated Co-RTWT parameters via a management frame. Optionally, a Co-RTWT requesting AP can also request a Co-RTWT responding AP to extend its R-TWT scheduling protection via a unicast management frame used to initiate negotiation. Upon receiving the aforementioned unicast management frame, the Co-RTWT responding AP can establish a Co-RTWT agreement, extending the R-TWT scheduling protection protection of the Co-RTWT requesting AP.

[0161] When BSS1 extends protection for the R-TWT scheduling of the Co BSS, BSS1 will ensure that its TXOP ends before the corresponding R-TWT SP start time of the Co BSS. For example, when BSS1 includes at least one site supporting R-TWT, BSS1 will broadcast the R-TWT information of the Co BSS via beacon frames. Thus, sites in BSS1 supporting R-TWT can follow this R-TWT information, such as ending their BSS1 TXOP before the R-TWT start time, to provide channel access protection for the R-TWT start time. As another example, if none of the sites in BSS1 belong to the Co BSS's R-TWT group, then the sites in BSS1 can disregard the silence interval. For example, sites in BSS1 can wait for the silence interval (e.g., 1ms) before competing for the channel, thus reducing the number of sites competing for the channel and increasing the probability that sites with low-latency services can successfully compete for the channel.

[0162] 7. Coordinated Time Division Multiple Access (Co-TDMA) Mechanism

[0163] Based on the Triggered TXOP sharing (TXS) mechanism, a Co-TDMA mechanism is proposed to realize TXOP sharing among multiple adjacent APs. In the Co-TDMA mechanism, TXOP holders (such as APs) can declare their willingness to share a portion of the TXOP duration via broadcast or unicast control frames and poll their neighboring cooperating APs to see if they need to share it. When polled, neighboring APs should respond and indicate whether they wish to participate in the shared TXOP.

[0164] Figure 5 This is a schematic diagram of the Co-TDMA mechanism provided in the embodiments of this application. Figure 5 An exemplary diagram is shown, comprising a polling phase, a TXOP allocation phase, and a TXOP return phase.

[0165] During the polling phase, a Co-TDMA sharing AP (such as AP1) can announce its intention to share a portion of the TXOP time allocation via an initial control frame (ICF). Optionally, AP1 can send an ICF during the TXOP period. The ICF polls one or more APs to determine the polled AP's intention within the TXOP, i.e., whether the polled AP desires time allocation through the Co-TDMA sharing AP. Optionally, the duration field of the ICF is set to one SIFS plus the time required for the polled AP to respond to the transmission request. When responding to the ICF, the polled AP indicates its intention to receive time allocation from the Co-TDMA sharing AP in the current TXOP; failure to respond is considered as not receiving. Figure 5 As shown, the polled APs include AP2 and AP3. AP2 does not receive time allocations from AP1 in the current TXOP, while AP3 receives time allocations from AP1 in the current TXOP.

[0166] During the TXOP allocation phase, the Co-TDMA sharing AP (AP1) can allocate a portion of its allocated time to an AP (such as AP3) that wishes to receive AP1's time allocation intent by sending a multi-user request to send (MU-RTS) TXS trigger frame within its acquired TXOP. After AP3 receives the MU-RTS TXS trigger frame from the Co-TDMA sharing AP (which contains the user information field and the allocated duration field of the shared AP), AP3 can send and / or receive one or more PPDUs within the allocated duration.

[0167] During the TXOP return phase, if there is any remaining time after the allocation, AP3 can return the remaining TXOP to AP1.

[0168] Figure 6 This is a schematic diagram of the format of a multi-user request to send (MU-RTS) TXS trigger frame provided in an embodiment of this application. The MU-RTS TXS trigger frame is a variant of the MU-RTS trigger frame. Before the Co-RTWT mechanism was proposed, an AP could allocate a portion of its TXOP to an associated STA. The Co-RTWT mechanism can reuse this MU-RTS TXS trigger frame, allowing AP1 to allocate a portion of its TXOP duration to other APs (such as...). Figure 6 AP3 (as shown).

[0169] like Figure 6 As shown, the MU-RTS TXS trigger frame includes at least one of the following: frame control, duration, receiver address (RA), transmitter address (TA), common information, user information list, padding, or frame check sequence (FCS). The common information field includes the triggered TXOP sharing mode field. The user information list field includes one or more user information fields.

[0170] For example, the triggered TXOP sharing mode field occupies 2 bits. The relationship between the values ​​and meanings of this triggered TXOP sharing mode field is illustrated in Table 2, which demonstrates the relationship between values ​​and meanings. It is understood that the relationship between values ​​and meanings shown in Table 2 is merely an example and is not intended to limit the embodiments of this application. As shown in Table 2, when the triggered TXOP sharing mode field is set to a non-zero value, the MU-RTS triggered frame is called an MU-RTS TXS triggered frame. The stations shown in Table 2 include non-AP STAs or APs.

[0171] Table 2 defines the fields for triggering the TXOP sharing mode.

[0172]

[0173] like Figure 6 As shown, the user information field can include two variants of user information: a first variant user information field and a second variant user information field. For example, the first variant user information field can be an HE variant user information field, and the second variant user information field can be an EHT variant user information field or a UHR variant user information field. The first variant user information field includes at least one of the following: association ID (AID)12, resource unit (RU) allocation, or allocation duration. The second variant user information field includes at least one of the following: AID12, RU allocation, allocation duration, and primary-secondary (PS)160.

[0174] For example, if the channel bandwidth of the MU-RTS TXS trigger frame is 320MHz or the channel bandwidth is punctured, then the second variant of the user information field is used. Otherwise, the AP can choose to use either variant of the user information field. Sites allocated a portion of the TXOP duration can use the identifier field (e.g., ...) in the user information field. Figure 6 The association ID (AID) shown in Figure 12) is used for identification. The resource unit (RU) allocation field indicates the RU used for transmitting clear-to-send (CTS) frames. The allocation duration field specifies the allocated TXOP time, such as 16 microseconds. The PS160 field set to 1 indicates a channel bandwidth of 320MHz.

[0175] Figure 6 The format of the MU-RTS TXS trigger frame shown is merely an example and is not intended to limit the embodiments of this application.

[0176] The explanations of the various terms or mechanisms above also apply to the following text, and will not be repeated here.

[0177] The following describes the methods involved in the embodiments of this application.

[0178] Figure 7 This is a schematic diagram illustrating the overlap of Co-RTWT SPs provided in an embodiment of this application. For example... Figure 7 As shown, a Co-RTWT cooperation relationship is established between BSS1 and BSS2. Alternatively, a Co-RTWT operation is established between BSS1 and BSS2. Or, a Co-RTWT mechanism is established between BSS1 and BSS2. Alternatively, a Co-RTWT cooperation relationship (or Co-RTWT operation, or Co-RTWT mechanism) is established between AP1 and AP2. AP1 is an AP in BSS1, and AP2 is an AP in BSS2. The method for establishing Co-RTWT between AP1 and AP2 is not limited in the embodiments of this application.

[0179] There is an overlap between the R-TWT SPs of these two BSSs, that is, the R-TWT SP start time of AP 1 is earlier than the R-TWT SP start time of AP 2, and the R-TWT SP start time of AP 2 is earlier than the R-TWT SP end time of AP 1.

[0180] At the start time of AP 2's R-TWT SP, not only does AP 1 need to truncate its TXOP to protect BSS2's channel access, but BSS2 also needs to access the channel. This will lead to the following problems:

[0181] (1) Low channel utilization: Because AP1's TXOP is truncated, its data transmission time is shortened, and AP1 may not be able to transmit its low-latency service data, resulting in low channel utilization due to channel resource fragmentation.

[0182] (2) Low channel access efficiency: Since AP 2 needs to compete for channel access at the start time of AP 2's R-TWT SP, channel access collisions may lead to low channel access efficiency. For example, if both the stations in BSS1 and BSS2 start competing for the channel at the start time of AP 2's R-TWT SP, the probability of channel collisions will be high, resulting in low channel access efficiency.

[0183] Therefore, embodiments of this application provide a communication method and apparatus that can effectively improve channel utilization and enhance the service carrying capacity of AP1. For example, it can improve AP1's ability to carry low-latency services. Optionally, the method provided in embodiments of this application can also improve the channel access efficiency of AP2 and enhance AP2's ability to carry low-latency services.

[0184] In this embodiment, the R-TWT SP can also be called a Co-RTWT SP, or simply SP. That is, SP, R-TWT SP, and Co-RTWT SP are interchangeable. For simplicity, the methods described below will all use SP as an example. The start time shown below can also be called the start moment, and the end time can also be called the end moment.

[0185] Figure 8 This is a flowchart illustrating the communication method provided in an embodiment of this application. This method can be applied to a communication device, a chip or circuit within the communication device, or a functional module within the communication device. For ease of description, the following description uses a first AP and a second AP as examples to illustrate the communication method. The description of the first AP and the second AP is given above and will not be repeated here. Figure 8 As shown, the method includes:

[0186] 801. The first AP and the second AP establish Co-RTWT.

[0187] Alternatively, a Co-RTWT cooperation relationship (or Co-RTWT operation, or Co-RTWT mechanism) is established between the first AP and the second AP. Alternatively, a Co-RTWT cooperation relationship is established between BSS1 and BSS2. Alternatively, a Co-RTWT operation is established between BSS1 and BSS2. Alternatively, a Co-RTWT mechanism is established between BSS1 and BSS2. The first AP is an AP within BSS1, and the second AP is an AP within BSS2.

[0188] The first AP and the second AP establish a Co-RTWT in the following ways: the first AP and the second AP establish a Co-RTWT through processes such as neighbor node discovery, working capacity, and working parameter negotiation. Optionally, after establishing a Co-RTWT, the second AP sends second RTWT information to the first AP. The first AP sends first RTWT information to the second AP.

[0189] The first AP and the second AP establish a Co-RTWT in the following ways: the first AP and the second AP establish a Co-RTWT by exchanging their respective RTWT information. For example, the second AP sends second RTWT information to the first AP. Or, the first AP sends first RTWT information to the second AP. The specific method by which the first AP and the second AP establish a Co-RTWT is not limited in the embodiments of this application.

[0190] The following describes embodiments of this application involving first RTWT information and second RTWT information. Figure 8 The interaction order of the first RTWT information and the second RTWT information shown is merely an example and is not intended to limit the embodiments of this application.

[0191] In one possible implementation, the second AP sends second RTWT information to the first AP, and the first AP receives the second RTWT information.

[0192] The second RTWT information is used to indicate the service priority corresponding to the second SP or at least one of the second SPs. The second SP is the R-TWT SP of the second AP. The second RTWT information includes at least one of the following: the start time of the second SP, the duration of the second SP, the period of the second SP, or the service priority corresponding to the second SP. For example, the second RTWT information includes the start time of the second SP. Or, the second RTWT information includes the start time of the second SP and the duration of the second SP. Or, the second RTWT information includes the start time of the second SP, the duration of the second SP, and the service priority corresponding to the second SP. The contents of the second RTWT information will not be listed here one by one.

[0193] Optionally, the second RTWT information can be used to indicate active R-TWT scheduling. Alternatively, the second R-TWT information can be used by the second AP to indicate to the first AP one or more active R-TWT schedulings of the second AP. An R-TWT scheduling may include one or more R-TWT SPs (also simply referred to as SPs).

[0194] Typically, an R-TWT is a set of one or more SPs, so the second RTWT information can indicate one or more SPs. The difference between the start times of two temporally adjacent SPs is the period interval of that SP, and the duration of that SP is the duration of that SP.

[0195] The second RTWT information can be carried in a TWT element, or in other types of elements or fields; this application does not limit this. The following description uses the example of the second RTWT information being carried in a TWT element.

[0196] For example, the start time of the second SP is carried in the TWT field of the TWT parameter information field of the TWT element. The duration of the second SP is carried in the minimum TWT wake-up duration field of the TWT parameter information field of the TWT element. The period of the second SP is carried in the TWT wake-up interval tail field of the TWT parameter information field of the TWT element. The service priority corresponding to the second SP is carried in the R-TWT downlink TID bitmap field / R-TWT uplink TID bitmap field of the R-TWT service information field of the TWT element. As one possible implementation, the format of the TWT element is referenced. Figure 4 This will not be elaborated upon here. For example, the format of the TWT element carrying the second RTWT information is different from... Figure 4 The format shown is the same. For example, the format of the TWT element carrying the second RTWT information is the same as... Figure 4 The formats shown may differ, such as the length of the fields or the meaning of the fields.

[0197] The second RTWT information can be carried in a management frame, such as within the TWT element of a management frame. Alternatively, the second RTWT information can be carried in a broadcast frame, such as a beacon frame. It can also be carried in a unicast management frame. Unicast management frames can use separate addressing. A frame carrying the second RTWT information can be used to request the first AP to establish a Co RTWT, thereby enabling the first AP to protect the second AP's R-TWT SP.

[0198] In this embodiment, the first AP obtains the start time of the second SP based on the second RTWT information, and determines whether the second SP overlaps with the first SP by combining relevant information of the first SP scheduled by this BSS (such as BSS1) (such as at least one of the start time or duration of the first SP). In other words, the first AP determines the overlap between the second SP and the first SP.

[0199] In one possible implementation, the method further includes: the first AP sending first RTWT information to the second AP, and correspondingly, the second AP receiving the first RTWT information.

[0200] The first RTWT information is used to indicate the service priority corresponding to the first SP or at least one of the first SPs. The first SP is the R-TWT SP of the first AP. The first RTWT information includes at least one of the following: the start time of the first SP, the duration of the first SP, the period of the first SP, or the service priority corresponding to the first SP. For example, the first RTWT information includes the start time and duration of the first SP. Or, the first RTWT information includes the start time, duration, and service priority corresponding to the first SP. The contents of the first RTWT information will not be listed here.

[0201] Optionally, the first RTWT information can be used to indicate an active R-TWT schedule. Alternatively, the first R-TWT information can be used by the first AP to indicate to the second AP one or more active R-TWT schedules of the first AP. An R-TWT schedule may include one or more R-TWT SPs (also simply referred to as SPs).

[0202] The first RTWT information can be carried in a TWT element, or in other types of elements or fields; this application embodiment does not limit this. For related descriptions of TWT elements, please refer to the above section on the second RTWT information. Figure 4 The description will not be elaborated here.

[0203] The first RTWT information can be carried in a management frame, such as in a TWT element within a management frame. Alternatively, the first RTWT information can be carried in a broadcast frame, such as a beacon frame. Or, the first RTWT information can be carried in a unicast management frame.

[0204] In this embodiment, the second AP obtains the start time of the first SP based on the first RTWT information, and determines whether the first SP and the second SP overlap by combining the relevant information of the second SP scheduled by this BSS (such as BSS2) (such as at least one of the start time or duration of the second SP). In other words, the second AP determines the overlap between the first SP and the second SP.

[0205] Optionally, the second AP is a Co-RTWT requesting AP, and the first AP is a Co-RTWT responding AP or a Co-RTWT coordinated AP. That is, the Co-RTWT requesting AP can request the Co-RTWT responding AP and its associated sites to protect the Co-RTWT requesting AP's R-TWT SP (or R-TWT scheduling / mechanism), thereby giving the Co-RTWT requesting AP and its sites a greater chance to compete for channel usage rights. For example, the second AP can request the first AP to protect the second SP through the second RTWT information.

[0206] Optionally, both the second AP and the first AP are cooperative APs. The second AP can act as a Co-RTWT request AP to request the Co-RTWT response AP (i.e., the first AP) and its associated sites to protect the R-TWT SP of the Co-RTWT request AP (i.e., the second AP). The first AP can also act as a Co-RTWT request AP to request the Co-RTWT response AP (i.e., the second AP) and its associated sites to protect the R-TWT SP of the Co-RTWT request AP (i.e., the first AP).

[0207] 802. If the first condition is met, the first AP does not end TXOP before the start time of the second SP.

[0208] Alternatively, under the condition that the first condition is met, the first AP does not truncate the TXOP before the start time of the second SP. "Truncation" means that the first AP interrupts or prematurely terminates its data transmission within its BSS before the start time of the second SP; or, if the first AP does not have sufficient time to complete frame interaction before the start time of the second SP, it re-selects backoff to postpone transmission. Correspondingly, "no truncation" means that the first AP does not perform the aforementioned "truncation" operation due to the start time of the R-TWT SP protecting the second AP. The first AP can compete for the channel and use the corresponding TXOP duration according to the usual enhanced distributed channel access (EDCA) procedure.

[0209] Alternatively, if the first condition is met, the first AP continues TXOP before the start time of the second SP. Or, if the first condition is met, the first AP continues TXOP at and after the start time of the second SP.

[0210] Alternatively, if the first condition is met, the first AP ignores the second RTWT information before the start time of the second SP. In other words, if the first condition is met, the first AP may not follow the second AP's R-TWT SP mechanism (or the second AP's R-TWT operation) before the start time of the second SP.

[0211] In other words, the start time of the TXOP is earlier than or equal to the start time of the second SP, and the end time of the TXOP is later than the start time of the second SP. That is, before the start time of the second SP, the first AP is using its acquired TXOP, and after the start time of the second SP, the first AP is still using the TXOP. Or, the overlap duration between the TXOP and the first SP is greater than the overlap duration between the TXOP and the second SP. Therefore, the first AP can choose not to terminate its own TXOP.

[0212] Optionally, the start time of the TXOP is located at or after the start time of the first SP. Alternatively, the start time of the TXOP is no earlier than the start time of the first SP.

[0213] Optionally, the start time of the TXOP is earlier than the start time of the first SP. In other words, the start time of the TXOP is earlier than the start time of the first SP. If the service priority of the service transmitted within the TXOP is included in the service priority set associated with the first SP, then the first AP may not terminate its TXOP at the start time of the first SP.

[0214] The first AP can continue transmitting data at or after the start time of the second SP. For example, the first AP can continue transmitting data for low-latency services.

[0215] Within a TXOP, the first AP can transmit low-latency service data. For example, within this TXOP, before the start time of the second SP, the first AP can transmit low-latency service data. Also, within this TXOP, within and after the start time of the second SP, the first AP can transmit low-latency service data. Within the first SP, the first AP can transmit low-latency service data, thus ensuring that the first AP can provide low-latency services in a timely manner.

[0216] The following describes the first condition involved in the embodiments of this application, which includes at least one of condition (1) to condition (3).

[0217] Condition (1) The start time of the second SP is later than the start time of the first SP, and the start time of the second SP is earlier than the end time of the first SP. In other words, the first SP and the second SP overlap, and the start time of the first SP is earlier than the start time of the second SP. The first AP is in a wake-up state within the first SP. The first AP may need to transmit data. Therefore, when the first SP and the second SP satisfy condition (1), the first AP may not terminate the TXOP.

[0218] Generally speaking, the start time of an SP, the duration of an SP, and the period of an SP are all indicated in units of TU. Therefore, as a possible implementation, the start time of the second SP is later than the start time of the first SP, including: the TU in which the second SP is located is later than the TU in which the first SP is located.

[0219] Figure 9This is a schematic diagram of R-TWT SP overlap provided in an embodiment of this application. t1' is the start time of the first SP, t2' is the start time of the second SP, and t1 is the time when the first AP obtains the TXOP (i.e., the time when the first AP successfully competes for the channel). The duration of the first SP can be τ1, i.e., t1' + τ1 is the end time of the first SP. Figure 9 (Not shown). The duration of the second SP can be τ2, that is, t2'+τ2 is the end time of the second SP. Figure 9 (Not shown).

[0220] At time t1, the first AP successfully accesses the network and acquires a TXOP of duration δ. The end time of this TXOP is later than the start time of the second SP, i.e., t1 + δ > t2'. At time t1, AP2 detects that the channel has changed from idle to busy. AP2 can determine the end time of the busy channel based on the frames it receives. AP2 can maintain a NAV based on the frames it receives, and the end time of the duration indicated by the NAV can be the end time of the TXOP acquired by AP1. The end time of the TXOP can be t1 + δ, and t1 + δ > t2'. That is, the end time of the TXOP is later than the start time of the second SP. The end time of the TXOP acquired by AP1 can be independent of the end time of the first SP. Both AP1 and AP2 can have the ability to trigger TXOP sharing.

[0221] Condition (2) The first condition also includes at least one of the following: before the start time of the second SP, the first AP has data to be transmitted; before the start time of the second SP, the data transmission of the first AP has not ended; or before the start time of the second SP, the priority of the low-latency service of the first AP is not lower than the priority of the low-latency service of the second AP.

[0222] Optionally, the data is for low-latency services. For example, if the first AP has low-latency service data to transmit before the start time of the second SP, or if the low-latency service data has not yet been transmitted, the first AP may not close the TXOP. Alternatively, if the first AP has low-latency service data to transmit or if the low-latency service data has not yet been transmitted, both at and after the start time of the second SP, the first AP may not close the TXOP. Furthermore, if both the first and second APs have low-latency service data to transmit before (or after) the start time of the second SP, or if neither has completed its low-latency service transmission, but the priority of the first AP's low-latency service is higher than or equal to the priority of the second AP's low-latency service, the first AP may not close the TXOP. This ensures that the first AP can successfully transmit low-latency services, improving its ability to handle low-latency services.

[0223] The priority of low-latency services in the first AP can be determined based on the R-TWT service information field in the TWT element carrying the first RTWT information, and the priority of low-latency services in the second AP can be determined based on the R-TWT service information field in the TWT element carrying the second RTWT information. If the priority of the low-latency service in the first AP is not lower than the priority of the low-latency service in the second AP, it means that the service priority associated with the first SP is higher than or equal to the service priority associated with the second SP.

[0224] Condition (3) The duration between the start time of the first SP and the start time of the second SP is less than or equal to the first threshold.

[0225] In other words, before the start time of the second SP, the first AP has a relatively short time to transmit data, and the first AP may still have more data to transmit. Therefore, the first AP may not need to end the TXOP. Taking the first threshold as T2 as an example, if t2'-t1'≤T2, the first AP may not need to end the TXOP.

[0226] For example, the first threshold can be 1 millisecond. This first threshold is a fixed value defined by the standard. Alternatively, the first threshold can be a constant value negotiated between the first AP and the second AP. For instance, the first AP and the second AP negotiate this first threshold during the establishment of Co-RTWT. Or, the first AP and the second AP negotiate this first threshold during the exchange of Co-RTWT information. The method of setting the first threshold is not limited in this application embodiment.

[0227] For example, the negotiation method is as follows: the second AP sends information about a first threshold, and the first AP receives this information. This first threshold information can be contained within a TWT element carrying second RTWT information. Alternatively, the first threshold information and the second RTWT information can be carried in different elements within the same frame. Or, the first threshold information and the second RTWT information can be carried in different frames. Optionally, the first AP sends a response message to the second AP. This response message can be used to confirm the first threshold information, reject the first threshold information, or suggest a new first threshold. This response message can be contained within a TWT element carrying the first RTWT information. Alternatively, the response message and the first RTWT information can be carried in different elements within the same frame. Or, the response message and the first RTWT information can be carried in different frames. The above example illustrates the second AP sending information about a first threshold. As another possible implementation, the first AP can also send the first threshold information, and the second AP can send a response message; this will not be detailed here.

[0228] The following examples illustrate the combination of conditions (1) to (3).

[0229] As one possible implementation, the first condition is condition (1). If condition (1) is met, the first AP does not end TXOP before the start time of the second SP. If condition (1) is not met, the first AP ends TXOP before the start time of the second SP. The situations in which condition (1) is not met include, but are not limited to: the start time of the second SP is outside the first SP; or, the start time of the second SP is later than the start time of the first SP, and the start time of the second SP is later than the end time of the first SP. Specific cases in which condition (1) is not met will not be listed here.

[0230] As another possible implementation, the first conditions are conditions (1) and (2). If conditions (1) and (2) are met, the first AP does not terminate the TXOP before the start time of the second SP. If at least one of conditions (1) or (2) is not met, the first AP terminates the TXOP before the start time of the second SP. The situations in which condition (2) is not met include, but are not limited to: the first AP has finished transmitting before the start time of the second SP; the first AP has no data to transmit before the start time of the second SP; or, before the start time of the second SP, the priority of the low-latency service of the first AP is lower than the priority of the low-latency service of the second AP. Specific situations in which condition (2) is not met will not be listed here. For example, if the start time of the second SP is later than the start time of the first SP, the start time of the second SP is earlier than the end time of the first SP, and the end time of the TXOP is later than the start time of the second SP, but the first AP has finished transmitting before the start time of the second SP, then the first AP can terminate the TXOP.

[0231] As another possible implementation, the first conditions are conditions (1) and (3). If conditions (1) and (3) are met, the first AP does not terminate TXOP before the start time of the second SP. If at least one of conditions (1) or (3) is not met, the first AP terminates TXOP before the start time of the second SP. The case where condition (3) is not met includes: the duration between the start time of the first SP and the start time of the second SP is greater than a first threshold.

[0232] As another possible implementation, the first condition is condition (1) to condition (3). The combinations of the various conditions involved in the first condition will not be listed here.

[0233] In this embodiment, the first AP is an AP that implements the Co-RTWT operation, that is, the parameter dot11CoRTwtOptionImplemented in the first AP is true. Similarly, the second AP can also be an AP that implements the Co-RTWT operation, that is, the parameter dot11CoRTwtOptionImplemented in the second AP is true.

[0234] In this embodiment, even if the first AP and the second AP establish a Co-RTWT, the first AP may not terminate the TXOP before the start time of the second SP. Therefore, the first AP's own R-TWT scheduling is minimized, ensuring the first AP has sufficient time to transmit data and improving channel utilization.

[0235] Figure 8 The method shown is illustrated using an Access Point (AP) as an example. The following explanation uses the associated sites of the first AP as an example. The associated sites of the first AP are non-AP STAs within the BSS where the first AP is located that have established an association with the first AP. Alternatively, the associated sites of the first AP are non-AP STAs belonging to the R-TWT group and associated with the first AP. For example, the associated sites of the first AP include non-AP STA1.

[0236] Figure 10 This is a flowchart illustrating the communication method provided in an embodiment of this application. This method can be applied to a communication device, a chip or circuit within the communication device, or a functional module within the communication device. For ease of description, the following description uses a first AP, a second AP, and an associated site of the first AP as examples to illustrate the communication method. The descriptions of the first AP, the second AP, and the associated site are as above and will not be detailed here.

[0237] like Figure 10 As shown, the method includes:

[0238] 1001. The first AP and the second AP establish Co-RTWT.

[0239] For an explanation of step 1001, please refer to step 801; it will not be detailed here.

[0240] In one possible implementation, the method further includes step 1002.

[0241] 1002. The first AP sends the third RTWT information, and the corresponding site of the first AP receives the third RTWT information.

[0242] The third RTWT information is used to indicate the active R-TWT scheduling of the second AP. This third RTWT information indicates at least one of the following: the second SP, or the service priority associated with the second SP. For example, the third RTWT information may include the start time of the second SP. Alternatively, the third RTWT information may include the start time of the second SP and the duration of the second SP. For further explanation of the third RTWT information, please refer to [link / reference]. Figure 8 The description of the second RTWT information is not detailed here.

[0243] The third RTWT information can be determined based on the second RTWT information. For example, the content of the third RTWT information can be the same as the content of the second RTWT information. Alternatively, the content of the third RTWT information can be different from the content of the second RTWT information. For instance, the second RTWT information includes the start time of the second SP, the duration of the second SP, and the service priority corresponding to the second SP. The third RTWT information can include the start time of the second SP and the service priority corresponding to the second SP. Another example is that the number of second SPs indicated by the second RTWT information is greater than or equal to the number of second SPs indicated by the third RTWT information. These are just a few examples.

[0244] The third RTWT information may include information about the second AP, allowing the associated site of the first AP to determine which AP corresponds to its second SP. Alternatively, the third RTWT information may not include information about the second AP. In this case, the associated site of the first AP, in conjunction with the R-TWT SP of this BSS and the second SP, determines whether to terminate the TXOP. The information about the second AP includes, but is not limited to, at least one of the following: the BSS color of the BSS where the second AP is located, the ID of the second AP, or the BSSID of the BSS where the second AP is located.

[0245] The third RTWT information can be carried in a TWT element, or in other types of elements or fields; this application does not limit this. For a description of the TWT element, please refer to [link / reference needed]. Figure 8 or Figure 4 Etc., will not be elaborated here.

[0246] The third RTWT information can be carried in a management frame. For example, this management frame may include a broadcast frame, such as a beacon frame. The first AP broadcasts the relevant information of the second SP through the broadcast frame, enabling all non-AP STAs within this BSS to learn about the second SP. Alternatively, the management frame may include a unicast frame. This unicast frame includes the station ID, or the station's AID, or the station's MAC address, etc. The first AP sends the relevant information of the second SP through the unicast frame, enabling the station corresponding to that unicast frame to learn about the second SP.

[0247] In this embodiment, the associated site of the first AP learns the start time of the second SP based on the third RTWT information, and determines whether the second SP overlaps with the first SP by combining the relevant information of the first SP scheduled by this BSS (such as BSS1) (such as at least one of the start time or duration of the first SP). In other words, the associated site of the first AP determines the overlap between the second SP and the first SP.

[0248] In one possible implementation, the method further includes step 1003.

[0249] 1003. The first AP sends the fourth RTWT information, and the corresponding site of the first AP receives the fourth RTWT information.

[0250] The fourth RTWT information can be used to indicate the active R-TWT scheduling of the first AP. Alternatively, the fourth RTWT information can be used to indicate the R-TWT scheduling of the first AP, such as including active R-TWT scheduling and idle R-TWT scheduling.

[0251] The fourth RTWT information is used to indicate the service priority corresponding to the first SP or at least one of the first SPs. For example, the fourth RTWT information may include the start time, duration, and period of the first SP. Alternatively, the fourth RTWT information may include the start time, duration, period, and service priority corresponding to the first SP. For further explanation of the fourth RTWT information, please refer to [link / reference]. Figure 8 The description of the first RTWT information is not detailed here.

[0252] The content in the fourth RTWT information can be the same as the content in the first RTWT information. Alternatively, the content in the fourth RTWT information can be different from the content in the first RTWT information. For example, the fourth RTWT information can be the same as the first SP indicated in the first RTWT information.

[0253] The fourth RTWT information can be carried in a TWT element, or in other types of elements or fields; this application does not limit this. For further explanation regarding the fourth RTWT information, please refer to [link / reference]. Figure 8 The description of the first RTWT information is not detailed here.

[0254] The fourth RTWT information can be carried in a management frame. For example, the management frame may include broadcast frames, such as beacon frames. Or, the management frame may include unicast frames.

[0255] The aforementioned third RTWT information and fourth RTWT information can be carried in the same frame or in different frames.

[0256] Figure 10 The transmission order of the fourth RTWT information and the second RTWT information shown is merely an example, and the transmission order of the second RTWT information and the first RTWT information is merely an example and is not intended to limit the embodiments of this application.

[0257] 1004. If the first condition is met, the associated site of the first AP does not terminate TXOP before the start time of the second SP.

[0258] For instructions on not ending TXOP, please refer to step 802; details will not be repeated here. The difference lies in... Figure 8 In the method shown, the TXOP holder is the first AP, while Figure 10 In the method shown, the TXOP holder is the associated site of the first AP.

[0259] At or after the start time of the second SP, the associated sites of the first AP can continue to transmit. For example, the associated sites of the first AP can continue to transmit low-latency service data.

[0260] Within a TXOP, the associated sites of the first AP can transmit low-latency service data. For example, within this TXOP, before the start time of the second SP, the associated sites of the first AP can transmit low-latency service data. Also, within this TXOP, within and after the start time of the second SP, the associated sites of the first AP can transmit low-latency service data. Within the first SP, the associated sites of the first AP can transmit low-latency service data. This ensures that the associated sites of the first AP can provide low-latency services in a timely manner.

[0261] The first condition includes at least one of the following:

[0262] The start time of the second SP is later than or equal to the start time of the first SP, and the start time of the second SP is earlier than the end time of the first SP. For an explanation of this condition, please refer to the description of condition (1) above, which will not be elaborated here.

[0263] Before the start time of the second SP, the associated site has data to be transmitted; before the start time of the second SP, the data transmission of the associated site has not been completed; or before the start time of the second SP, the priority of the low-latency service of the associated site is not lower than the priority of the low-latency service of the site corresponding to the second SP. For an explanation of this condition, please refer to the description of condition (2) above, which will not be elaborated here.

[0264] The duration between the start time of the first SP and the start time of the second SP is less than or equal to the first threshold. For an explanation of this condition, please refer to the description of condition (3) above, which will not be elaborated here.

[0265] For explanations of the combinations of various conditions, please refer to [link / reference]. Figure 8 This will not be elaborated upon here.

[0266] In this embodiment, even if the first AP and the second AP establish a Co-RTWT, the associated site of the first AP may not terminate its TXOP before the start time of the second SP. Therefore, the R-TWT scheduling of the associated site of the first AP is minimized, ensuring that the associated site of the first AP has sufficient time to transmit data and improving channel utilization.

[0267] The method described above allows the first AP's associated site to maintain its TXOP until the second SP's start time, provided the first condition is met. The following explanation uses the first AP as an example to illustrate how it shares its TXOP.

[0268] Figure 11 This is a flowchart illustrating the communication method provided in an embodiment of this application. This method can be applied to a communication device, a chip or circuit within the communication device, or a functional module within the communication device. For ease of description, the following description uses a first AP and a second AP as examples to illustrate the communication method. The description of the first AP and the second AP is given above and will not be repeated here. Figure 11 As shown, the method includes:

[0269] 1101. The first AP and the second AP establish Co-RTWT.

[0270] For details regarding step 1101, please refer to step 801; they will not be elaborated upon here.

[0271] 1102. If the first condition is met, the first AP does not end TXOP before the start time of the second SP.

[0272] For details regarding step 1102, please refer to step 802; they will not be elaborated upon here.

[0273] 1103. The first AP shares a first duration with the second AP, which is the remaining duration of the TXOP, or a portion of the remaining duration of the TXOP.

[0274] In other words, if the first AP learns the R-TWT SP information of the second AP (including the start time and duration of the second SP), and learns that the second SP overlaps with the first SP, or learns that the first condition is met, the first AP can share all or part of the remaining TXOP duration with the second AP within the TXOP duration it has obtained, so that the second AP can carry out transmission.

[0275] The first AP shares the first duration in the following ways: the first AP sends sharing information to the second AP, which indicates the first duration. The second AP receives the sharing information and transmits within the first duration. Alternatively, the first AP sends information for the first duration to the second AP, and the second AP receives the information for the first duration and transmits within that first duration.

[0276] The first AP can share the TXOP using the Co-TDMA procedure. This application embodiment does not limit whether the sharing information is contained in the MU-RTS frame or in other types of management frames. For example, the first duration can be carried in the allocation duration field of the user information field in the MU-RTS frame, and this user information field corresponds to the second AP. For the format of the MU-RTS frame, please refer to [reference needed]. Figure 6 The format of the MU-RTS TXS frame is shown below. For example, the AID12 field in the MU-RTS frame carrying sharing information can indicate the second AP. Also, the value and meaning of the triggered TXOP sharing mode field can be the same as or different from those in Table 2.

[0277] Optionally, the start time of the first duration can be the end time of the MU-RTS frame, that is, the time when the first AP finishes sending the MU-RTS frame, which is also the time when the second AP successfully receives the MU-RTS frame. The start time of the first duration can also be called the time when the first AP actively shares the TXOP.

[0278] As an example, the start time of the first duration is later than the start time of the second duration. Figure 12a This is a schematic diagram illustrating the sharing of TXOP by the first AP during Co-RTWT SP overlap, as provided in an embodiment of this application. AP 1 actively shares its TXOP with AP 2 at time t2, which is later than the start time t2' of the R-TWT SP. For example... Figure 12a As shown, t2 represents the start time of the first duration. Regarding... Figure 12a Other parameters involved are referenced above and will not be detailed here.

[0279] As another example, the start time of the first duration is equal to the start time of the second SP. Figure 12b This is a schematic diagram illustrating the sharing of TXOP by the first AP during Co-RTWT overlap, as provided in an embodiment of this application. Figure 12b As shown, at the start time t2' (t2' = t2) of AP2's R-TWT SP, AP1 actively shares its TXOP with AP2. Regarding... Figure 12b The parameters involved are described above and will not be detailed here.

[0280] AP1 can share the entire remaining duration of TXOP, or AP1 can share a portion of the remaining duration of TXOP. For example, if the first duration is denoted by τ3, and the end time of the first AP sharing TXOP is t3' = t2 + τ3, then t3' can be no later than the end time of the first SP, i.e., t3' = t1' + τ1, or t3'... <t1’+τ1。

[0281] In one possible implementation, if the first condition is met, the first AP does not terminate the TXOP and shares the remaining duration of the TXOP or a portion of the remaining duration of the TXOP with the second AP.

[0282] For example, if the first condition is condition (1) and condition (2), then the following explanation applies: the start time of the second SP is later than the start time of the first SP, and the start time of the second SP is earlier than the end time of the first SP; if the first AP has not finished transmitting its low-latency service before the start time of the second SP, then the first AP will not end the TXOP; if the first AP has finished transmitting its low-latency service data or partially transmitted its low-latency service data at or before the start time of the first duration, then the first AP can share the remaining duration of its TXOP (or part of the remaining duration) with the second AP.

[0283] For example, if the first condition is condition (1) and condition (2), then the following applies: The start time of the second SP is later than the start time of the first SP, and the start time of the second SP is earlier than the end time of the first SP; before the start time of the second SP, the first AP has not yet finished transmitting its low-latency service, and the priority of the low-latency service of the first AP is lower than the priority of the low-latency service of the second AP, then before the start time of the second SP, the first AP does not end the TXOP and shares the remaining duration (or part of the remaining duration) of its TXOP with the second AP. Or, the start time of the second SP is later than the start time of the first SP, and the start time of the second SP is earlier than the end time of the first SP; before the start time of the second SP, the first AP has not yet finished transmitting its low-latency service, and the priority of the low-latency service of the first AP is lower than the priority of the low-latency service of the second AP, then before the start time of the second SP, the first AP does not end the TXOP; after the first AP finishes transmitting its low-latency service, it shares the remaining duration (or part of the remaining duration) of its TXOP with the second AP.

[0284] For example, if the first condition is condition (1) and condition (3), then the following explanation applies: the start time of the second SP is later than the start time of the first SP, and the start time of the second SP is earlier than the end time of the first SP; the duration between the start time of the first SP and the start time of the second SP is less than or equal to the first threshold; then before the start time of the second SP, the first AP does not end the TXOP and shares the remaining duration of its TXOP (or part of the remaining duration) with the second AP.

[0285] For an explanation of the combination of conditions (1) to (3), please refer to [link / reference]. Figure 8 They will not be listed one by one here.

[0286] As another possible implementation, the first AP shares the first duration with the second AP, including: the first AP shares the first duration with the second AP when a second condition is met. The second condition includes at least one of conditions (4) to (6).

[0287] Condition (4) After the start time of the first duration, the priority of the low-latency service of the first AP is lower than the priority of the low-latency service of the second AP. Or, after the start time of the first duration, the first AP no longer needs to transmit low-latency services.

[0288] For example, with Figure 12a For example, before time t2', AP1 has not yet finished transmitting its low-latency service. At time t2, after AP1 finishes transmitting its low-latency service, it can share the remaining TXOP with AP2.

[0289] For example, with Figure 12b For example, before time t2', AP1 has not yet finished transmitting its low-latency service, but the priority of its transmitted low-latency service is lower than that of AP2's low-latency service. Therefore, at time t2', AP1 either does not terminate its TXOP, or after transmitting part of its low-latency service, it shares the remaining TXOP with AP2.

[0290] For further explanation of condition (4), please refer to the description of condition (2) above, or refer to the combined explanation of condition (1) and condition (2) above. It will not be elaborated here.

[0291] Under condition (4), the first AP can actively share its TXOP with the second AP. Thus, the second AP can also transmit low-latency services, improving its ability to carry low-latency services.

[0292] Condition (5) The duration between the start time of the second SP and the start time of the first duration is less than or equal to the second threshold. Taking the second threshold as represented by σ, then t2≥t2' and t2-t2'≤σ.

[0293] For example, the second threshold can be a fixed value defined by the standard. The standard-defined method for the second threshold is simple to implement. Another example is that the first and second APs can exchange the second threshold through a Co-TDMA process, thus improving the flexibility of the second threshold setting. Yet another example is that the first and second APs can exchange information via broadcast frames (such as beacon frames) or separately addressed unicast management frames, further enhancing the flexibility of the second threshold setting.

[0294] By satisfying condition (5), the time when the first AP shares TXOP can be avoided as late as possible, so that the second AP can also transmit data for low-latency services.

[0295] Condition (6) The first duration is greater than or equal to the third threshold. The third threshold can also be called the minimum duration threshold that is shared.

[0296] In other words, the TXOP duration shared by the first AP (i.e., the first duration) is not less than the minimum duration threshold that the second AP needs to share. Taking the third threshold as represented by T1 as an example, then τ3≥T1.

[0297] For example, the third threshold can be a fixed value defined by the standard. The standard-defined method for the third threshold is simple to implement. Alternatively, the first AP and the second AP can exchange the third threshold through a Co-TDMA process, thereby increasing the flexibility of the third threshold setting. Another example is that the first AP and the second AP can exchange information via broadcast frames (such as beacon frames) or individually addressed unicast management frames, further increasing the flexibility of the third threshold setting. This application does not limit the setting methods for the second and third thresholds. The setting methods for the second and third thresholds can be the same or different.

[0298] The distinction between the first and second conditions shown above is merely an example. In specific implementations, the distinction between the first and second conditions may not be made. That is, if the conditions are met, before the start time of the second SP, the first AP does not end the TXOP and shares a portion of the TXOP duration (such as the remaining duration of the TXOP, or a portion of the remaining duration); or, if the conditions are met, the first AP continues the TXOP at and after the start time of the second SP, and the first AP can share a portion of the TXOP duration. Figure 8 and Figure 11 Specific descriptions of the combinations are not listed here.

[0299] For example, satisfying the conditions means satisfying conditions (1), (2), and (3). For another example, satisfying the conditions means satisfying conditions (1), (2), and (6). For another example, satisfying the conditions means satisfying conditions (1) and (4). For another example, satisfying the conditions means satisfying conditions (1), (4), and (5). For another example, satisfying the conditions means satisfying conditions (1), (2), (4), and (6). Combinations of conditions (1) through (6) will not be listed here individually.

[0300] In one possible implementation, if the shared TXOP has remaining time, the second AP can return the remaining TXOP to the first AP.

[0301] In this embodiment, the first AP shares the TXOP, which not only ensures that the first AP has enough time to transmit data and improves channel utilization, but also allows the second AP to transmit data, thereby improving the efficiency of the second AP accessing the channel.

[0302] When the start time of the second SP is equal to the start time of the first SP, the first AP may not terminate the TXOP, or it may terminate the TXOP; this embodiment does not limit this. For example, when the start time of the second SP is equal to the start time of the first SP, the first AP may not terminate the TXOP, and after the first AP has transmitted part of the low-latency service data, or has transmitted all of the low-latency service data (e.g., the low-latency service has a higher priority than the low-latency service of the second AP), the first AP may share the entire remaining duration or part of the remaining duration of the TXOP with the second AP. For related explanations regarding TXOP and sharing, please refer to the above; they will not be listed here again.

[0303] Generally, the start time of an SP is indicated in time units (TU). 1 TU = 1024 microseconds (µs). The timing synchronization function (TSF) between the first AP and the second AP is not necessarily synchronized. Therefore, the start time of the second SP being equal to the start time of the first SP, as shown above, includes situations where the TU of the second SP's start time is the same as that of the first SP, or where there is an error between the start time (e.g., absolute time) of the second SP and the start time (e.g., absolute time) of the first SP, and this error is less than or equal to a certain range, such as 1 TU.

[0304] Before the method provided in this application embodiment, when the start time of the first SP equals the start time of the second SP, if AP1 is transmitting the same service that SP1 needs to transmit, AP1 does not need to stop TXOP. However, the Co-RTWT mechanism requires AP1 to stop TXOP at the start of SP2. This leads to a contradiction in AP1's behavior. Therefore, in this application embodiment, when the start time of the first SP equals the start time of the second SP, the first AP can not end TXOP, thus effectively ensuring the smooth operation of the first AP's service when it is already transmitting the service associated with the first SP, improving system utilization efficiency. Alternatively, when the start time of the first SP equals the start time of the second SP, the first AP ends TXOP, which is beneficial for the transmission of the second AP.

[0305] Table 3 provides an exemplary explanation of the meaning of each letter mentioned above. It is understood that the letters shown in the embodiments of this application are merely examples and are not intended to limit the scope of the embodiments.

[0306] Table 3 Symbol List

[0307]

[0308] The following describes the communication device provided in the embodiments of this application.

[0309] This application divides the communication device into functional modules according to the above-described method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and represents only one logical functional division; other division methods may be used in actual implementation. The following will combine... Figures 13 to 15 The communication device of the embodiments of this application is described in detail.

[0310] Figure 13 This is a schematic diagram of a communication device provided in an embodiment of this application. For example... Figure 13 As shown, the communication device includes a processing module 1301 and a transceiver module 1302. The transceiver module 1302 can implement corresponding communication functions, and the processing module 1301 is used to implement corresponding processing functions. The transceiver module 1302 can also be referred to as an interface, a communication interface, or a communication module, etc.

[0311] In some embodiments of this application, the communication device can be used to perform the actions performed by the first AP in the above method embodiments. In this case, the device can be the device itself or a chip or functional module configurable in the device. The transceiver module 1302 is used to perform the transceiver-related operations of the first AP in the above method embodiments, and the processing module 1301 is used to perform the processing-related operations of the first AP in the above method embodiments.

[0312] Processing module 1301 is configured to prevent the TXOP from ending before the start time of the second SP if a first condition is met. For example, processing module 1301 can be used to determine whether the first condition is met. Alternatively, the processor can be used to determine whether the condition for not ending the TXOP is met.

[0313] Optionally, the transceiver module 1302 is used to transmit data, such as data for low-latency services.

[0314] Optionally, the processing module 1301 is also used to share the remaining duration of the TXOP, or a portion of the remaining duration of the TXOP. For example, the processing module 1301 controls the transceiver module 1302 to send (or output) the shared information.

[0315] Optionally, the transceiver module 1302 is used to receive or input second RTWT information;

[0316] Optionally, the transceiver module 1302 is also used to send or output the first RTWT information.

[0317] Optionally, the transceiver module 1302 is also used to send or output third RTWT information and fourth RTWT information.

[0318] Reuse Figure 13 In other embodiments of this application, the device can be used to perform the actions performed by the non-AP STA (i.e., the associated site of the first AP) in the above method embodiments. In this case, the device can be the device itself or a chip or functional module configurable in the device. The transceiver module 1302 is used to perform the transceiver-related operations of the non-AP STA in the above method embodiments, and the processing module 1301 is used to perform the processing-related operations of the non-AP STA in the above method embodiments.

[0319] Processing module 1301 is configured to prevent the TXOP from ending before the start time of the second SP if a first condition is met. For example, processing module 1301 can be used to determine whether the first condition is met. Alternatively, the processor can be used to determine whether the condition for not ending the TXOP is met.

[0320] Optionally, the transceiver module 1302 is used to transmit data, such as data for low-latency services.

[0321] Optionally, the transceiver module 1302 is also used to receive or input third RTWT information and fourth RTWT information.

[0322] Reuse Figure 13 In some other embodiments of this application, the communication device can be used to perform the actions performed by the second AP in the above method embodiments. In this case, the device can be the device itself or a chip or functional module configurable in the device. The transceiver module 1302 is used to perform the transceiver-related operations of the second AP in the above method embodiments, and the processing module 1301 is used to perform the processing-related operations of the second AP in the above method embodiments.

[0323] The transceiver module 1302 is used to input shared information; the processing module 1301 is used to transmit data within a first duration. For example, the processing module 1301 can be used to control the transceiver module 1302 to transmit data within the first duration.

[0324] Optionally, the transceiver module 1302 is also used to send or output second RTWT information.

[0325] Optionally, the transceiver module 1302 is also used to receive or input first RTWT information.

[0326] For example, the transceiver module 1302 described above can be an antenna module. Alternatively, the transceiver module 1302 can be an input / output module. Optionally, in the above embodiments, the device may further include a storage module, which can be used to store instructions and / or data. The processing module 1301 can read the instructions and / or data from the storage module to enable the device to implement the aforementioned method embodiments.

[0327] For details regarding the specific explanations of each term, noun, or step in the above embodiments, please refer to the descriptions in the above method embodiments; they will not be detailed here.

[0328] The specific descriptions of the transceiver module and processing module shown in the above embodiments are merely examples. For the specific functions or execution steps of the transceiver module and processing module, please refer to the above method embodiments, which will not be described in detail here.

[0329] It is understandable that the module division in the above-mentioned device is merely a logical functional division. Each function can correspond to a functional module, or two or more functions can be integrated into one functional module. In actual implementation, all or some modules can be integrated into one physical entity, or they can be distributed across different physical entities. Furthermore, the above-mentioned functional modules can be implemented in hardware, software, or a combination of both.

[0330] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0331] The apparatus of the embodiments of this application has been described above. The possible product forms of the described apparatus are described below. Any device possessing the above-described features... Figure 13 Any form of product that incorporates the functionality of the described device falls within the protection scope of the embodiments of this application. The following description is merely illustrative and does not limit the product form of the device in the embodiments of this application to this specific example.

[0332] In one possible implementation, Figure 13 In the illustrated device, processing module 1301 can be one or more processors, and transceiver module 1302 can be a transceiver, or transceiver module 1302 can also be a transmitting module and a receiving module. The transmitting module can be a transmitter, and the receiving module can be a receiver. The transmitting module and the receiving module are integrated into one device, such as a transceiver. In this embodiment, the processor and transceiver can be coupled, etc., and the connection method between the processor and the transceiver is not limited in this embodiment. During the execution of the above method, the process of sending information in the above method can be the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to undergo other processing before being input into the processor.

[0333] Figure 14 This is another schematic diagram of the communication device provided in the embodiments of this application. For example... Figure 14 As shown, the communication device 140 includes one or more processors 1420 and transceivers 1410.

[0334] In some embodiments of this application, the above-described apparatus can be used to perform the steps, methods, or functions executed by the first AP, such as the processor 1420 being used to perform such... Figure 13 The transceiver 1410 can be used to perform the functions or steps implemented by the processing module 1301 shown. Figure 13 The transceiver module 1302 shown illustrates the functions or steps implemented by it. For detailed information on the processor 1420 and transceiver 1410, please refer to [link / reference needed]. Figure 13 Alternatively, the method embodiments shown above will not be described in detail here.

[0335] In other embodiments of this application, the above-described apparatus is used to perform steps, methods, or functions performed by an associated site of the first AP, such as a non-AP STA. For example, the processor 1420 may be used to perform... Figure 13 The transceiver 1410 can be used to perform the functions or steps implemented by the processing module 1301 shown. Figure 13 The transceiver module 1302 shown illustrates the functions or steps implemented by it. For detailed information on the processor 1420 and transceiver 1410, please refer to [link / reference needed]. Figure 13 Alternatively, the method embodiments shown above will not be described in detail here.

[0336] In some other embodiments of this application, the above-described apparatus can be used to perform the steps, methods, or functions of the second AP execution, such as the processor 1420 being used to perform such... Figure 13 The transceiver 1410 can be used to perform the functions or steps implemented by the processing module 1301 shown. Figure 13 The transceiver module 1302 shown illustrates the functions or steps implemented by it. For detailed information on the processor 1420 and transceiver 1410, please refer to [link / reference needed]. Figure 13 Alternatively, the method embodiments shown above will not be described in detail here.

[0337] exist Figure 14 In various implementations of the communication apparatus shown, the transceiver may include a receiver for performing a receiving function (or operation) and a transmitter for performing a transmitting function (or operation). The transceiver is also used to communicate with other devices / appliances via a transmission medium.

[0338] Optionally, the communication device 140 may further include one or more memories 1430 for storing program instructions and / or data. The memories 1430 are coupled to the processor 1420. The coupling in this embodiment is an indirect coupling or communication connection between communication devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between the communication devices, units, or modules. The processor 1420 may operate in conjunction with the memories 1430. The processor 1420 can execute program instructions stored in the memories 1430. Optionally, at least one of the aforementioned memories may be included in the processor.

[0339] This application embodiment does not limit the specific connection medium between the transceiver 1410, processor 1420, and memory 1430. This application embodiment... Figure 14 The memory 1430, processor 1420, and transceiver 1410 are connected via a bus 1440. Figure 14 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 14 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0340] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0341] In this application embodiment, the memory may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM), etc. Memory is any storage medium capable of carrying or storing program code in the form of instructions or data structures, and capable of being read and / or written by a computer (such as the communication device shown in this application), but is not limited to this. The memory in this application embodiment may also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0342] Processor 1420 is primarily used to process communication protocols (or standards) and communication data, control the entire communication device, execute software programs, and process the data from those programs. Memory 1430 is primarily used to store software programs and data. Transceiver 1410 may include control circuitry and an antenna. The control circuitry is primarily used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is primarily used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are primarily used to receive user input data and output data to the user.

[0343] When the communication device is powered on, the processor 1420 can read the software program in the memory 1430, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1420 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1420. The processor 1420 converts the baseband signal into data and processes the data.

[0344] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0345] The communication device shown in the embodiments of this application may also have a higher... Figure 14This application does not limit the use of other components or other related elements. The methods performed by the processor and transceiver shown above are merely examples; the specific steps performed by the processor and transceiver can be found in the methods described above. Figure 14 The dashed part indicates that it is optional.

[0346] In another possible implementation, Figure 13 In the communication device shown, the processing module 1301 can be one or more logic circuits, and the transceiver module 1302 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver module 1302 can also be a transmitting module and a receiving module. The transmitting module can be an output interface, and the receiving module can be an input interface. The transmitting module and the receiving module are integrated into one module, such as an input / output interface.

[0347] Figure 15 This is a schematic diagram of a chip provided in an embodiment of this application. For example... Figure 15 As shown, Figure 15 The chip shown includes logic circuitry 1501 and interface 1502. That is, the processing module 1301 can be implemented using logic circuitry 1501, and the transceiver module 1302 can be implemented using interface 1502. The logic circuitry 1501 can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface 1502 can be a communication interface, input / output interface, pins, etc. For example, Figure 15 The above device is used as an example of a chip, which includes logic circuit 1501 and interface 1502.

[0348] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method between the logic circuit and the interface is not limited in this embodiment. For example, the logic circuit 1501 can be used to perform... Figure 13 The processing module 1301 shown implements the functions or steps, and the interface 1502 can be used to execute such functions or steps. Figure 13 The transceiver module 1302 shown herein implements the functions or steps. For detailed descriptions of the logic circuit 1501 and interface 1502, please refer to [link / reference needed]. Figure 13 Alternatively, the method embodiments shown above will not be described in detail here.

[0349] The communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form, or it can implement the method provided in the embodiments of this application in software form, etc., and the embodiments of this application do not limit it in this way.

[0350] Furthermore, embodiments of this application also provide a communication system including a first AP, a second AP, and a non-AP STA, wherein the first AP, the second AP, and the non-AP STA can be used to perform the methods in any of the foregoing embodiments.

[0351] This application also provides a computer program for implementing the operations and / or processes performed by various communication devices in the methods provided in this application.

[0352] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by various communication devices in the methods provided in this application.

[0353] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by various entities in the method provided in this application to be executed.

[0354] In the embodiments provided in this application, it should be understood that the disclosed systems, communication devices, and methods can be implemented in other ways. For example, the communication device embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, communication devices, or modules, or it may be an electrical, mechanical, or other form of connection.

[0355] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.

[0356] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0357] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A communication method, characterized in that, The method includes: Under the condition that the first condition is met, the first AP does not terminate the transmission opportunity TXOP before the start time of the second service period SP of the second access point AP, and the first AP and the second AP have established a cooperative limit target wake-up time Co-RTWT; The first condition includes: The start time of the second SP is later than the start time of the first SP of the first AP, and the start time of the second SP is earlier than the end time of the first SP.

2. The method according to claim 1, characterized in that, The first condition also includes at least one of the following: Before the start time of the second SP, the first AP has data to be transmitted; Before the start time of the second SP, the data transmission of the first AP has not been completed; or, Before the start time of the second SP, the priority of the low-latency service of the first AP is no lower than the priority of the low-latency service of the second AP.

3. The method according to any one of claims 1-2, characterized in that, The first condition also includes: The duration between the start time of the first SP and the start time of the second SP is less than or equal to the first threshold.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: The first AP continues transmission at or after the start time of the second SP.

5. The method according to any one of claims 1-3, characterized in that, The method further includes: Within the TXOP, the first AP transmits data for low-latency services.

6. The method according to claim 5, characterized in that, Within the TXOP, the first AP transmits low-latency service data, including: Within the TXOP and before the start time of the second SP, the first AP transmits the data for the low-latency service.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: The first AP shares a first duration with the second AP, where the first duration is the remaining duration of the TXOP, or a portion of the remaining duration.

8. The method according to claim 7, characterized in that, The first AP shares a first duration with the second AP, including: If the second condition is met, the first AP shares the first duration with the second AP; The second condition includes at least one of the following: The duration between the start time of the second SP and the start time of the first duration is less than or equal to the second threshold; or, The first duration is greater than or equal to the third threshold.

9. The method according to claim 8, characterized in that, The second condition also includes: After the start time of the first duration, the low-latency service of the first AP has a lower priority than the low-latency service of the second AP.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: The first AP receives RTWT information from the second AP, and the RTWT information is used to instruct the second SP.

11. A communication method, characterized in that, The method includes: Under the condition that the first condition is met, before the start time of the second service period SP, the associated site of the first access point AP does not terminate the transmission opportunity TXOP, and the site corresponding to the first AP and the second SP has established a cooperative limit target wake-up time Co-RTWT. The first condition includes: The start time of the second SP is later than the start time of the first SP of the first AP, and the start time of the second SP is earlier than the end time of the first SP.

12. The method according to claim 11, characterized in that, The first condition also includes at least one of the following: Before the start time of the second SP, the associated site has data to be transmitted; Before the start time of the second SP, the data transmission of the associated site has not been completed; or, Before the start time of the second SP, the priority of the low-latency service of the associated site is no lower than the priority of the low-latency service of the site corresponding to the second SP.

13. The method according to claim 11 or 12, characterized in that, The first condition also includes: The duration between the start time of the first SP and the start time of the second SP is less than or equal to the first threshold.

14. The method according to any one of claims 11-13, characterized in that, The method further includes: The associated site continues transmission before or after the start time of the second SP.

15. The method according to any one of claims 11-13, characterized in that, The method further includes: Within the TXOP, the associated site transmits data for low-latency services.

16. The method according to claim 15, characterized in that, Within the TXOP, the associated site transmits low-latency service data, including: Within the TXOP and before the start time of the second SP, the associated site transmits the data for the low-latency service.

17. A communication method, characterized in that, The method includes: The second access point (AP) receives sharing information from the first AP. The sharing information is used to indicate a first duration, which is the remaining duration of the first AP's transmission opportunity (TXOP), or a portion of the remaining duration. The first duration is included in the first service period (SP) of the first AP. The second AP transmits data within the first duration; Wherein, the first SP satisfies a first condition, the first condition including: The start time of the second SP of the second AP is later than the start time of the first SP, and the start time of the second SP is earlier than the end time of the first SP.

18. The method according to claim 17, characterized in that, The first condition also includes: The duration between the start time of the first SP and the start time of the second SP is less than or equal to the first threshold.

19. The method according to claim 17 or 18, characterized in that, The first duration satisfies the second condition, which includes at least one of the following: The duration between the start time of the second SP and the start time of the first duration is less than or equal to the second threshold; The first duration is greater than or equal to the third threshold.

20. The method according to claim 19, characterized in that, The second condition also includes: After the start time of the first duration, the low-latency service of the first AP has a lower priority than the low-latency service of the second AP.

21. A communication device, characterized in that, Includes a module for performing the method as described in any one of claims 1-20.

22. A communication device, characterized in that, The device includes a processor and a transceiver, the processor and the transceiver being coupled to enable the communication device to implement the method as described in any one of claims 1-20.

23. A chip, characterized in that, The chip includes logic circuitry and an interface, the logic circuitry and the interface being coupled such that the chip implements the method as described in any one of claims 1-20.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which, when executed by a computer, performs the method as described in any one of claims 1-20.

25. A computer program product, characterized in that, When the computer program product is executed by a computer, the method described in any one of claims 1-20 is performed.

26. A communication system, characterized in that, The system includes a first AP and a second AP, wherein the first AP is configured to perform the method as described in any one of claims 1-10, and the second AP is configured to perform the method as described in any one of claims 17-20; or... The system includes a first AP and an associated site of the first AP, wherein the first AP is configured to perform the method as described in any one of claims 1-10, and the associated site is configured to perform the method as described in any one of claims 11-16.

Images