Non-simultaneous transmitting and receiving capability indication method, apparatus, and system

Abstract

To improve communication efficiency for a non-simultaneous transmitting and receiving capability indication method, an apparatus, and a system.SOLUTION: In the non-simultaneous transmitting and receiving capability indication method, a first multi-link device (MLD) transmits an association request frame and a management frame to a second MLD in sequence. The association request frame comprises first information that is used for indicating a first non-simultaneous transmitting and receiving (NSTR) capability between a first link and a second link. The management frame comprises second information that is used for indicating a second NSTR capability between the first link and the second link. The NSTR capability between links can be updated, such that the first MLD and the second MLD have a consistent understanding of the NSTR capability between the links.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001]

[0001] This application claims priority to Chinese Patent Application No. 202110485829.5 entitled "Method, Device and System for Indicating Non-Simultaneous Transmission and Reception Function," filed with the State Intellectual Property Office of the People's Republic of China on April 30, 2021, the entirety of which is incorporated herein by reference.

[0002]

[0002] Technical field This application relates to the field of communications, and more particularly to a method, apparatus, and system for indicating non-simultaneous transmit and receive capability. [Background technology]

[0003]

[0003] To achieve the technical goal of extremely high throughput, multi-link (ML) technology is used as one of the key technologies in the Institute of Electrical and Electronics Engineers (IEEE) 802.11be standard. A multi-link device (MLD) that supports ML has the ability to transmit and receive in multiple frequency bands to transmit data by using a larger bandwidth, thereby improving the throughput rate.

[0004]

[0004] As shown in Figure 1, an MLD may include multiple stations, and each station may establish a link with one station in another MLD for communication. In other words, two MLD devices can communicate with each other via multiple links. Among the multiple links, if the frequency spacing between two links is small, transmitting a signal on one link may affect receiving a signal on the other link. Therefore, transmission and reception cannot be performed simultaneously on the two links, i.e., non-simultaneous transmitting and receiving (NSTR) occurs between the two links.

[0005]

[0005] Currently, when a station in a non-access point MLD (i.e., non-AP MLD) initiates an association request to a station in an AP MLD, NSTR capability information is carried in the association request frame, which can indicate whether the link corresponding to the station is NSTR between another link in the non-AP MLD. Summary of the Invention

[0006]

[0006] The present application provides a non-simultaneous transmit / receive capability indication method, device, and system for updating NSTR capabilities between links so that both ends of a communication have a consistent understanding of the NSTR capabilities between the links, thereby improving communication efficiency.

[0007] According to a first aspect, a non-simultaneous transmission / reception capability indication method is provided. The method may be executed by a first MLD, or may be executed by a component within the first MLD, such as a processor, chip, or chip system of the first MLD, or may be implemented by a logic module or software capable of implementing all or part of the functions of the first MLD. In this application, an example in which the first MLD executes the method is used for explanation. The method includes the first MLD sending an association request frame to a second MLD and sending a management frame to the second MLD. The association request frame includes first information, which indicates a first non-simultaneous transmission / reception NSTR capability between the first link and the second link. The management frame includes second information, which indicates a second NSTR capability between the first link and the second link.

[0008]

[0008] Based on this solution, a first MLD can report a first NSTR capability and a second NSTR capability between a first link and a second link to a second MLD. Specifically, the first MLD can report the NSTR capability between the first link and the second link to the second MLD multiple times, so that the first MLD can timely notify the second MLD when the NSTR capability between the first link and the second link changes. In other words, the first MLD can indicate the updated NSTR capability between the first link and the second link to the second MLD. In this way, the first MLD and the second MLD can have a consistent understanding of the NSTR capability between the links, thereby improving communication efficiency.

[0009]

[0009] In one possible design, the first MLD transmitting a management frame to the second MLD includes: when a channel switch occurs, the first MLD transmitting a management frame to the second MLD, and the second NSTR capability is the NSTR capability between the first link and the second link after the channel switch.

[0010]

[0010] In one possible design, the first MLD transmitting a management frame to the second MLD includes: when a channel switch occurs and the first condition is not met, the first MLD transmitting a management frame to the second MLD, and the second NSTR capability is the NSTR capability between the first link and the second link after the channel switch.

[0011]

[0011] Based on the two possible designs mentioned above, in a channel switching scenario, the second MLD can know the NSTR capability after the channel switching, so that the first MLD and the second MLD can have a consistent understanding of the NSTR capability between links after the channel switching, thereby improving communication efficiency.

[0012]

[0012] In one possible design, the first condition includes at least one of: after channel switching, one of the frequency band accessed by the first link and the frequency band accessed by the second link is in the 2.4 GHz frequency band, and the other is in the 5 GHz or 6 GHz frequency band; before channel switching, there is STR between the first link and the second link, and after channel switching, the frequency spacing between the first link and the second link remains unchanged or becomes larger; or before channel switching, there is NSTR between the first link and the second link, and after channel switching, the frequency spacing between the first link and the second link remains unchanged or becomes smaller;

[0013]

[0013] Based on this possible design, the first condition in the above example relates to the frequency of the link. During the channel switching process, the second MLD can know the target channel after switching, so that the judgment of the first condition can also be performed by the second MLD. Therefore, when the first condition is met, the second MLD can know the NSTR capability between the first link and the second link after channel switching. In this scenario, the first MLD may not send a management frame, reducing signaling overhead.

[0014] In one possible design, the frequency spacing between the first link and the second link remaining unchanged or becoming larger after a channel change includes: after a channel change, the frequency spacing between the first link and the second link remaining unchanged or becoming larger, and the relative relationship between the frequencies of the first link and the second link remaining unchanged. The frequency spacing between the first link and the second link remaining unchanged or becoming smaller after a channel change includes: after a channel change, the frequency spacing between the first link and the second link remaining unchanged or becoming smaller, and the relative relationship between the frequencies of the first link and the second link remaining unchanged.

[0015]

[0015] In one possible design, the first MLD sending a management frame to the second MLD includes: the first MLD sending a management frame to the second MLD after a channel switch announcement is received but before the channel switch is performed, and the second NSTR capability is the NSTR capability between the first link and the second link after the channel switch.

[0016]

[0016] Based on this possible design, the first MLD can indicate to the second MLD before channel switching the NSTR capability between the first link and the second link after channel switching, so that the second MLD and the first MLD can communicate with each other as quickly as possible based on the NSTR capability after channel switching, thereby reducing communication delay.

[0017]

[0017] In one possible design, the management frame further includes third information, and the third information indicates that the second NSTR capability is the NSTR capability between the first link and the second link after channel switching.

[0018]

[0018] Based on a possible design, the second MLD can correctly understand the second NSTR capability, so that the second MLD does not understand the second NSTR capability as the NSTR capability before the channel switch.

[0019]

[0019] In one possible design, before the first MLD sends the management frame to the second MLD, the method further includes: the first MLD sending first operating mode control information to the second MLD, the first operating mode control information indicating that the channel bandwidth of the first link has changed and that the changed channel bandwidth is smaller than the channel bandwidth before the change.

[0020]

[0020] In one possible design, after the first MLD sends the management frame to the second MLD, the method further includes: the first MLD sending second operating mode control information to the second MLD, the second operating mode control information indicating that the channel bandwidth of the first link has changed and that the changed channel bandwidth is greater than the channel bandwidth before the change.

[0021]

[0021] Based on the two possible designs mentioned above, communication failures caused by the first MLD and the second MLD having different understandings of the NSTR capabilities between the first link and the second link can be avoided to the greatest extent possible.

[0022] According to a second aspect, a non-simultaneous transmission / reception capability indication method is provided. The method may be executed by a second MLD, or may be executed by a component within the second MLD, such as a processor, chip, or chip system of the second MLD, or may be implemented by a logic module or software capable of implementing all or part of the functions of the second MLD. In this application, an example in which the second MLD executes the method is used for explanation. The method includes the second MLD receiving an association request frame from a first MLD and a management frame from the first MLD. The association request frame includes first information, which indicates a first non-simultaneous transmission / reception NSTR capability between the first link and the second link. The management frame includes second information, which indicates a second NSTR capability between the first link and the second link. For technical effects provided by the second aspect, please refer to the technical effects provided by the first aspect. The details will not be explained again here.

[0023] In one possible design, a channel switch occurs before the second MLD receives a management frame from the first MLD. The method further includes: the second MLD determining that there is an NSTR between the first link and the second link in a first time interval, the first time interval being the time interval from when the channel switch occurs to when the management frame is received; if a second condition is met, the second MLD determining that there is an NSTR between the first link and the second link in the first time interval; or if a third condition is met, the second MLD determining that there is an NSTR between the first link and the second link in the first time interval.

[0024] In one possible design, the second condition includes at least one of: after the channel change, one of the frequency band accessed by the first link and the frequency band accessed by the second link is in the 2.4 GHz frequency band, and the other is in the 5 GHz or 6 GHz frequency band; or before the channel change, there is a STR between the first link and the second link, and after the channel change, the frequency spacing between the first link and the second link remains unchanged or becomes larger; The third condition includes: before the channel change, there is a NSTR between the first link and the second link, and after the channel change, the frequency spacing between the first link and the second link remains unchanged or becomes smaller;

[0025] In one possible design, the frequency spacing between the first link and the second link remaining unchanged or becoming larger after a channel change includes: after a channel change, the frequency spacing between the first link and the second link remaining unchanged or becoming larger, and the relative relationship between the frequencies of the first link and the second link remaining unchanged. The frequency spacing between the first link and the second link remaining unchanged or becoming smaller after a channel change includes: after a channel change, the frequency spacing between the first link and the second link remaining unchanged or becoming smaller, and the relative relationship between the frequencies of the first link and the second link remaining unchanged.

[0026]

[0026] In one possible design, the second MLD receiving a management frame from the first MLD includes: the second MLD receiving a management frame from the first MLD after a channel switch announcement is sent but before a channel switch is performed, and the second NSTR capability is the NSTR capability between the first link and the second link after the channel switch.

[0027]

[0027] In one possible design, the management frame further includes third information, which indicates that the second NSTR capability is the NSTR capability between the first link and the second link after channel switching.

[0028]

[0028] In one possible design, before the second MLD receives the management frame from the first MLD, the method further includes: the second MLD receiving first operating mode control information from the first MLD, the first operating mode control information indicating the channel bandwidth of the first link, and the changed channel bandwidth being smaller than the channel bandwidth before the change.

[0029]

[0029] In one possible design, after the second MLD receives the management frame from the first MLD, the method further includes: the second MLD receiving second operating mode control information from the first MLD, the second operating mode control information indicating that the channel bandwidth of the first link has changed and the changed channel bandwidth is greater than the channel bandwidth before the change.

[0030]

[0030] For the technical effects brought about by any possible design in the second aspect, please refer to the technical effects brought about by the corresponding design in the first aspect, and the details will not be described again here.

[0031]

[0031] In relation to the first aspect or the second aspect, in one possible design, the management frame includes a multi-link element, the second information is carried in the multi-link element, and the multi-link element is a basic variant multi-link element or an update variant multi-link element.

[0032]

[0032] In one possible design related to the first or second aspect, the multi-link element is a basic variant multi-link element, and the basic variant multi-link element includes a multi-link control field and a link information field.

[0033]

[0033] The multi-link control field includes a first field, the first field is set to 0, and the first field includes at least one of: a multi-link device medium access control address presence field, a link identifier information presence field, a change sequence presence field, a multi-link device capability presence field, or an enhanced multi-link single radio frequency EMLSR capability presence field.

[0034]

[0034] The link information field includes an NSRT indication bitmap field. Secondary information is carried in the NSTR indication bitmap field. The link information field includes a second field. The second field is set to 0. The second field includes at least one of: a completed profile field, a medium access control address present field, a beacon interval present field, or a delivery traffic indication map DTIM information present field.

[0035]

[0035] In one possible design related to the first or second aspect, the multi-link element is an update variant multi-link element, and the update variant multi-link element includes a multi-link control field and a link information field.

[0036]

[0036] The multi-link control field includes a type field. The type field is set to a first value. The multi-link control field does not include a first field. The first field includes at least one of: a multi-link device medium access control address present field, a link identifier information present field, a change sequence present field, a multi-link capability present field, or an EMLSR capability present field.

[0037]

[0037] The link information field includes an NSRT indication bitmap field. Secondary information is carried in the NSTR indication bitmap field. The link information field does not include a secondary field. The secondary field includes at least one of: a completed profile field, a station medium access control address present field, a beacon interval present field, or a DTIM information present field.

[0038]

[0038] In one possible design related to the first or second aspect, the link information field further includes an NSTR link pair presence field and an NSTR bitmap size field, where the NSTR link pair presence field indicates that the link information field includes an NSTR indication bitmap field, and the NSTR bitmap size field indicates the size of the NSTR indication bitmap field.

[0039]

[0039] Regarding the first aspect or the second aspect, in one possible design, the management frame includes a third field, where a value of the third field, when set to the first value, indicates that the management frame is used to update NSTR capabilities between the first link and the second link.

[0040]

[0040] Based on this possible design, the capabilities of the management frame can be indicated to the second MLD, so that the second MLD can correctly interpret the management frame and obtain the second NSTR capability between the first link and the second link.

[0041]

[0041] According to a third aspect, there is provided a communication device for implementing the aforementioned method. The communication device may be the first MLD in the first aspect, a device including the first MLD, or a device included in the first MLD, such as a chip; or the communication device may be the second MLD in the second aspect, a device including the second MLD, or a device included in the second MLD, such as a chip. The communication device includes corresponding modules, units, or means for implementing the aforementioned method. The modules, units, or means may be implemented by hardware, software, or hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned functions.

