Method and apparatus for determining data cache condition

Abstract

The embodiment of the application discloses a method and device for determining data cache condition, the method comprises the following steps: a first multi-link device (MLD) receives first indication information from a second MLD; according to 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, the cache condition of the cache data corresponding to at least one data type in the second MLD is determined; wherein the first indication information is used to indicate the cache condition of the cache data corresponding to the association identifier of the first MLD in the second MLD. Through the implementation of the embodiment of the application, the data cache condition in the data type dimension can be determined. The embodiment of the application can be applied to a wireless local area network system supporting IEEE 802.11 next-generation WiFi EHT protocol, that is, 802.11be and other 802.11 protocols.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for determining data buffering conditions. Background Technology

[0002] Improving throughput is a continuous goal in the evolution of cellular networks and wireless local area networks (WLANs). To achieve extremely high throughput, the next-generation standard IEEE 802.11be considers multi-link (ML) as a key technology. Multi-link devices (MLDs), capable of transmitting and receiving data across multiple frequency bands, can utilize greater bandwidth for data transmission, thus significantly improving throughput. An MLD consists of multiple stations (STAs), each capable of establishing a link with another station in another MLD for communication.

[0003] A non-access point (non-AP) site can be in an active state or a doze state. When a non-AP site is in an active state, the corresponding link is also active, and data can be transmitted between the non-AP site and the AP site through this link. When a non-AP site is in a doze state, the corresponding link is also dormant, and data cannot be transmitted between the non-AP site and the AP site.

[0004] When a non-AP site is in a dormant state, the AP MLD can cache data services to be sent to the non-AP site, and when the non-AP site is in an active state, send the cached data services to the non-AP site through the link corresponding to the non-AP site.

[0005] However, the non-AP MLD cannot know the cache status of the cached data corresponding to it within the AP MLD, which hinders the non-AP MLD from accurately determining the operational status of the associated link. Therefore, determining the cache status of the cached data corresponding to the non-AP MLD within the AP MLD has become an urgent technical problem to be solved. Summary of the Invention

[0006] This application provides a method and apparatus for determining data caching status, which can determine the data caching status of data type dimensions.

[0007] In a first aspect, embodiments of this application provide a method for determining data caching status. The method includes: a first multi-link device (MLD) receiving first indication information from a second MLD; the first indication information indicating the caching status of cached data corresponding to an association identifier of the first MLD in the second MLD; and the first MLD determining the caching status of cached data corresponding to at least one data type 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.

[0008] In this technical solution, the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD can be determined.

[0009] In one implementation, the first MLD may have multiple sites; the method may further include: the first MLD determining the working status of at least one of the multiple sites based on the caching status of cached data corresponding to at least one data type in the second MLD; the working status is either active or dormant.

[0010] In this technical solution, based on the data type of the cached data, it is beneficial to determine a more suitable working state for the stations in the first MLD, thereby helping to reduce power consumption.

[0011] In one implementation, the method may further include: a first MLD receiving second indication information from a second MLD, the second indication information being used to determine the correspondence between the association identifier of the first MLD and the data types supported by the first MLD.

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

[0013] In this technical solution, by indicating at least one associated identifier (AID) corresponding to at least one data type through the second indication information, AID can be assigned to the first MLD more flexibly.

[0014] In one implementation, the first MLD supports multiple data types; the aforementioned second indication information indicates a first association identifier, which corresponds to a first data type among the multiple data types; the method may further include: the first MLD determines the association identifiers corresponding to other data types among the multiple data types besides the first data type based on the first association identifier corresponding to the first data type.

[0015] In this technical solution, signaling overhead can be effectively saved by indicating an AID in the second indication information.

[0016] Secondly, embodiments of this application provide another method for determining data caching status. The method includes: a second multi-link device (MLD) determining the caching status of cached data corresponding to at least one data type supported by a first MLD in the second MLD; determining the caching status of cached data corresponding to an association identifier in the second MLD based on the caching status of cached data corresponding to at least one data type in the second MLD and the correspondence between the association identifier of the first MLD and the supported data types; and sending first indication information to the first MLD; the first indication information is used to indicate the caching status of cached data corresponding to the association identifier of the first MLD in the second MLD.

[0017] In this technical solution, by indicating the caching status of the cached data corresponding to the association identifier of the first MLD in the second MLD, it is beneficial for the first MLD to determine the caching status of at least one type of cached data in the second MLD by combining the correspondence between the association identifier and the supported data types.

[0018] In one implementation, the method may further include: the second MLD sending second indication information to the first MLD, the second indication information being used to determine the correspondence between the association identifier of the first MLD and the data types supported by the first MLD.

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

[0020] In this technical solution, by indicating at least one associated identifier (AID) corresponding to at least one data type through the second indication information, the AID can be assigned to the first MLD more flexibly.

[0021] In one implementation, the first MLD supports multiple data types; the second indication information indicates a first association identifier, which corresponds to a first data type among the multiple data types.

[0022] In this technical solution, signaling overhead can be effectively saved by indicating an AID in the second indication information.

[0023] Thirdly, embodiments of this application provide another method for determining data caching status. The method includes: a first multi-link device (MLD) receiving cached data from a second MLD via a first link, the cached data including third indication information; the third indication information indicating whether the second MLD caches at least one cached data corresponding to a second data type, wherein the second data type is any data type mapped to the first link; the first MLD determining whether the second MLD caches at least one cached data corresponding to a second data type based on the third indication information.

[0024] In this technical solution, the third indication information can be used to determine whether the second MLD has cached data corresponding to at least one second data type. In other words, the third indication information can be used to determine whether there is cached data that may be transmitted to the first MLD through the first link.

[0025] In one implementation, the first MLD has multiple sites; the method further includes: the first MLD determines the working status of the site corresponding to the first link among the multiple sites based on whether the second MLD caches at least one cached data corresponding to a second data type; the working status is an active state or a dormant state.

[0026] In this technical solution, depending on whether the second MLD contains cached data corresponding to at least one second data type, it is beneficial to determine a more suitable working state for the site corresponding to the first link.

[0027] In one implementation, the first MLD determines the working status of the station corresponding to the first link among multiple stations based on whether the second MLD caches at least one cached data corresponding to a second data type. Specifically, if the second MLD caches at least one cached data corresponding to a second data type, the first MLD determines that the working status of the station corresponding to the first link among multiple stations is active; if the second MLD does not cache any cached data corresponding to any second data type, the first MLD determines that the working status of the station corresponding to the first link among multiple stations is either active or dormant.

[0028] In this technical solution, when the second MLD caches at least one cached data corresponding to a second data type, the station corresponding to the first link is in an active state. If link 1 experiences congestion (or interference, etc.) and cannot transmit cached data, and the data type of the cached data to be transmitted on link 1 is also mapped to the first link, then the station corresponding to the first link remains in an active state until the cached data corresponding to that data type is completely sent; that is, link 1 is in a dormant state. Therefore, the second MLD can schedule the cached data to be transmitted on link 1 to the first link for transmission. This approach helps determine a more suitable working state for the station and facilitates the successful transmission of cached data from the second MLD to the first MLD.

[0029] In one implementation, a third indication information indicates that the second MLD has cached data corresponding to at least one second data type; the method further includes: the first MLD receiving a fourth indication information from the second MLD; the fourth indication information is used to indicate that the second MLD does not have cached data corresponding to any second data type.

[0030] In this technical solution, the fourth indication information can be a Quality of Service Null (QoS Null) frame. When the second MLD cannot send cached data to the second MLD through the first link, and also cannot indicate through the third indication information in the cached data that the second MLD does not cache any cached data corresponding to any second data type, the first MLD can determine that the second MLD does not cache any cached data corresponding to any second data type based on the fourth indication information from the second MLD.

[0031] Fourthly, embodiments of this application provide another method for determining data caching status. The method includes: a second multi-link device (MLD) determining whether it caches at least one type of cached data corresponding to a second data type; the second data type being any data type mapped to a first link; the second MLD sending cached data to a first MLD through the first link, the cached data including third indication information; the third indication information indicating whether the second MLD caches at least one type of cached data corresponding to a second data type.

[0032] In this technical solution, the third indication information can indicate whether the second MLD has cached data corresponding to at least one second data type. In other words, the third indication information can indicate whether there is cached data that may be transmitted to the first MLD through the first link.

[0033] In one implementation, the third indication information indicates that the second MLD has cached data corresponding to at least one second data type; the method may further include: the second MLD sending a fourth indication information to the first MLD; the fourth indication information is used to indicate that the second MLD does not have cached data corresponding to any second data type.

[0034] In this technical solution, the fourth indication information can be a QoS Null frame. When the second MLD cannot send cached data to the first MLD through the first link, and also cannot indicate through the third indication information in the cached data that the second MLD does not cache any cached data corresponding to any second data type, the second MLD can indicate that it does not cache any cached data corresponding to any second data type by sending the fourth indication information to the first MLD.

[0035] Fifthly, embodiments of this application provide another method for determining data caching status. The method includes: a first multi-link device (MLD) receiving cached data corresponding to a third data type from a second MLD. The cached data includes fifth indication information, which is used to indicate whether the second MLD caches cached data corresponding to the third data type; the first MLD determines whether the second MLD caches cached data corresponding to the third data type based on the fifth indication information.

[0036] In this technical solution, based on the fifth indication information in the cached data corresponding to the third data type, it can be determined whether the second MLD caches the cached data corresponding to the third data type.

[0037] In one implementation, the first MLD has multiple sites; the method further includes: the first MLD determines the working status of the site corresponding to the second link among the multiple sites based on whether the second MLD caches cached data corresponding to the third data type, wherein the third data type is mapped to the second link; the working status is either active or dormant.

[0038] In this technical solution, determining whether the second MLD contains cached data corresponding to the third data type helps to identify a more suitable working state for the site corresponding to the second link.

[0039] In one implementation, the method further includes: a first MLD determining whether the second link maps to data types other than the third data type; and the first MLD determining the working status of the station corresponding to the second link among multiple stations based on whether the second MLD caches cached data corresponding to the third data type. A specific implementation of this method is as follows: the first MLD determines the working status of the station corresponding to the second link among multiple stations based on whether the second MLD caches cached data corresponding to the third data type and whether the second link maps to data types other than the third data type.

[0040] In one implementation, the fifth indication information indicates that the second MLD does not cache data corresponding to the third data type; the cache data corresponding to the third data type received by the first MLD from the second MLD may also include a sixth indication information, which is used to indicate whether the second MLD caches cache data corresponding to at least one fourth data type; the fourth data type is any data type other than the third data type among the data types supported by the first MLD.

[0041] In this technical solution, the sixth indication information can determine whether the second MLD caches at least one cached data corresponding to a fourth data type. That is, the sixth indication information can determine the caching status of cached data corresponding to data types other than the third data type in the second MLD. The first MLD can then obtain more detailed caching information, which helps determine a more suitable operating state for the sites within the first MLD.

[0042] In one implementation, the fourth data type has higher priority than the third data type.

[0043] Sixthly, embodiments of this application provide yet another method for determining data caching status. The method includes: a second multi-link device (MLD) determining whether it caches cached data corresponding to a third data type; the second MLD sending the cached data corresponding to the third data type to a first MLD, the cached data including fifth indication information, the fifth indication information being used to indicate whether the second MLD caches cached data corresponding to the third data type.

[0044] In this technical solution, based on the fifth indication information in the cached data corresponding to the third data type, it can be determined whether the second MLD caches the cached data corresponding to the third data type.

[0045] In one implementation, the fifth indication information indicates that the second MLD does not cache data corresponding to the third data type; the cache data corresponding to the third data type sent by the second MLD to the first MLD also includes a sixth indication information, which is used to indicate whether the second MLD caches cache data corresponding to at least one fourth data type; the fourth data type is any data type other than the third data type among the data types supported by the first MLD.

[0046] In this technical solution, the sixth indication information can indicate whether the second MLD caches at least one cached data corresponding to a fourth data type. That is, the sixth indication information can indicate the caching status of cached data corresponding to data types other than the third data type in the second MLD.

[0047] In one implementation, the fourth data type has higher priority than the third data type.

[0048] In a seventh aspect, embodiments of this application provide yet another method for determining data caching status. The method includes: a first multi-link device (MLD) receiving seventh indication information from a second MLD, the seventh indication information indicating that the second MLD does not cache cached data corresponding to a fifth data type; the fifth data type being any data type supported by the first MLD; and the first MLD determining, based on the seventh indication information, that the second MLD does not cache cached data corresponding to the fifth data type.

[0049] In this technical solution, when the second MLD does not cache the cached data corresponding to the fifth data type, the second MLD cannot send the cached data corresponding to the fifth data type to itself, and the first MLD cannot determine that the second MLD does not cache the cached data corresponding to the fifth data type through the "More Data" subfield in the cached data corresponding to the fifth data type. At this time, the first MLD can determine that the second MLD does not cache the cached data corresponding to the fifth data type based on the seventh indication information from the second MLD.

[0050] In one implementation, the first MLD has multiple sites; the method further includes: the first MLD determining the working status of the site corresponding to the third link among the multiple sites based on the fact that the second MLD does not cache cached data corresponding to the fifth data type, wherein the aforementioned fifth data type is mapped to the third link; the working status is either active or dormant.

[0051] In this technical solution, the fact that the second MLD does not cache the cached data corresponding to the fifth data type helps to determine a more suitable working state for the site corresponding to the third link.

[0052] Eighthly, embodiments of this application provide yet another method for determining data caching status. The method includes: a second multi-link device (MLD) determining that the second MLD does not cache cached data corresponding to a fifth data type; the fifth data type being any data type supported by the first MLD; and the second MLD sending seventh indication information to the first MLD, the seventh indication information being used to indicate that the second MLD does not cache cached data corresponding to the fifth data type.

[0053] In this technical solution, when the second MLD does not cache the data corresponding to the fifth data type, the second MLD cannot send the cached data corresponding to the fifth data type to itself, nor can it use the "More Data" subfield in the cached data corresponding to the fifth data type to indicate that the second MLD does not cache the data corresponding to the fifth data type. In this case, the second MLD can determine that it does not cache the data corresponding to the fifth data type by sending a seventh indication message to the first MLD.

[0054] In a ninth aspect, embodiments of this application provide yet another method for determining data caching status. The method includes: a first multi-link device (MLD) receiving eighth indication information from a second MLD via a fourth link, the eighth indication information indicating that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link; the first MLD determining, based on the eighth indication information, that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0055] In this technical solution, the first MLD can determine, based on the eighth indication information, that the second MLD does not have cached data corresponding to any data type mapped to the fourth link, and thus can determine that the second MLD will not send data to the first MLD through the fourth link in the future.

[0056] In one implementation, the first MLD has multiple stations; the method further includes: the first MLD determining the working status of the station corresponding to the fourth link among the multiple stations based on the fact that the second MLD does not cache cached data corresponding to any data type mapped to the fourth link; the working status is either active or dormant.

[0057] In this technical solution, since the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link, it is beneficial to determine a more suitable working state for the site corresponding to the fourth link.

[0058] In a tenth aspect, embodiments of this application provide yet another method for determining data caching status. The method includes: a second multi-link device (MLD) determining that the second MLD does not cache any cached data corresponding to any data type mapped to a fourth link; the second MLD sending an eighth indication message to a first MLD through the fourth link, the eighth indication message being used to indicate that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0059] In this technical solution, the second MLD can send an eighth indication message to the first MLD to indicate that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link, that is, to indicate that the second MLD will not send data to the first MLD through the fourth link in the future.

[0060] Eleventhly, embodiments of this application provide another method for determining data caching status, the method comprising: a first multi-link device (MLD) receiving a ninth indication information from a second MLD, the ninth indication information being used to indicate the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD; the first MLD determining the caching status of cached data corresponding to at least one data type in the second MLD based on the ninth indication information.

[0061] In this technical solution, the first MLD can determine the caching status of cached data corresponding to more than one data type in the second MLD based on the ninth indication information.

[0062] In one implementation, the first MLD has multiple sites; the method further includes: the first MLD determining the working status of at least one of the multiple sites based on the caching status of cached data corresponding to at least one data type in the second MLD; the working status is either active or dormant.

[0063] In this technical solution, the caching status of cached data corresponding to at least one data type in the second MLD is beneficial for determining a more suitable working state for the sites in the first MLD.

[0064] In a twelfth aspect, embodiments of this application provide yet another method for determining data caching status, the method comprising: a second multi-link device (MLD) determining the caching status of cached data corresponding to at least one data type supported by a first MLD in the second MLD; the second MLD sending a ninth indication message to the first MLD, the ninth indication message being used to indicate the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD.

[0065] In this technical solution, the second MLD can use the ninth indication information to indicate to the first MLD the caching status of cached data corresponding to more than one data type in the second MLD.

[0066] In a thirteenth aspect, embodiments of this application provide yet another method for determining data caching status. The method includes: a first multi-link device (MLD) receiving tenth indication information from a second MLD, the tenth indication information being used to indicate the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to the first MLD in the second MLD; and the first MLD determining the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD based on the tenth indication information.

[0067] In this technical solution, based on the tenth instruction information, the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD can be determined. In this way, the caching status of cached data in the second MLD can be determined in more detail.

[0068] In one implementation, the first MLD has multiple sites; the method further includes: the first MLD determining the working state of at least one of the multiple sites based on the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD; the working state is either active or dormant.

[0069] In this technical solution, the caching status of cached data in the second MLD corresponding to at least one data type mapped to at least one link is beneficial for determining a more suitable working state for the sites in the first MLD.

[0070] In a fourteenth aspect, embodiments of this application provide yet another method for determining data caching status. The method includes: a second multi-link device (MLD) determining the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to a first MLD in the second MLD; the second MLD sending tenth indication information to the first MLD, the tenth indication information being used to indicate the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to the first MLD in the second MLD.

[0071] In this technical solution, the second MLD can use the tenth indication information to indicate to the first MLD the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD. In this way, the caching status of cached data in the second MLD can be indicated in more detail.

[0072] In a fifteenth aspect, embodiments of this application provide a communication device that has some or all of the functions of the first MLD described in the examples of the methods described in the first, third, fifth, seventh, ninth, eleventh, or thirteenth aspects above. For example, the communication device may have the functions of some or all of the embodiments in this application, or it may have the functions of any one embodiment in this application implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0073] In one implementation, the communication device may include a processing unit and a communication unit. The processing unit is configured to support the communication device in performing the corresponding functions described in the above method. The communication unit supports communication between the communication device and other devices. The communication device may also include a storage unit coupled to the processing unit and the transmitting unit, which stores necessary computer programs and data for the communication device.

[0074] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in the first aspect above, the communication device includes:

[0075] A communication unit is configured to receive first indication information from a second MLD; the first indication information is used to indicate the cache status of cached data corresponding to the associated identifier of the communication device in the second MLD.

[0076] The processing unit is configured to determine the caching status of cached data corresponding to at least one data type 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.

[0077] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0078] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in the first aspect above, the communication device includes:

[0079] A transceiver is used to receive first indication information from a second MLD; the first indication information is used to indicate the cache status of cached data corresponding to the associated identifier of the communication device in the second MLD.

[0080] The processor is configured to determine the caching status of cached data corresponding to at least one data type in the second MLD based on the first instruction information and the correspondence between the association identifier of the first MLD and the data types supported by the first MLD.

