Multi-link communication method and apparatus

Abstract

A multi-link communication method and apparatus are disclosed, which may be used in a wireless local area network system supporting IEEE 802.22ax next-generation Wi-Fi protocols, e.g., 802.22be, Wi-Fi 7, or EHT, and 802.22be next-generation protocols, e.g., Wi-Fi 8 or UHR, or in a UWB-based wireless personal local area network system, a sensing system, etc. The method includes a station in a multi-link device generating and transmitting a communication frame. A peer station operating on the same associated link as the transmitting station of the communication frame receives the communication frame and terminates a TWT agreement based on the communication frame. The communication frame includes a first field and a second field. The first field indicates one or more links, and the second field indicates the termination of a TWT agreement or TWT plan between the multi-link devices. Embodiments of the present application may effectively improve the flexibility of terminating a TWT agreement.

Description

[Technical Field]

[0001] This application claims priority to Chinese Patent Application No. 202211385738.5, entitled "MULTI-LINK COMMUNICATION METHOD AND APPARATUS," filed with the State Intellectual Property Office of the People's Republic of China on November 7, 2022, the entire contents of which are incorporated herein by reference.

[0002] [Technical field] The present application relates to the field of communication technologies, and more particularly to a multi-link communication method and apparatus. [Background technology]

[0003] The next generation Wi-Fi extreme high throughput (EHT) protocol of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 may use ultra-large bandwidth in new frequency bands above 6 GHz to transmit information packets, and multiple non-contiguous links may also be aggregated to form ultra-large bandwidth by using multi-link cooperation techniques.

[0004] Multi-link cooperation techniques can aggregate larger bandwidths and also share the medium access control (MAC) layer over multiple links to flexibly transmit information packets or simultaneously transmit information packets of the same service to the same station. For example, devices that implement multi-link cooperation techniques may be referred to as multi-link devices. Multi-link devices may associate with each other through a single link. In this way, multiple links may quickly associate with each other. A target wake time agreement (TWT agreement) may be set up for one or more links between MLDs.

[0005] However, in a multi-link scenario, how to release the TWT agreement needs to be resolved urgently. Summary of the Invention [Means for solving the problem]

[0006] The present application provides a multi-link communication method and apparatus for effectively implementing the flexibility to release TWT agreements.

[0007] According to a first aspect, an embodiment of the present application provides a multi-link communication method, the method including: generating a communication frame, the communication frame including a first field and a second field, the first field indicating one or more links, and the second field indicating releasing a target wake time TWT agreement or TWT plan between multi-link devices; and sending the communication frame.

[0008] The communication frame may be referred to as a TWT release frame, a TWT deletion frame, a TWT information frame, etc. The first field may be referred to as a link information field. For example, the first field may be used to carry a link identifier for each of one or more links, or the first field may be used to carry a bitmap, with each bit in the bitmap indicating whether to release the corresponding link. The second field may include a teardown all TWT field or a teardown all TWT setup on all links field. The TWT agreement may correspond to an individual TWT negotiation type, and the TWT plan may correspond to a broadcast TWT negotiation type.

[0009] In this embodiment of the present application, the first field and the second field are used. The receiving end of the communication frame can effectively know the TWT agreement or TWT plan to be released by the receiving end based on the two fields. This effectively improves the flexibility of releasing the TWT agreement.

[0010] In a possible implementation, if the value of the second field is the first value, the communication frame indicates the cancellation of all TWT agreements or TWT plans on one or more links indicated by the first field.

[0011] The first value may be equal to 1. If the value of the second field is the first value, the value of the TWT flow identifier field in the communication frame is reserved, or the value of the broadcast TWT identifier field is reserved.

[0012] In this embodiment of the present application, when the value of the second field is a first value, the receiving end of the communication frame may cancel all TWT agreements on one or more links indicated by the first field on the link indicated by the first field. For example, there may be one or more TWT agreements on one link. For example, when the first field indicates one link, the receiving end of the communication frame may delete one or more TWT agreements on the link. In another example, when the first field indicates multiple links, the receiving end of the communication frame may cancel one or more TWT agreements on each of the multiple links. When the value of the second field is a first value, the receiving end of the communication frame may cancel all TWT agreements or all TWT plans on one or more links indicated by the first field. This effectively improves the efficiency of canceling TWT agreements or TWT plans and reduces signaling overhead.

[0013] In a possible implementation, when the value of the second field is the second value, the communication frame indicates the termination of a TWT agreement corresponding to a combination including a TWT flow identifier on each of the one or more links indicated by the first field, or the communication frame indicates the termination of a TWT plan corresponding to a combination including a broadcast TWT identifier on each of the one or more links indicated by the first field.

[0014] The second value may be equal to 0. When the value of the second field is the second value, the receiving end of the communication frame may terminate the TWT agreement corresponding to the combination including the TWT flow identifier on the link indicated by the first field. For example, when the first field indicates one link, the receiving end of the communication frame may terminate the TWT agreement (or TWT plan) corresponding to the combination including the TWT flow identifier (broadcast TWT identifier) ​​on the link. In another example, when the first field indicates multiple links, the receiving end of the communication frame may terminate the TWT agreement (or TWT plan) corresponding to the combination including the TWT flow identifier (broadcast TWT identifier) ​​on multiple links.

[0015] In this embodiment of the present application, the TWT agreement is terminated based on the first field and the different values ​​of the second field, so that the receiving end can know exactly which TWT agreement or TWT plan needs to be terminated by the receiving end, which improves the efficiency and flexibility of terminating the TWT agreement.

[0016] In a possible implementation, the communication frame further includes a third field, wherein the third field is used to carry a TWT flow identifier, or the third field is used to carry a broadcast TWT identifier.

[0017] In this embodiment of the present application, based on different values ​​of the second field, the third field can be used to carry a specific TWT flow identifier or a broadcast TWT identifier, or the third field can be set to reserved. Therefore, based on the first field, the second field, and the third field, the receiving end can accurately know the TWT agreement or TWT plan that needs to be released by the receiving end. This improves the efficiency and flexibility of releasing the TWT agreement.

[0018] In a possible implementation, the TWT agreement corresponds to one of the following combinations, each of which includes a TWT flow identifier: a combination of a TWT flow identifier, a media access control MAC address of a station on each of the one or more links indicated by the first field, and a MAC address of a peer station on the link indicated by the first field; or a combination of a TWT flow identifier, a MAC address of a multilink device to which the transmitting end of the communication frame belongs, a MAC address of a multilink to which the receiving end of the communication frame belongs, and a link indicated by the first field.

[0019] The contents corresponding to the TWT agreement may also be referred to as elements of the TWT agreement, elements for identifying the TWT agreement, information for uniquely identifying the TWT agreement, etc. The station and the peer station are associated with the same link.

[0020] In a possible implementation, the TWT plan corresponds to one of the following combinations, each of which includes a broadcast TWT identifier, i.e., a combination of a broadcast TWT identifier and a media access control MAC address of an access station on each of the one or more links indicated by the first field, or a combination of a broadcast TWT identifier and a MAC address of a multi-link device to which an access station on each of the one or more links indicated by the first indication belongs, and the link indicated by the first field.

[0021] The content corresponding to the above-mentioned TWT plan may also be referred to as elements of the TWT plan, elements for identifying the TWT plan, or information for uniquely identifying the TWT plan.

[0022] In a possible implementation, the first field is included in a multilink operation information element in the communication frame.

[0023] In a possible implementation, the second field is included in the TWT flow field in the communication frame.

[0024] According to a second aspect, an embodiment of the present application provides a multi-link communication method, the method including: receiving a communication frame, the communication frame including a first field and a second field, the first field indicating one or more links and the second field indicating canceling a target wake time TWT agreement or TWT plan between multi-link devices; and canceling the TWT agreement or TWT plan based on the communication frame.

[0025] In a possible implementation, the method includes determining a TWT agreement based on one of the following combinations, each of which includes a TWT flow identifier: a combination of the TWT flow identifier, a media access control MAC address of a station on each of the one or more links indicated by the first field, and a MAC address of a peer station on the link indicated by the first field; or a combination of the TWT flow identifier, a MAC address of a multilink device to which the transmitting end of the communication frame belongs, a MAC address of a multilink to which the receiving end of the communication frame belongs, and the link indicated by the first field; or The method further includes determining a TWT plan based on any one of the following combinations, each of which includes a broadcast TWT identifier: a combination of the broadcast TWT identifier and a media access control (MAC) address of an access station on each of the one or more links indicated by the first field, or a combination of the broadcast TWT identifier and a MAC address of a multi-link device to which an access station (e.g., a transmitting end of a communication frame) on each of the one or more links indicated by the first field belongs, and the link indicated by the first field.

[0026] In a possible implementation, terminating a TWT agreement or TWT plan based on the communication frame includes terminating all TWT agreements or all TWT plans on each of the one or more links indicated by the first field when the value of the second field is the first value.

[0027] In a possible implementation, terminating a TWT agreement or TWT plan based on a communication frame may be: If the value of the second field is the second value, terminating the TWT agreement corresponding to the TWT flow identifier on each of the one or more links indicated by the first field, or if the value of the second field is the second value, terminating the TWT plan corresponding to the broadcast TWT identifier on each of the one or more links indicated by the first field.

[0028] In a possible implementation, the first field is included in a multilink operation information element in the communication frame.

[0029] In a possible implementation, the second field is included in the TWT flow field in the communication frame.

[0030] According to a third aspect, an embodiment of the present application provides a multi-link communication method, where a plurality of associated links are established between a multi-link device to which a transmitting end of a communication frame belongs and a multi-link device to which a receiving end of the communication frame belongs, the method comprising: The method includes generating a communication frame, the communication frame including instruction information, the instruction information instructing to release a TWT agreement or a TWT plan on multiple associated links established between the multi-link devices, and transmitting the communication frame.

[0031] According to a fourth aspect, an embodiment of the present application provides a multi-link communication method, where a plurality of associated links are established between a multi-link device to which a transmitting end of a communication frame belongs and a multi-link device to which a receiving end of the communication frame belongs. The method includes: The method includes receiving a communication frame, the communication frame including instruction information instructing to terminate a TWT agreement or a TWT plan on a plurality of associated links established between the multi-link devices, and terminating the TWT agreement or the TWT plan on the plurality of associated links established between the multi-link devices based on the communication frame.

[0032] Regarding the third or fourth aspect, in a possible implementation, the value of the indication information is the first value.

[0033] With respect to the third or fourth aspect, in a possible implementation, the indication information is included in a TWT flow field in the communication frame.

[0034] The indication information may be used to carry a release field for all TWTs or all TWTs set up on all links. The TWT agreement may correspond to an individual TWT negotiation type, and the TWT plan may correspond to a broadcast TWT negotiation type.

[0035] Regarding the third or fourth aspect, in a possible implementation, the TWT agreement may be any of the following combinations, each including a TWT flow identifier: Corresponding to any one of a combination of a TWT flow identifier, a media access control MAC address of a station on the link indicated by the first field, and a MAC address of a peer station on the link indicated by the first field, or a combination of a TWT flow identifier, a MAC address of a multilink device to which a transmitting end of the communication frame belongs, a MAC address of a multilink to which a receiving end of the communication frame belongs, and a link indicated by the first field; The TWT plan corresponds to any one of the following combinations, each of which includes a broadcast TWT identifier: a combination of a broadcast TWT identifier and a media access control MAC address of an access station on the link indicated by the first field, or a combination of a broadcast TWT identifier and a MAC address of a multi-link device to which an access station on the link indicated by the first field belongs, and the link indicated by the first field.

[0036] According to a fifth aspect, an embodiment of the present application provides a communication device configured to perform the method of the first aspect or any one of the possible implementations of the first aspect, wherein the communication device includes a unit for performing the method of the first aspect or any one of the possible implementations of the first aspect.

[0037] According to a sixth aspect, an embodiment of the present application provides a communication device configured to perform the method of the second aspect or any one of the possible implementations of the second aspect, wherein the communication device includes a unit for performing the method of the second aspect or any one of the possible implementations of the second aspect.

[0038] According to a seventh aspect, an embodiment of the present application provides a communication device configured to perform the method of the third aspect or any one of the possible implementations of the third aspect, wherein the communication device includes a unit for performing the method of the third aspect or any one of the possible implementations of the third aspect.

[0039] According to an eighth aspect, an embodiment of the present application provides a communication device configured to perform the method of the fourth aspect or any one of the possible implementations of the fourth aspect, wherein the communication device includes a unit for performing the method of the fourth aspect or any one of the possible implementations of the fourth aspect.

[0040] In the third, fourth, fifth, or sixth aspects, the communication device may include a transceiver unit and a processing unit, respectively. For specific descriptions of the transceiver unit and the processing unit, please refer to the device embodiments shown below.

[0041] According to a ninth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to perform the method of the first aspect or any one of the possible implementations of the first aspect. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method of the first aspect or any one of the possible implementations of the first aspect is performed.

[0042] In a possible implementation, the memory is located external to the communication device.

[0043] In a possible implementation, the memory is located within the communication device.

[0044] In this embodiment of the present application, the processor and memory may alternatively be integrated into one device, in other words, the processor and memory may alternatively be integrated together.

[0045] In a possible implementation, the communication device further includes a transceiver, the transceiver configured to receive a signal or to transmit a signal.

[0046] According to a tenth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to perform the method of the second aspect or any one of the possible implementations of the second aspect. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method of the second aspect or any one of the possible implementations of the second aspect is performed.

[0047] In a possible implementation, the memory is located external to the communication device.

[0048] In a possible implementation, the memory is located within the communication device.

[0049] In this embodiment of the present application, the processor and memory may alternatively be integrated into one device, in other words, the processor and memory may alternatively be integrated together.

[0050] In a possible implementation, the communication device further includes a transceiver, the transceiver configured to receive a signal or to transmit a signal.