[0042]

[0042] In one possible design, the communication device may include a transmitting module and / or a receiving module. Further, the communication device may include a processing module. The transmitting module may be configured to implement a transmitting-type function in any one of the aforementioned aspects and any one of the possible designs of the aforementioned aspects. The receiving module may be configured to implement a receiving-type function in any one of the aforementioned aspects and any one of the possible designs of the aforementioned aspects. The processing module may be configured to implement a processing function in any one of the aforementioned aspects and any one of the possible designs of the aforementioned aspects.

[0043]

[0043] According to a fourth aspect, there is provided a communications device. The device includes a processor and a memory. The memory is configured to store computer instructions. When the processor executes the instructions, the communications device is capable of performing a method according to any one of the preceding aspects. The communications device may be the first MLD of the first aspect, a device including the first MLD, or a device included in the first MLD, such as a chip; or the communications device may be the second MLD of the second aspect, a device including the second MLD, or a device included in the second MLD, such as a chip.

[0044]

[0044] According to a fifth aspect, there is provided a communication device. The communication device includes a processor and a communication interface. The communication interface is configured to communicate with a module other than the communication device. The processor is configured to execute a computer program or instructions such that the communication device performs a method according to any one of the preceding aspects. The communication device may be the first MLD of the first aspect, a device including the first MLD, or a device included in the first MLD, such as a chip; or the communication device may be the second MLD of the second aspect, a device including the second MLD, or a device included in the second MLD, such as a chip.

[0045]

[0045] According to a sixth aspect, there is provided a communication device. The communication device includes a logic circuit and an interface circuit. The interface circuit is configured to input information and / or output information. The logic circuit is configured to perform the method of any one of the preceding aspects to process the input information and / or generate output information. The communication device may be the first MLD of the first aspect, a device including the first MLD, or a device included in the first MLD, such as a chip; or the communication device may be the second MLD of the second aspect, a device including the second MLD, or a device included in the second MLD, such as a chip.

[0046]

[0046] Regarding the sixth aspect, in an implementation of the sixth aspect, the communication device may be configured to implement functionality of a first MLD.

[0047]

[0047] In one possible design, the input information is an association request frame and a management frame, the association request frame includes first information, the first information indicating a first NSTR capability between the first link and the second link, and the management frame includes second information, the second information indicating a second NSTR capability between the first link and the second link.

[0048]

[0048] In one possible design, the input information is first operating mode control information, which indicates that the channel bandwidth of the first link has changed and that the changed channel bandwidth is smaller than the channel bandwidth before the change.

[0049]

[0049] In one possible design, the input information is second operating mode control information, which indicates that the channel bandwidth of the first link has changed and that the changed channel bandwidth is larger than the channel bandwidth before the change.

[0050]

[0050] Regarding the sixth aspect, in an implementation of the sixth aspect, the communication device may be configured to implement functionality of a second MLD.

[0051]

[0051] In one possible design, the output information is an association request frame and a management frame, the association request frame including first information, the first information indicating a first NSTR capability between the first link and the second link, and the management frame including second information, the second information indicating a second NSTR capability between the first link and the second link.

[0052]

[0052] In one possible design, the output information is first operating mode control information, which indicates that the channel bandwidth of the first link has changed and that the changed channel bandwidth is smaller than the channel bandwidth before the change.

[0053]

[0053] In one possible design, the output information is second operating mode control information, which indicates that the channel bandwidth of the first link has changed and that the changed channel bandwidth is larger than the channel bandwidth before the change.

[0054]

[0054] According to a seventh aspect, there is provided a communication device. The communication device includes an interface circuit and a processor. The interface circuit is a code / data read / write interface circuit. The interface circuit is configured to receive computer-executable instructions (the computer-executable instructions may be stored in a memory and directly read from the memory, or may be read or retrieved via another component) and transmit the computer-executable instructions to the processor. The processor is configured to execute the computer-executable instructions, such that the communication device performs the method according to any one of the preceding aspects. The communication device may be the first MLD of the first aspect, a device including the first MLD, or a device included in the first MLD, such as a chip; or the communication device may be the second MLD of the second aspect, a device including the second MLD, or a device included in the second MLD, such as a chip.

[0055]

[0055] According to an eighth aspect, there is provided a communication device. The communication device includes at least one processor. The processor is configured to execute a computer program or instructions such that the communication device performs a method according to any one of the preceding aspects. The communication device may be the first MLD of the first aspect, a device including the first MLD, or a device included in the first MLD, such as a chip; or the communication device may be the second MLD of the second aspect, a device including the second MLD, or a device included in the second MLD, such as a chip.

[0056] In one possible design, the communication device includes a memory configured to store necessary computer programs or instructions, and the memory may be coupled to the processor or may be separate from the processor.

[0057] In one possible design, the communications device may be a chip or a chip system. When the device is a chip system, the chip system may include the chip, or may include the chip and other discrete devices.

[0058] According to a ninth aspect, there is provided a computer-readable storage medium having stored thereon a computer program or instructions which, when executed by a processor, perform a method according to any one of the preceding aspects.

[0059]

[0059] According to a tenth aspect, there is provided a computer program product which, when executed by a processor, performs a method according to any one of the preceding aspects.

[0060]

[0060] When the communication device according to any one of the third to tenth aspects is a chip, it can be understood that the operation / function of transmitting may be understood as outputting information, and the operation / function of receiving may be understood as inputting information.

[0061]

[0061] For the technical effects provided by any one of the designs of the third to tenth aspects, please refer to the technical effects provided by the various designs of the first or second aspects, and the details will not be described again here.

[0062] According to an eleventh aspect, there is provided a communication system, the communication system including a first MLD and a second MLD according to the previous aspect. [Brief explanation of the drawings]

[0063] [Figure 1]

[0063] Figure 1 is a schematic diagram of a multi-link device communication scenario according to the present application. [Figure 2]

[0064] FIG. 2 is a schematic diagram of a two-link non-duplex transmit-receive communication scenario according to the present application. [Figure 3]

[0065] FIG. 3 is a schematic diagram of the frame structure of a basic variant multi-link element according to the present application. [Figure 4]

[0066] FIG. 4 is a schematic diagram of the architecture of a communication system according to the present application. [Figure 5]

[0067] FIG. 5 is a schematic diagram of the structure of a WLAN device according to the present application. [Figure 6]

[0068] FIG. 6 is a schematic flow chart of a non-simultaneous transmit and receive capability indication method according to the present application. [Figure 7]

[0069] Figure 7 is a schematic diagram of the structure of the action frame according to the present application. [Figure 8]

[0070] FIG. 8 is a schematic diagram of a frame structure of a multi-link element according to the present application. [Figure 9]

[0071] FIG. 9 is a schematic diagram of a frame structure of a multi-link element according to the present application. [Figure 10]

[0072] FIG. 10 is a schematic flow chart of a non-simultaneous transmit and receive capability indication method according to the present application. [Figure 11]

[0073] FIG. 11 is a schematic flow chart of a non-simultaneous transmit and receive capability indication method according to the present application. [Figure 12]

[0074] FIG. 12 is a schematic diagram of the structure of the first MLD according to the present application. [Figure 13]

[0075] FIG. 13 is a schematic diagram of the structure of a second MLD according to the present application. [Figure 14]

[0076] FIG. 14 is a schematic diagram of the structure of a communication device according to the present application. DETAILED DESCRIPTION OF THE INVENTION

[0064]

[0077] Unless otherwise stated, " / " in the description of the embodiments of the present application represents an "or" relationship between related objects. For example, A / B may represent A or B. In the present application, "and / or" only describes a relationship to describe related objects, and represents that three relationships may exist. For example, A and / or B may represent the following three cases: only A exists, both A and B exist, and only B exists. A and B may be singular or plural.

[0065]

[0078] In the description of this application, unless otherwise stated, "plurality" means two or more than two. The term "at least one" or similar expressions refers to any combination of those items, including a singular item or any combination of multiple items. For example, "at least one" of a, b, or c can refer to a, b, c, ab, ac, bc, or abc, where a, b, and c can be singular or plural.

[0066]

[0079] Furthermore, in order to clearly describe the technical solutions in the embodiments of the present application, terms such as "first" and "second" are used in the embodiments of the present application to distinguish between identical or similar items that basically provide the same function or purpose. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity or execution order, and terms such as "first" and "second" do not indicate a clear distinction. Furthermore, in the embodiments of the present application, words such as "example" or "for example" are used to represent providing an example, illustration, or explanation. Any embodiment or design scheme described as an "example" or "for example" in the embodiments of the present application should not be described as being preferred or having more advantages than another embodiment or design scheme. Rather, the use of words such as "example" or "for example" is intended to present a relative concept in a specific way for ease of understanding.

[0067]

[0080] It can be understood that the term "embodiment" used throughout the specification means that a particular feature, structure, or characteristic associated with an embodiment is included in at least one embodiment of the present application. Therefore, embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in one or more embodiments by using any suitable method. It can be understood that the order of the processes described above does not imply the order of execution in various embodiments of the present application. The order of execution of the processes should be determined based on the functions and internal logic of the processes and should not be interpreted as any limitation on the implementation process of the embodiments of the present application.

[0068]

[0081] In this application, it can be understood that "when" and "if" mean that the corresponding process is performed in an objective situation, and are not intended to be time-limited, do not require actions to be determined at the time of implementation, and do not imply any other limitations.

[0069]

[0082] It can be understood that "predefined" in this application may also be understood as "define," "predefine," "store," "prestore," "prenegotiate," "pre-build," "embedded," or "pre-burned."

[0070]

[0083] It can be understood that in some scenarios, some optional features in the embodiments of the present application can be implemented independently to solve corresponding technical problems and achieve corresponding effects without relying on other features, such as the solutions on which the optional features are currently based. Alternatively, in some scenarios, optional features can be combined with other features based on requirements. Correspondingly, the devices provided in the embodiments of the present application can also implement these features or functions accordingly. Details will not be described here.

[0071]

[0084] In this application, unless otherwise stated, the same or similar parts of the embodiments shall be referred to each other. In the embodiments and implementations / implementation methods of the embodiments of this application, unless otherwise stated or a logical contradiction occurs, the terms and / or descriptions shall be consistent and may be mutually referenced between different embodiments and between implementations / implementation methods of the embodiments. The technical features in different embodiments and implementations / implementation methods of the embodiments may be combined to form new embodiments, implementations, or implementation methods according to their internal logical relationships. The following implementations of this application are not intended to limit the protection scope of this application.

[0072]

[0085] In order to facilitate understanding of the technical solutions in the embodiments of the present application, first, the technologies related to the present application are briefly described as follows:

[0086] 1. Multi-Link (ML):

[0087] The technical objective of the development and advancement of cellular networks and wireless local area networks (WLANs) is to continuously increase throughput. WLAN system protocols are primarily discussed in the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standardization group. Standards such as 802.11a / b / g / n / ac / ax are constantly improving the throughput rate of WLAN systems. The next-generation standard, IEEE 802.11be, is called the extremely high throughput (EHT) standard, and its primary technical objective is to significantly improve peak throughput rates.

[0073]

[0088] To achieve the technical goal of ultra-high throughput, IEEE 802.11be uses Multi-Layer Link (ML) as one of its key technologies. The core idea is that WLAN devices supporting the next-generation IEEE 802.11 standard will have multi-band transmission and reception capabilities, resulting in a wider bandwidth available for data transmission. This significantly improves throughput. The spatial path for access and data transmission in one frequency band can be referred to as a link. Therefore, access and transmission in multiple frequency bands is ML. Furthermore, multiple links reduce latency and improve robustness.

[0074]

[0089] For example, the plurality of frequency bands may include, but are not limited to, the 2.4 GHz (GHz) wireless fidelity (Wi-Fi) frequency band, the 5 GHz Wi-Fi frequency band, and the 6 GHz Wi-Fi frequency band.

[0075]

[0090] Furthermore, the access frequency bands of different links may be the same, i.e., different links may be located in the same frequency band, in which case different links can access different channels of the same frequency band and perform data transmission on different channels.

[0076]

[0091] 2. Multi-link device (MLD)

[0092] A multi-link device may be a WLAN device that supports multiple links simultaneously. In other words, a multi-link device has the ability to transmit and receive on multiple frequency bands. Compared with a device that only supports single-link transmission, a multi-link device has higher transmission efficiency and higher throughput.

[0077]

[0093] It should be noted that a multi-link device may also be referred to as a multi-band device. Of course, a multi-link device may have other names, and this is not particularly limited in this application.

[0078]

[0094] A multi-link device includes at least two affiliated stations (access point stations, STAs), which may be access point stations (AP STAs) or non-access point stations (non-AP STAs).

[0079]

[0095] For ease of explanation, in this application, a multi-link device whose affiliated stations are AP STAs will be referred to as an AP multi-link device (AP MLD), a multi-link AP, or a multi-link AP device, and a multi-link device whose affiliated stations are non-AP STAs will be referred to as a non-AP multi-link device (non-AP MLD), a multi-link STA, a multi-link STA device, or a STA multi-link device (STA MLD).

[0080]

[0096] A STA in a multi-link device may establish a link with a STA in another multi-link device for communication purposes, see the schematic diagram shown in Figure 1.

[0081]

[0097] Multi-link devices can be classified as simultaneous transmitting and receiving (STR) multi-link devices (STR MLD) and non-simultaneous transmitting and receiving (NSTR) multi-link devices (non-STR MLD). WLAN systems that include non-STR MLD may be referred to as non-STR multi-link systems.