[0081] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in the third aspect above, the communication device includes:

[0082] A communication unit is configured to receive cached data from a second MLD via a first link. The cached data includes third indication information. The third indication information is configured to indicate whether the second MLD caches at least one cached data corresponding to a second data type, wherein the second data type is any data type mapped to the first link.

[0083] The processing unit is configured to determine, based on the third indication information, whether the second MLD contains cached data corresponding to at least one second data type.

[0084] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0085] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in the third aspect above, the communication device includes:

[0086] A transceiver is used to receive cached data from a second MLD via a first link. The cached data includes third indication information. The third indication information is used to indicate whether the second MLD caches at least one cached data corresponding to a second data type, wherein the second data type is any data type mapped to the first link.

[0087] The processor is configured to determine, based on the third instruction information, whether the second MLD contains cached data corresponding to at least one second data type.

[0088] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in the fifth aspect above, the communication device includes:

[0089] A communication unit is used to receive cached data corresponding to a third data type from a second MLD. The cached data includes fifth indication information, which is used to indicate whether the second MLD has cached data corresponding to the third data type.

[0090] The processing unit is configured to determine, based on the fifth indication information, whether the second MLD contains cached data corresponding to the third data type.

[0091] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0092] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in the fifth aspect above, the communication device includes:

[0093] A transceiver is used to receive cached data corresponding to a third data type from a second MLD. The cached data includes fifth indication information, which is used to indicate whether the second MLD has cached data corresponding to the third data type.

[0094] The processor is configured to determine, based on the fifth instruction information, whether the second MLD contains cached data corresponding to the third data type.

[0095] In one implementation, when the communication device has some or all of the functions of the first MLD in the method example of the seventh aspect described above, the communication device includes:

[0096] The communication unit is configured to receive a seventh indication information from the second MLD, the seventh indication information indicating that the second MLD does not cache data corresponding to the fifth data type; the fifth data type is any data type among the data types supported by the communication device;

[0097] The processing unit is configured to determine, based on the seventh indication information, that the second MLD does not cache the cached data corresponding to the fifth data type.

[0098] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0099] In one implementation, when the communication device has some or all of the functions of the first MLD in the method example of the seventh aspect described above, the communication device includes:

[0100] A transceiver is used to receive a seventh indication message from a second MLD, the seventh indication message indicating that the second MLD does not cache data corresponding to a fifth data type; the fifth data type is any data type among the data types supported by the communication device;

[0101] The processor is configured to determine, based on the seventh indication information, that the second MLD does not cache the cached data corresponding to the fifth data type.

[0102] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in the ninth aspect above, the communication device includes:

[0103] A communication unit is configured to receive an eighth indication message from a second MLD via a fourth link, the eighth indication message being used to indicate that the second MLD does not have cached data corresponding to any data type mapped to the fourth link;

[0104] The processing unit is configured to determine, based on the eighth indication information, that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0105] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0106] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in the ninth aspect above, the communication device includes:

[0107] A transceiver is used to receive eighth indication information from a second MLD via a fourth link. The eighth indication information is used to indicate that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0108] The processor is configured to determine, based on the eighth indication information, that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0109] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in the eleventh aspect above, the communication device includes:

[0110] A communication unit is configured to receive a ninth indication information from a second MLD, the ninth indication information being used to indicate the caching status of cached data corresponding to at least one data type supported by the communication device in the second MLD.

[0111] The processing unit is configured to determine the caching status of cached data corresponding to at least one data type in the second MLD based on the ninth instruction information.

[0112] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0113] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in the eleventh aspect above, the communication device includes:

[0114] A transceiver is configured to receive a ninth indication information from a second MLD, the ninth indication information being used to indicate the caching status of cached data corresponding to at least one data type supported by the communication device in the second MLD.

[0115] The processor is configured to determine, based on the ninth instruction information, the caching status of cached data corresponding to at least one data type in the second MLD.

[0116] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in aspect thirteen above, the communication device includes:

[0117] A communication unit is configured to receive tenth indication information from a second MLD, the tenth indication information being used to indicate the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to the communication device in the second MLD;

[0118] The processing unit is configured to determine, based on the tenth instruction information, the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD.

[0119] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0120] In one implementation, when the communication device has some or all of the functions of the first MLD in the example of the method described in aspect thirteen above, the communication device includes:

[0121] A transceiver is configured to receive tenth indication information from a second MLD, the tenth indication information being used to indicate the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to the communication device in the second MLD;

[0122] The processor is configured to determine, based on the tenth instruction information, the cache status of cached data corresponding to at least one data type mapped to at least one link in the second MLD.

[0123] In a sixteenth aspect, embodiments of this application provide another communication device that has some or all of the functions of the second MLD in the method examples described in the second, fourth, sixth, eighth, tenth, twelfth, or fourteenth aspects above. For example, the communication device may have the functions of some or all of the embodiments in this application, or it may have the functions of implementing any one of the embodiments in this application individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0124] In one implementation, 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 the corresponding functions described in the above method. The communication unit supports communication between the communication device and other devices. The storage unit is coupled to the processing unit and the transmitting unit, and stores necessary computer programs and data for the communication device. The storage unit also stores cached data.

[0125] In one implementation, when the communication device has some or all of the functions of the second MLD in the method example described in the second aspect above, the communication device includes:

[0126] The processing unit is used to determine the caching status of cached data corresponding to at least one data type supported by the first MLD in the storage unit; and to determine the caching status of cached data corresponding to the association identifier in the storage unit based on the caching status of cached data corresponding to at least one data type in the storage unit and the correspondence between the association identifier of the first MLD and the supported data types.

[0127] A communication unit is used to send first indication information to the first MLD; the first indication information is used to indicate the caching status of the cached data corresponding to the associated identifier of the first MLD in the storage unit.

[0128] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0129] In one implementation, when the communication device has some or all of the functions of the second MLD in the method example described in the second aspect above, the communication device includes:

[0130] The processor is configured to determine the cache status of cached data corresponding to at least one data type supported by the first MLD in memory; and to determine the cache status of cached data corresponding to the association identifier in memory based on the cache status of cached data corresponding to at least one data type in memory and the correspondence between the association identifier of the first MLD and the supported data types.

[0131] A transceiver is used to send first indication information to a first MLD; the first indication information is used to indicate the cache status of cached data corresponding to the associated identifier of the first MLD in memory.

[0132] In one implementation, when the communication device has some or all of the functions of the second MLD in the method example of the fourth aspect described above, the communication device includes:

[0133] The processing unit is used to determine whether the storage unit caches at least one cached data corresponding to a second data type; the second data type is any data type mapped to the first link;

[0134] A communication unit is used to send cached data to a first MLD via the first link. The cached data includes third indication information. The third indication information is used to indicate whether the storage unit has cached data corresponding to at least one second data type.

[0135] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0136] In one implementation, when the communication device has some or all of the functions of the second MLD in the method example of the fourth aspect described above, the communication device includes:

[0137] The processor is configured to determine whether cached data corresponding to at least one second data type is cached in the memory; the second data type is any data type mapped to the first link;

[0138] A transceiver is used to send cached data to a first MLD via the first link. The cached data includes third indication information. The third indication information is used to indicate whether the memory contains cached data corresponding to at least one second data type.

[0139] In one implementation, when the communication device has some or all of the functions of the second MLD in the method example described in the sixth aspect above, the communication device includes:

[0140] The processing unit is used to determine whether the storage unit contains cached data corresponding to the third data type.

[0141] The communication unit is used to send cached data corresponding to the third data type to the first MLD. The cached data includes fifth indication information, which is used to indicate whether the storage unit has cached data corresponding to the third data type.

[0142] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0143] In one implementation, when the communication device has some or all of the functions of the second MLD in the method example described in the sixth aspect above, the communication device includes:

[0144] The processor is used to determine whether cached data corresponding to a third data type is cached in memory.

[0145] A transceiver is used to send cached data corresponding to the third data type to the first MLD. The cached data includes fifth indication information, which is used to indicate whether the memory has cached data corresponding to the third data type.

[0146] In one implementation, when the communication device has some or all of the functions of the second MLD in the method example of the eighth aspect described above, the communication device includes:

[0147] The processing unit is used to determine that the storage unit does not cache data corresponding to the fifth data type; the fifth data type is any data type among the data types supported by the first MLD;

[0148] The communication unit is used to send a seventh indication message to the first MLD, which indicates that the storage unit does not cache the cached data corresponding to the fifth data type.

[0149] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0150] In one implementation, when the communication device has some or all of the functions of the second MLD in the method example of the eighth aspect described above, the communication device includes:

[0151] The processor is configured to determine that the memory does not cache data corresponding to a fifth data type; the fifth data type is any data type among the data types supported by the first MLD.

[0152] A transceiver is used to send a seventh indication message to the first MLD, the seventh indication message being used to indicate that the memory does not cache data corresponding to the fifth data type.

[0153] In one implementation, when the communication device has some or all of the functions of the second MLD in the example of the method described in the tenth aspect above, the communication device includes:

[0154] The processing unit is used to determine that the storage unit does not cache any data corresponding to any data type mapped to the fourth link;

[0155] The communication unit is used to send an eighth indication message to the first MLD through the fourth link. The eighth indication message is used to indicate that the storage unit does not cache any cached data corresponding to any data type mapped to the fourth link.

[0156] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0157] In one implementation, when the communication device has some or all of the functions of the second MLD in the example of the method described in the tenth aspect above, the communication device includes:

[0158] The processor is used to determine that the memory does not cache any data corresponding to any data type mapped to the fourth link;

[0159] A transceiver is used to send an eighth indication message to the first MLD via the fourth link. The eighth indication message is used to indicate that the memory does not cache any data corresponding to any data type mapped to the fourth link.

[0160] In one implementation, when the communication device has some or all of the functions of the second MLD in the method example of the twelfth aspect described above, the communication device includes:

[0161] The processing unit is used to determine the caching status of cached data corresponding to at least one data type supported by the first MLD in the storage unit;

[0162] A communication unit is used to send a ninth indication message to the first MLD, the ninth indication message being used to indicate the caching status of cached data corresponding to at least one data type supported by the first MLD in the storage unit.

[0163] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0164] In one implementation, when the communication device has some or all of the functions of the second MLD in the method example of the twelfth aspect described above, the communication device includes:

[0165] The processor is configured to determine the cache status of cached data corresponding to at least one data type supported by the first MLD in memory;

[0166] A transceiver is used to send a ninth indication message to a first MLD, the ninth indication message being used to indicate the cache status of cached data corresponding to at least one data type supported by the first MLD in memory.

[0167] In one implementation, when the communication device has some or all of the functions of the second MLD in the example of the method described in the fourteenth aspect above, the communication device includes:

[0168] The processing unit is used to determine the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to the first MLD in the storage unit;

[0169] A communication unit is used to send a tenth indication information to a first MLD, the tenth indication information being used to indicate the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to the first MLD in the storage unit.

[0170] As an example, the processing unit can be a processor, the communication unit can be a transceiver or a communication interface, and the storage unit can be a memory.

[0171] In one implementation, when the communication device has some or all of the functions of the second MLD in the example of the method described in the fourteenth aspect above, the communication device includes:

[0172] The processor is configured to determine the cache status of cached data in memory corresponding to at least one data type mapped to at least one link corresponding to the first MLD;

[0173] A transceiver is used to send a tenth indication information to a first MLD, the tenth indication information being used to indicate the cache status of cached data corresponding to at least one data type mapped to at least one link corresponding to the first MLD in memory.

[0174] In a seventeenth aspect, embodiments of the present invention provide a computer-readable storage medium for storing a computer program for use by the first MLD described above, wherein when the computer program is executed, the first MLD performs the methods described in the first, third, fifth, seventh, ninth, eleventh, or thirteenth aspects.

[0175] In an eighteenth aspect, embodiments of the present invention provide a computer-readable storage medium for storing a computer program for use by the second MLD described above, wherein when the computer program is executed, the second MLD performs the methods described in the second, fourth, sixth, eighth, tenth, twelfth, or fourteenth aspects.

[0176] In a nineteenth aspect, this application also provides a computer program product including a computer program, which, when run on a computer, causes the computer to perform the methods described in the first, third, fifth, seventh, ninth, eleventh, or thirteenth aspects described above.

[0177] In a twentieth aspect, this application also provides a computer program product that, when run on a computer, causes the computer to perform the methods described in the second, fourth, sixth, eighth, tenth, twelfth, or fourteenth aspects described above.

[0178] In a twentieth aspect, this application provides a chip system including at least one processor and an interface for supporting a first MLD in implementing the functions involved in the first, third, fifth, seventh, ninth, eleventh, or thirteenth aspects, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the first MLD. The chip system may be composed of chips or may include chips and other discrete devices.

[0179] In a twenty-second aspect, this application provides a chip system comprising at least one processor, at least one memory, and an interface for supporting a second MLD in implementing the functions involved in the second, fourth, sixth, eighth, tenth, twelfth, or fourteenth aspects, such as determining or processing at least one of the data and information involved in the above methods. The memory is used to store cached data, as well as computer programs and data necessary for the second MLD. This chip system may be composed of a chip or may include chips and other discrete devices. Attached Figure Description

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

[0181] Figure 2 This is a flowchart illustrating a method for determining data caching status provided in an embodiment of this application;

[0182] Figure 3a This is a flowchart illustrating another method for determining data caching status provided in an embodiment of this application;

[0183] Figure 3b This is a schematic diagram of the management frames supported by a first MLD-a and a second MLD-b, and the AIDs corresponding to each AC, provided in an embodiment of this application.

[0184] Figure 4a This is a flowchart illustrating another method for determining data caching status provided in an embodiment of this application;

[0185] Figure 4b This is a schematic diagram illustrating a scenario where a second MLD sends cached data to a first MLD, as provided in an embodiment of this application.

[0186] Figure 5 This is a flowchart illustrating another method for determining data caching status provided in an embodiment of this application;

[0187] Figure 6aThis is a flowchart illustrating another method for determining data caching status provided in an embodiment of this application;

[0188] Figure 6b This is a schematic diagram of a scenario for determining the working state of a link, provided in an embodiment of this application;

[0189] Figure 6c This is a schematic diagram of another scenario for determining the working state of a link, provided by an embodiment of this application;

[0190] Figure 6d This is a schematic diagram of another scenario for determining the working state of a link, provided in an embodiment of this application;

[0191] Figure 7 This is a flowchart illustrating another method for determining data caching status provided in an embodiment of this application;

[0192] Figure 8 This is a flowchart illustrating another method for determining data caching status provided in an embodiment of this application;

[0193] Figure 9a This is a flowchart illustrating another method for determining data caching status provided in an embodiment of this application;

[0194] Figure 9b This is a schematic diagram of a More Data Per TID Per link subfield provided in an embodiment of this application;

[0195] Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0196] Figure 11 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0197] Figure 12 This is a schematic diagram of the structure of a chip provided in an embodiment of this application;

[0198] Figure 13 This is a schematic diagram of the structure of another communication device provided in the embodiments of this application;

[0199] Figure 14 This is a schematic diagram of the structure of another communication device provided in the embodiments of this application;

[0200] Figure 15 This is a schematic diagram of another chip structure provided in an embodiment of this application. Detailed Implementation

[0201] To facilitate understanding, the terminology used in this application will be introduced first.

[0202] 1. Traffic Indication Map (TIM) field

[0203] The TIM field can be included in the TIM element carried in an 802.11 beacon frame. An AP MLD can periodically send 802.11 beacon frames to one or more non-AP MLDs. The TIM element carried in these beacon frames can determine the cached data status of each site within each non-AP MLD within that AP MLD. The cached data status of a site within an AP MLD indicates whether the AP MLD has data cached and ready to be sent to that site.

[0204] Non-AP sites can operate in two modes: non-energy-saving mode and energy-saving mode. In non-energy-saving mode, the non-AP site is active regardless of whether data transmission is required between it and the AP site. In energy-saving mode, the non-AP site is active when data transmission between it and the AP site is required; otherwise, it can be in sleep mode, thus saving power consumption of the non-AP MLD.

[0205] Non-AP sites in power-saving mode can periodically wake up (i.e., become active) to receive beacon frames sent by the AP MLD to determine whether the AP MLD has cached data to be sent to that non-AP site. If the AP MLD does not have the corresponding data cached for that non-AP site, it can put that non-AP site into a sleep state; if the AP MLD has cached the corresponding data for that non-AP site, it can put that non-AP site into an active state to receive the corresponding data.

[0206] 802.11 beacon frames may include TIM beacon frames or Delivery Traffic Indication Map (DTIM) beacon frames. Both TIM and DTIM beacon frames carry TIM elements. The fields included in the TIM element are shown in Table 1.

[0207] Table 1. Fields included in TIM elements

[0208]

[0209] The TIM element consists of several fields: Element Identifier (ID) field: used to identify the element as a TIM element. Length field: indicates the number of bytes occupied by the TIM element. DTIM Count field: indicates how many TIM beacon frames are expected before the next DTIM beacon frame arrives. DTIM Period field: indicates the arrival interval between two adjacent DTIM beacon frames. Each of the following fields can occupy 1 byte: Element ID, Length, DTIM Count, DTIM Period, and Bitmap Control. Bit 0 in the Bitmap Control field indicates whether there is downlink multicast data service when the AP sends the DTIM beacon frame; bits 1-7 indicate the offset of a portion of the virtual bitmap, measured in bytes (8 bits). The virtual bitmap is the TIM field, and each bit in the TIM field corresponds to an association identifier (AID). For example, if the offset is 0, the virtual bitmap can start from AID1; if the offset is 1, the virtual bitmap can start from AID9.

[0210] 2. Access Category (AC)

[0211] Enhanced Distributed Channel Access (EDCA) is a channel contention mechanism that classifies data packets into four types of Access Controls (ACs). Higher-priority ACs have a greater chance of occupying the channel than lower-priority ACs. EDCA benefits high-priority packets by granting them priority transmission rights and 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).

[0212] 3. Traffic Identifier (TID)

[0213] Upper-layer entities can use TIDs to distinguish the Quality of Service (QoS) supported by the MAC Service Data Unit (MSDU) in the medium access control (MAC) layer. EDCA supports eight TIDs: TID0 through TID7. There is a correspondence between ACs and TIDs; one AC can correspond to one or more TIDs, and one TID corresponds to one AC.

[0214] 4. Management Frame

[0215] Management frames can be used to manage data packets, control the network, etc. Management frames may include, but are not limited to: beacon frames, probe request frames, probe response frames, Independent Basic Service Set (IBSS) Announcement Traffic Indication Message (ATIM) frames, disassociation frames, deauthentication frames, association request frames, reassociation request frames, authentication frames, and authentication frames. The management frames mentioned in the embodiments of this application may refer to any one or more of the above-mentioned management frames.

[0216] In this context, beacon frames can be used to declare the existence of a network. Mobile workstations can scan their area for 802.11 networks using Probe Request frames. If a network checked by a Probe Request frame is compatible, that network responds with a Probe Request frame. IBSS workstations buffer frames for dormant receivers and send IBSS ATIM frames during transmission to notify the receiver that a message is pending. Disassociation and Deauthentication frames can both be used to terminate an authentication relationship. A mobile workstation that finds a compatible network and authenticates sends an Association Request frame to attempt to join the network. Mobile workstations located in the same extended service area but moving between different basic service areas re-associate with the network using a Reassociation Request frame when using the distributed system again. Action frames are used to trigger measurement actions.