[0051] According to an eleventh aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to perform the method of the third aspect or any one of the possible implementations of the third aspect. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method of the third aspect or any one of the possible implementations of the third aspect is performed.

[0052] In a possible implementation, the memory is located external to the communication device.

[0053] In a possible implementation, the memory is located within the communication device.

[0054] In this embodiment of the present application, the processor and memory may alternatively be integrated into one device, in other words, the processor and memory may alternatively be integrated together.

[0055] In a possible implementation, the communication device further includes a transceiver, the transceiver configured to receive a signal or to transmit a signal.

[0056] According to a twelfth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to perform the method of the fourth aspect or any one of the possible implementations of the fourth aspect. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method of the fourth aspect or any one of the possible implementations of the fourth aspect is performed.

[0057] In a possible implementation, the memory is located external to the communication device.

[0058] In a possible implementation, the memory is located within the communication device.

[0059] In this embodiment of the present application, the processor and memory may alternatively be integrated into one device, in other words, the processor and memory may alternatively be integrated together.

[0060] In a possible implementation, the communication device further includes a transceiver, the transceiver configured to receive a signal or to transmit a signal.

[0061] According to a thirteenth aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface. The logic circuit is coupled to the interface. The logic circuit is configured to generate a communication frame. The interface outputs the communication frame.

[0062] According to a fourteenth aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface. The logic circuit is coupled to the interface. The interface inputs a communication frame. The logic circuit is configured to release a TWT agreement based on the communication frame.

[0063] For specific descriptions of the thirteenth and fourteenth aspects, please refer to the method embodiments set forth below.

[0064] According to a fifteenth aspect, an embodiment of the present application provides a computer-readable recording medium configured to store a computer program, which, when run on a computer, performs the method of the first aspect or any one of the possible implementations of the first aspect.

[0065] According to a sixteenth aspect, an embodiment of the present application provides a computer-readable recording medium configured to store a computer program, which, when run on a computer, performs the method of the second aspect or any one of the possible implementations of the second aspect.

[0066] According to a seventeenth aspect, an embodiment of the present application provides a computer-readable recording medium configured to store a computer program, which, when run on a computer, performs the method of the third aspect or any one of the possible implementations of the third aspect.

[0067] According to an eighteenth aspect, an embodiment of the present application provides a computer-readable recording medium configured to store a computer program, which, when run on a computer, performs the method of the fourth aspect or any one of the possible implementations of the fourth aspect.

[0068] According to a nineteenth aspect, an embodiment of the present application provides a computer program product, the computer program product including a computer program that, when run on a computer, performs the method of the first aspect or any one of the possible implementations of the first aspect.

[0069] According to a twentieth aspect, an embodiment of the present application provides a computer program product, the computer program product including a computer program that, when run on a computer, performs the method of the second aspect or any one of the possible implementations of the second aspect.

[0070] According to a twenty-first aspect, an embodiment of the present application provides a computer program product, the computer program product including a computer program that, when run on a computer, performs the method of the third aspect or any one of the possible implementations of the third aspect.

[0071] According to a twenty-second aspect, an embodiment of the present application provides a computer program product, the computer program product including a computer program that, when run on a computer, performs the method of the fourth aspect or any one of the possible implementations of the fourth aspect.

[0072] According to a twenty-third aspect, an embodiment of the present application provides a computer program, which, when run on a computer, performs the method of the first aspect or any one of the possible implementations of the first aspect.

[0073] According to a twenty-fourth aspect, an embodiment of the present application provides a computer program, which, when run on a computer, performs the method of the second aspect or any one of the possible implementations of the second aspect.

[0074] According to a twenty-fifth aspect, an embodiment of the present application provides a computer program, which, when run on a computer, performs the method of the third aspect or any one of the possible implementations of the third aspect.

[0075] According to a twenty-sixth aspect, an embodiment of the present application provides a computer program, which, when run on a computer, performs the method of the fourth aspect or any one of the possible implementations of the fourth aspect.

[0076] According to a 27th aspect, an embodiment of the present application provides a wireless communication system. The wireless communication system includes a transmitting end and a receiving end. The transmitting end is configured to perform the method of the first aspect or any one of possible implementations of the first aspect. The receiving end is configured to perform the method of the second aspect or any one of possible implementations of the second aspect.

[0077] According to a twenty-eighth aspect, an embodiment of the present application provides a wireless communication system. The wireless communication system includes a transmitting end and a receiving end. The transmitting end is configured to perform the method of the third aspect or any one of possible implementations of the third aspect. The receiving end is configured to perform the method of the fourth aspect or any one of possible implementations of the fourth aspect. [Brief explanation of the drawings]

[0078] [Figure 1a] 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application;

[0079] [Figure 1b] FIG. 2 is a schematic diagram of the architecture of another communication system according to an embodiment of the present application;

[0080] [Figure 2a] 2 is a schematic diagram of a connection scheme between a multi-link AP and a multi-link STA according to an embodiment of the present application;

[0081] [Figure 2b] 2 is a schematic diagram of a connection scheme between a multi-link AP and a multi-link STA according to an embodiment of the present application;

[0082] [Figure 2c]1 is a schematic diagram of an antenna of a multi-link device according to an embodiment of the present application;

[0083] [Figure 3a] 1 is a schematic diagram of a communication scenario according to an embodiment of the present application;

[0084] [Figure 3b] 1 is a schematic diagram of a communication scenario according to an embodiment of the present application;

[0085] [Figure 4] 1 is a schematic flowchart of a multi-link communication method according to an embodiment of the present application;

[0086] [Figure 5a] 1 is a schematic flowchart of a method for setting up a TWT agreement according to an embodiment of the present application;

[0087] [Figure 5b] FIG. 1 is a schematic diagram of a scenario for setting up a TWT agreement according to an embodiment of the present application.

[0088] [Figure 6a] 1 is a schematic diagram of the structure of a TWT element whose negotiation type is an individual TWT type according to an embodiment of the present application;

[0089] [Figure 6b] 1 is a schematic diagram of the structure of a TWT element whose negotiation type is a broadcast TWT type according to an embodiment of the present application;

[0090] [Figure 7a] 1 is a schematic diagram of a structure of a communication frame according to an embodiment of the present application;

[0091] [Figure 7b] 1 is a schematic diagram of a structure of a communication frame according to an embodiment of the present application;

[0092] [Figure 7c] 1 is a schematic diagram of a structure of a communication frame according to an embodiment of the present application;

[0093] [Figure 7d] 1 is a schematic diagram of a structure of a communication frame according to an embodiment of the present application;

[0094] [Figure 8a] 1 is a schematic diagram of a structure of a communication frame according to an embodiment of the present application;

[0095] [Figure 8b] 1 is a schematic diagram of a structure of a communication frame according to an embodiment of the present application;

[0096] [Figure 9] FIG. 9 is a schematic diagram of the structure of a communication device according to an embodiment of the present application.

[0097] [Figure 10] FIG. 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present application;

[0098] [Figure 11] 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0099] To make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described below with reference to the accompanying drawings.

[0100] Terms such as "first," "second," and the like in the specification, claims, and accompanying drawings of this application are used merely to distinguish between different objects and are not used to describe a particular order. In addition, terms such as "comprise" and "have," as well as any other variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the enumerated steps or units, but may optionally further include other unenumerated steps or units, or may optionally further include other inherent steps or units of the process, method, system, product, or device.

[0101] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described with reference to an embodiment may be included in at least one embodiment of the present application. Phrases appearing in various places in this specification do not necessarily refer to the same embodiment, nor are they exclusive, independent, or alternative embodiments of other embodiments. Those skilled in the art will understand, both explicitly and implicitly, that the embodiments described herein can be combined with other embodiments.

[0102] In this application, "at least one item" means one or more, "multiple" means two or more, "at least two items" means two, three, or more, and "and / or" is used to describe an association relationship between related objects and indicates that three relationships may exist. For example, "A and / or B" may indicate three cases: only A is present, only B is present, and both A and B are present, where A and B may be singular or plural. "Or" indicates that two relationships may exist. For example, if only A is present and only B is present, or if A and B are not mutually exclusive, three relationships may exist. For example, only A is present, only B is present, and both A and B are present. The character " / " typically indicates an "or" relationship between related objects. "At least one item of the following" or similar expressions means any combination of these items. For example, at least one item (part) of a, b, and c can indicate a, b, c, a and b, a and c, b and c, or a, b, and c.

[0103] The technical solutions provided in the embodiments of the present application may be applied to WLAN systems, such as Wi-Fi. The methods provided in the embodiments of the present application may be applied to IEEE 802.11 series protocols, such as 802.11a / b / g protocol, 802.11n protocol, 802.22ac protocol, 802.22ax protocol, 802.22be protocol, or next-generation protocols. Details will not be listed one by one in this specification. The technical solutions provided in the embodiments of the present application may further be applied to wireless personal area networks (WPANs) based on UWB technology. The methods provided in the embodiments of the present application may be applied to IEEE 802.15 series protocols, such as 802.15.4a protocol, 802.15.4z protocol, 802.15.4ab protocol, or next-generation UWB WPAN protocols. Details will not be listed one by one in this specification. The technical solutions provided in the embodiments of the present application may be further applied to other communication systems, for example, internet of things (IoT) systems, vehicle-to-X (V2X) systems, and narrow band internet of things (NB-IoT) systems, may be further applied to devices in the internet of things (IoT), internet of things nodes, sensors, etc. in the internet of vehicles, smart cameras, smart remote controllers, and smart water meters in smart homes, sensors in smart cities, etc., or may be further applied to long term evolution (LTE) systems, fifth generation (5G) communication systems, new communication systems emerging in future communication developments, etc.

[0104] The embodiments of the present application are primarily described using WLANs, particularly networks that comply with the IEEE 802.11 series of standards, as examples. For example, a system that supports Wi-Fi 7 and may also be referred to as an extreme high throughput (EHT) system, or a system that supports Wi-Fi 8 and may also be referred to as an ultra high reliability (UHR) system or an ultra high reliability and throughput (UHRT) system. Those skilled in the art will readily understand that various aspects of the embodiments of the present application can be extended to other networks that use various standards or protocols, such as Bluetooth®, high-performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, primarily used in Europe), and wide area networks (WANs), or other networks that are known or developed in the future. Therefore, various aspects provided in the embodiments of the present application are applicable to any suitable wireless network, regardless of the coverage area and wireless access protocol used.

[0105] The method provided in the embodiments of the present application may be implemented by a communication device in a wireless communication system, for example, the communication device may be an access point (AP) or a station (STA).

[0106] An access point is a device with wireless communication capabilities, supports communication or sensing according to a WLAN protocol, and has the function of communicating with or sensing other devices (e.g., stations or other access points) in a WLAN network. It is clear that an access point may also have the function of communicating with or sensing other devices. Alternatively, an access point corresponds to a bridge connecting a wired network and a wireless network. The main function of an access point is to connect various wireless network clients together and then connect the wireless network to Ethernet. In a WLAN system, an access point may be referred to as an access point station (AP STA). A device with wireless communication capabilities may be an entire device, or a chip, processing system, etc. installed in the entire device. A device installed with a chip or processing system may implement the methods and functions in the embodiments of the present application under the control of the chip or processing system. An AP in the embodiments of the present application is a device that provides services to STAs and may support the 802.11 series of protocols, subsequent protocols, etc. For example, an access point may be an access point for terminals (e.g., mobile phones) to access a wired (or wireless) network and is mainly located in homes, buildings, and parks. A typical coverage radius is from several tens of meters to several hundred meters. It is apparent that the access point may alternatively be located outdoors. In other examples, the AP may be a communication entity, such as a communication server, a router, a switch, or a bridge, or the AP may include various forms of macro base stations, micro base stations, relay stations, etc. It is apparent that the AP may alternatively be a chip or processing system within these devices in various forms for implementing the methods and functions in the embodiments of the present application.

[0107] A station is a device with wireless communication capabilities, supports communication or sensing according to a WLAN protocol, and has the ability to communicate with or sense other stations or access points in a WLAN network. In a WLAN system, a station may be referred to as a non-access point station (non-AP STA). For example, a STA is any user communication device that allows a user to communicate with an AP or sense an AP and further communicate with a WLAN. A device with wireless communication capabilities may be an entire device, or a chip, processing system, etc. installed in the entire device. A device with a chip or processing system installed may implement the methods and functions in the embodiments of the present application under the control of the chip or processing system. For example, a station may be a wireless communication chip, a wireless sensor, or a wireless communication terminal, and may also be referred to as a user. In other examples, a station may be 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 supporting Wi-Fi communication capabilities.

[0108] WLAN systems can provide high-speed, low-latency transmission. As WLAN application scenarios continue to evolve, WLAN systems are being applied to more scenarios and industries, such as the Internet of Things industry, the Internet of Vehicles industry, banking, corporate offices, stadium exhibition halls, concert halls, hotel rooms, dormitories, hospital rooms, classrooms, supermarkets, squares, streets, production plants, warehouses, etc. Of course, a device (e.g., an access point or station) supporting WLAN communication or sensing may be a sensor node (e.g., a smart water meter, a smart electricity meter, or a smart air detection node) in a smart city, a smart device (e.g., a smart camera, a projector, a display screen, a television, a stereo, a refrigerator, or a washing machine) in a smart home, a node in the Internet of Things, an entertainment terminal (e.g., a wearable device such as an augmented reality (AR) or virtual reality (VR) device), a smart device (e.g., a printer, a projector, a speaker, or a stereo) in a smart office, an Internet of Vehicles device in the Internet of Vehicles, infrastructure in everyday life scenarios (e.g., a vending machine, a self-service navigation console, a self-service cashier, or a self-service ordering machine in a supermarket), a device in a large sports and music venue, etc. For example, the access point and the station may be a device used in the Internet of Vehicles, an Internet of Things node, a sensor in the Internet of Things, a smart camera, a smart remote controller, and a smart water or electricity meter in a smart home, a sensor in a smart city, etc., respectively. The specific forms of the STA and AP are not limited to the embodiments of the present application and are merely examples for the purposes of explanation in this specification.

