Method and device for determining data buffer status

Abstract

To provide a method and a device for determining a data buffer status applicable to a wireless LAN system such as IEEE 802.11be.SOLUTION: In the method, a first multi-link device (MLD) receives first instruction information from a second MLD. The method determines a buffer status of bufferable data corresponding to at least one data type and stored in the second MLD, on the basis of the first instruction information and the correspondence relationship between an association identifier of the first MLD and a data type supported by the first MLD. The first instruction information corresponds to the association identifier of the first MLD, and is used to indicate the buffer status of the bufferable data stored in the second MLD. The first MLD receives the first instruction information to determine a data buffer status corresponding to the type of data stored in the second MLD.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001]

[0001] This application claims priority to Chinese Patent Application No. 202010180304.6, entitled "Method and Apparatus for Determining Data Buffer Status," filed with the State Intellectual Property Office of the People's Republic of China on March 13, 2020, the entire contents of which are incorporated herein by reference.

[0002]

[0002] TECHNICAL FIELD The present invention relates to the field of communications technology, and more particularly to a method and apparatus for determining data buffer status. [Background technology]

[0003]

[0003] The goal of the development and evolution of cellular networks and wireless local area networks (WLANs) is to continuously increase throughput. To achieve extremely high throughput, the next generation standard IEEE 802.11be uses multi-link (ML) as one of the key technologies. A multi-link device (MLD) that has the ability to transmit and receive data in multiple bands can transmit data using a larger bandwidth. This significantly increases the throughput. An MLD contains multiple stations (STAs), and each station can establish a link to one station in another MLD for communication.

[0004]

[0004] A non-access point (non-AP) station may be in an active state or a doze state. When a non-AP station is in an active state, the link corresponding to the non-AP station is also in an active state, and data can be transmitted between the non-AP station and the AP station via the link. When a non-AP station is in a doze state, the link corresponding to the non-AP station is also in a doze state, and data cannot be transmitted between the non-AP station and the AP station.

[0005]

[0005] When the non-AP station is in a doze state, the AP MLD is capable of buffering data services to be transmitted to the non-AP station, and when the non-AP station is in an active state, it transmits the bufferable data services to the non-AP station via a link corresponding to the non-AP station.

[0006]

[0006] However, the non-AP MLD cannot know the buffer status of the bufferable data corresponding to the non-AP MLD in the AP MLD. This does not contribute to the non-AP MLD to accurately determine the operation state of the associated link. Therefore, how to determine the buffer status of the bufferable data corresponding to the non-AP MLD in the AP MLD becomes an urgent technical problem to be solved. Summary of the Invention

[0007]

[0007] The embodiments of the present application provide a method and apparatus for determining a data buffer status, and determine the data buffer status in a dimension of a data type.

[0008]

[0008] According to a first aspect, an embodiment of the present application provides a method for determining a data buffer status, the method including: a first multi-link device (MLD) receiving first indication information from a second MLD, the first indication information being used to indicate a buffer status of bufferable data in the second MLD corresponding to an association identifier of the first MLD; and the first MLD determining a buffer status of bufferable data in the second MLD corresponding to at least one data type based on the first indication information and a correspondence between the association identifier of the first MLD and data types supported by the first MLD.

[0009]

[0009] In this technical solution, a buffer status of bufferable data in a second MLD, which corresponds to at least one data type supported by a first MLD, can be determined.

[0010]

[0010] In an implementation, the first MLD may have a plurality of stations. The method may further include the first MLD determining an operation state of at least one station of the plurality of stations based on a buffer status of bufferable data corresponding to the at least one data type and in the second MLD, where the operation state is an active state or a doze state.

[0011]

[0011] In this technical solution, a more suitable working state is determined for a station in the first MLD based on the data type of the bufferable data, which helps to reduce power consumption.

[0012]

[0012] In implementation, the method may further include a step of the first MLD receiving second instruction information from the second MLD, wherein the second instruction information is used to determine a correspondence between the related information of the first MLD and the data types supported by the first MLD.

[0013]

[0013] In an implementation, the second indication information indicates at least one association identifier, and the at least one association identifier corresponds to at least one data type.

[0014]

[0014] In this technical solution, at least one association identifier (AID) corresponding to at least one data type is indicated by using second indication information, so that the AID can be more flexibly assigned to the first MLD.

[0015]

[0015] In an implementation, the first MLD supports a plurality of data types. The second indication information indicates a first association identifier, and the first association identifier corresponds to a first data type of the plurality of data types. The method may further include the first MLD determining, based on the first association identifier corresponding to the first data type, an association identifier corresponding to a data type other than the first data type of the plurality of data types.

[0016]

[0016] In this technical solution, the AID is indicated in the second indication information, which can effectively reduce signaling overhead.

[0017]

[0017] According to a second aspect, the embodiment of the present application provides another method for determining a data buffer status, the method includes the steps of: a second multi-link device (MLD) determining a buffer status of bufferable data in the second MLD, which corresponds to at least one data type supported by the first MLD; determining a buffer status of bufferable data in the second MLD, which corresponds to an association identifier, based on the buffer status of the bufferable data in the second MLD, which corresponds to the at least one data type, and a correspondence between an association identifier of the first MLD and the supported data type; and sending first indication information to the first MLD, the first indication information being used to indicate the buffer status of the bufferable data in the second MLD, which corresponds to the association identifier of the first MLD.

[0018]

[0018] In this technical solution, a buffer status of bufferable data in a second MLD corresponding to an association identifier of a first MLD is indicated, which helps the first MLD to determine a buffer status of bufferable data in the second MLD corresponding to at least one data type based on the correspondence between the association identifier and the supported data type.

[0019]

[0019] In implementation, the method may further include a step of the second MLD sending second instruction information to the first MLD, wherein the second instruction information is used to determine a correspondence between an association identifier of the first MLD and a data type supported by the first MLD.

[0020]

[0020] In an implementation, the second indication information indicates at least one association identifier, and the at least one association identifier corresponds to at least one data type.

[0021]

[0021] In this technical solution, at least one association identifier (AID) corresponding to at least one data type is indicated by using second indication information, so that the AID can be more flexibly assigned to the first MLD.

[0022] In an implementation, the first MLD supports a plurality of data types, and the second indication indicates a first association identifier, the first association identifier corresponding to a first data type of the plurality of data types.

[0023]

[0023] In this technical solution, the AID is indicated in the second indication information, which can effectively reduce the signaling overhead.

[0024]

[0024] According to a third aspect, the embodiment of the present application provides yet another method for determining a data buffer status, the method including: a first multi-link device MLD receiving bufferable data from a second MLD via a first link, the bufferable data including third indication information, the third indication information being used to indicate whether the bufferable data corresponding to at least one second data type is buffered in the second MLD, the second data type being any data type mapped to the first link; and a step of the first MLD determining whether the bufferable data corresponding to at least one second data type is buffered in the second MLD based on the third indication information.

[0025]

[0025] In this technical solution, whether the bufferable data corresponding to at least one second data type is buffered in the second MLD can be determined based on the third indication information. In other words, whether the bufferable data can be transmitted to the first MLD via the first link can be determined based on the third indication information.

[0026]

[0026] In an implementation, the first MLD has a plurality of stations. The method further includes the step of the first MLD determining an operation state of a station corresponding to the first link among the plurality of stations based on whether bufferable data corresponding to at least one second data type is buffered in the second MLD, and the operation state is an active state or a doze state.

[0027]

[0027] In this technical solution, a more appropriate operating state is determined for a station corresponding to the first link based on whether bufferable data corresponding to at least one second data type is buffered in the second MLD.

[0028]

[0028] In an implementation, a particular implementation in which a first MLD determines an operational state of a station corresponding to a first link among a plurality of stations based on whether bufferable data corresponding to at least one second data type is buffered in the second MLD may be as follows: if bufferable data corresponding to at least one second data type is buffered in the second MLD, determine an operational state of the station corresponding to the first link among the plurality of stations as an active state; or if no bufferable data corresponding to any second data type is buffered in the second MLD, determine an operational state of the station corresponding to the first link among the plurality of stations as an active state or a doze state.

[0029]

[0029] In this technical solution, when at least one bufferable data corresponding to a second data type is buffered in the second MLD, the working state of the station corresponding to the first link is active. If the bufferable data cannot be transmitted due to link congestion (or cases such as interference) in link 1, and the data type of the bufferable data to be transmitted in link 1 is also mapped to the first link, the station corresponding to the first link is in active state, i.e., link 1 is in doze state, before the bufferable data corresponding to the data type is completely transmitted. Therefore, the second MLD can schedule the bufferable data to be transmitted in link 1 to the first link for transmission. In this way, a more suitable working state is determined for the station, and the bufferable data in the second MLD is successfully transmitted to the first MLD.

[0030]

[0030] In an implementation, the third indication indicates that at least one bufferable data corresponding to the second data type is buffered in the second MLD. The method further includes receiving a fourth indication from the second MLD, the fourth indication being used to indicate that no bufferable data corresponding to any second data type is buffered in the second MLD.

[0031]

[0031] In this technical solution, the fourth indication information may be a quality of service null (QoS Null) frame. If the second MLD cannot transmit the bufferable data to the second MLD via the first link and cannot indicate that the bufferable data corresponding to some second data type is not buffered in the second MLD by using the third indication information in the bufferable data, the first MLD can determine that the bufferable data corresponding to some second data type is not buffered in the second MLD based on the fourth indication information from the second MLD.

[0032]

[0032] According to a fourth aspect, the embodiment of the present application provides yet another method for determining a data buffer status, the method including: a step of a second multi-link device MLD determining whether bufferable data corresponding to at least one second data type is buffered in the second MLD, the second data type being any data type mapped to the first link; and a step of the second MLD transmitting the bufferable data to the first MLD via the first link, the bufferable data including third indication information, the third indication information being used to indicate whether bufferable data corresponding to at least one second data type is buffered in the second MLD.

[0033]

[0033] In this technical solution, whether the bufferable data corresponding to at least one second data type is buffered in the second MLD can be indicated by using the third indication information. In other words, whether the bufferable data is transmitted to the first MLD via the first link can be indicated by using the third indication information.

[0034]

[0034] In an implementation, the third indication information indicates that at least one bufferable data corresponding to the second data type is buffered in the second MLD. The method further includes the second MLD sending fourth indication information to the first MLD, where the fourth indication information is used to indicate that no bufferable data corresponding to any second data type is buffered in the second MLD.

[0035]

[0035] In this technical solution, the fourth indication information may be a QoS Null frame. If the second MLD cannot send the bufferable data to the second MLD through the first link and cannot indicate that the bufferable data corresponding to some second data type is not buffered in the second MLD by using the third indication information in the bufferable data, the second MLD can indicate that the bufferable data corresponding to some second data type is not buffered in the second MLD by sending the fourth indication information to the first MLD.

[0036]

[0036] According to a sixth aspect, an embodiment of the present application provides yet another method for determining a data buffer status, the method including: a first multi-link device MLD receiving bufferable data corresponding to a third data type from a second MLD, the bufferable data including fifth indication information, the fifth indication information being used to indicate whether the bufferable data corresponding to the third data type is buffered in the second MLD; and the first MLD determining whether the bufferable data corresponding to the third data type is buffered in the second MLD based on the fifth indication information.

[0037]

[0037] In this technical solution, whether the bufferable data corresponding to the third data type is buffered in the second MLD may be determined based on fifth indication information in the bufferable data corresponding to the third data type.

[0038]

[0038] In the implementation, the first MLD has a plurality of stations. The method further includes the step of the first MLD determining an operation state of a station corresponding to the second link among the plurality of stations based on whether bufferable data corresponding to a third data type is buffered in the second MLD, the third data type is mapped to the second link, and the operation state is an active state or a doze state.

[0039]

[0039] In this technical solution, a more appropriate operating state is determined for a station corresponding to the second link based on whether bufferable data corresponding to a third data type is buffered in the second MLD.

[0040]

[0040] In the implementation, the method further includes the step of the first MLD determining whether a data type other than the third data type is mapped to the second link. A specific implementation of the first MLD determining the operation state of the station corresponding to the second link among the multiple stations based on whether the bufferable data corresponding to the third data type is buffered in the second MLD may be as follows: the first MLD determines the operation state of the station corresponding to the second link among the multiple stations based on whether the bufferable data corresponding to the third data type is buffered in the second MLD and whether a data type other than the third data type is mapped to the second link.

[0041]

[0041] In an implementation, the fifth indication indicates that the bufferable data corresponding to the third data type is not buffered in the second MLD. The bufferable data corresponding to the third data type received by the first MLD from the second MLD may further include sixth indication, which is used to indicate whether at least one bufferable data corresponding to a fourth data type is buffered in the second MLD, and the fourth data type is any data type other than the third data type among the data types supported by the first MLD.

[0042]

[0042] In this technical solution, whether the bufferable data corresponding to at least one fourth data type is buffered in the second MLD may be determined based on the sixth indication information. That is, the buffer status of the bufferable data corresponding to a data type other than the third data type and in the second MLD may be determined based on the sixth indication information, and the first MLD can know a more detailed buffer status. This helps to determine a more suitable operating state for the station in the first MLD.

[0043]

[0043] In implementation, the priority of the fourth data type is higher than the priority of the third data type.

[0044]

[0044] According to a sixth aspect, the present embodiment provides yet another method for determining a data buffer status, the method including: a step of a second multi-link device (MLD) determining whether bufferable data corresponding to a third data type is buffered in the second MLD; and a step of the second MLD sending bufferable data corresponding to the third data type to the first MLD, the bufferable data including fifth indication information, the fifth indication information being used to indicate whether bufferable data corresponding to the third data type is buffered in the second MLD.

[0045]

[0045] In this technical solution, whether the bufferable data corresponding to the third data type is buffered in the second MLD can be determined based on fifth indication information in the bufferable data corresponding to the third data type.

[0046]

[0046] In an implementation, the fifth indication indicates that no bufferable data corresponding to the third data type is buffered in the second MLD. The bufferable data corresponding to the third data type sent by the second MLD to the first MLD further includes sixth indication, which is used to indicate whether at least one bufferable data corresponding to a fourth data type is buffered in the second MLD, and the fourth data type is any data type other than the third data type among the data types supported by the first MLD.

[0047]

[0047] In this technical solution, whether the bufferable data corresponding to at least one fourth data type is buffered in the second MLD can be indicated by using the sixth indication information, that is, the buffer status of the bufferable data corresponding to a data type other than the third data type and in the second MLD can be indicated by using the sixth indication information.

[0048]

[0048] In implementation, the priority of the fourth data type is higher than the priority of the third data type.

[0049]

[0049] According to a seventh aspect, an embodiment of the present application provides yet another method for determining a data buffer status, the method including: a first multi-link device MLD receiving seventh indication information from a second MLD, the seventh indication information being used to indicate that bufferable data corresponding to a fifth data type is not buffered in the second MLD, the fifth data type being any one data type supported by the first MLD; and the first MLD determining, based on the seventh indication information, that bufferable data corresponding to the fifth data type is not buffered in the second MLD.

[0050]

[0050] In this technical solution, if the bufferable data corresponding to the fifth data type is not buffered in the second MLD, the second MLD transfers the bufferable data corresponding to the fifth data type to the first MLD. 1 The first MLD cannot determine that the bufferable data corresponding to the fifth data type is not buffered in the second MLD based on the seventh indication information from the second MLD. The first MLD cannot determine that the bufferable data corresponding to the fifth data type is not buffered in the second MLD based on the “More Data” subfield in the bufferable data corresponding to the fifth data type. In this case, the first MLD can determine that the bufferable data corresponding to the fifth data type is not buffered in the second MLD based on the seventh indication information from the second MLD.

[0051]

[0051] In an implementation, the first MLD has a plurality of stations. The method further includes the step of the first MLD determining an operation state of a station among the plurality of stations corresponding to a third link based on the bufferable data corresponding to a fifth data type not being buffered in the second MLD, the fifth data type being mapped to the third link, and the operation state being an active state or a doze state.

[0052]

[0052] In this technical solution, a more appropriate operating state is determined for a station corresponding to the third link based on the fact that bufferable data corresponding to the fifth data type is not buffered in the second MLD.

[0053]

[0053] According to an eighth aspect, an embodiment of the present application provides yet another method for determining a data buffer status, the method including: determining, by a second multi-link device MLD, that bufferable data corresponding to a fifth data type is not buffered in the second MLD, the fifth data type being any one of data types supported by the first MLD; and sending, by the second MLD, seventh indication information to the first MLD, the seventh indication information being used to indicate that bufferable data corresponding to the fifth data type is not buffered in the second MLD.

[0054]

[0054] In this technical solution, if the bufferable data corresponding to the fifth data type is not buffered in the second MLD, the second MLD transfers the bufferable data corresponding to the fifth data type to the first MLD. 1 and cannot indicate that the bufferable data corresponding to the fifth data type is not buffered in the second MLD by using a More Data subfield in the bufferable data corresponding to the fifth data type. In this case, the second MLD can determine that the bufferable data corresponding to the fifth data type is not buffered in the second MLD by sending the seventh indication information to the first MLD.

[0055]

[0055] According to a ninth aspect, the embodiment of the present application provides yet another method for determining a data buffer status, the method including: a first multi-link device MLD receiving eighth indication information from a second MLD via a fourth link, the eighth indication information being used to indicate that bufferable data corresponding to a data type mapped to the fourth link is not buffered in the second MLD; and the first MLD determining, based on the eighth indication information, that bufferable data corresponding to a data type mapped to the fourth link is not buffered in the second MLD.

[0056]

[0056] In this technical solution, the first MLD can determine, based on the eighth instruction information, that bufferable data corresponding to some data type mapped to the fourth link is not buffered in the second MLD, i.e., the second MLD can determine not to transmit data to the first MLD via the fourth link any more.

[0057]

[0057] In an implementation, the first MLD has a plurality of stations. The method further includes the step of the first MLD determining an operation state of a station among the plurality of stations corresponding to a fourth link based on bufferable data corresponding to any data type mapped to the fourth link not being buffered in the second MLD, the operation state being an active state or a doze state.

[0058]

[0058] In this technical solution, a more appropriate operating state is determined for a station corresponding to the fourth link based on the fact that bufferable data corresponding to some data type mapped to the fourth link is not buffered in the second MLD.

[0059]

[0059] According to a tenth aspect, the embodiment of the present application provides yet another method for determining a data buffer status, the method including: a step of a second multi-link device MLD determining that bufferable data corresponding to a data type mapped to a fourth link is not buffered in the second MLD; and a step of the second MLD sending eighth indication information to the first MLD via the fourth link, the eighth indication information being used to indicate that bufferable data corresponding to a data type mapped to the fourth link is not buffered in the second MLD.

[0060]

[0060] In this technical solution, the second MLD can indicate that bufferable data corresponding to some data type mapped to the fourth link is not buffered in the second MLD by sending the eighth indication information to the first MLD, i.e., the second MLD can indicate that it will no longer send data to the first MLD via the fourth link.

[0061]

[0061] According to an eleventh aspect, the embodiment of the present application provides yet another method for determining a data buffer status, the method including: a first multi-link device MLD receiving ninth indication information from a second MLD, the ninth indication information being used to indicate a buffer status of bufferable data in the second MLD, which corresponds to at least one data type supported by the first MLD; and the first MLD determining a buffer status of the bufferable data in the second MLD, which corresponds to the at least one data type, based on the ninth indication information.

[0062]

[0062] In this technical solution, the first MLD can determine a buffer status of bufferable data corresponding to more than one data type and located in the second MLD based on the ninth indication information.

[0063]

[0063] In an implementation, the first MLD has a plurality of stations. The method further includes the first MLD determining an operation state of at least one station of the plurality of stations based on a buffer status of bufferable data corresponding to at least one data type and in the second MLD, the operation state being an active state or a doze state.

[0064]

[0064] In this technical solution, a more suitable operating state is determined for a station in the first MLD based on a buffer status of bufferable data corresponding to at least one data type and located in the second MLD.

[0065]

[0065] According to a twelfth aspect, an embodiment of the present application provides yet another method for determining a data buffer status, the method including: a step of a second multi-link device (MLD) determining a buffer status of bufferable data in the second MLD, the bufferable data corresponding to at least one data type supported by the first MLD; and a step of the second MLD sending ninth indication information to the first MLD, the ninth indication information being used to indicate a buffer status of the bufferable data in the second MLD, the bufferable data corresponding to at least one data type supported by the first MLD.

[0066]

[0066] In this technical solution, the second MLD can indicate to the first MLD the buffer status of bufferable data corresponding to more than one data type and located in the second MLD by using the ninth indication information.

[0067]

[0067] According to a thirteenth aspect, the embodiment of the present application provides yet another method for determining a data buffer status, the method including: a first multi-link device MLD receiving tenth indication information from a second MLD, the tenth indication information being used to indicate a buffer status of bufferable data in the second MLD, corresponding to at least one data type mapped to at least one link corresponding to the first MLD; and the first MLD determining a buffer status of bufferable data in the second MLD, corresponding to at least one data type mapped to at least one link, based on the tenth indication information.

[0068]

[0068] In this technical solution, a buffer status of the bufferable data in the second MLD, which corresponds to at least one data type mapped to at least one link, can be determined based on the tenth indication information. In this way, the buffer status of the bufferable data in the second MLD can be determined in more detail.

[0069]

[0069] In an implementation, the first MLD has a plurality of stations, and the method further includes determining an operation state of at least one station of the plurality of stations based on a buffer status of bufferable data in the second MLD corresponding to at least one data type mapped to at least one link, the operation state being an active state or a doze state.

[0070]

[0070] In this technical solution, a more suitable operating state is determined for a station in the first MLD based on the buffer status of bufferable data corresponding to at least one data type mapped to at least one link and located in the second MLD.

[0071]

[0071] According to a fourteenth aspect, the present embodiment provides yet another method for determining a data buffer status, the method including: a second multi-link device (MLD) determining a buffer status of bufferable data in the second MLD, the buffer status corresponding to at least one data type mapped to at least one link corresponding to the first MLD; and the second MLD sending tenth indication information to the first MLD, the tenth indication information being used to indicate a buffer status of bufferable data in the second MLD, the buffer status corresponding to the at least one data type mapped to at least one link corresponding to the first MLD.

[0072]

[0072] In this technical solution, the second MLD can indicate to the first MLD a buffer status of the bufferable data in the second MLD, which corresponds to at least one data type mapped to at least one link, by using the tenth indication information. In this way, the buffer status of the bufferable data in the second MLD can be indicated in more detail.

[0073]

[0073] According to a fifteenth aspect, an embodiment of the present application provides a communication device. The communication device has all or part of the functions of implementing the first MLD in the example method according to the first, third, fifth, seventh, ninth, eleventh, or thirteenth aspects. For example, the communication device may have the functions of implementing some or all of the embodiments of the present application, or may have the functions of independently implementing any of the embodiments of the present application. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions.

[0074]