[0217] To better understand the method for determining data caching status disclosed in the embodiments of this application, the communication system to which the embodiments of this application are applicable will be described first.

[0218] This application provides a communication method for a wireless communication system, which can be a wireless local area network (WLAN) or a cellular network. The method can be implemented by a communication device within the wireless communication system, or by a chip or processor within that device. This communication device can be a wireless communication device that supports parallel transmission across multiple links, for example, a multi-link device or a multi-band device. Compared to devices that only support single-link transmission, multi-link devices offer higher transmission efficiency and higher throughput.

[0219] A multi-link device includes one or more affiliated STAs. An affiliated STA is a logical site that can operate on a single link. The affiliated site can be an Access Point (AP) or a non-Access Point Station (non-AP STA). For ease of description, this application refers to a multi-link device whose affiliated site is an AP as a multi-link AP, a multi-link AP device, or an AP multi-link device, and a multi-link device whose affiliated site is a non-AP STA as a multi-link STA, a multi-link STA device, or a STA multi-link device. For ease of description, "a multi-link device includes affiliated STAs" is also briefly described in this embodiment as "a multi-link device includes STAs".

[0220] It is worth noting that a multi-link device includes multiple logical stations, each operating on one link, but multiple logical stations are allowed to operate on the same link. The link identifier mentioned below represents a station operating on a single link; that is, if there is more than one station on a link, more than one link identifier is needed to represent them. The link mentioned below may also sometimes refer to the station operating on that link.

[0221] Multi-link AP devices and multi-link STA devices can use link identifiers to identify a link or a station on a link during data transmission. Before communication, the multi-link AP devices and multi-link STA devices can negotiate or communicate the correspondence between the link identifier and a link or a station on a link. Therefore, during data transmission, it is not necessary to transmit a large amount of signaling information to indicate the link or the station on the link; carrying the link identifier is sufficient, reducing signaling overhead and improving transmission efficiency.

[0222] Multilink devices can implement wireless communication by following the 802.11 series of protocols. For example, they can follow Extremely High Throughput (EHT) stations or 802.11be-based or compatible stations to communicate with other devices. Of course, other devices can be multilink devices or not.

[0223] For example, the multi-link device in the embodiments of this application can be a single-antenna device or a multi-antenna device. For instance, it can be a device with two or more antennas. The embodiments of this application do not limit the number of antennas included in the multi-link device. In the embodiments of this application, the multi-link device can allow services of the same access type to be transmitted on different links, and even allow the same data packets to be transmitted on different links; it can also disallow services of the same access type to be transmitted on different links, but allow services of different access types to be transmitted on different links.

[0224] Multi-link devices can operate in the following frequency bands: sub 1GHz, 2.4GHz, 5GHz, 6GHz and high frequency 60GHz.

[0225] For example, a multi-link device is a device with wireless communication capabilities. This device can be a complete machine or a chip or processing system installed in a complete machine. Devices with these chips or processing systems installed can implement the methods and functions of the embodiments of this application under the control of these chips or processing systems. For example, the multi-link STA in the embodiments of this application has wireless transceiver capabilities, can support the 802.11 series protocols, and can communicate with multi-link APs or other multi-link STAs or single-link devices. For example, a multi-link STA is any user communication device that allows users to communicate with APs and then with WLANs. For example, a multi-link STA can be a user device that can connect to the Internet, such as a tablet, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), or mobile phone, or an IoT node in the Internet of Things, or an in-vehicle communication device in the Internet of Vehicles, etc. A multi-link STA can also be a chip and processing system in these terminals. The multi-link AP in the embodiments of this application provides services to the multi-link STA and can support the 802.11 series protocols. For example, a multi-link AP can be a communication entity such as a communication server, router, switch, or bridge. Alternatively, the multi-link AP can include various forms of macro base stations, micro base stations, and relay stations. Of course, a multi-link AP can also be the chip and processing system within these various types of devices, thereby implementing the methods and functions of the embodiments of this application. Furthermore, multi-link devices can support high-speed, low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can be applied to more scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, audio equipment, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR, and other wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-service checkout machines, self-service ordering machines, etc.). The specific forms of multi-link STAs and multi-link APs in the embodiments of this application are not specifically limited; they are merely illustrative examples. The 802.11 protocol can be a protocol that supports or is compatible with 802.11be.

[0226] Although the embodiments of this application are primarily illustrated using a network deploying IEEE 802.11 as an example, those skilled in the art will readily understand that the various aspects of this application can be extended to other networks employing various standards or protocols, such as BLUETOOTH, high-performance radio LAN (HIPERLAN) (a wireless standard similar to IEEE 802.11, primarily used in Europe), and wide area networks (WANs), wireless local area networks (WLANs), personal area networks (PANs), or other networks now known or developed in the future. Therefore, regardless of the coverage area and wireless access protocol used, the various aspects provided in this application can be applied to any suitable wireless network.

[0227] The following describes embodiments of this application, which do not limit the scope and applicability of the claims. Those skilled in the art can make adaptive changes to the function and deployment of the elements involved in this application without departing from the scope of the embodiments, or omit, substitute, or add various processes or components as appropriate.

[0228] Please see Figure 1 , Figure 1 This application provides an architectural diagram of a communication system according to an embodiment. The communication system may include, but is not limited to, a first MLD and a second MLD. Figure 1 The number and form of devices shown are for illustrative purposes and do not constitute a limitation on the embodiments of this application. In actual applications, there may be two or more first MLDs and two or more second MLDs. Figure 1 The communication system shown is an example comprising a first MLD101 and a second MLD102.

[0229] The second MLD102 can be used to determine the caching status of cached data corresponding to at least one data type supported by the first MLD101 in the second MLD102; and send indication information to the first MLD101; the indication information can be used to indicate the caching status of cached data corresponding to at least one data type supported by the first MLD101 in the second MLD102.

[0230] After receiving the instruction information from the second MLD102, the first MLD101 can determine the caching status of cached data corresponding to at least one data type supported by the first MLD101 in the second MLD102 based on the instruction information.

[0231] In this embodiment, the data types supported by the first MLD 101 may include at least one of service type and management frame, wherein the service type may refer to AC or TID. The first MLD 101 may support one or more data types. Taking data type 1 supported by the first MLD 101 as an example, the caching status of the cached data corresponding to data type 1 in the second MLD 102 can refer to whether the second MLD 102 caches cached data to be sent to the first MLD 101, and the data type of the cached data is data type 1. In this embodiment, the data types supported by the first MLD 101 can be determined during the process of establishing a connection between the first MLD 101 and the second MLD 102.

[0232] Different MLD101 versions can support the same or different data types. Figure 1 When the communication system shown includes multiple first MLDs 101, a second MLD 102 can determine the caching status of cached data corresponding to at least one data type supported by each first MLD 101 in the second MLD 102; and send indication information to each first MLD 101. It should be noted that the second MLD can broadcast the indication information to each first MLD. In this case, the indication information received by each first MLD is the same, indicating the caching status of cached data corresponding to at least one data type supported by each first MLD 101 in the second MLD 102. Alternatively, the second MLD can broadcast the indication information to each first MLD separately. In this case, the indication information received by each first MLD is different, indicating the caching status of cached data corresponding to at least one data type supported by that first MLD 101 in the second MLD 102. It should be noted that "at least one" mentioned in the embodiments of this application can be described as one or more.

[0233] when Figure 1 When the communication system shown includes multiple second MLDs 102, each second MLD 102 (such as second MLD-a and second MLD-b) can determine the caching status of cached data corresponding to at least one data type supported by the first MLD 101 in that second MLD 102, and send indication information to the first MLD 101 respectively. The indication information received by the first MLD 101 from the second MLD-a can indicate the caching status of cached data corresponding to at least one data type supported by the first MLD 101 in the second MLD-a. Similarly, the indication information received by the first MLD 101 from the second MLD-b can indicate the caching status of cached data corresponding to at least one data type supported by the first MLD 101 in the second MLD-b.

[0234] It is understood that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0235] The method and apparatus for determining the data caching situation provided in this application will be described in detail below with reference to the accompanying drawings.

[0236] Please see Figure 2 , Figure 2 This is a flowchart illustrating a method for determining data caching status according to an embodiment of this application. The method details how a first MLD determines the caching status of at least one data type of cached data in a second MLD based on indication information from a second MLD. Specifically, the execution subject of steps S201 to S202 is the second MLD or a chip within the second MLD, and the execution subject of step S203 is the first MLD or a chip within the first MLD. The following explanation uses the second MLD and the first MLD as examples of the execution subjects for determining the data caching status. Figure 2 As shown, the method may include, but is not limited to, the following steps:

[0237] Step S201: The second multi-link device (MLD) determines the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD.

[0238] In this embodiment, the second MLD can determine whether cached data corresponding to at least one data type supported by the first MLD is cached in the second MLD. When the first MLD supports a data type, the second MLD can determine whether there is cached data to be sent to the first MLD, and the data type of the cached data is a data type supported by the first MLD.

[0239] When the first MLD supports multiple data types, the second MLD can determine whether the cached data corresponding to each data type supported by the first MLD is cached in the second MLD. For example, when the first MLD supports three data types (data type 1, data type 2, and data type 3), the second MLD can determine whether the cached data corresponding to data type 1, data type 2, and data type 3 is cached in the second MLD, respectively. In another implementation, the second MLD can determine whether the cached data corresponding to data type 1 is cached in the second MLD, and also determine whether the cached data corresponding to at least one of data types 2 and 3 is cached in the second MLD. For example, in the second MLD, when the cached data corresponding to data type 1 is cached in cache region a, and the cached data corresponding to data types 2 and 3 is cached in cache region b, if the second MLD detects the existence of a bufferable unit (BU) in cache region a, it indicates that the second MLD caches the cached data corresponding to data type 1; if the second MLD detects the absence of a bufferable unit in cache region a, it indicates that the second MLD does not cache the cached data corresponding to data type 1. Similarly, if the second MLD detects the presence of a cache unit in cache region b, it indicates that the second MLD caches cached data corresponding to at least one of data types 2 and 3; if the second MLD detects the absence of a cache unit in cache region b, it indicates that the second MLD does not cache cached data corresponding to either data type 2 or data type 3.

[0240] It should be noted that the cache areas occupied by the cached data corresponding to the above-mentioned data types 1, 2, and 3 within the second MLD are merely examples and do not constitute a limitation on the embodiments of this application. The embodiments of this application do not limit how the cached data corresponding to at least one data type supported by the first MLD is cached within the second MLD. In one implementation, the second MLD can cache the cached data corresponding to at least one data type supported by the first MLD in a common cache area. Alternatively, the second MLD can cache the cached data corresponding to various data types supported by the first MLD in separate cache areas. Alternatively, the second MLD can combine a common cache with independent caches to cache the cached data corresponding to the data types supported by the first MLD. Alternatively, the second MLD can cache the cached data corresponding to the service types supported by the first MLD in one cache area and cache the cached data corresponding to the management frame in another cache area. The first MLD and the second MLD can be connected through multiple links. In one implementation, the second MLD can determine which link the cached data corresponding to at least one data type supported by the first MLD will be transmitted to the first MLD via, and further, the second MLD can cache the cached data transmitted via the same link in a separate cache area. It should also be noted that the second MLD can send cached data to the first MLD through a site. The site in the second MLD can schedule cached data from one or more cache areas and send it to the first MLD.

[0241] It should also be noted that when the second MLD has a connection relationship with multiple first MLDs, the second MLD can determine the caching status of cached data corresponding to at least one data type supported by each first MLD in the second MLD.

[0242] Step S202: The second MLD sends indication information to the first MLD, the indication information being used to indicate the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD.

[0243] Specifically, after the second MLD determines the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD, it can send indication information to the first MLD. Each bit in this indication information can correspond to one or more data types supported by the first MLD, and the value of each bit can indicate whether the cached data of the data type corresponding to that bit is cached in the second MLD. In this embodiment, the indication information can also be referred to as ninth indication information.

[0244] In one implementation, the aforementioned indication information may refer to the 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, meaning that information for eight control types can be carried through the corresponding bits of the EHT A-control field. The relevant information for the eight control types is shown in Table 2. It should be noted that the EHT A-control field is only an example; for instance, it could also be the HT control field containing the EHT A-control or HE A-control fields. As the standard version evolves, the name of this field may change, but as long as it indicates the corresponding function, it falls within the scope of this application's embodiments.

[0245] Table 2. Relevant information for 8 control types

[0246]

[0247] In Table 2, the type (More Data Per TID) with control ID = 7 is newly added. It should be noted that the values ​​and names of the control IDs in Table 2 are for illustrative purposes only and do not constitute a limitation on the embodiments of this application. It should also be noted that the newly added type, More Data Per TID, is based on the example where the first MLD supports data types including service types and management frames, and the service type is TID. When the service type is AC, the newly added type in Table 2 can be More Data Per AC. Correspondingly, in this case, More Data Per AC can occupy 5 bits, where each of the 4 bits corresponds to one type of AC, and the other bit corresponds to a management frame.

[0248] This application uses the newly added type "More Data Per TID" as an example for illustration. The More Data Per TID subfield can include 9 bits, of which 8 bits correspond to 8 types of TIDs, each of which corresponds to one type of TID, and the remaining bit corresponds to the management frame. When a bit in the More Data Per TID subfield corresponding to a TID is set to 1, it indicates that the second MLD caches the cached data corresponding to that TID. When that bit is set to 0, it indicates that the second MLD does not cache the cached data corresponding to that TID. When a bit in the More Data Per TID subfield corresponding to a management frame is set to 1, it indicates that the second MLD caches the cached data of the management frame. When that bit is set to 0, it indicates that the second MLD does not cache the cached data of the management frame.

[0249] In one implementation, a single bit in the More Data Per TID subfield can correspond to one or more TIDs. In this case, the number of bits occupied by More Data Per AC can be less than 9. For example, a single bit in the More Data Per TID subfield can correspond to TID1 and TID2. When this bit is set to 1, it indicates that the second MLD caches cached data corresponding to at least one of TIDs, TID1 and TID2. When this bit is set to 0, it indicates that the second MLD does not cache cached data corresponding to either TID1 or TID2.

[0250] In one implementation, a second MLD can send indication information to multiple first MLDs. This indication information can indicate the caching status of cached data corresponding to at least one data type supported by each first MLD in the second MLD. For example, when the second MLD sends indication information to first MLD-a and first MLD-b, a portion of the bits in the indication information can correspond to at least one data type supported by first MLD-a; that is, the value of this portion of bits is used to indicate the caching status of cached data corresponding to at least one data type supported by first MLD-a in the second MLD. Another portion of the bits in the indication information can correspond to at least one data type supported by first MLD-b; that is, the value of this other portion of bits is used to indicate the caching status of cached data corresponding to at least one data type supported by first MLD-b in the second MLD.

[0251] In this embodiment, the second MLD and the first MLD transmit data via links, each link being established between a station in the first MLD and a station in the second MLD. If a station in the first MLD or the second MLD is in a dormant state, the link corresponding to that station is also in a dormant state. In this case, data cannot be transmitted through that link, and the station in the first MLD corresponding to that link cannot receive data. In this embodiment, a station in the second MLD can schedule cached data in the second MLD and send the cached data to the corresponding station in the first MLD. When a station in the first MLD is in a dormant state, it cannot receive data.

[0252] In one implementation, the aforementioned indication information can be carried in the cached data sent by the second MLD to the first MLD. In this case, the indication information can be used to indicate whether the cached data corresponding to at least one data type supported by the first MLD has been sent (cached in the second MLD). Specifically, the indication information can be included in the EHT A-control field of the MAC frame. In another implementation, the second MLD can periodically send indication information to the second MLD belonging to a station in power-saving mode. In this case, the indication information can indicate whether the first MLD has cached cached data to be sent to the station while the station is in a dormant state. The indication information can be received by the station in the first MLD that is in an active state. The indication information can be carried in a control frame or a management frame.

[0253] Step S203: The first MLD determines the caching status of cached data corresponding to at least one data type in the second MLD based on the instruction information.

[0254] After receiving the instruction information from the second MLD, the first MLD can determine the caching status of cached data corresponding to at least one data type in the second MLD based on the instruction information.

[0255] Specifically, if a bit in the indication information has a first value (e.g., 1), the first MLD can determine that the cached data of the data type corresponding to that bit is cached in the second MLD; if the bit has a second value (e.g., 0), it can determine that the cached data of the data type corresponding to that bit is not cached in the second MLD. For example, if the indication information includes two bits (bit 1 and bit 2), and the first MLD supports three data types (data type 1, data type 2, and data type 3), with bit 1 corresponding to data type 1 and bit 2 corresponding to data types 2 and 3, then if bit 1 has a value of 1, the first MLD can determine that the second MLD caches the cached data corresponding to data type 1; if bit 1 has a value of 0, it can determine that the second MLD does not cache the cached data corresponding to data type 1. If bit 2 is 1, the first MLD can be certain that the second MLD caches cached data corresponding to at least one of data types 2 or 3; if bit 2 is 0, the second MLD does not cache cached data corresponding to either data type 2 or data type 3. The first value being 1 and the second value being 0 are merely examples and do not constitute a limitation on the embodiments of this application. Optionally, the first value can be 0 and the second value can be 1.

[0256] It should be noted that when the second MLD only caches cached data corresponding to some of the data types supported by the first MLD, the bits in the indication information may only correspond to some of the data types supported by the first MLD. For example, when the first MLD supports three data types (data type 1, data type 2, and data type 3), and the second MLD caches cached data corresponding to data type 1 but not cached data corresponding to data types 2 and 3, the indication information may include the bits corresponding to data type 1, but not the bits corresponding to data types 2 and / or 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 indicates that the second MLD caches cached data corresponding to data type 1; if the bit corresponding to data type 1 in the indication information is 0, it indicates that the second MLD does not cache cached data corresponding to data type 1. Since the indication information does not include the bits corresponding to data types 2 and / or 3, the first MLD can determine that the second MLD does not cache cached data corresponding to data type 2 or data type 3.

[0257] In one implementation, the first MLD may have multiple sites; after the first MLD determines the caching status of the cached data corresponding to at least one supported data type in the second MLD, it can determine the working status of at least one of the multiple sites in the first MLD based on the caching status of the cached data corresponding to at least one data type in the second MLD; the working status may be an active state or a dormant state.

[0258] Specifically, the first MLD can determine the data type corresponding to the bit with a value of 1 in the indication information, and thus determine that the second MLD caches cached data of that data type. Then, the first MLD can determine the link mapped to the data type containing the cached data based on the mapping relationship between the supported data types and the links corresponding to the first MLD.

[0259] In one implementation, the first MLD can determine the working status of all stations corresponding to the links mapped to the data types containing cached data as active. For example, the cached data corresponding to data type 1 supported by the first MLD is cached in the second MLD. Data type 1 is mapped to links 1 and 2, and links 1 and 2 correspond to stations 1 and 2 in the first MLD, respectively. In this case, the first MLD can determine the working status of both stations 1 and 2 as active. While the stations in the second MLD remain active, determining the working status of the stations corresponding to the links mapped to the data types containing cached data (the stations in the first MLD) as active ensures that the links mapped to the data types containing cached data are active. Consequently, the second MLD can send the cached data to the first MLD through these links.