[0109] For example, a communication system to which the method provided in the embodiments of the present application can be applied may include an access point and a station. For example, the embodiments of the present application can be applied to a scenario of communication or sensing between an AP and a STA, between APs, or between STAs in a WLAN. This is not limited to the embodiments of the present application. Optionally, an AP may communicate with or sense a single STA, or an AP may communicate with or sense multiple STAs simultaneously. Specifically, communication or sensing between an AP and multiple STAs can be further classified into downlink transmission in which an AP simultaneously sends signals to multiple STAs and uplink transmission in which multiple STAs send signals to an AP. WLAN communication protocols can be supported between an AP and a STA, between APs, or between STAs. The communication protocol can include IEEE 802.11 series protocols, for example, applicable to the 802.22be standard, and of course also applicable to standards later than the 802.22be standard.

[0110] FIG. 1a is a schematic diagram of an architecture of a communication system according to an embodiment of the present application. The communication system may include one or more APs and one or more STAs. FIG. 1a shows two access points, namely, AP 1 and AP 2, and three stations, namely, STA 1, STA 2, and STA 3. It can be understood that one or more APs may communicate with one or more STAs. Of course, an AP may communicate with an AP, and a STA may communicate with a STA. The method provided in the embodiment of the present application is applicable to, but not limited to, single-user uplink / downlink transmission, multi-user uplink / downlink transmission, vehicle-to-everything (V2X, where X may represent anything) communication, and device-to-device (D2D) communication. For example, V2X communications may include vehicle-to-vehicle (V2V) communications, vehicle-to-infrastructure (V2I) communications, vehicle-to-pedestrian (V2P) communications, vehicle-to-network (V2N) communications, etc.

[0111] In Fig. 1a, an example is used in which the STA is a mobile phone and the AP is a router, and it can be understood that this does not constitute a limitation on the types of APs and STAs in the embodiment of the present application. In addition, Fig. 1a shows only two APs and three STAs as an example. However, there may be more or fewer APs or STAs. This is not limited in the embodiment of the present application.

[0112] A multilink device includes one or more affiliated stations. An affiliated station is a logical station and may operate on one link, one frequency band, one channel, etc. An affiliated station may be an AP or a non-AP STA. For ease of explanation, in the embodiments of the present application, a multilink device whose affiliated station is an AP may be referred to as a multilink AP, a multilink AP device, or an AP multilink device (AP MLD). A multilink device whose affiliated station is a non-AP STA may be referred to as a multilink STA, a multilink STA device, or an STA multilink device (STA multilink device), or a multilink device whose affiliated station is a non-AP STA may be referred to as a multilink non-AP, a multilink non-AP device, a non-AP multilink device (non-AP MLD), etc. A multilink device (which may be a non-AP MLD or AP MLD in this specification) is a communication device having wireless communication capabilities. The communication apparatus may be an entire device, or may be a chip, a processing system, etc. installed in the entire device. A device with a chip or a processing system installed may perform the methods and functions in the embodiments of the present application under the control of the chip or the processing system.

[0113] The multi-link device MLD may perform wireless communication in accordance with an 802.11 series protocol, for example, in accordance with an Extremely High Throughput (EHT) protocol, or in accordance with an 802.22be-based or 802.22be-compatible protocol, thereby communicating with other devices, which may or may not be multi-link devices.

[0114] Each logical station can operate on one link, but multiple logical stations are allowed to operate on the same link. The link identifier described below represents one station operating on one link. In other words, if there are multiple logical stations on one link, multiple link identifiers are required to represent the logical stations. The link identifier described below may also represent a station operating on a link. When data transmission occurs between a multilink device and another multilink device, the multilink device and the other multilink device may first negotiate or communicate with each other regarding the correspondence between the link identifier and the link or the station on the link before communication, or the AP multilink device may indicate the correspondence between the link identifier and the link or the station on the link based on a broadcast management frame, e.g., a beacon frame. Therefore, during data transmission, the link identifier can be conveyed without transmitting a large amount of signaling to indicate the link or the station on the link. This reduces signaling overhead and improves transmission efficiency.

