Communication method and device

Abstract

The invention discloses a communication method and device, and the method and device support an IEEE protocol, such as an IEEE 802.11 be / Wi-Fi 7 / EHT protocol, an IEEE 802.11 bn / UHR / Wi-Fi 8 protocol, an IEEE 802.15 / UWB protocol, an IEEE 802.11 bf / perception protocol and the like. A first communication device sends a coexistence request, and a second communication device receives the coexistence request. The second communication device may determine whether to end the TXOP in advance or determine a mode of scheduling the first communication device based on the coexistence request. The coexistence request may include an identification of the coexistence request and operation type information, which may be used to indicate an operation type of the coexistence request. The coexistence request includes identification and operation type information, so that the second communication device can flexibly realize management of different coexistence requests.

Description

Technical Field

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

[0002] Currently, there is a coexistence mechanism. A communication apparatus (such as a terminal apparatus, etc.) may include a STA. The STA may be a STA belonging to a multi-link device, and the communication apparatus may further include other wireless modules. The other wireless modules may include Bluetooth (BT), ultra-wideband (UWB), Zigbee, and the fifth-generation (5 th -generation, 5G), etc. That is, the STA and the other wireless modules may coexist in the communication apparatus.

[0003] The STA in the above communication apparatus can transmit and receive signals, and the other wireless modules can also transmit and receive signals. There may be interference between the STA and the other wireless modules. In this case, the interference situation can be indicated by a coexistence request.

[0004] Therefore, the signaling indication in the coexistence request is an issue being studied by those skilled in the art. Summary of the Invention

[0005] Embodiments of this application provide a communication method and apparatus that can flexibly manage different coexistence requests.

[0006] In a first aspect, embodiments of this application provide a communication method. The method is applied to a first communication apparatus. The first communication apparatus may be a Wi-Fi device, or a chip or functional module disposed in a Wi-Fi device, etc. The method includes:

[0007] The first communication apparatus generates a coexistence request, where the coexistence request includes an identifier of the coexistence request and operation type information, and the operation type information is used to indicate the operation type of the coexistence request; the first communication apparatus sends the coexistence request.

[0008] In the embodiments of the present application, the first communication device may include a (transmit opportunity, TXOP) responder, and the second communication device may include a TXOP holder. The TXOP holder may be an access point (AP), and the TXOP responder may be a non-access point station (non-AP STA). Alternatively, the TXOP holder may be a non-AP STA, and the TXOP responder may be an AP. In the embodiments of the present application, an STA may include an AP STA (i.e., an AP) or a non-AP STA. For example, the first communication device may include an STA and other radio frequency modules (such as the radio frequency module corresponding to the radio frequency type in the coexistence request). For example, the second communication device may also include an STA and other radio frequency modules.

[0009] In the embodiments of the present application, by sending a coexistence request including an identifier and operation type information to the second communication device, the first communication device can enable the second communication device to flexibly manage different coexistence requests in combination with the identifier and perform different operations on the coexistence requests.

[0010] In a second aspect, the embodiments of the present application provide a communication method. The method is applied to a second communication device, and the second communication device may be a Wi-Fi device, or a chip or functional module disposed in a Wi-Fi device, etc. The method includes:

[0011] The second communication device receives a coexistence request, the coexistence request includes an identifier of the coexistence request and operation type information, and the operation type information is used to indicate an operation type of the coexistence request; the second communication device parses the coexistence request.

[0012] In the embodiments of the present application, by parsing the coexistence request, the second communication device can decide whether to respect the coexistence request. For example, the second communication device may perform different operations on the coexistence request based on update type information. For example, the second communication device may decide, in combination with the coexistence request: a way to schedule the first communication device (such as when the first communication device is a non-AP STA), or decide whether to end the TXOP in advance, etc., or may select a working bandwidth, or a maximum number of transceiver streams, or a maximum modulation and coding method, etc., so that the second communication device can perform different processes reasonably.

[0013] Combined with the first aspect or the second aspect, in a possible implementation manner, the operation type of the coexistence request includes any one of the following:

[0014] A newly added coexistence request; a removed coexistence request; a coexistence request for modifying parameters; or a temporarily suspended coexistence request.

[0015] In the embodiments of the present application, by indicating the above operation types, the coexistence request enables the second communication device to perform different operations in combination with different operation types.

[0016] Combined with the first aspect or the second aspect, in a possible implementation manner, the coexistence request further includes radio frequency type information, and the radio frequency type information is used to indicate the radio frequency type corresponding to the coexistence request.

[0017] In the embodiments of the present application, different radio frequency types may correspond to different service priorities. Therefore, by indicating its corresponding radio frequency type, the coexistence request enables the second communication device to determine whether to follow the coexistence request based on the radio frequency type.

[0018] Combined with the first aspect or the second aspect, in a possible implementation manner, the radio frequency type corresponding to the coexistence request includes any one of the following: Bluetooth (BT), ultra-wideband (UWB), Zigbee, fifth-generation (5G), Wi-Fi. th -generation, 5G), Wi-Fi.

[0019] In the embodiments of the present application, the first communication device may include a STA, and may further include a radio frequency module corresponding to the above radio frequency type. When the radio frequency type corresponding to the coexistence request is Wi-Fi, it may indicate that one STA in the first communication device is interfered by another STA. That is, the above Wi-Fi may be the Wi-Fi corresponding to the coexistence request in the first communication device.

[0020] Combined with the first aspect or the second aspect, in a possible implementation manner, the coexistence request further includes service priority information, and the service priority information is used to indicate the service priority of the radio frequency type corresponding to the coexistence request.

[0021] In the embodiments of the present application, based on the service priority information, the second communication device can learn about the service priority situation of the radio frequency type corresponding to the coexistence request, so that the second communication device can reasonably schedule the first communication device, enabling the first communication device to send and receive data with different service priorities in combination with the coexistence interference situation.

[0022] Combined with the first aspect or the second aspect, in a possible implementation manner, the coexistence request further includes an interference report, and the interference report is used to indicate the interference parameters of the radio frequency type corresponding to the coexistence request.

[0023] Combined with the first aspect or the second aspect, in a possible implementation manner, the interference parameter includes at least one of the following: link identifier, interference level, channel affected by interference, whether the interference is periodic, whether the interference is symmetric, interference start time, interference duration, interval between adjacent interference windows, and number of interference windows.

[0024] In the embodiments of the present application, the link identifier may indicate the identifier of the link affected by coexistence interference. The interference level may indicate the intensity or magnitude of the interference suffered by the STA in the first communication device. The channel affected by interference indicates the channel where the interference is located. The interference being periodic indicates that the interference generated by other radio frequency modules in the first communication device is periodic; the interference being aperiodic indicates that the interference generated by other radio frequency modules in the first communication device is aperiodic. Other radio frequency modules refer to other radio frequency modules (which may also include other STAs) in the first communication device except the STA. The interference being symmetric indicates that the radio frequency module corresponding to the coexistence request will cause interference to the STA in the first communication device, and this STA will also cause interference to the aforementioned radio frequency module; the interference being asymmetric indicates that the radio frequency module corresponding to the coexistence request causes interference to the STA, and this STA will not cause interference to the aforementioned radio frequency module, or the interference caused by the STA to the aforementioned radio frequency module is less than a certain threshold. The interference start time and the interference duration can be used to indicate the start time and duration of the coexistence interference. When the interference is periodic, it means that the interference will appear at a certain period. For example, the start time of the interference appearance is indicated by the interference start time, and the interference duration within one period is indicated by the interference duration. For example, the interference duration can also be referred to as an interference window. When the interference is periodic, the interference report may further include the interval between adjacent interference windows or the number of interference windows.

[0025] Combined with the first aspect or the second aspect, in a possible implementation manner, the coexistence request further includes expected behavior information, and the expected behavior information is used to indicate the expected behavior of the STA in the first communication device.

[0026] Combined with the first aspect or the second aspect, in a possible implementation manner, the coexistence request further includes time information, and the time information is used to indicate the time period corresponding to the expected behavior.

[0027] In the embodiments of the present application, combined with the expected behavior information and the time information, the first communication device can indicate the behavior expected by the STA during the time period indicated by the time information through these two pieces of information.

[0028] Combined with the first aspect or the second aspect, in a possible implementation manner, the expected behavior of the first communication device includes any one of the following:

[0029] Allowed to send signals; restricted received signals; allowed to receive signals; restricted transmitted signals; or not allowed to send signals nor receive signals.

[0030] Combined with the first aspect or the second aspect, in a possible implementation, the coexistence request further includes receiving parameters when the first communication device receives restricted signals, or transmitting parameters when the first communication device transmits restricted signals.

[0031] Combined with the first aspect or the second aspect, in a possible implementation, the transmitting parameters include at least one of the following: link identifier, maximum number of flows (or maximum number of spatial streams (number of spatial streams, NSS)), maximum transmit power (max Tx power), minimum transmit power, expected receive redundancy (expected Rx margin), expected maximum data length (or referred to as maximum TB - PPDU length (max TB - PPDU length)), expected bandwidth (expected bandwidth, expected BW), modulation and coding scheme, or maximum LDPC codeword length (max LDPC codeword length).

[0032] Combined with the first aspect or the second aspect, in a possible implementation, the receiving parameters include at least one of the following: link identifier, maximum number of flows, expected receive redundancy, expected maximum data length, expected bandwidth, modulation and coding scheme, or maximum LDPC codeword length.

[0033] Combined with the first aspect or the second aspect, in a possible implementation, the coexistence request is carried in an initial control frame (ICF) or an initial control response (ICR) frame, and the ICF or the ICR frame further includes listening mode enabling information, and the listening mode enabling information is used to indicate that the first communication device turns on the listening mode (or referred to as the monitoring mode) or exits the listening mode.

[0034] Combined with the first aspect or the second aspect, in a possible implementation, the coexistence request further includes listening mode enabling information, and the listening mode enabling information is used to indicate that the first communication device turns on the listening mode or exits the listening mode.

[0035] In combination with the first aspect or the second aspect, in a possible implementation, when the listening mode enabling information is a first value, it indicates that the first communication device exits the listening mode, and the mode to which the first communication device is to be switched is determined based on power management information; or, when the listening mode enabling information is a second value, it indicates that the first communication device enables the listening mode, and the state of the first communication device is determined based on at least one of power management information or more data information.

[0036] In combination with the first aspect, in a possible implementation, the method further includes: the first communication device receives a feedback result of the coexistence request from the second communication device.

[0037] In the embodiments of the present application, by sending a feedback result, the second communication device can enable the first communication device to effectively learn whether the second communication device follows the coexistence request, so as to learn the processing result of the second communication device and improve communication efficiency.

[0038] In combination with the second aspect, in a possible implementation, the method further includes: the second communication device sends a feedback result of the coexistence request to the first communication device.

[0039] In combination with the first aspect or the second aspect, in a possible implementation, the feedback result includes a buffer report, and the buffer report includes at least one of the following: the size of the buffered data, the minimum remaining time of the buffered data, or the service priority of the buffered data; or, the feedback result includes more data fields for indicating the state of the first communication device; or, the feedback result includes an indication information for indicating that the scheduling of the first communication device within the current transmission opportunity TXOP has ended.

[0040] In a third aspect, an embodiment of the present application provides a first communication device for executing the method in the first aspect or any possible implementation. The first communication device includes a module for executing the method in the first aspect or any possible implementation.

[0041] In a fourth aspect, an embodiment of the present application provides a second communication device for executing the method in the second aspect or any possible implementation. The second communication device includes a module for executing the method in the second aspect or any possible implementation.

[0042] In a fifth aspect, an embodiment of the present application provides a first communication device. The first communication device includes a processor for executing the method shown in the first aspect or any possible implementation. The processor is used to execute a program stored in a memory, and when the program is executed, the method shown in the first aspect or any possible implementation is executed.

[0043] In a possible implementation, the memory is located outside the above-mentioned first communication device.

[0044] In a possible implementation, the memory is located inside the above-mentioned first communication device.

[0045] In the embodiments of the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together. Exemplarily, the first communication device may be a chip.

[0046] In a possible implementation, the first communication device further includes a transceiver, which is used to receive information or send information. Exemplarily, the first communication device may be a multi-link device (MLD).