[0074] In the implementation, the structure of the communication device may include a processing unit and a communication unit. The processing unit is configured to support the communication device in performing corresponding functions in the aforementioned method. The communication unit is configured to support communication between the communication device and other devices. The communication device may further include a storage unit. The storage unit is configured to support the processing unit and communication The storage unit is configured to be coupled to the unit and stores computer programs and data required for the communication device.

[0075]

[0075] In an implementation, when the communication device has some or all of the functions to realize the first MLD in the example method according to the first aspect, the communication device includes: a communication unit configured to receive first indication information from a second MLD, the first indication information being used to indicate a buffer status of bufferable data that corresponds to an association identifier of the communication device and is in the second MLD; and and a processing unit configured to determine a buffer status of bufferable data in the second MLD, the buffer status corresponding to the at least one data type, based on the first indication information and a correspondence between an association identifier of the first MLD and a data type supported by the first MLD.

[0076]

[0076] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0077]

[0077] In an implementation, when the communication device has some or all of the functions to realize the first MLD in the example method according to the first aspect, the communication device includes: a transceiver configured to receive first indication information from a second MLD, the first indication information corresponding to an association identifier of the communication device and used to indicate a buffer status of bufferable data in the second MLD; and The processor is configured to determine a buffer status of bufferable data in the second MLD that corresponds to the at least one data type based on the first indication information and a correspondence between an association identifier of the first MLD and data types supported by the first MLD.

[0078]

[0078] In an implementation, when the communication device has some or all of the functions for realizing the first MLD in the example method according to the third aspect, the communication device includes: a communication unit configured to receive bufferable data from a second MLD via a first link, the bufferable data including third indication information, the third indication information being used to indicate whether bufferable data corresponding to at least one second data type is buffered in the second MLD, the second data type being any data type that is mapped to the first link; and A processing unit configured to determine, based on the third indication information, whether bufferable data corresponding to the at least one second data type is buffered in the second MLD.

[0079]

[0079] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0080]

[0080] In an implementation, when the communication device has some or all of the functions to realize the first MLD in the example method according to the third aspect, the communication device includes: a transceiver configured to receive bufferable data from a second MLD over a first link, the bufferable data including third indication information, the third indication information being used to indicate whether bufferable data corresponding to at least one second data type is buffered in the second MLD, the second data type being any data type that is mapped to the first link; and The processor configured to determine, based on the third indication, whether bufferable data corresponding to the at least one second data type is buffered in the second MLD.

[0081]

[0081] In an implementation, when the communication device has some or all of the functions to realize the first MLD in the example method according to the fifth aspect, the communication device includes: a communication unit configured to receive bufferable data corresponding to a third data type from a second MLD, the bufferable data including fifth indication information, the fifth indication information being used to indicate whether the bufferable data corresponding to the third data type is buffered in the second MLD; and A processing unit configured to determine, based on the fifth indication, whether bufferable data corresponding to the third data type is buffered in the second MLD.

[0082]

[0082] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0083]

[0083] In an implementation, when the communication device has some or all of the functions to realize the first MLD in the example method according to the fifth aspect, the communication device includes: a transceiver for receiving bufferable data corresponding to a third data type from a second MLD, the bufferable data including fifth indication information, the fifth indication information being used to indicate whether the bufferable data corresponding to the third data type is buffered in the second MLD; and The processor configured to determine, based on the fifth indication, whether bufferable data corresponding to the third data type is buffered in the second MLD.

[0084]

[0084] In an implementation, when the communication device has some or all of the functions to realize the first MLD in the example method according to the seventh aspect, the communication device includes: a communication unit configured to receive a seventh indication from a second MLD, the seventh indication being used to indicate that bufferable data corresponding to a fifth data type is not buffered in the second MLD, the fifth data type being any one of the data types supported by the communication device; and A processing unit configured to determine, based on the seventh indication information, that no bufferable data corresponding to the fifth data type is buffered in the second MLD.

[0085]

[0085] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0086]

[0086] In an implementation, when the communication device has some or all of the functions to realize the first MLD in the example method according to the seventh aspect, the communication device includes: a transceiver configured to receive a seventh indication from a second MLD, the seventh indication being used to indicate that bufferable data corresponding to a fifth data type is not buffered in the second MLD, the fifth data type being any one of the data types supported by the communication device; and A processor configured to determine, based on the seventh indication information, that no bufferable data corresponding to the fifth data type is buffered in the second MLD.

[0087]

[0087] In an implementation, when the communication device has some or all of the functions to realize the first MLD in the example method according to the ninth aspect, the communication device includes: a communication unit configured to receive an eighth indication from the second MLD via the fourth link, the eighth indication being used to indicate that bufferable data corresponding to a certain data type mapped to the fourth link is not buffered in the second MLD; and A processing unit configured to determine, based on the eighth indication information, that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD.

[0088]

[0088] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0089]

[0089] In an implementation, when the communication device has some or all of the functions to realize the first MLD in the example method according to the ninth aspect, the communication device includes: a transceiver configured to receive an eighth indication from the second MLD over a fourth link, the eighth indication being used to indicate that bufferable data corresponding to a data type mapped to the fourth link is not buffered in the second MLD; and The processor configured to determine, based on the eighth indication, that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD.

[0090]

[0090] In an implementation, when the communication device has some or all of the functions for realizing the first MLD in the example method according to the eleventh aspect, the communication device includes: a communication unit configured to receive ninth indication information from the second MLD, the ninth indication information being used to indicate a buffer status of bufferable data in the second MLD, the bufferable data corresponding to at least one data type supported by the communication device; and A processing unit configured to determine, based on the ninth indication, a buffer status of bufferable data corresponding to the at least one data type and located in the second MLD.

[0091]

[0091] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0092]

[0092] In an implementation, when the communication device has some or all of the functions for realizing the first MLD in the example method according to the eleventh aspect, the communication device includes: a transceiver configured to receive ninth indication information from the second MLD, the ninth indication information being used to indicate a buffer status of bufferable data in the second MLD, the bufferable data corresponding to at least one data type supported by the communication device; and The processor configured to determine a buffer status of bufferable data corresponding to the at least one data type and located in the second MLD based on the ninth indication.

[0093]

[0093] In an implementation, when the communication device has some or all of the functionality for realizing the first MLD in the example method according to the thirteenth aspect, the communication device includes: a communication unit configured to receive tenth indication information from the second MLD, the tenth indication information being used to indicate a buffer status of bufferable data in the second MLD, the bufferable data corresponding to at least one data type mapped to at least one link corresponding to the communication device; and A processing unit configured to determine, based on the tenth indication, a buffer status of bufferable data, corresponding to the at least one data type mapped to the at least one link and located in the second MLD.

[0094]

[0094] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0095]

[0095] In an implementation, when the communication device has some or all of the functions to realize the first MLD in the example method according to the thirteenth aspect, the communication device includes: a transceiver configured to receive tenth indication information from a second MLD, the tenth indication information being used to indicate a buffer status of bufferable data in the second MLD, the bufferable data corresponding to at least one data type mapped to at least one link corresponding to the communication device; and A processor configured to determine a buffer status of bufferable data in the second MLD corresponding to at least one data type mapped to the at least one link based on the tenth indication information.

[0096]

[0096] According to a sixteenth aspect, an embodiment of the present application provides another communication device. The communication device has all or part of the functions of implementing the second MLD in the example method according to the second, fourth, sixth, eighth, tenth, twelfth, or fourteenth aspects. For example, the communication device may have the functions of implementing some or all of the embodiments of the present application, or may have the functions of independently implementing any of the embodiments of the present application. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions.

[0097]

[0097] In implementation, the structure of the communication device may include a processing unit, a storage unit, and a communication unit. The processing unit is configured to support the communication device in performing corresponding functions in the aforementioned method. The communication unit is configured to support communication between the communication device and other devices. The storage unit is configured to support the processing unit and communication The storage unit is configured to be coupled to the communication device and stores computer programs and data required for the communication device. The storage unit is configured to store bufferable data.

[0098]

[0098] In an implementation, when the communication device has some or all of the functions to realize the second MLD in the example method according to the second aspect, the communication device includes: a processing unit configured to determine a buffer status of bufferable data in the second MLD, the buffer status corresponding to at least one data type supported by the first MLD; and to determine a buffer status of bufferable data in the storage unit, the buffer status corresponding to the association identifier based on a correspondence between the association identifier of the first MLD and the supported data types; and A communication unit configured to transmit first indication information to a first MLD, the first indication information being used to indicate a buffer status of bufferable data corresponding to an association identifier of the first MLD and residing in a storage unit.

[0099]

[0099] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0100]

[0100] In an implementation, when the communication device has some or all of the functions for realizing the second MLD in the example method according to the second aspect, the communication device includes: a processor configured to determine a buffer status of bufferable data corresponding to at least one data type supported by the first MLD and residing in the memory; and determine a buffer status of bufferable data corresponding to the association identifier and residing in the memory based on the buffer status of the bufferable data corresponding to the at least one data type and residing in the memory and a correspondence between the association identifier of the first MLD and the supported data types; and A transceiver configured to transmit first indication information to a first MLD, the first indication information being used to indicate a buffer status of bufferable data that corresponds to an association identifier of the first MLD and is in a memory.

[0101]

[0101] In an implementation, when the communication device has some or all of the functions for realizing the second MLD in the example method according to the fourth aspect, the communication device includes: a processing unit configured to determine whether bufferable data corresponding to at least one second data type is buffered in the storage unit, the second data type being any data type that is mapped to the first link; and A communication unit configured to transmit bufferable data to a first MLD via a first link, the bufferable data including third indication information, the third indication information being used to indicate whether the bufferable data corresponding to at least one second data type is buffered in a storage unit.

[0102]

[0102] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0103]

[0103] In an implementation, when the communication device has some or all of the functions for realizing the second MLD in the example method according to the fourth aspect, the communication device includes: a processor configured to determine whether bufferable data corresponding to at least one second data type is buffered in a memory, the second data type being any data type that is mapped to the first link; and A transceiver configured to transmit bufferable data to a first MLD over a first link, the bufferable data including third indication information, the third indication information used to indicate whether the bufferable data corresponding to at least one second data type is buffered in a memory.

[0104]

[0104] In an implementation, when the communication device has some or all of the functions for realizing the second MLD in the example method according to the sixth aspect, the communication device includes: a processing unit configured to determine whether bufferable data corresponding to a third data type is buffered in the storage unit; and A communication unit configured to transmit bufferable data corresponding to a third data type to a first MLD, the bufferable data including fifth indication information, the fifth indication information being used to indicate whether the bufferable data corresponding to the third data type is buffered in a storage unit.

[0105]

[0105] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0106]

[0106] In an implementation, when the communication device has some or all of the functions for realizing the second MLD in the example method according to the sixth aspect, the communication device includes: a processor configured to determine whether bufferable data corresponding to a third data type is buffered in the memory; and A transceiver configured to transmit bufferable data corresponding to a third data type to a first MLD, the bufferable data including fifth indication information, the fifth indication information being used to indicate whether the bufferable data corresponding to the third data type is buffered in a memory.

[0107]

[0107] In an implementation, when the communication device has some or all of the functions for realizing the second MLD in the example method according to the eighth aspect, the communication device includes: a processing unit configured to determine that bufferable data corresponding to a fifth data type is not buffered in the storage unit, the fifth data type being any one of the data types supported by the first MLD; and A communication unit configured to transmit seventh indication information to the first MLD, the seventh indication information being used to indicate that bufferable data corresponding to the fifth data type is not buffered in the storage unit.

[0108]

[0108] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0109]

[0109] In an implementation, when the communication device has some or all of the functions for realizing the second MLD in the example method according to the eighth aspect, the communication device includes: a processor configured to determine that bufferable data corresponding to a fifth data type is not buffered in memory, the fifth data type being any one of the data types supported by the first MLD; and A transceiver configured to transmit seventh indication information to the first MLD, the seventh indication information being used to indicate that bufferable data corresponding to the fifth data type is not buffered in the memory.

[0110]

[0110] In an implementation, when the communication device has some or all of the functions for realizing the second MLD in the example method according to the tenth aspect, the communication device includes: a processing unit configured to determine that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the storage unit; and A communication unit configured to transmit eighth indication information to the first MLD via a fourth link, the eighth indication information being used to indicate that bufferable data corresponding to a certain data type mapped to the fourth link is not buffered in the storage unit.

[0111]

[0111] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0112]

[0112] In an implementation, when the communication device has some or all of the functions for realizing the second MLD in the example method according to the tenth aspect, the communication device includes: a processor configured to determine that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the memory; and A transceiver configured to transmit eighth indication information to the first MLD via a fourth link, the eighth indication information being used to indicate that bufferable data corresponding to a data type mapped to the fourth link is not buffered in the memory.

[0113]

[0113] In an implementation, when the communication device has some or all of the functionality for realizing the second MLD in the example method according to the twelfth aspect, the communication device includes: a processing unit configured to determine a buffer status of bufferable data in the storage unit, the buffered data corresponding to at least one data type supported by the first MLD; and A communication unit configured to transmit ninth indication information to a first MLD, the ninth indication information being used to indicate a buffer status of bufferable data corresponding to at least one data type supported by the first MLD and residing in the storage unit.

[0114]

[0114] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0115]

[0115] In an implementation, when the communication device has some or all of the functionality for realizing the second MLD in the example method according to the twelfth aspect, the communication device includes: a processor configured to determine a buffer status of bufferable data in a memory, the buffered data corresponding to at least one data type supported by the first MLD; and A transceiver configured to transmit ninth instruction information to a first MLD, the ninth instruction information being used to indicate a buffer status of bufferable data corresponding to at least one data type supported by the first MLD and residing in a memory.

[0116]

[0116] In an implementation, when the communication device has some or all of the functionality for realizing the second MLD in the example method according to the fourteenth aspect, the communication device includes: a processing unit configured to determine a buffer status of bufferable data in the storage unit, the buffered data corresponding to at least one data type mapped to at least one link corresponding to the first MLD; and A communication unit configured to transmit tenth indication information to a first MLD, the tenth indication information being used to indicate a buffer status of bufferable data corresponding to at least one data type mapped to at least one link corresponding to the first MLD and residing in a storage unit.

[0117]

[0117] For example, the processing unit may be a processor, the communication unit may be a transceiver or a communication interface, and the storage unit may be a memory.

[0118]

[0118] In an implementation, when the communication device has some or all of the functionality for realizing the second MLD in the example method according to the fourteenth aspect, the communication device includes: a processor configured to determine a buffer status of bufferable data in a storage unit, the buffered data corresponding to at least one data type mapped to at least one link corresponding to the first MLD; and A transceiver configured to transmit tenth indication information to a first MLD, the tenth indication information being used to indicate a buffer status of bufferable data in a memory, the bufferable data corresponding to at least one data type mapped to at least one link corresponding to the first MLD.

[0119] According to a seventeenth aspect, an embodiment of the present invention provides a computer readable storage medium configured to store a computer program for use by a first MLD such that, when the computer program is run, the first MLD performs a method according to the first, third, fifth, seventh, ninth, eleventh or thirteenth aspect.

[0120] According to an eighteenth aspect, an embodiment of the present invention provides a computer readable storage medium configured to store a computer program for use by a second MLD, the computer program running to cause the second MLD to perform a method according to the second, fourth, sixth, eighth, tenth, twelfth or fourteenth aspect.

[0121]

[0121] According to a nineteenth aspect, the present application further provides a computer program product comprising a computer program which, when executed on a computer, enables the computer to carry out a method according to the first, third, fifth, seventh, ninth, eleventh or thirteenth aspects.

[0122]

[0122] According to a twentieth aspect, the present application further provides a computer program product comprising a computer program which, when executed on a computer, enables the computer to perform a method according to the second, fourth, sixth, eighth, tenth, twelfth or fourteenth aspect.

[0123]

[0123] According to a twenty-first aspect, the present application provides a chip system. The chip system includes at least one processor and an interface, which are configured to support the first MLD in implementing the functions of the first, third, fifth, seventh, ninth, eleventh, or thirteenth aspects, such as determining or processing at least one of the data and information in the aforementioned method. In a possible design, the chip system further includes a memory, which is configured to store computer programs and data required for the first MLD. The chip system may include a chip or may include a separate device apart from the chip.

[0124]

[0124] According to a twenty-second aspect, the present application provides a chip system. The chip system includes at least one processor and an interface, which are configured to support a second MLD in implementing the functions of the second, fourth, sixth, eighth, tenth, twelfth, or fourteenth aspects, such as determining or processing at least one of the data and information in the aforementioned method. The memory is configured to store bufferable data, as well as computer programs and data required for the second MLD. The chip system may include a chip, or may include a chip and another separate device. [Brief description of the drawings]

[0125] [Figure 1]

[0125] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application. [Diagram 2]

[0126] FIG. 2 is a schematic flowchart of a method for determining a data buffer status according to an embodiment of the present application. [Figure 3a]

[0127] FIG. 3a is a schematic flow chart of another method for determining a data buffer status according to an embodiment of the present application. [Figure 3b]

[0128] FIG. 3b is a schematic diagram of management frames and AIDs corresponding to each AC supported by the first MLD-a and the first MLD-b according to an embodiment of the present application. [Figure 4a]

[0129] FIG. 4a is a schematic flow chart of yet another method for determining data buffer status according to an embodiment of the present application. [Figure 4b]

[0130] FIG. 4b is a schematic diagram of a scenario in which a second MLD transmits bufferable data to a first MLD according to an embodiment of the present application. [Figure 5A]

[0131] FIG. 5A is a schematic flow chart of yet another method for determining data buffer status according to an embodiment of the present application. [Figure 5B]

[0131] FIG. 5B is a schematic flow chart of yet another method for determining a data buffer status according to an embodiment of the present application. [Figure 6a]

[0132] FIG. 6a is a schematic flow chart of yet another method for determining data buffer status according to an embodiment of the present application. [Figure 6b]

[0133] FIG. 6b is a schematic diagram of a scenario in which the operational state of a link is determined according to an embodiment of the present application. [Figure 6c]

[0134] FIG. 6c is a schematic diagram of another scenario in which the operational state of a link is determined according to an embodiment of the present application. [Figure 6d]

[0135] FIG. 6d is a schematic diagram of yet another scenario in which the operational state of a link is determined according to an embodiment of the present application. [Figure 7]

[0136] FIG. 7 is a schematic flow chart of yet another method for determining data buffer status according to an embodiment of the present application. [Figure 8]

[0137] FIG. 8 is a schematic flow chart of yet another method for determining data buffer status according to an embodiment of the present application. [Figure 9a]

[0138] FIG. 9a is a schematic flow chart of yet another method for determining data buffer status according to an embodiment of the present application. [Figure 9b]

[0139] FIG. 9b is a schematic diagram of the “More Data Per TID Per link” subfield according to an embodiment of the present application. [Figure 10]

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

[0141] FIG. 11 is a schematic diagram of the structure of another communication device according to an embodiment of the present application. [Figure 12]

[0142] FIG. 12 is a schematic diagram of the structure of a chip according to an embodiment of the present application. [Figure 13]

[0143] FIG. 13 is a schematic diagram of the structure of yet another communication device according to an embodiment of the present application. [Figure 14]

[0144] FIG. 14 is a schematic diagram of the structure of yet another communication device according to an embodiment of the present application. [Figure 15]

[0145] FIG. 15 is a schematic diagram of another chip structure according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0126]

[0146] For ease of understanding, the terminology used in this application will first be explained.

[0127]

[0147] 1. Traffic indication map (TIM) field

[0148] The TIM field may be included in a TIM element carried in an 802.11 Beacon frame. The AP MLD may periodically transmit 802.11 Beacon frames to one or more non-AP MLDs, and the buffer status of the bufferable data corresponding to each station included in each non-AP MLD and on the AP MLD may be determined based on the TIM element carried in the Beacon frame. The buffer status of the bufferable data corresponding to the station and on the AP MLD may indicate whether data to be transmitted to the station is buffered on the AP MLD.

[0128]

[0149] The non-AP station may have two operation modes: a non-energy saving mode and an energy saving mode. In the non-energy saving mode, the non-AP station is in an active state, whether or not it needs data to be transmitted between the non-AP station and the AP station. In the energy saving mode, if it needs data to be transmitted between the non-AP station and the AP station, the non-AP station can be in an active state. If it does not need data to be transmitted between the non-AP station and the AP station, the non-AP station can be in a doze state, so as to reduce the power consumption of the non-AP MLD.

[0129]

[0150] A non-AP station in the energy saving mode can be periodically woken up (i.e., in the active state) and receive the beacon frames transmitted by the AP MLD to determine whether data to be transmitted to the non-AP station is buffered on the AP MLD. If data corresponding to the AP station is not buffered on the AP MLD, the non-AP station can switch to the doze state. If data corresponding to the non-AP station is buffered on the AP MLD, the non-AP station can switch to the active state to receive the corresponding data.

[0130]

[0151] An 802.11 beacon frame may contain a TIM beacon frame or a delivery traffic indication map (DTIM) beacon frame. TIM and DTIM beacon frames each carry a TIM element. The fields contained in the TIM element may be those shown in Table 1.

[0131] Table 1 Fields contained in the TIM element

[0132]

number

[0152] The element identifier (ID) field is used to identify that the element is a TIM element. The length field is used to indicate the number of bytes that the TIM element occupies. The DTIM count field is used to indicate how many TIM beacon frames there are before the next DTIM beacon frame arrives. The DTIM period field indicates the interval between the arrival of two adjacent DTIM beacon frames. The element ID field, length field, DTIM count field, DTIM period field, and bitmap control field may each occupy one byte. Bit 0 in the bitmap control field may indicate whether a downlink multicast data service exists when the AP transmits the DTIM beacon frame, and bits 1 through 7 in the bitmap control field may indicate the offset of the partial virtual bitmap, where the offset is in bytes (i.e., 8 bits). Part of the virtual bitmap is the TIM field, and each bit in the TIM field corresponds to one association identifier (AID). For example, if the offset is 0, the partial virtual bitmap may start at AID 1; if the offset is 1, the partial virtual bitmap may start at AID 9.

[0133]

[0153] 2. Access category (AC)

[0154] Enhanced distributed channel access (EDCA) is a channel contention mechanism. EDCA classifies data packets into four ACs. Higher priority ACs have more channel occupancy opportunities than lower priority ACs. EDCA allows higher priority packets to be transmitted preferentially and occupy more bandwidth. The four ACs, in descending order of priority, are voice (AC_VO), video (AC_VI), background (AC_BK), and best effort (AC_BE).

[0134]

[0155] 3. Traffic Identifier (TID)

[0156] By using the TID, higher layer entities can differentiate the quality of service (QoS) supported by a MAC service data unit (MSDU) at the medium access control (MAC) layer. EDCA can support eight TIDs, which are TID 0 through TID 7. There is a correspondence between ACs and TIDs. One AC may correspond to one or more TIDs, and one TID corresponds to one AC.

[0135]

[0157] 4. Management Frames