[0115] For the sake of explanation, the following uses an example in which one of the multilink devices is an AP multilink device and the other multilink device is a STA multilink device. In one example, a management frame, such as a multilink probe response frame, transmitted when an AP multilink device establishes a basic service set (BSS) carries one or more link elements, and the link information field included in the multilink element can be used to establish a correspondence between the link identifier and the station operating on the corresponding link. The link identifier identifies a combination of the link's operating class, channel number, and the AP's BSSID (BSS identifier) ​​(or the AP's MAC address).

[0116] 1b is a schematic diagram of the architecture of another communication system according to an embodiment of the present application. As shown in FIG. 1b, the AP MLD includes AP 1, AP 2, ..., and AP n, and the non-AP MLD includes STA 1, STA 2, ..., and STAn. The AP MLD and the non-AP MLD may communicate in parallel over Link 1, Link 2, ..., and Link n. STA 1 in the non-AP MLD establishes an association relationship with AP 1 in the AP MLD. STA 2 in the non-AP MLD establishes an association relationship with AP 2 in the AP MLD. STA n in the non-AP MLD establishes an association relationship with AP n in the AP MLD. Thus, one or more STAs in the non-AP MLD and one or more APs in the AP MLD can communicate after establishing their association relationships. The frequency bands in which multi-link devices (including AP MLD and non-AP MLD) operate may include, but are not limited to, sub-1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high frequency 60 GHz.

[0117] 2a and 2b are schematic diagrams of a connection between a multi-link AP and a multi-link STA according to an embodiment of the present application. The 802.11 standard focuses on the 802.11 physical layer (PHY) and medium access control (MAC) layer of a multi-link device. Therefore, Fig. 2a and Fig. 2b only show the PHY layer and the MAC layer as an example.

[0118] As shown in FIGS. 2a and 2b, a multilink device (e.g., a multilink AP and a multilink STA) may include a physical layer (PHY) processing circuit (PHY#1, PHY#2, and PHY#n shown in FIG. 2a) and a medium access control (MAC) layer processing circuit. The physical layer processing circuit may be configured to process physical layer signals, and the MAC layer processing circuit may be configured to process MAC layer signals. The MAC layer may be further divided into a high-MAC layer (e.g., the high-MAC shown in FIG. 2a and the high-MAC#1 to high-MAC#n shown in FIG. 2b) and multiple low-MAC layers (e.g., the low-MAC#1, low-MAC#2 to low-MAC#n shown in FIGS. 2a and 2b, respectively). As shown in FIG. 2a, multiple APs included in a multilink AP are independent of each other in the lower MAC layer and PHY, but share the upper MAC layer. Multiple STAs included in a multilink STA are independent of each other in the lower MAC layer and PHY, but share the upper MAC layer. The upper MAC layer is separately connected to multiple lower MAC layers; that is, the upper MAC layer is shared by multiple links. As shown in Figure 2b, multiple APs included in a multi-link AP are independent of each other in the lower MAC layer and PHY, and also independent of each other in the upper MAC layer. Multiple STAs in a multi-link STA device are independent of each other in the lower MAC layer and PHY, and also independent of each other in the upper MAC layer. The upper MAC layer mainly completes operations such as assigning sequence numbers (SN) and packet numbers (PN) for MAC service data units (MSDUs), encryption, and decryption. Each lower MAC layer mainly completes operations such as assembling MAC protocol data units (MPDUs) on each link, channel access, and packet transmission and reception acknowledgment.

[0119] In FIG. 2a, the PHY#1 layer, lower MAC#1 layer, and upper MAC layer in the multi-link AP may be considered to be AP#1, the PHY#2 layer, lower MAC#2 layer, and upper MAC layer may be considered to be AP#2, ..., the PHY#n layer, lower MAC#n layer, and upper MAC layer may be considered to be AP#n. That is, it can be understood that the multi-link AP includes n AP entities. For a multi-link STA, the situation is similar. Specifically, the upper MAC layer in the multi-link STA is also shared by multiple links. The PHY#1 layer, lower MAC#1 layer, and upper MAC layer are considered to be STA#1, the PHY#2 layer, lower MAC#2 layer, and upper MAC layer are considered to be STA#2, ..., the PHY#n layer, lower MAC#n layer, and upper MAC layer are considered to be STA#n. That is, it can be understood that the multi-link STA includes n STA entities. As shown in Figure 2a, PHY #1 of AP #1 in the multilink AP is connected to PHY #1 of STA #1 in the multilink STA, so that AP #1 in the multilink AP and STA #1 in the multilink STA communicate with each other over a link (e.g., link #1 shown in Figure 2a). PHY #2 of AP #2 in the multilink AP is connected to PHY #2 of STA #2 in the multilink STA, so that AP #2 in the multilink AP and STA #2 in the multilink STA communicate with each other over a link (e.g., link #2 shown in Figure 2a). PHY #n of AP #n in the multilink AP is connected to PHY #n of STA #n in the multilink STA, so that AP #n in the multilink AP and STA #n in the multilink STA communicate with each other over a link (e.g., link #n shown in Figure 2a). For an explanation of Figure 2b, please refer to Figure 2a. The details will not be described again in this specification.

[0120] For example, the upper MAC layer or the lower MAC layer may be implemented by one processor in the chip system of the multilink device, or by different processing modules in the chip system. For example, the multilink device in the embodiment of the present application may be a single-antenna device or a multi-antenna device. For example, the device may have more than two antennas. The number of antennas included in the multilink device is not limited in the embodiment of the present application. Figure 2c is a schematic diagram of an antenna of a multilink device according to the present embodiment of the present application. Figure 2c uses an example in which the AP multilink device is a multi-antenna device and the STA multilink device is a single-antenna device. This should not be interpreted as a limitation on the present embodiment of the present application. In the present embodiment of the present application, the multilink device may allow services of the same access type to be transmitted on different links, or even allow the same data packet to be transmitted on different links. Alternatively, the multilink device may not allow services of the same access type to be transmitted on different links, but may allow services of different access types to be transmitted on different links. This is not limited in the embodiment of the present application.

[0121] The frequency bands in which a multi-link device operates may include, but are not limited to, sub-1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high frequency 60 GHz. Figures 3a and 3b are two schematic diagrams of communication between a multi-link device and other devices in a wireless local area network via multiple links.

[0122] 3a illustrates a scenario in which AP multilink device 101 communicates with STA multilink device 102. AP multilink device 101 includes affiliated AP 101-1 and affiliated AP 101-2, STA multilink device 102 includes affiliated STA 102-1 and affiliated STA 102-2, and AP multilink device 101 communicates with STA multilink device 102 in parallel over link 1 and link 2.

[0123] For example, Figure 3b illustrates a scenario in which AP MLD 101 communicates with non-AP MLD 102, non-AP MLD 103, and STA 104. AP MLD 101 includes affiliated APs 101-1 through 101-3. Non-AP MLD 102 includes affiliated STAs 102-1, 102-2, and 102-3. Non-AP MLD 103 includes affiliated STAs 103-1 and 103-2. STA 104 is a single-link device and includes STA 104-1. AP MLD 101 may separately communicate with non-AP MLD 102 on Link 1, Link 2, and Link 3, with non-AP MLD 103 on Link 2 and Link 3, and with STA 104 on Link 1. In one example, STA 104 operates in the 2.4 GHz frequency band, in non-AP MLD 103, STA 103-1 operates in the 5 GHz frequency band and STA 103-2 operates in the 6 GHz frequency band, and in non-AP MLD 102, STA 102-1 operates in the 2.4 GHz frequency band, STA 102-2 operates in the 5 GHz frequency band, and STA 102-3 operates in the 6 GHz frequency band. Uplink or downlink data may be transmitted on link 1 between AP 101-1, operating in the 2.4 GHz frequency band and in AP MLD 101, and STA 104 and STA 102-1, operating in non-AP MLD 102. Uplink or downlink data may be transmitted between AP 101-2, operating in the 5 GHz frequency band and in AP MLD 101, and STA 103-1, operating in the 5 GHz frequency band and in non-AP MLD 102 on link 2, and uplink or downlink data may further be transmitted between AP 101-2 and STA 102-2, operating in the 5 GHz frequency band and in non-AP MLD 103 on link 2.Uplink or downlink data may be transmitted between AP 101-3, operating in the 6 GHz frequency band and within AP MLD 101, and STA 102-3, operating in the 6 GHz frequency band and within non-AP MLD 102 on link 3, and uplink or downlink data may further be transmitted between AP 101-3 and STA 103-2 in the non-AP MLD on link 3.

[0124] Note that FIG. 3a only shows that the AP multi-link device supports two frequency bands, and FIG. 3b only shows an example in which the AP MLD 101 supports three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), each frequency band corresponds to one link, and the AP MLD 101 may operate on one or more links among link 1, link 2, or link 3. On the AP side or STA side, a link in this specification may be understood as a station operating on a link. In practical applications, the AP MLD and non-AP MLD may further support more or fewer frequency bands, i.e., the AP MLD and non-AP MLD may operate on more or fewer links. This is not limited in the embodiments of the present application.

[0125] It should be noted that Figures 3a and 3b are merely simple schematic diagrams, and do not constitute any limitation to the protection scope of the embodiments of the present application.

[0126] In the current protocol, elements related to a TWT agreement include a TWT flow identifier, a MAC address of the TWT requesting station, and a MAC address of the TWT responding station. A TWT requesting station is a station that sends a TWT element to request the setup of a TWT, and the TWT Request field in the Request Type field of the TWT element is set to 1. A TWT responding station is a station that sends a TWT element to respond to the setup of a TWT, and the TWT Request field in the Request Type field of the TWT element is set to 0. A TWT agreement can be terminated based on the above elements. For example, in a currently used method for terminating a TWT agreement, both communication parties to terminate the TWT agreement must be the same as both communication parties to set up the TWT agreement. That is, the MAC addresses of both communication parties to terminate the TWT agreement include the MAC address of the TWT requesting station and the MAC address of the TWT responding station. According to this method, in a single-link scenario, when the TWT agreement set up by both communication parties on one link needs to be released, the single-link transmitting end can send a TWT teardown frame to the single-link receiving end so that the TWT agreement can be directly released. When the above method is applied to a single-link scenario, the method is convenient, simple, and feasible. For a specific description of the TWT agreement, it can be understood that reference is made to the relevant description in Revme draft 2.0 of the 802.11 standard protocol. Details will not be described in this embodiment of the present application.

[0127] However, when the above-described method is applied to a multi-link scenario, multiple links are usually associated between multi-link devices. A TWT agreement on one link may be established by a station corresponding to another link (e.g., when one link in this specification is in a sleep or busy state, another link may establish a TWT agreement for the link), or TWT agreements on some links may be established by a station corresponding to a link other than some links between multi-link devices. Therefore, if the TWT agreement can still be terminated by using the above-described method for terminating a TWT agreement, the flexibility of terminating the TWT agreement is not high. For example, the links established between two multi-link devices include link 1 and link 2, and link 1 establishes a TWT agreement on link 2. In other words, the TWT request station and the TWT response station of the TWT agreement on link 2 are the stations corresponding to link 1. If a station on link 2 sends a TWT release frame, the receiving end of the TWT release frame will believe that the MAC address of the TWT requesting station is the MAC address of the sending station on link 2, not the MAC address of the station on link 1 that originally set up the TWT agreement. As a result, the station on link 2 cannot release the TWT agreement set up by link 1.

[0128] In view of this, the embodiments of the present application provide a multi-link communication method and apparatus for effectively improving the flexibility of releasing TWT agreements.

[0129] FIG. 4 is a schematic flowchart of a multilink communication method according to an embodiment of the present application. The method may be applied to the system shown in FIG. 1a and FIG. 1b, or the method may be applied to the multilink device shown in FIG. 3a and FIG. 3b. For ease of explanation, the method provided in the embodiment of the present application will be described below by using a transmitting end and a receiving end as examples. The transmitting end may be understood as an STA that transmits a communication frame, and the receiving end may be understood as an STA that receives a communication frame. Alternatively, the transmitting end may be understood as an STA in a multilink device configured to transmit a communication frame, and the receiving end may be understood as an STA in a multilink device configured to receive a communication frame. In some embodiments of the present application, no distinction is made between a non-AP STA and an AP STA, but it can be understood that the term STA is used to describe the method provided in the embodiment of the present application. In the embodiment of the present application, the multilink devices for both communication parties may both be AP MLDs, or both be STA MLDs, or one multilink device may be an AP MLD and the other multilink device may be an STA MLD. Details will not be listed one by one in this specification. It can be understood that in the embodiments of the present application, the method provided in the embodiments of the present application is described by using two sides, namely, a transmitting end and a receiving end. However, other devices may be involved in the process of information transmission between the transmitting end and the receiving end. For example, information between the transmitting end and the receiving end is transferred by using a transfer device. Therefore, in the embodiments of the present application, mutual information transfer can be implemented by technical means that can be completed by those skilled in the art, and devices other than the transmitting end and the receiving end are not limited in the embodiments of the present application.

[0130] Before describing the method shown in FIG. 4, a method for setting up a TWT agreement provided in one embodiment of the present application will be described in detail below. Of course, the following method for setting up a TWT agreement is merely an example and should not be construed as a limitation on the embodiment of the present application. In actual applications, there may be other methods for setting up a TWT agreement. The details will not be listed one by one.

[0131] 5a is a schematic flowchart of a method for setting up a TWT agreement according to an embodiment of the present application. The method is illustrated by using an example in which a non-AP MLD initiates a TWT setup request. This should not be understood as a limitation on the embodiment of the present application. As shown in FIG. 5a, the method includes the following steps:

[0132] 501: A STA in a non-AP MLD transmits a TWT setup request frame, and in response, an AP in an AP MLD receives a TWT setup request frame.

[0133] It can be understood that the TWT setup request frame and the TWT setup response frame shown in this embodiment of the present application are merely examples. For example, the TWT setup request frame and the TWT setup response frame may be collectively referred to as a TWT setup frame, with the difference being that the TWT request bit in the TWT element in the TWT setup frame is set to "1" or "0". Alternatively, the TWT setup request frame and the TWT setup response frame may be collectively referred to as a management frame used to set up a TWT agreement, etc. Details will not be listed one by one.

[0134] Optionally, after receiving the TWT setup request frame, the AP in the AP MLD may send an acknowledgement frame to the STA in the non-AP MLD, and the acknowledgement frame is used to confirm the TWT setup request frame.

[0135] It can be understood that step 501 is an optional step. Alternatively, sending an acknowledgement frame used to acknowledge the TWT setup request frame is also an optional step.

[0136] 502: The AP in the AP MLD transmits a TWT setup response frame, and in response, the STA in the non-AP MLD receives a TWT setup response frame.

[0137] Optionally, after receiving the TWT setup response frame, the STA in the non-AP MLD may send an acknowledgement frame to the AP in the AP MLD, and the acknowledgement frame is used to confirm the TWT setup response frame.

[0138] The TWT setup request frame and the TWT setup response frame will be described in detail below.

[0139] The TWT request frame includes a TWT element, and the TWT setup response frame includes a TWT element. Other elements in the TWT request frame and the TWT response frame are not shown one by one in the embodiments of the present application. The TWT element includes at least one of the following fields: an element number field, a length field, a control field, and a TWT parameter information field. For example, the control field includes at least one of the following fields: a null data packet paging (NDP paging) indication field, a responder power management (PM) mode field, a negotiation type field, a TWT information frame disabled field, a wake duration unit field, a link identifier bitmap present field (abbreviated as bitmap present field), and a reserved field.

[0140] The negotiation type included in the control field includes an individual TWT type and a broadcast TWT type. Figure 6a is a schematic diagram of the structure of a TWT element when the negotiation type is the individual TWT type according to this embodiment of the present application. As shown in Figure 6a, when the negotiation type indicates the individual TWT type, the TWT parameter information field includes at least one of a request type field, a target wake time field, a TWT group assignment field, a nominal minimum TWT wake duration field, a TWT wake interval mantissa field, a TWT channel field, a null data packet paging (NDP paging) field, and a link ID bitmap field. Figure 6b is a schematic diagram of the structure of a TWT element when the negotiation type is the broadcast TWT type according to this embodiment of the present application. As shown in FIG. 6b, when the negotiation type indicates a broadcast TWT type, the TWT parameter information field includes at least one of a request type field, a target wake time field (determined by a link-based timing synchronization function (TSF)), a nominal minimum TWT wake duration field, a TWT wake interval mantissa field, a broadcast TWT channel field, and a link identifier bitmap field.

[0141] For example, the request type field in the TWT parameter information field includes at least one of a TWT request field, a TWT setup command field, a reserved field, an implicit field, a flow type field, and a TWT flow identifier field, a TWT wake interval exponent field, and a TWT protection field.

[0142] The request type in the TWT parameter information field may include several parameters related to the TWT setup request and the TWT setup response. If the value of the TWT request field in the TWT element is 1, this indicates that the frame corresponding to the TWT element is a TWT setup request frame. If the value of the TWT request field in the TWT element is 0, this indicates that the frame corresponding to the TWT element is a TWT setup response frame. For example, in a TWT negotiation process, the TWT setup command field in the TWT element in the TWT setup request frame may be used to carry the value of "proposed TWT" (in this case, the value is 1). The TWT setup command field in the TWT element in the TWT setup response frame may be used to carry the value of "accepted TWT" (in this case, the value is 4). In this case, the TWT agreement is set up successfully.

[0143] It can be understood that the description of the aforementioned fields refers to relevant standards, protocols, etc. The details will not be described one by one in this embodiment of the present application.

[0144] The TWT flow identifier field, the link identifier bitmap present field, and the link identifier bitmap field in the embodiment of the present application are described in detail below.

[0145] The TWT flow identifier field contains a TWT flow identifier for identifying a request or for providing TWT information.

[0146] The control field in the TWT element provided in this embodiment of the present application includes a link identifier bitmap presence field, and the TWT parameter information field includes a link identifier bitmap field to negotiate TWT for another link on one link. For example, the link identifier bitmap presence field may indicate whether the link identifier bitmap field is present (included) in the TWT parameter information field. The length of the link identifier bitmap field may be determined based on the number of links established between the AP MLD and the non-AP MLD. This method is very flexible. Alternatively, the length of the link identifier bitmap field may be determined based on the maximum number of links allowed to be established between the AP MLD and the non-AP MLD. This method is simple. Alternatively, the length of the link identifier bitmap field may be constant, for example, 16 bits or 8 bits. For ease of explanation, the following uses an example in which the length of the link identifier bitmap field is 16 bits for illustration. Of course, the maximum number shown herein is merely an example. As standards evolve, the maximum number of links allowed to be established between multilink devices may change later. If the maximum number changes, the length of the link identifier bitmap field shown in this embodiment of the present application may also change. It can be understood that the name of the link identifier bitmap field is not limited in the embodiment of the present application. For example, the link identifier bitmap field may alternatively be referred to as a bitmap field, a link bitmap field, etc. Details will not be listed one by one.

[0147] Each bit in the link identifier bitmap field has a one-to-one correspondence with a link, and the value of each bit may indicate whether a TWT agreement should be set up on the corresponding link. For example, the content carried in the link identifier bitmap field is 0010 1110 0000 0001, which corresponds sequentially to links 1 to 16. A value of 1 for each bit indicates that a TWT agreement should be set up on the corresponding link. A value of 0 for each bit indicates that a TWT agreement should not be set up on the corresponding link. Therefore, the link identifier bitmap field indicates that TWT agreements can be set up on links 3, 5, 6, 7, and 16, respectively. When the values ​​of the link identifier bitmap field in the TWT setup request frame and the link identifier bitmap field in the TWT setup response frame are the same, both communicating parties can set up TWT agreements on links 3, 5, 6, 7, and 16 based on the TWT setup request frame and the TWT setup response frame shown in FIG. 5a. The flow identifier of the TWT agreement is the flow identifier indicated by the TWT flow identifier field in the request type field, and the flow identifiers of the TWT agreements set up on link 3, link 5, link 6, link 7, and link 16 are the same. It can be understood that the flow identifier of the TWT agreement set up on link 3 is different from the flow identifier of the TWT agreement set up on link 3. Similarly, the flow identifier of the TWT agreement set up on link 5 is different from the flow identifier of the TWT agreement set up on link 5. The rest can be deduced by analogy.Optionally, the TWT flow identifier of each TWT agreement needs to be unique among multiple TWT agreements set up by an MLD requesting TWT setup and an MLD responding to the TWT setup, or among multiple TWT agreements set up between an AP and a STA on the corresponding link. Therefore, this can effectively ensure that the TWT agreement specified in the TWT release frame is unique, and release errors are avoided. Generally, one bit in the link identifier bitmap field may be set to 1. In other words, on a link corresponding to the link identifier bitmap field, the value of a bit corresponding to one link may generally be 1. For example, this indicates that a TWT agreement on the corresponding link has been set up. Of course, multiple bits in the link identifier bitmap field may also be set to 1. This is not limited to the embodiments of the present application.

[0148] It may be understood that the above-mentioned link identifier bitmap is merely an example. For example, in actual applications, the above-mentioned link identifier bitmap presence field may alternatively be the link identifier presence field or the link identifier presence field. The above-mentioned link identifier bitmap field may alternatively be the link identifier field. The link identifier presence field may indicate that the link identifier bitmap field is present (contained) in the TWT parameter information field. The link identifier field may identify one or more links. Therefore, both communicating parties may set up a TWT agreement on one or more links indicated by the link identifier field based on the link identifier field. For example, both communicating parties may set up a TWT agreement on one or more links indicated by the link identifier field based on the content indicated in the TWT element. For example, a maximum of 16 links are allowed to be established between MLDs, and the length of the link identifier field is 4 bits. If the content carried in the link identifier field is 0001, this indicates that a TWT agreement needs to be set up on link 1. In another example, if the length of the link identifier field is 8 bits and the carried content is 0001 0011, this indicates that a TWT agreement needs to be set up on link 1 and link 3. It can be understood that the length of the link identifier field or the correspondence between the value and meaning of the link identifier field is not limited in the embodiments of the present application.

[0149] To further understand the method for establishing a TWT agreement provided in this embodiment of the present application, an example is used below for illustration.

[0150] 5b is a schematic diagram of a scenario for setting up a TWT agreement according to this embodiment of the present application. As shown in FIG. 5b, a TWT agreement needs to be set up between an AP MLD and a non-AP MLD through negotiation. For example, the AP MLD includes three affiliated AP stations, namely, AP 1, AP 2, and AP 3, operating at 2.4 GHz, 5 GHz, and 6 GHz, respectively. The non-AP MLD includes three affiliated non-AP stations, namely, STA 1, STA 2, and STA 3. Three links, namely, Link 1 between AP 1 and STA 1, Link 2 between AP 2 and STA 2, and Link 3 between AP 3 and STA 3, are associated between the AP MLD and the non-AP MLD.

[0151] For example, the AP MLD and the non-AP MLD may transmit management frames on link 1. For example, STA 1 sends a TWT setup request frame to AP 1. In response, AP 1 receives the TWT setup request frame. AP 1 sends a TWT setup response frame to STA 1. In response, STA 1 receives the TWT setup response frame. For an explanation of the TWT setup request frame and the TWT setup response frame, please refer to the above description. The details will not be described again herein. For example, the link identifier bitmap included in the TWT element in the TWT setup request frame indicates that a TWT agreement needs to be set up for link 2. In this case, the AP MLD and the non-AP MLD may set up a TWT agreement for link 2. Furthermore, all related parameters of the TWT agreement are determined based on the TWT element. The target wake time of the TWT element is based on the timing synchronization function (TSF) of the link indicated by the link identifier bitmap, which is based on the TSF of link 2 in this specification.

[0152] The above-described methods for setting up a TWT agreement are merely examples and should not be construed as limitations on the embodiments of the present application.

[0153] The method shown in Figure 4 will be described in detail below. As shown in Figure 4, the method includes the following steps:

[0154] 401: The transmitting end generates a communication frame.

[0155] In this embodiment of the present application, the transmitting end may be any station (operating on the associated link) of the multi-link device to which the STA that set up the TWT agreement belongs. Here, the station may be an AP or a non-AP STA. The communication frame may be a management frame, and the communication frame may include a TWT teardown frame, a TWT deletion frame, a TWT release request frame, a TWT information frame, etc.

[0156] For example, as shown in Table 1, the communication frame includes a TWT release frame, and the TWT release frame includes at least one of information of a category, an unprotected sub1GHz action, and a TWT flow. [Table 1]

[0157] When the negotiation type field in the TWT flow field has a value of 0 or 1, the negotiation type field corresponds to an individual TWT, or when the negotiation type field in the TWT flow field has a value of 2 or 3, the negotiation type field corresponds to a broadcast TWT. When the negotiation type field corresponds to an individual TWT, the TWT flow field includes at least one of the following fields, namely, a TWT flow identifier field, a reserved field, a negotiation type field, and a teardown all TWT field, as shown in Table 2a. For example, the length of the TWT flow identifier field may be 3 bits. Of course, the length of the TWT flow identifier field shown in this specification is merely an example. For example, as the standard evolves, the length of the TWT flow identifier field may be extended from 3 bits to more bits, for example, 4 bits.

[0158] For example, if the value of the negotiation type field is 3, the TWT flow field includes at least one of a broadcast TWT identifier field, a negotiation type field, and a teardown all TWT field, as shown in Table 2b. [Table 2a] [Table 2b]

[0159] It can be understood that the lengths of the fields (or referred to as the number of bits occupied by the fields) shown in Tables 2a and 2b are merely examples and should not be construed as limitations on the embodiments of the present application.

[0160] The communication frame provided in this embodiment of the present application will be described below with reference to Table 1, Table 2a, and Table 2b. The communication frame may include the following several implementations:

[0161] Implementation 1

[0162] The communication frame includes instruction information, which instructs the TWT agreement or TWT plan between the MLDs to be terminated. For example, the instruction information may instruct the termination of all TWT agreements or TWT plans between the MLDs. In a single-link scenario, if the value of the Release All TWTs field in Table 2a is 1, the TWT flow identifier field is set to Reserved. In this case, the Release All TWTs field instructs the termination of all TWTs, i.e., all TWTs on the link. However, the instruction information shown in this embodiment of the present application may be understood as instructing the termination of all TWT agreements or TWT plans on all associated links between the MLDs. For example, for an individual TWT, the instruction information may include a TWT release setup on all associated links field, a teardown all TWT setup on all links field, or a release all TWTs field. For example, in the case of a broadcast TWT, the instruction information may include a Release TWT plans set up on all links field, a Release all TWTs set up on all associated links field, or a Release all TWTs field.

[0163] Example 1

[0164] For example, based on Table 2a, in this embodiment of the present application, one piece of instruction information is added, and the instruction information instructs to release all TWT agreements on all links between MLDs. For example, the communication frame includes at least one of the following information: category (as shown in Table 1), unprotected sub1 GHz action, and TWT flow. As shown in Table 3 or FIG. 7a, the TWT flow field includes at least one of the following fields: TWT flow identifier field, release all TWTs set up on all links (i.e., instruction information field, reserved field, negotiation type field, and release all TWTs field). [Table 3]

[0165] For example, if the value of the Release All TWTs Set Up on All Links field is 1, the field may indicate that the sending end requests to release all TWT agreements on all links of the MLD to which it belongs, where all links are associated links established between two MLDs (the MLD to which the sending end of the communication frame belongs and the MLD to which the receiving end of the communication frame belongs). In another example, if the value of the Release All TWTs Set Up on All Links field is 0, the field may indicate that the sending end does not request to release all TWT agreements on all links of the MLD to which it belongs. In this case, the communication frame may include the first field. For example, the TWT agreements are released with reference to Implementation 2 shown below.

[0166] Example 2

[0167] For example, the Release All TWTs field may be used as the indication information. For example, as shown in FIG. 7b, the communication frame includes at least one of the following information: category (as shown in Table 1), unprotected sub-1 GHz action, and TWT flow. As shown in Table 2a or FIG. 7b, the TWT flow field includes at least one of the following fields: TWT flow identifier field, reserved field, negotiation type field, and release all TWTs field (i.e., indication information). If the value of the Release All TWTs field is 1 and the communication frame does not include an element for carrying the first field, the communication frame may indicate that all TWT agreements on all links of the MLD to which the transmitting end belongs are to be released. All links shown here are all associated links established between MLDs.

[0168] For example, when the Teardown All TWT field is set to 1 and the TWT Teardown frame does not carry the MLO Link Information element, the TWT Teardown frame indicates that the station is requesting the teardown of all TWT agreements on all links in the MLD to which it belongs. (A non-AP STA affiliated with a non-AP MLD may tear down all individual TWT agreements setup on all setup links by sending a TWT Teardown frame with the Teardown All TWT field set to 1 if the MLO Link Information element is not present in the TWT Teardown frame.)

[0169] It may be understood that the above-mentioned relationship between values ​​and corresponding meanings is merely an example and should not be construed as a limitation on the embodiments of the present application. If the value of the Release All TWTs Set Up on All Links field is 0, the field may indicate that the sending end requests to release all TWT agreements on all links of the MLD to which it belongs, where all links are associated links established between MLDs. If the value of the Release All TWTs Set Up on All Links field is 1, the field may indicate that the sending end does not request to release all TWT agreements on all links of the MLD to which it belongs.

[0170] Although the above examples 1 and 2 are for individual TWTs, the above method can also be applied to broadcast TWTs. Since the reserved field is not reserved in the TWT flow of a broadcast TWT, the indication information can be carried in the communication frame. As shown in FIG. 7c, the indication information may exist in the communication frame in the form of an element, or the indication information may exist in the communication frame in the form of a field. This is not limited to the embodiments of the present application. Alternatively, as shown in FIG. 7d, the release field for the entire TWT can be reused as the indication information. For the description of the broadcast TWT in FIG. 7c and FIG. 7d, please refer to the description of the indication information in the individual TWT. The details will not be described again in this specification. It can be understood that the first field in FIG. 7a to FIG. 7d is merely an example. For a specific description of the first field, please refer to Implementation 2.

[0171] In this embodiment of the present application, indication information is added in the TWT flow field, or the Release All TWT field is reused, so that all TWT agreements can be released, and an MLD-level TWT release method is implemented. One bit can indicate that all TWT agreements on all links between MLDs are to be released. This effectively improves the efficiency of releasing TWT agreements and reduces signaling overhead.

[0172] Implementation 2

[0173] The communication frame includes a first field and a second field, where the first field indicates one or more links, and the second field indicates that a TWT agreement between the MLDs is to be terminated.

[0174] Optionally, the release all TWTs field in the TWT flow field can be reused as the second field. Optionally, the second field can alternatively be the release all TWTs field set up on all links in Implementation 1. This is not limited in the embodiment of the present application. For ease of explanation, hereinafter, an example is used in which the second field includes the release all TWTs field. However, this should not be understood as a limitation on the embodiment of the present application.

[0175] Example 3

[0176] In one example, if the value of the second field is the first value, the communication frame may indicate the release of all TWT agreements on each of the one or more links indicated by the first field. A third field (e.g., a TWT flow identifier field) in the communication frame is set to reserved. In other words, if the value of the second field is the first value, the value of the TWT flow identifier field in the communication frame is reserved. For example, the value of the TWT flow identifier field may be (by way of example only) 0 (e.g., 000), or the value of the TWT flow identifier field is (by way of example only) 111.

[0177] It may be understood that all TWT agreements shown in this specification may be understood as follows: When the first field indicates one link, the all TWT agreements are one or more TWT agreements on the link indicated by the first field; When the first field indicates multiple links, the all TWT agreements are all TWT agreements on each of the multiple links indicated by the first field; When the first field indicates multiple links, whether all TWT agreements on the multiple links are set up based on the same TWT setup request frame is not limited in the embodiments of the present application. When the value of the second field is the first value, the communication frame does not include a TWT flow identifier field (for individual TWTs) or a broadcast TWT identifier field (for broadcast TWTs), i.e., the TWT flow identifier field is set to reserved; and the broadcast TWT identifier field is set to reserved. Therefore, the receiving end of the communication frame may release all TWT agreements on each of the one or more links indicated by the first field. There is no restriction on whether TWT agreements over multiple links share TWT parameters.

[0178] For example, the first field indicating one or more links may include that the first field is used to carry a link identifier of each of the one or more links, or that the first field is used to carry a link identifier bitmap, and the length of the link identifier bitmap may be constant, for example, 16 bits. In one example, the first field may indicate the link identifier of one link. For example, if the length of the first field is 4 bits, 0001 may indicate link 1, 0010 may indicate link 2, etc. In one example, the first field may be used to carry the link identifier bitmap. For example, if the value of the first field is 0000 0000 0000 0001 (1 indicates that the TWT agreement on the corresponding link needs to be released, and 0 indicates that the TWT agreement on the corresponding link does not need to be released), the link indicated by the first field is link 1, which indicates that the TWT agreement on link 1 needs to be released. Details will not be listed one by one in this specification. In other examples, the first field may indicate link identifiers of multiple links, or the link identifier bitmap field indicates the release of TWT agreements on multiple links. For a description of the first field, see the above description of the bitmap field and the link identifier field. The details will not be described again here.

[0179] It should be noted that the first field included in the communication frame may be independent of the link identifier bitmap field or link identifier field in the TWT setup request frame or the TWT setup response frame. As long as a TWT agreement is set up on the link indicated by the first field in the communication frame, whether the first field in the communication frame needs to be the same as the link identifier bitmap field or link identifier field in the TWT setup request frame or the TWT setup response frame is not limited in the embodiments of the present application. It may be understood that the number of TWT agreements or TWT plans allowed to be set up on one link is not limited in the embodiments of the present application. For example, one TWT agreement may be set up on one link, or multiple TWT agreements may be set up on one link.

[0180] For example, the first field may be carried in an element in the communication frame. For example, the element may be a newly added element to Table 1. For example, as shown in Table 4 or FIG. 8a, the communication frame includes a TWT release frame, and the TWT release frame includes at least one of the following information: category, unprotected sub-1 GHz action, TWT flow, and multi-link operation (MLO) link information element. [Table 4]

[0181] It may be understood that the names of MLO link information elements shown in this embodiment of the present application are merely examples and should not be construed as limitations on the embodiments of the present application.

[0182] For example, the first field is used to carry a link identifier bitmap. As shown in Table 5 or FIG. 8a, the MLO link information element includes at least one of an element ID field, a length field, an element ID extension field, and a link identifier bitmap field. It can be understood that the length of the link identifier bitmap field shown in Table 5 is merely an example. For example, the MLO link information element may include a link identifier field, and the length of the link identifier field may be 4 bits. This is not limited in the embodiment of the present application. It can be understood that the methods shown in Tables 4 and 5 in this embodiment of the present application can be applied to individual TWT or broadcast TWT, as shown in FIG. 8b. For a specific description of broadcast TWT shown in FIG. 8b, please refer to the description of individual TWT. The details will not be described one by one again. [Table 5]

[0183] For example, the first value is equal to 1, and the second field is the Release All TWT field. When the Release All TWT field is set to 1 and a communication frame carries an MLO link information element, the communication frame requests the release of all TWT agreements on one or more links indicated by the Link Identifier Bitmap field in the MLO link information element. When the MLO link information element is present in a TWT release frame, a non-AP STA subscribed to a non-AP MLD can release individual TWT agreements on all links indicated by the Link Identifier Bitmap subfield in the MLO link information element, and the Release All TWT field is set to 1. A non-AP STA subscribed to a non-AP MLD can send one TWT release frame to release all TWT agreements. The Release All TWT field is set to 1. All TWT agreements are established on the links indicated by the Link Identifier Bitmap field in the MLO link information element. (A non-AP STA affiliated with a non-AP MLD may tear down all individual TWT agreements setup on the link(s) indicated by the Link ID Bitmap subfield of the MLO Link Information element by sending a TWT Teardown frame with the Teardown All TWT field set to 1 if the MLO Link Information element is present in the TWT Teardown frame.) The all links indicated herein may be understood to be the links from which TWT agreements should be torn down and are indicated by the link identifier bitmap. For example, if the value of the link identifier bitmap is 0010 0000 0000 0000 and the value of the Release All TWT field is 1, the communication frame may indicate the tearing down of all TWT agreements on link 3.

[0184] It may be understood that the above-mentioned Example 3 is mainly for individual TWT, and the above-mentioned method is also applicable to broadcast TWT. For example, when the method is applied to broadcast TWT, the TWT flow identifier in Example 3 may alternatively be a broadcast TWT identifier. For example, when the value of the second field is a first value, the communication frame may indicate that all TWT plans on each of the one or more links indicated by the first field are to be released, and a third field (e.g., a broadcast TWT identifier field) in the communication frame is set to reserved. It may be understood that the description of the combination corresponding to the TWT agreement in the following Example 4 is also applicable to Examples 1, 2, and 3. Details will not be described in this embodiment of the present application.

[0185] Example 4

[0186] In another example, if the value of the second field is the second value, the communication frame may indicate termination of a TWT agreement corresponding to a combination including a TWT flow identifier on one or more links indicated by the first field, or the communication frame may indicate termination of a TWT agreement corresponding to a combination including a broadcast TWT identifier on one or more links indicated by the first field.

[0187] For example, the communication frame further includes a third field, and the third field indicates a TWT flow identifier (or a broadcast TWT identifier). For example, the third field may be the aforementioned TWT flow identifier field (or a broadcast TWT identifier field).

[0188] Method 1: The TWT Agreement is uniquely identified by, or corresponds to, the following combination (it can also be understood that the TWT Agreement corresponds to the following combination including the TWT Flow Identifier), that is, the following combination is the combination of the TWT Flow Identifier, the MAC address of the station on the link indicated by the first field, and the MAC address of the peer station of the link indicated by the first field (or the MAC address of the station corresponding to the link indicated by the first field, collectively referred to). The station and the transmission end of the communication frame belong to the same MLD, and the peer station and the receiving end of the communication frame belong to the same MLD. The above description can also be that the TWT Agreement is uniquely identified by, or corresponds to, <TWT Flow Identifier, MAC address of the station on the link indicated by the first field, and MAC address of the peer station of the link indicated by the first field>. For example, the TWT Agreement is uniquely identified by, or corresponds to, the following combination (it can also be understood that the TWT Agreement corresponds to the following combination including the TWT Flow Identifier), that is, the following combination is the combination of the TWT Flow Identifier, the MAC address of the STA operating in the link indicated by the Link ID Bitmap field, and the MAC address of the peer STA operating in the link indicated by the Link ID Bitmap field).Optionally, the elements associated with the TWT agreement include a TWT flow identifier, a MAC address of a station operating on the link indicated by the link identifier bitmap, a MAC address of a peer station operating on the link indicated by the link identifier bitmap, and a link indicated by the link identifier bitmap field. In other words, when a TWT release frame is successfully transmitted or received, the TWT agreement corresponding to the TWT flow number and the MAC addresses of the stations corresponding to the links indicated by the link identifier field (or bitmap field) in the TWT release frame (e.g., two stations corresponding to one link) can be released. Alternatively, when a TWT release frame is successfully transmitted or received, the TWT agreement corresponding to the TWT flow number, the MAC addresses of the stations corresponding to the links indicated by the link identifier field (or bitmap field) in the TWT release frame, and the MAC addresses of the peer stations corresponding to the links indicated by the link identifier field (or bitmap field) in the TWT release frame can be released.