[0047] In a sixth aspect, an embodiment of the present application provides a second communication device, which includes a processor for executing the method shown in the above second aspect or any possible implementation. The processor is used to execute a program stored in the memory, and when the program is executed, the method shown in the above second aspect or any possible implementation is executed.

[0048] In a possible implementation, the memory is located outside the above-mentioned second communication device.

[0049] In a possible implementation, the memory is located inside the above-mentioned second communication device.

[0050] In the embodiments of the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together. Exemplarily, the second communication device may be a chip.

[0051] In a possible implementation, the second communication device further includes a transceiver, which is used to receive information or send information. Exemplarily, the first communication device may be a multi-link device.

[0052] In a seventh aspect, an embodiment of the present application provides a first communication device, which includes a logic circuit and an interface, and the logic circuit and the interface are coupled; the interface is used for inputting and / or outputting information, and the logic circuit is used to execute the method as described in the first aspect or any possible implementation.

[0053] In an eighth aspect, an embodiment of the present application provides a second communication device, which includes a logic circuit and an interface, and the logic circuit and the interface are coupled; the interface is used for inputting and / or outputting information, and the logic circuit is used to execute the method as described in the second aspect or any possible implementation.

[0054] In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when running on a computer, causes the method shown in any one of the first aspect to the second aspect or any possible implementation manner to be executed.

[0055] In a tenth aspect, an embodiment of the present application provides a computer program product, which, when running on a computer, causes the method shown in any one of the first aspect to the second aspect or any possible implementation manner to be executed.

[0056] In an eleventh aspect, an embodiment of the present application provides a computer program, which, when running on a computer, causes the method shown in any one of the first aspect to the second aspect or any possible implementation manner to be executed.

[0057] In a twelfth aspect, an embodiment of the present application provides a communication system, which includes a first communication device and / or a second communication device. The first communication device is used to execute the method shown in the first aspect or any possible implementation manner of the first aspect, and the second communication device is used to execute the method shown in the second aspect or any possible implementation manner of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application;

[0059] Figure 2a is a schematic diagram of the architecture of another communication system provided by an embodiment of the present application;

[0060] Figure 2b is a schematic diagram of the address of an MLD provided by an embodiment of the present application;

[0061] Figure 3 is a schematic diagram of the framework of a communication device provided by an embodiment of the present application;

[0062] Figure 4a is a schematic diagram of the format of an MPDU provided by an embodiment of the present application;

[0063] Figure 4b is a schematic diagram of the format of a frame control field provided by an embodiment of the present application;

[0064] Figure 4c is a schematic diagram of the format of an aggregated-control (A-control) field provided by an embodiment of the present application;

[0065] Figure 5 is a schematic diagram of the flow of a communication method provided by an embodiment of the present application;

[0066] Figure 6a It is a schematic diagram of the format of an expected behavior field provided by an embodiment of the present application;

[0067] Figure 6b It is a schematic diagram of the format of a coexistence request provided by an embodiment of the present application;

[0068] Figure 7 It is a schematic diagram of the process of a communication method provided by an embodiment of the present application;

[0069] Figure 8a It is a schematic diagram of the format of a trigger frame provided by an embodiment of the present application;

[0070] Figure 8b It is a schematic diagram of the format of an extremely high throughput trigger based PPDU (EHT TB PPDU) provided by an embodiment of the present application;

[0071] Figure 8c It is a schematic diagram of the format of an ultra high reliability (UHR) TB PPDU provided by an embodiment of the present application;

[0072] Figure 8d It is a schematic diagram of the format of a multi-STA block acknowledgement (multi-STA BA) frame provided by an embodiment of the present application;

[0073] Figure 9 It is a schematic diagram of the structure of a communication device provided by an embodiment of the present application;

[0074] Figure 10 It is a schematic diagram of the structure of a communication device provided by an embodiment of the present application;

[0075] Figure 11 It is a schematic diagram of the structure of a communication device provided by an embodiment of the present application. Detailed implementation manners

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

[0077] In the description, claims, and drawings of this application, terms such as "first" and "second" are only used to distinguish different objects, rather than to describe a specific order. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device, etc. that includes a series of steps or units is not limited to the listed steps or units, but may optionally further include steps or units not listed, or may optionally further include other steps or units inherent to these processes, methods, products, or devices, etc.

[0078] As used herein, "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment can be included in at least one embodiment of this application. The phrase appearing in various positions in the description does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art can explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.