[0260] In this context, the link corresponding to the first MLD refers to the link between the first MLD and the second MLD. It should be noted that mapping data type 1 supported by the first MLD to link 1 means that the cached data corresponding to data type 1 is mapped to link 1, i.e., the cached data corresponding to data type 1 will be transmitted to the first MLD through link 1. Management frames can be mapped to one or more links, and a service type can be mapped to one or more links. Each link can be mapped to one or more service types, and can also be mapped to management frames. The mapping relationship between the service types supported by the first MLD (or the management frames to be sent to the first MLD) and the link corresponding to the first MLD can be determined through negotiation between the first MLD and the second MLD. For example, it can be determined during the connection establishment process between the first MLD and the second MLD. When the service type refers to TID, the mapping relationship between the service types supported by the first MLD and the link corresponding to the first MLD can be called TID-to-link mapping. When the service type refers to AC, the correspondence between the AC supported by the first MLD and the link corresponding to the first MLD can be determined based on the TID-to-link mapping and the correspondence between the AC and TID supported by the first MLD (i.e., AC-to-link mapping).

[0261] In another implementation, after the first MLD determines the link mapped to the data type containing cached data, it can identify the links that need to be converted to an active state based on the current power information of the first MLD. That is, it identifies the stations corresponding to the links mapped to the data type containing cached data that need to be converted to an active state. The power information may include, but is not limited to, one or more of the following: remaining power and whether it is in charging mode. For example, if the second MLD caches the AC_VO data supported by the first MLD, and AC_VO maps to links 1, 2, and 3, and the first MLD currently has low remaining power, then the first MLD can choose to determine the working state of some links in links 1, 2, and 3 as active, and the working state of another part of links in links 1, 2, and 3 as dormant. This ensures data reception and also helps reduce power consumption.

[0262] In another implementation, the first MLD can determine the links that need to be converted to an active state based on its service requirements information, within the links mapped to the data types containing cached data. For example, if the second MLD caches cached data corresponding to AC_VO and AC_VI supported by the first MLD, with AC_VO and AC_VI mapped to link 1 and link 2 respectively, and for the first MLD, the cached data corresponding to AC_VO has a higher priority than the cached data corresponding to AC_VI, then the first MLD can determine link 1 as active and link 2 as dormant, thus ensuring the reception of high-priority data. Similarly, if the second MLD caches management frames from the first MLD, as well as cached data corresponding to AC_VO supported by the first MLD, with management frames and AC_VO mapped to link 1 and link 2 respectively, and for the first MLD, the cached data corresponding to management frames has a higher priority than the cached data corresponding to AC_VO, then the first MLD can determine link 1 as active and link 2 as dormant, thus ensuring the reception of high-priority data.

[0263] In another implementation, the first MLD can determine which link needs to be converted to an active state based on its current battery level and service requirements, within the links mapped to the data type containing cached data. In the example above, if the first MLD has a high remaining battery level or is in charging mode, it can designate both link 1 and link 2 as active to receive data promptly. If the first MLD has a low remaining battery level and / or is not in charging mode, it can designate link 1 as active and link 2 as dormant to ensure the reception of high-priority data.

[0264] It should be noted that the service requirements of different devices may be the same or different. The above example, where the cached data corresponding to AC_VO has a higher priority than the cached data corresponding to AC_VI for the first MLD, is only for illustration and does not constitute a limitation on the embodiments of this application. In other cases or for other MLD devices, the cached data corresponding to AC_VO may have a lower priority than the cached data corresponding to AC_VI. By using at least one of power information and service requirement information, the working state of some links mapped to the data type with cached data can be determined as active, and the working state of the remaining links can be determined as dormant. This method helps to reduce power consumption.

[0265] It should also be noted that the higher priority of the cached data corresponding to the management frame compared to the cached data corresponding to AC_VO is merely an example and does not constitute a limitation on the embodiments of this application. This application does not limit the priority of the management frame or the cached data corresponding to each service type. Optionally, the priority of the cached data corresponding to the management frame may be higher than the priority of the cached data corresponding to all service types. Alternatively, the priority of the cached data corresponding to the management frame may be higher than the priority of the cached data corresponding to some service types. Alternatively, the priority of the cached data corresponding to the management frame may be lower than the priority of the cached data corresponding to any service type. In this application embodiment, the priority of the cached data corresponding to the management frame and the priority of the cached data corresponding to each service type can be determined by standard conventions or by negotiation between the first MLD and the second MLD; this application embodiment does not limit this.

[0266] In one implementation, when the second MLD does not cache any data of any data type mapped to a certain link, the operating state of that link is not limited in this embodiment. The first MLD can determine the operating state of the link as either a sleep state or an active state. For example, when the first MLD has a high remaining battery level or is in charging mode, the first MLD can determine that the operating state of the link is active. Conversely, when the first MLD has a low remaining battery level and / or is not in charging mode, the first MLD can determine that the operating state of the link is sleep mode. This approach helps reduce power consumption.

[0267] In this embodiment, the first MLD determines the working status of a link, which is equivalent to the first MLD determining that the station corresponding to that link in the first MLD has the same working status. In this embodiment, after the first MLD determines a station in an active state, it can send an indication message to the second MLD, which can indicate the active station. After receiving the indication message, the second MLD can determine the active link based on the active station. Furthermore, the second MLD can schedule cached data to the corresponding active link for transmission to the first MLD based on the mapping relationship between the data types supported by the first MLD and the links corresponding to the first MLD.

[0268] By implementing the embodiments of this application, the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD can be determined. Furthermore, based on the data type of the cached data, it is beneficial to determine a more suitable operating state for the site and to reduce power consumption.

[0269] Please see Figure 3a , Figure 3a This is a flowchart illustrating a method for determining data caching status according to an embodiment of this application. The method details how a first MLD determines the caching status of cached data corresponding to at least one data type in a second MLD based on first indication information and the correspondence between the first MLD's associated identifier and supported data types. Specifically, the execution subject of steps S301 to S303 is the second MLD or a chip within the second MLD, and the execution subject of step S304 is the first MLD or a chip within the first MLD. The following explanation uses the second MLD and the first MLD as examples of the execution subjects for determining the data caching status method. Figure 3a As shown, the method may include, but is not limited to, the following steps:

[0270] Step S301: The second MLD determines the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD.

[0271] It should be noted that the execution process of step S301 can be found in [reference needed]. Figure 2 The specific description of step S201 will not be repeated here.

[0272] Step S302: The second MLD determines the caching status of the cached data corresponding to the association identifier of the first MLD in the second MLD based on the caching status of the cached data corresponding to at least one data type supported by the first MLD in the second MLD, and the correspondence between the association identifier of the first MLD and the supported data types.

[0273] Specifically, after the second MLD determines the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD, it can combine the correspondence between the AID of the first MLD and the supported data types to determine the caching status of the cached data corresponding to the AID of the first MLD in the second MLD. In the embodiments of this application, the first MLD may have one or more associated identifiers (AIDs). One AID of the first MLD may correspond to one or more data types supported by the first MLD.

[0274] Table 3. Correspondence between AID and AC for the first MLD

[0275] AID AC AID0 AC_VO AID1 AC_VI AID2 AC_BK AID3 AC_BE

[0276] For example, taking the first MLD's supported data types including service types and management frames, with service type being AC, when the first MLD supports four ACs: AC_VO, AC_VI, AC_BK, and AC_BE, and the second MLD caches the management frame cache data of the first MLD, as well as the cached data corresponding to AC_VO and AC_VI supported by the first MLD, and the first MLD has five AIDs (AID0 to AID4), with AID4 corresponding to the first MLD's management frame, and the correspondence between the remaining AIDs and ACs of the first MLD is shown in Table 3, then the second MLD can be determined to have cached data corresponding to AID0, AID1, and AID4.

[0277] Step S303: The second MLD sends a first indication message to the first MLD; the first indication message is used to indicate the caching status of the cached data corresponding to the associated identifier of the first MLD in the second MLD.

[0278] After the second MLD determines the cached data corresponding to the AID of the first MLD in the second MLD, it can send a first indication message to the first MLD. Figure 2In the illustrated embodiment, each bit in the indication information sent from the second MLD to the first MLD can correspond to one or more data types supported by the first MLD, and the value of each bit can indicate whether the cached data of the data type corresponding to that bit is cached in the second MLD. In this embodiment, each bit in the first indication information sent from the second MLD to the first MLD can correspond to an AID of the first MLD. The value of each bit in the first indication information can indicate whether the cached data corresponding to the AID is cached in the second MLD. The first MLD can further determine the caching status of the cached data corresponding to at least one supported data type in the second MLD by combining the correspondence between the AID and the supported data types. The first indication information can be the TIM field in the beacon frame.

[0279] Step S304: The first MLD determines the caching status of cached data corresponding to at least one data type 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.

[0280] Specifically, after receiving the first indication information from the second MLD, the first MLD can determine the caching status of at least one data type in the second MLD based on the first indication information and the correspondence between the first MLD's Association Identifier (AID) and the data types supported by the first MLD. If a bit in the TIM field is 1 and corresponds to AID1, it indicates that the second MLD caches the data corresponding to AID1. If AID1 corresponds to data type 1 supported by the first MLD, it indicates that the second MLD caches the data corresponding to data type 1. If a bit in the TIM field is 0 and corresponds to AID2, it indicates that the second MLD does not cache the data corresponding to AID2. If AID2 corresponds to data type 2 supported by the first MLD, it indicates that the second MLD does not cache the data corresponding to data type 2.

[0281] The correspondence between the AID of the first MLD and the data types supported by the first MLD can be determined by the second indication information sent by the second MLD to the first MLD. The second indication information can be used to determine the correspondence between the AID of the first MLD and the data types supported by the first MLD, and can be included in the associated response frame. It should be noted that this application embodiment does not limit the order in which the second MLD sends the first and second indication information, nor does it limit the order in which the first MLD receives the first and second indication information. As long as the first MLD can determine the caching status of the cached data corresponding to at least one data type supported by the first MLD in the second MLD based on the first and second indication information, it is acceptable. Preferably, the second MLD can send the second indication information to the first MLD before sending the first indication information. Accordingly, for the first MLD, the reception time of the second indication information is earlier than the reception time of the first indication information.

[0282] In one implementation, the second indication information received by the first MLD can indicate at least one AID, and the at least one AID can correspond to at least one data type supported by the first MLD. For example, when the data type includes management frames and ACs, and the first MLD supports four types of ACs, the second indication information can include five AIDs, where one AID corresponds to a management frame, and the other four AIDs correspond to four ACs. It should be noted that the embodiments of this application do not limit the correspondence between the four ACs and the four AIDs in the second indication information. For example, when the four ACs are AC_VO, AC_VI, AC_BK, and AC_BE, and the four AIDs are AID0, AID1, AID2, and AID3, their correspondence can be as shown in Table 3 or Table 4.

[0283] Table 4. Correspondence between 4 AIDs and 4 ACs

[0284] AID AC AID0 AC_VI AID1 AC_VO AID2 AC_BE AID3 AC_BK

[0285] As shown in Table 3, the correspondence between the 4 AIDs and 4 ACs can be established one-to-one according to the size of the AID and the priority of the AC. As shown in Table 4, the correspondence between the 4 AIDs and 4 ACs can also be independent of the size of the AID and the priority of the AC. It should also be noted that the consecutiveness of the 4 AIDs in Tables 3 and 4 is merely an example and does not constitute a limitation on the embodiments of this application. In other feasible implementations, when the second indication information indicates multiple AIDs, these multiple AIDs can be consecutive or non-consecutive. In other words, the second MLD can arbitrarily select multiple AIDs from the available AID space and assign them to the first MLD. By indicating at least one AID corresponding to at least one data type supported by the first MLD through the second indication information, AIDs can be allocated to the first MLD more flexibly.

[0286] In one implementation, the first MLD can support multiple data types; the second indication information can indicate a first association identifier, which corresponds to a first data type among the multiple data types. The first MLD can determine the association identifiers corresponding to other data types among the multiple data types, excluding the first data type, based on the first association identifier corresponding to the first data type.

[0287] Taking data types including management frames and ACs as an example, if the first associated identifier indicated by the second indication information is AID0, and AID0 corresponds to the management frames supported by the first MLD, the first MLD can determine that AC_VO, AC_VI, AC_BK, and AC_BE correspond to AID0+1, AID0+2, AID0+3, and AID0+4 respectively, based on the priority of the supported management frames and various ACs. That is, the four ACs supported by the first MLD correspond to the four consecutive AIDs after AID0 indicated by the second indication information. Alternatively, AC_VO, AC_VI, AC_BE, and AC_BK can correspond to AID0+2, AID0+4, AID0+6, and AID0+8 respectively, meaning that the AIDs corresponding to the various data types supported by the first MLD may not be consecutive.

[0288] It should be noted that the first associated identifier indicated by the second indication information in the above example, AID0, and the correspondence between AID0 and the management frame, are merely examples and do not constitute a limitation on the embodiments of this application. For example, the first associated identifier indicated by the second indication information can be AID2, and AID1 corresponds to AC_VI among the four ACs supported by the first MLD. In this case, the first MLD can determine that the management frame, AC_VO, AC_BK, and AC_BE correspond to AID2+1, AID2+2, AID2+3, and AID2+4 respectively, based on the priority of the various supported data types. Alternatively, AC_VO corresponds to AID2-1, the management frame corresponds to AID2-2, and AC_BK and AC_BE correspond to AID2+1 and AID2+2 respectively. When an 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 AIDs corresponding to the other supported data types based on that AID. By indicating an AID in the second indication information, signaling overhead can be effectively saved.

[0289] In one implementation, when the second indication information indicates at least two AIDs, one of the at least two AIDs can correspond to the management frame, and the remaining AIDs correspond to the service types supported by the first MLD. By indicating the AID corresponding to the management frame and the AIDs corresponding to some of the service types supported by the first MLD through the second indication information, signaling overhead can be effectively saved, and the method by which the first MLD determines the AID corresponding to the management frame and the AIDs corresponding to each supported service type can be improved.

[0290] It should be noted that the second MLD can send second indication information to multiple first MLDs respectively, so as to assign different AIDs to each first MLD. In other words, different first MLDs have different AIDs. For example, when two first MLDs (first MLD-a and second MLD-b) both support management frames and four ACs (AC_VO (voice), AC_VI (video), AC_BE (best-effort), AC_BK (background)), the diagram of the management frames supported by first MLD-a and second MLD-b and the corresponding AIDs of each AC can be shown as follows. Figure 3b As shown. By Figure 3b It can be seen that the AID of the first MLD-a is AID0 to AID4, and the AID of the second MLD-b is AID5 to AID8, that is, the AID of the first MLD-a is different from the AID of the second MLD-b.

[0291] In one implementation, the number of AIDs allocated by the second MLD to the first MLD can be the same as the number of data types supported by the first MLD. When the first MLD adds supported data types, the second MLD then allocates new AIDs for those newly supported data types. This method avoids allocating unnecessary AIDs.

[0292] In one implementation, the second MLD can allocate one AID for one or more data types supported by the same first MLD. For example, when the first MLD supports data types such as management frames, AC_VO, AC_VI, AC_BE, and AC_BK, the second MLD can allocate one AID for management frames, AC_VO, and AC_VI, and another AID for AC_BE and AC_BK. Alternatively, the second MLD can allocate one AID for management frames, one AID for AC_VO, and another AID for AC_VI, AC_BE, and AC_BK. Or, the second MLD can allocate a different AID for management frames, AC_VO, and AC_VI, and another AID for AC_BE and AC_BK. By allocating the same AID for multiple data types, the number of AIDs allocated to the first MLD can be less than the number of data types supported by the first MLD. This effectively saves AIDs.

[0293] When the same AID is assigned to multiple data types, if the bit corresponding to that AID in the TIM field is 1, it indicates that the second MLD caches some or all of the data types corresponding to that AID. If the bit corresponding to that AID in the TIM field is 0, it indicates that the second MLD does not cache any data type corresponding to that AID.

[0294] In one implementation, after the first MLD determines the caching status of cached data of at least one supported data type in the second MLD, it can determine the working status of at least one of the multiple sites supported by the first MLD based on the caching status of the cached data of at least one data type in the second MLD. In another implementation, the first MLD can determine the working status of at least one of the multiple sites supported by the first MLD based on at least one of its current power information or service demand information, and the caching status of cached data of at least one data type in the second MLD. The execution process can be found in [reference needed]. Figure 2 The specific description of step S203 will not be repeated here.

[0295] By implementing the embodiments of this application, the caching status of cached data corresponding to at least one data type in the second MLD can be determined based on the first indication information and the correspondence between the association identifier of the first MLD and the supported data types. Furthermore, by determining the data type of the cached data, it is beneficial to identify a more suitable operating state for the site and to reduce power consumption.

[0296] Please see Figure 4a , Figure 4a This is a flowchart illustrating another method for determining data caching status provided in this application embodiment. The method details how a second MLD determines whether it caches at least one type of second data type of data, and how a first MLD determines whether it caches at least one type of second data type of data based on third indication information from the second MLD. The execution subject of steps S401 to S402 is the second MLD or a chip within the second MLD, and the execution subject of step S403 is the first MLD or a chip within the first MLD. The following explanation uses the second MLD and the first MLD as examples of the execution subjects for determining data caching status. This method may include, but is not limited to, the following steps:

[0297] Step S401: The second multi-link device MLD determines whether there is cached data corresponding to at least one second data type in the second MLD; the second data type is any data type mapped to the first link.

[0298] In this embodiment, a link can be mapped to one or more data types, and a data type can be mapped to one or more links. Cached data corresponding to each data type mapped to a certain link can be transmitted through that link. If the second MLD caches cached data corresponding to at least one second data type, it indicates that the cached data in the second MLD may be transmitted to the first MLD through the first link. If the second MLD does not cache cached data corresponding to any second data type, it indicates that the cached data corresponding to each data type mapped to the first link has been sent; in other words, the cached data in the second MLD will not be transmitted to the first MLD through the first link. By determining whether the second MLD caches cached data corresponding to at least one second data type, the second MLD can determine whether there is cached data that may be transmitted to the first MLD through the first link. Here, the first link is a link between the first MLD and the second MLD.

[0299] Step S402: The second MLD sends cached data to the first MLD through the first link. The cached data includes third indication information. The third indication information is used to indicate whether the second MLD has cached data corresponding to at least one second data type.

[0300] In this embodiment, third indication information can be carried in the cached data transmitted through the first link to indicate whether there is cached data that may be transmitted to the first MLD through the first link. It should be noted that determining whether the second MLD has cached data corresponding to at least one second data type means whether the second MLD has cached data corresponding to at least one second data type, excluding the cached data to which the third indication information belongs.

[0301] For example, if data type 'a' and data type 'b' are mapped on link 1, when the second MLD sends cached data to the first MLD via link 1, if the second MLD caches cached data corresponding to data type 'a' or cached data corresponding to data type 'b', it indicates that cached data may be transmitted to the first MLD via link 1. If the second MLD does not cache either data corresponding to data type 'a' or data corresponding to data type 'b', it indicates that no cached data will be transmitted to the first MLD via link 1.

