Communication method and apparatus

Abstract

The present application relates to the technical field of wireless communications, and particularly relates to a communication method and apparatus. The present application is applicable to the IEEE 802.11ax standard, the 802.11be standard, the 802.11bn standard, and other standards of the IEEE 802.11 series, such as the 802.11ad standard, the 802.11ay standard and the 802.11bq standard. In the method provided in the present application, a beacon frame sent by an AP may comprise a first TWT element, which is used for indicating a TWT parameter corresponding to a TWT agreement, wherein the TWT parameter comprises a broadcast TWT ID and a group ID, or the TWT parameter comprises a directional TWT ID determined on the basis of the broadcast TWT ID and the group ID. A TWT agreement is identified by means of a corresponding group ID or directional TWT ID, such that the TWT agreement involving a non-AP STA better suits the transmission direction of the non-AP STA, thereby improving the communication efficiency and the power saving efficiency.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411999441.7, filed with the China National Intellectual Property Administration on December 31, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless technology, and more particularly to a communication method and apparatus. Background Technology

[0003] Prior to the IEEE 802.11be standard, Wi-Fi transmission was limited to a single frequency band. The 802.11be standard introduced multi-link operation (MLO). Devices supporting MLO are called multi-link devices (MLDs). For one or more links between MLDs, a target wake time agreement (TWT agreement) can be established.

[0004] Millimeter waves are electromagnetic waves with wavelengths ranging from 1 to 10 millimeters and frequencies between 30 GHz and 300 GHz. Generally, the shorter the wavelength of an electromagnetic wave, the more limited its propagation range. Since millimeter waves have wavelengths on the millimeter scale, their propagation range is very limited. Beamforming technology focuses signal energy in a specific direction by adjusting the phase and amplitude of antenna elements, forming a directional beam, thereby improving transmission efficiency.

[0005] Therefore, how to improve communication efficiency by combining millimeter waves and TWT is an urgent issue to be addressed. Summary of the Invention

[0006] This application provides a communication method and apparatus that improves communication efficiency and energy efficiency.

[0007] In a first aspect, embodiments of this application provide a communication method, the method being applied to a first device. The method includes:

[0008] The first device generates a first frame, which includes a first target wake time (TWT) element. The first TWT element is used to indicate the TWT parameters corresponding to the TWT protocol. The TWT parameters include a broadcast TWT identifier (ID) and a group ID. The broadcast TWT ID and the group ID are used to identify the TWT protocol. The first device sends the first frame.

[0009] Broadcast TWT IDs and group IDs are used to identify TWT protocols. The broadcast TWT ID is the ID of the TWT protocol, and the group ID is the ID of the group to which the TWT protocol belongs. One group ID can correspond to one or more TWT protocols, or one group ID can correspond to one or more broadcast TWT IDs.

[0010] In this embodiment, the first device creates a TWT protocol based on a group ID, which makes the allocation of TWT protocols more reasonable, thereby effectively solving the hidden node problem in millimeter-wave communication, reducing collisions of hidden nodes, improving communication efficiency and energy efficiency, and reducing the waste of channel resources. For example, by adding a group ID to the TWT parameters, the second device can select a suitable TWT protocol based on the group ID, or the first device can allocate a suitable TWT protocol to the second device based on the group ID (or create a TWT protocol). This method effectively solves the problem of channel idle detection failure, increased collisions, and waste of channel resources caused by the inability of devices to receive data from each other in directional transmission, thereby improving communication efficiency and energy efficiency.

[0011] Secondly, embodiments of this application provide a communication method, which is applied to a first device. The method includes:

[0012] The first device generates a first frame, which includes a first TWT element. The first TWT element is used to indicate the TWT parameters corresponding to the TWT protocol. The TWT parameters include a directed TWT ID determined according to the broadcast TWT identifier ID and the group ID. The directed TWT ID is used to identify the TWT protocol. The first device then transmits the first frame.

[0013] In this embodiment of the application, the directional TWT in the TWT parameter corresponds to both the broadcast TWT ID and the group ID of the TWT protocol, which enables the second device to select a suitable TWT protocol by combining the directional TWT in the TWT parameter, thereby improving communication efficiency and energy efficiency.

[0014] For further explanation regarding group IDs, please refer to the first aspect; details will not be elaborated here.

[0015] In conjunction with the first or second aspect, in one possible implementation, the TWT parameters also include millimeter-wave link information, which indicates the millimeter-wave link to which the TWT protocol applies.

[0016] In this embodiment of the application, by adding millimeter-wave link information to the TWT parameters, the second device can determine the millimeter-wave link to which the TWT parameters can be applied based on the millimeter-wave link information, thereby improving communication efficiency.

[0017] In conjunction with the first or second aspect, in one possible implementation, the millimeter-wave link information includes the link ID of the millimeter-wave link; or, the millimeter-wave link is indicated by a millimeter-wave link ID bitmap.

[0018] In conjunction with either the first or second aspect, in one possible implementation, the group ID is determined based on the direction of transmission. Alternatively, the group ID is determined based on geographical location.

[0019] In this embodiment of the application, by combining the TWT protocol with the transmission direction (or geographical location), the second device can select a suitable TWT protocol according to its own transmission direction (or geographical location), thereby improving communication efficiency and energy efficiency.

[0020] In conjunction with the first or second aspect, in one possible implementation, the first frame further includes a second TWT element, which is used to indicate the correspondence between the one ID and the group ID.

[0021] In this embodiment, the first frame includes a second TWT element, enabling the second device to combine the ID in the first TWT element with the corresponding relationship in the second TWT element to determine the broadcast TWT ID or group ID corresponding to the ID. This allows the second device to select a suitable TWT protocol after knowing its corresponding group ID, improving communication efficiency and energy saving.

[0022] In conjunction with the first or second aspect, in one possible implementation, the first TWT element also includes a negotiation type field, which occupies 3 bits or 2 bits.

[0023] In conjunction with the first or second aspect, in one possible implementation, the second TWT element also includes a negotiation type field, which occupies 3 bits or 2 bits.

[0024] This negotiation type field can be used to distinguish between the first TWT element and the second TWT element. The value of the negotiation type field in the first TWT element is different from the value of the negotiation type field in the second TWT element.

[0025] In conjunction with the first or second aspect, in one possible implementation, the method further includes: sending a second TWT element, which indicates the correspondence between the directional TWTID and the group ID. For example, this second TWT element may be carried in frames preceding the first frame.

[0026] In conjunction with the first or second aspect, in one possible implementation, the method further includes:

[0027] A second frame is sent to the second device. The second frame includes a group ID or directional TWT ID corresponding to the second device. The group ID or directional TWT ID corresponding to the second device is determined by the first device and the second device after beamforming training.

[0028] In this embodiment, after beamforming training, the first device can send a second frame to the second device. Thus, the second device can determine a suitable TWT protocol based on the group ID or directional TWT ID corresponding to itself in the second frame, improving communication efficiency and energy saving efficiency.

[0029] In conjunction with the first or second aspect, in one possible implementation, the method further includes:

[0030] Receive a TWT request from a second device, the TWT request including a group ID or directed TWT ID corresponding to the second device, and TWT parameters of the TWT protocol corresponding to the group ID or directed TWT ID corresponding to the second device; send a TWT response to the TWT request to the second device.

[0031] Optionally, the TWT request does not include the TWT parameters of the TWT agreement corresponding to the group ID or directed TWT ID corresponding to the second device.

[0032] In this embodiment of the application, after the second device learns its corresponding group ID or directed TWT ID, it can request a TWT protocol suitable for itself.

[0033] In conjunction with the first or second aspect, in one possible implementation, the method further includes:

[0034] A spontaneous TWT response is sent to the second device, which indicates the TWT protocol corresponding to the second device. This spontaneous TWT response may include TWT parameters of the TWT protocol corresponding to the group ID or directed TWT ID of the second device.

[0035] In this embodiment of the application, after the first device learns the group ID or directional TWT ID corresponding to the second device, it can configure a suitable TWT protocol for the second device.

[0036] Thirdly, embodiments of this application provide a communication method applied to a second device. The method includes:

[0037] The second device receives a first frame, which includes a first TWT element. The first TWT element is used to indicate the TWT parameters corresponding to the TWT protocol. The TWT parameters include a broadcast TWT ID and a group ID, which are used to identify the TWT protocol. The second device parses the first frame.

[0038] Regarding the beneficial effects of the third aspect, please refer to the first or second aspect; they will not be elaborated here.

[0039] Fourthly, embodiments of this application provide a communication method applied to a second device. The method includes:

[0040] The second device receives a first frame, which includes a first TWT element. The first TWT element is used to indicate the TWT parameters corresponding to the TWT protocol. The TWT parameters include a directed TWT ID determined according to the broadcast TWT identifier ID and the group ID. The directed TWT ID is used to identify the TWT protocol. The second device parses the first frame.

[0041] The beneficial effects of the fourth aspect are discussed in the first or second aspects and will not be elaborated here.

[0042] In conjunction with the third or fourth aspect, in one possible implementation, the second device parsing the first frame includes: the second device determining the correspondence between the directional TWT ID and the group ID based on the first TWT element, or the second device determining the correspondence between the directional TWT ID, the group ID, and the TWT protocol based on the first TWT element.

[0043] In conjunction with the third or fourth aspect, in one possible implementation, the TWT parameters also include millimeter-wave link information, which indicates the millimeter-wave link to which the TWT protocol applies.

[0044] In conjunction with the third or fourth aspect, in one possible implementation, the millimeter-wave link information includes the link ID of the millimeter-wave link; or, the millimeter-wave link is indicated by a millimeter-wave link ID bitmap.

[0045] In conjunction with the third or fourth aspect, in one possible implementation, the first frame also includes a second TWT element, which is used to indicate the correspondence between the orientation TWT ID and the group ID.

[0046] In conjunction with the third or fourth aspect, in one possible implementation, the group ID is determined based on the direction of transmission. Alternatively, the group ID is determined based on geographical location.

[0047] In conjunction with the third or fourth aspect, in one possible implementation, the first frame also includes a second TWT element, which is used to indicate the correspondence between the orientation TWT ID and the group ID.

[0048] In conjunction with the third or fourth aspect, in one possible implementation, the first TWT element also includes a negotiation type field, which occupies 3 bits or 2 bits.