[0082]

[0098] At least two links in a non-STR MLD cannot perform simultaneous transmission and reception. For example, as shown in Figure 2, in the multiple links established between a non-STR MLD and another multi-link device, if the frequency spacing between Link 1 and Link 2 is small, when the time to transmit a block acknowledgement (BA) 2 for a physical protocol data unit (PPDU) 2 on Link 2 overlaps with the time to receive PPDU 1 on Link 1, the energy leaked to Link 1 during the process of transmitting BA 2 on Link 2 will interfere with the reception of PPDU 1 on Link 1. Therefore, the reception of PPDU 1 will be affected.

[0083]

[0099] 3. Association Request

[0100] When a non-AP MLD accesses the network, a station in the non-AP MLD may initiate an association request to an AP MLD station to access the WLAN. In this process, a station in the non-AP MLD may send an association request frame, where the association request frame may include a basic variant multi-link element, and the basic variant multi-link element may indicate whether simultaneous transmission and reception can be performed across multiple links in the non-AP MLD.

[0084]

[0101] In one example, the frame structure of a basic variant multi-link element may be as shown in Figure 3. See Figure 3. The basic variant multi-link element includes an element identifier (element ID) field, a length field, an element ID extension field, a multi-link control field, a common info field, and a link info field.

[0085]

[0102] The Element Identifier field and Element Identifier Extension field are used to identify a basic variant multi-link element. The Element Identifier field and Element Identifier Extension field of different basic variant multi-link elements are different. Typically, the Element Identifier field may be set to 255 and the Element Identifier Extension field is set to a value not used by another basic variant multi-link element. The Length field indicates the length of the basic variant multi-link element.

[0086]

[0103] The Multilink Control field carries multilink control information and may include a Type field, a Reserved field, and a Presence Bitmap field. The Presence Bitmap field may contain one or more Presence fields. For example, the Presence Bitmap field may contain the following: a Multi-Link Device Media Access Control (MAC) Address Present field indicating whether an MLD MAC Address field is present in the Common Information field; a Link ID Info Present field indicating whether a Link ID Info field is present in the Common Information field; A Change Sequence Present field indicating whether a Change Sequence field is present in the Common Information field; an MLD Capabilities Present field indicating whether a multi-link device capabilities field is present in the common information field, where the multi-link device capabilities field includes a Maximum Number Of Simultaneous Links field, a single response scheduling (SRS) Support field, and a Reserved field; and An enhanced multi-link single radio (EMLSR) Capabilities Present field that indicates whether an EMLSR capabilities field is present in the common information field, where the EMLSR capabilities field includes an EMLSR Support field, an EMLSR Delay field, and a Reserved field.

[0087]

[0104] The common information fields may further include to be determined (TBD) fields in addition to the fields indicated by the presence fields.

[0088]

[0105] The Link Information field carries link information and may contain a Per-STA Profile sub-element, which may have a one-to-one correspondence with stations in a multi-link device. Optionally, the Link Information field may further contain a Vendor Specific sub-element.

[0089]

[0106] The per-STA profile subelement may contain a Subelement ID field, a Length field, a Station Control field, a Station Info field, and a Station Profile field. The Station Profile field may contain zero or more Elements.

[0090]

[0107] The Subelement Identifier field identifies the per-STA profile subelement and is normally set to 0. The Length field indicates the length of the per-STA profile subelement.

[0091]

[0108] The station control field may contain: a link identifier (Link ID) field that identifies the link corresponding to the per-STA profile sub-element that contains the station control field; A Complete Profile field that indicates whether the Basic Variant Multi-Link element contains complete information for the link corresponding to the per-STA Profile subelement; MAC Address Present, indicating whether the STA MAC Address field is present in the Station Information field; a Beacon Interval Present field indicating whether a Beacon Interval field is present in the Station Information field; a delivery traffic indication map (DTIM) information present field indicating whether a DTIM count field and a DTIM period field are present in the station information field; an NSTR Link Pair Present field that indicates whether an NSTR Indication Bitmap field is present in the Station Information field, the NSTR Indication Bitmap field being capable of indicating whether simultaneous transmission and reception are possible on the link corresponding to the per-STA profile subelement in which the NSTR Indication Bitmap field is located and on other links; and An NSTR Bitmap Size field that indicates the size of the NSTR Indication Bitmap field, if present in the Station Information field, and the size of the NSTR Indication Bitmap field may be, for example, 8 bits or 16 bits.

[0092]

[0109] With respect to the aforementioned presence field, when the presence field is set to 1, it generally indicates that the field indicated by the presence field is present; when the presence field is set to 0, it generally indicates that the field indicated by the presence field is not present.

[0093]

[0110] It should be noted that the "Present field" in this application may also be referred to as the "Presence field," and the terms "Present field" and "Presence field" may be used interchangeably. This is not a limitation of this application.

[0094]

[0111] The above describes the frame structure of the Basic Variant Multi-Link element and the function of some fields. For descriptions of other fields, please refer to the definitions in the IEEE 802.11be standard. Details will not be provided here.

[0095]

[0112] 4.Channel switch:

[0113] During basic service set (BSS) operation, an AP may initiate a channel switch due to some reason (e.g., strong interference in the original channel or discovery of a radar satellite channel).

[0096]

[0114] For example, a channel switch may involve switching a link from a channel in one frequency band to a channel in another frequency band; or may involve switching a link from a channel in one frequency band to another channel in that frequency band. In the case of a multi-link device, the channel switches for multiple stations included in the multi-link device are independent. For example, a channel switch may be performed for some stations in the multi-link device but not for other stations.

[0097]

[0115] In the process of initiating a channel switch, an AP typically sends a Channel Switch Announcement element or an Extended Channel Switch Announcement element to non-APs several DTIM beacon cycles beforehand to inform the non-APs of the time and target channel of the channel switch. The Channel Switch Announcement element or Extended Channel Switch Announcement element may be carried in a beacon frame. When the time for the channel switch arrives, the AP and associated non-APs switch to the target channel.

[0098]

[0116] 5. Operating mode (OM) control:

[0117] The IEEE 802.11ax standard defines an Operating Mode Control subfield, which may be used by a transmitting station to change operating parameters such as the channel bandwidth and number of spatial streams of the transmitting station.

[0099]

[0118] Generally, when a transmitting station intends to change its operating parameters from high-capability parameters to low-capability parameters, the parameters change after the end of a transmission opportunity (TXOP) during which the transmitting station receives an acknowledgement frame. The acknowledgement frame is an acknowledgement frame corresponding to a frame carrying an operating mode control subfield. In other words, the transmitting station changes its parameters after confirming that an acknowledgement frame corresponding to the operating mode control subfield has been received.

[0100]

[0119] If the transmitting station intends to change its operating parameters from low-capability parameters to high-capability parameters, the parameters change after the TXOP for transmitting the operating mode control subfield ends. In other words, after the transmitting station transmits a frame carrying the operating mode control subfield, even if the transmitting station does not correctly receive the acknowledgement frame for that frame, the transmitting station needs to change its parameters after the TXOP for transmitting the operating mode control subfield ends. The reason the transmitting station does not correctly receive the acknowledgement frame may be that the receiving station transmits an acknowledgement frame after receiving the frame carrying the operating mode control subfield, but the acknowledgement frame is not correctly received due to interference or another reason. In this case, the receiving station may think that the transmitting station has changed its parameters to high-capability parameters, so the receiving station can communicate with the transmitting station by using the high-capability parameters. Because this case is possible, the transmitting station needs to change its parameters after the TXOP for transmitting the operating mode control subfield ends, regardless of whether the transmitting station correctly receives the acknowledgement frame.

[0101]

[0120] For example, the above parameter may be a bandwidth. A high-capacity parameter may refer to a large bandwidth, and a low-capacity parameter may refer to a small bandwidth. It will be understood that the large bandwidth and the small bandwidth in this case correspond to the bandwidth before and after the parameter is changed.

[0102]

[0121] As explained in the Background section, currently, when a non-AP MLD station initiates an association request to an AP MLD station, the non-AP MLD station reports to the AP MLD whether simultaneous transmission and reception is possible on the link. Reporting NSTR capability between links in other scenarios has not been discussed.

[0103]

[0122] Based on this, the present application provides an information transmission and reception method, which can be used to exchange non-simultaneous transmission and reception capabilities between links after a non-AP MLD accesses a network, so that the non-AP MLD and the AP MLD have a consistent understanding of the non-simultaneous transmission and reception capabilities between links, thereby improving communication efficiency.

[0104]

[0123] The methods provided in the present application are applicable to WLAN scenarios, such as IEEE 802.11 system standards, such as 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, or next-generation 802.11ax standards, such as 802.11be or further next-generation standards. Alternatively, embodiments of the present application are applicable to wireless local area network systems, such as internet of things (IoT) networks or vehicle-to-X (V2X) systems. It is evident that the embodiments of the present application are also applicable to other possible communication systems, such as a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, and future 5th generation (5G) communication systems.

[0105]

[0124] The communication systems applicable to the present application are merely examples for explanation, and the communication systems applicable to the present application are not limited thereto, which have been similarly described in the present application, and the details will not be described again below.

[0106]

[0125] 4 is a WLAN communication system provided in the present application to which the embodiments of the present application are applied. The WLAN communication system includes a first MLD 401 and a second MLD 402.

[0107]

[0126] A plurality of links are established between the first MLD 401 and the second MLD 402. In the following embodiments of the present application, an example in which the plurality of links between the first MLD 401 and the second MLD 402 include a first link and a second link is used for illustration.

[0108]

[0127] In a possible implementation, in the present application, the first MLD 401 is a non-AP MLD and the second MLD 402 is an AP MLD. In this scenario, the first MLD may be a non-AP MLD associated with the second MLD.

[0109]

[0128] In another possible implementation, in the present application, the first MLD 401 is a non-AP MLD and the second MLD 402 is a non-AP MLD.

[0110]

[0129] The non-AP MLD in this application may be a wireless communication chip, a wireless sensor, or a wireless communication terminal. Examples of a non-AP MLD may be a Wi-Fi-enabled user terminal, user equipment, access device, subscriber station, subscriber unit, mobile station, user agent, and user device. A user terminal may be any one of a variety of devices capable of wireless communication, such as a handheld device, an in-vehicle device, a wearable device, an Internet of Things (IoT) device, a computing device, another processing device connected to a wireless modem, and various forms of user equipment (UE), mobile station (MS), terminal, terminal equipment, portable communication device, handheld device, portable computing device, entertainment device, gaming device or system, global positioning system device, or any other suitable device configured for network communication over a wireless medium. Furthermore, a non-AP MLD may support the 802.11be standard or its next-generation WLAN standard. Non-AP MLD may also support multiple WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0111]

[0130] In an embodiment of the present application, an AP MLD may be a device deployed in a wireless communication network to provide wireless communication capabilities to non-APs associated with the AP MLD. AP MLDs are primarily deployed in homes, buildings, and campuses, with a typical coverage radius ranging from tens to hundreds of meters. Of course, AP MLDs may alternatively be deployed outdoors. The AP MLD is equivalent to a bridge connecting a wired network and a wireless network. The main function of the AP MLD is to connect various wireless network clients to each other and then connect the wireless network to an Ethernet. Specifically, the AP MLD may be a communication device with a Wi-Fi chip, such as a base station, router, gateway, repeater, communication server, switch, or bridge. Base stations may include various types, such as macro base stations, micro base stations, and relay stations. Furthermore, the AP MLD may support the 802.11be standard or the next-generation WLAN standard of the 802.11be standard. AP MLD may also support WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0112]

[0131] In some embodiments, the AP MLD and non-AP MLD in this application may be collectively referred to as a WLAN device. In a specific implementation, the WLAN device may use the organizational structure shown in Figure 5 or may include the components shown in Figure 5.

[0113]

[0132] 5 is a schematic diagram of a WLAN device 500 according to the present application. The WLAN device 500 may be a non-AP MLD, a chip within a non-AP MLD, or a chip system (also referred to as a system-on-chip), or an AP MLD, a chip within an AP MLD, or a chip system (also referred to as a system-on-chip). In an embodiment of the present application, the chip system may include a chip, or may include a chip and other discrete components.

[0114]

[0133] 5, the WLAN device 500 includes a processor 501 and a transceiver 502. Furthermore, the WLAN device 500 may further include a memory 504. The processor 501, the memory 504, and the transceiver 502 may be connected via a communication line 503.

[0115]

[0134] The processor 501 may be a central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. Alternatively, the processor 501 may be another device having processing capabilities, such as, but not limited to, a circuit, a component, or a software module.

[0116]

[0135] The transceiver 502 is configured to communicate with another device or another communication network, which may be an Ethernet, a radio access network (RAN), a WLAN, etc. The transceiver 502 may be a module, a circuit, a transceiver, or any device capable of implementing communications.

[0117]

[0136] The communication lines 503 are configured to transmit information between components included in the WLAN device 500 .

[0118]

[0137] The memory 504 is configured to store computer programs or instructions.

[0119]

[0138] Memory 504 may be read-only memory (ROM) or another type of static storage device capable of storing static information and / or instructions, random access memory (RAM) or another type of dynamic storage device capable of storing information and / or instructions, or may be, without limitation, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other compact disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disc storage media, or another magnetic storage device.

[0120]