[0302] It should also be noted that each cached data sent by the second MLD to the first MLD through the first link carries third indication information. The third indication information carried in each cached data is used to indicate whether the second MLD has cached data corresponding to at least one second data type.

[0303] The MAC frame structure of the cached data includes a Frame Control field, which includes a More Data subfield, each with a length of 1 bit. In this embodiment, the third indication information may refer to the More Data subfield in the cached data. Specifically, when the second MLD sends cached data to the first MLD via the first link, if the second MLD caches at least one cached data corresponding to a second data type, the value of the More Data subfield in that cached data can be 1. If the second MLD does not cache any cached data corresponding to any second data type, the value of the More Data subfield in that cached data can be 0. It should be noted that the third indication information referring to the More Data subfield in the cached data is only for illustrative purposes and does not constitute a limitation on the embodiments of this application. In other feasible implementations, the third indication information may be other fields in the MAC frame structure of the cached data.

[0304] Step S403: The first MLD determines, based on the third instruction information, whether the second MLD caches at least one cached data corresponding to a second data type.

[0305] Specifically, after the first MLD receives cached data from the second MLD via the first link, it can determine whether the second MLD caches at least one type of cached data corresponding to a second data type based on the third indication information in the cached data. When the third indication information refers to the More Data subfield in the cached data, if the value of the More Data subfield in the cached data is 1, the first MLD can determine that the second MLD caches at least one type of cached data corresponding to a second data type. If the value of the More Data subfield in the cached data is 0, the first MLD can determine that the second MLD does not cache any type of cached data corresponding to a second data type. For example, when the data types mapped on the first link include management frames and AC_VO, if the value of the More Data subfield in the cached data received by the first MLD via the first link is 1, it indicates that at least one type of cached data, namely the cached data corresponding to management frames and the cached data corresponding to AC_VO, will be transmitted to the first MLD via the first link. If the More Data subfield in the cached data received by the first MLD through the first link is 0, it means that no cached data corresponding to the management frame will be transmitted to the first MLD through the first link, nor will any cached data corresponding to AC_VO be transmitted to the first MLD through the first link.

[0306] In one implementation, the first MLD may have multiple sites; after the first MLD determines whether the second MLD caches at least one cached data corresponding to a second data type, it can determine the working status of the site corresponding to the first link among the multiple sites of the first MLD based on whether the second MLD caches at least one cached data corresponding to a second data type.

[0307] In one implementation, if the second MLD caches at least one cached data corresponding to a second data type, i.e., the More Data subfield is 1, then the first MLD can determine that the working status of the site corresponding to the first link is active; if the second MLD does not cache any cached data corresponding to any second data type, i.e., the More Data subfield is 0, then the first MLD can determine that the working status of the site corresponding to the first link is active or dormant.

[0308] In existing technology, the second MLD may include multiple cache areas, with each cache area corresponding to a link. Cache data cached in different cache areas is transmitted to the first MLD through different links. The More Data subfield in the cache data indicates whether the cache area corresponding to the link transmitting the cache data contains cached data. If the cache area corresponding to the link used to transmit the cache data (such as link 1) does not contain cached data, the More Data subfield in the cache data is set to 0. Accordingly, the first MLD can determine the working status of the station corresponding to link 1 as a dormant state. However, if link congestion or interference occurs on other links (such as link 2), causing the first MLD to be unable to receive cached data through link 2, the cached data originally transmitted through link 2 cannot be scheduled to be transmitted through link 1 because link 1 is in a dormant state.

[0309] However, in this embodiment, if the data type of the cached data originally transmitted via link 2 is also mapped to link 1 (i.e., the first link), then before the cached data corresponding to that data type is completely sent, the first MLD will not determine the working state of the station corresponding to link 1 as a dormant state; that is, link 1 will not be in a dormant state. Therefore, the second MLD can schedule the cached data corresponding to that data type (including the cached data originally transmitted via link 2) to link 1 for transmission. By implementing this embodiment, it is beneficial to determine a more suitable working state for the station and to successfully send the cached data in the second MLD to the first MLD.

[0310] In another implementation, the first MLD can determine the working status of the site corresponding to the first link among the multiple sites owned by the first MLD based on at least one of its current power information or service demand information, and whether the second MLD caches cached data corresponding to at least one second data type. The execution process can be found in [reference needed]. Figure 2 The specific description of step S203 will not be repeated here.

[0311] In one implementation, if the third indication information indicates that the second MLD caches at least one cached data corresponding to a second data type, the second MLD can send a fourth indication information to the first MLD. This fourth indication information indicates that the second MLD does not cache any cached data corresponding to any second data type. Upon receiving this fourth indication information, the first MLD can determine that the second MLD does not cache any cached data corresponding to any second data type. That is, after receiving the fourth indication information, the first MLD can determine that no cached data will subsequently be transmitted through the first link.

[0312] by Figure 4bTaking the scenario diagram of the second MLD sending cached data to the first MLD 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 and link 2, and link 1 is mapped to data type a and data type b, while link 2 is mapped to data type b. Figure 4b The white-filled squares represent cached data corresponding to data type a, and the gray-filled squares represent cached data corresponding to data type b. The numbers in the squares are used to uniquely identify a cached data. Figure 4b In the sequence, the last buffered data transmitted on link 1 is buffered data 2, and the last buffered data transmitted on link 2 is buffered data 4. Figure 4b It can be seen that when the second MLD sends cached data 2 to the first MLD via link 1, since the second MLD caches cached data 4, and link 1 maps to the data type b to which cached data 4 belongs, the second MLD can set the value of the More Data subfield in cached data 2 to 1.

[0313] Since data type b is mapped to both Link 1 and Link 2, cached data 4 can be transmitted via either Link 1 or Link 2. If the second MLD subsequently sends cached data 4 to the first MLD via Link 2, at this point, since the cached data corresponding to data types a and b mapped to Link 1 has been completely sent, the second MLD cannot send cached data to the first MLD via Link 1. Furthermore, the "More Data" subfield in the cached data cannot indicate that the second MLD has neither cached data corresponding to data type a nor cached data corresponding to data type b. In other words, the "More Data" subfield in the cached data cannot indicate that no further cached data will be transmitted to the first MLD via Link 1.

[0314] At this point, the second MLD can resolve the aforementioned problem by sending a fourth indication message to the first MLD. The fourth indication message indicates that the second MLD does not cache any cached data corresponding to any data type mapped to Link 1; that is, the fourth indication message indicates that the second MLD does not cache either data type a or data type b.

[0315] In one implementation, the fourth indication information can be a QoS Null frame, which is a data frame without a payload, and the More Data subfield in the QoS Null frame has a value of 0. The second MLD can send the QoS Null frame to the first MLD via the first link.

[0316] In one implementation, after receiving the fourth indication information from the second MLD, the first MLD can determine the operating state of the station corresponding to the first link as a sleep state based on the fourth indication information. This helps reduce power consumption. In another implementation, the first MLD can determine the operating state of the station corresponding to the first link based on at least one of the current power information or service demand information, and the fourth indication information. For example, after receiving the fourth indication information from the second MLD, if the first MLD's current remaining power is low, and / or the first MLD is not in charging mode, the operating state of the station corresponding to the first link can be determined as a sleep state. If the first MLD's current remaining power is high or the first MLD is in charging mode, the operating state of the station corresponding to the first link can be determined as an active state.

[0317] In one implementation, when the second MLD sends cached data (such as cached data 1) to the first MLD via the first link, if the second MLD also caches at least one cached data corresponding to a second data type besides cached data 1, the second MLD can set the value of the More Data subfield in cached data 1 to 0. After receiving cached data 1, the first MLD can set the station corresponding to link 1 that transmits cached data 1 to a dormant state, and correspondingly, link 1 also enters a dormant state. After receiving the link status indication information sent by the first MLD indicating that link 1 is in an active state, the second MLD can send data through link 1. Before receiving the link status indication information sent by the first MLD indicating that link 1 is in an active state, the second MLD can choose not to send data through link 1. In this way, when it is uncertain whether link 1 is in an active state, the second MLD can avoid scheduling cached data that would normally be transmitted through other links to be transmitted through link 1, which helps to avoid unnecessary overhead. The link status indication information indicating that link 1 is in an active state can be a power saving poll (PS-Poll) frame. PS-Poll frames can be used to indicate that a link is active.

[0318] It should be noted that the second MLD sends cached data to the first MLD via the first link (i.e., step S402) when it is determined that the first link is active. The first MLD can send a PS-Poll frame to the second MLD to indicate that the first link is active. The first MLD can determine that the first link is active when it is determined that the second MLD has cached data that needs to be transmitted via the first link, and then send a PS-Poll frame to the second MLD to indicate that the first link is active. In one implementation, the second MLD can send a beacon frame (as in the prior art) to the first MLD. The TIM field in this beacon frame is used to indicate the cache status of cached data at each station of the first MLD in the second MLD. Based on the TIM field and the correspondence between the link and the stations of the first MLD, the first MLD can determine whether the second MLD has cached data that needs to be transmitted via the first link.

[0319] In another implementation, the second MLD can send to the first MLD. Figure 3a In the illustrated embodiment, the first indication information allows the first MLD to determine the caching status of at least one data type corresponding to cached data in the second MLD based on this first indication information and the correspondence between the first MLD's associated identifier and the data types it supports. Furthermore, based on the caching status of at least one data type corresponding to cached data in the second MLD and the mapping relationship between the data types supported by the first MLD and the link, it is determined whether the second MLD caches cached data that needs to be transmitted through the first link. The execution process can be found in [reference needed]. Figure 5 The illustrated embodiment.

[0320] By implementing the embodiments of this application, it can be determined whether the second MLD contains cached data corresponding to at least one second data type based on the third indication information. Furthermore, determining whether the second MLD contains cached data corresponding to at least one second data type helps in determining a more suitable working state for the site and facilitates the successful transmission of cached data from the second MLD to the first MLD.

[0321] Please see Figure 5 , Figure 5This is a flowchart illustrating another method for determining data caching status provided in this application embodiment. In steps S501-S503, S507, and S508, the executing entity is the second MLD or a chip within the second MLD. Steps S504-S506 and S509 are executed by the first MLD or a chip within the first MLD. The following description uses the second MLD and first MLD as examples of the executing entities for determining data caching status. This method may include, but is not limited to, the following steps:

[0322] Step S501: The second MLD determines the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD.

[0323] Step S502: The second MLD determines the caching status of the cached data corresponding to the association identifier of the first MLD in the second MLD based on the caching status of the cached data corresponding to at least one data type supported by the first MLD in the second MLD, and the correspondence between the association identifier of the first MLD and the supported data types.

[0324] Step S503: The second MLD sends a first indication message to the first MLD; the first indication message is used to indicate the caching status of the cached data corresponding to the associated identifier of the first MLD in the second MLD.

[0325] Step S504: The first MLD determines the caching status of cached data corresponding to at least one data type in the second MLD based on the first instruction information and the correspondence between the association identifier of the first MLD and the data types supported by the first MLD.

[0326] It should be noted that the execution process of steps S501 to S504 can be found in the following references: Figure 3a The specific descriptions of steps S301 to S304 are not repeated here.

[0327] Step S505: The first MLD determines that the working status of the site corresponding to the first link is active based on the caching status of cached data corresponding to at least one data type in the second MLD, and the mapping relationship between the data types supported by the first MLD and the link corresponding to the first MLD.

[0328] Specifically, the first MLD, based on the caching status of cached data corresponding to at least one data type in the second MLD, and the mapping relationship between the data types supported by the first MLD and the links corresponding to the first MLD, can determine the links mapped to the data types with cached data. If the links mapped to the data types with cached data include the first link, then the first MLD can determine that the working status of the site corresponding to the first link is active.

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

[0330] After the first MLD determines that the station corresponding to the first link is active, it can confirm that the first link itself is active. If the first link is active, it sends link status indication information to the second MLD. This link status indication information can be a PS-Poll frame. In one implementation, the link status indication information can be sent from the first link to the second MLD.

[0331] Step S507: The second MLD determines whether it caches at least one type of second data type; the second data type is any data type mapped to the first link.

[0332] After receiving the link status indication information, the second MLD can determine that the first link is active. If the first link is active, it can send buffered data carrying the third indication information to the first MLD via the first link.

[0333] Step S508: The second MLD sends cached data to the first MLD through the first link. The cached data includes third indication information. The third indication information is used to indicate whether the second MLD has cached data corresponding to at least one second data type.

[0334] Step S509: The first MLD determines whether the second MLD caches at least one cached data corresponding to a second data type based on the third instruction information.

[0335] It should be noted that the execution process of steps S507 to S509 can be found in the following references: Figure 4a The specific descriptions of steps S401 to S403 are not repeated here.

[0336] In this embodiment, the first MLD can determine that the station corresponding to the first link is in an active state based on the caching status of cached data corresponding to at least one data type in the second MLD, and the 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 the link status indication information from the first MLD. And if it is determined that the first link is in an active state, it sends cached data carrying third indication information to the first MLD through the first link.

[0337] Please see Figure 6a , Figure 6a This is a flowchart illustrating another method for determining data caching status provided in this application embodiment. The method details how a first MLD determines, based on fifth indication information, whether a second MLD caches cached data corresponding to a third data type. Specifically, the execution subject of steps S601 to S602 is the second MLD or a chip within the second MLD, and the execution subject of step S603 is the first MLD or a chip within the first MLD. The following explanation uses the second MLD and the first MLD as examples of the execution subjects for determining data caching status. This method may include, but is not limited to, the following steps:

[0338] Step S601: The second multi-link device MLD determines whether there is cached data corresponding to the third data type in the second MLD.

[0339] In this embodiment, a data type can be mapped to one or more links. Cache data corresponding to the data type cached in the second MLD can be transmitted to the first MLD through any link mapped to that data type. For example, when the first MLD supports data type 'a', and the links between the first MLD and the second MLD include link 1, link 2, and link 3, and data type 'a' is mapped to link 1, link 2, and link 3, the cache data corresponding to data type 'a' can be transmitted to the first MLD through one or more of the links 1, link 2, and link 3.

[0340] The second MLD determines whether it caches data corresponding to the third data type, which is equivalent to determining whether the cached data corresponding to the third data type in the second MLD has been completely sent. If the second MLD caches data corresponding to the third data type, it means that the cached data for that data type has not been completely sent. If the second MLD does not cache data corresponding to the third data type, it means that the cached data for that data type has been completely sent.

[0341] Step S602: The second MLD sends cached data corresponding to the third data type to the first MLD. The cached data includes fifth indication information, which is used to indicate whether the second MLD has cached data corresponding to the third data type.

[0342] In this embodiment, a fifth indication information can be carried in the cached data corresponding to the third data type to indicate whether the second MLD has cached the corresponding third data type (i.e., whether the cached data corresponding to the third data type has been completely sent). It should be noted that the second MLD determining whether it has cached the corresponding third data type means: excluding the cached data containing the fifth indication information, whether the second MLD has cached the corresponding third data type. It should also be noted that each cached data sent by the second MLD to the first MLD carries the fifth indication information, which is used to indicate whether the second MLD has cached the cached data corresponding to the data type to which the cached data belongs.

[0343] In one implementation, the fifth indication information can refer to the More Data subfield in the cached data. Specifically, when the second MLD sends cached data corresponding to the third data type (such as cached data 1) to the first MLD, if the second MLD caches cached data corresponding to the third data type, the value of the More Data subfield in cached data 1 can be 1. If the second MLD does not cache cached data corresponding to the third data type, the value of the More Data subfield in cached data 1 can be 0. It should be noted that the fifth indication information referring to the More Data subfield in the cached data is only for example and does not constitute a limitation on the embodiments of this application. In other feasible implementations, the fifth indication information can be other fields in the MAC frame structure of the cached data.

[0344] Step S603: The first MLD determines whether the second MLD has cached data corresponding to the third data type based on the fifth instruction information.

[0345] Specifically, after the first MLD receives the cached data corresponding to the third data type from the second MLD, it can determine whether the second MLD caches the cached data corresponding to the third data type based on the fifth indication information in the cached data. When the fifth indication information points to the More Data subfield in the cached data, if the value of the More Data subfield in the cached data is 1, the first MLD can determine that the second MLD caches the cached data corresponding to the third data type. If the value of the More Data subfield in the cached data is 0, the first MLD can determine that the second MLD does not cache the cached data corresponding to the third data type.

[0346] In one implementation, the first MLD can have multiple stations. After determining whether the second MLD caches data corresponding to the third data type, the first MLD can determine the working status of the station corresponding to the second link among the multiple stations of the first MLD based on whether the second MLD caches such data. The third data type is mapped to this second link. For example, if the second MLD caches data corresponding to the third data type, meaning the cached data corresponding to the third data type has not been completely sent, the first MLD can determine that the working status of the station corresponding to the second link is active, so that the unsent cached data corresponding to the third data type can be transmitted to the first MLD through the second link. The number of second links can be one or more.

[0347] In another implementation, the first MLD can determine the working status of the site corresponding to the second link among the multiple sites owned by the first MLD based on at least one of its current power information or service demand information, and whether the second MLD caches cached data corresponding to the third data type. The execution process can be found in [reference needed]. Figure 2 The specific description of step S203 will not be repeated here.

[0348] In another implementation, after the first MLD determines whether the second MLD caches data corresponding to the third data type, it can determine whether the second link maps to other data types besides the third data type. Based on whether the second MLD caches data corresponding to the third data type and whether the second link maps to other data types, the first MLD determines the operating state of the station corresponding to the second link among its multiple stations. Specifically, if the second MLD does not cache data corresponding to the third data type, but the second link maps to other data types besides the third data type (meaning cached data corresponding to other data types mapped to the second link may be transmitted through this second link), the first MLD can determine that the station corresponding to the second link is in an active state. If the second MLD does not cache data corresponding to the third data type, and the second link does not map to other data types besides the third data type (meaning no cached data will be transmitted through the second link), the first MLD can determine that the station corresponding to the second link is in a dormant state. This approach helps determine a more suitable operating state for the stations in the first MLD and reduces power consumption.

[0349] by Figure 6b Taking the schematic diagram of the scenario for determining the working status of the link 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. Link 1 is mapped to data type a and data type b, link 2 is mapped to data type b, and link 3 is mapped to data type b. Figure 6b The white-filled squares represent cached data corresponding to data type a, and the gray-filled squares represent cached data corresponding to data type b. The numbers in the squares are used to uniquely identify a cached data. Figure 6b In the above, the last cached data transmitted on link 1 is cached data a2, the last cached data transmitted on link 2 is cached data b4, and the last cached data transmitted on link 3 is cached data b2.

[0350] As shown in 6b, the last cached data (a2) corresponding to data type 'a' cached in the second MLD is sent via link 1, and the last cached data (b4) corresponding to data type 'b' cached in the second MLD is sent via link 2. Therefore, the value of the "More Data" subfield in cached data a2 is 0, indicating that before sending cached data a2, the second MLD cached data corresponding to data type 'a', and after sending cached data a2, the second MLD no longer cached data corresponding to data type 'a'. Similarly, the value of the "More Data" subfield in cached data b4 is 0, indicating that before sending cached data b4, the second MLD cached data corresponding to data type 'b', and after sending cached data b4, the second MLD no longer cached data corresponding to data type 'b'.