[0189] Method 2: The TWT Agreement is uniquely identified by, or corresponds to, the following combination (it can also be understood that the TWT Agreement corresponds to the following combination including the TWT Flow Identifier), that is, the following combination is the combination of the TWT Flow Identifier, the MAC address of the MLD of the TWT requesting station (MAC address of TWT requesting MLD), the MAC address of the MLD of the TWT responding station (MAC address of TWT responding MLD), and the link indicated by the Link Identifier field (or Link Identifier bitmap field). The foregoing description may alternatively be that the TWT Agreement is uniquely identified by, or corresponds to, <the link indicated by the TWT Flow Identifier, the MAC address of the MLD of the TWT requesting station (MAC address of TWT requesting MLD), the MAC address of the MLD of the TWT responding station (MAC address of TWT responding MLD), and the Link Identifier field (or Link Identifier bitmap field)>. For example, when the TWT Teardown frame is successfully transmitted or received, the TWT Agreement corresponding to the TWT Flow Identifier field, the MAC address of the MLD requesting the TWT Agreement, the MAC address of the MLD responding to the request, and the link indicated by the Link Identifier field (or Link Identifier bitmap field) in the TWT Teardown frame may be deleted (When a TWT Teardown frame is successfully transmitted or received, the TWT agreement corresponding to the TWT Flow Identifier field, the TWT requesting MLD MAC address, the TWT responding MLD MAC address, and link ID of the TWT Teardown frame shall be deleted).Alternatively, the TWT Agreement is uniquely identified by, or corresponds to, the following combination (it may also be understood that the TWT Agreement corresponds to the following combination including the TWT Flow Identifier), that is, the following combination is the combination of the TWT Flow Identifier, the MAC address of the multi-link device to which the transmission end of the communication frame belongs, the MAC address of the multi-link to which the reception end of the communication frame belongs, and the link indicated by the first field. Generally, the MAC address of the MLD of the TWT Request Station (or the TWT Response Station) is the same as the MAC address of the MLD to which the transmission end (or reception end) of the communication frame belongs, or the MAC address of the MLD of the TWT Request Station (or the TWT Response Station) is the same as the MAC address of the MLD to which the reception end (or transmission end) of the communication frame belongs.