[0139] It should be noted that the memory 504 may be independent of the processor 501 or may be integrated with the processor 501. The memory 504 may be configured to store instructions, program codes, some data, etc. The memory 504 may be located within the WLAN device 500 or may be located outside the WLAN device 500. This is not limited thereto. The processor 501 is configured to execute instructions stored in the memory 504 to implement the methods provided in the following embodiments of the present application.

[0121]

[0140] In one example, processor 501 may include one or more CPUs, for example, CPU 0 and CPU 1 in FIG.

[0122]

[0141] In an optional implementation, the WLAN device 500 includes multiple processors. For example, in addition to the processor 501 of FIG.

[0123]

[0142] In an optional implementation, the WLAN device 500 further includes an output device 505 and an input device 506. The input device 506 is a device such as a keyboard, a mouse, a microphone, or a joystick, and the output device 505 is a device such as a display screen or a speaker.

[0124]

[0143] It will be understood that the organizational structure shown in Figure 5 does not constitute a limitation on a WLAN device. In addition to the components shown in Figure 5, a WLAN device may include more or fewer components than those shown in the figure, combine some components, or have a different component arrangement.

[0125]

[0144] The above describes the communication system and WLAN device provided in the present application. Hereinafter, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application.

[0126]

[0145] It should be noted that in the following embodiments of the present application, the names of messages, parameters, information, etc. between devices are merely examples, and other names may be used in other embodiments, which are not limited in the manner provided in the present application.

[0127]

[0146] It will be understood that in the embodiments of the present application, the first MLD and / or the second MLD may perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples. Other operations or variations of various operations may also be performed in the embodiments of the present application. Furthermore, steps may be performed in a different order than presented in the embodiments of the present application, and not all operations in the embodiments of the present application need be performed.

[0128]

[0147] 6 is a schematic flowchart of an information transmitting and receiving method according to an embodiment of the present application. In the following, an example is used in which the method provided in this embodiment of the present application is applied to the application scenario shown in FIG. 4, and the link between the first MLD and the second MLD includes a first link and a second link. Of course, the embodiment of the present application may be applied to other possible communication scenarios or communication systems. For example, in a scenario of reporting NSTR capabilities between links, the reporting may be performed by using the method provided in the embodiment of the present application.

[0129]

[0148] It should be noted that in the following embodiments of the present application, the interaction between the first MLD and the second MLD may actually be an interaction between a station associated with the first MLD and a station associated with the second MLD. The station may be a station corresponding to any enabled link between the first MLD and the second MLD. For example, the interaction between the first MLD and the second MLD may be an interaction between a station corresponding to a first link in the first MLD and a station corresponding to a first link in the second MLD. For ease of explanation, the following embodiments of the present application use the interaction between the first MLD and the second MLD as an illustrative method. In fact, the interaction may alternatively be an interaction between a station associated with the first MLD and a station associated with the second MLD.

[0130]

[0149] Specifically, as shown in FIG. 6, the information transmitting and receiving method provided in this application includes the following steps:

[0131]

[0150] S601: A first MLD transmits an association request frame to a second MLD. In response, the second MLD receives an association request frame from the first MLD.

[0132]

[0151] The association request frame includes first information, and the first information indicates a first NSTR capability between the first link and the second link.

[0133]

[0152] For example, if the first MLD is a non-AP MLD and the second MLD is an AP MLD, the first NSTR capability is the NSTR capability between the first link and the second link in the association process.

[0134]

[0153] In a possible implementation, the association request frame may include a basic variant multi-link element, and the first information may be carried in an NSTR indication bitmap field in the basic variant multi-link element. For the frame structure of the basic variant multi-link element, please refer to Figure 3 and the corresponding description of Figure 3. Details will not be described again here.

[0135]

[0154] S602: The first MLD transmits a management frame to the second MLD, and in response, the second MLD receives a management frame from the first MLD.

[0136]

[0155] The management frame includes second information, the second information indicating a second NSTR capability between the first link and the second link.

[0137]

[0156] In a possible implementation, the second NSTR capability is used to replace or update the first NSTR capability, in other words, the second NSTR capability may be the most recent NSTR capability between the first link and the second link.

[0138]

[0157] In a particular example, if the first MLD is a non-AP MLD and the second MLD is an AP MLD, the non-AP MLD may transmit a management frame after the non-AP MLD is associated with the AP MLD, and the second NSTR capability may be the most recent NSTR capability between the first link and the second link after the association.

[0139]

[0158] In a possible implementation, the NSTR capability may be used to indicate whether two links are NSTR. In other words, the NSTR capability may be used to indicate whether the two links can perform simultaneous transmission and reception. For example, the NSTR capability may be true, indicating that the two links are NSTR, i.e., simultaneous transmission and reception cannot be performed on the two links; or the NSTR capability may be false, indicating that the two links are STR, i.e., simultaneous transmission and reception can be performed on the two links.

[0140]

[0159] One example is the inability to transmit and receive simultaneously on two links: This may include the fact that when a signal is received on one link, it is not possible to transmit a signal on the other link; or the fact that receiving a signal on one link prevents the simultaneous transmission of a signal on the other link. This may include that when a signal is received on one link, it is possible to transmit a signal on the other link; or, alternatively, receiving a signal on one link does not prevent simultaneous transmission of a signal on the other link.

[0141]

[0160] In some embodiments, the solution of the present application may be modified appropriately. For example, NSTR capability may be changed to STR capability, and the STR capability may indicate whether two links are STR between them. In other words, the STR capability may indicate whether two links are capable of performing simultaneous transmission and reception. Therefore, the STR capability and the NSTR capability have the same function, but the interpretation of the STR capability and the interpretation of the NSTR capability are opposite. For example, when the NSTR capability is true, the STR capability is false; or when the NSTR capability may be false, the STR capability is true.

[0142]

[0161] Additionally, NSTR capability in this application may also be referred to as NSTR / STR capability or may be referred to as NSTR capability status and may be used interchangeably, without any particular limitation in this application.

[0143]

[0162] In a possible implementation, the link pair formed by the first link and the second link may be referred to as the first link pair, and the NSTR capability between the first link and the second link may be referred to as the NSTR capability of the first link pair.

[0144]

[0163] In some embodiments, the first information indicating a first NSTR capability between the first link and the second link may also be understood as follows: the first information indicates a first sending and receiving relationship between the first link and the second link, where the first sending and receiving relationship includes an NSTR and an STR. If the first sending and receiving relationship is an NSTR, the first NSTR capability may be considered true; or, if the first sending and receiving relationship is an STR, the first NSTR capability may be considered false.

[0145]

[0164] In some embodiments, the second information indicating a second NSTR capability between the first link and the second link may be understood as follows: the second information indicates a second sending and receiving relationship between the first link and the second link, where the second sending and receiving relationship includes an NSTR and an STR. If the second sending and receiving relationship is an NSTR, the second NSTR capability may be considered true; or, if the second sending and receiving relationship is an STR, the second NSTR capability may be considered false.

[0146]

[0165] It can be appreciated that the first MLD may generate an association request frame before the first MLD sends an association request frame, and similarly, a management frame may be generated before the first MLD sends a management frame.

[0147]

[0166] In some embodiments, the management frame may be an action frame. FIG. 7 shows a common frame structure of an action frame, which includes a category field and an action details field. The category field indicates the type of action frame. For example, the action frame in this application may be an EHT action frame. The action details field typically includes an action field that indicates the format (or function) of the action frame indicated by the category field. An EHT action frame is used as an example. The action field may indicate the format (or function) of the EHT action frame. For example, if the action field is set to 0, it indicates that the EHT action frame is used for compressed beamforming.

[0148]

[0167] In some other embodiments, the management frame may be a new type of management frame. For ease of description, the new type of management frame is referred to as a first management frame in this application. The type of the first management frame may be indicated by using an Element ID field and / or an Element ID Extension field. For example, the type of the first management frame may be indicated by using a reserved element ID value; or, if the element ID is equal to 255, the type of the first management frame may be indicated by using a reserved element ID extension value.

[0149]

[0168] In the present application, the management frame including the second information may be referred to as an NSTR capability update frame. Of course, the management frame may have another name, for example, an NSTR capability report frame. The name of the management frame is not particularly limited in the present application.

[0150]

[0169] In some embodiments, after receiving the management frame, the second MLD may use the management frame. For example, the NSTR capability between the first link and the second link is determined based on the second information included in the management frame, so as to communicate with the first MLD in a manner consistent with the NSTR capability. Of course, after receiving the management frame, the second MLD may further perform other operations, which are not particularly limited in the present application.

[0151]

[0170] The above describes the NSTR capability indication between the first link and the second link using an example in which the link between the first MLD and the second MLD includes the first link and the second link. In some implementation scenarios, in addition to the first link and the second link, the link between the first MLD and the second MLD may further include another link. In other words, in addition to the first link pair formed by the first link and the second link, another link pair may further be included.

[0152]

[0171] In this implementation scenario, in a possible implementation, in addition to the NSTR capability of the first link pair, the first MLD also reports the NSTR capability of another link pair in the management frame, regardless of whether the NSTR capability of the other link pair changes.

[0153]

[0172] For example, the link between the first MLD and the second MLD further includes a third link, and the link pair formed by the first link and the third link is a second link pair, and the link pair formed by the second link and the third link is a third link pair. If the NSTR capability of the first link pair changes, the NSTR capability of the second link pair changes, and the NSTR capability of the third link pair does not change, the management frame may indicate the NSTR capability of the first link pair, the NSTR capability of the second link pair, and the NSTR capability of the third link pair.

[0154]

[0173] In another possible implementation, the first MLD reports in a management frame the NSTR capabilities of the link pair where the NSTR capabilities of the link pair have changed. After receiving the management frame, the second MLD updates the NSTR capabilities of this part of the link pair. For NSTR capabilities of the link pair that are not reported in the management frame, the second MLD considers the NSTR capabilities unchanged by default.

[0155]

[0174] For example, the link between the first MLD and the second MLD further includes a third link. The link pair formed by the first link and the third link is a second link pair, and the link pair formed by the second link and the third link is a third link pair. If the NSTR capability of the first link pair changes, the NSTR capability of the second link pair changes, and the NSTR capability of the third link pair does not change, the management frame may indicate the NSTR capability of the first link pair and the NSTR capability of the second link pair.

[0156]

[0175] Additionally, in some implementation scenarios, there may be a delay in switching the NSTR capability of a link pair. For these scenarios, when the NSTR capability of a link pair changes from STR to NSTR, a management frame may be sent first to report the changed NSTR capability, and then the capability switch is performed. When the NSTR capability of a link pair changes from NSTR to STR, a capability switch may be performed first, and then a management frame is sent to report the changed NSTR capability.

[0157]

[0176] In a particular example, if the NSTR capability of multiple link pairs changes, e.g., if the NSTR capability of a Type-1 link pair changes from STR to NSTR and the NSTR capability of a Type-2 link pair changes from NSTR to STR, the NSTR capability of the Type-1 link pair may be reported in one management frame and the NSTR capability of the Type-2 link pair may be reported in another management frame.

[0158]

[0177] Based on this solution, a first MLD may report a first NSTR capability and a second NSTR capability between a first link and a second link to a second MLD. Specifically, the first MLD may report the NSTR capability between the first link and the second link to the second MLD multiple times, thereby enabling the first MLD to notify the second MLD in a timely manner when the NSTR capability between the first link and the second link changes. In this way, the first MLD and the second MLD are able to have a consistent understanding of the NSTR capability between the links, thereby improving communication efficiency.

[0159]

[0178] A method for carrying the second information in a management frame will be described below.

[0160]

[0179] In some embodiments, the management frame may include a first bitmap, where bits in the first bitmap have a one-to-one correspondence with link pairs, each bit indicating the NSTR capability of one link pair. In this manner, the second information may be specified by using one bit in the first bitmap.

[0161]

[0180] Alternatively, the management frame may include multiple second bitmaps, each of which has a one-to-one correspondence with multiple links in the first MLD. Each bit in the second bitmap indicates the NSTR capability between the link corresponding to the second bitmap and another link. It should be understood that the bit sequence in the second bitmap has a mapping relationship with the sequence of another link. For example, the bits from most significant to least significant in the second bitmap correspond sequentially to the links of the link identifier in descending order; or the bits from most significant to least significant in the second bitmap correspond sequentially to the links of the link identifier in ascending order. In this way, the second information may be indicated by using one bit in the second bitmap corresponding to the first link.

[0162]

[0181] For example, the multiple links of the first MLD include a first link, a second link, a third link, and a fourth link, and the management frame may include a second bitmap A, a second bitmap B, a second bitmap C, and a second bitmap D, which correspond to the first link, the second link, the third link, and the fourth link, respectively.

[0163] The second bitmap A may include four bits corresponding to the NSTR capability between the first link and the first link, the NSTR capability between the first link and the second link, the NSTR capability between the first link and the third link, and the NSTR capability between the first link and the fourth link, respectively. The bit indicating the NSTR capability between the first link and the first link is meaningless and may be used as a reserved bit.

[0164] Similarly, the second bitmap B may also include four bits corresponding to the NSTR capability between the second link and the first link, the NSTR capability between the second link and the second link, the NSTR capability between the second link and the third link, and the NSTR capability between the second link and the fourth link. The bit indicating the NSTR capability between the second link and the second link is meaningless and may be used as a reserved bit.

[0165] The second bitmap C may also include four bits corresponding to the NSTR capability between the third link and the first link, the NSTR capability between the third link and the second link, the NSTR capability between the third link and the third link, and the NSTR capability between the third link and the fourth link. The bit indicating the NSTR capability between the third link and the third link is meaningless and may be used as a reserved bit.