[0049] In conjunction with the third or fourth aspect, in one possible implementation, the second TWT element also includes a negotiation type field, which occupies 3 bits or 2 bits.

[0050] This negotiation type field can be used to distinguish between the first TWT element and the second TWT element. The value of the negotiation type field in the first TWT element is different from the value of the negotiation type field in the second TWT element.

[0051] In conjunction with the third or fourth aspect, in one possible implementation, the method further includes: receiving a second TWT element, which indicates the correspondence between a directional TWT ID and a group ID. For example, this second TWT element may be carried in frames preceding the first frame.

[0052] In conjunction with the third or fourth aspect, in one possible implementation, the method further includes:

[0053] A second frame is received from the first device, the second frame including a group ID or directional TWT ID corresponding to the second device, the group ID or directional TWT ID corresponding to the second device being determined by the first device and the second device after beamforming training.

[0054] In conjunction with the third or fourth aspect, in one possible implementation, the method further includes:

[0055] Send a TWT request to the first device. The TWT request includes a group ID or directed TWT ID corresponding to the second device, and TWT parameters of the TWT protocol corresponding to the group ID or directed TWT ID corresponding to the second device. Receive a TWT response from the TWT request of the first device.

[0056] In conjunction with the third or fourth aspect, in one possible implementation, the method further includes:

[0057] Receive a spontaneous TWT response from the first device, the spontaneous TWT response being used to indicate the TWT agreement corresponding to the second device.

[0058] Fifthly, embodiments of this application provide a communication method, which is applied to a first device. The method includes:

[0059] Receive a TWT request from a second device, the TWT request being used to request a TWT agreement; send a TWT response to the TWT request to the second device, the TWT response including TWT parameters of the TWT agreement corresponding to the second device, the TWT parameters of the TWT agreement being determined according to the beam direction of the second device, the beam direction being determined by the first device and the second device after beamforming training.

[0060] In this embodiment, the first device configures the TWT protocol for the second device in conjunction with the beam direction of the second device, so that the TWT protocol can be better matched to the second device, thereby improving communication efficiency and energy efficiency.

[0061] Sixthly, embodiments of this application provide a communication method, which is applied to a second device. The method includes:

[0062] A TWT request is sent to the first device, which requests a TWT agreement; a TWT response is received from the first device in response to the TWT request, which includes TWT parameters of the TWT agreement corresponding to the second device. The TWT parameters of the TWT agreement are determined based on the beam direction of the second device, which is determined by the first device and the second device after beamforming training.

[0063] In a seventh aspect, embodiments of this application provide a first apparatus for performing the method in the first aspect, the second aspect, the fifth aspect, or any possible implementation thereof. The first apparatus includes modules having the ability to perform the method in the first aspect, the second aspect, the fifth aspect, or any possible implementation thereof.

[0064] Eighthly, embodiments of this application provide a second apparatus for performing the methods of the third, fourth, sixth, or any possible implementation thereof. The second apparatus includes modules for performing the methods of the third, fourth, sixth, or any possible implementation thereof.

[0065] Ninthly, embodiments of this application provide a first apparatus, the first apparatus including a processor and a transceiver. For example, the processor is used to generate a first frame, and the transceiver is used to transmit the first frame. The transceiver is also used to transmit a second frame. The transceiver is also used to receive TWT requests and send TWT responses. The transceiver is also used to send spontaneous TWT responses. Alternatively, the processor is used to control the transceiver to receive TWT requests and send TWT responses.

[0066] For descriptions of the first frame, the second frame, or spontaneous TWT responses, please refer to the first to fourth aspects or specific embodiments, which will not be repeated here. For descriptions of TWT requests or TWT responses, please refer to the first to sixth aspects or specific embodiments, which will not be repeated here.

[0067] In a tenth aspect, embodiments of this application provide a second apparatus, the second apparatus including a processor and a transceiver. For example, the transceiver is used to receive a first frame, and the processor is used to parse the first frame. The transceiver is also used to receive a second frame. The transceiver is also used to send a TWT request and receive a TWT response. The transceiver is also used to receive spontaneous TWT responses. Furthermore, the processor is used to control the transceiver to send TWT requests and receive TWT responses.

[0068] For descriptions of the first frame, the second frame, or spontaneous TWT responses, please refer to the first to fourth aspects or specific embodiments, which will not be repeated here. For descriptions of TWT requests or TWT responses, please refer to the first to sixth aspects or specific embodiments, which will not be repeated here.

[0069] Eleventhly, embodiments of this application provide a chip including logic circuitry and an interface. The logic circuitry generates a first frame, and the interface outputs the first frame. The interface is also used to output a second frame. The interface is further used to input a TWT request and output a TWT response. The interface is also used to output a spontaneous TWT response.

[0070] For example, an interface can be used to input TWT requests and output TWT responses. For instance, after an interface inputs a TWT request, the logic circuit parses the TWT request and generates a TWT response, which the interface then outputs.

[0071] In a twelfth aspect, embodiments of this application provide a chip including logic circuitry and an interface. The interface is used to input a first frame, and the logic circuitry is used to parse the first frame. The interface is also used to input a second frame. The interface is also used to output a TWT request and input a TWT response. The interface is also used to input spontaneous TWT responses.

[0072] For example, an interface can be used to output TWT requests and input TWT responses. For instance, a logic circuit generates a TWT request, the interface outputs the TWT request and inputs a TWT response, and the logic circuit parses the TWT response.

[0073] In a thirteenth aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer (such as the device shown above), causes the methods in any of the first to sixth aspects or any possible implementations described above to be executed.

[0074] In a fourteenth aspect, embodiments of this application provide a computer program product comprising a computer program that, when run on a computer (such as the device shown above), causes the methods in any of the first to sixth aspects or any possible implementation thereof to be executed.

[0075] In a fifteenth aspect, embodiments of this application provide a computer program that, when run on a computer, executes the methods in any of the first to sixth aspects or any possible implementations described above.

[0076] In a sixteenth aspect, embodiments of this application provide a communication system comprising a first device and a second device. The first device is configured to perform the methods described in the first, second, or fifth aspects or any possible implementation thereof, and the second device is configured to perform the methods described in the third, fourth, or sixth aspects or any possible implementation thereof. Attached Figure Description

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

[0078] Figure 2a is a schematic diagram of the negotiation stage in the process of establishing an individual TWT agreement;

[0079] Figure 2b is a schematic diagram of the negotiation phase in the establishment process of broadcast TWT;

[0080] Figure 3a is a schematic diagram of omnidirectional transmission;

[0081] Figures 3b and 3c are schematic diagrams of directional transmission;

[0082] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0083] Figure 5 is a schematic diagram of the relationship between TWT SPs provided in the embodiments of this application;

[0084] Figure 6 is a schematic diagram of the transmission direction division provided in an embodiment of this application;

[0085] Figure 7a is a schematic diagram of a format of the first TWT element provided in an embodiment of this application;

[0086] Figure 7b is a schematic diagram of another format of the first TWT element provided in the embodiments of this application;

[0087] Figure 7c is a schematic diagram of another format of the first TWT element provided in the embodiments of this application;

[0088] Figure 8a is a schematic diagram of the format of the action frame provided in an embodiment of this application;

[0089] Figure 8b is a schematic diagram of the trigger frame format provided in an embodiment of this application;

[0090] Figure 9 is a schematic diagram of a scenario of the communication method provided in an embodiment of this application;

[0091] Figure 10 is another flowchart illustrating the communication method provided in an embodiment of this application;

[0092] Figure 11a is a schematic diagram of a format of the second TWT element provided in an embodiment of this application;

[0093] Figure 11b is a schematic diagram of another format of the second TWT element provided in an embodiment of this application;

[0094] Figure 11c is a schematic diagram of another format of the second TWT element provided in the embodiments of this application;

[0095] Figure 11d is a schematic diagram of another format of the second TWT element provided in the embodiments of this application;

[0096] Figure 12 is a schematic diagram of the format of the TWT element provided in the embodiment of this application;

[0097] Figure 13 is a schematic flowchart of another communication method provided in an embodiment of this application;

[0098] Figure 14 is a schematic diagram of the format of the TWT parameter information field in the TWT element of the TWT request provided in the embodiment of this application;

[0099] Figure 15 is a schematic diagram of the device provided in an embodiment of this application;

[0100] Figure 16 is a schematic diagram of the device provided in an embodiment of this application;

[0101] Figure 17 is a schematic diagram of the chip provided in an embodiment of this application. Detailed Implementation

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

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

[0104] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0105] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. "Or" indicates that there can be two relationships, such as only A exists and only B exists; when A and B are not mutually exclusive, it can also mean that there are three relationships, such as only A exists, only B exists, and both A and B exist simultaneously. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".

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

[0107] In this application, the dashed lines in the accompanying drawings indicate that they are optional.

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

[0109] The technical solutions provided in this application can be applied to wireless local area network (WLAN) systems. For example, the methods provided in this application can be applied to the IEEE 802.11 series standards, such as 802.11a / b / g, 802.11bf, 802.11az, 802.11bk, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn, or next-generation standards, and even more specifically, 802.11ad, 802.11ay, 802.11bq, or next-generation standards, etc., which will not be listed here. The technical solutions provided in this application can also be applied to wireless personal area networks (WPANs) based on ultra-wideband (UWB) technology. The technical solutions provided in the embodiments of this application can be applied to the IEEE 802.15 series standards, such as the 802.15.4a, 802.15.4z, or 802.15.4ab standards, or a future generation of UWB WPAN standards. The technical solutions provided in the embodiments of this application can also be applied to WiFi AI wireless local area network systems, sensing systems, or other similar systems, which will not be listed here. The technical solutions provided in the embodiments of this application can also be applied to the following communication systems, such as Internet of Things (IoT) systems, vehicle-to-everything (V2X) systems, narrowband Internet of Things (NB-IoT) systems, long term evolution (LTE) systems, 5th generation (5G) communication systems, and other new communication systems that will emerge in future communication developments.

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

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

[0112] In one possible implementation, the method provided in this application embodiment can be implemented by a communication device in a communication system. That is, the communication device is used to implement the method provided in this application embodiment. The communication device can support frequency bands from 2.4 GHz to 7.25 GHz (sub-7 GHz), such as supporting at least one of 2.4 GHz, 5 GHz, or 6 GHz. The communication device can also support frequency bands between 42 GHz and 71 GHz. Optionally, the operation of the physical (PHY) layer and medium access control (MAC) layer in the frequency band between 42 GHz and 71 GHz can utilize or reuse the PHY and MAC operations in the sub-7 GHz frequency band.