[0190] The MAC address of the MLD is associated with the TWT Agreement. Since it is required that the STA in the non-AP MLD be de-associated after the AP MLD and the non-AP MLD are associated with the link, this can effectively avoid the problem that the MAC address of the TWT Request Station is invalid.

[0191] Method 3: The TWT Agreement is uniquely identified by, or corresponds to, the combination of <TWT Flow Identifier, MAC address of the TWT Request Station, and MAC address of the TWT Response Station>. However, the TWT Request Station and the TWT Response Station can be understood as follows.

[0192] A. When the link identifier bitmap field or the element in which the link identifier bitmap field is located is not present in the TWT setup frame, the TWT requesting station is a station that sends a TWT element to request setting up a TWT, and the TWT request field in the request type field in the TWT element field is set to 1. The TWT responding station is a station that sends a TWT element to respond to setting up a TWT, and the TWT request field in the request type field in the TWT element field is set to 0. For example, when the TWT setup frame does not include a link identifier bitmap field or an element in which the link identifier bitmap field is located, the TWT requesting station and the TWT responding station may set up a TWT agreement for the link corresponding to the TWT requesting station based on the TWT setup frame. For example, when the TWT setup frame includes a link identifier bitmap field or an element in which the link identifier bitmap field is located, the TWT requesting station and the TWT responding station may set up TWT agreements for other links (links other than the link corresponding to the TWT requesting station between MLDs) based on the TWT setup frame, or may set up TWT agreements for multiple links based on the TWT setup frame.

[0193] B. When the Link Identifier Bitmap field or the element in which the Link Identifier Bitmap field is located is not present in the TWT Release frame, the TWT Requesting Station is the station that sends the TWT element to request the setup of a TWT, and the TWT Request field in the Request Type field in the TWT Element field is set to 1. The TWT Responding Station is the station that sends the TWT element to respond to the setup of a TWT, and the TWT Request field in the Request Type field in the TWT Element field is set to 0. For example, when the TWT Release frame does not include the Link Identifier Bitmap field or the element in which the Link Identifier Bitmap field is located, the station requesting to release the TWT agreement must match the station requesting to set up the TWT agreement. For example, when the TWT Release frame includes the Link Identifier Bitmap field or the element in which the Link Identifier Bitmap field is located, the TWT Requesting Station can be different from the station requesting to set up the TWT agreement. In this way, all stations that belong to the same MLD as the station requesting to set up the TWT agreement can release the TWT agreement.

[0194] C. When the Link Identifier Bitmap field or the element in which the Link Identifier Bitmap field is located is present in a TWT Setup frame, the TWT Requesting Station is a station operating on the link indicated by the Link Identifier Bitmap in the TWT element, the station sending the TWT element to request to set up a station and a TWT belongs to a multilink device, and the TWT Request field in the Request Type field in the TWT Element field is set to 1. The TWT Responding Station is a peer station operating on the link indicated by the Link Identifier Bitmap in the TWT element, the station sending the TWT element to respond to the peer station and TWT setup belongs to a multilink device, and the TWT Request field in the Request Type field in the TWT Element field is set to 0.

[0195] D. When a link identifier bitmap field or an element in which the link identifier bitmap field is located is present in a TWT release frame, the TWT requesting station is a station operating on the link indicated by the link identifier bitmap in the TWT release frame, and that station and the station sending the TWT release frame belong to a multilink device. The TWT responding station is a peer station operating on the link indicated by the link identifier bitmap in the TWT release frame, and the peer station and the station receiving the TWT release frame belong to a multilink device.

[0196] For the explanation of C and D, please refer to the explanation of Scheme 1 and Scheme 2 shown in this embodiment of the present application. Details will not be described again in this specification. Regarding A and B, when the link identifier bitmap field or the element in which the link identifier bitmap field is located is not present in the TWT setup frame and / or is not present in the TWT release frame, this may indicate that the station requesting to release the TWT agreement is the station setting up the TWT agreement; in other words, the MAC address of the station corresponding to the link on which the TWT agreement is set up must match the MAC address of the station requesting to release the TWT agreement. Therefore, in this embodiment of the present application, both communication parties can implicitly know the meaning of the TWT request station and the TWT responder station depending on whether the link identifier bitmap field is present in the TWT release frame. It may be understood that the explanation of the link identifier bitmap field shown in A, B, C, and D is merely an example. For example, the link identifier bitmap field may alternatively be the link identifier field.

[0197] For example, the second value is equal to 0, and the second field is a Release All TWT field. When the Release All TWT field is set to 0 and the communication frame carries an MLO link information element, the communication frame requests the release of TWT agreements that satisfy the corresponding relationship on one or more links indicated by the link identifier bitmap field in the MLO link information element. For the correspondence relationship in this specification, please refer to Scheme 1 to Scheme 3. It can be understood that Scheme 1 to Scheme 3 can be used to identify a TWT agreement. Therefore, Scheme 1 to Scheme 3 are all applicable to a TWT agreement, i.e., Scheme 1 to Scheme 3 are all applicable to the above-mentioned Examples 1 to 4. It can be understood that the receiving end can uniquely identify one TWT agreement based on Scheme 1 to Scheme 3, or the receiving end can determine a TWT agreement based on Scheme 1 to Scheme 3.

[0198] For example, a non-AP STA belonging to a non-AP MLD may send a TWT Teardown frame to tear down one or more TWT agreements, where the Negotiation Type subfield in the TWT Teardown frame is set to 0, and the Teardown All TWT field is set to 0. One or more TWT agreements are separately set up on links corresponding to one or more bits of the Link ID Bitmap subfield set to 1 within the MLO Link Information element. One TWT agreement corresponds to one link, and a TWT agreement corresponds separately to a combination of <TWT Flow Identifier, MAC address of the station operating on the link indicated by the Link ID Bitmap, and MAC address of the peer station operating on the link indicated by the Link ID Bitmap> or <TWT Flow Identifier, MAC address of the station operating on the link indicated by the Link ID Bitmap, MAC address of the peer station operating on the link indicated by the Link ID Bitmap, and link indicated by the Link ID Bitmap field>. (A non-AP STA affiliated with a non-AP MLD may tear down one or more TWT agreements by sending a TWT Teardown frame with the Negotiation Type subfield set to 0 and one or more bits in the Link ID Bitmap subfield of the MLO Link Information element set to 1 and Teardown All TWT field set to 0).

[0199] It can be understood that Example 4 is mainly for individual TWT, and the above method is also applicable to broadcast TWT. For example, when the method is applied to broadcast TWT, the TWT flow identifier in Example 4 may alternatively be a broadcast TWT identifier. For example, if the value of the second field is the second value, the communication frame may instruct to release a TWT plan corresponding to a combination including the broadcast TWT identifier on each of one or more links indicated by the first field. For example, the TWT plan corresponds to any one of the following combinations, each including a broadcast TWT identifier: a combination of a broadcast TWT identifier and a media access control (MAC) address of an access station on the link indicated by the first field, or a combination of a broadcast TWT identifier, a MAC address of a multi-link device to which an access station on the link indicated by the first field belongs, and the link indicated by the first field. For descriptions of the first field and the MLO link information element, please refer to Tables 4 and 5. Details will not be described in this embodiment of the present application. For an individual TWT, the combination including the TWT flow identifier may be understood to include the MAC address of the station on the link indicated by the first field and the MAC address of the peer station on the link (or the MAC address of the MLD of the TWT requesting station and the MAC address of the MLD of the TWT responding station). For a broadcast TWT, the combination including the broadcast TWT identifier may include the MAC address of the access station on the link indicated by the first field, or the MAC address of the MLD to which the access station on the link indicated by the first field belongs.

[0200] In this embodiment of the present application, the TWT agreement is terminated based on the first field and the different values ​​of the second field, so that the receiving end can know exactly which TWT agreement or TWT plan needs to be terminated by the receiving end, which improves the efficiency and flexibility of terminating the TWT agreement.

[0201] Implementation 3

[0202] The communication frame includes a first field and does not include a second field. For example, if the first field is used to carry a link identifier of the link, the communication frame may indicate terminating a TWT agreement on the link indicated by the first field. In another example, if the first field is used to carry a link identifier bitmap, the communication frame may indicate terminating a TWT agreement on the link corresponding to a bit with a value of 1 in the link identifier bitmap field.

[0203] For example, the first field may be carried in the aforementioned MLO link information element. For a description of the first value and the MLO link information element, please refer to Implementation 1 or Implementation 2. The details will not be described again in this specification.

[0204] Implementation 4

[0205] The first field may not be included independently in an element, but may be included in the communication frame in the form of a field. For example, the communication frame may include a second field and an indication field indicating whether the first field is present. If the indication field occupies one bit, the indication field may optionally be included in the TWT flow field. If the indication field indicates that the first field is present and the communication frame includes the first field and the second field, refer to Implementation 2 above for a specific description of the communication frame. Details will not be described again in this specification. In another example, if the indication field indicates that the first field is absent, the communication frame includes a second field, and the value of the second field is the first value, the communication frame may indicate that all TWT agreements on all links of the MLD to which the transmitting end belongs are to be terminated. All links shown here are all associated links established between MLDs.

[0206] In Table 1, Table 2a, Table 2b, Table 3, Table 4, and Table 5, the example in which the communication frame is a TWT release frame is used in implementations 1 to 4. The example in which the communication frame is a TWT information frame is used below for explanation purposes.

[0207] The communication frame is a TWT information frame. For example, as shown in Table 6, the TWT information frame includes at least one of the following information: category, unprotected sub-1 GHz action, TWT information, and MLO link information element. [Table 6]