[0166] The second bitmap D may also include four bits corresponding to the NSTR capability between the fourth link and the first link, the NSTR capability between the fourth link and the second link, the NSTR capability between the fourth link and the third link, and the NSTR capability between the fourth link and the fourth link. The bit indicating the NSTR capability between the fourth link and the fourth link is meaningless and may be used as a reserved bit.

[0167]

[0182] In some other embodiments, the management frame may include a multi-link element, and the second information may be carried in the multi-link element. The multi-link element may be implemented in two ways:

[0168]

[0183] Method 1: A multi-link element may be a basic variant multi-link element.

[0169]

[0184] In a possible implementation, the frame structure of a basic variant multi-link element may be as shown in Figure 3. The basic variant multi-link element includes a multi-link control field and a link information field.

[0170]

[0185] When the basic variant multi-link element carries second information, the second information may be carried in an NSTR indication bitmap field in the link information field. Additionally, the second information may be carried in an NSTR indication bitmap field in the per-STA profile field corresponding to the first link and included in the link information field.

[0171]

[0186] If the basic variant multi-link element carries second information, the first field may be set to 0. The first field may include at least one of the following: a multi-link device medium access control address present field, a link identifier information present field, a change sequence present field, a multi-link device capabilities present field, or an EMLSR capabilities present field, which are included in the multi-link control field. If the first field is set to 0, it may indicate that the common information fields in the basic variant multi-link element do not include at least one of the following: a multi-link device medium access control address field, a link identifier information field, a change sequence field, a multi-link device capabilities field, or an EMLSR capabilities field.

[0172]

[0187] It will be understood that the presence fields included in the first field correspond to fields not included in the common information field, for example, if the first field includes a link identifier information presence field, the common information field does not include a link identifier information field.

[0173]

[0188] If the basic variant multi-link element carries second information, the second field included in the link information field may be set to 0. The second field may include at least one of the following: a complete profile field, a medium access control address present field, a beacon interval present field, or a DTIM information present field. If the second field is set to 0, it may indicate that the basic variant multi-link element does not include complete information of the first link, or that the station information field in the link information field does not include a station medium access control address field, a beacon interval field, a DTIM quantity field, or a DTIM period field.

[0174]

[0189] It will be understood that the presence fields included in the second field correspond to fields not included in the station information field, for example, if the second field includes a beacon interval presence field, the station information field does not include a beacon interval field.

[0175]

[0190] Additionally, if the Basic Variant Multi-Link element carries second information, the Basic Variant Multi-Link element may not include a Station Profile field.

[0176]

[0191] The Full Profile field, Medium Access Control Address Present field, Beacon Interval Present field, and DTIM Information Present field may be collectively referred to as a second field, which may be carried in the Link Information field and in the per-STA Profile field corresponding to the first link.

[0177]

[0192] In conclusion, when the basic variant multi-link element carries second information, in a particular example, the frame structure and configuration of some fields of the basic variant multi-link element may be as shown in Figure 8.

[0178]

[0193] It should be noted that the basic variant multi-link element in Scheme 1 is designed based on the basic variant multi-link element in the current 802.11be standard. If the frame structure of the basic variant multi-link element in the current 802.11be standard changes in the subsequent standardization evolution process, Scheme 1 may also be appropriately modified so that it can be applied to NSTR capability reporting in the evolved standard. For example, if a presence field is newly added to the basic variant multi-link element in the subsequent standard, if the solution of the present application is used, the newly added presence field may be set to 0 to indicate that there is no field corresponding to the presence field.

[0179]

[0194] Method 2: The Multi-Link element may be an Update variant Multi-Link element.

[0180]

[0195] In a possible implementation, the Update Variant Multi-Link element may include a Multi-Link Control field and a Link Information field.

[0181]

[0196] In one example, the multi-link control field may include a type field, and the type field may be set to a first value, and the first value may be a type value not used by the basic variant multi-link element. For example, the first value is 2. Furthermore, the multi-link control field does not include the first field. For the first field, please refer to the description of Method 1. Details will not be described again here.

[0182]

[0197] In one example, the link information field may include an NSTR indication bitmap field, and the second information may be carried in the NSTR indication bitmap field. In a specific example, one bit in the NSTR bitmap may correspond to one link pair, and the value of the bit may indicate the NSTR capability of the link pair corresponding to the bit. For example, the NSTR bitmap may include a bit corresponding to a first link pair formed by a first link and a second link, and the value of the bit may indicate the NSTR capability of the first link pair, i.e., the bit may indicate the second information. Also, the link information field does not include a second field. For the second field, please refer to the description in Scheme 2 above. Details will not be described again here.

[0183]

[0198] Optionally, the link information field may include a per-STA profile subelement, which has a one-to-one correspondence with the first MLD link. The per-STA profile field may include a Subelement ID field, a Length field, a Station Control field, and a Station Info field. For the functions of the Subelement ID field and the Length Identifier field, please refer to the description of the corresponding fields in the frame structure shown in Figure 3. The details will not be described again here. The Station Information field may include the NSTR Indication Bitmap field described above.

[0184]

[0199] Optionally, the Station Control field may contain an NSTR Link Pair Present field and an NSTR Bitmap Size field. The NSTR Link Pair Present field indicates whether the Link Information field contains an NSTR Indication Bitmap field. The NSTR Bitmap Size field indicates the size of the NSTR Indication Bitmap field if the Link Information field contains an NSTR Indication Bitmap field.

[0185]

[0200] In a specific example, the NSTR link pair presence field indicates whether the station information field within the link information field includes an NSTR indication bitmap field. The NSTR bitmap size field indicates the size of the NSTR indication bitmap field if the station information field within the link information field includes an NSTR indication bitmap field. It will be understood that the present application is described using an example in which the link information field includes an NSTR indication bitmap field.

[0186]

[0201] Additionally, the Station Control field may further include a Link Identifier field for identifying the link (e.g., the first link) corresponding to the per-STA Profile sub-element that includes the Station Control field. Additionally, the Station Control field may further include a Reserved field.

[0187]

[0202] Optionally, in addition to the Multi-Link Control and Link Information fields, the Update Variant Multi-Link element may further contain at least one of the following: an Element ID field, a Length field, or an Element ID Extension field. The Element ID field and the Element ID Extension field are used to identify the Update Variant Multi-Link element, and the Length field indicates the length of the Update Variant Multi-Link element.

[0188]

[0203] In conclusion, a possible frame structure of the Update Variant Multi-Link element provided in Scheme 2 may be that shown in Figure 9.

[0189]

[0204] It should be noted that the Update Variant Multi-Link element in this application may also have a different name, for example, Update Variant Multi-Link Element. The name of the Update Variant Multi-Link element is not particularly limited in this application. Furthermore, in this application, each field or sub-element within the Update Variant Multi-Link element may have a different name. This is not particularly limited in this application.

[0190]

[0205] In some embodiments, in addition to the multi-link element, the management frame may further include a third field, which, when set to a second value, may indicate that the management frame is used to update NSTR capabilities between the first link and the second link.

[0191]

[0206] In one example, when the management frame is an action frame, the third field may be an action field in an action detail field in the action frame, and the second value may be, for example, 1. Of course, the third field may alternatively be another field in the action frame, which is not particularly limited in the present application.

[0192]

[0207] Based on this solution, the capabilities of the management frame can be notified to the second MLD, so that the second MLD can correctly interpret the management frame and obtain the second NSTR capability between the first link and the second link.

[0193]

[0208] The above description describes the overall process of reporting NSTR capabilities. Furthermore, after a channel switch, the frequency spacing between two links may change. The frequency spacing is an important factor affecting the NSTR capabilities between links. Therefore, the interaction of NSTR capabilities in a channel switch scenario is further considered in this application. Below, the procedure shown in FIG. 6 is further explained by using an example where the first MLD is a non-AP MLD and the second MLD is an AP MLD.

[0194]

[0209] Regarding the first MLD, this application mainly provides the conditions for sending management frames. For example, in a channel switching scenario, the first MLD may send management frames in the following two cases:

[0195]

[0210] Case 1: When a channel switch occurs, the first MLD transmits a management frame to the second MLD.

[0196]

[0211] In a specific example, in case 1, the second NSTR capability indicated by the second information included in the management frame is the NSTR capability between the first link and the second link after channel switching.

[0197]

[0212] In this case, the NSTR capability report is triggered by a channel switch. In other words, the first MLD may report NSTR capability after a channel switch occurs, regardless of whether the NSTR capability between the first link and the second link changes after the channel switch occurs.

[0198]

[0213] Case 2: When a channel switch occurs and the first condition is not met, the first MLD transmits a management frame to the second MLD.

[0199]

[0214] In a specific example, in case 2, the second NSTR capability indicated by the second information included in the management frame is the NSTR capability between the first link and the second link after channel switching.

[0200]

[0215] In an implementation, the first condition includes at least one of the following:

[0216] (1) After a channel switch, one of the frequency band accessed by the first link and the frequency band accessed by the second link is within the first frequency band, and the other is within the second frequency band.

[0201]

[0217] In one example, the first and second frequency bands may be specified in the protocol. For example, the first frequency band may be the 2.4 GHz frequency band, and the other may be the 5 GHz frequency band or the 6 GHz frequency band. In other words, after the channel switch, one of the frequency bands accessed by the first link and the second link is in the 2.4 GHz frequency band, and the other is in the 5 GHz frequency band or the 6 GHz frequency band.

[0202]

[0218] In a possible implementation, if a new Wi-Fi frequency band is allocated in subsequent standard evolution, the first frequency band and the second frequency band may also change. For example, if the 7 GHz Wi-Fi frequency band is subsequently allocated, condition (1) may be: one of the frequency band accessed by the first link and the frequency band accessed by the second link is within the 2.4 GHz frequency band, and the other is within the 5 GHz, 6 GHz, or 7 GHz frequency band. Alternatively, condition (1) may be: one of the frequency band accessed by the first link and the frequency band accessed by the second link is within the 5 GHz frequency band, and the other is within the 7 GHz frequency band.

[0203]

[0219] In a possible implementation, if one of the frequency bands accessed by the first link and the second link is within the first frequency band and the other is within the second frequency band, then there is an STR between the first link and the second link.

[0204]

[0220] (2) After the channel switch, the frequency spacing between the first link and the second link is greater than or equal to the first threshold.

[0205]

[0221] In a particular example, the frequency spacing between the first link and the second link may be the difference between the closest frequency edges of the first link and the second link (the difference between the closest frequency edges of the two links), or may be the spacing between the center frequencies of the first link and the second link.

[0206]

[0222] For example, the channel bandwidth of the first link is A, the channel bandwidth of the second link is B, the center frequency of the first link is A0, and the center frequency of the second link is B0, where A0 is lower than B0. The closest frequency edges of the first link and the second link are BL and AH, where BL = B0 - B / 2; AH = A0 + A / 2.

[0207]

[0223] In a possible implementation, the first threshold may be determined by the first MLD. For example, the first threshold may be a threshold reported by the non-AP MLD to the AP MLD during the association process. For example, the non-AP MLD may report a parameter for frequency separation for STR, and the parameter indicates the first threshold.

[0208]

[0224] In another possible implementation, the first threshold may be predefined in the protocol or may be set by the second MLD for the first MLD, which is not particularly limited in the present application.

[0209]

[0225] In a possible implementation, the first link and the second link are in STR if the frequency interval between the center frequency of the first frequency band and the center frequency of the second frequency band is greater than or equal to a second threshold.

[0210]

[0226] (3) Before the channel change, there is a STR between the first link and the second link, and after the channel change, the frequency interval between the first link and the second link remains unchanged or becomes larger.

[0211]

[0227] In a specific example, for the frequency interval between the first link and the second link, please refer to the relevant description in (2), and the details will not be described again here.

[0212]

[0228] In a possible implementation, before the channel change, there is a STR between the first link and the second link. After the channel change, if the frequency spacing between the first link and the second link remains unchanged or becomes larger, there is still a STR between the first link and the second link.

[0213]

[0229] In a particular example, the frequency spacing between the first link and the second link remaining unchanged or becoming larger after a channel switch may include: after a channel switch, the frequency spacing between the first link and the second link remaining unchanged or becoming larger, and the relative relationship of the frequencies of the first link and the second link remaining unchanged.

[0214]

[0230] For example, the relative relationship between the frequency of the first link and the frequency of the second link may refer to the relationship between the center frequency of the first link and the center frequency of the second link. The relative relationship between the frequencies of the first link and the second link remaining unchanged may include: before channel switching, the center frequency of the first link is greater than the center frequency of the second link, and after channel switching, the center frequency of the first link is still greater than the center frequency of the second link; or before channel switching, the center frequency of the first link is less than the center frequency of the second link, and after channel switching, the center frequency of the first link is still less than the center frequency of the second link.

[0215]

[0231] (4) Before the channel change, there is a NSTR between the first link and the second link, and after the channel change, the frequency spacing between the first link and the second link remains unchanged or becomes smaller.

[0216]

[0232] In a specific example, for the frequency interval between the first link and the second link, please refer to the relevant description in (2), and the details will not be described again here.

[0217]

[0233] In a possible implementation, before a channel change, there is a NSTR between the first link and the second link. After a channel change, the frequency separation between the first link and the second link remains unchanged or becomes larger, and there is still a NSTR between the first link and the second link.

[0218]