[0113] The communication device includes a first device or a second device. This application describes the method provided by the embodiments of this application using a first device and a second device. However, during the transmission of a frame, the first device and the second device can also forward the frame through other devices, such as a forwarding device to forward frames between the first device and the second device. This application does not limit the use of devices other than the first device and the second device.

[0114] As an example, the first device is an access point (AP), and the second device is a non-access point station (non-AP STA). As another example, the first device is a management node (G node), and the second device is a terminal (T) node. G nodes and T nodes are the nodes involved in the StarScan standard. For example, a T node can be a barcode scanner, radio frequency identification (RFID), a sensor, a global positioning system (GPS), LiDAR, a battery cell, a mobile phone with positioning capabilities, a wearable device, a personal digital assistant (PDA), a positioning card, or a positioning terminal, etc. As yet another example, the first device is a network device, and the second device is a terminal device. The specific types of the first and second devices are not listed here.

[0115] An access point is a device with wireless communication capabilities, supporting communication or sensing using WLAN protocols. It has the function of communicating or sensing with other devices in the WLAN network (such as non-AP STAs or other access points), and can also have the function of communicating or sensing with other devices. Alternatively, an access point acts as a bridge connecting wired and wireless networks, its main function being to connect various wireless network clients together and then connect the wireless network to the Ethernet. In a WLAN system, an access point can be called an Access Point Station (AP STA). This wireless communication device can be a complete device, or it can be a chip, processing system, or functional module installed in a complete device. The device with these chips, processing systems, or functional modules can implement the methods and functions of the embodiments of this application under the control of the chips, processing systems, or functional modules. The AP in the embodiments of this application is a device that provides services to non-AP STAs and can support 802.11 series protocols or subsequent protocols. For example, an access point can be an access point for terminals (such as mobile phones) to enter a wired (or wireless) network, mainly deployed in homes, buildings, and parks, with a typical coverage radius of tens to hundreds of meters; of course, it can also be deployed outdoors. For example, an AP can be a communication server, router, switch, bridge, mobile phone, or computer; APs can include various forms of macro base stations, micro base stations, and repeater stations. Of course, an AP can also be an AP belonging to a multi-link device (MLD), or a co-located AP, etc.

[0116] A non-AP STA is a device with wireless communication capabilities that supports communication or sensing using WLAN protocols and has the ability to communicate or sense with other non-AP STAs or access points in a WLAN network. For example, a non-AP STA is any user communication device that allows a user to communicate or sense with an AP and thus 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. Devices with these chips, processing systems, or functional modules can implement the methods and functions of the embodiments of this application under the control of the chips, processing systems, or functional modules. For example, a non-AP STA can be a wireless communication chip, a wireless sensor, or a wireless communication terminal, and can also be referred to as a user. Another example is a non-AP STA that supports Wi-Fi communication, such as a mobile phone, a tablet computer, a set-top box, a smart TV, a smart wearable device, an in-vehicle communication device, or a computer. Of course, a non-AP STA can also be a non-AP STA belonging to an MLD or a co-located STA.

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

[0118] Figure 1 is a schematic diagram of an architecture of a communication system provided in an embodiment of this application. The communication system includes at least one AP / AP MLD and at least one non-AP STA / non-AP STA MLD. Figure 1 exemplarily illustrates one AP and two non-AP STAs, such as non-AP STA1 and non-AP STA2. For example, both the AP and the non-AP STA are Wi-Fi devices that simultaneously support the sub-7GHz band and the millimeter-wave (mmWave) band. Both the AP and the non-AP STA can support multi-link operation (MLO) and the TWT protocol.

[0119] For example, the transmission between the AP and the non-AP STA is a single-user (SU) transmission, meaning that the AP communicates with only one non-AP STA at a time.

[0120] Figure 1 uses a non-AP STA as a mobile phone and an AP as a router as an example, and does not imply any limitation on the AP and non-AP STA types in the embodiments of this application.

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

[0122] 1. Beamforming and Beamforming Training (BFT)

[0123] Millimeter waves are electromagnetic waves with wavelengths ranging from 1 to 10 millimeters and frequencies between 30 GHz and 300 GHz. Generally, the shorter the wavelength of an electromagnetic wave, the more limited its propagation range. Because millimeter waves have wavelengths on the millimeter scale, their propagation range is severely limited. Beamforming technology focuses signal energy in a specific direction by adjusting the phase and amplitude of an antenna, forming a directional beam, thereby improving transmission efficiency. Through beamforming, electromagnetic wave signals can be transmitted more accurately to the target receiver, avoiding signal scattering and propagation loss. Beamforming training is a process used to determine the optimal beam direction and parameter settings; for example, the transmitter and receiver search for possible beam directions to determine the optimal one.

[0124] 2. Multi-link operation (MLO)

[0125] Multi-link operation (MLO) establishes multiple links between access points (APs) and non-AP STAs, simultaneously connecting to the 2.4GHz, 5GHz, and 6GHz frequency bands. It allows for simultaneous data transmission and reception across these bands, achieving faster speeds, increased throughput, reduced latency, and improved reliability by aggregating bandwidth across multiple concurrently used frequency bands. Through multi-link operation, data streams can be distributed across different links, achieving load balancing and preventing overload or congestion on any single link, thereby improving network performance and stability. Devices supporting MLO are called multi-link devices (MLDs).

[0126] 3. TWT Agreement

[0127] The TWT (Time-to-Wake) protocol is an important resource scheduling function. Its main function is to reduce the number of devices competing for the channel at the same time and help devices reduce energy consumption. Through the TWT protocol, non-AP STAs can reach a consensus on wake-up scheduling with the AP. Non-AP STAs are only in the wake-up state when needed, and can remain in the doze state the rest of the time. A TWT agreement specifies one or more TWT service periods (SPs). Non-AP STAs wake up before the start of a TWT SP to receive or send data. A TWT agreement allows a non-AP STA to participate in multiple periodically wake-up TWT SPs. Optionally, TWT can be implemented to create TWT agreements across links to support MLO (Mean Time Logging).

[0128] TWT mechanisms can be divided into two types: individual TWT and broadcast TWT. In this application embodiment, for individual TWT, the TWT protocol can be called the individual TWT protocol; for broadcast TWT, the TWT protocol can be called the broadcast TWT operation. Alternatively, the TWT protocol can also be called the TWT protocol, TWT session, TWT planning, or TWT schedule, etc. For ease of description, this application embodiment uses the TWT protocol as an example, but the name of the TWT protocol is not intended to limit the embodiments of this application.

[0129] The following will explain each point separately.

[0130] (1) Individual TWT

[0131] The non-AP STA and AP establish a one-to-one TWT agreement. The establishment process of a personal TWT includes a negotiation phase, in which the AP and non-AP STA determine common TWT parameters for the personal TWT agreement. These TWT parameters include, but are not limited to, at least one of the following: TWT, TWT wake interval, or TWT channel.

[0132] Figure 2a is a schematic diagram of the negotiation phase in the establishment of a personal TWT agreement. As shown in Figure 2a, the non-AP STA, acting as the TWT requesting STA, sends a TWT request to the AP to request the establishment of a TWT agreement. After receiving the TWT request, the AP, acting as the TWT responding STA, replies to the non-AP STA with a TWT response, indicating whether the TWT request is accepted or rejected.

[0133] A TWT request includes one or more TWT elements, each containing TWT parameters. Optionally, the TWT element includes a link ID bitmap, which indicates the link corresponding to the TWT parameters in the TWT element. If multiple links use the same TWT parameters, the TWT request may include only one TWT element, which includes an aligned TWT link bitmap, indicating other links sharing the TWT element. The link ID bitmap and the aligned TWT link bitmap can be carried in the individual TWT parameter set field within the TWT element. By using the link ID bitmap and the aligned TWT link bitmap, TWT agreements for one or more different links can be negotiated through a single link, thereby improving implementation efficiency.

[0134] (2) Broadcast TWT

[0135] The AP configures a shared TWT protocol for multiple non-AP STAs. For broadcast TWTs, the AP broadcasts one or more TWT parameters corresponding to the TWT protocol via a beacon frame. This beacon frame includes one or more TWT elements, each containing a TWT parameter corresponding to a TWT protocol. Thus, non-AP STAs can request to join the TWT protocol.

[0136] Optionally, one or more of the aforementioned TWT protocols can be applied to the current link. The current link is the link that transmits beacon frames. Optionally, the TWT element also includes an aligned field, which indicates whether a TWT protocol overlapping with the current link is configured on other links. The overlapping TWT protocol may have some or all of its parameters being the same. For example, the beacon frame is transmitted on a 2.4 GHz link, and the value of the aligned field in the TWT element on that 2.4 GHz link is 1. Then, after learning the value of the aligned field, the non-AP STA can wake up the 5 GHz link to receive the beacon frame, confirm the TWT protocol on the 5 GHz link, and decide whether to join the TWT protocol on the 5 GHz link.

[0137] However, the above scheme means that non-AP STAs can only confirm whether there are other links with overlapping or the same broadcast TWT protocol through beacon frames, but cannot confirm which specific link it is. Non-AP STAs can only confirm the TWT protocol on the current link through the beacon frames received on the current link.

[0138] Figure 2b is a schematic diagram of the negotiation phase in the establishment process of a broadcast TWT. As shown in Method 1 of Figure 2b, the non-AP STA, acting as the TWT scheduled STA, sends a TWT request to the AP. This TWT request includes a TWT element, which includes TWT parameters for the broadcast TWT protocol. These TWT parameters include a broadcast TWT ID, which identifies a specific broadcast TWT protocol that the non-AP STA wants to join. The AP, acting as the TWT scheduling STA, replies to the non-AP STA with a TWT response, indicating whether or not the TWT request is accepted.

[0139] As shown in Method 2 of Figure 2b, if the AP does not receive a TWT request from the non-AP STA, it can directly send a spontaneous TWT response to the non-AP STA. This spontaneous TWT response includes a TWT element. This spontaneous TWT response can be used to directly add the non-AP STA to the TWT protocol corresponding to the TWT element.