[0208] For example, as shown in Table 7, the TWT information field includes at least one of a TWT flow identifier field, a response request field, a next TWT request field, a next TWT field size field, an all TWT field, and a next TWT field. [Table 7]

[0209] For example, if the All TWTs field is set to a first value, e.g., 1, the TWT information frame may be used to indicate replanning of all TWTs, where replanning includes suspending and / or resuming.

[0210] For the function of the Total TWT field, see the second field in the above embodiment. For example, when the Total TWT field is set to 1 and the TWT information frame carries the first field (see the above MLO link information element), the TWT information frame can be used to request replanning of all TWTs on one or more links indicated by the link identifier bitmap field (or link identifier field) in the MLO link information element. For an explanation that the communication frame is a TWT information frame, the TWT information frame includes the Total TWT field and the first field, and the value of the Total TWT field in the TWT information frame is the first value, see Example 3 in Implementation 2 above. Details will not be described again in this specification.

[0211] For example, when the all TWT fields are set to 0 and the TWT information frame carries an MLO link information element, the TWT information frame can be used to request replanning of a TWT agreement corresponding to a combination including a TWT flow identifier on one or more links indicated by the link identifier bitmap field in the MLO link information element. For an explanation of the communication frame being a TWT information frame, the TWT information frame including the all TWT field and a first field, and the value of the all TWT field in the TWT information frame being the second value, see Example 4 in Implementation 2 above. Details will not be described again in this specification.

[0212] For example, a non-AP STA belonging to a non-AP MLD may send a TWT Information frame to reschedule one or more TWT agreements, where all TWT fields in the TWT Information frame are set to 0. One or more TWT agreements are separately set up on links corresponding to one or more bits of the Link ID Bitmap subfield set to 1 within the MLO Link Information element. One TWT agreement corresponds to one link, and a TWT agreement corresponds separately to a combination of <TWT Flow Identifier, MAC address of the station operating on the link indicated by the Link ID Bitmap, and MAC address of the peer station operating on the link indicated by the Link ID Bitmap> or <TWT Flow Identifier, MAC address of the station operating on the link indicated by the Link ID Bitmap, MAC address of the peer station operating on the link indicated by the Link ID Bitmap, and the link indicated by the Link ID Bitmap field>. (A non-AP STA affiliated with a non-AP MLD may reschedule one or more TWT agreements by sending a TWT Information frame with one or more bits in the Link ID Bitmap subfield of the MLO Link Information element set to 1 and All TWT field set to 0).

[0213] For example, when the all TWT fields are set to 1 and the TWT information frame does not carry an MLO link information element, the TWT information frame indicates that the station requests to replan all TWT agreements on all links of the MLD to which it subscribes. For an explanation of the communication frame being a TWT information frame, the TWT information frame including the all TWT fields but not the first field, and the value of the all TWT fields in the TWT information frame being the first value, see Implementation 1 above. The details will not be described again in this specification.

[0214] It can be understood that the above description of the TWT information frame is merely an example, and for a specific description of the TWT information frame, please refer to the TWT release frame described above.

[0215] It should be noted that the TWT agreement referred to in this embodiment of the present application may alternatively be a TWT plan. Generally, the TWT agreement is an individual TWT agreement, and the TWT plan is a broadcast TWT plan. Therefore, when the communication frame is a TWT information frame, the specific description of the broadcast TWT plan will adaptively refer to the individual TWT agreement. Details will not be described in this embodiment of the present application.

[0216] 402: The transmitting end transmits a communication frame, and the receiving end receives the communication frame correspondingly.

[0217] The receiving end may be a peer STA operating on the same associated link as the transmitting end.

[0218] 403: The receiving end releases the TWT agreement based on the communication frame.

[0219] For a description of the communication frame, see step 401. Only a specific method for releasing the TWT agreement by the receiving end is described herein as an example.

[0220] In one example, when the communication frame is a TWT release frame, referring to implementation 1, the receiving end may release all TWT agreements on all associated links between the MLD to which the receiving end belongs and the MLD to which the transmitting end belongs based on the release all TWTs on all links setup field.

[0221] In another example, when the communication frame is a TWT release frame, referring to Implementation 2, the communication frame includes a first field and a second field, and the value of the second field is the first value. In this case, the receiving end may release all TWT agreements on one or more links indicated by the first field based on the communication frame.

[0222] In yet another example, when the communication frame is a TWT release frame, referring to Implementation 2, the communication frame includes a first field and a second field, and the value of the second field is a second value. In this case, the receiving end may release a TWT agreement corresponding to a combination including a TWT flow identifier on one or more links indicated by the first field based on the communication frame.

[0223] In yet another example, the communication frame includes the indication information and does not include an element for carrying the first field, in which case the receiving end may cancel all TWT agreements on all associated links between the MLD to which the sending end belongs and the MLD to which the receiving end belongs based on the communication frame.

[0224] Optionally, when the communication frame is a TWT information frame, the aforementioned step 403 may alternatively involve the receiving end replanning the TWT agreements based on the communication frame. For example, when the all TWT fields are set to 1 and the TWT information frame carries the first field, the receiving end may replan all TWTs on one or more links indicated by the link identifier bitmap field (or link identifier field) in the MLO link information element based on the TWT information frame. For example, when the all TWT fields are set to 0 and the TWT information frame carries an MLO link information element, the receiving end may replan TWT agreements corresponding to combinations including TWT flow identifiers on one or more links indicated by the link identifier bitmap field in the MLO link information element based on the TWT information frame. For example, when the all TWT fields are set to 1 and the TWT information frame does not carry an MLO link information element, the receiving end may replan all TWT agreements on all links of the MLD to which the station subscribes based on the TWT information frame.

[0225] In a possible implementation, the receiving end may further send an acknowledgement frame, which is used to acknowledge that the TWT agreement has been successfully released.

[0226] In this embodiment of the present application, the receiving end of the communication frame can effectively know that it can delete the TWT agreement set up by another link based on the first field and the second field, which effectively improves the flexibility of releasing the TWT agreement.

[0227] In the embodiments of the present application, "field" is used as an example for explanation, and it should be noted that "field" and "subfield" are not particularly distinguished from each other. Although "field" and "subfield" are not particularly distinguished from each other in the embodiments of the present application, those skilled in the art may adaptively distinguish the relationship between fields (or between elements and fields) shown in the present application. Optionally, in practical applications, fields, elements, etc. in the embodiments of the present application may also be expressed in the form of information. Therefore, the representation format of contents such as fields, subfields, elements, and instruction information is not limited in the embodiments of the present application.

[0228] A communication device provided in an embodiment of the present application will be described below.

[0229] In the present application, the communication device is divided into functional modules based on the embodiment of the aforementioned method. For example, functional modules corresponding to functions may be obtained through division, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in the form of hardware or software functional modules. It should be noted that in the present application, the module division is an example and is merely a logical functional division. Other division methods may be used in actual implementation. Hereinafter, the communication device in the embodiment of the present application will be described in detail with reference to Figures 9 to 11.

[0230] 9 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. As shown in FIG. 9, the communication device includes: a processing unit 901 and a transceiving unit 902.

[0231] In some embodiments of the present application, the communication device may be the transmitting end or the chip shown above, and the chip may be located at the transmitting end. In other words, the communication device may be configured to perform the steps, functions, etc. performed by the transmitting end in the method embodiments (FIG. 4, FIG. 5a, or FIG. 5b).

[0232] The processing unit 901 is configured to generate a communication frame. The transceiver unit 902 is configured to output the communication frame.

[0233] For example, the transceiver unit 902 is further configured to input an acknowledgement frame.

[0234] In some other embodiments of the present application, the communication device may be the receiving end or the above-mentioned chip, and the chip may be located at the receiving end. In other words, the communication device may be configured to perform the steps, functions, etc. performed by the receiving end in the method embodiment (FIG. 4).

[0235] The transceiver 902 is configured to input a communication frame, and the processing unit 901 is configured to release a TWT agreement based on the communication frame.

[0236] It can be understood that for a specific description of releasing the TWT agreement by the processing unit 901, please refer to the aforementioned method embodiments, and the details will not be described again in this specification.

[0237] For example, the processing unit 901 is further configured to identify a TWT agreement (or a TWT plan) in the above-mentioned schemes 1 to 3.

[0238] For example, the processing unit 901 is particularly configured to release (or re-plan) all TWT agreements or all TWT plans on one or more links indicated by the first field when the value of the second field is the first value.

[0239] For example, the processing unit 901 is particularly configured to terminate (or replan) a TWT agreement corresponding to a combination including a TWT flow identifier on each of the one or more links indicated by the first field when the value of the second field is the second value, or to terminate (or replan) a TWT plan corresponding to a combination including a broadcast TWT identifier on each of the one or more links indicated by the first field when the value of the second field is the second value.

[0240] For example, the transceiver unit 902 is further configured to output an acknowledgement frame.

[0241] It can be understood that the specific description of the transceiver unit and the processing unit described in this embodiment of the present application is merely an example. For the specific functions, steps performed, etc. of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiment. The details will not be described again in this specification.

[0242] For the description of the communication frame, the first field, the second field, the third field, the TWT flow field, etc. in the above embodiment, please refer to the description in the above method embodiment, and the details will not be described one by one in this specification.

[0243] The above describes the communication device in this embodiment of the present application. Hereinafter, possible product forms of the communication device will be described. It should be understood that any product in any form having the functions of the communication device described in FIG. 9 falls within the scope of protection of the embodiment of the present application. It should be further understood that the following description is merely an example and does not limit the product form of the communication device in the embodiment of the present application.

[0244] In a possible implementation, in the communication device shown in FIG. 9, the processing unit 901 may be one or more processors. The transceiver unit 902 may be a transceiver, or the transceiver unit 902 may be a transmitting unit and a receiving unit. The transmitting unit may be a transmitter, and the receiving unit may be a receiver. The transmitting unit and the receiving unit may be integrated into one device, for example, a transceiver. In this embodiment of the present application, the processor and the transceiver may be combined, etc. The manner of connection between the processor and the transceiver is not limited in this embodiment of the present application. In the process of performing the above-mentioned method, the information transmitting process in the above-mentioned method may be understood as a process of outputting the information by the processor. When outputting the information, the processor outputs the information to the transceiver, and the transceiver thereby transmits the information. After the information is output by the processor, other processing may be required on the information before it arrives at the transceiver. Similarly, the information receiving process in the above-mentioned method may be understood as a process of receiving the input information by the processor. When the processor receives the input information, the transceiver receives the information and inputs it to the processor. Additionally, after the transceiver receives such information, other processing may need to be performed on the information before it is input to the processor.

[0245] As shown in FIG. 10, the communications device 100 includes one or more processors 1020 and a transceiver 1010 .

[0246] In some embodiments of the present application, the communication device may be configured to perform steps, functions, etc. performed by the transmitting end in the method embodiments (FIG. 4).

[0247] The processor 1020 is configured to generate the communication frame. The transceiver 1010 is configured to transmit the communication frame.

[0248] For example, the transceiver 1010 is further configured to receive an acknowledgement frame.

[0249] In some other embodiments of the present application, the communication device may be configured to perform the steps, functions, etc. performed by the receiving end in the method embodiments (FIG. 4).

[0250] The transceiver 1010 is configured to receive a communication frame. The processor 1020 is configured to release a TWT agreement based on the communication frame.

[0251] For example, the processor 1020 is further configured to identify a TWT agreement (or a TWT plan) in the above-described methods 1 to 3.

[0252] For example, the processor 1020 is specifically configured to release (or re-plan) all TWT agreements or all TWT plans on one or more links indicated by the first field when the value of the second field is the first value.

[0253] For example, the processor 1020 is particularly configured to, when the value of the second field is the second value, terminate (or replan) a TWT agreement corresponding to a combination including a TWT flow identifier on each of the one or more links indicated by the first field, or, when the value of the second field is the second value, terminate (or replan) a TWT plan corresponding to a combination including a broadcast TWT identifier on each of the one or more links indicated by the first field.

[0254] For example, the transceiver 1010 is further configured to transmit an acknowledgement frame.

[0255] It can be understood that the specific description of the transceiver and the processor described in this embodiment of the present application is merely an example. For the specific functions of the transceiver and the processor, the steps performed, etc., please refer to the above-mentioned method embodiment. The details will not be described again in this specification.

[0256] For the description of the communication frame, the first field, the second field, the third field, the TWT flow field, etc. in the above embodiment, please refer to the description in the above method embodiment, and the details will not be described one by one in this specification.

[0257] In each implementation of the communication apparatus shown in Figure 10, the transceiver may include a receiver and a transmitter. The receiver is configured to perform receiving functions (or operations), and the transmitter is configured to perform transmitting functions (or operations). The transceiver is configured to communicate with other devices / apparatuses over a transmission medium.

[0258] Optionally, the communication device 100 may further include one or more memories 1030 configured to store program instructions and / or data. The memory 1030 is coupled to the processor 1020. A coupling in this embodiment of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be in an electrical, mechanical, or other form and is used for exchanging information between the devices, units, or modules. The processor 1020 may operate together with the memory 1030. The processor 1020 may execute program instructions stored in the memory 1030. Optionally, at least one of the one or more memories may be included in the processor.

[0259] The specific connection medium between the transceiver 1010, the processor 1020, and the memory 1030 is not limited in the embodiment of the present application. In the present embodiment of the present application, in FIG. 10, the memory 1030, the processor 1020, and the transceiver 1010 are connected to each other via a bus 1040. In FIG. 10, the bus is shown with a bold line. The manner of connection between other components is described merely as an example, but is not limited thereto. The bus may be classified into an address bus, a data bus, a control bus, etc. For ease of representation, the bus is represented by only one bold line in FIG. 10. However, this does not mean that there is only one bus or only one type of bus.