[0234] In a specific example, the frequency interval between the first link and the second link remaining unchanged or becoming smaller after a channel change may include: after a channel change, the frequency interval between the first link and the second link remaining unchanged or becoming smaller, and the relative relationship between the frequencies of the first link and the second link remaining unchanged. For the relative relationship between the frequencies of the first link and the second link, please refer to the explanation in the above condition (3). Details will not be described again here.

[0219]

[0235] It will be understood that the change in frequency spacing between the first link and the second link in (3) and (4) is relative to the frequency spacing between the first link and the second link before the channel change. For example, an increase in frequency spacing between two links after a channel change is relative to the frequency spacing between the two links before the channel change.

[0220]

[0236] The first condition in the above example relates to the frequency of the link. During the channel switching process, the AP MLD can know the target channel after switching, so the judgment of the first condition can also be performed by the AP MLD. Therefore, if the first condition is met, the AP MLD can know the NSTR capability between the first and second links after the channel switching. In this scenario, the non-AP MLD does not need to send management frames.

[0221]

[0237] If the first condition is not met, the AP MLD may not be able to determine the NSTR capability between the first link and the second link after the channel switch. In this scenario, the non-AP MLD may send a management frame to the AP to report the NSTR capability between the first link and the second link after the channel switch.

[0222]

[0238] In a particular example, the reason why AP MLD cannot determine the NSTR capability between the first link and the second link after a channel switch, and non-AP MLD can determine the NSTR capability between the first link and the second link after a channel switch, may be that non-AP MLD knows more link information than AP MLD.

[0223]

[0239] Case 3: After a channel switch announcement is received but before a channel switch is executed, the first MLD sends a management frame to the second MLD.

[0224]

[0240] In a specific example, in case 3, the second NSTR capability indicated by the second information included in the management frame is the NSTR capability between the first link and the second link after channel switching.

[0225]

[0241] The channel switch announcement indicates the channel switch time and the target channel. For example, the channel switch announcement may be carried in a channel switch announcement element or an extended channel switch announcement element.

[0226]

[0242] In a possible implementation, the second MLD may send a channel switch announcement to the first MLD in advance in several DTIM beacons, so that the first MLD can determine, before the channel switch, the NSTR between the first link and the second link and what it will be after the channel switch, and send a management frame to the second MLD before the channel switch is performed to indicate the NSTR capability between the first link and the second link after the channel switch.

[0227]

[0243] Since the management frame is sent before the channel change, it may be indistinguishable for the second MLD whether the second NSTR capability indicated by the action is the NSTR capability before the channel change or the NSTR capability after the channel change.

[0228]

[0244] Therefore, in a possible implementation, the second MLD may use the NSTR capability indicated by a management frame received after the channel switch announcement is sent as the NSTR capability after the channel switch.

[0229]

[0245] In another possible implementation, the management frame may further include third information, which indicates that the second NSTR capability is an NSTR capability between the first link and the second link after a channel switch. For example, the third information may be carried in a multi-link element. For example, a 1-bit may be added to the multi-link element for indication, and the value of the bit may indicate whether the NSTR capability is an NSTR capability before a channel switch or an NSTR capability after a channel switch. For example, when the bit is set to 0, it indicates that the NSTR capability indicated by the multi-link element is an NSTR capability before a channel switch, and when the bit is set to 1, it indicates that the NSTR capability indicated by the multi-link element is an NSTR capability after a channel switch. In a specific example, the 1-bit indication may be carried in a station control field in a per-STA profile field.

[0230]

[0246] When the first MLD reports the NSTR capability after a channel switch, the first MLD may need to perform channel contention before transmitting a management frame. Thus, there is a delay in transmitting and receiving the management frame. Therefore, with respect to the second MLD, the present application mainly provides a manner in which the second MLD determines the NSTR capability between the first link and the second link in a first time interval. The first time interval is the time interval from when a channel switch occurs to when the second MLD receives a management frame. For example, the second MLD may determine the NSTR capability between the first link and the second link in a time interval in at least one of the following three manners:

[0247] Method 1: The second MLD determines that there is an NSTR between the first link and the second link in the first time interval.

[0231]

[0248] In this method 1, the second MLD can simply consider that there is an NSTR between the first link and the second link, thereby reducing the complexity of the implementation of the second MLD. Furthermore, the second MLD determines that there is an NSTR between the first link and the second link. Even if there is actually an STR between the first link and the second link in the first time interval, the second MLD communicates with the first MLD by using parameters corresponding to the NSTR. In this case, there is no significant transmission error.

[0232]

[0249] Method 2: If the second condition is met, the second MLD determines that there is an STR between the first link and the second link in the first time interval.

[0233]

[0250] In a possible implementation, the second condition includes at least one of the following:

[0251] (1) After a channel change, one of the frequency bands accessed by the first link and the second link is in the first frequency band, and the other is in the second frequency band.

[0234]

[0252] For example, after channel switching, one of the frequency bands accessed by the first link and the second link is in the 2.4 GHz frequency band, and the other is in the 5 GHz frequency band or the 6 GHz frequency band.

[0235]

[0253] (2) After the channel switch, the frequency spacing between the first link and the second link is greater than or equal to the first threshold.

[0236]

[0254] (3) Before the channel change, there is an STR between the first link and the second link, and after the channel change, the frequency spacing between the first link and the second link remains unchanged or becomes larger.

[0237]

[0255] Regarding the second condition (1), (2), and (3), please refer to the relevant explanations of the first condition (1), (2), and (3), and the details will not be explained again here.

[0238]

[0256] Method 3: If the third condition is met, the second MLD determines that there is an NSTR between the first link and the second link in the first time interval.

[0239]

[0257] In a possible implementation, the third condition is: before the channel change, the frequency interval between the first link and the second link is NSTR, and after the channel change, the frequency interval between the first link and the second link remains unchanged or becomes smaller. For details, please refer to the relevant explanation of (4) of the first condition. The details will not be described again here.

[0240]

[0258] It should be noted that in practical applications, the method for implementing the first MLD provided above and the method for implementing the second MLD may be used simultaneously. For example, the first MLD uses the transmission scheme in Case 1, and the second MLD uses the determination scheme provided in Scheme 1. Alternatively, the first MLD uses the transmission scheme in Case 1, and the second MLD uses the determination scheme provided in Scheme 2 or Scheme 3. Alternatively, the first MLD uses the transmission scheme in Case 2, and the second MLD uses the determination scheme provided in Scheme 1. Alternatively, the first MLD uses the transmission scheme in Case 2, and the second MLD uses the determination scheme provided in Scheme 2 or Scheme 3.

[0241]

[0259] Alternatively, in practical applications, the above-mentioned implementation method for the first MLD and the implementation method for the second MLD may be used separately. For example, the first MLD uses the transmission method in Case 1 or Case 2, and the second MLD uses another determination method other than the method provided above. This is not particularly limited in the present application.

[0242]

[0260] Based on the aforementioned solution, in a channel switching scenario, the second MLD can know the NSTR capability after the channel switching, so that the first MLD and the second MLD can have a consistent understanding of the NSTR capability between the links after the channel switching, thereby improving communication efficiency.

[0243]

[0261] In addition to channel switching, changes in station operating parameters (eg, bandwidth) can also change the frequency spacing between links, thus affecting the NSTR capability between the links.

[0244]

[0262] For example, the operating parameter is bandwidth. It is assumed that before the bandwidth is changed, there is a NSTR between Link 1 and Link 2. If the bandwidth of Link 1 changes from 320 megahertz (MHz) to 80 MHz, i.e., the bandwidth decreases, the frequency separation between Link 1 and Link 2 may become larger because the bandwidth of Link 1 is decreased. Therefore, after the bandwidth is changed, there may be a STR between Link 1 and Link 2.

[0245]

[0263] Alternatively, it is assumed that before the bandwidth is changed, there is a STR between Link 1 and Link 2. If the bandwidth of Link 1 changes from 80 MHz to 320 MHz, i.e., the bandwidth increases, the frequency spacing between Link 1 and Link 2 may become smaller because the bandwidth of Link 1 increases. Therefore, there may be an NSTR between Link 1 and Link 2 after the bandwidth is changed.

[0246]

[0264] Below, we will explain the reporting of NSTR capability in this scenario by using an example where the first MLD changes the channel bandwidth of the first link.

[0247]

[0265] It will be appreciated that if the update of the operating mode parameters does not change the NSTR capability, the first MLD may not transmit a management frame, or in other words, may not perform an NSTR capability update report.

[0248]

[0266] In some embodiments, when the first MLD reduces the channel bandwidth of the first link, the first MLD may first send a management frame to the second MLD to indicate a second NSTR capability, and then send first operation mode control information to the second MLD to indicate that the channel bandwidth of the first link has changed and that the changed channel bandwidth is smaller than the channel bandwidth before the change. The second NSTR capability is the NSTR capability between the first link and the second link after the channel bandwidth of the first link has changed.

[0249]

[0267] In other words, as shown in FIG. 10 , before step S602, the method may further include the following step S600:

[0268] S600: The first MLD transmits first operation mode control information to the second MLD. In response, the second MLD receives the first operation mode control information from the first MLD.

[0250]

[0269] The first operation mode control information indicates that the channel bandwidth of the first link is changed, and that the changed channel bandwidth is smaller than the channel bandwidth before the change.

[0251]

[0270] Furthermore, the first MLD may first send a management frame to the second MLD to indicate the second NSTR capability, and after receiving an acknowledgment frame of the management frame, send the first operation mode control information to the second MLD.

[0252]

[0271] In a particular example, the first operation mode control information may be carried in the operation mode control subfield. Of course, the information may alternatively be carried in another field. This is not particularly limited in the present application.

[0253]

[0272] For example, the channel bandwidth of the first link before the change is 320 MHz, and the channel bandwidth of the first link after the change is 80 MHz. If there is NSTR between the first link and the second link before the change, there is a possibility that there is STR between the first link and the second link after the change. Assuming that the first operation mode control information and the management frame are carried in the same PPDU (or MAC frame), after receiving the PPDU, the second MLD responds with an acknowledgment frame corresponding to the PPDU. However, if the acknowledgment frame is not correctly received by the first MLD, according to the existing OM parameter update rule, the first MLD keeps the channel bandwidth of the first link unchanged at 320 MHz after the TXOP to transmit the PPDU because the first MLD did not receive the acknowledgment frame. In this case, NSTR is also maintained between the first link and the second link. However, since the second MLD receives the PPDU, it may consider that the first MLD has adjusted the channel bandwidth of the first link to 80 MHz and that the first link and the second link are in STR mode. Therefore, the second MLD may communicate with the first MLD by using the STR procedure, and finally, a communication failure may occur because the first MLD does not actually have STR capability.

[0254]

[0273] Therefore, when the first MLD reduces the channel bandwidth of the first link, it is unreasonable to carry the first operation mode control information and the management frame for indicating the second NSTR capability in the same PPDU (or MAC frame). In other words, the first operation mode control information and the management frame for indicating the second NSTR capability are carried separately in different PPDUs (or MAC frames) for transmission. Also, the first operation mode control information may be transmitted first, followed by the management frame for indicating the second NSTR capability.

[0255]

[0274] After the first operation mode control information is successfully transmitted and the channel bandwidth of the first link is reduced, the state between the first link and the second link may change from NSTR to STR. In this case, because the management frame for indicating the second NSTR capability is transmitted after the first operation mode control information, there is a delay between the time when the second MLD receives the first operation mode control information and the time when the second MLD receives the management frame. During the delay, the second MLD may still believe that the state between the first link and the second link is NSTR. Even if the second MLD communicates with the first MLD by using the NSTR procedure during the delay, no communication failure occurs. If the order of transmitting the first operation mode control information and the management frame is changed, a communication failure may occur due to the two MLDs having different understandings of the NSTR capability between the first link and the second link.

[0256]

[0275] In other words, based on this solution, when the channel bandwidth of the link decreases, communication failures caused by the first MLD and the second MLD having different understandings of the NSTR capability between the first link and the second link may be avoided to the greatest extent.

[0257]

[0276] In some other embodiments, when the first MLD increases the channel bandwidth of the first link, the first MLD may first send second operation mode control information to the second MLD to indicate that the channel bandwidth of the first link has changed and that the changed channel bandwidth is greater than the channel bandwidth before the change. Then, the first MLD sends a management frame to the second MLD to indicate a second NSTR capability. The second NSTR capability is the NSTR capability between the first link and the second link after the channel bandwidth of the first link has changed.

[0258]

[0277] In other words, as shown in FIG. 11 , after step S602, the method may further include the following step S603:

[0278] S603: The first MLD transmits the second operation mode control information to the second MLD. In response, the second MLD receives the second operation mode control information from the first MLD.

[0259]

[0279] The second operation mode control information indicates that the channel bandwidth of the first link has changed and that the changed channel bandwidth is larger than the channel bandwidth before the change.

[0260]

[0280] Furthermore, the first MLD may first send second operation mode control information to the second MLD, and after receiving an acknowledgment of the second operation mode control information, send a management frame to the second MLD to indicate the second NSTR capability.

[0261]

[0281] In a particular example, the second operation mode control information may be carried in the operation mode control subfield. Of course, the information may alternatively be carried in another field. This is not particularly limited in the present application.

[0262]