[0158] The management frames may be used to manage data packets, control the network, and the like. The management frames may include, but are not limited to, a beacon frame, a probe request frame, a probe response frame, an Independent Basic Service Set (IBSS) Announcement Traffic Indication Message (ATIM) frame, a disassociation frame, a deauthentication frame, an association request frame, a reassociation request frame, an authentication frame, and an action frame. The management frames referred to in the embodiments of the present application may be any one or more of the above management frames.

[0136]

[0159] Beacon frames may be used to announce the presence of a network. A mobile workstation may scan an area, where it locates for a particular 802.11 network by using a probe request frame. If the network checked by using the probe request frame is compatible with the probe request frame, the network responds with a probe request frame. The IBSS station buffers the frame for the receiver in the doze state. Upon transmission, the IBSS station transmits an IBSS ATIM frame to inform the receiver that a message is to be transmitted. Disassociation and Deauthentication frames may each be used to terminate an authentication relationship. After the mobile workstation discovers a compatible network and the authentication is successful, the mobile workstation transmits an Association Request frame to attempt to access the network. When a mobile station located within the same extended service area but moving between different basic service areas uses the distributed system again, the mobile station reassociates with the network by using a reassociation request frame. Action frames are used to trigger measurement operations.

[0137]

[0160] In order to better understand the method for determining a data buffer status disclosed in the embodiment of the present application, a communication system to which the embodiment of the present application is applicable will be first described below.

[0138]

[0161] An embodiment of the present application provides a communication method applied to a wireless communication system. The wireless communication system may be a wireless local area network (WLAN) or a cellular network, and the method may be implemented by a communication device in the wireless communication system or a chip or processor in the communication device. The communication device may be a wireless communication device that supports parallel transmission over multiple links, for example, the wireless communication device is called a multi-link device or a multi-band device. The multi-link device has higher transmission efficiency and higher throughput compared to a device that supports only single-link transmission.

[0139]

[0162] A Multi-Link device is a device that connects one or more affiliated stations. hmm(The affiliation STA includes affiliated STAs. An affiliation STA is a logical station and can operate on one link. An affiliation station can be an Access Point (AP) or a non-Access Point Station (non-AP STA). For ease of explanation, in this application, a multi-link device whose affiliated station is an AP may be referred to as a multi-link AP, a multi-link AP device, or an AP multi-link device. A multi-link device whose affiliated station is a non-AP STA may be referred to as a multi-link STA, a multi-link STA device, or an STA multi-link device. For ease of explanation, "a multi-link device includes an affiliated STA" is also simply described as "a multi-link device includes a STA" in the embodiments of this application.

[0140]

[0163] It should be noted that a multi-link device contains multiple logical stations, each operating on a link, but multiple logical stations are permitted to operate on the same link. A link identifier referred to below represents a station operating on a link. In other words, if there are multiple stations on a link, more than one link identifier is required to represent the more than one station. A link referred to below may also represent a station operating on a link.

[0141]

[0164] When data is to be transmitted between a multi-link AP device and a multi-link STA, a link identifier can be used to identify a link or a station on a link. Before communication, the multi-link AP device and the multi-link STA device can first negotiate or contact each other about the correspondence between the link identifier and the link or a station on the link. Thus, during data transmission, the link identifier is carried without the need to transmit a lot of signaling information to indicate the link or the station on the link. This reduces signaling overhead and improves transmission efficiency.

[0142]

[0165] A multi-link device can realize wireless communication according to the 802.11 family of standards. For example, a station conforming to Extremely High Throughput (EHT), or a station conforming to 802.11be, or a station compatible with a station supporting 802.11be, can communicate with another device. Indeed, the other device may or may not be a multi-link device.

[0143]

[0166] For example, the multi-link device in this embodiment of the present application may be a single antenna device or a multi-antenna device. For example, the device may be a device having two or more antennas. The number of antennas included in the multi-link device is not limited in this embodiment of the present application. In this embodiment of the present application, the multi-link device may allow services of the same access type to be transmitted on different links, and may even allow the same data packet to be transmitted on different links; or, it may not allow services of the same access type to be transmitted on different links, but may allow services of different access types to be transmitted on different links.

[0144]

[0167] Multi-Link devices are capable of operating in the sub-1 GHz, 2.4 GHz, 5 GHz, 6 GHz frequency bands, and the high frequency band of 60 GHz.

[0145]

[0168] For example, a multi-link device is a device having wireless communication capabilities. The device may be an integrated device, or a chip, processing system, etc., mounted on an integrated device. The device having the chip or processing system mounted thereon may be controlled by the chip or processing system to implement the methods and functions in the embodiments of the present application. For example, a multi-link STA in this embodiment of the present application may have wireless transceiver capabilities, support the 802.11 family of standards, and communicate with a multi-link AP, another multi-link STA, or a single-link device. For example, a multi-link STA is any user communication device that allows a user to communicate with an AP and further with a WLAN. For example, the multi-link STA may be a user device capable of accessing the network, such as a tablet computer, a desktop computer, a laptop computer, a notebook computer, an ultra-mobile personal computer (UMPC), a handheld computer, a netbook, a personal digital assistant (PDA), or a mobile phone, or may be an Internet of Things node in the Internet of Things, an in-vehicle communication device in the Internet of Vehicles, etc. Alternatively, the multi-link STA may be a chip or a processing system in the aforementioned terminal. The multi-link AP in this embodiment of the present application is a device that provides services for the multi-link STA and can support the 802.11 family of standards. For example, the multi-link AP may be a communication entity such as a communication server, a router, a switch, or a bridge, or the multi-link AP may include various forms of macro base stations, micro base stations, relay stations, etc. Indeed, the multi-link AP may alternatively be a processing system or a chip in various forms of devices for implementing the methods and functions in the embodiments of the present application.In addition, the multi-link device can support high-speed low-latency transmission. With the continuous evolution of wireless local area network application scenarios, the multi-link device can also be applied to more scenarios, such as sensor nodes (e.g., smart water meters, smart power meters, smart air detection nodes) in smart cities, smart devices (e.g., smart cameras, projectors, displays, televisions, stereos, refrigerators, or washing machines) in smart homes, nodes in Internet of Things, entertainment terminals (e.g., wearable devices such as AR or VR), smart devices (e.g., printers or projectors) in smart offices, Internet of Vehicles devices in Internet of Vehicles, and infrastructures (e.g., vending machines, self-service navigation machines in supermarkets, self-service cash register devices, or self-service ordering devices) in daily life scenarios. The specific forms of the multi-link STA and the multi-link AP are not specifically limited in this embodiment of the present application, and are merely illustrative of the description in this case. The 802.11 protocol may be a protocol that supports 802.11be or may be a protocol that is compatible with 802.11be.

[0146]

[0169] Although the embodiments of the present application are described primarily using an IEEE 802.11 deployed network as an example, one skilled in the art will readily appreciate that various aspects of the present application can be extended to other networks using various standards or protocols, such as, for example, BLUETOOTH, high performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard and used primarily in Europe), wide area networks (WANs), wireless local area networks (WLANs), personal area networks (PANs), or other known or later developed networks. Thus, various aspects provided herein are applicable to any suitable wireless network, regardless of coverage and radio access protocol.

[0147]

[0170] The following describes the embodiments of the present application, and the embodiments of the present application do not limit the protection scope and applicability of the claims. Those skilled in the art can adaptively change the functions and arrangements of the elements in the present application without departing from the scope of the embodiments of the present application, and can omit, replace, or add various processes or components as appropriate.

[0148]

[0171] FIG. 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application. The communication system may include, but is not limited to, one first MLD and one second MLD. The quantity and form of devices shown in FIG. 1 are used as an example and do not constitute limitations on this embodiment of the present application. In practical applications, two or more first MLDs and two or more second MLDs may be included. For example, the communication system shown in FIG. 1 includes one first MLD 101 and one second MLD 102.

[0149]

[0172] The second MLD 102 is configured to determine a buffer status of bufferable data corresponding to at least one data type supported by the first MLD 101 and residing in the second MLD 102; and to send indication information to the first MLD 101, where the indication information can be used to indicate a buffer status of the bufferable data corresponding to at least one data type supported by the first MLD 101 and residing in the second MLD 102.

[0150]

[0173] After receiving the indication information from the second MLD 102, the first MLD 101 can determine, based on the indication information, a buffer status of bufferable data that corresponds to at least one data type supported by the first MLD 101 and is in the second MLD 102.

[0151]

[0174] In this embodiment of the present application, the data type supported by the first MLD 101 may include at least one of a service type and a management frame, where the service type may be an AC or a TID. The first MLD 101 may support one or more data types. For example, the data type supported by the first MLD 101 is data type 1. The buffer status of the bufferable data corresponding to data type 1 and in the second MLD 102 may refer to whether the bufferable data to be transmitted to the first MLD 101 is buffered in the second MLD 102, where the data type of the bufferable data is data type 1. In this embodiment of the present application, the data type supported by the first MLD 101 may be determined in the process of establishing a connection between the first MLD 101 and the second MLD 102.

[0152]

[0175] The data types supported by different first MLDs 101 may be the same or different. When the communication system shown in FIG. 1 includes multiple first MLDs 101, the second MLD 102 can determine the buffer status of the bufferable data corresponding to at least one data type supported by each first MLD 101 and residing in the second MLD 102; and send the indication information to each first MLD 101. It should be noted that the second MLD may broadcast the indication information to each first MLD. In this case, the indication information received by all first MLDs is the same. The indication information may indicate the buffer status of the bufferable data corresponding to at least one data type supported by each first MLD 101 and residing in the second MLD 102. Alternatively, the second MLD may send the indication information to each first MLD separately. send In this case, the indication information received by all the first MLDs is different. The indication information received by each first MLD is used to indicate the buffer status of bufferable data in the second MLD 102, which corresponds to at least one data type supported by the first MLD 101. It should be noted that "at least one" referred to in this embodiment of the present application may be described as "one or more".

[0153]

[0176] 1 includes multiple second MLDs 102, each of the second MLDs 102 (e.g., second MLD-a and second MLD-b) may determine a buffer status of bufferable data in the second MLD 102 that corresponds to at least one data type supported by the first MLD 101; and may transmit indication information to the first MLD 101. The indication information received by the first MLD 101 from the second MLD-a may indicate a buffer status of bufferable data in the second MLD-a that corresponds to at least one data type supported by the first MLD 101. Similarly, the indication information received by the first MLD 101 from the second MLD-b may indicate a buffer status of bufferable data in the second MLD-b that corresponds to at least one data type supported by the first MLD 101.

[0154]

[0177] It can be understood that the communication system described in the embodiments of the present application is intended to more clearly explain the technical solutions of the embodiments of the present application, but does not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art can know that with the evolution of system architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present application can also be applied to similar technical problems.

[0155]

[0178] The method and apparatus for determining a data buffer status provided in the present application are described in detail below with reference to the accompanying drawings.

[0156]

[0179] FIG. 2 is a schematic flow chart of a method for determining a data buffer status according to an embodiment of the present application. The method describes in detail how a first MLD determines a buffer status of bufferable data, which corresponds to at least one data type and is in the second MLD, based on indication information from the second MLD. Steps S201 and S202 are performed by the second MLD or a chip in the second MLD, and step S203 is performed by the first MLD or a chip in the first MLD. An example in which the second MLD and the first MLD perform the method for determining a data buffer status is used in the following description. As shown in FIG. 2, the method may include, but is not limited to, the following steps:

[0157]

[0180] Step S201: A second multi-link device MLD determines a buffer status of bufferable data in the second MLD, which corresponds to at least one data type supported by the first MLD.

[0158]

[0181] In this embodiment of the present application, the second MLD can determine whether bufferable data corresponding to at least one data type supported by the first MLD is buffered in the second MLD, and if the first MLD supports one data type, the second MLD can determine whether data to be transmitted to the first MLD is buffered in the second MLD, where the data type of the bufferable data is a data type supported by the first MLD.

[0159]

[0182] If the first MLD supports multiple data types, the second MLD may determine whether bufferable data corresponding to each data type supported by the first MLD is buffered in the second MLD. For example, if the first MLD supports three data types (data type 1, data type 2, and data type 3), the second MLD may determine whether bufferable data corresponding to each of data type 1, data type 2, and data type 3 is buffered in the second MLD. In another implementation, the second MLD may determine whether bufferable data corresponding to data type 1 is buffered in the second MLD, and determine whether bufferable data corresponding to at least one of data type 2 and data type 3 is buffered in the second MLD. For example, in the second MLD, bufferable data corresponding to data type 1 is buffered in buffer area a, and bufferable data corresponding to data type 2 and data type 3 is buffered in buffer area b. At least one of In the case where bufferable data corresponding to data type 1 is buffered in buffer area b, if the second MLD detects that a bufferable unit (BU) exists in buffer area a, it indicates that bufferable data corresponding to data type 1 is not buffered in the second MLD; if the second MLD detects that a bufferable unit does not exist in buffer area a, it indicates that bufferable data corresponding to data type 1 is not buffered in the second MLD. Similarly, if the second MLD detects that a bufferable unit exists in buffer area b, it indicates that bufferable data corresponding to at least one of data type 2 and data type 3 is buffered in the second MLD; If the second MLD detects that no bufferable units exist in buffer area b, it indicates that neither the bufferable data corresponding to data type 2 nor the bufferable data corresponding to data type 3 will be buffered in the second MLD.

[0160]

[0183] It should be noted that the buffer areas occupied by the bufferable data corresponding to data type 1, data type 2, and data type 3 in the second MLD are merely illustrative and do not constitute a limitation to this embodiment of the present application. How the bufferable data corresponding to at least one data type supported by the first MLD is buffered in the second MLD is not limited in this embodiment of the present application. In an implementation, the second MLD can buffer the bufferable data corresponding to at least one data type supported by the first MLD in a common buffer area. Alternatively, the second MLD can buffer the bufferable data corresponding to each data type supported by the first MLD in a separate buffer area. Alternatively, the second MLD can buffer the bufferable data corresponding to the data type supported by the first MLD using a combination of a common buffer scheme and a separate buffer scheme. Alternatively, the second MLD may buffer the bufferable data corresponding to the service type supported by the first MLD in one buffer area and buffer the bufferable data corresponding to the management frame in another buffer area. The first MLD and the second MLD may be connected via multiple links. In the implementation, the second MLD may determine a link through which the bufferable data corresponding to at least one data type supported by the first MLD will be transmitted to the first MLD. Furthermore, the second MLD may buffer the bufferable data to be transmitted via the same link in a separate buffer area. It should be further noted that the second MLD may transmit the bufferable data to the first MLD via a station, and the station in the second MLD may schedule the bufferable data from one or more buffer areas to transmit the bufferable data to the first MLD.

[0161]

[0184] It should be further noted that when the second MLD has a connection relationship with multiple first MLDs, the second MLD can determine the buffer status of bufferable data within the second MLD that corresponds to at least one data type supported by each of the first MLDs.

[0162]

[0185] Step S202: The second MLD sends indication information to the first MLD, where the indication information is used to indicate a buffer status of bufferable data corresponding to at least one data type supported by the first MLD and located in the second MLD.

[0163]

[0186] Specifically, the second MLD may send the indication information to the first MLD after determining a buffer status of the bufferable data in the second MLD, the bufferable data corresponding to at least one data type supported by the first MLD. Each bit of the indication information may correspond to one or more data types supported by the first MLD, and the value of each bit may indicate whether the bufferable data of the data type corresponding to the bit is buffered in the second MLD. In this embodiment of the present application, the indication information may also be referred to as the ninth indication information.

[0164]

[0187] In implementation, the indication information may refer to a bit occupied by control type a in the EHT A-control field of the MAC frame. The EHT A-control field can support eight control types, that is, information about the eight control types can be carried using the bits corresponding to the EHT A-control field. The relevant information of the eight control types may be as shown in Table 2. It should be noted that the EHT A-control field is only an example. Alternatively, the HT control field in which the EHT A-control field or the HE A-control field is located may be used as a specific example. With the evolution of the standard version, the name of the field may change, and if the field indicates the corresponding function, the field belongs to the scope of the embodiment of the present application.

[0165] Table 2. Information on the eight control types

[0166]

number

[0188] In Table 2, a type (More Data Per TID) with a control ID of 7 is newly added. It should be noted that the values ​​and names of the control IDs in Table 2 are merely used as examples and do not constitute limitations on this embodiment of the present application. It should be further noted that the newly added type is "More Data PER TID", the data types supported by the first MLD include service type and management frame, and the service type is TID, are used as examples. If the service type is AC, the newly added type in Table 2 may be more data per AC (More Data Per AC). Correspondingly, in this case, More Data Per AC may occupy 5 bits, and each of 4 bits corresponds to one AC, and the other bit corresponds to management frame.

[0167]

[0189] In this embodiment of the present application, a concrete example in which the newly added type is "More Data Per TID" is used for explanation. The "More Data Per TID" subfield may include 9 bits, where 8 bits correspond to 8 TIDs, each of the 8 bits corresponds to one TID, and another bit corresponds to a management frame. If a bit corresponding to a TID and in the "More Data Per TID" subfield is set to 1, it may indicate that the bufferable data corresponding to the TID is buffered in the second MLD. If a bit is set to 0, it may indicate that the bufferable data corresponding to the TID is not buffered in the second MLD. If a bit corresponding to a management frame and in the "More Data Per TID" subfield is set to 1, it may indicate that the bufferable data of the management frame is buffered in the second MLD. If a bit is set to 0, it may indicate that the bufferable data of the management frame is not buffered in the second MLD.

[0168]

[0190] In implementation, one bit in the "More Data Per TID" subfield may correspond to one or more TIDs. TID The amount of bits occupied by the "More Data Per TID" subfield may be less than 9. For example, the bits of the "More Data Per TID" subfield may correspond to TID 1 and TID 2. If the bit is set to 1, it may indicate that the bufferable data corresponding to at least one of TID 1 and TID 2 is buffered in the second MLD. If the bit is set to 0, it may indicate that neither the bufferable data corresponding to TID 1 nor the bufferable data corresponding to TID 2 is buffered in the second MLD.

[0169]

[0191] In the implementation, the second MLD may transmit indication information to a plurality of first MLDs, where the indication information may indicate a buffer status of bufferable data in the second MLDs corresponding to at least one data type supported by each of the first MLDs. For example, when the second MLD transmits indication information to the first MLD-a and the first MLD-b, a part of the bits in the indication information may correspond to at least one data type supported by the first MLD-a. Specifically, the value of the part of the bits is used to indicate a buffer status of bufferable data in the second MLDs corresponding to at least one data type supported by the first MLD-a. Another part of the bits in the indication information may correspond to at least one data type supported by the first MLD-b. Specifically, the value of the other part of the bits is used to indicate a buffer status of bufferable data in the second MLDs corresponding to at least one data type supported by the first MLD-b.

[0170]

[0192] In this embodiment of the present application, data will be transmitted through links between the second MLD and the first MLD, and each link is established between one station in the first MLD and one station in the second MLD. When a station in the first MLD or the second MLD is in a doze state, the link corresponding to the station is also in a doze state. In this case, data cannot be transmitted through the link, and the station corresponding to the link in the first MLD cannot receive data. In this embodiment of the present application, a station in the second MLD may schedule bufferable data in the second MLD and transmit the bufferable data to the corresponding station in the first MLD. When a station in the first MLD is in a doze state, the station cannot receive data.

[0171]

[0193] In an implementation, the indication information may be carried in the bufferable data transmitted by the second MLD to the first MLD. In this case, the indication information may be used to indicate whether the bufferable data (buffered in the second MLD) corresponding to at least one data type supported by the first MLD has been completely transmitted. Specifically, the indication information may be included in an EHT A control field in a MAC frame. In another implementation, the second MLD may be used to indicate whether the bufferable data (buffered in the second MLD) corresponding to at least one data type supported by the first MLD has been completely transmitted. 1 In this case, the indication information may be periodically sent to the MLD of the 1 The bufferable data to be transmitted to the station in the energy saving mode in the MLD of the first 2 The indication may indicate whether the received signal is buffered on the first MLD. The indication may be received by an active station in the first MLD. The indication may be carried in a control frame or a management frame.

[0172]

[0194] Step S203: The first MLD determines, according to the indication information, a buffer status of bufferable data corresponding to at least one data type and located in the second MLD.

[0173]

[0195] After receiving the indication information from the second MLD, the first MLD can determine, based on the indication information, a buffer status of bufferable data corresponding to the at least one data type and located in the second MLD.

[0174]

[0196] Specifically, if the value of a bit in the indication information is a first value (e.g., 1), the first MLD may determine that bufferable data of a data type corresponding to the bit is buffered in the second MLD; if the value of the bit is a second value (e.g., 0), the first MLD may determine that bufferable data of a data type corresponding to the bit is not buffered in the second MLD. For example, the indication information includes two bits (bit 1 and bit 2), the first MLD supports three data types (data type 1, data type 2, data type 3), bit 1 corresponds to data type 1, and bit 2 corresponds to data type 2 and data type 3. If the value of bit 1 is 1, the first MLD may determine that bufferable data corresponding to data type 1 is buffered in the second MLD. If the value of bit 1 is 0, the first MLD may determine that bufferable data corresponding to data type 1 is not buffered in the second MLD. If the value of bit 2 is 1, the first MLD may determine that bufferable data corresponding to at least one of data type 2 or data type 3 is buffered in the second MLD. If the value of bit 2 is 0, the first MLD may determine that neither bufferable data corresponding to data type 2 nor bufferable data corresponding to data type 3 is buffered in the second MLD. The first value being 1 and the second value being 0 are used merely as an example and do not constitute a limitation to this embodiment of the present application. Optionally, the first value may be 0 and the second value may be 1.

[0175]

[0197] It should be noted that if only bufferable data corresponding to a data type portion of the data types supported by the first MLD is buffered in the second MLD, the bit of the indication information may only correspond to a data type portion of the data types supported by the first MLD. For example, if the first MLD supports three data types (data type 1, data type 2, and data type 3) and bufferable data corresponding to data type 1 is buffered in the second MLD, but bufferable data corresponding to data type 2 and bufferable data corresponding to data type 3 are not buffered in the second MLD, the indication information may include a bit corresponding to data type 1 but not a bit corresponding to data type 2 and / or data type 3. In this case, after the first MLD receives the indication information, if the bit corresponding to data type 1 in the indication information is 1, it may indicate that the bufferable data corresponding to data type 1 is buffered in the second MLD; if the bit corresponding to data type 1 in the indication information is 0, it may indicate that the bufferable data corresponding to data type 1 is not buffered in the second MLD. If the indication information does not include bits corresponding to data type 2 and / or data type 3, the first MLD may determine that neither the bufferable data corresponding to data type 2 nor the bufferable data corresponding to data type 3 is buffered in the second MLD.

[0176]

[0198] In an implementation, the first MLD may have a plurality of stations. After determining the buffer status of the bufferable data corresponding to the at least one supported data type and residing in the second MLD, the first MLD may determine an operation state of at least one station among the plurality of stations in the first MLD based on the buffer status of the bufferable data corresponding to the at least one data type and residing in the second MLD. The operation state may be an active state or a doze state.