[0140] For personal TWTs and broadcast TWTs, a TWT protocol can have two different operating modes: a. trigger-enabled, where the AP schedules the transmission of non-AP STAs within the TWT SP by sending a trigger frame; b. non-trigger-enabled, where no trigger frame is needed, allowing each non-AP STA within the TWT SP to decide when to transmit.

[0141] The TWT mechanism can coordinate the wake-up or sleep of non-AP STAs at different times, thereby controlling the number of non-AP STAs competing for the channel at the same time. Within the TWT SP, APs or non-AP STAs still access the channel for data transmission through contention.

[0142] Figure 3a is a schematic diagram of omnidirectional transmission. As shown in Figure 3a, for the sub-7GHz frequency band, an AP or non-AP STA can use an omnidirectional antenna to enable electromagnetic waves to radiate energy uniformly in space.

[0143] Figures 3b and 3c illustrate directional transmission. As shown in Figure 3b, for millimeter-wave bands, directional beams are typically used to transmit or receive signals in a directional manner to achieve high-speed data transmission and reliable communication. As shown in Figure 3c, due to the characteristics of millimeter-wave communication, a device A operating in the millimeter-wave band may not be able to receive directional information (e.g., RTS / CTS frames) sent by an access point (AP) to another millimeter-wave device B, resulting in device A's channel idle detection failing. In other words, device A believes the channel is idle and transmits data to the AP, but because the AP's transmission direction is towards device B, the AP cannot receive the data from device A. Device A may then attempt multiple retransmissions, leading to increased collisions and wasted channel resources. Devices A and B are in a wake-up state.

[0144] In other words, due to the characteristics of millimeter-wave communication, there is a problem of hidden nodes during the communication process, which leads to collisions of hidden nodes and thus wastes channel resources.

[0145] In view of this, embodiments of this application provide a communication method and apparatus that can effectively solve the hidden node problem in millimeter-wave communication, reduce collisions of hidden nodes, improve communication efficiency and energy efficiency, and reduce the waste of channel resources.

[0146] Figure 4 is a schematic flowchart of a communication method provided in an embodiment of this application. The descriptions of the first and second devices involved in this method are as above and will not be repeated here. For ease of description, the following description will use the example of the first device being an AP and the second device being a non-AP STA. As shown in Figure 4, the method includes:

[0147] 401. The first device generates a first frame, which includes a first TWT element. The first TWT element is used to indicate the TWT parameters corresponding to the TWT protocol. The TWT parameters include a broadcast TWT ID and a group ID. The broadcast TWT ID and the group ID are used to identify the TWT protocol.

[0148] One broadcast TWT ID corresponds to one TWT protocol. This broadcast TWT ID is used to uniquely identify a broadcast TWT protocol. One group ID corresponds to one or more TWT protocols. Alternatively, one group ID corresponds to one or more broadcast TWT IDs. Different broadcast TWT IDs can correspond to the same group ID. The group ID is the group ID of the TWT protocol.

[0149] The TWT parameters also include at least one of the following: target wake time (TWT), nominal minimum TWT wake duration, TWT wake interval mantissa, and TWT channel. TWT, nominal minimum TWT wake duration, and TWT wake interval mantissa can be used to determine the TWT SP. For example, if TWT is the start time of the TWT SP, the nominal minimum TWT wake duration and TWT wake interval mantissa can be used to determine the duration of the TWT SP. The specific calculation method for the relationship between TWT, nominal minimum TWT wake duration, TWT wake interval mantissa, and TWT SP is not limited in the embodiments of this application. During the TWT SP, the non-AP STA is in a wake-up state and can receive or send data. Since some parameters in the TWT parameters can be used to determine the TWT SP and the relationship between the TWT parameters and the TWT protocol, the TWT SP can be used to distinguish different TWT protocols.

[0150] For example, TWT protocols with the same group ID may have partially or completely overlapping TWT SPs. This allows for efficient time utilization and improved time efficiency. Consequently, after the second device successfully competes for the channel, it can occupy the channel for as long as possible, ensuring transmission duration and improving communication efficiency and time utilization.

[0151] As an example, TWT protocols with different group IDs correspond to completely non-overlapping TWT SPs. This effectively solves the hidden node problem, avoids collisions, and significantly reduces channel resources.

[0152] As an example, TWT protocols with different group IDs have overlapping TWT SPs. This can effectively improve the flexibility of AP scheduling TWT protocols.

[0153] Alternatively, in order to minimize the hidden node problem in millimeter-wave communication and help millimeter-wave devices save energy, non-AP STAs cannot compete for channel space outside of the TWT protocol (i.e., outside of the TWT SP).

[0154] Figure 5 is a schematic diagram illustrating the relationship between TWT SPs provided in an embodiment of this application. Figure 5 exemplarily shows four types of TWT SPs, TWT SP1 to TWT SP4. As shown in Figure 5, TWT SP1 and TWT SP2 completely overlap. TWT SP1 and TWT SP3 partially overlap. TWT SP1 and TWT SP4 do not overlap at all.

[0155] As an example, the group ID is determined based on the transmission direction. In other words, the group ID indicates the transmission direction corresponding to the TWT protocol. Multiple TWT protocols with the same group ID correspond to the same transmission direction, but their broadcast TWT IDs are different.

[0156] For example, multiple non-AP STAs participating in the TWT protocol in the same transmission direction may have the same group ID. These non-AP STAs, being spatially close and transmitting in the same direction, can trigger channel idle detection because they can hear each other's data transmissions, even if they are transmitting directionally. Conversely, multiple non-AP STAs in different transmission directions cannot receive each other's data and therefore cannot trigger channel idle detection. To avoid frequent channel contention and data retransmissions, the group IDs of the TWT protocols participated in by non-AP STAs in different transmission directions are different. If non-AP STAs in different transmission directions use the same TWT SP, they will not receive each other's data transmissions, leading to channel idle detection failure. This can cause non-AP STAs participating in channel contention to mistakenly believe they have successfully acquired the channel, increasing collisions and wasting channel resources.

[0157] As another example, the group ID is determined based on geographic location. In other words, the group ID indicates the geographic location corresponding to the TWT agreement. Multiple TWT agreements with the same group ID correspond to the same geographic location, but their broadcast TWT IDs are different. For example, TWT agreements involving non-AP STAs within the same geographic area have the same group ID. Conversely, TWT agreements involving non-AP STAs within different geographic areas have different group IDs.

[0158] In this embodiment, the group ID can also be called area ID, direction ID, or sector ID, etc. The TWT protocol can also be called a directional TWT protocol, or a directional broadcast TWT, etc., and will not be listed here. The transmission direction can be considered as a two-dimensional space or a three-dimensional space; this embodiment does not limit this. It is understood that this embodiment illustrates the example of the group ID being included in the TWT parameters. As another possible implementation, it can also be classified as follows: the first frame includes a first TWT element, which includes information indicating the TWT parameters corresponding to the TWT protocol, and information indicating the group ID. The TWT parameters and the group ID are included side-by-side in the first TWT element.

[0159] Figure 6 is a schematic diagram of transmission direction division provided in an embodiment of this application. The group identifiers shown in Figure 6 are merely examples and are not intended to limit this application. As shown in Figure 6, the AP can divide space (such as planar space) into 8 parts, with each transmission direction corresponding to a 45-degree two-dimensional space. The AP creates one or more TWT protocols for each transmission direction. The TWT protocols corresponding to different transmission directions are different. For example, the TWT SPs corresponding to the TWT protocols created by the AP in different transmission directions do not overlap completely or partially overlap. For example, transmission direction 1 corresponds to group ID1, transmission direction 2 corresponds to group ID2, and so on. Figure 6 exemplarily shows the TWT protocols created by the AP in transmission direction 1, transmission direction 3, and transmission direction 6.

[0160] For example, if non-AP STA1's spatial location falls within the area covered by transmission direction 1, then the TWT protocol that non-AP STA1 can request to create or participate in is the TWT protocol corresponding to transmission direction 1. As shown in Figure 6, non-AP STAs in the same transmission direction are spatially close, so they can detect data sent or received by other non-AP STAs, thus triggering channel idle detection. Consequently, the TWT SPs corresponding to the TWT protocols participated in by non-AP STAs in the same transmission direction can partially or completely overlap. Conversely, non-AP STAs in different transmission directions are geographically distant and cannot receive data from each other, potentially failing to trigger channel idle detection. To avoid frequent channel contention and data retransmission by these non-AP STAs, the TWT SPs corresponding to the TWT protocols participated in by non-AP STAs in different transmission directions can be different. This ensures that non-AP STAs competing for the channel are all in the same transmission direction during the same time period.

[0161] Optionally, given the relationship between group IDs and TWT protocols involved in the embodiments of this application, and the relationship between TWT protocols and non-AP STAs, the AP can group its associated millimeter-wave devices. For example, devices located close to each other can be grouped together, or devices with the same transmission direction as the AP can be grouped together, or devices whose beam coverage directions overlap after beamforming training (such as the optimal beam or the beam matched with the second device) can be grouped together. Devices in the same group can participate in TWT protocols with the same group ID. Devices in different groups participate in TWT protocols with different group IDs and communicate according to different TWT protocols. The aforementioned devices can be second devices.

[0162] Figure 7a is a schematic diagram of a format of the first TWT element provided in an embodiment of this application. As shown in Figure 7a, the first TWT element includes at least one of the following: element ID, length, control, or TWT parameter information. The TWT parameter information field includes at least one of the following: request type, TWT, minimum TWT wake-up time, minimum TWT wake-up interval (decimal value), broadcast TWT information, restricted TWT traffic information, or group ID. The broadcast TWT ID is carried in the broadcast TWT information field.

[0163] The control field may include a negotiation type field. If this negotiation type field occupies 2 bits, the relationship between the values ​​and meanings of these 2 bits is as follows: 0 indicates that the TWT parameters carried by the first TWT element are for a personal TWT protocol; 1 indicates that the TWT parameters carried by the first TWT element are for the target beacon transmission time (TBTT) interval; 2 indicates that the TWT parameters carried by the first TWT element are for a broadcast TWT protocol, and optionally, the first TWT element may also include one or more broadcast TWT parameter setting fields; 3 indicates that the TWT parameters carried by the first TWT element are for a broadcast TWT protocol, and optionally, the first TWT element may include a broadcast TWT parameter setting field.