[0260] In the present embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which may implement or perform the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, any conventional processor, etc. The steps of the methods disclosed with reference to the embodiments of the present application may be performed and achieved directly by a hardware processor, or may be performed and achieved by using a combination of hardware modules and software modules in a processor.

[0261] In this embodiment of the present application, the memory may include, but is not limited to, a non-volatile memory, such as a hard disk drive (HDD) or solid-state drive (SSD), a random access memory (RAM), an erasable programmable read-only memory (EPROM), a read-only memory (ROM), or a compact disc read-only memory (CD-ROM). The memory is any recording medium that can be used to carry or store program code in the form of instructions or data structures and that can be read and / or written by a computer (e.g., a communication device shown in this application). However, it is not limited thereto. The memory in this embodiment of the present application may alternatively be a circuit or any other device capable of implementing a storage function and configured to store program instructions and / or data.

[0262] For example, the processor 1020 is primarily configured to process communication protocols and communication data, control the entire communication device, execute software programs, and process data of the software programs. The memory 1030 is primarily configured to store software programs and data. The transceiver 1010 may include a control circuit and an antenna. The control circuit is primarily configured to convert between baseband signals and radio frequency signals and process the radio frequency signals. The antenna is primarily configured to receive and transmit radio frequency signals in the form of electromagnetic waves. The input / output device, for example, a touch screen, a display, or a keyboard, is primarily configured to receive data input by a user and output data to the user.

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

[0264] In other implementations, the radio frequency circuitry and antenna may be located independently of the processor that performs the baseband processing, for example, in a distributed scenario, the radio frequency circuitry and antenna may be located independently and remote from the communication device.

[0265] It can be understood that the communication device described in this embodiment of the present application may further include more components than those shown in Fig. 10. This is not limited in the embodiment of the present application. The above-mentioned method performed by the processor and the transceiver is merely an example. Please refer to the above-mentioned method for specific steps performed by the processor and the transceiver.

[0266] In another possible implementation, in the communication device shown in FIG. 9 , the processing unit 901 may be one or more logic circuits, and the transceiver unit 902 may be an input / output interface, also referred to as a communication interface, interface circuit, interface, etc. Alternatively, the transceiver unit 902 may be a transmitting unit and a receiving unit. The transmitting unit may be an output interface, and the receiving unit may be an input interface. The transmitting unit and the receiving unit are integrated into one unit, for example, an input / output interface. As shown in FIG. 11 , the communication device shown in FIG. 11 includes a logic circuit 1101 and an interface 1102. In other words, the processing unit 901 may be implemented by the logic circuit 1101, and the transceiver unit 902 may be implemented by the interface 1102. The logic circuit 1101 may be a chip, a processing circuit, an integrated circuit, a system on chip (SoC), etc. The interface 1102 may be a communication interface, an input / output interface, a pin, etc. For example, FIG. 11 illustrates an example in which the communication device is a chip. The chip includes a logic circuit 1101 and an interface 1102 .

[0267] In this embodiment of the present application, the logic circuit and the interface may be further coupled to each other, and the specific manner of connection between the logic circuit and the interface is not limited in the embodiment of the present application.

[0268] In some embodiments of the present application, the communication device may be configured to perform steps, functions, etc. performed by the transmitting end in the method embodiments (FIG. 4).

[0269] The logic circuit 1101 generates a communication frame, and the interface 1102 outputs the communication frame.

[0270] For example, the interface 1102 is further configured to input an acknowledgement frame.

[0271] In some other embodiments of the present application, the communication device may be configured to perform the steps, functions, etc. performed by the receiving end in the method embodiments (FIG. 4).

[0272] The interface 1102 receives a communication frame, and the logic circuit 1101 is configured to release the TWT agreement based on the communication frame.

[0273] For example, the logic circuit 1101 is further configured to identify the TWT agreement (or TWT plan) in Method 1 to Method 3 described above.

[0274] For example, the logic circuit 1101 is specifically configured to release (or re-plan) all TWT agreements or all TWT plans on one or more links indicated by the first field when the value of the second field is the first value.

[0275] For example, the logic circuit 1101 is specifically configured to terminate (or re-plan) a TWT agreement corresponding to a combination including a TWT flow identifier on each of the one or more links indicated by the first field when the value of the second field is a second value, or to terminate (or re-plan) a TWT plan corresponding to a combination including a broadcast TWT identifier on each of the one or more links indicated by the first field when the value of the second field is a second value.

[0276] For example, the interface 1102 is further configured to output an acknowledgement frame.

[0277] It can be understood that the specific descriptions of the logic circuits and interfaces described in this embodiment of the present application are merely examples. For the specific functions of the logic circuits and interfaces, the steps performed, etc., please refer to the above-mentioned method embodiments. The details will not be described again in this specification.

[0278] For the description of the communication frame, the first field, the second field, the third field, the TWT flow field, etc. in the above embodiment, please refer to the description in the above method embodiment, and the details will not be described one by one in this specification.

[0279] It can be understood that the communication device described in this embodiment of the present application can implement the method provided in this embodiment of the present application in the form of hardware or software, which is not limited in the embodiment of the present application.

[0280] An embodiment of the present application further provides a wireless communication system, which includes a transmitting end and a receiving end, and the transmitting end and the receiving end can be configured to perform the method in any embodiment (for example, FIG. 4).

[0281] In addition, the present application further provides a computer program, which is used to implement the actions and / or processes performed by the transmitting end in the methods provided in the present application.

[0282] The present application further provides a computer program, which is used to implement the actions and / or processes performed by the receiving end in the methods provided in the present application.

[0283] The present application further provides a computer-readable recording medium, which stores computer code that, when executed on a computer, enables the computer to perform the actions and / or processes performed by the transmitting end in the methods provided herein.

[0284] The present application further provides a computer-readable recording medium, which stores computer code that, when executed on a computer, enables the computer to perform the actions and / or processes performed by the receiving end in the methods provided herein.

[0285] The present application further provides a computer program product, which includes computer code or a computer program that, when executed on a computer, performs the actions and / or processes performed by the sending end in the methods provided herein.

[0286] The present application further provides a computer program product, which includes computer code or a computer program that, when executed on a computer, performs the actions and / or processes performed by a receiving end in the methods provided herein.

[0287] In some embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into other systems, or some features may be omitted or not implemented. In addition, the shown or described mutual couplings or direct couplings or communication connections may be implemented via some interfaces. Indirect couplings or communication connections between devices or units may be implemented electrically, mechanically, or in other ways.

[0288] The units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, and may be located in one location or distributed over multiple network units. Some or all of the units may be selected based on actual requirements to achieve the technical effects of the solutions provided in the embodiments of the present application.

[0289] In addition, the functional units in the embodiments of the present application may be integrated into one processing unit, and each functional unit may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware or a software functional unit.

[0290] When an integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable recording medium. Based on this understanding, the technical solution of the present application may essentially be implemented in the form of a software product, or a portion of the technical solution may be implemented in the form of a software product. The computer software product may be stored in a computer-readable recording medium and may include instructions for instructing a computer device (such as a personal computer, a server, a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The computer-readable recording medium may include any medium capable of storing program code, such as a USB flash drive, a removable hard disk drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0291] The above description is merely a specific implementation of the present application and is not intended to limit the scope of protection of the present application. Any variations or replacements that can be easily conceived by those skilled in the art within the technical scope disclosed in the present application shall fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. 1. A multi-link communication method, the method comprising: generating a communication frame, the communication frame including a first field and a second field, the first field indicating one link and the second field indicating releasing a target wake time TWT agreement or TWT plan between multi-link devices; transmitting the communication frame; A method comprising:

2. 2. The method of claim 1, wherein if the value of the second field is a first value, the communication frame indicates that all TWT agreements or TWT plans on the link indicated by the first field are to be released.

3. 2. The method of claim 1, wherein, when the value of the second field is a second value, the communication frame indicates that a TWT agreement corresponding to a combination including a TWT flow identifier on the link indicated by the first field is to be terminated, or the communication frame indicates that a TWT plan corresponding to a combination including a broadcast TWT identifier on the link indicated by the first field is to be terminated.

4. 4. The method of claim 3, wherein the communication frame further includes a third field, wherein the third field is used to carry the TWT flow identifier, or the third field is used to carry the broadcast TWT identifier.

5. The TWT agreement may include the following combinations, each of which includes the TWT flow identifier: a combination of the TWT flow identifier, a media access control (MAC) address of a station on the link indicated by the first field, and a MAC address of a peer station on the link indicated by the first field; or A combination of the TWT flow identifier, a MAC address of a multilink device to which a transmitting end of the communication frame belongs, a MAC address of a multilink to which a receiving end of the communication frame belongs, and the link indicated by the first field; corresponds to one of the The TWT plans may be any of the following combinations, each of which includes the broadcast TWT identifier: a combination of the broadcast TWT identifier and a media access control MAC address of an access station on the link indicated by the first field; or a combination of the broadcast TWT identifier, a MAC address of a multi-link device to which an access station on the link indicated by the first field belongs, and the link indicated by the first field; corresponds to one of the 5. The method according to any one of claims 1 to 4.

6. The method of claim 1 , wherein the first field is included in a multilink operation information element in the communication frame.

7. The method of claim 1 , wherein the second field is included in a TWT flow field in the communication frame.

8. 1. A multi-link communication method, the method comprising: receiving a communication frame, the communication frame including a first field and a second field, the first field indicating one link and the second field indicating to release a target wake time TWT agreement or TWT plan between multi-link devices; Terminating the TWT agreement or the TWT plan based on the communication frame; A method comprising:

9. The following combinations, each containing a TWT flow identifier: a combination of the TWT flow identifier, a media access control MAC address of a station on the link indicated by the first field, and a MAC address of a peer station on the link indicated by the first field, or a combination of the TWT flow identifier, a MAC address of a multilink device to which a transmitting end of the communication frame belongs, a MAC address of a multilink to which a receiving end of the communication frame belongs, and the link indicated by the first field; determining the TWT agreement based on any one of: The following combinations, each containing a broadcast TWT identifier: a combination of the broadcast TWT identifier and a media access control (MAC) address of an access station on the link indicated by the first field, or a combination of the broadcast TWT identifier, a MAC address of a multi-link device to which an access station on the link indicated by the first field belongs, and the link indicated by the first field; determining the TWT plan based on any one of the following: The method of claim 8 further comprising:

10. The step of canceling the TWT agreement or the TWT plan based on the communication frame includes:

2. The method of claim 1, further comprising: if the value of the second field is a first value, terminating all TWT agreements or plans on the link indicated by the first field.

11. The step of canceling the TWT agreement or the TWT plan based on the communication frame includes: If the value of the second field is a second value, canceling the TWT agreement corresponding to the combination including the TWT flow identifier on the link indicated by the first field; or If the value of the second field is a second value, canceling a TWT plan corresponding to the combination including the broadcast TWT identifier on the link indicated by the first field.

10. The method according to claim 8 or 9.

12. 12. The method of claim 8, wherein the first field is included in a multilink operation information element in the communication frame.

13. The method of claim 8 , wherein the second field is included in a TWT flow field in the communication frame.

14. A multi-link communication method in which a plurality of associated links are established between a multi-link device to which a transmitting end of a communication frame belongs and a multi-link device to which a receiving end of the communication frame belongs, the method comprising: generating the communication frame, the communication frame including instruction information, the instruction information instructing to terminate TWT agreements or TWT plans on the plurality of associated links established between the multi-link devices; transmitting the communication frame; A multi-link communication method comprising:

15. A multi-link communication method in which a plurality of associated links are established between a multi-link device to which a transmitting end of a communication frame belongs and a multi-link device to which a receiving end of the communication frame belongs, the method comprising: receiving the communication frame, the communication frame including instruction information, the instruction information instructing the multilink device to terminate a TWT agreement or a TWT plan on the plurality of associated links established between the multilink devices; based on the communication frame, canceling the TWT agreement or the TWT plan on the associated links established between the multi-link devices; A multi-link communication method comprising:

16. The method according to claim 14 or 15, wherein the value of the indication information is a first value.

17. 17. The method of claim 14, wherein the indication is included in a TWT flow field in the communication frame.

18. The TWT agreement comprises the following combinations, each of which includes a TWT flow identifier: a combination of the TWT flow identifier, a media access control (MAC) address of a station on the link indicated by the first field, and a MAC address of a peer station on the link indicated by the first field; or A combination of the TWT flow identifier, a MAC address of the multilink device to which the transmitting end of the communication frame belongs, a MAC address of the multilink to which the receiving end of the communication frame belongs, and a link indicated by a first field; corresponds to one of the The TWT plans may be any of the following combinations, each containing a broadcast TWT identifier: a combination of the Broadcast TWT identifier and a Media Access Control MAC address of an access station on the link indicated by the first field; or a combination of the broadcast TWT identifier, a MAC address of a multi-link device to which an access station on the link indicated by the first field belongs, and the link indicated by the first field; corresponds to one of the 18. The method of any one of claims 14 to 17.

19. A communication device comprising a unit configured to perform the method of any one of claims 1 to 18.

20. A communication device including a processor and a memory, the memory is configured to store instructions; The processor is configured to execute the instructions and to perform the method of any one of claims 1 to 18. Communication equipment.

21. A communication device including a logic circuit and an interface, the logic circuit coupled to the interface; A communications device, wherein the interface is configured to input and / or output code instructions, and the logic circuit is configured to execute the code instructions and to perform the method of any one of claims 1 to 18.

22. 20. A computer-readable recording medium configured to store a computer program that, when executed, performs the method of any one of claims 1 to 18.

23. A computer program which, when executed, performs the method of any one of claims 1 to 18.

24. A communication system comprising a transmitting end and a receiving end, wherein the transmitting end is configured to perform the method of any one of claims 1 to 7 and the receiving end is configured to perform the method of any one of claims 8 to 13, or the transmitting end is configured to perform the method of claim 14, 16, 17 or 18 and the receiving end is configured to perform the method of any one of claims 15 to 18.

Images