[0199] Specifically, the first MLD can determine that the bufferable data corresponding to the data type is buffered in the second MLD by determining a data type corresponding to a bit in the indicator information whose value is 1. Then, the first MLD can determine a link to which the data type corresponding to the bufferable data is mapped based on a mapping relationship between the supported data types and the links corresponding to the first MLD.

[0177]

[0200] In the implementation, the first MLD can determine the operation states of all of the stations corresponding to the links to which the data type corresponding to the bufferable data is mapped as an active state. For example, the bufferable data corresponding to data type 1 supported by the first MLD is buffered in the second MLD, and data type 1 is mapped to link 1 and link 2, and link 1 and link 2 correspond to station 1 and station 2 in the first MLD, respectively. In this case, the first MLD may determine the operation states of both station 1 and station 2 as an active state. If the station in the second MLD remains in an active state, the operation states of the stations (stations in the first MLD) corresponding to the links to which the data type corresponding to the bufferable data is mapped are determined as an active state, so that the links to which the data type corresponding to the bufferable data is mapped can be in an active state. Furthermore, the second MLD can transmit the bufferable data over the links to the first MLD.

[0178]

[0201] The link corresponding to the first MLD is a link between the first MLD and the second MLD. Note that the mapping of the data type 1 supported by the first MLD to the link 1 may indicate that the bufferable data corresponding to the data type 1 is mapped to the link 1, that is, the bufferable data corresponding to the data type 1 is transmitted to the first MLD via the link 1. A management frame may be mapped to one or more links, and one service type may be mapped to one or more links. One or more service types may be mapped to each link, and a management frame may further be mapped to each link. A mapping relationship between a service type supported by the first MLD (or a management frame to be transmitted to the first MLD) and a link corresponding to the first MLD may be determined through negotiation between the first MLD and the second MLD. For example, the mapping relationship is determined in a process of establishing a connection between the first MLD and the second MLD. When the service type is a TID, the mapping relationship between the service type supported by the first MLD and the link corresponding to the first MLD may be referred to as a TID-to-link mapping. When the service type is an AC, the correspondence relationship between the AC supported by the first MLD and the link corresponding to the first MLD (i.e., AC-to-link mapping) may be determined based on the TID-to-link mapping and the correspondence relationship between the AC and the TID supported by the first MLD.

[0179]

[0202] In another implementation, after determining the links to which the data type corresponding to the bufferable data is mapped, the first MLD can determine the links that need to be switched to the active state from among the links to which the data type corresponding to the bufferable data is mapped based on the current buffer level information of the first MLD, i.e., the stations that need to be switched to the active state from among the stations corresponding to the links to which the data type corresponding to the bufferable data is mapped. The battery level information may include, but is not limited to, one or more remaining battery levels and whether the first MLD is in a charging mode. For example, if the bufferable data corresponding to AC_VO supported by the first MLD is buffered in the second MLD, and AC_VO is mapped to link 1, link 2, and link 3, and the current remaining battery level of the first MLD is relatively low, the first MLD may choose to determine the operating states of a part of link 1, link 2, and link 3 as an active state and the operating states of the other parts of link 1, link 2, and link 3 as a doze state. This can contribute to ensuring the reception of data and reducing power consumption.

[0180]

[0203] In yet another implementation, the first MLD can determine the link that needs to be switched to the active state from among the links to which the data type corresponding to the bufferable data is mapped based on the service requirement information of the first MLD. For example, when the bufferable data corresponding to AC_VO supported by the first MLD and the bufferable data corresponding to AC_VI supported by the first MLD are buffered in the second MLD, AC_VO and AC_VI are mapped to link 1 and link 2, respectively, and for the first MLD, if the priority of the bufferable data corresponding to AC_VO is higher than the priority of the bufferable data corresponding to AC_VI, the first MLD can determine the state of link 1 as the active state and the state of link 2 as the doze state. This can ensure the reception of the high priority data. In another example, when bufferable data corresponding to a management frame of a first MLD and bufferable data corresponding to an AC_VO supported by the first MLD are buffered in a second MLD, the management frame and the AC_VO are mapped to link 1 and link 2, respectively, and for the first MLD, if the priority of the bufferable data corresponding to the management frame is higher than the priority of the bufferable data corresponding to the AC_VO, the first MLD can determine the state of link 1 as an active state and the state of link 2 as a doze state, which can ensure the reception of the high priority data.

[0181]

[0204] In yet another implementation, the first MLD may determine, based on the first MLD's current battery level information and service requirement information, the link that needs to be switched to the active state from among the links to which the data type corresponding to the bufferable data is mapped. In the above example, if the first MLD's current remaining battery level is relatively high or if the first MLD is in a charging mode, the first MLD may determine the states of both Link 1 and Link 2 as active states to receive data in time. If the first MLD's current remaining battery level is relatively low and / or the first MLD is not in a charging mode, the first MLD may determine the state of Link 1 as active state and the state of Link 2 as doze state to ensure reception of high priority data.

[0182]

[0205] It should be noted that the service requirements of different devices may be the same or different. For the first MLD, the priority of the bufferable data corresponding to AC_VO is higher than the priority of the bufferable data corresponding to AC_VI. This is merely used as an example and does not constitute a limitation to this embodiment of the present application. In another case or for another MLD device, the priority of the bufferable data corresponding to AC_VO may be lower than the priority of the bufferable data corresponding to AC_VI. Based on at least one of the battery level information or the service request information, the operation state of some links in the links to which the data type corresponding to the bufferable data is mapped may be determined as an active state, and the operation state of the remaining links may be determined as a doze state. This helps to reduce power consumption.

[0183]

[0206] It should be further noted that the priority of the bufferable data corresponding to the management frame is higher than the priority of the bufferable data corresponding to the AC_VO, which is merely used as an example and does not constitute a limitation on the embodiment of the present application. The priority of the management frame and the bufferable data corresponding to each service type is not limited to this embodiment of the present application. Optionally, the priority of the bufferable data corresponding to the management frame may be higher than the priority of the bufferable data corresponding to all service types. Alternatively, the priority of the bufferable data corresponding to the management frame may be higher than the priority of the bufferable data corresponding to some service types. Alternatively, the priority of the bufferable data corresponding to the management frame may be lower than the priority of the bufferable data corresponding to any service type. In this embodiment of the present application, the priority of the bufferable data corresponding to the management frame and the priority of the bufferable data corresponding to each service type may be agreed upon according to a standard or may be determined by negotiation between the first MLD and the second MLD. This is not limited to this embodiment of the present application.

[0184]

[0207] In the implementation, when bufferable data of any data type mapped to the link is not buffered in the second MLD, the operation state of the link is not limited in this embodiment of the present application. The first MLD can determine the operation state of the link as a doze state or an active state. For example, if the remaining battery level of the first MLD is relatively high or if the first MLD is in a charging mode, the first MLD can determine the operation state of the link as an active state. As another example, if the remaining battery level of the first MLD is relatively low and / or if the first MLD is not in a charging mode, the first MLD can determine the operation state of the link as a doze state. This helps to reduce power consumption.

[0185]

[0208] In this embodiment of the present application, the first MLD determining the operational state of the link is equivalent to the first MLD determining the operational state of the station corresponding to the link in the first MLD as the same operational state. In this embodiment of the present application, after determining the station whose operational state is in the active state, the first MLD can send an indication message to the second MLD, where the indication message can indicate the station in the active state. After receiving the indication message, the second MLD can determine the active link based on the station in the active state. Furthermore, the second MLD can schedule the bufferable data to the corresponding link in the active state based on the mapping relationship between the data type supported by the first MLD and the link corresponding to the first MLD to transmit the bufferable data to the first MLD.

[0186]

[0209] According to this embodiment of the present application, a buffer status of bufferable data in a second MLD corresponding to at least one data type supported by a first MLD can be determined. Further, a more suitable operating state is determined for a station based on the data type of the bufferable data. This helps to reduce power consumption.

[0187]

[0210] FIG. 3a is a schematic flow chart of a method for determining a data buffer status according to an embodiment of the present application. The method details how the first MLD determines a buffer status of bufferable data in the second MLD, which corresponds to at least one data type, based on the first indication information and the corresponding relationship between the association identifier of the first MLD and the supported data types. Steps S301 and S303 are performed by the second MLD or a chip in the second MLD, and step S304 is performed by the first MLD or a chip in the first MLD. An example of the second MLD and the first MLD performing the method for determining a data buffer status is used in the following description. As shown in FIG. 3a, the method may include, but is not limited to, the following steps:

[0188]

[0211] Step S301: A second multi-link device MLD determines a buffer status of bufferable data in the second MLD, which corresponds to at least one data type supported by the first MLD.

[0189]

[0212] It should be noted that for the process of performing step S301, please refer to the specific description of step S201 in Figure 2. The details will not be described again here.

[0190]

[0213] Step S302: The second MLD determines a buffer status of bufferable data in the second MLD that corresponds to at least one data type supported by the first MLD, and a buffer status of bufferable data in the second MLD that corresponds to an association identifier of the first MLD based on a correspondence between the association identifier of the first MLD and the supported data types.

[0191]

[0214] Specifically, after determining the buffer status of the bufferable data in the second MLD corresponding to at least one data type supported by the first MLD, the second MLD can determine the buffer status of the bufferable data in the second MLD corresponding to the AID of the first MLD based on the correspondence between the AID of the first MLD and the supported data type. In this embodiment of the present application, the first MLD may have one or more association identifiers (AIDs). One AID of the first MLD may correspond to one or more data types supported by the first MLD.

[0192] Table 3 Correspondence between AID and AC of the first MLD

[0193]

number

[0215] For example, the data types supported by the first MLD include a service type and a management frame, and the service type is an AC. The four ACs supported by the first MLD are AC_VO, AC_VI, AC_BK, and AC_BE, and the bufferable data of the management frame of the first MLD, the bufferable data corresponding to AC_VO supported by the first MLD, and the bufferable data corresponding to AC_VI supported by the first MLD are buffered in the second MLD, and the first MLD has five AIDs, AID 0 to AID 4, and AID 4 corresponds to the management frame of the first MLD, and the correspondence between other AIDs of the first MLD and other ACs is shown in Table 3. In this case, the second MLD can determine that the bufferable data corresponding to AID 0, the bufferable data corresponding to AID 1, and the bufferable data corresponding to AID 4 are buffered in the second MLD.

[0194]

[0216] Step S303: The second MLD sends first indication information to the first MLD, where the first indication information is used to indicate a buffer status of bufferable data corresponding to an association identifier of the first MLD and located in the second MLD.

[0195]

[0217] The second MLD may send a first indication information to the first MLD after determining the buffer status of the bufferable data corresponding to the AID of the first MLD and residing in the second MLD. In the embodiment shown in FIG. 2, each bit of the indication information sent by the second MLD to the first MLD may correspond to one or more data types supported by the first MLD, and the value of each bit may indicate whether the bufferable data of the data type corresponding to the bit is buffered in the second MLD. In this embodiment of the present application, each bit of the first indication information sent by the second MLD to the first MLD may correspond to one AID of the first MLD. The value of each bit in the first indication information may indicate the AID corresponding to the bit and whether the corresponding bufferable data is buffered in the second MLD. The first MLD may further determine the buffer status of the bufferable data corresponding to at least one supported data type and residing in the second MLD based on the correspondence between the AID and the supported data type. The first indication information may be a TIM field in the beacon frame.

[0196]

[0218] Step S304: The first MLD determines a buffer status of bufferable data corresponding to at least one data type and located in the second MLD based on the first indication information and the correspondence between the association identifier of the first MLD and the data types supported by the first MLD.

[0197]

[0219] Specifically, after receiving the first indication information from the second MLD, the first MLD can determine a buffer status of bufferable data corresponding to at least one data type and in the second MLD based on the first indication information and the correspondence between an association identifier (AID) of the first MLD and a data type supported by the first MLD. If the value of a bit in the TIM field is 1 and the bit corresponds to AID 1, it can indicate that the bufferable data corresponding to AID 1 is buffered in the second MLD. If AID 1 corresponds to data type 1 supported by the first MLD, it can indicate that the bufferable data corresponding to data type 1 is buffered in the second MLD. If the value of a bit in the TIM field is 0 and the bit corresponds to AID 2, it can indicate that the bufferable data corresponding to AID 2 is not buffered in the second MLD. If AID 2 corresponds to data type 2 supported by the first MLD, it may indicate that bufferable data corresponding to data type 2 is not buffered in the second MLD.

[0198]

[0220] The correspondence between the AID of the first MLD and the data type supported by the first MLD may be determined based on second indication information sent by the second MLD to the first MLD. The second indication information may be used to determine the correspondence between the AID of the first MLD and the data type supported by the first MLD, and the second indication information may be included in the association response frame. It should be noted that this embodiment of the present application does not limit the sequence in which the second MLD sends the first indication information and the second indication information, and the sequence in which the first MLD receives the first indication information and the second indication information, provided that the first MLD can determine the buffer status of bufferable data in the second MLD that corresponds to at least one data type supported by the first MLD based on the first indication information and the second indication information. Preferably, the second MLD may send the second indication information to the first MLD before sending the first indication information, and correspondingly, the first MLD receives the second indication information earlier than the first MLD receives the first indication information.

[0199]

[0221] In implementation, the second indication information received by the first MLD may indicate at least one AID, and the at least one AID may correspond to at least one data type supported by the first MLD. For example, if the data type includes a management frame and an AC, and the first MLD supports four ACs, the second indication information includes five AIDs, where one AID corresponds to a management frame, and the other four AIDs correspond to the four ACs. It should be noted that the correspondence between the four AIDs and the four ACs in the second indication information is not limited in this embodiment of the present application. For example, if the four ACs are AC_VO, AC_VI, AC_BK, and AC_BE, and the four AIDs are AID 0, AID 1, AID 2, and AID 3, the correspondence between the four ACs and the four AIDs may be as shown in Table 3 or Table 4.

[0200] Table 4 Correspondence between AID and four ACs

[0201]

number

[0222] It can be seen from Table 3 that the correspondence between the four AIDs and the four ACs may be such that the size of the AIDs corresponds one-to-one with the priority of the AC. It can be seen from Table 4 that the correspondence between the four AIDs and the four ACs may alternatively be independent of the size of the AIDs and the priority of the AC. It should be further noted that in Tables 3 and 4, four consecutive AIDs are used merely as an example, but do not constitute a limitation to this embodiment of the present application. In another possible implementation, when the second indication information indicates multiple AIDs, the multiple AIDs may be consecutive or non-consecutive. In other words, the second MLD may randomly select multiple AIDs from the available AID space and allocate the multiple AIDs to the first MLD. At least one AID corresponding to at least one data type supported by the first MLD is indicated by using the second indication information, so that the AIDs can be more flexibly allocated to the first MLD.

[0202]

[0223] In an implementation, the first MLD may support a plurality of data types, the second indication may indicate a first association identifier, the first association identifier corresponding to the first data type of the plurality of data types, and the first MLD may determine an association identifier corresponding to a data type other than the first data type of the plurality of data types based on the first association identifier corresponding to the first data type.

[0203]

[0224] For example, the data type includes a management frame and an AC. It is assumed that the first association identifier indicated by the second indication is AID 0, and AID 0 corresponds to a management frame supported by the first MLD. The first MLD may determine that AC_VO, AC_VI, AC_BK, and AC_BE correspond to AID 0+1, AID 0+2, AID 0+3, and AID 0+4, respectively, based on the supported management frames and the priorities of various ACs. That is, the four ACs supported by the first MLD correspond to the four consecutive AIDs following AID 0 indicated by the second indication. Alternatively, AC_VO, AC_VI, AC_BE, and AC_BK may correspond to AID 0+2, AID 0+4, AID 0+6, and AID 0+8, respectively. That is, the AIDs corresponding to the various data types supported by the first MLD may not be consecutive.

[0204]

[0225] In the above example, the first association identifier indicated by the second indication information is AID 0, and AID 0 corresponds to a management frame, which is merely used as a specific example and does not constitute a limitation to this embodiment of the present application. For example, the first association identifier indicated by the second indication information may be AID 2, and AID 3 corresponds to a management frame. 2corresponds to AC_VI in four ACs supported by the first MLD. In this case, the first MLD may determine that the management frame, AC_VO, AC_BK, and AC_BE correspond to AID 2+1, AID 2+2, AID 2+3, and AID 2+4, respectively, based on the priority of various supported data types. Alternatively, AC_VO corresponds to AID 2-1, the management frame corresponds to AID 2-2, and AC_BK and AC_BE correspond to AID 2+1 and AID 2+2, respectively. If the AID indicated by the second indication information corresponds to one of the data types supported by the first MLD, the first MLD can determine the AID corresponding to the other supported data type based on the AID. The AID is indicated in the second indication information. This can effectively reduce the signaling overhead.

[0205]

[0226] In implementation, when the second indication information indicates at least two AIDs, one AID among the at least two AIDs corresponds to a management frame, and the remaining AIDs correspond to service types supported by the first MLD. The AIDs corresponding to some service types supported by the first MLD and the AIDs corresponding to the management frame are indicated by using the second indication information, so that the signaling overhead can be effectively reduced, and the method in which the first MLD determines the AID corresponding to the management frame and the AID corresponding to each supported service type can be improved.

[0206]