[0164] For example, this negotiation type field occupies 3 bits. For an explanation of these 3 bits, please refer to the relevant description in Figure 10, which will not be elaborated here.

[0165] The TWT parameter information field can also be called the broadcast TWT parameter set field. Figure 7a also illustrates the length of each field. The order or length of the fields is not limited in this embodiment.

[0166] Optionally, if the TWT protocol corresponding to the group ID is updated, such as by adding or deleting a TWT protocol, the first device can also send the updated first TWT element.

[0167] In one possible implementation, the TWT parameters also include millimeter-wave link information, which indicates the millimeter-wave link to which the TWT protocol applies. Thus, even if the first device does not transmit the first frame on the millimeter-wave band, the second device can determine the TWT protocol on the millimeter-wave band through the first frame. Optionally, the first TWT element is used to indicate the TWT parameters corresponding to the TWT protocol applied on the millimeter-wave link.

[0168] As an example, millimeter-wave link information includes the link ID of the millimeter-wave link. As another example, millimeter-wave links are indicated by a millimeter-wave link ID bitmap. For instance, this millimeter-wave link ID bitmap includes multiple bits, each corresponding to a millimeter-wave link, and the value of the bit indicates whether the TWT protocol corresponding to the first TWT element applies to the millimeter-wave link corresponding to that bit.

[0169] As described above, the alignment field allows non-AP STAs to confirm whether other links overlap or share the same broadcast TWT protocol via beacon frames, but it cannot pinpoint the specific link. However, this application not only adds millimeter-wave link information related to the millimeter-wave band to the first TWT element, but also enables this millimeter-wave link information to indicate which millimeter-wave links the second device uses for the TWT protocol corresponding to the first TWT element.

[0170] Figure 7b is a schematic diagram of another format of the first TWT element provided in an embodiment of this application. As shown in Figure 7b, the TWT parameter information field in the first TWT element also includes a millimeter-wave link ID bitmap. For further explanation of Figure 7b, please refer to Figure 7a, which will not be detailed here.

[0171] In one possible implementation, the first frame may include a millimeter-wave link ID bitmap, but not a group ID.

[0172] Figure 7c is a schematic diagram of another format of the first TWT element provided in an embodiment of this application. As shown in Figure 7c, the TWT parameter information field in this first TWT element includes a millimeter-wave link ID bitmap, but does not include the group ID. For further explanation of Figure 7c, please refer to Figure 7a, which will not be detailed here.

[0173] The first frame includes one or more first TWT elements. Optionally, the group IDs corresponding to the TWT protocols indicated by multiple first TWT elements are the same. Optionally, at least two of the multiple first TWT elements indicate different group IDs corresponding to the TWT protocols.

[0174] In this embodiment of the application, the first frame may be a beacon frame, or other types of management frames or control frames, etc.

[0175] 402. The first device sends the first frame. Correspondingly, the second device receives the first frame.

[0176] Optionally, the first device transmits the first frame in the sub-7GHz band.

[0177] 403. The second device analyzes the first frame.

[0178] For example, the second device determines the correspondence between the broadcast TWT ID and the group ID based on the first TWT element in the first frame. Alternatively, the second device determines the correspondence between the broadcast TWT ID, the group ID, and the TWT protocol based on the first TWT element. Another example is that the second device determines the TWT parameters of the TWT protocol indicated by the first TWT element based on the first TWT element in the first frame. For an explanation of the TWT parameters, refer to the description in step 401; it will not be detailed here.

[0179] In one possible implementation, the method shown in Figure 4 further includes:

[0180] 404. The first device sends a second frame to the second device. The second frame includes a group ID corresponding to the second device, which is determined by the first and second devices after beamforming training. Correspondingly, the second device receives the second frame.

[0181] As an example, the first device transmits a second frame over a millimeter-wave link. Correspondingly, the second device receives the second frame over the same millimeter-wave link.

[0182] As another example, the first device transmits the second frame on a sub-7GHz link. Correspondingly, the second device receives the second frame on the sub-7GHz link.

[0183] The embodiments of this application do not limit the order of steps 404 and 402, and similarly, do not limit the order of steps 404 and 401.

[0184] The first and second devices perform beamforming training. The first device determines the transmission direction or geographical location of the second device based on the beam matched with it, and determines the group ID corresponding to the second device. Optionally, the first device can group multiple second devices according to the beam matched with each second device, and determine the group ID corresponding to the second device according to the correspondence between the grouping of the second devices and the grouping in the TWT agreement. For an explanation of the group ID, please refer to step 401 above, which will not be detailed here.

[0185] As an example, the second frame includes a group ID corresponding to a second device. For instance, after the first device and a second device perform beamforming training, the first device sends a second frame to the second device via unicast, and this second frame includes the group ID corresponding to the second device.

[0186] As another example, the second frame includes group IDs corresponding to multiple second devices. For instance, after the first device and multiple second devices perform beamforming training, the second frame is sent via broadcast or multicast, and this second frame includes the group IDs corresponding to these multiple second devices.

[0187] As one possible implementation, the second frame is a management frame that includes the group ID corresponding to the second device. For example, the management frame could be an action frame, such as a beamforming grouping announcement frame.

[0188] Figure 8a is a schematic diagram of the action frame format provided in an embodiment of this application. As shown in Figure 8a, the action frame includes: category, IMMW action, and group ID. The IMMW action field is used to indicate the type of the action frame. The group ID field is used to carry the group ID. The embodiments of this application do not limit the length or position of the various fields shown in Figure 8a.

[0189] For example, management frames can be either protected frames or unprotected frames.

[0190] As another possible implementation, the second frame is a control frame, such as a trigger frame.

[0191] Figure 8b is a schematic diagram of the trigger frame format provided in an embodiment of this application. As shown in Figure 8b, the trigger frame includes at least one of the following: frame control, duration, receiver address (RA), transmitter address (TA), common information, user information list, padding, or frame check sequence (FCS). The user information list field includes one or more user information fields.

[0192] The user information field includes an identifier corresponding to the second device and a group ID corresponding to the second device. As shown in Figure 8b, the user information field includes at least one of the following: association identifier (AID) (e.g., AID12), resource unit allocation, coding type, modulation and coding scheme, dual carrier modulation (DCM), spatial stream allocation, uplink target receive power, reserved, trigger dependent user information, or group ID. The group ID field is used to indicate the group ID corresponding to the second device identified by AID12. Figure 8b illustrates an example where the group ID field is carried within the user information field. As another possible implementation, the group ID field can also be carried within the trigger dependent user information field. The specific location of the group ID field within the user information field is not limited in this embodiment.

[0193] The trigger frame format shown in Figure 8b is merely an example, and its format may change as standards evolve. Even if the trigger frame format changes, as long as the trigger frame includes a user information field that includes a group ID, the trigger frame falls within the protection scope of this application's embodiments.

[0194] In one possible implementation, when the second device and the first device re-perform beamforming training, after the beamforming training is completed, the first device can reassign a group ID to the second device. If the group ID corresponding to the second device is updated, the first device can indicate the new group ID to the second device. The method by which the first device assigns a group ID to the second device is similar to the description of the second frame above, and will not be elaborated here.

[0195] Before sending the second frame, the first device may also generate the second frame. For a description of the second frame, please refer to the above; it will not be detailed here.

[0196] After receiving the second frame, the second device can further parse it. For example, the second device can determine its own group ID based on the second frame. After determining its group ID, the second device can request the first device to create or join a TWT protocol. This TWT protocol can be a TWT protocol applied to millimeter-wave links, or a TWT protocol corresponding to its own group ID.

[0197] As an example, the second device requests the TWT protocol based on its corresponding group ID (as in steps 405 and 406). Before requesting participation in the TWT protocol applied to the millimeter-wave link, or before requesting participation in the TWT protocol in a certain transmission direction, the second device completes beamforming training with the first device.

[0198] As another example, the first device autonomously assigns a TWT protocol to the second device based on the group ID corresponding to the second device (as in step 407).

[0199] In one possible implementation, the method shown in Figure 4 further includes:

[0200] 405. The second device sends a TWT request, which includes TWT parameters of the TWT protocol corresponding to the group ID of the second device. Correspondingly, the first device receives the TWT request.

[0201] The TWT parameter includes the group ID corresponding to the second device. Optionally, the TWT parameter also includes the broadcast TWT ID of the TWT protocol. Optionally, the TWT parameter also includes at least one of the following: TWT, minimum TWT wake-up duration, or a fractional part of the minimum TWT wake-up interval, etc., which will not be described in detail here.

[0202] Optionally, the TWT request includes a TWT element, which carries the aforementioned TWT parameters. For a description of the TWT element, please refer to the above text; it will not be elaborated upon here.

[0203] 406. The first device sends a TWT response to the TWT request. Correspondingly, the second device receives the TWT response.

[0204] A TWT response is used to accept or reject a TWT request.

[0205] For specific details regarding TWT requests and TWT responses, please refer to the above or relevant standards. This application does not limit the specific format of TWT requests and TWT responses.

[0206] In one possible implementation, the method shown in Figure 4 further includes:

[0207] 407. The first device sends a spontaneous TWT response, which indicates the TWT agreement corresponding to the second device. Correspondingly, the second device receives the spontaneous TWT response.

[0208] The spontaneous TWT response includes a TWT element, the TWT protocol indicated by which is determined based on the group ID corresponding to the second device. For example, the first device determines the TWT protocol corresponding to the second device based on the correspondence between the TWT protocol and the group ID, and the group ID corresponding to the second device.

[0209] For specific details regarding spontaneous TWT responses, please refer to the above or relevant standards. This application does not limit the specific format of spontaneous TWT responses in its embodiments.

[0210] In the steps shown in Figure 4, steps 401 to 403 are mandatory, while steps 404 to 407 are optional. Steps 401 and 403 can be separate embodiments, or at least one of steps 404 to 407 can be combined with a foregoing embodiment to form a new embodiment. Alternatively, steps 401 to 403 can be optional, while steps 404 to 406 are mandatory, or steps 404 and 407 are mandatory. Steps 404 to 406 can be separate embodiments, or steps 404 and 407 can be separate embodiments, with steps 401 to 403 combined with a foregoing embodiment to form a new embodiment. The combinations of steps 401 to 407 are not listed here individually.