[0282] For example, the channel bandwidth of the first link before the change is 80 MHz, and the channel bandwidth of the first link after the change is 320 MHz. If the first link and the second link before the change were in STR, the first link and the second link after the change may be in NSTR. Assuming that the second operation mode control information and the management frame are carried in the same PPDU (or MAC frame), if the second MLD does not correctly receive the PPDU and therefore does not respond with an acknowledgment frame corresponding to the PPDU, according to the existing OM parameter update rule, the first MLD adjusts the channel bandwidth of the first link to 80 MHz after the TXOP for transmitting the PPDU ends. In this case, the channel bandwidth between the first link and the second link changes from STR to NSTR. However, because the second MLD does not receive the PPDU, the second MLD may believe that the channel bandwidth of the first link is still 80 MHz and that the channel bandwidth between the first link and the second link is still in STR. Therefore, the second MLD may communicate with the first MLD by using the STR procedure, and ultimately, a communication failure may occur because the first MLD does not actually have STR capability.

[0263]

[0283] Therefore, when the first MLD increases the channel bandwidth of the first link, it is unreasonable to carry the second operation mode control information and the management frame for indicating the second NSTR capability in the same PPDU (or MAC frame). In other words, the second operation mode control information and the management frame for indicating the second NSTR capability are carried separately in different PPDUs (or MAC frames) for transmission. Furthermore, the management frame for indicating the second NSTR capability may be transmitted first, followed by the second operation mode control information.

[0264]

[0284] If the management frame indicating the second NSTR capability is successfully transmitted, the channel bandwidth of the first link remains 80 MHz, and STR remains between the first and second links. In this case, since the second MLD successfully receives the management frame, it may determine that NSTR is in effect between the first and second links, and therefore communicate with the first MLD using the NSTR procedure. In this case, although the first and second MLDs have different understandings of the NSTR capability between the first and second links, communication failures can be avoided to the greatest extent possible. If the order of transmitting the second operation mode control information and the management frame is changed, a communication failure may occur due to the two MLDs having different understandings of the NSTR capability between the first and second links.

[0265]

[0285] In other words, when the channel bandwidth of the link increases, based on this solution, communication failures caused by the first MLD and the second MLD having different understandings of the NSTR capability between the first link and the second link may be avoided to the greatest extent.

[0266]

[0286] It will be understood that in the foregoing embodiments, the methods and / or steps performed by the first MLD may also be performed by components (e.g., chips or circuits) that may be used in the first MLD, and the methods and / or steps performed by the second MLD may also be performed by components (e.g., chips or circuits) that may be used in the second MLD.

[0267]

[0287] The above mainly describes the solution provided in the present application from the viewpoint of interactions between devices. Correspondingly, the present application further provides a communication device configured to implement the aforementioned method. The communication device may be a first MLD, a device including the first MLD, or a component that may be used in the first MLD in the aforementioned method embodiment. Alternatively, the communication device may be a second MLD, a device including the second MLD, or a component that may be used in the second MLD in the aforementioned method embodiment.

[0268]

[0288] It will be understood that to implement the above-described functions, the communication device includes corresponding hardware structures and / or software modules for performing each function. Those skilled in the art will readily recognize that the present application may be implemented by hardware or a combination of hardware and computer software in combination with the specific units and algorithm steps described in the embodiments disclosed herein. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use various methods to implement the described functions for each specific application, but such implementation should not be considered to go beyond the scope of the present application.

[0269]

[0289] In the embodiments of the present application, the communication device may be divided into functional modules based on the above-described method embodiments. For example, each functional module may be obtained by dividing the functional modules based on their corresponding functions, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware or in the form of a software functional module. It should be noted that in the embodiments of the present application, the division into modules is an example and is merely a logical division of functions. In actual implementation, other division methods may be used.

[0270]

[0290] In the implementation scenario, an example is taken in which the communication device is the first MLD in the embodiment of the aforementioned method. Figure 12 is a schematic diagram of the structure of the first MLD 120. The first MLD 120 includes a first transmitting module 1201 and a second transmitting module 1202. The first transmitting module 1201 and the second transmitting module 1202 may be collectively referred to as a transmitting module.

[0271]

[0291] In some embodiments, the first MLD 120 may further include a processing module 1203 .

[0272]

[0292] In some embodiments, the first MLD 120 may further include a receiving module 1204. The receiving module 1204 and the transmitting module may be collectively referred to as a transceiver module.

[0273]

[0293] In some embodiments, the receiving module 1204 may alternatively be referred to as a receiving unit. The transmitting module may alternatively be referred to as a transmitting unit. The receiving module 1204 may include a receiver circuit, a receiver, a receiver machine, or a communication interface. The transmitting module may include a transmitter circuit, a transmitter, a transmitter machine, or a communication interface.

[0274]

[0294] In some embodiments, the first MLD 120 may further include a storage module (not shown in FIG. 12) configured to store computer programs or instructions.

[0275]

[0295] In some embodiments, receiving module 1204 may be configured to perform receiving steps performed by the first MLD in the aforementioned method embodiments and / or to support other processes of the techniques described herein. First transmitting module 1201 and second transmitting module 1202 may be configured to perform transmitting steps performed by the first MLD in the aforementioned method embodiments and / or to support other processes of the techniques described herein. Processing module 1203 may be configured to perform processing (e.g., generating and determining) steps performed by the first MLD in the aforementioned method embodiments and / or to support other processes of the techniques described herein.

[0276]

[0296] In one example:

[0297] the first transmitting module 1201 is configured to transmit an association request frame to the second MLD, the association request frame including first information, the first information indicating a first non-simultaneous transmission / reception NSTR capability between the first link and the second link; and The second transmitting module 1202 is configured to transmit a management frame to the second MLD, the management frame including second information, the second information indicating a second NSTR capability between the first link and the second link.

[0277]

[0298] In a possible implementation, configuring the second transmitting module 1202 to transmit a management frame to the second MLD includes: configuring the second transmitting module 1202 to transmit a management frame to the second MLD when the processing module 1203 determines that a channel switch has occurred, where the second NSTR capability is the NSTR capability between the first link and the second link after the channel switch.

[0278]

[0299] In a possible implementation, configuring the second transmitting module 1202 to transmit a management frame to the second MLD includes: configuring the second transmitting module 1202 to transmit a management frame to the second MLD when the processing module 1203 determines that a channel switch has occurred and the first condition is not satisfied, where the second NSTR capability is the NSTR capability between the first link and the second link after the channel switch.

[0279]

[0300] In a possible implementation, configuring the second transmitting module 1202 to transmit a management frame to the second MLD includes: configuring the second transmitting module 1202 to transmit a management frame to the second MLD after the receiving module 1204 receives a channel switch announcement and before the processing module 1203 performs a channel switch, where the second NSTR capability is the NSTR capability between the first link and the second link after the channel switch.

[0280]

[0301] In a possible implementation, the second transmitting module 1202 is further configured to transmit first operating mode control information to the second MLD, where the first operating mode control information indicates that the channel bandwidth of the first link has changed and the changed channel bandwidth is smaller than the channel bandwidth before the change.

[0281]

[0302] In a possible implementation, the second transmitting module 1202 is further configured to transmit second operating mode control information to the second MLD, where the second operating mode control information indicates that the channel bandwidth of the first link has changed and the changed channel bandwidth is larger than the channel bandwidth before the change.

[0282]

[0303] All relevant contents of the steps in the above method embodiments can be cited in the functional descriptions of the corresponding functional modules, and the details will not be described again here.

[0283]

[0304] In this application, the first MLD 120 is presented in the form of functional modules obtained by dividing it in a unified manner. A "module" in this application may be an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other device capable of providing the aforementioned functionality.

[0284]

[0305] In some embodiments, for hardware implementation, one skilled in the art can appreciate that the first MLD 120 may be in the form of a WLAN device 500 shown in FIG.

[0285]

[0306] In one example, the function / implementation process of the processing module 1203 of FIG. 12 may be implemented by the processor 501 in the WLAN device 500 shown in FIG. 5 by invoking computer-executable instructions stored in the memory 504, and the function / implementation process of the receiving module 1204, the first transmitting module 1201, or the second transmitting module 1202 of FIG. 12 may be performed by using the transceiver 502 in the WLAN device 500 shown in FIG. 5.

[0286]

[0307] In some embodiments, when the first MLD 120 in FIG. 12 is a chip or a chip system, the function / implementation process of the receiving module 1204, the first transmitting module 1201, or the second transmitting module 1202 may be implemented by using an input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 1203 may be implemented by using a processor (or processing circuit) of the chip or chip system.

[0287]

[0308] The first MLD 120 provided in this embodiment can perform the aforementioned method. Therefore, please refer to the aforementioned method embodiment for the technical effects that can be achieved by the first MLD 120. The details will not be described again here.

[0288]

[0309] In the implementation scenario, an example is taken in which the communication device is the second MLD in the embodiment of the above-mentioned method. Figure 13 is a schematic diagram of the structure of the second MLD 130. The second MLD 130 includes a first receiving module 1301 and a second receiving module 1302. The first receiving module 1301 and the second receiving module 1302 may be collectively referred to as a receiving module.

[0289]

[0310] In some embodiments, the second MLD 130 may further include a processing module 1303 .

[0290]

[0311] In some embodiments, the second MLD 130 may further include a transmitting module 1304. The transmitting module 1304 and the receiving module may be collectively referred to as a transceiver module.

[0291]

[0312] In some embodiments, a receiving module may alternatively be referred to as a receiving unit. A transmitting module may alternatively be referred to as a transmitting unit. A receiving module may include a receiver circuit, a receiver, a receiver machine, or a communications interface. A transmitting module may include a transmitter circuit, a transmitter, a transmitter machine, or a communications interface.

[0292]

[0313] In some embodiments, the second MLD 130 may further include a storage module (not shown in FIG. 13) configured to store computer programs or instructions.

[0293]

[0314] In some embodiments, first receiving module 1301 and second receiving module 1302 may be configured to perform receiving steps performed by the second MLD in the aforementioned method embodiments and / or to support other processes of the techniques described herein. Transmitting module 1304 may be configured to perform transmitting steps performed by the second MLD in the aforementioned method embodiments and / or to support other processes of the techniques described herein. Processing module 1303 may be configured to perform processing (e.g., using) steps performed by the second MLD in the aforementioned method embodiments and / or to support other processes of the techniques described herein.

[0294]

[0315] In one example:

[0316] the first receiving module 1301 is configured to receive an association request frame from the first MLD, the association request frame including first information, the first information indicating a first non-simultaneous transmission / reception NSTR capability between the first link and the second link; and The second receiving module 1302 is configured to receive a management frame from the first MLD, the management frame including second information, the second information indicating a second NSTR capability between the first link and the second link.

[0295]

[0317] In a possible implementation, the processing module 1303 is configured to determine that there is an NSTR between the first link and the second link during a first time interval, where the first time interval is a time interval from when a channel switch occurs to when a management frame is received; or The processing module 1303 is configured to determine that there is a STR between the first link and the second link in the first time interval if a second condition is met; or The processing module 1303 is configured to determine that there is an NSTR between the first link and the second link in the first time interval if a third condition is met.

[0296]

[0318] In a possible implementation, the second receiving module 1302 is configured to receive a management frame from the first MLD: after the transmitting module 1304 sends a channel switch announcement and before the processing module 1203 performs a channel switch, the second receiving module 1302 is configured to receive a management frame from the first MLD, and the second NSTR capability is an NSTR capability between the first link and the second link after the channel switch.

[0297]

[0319] In a possible implementation, the second receiving module 1302 is further configured to receive first operating mode control information from the first MLD, where the first operating mode control information indicates a channel bandwidth of the first link, and the changed channel bandwidth is smaller than the channel bandwidth before the change.

[0298]

[0320] In a possible implementation, the second receiving module 1302 is further configured to receive second operating mode control information from the first MLD, where the second operating mode control information indicates that the channel bandwidth of the first link has changed and that the changed channel bandwidth is larger than the channel bandwidth before the change.

[0299]

[0321] All relevant contents of the steps in the above method embodiments can be cited in the functional descriptions of the corresponding functional modules, and the details will not be described again here.

[0300]

[0322] In this application, the second MLD 130 is presented in the form of functional modules obtained by dividing it in a unified manner. A "module" in this application may be an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other device capable of providing the aforementioned functionality.

[0301]

[0323] In some embodiments, for hardware implementation, one skilled in the art can appreciate that the second MLD 130 may be in the form of a WLAN device 500 shown in FIG.

[0302]

[0324] In one example, the function / implementation process of the processing module 1303 of FIG. 13 may be implemented by the processor 501 in the WLAN device 500 shown in FIG. 5 by invoking computer-executable instructions stored in the memory 504, and the function / implementation process of the transmitting module 1304, the first receiving module 1301, or the second receiving module 1302 of FIG. 13 may be implemented by using the transceiver 502 in the WLAN device 500 shown in FIG. 5.

[0303]

[0325] In some embodiments, when the second MLD 130 in FIG. 13 is a chip or a chip system, the function / implementation process of the transmitting module 1304, the first receiving module 1301, or the second receiving module 1302 may be implemented by using an input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 1303 may be implemented by using a processor (or processing circuit) of the chip or chip system.

[0304]

[0326] The second MLD 130 provided in this embodiment can perform the aforementioned method. Therefore, please refer to the aforementioned method embodiment for the technical effects that can be achieved by the second MLD 130. The details will not be described again here.

[0305]

[0327] In possible product forms, the first MLD and second MLD in this embodiment of the present application may further be implemented using one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuitry, or any combination of circuits capable of performing the various functions described herein.

[0306]

[0328] In some embodiments, embodiments of the present application further provide a communications device, the communications device including a processor configured to perform the method in any of the preceding method embodiments.

[0307]