[0227] It should be noted that the second MLD can send the second indication information to each of the multiple first MLDs to assign a different AID to each first MLD. In other words, different first MLDs have different AIDs. For example, when two first MLDs (first MLD-a and 1If each of the first MLD-a and the second MLD-b supports management frames and four ACs (AC_VO (voice), AC_VI (video), AC_BE (best effort), and AC_BK (background)), the first MLD-a and 1 A schematic diagram of the management frames supported by the MLD-b and the AIDs corresponding to each AC may be as shown in FIG. 3b. The AIDs of the first MLD-a are AID 0 to AID 4, and the AIDs of the second MLD-b are AID 1 to AID 4. 1 It can be seen from FIG. 3b that the AIDs of the first MLD-b are AID 5 to AID 8. That is, the AIDs of the first MLD-a are AID 5 to AID 8. 1 This differs from the AID of MLD-b.

[0207]

[0228] In implementation, the quantity of AIDs assigned by the second MLD to the first MLD may be equal to the quantity of data types supported by the first MLD. When a data type supported by the first MLD is added, the second MLD assigns a new AID to the newly supported data type by the first MLD. In this way, unnecessary AID assignment can be avoided.

[0208]

[0229] In an implementation, the second MLD may assign one AID to one or more data types supported by the same first MLD. For example, if the data types supported by the first MLD are management frames, AC_VO, AC_VI, AC_BE, and AC_BK, the second MLD may assign one AID to management frames, AC_VO, and AC_VI, and another AID to AC_BE and AC_BK. Alternatively, the second MLD may assign one AID to management frames, one AID to AC_VO, and another AID to AC_VI, AC_BE, and AC_BK. Alternatively, the second MLD may assign one different AID to each of management frames, AC_VO, and AC_VI, and another AID to AC_BE and AC_BK. The same AID may be assigned to multiple data types, so that the number of AIDs assigned to the first MLD may be less than the number of data types supported by the first MLD, thus effectively reducing the number of AIDs.

[0209]

[0230] In the case where the same AID is assigned to multiple data types, if the value of the bit corresponding to the AID in the TIM field is 1, it may indicate that all or some of the bufferable data of the data type corresponding to the AID is buffered in the second MLD. If the value of the bit corresponding to the AID in the TIM field is 0, it may indicate that no bufferable data of any data type corresponding to the AID is buffered in the second MLD.

[0210]

[0231] In the implementation, after determining the buffer status of the bufferable data corresponding to at least one supported data type and located in the second MLD, the first MLD can determine the operation status of at least one station among the multiple stations in the first MLD based on the buffer status of the bufferable data corresponding to at least one data type and located in the second MLD. In the implementation, the first MLD can determine the operation status of at least one station among the multiple stations in the first MLD based on at least one of the current battery level information or service requirement information of the first MLD and based on the buffer status of the bufferable data corresponding to at least one data type and located in the second MLD. For the execution process, please refer to the specific description of step S203 in FIG. 2. Details will not be described again here.

[0211]

[0232] According to this embodiment of the present application, a buffer status of bufferable data in the second MLD corresponding to at least one data type can be determined based on the first indication information and the correspondence between the association identifier of the first MLD and the supported data type. Further, a more suitable working state is determined for the station based on the data type of the bufferable data, which is helpful to reduce power consumption.

[0212]

[0233] FIG. 4a is a schematic flow chart of another method for determining a data buffer status according to an embodiment of the present application. The method describes in detail how the second MLD determines whether at least one bufferable data corresponding to a second data type is buffered, and how the first MLD determines whether at least one bufferable data corresponding to a second data type is buffered in the second MLD based on the third indication information from the second MLD. Steps S401 and S402 are performed by the second MLD or a chip in the second MLD, and step S403 is performed by the first MLD or a chip in the first MLD. A specific example of the second MLD and the first MLD performing the method for determining a data buffer status is used in the following description. The method may include, but is not limited to, the following steps:

[0213]

[0234] Step S401: A second multi-link device MLD determines whether bufferable data corresponding to at least one second data type is buffered in the second MLD, where the second data type is any data type mapped to the first link.

[0214]

[0235] In this embodiment of the present application, one or more data types are mapped to one link, one data type is mapped to one or more links, and bufferable data corresponding to each data type mapped to the link can be transmitted over the link. If the bufferable data corresponding to at least one second data type is buffered in the second MLD, it can indicate that the bufferable data in the second MLD may be transmitted over the first link to the first MLD. If the bufferable data corresponding to the second data type is not buffered in the second MLD, it can indicate that the bufferable data corresponding to each data type mapped to the first link has been completely transmitted. In other words, the bufferable data in the second MLD is not transmitted over the first link to the first MLD. The second MLD can determine whether the bufferable data corresponding to at least one second data type is buffered in the second MLD, thereby determining whether the bufferable data is transmitted over the first link to the first MLD. The first link is a link between the first MLD and the second MLD.

[0215]

[0236] Step S402: The second MLD transmits bufferable data to the first MLD via the first link, where the bufferable data includes third indication information, and the third indication information is used to indicate whether the bufferable data corresponding to at least one second data type is buffered in the second MLD.

[0216]

[0237] In this embodiment of the present application, the bufferable data transmitted through the first link may carry third indication information to indicate whether the bufferable data is transmitted to the first MLD through the first link. It should be noted that the second MLD determines whether at least one bufferable data corresponding to the second data type is buffered in the second MLD means: whether at least one bufferable data corresponding to the second data type is buffered in the second MLD in addition to the bufferable data to which the third indication information belongs.

[0217]

[0238] For example, data type a and data type b are mapped to link 1. When the second MLD transmits bufferable data to the first MLD via link 1, if the bufferable data corresponding to data type a or the bufferable data corresponding to data type b is buffered in the second MLD, it may indicate that the bufferable data may be transmitted to the first MLD via link 1. If neither the bufferable data corresponding to data type a nor the bufferable data corresponding to data type b is buffered in the second MLD, it may indicate that the bufferable data is not transmitted to the first MLD via link 1.

[0218]

[0239] It should be further noted that each piece of bufferable data transmitted by the second MLD to the first MLD via the first link carries third indication information, and the third indication information carried in each piece of bufferable data is used to indicate whether or not the bufferable data corresponding to at least one second data type is buffered in the second MLD.

[0219]

[0240] The MAC frame structure of the bufferable data includes a Frame Control field, the Frame Control field includes a More Data subfield, and the length of the More Data subfield is 1 bit. In this embodiment of the present application, the third indication information may be a More Data subfield in the bufferable data. Specifically, when the second MLD transmits the bufferable data to the first MLD via the first link, if at least one bufferable data corresponding to the second data type is buffered in the second MLD, the value of the More Data subfield in the bufferable data may be 1. If no bufferable data corresponding to any second data type is buffered in the second MLD, the value of the More Data subfield in the bufferable data may be 0. The fact that the third indication information is a More Data subfield in the bufferable data is merely used as a specific example and does not constitute a limitation on this embodiment of the present application. In another possible implementation, the third indication information may be another field in the MAC frame structure of the bufferable data.

[0220]

[0241] Step S403: The first MLD determines, according to the third indication information, whether at least one bufferable data corresponding to the second data type is buffered in the second MLD.

[0221]

[0242] Specifically, after receiving the bufferable data from the second MLD via the first link, the first MLD can determine whether the bufferable data corresponding to at least one second data type is buffered in the second MLD based on the third indication information in the bufferable data. When the third indication information is a More Data subfield in the bufferable data, if the value of the More Data subfield in the bufferable data is 1, the first MLD can determine that the bufferable data corresponding to at least one second data type is buffered in the second MLD. If the value of the More Data subfield in the bufferable data is 0, the first MLD can determine that no bufferable data corresponding to any second data type is buffered in the second MLD. For example, if the data types mapped to the first link include management frames and AC_VO, a value of 1 in the More Data subfield in the bufferable data received by the first MLD on the first link indicates that at least one type of bufferable data in the bufferable data corresponding to the management frames and the bufferable data corresponding to the AC_VO will be transmitted to the first MLD on the first link. A value of 0 in the More Data subfield in the bufferable data received by the first MLD on the first link indicates that neither the bufferable data corresponding to the management frames nor the bufferable data corresponding to the AC_VO will be transmitted to the first MLD on the first link.

[0222]

[0243] In an implementation, the first MLD may have a plurality of stations. After determining whether bufferable data corresponding to at least one second data type is buffered in the second MLD, the first MLD may determine an operation state of a station corresponding to the first link among the plurality of stations in the first MLD based on whether bufferable data corresponding to at least one second data type is buffered in the second MLD.

[0223]

[0244] In the implementation, if at least one bufferable data corresponding to the second data type is buffered in the second MLD, i.e., if the value of the More Data subfield is 1, the first MLD can determine the operating state of the station corresponding to the first link as an active state; if no bufferable data corresponding to the second data type is buffered in the second MLD, i.e., if the value of the More Data subfield is 0, the first MLD can determine the operating state of the station corresponding to the first link as an active state or a doze state.

[0224]

[0245] In the prior art, the second MLD may include multiple buffer areas, one buffer area corresponding to one link, and the bufferable data buffered in different buffer areas is transmitted to the first MLD through different links. The More Data subfield of the bufferable data is used to indicate whether there is bufferable data buffered in the buffer area corresponding to the link for transmitting the bufferable data. If there is no bufferable data buffered in the buffer area corresponding to the link for transmitting the bufferable data (e.g., link 1), the value of the More Data subfield of the bufferable data is 0. Accordingly, the first MLD can determine the operation state of the station corresponding to link 1 as a doze state. However, the first MLD cannot receive the bufferable data through link 2 when cases such as link congestion and interference occur on other links (e.g., link 2). Since link 1 is in the doze state, the bufferable data that should be transmitted through link 2 cannot be scheduled for transmission to link 1.

[0225]

[0246] However, in this embodiment of the present application, if the data type of the bufferable data that should originally be transmitted via link 2 is also mapped to link 1 (i.e., the first link), before the bufferable data corresponding to the data type is completely transmitted, the first MLD does not determine the operation state of the station corresponding to link 1 as a doze state. That is, link 1 is not in a doze state. Therefore, the second MLD can schedule the bufferable data corresponding to the data type (including the bufferable data that should originally be transmitted via link 2) to link 1 for transmission. According to this embodiment of the present application, a more suitable operation state is determined for the station, and the bufferable data in the second MLD is successfully transmitted to the first MLD.

[0226]

[0247] In another implementation, based on at least one of the current battery level information or service requirement information of the first MLD, and based on whether bufferable data corresponding to at least one second data type is buffered in the second MLD, the first MLD can determine the operation state of the station corresponding to the first link among the multiple stations in the first MLD. For the execution process, please refer to the specific description of step S203 in Figure 2. The details will not be described again here.

[0227]

[0248] In an implementation, if the third indication information indicates that at least one bufferable data corresponding to the second data type is buffered in the second MLD, the second MLD can send a fourth indication information to the first MLD, and the fourth indication information is used to indicate that no bufferable data corresponding to any second data type is buffered in the second MLD. After receiving the fourth indication information, the first MLD can determine that no bufferable data corresponding to any second data type is buffered in the second MLD. That is, after receiving the fourth indication information, the first MLD can determine that no bufferable data will be transmitted through the first link thereafter.

[0228]

[0249] A schematic diagram of a scenario shown in Fig. 4b, in which a second MLD transmits bufferable data to a first MLD, is used as an example. The first MLD supports data type a and data type b, and the links between the first MLD and the second MLD include link 1 and link 2, where data type a and data type b are mapped to link 1, and data type b is mapped to link 2. In Fig. 4b, the white-filled rectangles indicate bufferable data corresponding to data type a, the grey-filled rectangles indicate bufferable data corresponding to data type b, and the numbers in the rectangles are used to uniquely identify one piece of bufferable data. In Fig. 4b, the last piece of bufferable data to be transmitted on link 1 is bufferable data 2, and the last piece of bufferable data to be transmitted on link 2 is bufferable data 4. When the second MLD transmits bufferable data 2 to the first MLD via link 1, the second MLD can set the value of the More Data subfield in bufferable data 2 to 1 because bufferable data 4 is buffered in the second MLD and data type b to which bufferable data 4 belongs is mapped to link 1.

[0229]

[0250] Since data type b is mapped to link 1 and link 2, bufferable data 4 can be transmitted via link 1 or link 2. If the second MLD then transmits bufferable data 4 to the first MLD via link 2, the second MLD can transmit the bufferable data to the first MLD via link 2 because both the bufferable data corresponding to data type a mapped to link 1 and the bufferable data corresponding to data type b mapped to link 1 are transmitted completely. 1MLD via the first link, and it is not possible to use the More Data subfield in the bufferable data to indicate that neither the bufferable data corresponding to data type a nor the bufferable data corresponding to data type b is buffered in the second MLD. In other words, it is not possible to indicate by using the More Data subfield in the bufferable data that no more bufferable data will be transmitted to the first MLD via link 1.

[0230]

[0251] In this case, the above problem can be solved by sending a fourth indication information by the second MLD to the first MLD. The fourth indication information can indicate that no bufferable data corresponding to any data type mapped to link 1 is buffered in the second MLD. Specifically, the fourth indication information can indicate that neither the bufferable data corresponding to data type a nor the bufferable data corresponding to data type b is buffered in the second MLD.

[0231]

[0252] In an implementation, the fourth indication may be a QoS Null frame, which is a data frame that carries no payload, and in which a More Data subfield in the QoS Null frame has a value of 0. The second MLD may transmit the QoS Null frame to the first MLD via the first link.

[0232]

[0253] In an implementation, after receiving the fourth instruction information from the second MLD, the first MLD may determine the operation state of the station corresponding to the first link as a doze state based on the fourth instruction information. This helps to reduce power consumption. In another implementation, the first MLD may determine the operation state of the station corresponding to the first link based on the fourth instruction information and at least one of the current battery level information or the service requirement information. For example, after the first MLD receives the fourth instruction information from the second MLD, if the current remaining battery level of the first MLD is relatively low and / or the first MLD is not in a charging mode, the operation state of the station corresponding to the first link may be determined as a doze state. If the current remaining battery level of the first MLD is relatively high or the first MLD is in a charging mode, the operation state of the station corresponding to the first link may be determined as an active state.

[0233]

[0254] In an implementation, when the second MLD transmits bufferable data (e.g., bufferable data 1) to the first MLD via the first link, if bufferable data corresponding to at least one second data type is further buffered in the second MLD in addition to the bufferable data 1, the second MLD may set a value of a More Data subfield in the bufferable data 1 to 0. After receiving the bufferable data 1, the first MLD may set the station corresponding to the link 1 for transmitting the bufferable data 1 to a doze state. Correspondingly, the link 1 also enters a doze state. After receiving the link status indication information used to indicate that the link 1 is in an active state and transmitted by the first MLD, the second MLD may transmit data via the link 1. Before receiving the link status indication information used to indicate that the link 1 is in an active state and transmitted by the first MLD, the second MLD may not transmit data via the link 1. In this way, the second MLD can avoid scheduling bufferable data to link 1 for transmission if link 1 is not determined to be in an active state, which would otherwise be transmitted over another link. This helps to avoid unnecessary overhead. The link status indication used to indicate that link 1 is in an active state may be a power saving poll (PS-Poll) frame. The PS-Poll frame may be used to indicate that the link is in an active state.

[0234]

[0255] It should be noted that upon determining that the first link is in an active state, the second MLD transmits bufferable data to the first MLD via the first link (i.e., step S402). The first MLD may transmit a PS-Poll frame to the second MLD to inform the second MLD that the first link is in an active state. If the first MLD determines that bufferable data that needs to be transmitted via the first link is buffered in the second MLD, the first MLD may determine the operation state of the first link as an active state and transmit a PS-Poll frame to the second MLD that is used to indicate that the first link is in an active state. In an implementation, the second MLD may send a conventional beacon frame to the first MLD, where a TIM field in the beacon frame is used to indicate the buffer status of the bufferable data of each station in the first MLD in the second MLD. The first MLD can determine whether bufferable data that needs to be transmitted over the first link is buffered in the second MLD based on the TIM field and the correspondence between the links and stations of the first MLD.

[0235]

[0256] In another implementation, the second MLD can send the first indication information in the embodiment shown in Fig. 3a to the first MLD. The first MLD can determine a buffer status of the bufferable data corresponding to at least one data type and in the second MLD based on the first indication information and the corresponding relationship between the association identifier of the first MLD and the data type supported by the first MLD. Furthermore, the first MLD determines whether the bufferable data that needs to be transmitted on the first link is buffered in the second MLD based on the buffer status of the bufferable data corresponding to at least one data type and in the second MLD and the mapping relationship between the data type supported by the first MLD and the link. For the implementation process, please refer to the embodiment shown in Fig. 5A and Fig. 5B.

[0236]

[0257] According to this embodiment of the present application, whether the bufferable data corresponding to at least one second data type is buffered in the second MLD may be determined based on the third indication information.Furthermore, based on whether the bufferable data corresponding to at least one second data type is buffered in the second MLD, a more suitable operating state is determined for the station, and the bufferable data in the second MLD is successfully transmitted to the first MLD.

[0237]

[0258] 5A and 5B are schematic flow charts of yet another method for determining a data buffer status according to an embodiment of the present application. Steps S501 to S503, S507, and S508 are performed by the second MLD or a chip in the second MLD, and steps S504 to S506, and S509 are performed by the first MLD or a chip in the first MLD. A specific example of the second MLD and the first MLD performing the method for determining a data buffer status is used in the following description. The method may include, but is not limited to, the following steps:

[0238]

[0259] Step S501: A second MLD determines a buffer status of bufferable data in the second MLD, which corresponds to at least one data type supported by the first MLD.

[0239]

[0260] Step S502: The second MLD determines a buffer status of bufferable data in the second MLD that corresponds to at least one data type supported by the first MLD, and corresponds to an association identifier of the first MLD based on a correspondence between the association identifier of the first MLD and the supported data types.

[0240]

[0261] Step S503: The second MLD sends first indication information to the first MLD, where the first indication information corresponds to an association identifier of the first MLD and is used to indicate a buffer status of bufferable data in the second MLD.

[0241]

[0262] Step S504: The first MLD determines a buffer status of bufferable data in the second MLD that corresponds to at least one data type based on the first indication information and the correspondence between the association identifier of the first MLD and the data types supported by the first MLD.

[0242]

[0263] It should be noted that for the process of performing steps S501 to S504, please refer to the specific description of each step S301 to S304 in Fig. 3a, and the details will not be described again here.

[0243]

[0264] Step S505: The first MLD determines an operating state of a station corresponding to the first link as an active state based on a buffer status of bufferable data corresponding to at least one data type and in the second MLD, and a mapping relationship between the data types supported by the first MLD and the links corresponding to the first MLD.

[0244]

[0265] Specifically, the first MLD may determine a link to which the data type corresponding to the bufferable data is mapped based on a buffer status of the bufferable data corresponding to at least one data type and in the second MLD, and a mapping relationship between the data types supported by the first MLD and the links corresponding to the first MLD. If the links to which the data type corresponding to the bufferable data is mapped include the first link, the first MLD may determine the operation state of the station corresponding to the first link as an active state.

[0245]

[0266] Step S506: The first MLD sends a link status indication information to the second MLD, where the link status indication information is used to indicate that the first link is in an active state.

[0246]

[0267] After determining the operational state of the station corresponding to the first link as an active state, the first MLD may determine the operational state of the first link as an active state. If the operational state of the first link is an active state, the first MLD sends link status indication information to the second MLD. The link status indication information may be a PS-Poll frame. In an implementation, the link status indication information may be sent to the second MLD via the first link.

[0247]

[0268] Step S507: The second MLD determines whether bufferable data corresponding to at least one second data type is buffered in the second MLD, where the second data type is any data type mapped to the first link.

[0248]

[0269] After receiving the link status indication, the second MLD may determine that the first link is in an active state based on the link status indication, and if the second MLD determines that the first link is in an active state, the second MLD may transmit bufferable data carrying the third indication to the first MLD over the first link.

[0249]

[0270] Step S508: The second MLD transmits bufferable data to the first MLD via the first link, where the bufferable data includes third indication information, and the third indication information is used to indicate whether the bufferable data corresponding to at least one second data type is buffered in the second MLD.

[0250]

[0271] Step S509: The first MLD determines, based on the third indication information, whether at least one bufferable data corresponding to the second data type is buffered in the second MLD.

[0251]

[0272] It should be noted that for the process of performing step S507 to step S509, please refer to the specific description of step S401 to step S403 in Fig. 4a respectively, and the details will not be described again here.

[0252]

[0273] In this embodiment of the present application, the first MLD can determine an operation state of the station corresponding to the first link as an active state based on a buffer status of the bufferable data corresponding to at least one data type and in the second MLD, and a mapping relationship between the data types supported by the first MLD and the links corresponding to the first MLD. The second MLD can determine that the first link is in an active state based on link status indication information from the first MLD. When determining that the first link is in an active state, the second MLD transmits the bufferable data carrying the third indication information to the first MLD via the first link.

[0253]

[0274] FIG. 6a is a schematic flow chart of yet another method for determining a data buffer status according to an embodiment of the present application. The method describes in detail how the first MLD determines whether bufferable data corresponding to a third data type is buffered in the second MLD based on the fifth indication information. Steps S601 and S602 are performed by the second MLD or a chip in the second MLD, and step S603 is performed by the first MLD or a chip in the first MLD. A concrete example of the second MLD and the first MLD performing the method for determining a data buffer status is used in the following description. The method may include, but is not limited to, the following steps:

[0254]

[0275] Step S601: A second multi-link device MLD determines whether bufferable data corresponding to a third data type is buffered in the second MLD.

[0255]

[0276] In this embodiment of the present application, a data type can be mapped to one or more links, and bufferable data corresponding to the data type and buffered in the second MLD can be transmitted to the first MLD via any link to which the data type is mapped. For example, if the first MLD supports data type a, the links between the first MLD and the second MLD include link 1, link 2, and link 3, data type a is mapped to link 1, link 2, and link 3, and bufferable data corresponding to data type a can be transmitted to the first MLD via one or more of link 1, link 2, and link 3.

[0256]

[0277] The second MLD determining whether the bufferable data corresponding to the third data type is buffered in the second MLD is equivalent to determining whether the bufferable data corresponding to the third data type and buffered in the second MLD is completely transmitted. If the bufferable data corresponding to the third data type is buffered in the second MLD, it indicates that the bufferable data corresponding to the third data type is not completely transmitted. If the bufferable data corresponding to the third data type is not buffered in the second MLD, it indicates that the bufferable data corresponding to the third data type is completely transmitted.

[0257]

[0278] Step S602: The second MLD sends bufferable data corresponding to a third data type to the first MLD, where the bufferable data includes fifth indication information, and the fifth indication information is used to indicate whether the bufferable data corresponding to the third data type is buffered in the second MLD.

[0258]

[0279] In this embodiment of the present application, the fifth indication information may be carried in the bufferable data corresponding to the third data type to indicate whether the bufferable data corresponding to the third data type is buffered in the second MLD (i.e., to indicate whether the bufferable data corresponding to the third data type has been completely transmitted). It should be noted that the second MLD determines whether the bufferable data corresponding to the third data type is buffered in the second MLD: means whether the bufferable data corresponding to the third data type is buffered in the second MLD in addition to the bufferable data to which the fifth indication information belongs. It should be further noted that each piece of bufferable data transmitted by the second MLD to the first MLD carries the fifth indication information, and the fifth indication information carried in each piece of bufferable data is used to indicate whether the bufferable data corresponding to the data type to which the bufferable data belongs is buffered in the second MLD.

[0259]

[0280] In an implementation, the fifth indication information may be a More Data subfield in the bufferable data. Specifically, when the second MLD transmits bufferable data (e.g., bufferable data 1) corresponding to a third data type to the first MLD, if the bufferable data corresponding to the third data type is buffered in the second MLD, the value of the More Data subfield in the bufferable data 1 may be 1. If the bufferable data corresponding to the third data type is not buffered in the second MLD, the value of the More Data subfield in the bufferable data 1 may be 0. The fact that the fifth indication information is a More Data subfield in the bufferable data is used merely as a concrete example and does not constitute a limitation to this embodiment of the present application. In another possible implementation, the fifth indication information may be another field in the MAC frame structure of the bufferable data.

[0260]

[0281] Step S603: The first MLD determines, according to the fifth indication information, whether bufferable data corresponding to the third data type is buffered in the second MLD.

[0261]

[0282] Specifically, after receiving the bufferable data corresponding to the third data type from the second MLD, the first MLD may determine whether the bufferable data corresponding to the third data type is buffered in the second MLD based on the fifth indication information in the bufferable data. If the fifth indication information is a More Data subfield of the bufferable data, the first MLD may determine that the bufferable data corresponding to the third data type is buffered in the second MLD if the value of the More Data subfield in the bufferable data is 1. If the value of the More Data subfield in the bufferable data is 0, the first MLD may determine that the bufferable data corresponding to the third data type is not buffered in the second MLD.

[0262]

[0283] In the implementation, the first MLD may have multiple stations. After determining whether the bufferable data corresponding to the third data type is buffered in the second MLD, the first MLD may determine the operation state of the station corresponding to the second link among the multiple stations in the first MLD based on whether the bufferable data corresponding to the third data type is buffered in the second MLD. The third data type is mapped to the second link. For example, if the bufferable data corresponding to the third data type is buffered in the second MLD, i.e., the bufferable data corresponding to the third data type has not been completely transmitted, the first MLD determines the operation state of the station corresponding to the second link as an active state, so that the bufferable data corresponding to the third data type and not completely transmitted can be transmitted to the first MLD via the second link. There may be one or more second links.

[0263]

[0284] In another implementation, the first MLD can determine the working state of the station corresponding to the second link among the multiple stations in the first MLD based on at least one of the current battery level information or service requirement information of the first MLD and based on whether the bufferable data corresponding to the third data type is buffered in the second MLD. For the execution process, please refer to the specific description of step S203 in FIG. 2. Details will not be described again here.

[0264]

[0285] In yet another implementation, after determining whether the bufferable data corresponding to the third data type is buffered in the second MLD, the first MLD determines whether a data type other than the third data type is mapped to the second link; and may determine an operation state of a station corresponding to the second link among a plurality of stations in the first MLD based on whether the bufferable data corresponding to the third data type is buffered in the second MLD and whether a data type other than the third data type is mapped to the second link. Specifically, if the bufferable data corresponding to the third data type is not buffered in the second MLD but a data type other than the third data type is mapped to the second link, i.e., if the bufferable data corresponding to the data type other than the third data type mapped to the second link may be transmitted on the second link, the first MLD may determine the operation state of the station corresponding to the second link as an active state. If the bufferable data corresponding to the third data type is not buffered in the second MLD, and data types other than the third data type are not mapped to the second link, i.e., the bufferable data is not transmitted on the second link any more, the first MLD can determine the operation state of the station corresponding to the second link as a doze state. In this way, a more suitable operation state is determined for the station in the first MLD, and power consumption is reduced.

[0265]

[0286] The schematic diagram of the scenario for determining the operational state of links shown in Fig. 6b is used as an example. The first MLD supports data type a and data type b, the links between the first MLD and the second MLD include link 1, link 2, and link 3, data type a and data type b are mapped to link 1, data type b is mapped to link 2, and data type b is mapped to link 3. In Fig. 6b, the white-filled rectangles indicate bufferable data corresponding to data type a, the gray-filled rectangles indicate bufferable data corresponding to data type b, and the numbers in the rectangles are used to uniquely identify one piece of bufferable data. In Fig. 6b, the last piece of bufferable data to be transmitted on link 1 is bufferable data a2, the last piece of bufferable data to be transmitted on link 2 is bufferable data b4, and the last piece of bufferable data to be transmitted on link 3 is bufferable data b2.

[0266]

[0287] It can be seen from Fig. 6b that the last piece of bufferable data (a2) corresponding to data type a and buffered in the second MLD is transmitted via link 1, and the last piece of bufferable data (b4) corresponding to data type b and buffered in the second MLD is transmitted via link 2. Thus, if the value of the More Data subfield of the bufferable data a2 is 0, it indicates that before the second MLD transmits the bufferable data a2, the bufferable data corresponding to data type a is buffered in the second MLD, and after the second MLD transmits the bufferable data a2, the bufferable data corresponding to data type a is not buffered in the second MLD. If the value of the More Data subfield of the bufferable data b4 is 0, it indicates that before the second MLD transmits the bufferable data b4, the bufferable data corresponding to the data type b is buffered in the second MLD, and after the second MLD transmits the bufferable data b4, the bufferable data corresponding to the data type b is not buffered in the second MLD.

[0267]

[0288] Only data type b is mapped to link 2 and link 3, i.e., link 2 and link 3 transmit only bufferable data corresponding to data type b. Therefore, after receiving b4, the first MLD can determine the operation state of both the station corresponding to link 2 and the station corresponding to link 3 as a doze state (i.e., the operation state of link 2 and link 3 can be determined as a doze state). This helps to reduce power consumption. Also, after the first MLD receives a2, both the last piece of bufferable data corresponding to data type a mapped to link 1 (i.e., a2) and the last piece of bufferable data corresponding to data type b mapped to link 1 (i.e., b4) are transmitted to the first MLD, so the first MLD can determine the operation state of the station corresponding to link 1 as a doze state (i.e., the operation state of link 1 can be determined as a doze state).

[0268]

[0289] If the More Data subfield of the bufferable data is used to indicate whether the bufferable data to be transmitted to the first MLD is buffered in the second MLD, in FIG. 6b, link 1, link 2, and link 3 indicate whether the first MLD has received the last bufferable data transmitted by the second MLD. data(i.e., a2) is received. In other words, none of Link 1, Link 2, and Link 3 can be switched to the doze state if the bufferable data to be transmitted to the first MLD is still buffered in the second MLD. Thus, compared with the More Data subfield of the bufferable data being used to indicate whether the bufferable data to be transmitted to the first MLD is buffered in the second MLD, according to this embodiment of the present application, a part of the link between the first MLD and the second MLD can be in the doze state if the bufferable data to be transmitted to the first MLD is still buffered in the second MLD. Correspondingly, the station corresponding to the doze state link of the first MLD also goes into the doze state. This reduces power consumption.

[0269]

[0290] The first MLD can know whether the bufferable data corresponding to the third data type is buffered in the second MLD based on the fifth indication information of the bufferable data 1. However, the first MLD can know whether the bufferable data corresponding to the third data type is buffered in the second MLD based on the fifth indication information of the bufferable data 1. Bufferable data corresponding to In the implementation, the bufferable data corresponding to the third data type received by the first MLD from the second MLD may further include sixth indication information, where the sixth indication information is used to indicate whether at least the bufferable data corresponding to the fourth data type is buffered in the second MLD, and the fourth data type is any data type other than the third data type among the data types supported by the first MLD. When the fifth indication information indicates that the bufferable data corresponding to the third data type is not buffered in the second MLD, i.e., the bufferable data corresponding to the third data type has been completely transmitted, the sixth indication information may indicate whether the bufferable data to be transmitted to the first MLD is buffered in the second MLD.

[0270]

[0291] In an implementation, if the fifth indication information of the bufferable data corresponding to the third data type indicates that the bufferable data corresponding to the third data type is not buffered in the second MLD, the bufferable data corresponding to the third data type may further include sixth indication information. If the fifth indication information of the bufferable data corresponding to the third data type indicates that the bufferable data corresponding to the third data type is buffered in the second MLD, the bufferable data corresponding to the third data type may not include the sixth indication information.

[0271]

[0292] In an implementation, the sixth indication information may be a "More Fragment" subfield of the bufferable data. Specifically, when the second MLD transmits bufferable data corresponding to the third data type (e.g., bufferable data 1) to the first MLD, and the value of the More Data subfield of the bufferable data 1 is 0 (i.e., the bufferable data corresponding to the third data type is completely transmitted), if at least one bufferable data corresponding to the fourth data type is buffered in the second MLD, the value of the More Fragment subfield of the bufferable data 1 may be 1. If no bufferable data corresponding to the fourth data type is buffered in the second MLD, the value of the More Fragment subfield of the bufferable data 1 may be 0. It should be noted that the sixth indication information being a More Fragment subfield of the bufferable data is used merely as a concrete example and does not constitute a limitation to this embodiment of the present application. In another possible implementation, the sixth indication information may be another field of the MAC frame structure of the bufferable data. If the first MLD receives the bufferable data 1 and the values ​​of the More Data subfield and the More Fragment subfield of the bufferable data 1 are both 0, it may indicate that the bufferable data to be transmitted to the first MLD is not buffered in the second MLD. In this case, the first MLD may switch all links between the first MLD and the second MLD to a doze state to reduce power consumption.For example, if the data types supported by the first MLD include management frames and AC_VO, if the value of the More Data subfield of the bufferable data corresponding to the AC_VO and received by the first MLD is 0 and the value of the More Fragment subfield of the bufferable data corresponding to the AC_VO and received by the first MLD is 0, it indicates that both the bufferable data corresponding to the AC_VO and the bufferable data corresponding to the management frames have been completely transmitted.

[0272]

[0293] In the implementation, the priority of the fourth data type may be higher than the priority of the third data type. In this case, the sixth indication information is used to indicate whether bufferable data corresponding to a data type having a higher priority than the priority of the third data type is buffered in the second MLD. If the priority of only one data type (e.g., data type 1) among the data types supported by the first MLD is higher than the priority of the third data type, the sixth indication information may indirectly indicate whether bufferable data corresponding to data type 1 is buffered in the second MLD. In the case where the priority of at least two data types among the data types supported by the first MLD is higher than the priority of the third data type, if the sixth indication information indicates that bufferable data corresponding to a data type having a higher priority than the third data type is not buffered in the second MLD, it may indicate that bufferable data corresponding to at least two data types is not buffered in the second MLD. By using the sixth indication information, the second MLD can inform the first MLD of a more detailed buffer status, so that the stations of the first MLD can know to determine a more appropriate operating state and reduce power consumption.

[0273]

[0294] In an implementation, the second MLD may determine that bufferable data corresponding to a fifth data type is not buffered in the second MLD, where the fifth data type is any one of data types supported by the first MLD, and the second MLD may send seventh indication information to the first MLD, where the seventh indication information is used to indicate that bufferable data corresponding to the fifth data type is not buffered in the second MLD. After receiving the seventh indication information, the first MLD may determine that bufferable data corresponding to the fifth data type is not buffered in the second MLD based on the seventh indication information.

[0274]

[0295] If the bufferable data corresponding to one or more data types (e.g., data type c) supported by the first MLD is not buffered in the second MLD, the second MLD cannot transmit the bufferable data corresponding to data type c to the second MLD, and cannot indicate that the bufferable data corresponding to data type c is not buffered in the second MLD by using the More Data subfield of the bufferable data corresponding to data type c. In other words, the first MLD cannot know that the bufferable data corresponding to data type c is not buffered in the second MLD. As a result, the first MLD cannot determine whether the station corresponding to the link to which data type c is mapped can switch to the doze state. In this case, if the seventh indication information received by the first MLD can indicate that the bufferable data corresponding to data type c is not buffered in the second MLD, the aforementioned problem can be solved.

[0275]

[0296] A schematic diagram of a scenario for determining the working state of a link shown in Fig. 6c is used as an example. Compared with Fig. 6b, a data type c supported by the first MLD is added to Fig. 6c, and the data type c is mapped to link 3. It can be seen from Fig. 6c that the last piece of bufferable data corresponding to data type b and buffered in the second MLD is b4. Only data type b is mapped to link 2, and data type c is mapped to link 3 in addition to data type b. Therefore, after receiving b4, the first MLD can determine the working state of the station corresponding to link 2 as a doze state, but cannot determine whether the working state of the station corresponding to link 3 can be determined as a doze state. In the implementation, if the first MLD receives the seventh indication information used to indicate that the bufferable data corresponding to the data type c is not buffered in the second MLD after the first MLD receives b4, the first MLD can determine the operation state of the station corresponding to the link 3 as a doze state after the first MLD receives the seventh indication information. It should be noted that in FIG. 6c, the second MLD sending the seventh indication information after b4 is used as a mere concrete example, but does not constitute a limitation on the present application. Alternatively, the second MLD may send the seventh indication information before b4, or may send b4 and the seventh indication information simultaneously.

[0276]

[0297] In the implementation, the seventh indication information is a QoS Null frame, which is a data frame that does not carry a payload, and the value of the More Data subfield of the QoS Null frame is 0. In the embodiment of the present application, the fifth data type indicated by the QoS Null frame may be determined based on a data type indication field in the QoS Null frame. For example, if the TID indicated by the data type indication field of the QoS Null frame is included in TID8 to TID15, it may be determined that the fifth data type indicated by the QoS Null frame is a management frame. If the TID indicated by the data type indication field of the QoS Null frame is TID 1, it may be determined that the fifth data type indicated by the QoS Null frame is TID 1. It should be noted that in FIG. 6c, the second MLD transmits the QoS Null frame to the first MLD via link 3 is used merely as an example, but does not constitute a limitation to the present application. The second MLD may transmit the QoS Null frame to the first MLD via any link between the first MLD and the second MLD.

[0277]

[0298] In the implementation, the second MLD determines that the bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD, and sends the eighth indication information to the first MLD through the fourth link, where the eighth indication information is used to indicate that the bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD. After receiving the eighth indication information, the first MLD can determine that the bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD based on the eighth indication information. For the implementation process, please refer to the specific description of the embodiment shown in FIG. 8. Details will not be described here.

[0278]

[0299] A schematic diagram of a scenario for determining the operational state of a link shown in Fig. 6d is used as an example. Compared with Fig. 6b, data types c and d supported by the first MLD are added to Fig. 6d, and both data types c and d are mapped to link 3. It can be seen from Fig. 6d that the last piece of bufferable data corresponding to data type b and buffered in the second MLD is b4. Only data type b is mapped to link 2, and data types c and d are mapped to link 3 in addition to data type b. Therefore, after receiving b4, the first MLD can determine the operational state of the station corresponding to link 2 as a doze state, but cannot determine whether the operational state of the station corresponding to link 3 can be determined as a doze state. In an implementation, after the first MLD receives b4, if the first MLD receives, via link 3, eighth indication information, the eighth indication information being used to indicate that bufferable data corresponding to any data type mapped to link 3 (i.e., the fourth link) is not buffered in the second MLD, the first MLD may determine the operation state of the station corresponding to link 3 as a doze state after the first MLD receives the eighth indication information.

[0279]

[0300] It should be noted that the second MLD may transmit bufferable data corresponding to the third data type to the first MLD via any link among the links to which the third data type is mapped. If it is determined that at least one link among the links to which the third data type is mapped is in an active state, the second MLD is required to transmit bufferable data corresponding to the third data type to the first MLD via the link to which the third data type is mapped and in an active state (e.g., link 1) (i.e., step S602). The first MLD may transmit a PS-Poll frame to the second MLD to indicate to the second MLD that link 1 is in an active state. If it is determined that the bufferable data corresponding to the third data type mapped to link 1 is buffered in the second MLD, the first MLD may determine the operation state of link 1 as an active state and transmit a PS-Poll frame to the second MLD used to indicate that link 1 is in an active state. In an implementation, the second MLD may send the first indication information in the embodiment shown in Fig. 3a to the first MLD, and the first MLD may determine that bufferable data corresponding to the third data type mapped to link 1 is buffered in the second MLD based on the first indication information and the correspondence between the association identifier of the first MLD and the data type supported by the first MLD.

[0280]

[0301] According to this embodiment of the present application, it is possible to determine whether the bufferable data corresponding to the third data type is buffered in the second MLD based on the fifth indication information of the bufferable data corresponding to the third data type. Furthermore, a more suitable working state is determined for the station of the first MLD based on whether the bufferable data corresponding to the third data type is buffered in the second MLD, and power consumption is reduced.

[0281]

[0302] 7 is a schematic flow chart of yet another method for determining a data buffer status according to an embodiment of the present application. Steps S701 and S702 are performed by the second MLD or a chip in the second MLD, and step S703 is performed by the first MLD or a chip in the first MLD. A specific example of the second MLD and the first MLD performing the method for determining a data buffer status is used in the following description. The method may include, but is not limited to, the following steps:

[0282]

[0303] Step S701: A second MLD determines that bufferable data corresponding to a fifth data type is not buffered in the second MLD, where the fifth data type is any data type supported by the first MLD.

[0283]

[0304] Step S702: The second MLD sends seventh indication information to the first MLD, where the seventh indication information is used to indicate that bufferable data corresponding to the fifth data type is not buffered in the second MLD.

[0284]

[0305] Step S703: The first MLD determines, based on the seventh indication information, that the bufferable data corresponding to the fifth data type is not buffered in the second MLD.

[0285]

[0306] It should be noted that for the process of performing steps S701 to S703, please refer to the specific description of step S603 in Fig. 6a, and the details will not be described again here.

[0307] In an implementation, the first MLD may have a plurality of stations. After determining that the bufferable data corresponding to the fifth data type is not buffered in the second MLD, the first MLD may determine an operational state of a station corresponding to a third link among the plurality of stations of the first MLD based on the bufferable data corresponding to the fifth data type not being buffered in the second MLD, where the fifth data type is mapped to the third link. For example, the first MLD may determine an operational state of the station corresponding to the third link as a doze state based on the bufferable data corresponding to the fifth data type not being buffered in the second MLD.

[0286]

[0308] In the implementation, the first MLD may determine an operational state of a station corresponding to the third link among the plurality of stations of the first MLD based on one or more related information and based on bufferable data corresponding to the fifth data type not being buffered in the second MLD, where the related information may include, but is not limited to: current battery level information of the first MLD, service requirement information of the first MLD, whether a data type other than the fifth data type is mapped to the third link, a priority of the fifth data type, and a priority of the data type other than the fifth data type mapped to the third link (if there is a data type other than the fifth data type that is mapped to the third link).

[0287]

[0309] According to this embodiment of the present application, it can be determined based on the seventh indication information that the bufferable data corresponding to the fifth data type is not buffered in the second MLD.

[0288]

[0310] 8 is a schematic flowchart of yet another method for determining a data buffer status according to an embodiment of the present application. Steps S801 and S802 are performed by the second MLD or a chip in the second MLD, and step S803 is performed by the first MLD or a chip in the first MLD. A specific example of the second MLD and the first MLD performing the method for determining a data buffer status is used in the following description. The method may include, but is not limited to, the following steps:

[0289]

[0311] Step S801: The second MLD determines that no bufferable data corresponding to any data type mapped to the fourth link is buffered in the second MLD.

[0290]

[0312] If bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD, it may indicate that the second MLD will not transmit data to the first MLD over the fourth link. For example, if the fourth link is link 1 and data type a and data type b are mapped to link 1, if neither bufferable data corresponding to data type a nor bufferable data corresponding to data type b is buffered in the second MLD, it may be determined that bufferable data corresponding to any data type mapped to link 1 (i.e., the fourth link) is not buffered in the second MLD.

[0291]

[0313] Step S802: The second MLD sends eighth indication information to the first MLD via the fourth link, where the eighth indication information is used to indicate that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD.

[0292]

[0314] In this embodiment of the present application, the eighth indication information is a QoS Null frame, which is a data frame that does not carry a payload, and the value of the More Data subfield of the QoS Null frame is 0. When the QoS Null frame is transmitted to the first MLD via link 1, it may indicate that bufferable data (used to transmit the QoS Null frame) corresponding to any data type mapped to link 1 is not buffered in the second MLD.

[0293]

[0315] Step S803: The first MLD determines, based on the eighth indication information, that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD.

[0294]

[0316] Specifically, after receiving the eighth indication information from the second MLD via the fourth link, the first MLD is capable of determining, based on the eighth indication information, that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD.

[0295]

[0317] In an implementation, the first MLD may have a plurality of stations. After determining that the bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD, the first MLD may determine an operational state of a station corresponding to the fourth link among the plurality of stations in the first MLD based on the bufferable data corresponding to any data type mapped to the fourth link not being buffered in the second MLD. For example, the first MLD may determine an operational state of a station corresponding to the fourth link as a doze state based on the bufferable data corresponding to any data type mapped to the fourth link not being buffered in the second MLD.

[0296]

[0318] In an implementation, the first MLD may determine an operating state of a station corresponding to the fourth link based on one or more of the first MLD's current battery level information or service requirement information, and based on the fact that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD.

[0297]

[0319] According to this embodiment of the present application, based on the eighth indication information, it can be determined that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD.

[0298]

[0320] FIG. 9a is a schematic flow chart of yet another method for determining data buffer status according to an embodiment of the present application. The method describes in detail how the first MLD determines the buffer status of bufferable data in the second MLD, which corresponds to at least one data type mapped to at least one link, based on the tenth indication information. Steps S901 and S902 are performed by the second MLD or a chip in the second MLD, and step S903 is performed by the first MLD or a chip in the first MLD. A specific example of the second MLD and the first MLD performing the method for determining data buffer status is used in the following description. The method may include, but is not limited to, the following steps:

[0299]

[0321] Step S901: A second MLD determines a buffer status of bufferable data in the second MLD, which corresponds to at least one data type mapped to at least one link corresponding to the first MLD.

[0300]

[0322] In this embodiment of the present application, the second MLD may include multiple buffer areas, and each buffer area may be used to buffer bufferable data corresponding to one or more links (between the second MLD and the first MLD). If a buffer area r is used to buffer bufferable data corresponding to link 1, it may indicate that the bufferable data in buffer area r is to be transmitted to the first MLD via link 1. If a buffer area r is used to buffer bufferable data corresponding to link 1 and bufferable data corresponding to link 2, it may indicate that the bufferable data in buffer area r may be transmitted to the first MLD via at least one of links 1 and 2. Thus, the second MLD may determine whether bufferable data of a link corresponding to each buffer area exists in the second MLD by detecting whether bufferable data exists in each buffer area in the second MLD. One or more data types may be mapped to one link. Additionally, the second MLD may determine, in each buffer area, a buffer status of the data types mapped to the link corresponding to the buffer area.

[0301]

[0323] For example, the data type is a TID. If one buffer area is used to buffer the bufferable data corresponding to one link and the first MLD supports eight TIDs, the second MLD is capable of determining the buffer status of each TID in each buffer area.

[0302]

[0324] Step S902: The second MLD sends tenth indication information to the first MLD, where the tenth indication information is used to indicate a buffer status of bufferable data in the second MLD, corresponding to at least one data type mapped to at least one link corresponding to the first MLD.

[0303]

[0325] The tenth indication information may be a bit occupied by control type b in the EHT A-control field of the MAC frame. For the description of the EHT A-control field, please refer to the embodiment shown in Figure 2. The details will not be described again here. Control type b is a newly added control type.

[0304]

[0326] If the data type includes a management frame and a TID, control type b may be referred to as "More Data Per TID Per link". The number of bits occupied by "More Data Per TID Per link" may be 9*L, where L is the number of bits in the first MLD and Second The number of links between the first MLD and the second MLD. In this case, the "More Data Per TID Per link" subfield may include a "per link structure", where one "per link structure" corresponds to one link, and each "per link structure" may include 9 bits, where one bit in the "per link structure" corresponds to one data type. Specifically, one bit corresponds to a management frame, and each of the other 8 bits corresponds to one TID on the link. If the value of the bit in the "per link structure" corresponding to link 1 is 1, it may indicate that bufferable data of the data type corresponding to that bit (e.g., management frame or TID) is to be buffered in the second MLD and the bufferable data is to be transmitted via link 1 to the first MLD. If the value of the bit in the "per link structure" corresponding to link 1 is 0, it may indicate that bufferable data of the data type corresponding to that bit (e.g., management frame or TID) to be transmitted via link 1 is not buffered in the second MLD.

[0305]

[0327] Step S903: The first MLD determines, based on the tenth indication information, a buffer status of bufferable data in the second MLD, which corresponds to at least one data type mapped to at least one link.

[0306]

[0328] In an implementation, the tenth indication information may be a bit occupied by the "More Data Per TID Per link" subfield. In an implementation, if the first MLD assigns different buffer areas to each link, and one bit of the "per link structure" corresponds to one data type, after receiving the tenth indication information from the second MLD, the first MLD can determine the buffer status of the bufferable data, which corresponds to each data type mapped to each link and is in the second MLD, based on the tenth indication information. For example, if the links between the first MLD and the second MLD include link 1 and link 2, the schematic diagram of the "More Data Per TID Per link" subfield may be as shown in FIG. 9b. As shown in FIG. 9b, the "More Data Per TID Per link" subfield includes two "per link structures" (link 1 and link 2), and each small square in the figure represents one bit. Each bit of the "per link structure" corresponding to link 1 corresponds to one data type, and different bits correspond to different data types. In FIG. 9b, the 9 bits of the "per link structure" corresponding to link 1 (or link 2) correspond to T1D0 to TID7 and management frames, respectively. In the "per link structure" corresponding to link 1, the first 4 bits have a value of 1, and the last 4 bits have a value of 0. This can indicate that the bufferable data corresponding to TID 0 to TID 3 is buffered in the buffer area corresponding to link 1 of the second MLD, but the bufferable data corresponding to TID 4 to TID 7 and management frames is not buffered in the buffer area corresponding to link 1 of the second MLD. In the "per link structure" corresponding to link 2, the first and last bits have a value of 1, and the other bits have a value of 0.This may indicate that bufferable data corresponding to TID 0 and management frames is buffered in the buffer area corresponding to link 2 of the second MLD, but bufferable data corresponding to TID 1 through TID 7 is not buffered in the buffer area corresponding to link 2 of the second MLD.

[0307]

[0329] It should be noted that a "per link structure" containing 9 bits is merely used as an example, and in other possible implementations, a "per link structure" may contain one or more bits. For example, the number of bits contained in a "per link structure" may be the same as the number of data types mapped to the links corresponding to the "per link structure". If the data type is an AC, the number of bits contained in a "per link structure" may be the same as the number of ACs corresponding to the TIDs mapped to the links corresponding to the "per link structure".

[0308]

[0330] One bit in the "per link structure" corresponds to one data type (management frame, TID, or AC), and one bit in the "per link structure" may correspond to more than one data type (management frame, TID, or AC).

[0309]

[0331] In the implementation, when the first MLD assigns a different buffer area to each link and the bits of the "per link structure" correspond to at least two types, after receiving the tenth indication information from the second MLD, the first MLD can determine the buffer status of the bufferable data corresponding to the at least two types mapped to each link and located in the second MLD based on the tenth indication information. For example, if the first bit of the "per link structure" corresponding to link 1 corresponds to TID 1 and TID 2, and the value of the first bit is 1, it can indicate that the bufferable data corresponding to at least one TID of TID 1 and TID 2 is buffered in the buffer area corresponding to link 1 of the second MLD. If the value of the first bit is 0, it can indicate that neither the bufferable data corresponding to TID 1 nor the bufferable data corresponding to TID 2 is buffered in the buffer area corresponding to link 1 of the second MLD.

[0310]

[0332] In implementation, if the first MLD can allocate the same buffer area to at least two links, and one bit of the "per link structure" corresponds to one data type, after receiving the tenth indication information from the second MLD, the first MLD performs the following steps based on the tenth indication information: each Link At least one of at least two types mappedThe buffer status of the corresponding bufferable data in the second MLD may be determined. For example, if the buffer area r of the second MLD corresponds to link 1 and link 2, and the first bit of the "per link structures" corresponding to link 1 and link 2 corresponds to TID 1, if the value of the first bit is 1, it may indicate that the bufferable data corresponding to TID 1 is buffered in the buffer area r, and the bufferable data may be transmitted to the first MLD via link 1 and / or link 2. If the value of the first bit is 0, it may indicate that the bufferable data corresponding to TID 1 is not buffered in the buffer area r, and neither link 1 nor link 2 is used to transmit the bufferable data corresponding to TID 1.

[0311]

[0333] In the implementation, if the first MLD is capable of allocating the same buffer area to at least two links and the bits of the "per link structure" correspond to at least two data types, after receiving the tenth indication information from the second MLD, the first MLD can determine, based on the tenth indication information, the buffer status of bufferable data in the second MLD that corresponds to the at least two data types mapped to the at least two links.

[0312]

[0334] In the implementation, the first MLD may have multiple stations. The first MLD may determine an operational state of at least one of the multiple statuses of the first MLD based on a buffer status of bufferable data corresponding to at least one data type mapped to at least one link and residing in the second MLD. Specifically, the first MLD may determine an operational state of each status of the first MLD based on a buffer status of bufferable data corresponding to each data type mapped to each link and residing in the second MLD. For example, if bufferable data corresponding to TID 0 through TID 3 are buffered in a buffer area corresponding to link 1 of the second MLD, and bufferable data corresponding to TID 1 and TID 7 are buffered in a buffer area corresponding to link 2 of the second MLD, i.e., both the bufferable data corresponding to link 1 and the bufferable data corresponding to link 2 are buffered in the second MLD, the first MLD may determine the operational state of link 1 and link 2 as active. In this manner, bufferable data corresponding to TID 0 through TID 3 may be received via link 1, and bufferable data corresponding to TID 1 and TID 7 may be received via link 2.

[0313]

[0335] In an implementation, the first MLD may determine an operational status of at least one station in the plurality of stations of the first MLD based on one or more of current battery level information or service requirement information of the first MLD and based on a buffer status of bufferable data in the second MLD that corresponds to at least one data type mapped to at least one link.

[0314]

[0336] In this embodiment of the present application, a buffer status of the bufferable data in the second MLD, which corresponds to at least one data type mapped to at least one link, can be determined based on the tenth indication information. In this way, the buffer status of the bufferable data in the second MLD can be determined in more detail, which is helpful to determine a more suitable operating state for the station in the first MLD.

[0315]

[0337] In the above-mentioned embodiments provided in the present application, the method provided in the embodiment of the present application is described separately in terms of the first MLD and the second MLD. To realize the functions in the method provided in the above-mentioned embodiments of the present application, the first MLD and the second MLD each include a hardware structure and a software module, and can realize the above-mentioned functions in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. The functions in the above-mentioned functions may be performed in the manner of a hardware structure, a software module, or a combination of a hardware structure and a software module.

[0316]

[0338] Fig. 10 is a schematic diagram of a structure of a communication device 100 according to an embodiment of the present application. The communication device 100 shown in Fig. 10 may include a communication unit 1001 and a processing unit 1002. The communication unit 1001 may include a transmitting unit and / or a receiving unit. The transmitting unit is configured to realize a transmitting function, and the receiving unit is configured to realize a receiving function, and the communication unit 1001 can realize a transmitting function and / or a receiving function. Also, the communication unit may be described as a transceiver unit.

[0317]

[0339] The communication device 100 may be a first MLD, or may be a device in the first MLD, or may be a device capable of being used with the first MLD. When the communication device 100 is a first MLD, the communication device 100 may be a device that is capable of being used with the first MLD. Any of It may be the first MLD in the embodiment shown in FIG.

[0318]

[0340] The communication device 100 is a first MLD in the embodiment shown in FIG. 3a or FIGS. 5A and 5B.

[0319]

[0341] The communication unit 1001 is configured to receive first indication information from the second MLD, the first indication information being used to indicate a buffer status of bufferable data that corresponds to an association identifier of the communication device 100 and is in the second MLD.

[0320]

[0342] The processing unit 1002 is configured to determine a buffer status of bufferable data corresponding to at least one data type and in the second MLD based on the first indication information and a correspondence between an association identifier of the first MLD and a data type supported by the first MLD.

[0321]

[0343] In an implementation, the communication device 100 has a plurality of stations. The communication unit 1001 may be further configured to determine an operation state of at least one of the plurality of stations based on a buffer status of bufferable data corresponding to at least one data type and in a second MLD, where the operation state is an active state or a doze state.

[0322]

[0344] In the implementation, the communication unit 1001 is further configured to receive second indication information from the second MLD, where the second indication information is used to determine a correspondence between the association identifier and the data type.

[0323]

[0345] In an implementation, the second indication indicates at least one association identifier, the at least one association identifier corresponding to the at least one data type.

[0324]

[0346] In an embodiment, the communication device 100 may support a plurality of data types. The second indication indicates a first association identifier, where the first association identifier corresponds to a first data type in the plurality of data types. Further, the processing unit 1002 is configured to determine, based on the first association identifier corresponding to the first data type, an association identifier corresponding to a data type other than the first data type in the plurality of data types.

[0325]

[0347] The communication device 100 is a first MLD in the embodiment shown in FIG. 4a or FIGS. 5A and 5B.

[0326]

[0348] The communication unit 1001 is configured to receive bufferable data from a second MLD via a first link, the bufferable data including third indication information, the third indication information being used to indicate whether or not bufferable data corresponding to at least one second data type is buffered in the second MLD, the second data type being any data type mapped to the first link.

[0327]

[0349] The processing unit 1002 is configured to determine, based on the third indication, whether bufferable data corresponding to the at least one second data type is buffered in the second MLD.

[0328]

[0350] In an implementation, the communication device 100 has a plurality of stations. The processing unit 1002 is further configured to determine an operation state of a station corresponding to the first link among the plurality of stations based on whether bufferable data corresponding to the at least one second data type is buffered in the second MLD, where the operation state is an active state or a doze state.

[0329]

[0351] In an implementation, when the processing unit 1002 is configured to determine an operational state of a station corresponding to a first link among the plurality of stations based on whether bufferable data corresponding to at least one second data type is buffered in the second MLD, the processing unit 1002 is specifically configured to: determine an operational state of the station corresponding to the first link among the plurality of stations as an active state if bufferable data corresponding to at least one second data type is buffered in the second MLD; or, when no bufferable data corresponding to any second data type is buffered in the second MLD, determine an operational state of the station corresponding to the first link among the plurality of stations as an active state or a doze state.

[0330]

[0352] In an implementation, the third indication information indicates that at least one bufferable data corresponding to the second data type is buffered in the second MLD. The communication unit 1001 is further configured to receive a fourth indication information from the second MLD, where the fourth indication information is used to indicate that no bufferable data corresponding to any second data type is buffered in the second MLD.

[0331]

[0353] The communication device 100 is a first MLD in the embodiment shown in FIG. 6a.

[0332]

[0354] The communication unit 1001 is configured to receive bufferable data corresponding to a third data type from a second MLD, where the bufferable data includes fifth indication information, and the fifth indication information is used to indicate whether the bufferable data corresponding to the third data type is buffered in the second MLD.

[0333]

[0355] The processing unit 1002 is configured to determine, based on the fifth indication, whether bufferable data corresponding to the third data type is buffered in the second MLD.

[0334]

[0356] In an implementation, the communication device 100 has a plurality of stations. The processing unit 1002 may be further configured to determine an operation state of a station corresponding to a second link among the plurality of stations based on whether bufferable data corresponding to a third data type is buffered in a second MLD, where the third data type is mapped to the second link and the operation state is an active state or a doze state.

[0335]

[0357] In implementations, the processing unit 1002 may be further configured to determine whether a data type other than the third data type is mapped to the second link.

[0336]

[0358] When the processing unit 1002 is configured to determine an operation state of a station corresponding to a second link among the plurality of stations based on whether bufferable data corresponding to a third data type is buffered in the second MLD, the processing unit 1002 is specifically configured to determine an operation state of a station corresponding to a second link among the plurality of stations based on whether bufferable data corresponding to the third data type is buffered in the second MLD and whether a data type other than the third data type is mapped to the second link.

[0337]

[0359] In an implementation, the fifth indication indicates that no bufferable data corresponding to the third data type is buffered in the second MLD. The bufferable data corresponding to the third data type received by the communication unit 1001 from the second MLD further includes sixth indication, which is used to indicate whether or not at least one bufferable data corresponding to a fourth data type is buffered in the second MLD, and the fourth data type is any data type other than the third data type among the data types supported by the communication device 100.

[0338]

[0360] In an implementation, the fourth data type may have a higher priority than the third data type.

[0339]

[0361] The communication device 100 is a first MLD of the embodiment shown in FIG.

[0340]

[0362] The communication unit 1001 is configured to receive seventh indication information from the second MLD, the seventh indication information being used to indicate that bufferable data corresponding to a fifth data type is not buffered in the second MLD, and the fifth data type is 100 The data type can be one of the data types supported by .

[0341]

[0363] The processing unit 1002 is configured to determine, based on the seventh indication, that the bufferable data corresponding to the fifth data type is not buffered in the second MLD.

[0342]

[0364] In an implementation, the communication device 100 has a plurality of stations. The processing unit 1002 is further configured to determine an operation state of a station corresponding to a third link among the plurality of stations based on the bufferable data corresponding to the fifth data type not being buffered in the second MLD, where the fifth data type is mapped to the third link and the operation state is an active state or a doze state.

[0343]

[0365] The communication device 100 is a first MLD in the embodiment shown in FIG.

[0344]

[0366] The communication unit 1001 is configured to receive an eighth indication information from the second MLD via the fourth link, where the eighth indication information is used to indicate that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD.

[0345]

[0367] The processing unit 1002 is configured to determine, based on the eighth indication information, that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD.

[0346]

[0368] In an implementation, the communication device 100 has a plurality of stations. The processing unit 1002 is further configured to determine an operation state of a station corresponding to the fourth link among the plurality of stations based on the bufferable data corresponding to any data type mapped to the fourth link not being buffered in the second MLD, where the operation state is an active state or a doze state. 。

[0347] [

[0370] The communication device 100 is a first MLD in the embodiment shown in FIG.

[0348]

[0371] The communication unit 1001 is configured to receive ninth indication information from the second MLD, the ninth indication information being used to indicate a buffer status of bufferable data corresponding to at least one data type supported by the communication device and located in the second MLD.

[0349]

[0372] The processing unit 1002 is configured to determine, based on the ninth indication, a buffer status of bufferable data corresponding to the at least one data type and located in the second MLD.

[0350]

[0373] In an implementation, the communication device 100 has multiple stations. The processing unit 1002 is Supports at least one data type and To the second MLD be The communication device is further configured to determine an operational state of at least one station of the plurality of stations based on a buffer status of the bufferable data, where the operational state is an active state or a doze state.

[0351]

[0374] The communication device 100 is a first MLD of the embodiment shown in FIG. 9a.

[0352]

[0375] The communication unit 1001 is configured to receive tenth indication information from the second MLD, where the tenth indication information is used to indicate a buffer status of bufferable data in the second MLD corresponding to at least one data type mapped to at least one link corresponding to the communication device.

[0353]

[0376] The processing unit 1002 is configured to determine, based on the tenth indication, a buffer status of bufferable data corresponding to the at least one data type mapped to the at least one link and located in the second MLD.

[0354]

[0377] In an implementation, the communication device 100 has a plurality of stations. The processing unit 1002 is further configured to determine an operation state of at least one of the plurality of stations based on a buffer status of bufferable data in the second MLD corresponding to at least one data type mapped to the at least one link, where the operation state is an active state or a doze state.

[0355]

[0378] 11 is a schematic diagram of the structure of another communication device 110 according to an embodiment of the present application. The communication device 110 may be a first MLD, or may be a chip, a chip system, a processor, etc., that supports the first MLD in implementing the aforementioned method. The device may be configured to implement the method described in the aforementioned method embodiment. For details, please refer to the description of the aforementioned method embodiment.

[0356]

[0379] The communication device 110 may include one or more processors 1101. The processor 1101 may be a general-purpose processor, a special-purpose processor, etc. For example, the processor 1101 may be a baseband processor or a central processing unit. The baseband processor may be configured to process communication protocols and communication data, and the central processing unit may be configured to control a communication device (e.g., a base station, a baseband chip, a terminal, a terminal chip, a DU, or a CU) to execute a computer program and process data of the computer program.

[0357]

[0380] The communication device 110 may further include a transceiver 1105. The transceiver 1105 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, etc., and is configured to implement a transceiver function. The transceiver 1105 may include a receiver and a transmitter. The receiver may be referred to as a receiving device, a receiving circuit, etc., and is configured to implement a receiving function. The transmitter may be referred to as a transmitting device, a transmitting circuit, etc., and is configured to implement a transmitting function. Optionally, the communication device 110 may further include an antenna 1106.

[0358]

[0381] Optionally, the communication device 110 may include one or more memories 1102, which may store computer programs 1104. The computer programs may be executed in the communication device 110, so that the communication device 110 executes the methods described in the above method embodiments. Optionally, the memory 1102 may further store data. The communication device 110 and the memory 1102 may be located separately or may be integrated.

[0359]

[0382] The processor 1101 is configured to execute step S203 of FIG. 2, step S304 of FIG. 3a, step S403 of FIG. 4a, steps S504, S505, and S509 of FIG. 5A and FIG. 5B, step S603 of FIG. 6a, step S703 of FIG. 7, step S803 of FIG. 8, and step S903 of FIG. 9a.

[0360]

[0383] The transceiver 1105 is configured to, in the embodiment shown in FIG. 2, receive indication information from the second MLD; in the embodiment shown in FIG. 3a, receive first indication information from the second MLD; in the embodiment shown in FIG. 4a, receive bufferable data from the second MLD; in the embodiment shown in FIG. 5A and FIG. 5B, receive first indication information and bufferable data from the second MLD and transmit link status indication information to the second MLD; in the embodiment shown in FIG. 6a, receive bufferable data corresponding to a third data type from the second MLD; in the embodiment shown in FIG. 7, receive seventh indication information from the second MLD; in the embodiment shown in FIG. 8, receive eighth indication information from the second MLD; and in the embodiment shown in FIG. 9a, receive tenth indication information from the second MLD.

[0361]

[0384] In an implementation, the processor 1101 may include a transceiver configured to perform receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, the interface, or the interface circuit configured to perform the transmitting function and the transceiver circuit, the interface, or the interface circuit configured to perform the receiving function may be separate or integrated. The transceiver circuit, the interface, or the interface circuit may be configured to read and write code or data. Alternatively, the transceiver circuit, the interface, or the interface circuit may be configured to transmit or forward a signal.

[0362]

[0385] In an implementation, the processor 1101 may store a computer program 1103, which is executed on the processor 1101, so that the communication device 110 executes the method described in the above method embodiments. The computer program 1103 may be fixed in the processor 1101, in which case the processor 1101 may be implemented by hardware.

[0363]

[0386] In implementations, the communication device 110 may include circuitry that may implement the functions of transmitting, receiving, or communicating in the above-described method embodiments. The processors and transceivers described herein may be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed signal ICs, application specific integrated circuits (ASICs), or printed circuit boards (PCBs), electronic devices, etc. Alternatively, the processors and transceivers may be implemented in a variety of IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide semiconductor (n-type), n-type MOS, ... -type Metal-oxide-semiconductor, NMOS, p-type metal oxide semiconductor (p -type The transistors may be fabricated using metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), and gallium arsenide (GaAs).

[0364]

[0387] The communication device described in the above embodiment may be a first MLD. However, the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited by FIG. 11. The communication device may be an independent device or a part of a larger device. For example, the communication device may be: (1) An independent integrated circuit IC, chip, chip system, or subsystem; (2) A set including one or more integrated circuits. Optionally, the set of integrated circuits may further include a storage component configured to store data and computer programs; (3) ASIC, e.g., modem; (4) Modules that can be embedded into other devices; (5) Receivers, terminals, intelligent terminals, cellular telephones, wireless devices, mobile terminals, mobile units, in-vehicle devices, network devices, cloud devices, artificial intelligence devices, etc.; or (6)Others, etc.

[0365]

[0388] For the case where the communication device may be a chip or a chip system, please refer to the schematic diagram of the structure of the chip shown in Figure 12. The chip shown in Figure 12 includes a processor 1201 and an interface 1202. There may be more than one processor 1201 and there may be more than one interface 1202.

[0366]

[0389] In the embodiment shown in FIG. 3a or FIGS. 5A and 5B, if the chip is configured to implement the functionality of the first MLD: The interface 1202 is configured to receive a first indication from a second MLD, where the first indication is used to indicate a buffer status of bufferable data that corresponds to an association identifier of the first MLD and is in the second MLD; and The processor 1201 is configured to determine a buffer status of bufferable data corresponding to at least one data type and located in the second MLD based on the first indication information, a correspondence between an association identifier of the first MLD and data types supported by the first MLD.

[0367]

[0390] In an implementation, the first MLD has a plurality of stations, and the processor 1201 may be further configured to determine an operating state of at least one of the plurality of stations based on a buffer status of bufferable data corresponding to at least one data type and in the second MLD, the operating state being an active state or a doze state.

[0368]

[0391] In an implementation, the interface 1202 is further configured to receive second indication information from the second MLD, where the second indication information is used to determine a correspondence between the association identifier and the data type.

[0369]

[0392] In an implementation, the second indication indicates at least one association identifier, the at least one association identifier corresponding to the at least one data type.

[0370]

[0393] In an implementation, the first MLD may support a plurality of data types. The second indication indicates a first association identifier, the first association identifier corresponding to a first data type in the plurality of data types. The processor 1201 is further configured to determine an association identifier corresponding to a data type other than the first data type in the plurality of data types based on the first association identifier corresponding to the first data type.

[0371]

[0394] In the embodiment shown in FIG. 4a or FIGS. 5A and 5B, if the chip is configured to implement the functionality of the first MLD: The interface 1202 is configured to receive bufferable data from the second MLD via the first link, where the bufferable data includes third indication information, the third indication information is used to indicate whether the bufferable data corresponding to at least one second data type is buffered in the second MLD, the second data type being any data type mapped to the first link; and The processor 1201 is configured to determine, based on the third indication, whether bufferable data corresponding to the at least one second data type is buffered in the second MLD.

[0372]

[0395] In an implementation, the first MLD has a plurality of stations. The processor 1201 is further configured to determine an operation state of a station corresponding to the first link among the plurality of stations based on whether bufferable data corresponding to at least one second data type is buffered in the second MLD, the operation state being an active state or a doze state.

[0373]

[0396] In an implementation, when the processor 1201 is configured to determine an operational state of a station corresponding to a first link among the plurality of stations based on whether bufferable data corresponding to at least one second data type is buffered in the second MLD, the processor 1201 is specifically configured to: determine the operational state of the station corresponding to the first link among the plurality of stations as an active state if bufferable data corresponding to at least one second data type is buffered in the second MLD; or determine the operational state of the station corresponding to the first link among the plurality of stations as an active state or a doze state if no bufferable data corresponding to any second data type is buffered in the second MLD.

[0374]

[0397] In an implementation, the third indication indicates that at least one bufferable data corresponding to the second data type is buffered in the second MLD. The interface 1202 is further configured to receive a fourth indication from the second MLD, the fourth indication being used to indicate that no bufferable data corresponding to any second data type is buffered in the second MLD.

[0375]

[0398] In the embodiment shown in FIG. 6a, if the chip is configured to implement the functionality of the first MLD: the interface 1202 is configured to receive bufferable data corresponding to a third data type from the second MLD, the bufferable data including fifth indication information, the fifth indication information being used to indicate whether the bufferable data corresponding to the third data type is buffered in the second MLD; and The processor 1201 is configured to determine, based on the fifth indication, whether bufferable data corresponding to the third data type is buffered in the second MLD.

[0376]

[0399] In an implementation, the first MLD has a plurality of stations. The processor 1201 may be further configured to determine an operational state of a station corresponding to a second link among the plurality of stations based on whether bufferable data corresponding to a third data type is buffered in the second MLD, where the third data type is mapped to the second link and the operational state is an active state or a doze state.

[0377]

[0400] In the implementation, the processor 1201 may be further configured to determine whether a data type other than the third data type is mapped to the second link. When the processor 1201 is configured to determine an operational state of a station corresponding to the second link among the plurality of stations based on whether bufferable data corresponding to the third data type is buffered in the second MLD, the processor 1201 is specifically configured to determine an operational state of a station corresponding to the second link among the plurality of stations based on whether bufferable data corresponding to the third data type is buffered in the second MLD and whether a data type other than the third data type is mapped to the second link.

[0378]

[0401] In an implementation, the fifth indication indicates that the bufferable data corresponding to the third data type is not buffered in the second MLD. The bufferable data corresponding to the third data type received by the interface 1202 from the second MLD further includes sixth indication, where the sixth indication is used to indicate whether or not at least one bufferable data corresponding to a fourth data type is buffered in the second MLD, and the fourth data type is any data type other than the third data type among the data types supported by the first MLD.

[0379]

[0402] In an implementation, the fourth data type may have a higher priority than the third data type.

[0380]

[0403] In the embodiment shown in FIG. 7, when the chip is configured to implement the functionality of the first MLD: the interface 1202 is configured to receive a seventh indication from the second MLD, the seventh indication being used to indicate that bufferable data corresponding to a fifth data type is not buffered in the second MLD, the fifth data type being any of the data types supported by the first MLD; and The processor 1201 is configured to determine, based on the seventh indication information, that the bufferable data corresponding to the fifth data type is not buffered in the second MLD.

[0381]

[0404] In an implementation, the first MLD has a plurality of stations. The processor 1201 is further configured to determine an operation state of a station among the plurality of stations corresponding to a third link based on the bufferable data corresponding to the fifth data type not being buffered in the second MLD, where the fifth data type is mapped to the third link and the operation state is an active state or a doze state.

[0382]

[0405] In the embodiment shown in FIG. 8, when the chip is configured to implement the functionality of the first MLD: the interface 1202 is configured to receive an eighth indication from the second MLD via the fourth link, the eighth indication being used to indicate that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD; and The processor 1201 is configured to determine, based on the eighth indication information, that bufferable data corresponding to any data type mapped to the fourth link is not buffered in the second MLD.

[0383]

[0406] In an implementation, the first MLD has a plurality of stations. The processor 1201 is further configured to determine an operation state of a station corresponding to the fourth link among the plurality of stations based on bufferable data corresponding to any data type mapped to the fourth link not being buffered in the second MLD, where the operation state is an active state or a doze state.

[0384]

[0407] In the embodiment shown in FIG. 2, when the chip is configured to implement the functionality of the first MLD: the interface 1202 is configured to receive a ninth indication from the second MLD, the ninth indication being used to indicate a buffer status of bufferable data corresponding to at least one data type supported by the first MLD and present in the second MLD; and The processor 1201 is configured to determine, based on the ninth indication, a buffer status of bufferable data corresponding to the at least one data type and located in the second MLD.

[0385]

[0408] In an implementation, the processor 1201 Supports at least one data type andTo the second MLD be The communication device is further configured to determine an operational state of at least one station of the plurality of stations based on a buffer status of the bufferable data, where the operational state is an active state or a doze state.

[0386]

[0409] In the embodiment shown in FIG. 9a, when the chip is configured to implement the functionality of the first MLD: the interface 1202 is configured to receive tenth indication information from the second MLD, the tenth indication information being used to indicate a buffer status of bufferable data in the second MLD, the bufferable data corresponding to at least one data type mapped to at least one link corresponding to the first MLD; and The processor 1201 is configured to determine, based on the tenth indication information, a buffer status of bufferable data corresponding to at least one data type mapped to the at least one link and in the second MLD.

[0387]

[0410] In an implementation, the first MLD has a plurality of stations. The processor 1201 is further configured to determine at least one status of the plurality of statuses based on a buffer status of bufferable data in the second MLD corresponding to at least one data type mapped to the at least one link, where the operating state is an active state or a doze state.

[0388]

[0411] Optionally, the chip further comprises a memory 1203, the memory 1203 being adapted to store necessary computer programs and data.

[0389]

[0412] 13 is a schematic diagram of the structure of yet another communication device 130 according to an embodiment of the present application. The communication device 130 shown in FIG. 13 may include a communication unit 1301, a processing unit 1302, and a storage unit 1303. The communication unit 1301 may include a transmitting unit and / or a receiving unit. The transmitting unit is configured to realize a transmitting function, and the receiving unit is configured to realize a receiving function, and the communication unit 1301 can realize a transmitting function and / or a receiving function. Also, the communication unit may be described as a transceiver unit.

[0390]

[0413] The communication device 130 may be a second MLD, or may be a device within the second MLD, or may be a device capable of being used with the second MLD. When the communication device 130 is a second MLD, the communication device 130 may be a device within the second MLD, or may be a device capable of being used with the second MLD. Any of In the illustrated embodiment, the communication device 130 may be a second MLD.

[0391]

[0414] The communication device 130 is the second MLD in the embodiment shown in FIG. 3a or FIGS. 5A and 5B.

[0392]

[0415] The processing unit 1302 is configured to determine a buffer status of bufferable data corresponding to at least one data type supported by the first MLD and residing in the storage unit 1303; and determine a buffer status of bufferable data corresponding to the association identifier and residing in the storage unit 1303 based on the buffer status of the bufferable data corresponding to the at least one data type and residing in the storage unit 1303, and a correspondence between the association identifier of the first MLD and the supported data types.

[0393]

[0416] The communication unit 1301 is configured to send first indication information to the first MLD, where the first indication information corresponds to an association identifier of the first MLD and is used to indicate a buffer status of bufferable data in the memory unit 1303.

[0394]

[0417] In the implementation, the communication unit 1301 is further configured to send second indication information to the first MLD, where the second indication information is used to determine a correspondence between an association identifier of the first MLD and a data type supported by the first MLD.

[0395]

[0418] In an implementation, the second indication indicates at least one association identifier, the at least one association identifier corresponding to the at least one data type.

[0396]

[0419] In an implementation, the first MLD supports a plurality of data types, and the second indication indicates a first association identifier, the first association identifier corresponding to a first data type in the plurality of data types.

[0397]

[0420] The communication device 130 is the second MLD in the embodiment shown in FIG. 4a or FIGS. 5A and 5B.

[0398]

[0421] The processing unit 1302 is configured to determine whether bufferable data corresponding to at least one second data type is buffered in the storage unit 1303, the second data type being any data type mapped to the first link.

[0399]

[0422] The communication unit 1301 is configured to transmit bufferable data to the first MLD via a first link, the bufferable data including third indication information, the third indication information being used to indicate whether the bufferable data corresponding to at least one second data type is buffered in the storage unit 1303.

[0400]

[0423] In an implementation, the third indication information indicates that at least one bufferable data corresponding to the second data type is buffered in the storage unit 1303. The communication unit 1301 is further configured to send fourth indication information to the first MLD, where the fourth indication information is used to indicate that no bufferable data corresponding to any second data type is buffered in the storage unit 1303.

[0401]

[0424] The communication device 130 is a second MLD in the embodiment shown in FIG. 6a.

[0402]

[0425] The processing unit 1302 is configured to determine whether bufferable data corresponding to a third data type is buffered in the storage unit 1303 .

[0403]

[0426] The communication unit 1301 is configured to send bufferable data corresponding to a third data type to the first MLD, the bufferable data including fifth indication information, the fifth indication information being used to indicate whether the bufferable data corresponding to the third data type is buffered in the storage unit 1303.

[0404]

[0427] In an implementation, the fifth indication information indicates that no bufferable data corresponding to the third data type is buffered in the storage unit 1303. The bufferable data corresponding to the third data type transmitted from the communication unit 1301 to the first MLD further includes sixth indication information, which is used to indicate whether or not at least one bufferable data corresponding to a fourth data type is buffered in the storage unit 1303, and the fourth data type is any data type other than the third data type among the data types supported by the first MLD.

[0405]

[0428] In an implementation, the fourth data type may have a higher priority than the third data type.

[0406]

[0429] The communication device 130 is a second MLD in the embodiment shown in FIG.

[0407]

[0430] The processing unit 1302 is configured to determine that bufferable data corresponding to a fifth data type is not buffered in the storage unit 1303, the fifth data type being any of the data types supported by the first MLD.

[0408]

[0431] The communication unit 1301 is configured to send seventh indication information to the first MLD, where the seventh indication information is used to indicate that the bufferable data corresponding to the fifth data type is not buffered in the storage unit 1303.

[0409]

[0432] The communication device 130 is a second MLD in the embodiment shown in FIG.

[0410]

[0433] The processing unit 1302 is configured to determine that no bufferable data corresponding to any data type mapped to the fourth link is buffered in the storage unit 1303.

[0411]

[0434] The communication unit 1301 is configured to send eighth indication information to the first MLD via the fourth link, and the eighth indication information is used to indicate that no bufferable data corresponding to any data type mapped to the fourth link is buffered in the storage unit 1303.

[0412]

[0435] The communication device 130 is a second MLD in the embodiment shown in FIG.

[0413]

[0436] The processing unit 1302 is configured to determine a buffer status of bufferable data that corresponds to at least one data type supported by the first MLD and that is in the storage unit 1303 .

[0414]

[0437] The communication unit 1301 is configured to send ninth indication information to the first MLD, where the ninth indication information is used to indicate a buffer status of bufferable data corresponding to at least one data type supported by the first MLD and residing in the memory unit 1303.

[0415]

[0438] The communication device 130 is a second MLD in the embodiment shown in FIG. 9a.

[0416]

[0439] The processing unit 1302 is configured to determine a buffer status of bufferable data in the storage unit 1303, the buffered data corresponding to at least one data type mapped to at least one link corresponding to the first MLD.

[0417]

[0440] The communication unit 1301 is configured to send tenth indication information to the first MLD, where the tenth indication information is used to indicate a buffer status of bufferable data corresponding to at least one data type mapped to at least one link corresponding to the first MLD and residing in the memory unit 1303.

[0418]

[0441] 14 is a schematic diagram of the structure of yet another communication device 140 according to an embodiment of the present application. The communication device 140 may be a second MLD, or may be a chip, a chip system, a processor, etc., that supports the second MLD in implementing the aforementioned method. The device may be configured to implement the method described in the aforementioned method embodiment. For details, please refer to the description of the aforementioned method embodiment.

[0419]

[0442] The communication device 140 may include one or more processors 1401. The processor 1401 may be a general-purpose processor, a special-purpose processor, etc. For example, the processor 1401 may be a baseband processor or a central processing unit. The baseband processor may be configured to process communication protocols and communication data, and the central processing unit may be configured to control a communication device (e.g., a base station, a baseband chip, a terminal, a terminal chip, a DU, or a CU) to execute a computer program and process data of the computer program.

[0420]

[0443] The communication device 140 may further include a transceiver 1405. The transceiver 1405 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, etc., and is configured to implement a transceiver function. The transceiver 1405 may include a receiver and a transmitter. The receiver may be referred to as a receiving device, a receiving circuit, etc., and is configured to implement a receiving function. The transmitter may be referred to as a transmitting device, a transmitting circuit, etc., and is configured to implement a transmitting function. Optionally, the communication device 140 may further include an antenna 1406.

[0421]

[0444] The communication device 140 may further include one or more memories 1402, which may store computer programs 1404. The computer programs may be executed in the communication device 140, such that the communication device 140 performs the methods described in the above method embodiments. Optionally, the memory 1402 may further store data. The communication device 140 and the memory 1402 may be located separately or may be integrated.

[0422]

[0445] The processor 1401 is configured to execute step S201 of FIG. 2, step S301 and step S302 of FIG. 3a, step S401 of FIG. 4a, step S501, step S502, and step S507 of FIG. 5A and FIG. 5B, step S601 of FIG. 6a, step S701 of FIG. 7, step S801 of FIG. 8, and step S901 of FIG. 9a.

[0423]

[0446] The processor 1405 is configured to execute step S202 of FIG. 2, step S303 of FIG. 3a, step S402 of FIG. 4a, step S503 and step S508 of FIG. 5A and FIG. 5B, step S602 of FIG. 6a, step S702 of FIG. 7, step S802 of FIG. 8, and step S902 of FIG. 9a.

[0424]

[0447] In an implementation, the processor 1401 may include a transceiver configured to perform receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, the interface, or the interface circuit configured to perform the transmitting function and the transceiver circuit, the interface, or the interface circuit configured to perform the receiving function may be separate or integrated. The transceiver circuit, the interface, or the interface circuit may be configured to read and write code or data. Alternatively, the transceiver circuit, the interface, or the interface circuit may be configured to transmit or forward a signal.

[0425]

[0448] In the implementation, the processor 1401 can store a computer program 1403, which runs on the processor 1101, so that the communication device 140 executes the method described in the above method embodiment. The computer program 1403 may be fixed in the processor 1401, in which case the processor 1401 may be implemented by hardware.

[0449] In implementations, the communication device 140 may include circuits that may implement the functions of transmitting, receiving, or communicating in the above-described method embodiments. The processors and transceivers described herein may be implemented in an integrated circuit (IC), analog IC, radio frequency integrated circuit (RFIC), mixed signal IC, application specific integrated circuit (ASIC), or printed circuit board (PCB), electronic device, etc. Alternatively, the processors and transceivers may be fabricated using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide semiconductor (NMOS), p-type metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), and gallium arsenide (GaAs).

[0426]

[0450] The communication device described in the above embodiment may be a second MLD. However, the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited by FIG. 14. The communication device may be an independent device or part of a larger device. For example, the communication device may be: (1) An independent integrated circuit IC, chip, chip system, or subsystem; (2) A set including one or more integrated circuits. Optionally, the set of integrated circuits may further include a storage component configured to store data and computer programs; (3) ASIC, e.g., modem; (4) Modules that can be embedded into other devices; (5) Receivers, terminals, intelligent terminals, cellular telephones, wireless devices, mobile terminals, mobile units, in-vehicle devices, network devices, cloud devices, artificial intelligence devices, etc.; or (6)Others, etc.

[0427]

[0451] For the case where the communication device may be a chip or a chip system, please refer to the schematic diagram of the structure of the chip shown in Figure 15. The chip shown in Figure 15 includes a processor 1501, an interface 1502, and a memory 1503. There may be one or more processors 1501, there may be multiple interfaces 1502, and there may be one or more memories 1503. The memory 1503 is configured to store bufferable data, as well as necessary computer programs and data.

[0428]

[0452] If the chip is configured to implement the functionality of the second MLD in the embodiment shown in FIG. 3a or FIGS. 5A and 5B: The processor 1501 is configured to determine a buffer status of bufferable data corresponding to at least one data type supported by the first MLD and residing in the memory 1503; and determine a buffer status of bufferable data corresponding to an association identifier and residing in the memory 1503 based on the buffer status of the bufferable data corresponding to the at least one data type and residing in the memory 1503 and a correspondence between an association identifier of the first MLD and the supported data types; and The interface 1502 is configured to transmit first indication information to the first MLD, the first indication information being used to indicate a buffer status of bufferable data corresponding to an association identifier of the first MLD and residing in the memory 1503.

[0429]

[0453] In an implementation, the interface 1502 is further configured to send second instruction information to the first MLD, where the second instruction information is used to determine a correspondence between an association identifier of the first MLD and a data type supported by the first MLD.

[0430]

[0454] In an implementation, the second indication indicates at least one association identifier, the at least one association identifier corresponding to the at least one data type.

[0431]

[0455] In an implementation, the first MLD supports a plurality of data types, and the second indication indicates a first association identifier, the first association identifier corresponding to a first data type of the plurality of data types.

[0432]

[0456] If the chip is configured to implement the functionality of the second MLD in the embodiment shown in FIG. 4a or FIGS. 5A and 5B: The processor 1501 is configured to determine whether bufferable data corresponding to at least one second data type is buffered in the memory 1503, where the second data type is any data type mapped to the first link; and The interface 1502 is configured to transmit the bufferable data to the first MLD via the first link, the bufferable data including third indication information, the third indication information being used to indicate whether the bufferable data corresponding to the at least one second data type is buffered in the memory 1503.

[0433]

[0457] In an implementation, the third indication information indicates that at least one bufferable data corresponding to the second data type is buffered in the memory 1503. Further, the interface 1502 is configured to send a fourth indication information to the first MLD, where the fourth indication information is used to indicate that no bufferable data corresponding to the second data type is buffered in the memory 1503.

[0434]

[0458] When the chip is configured to implement the functionality of the second MLD in the embodiment shown in FIG. 6a: The processor 1501 is configured to determine whether bufferable data corresponding to a third data type is buffered in the memory 1503; and The interface 1502 is configured to transmit to the first MLD bufferable data corresponding to a third data type, the bufferable data including fifth indication information, the fifth indication information being used to indicate whether the bufferable data corresponding to the third data type is buffered in the memory 1503.

[0435]

[0459] In an implementation, the fifth indication information indicates that the bufferable data corresponding to the third data type is not buffered in the memory 1503. The bufferable data corresponding to the third data type sent by the interface 1502 to the first MLD further includes sixth indication information, where the sixth indication information is used to indicate whether or not the bufferable data corresponding to at least one fourth data type is buffered in the memory 1503, and the fourth data type is any data type other than the third data type among the data types supported by the first MLD.

[0436]

[0460] In an implementation, the fourth data type may have a higher priority than the third data type.

[0437]

[0461] When the chip is configured to implement the functionality of the second MLD in the embodiment shown in FIG. 7: The processor 1501 is configured to determine that bufferable data corresponding to a fifth data type is not buffered in the memory 1503, the fifth data type being any of the data types supported by the first MLD; and The interface 1502 is configured to send seventh indication information to the first MLD, where the seventh indication information is used to indicate that the bufferable data corresponding to the fifth data type is not buffered in the memory 1503.

[0438]

[0462] When the chip is configured to implement the functionality of the second MLD in the embodiment shown in FIG. 8: The processor 1501 is configured to determine that no bufferable data corresponding to any data type mapped to the fourth link is buffered in the memory 1503; and The interface 1502 is configured to transmit an eighth indication to the first MLD via the fourth link, the eighth indication being used to indicate that no bufferable data corresponding to any data type mapped to the fourth link is buffered in the memory 1503.

[0439]

[0463] When the chip is configured to implement the functionality of the second MLD in the embodiment shown in FIG. 2: The processor 1501 is configured to determine a buffer status of bufferable data that corresponds to at least one data type supported by the first MLD and that is in the memory 1503; and The interface 1502 is configured to transmit ninth indication information to the first MLD, the ninth indication information being used to indicate a buffer status of bufferable data corresponding to at least one data type supported by the first MLD and residing in the memory 1503.

[0440]

[0464] When the chip is configured to implement the functionality of the second MLD in the embodiment shown in FIG. 9a: The processor 1501 is configured to determine a buffer status of bufferable data in the memory 1503, the buffered data corresponding to at least one data type mapped to at least one link corresponding to the first MLD; and The interface 1502 is configured to transmit tenth indication information to the first MLD, the tenth indication information being used to indicate a buffer status of bufferable data corresponding to at least one data type mapped to at least one link corresponding to the first MLD and residing in the memory 1503.

[0441]

[0465] Those skilled in the art can further understand that the various illustrative logical blocks and steps enumerated in the embodiments of the present application may be realized by electronic hardware, computer software, or a combination thereof. Whether a function is realized by hardware or software depends on the design requirements of a specific application and the overall system. Those skilled in the art can 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 embodiments of the present application.

[0442]

[0466] The present application further provides a computer-readable storage medium, which stores a computer program, and when the computer-readable storage medium is executed by a computer, the functions of any one of the above-mentioned method embodiments are implemented.

[0443]

[0467] The present application further provides a computer program product, which, when implemented by a computer, performs the functions of any one of the above method embodiments.

[0444]

[0468] All or part of the above-mentioned embodiments may be implemented by software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer programs are loaded into a computer and executed, the procedures or functions according to the embodiments of the present application occur in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer program may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wired (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave) methods. A computer readable storage medium may be any available medium accessible by a computer, or a data storage device integrating one or more available media, such as a server or a data center. The available media may be magnetic media (e.g., floppy disk, hard disk, or magnetic tape), optical media (e.g., digital video disc (DVD)), semiconductor media (e.g., solid state disk (SSD)), etc.

[0445]

[0469] Those skilled in the art can understand that the various numerals such as first and second in the present application are merely distinguished for the convenience of description, and are not used to limit the scope of the embodiments of the present application or to indicate the order.

[0446]

[0470] "At least one" in this application can alternatively be described as one or more, and "multiple" means two, three, four or more. This is not limited in this application. In the embodiments of this application, "first", "second", "third", "A", "B", "C", "D", etc. are used to distinguish the technical features described by them. No chronological or dimensional order is assumed between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0447]