[0211] Figure 9 is a schematic diagram of a communication method provided in an embodiment of this application. The first device is an IMMW AP MLD, and the second device is an IMMW non-AP MLD. As shown in Figure 9, the IMMW AP MLD transmits a beacon frame on a sub-7GHz link. The beacon frame includes one or more first TWT elements, which include a broadcast TWT ID and a group ID. For a detailed description of the first TWT element, please refer to the above text; it will not be elaborated here. The IMMW non-AP MLD receives the beacon frame. The IMMW non-AP MLD can store the TWT parameters corresponding to the broadcast TWT protocol. After beamforming training, the IMMW AP MLD and the IMMW non-AP MLD transmit a second frame, which includes the group ID corresponding to the IMMW non-AP MLD. The IMMW non-AP MLD receives the second frame. This second frame can be transmitted on a millimeter-wave link or a sub-7GHz link. Optionally, the IMMW non-AP MLD responds with an acknowledgement (ACK). ACK can be transmitted on millimeter-wave links or sub-7GHz links. Further, the IMMW non-AP MLD sends a TWT request, which includes the TWT parameters of the TWT protocol corresponding to the group ID of the IMMW non-AP MLD. The IMMW AP MLD receives the TWT request and replies with a TWT response. Optionally, after the IMMW AP MLD accepts the TWT request, the IMMW AP MLD and the IMMW non-AP STA communicate within the negotiated TWT SP in the agreed direction.

[0212] For a detailed explanation of Figure 9, please refer to the description in Figure 4; it will not be repeated here.

[0213] In this embodiment of the application, the first device creates a TWT protocol based on the group ID, which makes the allocation of the TWT protocol more reasonable, thereby effectively solving the hidden node problem in the millimeter wave communication process, reducing the collision of hidden nodes, improving communication efficiency and energy efficiency, and reducing the waste of channel resources.

[0214] In the method shown in Figure 4, a TWT protocol is identified by two IDs: a broadcast TWT ID and a group ID. The broadcast TWT ID can be considered to identify the TWT protocol in terms of time, while the group ID identifies the TWT protocol in terms of transmission direction or geographical location. In the method shown in Figure 10 below, a TWT protocol uses a single ID to simultaneously describe the TWT protocol in terms of time and transmission direction (or geographical location).

[0215] Figure 10 is a schematic flowchart of another communication method provided in an embodiment of this application. The descriptions of the first and second devices involved in this method are as above and will not be repeated here. As shown in Figure 10, the method includes:

[0216] 1001. The first device generates a first frame, which includes a first TWT element. The first TWT element is used to indicate the TWT parameters corresponding to the TWT protocol. The TWT parameters include an ID determined according to the broadcast TWT identifier ID and the group ID. This ID is used to identify the TWT protocol.

[0217] Alternatively, this ID considers both the broadcast TWT ID and the group ID. Alternatively, this ID represents the temporal and spatial (e.g., transmission direction or geographical location) relationship of the TWT protocol. Alternatively, this ID can be used to describe the TWT protocol in terms of time and transmission direction (or geographical location). Alternatively, the first device creates the TWT protocol based on the TWT SP and transmission direction (or geographical location). The explanation of the broadcast TWT ID and group ID is given above and will not be detailed here. For ease of description, the aforementioned ID is referred to as the directional TWT ID or spatial TWT ID in this embodiment. This directional TWT ID can be used to identify a directional TWT protocol. Optionally, the format of the first TWT element is shown in FIG12 and will not be detailed here.

[0218] In one possible implementation, the TWT parameters also include millimeter-wave link information, which indicates the millimeter-wave link to which the TWT protocol applies. The millimeter-wave link information includes the link ID of the millimeter-wave link; alternatively, the millimeter-wave link is indicated by a millimeter-wave link ID bitmap. For a description of the millimeter-wave link information, refer to Figure 4; the details are similar and will not be repeated here.

[0219] For further details regarding the first frame, please refer to Figure 4, as the details are similar and will not be repeated here. For ease of reference, both Figure 4 and Figure 10 use the first TWT element for illustration. As another possible implementation, the names of the first TWT elements in Figure 4 and Figure 10 may differ, and this embodiment does not limit this. The description of the names here also applies to the first frame or the second frame.

[0220] As an example, the first device maintains the relationship between the group ID and the directional TWT ID. For instance, the first device divides the space into N transmission directions, each corresponding to one or more TWT protocols, and the total number of TWT protocols across all N transmission directions is M. M and N are positive integers.

[0221] For example, as shown in Table 1, the first device maintains the relationship between group IDs and directional TWT IDs in a tabular format. The directional TWT ID indicates the transmission direction (or geographical location, etc.) corresponding to the TWT protocol. For instance, a directional TWT ID of 1 or 2 corresponds to transmission direction 1 of the TWT protocol, applicable to non-AP STAs in group 1. These are not listed individually here. 1+2+3+……+P-1+P=M. P is a positive integer. The identifiers 1 to P in Table 1 are merely examples and are not intended to limit the embodiments of this application.

[0222] Table 1

[0223] As another example, the first device maintains the relationship between broadcast TWT IDs and directed TWT IDs. For instance, the first device divides P TWT protocols into multiple groups according to the transmission direction, with each group containing TWT protocols having the same group ID. Since the number of broadcast TWT IDs in each group is the same as the number of directed TWT IDs, the directed TWT ID and the broadcast TWT ID can be the same ID or different IDs.

[0224] For example, as shown in Table 2, the first device maintains the relationship between broadcast TWT IDs and directed TWT IDs in a tabular manner. For example, x1 = 1, x2 = 2, and so on. For example, x1 ≠ 1, x2 ≠ 2, and so on.

[0225] Table 2

[0226] As yet another example, the relationship between the first device maintenance group ID, broadcast TWT ID, and directed TWT ID.

[0227] Table 3

[0228] For an explanation of Table 3, please refer to Tables 1 and 2; it will not be elaborated here.

[0229] As one possible implementation, the first frame also includes a second TWT element.

[0230] As an example, this second TWT element is used to indicate the mapping between the directional TWT ID and the group ID. For a description of the mapping, refer to the above (such as Table 1, etc.), which will not be detailed here. Optionally, the second TWT element includes a control field, which includes a negotiation type field. For a description of the negotiation type field, refer to the following text, which will not be detailed here.

[0231] For example, the second TWT element includes a group number field indicating the total number of group IDs. The second TWT element may also include a directed TWT ID field for each group ID, indicating the number of directed TWT IDs corresponding to that group ID.

[0232] Optionally, the targeted TWT ID can be determined based on the total number of group IDs and the number of targeted TWT IDs corresponding to each group ID. For example, the targeted TWT IDs corresponding to group ID n are M n-1 +1, ..., M n +M n-1 Mn represents the number of directed TWT IDs corresponding to group ID n. n = 1, 2, ..., N, where N is the total number of group IDs. When n = 1, M0 = 0.

[0233] Figure 11a is a schematic diagram of a format of a second TWT element provided in an embodiment of this application. As shown in Figure 11a, the second TWT element includes at least one of the following: element ID, length, and control or TWT parameter information. The TWT parameter information field includes the number of IMMW groups and directional TWT information. The directional TWT information field includes the number of directional TWT1, the number of directional TWT2, ..., the number of directional TWT N.

[0234] The IMMW group quantity field indicates the total number of group IDs, such as N. The Directed TWT 1 quantity field indicates the number M1 of directed TWT IDs corresponding to group ID 1, and so on. The Directed TWT N quantity field indicates the number M of directed TWT IDs corresponding to group ID N. n The group IDs corresponding to the number of directed TWTs in the directed TWT information are ordered in ascending order of group ID. The order shown in Figure 11a is only an example and is not intended to limit the embodiments of this application.

[0235] Optionally, the length of the quantity field of the IMW group is 8 bits, and the length of the directed TWT information is variable, with the length of the quantity field of a directed TWT N being 6 bits. The embodiments of this application do not limit the length of each field.

[0236] Figure 11b is a schematic diagram of another format of the second TWT element provided in an embodiment of this application. As shown in Figure 11b, the directed TWT information field includes the directed TWT ID corresponding to group ID1, the directed TWT ID corresponding to group ID2, and so on, with the directed TWT ID corresponding to group IDN. For other descriptions of Figure 11b, please refer to Figure 11a, which will not be detailed here.

[0237] Optionally, the length of the number field of the IMW group is bits, and the length of the directed TWT information is variable. The length of the directed TWT field corresponding to a group ID N is 24 bits. The embodiments of this application do not limit the length of each field.

[0238] Figure 11c is a schematic diagram of another format of the second TWT element provided in an embodiment of this application. As shown in Figure 11c, the control fields in the second TWT element include at least one of the following: IMMW group quantity existence, IMMW group existence, directed TWT quantity existence, or directed TWT ID existence. The IMMW group quantity existence field is used to indicate whether the TWT parameter information field contains an IMMW group quantity field; the IMMW group existence field is used to indicate whether the TWT parameter information field contains an ID for each group; the directed TWT quantity existence field is used to indicate whether the TWT parameter information field contains a directed TWT quantity field; and the directed TWT ID existence field is used to indicate whether the TWT parameter information field contains a directed TWT ID.

[0239] The lengths of each field in Figure 11c can be found in Figures 11a and 11b, etc., and will not be listed here. Other explanations regarding Figure 11c can be found in Figures 11a or 11b, and will not be elaborated here.

[0240] The control fields in the second TWT element include a negotiation type field. If this negotiation type field occupies 3 bits, the value of these 3 bits can be any one of 4-7, and any one of 4-7 indicates the type of the second TWT element.

[0241] For example, for a personal TWT, the TWT parameter setting field in the TWT element can be called the personal TWT parameter setting field. For a broadcast TWT, the TWT parameter setting field in the TWT element can be called the broadcast TWT parameter setting field. Referring to Figure 10, the TWT parameter setting field in the TWT element can be called the directed TWT parameter setting field. If the negotiation type field has a value of 4, it indicates that the TWT element includes a directed TWT parameter setting field.

[0242] Figure 11d is a schematic diagram of another format of the second TWT element provided in an embodiment of this application. As shown in Figure 11d, the control field of the second TWT element includes a negotiation type field. The lengths of each field shown in Figure 11d are only examples; the lengths of each field can be referred to in Figure 11a, etc., and will not be listed here.