[0079] In this application, "at least one (item)" means one or more, "a plurality" means two or more, "at least two (items)" means two or three or more, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist. For example, "A and / or B" can represent: only A exists, only B exists, and both A and B exist simultaneously. Here, A and B can be singular or plural. "Or" indicates that two relationships can exist, such as only A exists and only B exists; when A and B are not mutually exclusive, it can also represent three relationships, such as only A exists, only B exists, and both A and B exist simultaneously. The character " / " generally represents an "or" relationship between the associated objects before and after. "At least one (one) of the following" or a similar expression means any combination of these items. For example, at least one (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".

[0080] In this application, "indicating" may include direct indication, indirect indication, display indication, and implicit indication. When it is described that a certain indication information is used to indicate A, it can be understood that this indication information carries A, directly indicates A, or indirectly indicates A.

[0081] In this application, the information indicated by the indication information is referred to as the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated. For example, but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. It is also possible to indirectly indicate the information to be indicated by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to only indicate a part of the information to be indicated, while the other parts of the information to be indicated are known or pre-agreed. For example, it is also possible to use the arrangement order of each piece of information pre-agreed (such as stipulated in the protocol) to implement the indication of specific information, thereby reducing the indication overhead to a certain extent. In addition, the information to be indicated can be sent as a whole, or can be divided into multiple sub-information and sent separately, and the sending periods and / or sending opportunities of these sub-information can be the same or different.

[0082] In this application, "sending" and "receiving" represent the direction of signal transmission. For example, "sending information to XX" can be understood as the destination of the information is XX, which can include directly sending through the air interface, and also includes indirectly sending through the air interface by other units or modules. "Receiving information from YY" can be understood as the source of the information is YY, which can include directly receiving from YY through the air interface, and can also include indirectly receiving from YY through the air interface from other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface. In other words, sending and receiving can be carried out between devices. For example, between a network device and a terminal device, or can also be carried out within a device. For example, sending or receiving between components, modules, chips, software modules or hardware modules within a device through a bus, trace or interface.

[0083] This application provides a communication method and apparatus, which can flexibly manage coexistence requests.

[0084] The following introduces the communication system involved in the embodiments of this application.

[0085] The technical solutions provided by the embodiments of the present application can be applied to a wireless local area network (WLAN) system, such as Wi-Fi. For example, the methods provided by the embodiments of the present application can be applicable to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of protocols, such as the 802.11be protocol, the 802.11bn protocol (802.11bn is also known as Wi-Fi 8, or ultra-high reliability (UHR), or ultra-high reliability and throughput (UHRT), or the next-generation protocol of the 802.11bn protocol, or a protocol that supports ambient power (AMP), etc., which will not be listed one by one. The technical solutions provided by the embodiments of the present application can also be applied to a wireless personal area network (WPAN) based on millimeter wave (MMW) and ultra-wideband (UWB) technologies. For example, the methods provided by the embodiments of the present application can be applicable to the IEEE 802.15 series of protocols, such as the 802.15.4a protocol, the 802.15.4z protocol, or the 802.15.4ab protocol, or a future generation of UWB WPAN protocol, etc., which will not be listed one by one. The technical solutions provided by the embodiments of the present application can also be applied to the following communication systems. For example, it can be an Internet of Things (IoT) system, vehicle-to-everything (V2X, where X can represent anything), device-to-device (D2D), narrow-band Internet of Things (NB-IoT) system, long-term evolution (LTE) system, fifth-generation (5G) communication system, and new communication systems that emerge in the future development of communications. For example, the V2X can include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-network (V2N) communication, etc.

[0086] WLAN systems can provide high-speed and low-latency transmission. As the application scenarios of WLAN continue to evolve, WLAN systems will be applied to more scenarios or industries. For example, they can be applied to the Internet of Things industry, the vehicle-to-everything (V2X) industry, the banking industry, enterprise offices, stadiums and exhibition halls, concert halls, hotel rooms, dormitories, wards, classrooms, shopping malls, squares, streets, production workshops, and warehouses. Of course, devices that support WLAN communication or sensing (such as access points or stations) can be sensor nodes in a smart city (such as smart water meters, smart electricity meters, and smart air detection nodes), smart devices in a smart home (such as smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (such as wearable devices like augmented reality (AR) and virtual reality (VR)), smart devices in intelligent office environments (such as printers, projectors, loudspeakers, speakers, etc.), vehicle-to-everything (V2X) devices in the vehicle-to-everything industry, infrastructure in daily life scenarios (such as vending machines, self-guided navigation stations in shopping malls, self-checkout devices, self-ordering machines, etc.), and devices in large sports and music venues.

[0087] Although the embodiments of this application mainly take WLAN as an example, especially networks that apply the IEEE 802.11 series of standards. All aspects involved in the embodiments of this application can be extended to other networks that adopt various standards or protocols. For example, Bluetooth, high performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard), and wide area network (WAN) or other currently known or future-developed networks.

[0088] The method provided by the embodiments of this application can be implemented by a communication device in a communication system. For example, the communication device can be an access point (AP), a station (STA), or a multi-link device. The following is a detailed description:

[0089] An AP is a device with wireless communication capabilities that supports communication, sensing, or energy transfer using the WLAN protocol. It has the function of communicating, sensing, or transferring energy with other devices (such as non-access point stations (non-AP STAs) or other access points) in the WLAN network. Of course, it can also have the function of communicating, sensing, or transferring energy with other devices. Alternatively, the access point is equivalent to a bridge connecting a wired network and a wireless network. Its main role is to connect various wireless network clients together and then connect the wireless network to the Ethernet. In a WLAN system, the access point can be referred to as an access point station (AP STA). The device with wireless communication capabilities can be a complete device or a chip, processing system, or functional module installed in the complete device. The device installed with these chips, processing systems, or functional modules can, under the control of the chips, processing systems, or functional modules, implement the methods and functions of the embodiments of the present application. The AP in the embodiments of the present application is a device that provides services for non-AP STAs and can support 802.11 series protocols or subsequent protocols, etc. For example, the access point can be an access point for a terminal (such as a mobile phone) to enter a wired (or wireless) network, mainly deployed in homes, buildings, and campuses, with a typical coverage radius of dozens of meters to hundreds of meters. Of course, it can also be deployed outdoors. For another example, the AP can be a communication entity such as a communication server, router, switch, or bridge; the AP can include various forms of macro base stations, micro base stations, relay stations, etc. Of course, the AP can also be a chip, processing system, or module in the above various forms of devices to implement the methods and functions of the embodiments of the present application. The description of the AP here also applies to the AP multi-link device (AP MLD) shown below.

[0090] STA is a device with wireless communication capabilities, supporting communication, sensing, or energy transfer using the WLAN protocol, and having the ability to communicate, sense, or transfer energy with other non-AP STAs or access points in the WLAN network. In a WLAN system, a station can be referred to as a non-access point station (non-AP STA). For example, an STA is any user communication device that allows a user to communicate, sense, or transfer energy with an AP and thereby communicate with the WLAN. This device with wireless communication capabilities can be a complete device, or it can be a chip, processing system, or functional module installed in a complete device. The device installing these chips, processing systems, or functional modules can, under the control of the chip, processing system, or functional module, implement the methods and functions of the embodiments of this application. For example, an STA can be a wireless communication chip, wireless sensor, or wireless communication terminal, etc., and can also be referred to as a user. Another example is that an STA can be a mobile phone supporting Wi-Fi communication function, a tablet computer supporting Wi-Fi communication function, a set-top box supporting Wi-Fi communication function, a smart TV supporting Wi-Fi communication function, a smart wearable device supporting Wi-Fi communication function, a vehicle-mounted communication device supporting Wi-Fi communication function, and a computer supporting Wi-Fi communication function, etc. Of course, an STA can also be a chip, processing system, or module in the above various forms of devices to implement the methods and functions of the embodiments of this application. The description of STA here also applies to the non-AP multi-link device (non-AP MLD) shown below.

[0091] For ease of description, in the following when referring to specific examples, an STA can include an AP STA (or referred to as an AP) or a non-AP STA.

[0092] A multi-link device (MLD) refers to a device that simultaneously has multiple STAs (such as an AP or a non-AP STA), each operating on a different frequency band or channel. When the channel spacing between two stations within a multi-link device is large enough, they can operate independently without interfering with each other. If any two stations support one station transmitting while the other is receiving, it can be said that the two stations support simultaneous transmitting and receiving (STR) capabilities; otherwise, it is said that the two stations do not have non-simultaneous transmitting and receiving (NSTR) capabilities. A multi-link device includes multiple subordinate stations, which can be physical stations or logical stations. Each station can operate on a single link, frequency band, channel, etc. The subordinate stations shown here can be APs or non-AP STAs. For ease of description, in the embodiments of this application, a multi-link device with an AP as a subordinate station can be referred to as a multi-link AP, a multi-link AP device, or an AP multi-link device (AP MLD). A multi-link device with a non-AP STA as a subordinate station is called a multi-link STA, a multi-link STA device, or a STA multi-link device (STA MLD). Alternatively, a multi-link device with a non-AP STA as a subordinate station is called a multi-link non-AP, a multi-link non-AP device, or a non-AP multi-link device (non-AP MLD). A multi-link device (which can be either a non-AP MLD or an AP MLD here) is a communication device with wireless communication capabilities. This communication device can be a complete device, or it can be a chip or a processing system installed in a complete device. The device installed with these chips or processing systems can, under the control of these chips or processing systems, implement the methods and functions of the embodiments of this application.

[0093] Figure 1 It is a schematic diagram of the architecture of a communication system provided by the embodiments of this application. As Figure 1As shown, embodiments of the present application can be applicable to scenarios such as communication or sensing between an AP and a non-AP STA, between APs, or between non-AP STAs in a WLAN. Embodiments of the present application do not limit this. Exemplarily, an AP can communicate or sense with a single non-AP STA, or an AP can communicate or sense with multiple non-AP STAs simultaneously. Exemplarily, the communication or sensing between an AP and multiple non-AP STAs can be further divided into a downlink transmission where the AP sends signals to multiple non-AP STAs simultaneously, and an uplink transmission where multiple non-AP STAs send signals to the AP. Exemplarily, AP1 can be an AP belonging to an AP MLD, or AP2 can be an AP belonging to an MLD. Exemplarily, non-AP STA1 or non-AP STA2 or non-AP STA3 can be a non-AP STA belonging to a non-AP MLD. Among them, between an AP and a non-AP STA, between APs, and between non-AP STAs and non-AP STAs, a WLAN communication protocol can be supported. This communication protocol can include protocols in the IEEE 802.11 series, such as being applicable to the 802.11bn protocol, and of course it is also applicable to protocols after 802.11bn.

[0094] Figure 1 Taking a non-AP STA as a mobile phone and an AP as a router as an example does not limit the types of APs and non-AP STAs in embodiments of the present application. At the same time, Figure 1 The number of APs and non-AP STAs shown is only an example. In specific implementations, the number of such APs or non-AP STAs can be more or less. Embodiments of the present application do not limit this.

[0095] Figure 2a It is a schematic diagram of the architecture of another communication system provided by embodiments of the present application. The 802.11 standard focuses on the physical layer (PHY) and medium access control (MAC) layer parts in multi-link devices. Therefore, Figure 2a Exemplarily, the PHY and MAC layers are shown.

[0096] As Figure 2a shown, a multi-link device (such as a multi-link AP or a multi-link non-AP) can include a physical layer (PHY) (such as Figure 2aThe physical layer (e.g., PHY#1 and PHY#2 as shown) and the medium access control (MAC) layer. The physical layer can be used to process physical layer signals, and the MAC layer can be used to process MAC layer signals. Further, in the MAC layer, it can be further divided into a high-MAC layer (such as the high-MAC as shown in Figure 2a and multiple low-MAC layers (such as the low-MAC#1 and low-MAC#2 as shown in Figure 2a ). As shown in Figure 2a , the multiple APs included in the multi-link AP are independent of each other in the low-MAC layer and PHY, and share the high-MAC layer. The multiple STAs included in the multi-link non-AP are independent of each other in the low-MAC layer and PHY, and share the high-MAC layer. The high-MAC layer is respectively connected to the multiple low-MAC layers, and the high-MAC layer can be shared by multiple links. Exemplarily, the high-MAC layer mainly completes operations such as the allocation of the sequence number (SN) and packet number (PN) of the MAC service data unit (MSDU) and encryption and decryption. Exemplarily, the low-MAC layer mainly completes operations such as the assembly of the MAC protocol data unit (MPDU) of its respective link, channel access, packet transmission, and reception confirmation. The functions implemented by the high-MAC layer or low-MAC layer shown here are only examples and should not be construed as limitations on the embodiments of the present application.

[0097] In Figure 2a , the PHY#1 layer, low-MAC#1 layer, and high-MAC layer in the multi-link AP can be regarded as AP#1, and the PHY#2 layer, low-MAC#2 layer, and high-MAC layer can be regarded as AP#2. That is to say, the multi-link AP can include 2 AP entities. In the multi-link non-AP, the situation is similar, that is, the high-MAC layer in the multi-link non-AP is also shared by multiple links. The PHY#1 layer, low-MAC#1 layer, and high-MAC layer are regarded as STA#1 (or non-AP STA#1), and the PHY#2 layer, low-MAC#2 layer, and high-MAC layer are regarded as STA#2 (or non-AP STA#2). That is to say, the multi-link non-AP includes 2 STA entities (i.e., 2 non-AP STA entities). As shown in Figure 2a , the PHY#1 of AP#1 in the multi-link AP and the PHY#1 of STA#1 in the multi-link non-AP work on the same channel. For example, AP#1 in the multi-link AP and STA#1 in the multi-link non-AP are connected through a link (such as Figure 2aThe link shown in #1) enables communication. The PHY #2 of AP #2 in the multi-link AP and the PHY #2 of STA #2 in the multi-link non-AP operate on another same channel. For example, AP #2 in the multi-link AP and STA #2 in the multi-link non-AP communicate through a link (such as Figure 2a the link shown in #2).

[0098] Exemplarily, the high MAC layer or the low MAC layer can be implemented by a processor in the chip system of the multi-link device, or can be respectively implemented by different software processing modules in a chip system, etc., which are not enumerated in the embodiments of this application. Figure 2a It can be a division of functional modules of the multi-link device. Figure 2a Each of the modules shown can be implemented in the form of hardware or in the form of software function modules, etc. Figure 2a The PHY and MAC layers shown can be understood as a division of logical functions, and there can be other division methods in actual implementation. Figure 2a It is shown by taking the multi-link device including two stations as an example. In specific implementation, the multi-link device can also include more or fewer stations, which are not enumerated here. In the embodiments of this application, the frequency bands in which the multi-link device operates can include but are not limited to: sub 1GHz, 2.4GHz, 5GHz, 6GHz, etc., which are not listed one by one here.

[0099] For the non-AP MLD, it can simultaneously establish associations with multiple links of the AP MLD by performing multi-link establishment operations on one of its links. Among them, the link for exchanging the multi-link association request frame or the multi-link association response frame is called the transmitted link, and other links are called non-transmitted links. The multi-link association request frame or the multi-link association response frame can carry information of multiple links to achieve simultaneous association of multiple links. For the process of multi-link establishment or association, relevant standards or protocols can be referred to, which are not elaborated here.

[0100] Figure 2b It is a schematic diagram of the address of an MLD provided by the embodiments of this application. As Figure 2b shown, for a multi-link device, each link in each multi-link device can correspond to a link address. For example, Figure 2bThe link address 1 and link address 2 therein, and the multi-link device may also correspond to an MLD MAC address. Taking Figure 2a the architecture shown as an example, the high MAC layer can be uniquely identified by the MAC address corresponding to the MLD, and the low MAC layer can be uniquely identified by the MAC address corresponding to the link. For example, Low MAC#1 and Low MAC#2 can respectively correspond to the MAC addresses of their respective corresponding links. The MLD MAC address can also be referred to as the MLD high MAC layer address, and the link address can also be referred to as the MLD low MAC layer address. The IDs within the MLD shown below can be similar to Figure 2b the MLD MAC address shown.

[0101] Figure 3 FIG. th is a schematic framework diagram of a communication device provided by an embodiment of the present application. The communication device supports a coexistence mechanism inside the device. For example, the communication device may include an MLD (such as an AP MLD or a non-AP MLD), and the MLD includes a Wi-Fi radio frequency module (or referred to as Wi-Fi radio frequency or Wi-Fi module). In addition to the MLD, other wireless modules may also be provided in the communication device. Other wireless modules may include, but are not limited to: a Bluetooth (BT) module, a UWB module, a Zigbee module, a fifth-generation (5 th -generation, 5G) module, etc. For example, the above wireless modules may include radio frequency modules, and the above BT module or UWB module, etc. may also include corresponding radio frequency modules. Of course, in addition to radio frequency modules, the wireless modules may also include other modules, which are not listed here. The radio frequency modules shown below may also represent the wireless modules of the radio frequency modules.

[0102] Figure 3 The interface therein may include a coexistence coordination interface. The coexistence coordination interface can be used to obtain coexistence requests sent by other radio frequency modules. Coexistence request #n is the coexistence request corresponding to the BT module, and coexistence request #m is the coexistence request corresponding to the 5G module. The format of the coexistence requests sent by other radio frequency modules to the STA may be the same as the format of the coexistence requests sent by the STA to other STAs, or, alternatively, may be different. The embodiments of the present application do not limit the format of the coexistence requests sent by other radio frequency modules to the TA. The radio frequency modules shown below sending and receiving signals or caching data, etc. can be understood as the corresponding wireless modules sending and receiving signals or caching data.

[0103] Exemplarily, there may be interference between different radio frequency modules, and such interference may be asymmetric or symmetric. Exemplarily, certain resources may be shared between different radio frequency modules, such as operating on the same channel, or sharing the same antenna or multiple antennas, etc. Figure 3 Taking the example where the MLD includes STA1 and STA2, in a specific implementation, the MLD may further include more or fewer STAs. Figure 3 The communication device shown is also applicable to the first communication device or the second communication device. For example, the first communication device may include an STA (such as STA 1), and may further include other radio frequency modules coexisting with the STA (the other radio frequency modules may include STA 2). The STA in the first communication device can transmit and receive signals, and the above-mentioned other radio frequency modules can also transmit and receive signals. That is, there is a situation where the STA and other radio frequency modules coexist within the first communication device, and coexistence interference may occur during the coexistence process.

[0104] In the embodiments of the present application, the non-AP MLD may include the UHR non-AP MLD, and the AP MLD may include the UHR AP MLD. The specific product forms of the AP MLD or the non-AP MLD are not limited in the embodiments of the present application.

[0105] From different perspectives of sending and receiving coexistence requests, the first communication device shown below may be a communication device that sends a coexistence request, and the second communication device may be a communication device that receives a coexistence request. Alternatively, the first communication device may also be referred to as a sending end, and the second communication device may also be referred to as a receiving end.

[0106] From the perspective of the TXOP holder and the TXOP responder, the first communication device shown below may include the TXOP responder, and the second communication device may include the TXOP holder. As an example, the AP may act as the TXOP holder, and the non-AP STA may act as the TXOP responder, such as when there are other radio frequency modules inside the device where the non-AP STA is located. As another example, the non-AP STA may also act as the TXOP holder, and the AP may act as the TXOP responder, such as when there are other radio frequency modules inside the device where the AP is located. As yet another example, there are other radio frequency modules inside both the TXOP holder and the TXOP responder. For example, the above-mentioned AP or the above-mentioned non-AP STA may also be the AP or non-AP STA belonging to the MLD.

[0107] The embodiments of the present application describe the method provided by the present application from the perspectives of the first communication device and the second communication device. However, during the signal transmission process between the first communication device and the second communication device, the signal can also be forwarded by other devices, such as forwarding the signal between the first communication device and the second communication device through a forwarding device. The embodiments of the present application do not limit other devices other than the first communication device and the second communication device.

[0108] The following introduces the terms related to the embodiments of the present application.

[0109] 1. Medium Protocol Data Unit (MPDU)

[0110] Figure 4a It is a format schematic diagram of an MPDU provided by the embodiments of the present application. As Figure 4a shown, the MPDU may include at least one of the following: Frame Control, Duration, Address 1, Address 2, Address 3, Sequence Control, Quality of Service (QoS) Control, High Throughput (HT) Control, Frame Body, or Frame Check Sequence (FCS). For the descriptions of each field, reference can be made to relevant standards or protocols, which will not be elaborated here.

[0111] Figure 4b It is a format schematic diagram of the frame control field provided by the embodiments of the present application. As Figure 4b shown, the frame control field may include at least one of the following: Protocol Version, Type, Subtype, To Distributed System (DS), From DS, More Fragment, Retry, Power Management, More Data, Protected Frame, and the presence of HT Control (HCT).

[0112] The power management field is used to indicate the power management mode of the transmitting end. The more data field is used to indicate whether the transmitting end still has buffered data to be received by the receiving end that is in the power saving mode. The transmitting end can switch back and forth between the awake state and the sleep state in the power saving mode. If the transmitting end has data to be received, it remains in the awake state; if there is no data to be received, it switches to the sleep state. For the descriptions of other fields, reference can be made to relevant standards or protocols, which will not be elaborated here. The transmitting end shown here is the communication device that transmits the above MPDU, and the receiving end can be the device that receives the MPDU.

[0113] Exemplarily, the format of the HT control field can be as shown in Table 1. Based on the settings of B1 and B1, the HT control field can have different formats. Of course, Table 1 is only an example, and as the standard progresses, the HT control field can also have other formats. The relationship between the values and meanings of each bit shown in Table 1 is only an example and should not be construed as a limitation on the embodiments of the present application.

[0114] Table 1

[0115]

[0116] Figure 4c is a schematic diagram of the format of an A-control field provided by an embodiment of the present application. As Figure 4c shown, the A-control field can include a control list and padding. The control list field can include one or more control fields, and the control field can include a control identifier and control information.

[0117] The number of bits (or bytes) occupied by each field, the order between different fields, etc. given in the drawings of the embodiments of the present application are only examples and should not constitute a limitation on the format, frame length, or the order of each field proposed by the embodiments of the present application. The names of each frame and the fields included in the drawings of the embodiments of the present application are only examples and should not constitute a limitation on each frame proposed by the embodiments of the present application. For ease of description, each embodiment shown in the present application is illustrated by taking "field" as an example, without specifically distinguishing between "field", "sub-field", "element", "sub-element", etc. Although each embodiment shown in the present application does not specifically distinguish between "field", "sub-field", "element", "sub-element", those skilled in the art can adaptively distinguish the relationships between the various fields shown in the embodiments of the present application.

[0118] 2. Transmit Opportunity (TXOP)

[0119] A transmission opportunity refers to a bounded time period during which a device (such as an AP or a non-AP STA) can transmit a specific type of communication. The specific duration can be indicated by the duration field in the MPDU header (such as Figure 4a ). In the enhanced distributed channel access (EDCA) scenario, the device can obtain a TXOP through the channel access process. Once the TXOP is obtained, the device can continue to transmit data frames, control frames, and management frames, as well as receive response frames, etc. The duration of these frames does not exceed the TXOP upper limit set for the corresponding access category (AC).

[0120] Generally speaking, a device that obtains a TXOP can be called a TXOP holder, and the corresponding receiving end can be called a TXOP responder.

[0121] 3. Coexistence Request

[0122] When there is coexistence interference between different radio frequency modules in a device, the radio frequency module can generate a coexistence request. This coexistence request can be used to coordinate the coexistence interference between different radio frequency modules. For example, the coexistence request can include information about other radio frequency modules and / or information about the STA. For Figure 3 example, the coexistence request can be a coexistence request initiated by the BT module, or a coexistence request initiated by the UWB module, or a coexistence request initiated by the ZigBee module, or a coexistence request initiated by the 5G module.

[0123] As an example, the coexistence request sent by the first communication device can be a coexistence request of a radio frequency module inside the device. For example, a coexistence request obtained by the STA (or the MLD to which the STA belongs) through an interface from a radio frequency module.

[0124] As another example, the coexistence request sent by the first communication device is a coexistence request after merging multiple radio frequency modules inside the device. For example, after the STA (or the MLD to which the STA belongs) obtains coexistence requests from multiple radio frequency modules through an interface, the coexistence requests of the multiple radio frequency modules can be merged into one coexistence request. For example, when there is coexistence interference between different radio frequency modules in a device, the STA (or the MLD to which the STA belongs) can merge multiple coexistence requests into one coexistence request after receiving coexistence requests sent by other radio frequency modules.

[0125] The methods involved in the embodiments of the present application are introduced below.

[0126] Figure 5It is a schematic flowchart of a communication method provided by an embodiment of the present application. As Figure 5 shown, the method includes:

[0127] 501. The first communication device sends a coexistence request. Correspondingly, the second communication device receives the coexistence request.

[0128] When the first communication device is an MLD, the coexistence request can be sent by the STA affiliated with the MLD. Exemplarily, before the first communication device sends the coexistence request, it can also obtain or generate the coexistence request. For example, the step of obtaining the coexistence request can be executed by the above STA. As an example, the step of generating the coexistence request can be executed by the above STA. As another example, the step of generating the coexistence request can be executed by the processing module in the MLD. The present application embodiment does not limit which chip or functional module generates the coexistence request specifically.

[0129] As an example, the coexistence request can be included in a control frame or a management frame. The format of the control frame or management frame can refer to the description of the MPDU shown in Figure 4a and will not be elaborated here. For example, the coexistence request can be carried in the frame body field.

[0130] As another example, the coexistence request can be included in a data frame. The format of the data frame can refer to the description of the MPDU shown in Figure 4a and will not be elaborated here. For example, the coexistence request can be carried in the control information field in the A-control field. The format of the A-control field can refer to Figure 4c . The above control frame, management frame or data frame can be collectively referred to as a wireless frame.

[0131] Exemplarily, the coexistence request can be included in an ICF or an ICR frame. For example, when the first communication device includes an AP, the coexistence request can be included in the ICF. Another example is that when the first communication device includes a non-AP STA, the coexistence request can be included in the ICR frame.

[0132] In the embodiment of the present application, by sending the coexistence request, the first communication device enables the second communication device to make a reasonable decision (or called processing) in combination with the coexistence request. The decision can include but is not limited to: ending the current TXOP in advance, ending the scheduling of the first communication device within the current TXOP (that is, not scheduling the first communication device within the current TXOP), reasonably scheduling the first communication device, or selecting the working bandwidth, maximum number of transceiver streams, or maximum modulation and coding method, etc.

[0133] 502. The second communication device parses the coexistence request.

[0134] Example 1, the TXOP holder can respect and follow the coexistence requests from one or more TXOP responders and schedule transmissions based on the coexistence requests. Meanwhile, the STA (such as a non-AP STA or an AP) can also remove or suspend or modify the coexistence requests (such as the operation type information shown below).

[0135] Example 2, the TXOP holder can have the final decision-making power. For example, as the TXOP holder, the AP can decide how to schedule transmissions or whether to end the TXOP in advance according to the coexistence requests from one or more non-AP STAs. The ways to end the TXOP in advance can include: the TXOP holder sends a contention-free end (CF-end) to instruct the TXOP responder to end this TOXP in advance. For example, by parsing the coexistence request, the second communication device can know whether it is necessary to end the TXOP in advance. By sending a coexistence request to the second communication device, the first communication device can enable the second communication device to effectively know the coexistence interference situation inside the first communication device. Thus, the second communication device can end the TXOP in advance and no longer schedule the transmission of the first communication device within this TXOP. Another example is that when the second communication device is an AP, the second communication device can know how to specifically schedule the non-AP STA. For example, the AP can not schedule the non-AP STA or reduce the modulation and coding strategy during the time when the non-AP STA has coexistence interference.

[0136] For the steps performed by the second communication device, reference can also be made to the description of the feedback result below, which will not be elaborated here for the time being.

[0137] The coexistence requests involved in the embodiments of the present application are introduced below.

[0138] The coexistence request includes at least one of the following: identification, operation type information, radio frequency type information, service priority information, interference report, expected behavior information, or listening mode enabling information. The following is a detailed description.

[0139] It should be understood that the above-mentioned various information can be included in the coexistence request at the same time; or when the coexistence request is included in a wireless frame, some of the above information can be carried in other elements or other fields in the wireless frame other than the coexistence request, and the other part of the information is carried in the coexistence request in the wireless frame. The specific position or order in the coexistence request or the wireless frame is not limited in the embodiments of the present application.

[0140] For ease of description, in the following when referring to specific examples, it is assumed that the first communication device includes a TXOP responder, with a non-AP STA as the TXOP responder, and the second communication device includes a TXOP holder, with an AP as the TXOP holder. However, this should not be construed as a limitation on the embodiments of the present application.

[0141] (1) Identifier

[0142] The identifier can be used to uniquely identify a coexistence request. For example, the identifier can include a coexistence request identifier (ID) (coexistencerequest ID). To facilitate the management of coexistence requests between different radio frequency modules, the first communication device can assign an identifier to each coexistence request, such as a coexistence request ID. The coexistence request ID assigned by the first communication device can be within the MLD range. For example, the coexistence request ID can be an ID within the MLD range that the first communication device can assign.

[0143] Exemplarily, the identifier can be carried in the coexistencerequest ID field in the coexistence request.

[0144] By carrying the coexistence request ID in the coexistence request, the second communication device can flexibly operate on different coexistence requests, identify different coexistence requests, and improve the management flexibility of coexistence requests. Subsequently, the second communication device can distinguish different coexistence requests sent by the first communication device or coexistence requests from different first communication devices based on the coexistence request ID, enabling the second communication device to facilitate the management of different coexistence requests and improve the management efficiency.

[0145] (2) Operation type information

[0146] The operation type information can be used to indicate the operation type of the coexistence request. The operation type of the coexistence request can include but is not limited to: a newly added coexistence request; a removed coexistence request; a coexistence request with modified parameters; a temporarily suspended coexistence request. The operation type of the coexistence request indicated by the operation type information can be any one of the above operation types.

[0147] Exemplarily, the operation type information can be carried in the operation type field in the coexistence request. The name of the operation type information or the operation type field is only an example. For example, the operation type information can also be called update type information, and the operation type field can also be called the update type field.

[0148] Exemplarily, the relationship between the value and meaning of the operation type information (i.e., the operation type field) can be as follows: when the operation type information is set to 00, it indicates that the coexistence request is a newly added coexistence request; when the operation type information is set to 01, it indicates removing the coexistence request; when the value of the operation type information is set to 10, it indicates modifying the relevant parameters of the coexistence request (such as the sending parameters and / or receiving parameters shown below); when the operation type information is set to 11, it indicates temporarily suspending the coexistence request until it is resumed, or temporarily suspending the coexistence request until the indicated time point. The description of the relationship between the value and meaning of the operation type information shown here is only an example, and there can be other relationships between the value and meaning of the operation type information. For example, when the value of the operation type information is set to 11, it indicates a newly added coexistence request; when the value of the operation type information is set to 00, it indicates removing the coexistence request; when the value of the operation type information is set to 10, it indicates removing the coexistence request; when the value of the operation type information is set to 01, it indicates temporarily suspending the coexistence request, etc., which will not be listed one by one here.

[0149] When the operation type information indicates that the coexistence request is a temporarily suspended coexistence request, the coexistence request may further include information indicating the recovery time of the coexistence request ( Figure 6b (not shown). For example, at the moment indicated by the recovery time information, the coexistence request can be released from temporary suspension. Exemplarily, the recovery time information can be carried in the timing synchronization function (TSF) (resume TSF) field, and this field can include at least one of the following: next starting time, next duration, next interval, etc. How to indicate the recovery time of the coexistence request will not be elaborated here. For example, when the service of the radio frequency type corresponding to the coexistence request is temporarily stopped, the operation type of the coexistence request can be a temporarily suspended coexistence request.

[0150] The second communication device can know the operation type of the coexistence request based on the operation type information. Exemplarily, the second communication device can perform different processing for different operation types.

[0151] As an example, when the operation type information indicates that the coexistence request is a newly added coexistence request, the second communication device may save the coexistence request. For example, the TXOP holder may schedule the TXOP responder based on the coexistence request, or process the transmission request (or scheduling request, etc.) of the TXOP responder. As another example, when the operation type information indicates that the coexistence request is a coexistence request to be removed, the second communication device may delete the cache regarding the coexistence request. As yet another example, when the operation type information indicates that the coexistence request is a coexistence request for which parameters need to be modified, the second communication device may update the saved coexistence request based on the parameters indicated in the coexistence request. When the second communication device is an AP, the AP may schedule non-AP STAs using the updated coexistence request. As yet another example, when the operation type information indicates that the coexistence request is temporarily suspended, the second communication device may temporarily ignore the coexistence request. For example, after the moment indicated by the above recovery time information, the coexistence request becomes valid again.

[0152] (3) RF type information

[0153] The RF type information can be used to indicate the RF type (or coexistence type) corresponding to the coexistence request. For example, the RF type may include but is not limited to: BT, WUB, ZigBee, 5G, Wi-Fi. The RF type corresponding to the coexistence request shown in the embodiments of the present application may also be referred to as the RF type of the RF module corresponding to the coexistence request, or the RF type of other RF modules. The other RF module is relative to the STA. In the embodiments of the present application, the RF type corresponding to the coexistence request may also be replaced with the RF module corresponding to the coexistence request, or the wireless module corresponding to the coexistence request.

[0154] As an example, when the value of the RF type information is a special value, the RF type information may implicitly indicate that the coexistence request is a coexistence request merged from coexistence requests corresponding to multiple RF modules. As another example, when the value of the RF type information is a normal value, the RF type information may implicitly indicate that the coexistence request is a coexistence request corresponding to one RF module. For example, when the value of the RF type information is normal value #1, it indicates that the RF type corresponding to the coexistence request is BT; another example, when the value of the RF type information is normal value #2, it indicates that the RF type corresponding to the coexistence request is WUB, etc. Specific values of the normal value or special value are not listed one by one here.

[0155] The second communication device can learn the radio frequency type of the coexistence request based on the radio frequency type information and make a reasonable decision based on this radio frequency type. For example, the second communication device can determine whether to follow (or respect or comply with) the coexistence request based on this radio frequency type. To avoid interference between different radio frequency modules inside the first communication device or control the interference within a reasonable range, the second communication device can follow the coexistence request. For example, the second communication device can end the TXOP in advance; or for another example, the second communication device can refrain from scheduling the first communication device during the period when there is coexistence interference in the first communication device (such as within the interference window shown below). When the second communication device does not follow the coexistence request, the second communication device can ignore the coexistence request. For example, the radio frequency type is 5G, and the 5G module corresponds to low-latency services. The second communication device can follow the coexistence request from the first communication device. Examples are not listed one by one here.

[0156] (4) Service priority information

[0157] The service priority information can be used to indicate the service priority of the radio frequency type corresponding to the coexistence request. Exemplarily, the service priority information can be carried in the traffic priority field.

[0158] The service priority information can include but is not limited to: access category, traffic identifier (TID), differentiated services code point (DSCP), or minimum remaining time. For example, the access category refers to the access type of the radio frequency type corresponding to the coexistence request. Different access types can correspond to different service priorities. For example, the access category can occupy 2 bits. Four different access types can be indicated by these 2 bits. For example, the traffic identifier refers to the TID of the radio frequency type corresponding to the coexistence request. Different TIDs can correspond to different service priorities. For example, the TID can occupy 4 bits. For another example, DSCP is a quality of service (QoS) classification standard, and the priority can be distinguished by the coding value. For example, DSCP can occupy 6 bits. The minimum remaining time refers to the minimum remaining time of the radio frequency type corresponding to the coexistence request. That is, the minimum remaining time can indicate the minimum remaining time of the cached data corresponding to other radio frequency modules. The cached data can be the data corresponding to the radio frequency module corresponding to the coexistence request. When the minimum remaining time is exceeded, the cached data corresponding to other radio frequency modules may be discarded or the QoS deteriorates severely. Generally speaking, the shorter the minimum remaining time, the higher the service priority of the cached data.

[0159] The second communication device can learn about the service priority situation of the radio frequency type corresponding to the coexistence request based on the service priority information, so as to reasonably schedule the first communication device, enabling the first communication device to transmit and receive data with different service priorities in combination with the coexistence interference situation.

[0160] (5) Interference Report

[0161] The interference report can indicate whether the interference is asymmetric or symmetric.

[0162] When the interference is asymmetric, it means that the radio frequency type corresponding to the coexistence request will cause interference to the STA (such as including the Wi-Fi radio frequency), but the STA will not cause interference to the radio frequency type corresponding to the coexistence request, or the interference caused is less than a certain threshold, or the interference caused by the STA to the radio frequency type corresponding to the coexistence request is less than the interference caused by the radio frequency type corresponding to the coexistence request to the STA. For example, the coexistence request can carry an interference report. The interference report can indicate the parameters of the interference of the radio frequency type corresponding to the coexistence request on the STA.

[0163] When the interference is symmetric, it means that the radio frequency type corresponding to the coexistence request will cause interference to the STA, and the STA will also cause interference to this radio frequency type. For example, the coexistence request can carry two interference reports, respectively indicating the parameters of the interference of the radio frequency type corresponding to the coexistence request on the STA and the interference parameters of the STA on this radio frequency type.

[0164] Exemplarily, the interference report can be carried in the coexistence report field. Whether the interference is asymmetric or symmetric can be carried in the symmetric interference field in the coexistence report.

[0165] Exemplarily, in addition to indicating whether the interference is asymmetric or symmetric, the interference report can further include at least one of the following: link ID (link ID) ( Figure 6b (not shown), interference level, channel affected by interference, whether the interference is periodic or aperiodic, interference start time, interference duration, interval between adjacent interference windows, number of interference windows. Exemplarily, the interference level can be carried in the interference level field in the coexistence report, the channel affected by interference can be carried in the interference channel field in the coexistence report, the interference start time can be carried in the start time field in the coexistence report, the interference duration can be carried in the duration (or called continuous duration or duration, etc.) field in the coexistence report, the interval between adjacent interference windows can be carried in the interval field in the coexistence report, and the number of interference windows can be carried in the count field in the coexistence report.

[0166] Among them, the link ID refers to the identifier of the link affected by coexistence interference. The interference level is used to indicate the intensity or magnitude of the interference to which the STA is subjected. The channel affected by interference represents the channel where the interference is located. The interference being periodic indicates that the coexistence interference is periodic. The interference being aperiodic indicates that the coexistence interference is not periodic. The interference start time can be used to indicate the start time when the coexistence interference appears. The interference duration can be used to indicate the duration for which the coexistence interference persists. When the interference is periodic, it means that the interference will occur at a certain period. For example, the start time of the interference is indicated by the interference start time, and the duration of the interference within one period is indicated by the interference duration. The interference start time and the interference duration can form an interference window. When the interference is periodic, the interference report can also include the interval between adjacent interference windows or the number of interference windows. That is to say, the interference window is periodic.

[0167] The information shown above is exemplified by being carried in the interference report. For example, the above information can be carried in the coexistence report field in the form of fields. However, in specific implementations, each of the information listed in the above (5) can also be carried in the coexistence request in other forms, which will not be listed one by one here. For example, the priority information shown in the above (4) can be carried in the coexistence report (as Figure 6b shown). The specific form in which each of the information in (1)-(7) shown in the embodiments of the present application is carried in the coexistence request is not limited in the embodiments of the present application. There may be duplicate information among the information in (1)-(7) shown in the embodiments of the present application. These duplicate information may not appear repeatedly in the coexistence request, or these duplicate information may also appear repeatedly in the coexistence request. The embodiments of the present application do not limit this.

[0168] (6) Desired behavior information

[0169] The desired behavior information is used to indicate the desired behavior of the STA in the first communication device. That is to say, for this coexistence request, it is the behavior desired by the STA in the first communication device. Or rather, it is the behavior desired by the STA in response to interference caused by other radio frequency modules to this STA.

[0170] Exemplarily, the desired behavior information can be carried in the desired behavior (expectedbehavior) field.

[0171] Exemplarily, the above desired behavior includes any one of the following:

[0172] a. Available for transmission (available Tx), or equivalently, not allowed to receive (disallowed Rx). For example, due to coexistence interference within the first communication device, the STA expects to be available for transmission. Based on this expected behavior information, the second communication device can schedule the STA within the first communication device for transmission. Exemplarily, other radio frequency modules within the first communication device need to transmit signals during the interference window, so the first communication device can expect the STA (such as the Wi-Fi radio frequency within the first communication device) to transmit signals. This can minimize the interference from other radio frequency modules to the STA and control the interference within a reasonable range.

[0173] b. Restricted reception (restricted Rx), or equivalently, available for transmission and available for receiving signals with restricted parameters (available Tx and available Rx with restricted parameters). In this case, the coexistence request may further include restricted parameters, such as reception parameters when the STA within the first communication device receives signals in a restricted manner. The reception parameters include at least one of the following: link ID, maximum number of streams, expected reception margin, expected maximum data length, expected bandwidth, coding type (or coding and modulation type, etc.), maximum LDPC codeword length, maximum MCS.

[0174] Among them, the link ID is used to indicate the identity of the link affected by coexistence interference. The maximum number of streams can be used to indicate the maximum number of streams that can be adopted when the STA receives signals. The maximum MCS can be used to indicate the maximum MCS adopted when the STA receives signals. The reception margin can be used to determine the SNR redundancy corresponding to the maximum MCS. The expected maximum data length can indicate the maximum TB-PPDU length that the STA expects to receive. The expected bandwidth can be used to indicate the maximum transmission bandwidth. The coding type can indicate the coding method, such as low-density parity-check (LDPC) coding method or other coding methods, which are not listed here. The maximum LDPC codeword length can be used to indicate the maximum allowed LDPC codeword length.

[0175] In the embodiments of the present application, by including reception parameters in the coexistence request, coexistence among multiple radio frequency modules within the first communication device can be achieved, and interference among them can be minimized as much as possible.

[0176] c. Available Rx, or equivalently, disallowed Tx. For example, based on interference existing within the first communication device, the STA expects to receive signals. The second communication device may send signals to the first communication device based on this expected behavior information. Exemplarily, other radio frequency modules within the first communication device may receive signals, and the STA may also expect to receive signals, thereby minimizing interference between them as much as possible.

[0177] d. Restricted Tx, or equivalently, available Rx and available Tx with restricted parameters. In this case, the coexistence request may further include restricted parameters, that is, the transmission parameters when the STA within the first communication device transmits signals in a restricted manner. The transmission parameters include at least one of the following: link identifier, maximum number of flows, maximum transmit power, minimum transmit power, desired reception redundancy, desired maximum data length, desired bandwidth, coding type (or maximum LDPC codeword length). For example, for a trigger-based (TB) physical layer (PHY) protocol data unit (PPDU), the second communication device may schedule the first communication device through the transmission parameters in the coexistence request.

[0178] Among them, the maximum transmit power can be used to indicate the maximum transmit power allowed for the STA when transmitting a TB-PPDU. The minimum transmit power can be used to indicate the minimum transmit power that the second communication device can use when sending signals to the first communication device. For the description of other parameters, reference can be made to the description in b, and details are not elaborated here.

[0179] In the embodiments of this application, by including transmission parameters in the coexistence request, coexistence between multiple radio frequency modules within the first communication device can be achieved, and interference between them can be minimized as much as possible.

[0180] e. Disallowed Tx and disallowed Rx, or equivalently, unavailable. For example, within the interference window, the first communication device neither sends nor receives signals. Exemplarily, the interference caused by other radio frequency modules to the STA is relatively large, and the interference cannot be controlled within a reasonable range. Therefore, the STA expects to disallow both sending and receiving signals.

[0181] As an example, the time corresponding to the desired behavior information may be the same as the time shown in (5). Exemplarily, when the coexistence request includes an interference report, the interference report includes an interference start time and an interference duration, or the interference report further includes an interval between adjacent interference windows and the number of interference windows, the second communication device may schedule the first communication device based on the interference windows indicated in the interference report, etc. That is, the time period corresponding to the above-mentioned desired behavior may be determined by the time (such as the interference start time, the interference duration, the interval or the number) indicated in (5). When the coexistence request does not include an interference report, the coexistence request may further include time information, and the time information may be used to indicate the time period corresponding to the above-mentioned desired behavior. For example, the time information may be the interference start time and the interference duration. For example, the time information may further include at least one of the interval between adjacent interference windows or the number of interference windows. The description of the time information may refer to the description of the interference start time, the interference duration, the interval or the number in (5) above, and will not be elaborated here.

[0182] As another example, the time period corresponding to the desired behavior may be different from the time shown in (5). For example, the desired behavior information may further include time information. The time period indicated by the time information may partially overlap or completely not overlap with the interference windows indicated in (5). For example, the time information may include a start time and a duration. For another example, the time information may include a start time and an end time. For another example, the time information may include a start time, a duration and a period, etc. The description of the time information shown here may also refer to the description of the interference windows above.

[0183] Exemplarily, the coexistence request may further include information indicating whether they are the same ( Figure 6b (not shown), and this information may be used to indicate whether the interference window is the same as the time period corresponding to the desired behavior, or rather, this information may implicitly indicate whether the time period corresponding to the desired behavior will appear in the coexistence request. For example, when the interference window is the same as the time period corresponding to the desired behavior, the time period corresponding to the desired behavior may not appear in the coexistence request. For another example, when the interference window is different from the time period corresponding to the desired behavior, the time period corresponding to the desired behavior may appear in the coexistence request.

[0184] Figure 6a is a schematic diagram of the format of a desired behavior field provided by an embodiment of the present application. Such as Figure 6a shown, the desired behavior field may include a control field and a time field. The control field may include a desired behavior control field and a bitmap present field.

[0185] Among them, the above time field can be used to indicate the time period corresponding to the desired behavior. For example, if the desired behavior is not to allow sending signals nor receiving signals, then this time field can be used to indicate the unavailable time period (or called the unavailable window). That is, within the time period indicated by this time field, the STA is not allowed to send signals nor receive signals. Another example is that if the desired behavior is restricted signal reception, then this time field can be used to indicate that within the time period indicated by this time field, the STA can use the reception parameters in the coexistence request to receive signals. The description of the time field can refer to the shown time information, which will not be elaborated here.

[0186] The desired behavior control field can be used to indicate any one of the above a to e. As an example, this desired behavior control field can occupy 3 bits. If the value of this field is value #1, it can indicate that the desired behavior is to allow sending signals; if the value of this field is value #2, it can indicate that the desired behavior is restricted signal reception; if the value of this field is value #3, it can indicate that the desired behavior is to allow receiving signals; if the value of this field is value #4, it can indicate that the desired behavior is restricted signal transmission; if the value of this field is value #5, it can indicate that the desired behavior is not to allow sending signals nor receiving signals. As another example, this desired behavior control field can occupy 5 bits. For example, the first bit among these 5 bits can be used to indicate that the desired behavior is to allow sending signals, that is, the first bit can correspond to a above. And so on, the second bit can correspond to b above, the third bit can correspond to c above, the fourth bit can correspond to d above, and the fifth bit can correspond to e above. They will not be listed one by one here. The relationship between the bit order and the meaning shown here is only an example and should not be construed as a limitation on the embodiments of this application.

[0187] The bit map presence field can be used to indicate whether the following information exists: the maximum number of flows, the maximum MCS, the maximum LDPC codeword length, the maximum TB-PPDU length, the expected bandwidth, the expected Rx margin, or the maximum transmit power. For example, this bit map presence field can occupy 8 bits, and these 8 bits can be used to indicate whether the corresponding information appears. The information listed here is only an example. In specific implementations, the length of the bit map presence field can be longer or shorter, and there can be more or fewer of the above information that the desired behavior field may have. The embodiments of this application do not make limitations in this regard.

[0188] Figure 6bIt is a schematic diagram of the format of a coexistence request provided by an embodiment of the present application. The coexistence request may include a coexistence control field and an expected behavior field. For example, the coexistence request may further include a coexistence report field.

[0189] Exemplarily, the coexistence control field may include a coexistence request ID field, an operation type field, and a coexistence report existence field. For the description of the coexistence request ID field, reference may be made to the description in (1) above. For the description of the operation type field, reference may be made to the description in (2) above, which will not be elaborated here. The coexistence report existence field may be used to indicate whether there is a coexistence report in the coexistence request. For the description of the coexistence report field, reference may be made to the description in (5) above. For the description of the service priority field in the coexistence report field, reference may be made to the description in (4) above. For the description of the expected behavior field, reference may be made to the description in (6) above. Figure 6b In [the above], the expected behavior indicated by the expected behavior control field may be any one of a to e above. Although Figure 6b the expected behavior field in [the above] includes a time field, and the interference report field includes a start time field, a duration field, an interval field, and a count field. However, it should not be construed as a limitation on the embodiments of the present application. Figure 6b The order or position of the various fields shown is only an example and should not be construed as a limitation on the embodiments of the present application.

[0190] (7) Listening mode enable information

[0191] The listening mode enable information may be used to instruct a first communication device (such as an STA in the first communication device) to enable the listening mode or exit the listening mode (or referred to as the listening mode). Generally speaking, for energy saving, the STA may choose to operate in the listening mode. In the listening mode, the STA may transmit and receive signals in the case of small bandwidth, single stream, or low MCS. Thereby, the power consumption of the communication device can be effectively reduced.

[0192] In the embodiments of the present application, the listening mode enable information may be carried in the coexistence request. Alternatively, the listening mode enable information may be carried in a wireless frame, and the wireless frame includes the listening mode enable information and the coexistence request. Or, the coexistence request does not include the listening mode enable information, but the wireless frame including the coexistence request includes the listening mode enable information. Regarding the positions of the various information shown in (1) to (7) in the wireless frame, the embodiments of the present application do not make any limitations.

[0193] As an example, when the listening mode enabling information is the first value, it indicates that the first communication device exits the listening mode. The mode to which the first communication device is to be switched is determined based on the power management information. Exemplarily, the first value may be 0.

[0194] In Method 1A, if the value of the listening mode enabling information is 0, the first communication device can exit the listening mode, for example, by default, it switches to the active mode (or the active state).

[0195] In Method 2A, if the value of the listening mode enabling information is 0, the first communication device can exit the listening mode and switch to a specified mode. The specified mode can be determined by the power management field in the radio frame including the coexistence request. The power management field can be used to carry the power management information. For the description of the power management field, reference can be made to Term 1 above.

[0196] For example, if the value of the power management field is 1, it means exiting the listening mode and switching to the power save (PS) mode.

[0197] Again, for example, if the value of the power management field is 0, it means exiting the listening mode and switching to the active state (or the active mode or the active state, etc.). Of course, the correspondence between the value and the meaning of the power management field shown here is only an example. For example, if the value of the power management field is 0, it can mean exiting the listening mode and switching to the power save mode; if the value of the power management field is 1, it means exiting the listening mode and switching to the active mode.

[0198] As another example, when the listening mode enabling information is the second value, it indicates that the first communication device enters the listening mode. The state of the first communication device is determined based on at least one of the power management information or more data information. Exemplarily, the second value may be 1. Generally speaking, the listening mode may include an awake state or a doze state.

[0199] In Method 1B, if the value of the listening mode enabling information is 1, it means that the first communication device enters the listening mode and remains in the awake state, and is not allowed to switch to the doze state. For example, in the listening mode, when the first communication device is in the awake state, it can transmit and receive signals with parameters such as a small bandwidth, a single stream, or a low MCS. For Method 1B, the listening mode and the power save mode can be in a parallel relationship.

[0200] In Method 2B, if the value of the listening mode enabling information is 1, the first communication device can switch between the awake state and the doze state based on the power management field or more data fields. For example, in the listening mode, the first communication device can switch back and forth between the awake state and the doze state. For Method 2B, the listening mode and the power save mode can be used in combination.

[0201] For example, if the value of the power management field is 1, the first communication device can switch back and forth between the awake state and the sleep state based on the data field. If more data fields are 1, the first communication device can receive signals through the reception parameters in the coexistence request until more data fields are set to 0, and the first communication device can switch to the sleep state.

[0202] For another example, if the value of the power management field is 0, it means that the first communication device enters the listening mode and remains in the awake state, and is not allowed to switch to the sleep state.

[0203] By reusing the meaning of the current more data fields, the listening mode and the energy-saving mode can be in a parallel relationship, and it is known that the two can be used in combination (such as the above-mentioned method 2B) or separately (such as method 1B). This is equivalent to adding a listening mode without changing the operation of the existing energy-saving mode, with little change to the protocol.

[0204] In the embodiments of the present application, by sending a coexistence request to the second communication device, on the one hand, the second communication device schedules the first communication device based on the coexistence request, and on the other hand, the coexistence request includes identification or operation type information, enabling the second communication device to flexibly manage different coexistence requests.

[0205] In the embodiments of the present application, after receiving the above coexistence request, the second communication device can also send a feedback result to the first communication device. Based on the feedback result, the first communication device can learn about the decision of the second communication device. For example, the feedback result can explicitly indicate the decision of the second communication device or implicitly indicate the decision of the second communication device. For example, the feedback result can include a cache report, more data fields, and indication information. The following takes the TXOP holder and the TXOP responder as examples for detailed description:

[0206] In the first method, the feedback result can include a cache report, or the feedback result can be a cache report. The cache report can be used to indicate the situation of the data cached by the TXOP holder. For example, the cache report can be carried in the ICF or A-control. After receiving the cache report, the TXOP responder can learn whether there is other data with a higher priority to be received.

[0207] For example, when a non-AP STA receives a buffer report sent by an AP indicating that the non-AP STA has higher-priority data to receive (the data can be data corresponding to other RF modules), the non-AP STA can suspend or remove a previous coexistence request (such as the coexistence request before receiving the buffer report). The non-AP STA can carry the coexistence request through the BA or A-Control field or in the ICR frame, and indicate to the AP to temporarily suspend or remove the corresponding coexistence request (such as the coexistence request before receiving the buffer report) through the operation type information. For example, the coexistence request can include a coexistence request ID, operation type information, and resume time information. The resume time information can also be carried in the timingsynchronization function (TSF) (resume TSF) field, etc. The resume time information can be used to indicate the resume time point, such as indicating the lower part of the TSF. Exemplarily, the above buffer report can include at least one of the following: the size of the buffered data, the minimum remaining time of the buffered data, or the service priority of the buffered data. For the descriptions of the minimum remaining time and the service priority, reference can be made to the above, and details are not elaborated here.

[0208] For another example, the TXOP responder determines the maximum bandwidth, maximum MAC, and / or maximum number of flows to be used for the next data transmission according to the buffer report sent by the TXOP holder.

[0209] In the embodiments of the present application, the TXOP holder can implicitly indicate the processing result of the coexistence request sent by the TXOP responder by sending a buffer report to the TXOP responder. When the buffer report indicates that the TXOP responder has higher-priority data to receive, it can implicitly indicate that the TXOP holder may not follow the coexistence request, and the TXOP holder will still send data to the TXOP responder.

[0210] In the second method, the feedback result can include more data fields. For example, the MPDU format of the feedback result can refer to Figure 4a or Figure 4b the description. Based on the more data fields, the TXOP responder can know whether it still has data to receive. For example, when the more data fields are set to 1, the TXOP responder can continue to receive data until the more data fields in the MPDU it receives again are set to 0. For the description of the more data fields, reference can be made to the above.

[0211] In the embodiments of the present application, when the more data fields are set to 1, it means that the TXOP holder will still send data to the TXOP responder, which can implicitly indicate that the TXOP holder may not follow the coexistence request.

[0212] In Way 3, the feedback result may include indication information, which is used to indicate whether the TXOP holder has received the coexistence request or whether the TXOP holder follows the coexistence request. For example, the indication information may be carried in the A-Contro field, BA, wireless frame, etc. Through the above indication information, the TXOP responder can learn the decision of the TXOP holder on the coexistence request.

[0213] In Way 4, the feedback result may include indication information, which can be used to indicate that the scheduling of the TXOP responder within this TXOP has ended, or that the TXOP responder stops transmitting and receiving signals within this TXOP. When the TXOP responder receives this indication information, it can learn the scheduling situation of the TXOP holder for the TXOP responder. For example, the indication information may be carried in the A-Control field, and a new value may be defined in the control identifier field of the A-Control field, and the newly defined value can be used to indicate that the role of the A-Control field is to indicate that the AP will no longer schedule the non-AP STA within this TXOP.

[0214] For Figure 5 Regarding Example 2 in step 502 shown above, since the TXOP holder may have the decision-making power, it is possible that the TXOP holder does not follow the coexistence request. When the TXOP holder does not follow the coexistence request, the following situations may occur: The duration of the TXOP partially or completely overlaps in time with the unavailable window indicated in the coexistence requests of one or more TXOP responders. For example, the TXOP holder may not follow the coexistence requests sent by one or more TXOP responders. For example, the TXOP holder may still schedule the TXOP holder within the unavailable window of a certain or some TXOP holders. In the above situations, Ways 1 to 4 described above can also be combined to enable the TXOP responder to learn the decision of the TXOP holder on the coexistence request and further improve the communication efficiency.

[0215] The coexistence request shown above can be combined with other examples or ways shown above. For the specific combination methods, they will not be elaborated here.

[0216] The following exemplarily introduces the scenarios involved in the embodiments of the present application.

[0217] Generally speaking, when either end of the two communication parties is in the coexistence mode, the two communication parties can exchange an initial control frame (ICF) and an initial control response (ICR) frame at the beginning of each TXOP. Coexistence requests or received parameters, etc. are exchanged by exchanging ICF and ICR frames. Exemplarily, the ICF and ICR frames can be newly defined control frames. Or the formats of the ICF and ICR frames reuse the formats of existing control frames. For example, the format of the ICR can refer to the format of the multi-user request to send (MU-RTS), and the format of the ICR frame can refer to the format of the clear to sent (CTS); or the format of the ICR can refer to the format of the MU-BAR, and the format of the ICR frame can refer to the format of the BA.

[0218] Currently, Wi-Fi 8 also discusses the energy saving of devices. For example, in order to save energy, a station can choose to work in the listening mode or the energy-saving mode. In the above modes, the station can work with a small bandwidth, a single stream, and a low MCS. If the AP obtains a TXOP and wants to perform data transmission with a non-AP STA, the two communication parties can exchange ICF / ICR frames. For example, the non-AP STA can carry a coexistence request in the ICR frame to inform the AP of parameters such as the maximum bandwidth, the maximum MCS, and the maximum number of streams used during data transmission.

[0219] Figure 7 It is a schematic flow diagram of a communication method provided by an embodiment of the present application. Figure 7 Among them, the AP can be the TXOP holder, and the non-AP STA1 and non-AP STA2 can be the TXOP responders. Figure 7 It is shown by taking the AP-triggered uplink multi-user transmission as an example. The AP obtains a TXOP through EDCA channel competition. The non-AP STA 1 or non-AP STA2 works in the coexistence mode or is in the listening mode (or the energy-saving mode). At the beginning of the TXOP, the ICF and ICR frames are exchanged first.

[0220] Such as Figure 7 As shown, the AP sends the ICF. After receiving the ICF, the non-AP STA1 or non-AP STA2 can reply with an ICR frame.

[0221] As an example, the ICF can carry a coexistence request inside the TXOP holder, and the ICR frame can carry a coexistence request inside the TXOP responder. For the description of the coexistence request, reference can be made to Figure 5 OrFigure 6b Descriptions such as [are not elaborated here.

[0222] As another example, a coexistence request inside the TXOP responder can be carried in the ICR frame. Since the TXOP holder can control the transmissions within the TXOP by itself, this TXOP holder may not need to indicate its internal coexistence request.

[0223] Take Figure 7 as an example. For instance, non-AP STA 1 and non-AP STA2 can respectively declare their coexistence requests in the ICR frame. For example, non-AP STA 1 requests that the TXOP ends at time T1, with a duration of A, and a corresponding traffic priority of X. Non-AP STA2 requests that the TXOP ends at time T2, with a duration of B, and a corresponding traffic priority of Y. If the desired behavior of the coexistence request sent by non-AP STA1 is unavailable, the time information can be used to indicate the unavailable time (i.e., the unavailable window). For example, non-AP STA1 can indicate through the time information that this non-AP STA1 requests that this TXOP ends at time T1. Time T1 can be determined by the start time of the unavailable time. For example, time T1 can be the start time of the unavailable time. The duration A can be indicated by the duration field in the time information. X can be indicated by the traffic priority information. Similarly, the description of non-AP STA 2 can refer to that of non-AP STA 1 and will not be elaborated here. Regarding the steps performed by the AP based on the coexistence request, reference can be made to Example 1 or Example 2 above and will not be elaborated here.

[0224] Optionally, the AP can send data, and non-AP STA1 or non-AP STA2 receives the data. After receiving the data, non-AP STA1 or non-AP STA2 can reply with a block acknowledgement (BA) frame.

[0225] Exemplarily, when the AP needs to feedback the processing result of the coexistence request, the above data can include the feedback result shown above.

[0226] The AP may not follow the coexistence request of non-AP STA 1 and / or the coexistence request of non-AP STA2. For example, the AP will still continue to schedule non-AP STA1 or non-AP STA 2. Exemplarily, the desired behavior of non-AP STA1 or non-AP STA 2 can be allowed transmission, or restricted transmission of signals. Such as Figure 7As shown, the AP can send a trigger frame, which is received by non-AP STA1 or non-AP STA2.

[0227] Exemplarily, the trigger frame includes resource scheduling for one or more users (stations) to send uplink data and other parameters (such as association identification, coding and modulation strategies, etc.). Figure 8a It is a schematic diagram of the format of a trigger frame provided by an embodiment of the present application. The trigger frame may include a common information (commoninfo) field and a user information list (userinfolist) field. The common information field may include common information that multiple users need to read. The user information list field is composed of one or more user information fields. The first user information field may be a special user information field, and the associated identification (AID) field indicates 2007. Some common information is carried after the AID field in the special user information field. Although it is a user information field, it carries common information, so the first user information field is called a special user information field. Starting from the second user information field, each user information field contains information that each user needs to read separately. In the user information field, the association identification 12 (AID12) (such as the lower 12 bits of the AID) indicates the association identification of a certain STA, usually simply referred to as the association identification field. The resource unit (RU) allocation field, combined with the primary and secondary 160 fields, indicates the specific resource unit or multi-resource unit (MRU) position allocated to this user (the user corresponding to AID12). Other descriptions of the trigger frame can refer to relevant standards or protocols, which will not be elaborated here.

[0228] Figure 8a The trigger frame shown is only an example. As the standard progresses, other types of trigger frames will appear later. The trigger frame may also have other formats, which are not limited in the embodiments of the present application.

[0229] After receiving the trigger frame, non-AP STA1 or non-AP STA2 can read the common information field and the special user information field, and parse out the user information field that matches its own AID. Then, it sends a trigger-based PPDU (TB PPDU) on the RU or MRU indicated by the resource unit allocation field in the user information field. For example, the TB PPDU can include an extremely high throughput trigger based PPDU (EHTTB PPDU) or an ultra high reliability trigger based PPDU (UHR TB PPDU). The types of TB PPDU here are only examples and should not be construed as limitations on the embodiments of this application.

[0230] Figure 8b It is a schematic diagram of the format of an EHT TB PPDU provided by an embodiment of this application. Figure 8c It is a schematic diagram of the format of a UHR TB PPDU provided by an embodiment of this application. Exemplarily, the TB PPDU can include at least one of the following: legacy short training field (L-STF), legacy long training field (L-LTF), legacy signal field (L-SIG), repeated legacy signal field (RL-SIG), Universal SIG (U-SIG), EHT-STF or UHR-STF, EHT-LTF or UHR-LTF, data, or packet extension (PE).

[0231] Table 2 exemplarily shows the functions of each field, but should not be construed as limitations on the embodiments of this application.

[0232] Table 2

[0233]

[0234]

[0235] Such as Figure 7As shown, after the AP receives one or more TB PPDUs sent by non-AP STAs, it replies with a multi-STA block acknowledgement (multi-STABA) frame.

[0236] Figure 8d It is a schematic diagram of the format of a multi-STABA frame provided by an embodiment of the present application. As Figure 8d shown, the multi-STA BA frame may include at least one of the following: frame control, duration, received address (RA), transmitting address (TA), BA control, BA information, or FCS. The BA control field may include BA type, no memory kept, memory configuration tag, management ack, or TID info. Descriptions of each field can refer to relevant standards or protocols and will not be elaborated here. Different BA types may correspond to different BA information. That is, when the value of the BA type field is different, the format of the BA information field may also be different. This will not be elaborated here.

[0237] In the embodiments of the present application, coexistence requests are carried in the ICF / ICR frames, and coexistence requests can be flexibly managed through the coexistence request ID and operation type information. At the same time, it also solves the problem of how to make full use of the current TXOP for transmission while ensuring coexistence when the TXOP end times indicated by different non-AP STAs in a multi-user scenario are inconsistent. For example, the AP can schedule these non-AP STAs using the coexistence requests based on different non-AP STAs, such as following the coexistence requests of these non-AP STAs, or not following the coexistence requests of one or more non-AP STAs, etc.

[0238] The communication device provided by the embodiments of the present application will be introduced below.

[0239] This application divides the functional modules of the communication device according to the above method embodiments. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in this application is illustrative, only a logical function division, and there may be other division methods in actual implementation. The following will be combined with Figures 9 to 11 to describe in detail the communication device of the embodiments of this application.

[0240] Figure 9 is a schematic structural diagram of a communication device provided by an embodiment of this application. As Figure 9 shown, the communication device includes a processing module 901 and a transceiver module 902. The transceiver module 902 can implement corresponding communication functions, and the processing module 901 is used to implement corresponding processing functions. For example, the transceiver module 902 can also be referred to as an interface, a communication interface, a communication module, etc.

[0241] In some embodiments of this application, the communication device can be used to perform the actions performed by the first communication device in the above method embodiments. At this time, the first communication device can be the Wi-Fi device itself or a chip or functional module that can be configured in the device, etc. The transceiver module 902 is used to perform the operations related to the transceiver of the first communication device in the above method embodiments, and the processing module 901 is used to perform the operations related to the processing of the first communication device in the above method embodiments.

[0242] Exemplarily, the processing module 901 can be used to generate a coexistence request; the transceiver module 902 can be used to send or output the coexistence request.

[0243] Exemplarily, the transceiver module 902 can also be used to receive or input a buffer report; or, receive or input indication information, etc.

[0244] Exemplarily, the transceiver module 902 can include a radio frequency module, an antenna module, etc. Exemplarily, the transceiver module 902 can include a pin module, etc.

[0245] Multiplexing Figure 9 , in some other embodiments of this application, the communication device can be used to perform the actions performed by the second communication device in the above method embodiments. At this time, the communication device can be the Wi-Fi device itself or a chip or functional module that can be configured in the device, etc. The transceiver module 902 is used to perform the operations related to the transceiver of the second communication device in the above method embodiments, and the processing module 901 is used to perform the operations related to the processing of the second communication device in the above method embodiments.

[0246] Exemplarily, the transceiver module 902 can be used to receive or input a coexistence request; the processing module 901 can be used to parse the coexistence request.

[0247] Exemplarily, the transceiver module 902 can be used to send or output a cache report; or, send or output indication information.

[0248] Exemplarily, the transceiver module 902 can include a radio frequency module, an antenna module, etc. Exemplarily, the transceiver module 902 can include a pin module, etc. The transceiver module can include multiple radio frequency modules.

[0249] Optionally, in each of the above embodiments, the communication device may further include a storage module, which can be used to store instructions and / or data. The processing module 901 can read the instructions and / or data in the storage module to enable the communication device to implement the foregoing method embodiments. Exemplarily, the storage module can be used to store coexistence requests, etc.

[0250] In each of the above embodiments, the specific descriptions of each term or step, etc. can refer to the introduction in the foregoing method embodiments, and will not be elaborated here one by one.

[0251] The specific descriptions of the transceiver module and the processing module shown in each of the above embodiments are only examples. For the specific functions or steps executed by the transceiver module and the processing module, etc., reference can be made to the foregoing method embodiments, and will not be elaborated here.

[0252] The communication device of the embodiments of the present application has been introduced above. The possible product forms of the communication device will be introduced below. Any product form that has the functions of the foregoing Figure 9 communication device falls within the protection scope of the embodiments of the present application. The following introduction is only for example and does not limit the product form of the communication device of the embodiments of the present application to this.

[0253] In a possible implementation manner, Figure 9In the communication device shown, the processing module 901 may be one or more processors, and the transceiver module 902 may be a transceiver, or the transceiver module 902 may also be a transmitting module and a receiving module. The transmitting module may be a transmitter, and the receiving module may be a receiver. The transmitting module and the receiving module are integrated into one device, such as a transceiver. In the embodiments of the present application, the processor and the transceiver may be coupled, etc. The embodiments of the present application do not limit the connection manner of the processor and the transceiver. During the process of executing the above method, the process of sending information in the above method may be the process of outputting the above information by the processor. When outputting the above information, the processor outputs the above information to the transceiver for transmission by the transceiver. After the above information is output by the processor, other processing may be required before it reaches the transceiver. Similarly, the process of receiving information in the above method may 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 to the processor. Further, after the transceiver receives the above information, the above information may need to be processed otherwise before being input to the processor.

[0254] As Figure 10 shown, the communication device 100 includes one or more processors 1020 and a transceiver 1010.

[0255] In some embodiments of the present application, the communication device may be used to execute the steps, methods, or functions performed by the above first communication device. For example, the processor 1020 may be used to execute the functions or steps implemented by the processing module 901 as Figure 9 shown, and the transceiver 1010 may be used to execute the functions or steps implemented by the transceiver module 902 as Figure 9 shown. For the specific descriptions of the processor 1020 and the transceiver 1010, reference may be made to Figure 9 or the method embodiments shown above, which will not be elaborated here.

[0256] In other embodiments of the present application, the communication device is used to execute the steps, methods, or functions performed by the above second communication device. For example, the processor 1020 may be used to execute the functions or steps implemented by the processing module 901 as Figure 9 shown, and the transceiver 1010 may be used to execute the functions or steps implemented by the transceiver module 902 as Figure 9 shown. For the specific descriptions of the processor 1020 and the transceiver 1010, reference may be made to Figure 9 or the method embodiments shown above, which will not be elaborated here.

[0257] In Figure 10In each implementation of the communication device shown, the transceiver may include a receiver and a transmitter. The receiver is used to perform the receiving function (or operation), and the transmitter is used to perform the transmitting function (or operation). And the transceiver is used to communicate with other devices / equipment through a transmission medium.

[0258] Optionally, the communication device 100 may further include one or more memories 1030 for storing program instructions and / or data. The memory 1030 is coupled to the processor 1020. The coupling in the embodiments of the present application is an indirect coupling or communication connection between communication devices, units or modules, which can be electrical, mechanical or other forms for information interaction between communication devices, units or modules. The processor 1020 may cooperate with the memory 1030. The processor 1020 can execute the program instructions stored in the memory 1030. Optionally, at least one of the above one or more memories may be included in the processor.

[0259] In the embodiments of the present application, the specific connection medium between the transceiver 1010, the processor 1020 and the memory 1030 is not limited. In the embodiments of the present application Figure 10 it is shown that the memory 1030, the processor 1020 and the transceiver 1010 are connected through a bus 1040. The bus is represented by a thick line in Figure 10 The connection manners between other components are only for illustrative purposes and are not to be construed as limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity of representation, Figure 10 only one thick line is used to represent it in

[0260] In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., which can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor, etc.

[0261] In the embodiments of the present application, the memory may include, but is not limited to, non-volatile memories such as hard disk drives (HDDs) or solid-state drives (SSDs), random access memories (RAMs), erasable programmable read-only memories (EPROMs), read-only memories (ROMs), or compact disc read-only memories (CD-ROMs), etc. The memory is any storage medium that can be used to carry or store program code in the form of instructions or data structures and can be read and / or written by a computer (such as the communication device shown in the present application), but is not limited thereto. The memory in the embodiments of the present application may also be a circuit or any other device capable of implementing a storage function, for storing program instructions and / or data.

[0262] The processor 1020 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of software programs. The memory 1030 is mainly used to store software programs and data. The transceiver 1010 may include a control circuit and an antenna. The control circuit is mainly used for the conversion between baseband signals and radio frequency signals and the processing of radio frequency signals. The antenna is mainly used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, keyboards, etc., are mainly used to receive data input by users and output data to users.

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

[0264] In another implementation, the radio frequency circuit and the antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuit and the antenna may be independent of the communication device and arranged in a remote manner.

[0265] The communication device shown in the embodiments of the present application may also have more than Figure 10More components, etc. are not limited in the embodiments of the present application. The methods executed by the above-mentioned processor and transceiver are only examples, and for the specific steps executed by the processor and transceiver, reference can be made to the methods introduced above.

[0266] In another possible implementation, Figure 9 In the shown communication device, the processing module 901 can be one or more logic circuits, and the transceiver module 902 can be an input / output interface, or also referred to as a communication interface, or an interface circuit, or an interface, etc. Or the transceiver module 902 can also be a sending module and a receiving module. The sending module can be an output interface, and the receiving module can be an input interface. The sending module and the receiving module are integrated into one module, such as an input / output interface. As Figure 11 shown, Figure 11 The shown communication device includes a logic circuit 1101 and an interface 1102. That is, the above-mentioned processing module 901 can be implemented by the logic circuit 1101, and the transceiver module 902 can be implemented by the interface 1102. Among them, the logic circuit 1101 can be a chip, a processing circuit, an integrated circuit, or a system on chip (SoC) chip, etc., and the interface 1102 can be a communication interface, an input / output interface, a pin, etc. Exemplarily, Figure 11 is given taking the above-mentioned communication device as a chip as an example. The chip includes a logic circuit 1101 and an interface 1102.

[0267] In the embodiments of the present application, the logic circuit and the interface can also be coupled to each other. For the specific connection manner between the logic circuit and the interface, the embodiments of the present application do not make a limitation. Exemplarily, the logic circuit 1101 can be used to execute the functions or steps implemented by the processing module 901 as shown in Figure 9 shown, and the interface 1102 can be used to execute the functions or steps implemented by the transceiver module 902 as shown in Figure 9 shown. For the specific description of the logic circuit 1101 and the interface 1102, reference can be made to Figure 9 or the method embodiments shown above, which will not be elaborated here.

[0268] The communication device shown in the embodiments of the present application can implement the method provided in the embodiments of the present application in the form of hardware, or can also implement the method provided in the embodiments of the present application in the form of software, etc. The embodiments of the present application do not make a limitation on this.

[0269] The embodiments of the present application also provide a communication system, which includes a first communication device and a second communication device. The first communication device and the second communication device can be used to execute the method in any of the foregoing embodiments.

[0270] In addition, the present application also provides a computer program for implementing the operations and / or processes executed by each communication device in the method provided by the present application.

[0271] The present application also provides a computer-readable storage medium storing computer code, which, when running on a computer, causes the computer to execute the operations and / or processes executed by each communication device in the method provided by the present application.

[0272] The present application also provides a computer program product including computer code or a computer program, which, when running on a computer, causes the operations and / or processes executed by each in the method provided by the present application to be executed.

[0273] In several embodiments provided by the present application, it should be understood that the disclosed system, communication device, and method can be implemented in other ways. For example, the communication device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Additionally, the displayed or discussed couplings or direct couplings or communication connections to each other can be indirect couplings or communication connections through some interfaces, communication devices, or modules, and can also be electrical, mechanical, or other forms of connection.

[0274] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they can be located in one place or distributed to 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 by the embodiments of the present application.

[0275] Furthermore, in each embodiment of the present application, the various functional modules can be integrated in one processing module, or each module can exist physically alone, or two or more modules can be integrated in one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules.

[0276] When the integrated module is implemented in the form of 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 the present 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. The computer software product is stored in a readable storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present application. The aforementioned readable storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs.

[0277] As described above, the foregoing is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered by the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A communication method, characterized in that, The method includes: A first communication device generates a coexistence request, where the coexistence request includes an identifier of the coexistence request and operation type information, and the operation type information is used to indicate the operation type of the coexistence request; The first communication device sends the coexistence request.

2. A communication method, characterized in that, The method includes: A second communication device receives a coexistence request, where the coexistence request includes an identifier of the coexistence request and operation type information, and the operation type information is used to indicate the operation type of the coexistence request; The second communication device parses the coexistence request.

3. The method according to claim 1 or 2, characterized in that, The operation type of the coexistence request includes any one of the following: A newly added coexistence request; A removed coexistence request; A coexistence request for modifying parameters; or A temporarily suspended coexistence request.

4. The method according to any one of claims 1 to 3, characterized in that The coexistence request further includes expected behavior information, and the expected behavior information is used to indicate the expected behavior corresponding to a station STA in the first communication device.

5. The method according to claim 4, characterized in that, The expected behavior includes any one of the following: Allowing signal transmission; Restricted signal reception; Allowing signal reception; Restricted signal transmission; or Not allowing signal transmission nor signal reception.

6. The method according to claim 4 or 5, characterized in that, The coexistence request further includes time information, and the time information is used to indicate the time period corresponding to the expected behavior.

7. The method according to claim 5 or 6, characterized in that, The coexistence request further includes reception parameters when the first communication device is restricted in receiving signals, or transmission parameters when the first communication device is restricted in transmitting signals.

8. The method according to any one of claims 1-7, characterized in that The coexistence request further includes radio frequency type information, and the radio frequency type information is used to indicate the radio frequency type corresponding to the coexistence request.

9. The method according to any one of claims 1-8, characterized in that, The coexistence request further includes service priority information, and the service priority information is used to indicate the service priority of the radio frequency type corresponding to the coexistence request.

10. The method according to any one of claims 1-9, characterized in that, The coexistence request further includes an interference report, and the interference report is used to indicate interference parameters of the radio frequency type corresponding to the coexistence request, and the interference parameters include at least one of the following: link identifier, interference level, channel affected by interference, whether the interference is periodic, whether the interference is symmetric, interference start time, interference duration.

11. The method according to any one of claims 1-10, characterized in that, The coexistence request further includes listening mode enabling information, and the listening mode enabling information is used to indicate that the first communication device enables or exits the listening mode.

12. The method according to any one of claims 1-10, characterized in that, The coexistence request is carried in an initial control frame ICF or an initial control response ICR frame, and the ICF or the ICR frame further includes listening mode enabling information, and the listening mode enabling information is used to indicate that the first communication device enables or exits the listening mode.

13. The method according to claim 11 or 12, characterized in that When the listening mode enabling information is a first value, it indicates that the first communication device exits the listening mode, and the mode to be switched by the first communication device is determined based on power management information; or, When the listening mode enabling information is a second value, it indicates that the first communication device enables the listening mode, and the state of the first communication device is determined based on at least one of power management information or more data information.

14. The method according to claim 1, characterized in that, The method further includes: The first communication device receives a feedback result regarding the coexistence request.

15. The method according to claim 2, wherein The method further includes: The second communication device sends a feedback result regarding the coexistence request.

16. The method according to claim 14 or 15, wherein the feedback result includes a cache report, and the cache report includes at least one of the following: the size of the cached data, the minimum remaining time of the cached data, or the service priority of the cached data; or the feedback result includes more data fields, and the more data fields are used to indicate the state of the first communication device; or the feedback result includes indication information, and the indication information is used to indicate that the scheduling of the first communication device within the current transmission opportunity TXOP has ended.

17. A communication device, characterized in that, comprising a module for performing the method according to any one of claims 1-16.

18. A communication device, characterized in that, comprising a processor, the processor being configured to perform the method according to any one of claims 1-16.

19. A communication device, characterized in that, comprising a logic circuit and an interface, the logic circuit and the interface being coupled; the interface is used to input and / or output information, and the logic circuit is configured to perform the method according to any one of claims 1-16.

20. A computer-readable storage medium, characterized in that, the computer-readable storage medium is used to store a computer program, and when the computer program is executed, the method according to any one of claims 1-16 is executed.

21. A computer program product, characterized in that, when the computer program product is executed, the method according to any one of claims 1-16 is executed.

22. A communication system, characterized in that, the communication system includes a first communication device and a second communication device, the first communication device being configured to perform the method according to any one of claims 1, 3-14, 16, and the second communication device being configured to perform the method according to any one of claims 2-13, 15, 16.

Images