[0351] Since links 2 and 3 are only mapped to data type b, meaning they are only used to transmit cached data corresponding to data type b, the first MLD, upon receiving b4, can determine the working state of both the station corresponding to link 2 and the station corresponding to link 3 as a sleep state (i.e., determine links 2 and 3 as sleep states), which helps reduce power consumption. Furthermore, upon receiving a2, since the last cached data corresponding to data type a (i.e., a2) and the last cached data corresponding to data type b (i.e., b4) mapped to link 1 are both sent to the first MLD, the first MLD can determine the working state of the station corresponding to link 1 as a sleep state (i.e., determine link 1 as a sleep state).

[0352] If the More Data subfield in the cached data is used to indicate whether there is cached data in the second MLD that needs to be sent to the first MLD, then in Figure 6b In this configuration, links 1, 2, and 3 can only switch to a sleep state after the first MLD receives the last buffer unit (i.e., a2) sent by the second MLD. In other words, if the second MLD still has buffered data to be sent to the first MLD, none of links 1, 2, or 3 can switch to a sleep state. Therefore, compared to the More Data subfield in the buffered data, which indicates whether the second MLD has buffered data to be sent to the first MLD, by implementing the embodiments of this application, some links between the first and second MLDs can be put into a sleep state even when the second MLD still has buffered data to be sent to the first MLD. Correspondingly, the stations in the first MLD corresponding to the links in a sleep state are also in a sleep state, which helps to reduce power consumption.

[0353] Through the fifth indication information in cached data 1, the first MLD can determine whether the second MLD has cached data corresponding to the third data type. However, the first MLD cannot determine the caching status of other data types in the second MLD. In one implementation, the cached data corresponding to the third data type received by the first MLD from the second MLD may further include a sixth indication information. This sixth indication information can be used to indicate whether the second MLD has cached data corresponding to at least one fourth data type; the fourth data type is any data type other than the third data type supported by the first MLD. If the fifth indication information indicates that the second MLD does not have cached data corresponding to the third data type, that is, if the cached data corresponding to the third data type has been sent, the sixth indication information can indicate whether the second MLD has cached data to be sent to the first MLD.

[0354] In one implementation, if the fifth indication information in the cached data corresponding to the third data type indicates that the second MLD does not cache the corresponding data type, the cached data corresponding to the third data type may also include a sixth indication information. If the fifth indication information in the cached data corresponding to the third data type indicates that the second MLD caches the corresponding data type, the cached data corresponding to the third data type may not include the sixth indication information.

[0355] In one implementation, the sixth indication information can refer to the "MoreFragment" subfield in the cached data. Specifically, when the second MLD sends cached data corresponding to a third data type (such as cached data 1) to the first MLD, and the value of the More Data subfield in cached data 1 is 0 (i.e., the cached data corresponding to the third data type has been sent), if the second MLD has cached data corresponding to at least one fourth data type, the value of the More Fragment subfield in cached data 1 can be 1. If the second MLD has not cached any cached data corresponding to any fourth data type, the value of the More Fragment subfield in cached data 1 can be 0. It should be noted that the sixth indication information referring to the More Fragment subfield in the cached data is only for example and does not constitute a limitation on the embodiments of this application. In other feasible implementations, the sixth indication information can be other fields in the MAC frame structure of the cached data. When the first MLD receives cached data 1, and the values ​​of both the More Data subfield and the More Fragment subfield in cached data 1 are 0, it can be indicated that the second MLD has not cached any cached data to be sent to the first MLD. At this point, the first MLD can put all links between itself and the second MLD into a sleep state to reduce power consumption. For example, when the data types supported by the first MLD include management frames and AC_VO, if the More Data subfield in the buffered data corresponding to AC_VO received by the first MLD has a value of 0, and the More Fragment subfield has a value of 0, it means that the buffered data corresponding to AC_VO and the buffered data corresponding to the management frame have been sent.

[0356] In one implementation, the priority of the aforementioned fourth data type can be higher than that of the third data type. In this case, the sixth indication information is used to indicate whether the second MLD caches cached data corresponding to a data type with a higher priority than the third data type. When only one data type (such as data type 1) among the data types supported by the first MLD has a higher priority than the third data type, the sixth indication information can indirectly indicate whether the second MLD caches cached data corresponding to data type 1. When at least two data types among the data types supported by the first MLD have a higher priority than the third data type, if the sixth indication information indicates that the second MLD does not cache cached data corresponding to a data type with a higher priority than the third data type, it can be said that the second MLD does not cache cached data corresponding to the aforementioned at least two data types. Therefore, through the sixth indication information, the second MLD can indicate more detailed caching information to the first MLD, which is beneficial for determining a more suitable operating state for the stations in the first MLD and for reducing power consumption.

[0357] In one implementation, the second MLD can determine that it does not cache data corresponding to a fifth data type, where the fifth data type is any data type supported by the first MLD; and sends a seventh indication message to the first MLD, which indicates that the second MLD does not cache data corresponding to the fifth data type. After receiving the seventh indication message, the first MLD can determine, based on the seventh indication message, that the second MLD does not cache data corresponding to the fifth data type.

[0358] When the second MLD does not cache data corresponding to one or more data types (such as data type c) supported by the first MLD, the second MLD cannot send cached data corresponding to data type c to itself, nor can it use the "More Data" subfield in the cached data corresponding to data type c to indicate that the second MLD does not cache cached data corresponding to data type c. In other words, the first MLD cannot know that the second MLD does not cache cached data corresponding to data type c. This causes the first MLD to be unable to determine whether it can switch the site corresponding to the link mapped to data type c to a dormant state. In this case, if the seventh indication information received by the first MLD can indicate that the second MLD does not cache cached data corresponding to data type c, the above problem can be solved.

[0359] by Figure 6c Taking the schematic diagram of a scenario showing the working state of a determined link as an example, compared to... Figure 6b , Figure 6c The first MLD in the code adds supported data type c, and data type c maps to link 3. (By...) Figure 6c It is known that the last cached data corresponding to data type b in the second MLD is b4. Since link 2 only maps to data type b, while link 3 maps to both data type b and data type c, the first MLD, after receiving b4, can determine the working state of the station corresponding to link 2 as dormant, but cannot determine whether it can determine the working state of the station corresponding to link 3 as dormant. In one implementation, if the first MLD receives a seventh indication message after receiving b4, indicating that the second MLD does not cache data corresponding to data type c, then the first MLD, after receiving this seventh indication message, can determine the working state of the station corresponding to link 3 as dormant. It should be noted that... Figure 6c In this example, the second MLD sending the seventh instruction information after b4 is merely illustrative and does not constitute a limitation of this application. The second MLD may also send the seventh instruction information before b4, or send b4 and the seventh instruction information simultaneously.

[0360] In one implementation, the seventh indication information can be a QoS Null frame, which is a data frame without a payload, and the More Data subfield in the QoS Null frame has a value of 0. In this embodiment, the fifth data type indicated by the QoS Null frame can be determined through the data type indication field in the QoS Null frame. For example, if the TID indicated by the data type indication field in the QoS Null frame includes TID8 to TID15, then the fifth data type indicated by the QoS Null frame can be determined to be a management frame. If the TID indicated by the data type indication field in the QoS Null frame is TID1, then the fifth data type indicated by the QoS Null frame can be determined to be TID1. It should be noted that... Figure 6c In this example, the second MLD sending a QoS Null frame to the first MLD via link 3 is merely illustrative and does not constitute a limitation of this application. The second MLD can send a QoS Null frame to the first MLD via any link between the first MLD and the second MLD.

[0361] In one implementation, the second MLD determines that it does not cache any cached data corresponding to any data type mapped to the fourth link, and sends an eighth indication message to the first MLD via the fourth link. This eighth indication message indicates that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link. After receiving the eighth indication message, the first MLD can determine, based on the eighth indication message, that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link. The execution process can be found in [reference needed]. Figure 8 The specific descriptions of the embodiments shown are not repeated here.

[0362] by Figure 6d Taking the schematic diagram of a scenario showing the working state of a determined link as an example, compared to... Figure 6b , Figure 6d The first MLD in the code adds supported data types c and d, and both data types c and d are mapped to link 3. Figure 6dIt is known that the last cached data corresponding to data type b cached in the second MLD is b4. Since link 2 only maps to data type b, while link 3 maps to data types c and d in addition to data type b, the first MLD, after receiving b4, can determine the working state of the station corresponding to link 2 as dormant, but cannot determine whether it can determine the working state of the station corresponding to link 3 as dormant. In one implementation, if the first MLD, after receiving b4, receives an eighth indication message through link 3 indicating that the second MLD does not cache any cached data corresponding to any data type mapped to link 3 (i.e., the fourth link), then the first MLD, after receiving the eighth indication message, can determine the working state of the station corresponding to link 3 as dormant.

[0363] It should be noted that when the second MLD sends the cached data corresponding to the third data type to the first MLD, the cached data can be sent through any link mapped to the third data type. The second MLD needs to determine that at least one link mapped to the third data type is active before sending the cached data corresponding to the third data type to the first MLD via an active link (e.g., link 1) (i.e., step S602). The first MLD can send a PS-Poll frame to the second MLD to indicate that link 1 is active. The first MLD can determine the working state of link 1 as active and send a PS-Poll frame to the second MLD to indicate that link 1 is active if it determines that the second MLD has cached data corresponding to the third data type mapped to link 1. In one implementation, the second MLD can send... Figure 3a In the embodiment shown, the first indication information allows the first MLD to determine that the second MLD caches cached data corresponding to the third data type mapped to link 1 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.

[0364] By implementing the embodiments of this application, it is possible to determine whether the second MLD caches cached data corresponding to the third data type based on the fifth indication information in the cached data corresponding to the third data type. Furthermore, determining whether the second MLD caches cached data corresponding to the third data type is beneficial for determining a more suitable operating state for the stations in the first MLD and for reducing power consumption.

[0365] Please see Figure 7 , Figure 7This is a flowchart illustrating another method for determining data caching status provided in this application embodiment. In step S701 to S702, the executing entity is the second MLD, or a chip within the second MLD; in step S703, the executing entity is the first MLD, or a chip within the first MLD. The following explanation uses the second MLD and the first MLD as examples of the executing entities for determining the data caching status method. This method may include, but is not limited to, the following steps:

[0366] Step S701: The second MLD determines that it does not cache data corresponding to the fifth data type, where the fifth data type is any data type supported by the first MLD.

[0367] Step S702: The second MLD sends a seventh indication message to the first MLD, which indicates that the second MLD does not have cached data corresponding to the fifth data type.

[0368] Step S703: The first MLD determines, based on the seventh instruction information, that the second MLD does not cache the cached data corresponding to the fifth data type.

[0369] It should be noted that the execution process of steps S701 to S703 can be found in [reference needed]. Figure 6a The specific description of step S603 will not be repeated here.

[0370] In one implementation, the first MLD can have multiple sites. After determining that the second MLD does not cache data corresponding to the fifth data type, the first MLD can determine the working status of the site corresponding to the third link among the multiple sites of the first MLD, based on the absence of cached data corresponding to the fifth data type in the second MLD. The fifth data type is mapped to the third link. For example, based on the absence of cached data corresponding to the fifth data type in the second MLD, the first MLD can determine the working status of the site corresponding to the third link as a dormant state.

[0371] In one implementation, the first MLD can determine the working status of the station corresponding to the third link among the multiple stations it has based on one or more of the relevant information and the fact that the second MLD does not cache the cached data corresponding to the fifth data type. The relevant information may include, but is not limited to: the current power information of the first MLD, the service requirement information of the first MLD, whether the third link maps to data types other than the fifth data type, the priority of the fifth data type, and the priority of other data types mapped to the third link (if the third link maps to other data types besides the fifth data type).

[0372] By implementing the embodiments of this application, it can be determined, based on the seventh instruction information, that the second MLD does not cache cached data corresponding to the fifth data type.

[0373] Please see Figure 8 , Figure 8 This is a flowchart illustrating another method for determining data caching status provided in this application embodiment. In step S801 to S802, the executing entity is the second MLD, or a chip within the second MLD; in step S803, the executing entity is the first MLD, or a chip within the first MLD. The following explanation uses the second MLD and the first MLD as examples of the executing entities for determining the data caching status method. This method may include, but is not limited to, the following steps:

[0374] Step S801: The second MLD determines that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0375] If the second MLD does not cache any data corresponding to any data type mapped to the fourth link, it indicates that the second MLD will not send data to the first MLD via the fourth link. For example, if the fourth link is link 1, and link 1 is mapped to data type a and data type b, and the second MLD does not cache either data corresponding to data type a or data type b, then it can be determined that the second MLD does not cache any data corresponding to any data type mapped to link 1 (i.e., the fourth link).

[0376] Step S802: The second MLD sends an eighth indication message to the first MLD through the fourth link. The eighth indication message is used to indicate that the second MLD does not have cached data corresponding to any data type mapped to the fourth link.

[0377] In this embodiment, the eighth indication information can be a QoS Null frame, which is a data frame without a payload, and the More Data subfield in the QoS Null frame has a value of 0. When the QoS Null frame is transmitted to the first MLD via Link 1, it can indicate that the second MLD does not have cached data corresponding to any data type of Link 1 (used for transmitting the QoS Null frame).

[0378] Step S803: The first MLD determines, according to the eighth instruction information, that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0379] Specifically, after the first MLD receives the eighth indication information from the second MLD through the fourth link, it can determine, based on the eighth indication information, that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0380] In one implementation, the first MLD can have multiple stations. After determining that the second MLD does not cache any data corresponding to any data type mapped to the fourth link, the first MLD can determine the working status of the station corresponding to the fourth link among the multiple stations of the first MLD based on the fact that the second MLD does not cache any data corresponding to any data type mapped to the fourth link. For example, based on the fact that the second MLD does not cache any data corresponding to any data type mapped to the fourth link, the first MLD can determine that the working status of the station corresponding to the fourth link is a dormant state.

[0381] In one implementation, the first MLD can determine the working status of the station corresponding to the fourth link based on one or more of the current power information or service demand information of the first MLD, and the fact that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0382] By implementing the embodiments of this application, it can be determined, based on the eighth instruction information, that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0383] Please see Figure 9a , Figure 9a This is a flowchart illustrating another method for determining data caching status provided in this application embodiment. The method details how a first MLD determines the caching status of cached data corresponding to at least one data type mapped to at least one link in a second MLD based on tenth instruction information. Specifically, the execution subject of steps S901 to S902 is the second MLD or a chip within the second MLD, and the execution subject of step S903 is the first MLD or a chip within the first MLD. The following explanation uses the second MLD and the first MLD as examples of the execution subjects for determining the data caching status. This method may include, but is not limited to, the following steps:

[0384] Step S901: The second MLD determines the caching status of cached data corresponding to at least one data type of at least one link mapped to the first MLD in the second MLD.

[0385] In this embodiment, the second MLD may include multiple cache regions, each of which can be used to cache cached data corresponding to one or more links (between the second MLD and the first MLD). If cache region r is used to cache cached data corresponding to link 1, it indicates that the cached data in cache region r will be transmitted to the first MLD via link 1. If cache region r is used to cache cached data corresponding to links 1 and 2, it indicates that the cached data in cache region r can be transmitted to the first MLD via at least one of links 1 and 2. Therefore, by detecting whether cached data exists in each cache region of the second MLD, the second MLD can determine whether the links corresponding to each cache region have cached data in the second MLD. One or more data types can be mapped on a link. Furthermore, the second MLD can determine the caching status of the data types mapped to the links corresponding to each cache region in that cache region.

[0386] Taking data type TID as an example, when a cache area is used to cache the cache data corresponding to a link, and the first MLD supports 8 types of TID, the second MLD can determine the caching status of each type of TID in each cache area.

[0387] Step S902: The second MLD sends a tenth indication information to the first MLD. The tenth indication information is used to indicate the caching status of cached data corresponding to at least one data type mapped to at least one link of the first MLD in the second MLD.

[0388] The tenth indication information may refer to the bits occupied by control type b in the EHT A-control field of the MAC frame. For a description of the EHT A-control field, please refer to [link to relevant documentation]. Figure 2 The illustrated embodiment will not be described in detail here. Control type b is a newly added control type.

[0389] When the data type includes management frames and TIDs, control type b can be called "More Data Per TID Per link". The number of bits occupied by "More Data Per TID Per link" can be 9*L, where L is the number of links between the first MLD and the MLDs. In this case, the "More Data Per TID Per link" subfield can include L "per link structures". One "per link structure" can correspond to one link, and each per link structure can contain 9 bits. One bit in the per link structure corresponds to one data type. Specifically, one bit can correspond to a management frame, and each of the other 8 bits corresponds to a TID on the link. When a bit in the per link structure corresponding to link 1 is 1, it indicates that the second MLD has cached data of the data type (such as a management frame or TID) corresponding to that bit, and this cached data will be sent to the first MLD via link 1. When a certain bit in the per-link structure corresponding to link 1 is 0, it can indicate that the second MLD does not cache data of the data type (such as management frame or TID) that will be sent through link 1.

[0390] Step S903: The first MLD determines the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD according to the tenth instruction information.

[0391] In one implementation, the tenth indication information can refer to the bits occupied by the More Data Per TID Per link subfield. In another implementation, when the first MLD allocates different buffer areas for each link, and one bit in the perlink structure corresponds to one data type, after receiving the tenth indication information from the second MLD, the first MLD can determine the buffering status of the buffered data corresponding to the various data types mapped to each link in the second MLD based on the tenth indication information. For example, when the links between the first MLD and the second MLD include link 1 and link 2, a schematic diagram of the More Data Per TID Per link subfield can be shown as follows. Figure 9b As shown. Figure 9b As shown, the "More Data Per TID Perlink" subfield includes two per-link structures (link 1 and link 2), with small squares representing a single bit. In the per-link structure corresponding to link 1, each bit corresponds to a data type, with different bits representing different data types.Figure 9b In the per-link structure corresponding to Link 1 (or Link 2), the 9 bits correspond to T1D0 to TID7 and the management frame, respectively. The first 4 bits of the per-link structure corresponding to Link 1 are 1, and the last 4 bits are 0, indicating that the buffer region in the second MLD corresponding to Link 1 contains cached data corresponding to TID0 to TID3, but not cached data corresponding to TID4 to TID7 and the management frame. Similarly, the first and last bits of the per-link structure corresponding to Link 2 are 1, and the remaining bits are 0, indicating that the buffer region in the second MLD corresponding to Link 2 contains cached data corresponding to TID0 and the management frame, but not cached data corresponding to TID1 to TID7.

[0392] It should be noted that the 9-bit per-link structure is only for illustrative purposes. In other feasible implementations, a per-link structure may include one or more bits. For example, the number of bits in a per-link structure can be the same as the number of data types in the link mapping corresponding to that per-link structure. When the data type is AC, the number of bits in the per-link structure can be the same as the number of ACs corresponding to the TID of the link mapping corresponding to that per-link structure.

[0393] It should also be noted that the statement that one bit in the per link structure corresponds to one data type (management frame, TID, or AC) is only for illustrative purposes. One bit in the per link structure can correspond to one or more data types (management frame, TID, or AC).