[0243] As another example, the second TWT element is used to indicate the mapping between broadcast TWT IDs and directed TWT IDs. As yet another example, the second TWT element is used to indicate the mapping between broadcast TWT IDs, group IDs, and directed TWT IDs. Optionally, the second TWT element includes a control field, which includes a negotiation type field. For an explanation of the negotiation type field, please refer to the above; it will not be detailed here. Other formats of the second TWT element are not listed here.

[0244] As another possible implementation, the method shown in Figure 10 further includes: the first device sending a second TWT element, and correspondingly, the second device receiving the second TWT element. This second TWT element may be carried in a management frame or a control frame, etc. That is, the second TWT element can be included in the same frame as the first TWT element, or it can be included in different frames. For a description of the second TWT element, refer to the implementation described above; the details are similar and will not be repeated here.

[0245] 1002. The first device sends the first frame. Correspondingly, the second device receives the first frame.

[0246] For an explanation of step 1002, please refer to step 402. The details are similar and will not be repeated here.

[0247] 1003. The second device analyzes the first frame.

[0248] For example, the second device determines the correspondence between the directional TWT ID and the TWT protocol based on the first TWT element in the first frame. Similarly, the second device determines the correspondence between the directional TWT ID and the group ID based on the first and second TWT elements in the first frame. Furthermore, the second device determines the correspondence between the broadcast TWT ID, the group ID, and the TWT protocol based on the first TWT element and the second TWT factor. These are just a few examples.

[0249] In one possible implementation, the method shown in Figure 10 further includes:

[0250] 1004. The first device sends a second frame to the second device. The second frame includes a group ID or directional TWT ID corresponding to the second device. The group ID or directional TWT ID corresponding to the second device is determined by the first device and the second device after beamforming training. Correspondingly, the second device receives the second frame.

[0251] The relationship between group ID and directed TWT ID is explained above and will not be elaborated here.

[0252] As an example, the first device transmits the second frame on a millimeter-wave link. Correspondingly, the second device receives the second frame on the millimeter-wave link. As another example, the first device transmits the second frame on a sub-7GHz link. Correspondingly, the second device receives the second frame on a sub-7GHz link. This application embodiment does not limit the order of steps 1004 and 1002, and similarly, does not limit the order of steps 1004 and 1001.

[0253] The first device and the second device perform beamforming training. The first device determines the transmission direction or geographical location of the second device based on the beam matched with the second device, and determines the group ID or directional TWT ID corresponding to the second device.

[0254] As an example, the second frame includes a group ID or directional TWT ID corresponding to a second device. For instance, after the first device and a second device perform beamforming training, the first device sends a second frame to the second device via unicast, and this second frame includes the group ID or directional TWT ID corresponding to the second device.

[0255] As another example, the second frame includes group IDs or orientation TWT IDs corresponding to multiple second devices. For instance, after the first device and multiple second devices perform beamforming training, the second frame is sent via broadcast or multicast, and this second frame includes the group IDs or orientation TWT IDs corresponding to these multiple second devices.

[0256] The second frame can be a management frame or a control frame, etc. For other explanations about the second frame, please refer to step 404, or the description in Figure 8a or Figure 8b, etc. The details are similar and will not be repeated here.

[0257] In one possible implementation, when the second device and the first device re-perform beamforming training, after the beamforming training is completed, the first device can reassign the group ID or directional TWT ID to the second device. For an explanation of the reassignment, refer to step 404; it will not be repeated here.

[0258] As an example, the second device requests a TWT agreement based on its corresponding group ID or directional TWT ID (as in steps 1005 and 1006). Before requesting participation in a TWT agreement applied to a millimeter-wave link, or before requesting participation in a TWT agreement in a certain transmission direction, the second device completes beamforming training with the first device.

[0259] As another example, the first device autonomously assigns a TWT protocol to the second device based on the group ID or directional TWT ID corresponding to the second device (as in step 1007).

[0260] Optionally, for the second TWT element shown in Figure 11a, the second device determines the directional TWT IDs of all TWT protocols in the transmission direction corresponding to that group ID based on its own group ID and the second TWT element. For example, if its own group ID is n, then the directional TWT ID corresponding to group ID n is M. n-1 +1, ..., M n +M n-1 The second device requests the creation or joining of a TWT agreement with a directional TWT ID, including M. n-1 +1, ..., M n +M n-1 .

[0261] In one possible implementation, the method shown in Figure 10 further includes:

[0262] 1005. The second device sends a TWT request, which includes TWT parameters of the TWT agreement corresponding to the group ID or directed TWT ID corresponding to the second device. Correspondingly, the first device receives the TWT request.

[0263] The TWT parameter includes the group ID or orientation TWT ID corresponding to the second device.

[0264] Figure 12 is a schematic diagram of the format of a TWT element provided in an embodiment of this application. As shown in Figure 12, the TWT element in a TWT request may include a directional TWT ID corresponding to the second device. Other descriptions of Figure 12 are as described above and will not be repeated here.

[0265] 1006. The first device sends a TWT response to the TWT request. Correspondingly, the second device receives the TWT response. The TWT response is used to accept or reject the TWT request.

[0266] In one possible implementation, the method shown in Figure 10 further includes:

[0267] 1007. The first device sends a spontaneous TWT response, which indicates the TWT agreement corresponding to the second device. Correspondingly, the second device receives the spontaneous TWT response.

[0268] The spontaneous TWT response includes a TWT element, the TWT agreement indicated by which is determined based on the group ID or directional TWT ID corresponding to the second device.

[0269] The relationship between the steps is shown in Figure 4, and will not be elaborated here.

[0270] In this embodiment, the first device creates a TWT protocol based on the group ID and the directional TWT ID corresponding to the broadcast TWT ID, which makes the allocation of TWT protocols more reasonable, thereby effectively solving the hidden node problem in millimeter wave communication, reducing collisions of hidden nodes, improving communication efficiency and energy efficiency, and reducing the waste of channel resources.

[0271] Figure 13 is a schematic flowchart of another communication method provided in an embodiment of this application. The descriptions of the first and second devices involved in this method are as above and will not be repeated here. As shown in Figure 13, the method includes:

[0272] 1301. The second device sends a TWT request, which is used to request the TWT agreement. Correspondingly, the first device receives the TWT request.

[0273] 1302. The first device sends a TWT response to the second device in response to the TWT request. The TWT response includes TWT parameters of the TWT agreement corresponding to the second device. The TWT parameters are determined according to the beam direction of the second device. The beam direction is determined by the first device and the second device after beamforming training.

[0274] In this embodiment, the first device configures the TWT protocol for the second device in conjunction with the beam direction of the second device, so that the TWT protocol can be better matched to the second device, thereby improving communication efficiency and energy efficiency.

[0275] This application also provides a communication method, which includes:

[0276] The second device sends a TWT request, and the corresponding first device receives the TWT request. The TWT request includes a trigger field, which indicates whether the Access Point (AP) or a non-AP STA is the TXOP holder on the millimeter-wave link. If the trigger field value is a first value (e.g., 1), it indicates that the AP is the TXOP holder on the millimeter-wave link; if the trigger field value is a second value (e.g., 0), it indicates that a non-AP STA is the TXOP holder on the millimeter-wave link. In other words, when the trigger field value is the first value, the AP initiates data transmission as the TXOP holder after successfully participating in channel contention within the TWT SP. When the trigger field value is the second value, a non-AP STA initiates data transmission as the TXOP holder after successfully participating in channel contention within the TWT SP.

[0277] Figure 14 is a schematic diagram illustrating the format of the TWT parameter information field in the TWT element of a TWT request provided in an embodiment of this application. Figure 14 exemplarily shows the fields included in the TWT parameter information field. The trigger field is B4 bits. Of course, the format of the TWT request shown in Figure 14 is merely an example and is not intended to limit the embodiments of this application.

[0278] This application also provides a communication method applicable to restricted TWT (R-TWT) operation. R-TWT operation allows non-AP STAs to use enhanced channel orientation protection and resource reservation mechanisms to transmit latency-sensitive data. The R-TWT protocol is a type of broadcast TWT protocol.

[0279] As an example, any non-AP STA supporting R-TWT functionality, when acting as a TXOP holder, must ensure that its TXOP ends before the start time of any other non-AP STA's TWT SP. That is, there should be no other ongoing TXOPs within this BSS when other non-AP STAs' TWT SPs begin (applicable only to all non-AP STAs supporting R-TWT functionality). Optionally, the non-AP STAs mentioned here, along with other non-AP STAs, all support R-TWT functionality. The other non-AP STAs mentioned here refer to other non-AP STAs within this BSS that also have established R-TWT functionality, excluding the current TXOP holder.

[0280] As another example, on millimeter-wave links, the TXOP holder must ensure that the TXOP of the non-AP STA ends before the start time of the TWT SP of other TXOP holders in the same transmission direction.

[0281] The names, lengths, and positions of the frames, elements, or fields shown in the embodiments of this application are merely examples and are not intended to limit the embodiments of this application. This application uses fields as examples and does not specifically distinguish between fields, subfields, elements, or subelements, but this should not be considered a limitation on the embodiments of this application. The unit of length for each field can be bits, bytes, or double bytes; this application does not limit this.

[0282] In this embodiment of the application, the fields shown by the dashed lines in the accompanying drawings are optional fields, and fields with a length of 0 are also optional fields.

[0283] The apparatus provided in the embodiments of this application will be described below.

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

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

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

[0287] Processing module 1501 is used to generate the first frame;

[0288] The transceiver module 1502 is used to send or output the first frame.

[0289] The transceiver module 1502 is also used to send or output a second frame. Optionally, the processing module 1501 is also used to generate a second frame.

[0290] The transceiver module 1502 is also used to receive or input TWT requests and to send or output TWT responses. Optionally, the processing module 1501 is also used to parse TWT requests and generate TWT responses.

[0291] The transceiver module 1502 is also used to send or output spontaneous TWT responses. Optionally, the processing module 1501 is also used to generate spontaneous TWT responses.

[0292] Reusing Figure 15, in some other embodiments of this application, the device can be used to perform the actions performed by the second device in the above method embodiments. In this case, the device can be the device itself or a chip or functional module configurable in the device. The transceiver module 1502 is used to perform the transceiver-related operations of the second device in the above method embodiments, and the processing module 1501 is used to perform the processing-related operations of the second device in the above method embodiments.