[0471] The correspondences shown in the tables in this application may be set or predefined. The values ​​of the information in the tables are merely illustrative and other values ​​may be set. This is not a limitation of this application. When the correspondences between the information and each parameter are set, it is not necessary that all the correspondences shown in the tables are set. For example, in the tables in this application, the correspondences shown in some rows may alternatively not be set. In another example, appropriate modifications and adjustments, such as division and combination, may be performed based on the above tables. The names of the parameters shown in the titles of the above tables may alternatively be other names that can be understood by the communication device, and the values ​​and representations of the parameters may alternatively be other values ​​and representations that can be understood by the communication device. In implementing the above tables, other data structures such as arrays, queues, containers, stacks, strip tables, pointers, linked lists, trees, graphs, structures, classes, piles, or hash tables may alternatively be used.

[0448]

[0472] "Predefined" in this application may be understood as "defined", "predefined", "stored", "prestored", "prenegotiated", "preconfigured", "bundled", or "preprocessed".

[0449]

[0473] Those skilled in the art can realize that, with respect to the units and algorithm steps described in the examples of the embodiments disclosed herein, the embodiments of the present application may be realized by electronic hardware or a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the design constraints of a specific application and technical solution. Those skilled in the art can use various methods to implement the described functions for each specific application, but the implementation should not be considered to go beyond the scope of the present application.