[0394] In one implementation, when the first MLD allocates different buffer regions for each link, and the bits in the per-link structure can correspond to at least two data types, after receiving the tenth indication information from the second MLD, the first MLD can determine the buffering status of the buffered data corresponding to the at least two data types mapped to each link in the second MLD based on the tenth indication information. For example, when the first bit in the per-link structure corresponding to link 1 corresponds to TID1 and TID2, and the value of the first bit is 1, it can indicate that the buffer region in the second MLD corresponding to link 1 has buffered data corresponding to at least one of TID1 and TID2. A value of 0 for the first bit can indicate that the buffer region in the second MLD corresponding to link 1 has neither buffered data corresponding to TID1 nor buffered data corresponding to TID2.

[0395] In one implementation, when the first MLD can allocate the same buffer region for at least two links, and one bit in the perlink structure corresponds to a data type, after receiving the tenth indication information from the second MLD, the first MLD can determine the buffering status of the buffered data corresponding to the various data types mapped to the at least two links in the second MLD based on the tenth indication information. For example, when the buffer region r in the second MLD corresponds to links 1 and 2, and the first bit in the perlink structure corresponding to links 1 and 2 corresponds to TID1, if the value of the first bit is 1, it indicates that the buffer region r contains buffered data corresponding to TID1, which may be sent to the first MLD through links 1 and / or 2. If the value of the first bit is 0, it indicates that the buffer region r does not contain buffered data corresponding to TID1, and neither links 1 nor 2 will transmit the buffered data corresponding to TID1.

[0396] In one implementation, when the first MLD can allocate the same buffer region for at least two links, and the bits in the perlink structure can correspond to at least two data types, after receiving the tenth indication information from the second MLD, the first MLD can determine the buffering status of the buffered data corresponding to the at least two data types mapped to the at least two links in the second MLD based on the tenth indication information.

[0397] In one implementation, the first MLD can have multiple stations. The first MLD can determine the working status of at least one of its multiple stations based on the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD. Specifically, the first MLD can determine the working status of each station based on the caching status of cached data corresponding to various data types mapped to each link in the second MLD. For example, if the cache region corresponding to link 1 in the second MLD caches cached data corresponding to TID0 to TID3, and the cache region corresponding to link 2 in the second MLD caches cached data corresponding to TID1 and TID7, that is, if the second MLD caches cached data corresponding to both link 1 and link 2, the first MLD can determine that links 1 and 2 are active. Thus, the cached data corresponding to TID0 to TID3 can be received through the first link, and the cached data corresponding to TID1 and TID7 can be received through link 2.

[0398] In one implementation, the first MLD can determine the working status of at least one of the multiple sites it has based on one or more of the current power information or service demand information of the first MLD, as well as the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD.

[0399] In this embodiment, based on the tenth instruction information, the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD can be determined. In this way, the caching status of cached data in the second MLD can be determined in more detail, thereby facilitating the determination of a more suitable operating state for the sites in the first MLD.

[0400] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspectives of a first MLD and a second MLD, respectively. To implement the functions of the methods provided in the embodiments of this application, the first MLD and the second MLD may include hardware structures and software modules, and the above functions may be implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions may be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0401] Please see Figure 10 This is a schematic diagram of the structure of a communication device 100 provided in an embodiment of this application. Figure 10 The communication device 100 shown 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 used to implement the transmitting function, and the receiving unit is used to implement the receiving function. The communication unit 1001 can implement both the transmitting and / or receiving functions. The communication unit may also be described as a transceiver unit.

[0402] The communication device 100 can be a first MLD, a device within the first MLD, or a device compatible with the first MLD. When the communication device 100 is the first MLD, it can be one of the aforementioned. Figure 2 - Figure 9a The first MLD in the illustrated embodiment.

[0403] Communication device 100 is Figure 3a or Figure 5 The first MLD in the illustrated embodiment:

[0404] The communication unit 1001 is used to receive first indication information from the second MLD; the first indication information is used to indicate the caching status of the cached data corresponding to the associated identifier of the communication device 100 in the second MLD;

[0405] The processing unit 1002 is configured to determine the caching status of cached data corresponding to at least one data type 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.

[0406] In one implementation, the communication device 100 has multiple stations; the communication unit 1001 can also be used to determine the working state of at least one of the multiple stations based on the caching status of cached data corresponding to at least one data type in the second MLD; the working state is an active state or a dormant state.

[0407] In one implementation, the communication unit 1001 is further configured to receive second indication information from the second MLD, the second indication information being used to determine the correspondence between the associated identifier and the data type.

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

[0409] In one implementation, the communication device 100 can support multiple data types; the second indication information indicates a first association identifier, which corresponds to a first data type among the multiple data types; the processing unit 1002 is further configured to determine the association identifiers corresponding to other data types among the multiple data types besides the first data type based on the first association identifier corresponding to the first data type.

[0410] Communication device 100 is Figure 4a or Figure 5 The first MLD in the illustrated embodiment:

[0411] The communication unit 1001 is used to receive cached data from the second MLD via a first link. The cached data includes third indication information. The third indication information is used to indicate whether the second MLD has cached data corresponding to at least one second data type, wherein the second data type is any data type mapped to the first link.

[0412] The processing unit 1002 is configured to determine, based on the third indication information, whether the second MLD contains cached data corresponding to at least one second data type.

[0413] In one implementation, the communication device 100 has multiple stations; the processing unit 1002 is further configured to determine the working state of the station corresponding to the first link among the multiple stations based on whether the second MLD contains cached data corresponding to at least one second data type; the working state is either active or dormant.

[0414] In one implementation, the processing unit 1002 is used to determine the working status of the station corresponding to the first link among multiple stations based on whether the second MLD caches at least one cached data corresponding to a second data type. Specifically, it is used to: if the second MLD caches at least one cached data corresponding to a second data type, then determine that the working status of the station corresponding to the first link among multiple stations is active; if the second MLD does not cache any cached data corresponding to any second data type, then determine that the working status of the station corresponding to the first link among multiple stations is active or dormant.

[0415] In one implementation, the third indication information indicates that the second MLD has cached data corresponding to at least one second data type; the communication unit 1001 is further configured to receive a fourth indication information from the second MLD; the fourth indication information is used to indicate that the second MLD does not have cached data corresponding to any second data type.

[0416] Communication device 100 is Figure 6a The first MLD in the illustrated embodiment:

[0417] The communication unit 1001 is used to receive cached data corresponding to a third data type from the second MLD. The cached data includes fifth indication information, which is used to indicate whether the second MLD has cached data corresponding to the third data type.

[0418] The processing unit 1002 is used to determine, based on the fifth indication information, whether the second MLD contains cached data corresponding to the third data type.

[0419] In one implementation, the communication device 100 has multiple stations; the processing unit 1002 can also be used to determine the working state of the station corresponding to the second link among the multiple stations based on whether the second MLD has cached data corresponding to the third data type, wherein the third data type is mapped to the second link; the working state is an active state or a dormant state.

[0420] In one implementation, the processing unit 1002 can also be used to determine whether the second link maps to data types other than the third data type.

[0421] The processing unit 1002 is used to determine the working status of the station corresponding to the second link among multiple stations based on whether the second MLD caches cached data corresponding to the third data type. Specifically, it is used to determine the working status of the station corresponding to the second link among multiple stations based on whether the second MLD caches cached data corresponding to the third data type and whether the second link maps to other data types besides the third data type.

[0422] In one implementation, the fifth indication information indicates that the second MLD does not cache data corresponding to the third data type; the cache data corresponding to the third data type received by the communication unit 1001 from the second MLD also includes a sixth indication information, which is used to indicate whether the second MLD caches cache data corresponding to at least one fourth data type; the fourth data type is any data type other than the third data type among the data types supported by the communication device 100.

[0423] In one implementation, the priority of the fourth data type can be higher than that of the third data type.

[0424] Communication device 100 is Figure 7 The first MLD in the illustrated embodiment:

[0425] The communication unit 1001 is configured to receive a seventh indication information from the second MLD, the seventh indication information being used to indicate that the second MLD does not cache data corresponding to the fifth data type; the fifth data type is any data type among the data types supported by the communication device;

[0426] The processing unit 1002 is used to determine, based on the seventh indication information, that the second MLD does not cache the cached data corresponding to the fifth data type.

[0427] In one implementation, the communication device 100 has multiple stations; the processing unit 1002 is further configured to determine the working state of the station corresponding to the third link among the multiple stations based on the fact that the second MLD does not cache cached data corresponding to the fifth data type, wherein the fifth data type is mapped to the third link; the working state is either an active state or a dormant state.

[0428] Communication device 100 is Figure 8 The first MLD in the illustrated embodiment:

[0429] The communication unit 1001 is used to receive eighth indication information from the second MLD via the fourth link. The eighth indication information is used to indicate that the second MLD does not have cached data corresponding to any data type mapped to the fourth link.

[0430] Processing unit 1002 is configured to determine, based on the eighth indication information, that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0431] In one implementation, the communication device 100 has multiple stations; the processing unit 1002 is further configured to determine the working state of the station corresponding to the fourth link among the multiple stations based on the fact that the second MLD does not cache cached data corresponding to any data type mapped to the fourth link; the working state is either active or dormant.

[0432] 100 has multiple stations; processing unit 1002 is also used to correspond to at least one data type.

[0433] Communication device 100 is Figure 2 The first MLD in the illustrated embodiment:

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

[0435] Processing unit 1002 is used to determine the caching status of cached data corresponding to at least one data type in the second MLD based on the ninth instruction information.

[0436] In one implementation, the communication device 100 has multiple stations; the processing unit 1002 is further configured to determine the working state of at least one of the multiple stations based on the caching status of the communication device's cached data in the second MLD; the working state is either an active state or a dormant state.

[0437] Communication device 100 is Figure 9a The first MLD in the illustrated embodiment:

[0438] The communication unit 1001 is configured to receive tenth indication information from the second MLD, the tenth indication information being used to indicate the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to the communication device in the second MLD;

[0439] Processing unit 1002 is configured to determine, based on the tenth instruction information, the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD.

[0440] In one implementation, the communication device 100 has multiple stations; the processing unit 1002 is further configured to determine the working state of at least one of the multiple stations based on the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD; the working state is either an active state or a dormant state.

[0441] Please see Figure 11 , Figure 11 This is a schematic diagram of another communication device 110 provided in an embodiment of this application. The communication device 110 may be a first MLD, or a chip, chip system, or processor that supports the first MLD in implementing the above methods. This device can be used to implement the methods described in the above method embodiments, and for details, please refer to the description in the above method embodiments.

[0442] The communication device 110 may include one or more processors 1101. The processor 1101 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal, terminal chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0443] The communication device 110 may further include a transceiver 1105. The transceiver 1105, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transmission and reception functions. The transceiver 1105 may include a receiver and a transmitter. The receiver, also known as a receiver circuit, is used to implement a receiving function; the transmitter, also known as a transmitter or transmitting circuit, is used to implement a transmitting function. Optionally, the communication device 110 may further include an antenna 1106.

[0444] Optionally, the communication device 110 may include one or more memories 1102, on which a computer program 1104 may be stored. This computer program can be run on the communication device 110, causing the communication device 110 to perform the methods described in the above method embodiments. Optionally, the memory 1102 may also store data. The communication device 110 and the memory 1102 may be provided separately or integrated together.

[0445] Processor 1101 is used to execute Figure 2 Step S203 in the process; Figure 3a Step S304 in the process; Figure 4a Step S403 in the process; Figure 5 Steps S504-S505 and S509; Figure 6a Step S603 in the process; Figure 7 Step S703 in the process; Figure 8 Step S803 or Figure 9a Step S903 in the process.

[0446] Transceiver 1105 is used in Figure 2 In the illustrated embodiment, indication information is received from a second MLD; in Figure 3a In the illustrated embodiment, first indication information is received from the second MLD; in Figure 4a In the illustrated embodiment, cached data is received from the second MLD; in Figure 5 In the illustrated embodiment, first indication information and cached data are received from the second MLD, and link status indication information is sent to the second MLD; Figure 6a In the illustrated embodiment, cached data corresponding to a third data type from a second MLD is received; in Figure 7In the illustrated embodiment, seventh indication information is received from the second MLD; in Figure 8 In the illustrated embodiment, the eighth indication information is received from the second MLD; in Figure 9a In the illustrated embodiment, tenth instruction information is received from the second MLD;

[0447] In one implementation, the processor 1101 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0448] In one implementation, processor 1101 may store computer program 1103, which runs on processor 1101 and causes communication device 110 to perform the methods described in the above method embodiments. Computer program 1103 may be embedded in processor 1101, in which case processor 1101 may be implemented in hardware.

[0449] In one implementation, the communication device 110 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0450] The communication device described in the above embodiments may be a first MLD, but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may vary. Figure 11 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0451] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0452] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0453] (3) ASIC, such as modem;

[0454] (4) Modules that can be embedded in other devices;

[0455] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.

[0456] (6) Others, etc.

[0457] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 12 The diagram shows the structure of the chip. Figure 12 The chip shown includes a processor 1201 and an interface 1202. There can be one or more processors 1201, and multiple interfaces 1202.

[0458] For chips used to implement Figure 3a or Figure 5 The functionality of the first MLD in the illustrated embodiment is as follows:

[0459] Interface 1202 is used to receive first indication information from the second MLD; the first indication information is used to indicate the caching status of the cached data corresponding to the associated identifier of the first MLD in the second MLD;

[0460] Processor 1201 is configured to determine the caching status of cached data corresponding to at least one data type 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.

[0461] In one implementation, the first MLD has multiple stations; the processor 1201 can also be used to determine the working state of at least one of the multiple stations based on the caching status of cached data corresponding to at least one data type in the second MLD; the working state is either active or dormant.

[0462] In one implementation, interface 1202 is further configured to receive second indication information from a second MLD, the second indication information being used to determine the correspondence between the associated identifier and the data type.

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

[0464] In one implementation, the first MLD can support multiple data types; the second indication information indicates a first association identifier, which corresponds to the first data type among the multiple data types; the processor 1201 is further configured to determine the association identifiers corresponding to other data types among the multiple data types besides the first data type based on the first association identifier corresponding to the first data type.

[0465] For chips used to implement Figure 4a or Figure 5 The functionality of the first MLD in the illustrated embodiment is as follows:

[0466] Interface 1202 is used to receive cached data from a second MLD via a first link. The cached data includes third indication information. The third indication information is used to indicate whether the second MLD caches at least one cached data corresponding to a second data type, wherein the second data type is any data type mapped to the first link.

[0467] Processor 1201 is configured to determine, based on the third indication information, whether the second MLD contains cached data corresponding to at least one second data type.

[0468] In one implementation, the first MLD has multiple stations; the processor 1201 is further configured to determine the working state of the station corresponding to the first link among the multiple stations based on whether the second MLD caches at least one cached data corresponding to a second data type; the working state is either active or dormant.

[0469] In one implementation, the processor 1201 is used to determine the working state of the station corresponding to the first link among multiple stations based on whether the second MLD caches cached data corresponding to at least one second data type. Specifically, it is used to: if the second MLD caches cached data corresponding to at least one second data type, then determine that the working state of the station corresponding to the first link among multiple stations is active; if the second MLD does not cache cached data corresponding to any second data type, then determine that the working state of the station corresponding to the first link among multiple stations is active or dormant.

[0470] In one implementation, the third indication information indicates that the second MLD has cached data corresponding to at least one second data type; the interface 1202 is also used to receive a fourth indication information from the second MLD; the fourth indication information is used to indicate that the second MLD does not have cached data corresponding to any second data type.

[0471] For chips used to implement Figure 6a The functionality of the first MLD in the illustrated embodiment is as follows:

[0472] Interface 1202 is used to receive cached data corresponding to a third data type from a second MLD. The cached data includes fifth indication information, which is used to indicate whether the second MLD has cached data corresponding to the third data type.

[0473] Processor 1201 is used to determine, based on the fifth instruction information, whether the second MLD contains cached data corresponding to the third data type.

[0474] In one implementation, the first MLD has multiple stations; the processor 1201 can also be used to determine the working state of the station corresponding to the second link among the multiple stations based on whether the second MLD caches cached data corresponding to the third data type, the third data type being mapped to the second link; the working state is either active or dormant.

[0475] In one implementation, the processor 1201 can also be used to determine whether the second link maps to other data types besides the third data type; when the processor 1201 is used to determine the working status of the station corresponding to the second link among multiple stations based on whether the second MLD caches cached data corresponding to the third data type, it is specifically used to: determine the working status of the station corresponding to the second link among multiple stations based on whether the second MLD caches cached data corresponding to the third data type and whether the second link maps to other data types besides the third data type.

[0476] In one implementation, the fifth indication information indicates that the second MLD does not cache data corresponding to the third data type; the cache data corresponding to the third data type received by interface 1202 from the second MLD also includes a sixth indication information, which is used to indicate whether the second MLD caches cache data corresponding to at least one fourth data type; the fourth data type is any data type other than the third data type among the data types supported by the first MLD.

[0477] In one implementation, the priority of the fourth data type can be higher than that of the third data type.

[0478] For chips used to implement Figure 7 The functionality of the first MLD in the illustrated embodiment is as follows:

[0479] Interface 1202 is used to receive a seventh indication information from the second MLD, the seventh indication information being used to indicate that the second MLD does not cache data corresponding to the fifth data type; the fifth data type is any data type among the data types supported by the first MLD;

[0480] Processor 1201 is used to determine, based on the seventh indication information, that the second MLD does not cache the cached data corresponding to the fifth data type.

[0481] In one implementation, the first MLD has multiple stations; the processor 1201 is further configured to determine the working state of the station corresponding to the third link among the multiple stations based on the fact that the second MLD does not cache cached data corresponding to the fifth data type, wherein the fifth data type is mapped to the third link; the working state is either active or dormant.

[0482] For chips used to implement Figure 8 The functionality of the first MLD in the illustrated embodiment is as follows:

[0483] Interface 1202 is used to receive eighth indication information from the second MLD via the fourth link. The eighth indication information is used to indicate that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0484] Processor 1201 is configured to determine, based on the eighth indication information, that the second MLD does not cache any cached data corresponding to any data type mapped to the fourth link.

[0485] In one implementation, the first MLD has multiple stations; the processor 1201 is further configured to determine the working state of the station corresponding to the fourth link among the multiple stations based on the fact that the second MLD does not cache cached data corresponding to any data type mapped to the fourth link; the working state is either active or dormant.

[0486] For chips used to implement Figure 2 The functionality of the first MLD in the illustrated embodiment is as follows:

[0487] Interface 1202 is used to receive a ninth indication information from the second MLD, the ninth indication information being used to indicate the caching status of cached data corresponding to at least one data type supported by the first MLD in the second MLD;

[0488] Processor 1201 is configured to determine, based on the ninth instruction information, the caching status of cached data corresponding to at least one data type in the second MLD.

[0489] In one implementation, the processor 1201 is further configured to determine the working state of at least one of the multiple sites based on the cached data of the first MLD in the second MLD; the working state is either active or dormant.

[0490] For chips used to implement Figure 9a The functionality of the first MLD in the illustrated embodiment is as follows:

[0491] Interface 1202 is used to receive tenth indication information from the second MLD, the tenth indication information being used to indicate the caching status of cached data corresponding to at least one data type mapped to at least one link of the first MLD in the second MLD;

[0492] Processor 1201 is configured to determine, based on the tenth instruction information, the cache status of cached data corresponding to at least one data type mapped to at least one link in the second MLD.