[0293] The transceiver module 1502 is used to receive or input the first frame;

[0294] Processing module 1501 is used to parse the first frame.

[0295] The transceiver module 1502 is also used to receive or input the second frame. Optionally, the processing module 1501 is also used to parse the second frame.

[0296] The transceiver module 1502 is also used to send or output TWT requests and to receive or input TWT responses. Optionally, the processing module 1501 is also used to generate TWT requests and parse TWT responses.

[0297] The transceiver module 1502 is also used to receive or input spontaneous TWT responses. Optionally, the processing module 1501 is also used to parse the spontaneous TWT response.

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

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

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

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

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

[0303] The apparatus of the embodiments of this application has been described above. The possible product forms of the described apparatus are described below. Any product possessing the functions of the apparatus described in FIG. 15 above falls within the protection scope of the embodiments of this application. The following description is merely illustrative and does not limit the product form of the apparatus of the embodiments of this application to this.

[0304] In one possible implementation, in the device shown in FIG15, the processing module 1501 may be one or more processors, and the transceiver module 1502 may be a transceiver, or the transceiver module 1502 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 a single device, such as a transceiver. In the embodiments of this application, the processor and the transceiver may be coupled, etc., and the connection method between the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information in the above method may be the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method 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 into the processor. Furthermore, after the transceiver receives the above information, the above information may need to undergo other processing before being input into the processor.

[0305] Figure 16 is a schematic diagram of an apparatus provided in an embodiment of this application. As shown in Figure 16, the apparatus 160 includes one or more processors 1620 and transceivers 1610.

[0306] In some embodiments of this application, the above-described apparatus can be used to perform the steps, methods, or functions performed by the first apparatus. For example, the processor 1620 can be used to perform the functions or steps implemented by the processing module 1501 shown in FIG. 15, and the transceiver 1610 can be used to perform the functions or steps implemented by the transceiver module 1502 shown in FIG. 15. Detailed descriptions of the processor 1620 and the transceiver 1610 can be found in FIG. 15 or the method embodiments shown above, and will not be elaborated further here.

[0307] In other embodiments of this application, the above-described apparatus is used to perform the steps, methods, or functions performed by the second apparatus. For example, the processor 1620 can be used to perform the functions or steps implemented by the processing module 1501 shown in FIG. 15, and the transceiver 1610 can be used to perform the functions or steps implemented by the transceiver module 1502 shown in FIG. 15. Detailed descriptions of the processor 1620 and the transceiver 1610 can be found in FIG. 15 or the method embodiments shown above, and will not be elaborated further here.

[0308] The following explanation uses the device shown in Figure 16 as an example of a communication device.

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

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

[0311] This embodiment does not limit the specific connection medium between the transceiver 1610, processor 1620, and memory 1630. In Figure 16, the memory 1630, processor 1620, and transceiver 1610 are connected via a bus 1640, indicated by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 16, but this does not imply that there is only one bus or one type of bus.

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

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

[0314] The processor 1620 is primarily used for processing communication protocols and data, controlling the entire communication device, executing software programs, and processing software program data. The memory 1630 is primarily used for storing software programs and data. The transceiver 1610 may include control circuitry and an antenna. The control circuitry is primarily used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is primarily used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are primarily used for receiving user input data and outputting data to the user.

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

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

[0317] The communication device shown in this application embodiment may also have more components than those in Figure 16, and this application embodiment does not limit this. The methods executed by the processor and transceiver shown above are only examples, and the specific steps executed by the processor and transceiver can be referred to the methods described above. The dashed lines in Figure 16 indicate optional parts.

[0318] In another possible implementation, in the communication device shown in Figure 15, the processing module 1501 can be one or more logic circuits, and the transceiver module 1502 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver module 1502 can also be a transmitting module and a receiving module, where the transmitting module can be an output interface and the receiving module can be an input interface, and the transmitting module and the receiving module are integrated into one module, such as an input / output interface.

[0319] Figure 17 is a schematic diagram of a chip provided in an embodiment of this application. As shown in Figure 17, the chip includes a logic circuit 1701 and an interface 1702. That is, the processing module 1501 can be implemented using the logic circuit 1701, and the transceiver module 1502 can be implemented using the interface 1702. The logic circuit 1701 can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface 1702 can be a communication interface, input / output interface, pins, etc. For example, Figure 17 illustrates a chip using the aforementioned device as an example, where the chip includes a logic circuit 1701 and an interface 1702.

[0320] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method of the logic circuit and the interface is not limited in this embodiment. For example, the logic circuit 1701 can be used to execute the functions or steps implemented by the processing module 1501 shown in FIG. 15, and the interface 1702 can be used to execute the functions or steps implemented by the transceiver module 1502 shown in FIG. 15. For a detailed description of the logic circuit 1701 and the interface 1702, please refer to FIG. 15 or the method embodiment shown above, which will not be detailed here.

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

[0322] Furthermore, embodiments of this application also provide a communication system, which includes a first device and a second device, the first device and the second device being usable for performing the methods in any of the foregoing embodiments.

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

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

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

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

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

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

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

Claims

1. A communication method, characterized in that, The method includes: The first device generates a first frame, which includes a first target wake-up time (TWT) element. The first TWT element is used to indicate the TWT parameters corresponding to the TWT protocol. The TWT parameters include a broadcast TWT identifier ID and a group ID. The broadcast TWT ID and the group ID are used to identify the TWT protocol. The first device sends the first frame.

2. A communication method, characterized in that, The method includes: The first device generates a first frame, the first frame including a first target wake-up time (TWT) element, the first TWT element being used to indicate the TWT parameters corresponding to the TWT protocol, the TWT parameters including a directed TWT ID determined according to the broadcast TWT identifier ID and the group ID, the directed TWT ID being used to identify the TWT protocol; The first device sends the first frame.

3. The method according to claim 1 or 2, characterized in that, The TWT parameters also include millimeter-wave link information, which is used to indicate the millimeter-wave link to which the TWT protocol is applied.

4. The method according to claim 3, characterized in that, The millimeter-wave link information includes the link ID of the millimeter-wave link; or, the millimeter-wave link is indicated by a millimeter-wave link ID bitmap.

5. The method according to claim 2, characterized in that, The first frame also includes a second TWT element, which is used to indicate the correspondence between the directional TWT ID and the group ID.

6. The method according to any one of claims 1-5, characterized in that, The group ID is determined based on the transmission direction.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: A second frame is sent to the second device. The second frame includes a group ID or directional TWT ID corresponding to the second device. The group ID or directional TWT ID corresponding to the second device is determined by the first device and the second device after beamforming training.

8. The method according to claim 7, characterized in that, The method further includes: Receive a TWT request from the second device, the TWT request including TWT parameters of the TWT protocol corresponding to the ID of the second device, the TWT parameters including the group ID or directed TWT ID corresponding to the second device; Send the TWT response to the TWT request to the second device.

9. The method according to claim 7, characterized in that, The method further includes: Send a spontaneous TWT response to the second device, the spontaneous TWT response being used to indicate the TWT agreement corresponding to the second device.

10. A communication method, characterized in that, The method includes: The second device receives a first frame, the first frame including a first target wake-up time (TWT) element, the first TWT element being used to indicate the TWT parameters corresponding to the TWT protocol, the TWT parameters including a broadcast TWT identifier ID and a group ID, the broadcast TWT ID and the group ID being used to identify the TWT protocol; The second device parses the first frame.

11. A communication method, characterized in that, The method includes: The second device receives a first frame, the first frame including a first target wake-up time (TWT) element, the first TWT element being used to indicate the TWT parameters corresponding to the TWT protocol, the TWT parameters including a directed TWT ID determined according to the broadcast TWT identifier ID and the group ID, the directed TWT ID being used to identify the TWT protocol; The second device parses the first frame.

12. The method according to claim 10 or 11, characterized in that, The TWT parameters also include millimeter-wave link information, which is used to indicate the millimeter-wave link to which the TWT protocol is applied.

13. The method according to claim 12, characterized in that, The millimeter-wave link information includes the link ID of the millimeter-wave link; or, the millimeter-wave link is indicated by a millimeter-wave link ID bitmap.

14. The method according to claim 11, characterized in that, The first frame also includes a second TWT element, which is used to indicate the correspondence between the directional TWT ID and the group ID.

15. The method according to any one of claims 10-14, characterized in that, The group ID is determined based on direction.

16. The method according to any one of claims 10-15, characterized in that, The method further includes: A second frame is received from the first device, the second frame including a group ID or directional TWT ID corresponding to the second device, the group ID or directional TWT ID corresponding to the second device being determined by the first device and the second device after beamforming training.

17. The method according to claim 16, characterized in that, The method further includes: Send a TWT request to the first device. The TWT request includes a group ID or directed TWT ID corresponding to the second device, and TWT parameters of the TWT agreement corresponding to the group ID or directed TWT ID corresponding to the second device. Receive a TWT response from the TWT request received from the first device.

18. The method according to claim 16, characterized in that, The method further includes: Receive a spontaneous TWT response from the first device, the spontaneous TWT response being used to indicate a TWT agreement corresponding to the second device.

19. A communication method, characterized in that, The method includes: Receive a Target Wake-Up Time (TWT) request from a second device, the TWT request being used to request a TWT agreement; The first device sends a TWT response to the TWT request to the second device. The TWT response includes TWT parameters of the TWT protocol corresponding to the second device. The TWT parameters of the TWT protocol are determined according to the beam direction of the second device. The beam direction is determined by the first device and the second device after beamforming training.

20. A communication method, characterized in that, The method includes: Send a Target Wake-up Time (TWT) request to the first device, the TWT request being used to request the TWT agreement; The device receives a TWT response to the TWT request from the first device. The TWT response includes TWT parameters of a TWT protocol corresponding to the second device. The TWT parameters of the TWT protocol are determined based on the beam direction of the second device. The beam direction is determined by the first device and the second device after beamforming training.

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

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

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

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

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

26. A communication system, characterized in that, The system includes a first device and a second device, the first device being configured to perform the method as described in any one of claims 1-9 and 19, and the second device being configured to perform the method as described in any one of claims 10-18 and 20.

Images