[0450]

[0474] For convenience and conciseness of description, those skilled in the art can clearly understand that for the detailed operation processes of the above-mentioned systems, devices, and units, please refer to the corresponding processes in the above-mentioned method embodiments, and the details will not be described again here.

[0451]

[0475] The above description is merely a specific implementation of the present application, and is not intended to limit the scope of protection of the present application. Any modifications or replacements that a person skilled in the art can readily understand within the technical scope disclosed in the present application shall be included in the scope of protection of the present application. Therefore, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. 1. A method for determining a data buffer status, the method comprising: A second multi-link device (MLD) determines whether bufferable data corresponding to the management frame is buffered in the second MLD; and a step of a second MLD transmitting bufferable data corresponding to the management frame to a first MLD via a first link, the bufferable data including third indication information, the third indication information being used to indicate whether the bufferable data corresponding to the management frame is buffered in the second MLD; The method includes:

2. 2. The method of claim 1, wherein the third indication information is also used to indicate whether bufferable data corresponding to the at least one second data type is buffered in the second MLD, the second data type being any data type mapped to the first link.

3. 3. The method according to claim 1 or 2, wherein the third indication is a More Data subfield; the More Data subfield has a value of 1, indicating that the management frame or bufferable data corresponding to the at least one second data type is buffered in the second MLD; or The More Data subfield has a value of 0, indicating that no management frames or the bufferable data corresponding to any second data type are buffered in the second MLD.