[0493] In one implementation, the first MLD has multiple stations; the processor 1201 is further configured to determine the working state of at least one of the multiple stations based on the caching status of cached data corresponding to at least one data type mapped to at least one link in the second MLD; the working state is either active or dormant.

[0494] Optionally, the chip also includes a memory 1203 for storing necessary computer programs and data.

[0495] Please see Figure 13 This is a schematic diagram of the structure of another communication device 130 provided in the embodiments of this application. Figure 13The communication device 130 shown 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 implements a transmitting function, and the receiving unit implements a receiving function. The communication unit 1301 can implement both transmitting and / or receiving functions. The communication unit may also be described as a transceiver unit.

[0496] The communication device 130 can be a second MLD, a device within a second MLD, or a device compatible with a second MLD. When the communication device 130 is a second MLD, it can be one of the aforementioned devices. Figure 2 - Figure 9a The second MLD in the illustrated embodiment.

[0497] Communication device 130 is Figure 3a or Figure 5 The second MLD in the illustrated embodiment:

[0498] Processing unit 1302 is used to determine the caching status of cached data corresponding to at least one data type supported by the first MLD in storage unit 1303; and to determine the caching status of cached data corresponding to the association identifier in storage unit 1303 based on the caching status of cached data corresponding to at least one data type in storage unit 1303 and the correspondence between the association identifier of the first MLD and the supported data types.

[0499] The communication unit 1301 is used to send first indication information to the first MLD; the first indication information is used to indicate the cache status of the cached data corresponding to the associated identifier of the first MLD in the storage unit 1303.

[0500] In one implementation, the communication unit 1301 is further configured to send second indication information to the first MLD, the second indication information being used to determine the correspondence between the association identifier of the first MLD and the data types supported by the first MLD.

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

[0502] In one implementation, the first MLD supports multiple data types; the second indication information indicates a first association identifier, which corresponds to a first data type among the multiple data types.

[0503] Communication device 130 is Figure 4a or Figure 5 The second MLD in the illustrated embodiment:

[0504] The processing unit 1302 is used to determine whether the storage unit 1303 has cached data corresponding to at least one second data type; the second data type is any data type mapped to the first link;

[0505] The communication unit 1301 is used to send cached data to the first MLD through the first link. The cached data includes third indication information. The third indication information is used to indicate whether the storage unit 1303 has cached data corresponding to at least one second data type.

[0506] In one implementation, the third indication information indicates that the storage unit 1303 has cached data corresponding to at least one second data type; the communication unit 1301 is further configured to send a fourth indication information to the first MLD; the fourth indication information is used to indicate that the storage unit 1303 does not have cached data corresponding to any second data type.

[0507] Communication device 130 is Figure 6a The second MLD in the illustrated embodiment:

[0508] Processing unit 1302 is used to determine whether there is cached data corresponding to the third data type in storage unit 1303;

[0509] The communication unit 1301 is used to send cached data corresponding to the third data type to the first MLD. The cached data includes fifth indication information, which is used to indicate whether the storage unit 1303 has cached data corresponding to the third data type.

[0510] In one implementation, the fifth indication information indicates that the storage unit 1303 does not cache data corresponding to the third data type; the cache data corresponding to the third data type sent by the communication unit 1301 to the first MLD also includes a sixth indication information, which is used to indicate whether the storage unit 1303 caches cache data corresponding to at least one fourth data type; the fourth data type is any data type other than the third data type among the data types supported by the first MLD.

[0511] In one implementation, the priority of the fourth data type can be higher than that of the third data type.

[0512] Communication device 130 is Figure 7 The second MLD in the illustrated embodiment:

[0513] Processing unit 1302 is used to determine that storage unit 1303 does not cache data corresponding to the fifth data type; the fifth data type is any data type among the data types supported by the first MLD;

[0514] The communication unit 1301 is used to send a seventh indication information to the first MLD, the seventh indication information being used to indicate that the storage unit 1303 does not cache data corresponding to the fifth data type.

[0515] Communication device 130 is Figure 8 The second MLD in the illustrated embodiment:

[0516] Processing unit 1302 is used to determine that storage unit 1303 does not cache any cached data corresponding to any data type mapped to the fourth link;

[0517] The communication unit 1301 is used to send an eighth indication message to the first MLD through the fourth link. The eighth indication message is used to indicate that the storage unit 1303 does not cache any cached data corresponding to any data type mapped to the fourth link.

[0518] Communication device 130 is Figure 2 The second MLD in the illustrated embodiment:

[0519] Processing unit 1302 is used to determine the caching status of cached data corresponding to at least one data type supported by the first MLD in storage unit 1303;

[0520] The communication unit 1301 is used to send a ninth indication information to the first MLD, the ninth indication information being used to indicate the caching status of cached data corresponding to at least one data type supported by the first MLD in the storage unit 1303.

[0521] Communication device 130 is Figure 9a The second MLD in the illustrated embodiment:

[0522] Processing unit 1302 is used to determine the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to the first MLD in storage unit 1303;

[0523] The communication unit 1301 is used to send tenth indication information to the first MLD. The tenth indication information is used to indicate the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to the first MLD in the storage unit 1303.

[0524] Please see Figure 14 , Figure 14 This is a schematic diagram of another communication device 140 provided in an embodiment of this application. The communication device 140 may be a second MLD, or a chip, chip system, or processor that supports the second MLD in implementing the above methods. This device can be used to implement the methods described in the above method embodiments, and for details, please refer to the description in the above method embodiments.

[0525] The communication device 140 may include one or more processors 1401. The processor 1401 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal, terminal chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0526] The communication device 140 may further include a transceiver 1405. The transceiver 1405 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement transmission and reception functions. The transceiver 1405 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement a receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement a transmitting function. Optionally, the communication device 140 may further include an antenna 1406.

[0527] The communication device 140 may further include one or more memories 1402, on which a computer program 1404 may be stored. This computer program can be run on the communication device 140, causing the communication device 140 to perform the methods described in the above method embodiments. Optionally, the memory 1402 may also store data. The communication device 140 and the memory 1402 may be provided separately or integrated together.

[0528] Processor 1401 is used to execute Figure 2 Step S201 in the process; Figure 3a Steps S301 to S302 in the process; Figure 4a Step S401 in the process; Figure 5 Steps S501 to S502 and step S507; Figure 6a Step S601 in the process; Figure 7 Step S701 in the process; Figure 8 Step S801 or Figure 9a Step S901 in the process.

[0529] Transceiver 1405 is used to perform Figure 2 S202 in; Figure 3a Step S303 in the process; Figure 4a Step S402 in the process; Figure 5 Steps S503 and S508; Figure 6a Step S602 in the process; Figure 7 Step S702 in the process; Figure 8 Step S802 or Figure 9a Step S902 in the process.

[0530] In one implementation, the processor 1401 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0531] In one implementation, processor 1401 may store computer program 1403, which runs on processor 1401 and causes communication device 140 to perform the methods described in the above method embodiments. Computer program 1403 may be embedded in processor 1401; in this case, processor 1401 may be implemented in hardware.

[0532] In one implementation, the communication device 140 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0533] The communication device described in the above embodiments may be a second MLD, but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may be unrestricted. Figure 14 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0534] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0535] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0536] (3) ASIC, such as modem;

[0537] (4) Modules that can be embedded in other devices;

[0538] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.

[0539] (6) Others, etc.

[0540] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 15 The diagram shows the structure of the chip. Figure 15 The chip shown includes a processor 1501, an interface 1502, and a memory 1503. There can be one or more processors 1501, multiple interfaces 1502, and one or more memory units 1503. The memory 1503 is used to store cached data, as well as necessary computer programs and data.

[0541] For chips used to implement Figure 3a or Figure 5 The functionality of the second MLD in the illustrated embodiment is as follows:

[0542] Processor 1501 is used to determine the cache status of cached data corresponding to at least one data type supported by the first MLD in memory 1503; and to determine the cache status of cached data corresponding to the association identifier in memory 1503 based on the cache status of cached data corresponding to at least one data type in memory 1503 and the correspondence between the association identifier of the first MLD and the supported data types.

[0543] Interface 1502 is used to send first indication information to the first MLD; the first indication information is used to indicate the cache status of the cached data corresponding to the associated identifier of the first MLD in memory 1503.

[0544] In one implementation, interface 1502 is further used to send second indication information to the first MLD, the second indication information being used to determine the correspondence between the association identifier of the first MLD and the data types supported by the first MLD.

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

[0546] In one implementation, the first MLD supports multiple data types; the second indication information indicates a first association identifier, which corresponds to a first data type among the multiple data types.

[0547] For chips used to implement Figure 4a or Figure 5 The functionality of the second MLD in the illustrated embodiment is as follows:

[0548] Processor 1501 is configured to determine whether memory 1503 caches at least one cached data corresponding to a second data type; the second data type is any data type mapped to the first link;

[0549] Interface 1502 is used to send cached data to the first MLD via the first link. The cached data includes third indication information. The third indication information is used to indicate whether the memory 1503 has cached data corresponding to at least one second data type.

[0550] In one implementation, the third indication information indicates that the memory 1503 has cached data corresponding to at least one second data type; the interface 1502 is also used to send a fourth indication information to the first MLD; the fourth indication information is used to indicate that the memory 1503 does not have cached data corresponding to any second data type.

[0551] For chips used to implement Figure 6a The functionality of the second MLD in the illustrated embodiment is as follows:

[0552] Processor 1501 is used to determine whether there is cached data corresponding to the third data type in memory 1503;

[0553] Interface 1502 is used to send cached data corresponding to the third data type to the first MLD. The cached data includes fifth indication information, which is used to indicate whether the memory 1503 has cached data corresponding to the third data type.

[0554] In one implementation, the fifth indication information indicates that the memory 1503 does not cache data corresponding to the third data type; the cache data corresponding to the third data type sent by the interface 1502 to the first MLD also includes a sixth indication information, which is used to indicate whether the memory 1503 caches cache data corresponding to at least one fourth data type; the fourth data type is any data type other than the third data type among the data types supported by the first MLD.

[0555] In one implementation, the priority of the fourth data type can be higher than that of the third data type.

[0556] For chips used to implement Figure 7 The functionality of the second MLD in the illustrated embodiment is as follows:

[0557] Processor 1501 is configured to determine that memory 1503 does not cache data corresponding to a fifth data type; the fifth data type is any data type among the data types supported by the first MLD;

[0558] Interface 1502 is used to send a seventh indication message to the first MLD, the seventh indication message being used to indicate that the memory 1503 does not cache data corresponding to the fifth data type.

[0559] For chips used to implement Figure 8 The functionality of the second MLD in the illustrated embodiment is as follows:

[0560] Processor 1501 is used to determine that memory 1503 does not cache any data corresponding to any data type mapped to the fourth link;

[0561] Interface 1502 is used to send an eighth indication message to the first MLD through the fourth link. The eighth indication message is used to indicate that the memory 1503 does not cache any cached data corresponding to any data type mapped to the fourth link.

[0562] For chips used to implement Figure 2 The functionality of the second MLD in the illustrated embodiment is as follows:

[0563] Processor 1501 is used to determine the cache status of cached data corresponding to at least one data type supported by the first MLD in memory 1503;

[0564] Interface 1502 is used to send a ninth indication information to the first MLD, the ninth indication information being used to indicate the caching status of cached data corresponding to at least one data type supported by the first MLD in memory 1503.

[0565] For chips used to implement Figure 9a The functionality of the second MLD in the illustrated embodiment is as follows:

[0566] Processor 1501 is configured to determine the cache status of cached data corresponding to at least one data type mapped to at least one link corresponding to the first MLD in memory 1503.

[0567] Interface 1502 is used to send tenth indication information to the first MLD, the tenth indication information being used to indicate the caching status of cached data corresponding to at least one data type mapped to at least one link corresponding to the first MLD in memory 1503.

[0568] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0569] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, implements the functions of any of the above method embodiments.

[0570] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0571] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0572] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., involved in this application are merely for the convenience of description and are not intended to limit the scope of the embodiments of this application, nor do they indicate the order of sequence.

[0573] At least one in this application can also be described as one or more, and multiple can be two, three, four or more, and this application does not impose any limitation. In the embodiments of this application, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order or size among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0574] The correspondences shown in the tables of this application can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this application is not limited to these values. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this application may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headings of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0575] The term "predefined" in this application can be understood as definition, pre-defined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0576] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0577] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0578] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of determining a data cache condition, the method comprising: determining a number of cache misses in a cache; and determining a number of cache hits in the cache. The method comprises: A first multi-link device (MLD) receives buffered data from a second MLD through a first link, the buffered data comprising third indication information; the third indication information is used to indicate whether the second MLD buffers buffered data corresponding to at least one second data type, wherein the second data type is any data type mapped to the first link; The first MLD determines whether the second MLD buffers buffered data corresponding to at least one second data type according to the third indication information.

2. The method of claim 1, wherein, The first MLD has multiple stations, and the method further comprises: The first MLD determines the working state of at least one station in the multiple stations according to whether the second MLD buffers buffered data corresponding to at least one data type; the working state is an active state or a sleep state.

3. The method of claim 2, wherein, If the second MLD buffers buffered data corresponding to at least one second data type, the working state of the station corresponding to the first link in the multiple stations is determined as the active state. If the second MLD does not buffer buffered data corresponding to any second data type, the working state of the station corresponding to the first link in the multiple stations is determined as the active state or the sleep state.

4. The method of claim 1, wherein the step of determining the location of the mobile device is performed by a location server. The third indication information is also used to indicate whether the second MLD buffers buffered data corresponding to management frames.

5. The method of claim 1, wherein, The third indication information is a more data (More Data) subfield; a value of the More Data subfield is 1, indicating that the second MLD buffers buffered data corresponding to at least one second data type; or a value of the More Data subfield is 0, indicating that the second MLD does not buffer buffered data corresponding to any second data type.

6. The method of claim 2, wherein, The third indication information is a more data (More Data) subfield; a value of the More Data subfield is 1, indicating that the second MLD buffers buffered data corresponding to at least one second data type; or a value of the More Data subfield is 0, indicating that the second MLD does not buffer buffered data corresponding to any second data type.

7. The method of claim 1, wherein, The method further comprises: The first MLD sends a power saving poll (PS-Poll) frame to the second MLD.

8. The method of any one of claims 1 to 7, wherein, The first MLD is also used to receive fourth indication information of the second MLD, the fourth indication information being used to indicate that the second MLD does not buffer buffered data corresponding to any second data type.

9. The method of claim 8, wherein, The fourth indication information is a quality of service null (QoS Null) frame, which is a data frame without carrying a payload; a value of a More Data subfield in the QoS Null frame is 0.

10. A communications device, characterized by The apparatus comprises a transceiver and a processor; the transceiver is configured to receive, from the second MLD, buffer data over the first link, the buffer data comprising third indication information; the third indication information is used to indicate whether buffer data corresponding to at least one second data type is buffered in the second MLD, wherein the second data type is any data type mapped to the first link; the processor is configured to determine, according to the third indication information, whether buffer data corresponding to at least one second data type is buffered in the second MLD.

11. The communication apparatus according to claim 10, wherein The communication device has a plurality of stations; the processor is further configured to determine, according to whether buffer data corresponding to at least one second data type is buffered in the second MLD, an operating state of a station corresponding to the first link in the plurality of stations; the operating state is an active state or a dormant state.

12. The communication device of claim 11, wherein the processor is specifically configured to determine, if buffer data corresponding to at least one second data type is buffered in the second MLD, that the operating state of the station corresponding to the first link in the plurality of stations is the active state; and determine, if no buffer data corresponding to any second data type is buffered in the second MLD, that the operating state of the station corresponding to the first link in the plurality of stations is the active state or the dormant state. the third indication information is further used to indicate whether buffer data corresponding to a management frame is buffered in the second MLD.

13. The communication device as claimed in claim 10, characterized in that, the third indication information is a More Data subfield; a value of the More Data subfield is 1, indicating that buffer data corresponding to at least one second data type is buffered in the second MLD; or a value of the More Data subfield is 0, indicating that no buffer data corresponding to any second data type is buffered in the second MLD.

14. The communication apparatus of claim 10, wherein, the third indication information is a More Data subfield; a value of the More Data subfield is 1, indicating that buffer data corresponding to at least one second data type is buffered in the second MLD; or a value of the More Data subfield is 0, indicating that no buffer data corresponding to any second data type is buffered in the second MLD.

15. The communication apparatus of claim 11, wherein, the transceiver is further configured to send, to the second MLD, a power save poll (PS-Poll) frame.

16. The communication apparatus of claim 10, wherein, the transceiver is further configured to receive, from the second MLD, fourth indication information; the fourth indication information is used to indicate that no buffer data corresponding to any second data type is buffered in the second MLD.

17. The communication apparatus according to any one of claims 10-16, wherein, the fourth indication information is a quality of service null (QoS Null) frame, the QoS Null frame being a data frame without carrying a payload, and a value of a More Data subfield in the QoS Null frame is 0.

18. The communication apparatus according to claim 17, wherein comprise at least one processor and an interface; 19. A chip system, characterized by ​ The interface is configured to receive buffer data from the second MLD through the first link, and the buffer data includes third indication information; the third indication information is used to indicate whether buffer data corresponding to at least one second data type is buffered in the second MLD, wherein the second data type is any data type mapped to the first link. The processor is configured to determine, according to the third indication information, whether buffer data corresponding to at least one second data type is buffered in the second MLD.

20. The chip system of claim 19, wherein The processor is further configured to determine, according to whether buffer data corresponding to at least one second data type is buffered in the second MLD, an operating state of a station corresponding to the first link in a plurality of stations; the operating state is an active state or a dormant state.

21. The chip system of claim 20, wherein The processor is specifically configured to determine, if buffer data corresponding to at least one second data type is buffered in the second MLD, that the operating state of the station corresponding to the first link in the plurality of stations is the active state. The processor is specifically configured to determine, if no buffer data corresponding to any second data type is buffered in the second MLD, that the operating state of the station corresponding to the first link in the plurality of stations is the active state or the dormant state.

22. The chip system of claim 19, wherein the first and second chip systems are mounted on a single substrate. The third indication information is further used to indicate whether buffer data corresponding to a management frame is buffered in the second MLD.

23. The chip system of claim 19 or 20, wherein The third indication information is a More Data subfield; a value of the More Data subfield is 1, indicating that buffer data corresponding to at least one second data type is buffered in the second MLD; or a value of the More Data subfield is 0, indicating that no buffer data corresponding to any second data type is buffered in the second MLD.

24. The chip system of claim 19, wherein, The interface is further configured to send a power save poll (PS-Poll) frame to the second MLD.

25. The chip system according to claim 19 or 20, characterized by The interface is further configured to receive fourth indication information from the second MLD; the fourth indication information is used to indicate that no buffer data corresponding to any second data type is buffered in the second MLD.

26. The chip system of claim 25, wherein The fourth indication information is a quality of service (QoS) null frame, which is a data frame without carrying a payload; a value of a More Data subfield in the QoS null frame is 0.

27. A computer readable storage medium, characterized in that, A computer program product for storing a computer program, which, when executed on a computer, causes the computer to perform the method of any one of claims 1-9.

28. A computer program product, characterised in that, A computer program product for storing a computer program, which, when executed on a computer, causes the computer to perform the method of any one of claims 1-9.

Images