[0329] In a possible implementation, the communication device further includes a memory. The memory is configured to store necessary computer programs or necessary instructions. The processor may call the computer programs or instructions stored in the memory to instruct the communication device to perform the method in any of the above-mentioned method embodiments. Of course, the memory may alternatively not be located within the communication device.

[0308]

[0330] In another possible implementation, the communication device further includes an interface circuit, which is a code / data read / write interface circuit configured to receive computer-executable instructions (which may be stored in a memory and read directly from the memory or read via another component) and transmit the computer-executable instructions to the processor.

[0309]

[0331] In yet another possible implementation, the communication device further includes a communication interface, the communication interface configured to communicate with a module other than the communication device.

[0310]

[0332] It will be understood that the communication device may be a chip or a chip system. When the communication device is a chip system, the chip system may include a chip, or may include a chip and other discrete devices. This is not particularly limited in the embodiments of the present application.

[0311]

[0333] In some embodiments, embodiments of the present application further provide a communications device. The communications device includes an interface circuit and a logic circuit. The interface circuit is configured to input information and / or output information. The logic circuit is configured to perform the method of any of the foregoing method embodiments to process the input information and / or generate output information.

[0312]

[0334] In a possible implementation, when the communication device is configured to implement the functionality of the first MLD:

[0335] In one possible design, the input information is an association request frame and a management frame, the association request frame including first information, the first information indicating a first NSTR capability between the first link and the second link, and the management frame including second information, the second information indicating a second NSTR capability between the first link and the second link.

[0313]

[0336] In one possible design, the input information is first operating mode control information, and the first operating mode control information indicates that the channel bandwidth of the first link is changed, and the changed channel bandwidth is smaller than the channel bandwidth before the change.

[0314]

[0337] In one possible design, the input information is second operating mode control information, and the second operating mode control information indicates that the channel bandwidth of the first link has changed and that the changed channel bandwidth is larger than the channel bandwidth before the change.

[0315]

[0338] In a possible implementation, when the communication device is configured to implement the functionality of the second MLD:

[0339] In one possible design, the output information is an association request frame and a management frame, the association request frame including first information, the first information indicating a first NSTR capability between the first link and the second link, and the management frame including second information, the second information indicating a second NSTR capability between the first link and the second link.

[0316]

[0340] In one possible design, the output information is first operating mode control information, and the first operating mode control information indicates that the channel bandwidth of the first link has changed, and the changed channel bandwidth is smaller than the channel bandwidth before the change.

[0317]

[0341] In one possible design, the output information is second operating mode control information, and the second operating mode control information indicates that the channel bandwidth of the first link has changed, and the changed channel bandwidth is larger than the channel bandwidth before the change.

[0318]

[0342] In a possible product form, the first MLD and the second MLD in the embodiments of the present application may be implemented by using a common bus architecture.

[0319]

[0343] For ease of explanation, please refer to Fig. 14. Fig. 14 is a schematic diagram of the structure of a communication device 1400 according to an embodiment of the present application. The communication device 1400 includes a processor 1401 and a transceiver 1402. The communication device 1400 may be a first MLD or a second MLD, or a chip within the first MLD or the second MLD. Fig. 14 shows only the main components of the communication device 1400. In addition to the processor 1401 and the transceiver 1402, the communication device may further include a memory 1403 and input / output devices (not shown).

[0320]

[0344] The processor 1401 is primarily configured to process communication protocols and communication data, control the entire communication device, execute software programs, and process data from the software programs. The memory 1403 is primarily configured to store software programs and data. The transceiver 1402 may include a radio frequency circuit and an antenna. The radio frequency 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. An input / output device, such as a touch screen, display, or keyboard, is primarily configured to receive data input by a user and output data to a user.

[0321]

[0345] The processor 1401, the transceiver 1402, and the memory 1403 may be connected via a communication bus.

[0322]

[0346] After the communication device is powered on, the processor 1401 may load a software program in the memory 1403, interpret and execute instructions of the software program, and process data of the software program. When data needs to be transmitted wirelessly, the processor 1401 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 by using 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 1401. The processor 1401 converts the baseband signal to data and processes the data.

[0323]

[0347] In another implementation, 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.

[0324]

[0348] The present application further provides a computer-readable storage medium, the computer-readable storage medium storing a computer program or instructions; when the computer program or instructions are executed by a processor, the functions of any of the aforementioned method embodiments are performed.

[0325]

[0349] The present application further provides a computer program product, which, when executed by a processor, performs the functions of any of the aforementioned method embodiments.

[0326]

[0350] Those skilled in the art will understand that for convenience and clarity of description, for the detailed operation processes of the aforementioned systems, devices and units, please refer to the corresponding processes in the aforementioned method embodiments, and the details will not be described again here.

[0327]

[0351] It will be understood that the systems, devices, and methods described in this application may alternatively be implemented in other manners. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical division of function, and actual implementation may involve other divisions. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. Furthermore, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented using some interface. Indirect couplings or communication connections between devices or units may be implemented in electronic, mechanical, or other forms.

[0328]

[0352] The units described as separate parts may or may not be physically separated, i.e., they may be co-located or distributed over multiple network units. The parts shown as units may or may not be physical units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.

[0329]

[0353] Furthermore, the functional units in the embodiments of the present application may be integrated into one processing unit, or each of the units may exist physically alone, or two or more units may be integrated into one unit.

[0330]

[0354] All or part of the above-described embodiments may be implemented using software, hardware, firmware, or any combination thereof. When a software program is used to implement an embodiment, the embodiment may be fully or partially embodied in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program or instructions are loaded into a computer and executed, the procedures or functions according to the embodiments of the present application are fully or partially performed. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, or Digital Subscriber Line (DSL)) or wireless (e.g., infrared, radio, or microwave) methods. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device such as a server or data center that integrates one or more available media. The available medium may be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., DVDs), semiconductor media (e.g., solid-state disks (SSDs)), etc. In embodiments of the present application, a computer may include the above-mentioned devices.

[0331]

[0355] Although the present application has been described with reference to embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other variations of the disclosed embodiments by studying the accompanying drawings, the disclosed content, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the words "a" or "any" do not exclude a plurality of cases. A single processor or other unit may perform several functions recited in the claims. Although some means are recited in mutually different dependent claims, this does not mean that these means cannot be combined to produce better effects.

[0332]

[0356] While the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Correspondingly, the specification and accompanying drawings are merely exemplary descriptions of the present application as defined by the appended claims, and any and all modifications, variations, combinations, or equivalents covering the scope of the present application are deemed to be included. It is apparent that those skilled in the art can make various modifications and variations to the present application without departing from the spirit and scope of the present application. The present application is intended to cover these modifications and variations of the present application, provided that they fall within the scope of protection defined by the following claims and their equivalent technologies.

Claims

1. 1. A method for indicating non-simultaneous transmit / receive capability, comprising: a step of transmitting a management frame from a first MLD to a second MLD, the management frame including information indicating a second NSTR capability between the first link and the second link after a channel switch; wherein the management frame includes a multi-link element, the second information is carried by the multi-link element, and the multi-link element is a basic variant multi-link element or an update variant multi-link element.

2. 2. The method of claim 1, wherein the multi-link element is an update variant multi-link element, and the update variant multi-link element includes a multi-link control field and a link information field; the multi-link control field includes a type field, the type field is set to a first value, the multi-link control field does not include a first field, the first field includes at least one of: a multi-link device medium access control address present field, a link identifier information present field, a change sequence present field, a multi-link capability present field, or an EMLSR capability present field; and The method, wherein the link information field includes an NSRT indication bitmap field, the second information is carried in the NSTR indication bitmap field, the link information field does not include a second field, and the second field includes at least one of: a completed profile field, a station medium access control address present field, a beacon interval present field, or a DTIM information present field.

3. 3. The method of claim 2, wherein the link information field further includes an NSTR link pair presence field and an NSTR bitmap size field, the NSTR link pair presence field indicating that the link information field includes the NSTR indication bitmap field, and the NSTR bitmap size field indicating the size of the NSTR indication bitmap field.

4. 2. The method of claim 1, wherein the management frame includes a third field, and when the value of the third field is a second value, it indicates that the management frame is used to update the NSTR capability between the first link and the second link.

5. 3. The method of claim 2, wherein the multi-link control field includes a type field, and the value of the type field is set to 2.

6. The method of claim 1 , wherein the management frame is an action frame.

7. 1. A method for indicating non-simultaneous transmit / receive capability, comprising: a step of receiving, by a second MLD, a management frame from a first MLD, wherein the second NSTR capability is an NSTR capability between the first link and the second link after the channel switch; wherein the management frame includes a multi-link element, information is carried on the multi-link element, and the multi-link element is a basic variant multi-link element or an update variant multi-link element.

8. 8. The method of claim 7, wherein the multi-link element is an update variant multi-link element, and the update variant multi-link element includes a multi-link control field and a link information field; the multi-link control field includes a type field, the type field is set to a first value, the multi-link control field does not include a first field, the first field includes at least one of: a multi-link device medium access control address present field, a link identifier information present field, a change sequence present field, a multi-link capability present field, or an EMLSR capability present field; and The method, wherein the link information field includes an NSRT indication bitmap field, the second information is carried in the NSTR indication bitmap field, the link information field does not include a second field, and the second field includes at least one of: a completed profile field, a station medium access control address present field, a beacon interval present field, or a DTIM information present field.

9. 9. The method of claim 8, wherein the link information field further includes an NSTR link pair presence field and an NSTR bitmap size field, the NSTR link pair presence field indicating that the link information field includes the NSTR indication bitmap field, and the NSTR bitmap size field indicating the size of the NSTR indication bitmap field.

10. 8. The method of claim 7, wherein the management frame includes a third field, and when the value of the third field is a second value, it indicates that the management frame is used to update the NSTR capability between the first link and the second link.

11. 9. The method of claim 8, wherein the multi-link control field includes a type field, and the value of the type field is set to 2.

12. The method of claim 7, wherein the management frame is an action frame.

13. 1. A communication device including a first transmitting module and a second transmitting module: the transmitting module is configured to transmit a management frame to the second MLD, the management frame including information, the information indicating a second NSTR capability between the first link and the second link after the channel switch; The apparatus, wherein the management frame includes a multi-link element, the second information is carried by the multi-link element, and the multi-link element is a basic variant multi-link element or an update variant multi-link element.

14. 14. The apparatus of claim 13, wherein the multi-link element is an update variant multi-link element, and the update variant multi-link element includes a multi-link control field and a link information field; the multi-link control field includes a type field, the type field is set to a first value, the multi-link control field does not include a first field, the first field includes at least one of: a multi-link device medium access control address present field, a link identifier information present field, a change sequence present field, a multi-link capability present field, or an EMLSR capability present field; and the link information field includes an NSRT indication bitmap field, the second information is carried in the NSTR indication bitmap field, the link information field does not include a second field, and the second field includes at least one of: a completed profile field, a station medium access control address present field, a beacon interval present field, or a DTIM information present field.

15. 15. The apparatus of claim 14, wherein the link information field further includes an NSTR link pair presence field and an NSTR bitmap size field, the NSTR link pair presence field indicating that the link information field includes the NSTR indication bitmap field, and the NSTR bitmap size field indicating the size of the NSTR indication bitmap field.

16. 14. The apparatus of claim 13, wherein the management frame includes a third field, and when the value of the third field is a second value, it indicates that the management frame is used to update the NSTR capability between the first link and the second link.

17. 15. The apparatus of claim 14, wherein the multi-link control field includes a type field, and the value of the type field is set to 2.

18. 14. The apparatus of claim 13, wherein the management frame is an action frame.

19. 1. A communication device including a receiving module: receiving a management frame from the first MLD, the second NSTR capability being an NSTR capability between the first link and the second link after the channel switch; The apparatus, wherein the management frame includes a multi-link element, information is carried on the multi-link element, and the multi-link element is a basic variant multi-link element or an update variant multi-link element.

20. 20. The apparatus of claim 19, wherein the multi-link element is an update variant multi-link element, the update variant multi-link element including a multi-link control field and a link information field; the multi-link control field includes a type field, the type field is set to a first value, the multi-link control field does not include a first field, the first field includes at least one of: a multi-link device medium access control address present field, a link identifier information present field, a change sequence present field, a multi-link capability present field, or an EMLSR capability present field; and the link information field includes an NSRT indication bitmap field, the second information is carried in the NSTR indication bitmap field, the link information field does not include a second field, and the second field includes at least one of: a completed profile field, a station medium access control address present field, a beacon interval present field, or a DTIM information present field.

21. 21. The apparatus of claim 20, wherein the link information field further includes an NSTR link pair presence field and an NSTR bitmap size field, the NSTR link pair presence field indicating that the link information field includes the NSTR indication bitmap field, and the NSTR bitmap size field indicating the size of the NSTR indication bitmap field.

22. 20. The apparatus of claim 19, wherein the management frame includes a third field, and when the value of the third field is a second value, it indicates that the management frame is used to update the NSTR capability between the first link and the second link.

23. 21. The apparatus of claim 20, wherein the multi-link control field includes a type field, and the value of the type field is set to 2.

24. 20. The apparatus of claim 19, wherein the management frame is an action frame.

25. 13. A computer readable storage medium comprising instructions which, when executed on a communications device, enable the communications device to perform a method according to any one of claims 1 to 6 or enable the communications device to perform a method according to any one of claims 7 to 12.

26. 13. A communication device comprising a processor and a communication interface, the communication interface being configured to communicate with a module other than the communication device, the processor being configured to execute a computer program or instructions to perform a method according to any one of claims 1 to 6 or to perform a method according to any one of claims 7 to 12.

Images