4. 10. The method of claim 1, further comprising: the second MLD receiving a Power Saving Poll (PS-Poll) frame from the first MLD; The method includes:

5. 5. The method according to any one of claims 1 to 4, further comprising: A method comprising the step of transmitting fourth indication information to the first MLD, the fourth indication information being used to indicate that no management frames or bufferable data corresponding to any second data type are buffered in the second MLD.

6. 6. The method of claim 5, wherein the fourth indication information is a Quality of Service Null (QoS Null) frame, the QoS Null frame being a data frame carrying no payload, and a value of a More Data subfield in the QoS Null frame being 0.

7. a second multi-link device (MLD) including a transceiver and a processor, The processor is configured to determine whether bufferable data corresponding to a management frame is buffered in the second MLD; and a second MLD, wherein the transceiver is configured to transmit bufferable data corresponding to the management frame via a first link to a first MLD, the bufferable data including third indication information, the third indication information being used to indicate whether the bufferable data corresponding to the management frame is buffered in the second MLD.

8. In the second MLD of claim 7, the third indication information is also used to indicate whether bufferable data corresponding to at least one second data type is buffered in the second MLD, the second data type being any data type mapped to the first link.

9. In the second MLD according to claim 7 or 8, the third indication information is a More Data subfield; the More Data subfield has a value of 1, indicating that the management frame or bufferable data corresponding to the at least one second data type is buffered in the second MLD; or A second MLD, wherein the More Data subfield has a value of 0, indicating that no management frames or the bufferable data corresponding to any second data type are buffered in the second MLD.

10. 8. The second MLD of claim 7, wherein the transceiver is further configured to receive a Power Saving Polling (PS-Poll) frame from the first MLD.

11. In the second MLD described in any one of claims 7 to 10, the transceiver is further configured to transmit fourth indication information to the first MLD, the fourth indication information being used to indicate that none of the bufferable data corresponding to any of the second data types or the management frames is buffered in the second MLD.

12. 12. The second MLD according to claim 11, wherein the fourth indication information is a quality of service null value (QoS Null) frame, the QoS Null frame being a data frame carrying no payload, and a value of a More Data subfield in the QoS Null frame being 0.

Images