WO2021180179A1 - 一种数据缓存情况的确定方法及其装置 - Google Patents

一种数据缓存情况的确定方法及其装置 Download PDF

Info

Publication number
WO2021180179A1
WO2021180179A1 PCT/CN2021/080254 CN2021080254W WO2021180179A1 WO 2021180179 A1 WO2021180179 A1 WO 2021180179A1 CN 2021080254 W CN2021080254 W CN 2021080254W WO 2021180179 A1 WO2021180179 A1 WO 2021180179A1
Authority
WO
WIPO (PCT)
Prior art keywords
mld
data
indication information
data type
cache
Prior art date
Application number
PCT/CN2021/080254
Other languages
English (en)
French (fr)
Inventor
李云波
淦明
郭宇宸
周逸凡
李伊青
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to KR1020227031880A priority Critical patent/KR20220143707A/ko
Priority to JP2022554753A priority patent/JP7389266B2/ja
Priority to BR112022016925A priority patent/BR112022016925A2/pt
Priority to EP21768886.0A priority patent/EP4099755A4/en
Priority to AU2021236081A priority patent/AU2021236081B2/en
Publication of WO2021180179A1 publication Critical patent/WO2021180179A1/zh
Priority to US17/891,785 priority patent/US20220394556A1/en
Priority to US18/331,196 priority patent/US20230319640A1/en
Priority to JP2023194785A priority patent/JP2024020422A/ja

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0037—Inter-user or inter-terminal allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/27—Control channels or signalling for resource management between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This application relates to the field of communication technology, and in particular to a method and device for determining a data cache situation.
  • MLD multi-link devices
  • STA stations
  • a non-access point (non-access point, non-AP) station may be in an active state (active state) or a dormant state (doze state).
  • active state active state
  • dormant state dormant state
  • the link corresponding to the non-AP site is also active, and data can be transmitted between the non-AP site and the AP site through the link; in the non-AP site
  • the link corresponding to the non-AP station is also in the dormant state, and data cannot be transmitted between the non-AP station and the AP station.
  • the AP MLD can buffer the data services to be sent to the non-AP site, and when the non-AP site is active, pass the corresponding non-AP site The link sends the buffered data service to the non-AP site.
  • the non-AP MLD cannot know the buffer status of the buffer data corresponding to the non-AP MLD in the AP MLD, which is not conducive to the non-AP MLD to accurately determine the working status of the associated link. Therefore, how to determine the cache condition of the buffered data corresponding to the non-AP MLD in the AP MLD has become a technical problem to be solved urgently.
  • the embodiment of the present application provides a method and device for determining a data cache condition, which can determine the data cache condition of the data type dimension.
  • an embodiment of the present application provides a method for determining a data buffering condition.
  • the method includes: a first multilink device MLD receives first indication information from a second MLD; and the first indication information is used to indicate the second MLD.
  • the first MLD may have multiple sites; the method may further include: the first MLD determines that at least one of the multiple sites is at least The working status of a site; the working status is active or dormant.
  • the method may further include: the first MLD receives second indication information from the second MLD, where the second indication information is used to determine whether the association identifier of the first MLD is related to the data type supported by the first MLD. Correspondence between.
  • the second indication information indicates at least one association identifier, and the at least one association identifier corresponds to at least one data type.
  • At least one associated identifier (AID) corresponding to at least one data type is indicated by the second indication information, so that the AID can be allocated to the first MLD more flexibly.
  • the first MLD supports multiple data types; the aforementioned second indication information indicates a first association identifier, and the first association identifier corresponds to a first data type among the multiple data types; the method also It may include: the first MLD determines, according to the first association identifier corresponding to the first data type, association identifiers corresponding to data types other than the first data type among the multiple data types.
  • an embodiment of the present application provides another method for determining a data cache situation, the method includes: the second multilink device MLD determines that the cached data corresponding to at least one data type supported by the first MLD is in the second The cache condition in the MLD; determine the cache data corresponding to the association identifier according to the cache condition of the cache 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 Cache status in the second MLD; send first indication information to the first MLD; the first indication information is used to indicate the cache status of the cache data corresponding to the association identifier of the first MLD in the second MLD.
  • the first MLD by indicating the caching situation 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 at least one correspondence between the association identifier and the supported data type.
  • the method may further include: the second MLD sends second indication information to the first MLD, where the second indication information is used to determine whether the association identifier of the first MLD is related to the data type supported by the first MLD. Correspondence between.
  • the second indication information indicates at least one association identifier, and the at least one association identifier corresponds to at least one data type.
  • At least one associated identifier (AID) corresponding to at least one data type is indicated by the second indication information, so that the AID can be allocated to the first MLD more flexibly.
  • the first MLD supports multiple data types; the second indication information indicates a first association identifier, and the first association identifier corresponds to a first data type among the multiple data types.
  • an embodiment of the present application provides yet another method for determining a data buffering situation.
  • the method includes: a first multilink device MLD receives buffered data from a second MLD through a first link, and the buffered data includes a third Indication information; the third indication information is used to indicate whether there is at least one type of cache data corresponding to the second data type cached in the second MLD, where the second data type is any data type mapped to the first link; An MLD determines, according to the third indication information, whether there is at least one type of cache data corresponding to the second data type cached in the second MLD.
  • the third indication information can be used to determine whether there is at least one cached data corresponding to the second data type in the second MLD.
  • the third indication information can be used to determine whether any cached data may pass through the first link. Route to the first MLD.
  • the first MLD has multiple sites; the method further includes: the first MLD determines whether the second MLD has cached data corresponding to at least one second data type in the second MLD, and determines the The working state of the station corresponding to a link; the working state is an active state or a dormant state.
  • the second MLD has cached data corresponding to at least one second data type, it is beneficial to determine a more suitable working state for the station corresponding to the first link.
  • the first MLD determines the working status of the site corresponding to the first link among the multiple sites according to whether there is at least one cache data corresponding to the second data type cached in the second MLD. It may be: if there is at least one cache data corresponding to the second data type cached in the second MLD, the first MLD determines that the working status of the station corresponding to the first link among the multiple stations is active; if the second MLD If there is no cache data corresponding to any second data type in the cache, the first MLD determines that the working state of the station corresponding to the first link among the multiple stations is an active state or a dormant state.
  • the working state of the station corresponding to the first link is the active state. If link 1 has link congestion (or interference, etc.) which results in the inability to transmit buffered data, and the data type of the buffered data to be transmitted on this link 1 is also mapped to the first link, then the data type corresponding to the Before the buffered data is sent, the station corresponding to the first link is in an active state, that is, link 1 is in a dormant state. Therefore, the second MLD can schedule the buffered data to be transmitted on link 1 to the first link for transmission. In this way, it is beneficial to determine a more suitable working state for the site, and it is beneficial to successfully send the buffered data in the second MLD to the first MLD.
  • the third indication information indicates that at least one cache data corresponding to the second data type is cached in the second MLD; the method further includes: the first MLD receives fourth indication information from the second MLD; The fourth indication information is used to indicate that no cache data corresponding to any second data type is cached in the second MLD.
  • the fourth indication information may be a quality of service Null (QoS Null) frame.
  • QoS Null quality of service Null
  • the first MLD may determine, according to the fourth indication information from the second MLD, that no cache data corresponding to any second data type is cached in the second MLD.
  • an embodiment of the present application provides yet another method for determining a data caching situation, the method including: the second multilink device MLD determines whether the second MLD has cached data corresponding to at least one second data type The second data type is any data type mapped to the first link; the second MLD sends buffered data to the first MLD through the first link, and the buffered data includes third indication information; the third indication information It is used to indicate whether there is at least one type of cache data corresponding to the second data type cached in the second MLD.
  • the third indication information can indicate whether there is at least one cached data corresponding to the second data type in the second MLD. In other words, the third indication information can indicate whether any cached data may pass through the first link. Route to the first MLD.
  • the third indication information indicates that at least one cache data corresponding to the second data type is cached in the second MLD; the method may further include: the second MLD sends fourth indication information to the first MLD; The fourth indication information is used to indicate that no cache data corresponding to any second data type is cached in the second MLD.
  • the fourth indication information may be a QoS Null frame.
  • the second MLD cannot send cached data to the second MLD through the first link, and cannot use the third indication information in the cached data to indicate that there is no cached data corresponding to any second data type in the second MLD, By sending the fourth indication information to the first MLD, the second MLD can indicate that no cache data corresponding to any second data type is cached in the second MLD.
  • an embodiment of the present application provides yet another method for determining a data cache condition.
  • the method includes: the first multilink device MLD receives cache data corresponding to the third data type from the second MLD, and the cache data includes the first multilink device MLD.
  • Five indication information the fifth indication information is used to indicate whether there is cache data corresponding to the third data type in the second MLD; the first MLD determines whether the second MLD is cached in the second MLD according to the fifth indication information Cache data corresponding to the three data types.
  • the fifth indication information in the cache data corresponding to the third data type it can be determined whether the cache data corresponding to the third data type is cached in the second MLD.
  • the first MLD has a plurality of sites; the method further includes: the first MLD determines whether the second MLD has cached data corresponding to the third data type in the second MLD, and determines the link between the plurality of sites and the second link. Corresponding to the working state of the station, the third data type is mapped to the second link; the working state is an active state or a dormant state.
  • the method further includes: the first MLD determines whether the second link is mapped with other data types other than the third data type; the first MLD corresponds to whether the third data type is cached in the second MLD
  • the specific implementation manner for determining the working status of the station corresponding to the second link among the multiple stations may be: the first MLD caches the cache data corresponding to the third data type according to whether the second MLD caches the cache data corresponding to the third data type, and the second Whether the link is mapped with data types other than the third data type determines the working status of the station corresponding to the second link among the multiple stations.
  • the fifth indication information indicates that the cache data corresponding to the third data type is not cached in the second MLD; 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, the sixth indication information is used to indicate whether the second MLD has cached data corresponding to at least one fourth data type; the fourth data type is the third data type among the data types supported by the first MLD Any data type other than those.
  • the sixth indication information it can be determined whether the second MLD caches at least one type of cache data corresponding to the 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, and the first MLD can learn more detailed caching status, which is beneficial for the information in the first MLD. The site determines a more appropriate working status.
  • the priority of the fourth data type is higher than the priority of the third data type.
  • an embodiment of the present application provides yet another method for determining a data cache condition, the method includes: the second multilink device MLD determines whether there is cached data corresponding to the third data type in the second MLD; A second MLD sends cache data corresponding to the third data type to the first MLD, where the cache data includes fifth indication information, and the fifth indication information is used to indicate whether the second MLD caches the cache data corresponding to the third data type .
  • the fifth indication information in the cache data corresponding to the third data type it can be determined whether the cache data corresponding to the third data type is cached in the second MLD.
  • the fifth indication information indicates that the cache data corresponding to the third data type is not cached in the second MLD; the cache data corresponding to the third data type sent by the second MLD to the first MLD further includes a sixth indication Information, the sixth indication information is used to indicate whether the second MLD has cached data corresponding to at least one fourth data type; the fourth data type is the data type supported by the first MLD except for the third data type Any data type of.
  • the sixth indication information can indicate whether the second MLD caches at least one type of cache data corresponding to the fourth data type. That is, the sixth indication information can indicate the caching status of the cached data corresponding to the data types other than the third data type in the second MLD.
  • the priority of the fourth data type is higher than the priority of the third data type.
  • an embodiment of the present application provides yet another method for determining a data buffering situation.
  • the method includes: a first multilink device MLD receives seventh indication information from a second MLD, where the seventh indication information is used to indicate The second MLD does not cache the 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; the first MLD determines the second data type according to the seventh indication information.
  • the MLD does not cache the cache data corresponding to the fifth data type.
  • the second MLD when the second MLD does not cache the cache data corresponding to the fifth data type, the second MLD cannot send the cache data corresponding to the fifth data type to the second MLD, and the first MLD cannot pass the fifth data.
  • the "More Data" subfield in the cache data corresponding to the type determines that the second MLD does not cache the cache data corresponding to the fifth data type.
  • the first MLD can determine that the second MLD does not cache the cache data corresponding to the fifth data type.
  • the first MLD has multiple sites; the method further includes: the first MLD determines that the third link of the multiple sites corresponds to the third link according to the second MLD not having cached data corresponding to the fifth data type.
  • the aforementioned fifth data type is mapped to the third link; the working state is the active state or the dormant state.
  • the cached data corresponding to the fifth data type is not cached, which is beneficial to determine a more suitable working state for the station corresponding to the third link.
  • an embodiment of the present application provides yet another method for determining a data caching situation.
  • the method includes: the second multilink device MLD determines that the second MLD does not have cached data corresponding to the fifth data type;
  • the fifth data type is any one of the data types supported by the first MLD;
  • the second MLD sends seventh indication information to the first MLD, and the seventh indication information is used to indicate that the second MLD does not buffer the fifth The cached data corresponding to the data type.
  • the second MLD when the second MLD does not cache the cache data corresponding to the fifth data type, the second MLD cannot send the cache data corresponding to the fifth data type to the second MLD, nor can it pass the cache data corresponding to the fifth data type.
  • the More Data subfield in the cache data indicates that the second MLD does not cache the cache data corresponding to the fifth data type.
  • the second MLD by sending the seventh indication information to the first MLD, the second MLD can determine that the second MLD does not cache the cache data corresponding to the fifth data type.
  • an embodiment of the present application provides yet another method for determining a data buffering situation.
  • the method includes: a first multilink device MLD receives eighth indication information from a second MLD through a fourth link, and the eighth indication The information is used to indicate that the second MLD does not have cached data corresponding to any data type mapped to the fourth link; the first MLD determines that the second MLD does not cache the cached data corresponding to any data type mapped to the fourth link according to the eighth indication information. Cache data corresponding to any data type of the link.
  • the first MLD can determine that the second MLD has not cached the cache data corresponding to any data type mapped to the fourth link, so that it can be determined that the subsequent second MLD will not Send data to the first MLD through the fourth link.
  • the first MLD has a plurality of stations; the method further includes: the first MLD determines a plurality of stations according to the cache data corresponding to any data type mapped to the fourth link that is not cached in the second MLD The working state of the station corresponding to the fourth link in the station; the working state is an active state or a dormant state.
  • the cache data corresponding to any data type mapped to the fourth link is not cached, which is beneficial to determine a more suitable working state for the station corresponding to the fourth link.
  • an embodiment of the present application provides yet another method for determining a data cache condition, the method includes: the second multilink device MLD determines that the second MLD does not cache any data type corresponding to the fourth link The second MLD sends eighth indication information to the first MLD through the fourth link, the eighth indication information is used to indicate that the second MLD does not cache any data type corresponding to the fourth link Cached data.
  • the second MLD may send eighth indication information to the first MLD to indicate that the second MLD does not cache the cached data corresponding to any data type mapped to the fourth link, that is, instruct the subsequent second MLD The second MLD will not send data to the first MLD through the fourth link.
  • an embodiment of the present application provides yet another method for determining a data cache condition.
  • the method includes: a first multilink device MLD receives ninth indication information from a second MLD, and the ninth indication information is used for Indicates the caching status of the cache data corresponding to at least one data type supported by the first MLD in the second MLD; the first MLD determines that the cache data corresponding to the at least one data type is in the second MLD according to the ninth indication information The cache situation.
  • the first MLD can determine, according to the ninth indication information, the caching status of the cached data corresponding to more than one data type in the second MLD.
  • the first MLD has multiple sites; the method further includes: the first MLD determines at least one of the multiple sites according to the cache condition of the cached data corresponding to the at least one data type in the second MLD The working status of the site; the working status is active or dormant.
  • an embodiment of the present application provides yet another method for determining a data cache situation, the method includes: the second multilink device MLD determines that the cache data corresponding to at least one data type supported by the first MLD is in the first MLD 2. Cache situation in the MLD; the second MLD sends ninth indication information to the first MLD, where the ninth indication information is used to indicate the cache of the cache data corresponding to at least one data type supported by the first MLD in the second MLD Condition.
  • the second MLD may indicate to the first MLD the caching status of the cached data corresponding to more than one data type in the second MLD through the ninth indication information.
  • an embodiment of the present application provides yet another method for determining a data buffering situation.
  • the method includes: a first multilink device MLD receives tenth indication information from a second MLD, and the tenth indication information is used for Indicate the buffering situation of the buffer data corresponding to at least one data type mapped to at least one link corresponding to the first MLD in the second MLD; the first MLD determines the data mapped to the at least one link according to the tenth indication information The cache situation of the cache data corresponding to the at least one data type in the second MLD.
  • the tenth indication information it is possible to determine the buffering situation of the buffered data corresponding to the at least one data type mapped to the at least one link in the second MLD. In this way, the caching situation of the cached data in the second MLD can be determined in more detail.
  • the first MLD has a plurality of stations; the method further includes: the first MLD according to the cache situation of the cache data corresponding to the at least one data type mapped to the at least one link in the second MLD, Determine the working status of at least one of the multiple stations; the working status is active or dormant.
  • an embodiment of the present application provides yet another method for determining a data cache condition, the method including: a second multilink device MLD determines at least one data type mapped to at least one link corresponding to the first MLD Cache status of the corresponding cached data in the second MLD; the second MLD sends tenth indication information to the first MLD, and the tenth indication information is used to indicate at least one type of data mapped to at least one link corresponding to the first MLD The cache status of the cache data corresponding to the type in the second MLD.
  • the second MLD may indicate to the first MLD the caching status of the cache data corresponding to the at least one data type mapped to the at least one link in the second MLD through the tenth indication information. In this way, the cache condition of the cached data in the second MLD can be indicated in more detail.
  • an embodiment of the present application provides a communication device that can implement the above-mentioned first aspect, third aspect, fifth aspect, seventh aspect, ninth aspect, eleventh aspect, or thirteenth aspect.
  • the function of the communication device may have some or all of the functions in the embodiments of the present application, or may be capable of independently implementing any of the embodiments of the present application.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above-mentioned functions.
  • the structure of the communication device may include a processing unit and a communication unit, and the processing unit is configured to support the communication device to perform corresponding functions in the foregoing method.
  • the communication unit is used to support communication between the communication device and other devices.
  • the communication device may further include a storage unit for coupling with the processing unit and the sending unit, which stores computer programs and data necessary for the communication device.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the first aspect, the communication device includes:
  • the communication unit is configured 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 in the second MLD;
  • the processing unit is configured to determine, according to the first indication information and the correspondence between the association identifier of the first MLD and the data types supported by the first MLD, whether the cache data corresponding to at least one data type is in the second MLD Cache situation.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the first aspect, the communication device includes:
  • a transceiver configured to receive first indication information from the second MLD; the first indication information is used to indicate the buffering status of the buffered data corresponding to the associated identifier of the communication device in the second MLD;
  • the processor is configured to determine, according to the first indication information and the correspondence between the association identifier of the first MLD and the data type supported by the first MLD, whether the cache data corresponding to at least one data type is in the second MLD Cache situation.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the third aspect, the communication device includes:
  • the communication unit is configured to receive buffered data from the second MLD through the first link, the buffered data includes third indication information; the third indication information is used to indicate whether there is at least one second data type corresponding to the buffer in the second MLD Cached data of, where the second data type is any data type mapped to the first link;
  • the processing unit is configured to determine, according to the third indication information, whether there is at least one type of cache data corresponding to the second data type cached in the second MLD.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the third aspect, the communication device includes:
  • the transceiver is configured to receive buffered data from the second MLD through the first link, the buffered data includes third indication information; the third indication information is used to indicate whether there is at least one second data type corresponding to the buffer in the second MLD Cached data of, where 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 there is at least one type of cache data corresponding to the second data type cached in the second MLD.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the fifth aspect, the communication device includes:
  • the communication unit is configured to receive buffer data corresponding to the third data type from the second MLD, where the buffer data includes fifth indication information, and the fifth indication information is used to indicate whether the second MLD has buffered data corresponding to the third data type.
  • Cache data ;
  • the processing unit is configured to determine, according to the fifth indication information, whether there is cache data corresponding to the third data type in the second MLD.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the fifth aspect, the communication device includes:
  • the transceiver is configured to receive buffer data corresponding to the third data type from the second MLD, where the buffer data includes fifth indication information, and the fifth indication information is used to indicate whether there is a buffer corresponding to the third data type in the second MLD Cache data;
  • the processor is configured to determine, according to the fifth indication information, whether there is cache data corresponding to the third data type in the second MLD.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the seventh aspect, the communication device includes:
  • the communication unit is configured to receive seventh indication information from the second MLD, where the seventh indication information is used to indicate that the second MLD does not have cached data corresponding to the fifth data type; the fifth data type is used by the communication device Any of the supported data types;
  • the processing unit is configured to determine, according to the seventh indication information, that the second MLD does not cache the cache data corresponding to the fifth data type.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the seventh aspect, the communication device includes:
  • the transceiver is configured to receive seventh indication information from the second MLD, where the seventh indication information is used to indicate that the second MLD does not have cached data corresponding to the fifth data type; the fifth data type is used by the communication device Any of the supported data types;
  • the processor is configured to determine, according to the seventh indication information, that the second MLD does not cache the cache data corresponding to the fifth data type.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the ninth aspect, the communication device includes:
  • the communication unit is configured to receive eighth indication information from the second MLD via the fourth link, where the eighth indication information is used to indicate that the second MLD does not have a cache corresponding to any data type mapped to the fourth link data;
  • the processing unit is configured to determine, according to the eighth indication information, that the second MLD does not have cached data corresponding to any data type mapped to the fourth link.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the ninth aspect, the communication device includes:
  • a transceiver configured to receive eighth indication information from the second MLD through the fourth link, where the eighth indication information is used to indicate that the second MLD does not have a cache corresponding to any data type mapped to the fourth link data;
  • the processor is configured to determine, according to the eighth indication information, that the second MLD does not have cached data corresponding to any data type mapped to the fourth link.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the eleventh aspect, the communication device includes:
  • the communication unit is configured to receive ninth indication information from the second MLD, where the ninth indication information is used to indicate the buffer status of the buffered data corresponding to at least one data type supported by the communication device in the second MLD;
  • the processing unit is configured to determine, according to the ninth indication information, the caching situation of the cached data corresponding to at least one data type in the second MLD.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the eleventh aspect, the communication device includes:
  • a transceiver configured to receive ninth indication information from the second MLD, where the ninth indication information is used to indicate the buffer status of the buffered data corresponding to at least one data type supported by the communication device in the second MLD;
  • the processor is configured to determine, according to the ninth indication information, a cache situation of the cache data corresponding to at least one data type in the second MLD.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the thirteenth aspect, the communication device includes:
  • the communication unit is configured to receive tenth indication information from the second MLD, where the tenth indication information is used to indicate that buffer data corresponding to at least one data type mapped to at least one link corresponding to the communication device is in the second MLD Cache situation;
  • the processing unit is configured to determine, according to the tenth indication information, the buffering situation of the buffered data corresponding to the at least one data type mapped to the at least one link in the second MLD.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the first MLD in the method example described in the thirteenth aspect, the communication device includes:
  • the transceiver is configured to receive tenth indication information from the second MLD, where the tenth indication information is used to indicate that buffer data corresponding to at least one data type mapped to at least one link corresponding to the communication device is in the second MLD Cache situation;
  • the processor is configured to determine, according to the tenth indication information, a buffering situation of the buffered data corresponding to the at least one data type mapped to the at least one link in the second MLD.
  • the embodiments of the present application provide another communication device that can implement the second, fourth, sixth, eighth, tenth, twelfth, or tenth aspect described above.
  • the function of the communication device may have some or all of the functions in the embodiments of the present application, or may be capable of independently implementing any of the embodiments of the present application.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above-mentioned functions.
  • the structure of the communication device may include a processing unit, a storage unit, and a communication unit, and the processing unit is configured to support the communication device to perform corresponding functions in the foregoing method.
  • the communication unit is used to support communication between the communication device and other devices.
  • the storage unit is used for coupling with the processing unit and the sending unit, and it stores computer programs and data necessary for the communication device.
  • the storage unit is used to store cache data.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the second aspect, the communication device includes:
  • the processing unit is configured to determine the caching status of the cached data corresponding to at least one data type supported by the first MLD in the storage unit; according to the caching status of the cached data corresponding to the at least one data type in the storage unit, and the first Correspondence between the associated identifier of the MLD and the supported data types, and determine the caching situation of the cached data corresponding to the associated identifier in the storage unit;
  • the communication unit is configured to send first indication information to the first MLD; the first indication information is used to indicate the caching status of the cache data corresponding to the associated identifier of the first MLD in the storage unit.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the second aspect, the communication device includes:
  • the processor is configured to determine the cache condition of the cache data corresponding to at least one data type supported by the first MLD in the memory; according to the cache condition of the cache data corresponding to the at least one data type in the memory, and the cache condition of the first MLD Correspondence between the association identifier and the supported data types, and determine the caching situation of the cache data corresponding to the association identifier in the memory;
  • the transceiver is configured to send first indication information to the first MLD; the first indication information is used to indicate the caching status of the cache data corresponding to the associated identifier of the first MLD in the memory.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the fourth aspect, the communication device includes:
  • a processing unit configured to determine whether there is cache data corresponding to at least one second data type in the storage unit; the second data type is any data type mapped to the first link;
  • the communication unit is configured to send buffered data to the first MLD through the first link, where the buffered data includes third indication information; the third indication information is used to indicate whether at least one second data type is buffered in the storage unit Corresponding cache data.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the fourth aspect, the communication device includes:
  • a processor configured to determine whether there is cache data corresponding to at least one second data type cached in the memory; the second data type is any data type mapped to the first link;
  • the transceiver is configured to send buffered data to the first MLD via the first link, the buffered data includes third indication information; the third indication information is used to indicate whether there is at least one second data type corresponding to the buffer in the memory Cached data.
  • the communication device when the communication device has part or all of the functions of the second MLD in the method example described in the sixth aspect, the communication device includes:
  • the processing unit is configured to determine whether there is cached data corresponding to the third data type in the storage unit;
  • the communication unit is configured to send buffer data corresponding to the third data type to the first MLD, where the buffer data includes fifth indication information, and the fifth indication information is used to indicate whether the storage unit has buffer data corresponding to the third data type. Cache data.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of the second MLD in the method example described in the sixth aspect, the communication device includes:
  • the processor is configured to determine whether there is cache data corresponding to the third data type in the memory
  • the transceiver is configured to send buffer data corresponding to the third data type to the first MLD, where the buffer data includes fifth indication information, and the fifth indication information is used to indicate whether a buffer corresponding to the third data type is buffered in the memory data.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the eighth aspect, the communication device includes:
  • a processing unit configured to determine that the storage unit does not have cached data corresponding to the fifth data type; the fifth data type is any data type among the data types supported by the first MLD;
  • the communication unit is configured to send seventh indication information to the first MLD, where the seventh indication information is used to indicate that the storage unit does not have cached data corresponding to the fifth data type.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the eighth aspect, the communication device includes:
  • a processor configured to determine that the cache data corresponding to the fifth data type is not cached in the memory; the fifth data type is any data type among the data types supported by the first MLD;
  • the transceiver is configured to send seventh indication information to the first MLD, where the seventh indication information is used to indicate that the memory does not have cached data corresponding to the fifth data type.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the tenth aspect, the communication device includes:
  • a processing unit configured to determine that the storage unit does not cache any cached data corresponding to any data type mapped to the fourth link;
  • the communication unit is configured to send eighth indication information to the first MLD through the fourth link, where the eighth indication information is used to indicate that the storage unit does not cache any cache data corresponding to any data type mapped on the fourth link .
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the tenth aspect, the communication device includes:
  • a processor configured to determine that the memory does not have cached data corresponding to any data type mapped to the fourth link;
  • the transceiver is configured to send eighth indication information to the first MLD through the fourth link, where the eighth indication information is used to indicate that the memory does not have cached data corresponding to any data type mapped on the fourth link.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the twelfth aspect, the communication device includes:
  • a processing unit configured to determine the cache condition of the cache data corresponding to at least one data type supported by the first MLD in the storage unit;
  • the communication unit is configured to send ninth indication information to the first MLD, where the ninth indication information is used to indicate the cache condition of the cache data corresponding to at least one data type supported by the first MLD in the storage unit.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the twelfth aspect, the communication device includes:
  • a processor configured to determine a cache condition in the memory of cache data corresponding to at least one data type supported by the first MLD;
  • the transceiver is configured to send ninth indication information to the first MLD, where the ninth indication information is used to indicate the caching status of the cache data corresponding to at least one data type supported by the first MLD in the memory.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the fourteenth aspect, the communication device includes:
  • a processing unit configured to determine the buffering condition of the buffered data corresponding to the at least one data type mapped to the at least one link corresponding to the first MLD in the storage unit;
  • the communication unit is configured to send tenth indication information to the first MLD, where the tenth indication information is used to indicate the buffering of the buffer data corresponding to the at least one data type mapped to the at least one link corresponding to the first MLD in the storage unit Condition.
  • the processing unit may be a processor
  • the communication unit may be a transceiver or a communication interface
  • the storage unit may be a memory.
  • the communication device when the communication device has part or all of the functions of implementing the second MLD in the method example described in the fourteenth aspect, the communication device includes:
  • a processor configured to determine a cache condition in the memory of cache data corresponding to at least one data type mapped to at least one link corresponding to the first MLD;
  • the transceiver is configured to send tenth indication information to the first MLD, where the tenth indication information is used to indicate the buffer status of the buffer data corresponding to at least one data type mapped to the at least one link corresponding to the first MLD in the memory .
  • an embodiment of the present invention provides a computer-readable storage medium for storing a computer program used for the above-mentioned first MLD.
  • the first MLD executes the above-mentioned first aspect, The method of the third, fifth, seventh, ninth, eleventh, or thirteenth aspect.
  • an embodiment of the present invention provides a computer-readable storage medium for storing a computer program used for the above-mentioned second MLD.
  • the second MLD executes the above-mentioned second aspect, The fourth, sixth, eighth, tenth, twelfth, or fourteenth aspect methods.
  • this application also provides a computer program product including a computer program, which when it runs on a computer, enables the computer to execute the above-mentioned first, third, fifth, seventh, and ninth aspects.
  • a computer program product including a computer program, which when it runs on a computer, enables the computer to execute the above-mentioned first, third, fifth, seventh, and ninth aspects.
  • this application also provides a computer program product including a computer program, which when it runs on a computer, enables the computer to execute the above-mentioned second, fourth, sixth, eighth, and tenth aspects. Aspect, the twelfth aspect, or the method described in the fourteenth aspect.
  • the present application provides a chip system including at least one processor and an interface for supporting the first MLD to implement the first aspect, the third aspect, the fifth aspect, the seventh aspect, and the first aspect.
  • the function involved in the ninth aspect, the eleventh aspect, or the thirteenth aspect for example, determining or processing at least one of the data and information involved in the foregoing method.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the first MLD.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the present application provides a chip system that includes at least one processor, at least one memory, and an interface, and is used to support the second MLD to implement the second, fourth, sixth, and third aspects.
  • the eighth aspect, the tenth aspect, the twelfth aspect, or the fourteenth aspect involves functions, for example, determining or processing at least one of the data and information involved in the above-mentioned methods.
  • the memory is used to store cached data, and computer programs and data necessary for the second MLD.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method for determining a data caching situation provided by an embodiment of the present application
  • FIG. 3a is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application
  • FIG. 3b is a schematic diagram of a management frame supported by the first MLD-a and the second MLD-b and the AID corresponding to each AC according to an embodiment of the present application;
  • 4a is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application.
  • 4b is a schematic diagram of a scenario in which a second MLD sends buffered data to the first MLD according to an embodiment of the present application;
  • FIG. 5 is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application.
  • FIG. 6a is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application.
  • Figure 6b is a schematic diagram of a scenario for determining the working status of a link provided by an embodiment of the present application.
  • Figure 6c is a schematic diagram of another scenario for determining the working status of a link provided by an embodiment of the present application.
  • Figure 6d is a schematic diagram of yet another scenario for determining the working status of a link provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application.
  • FIG. 9a is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application.
  • Figure 9b is a schematic diagram of a More Data Per TID Per link subfield provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a chip provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of another chip provided by an embodiment of the present application.
  • the TIM field may be included in the TIM element carried in the 802.11 beacon (Beacon) frame.
  • AP MLD can periodically send 802.11 beacon frames to one or more non-AP MLDs, and the TIM element carried in the beacon frame can determine that the buffered data corresponding to each station included in each non-AP MLD is in the AP Cache situation in MLD.
  • the caching status of the cached data corresponding to a site in the AP MLD may refer to whether the AP MLD caches data to be sent to the site.
  • a non-AP site can have two working modes, one is a non-energy-saving mode, and the other is an energy-saving mode.
  • the non-energy-saving mode the non-AP station is active regardless of whether data needs to be transmitted between the non-AP station and the AP station.
  • the energy-saving mode when data needs to be transmitted between a non-AP site and an AP site, the non-AP site can be active; when there is no need to transmit data between a non-AP site and an AP site, the non-AP site The site can be in a dormant state, which can save non-AP MLD power consumption.
  • a non-AP station in the energy-saving mode can periodically wake up (that is, in an active state) to receive beacon frames sent by the AP MLD to determine whether the AP MLD buffers data to be sent to the non-AP station. If the AP MLD does not cache the data corresponding to the non-AP site, the non-AP site can be converted to the dormant state; if the AP MLD caches the data corresponding to the non-AP site, the non-AP site can be converted to Active state to receive corresponding data.
  • the 802.11 beacon frame may include a TIM beacon frame or a delivery traffic indication map (DTIM) beacon frame. Both the TIM beacon frame and the DTIM beacon frame carry TIM elements.
  • the fields included in the TIM element may be as shown in Table 1.
  • the element identifier (identifier, ID) field used to identify the element as a TIM element.
  • Length field used to indicate the number of bytes occupied by the TIM element.
  • the DTIM count field is used to indicate how many TIM beacon frames appear before the arrival of the next DTIM beacon frame.
  • the DTIM period field indicates the arrival interval of two adjacent DTIM beacon frames.
  • the element ID field, length field, DTIM count field, DTIM period field, and bitmap control field can each occupy 1 byte. Bit 0 in the bitmap control field can indicate whether there is a downlink multicast data service when the AP sends a DTIM beacon frame, and bits 1-7 can indicate the offset of part of the virtual bitmap, and the offset is expressed in bytes.
  • Some virtual bits are the TIM field, and each bit in the TIM field corresponds to an association identifier (AID). For example, if the offset is 0, part of the virtual bitmap can start from AID1. If the offset is 1, part of the virtual bitmap can start from AID9.
  • Enhanced distributed channel access edca It is conducive to high-priority packets to enjoy the right of priority transmission and more bandwidth.
  • the four ACs are: voice (AC_VO), video (AC_VI), background (AC_BK), and best effort (AC_BE).
  • the upper layer entity can distinguish the quality of service (quality of service, QoS) supported by the MAC service data unit (MSDU) in the medium access control (MAC) layer through the TID.
  • QoS quality of service
  • MSDU MAC service data unit
  • MAC medium access control
  • 8 TIDs can be supported in EDCA, and the 8 TIDs are: TID0 ⁇ TID7.
  • AC and TID have a corresponding relationship.
  • One type of AC can correspond to one or more types of TID, and one type of TID corresponds to one type of AC.
  • the management frame can be used to manage data packets, control the network, and so on.
  • Management frames may include but are not limited to: beacon frames, probe request (Probe Request) frames, probe response (Probe Response) frames, independent basic service set (Independent Basic Service Set, IBSS) notification transmission indication message (Announcement Traffic Indication Message, ATIM) frame, Disassociation frame, Deauthentication frame, Association Request frame, Reassociation Request frame, Authentication frame, Aciton frame.
  • the management frame mentioned in the embodiment of this application may refer to any one or more of the foregoing management frames.
  • the beacon frame can be used to declare the existence of a certain network.
  • the mobile workstation can scan which 802.11 networks are in the area through the Probe Request frame. If the network checked by the Probe Request frame is compatible with it, the network responds with the Probe Request frame.
  • the IBSS workstation buffers the frame for the receiver in the dormant state, and sends an IBSS ATIM frame during the transmission period to notify the other party that there is a message to be transmitted.
  • Both the Disassociation frame and the Deauthentication frame can be used to end an authentication relationship.
  • the mobile workstation finds a compatible network and passes the authentication, and then sends an Association Request frame to try to join the network. Mobile workstations located in the same extended service area but wandering between different basic service areas will reassociate with the network through the Reassociation Request frame when using the distributed system again.
  • the Aciton frame is used to trigger the measurement action.
  • the embodiments of the present application provide a communication method applied to a wireless communication system.
  • the wireless communication system may be a wireless local area network (WLAN) or a cellular network.
  • the method may be used by a communication device or a communication device in the wireless communication system.
  • the communication device can be a wireless communication device that supports parallel transmission of multiple links, for example, called a multi-link device or a multi-band device. device). Compared with devices that only support single link transmission, multi-link devices have higher transmission efficiency and higher throughput.
  • the multi-link device includes one or more affiliated STAs (affiliated STA), and the affiliated STA is a logical station and can work on one link.
  • the subordinate station may be an access point (Access Point, AP) or a non-Access Point station (non-Access Point Station, non-AP STA).
  • this application refers to a multi-link device whose station is an AP may be called a multi-link AP or a multi-link AP device or an AP multi-link device (AP multi-link device), and the station to which it belongs is a non-
  • the multi-link device of the AP STA may be called a multi-link STA or a multi-link STA device or an STA multi-link device (STA multi-link device).
  • STA multi-link device STA multi-link device.
  • “multi-link device includes subordinate STA” is also briefly described as “multi-link device includes STA” in the embodiment of the present application.
  • a multi-link device includes multiple logical sites, and each logical site works on a link, but allows multiple logical sites to work on the same link.
  • the link identification mentioned below characterizes a station working on a link, that is, if there are more than one station on a link, more than one link identification is required to characterize them.
  • the link mentioned below sometimes also refers to the station working on that link.
  • link identifiers can be used to identify a link or a station on a link.
  • the multi-link AP device and the multi-link STA device may first negotiate or communicate the corresponding relationship between the link identifier and a link or a station on a link. Therefore, in data transmission, there is no need to transmit a large amount of signaling information to indicate a link or a station on the link, and it is sufficient to carry a link identifier, which reduces signaling overhead and improves transmission efficiency.
  • Multi-link devices can follow the 802.11 series of protocols to achieve wireless communication, for example, follow Extremely High Throughput (EHT) sites, or follow 802.11be-based or compatible 802.11be-supported sites to achieve communication with other devices, of course
  • EHT Extremely High Throughput
  • Other devices can be multi-link devices or not.
  • the multi-link device in the embodiment of the present application may be a device with a single antenna or a device with multiple antennas.
  • it can be a device with more than two antennas.
  • the embodiment of the present application does not limit the number of antennas included in the multi-link device.
  • the multi-link device may allow the same access type of service to be transmitted on different links, and even allow the same data packet to be transmitted on different links; it may also not allow the same access type of service Transmission on different links, but allows different access types of services to be transmitted on different links.
  • the available frequency bands for multi-link devices include: sub 1GHz, 2.4GHz, 5GHz, 6GHz and high frequency 60GHz.
  • the multi-link device is a device with wireless communication function.
  • the device may be a complete device, or a chip or processing system installed in the complete device.
  • the device is equipped with these chips or processing systems.
  • the methods and functions of the embodiments of the present application can be implemented under the control of these chips or processing systems.
  • the multi-link STA in the embodiment of the present application has a wireless transceiver function, may support 802.11 series protocols, and can communicate with a multi-link AP or other multi-link STAs or single-link devices, for example, a multi-link STA It is any user communication device that allows the user to communicate with the AP and then with the WLAN.
  • a multi-link STA can be a tablet computer, desktop, laptop, notebook computer, Ultra-mobile Personal Computer (UMPC), handheld computer, netbook, personal digital assistant (Personal Digital Assistant, PDA) , Mobile phones and other user equipment that can be connected to the Internet, or Internet of Things nodes in the Internet of Things, or in-vehicle communication devices in the Internet of Vehicles, etc.
  • the multi-link STA can also be the chips and processing systems in these terminals.
  • the multi-link AP in the embodiment of the present application provides services for the multi-link STA, and can support the 802.11 series of protocols.
  • a multi-link AP may be a communication entity such as a communication server, a router, a switch, or a bridge, or the multi-link AP may include various forms of macro base stations, micro base stations, relay stations, etc., of course, a multi-link AP is also It may be the chips and processing systems in these various forms of equipment, so as to realize the methods and functions of the embodiments of the present application.
  • multi-link devices can support high-speed and low-latency transmission.
  • multi-link devices can also be applied in more scenarios, such as sensor nodes in smart cities (for example, Smart water meters, smart electricity meters, smart air detection nodes), smart devices in smart homes (such as smart cameras, projectors, display screens, TVs, stereos, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (such as AR, VR and other wearable devices), smart devices in smart offices (such as printers, projectors, etc.), connected vehicles in the Internet of Vehicles, and some infrastructure in daily life scenarios (such as vending machines, supermarkets, etc.) Self-service navigation station, self-service cash register equipment, self-service ordering machine, etc.).
  • the specific forms of the multi-link STA and the multi-link AP are not particularly limited, which are only exemplary descriptions here.
  • the 802.11 protocol may be a protocol that supports 802.11be or is compatible with 802.11be.
  • FIG. 1 is a schematic structural diagram of a communication system provided by an embodiment of the application.
  • the communication system may include, but is not limited to, a first MLD and a second MLD.
  • the number and form of devices shown in FIG. 1 are used as examples and do not constitute a limitation to the embodiment of the present application. In actual applications, it may include two or two The above first MLD, and two or more second MLDs.
  • the communication system shown in FIG. 1 takes as an example a first MLD101 and a second MLD102.
  • the second MLD102 can be used to determine the buffer status of the buffered 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 first MLD101 Cache status of cached data corresponding to at least one data type supported by one MLD101 in the second MLD102.
  • the first MLD 101 After the first MLD 101 receives the instruction information from the second MLD 102, it can determine the caching status of the cache data corresponding to at least one data type supported by the first MLD 101 in the second MLD 102 according to the instruction information.
  • the data type supported by the first MLD 101 may include at least one of a service type and a management frame, where the service type may refer to AC or TID.
  • the first MLD101 may support one or more data types. Taking the data type supported by the first MLD101 as data type 1 as an example, the cache condition of the cached data corresponding to the data type 1 in the second MLD102 may refer to: whether the cached data to be sent to the first MLD101 is cached in the second MLD102 , And the data type of the cached data is data type 1.
  • the data type supported by the first MLD 101 may be determined during the process of establishing a connection between the first MLD 101 and the second MLD 102.
  • the data types supported by different first MLD101 may be the same or different.
  • the second MLD102 can determine the caching status of the cached data corresponding to at least one data type supported by each first MLD101 in the second MLD102;
  • An MLD101 sends instructions.
  • the second MLD may broadcast indication information to each first MLD.
  • the indication information received by each first MLD is the same, and the indication information may indicate at least one type of data supported by each first MLD 101 The cache status of the cache data corresponding to the type in the second MLD102.
  • the second MLD may respectively broadcast indication information to each first MLD.
  • the indication information received by each first MLD is different, and the indication information received by each first MLD is used to indicate that the first MLD 101 supports Cache status of the cached data corresponding to at least one data type in the second MLD 102. It should be noted that at least one mentioned in the embodiments of the present application may be described as one or more.
  • each second MLD 102 (such as the second MLD-a and the second MLD-b) can determine the cache corresponding to at least one data type supported by the first MLD 101
  • the data is buffered in the second MLD 102, and indication information is sent to the first MLD 101 respectively.
  • the indication information received by the first MLD 101 from the second MLD-a may indicate the caching status of the cached data corresponding to at least one data type supported by the first MLD 101 in the second MLD-a.
  • the indication information received by the first MLD 101 from the second MLD-b may indicate the buffer status of the buffered data corresponding to at least one data type supported by the first MLD 101 in the second MLD-b.
  • FIG. 2 is a schematic flowchart of a method for determining a data caching situation provided by an embodiment of the present application.
  • This method describes in detail how the first MLD determines the cache condition of the cached data corresponding to at least one data type in the second MLD according to the indication information from the second MLD.
  • the execution subject of step S201 to step S202 is the second MLD, or the chip in the second MLD
  • the execution subject of step S203 is the first MLD, or the chip in the first MLD.
  • the second MLD and the first MLD are executed.
  • An MLD is an example of the execution subject of the method for determining the data caching situation. As shown in Figure 2, the method may include but is not limited to the following steps:
  • Step S201 The second multi-link device MLD determines the buffer status of the buffered data corresponding to at least one data type supported by the first MLD in the second MLD.
  • the second MLD may determine whether the cache data corresponding to at least one data type supported by the first MLD is cached in the second MLD.
  • the second MLD can determine whether to buffer cache data to be sent to the first MLD, and the data type of the cache data is a data type supported by the first MLD.
  • the second MLD can determine whether the cache data corresponding to the various data types supported by the first MLD are cached in the second MLD. For example, when the first MLD supports 3 data types (data type 1, data type 2, and data type 3), the second MLD can respectively determine whether the cache data corresponding to data type 1, data type 2, and data type 3 is cached in This second MLD. In another implementation manner, the second MLD may determine whether the cache data corresponding to data type 1 is cached in the second MLD, and determine whether the cache data corresponding to at least one of data type 2 and data type 3 is cached in the second MLD. Cached in the second MLD.
  • the second MLD when the cache data corresponding to the data type 1 is cached in the cache area a, and the cache data corresponding to the data type 2 and the data type 3 are cached in the cache area b. If the second MLD detects that there is a bufferable unit (BU) in the cache area a, it means that the second MLD has cached data corresponding to data type 1; if the second MLD detects that there is no cache unit in the cache area a , Which means that there is no cached data corresponding to data type 1 in the second MLD.
  • BU bufferable unit
  • the second MLD detects that there is a cache unit in the cache area b, it means that the second MLD has cached data corresponding to at least one of data type 2 and data type 3; if the second MLD detects There is no cache unit in the cache area b, which means that there is no cache data corresponding to data type 2 and no cache data corresponding to data type 3 in the second MLD.
  • the cache area occupied by the cache data corresponding to the above data type 1, data type 2, and data type 3 in the second MLD is only for example, and does not constitute a limitation to the embodiment of the present application.
  • the embodiment of the present application does not limit how the cached data corresponding to at least one data type supported by the first MLD is cached in the second MLD.
  • the second MLD may cache cache data corresponding to at least one data type supported by the first MLD in a common cache area.
  • the second MLD may cache cache data corresponding to various data types supported by the first MLD in a separate cache area.
  • the second MLD may combine a public cache plus an independent cache to cache the cache data corresponding to the data type supported by the first MLD.
  • the second MLD may cache the cache data corresponding to the service type supported by the first MLD in one cache area, and cache the cache data corresponding to the management frame in another cache area.
  • the first MLD and the second MLD may be connected by multiple links.
  • the second MLD may determine which link the cache data corresponding to at least one data type supported by the first MLD will be transmitted to the first MLD, and further, the second MLD may be transmitted through the same
  • the buffered data transmitted by the link is buffered in a separate buffer area.
  • the second MLD may send buffered data to the first MLD through the station, and the station in the second MLD may schedule the buffered data from one or more buffer areas and send it to the first MLD.
  • the second MLD can respectively determine whether the cache data corresponding to at least one data type supported by each first MLD is in the second MLD. Cache situation.
  • Step S202 The second MLD sends indication information to the first MLD, where the indication information is used to indicate the caching status of the cached data corresponding to at least one data type supported by the first MLD in the second MLD.
  • the second MLD may send indication information to the first MLD after determining the cache condition of the buffered data corresponding to at least one data type supported by the first MLD in the second MLD.
  • each bit in the indication information may correspond to one or more data types supported by the first MLD, and the value of each bit may indicate whether the buffered data of the data type corresponding to the bit is cached in the first MLD.
  • the indication information may also be referred to as ninth indication information.
  • the foregoing indication information may refer to the bits occupied by the control type a in the EHT A-control field in the MAC frame.
  • the EHT A-control field can support 8 control types, that is, the bits corresponding to the EHT A-control field can carry information of the 8 control types. Among them, the relevant information of the 8 control types can be shown in Table 2. It should be noted that the EHT A-control field is just an example. For example, it can also be the HT control field where the EHT A-control or HE A-control field is located. With the evolution of the standard version, the name of this field may change, but as long as Indicating the corresponding function is the scope of the embodiments of this application.
  • the service type is AC
  • the newly added type in Table 2 can be More Data Per AC.
  • More Data Per AC can occupy 5 bits, where each of the 4 bits corresponds to a type of AC, and the other 1 bit corresponds to a management frame.
  • More Data Per TID subfield may include 9 bits, of which 8 bits correspond to 8 types of TIDs, each of the 8 bits corresponds to a type of TID, and the other 1 bit corresponds to a management frame.
  • a bit corresponding to the TID in the More Data Per TID subfield is set to 1, it may indicate that the buffer data corresponding to the TID is cached in the second MLD.
  • the bit is set to 0, it may indicate that the buffer data corresponding to the TID is not buffered in the second MLD.
  • bit corresponding to the management frame in the More Data Per TID subfield When the bit corresponding to the management frame in the More Data Per TID subfield is set to 1, it may indicate that the buffered data of the management frame is buffered in the second MLD. When this bit is set to 0, it may indicate that the buffered data of the management frame is not buffered in the second MLD.
  • one bit in the More Data Per TID subfield may correspond to one or more TIDs.
  • the number of bits occupied by More Data Per AC may be less than 9.
  • a bit in the More Data Per TID subfield can correspond to TID1 and TID2. When this bit is set to 1, it can indicate that the second MLD has cached data corresponding to at least one of TID1 and TID2. . When this bit is set to 0, it can indicate that neither the buffer data corresponding to TID1 nor the buffer data corresponding to TID2 is buffered in the second MLD.
  • the second MLD may send indication information to a plurality of first MLDs, and the indication information may indicate the caching status of the cached data corresponding to at least one data type supported by each first MLD in the second MLD .
  • the second MLD sends indication information to the first MLD-a and the first MLD-b
  • a part of the bits in the indication information may correspond to at least one data type supported by the first MLD-a, that is, the The value of some bits is used to indicate the buffering condition of the buffered data corresponding to at least one data type supported by the first MLD-a in the second MLD.
  • the other part of the bits in the indication information may correspond to at least one data type supported by the first MLD-b, that is, the value of the other part of the bits is used to indicate at least one of the data types supported by the first MLD-b
  • the buffer status of the buffered data corresponding to the data type in the second MLD.
  • data is transmitted between the second MLD and the first MLD through links, and each link is established between a station in the first MLD and a station in the second MLD. If the station in the first MLD or the second MLD is in the dormant state, the link corresponding to the station is also in the dormant state. At this time, data cannot be transmitted through the link, and the station in the first MLD corresponding to the link Also cannot receive data.
  • the station in the second MLD may schedule the buffered data in the second MLD and send the buffered data to the corresponding station in the first MLD. When the station in the first MLD is in a dormant state, it cannot receive data.
  • the foregoing indication information may be carried in the buffered data sent by the second MLD to the first MLD.
  • the indication information may be used to indicate (cached in the second MLD) that the first MLD supports Whether the buffered data corresponding to at least one data type has been sent.
  • the indication information may be included in the EHT A-control field in the MAC frame.
  • the second MLD may periodically send indication information to the second MLD to which the station in the energy-saving mode belongs. At this time, the indication information may indicate the station in the energy-saving mode in the second MLD. While the site is in the dormant state, whether the first MLD has cached the cached data to be sent to the site.
  • the indication information may be received by a station in an active state in the first MLD.
  • the indication information can be carried in a control frame or a management frame.
  • Step S203 The first MLD determines, according to the indication information, the caching status of the cached data corresponding to at least one data type in the second MLD.
  • the first MLD After the first MLD receives the indication information from the second MLD, it can determine the cache condition of the cache data corresponding to at least one data type in the second MLD according to the indication information.
  • the first MLD can determine that the buffered data of the data type corresponding to the bit is cached in the second MLD; if the bit is If the value of is a second value (such as 0), it can be determined that the buffered data of the data type corresponding to the bit is not buffered in the second MLD.
  • the indication information includes 2 bits (bit 1 and bit 2), the first MLD supports 3 data types (data type 1, data type 2, and data type 3), and bit 1 corresponds to data type 1. , When bit 2 corresponds to data type 2 and data type 3.
  • the first MLD can determine that there is buffered data corresponding to data type 1 in the second MLD; if the value of bit 1 is 0, it can be determined that there is no buffer in the second MLD. Cache data corresponding to data type 1. If the value of bit 2 is 1, the first MLD can determine that the buffer data corresponding to at least one of data type 2 or data type 3 is cached in the second MLD; if the value of bit 2 is 0 , It can be determined that neither the cache data corresponding to data type 2 nor the cache data corresponding to data type 3 is cached in the second MLD.
  • the first value is 1, and the second value is 0 only for example, and does not constitute a limitation to the embodiment of the present application.
  • the first value may be 0, and the second value may be 1.
  • the bits in the indication information may only correspond to the data types supported by the first MLD.
  • Some data types For example, when the first MLD supports 3 data types (data type 1, data type 2, and data type 3), and the second MLD has cached data corresponding to data type 1, data type 2 and data type 3 are not cached
  • the indication information may include bits corresponding to data type 1, but not bits corresponding to data type 2 and/or data type 3.
  • the first MLD after the first MLD receives the indication information, if the bit corresponding to data type 1 in the indication information is 1, it can indicate that the second MLD has cached data corresponding to data type 1; if this If the bit corresponding to data type 1 in the indication information is 0, it may indicate that there is no buffered data corresponding to data type 1 in the second MLD.
  • the indication information does not include the bit corresponding to data type 2 and/or data type 3.
  • the first MLD can determine that there is no buffered data corresponding to data type 2 in the second MLD, and no data corresponding to data type 3 is buffered. Cache data.
  • the first MLD may have multiple sites; after the first MLD determines the cached data corresponding to the supported at least one data type in the second MLD, it may correspond according to the at least one data type
  • the caching status of the cached data in the second MLD determines the working state of at least one of the multiple sites of the first MLD; the working state can be an active state or a dormant state.
  • the first MLD can determine that the buffer data corresponding to the data type is cached in the second MLD. Then, the first MLD may determine the link to which the data type with cached data is mapped according to the mapping relationship between the supported data type and the link corresponding to the first MLD.
  • the first MLD may determine the working status of the station corresponding to the link to which the data type with the cached data is mapped as the active status. For example, the cache data corresponding to data type 1 supported by the first MLD is cached in the second MLD, and the data type 1 is mapped to link 1 and link 2, and link 1 and link 2 correspond to the stations in the first MLD respectively. 1. Site 2 corresponds. At this time, the first MLD may determine both the working status of the station 1 and the station 2 as the active state.
  • the working status of the station (the station in the first MLD) corresponding to the link mapped by the data type with the cached data is determined to be the active state, which can make it possible to have the cache
  • the link to which the data type of the data is mapped is in an active state, and further, the second MLD can send the buffered data to the first MLD through the link.
  • the link corresponding to the first MLD refers to the link between the first MLD and the second MLD. It should be noted that the mapping of data type 1 supported by the first MLD to link 1 can indicate that the cached data corresponding to data type 1 is mapped to link 1, that is, the cached data corresponding to data type 1 will be transmitted to the first link through link 1.
  • One MLD. Management frames can be mapped to one or more links, and one service type can be mapped to one or more links. Each link can be mapped with one or more service types, and can also be mapped with management frames.
  • the mapping relationship between the service type supported by the first MLD (or the management frame to be sent to the first MLD) and the link corresponding to the first MLD may be negotiated and determined by the first MLD and the second MLD. For example, it is determined in the process of establishing a connection between the first MLD and the second MLD.
  • the mapping relationship between the service type supported by the first MLD and the link corresponding to the first MLD may be called TID-to-link mapping.
  • the link between the AC supported by the first MLD and the link corresponding to the first MLD can be determined The corresponding relationship (ie AC-to-link mapping).
  • the first MLD determines the link mapped by the data type with the cached data
  • it may be determined in the link mapped by the data type with the cached data according to the current power information of the first MLD
  • the link that needs to be converted to the active state is determined, that is, the site that needs to be converted to the active state among the stations corresponding to the link mapped by the data type with the buffered data.
  • the power information may include, but is not limited to, one or more of the remaining power and whether it is in the charging mode.
  • the first MLD MLD can choose to determine the working status of some of the links in link 1, link 2 and link 3 as active, and determine the working state of another part of links in link 1, link 2 and link 3. It is determined to be in a sleep state, which can ensure the reception of data and also help reduce power consumption.
  • the first MLD may determine the link that needs to be converted to the active state among the links mapped by the data type of the cached data according to the service requirement information of the first MLD. For example, if the second MLD has cached data corresponding to AC_VO and AC_VI supported by the first MLD, AC_VO and AC_VI are mapped to Link 1 and Link 2, respectively, and for the first MLD, the cache data corresponding to AC_VO The priority of is higher than the priority of the buffered data corresponding to AC_VI, then the first MLD can determine link 1 as the active state and link 2 as the dormant state, which can ensure the reception of high-priority data.
  • the management frame of the first MLD and the buffered data corresponding to AC_VO supported by the first MLD are buffered in the second MLD, the management frame and AC_VO are respectively mapped to link 1 and link 2, and for the first MLD
  • the first MLD can determine the link 1 as the active state and the link 2 as the dormant state, which can ensure high Priority data reception.
  • the first MLD may determine the link that needs to be converted to the active state among the links mapped by the data type with the cached data according to the current power information and service demand information of the first MLD. In the above example, if the current remaining power of the first MLD is relatively high, or the first MLD is in the charging mode, the first MLD may determine that both link 1 and link 2 are active and receive data in a timely manner. If the current remaining power of the first MLD is low, and/or the first MLD is not in the charging mode, the first MLD may determine the link 1 as the active state and the link 2 as the sleep state to ensure high Priority data reception.
  • the service requirements of different devices can be the same or different.
  • the priority of the buffered data corresponding to AC_VO is higher than the priority of the buffered data corresponding to AC_VI. This is only for example and does not constitute Limitations of the embodiments of this application. In other cases or for other MLD devices, the priority of the cache data corresponding to AC_VO may be lower than the priority of the cache data corresponding to AC_VI.
  • the working state of some links in the link mapped by the data type of the buffered data can be determined as active, and the working state of the remaining links can be determined as dormant state. In this way, it is beneficial to reduce power consumption.
  • the priority of the buffered data corresponding to the above management frame is higher than the priority of the buffered data corresponding to AC_VO is only for example, and does not constitute a limitation to the embodiment of the present application.
  • the embodiment of the present application does not limit the priority of the management frame and the buffered data corresponding to each service type.
  • the priority of the buffered data corresponding to the management frame may be higher than the priority of the buffered data corresponding to all service types.
  • the priority of the buffered data corresponding to the management frame may be higher than the priority of the buffered data corresponding to some service types.
  • the priority of the buffered data corresponding to the management frame may be lower than the priority of the buffered data corresponding to any service type.
  • the priority of the buffered data corresponding to the management frame and the priority of the buffered data corresponding to each service type may be agreed upon by a standard, or may be negotiated and determined by the first MLD and the second MLD. There is no restriction on this.
  • the embodiment of the present application does not limit the working state of the link.
  • the first MLD may determine the working state of the link as a dormant state or an active state. For example, when the remaining power of the first MLD is relatively high or the first MLD is in the charging mode, the first MLD may determine that the working state of the link is the active state. For another example, the remaining power of the first MLD is relatively low, and/or when the first MLD is not in the charging mode, the first MLD may determine that the working state of the link is the sleep state. In this way, it is beneficial to reduce power consumption.
  • the first MLD determines the working state of a certain link, which is equivalent to that the first MLD determines the station corresponding to the link in the first MLD to have the same working state.
  • an indication message may be sent to the second MLD, and the indication message may indicate the station in the active state.
  • the second MLD may determine the link in the active state according to the station in the active state. Further, the second MLD may schedule the buffered data to the corresponding active link for sending to the first MLD according to the mapping relationship between the data type supported by the first MLD and the link corresponding to the first MLD. MLD.
  • the cache condition of the cached data corresponding to at least one data type supported by the first MLD in the second MLD. Furthermore, according to the data type of the cached data, it is helpful to determine a more suitable working state for the site, and it is helpful to reduce power consumption.
  • FIG. 3a is a schematic flowchart of a method for determining a data caching situation provided by an embodiment of the present application.
  • This method describes in detail how the first MLD determines the cache of the cached data corresponding to at least one data type in the second MLD according to the first indication information and the correspondence between the associated identifier of the first MLD and the supported data types.
  • the execution subject of step S301 to step S303 is the second MLD, or the chip in the second MLD
  • the execution subject of step S304 is the first MLD, or the chip in the first MLD.
  • the second MLD and the first MLD are executed.
  • An MLD is an example of the execution subject of the method for determining the data caching situation. As shown in Figure 3a, the method may include but is not limited to the following steps:
  • Step S301 The second MLD determines the cache condition of the cached data corresponding to at least one data type supported by the first MLD in the second MLD.
  • step S301 please refer to the specific description of step S201 in FIG. 2, which will not be repeated here.
  • Step S302 The second MLD is based on the caching situation 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 associated identifier of the first MLD and the supported data types. Determine the cache condition of the cache data corresponding to the association identifier of the first MLD in the second MLD.
  • the second MLD determines the cache condition of the cached data corresponding to at least one data type supported by the first MLD in the second MLD
  • the corresponding relationship between the AID of the first MLD and the supported data type may be combined , Determine the cache condition of the cache data corresponding to the AID of the first MLD in the second MLD.
  • the first MLD may have one or more association identifiers (AIDs).
  • An AID of the first MLD may correspond to one or more data types supported by the first MLD.
  • the second MLD buffer contains the first The buffer data of the management frame of the MLD and the buffer data corresponding to AC_VO and AC_VI supported by the first MLD.
  • the 5 AIDs of the first MLD are AID0 ⁇ AID4, and AID4 corresponds to the management frame of the first MLD.
  • the corresponding relationship between the remaining AID and AC is shown in Table 3.
  • the second MLD may determine that the cache data corresponding to AID0, the cache data corresponding to AID1, and the cache data corresponding to AID4 are cached.
  • Step S303 The second MLD sends first indication information to the first MLD; the first indication information is used to indicate the caching status of the cache data corresponding to the association identifier of the first MLD in the second MLD.
  • the first indication information may be sent to the first MLD.
  • each bit in the indication information sent by 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 be Indicates whether the buffer data of the data type corresponding to the bit is buffered in the second MLD.
  • each bit in the first indication information sent by the second MLD to the first MLD may correspond to an AID of the first MLD.
  • the value of each bit in the first indication information can indicate the AID corresponding to the bit, and whether the corresponding buffered data is cached in the second MLD.
  • the first MLD further combines the AID with the supported data type.
  • the corresponding relationship of the at least one supported data type can be determined in the second MLD.
  • the first indication information may be the TIM field in the beacon frame.
  • Step S304 The first MLD determines that the cache data corresponding to at least one data type is in the second MLD according to the first indication information and the correspondence between the association identifier of the first MLD and the data types supported by the first MLD. Cache situation in.
  • the first MLD after the first MLD receives the first indication information from the second MLD, it can be based on the first indication information and the relationship between the association identifier (AID) of the first MLD and the data type supported by the first MLD. Correspondence, determining the cache condition of the cache data of at least one data type in the second MLD. If the value of a certain bit in the TIM field is 1, and the bit corresponds to AID1, it may indicate that the buffer data corresponding to AID1 is buffered in the second MLD. If the AID1 corresponds to the data type 1 supported by the first MLD, it may indicate that the cache data corresponding to the data type 1 is cached in the second MLD.
  • the AID2 may indicate that the buffer data corresponding to AID2 is not buffered in the second MLD. If the AID2 corresponds to the data type 2 supported by the first MLD, it may indicate that the cache data corresponding to the data type 2 is not cached in the second MLD.
  • the correspondence between the AID of the first MLD and the data type supported by the first MLD may be determined by the second indication information sent by the second MLD to the first MLD.
  • the second indication information may be used to determine the correspondence between the AID of the first MLD and the data type supported by the first MLD, and the second indication information may be included in the association response frame.
  • the embodiment of the present application does not limit the order in which the second MLD sends the first indication information and the second indication information, and does not limit the order in which the first MLD receives the first indication information and the second indication information.
  • the first MLD can determine the cache condition of the cached data corresponding to at least one data type supported by the first MLD in the second MLD according to the first indication information and the second indication information.
  • the second MLD may send the second indication information to the first MLD before sending the first indication information.
  • the receiving time of the second indication information is earlier than the receiving time of the first indication information.
  • the second indication information received by the first MLD may indicate at least one AID, and the at least one AID may correspond to at least one data type supported by the first MLD.
  • the second indication information may include 5 AIDs, where 1 AID corresponds to the management frame, and the other 4 AIDs correspond to 4 ACs.
  • the embodiment of the present application does not limit the correspondence between the 4 ACs and the 4 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, the corresponding relationship can be shown in Table 3 or Table 4.
  • the correspondence between the 4 AIDs and the 4 ACs can be one-to-one corresponding to the size of the AID and the priority of the AC. It can be seen from Table 4 that the correspondence between the 4 AIDs and the 4 ACs may also be irrelevant to the size of the AID and the priority of the AC. It should also be noted that in the foregoing Table 3 and Table 4, the 4 consecutive AIDs are only used as examples, and do not constitute a limitation to the embodiments of the present application.
  • the second indication information indicates multiple AIDs, the multiple AIDs may be continuous or discontinuous. In other words, the second MLD can arbitrarily select multiple AIDs from the available AID space and allocate them to the first MLD.
  • the second indication information indicates at least one AID corresponding to at least one data type supported by the first MLD, so that the AID can be allocated to the first MLD more flexibly.
  • the first MLD may support multiple data types; the second indication information may indicate a first association identifier, and the first association identifier corresponds to a first data type of the multiple data types.
  • the first MLD may determine, according to the first association identifier corresponding to the first data type, association identifiers corresponding to data types other than the first data type among the multiple data types.
  • the first association identifier indicated by the second indication information is AID0
  • AID0 corresponds to the management frame supported by the first MLD.
  • the first MLD can determine that AC_VO, AC_VI, AC_BK, AC_BE correspond to AID0+1, AID0+2, AID0+3, AID0+4, respectively, according to the supported management frames and the priority levels of various ACs, that is, the first The 4 ACs supported by the MLD respectively correspond to the 4 consecutive AIDs after the AID0 indicated by the second indication information.
  • AC_VO, AC_VI, AC_BE, and AC_BK may correspond to AID0+2, AID0+4, AID0+6, and AID0+8, respectively, that is, the AIDs corresponding to various data types supported by the first MLD may not be continuous.
  • the first association identifier indicated by the second indication information in the above example is AID0
  • the AID0 corresponding to the management frame is only for example, and does not constitute a limitation to the embodiment of the present application.
  • the first association identifier indicated by the second indication information may be AID2, and AID1 corresponds to AC_VI of the 4 ACs supported by the first MLD.
  • the first MLD may determine that the management frame, AC_VO, AC_BK, and AC_BE correspond to AID2+1, AID2+2, AID2+3, and AID2+4, respectively, according to the priority levels of various supported data types.
  • AC_VO corresponds to AID2-1
  • the management frame corresponds to AID2-2
  • AC_BK and AC_BE correspond to AID2+1 and AID2+2, respectively.
  • the second indication information indicates at least two AIDs
  • one of the at least two AIDs may correspond to the management frame
  • the remaining AIDs correspond to the service types supported by the first MLD.
  • the AID mode corresponding to the service type.
  • the second MLD may send second indication information to multiple first MLDs, so as to allocate different AIDs to each first MLD.
  • different first MLDs have different AIDs.
  • first MLD-a and second MLD-b both support management frames and 4 types of AC (AC_VO (voice), AC_VI (video), AC_BE (best effort), AC_BK (background) )
  • AC_VO voice
  • AC_VI video
  • AC_BE best effort
  • AC_BK background
  • 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.
  • the number of AIDs allocated by the second MLD to the first MLD may be the same as the number of data types supported by the first MLD.
  • the second MLD allocates a new AID to the data type newly supported by the first MLD. In this way, you can avoid assigning unnecessary AIDs.
  • the second MLD may assign an AID to one or more data types supported by the same first MLD. For example, when the data types supported by the first MLD are management frame, AC_VO, AC_VI, AC_BE, AC_BK, the second MLD may allocate one AID for the management frame, AC_VO, and AC_VI, and another AID for AC_BE and AC_BK. Alternatively, the second MLD may allocate one AID for the management frame, one AID for AC_VO, and another AID for AC_VI, AC_BE, and AC_BK. Alternatively, the second MLD may allocate a different AID to the management frame, AC_VO, and AC_VI, and allocate another AID to AC_BE and AC_BK. By assigning the same AID to multiple data types, the number of AIDs assigned to the first MLD can be made smaller than the number of data types supported by the first MLD. In this way, AID can be effectively saved.
  • the value of the bit corresponding to the AID in the TIM field is 1, it can indicate that part or all of the data types corresponding to the AID are buffered in the second MLD Cached data of the data type. If the value of the bit corresponding to the AID in the TIM field is 0, it can indicate that there is no buffer data of any data type corresponding to the AID in the second MLD.
  • the cache data of the at least one data type may be cached in the second MLD according to the cache status of the at least one data type.
  • the first MLD may determine the first MLD according to at least one of the current power information or service requirement information of the first MLD, and the caching status of at least one data type of cached data in the second MLD.
  • the working status of at least one of the multiple sites of an MLD please refer to the specific description of step S203 in FIG. 2, which will not be repeated here.
  • FIG. 4a is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application.
  • This method describes in detail how the second MLD determines whether there is at least one cached data corresponding to the second data type, and how the first MLD determines whether there is at least one cached data in the second MLD according to the third indication information from the second MLD. Cache data corresponding to a second data type.
  • the execution subject of step S401 to step S402 is the second MLD, or the chip in the second MLD
  • the execution subject of step S403 is the first MLD, or the chip in the first MLD.
  • the second MLD and the first MLD are executed.
  • An MLD is an example of the execution subject of the method for determining the data caching situation. The method may include but is not limited to the following steps:
  • Step S401 The second multi-link device MLD determines whether the second MLD has cached data corresponding to at least one second data type; the second data type is any data type mapped to the first link.
  • one link can be mapped to one or more data types, one data type can be mapped to one or more links, and the cache data corresponding to each data type of a certain link can be mapped Can be transmitted over this link. If at least one type of cache data corresponding to the second data type is cached in the second MLD, it may indicate that the cache data in the second MLD may be transmitted to the first MLD through the first link. If there is no cache data corresponding to any second data type in the second MLD, it can indicate that the cache data corresponding to each data type mapped to the first link has been sent. In other words, the cache data in the second MLD It will not be transmitted to the first MLD through the first link.
  • the second MLD can determine whether there is cache data corresponding to at least one second data type cached in the second MLD, so as to determine whether there is cache data that may be transmitted to the first MLD through the first link.
  • the first link is a certain link between the first MLD and the second MLD.
  • Step S402 The second MLD sends buffered data to the first MLD through the first link, the buffered data includes third indication information; the third indication information is used to indicate whether at least one second data type is buffered in the second MLD Corresponding cache data.
  • the third indication information may be carried in the buffered data transmitted through the first link to indicate whether the buffered data may be transmitted to the first MLD through the first link.
  • the second MLD determining whether there is at least one type of cache data corresponding to the second data type is cached in the second MLD means: excluding the cache data to which the third indication information belongs, whether there is at least one cache data in the second MLD Cache data corresponding to the second data type.
  • data type a and data type b are mapped on link 1.
  • the second MLD sends buffered data to the first MLD through link 1
  • the second MLD buffers the buffered data corresponding to data type a, or the buffer
  • it can indicate that there may be cache data transmitted to the first MLD through link 1.
  • it can indicate that no cache data will be transmitted to the first MLD through link 1.
  • each buffer 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 buffer data is used to indicate Whether there is cached data corresponding to at least one second data type.
  • the MAC frame structure of the buffered data includes a frame control (Frame Control) field, and the Frame Control field includes a More Data subfield, and the length of the More Data subfield is 1 bit.
  • the third indication information may refer to the More Data subfield in the cached data.
  • the second MLD sends cache data to the first MLD through the first link
  • the value of the More Data subfield in the cache data is The value can be 1. If no cache data corresponding to any second data type is cached in the second MLD, the value of the More Data subfield in the cache data may be 0.
  • the third indication information refers to the More Data subfield in the cached data only for example, and does not constitute a limitation to the embodiment of the present application. In other feasible implementation manners, the third indication information may be other fields in the MAC frame structure of the buffered data.
  • Step S403 The first MLD determines, according to the third indication information, whether there is at least one cached data corresponding to the second data type in the second MLD.
  • the first MLD after the first MLD receives the buffered data from the second MLD through the first link, it can be determined according to the third indication information in the buffered data whether there is at least one buffer corresponding to the second data type in the second MLD. Cache data.
  • the third indication information refers to the More Data subfield in the cached data
  • the first MLD if the value of the More Data subfield in the cached data is 1, the first MLD can determine that at least one second data type is cached in the second MLD Corresponding cache data. If the value of the More Data subfield in the cache data is 0, the first MLD can determine that no cache data corresponding to any second data type is cached in the second MLD.
  • the data type mapped on the first link includes management frames and AC_VO
  • the value of the More Data subfield in the buffer data received by the first MLD through the first link is 1, it means that there will be subsequent At least one of the buffer data corresponding to the management frame and the buffer data corresponding to the AC_VO is transmitted to the first MLD through the first link.
  • the value of the More Data subfield in the buffer data received by the first MLD through the first link is 0, it means that no buffer data corresponding to the management frame will be subsequently transmitted to the first MLD through the first link. No buffer data corresponding to AC_VO will be transmitted to the first MLD through the first link.
  • the first MLD may have multiple sites; after the first MLD determines whether there is at least one cached data corresponding to the second data type in the second MLD, it may be based on whether the second MLD has at least One type of cache data corresponding to the second data type determines the working status of the station corresponding to the first link among the multiple stations of the first MLD.
  • the first MLD can determine the data corresponding to the first link The working status of the station is active; if there is no cached data corresponding to any second data type in the second MLD, that is, the value of the More Data subfield is 0, the first MLD can be determined to correspond to the first link The working status of the site is active or dormant.
  • the second MLD may include multiple cache areas, one cache area corresponds to one link, and cache data cached in different cache areas are transmitted to the first MLD through different links.
  • the More Data subfield in the cache data is used to indicate whether there is cache data in the cache area corresponding to the link that transmits the cache data. If there is no cached data in the cache area corresponding to the link used to transmit the cached data (such as link 1), the value of the More Data subfield in the cached data is 0, and accordingly, the first MLD may The working state of the station corresponding to link 1 is determined to be the dormant state.
  • link congestion or interference occurs on other links (such as link 2), and the first MLD cannot receive buffered data through link 2, since link 1 is in a dormant state, it cannot pass the original link.
  • the buffered data transmitted by link 2 is scheduled to link 1 for transmission.
  • the second MLD can schedule the buffered data corresponding to the data type (including the buffered data originally transmitted through link 2) to link 1 for transmission.
  • the first MLD may be based on at least one of the current power information or service requirement information of the first MLD, and whether the second MLD caches at least one type of cache data corresponding to the second data type. , Determining the working status of the station corresponding to the first link among the multiple stations of the first MLD.
  • the execution process please refer to the detailed description of step S203 in Fig. 2, which will not be repeated here.
  • the second MLD may send fourth indication information to the first MLD;
  • the fourth indication information is used to indicate that no cache data corresponding to any second data type is cached in the second MLD. After the first MLD receives the fourth indication information, it can be determined that no cache data corresponding to any second data type is cached in the second MLD. That is, after the first MLD receives the fourth indication information, it can be determined that no buffered data will be subsequently transmitted through the first link.
  • the first MLD supports data type a and data type b
  • the link between the first MLD and the second MLD includes link 1.
  • link 2 is mapped with data type b.
  • the white filled square in FIG. 4b represents the cache data corresponding to data type a
  • the gray filled square represents the cache data corresponding to data type b
  • the number in the square is used to uniquely identify a cache data.
  • the last buffered data transmitted on link 1 is buffered data 2
  • the last buffered data transmitted on link 2 is buffered data 4.
  • the second MLD may set the value of the More Data subfield in the cache data 2 to 1.
  • the buffered data 4 can be transmitted through the link 1 or the link 2. If the second MLD subsequently sends the buffered data 4 to the first MLD through the link 2, at this time, since the buffered data corresponding to the data type a and the data type b mapped on the link 1 are all sent, the second MLD cannot pass The first link sends cached data to the second MLD, and it cannot use the More Data subfield in the cached data to indicate that neither the cached data corresponding to data type a nor the cache corresponding to data type b is cached in the second MLD. data. That is, the More Data subfield in the cached data cannot be used to indicate that no cached data will be transmitted to the first MLD through the link 1 in the future.
  • the second MLD can solve the foregoing problem by sending the fourth indication information to the first MLD.
  • the fourth indication information may indicate that there is no cache data corresponding to any data type mapped to link 1 in the second MLD, that is, the fourth indication information may indicate that there is no cache data corresponding to data type a in the second MLD. , There is no cached data corresponding to data type b.
  • the fourth indication information may be a QoS Null frame
  • the QoS Null frame is a data frame that does not carry a payload
  • the value of the More Data subfield in the QoS Null frame is 0.
  • the second MLD may send a QoS Null frame to the first MLD through the first link.
  • the first MLD may determine the working state of the station corresponding to the first link as the dormant state according to the fourth indication information. In this way, it is beneficial to reduce power consumption.
  • the first MLD may determine the working status of the station corresponding to the first link according to at least one of the current power information or service demand information, and the fourth indication information. For example, after the first MLD receives the fourth indication information from the second MLD, if the current remaining power of the first MLD is low, and/or the first MLD is not in the charging mode, the first link can be The working state of the site is determined to be the dormant state. If the current remaining power of the first MLD is relatively high or the first MLD is in the charging mode, the working state of the station corresponding to the first link may be determined as the active state.
  • the second MLD when the second MLD sends buffered data (such as buffered data 1) to the first MLD through the first link, if the buffered data 1 is removed, at least one second type is also buffered in the second MLD.
  • the second MLD may set the value of the More Data subfield in the cache data 1 to 0.
  • the station corresponding to the link 1 that transmits the buffered data 1 can be set to a dormant state, and correspondingly, the link 1 is also in a dormant state.
  • the second MLD may send data through the link 1. Before receiving the link state indication information sent by the first MLD for indicating that the link 1 is in an active state, the second MLD may not send data through the link 1. In this way, when it is uncertain that the link 1 is in an active state, the second MLD can prevent the second MLD from scheduling the buffered data originally transmitted through other links to the link 1 for transmission, which is beneficial to avoid unnecessary overhead.
  • the link state indication information used to indicate that the link 1 is in an active state may be a power saving poll (PS-Poll) frame.
  • PS-Poll power saving poll
  • the second MLD sends buffered data to the first MLD through the first link when it is determined that the first link is in an active state (that is, step S402).
  • the first MLD may send a PS-Poll frame to the second MLD to indicate that the first link of the second MLD is in an active state.
  • the first MLD may determine the working state of the first link as the active state when it is determined that there is buffered data that needs to be transmitted through the first link in the second MLD, and send to the second MLD indicating the first link. PS-Poll frame with active link.
  • the second MLD may send a beacon frame in the prior art to the first MLD, and the TIM field in the beacon frame is used to indicate that the buffered data of each site of the first MLD is in the second MLD.
  • the cache situation According to the corresponding relationship between the TIM field, the link, and the station of the first MLD, the first MLD can determine whether there is buffered data in the second MLD that needs to be transmitted through the first link.
  • the second MLD may send the first indication information in the embodiment shown in FIG. 3a to the first MLD, and the first MLD may be based on the first indication information, and the association identifier of the first MLD and the first MLD.
  • the correspondence between the data types supported by an MLD determines the caching status of the cached data corresponding to at least one data type in the second MLD. Furthermore, according to the cache situation of the cached data corresponding to the at least one data type in the second MLD, and the mapping relationship between the data type supported by the first MLD and the link, it is determined whether the cache in the second MLD needs to pass through the first MLD. Cached data transmitted by the link. For the execution process, refer to the embodiment shown in FIG. 5.
  • FIG. 5 is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application, in which steps S501 to S503, step S507, and step S508 are executed by the second MLD, or For the chip in the second MLD, steps S504 to S506, and the execution subject of step S509 is the first MLD or the chip in the first MLD.
  • the following uses the second MLD and the first MLD as the method for determining the data cache situation. Take the main body as an example.
  • the method may include but is not limited to the following steps:
  • Step S501 The second MLD determines the cache condition of the cached data corresponding to at least one data type supported by the first MLD in the second MLD.
  • Step S502 The second MLD is based on the caching situation 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 associated identifier of the first MLD and the supported data types. Determine the cache condition of the cache data corresponding to the association identifier of the first MLD in the second MLD.
  • Step S503 The second MLD sends first indication information to the first MLD; the first indication information is used to indicate the caching status of the cache data corresponding to the association identifier of the first MLD in the second MLD.
  • Step S504 The first MLD determines that the cache data corresponding to at least one data type is in the second MLD according to the first indication information and the correspondence between the association identifier of the first MLD and the data types supported by the first MLD. Cache situation in.
  • step S501 to step S504 please refer to the specific description of step S301 to step S304 in FIG. 3a respectively, which will not be repeated here.
  • Step S505 The first MLD determines the relationship between the data type supported by the first MLD and the link corresponding to the first MLD according to the cache condition of the cached data corresponding to the at least one data type in the second MLD and the mapping relationship between the data type and the link corresponding to the first MLD.
  • the working state of the station corresponding to the first link is the active state.
  • the first MLD may determine according to the caching situation of the cached data corresponding to at least one data type in the second MLD and the mapping relationship between the data type supported by the first MLD and the link corresponding to the first MLD The link to which the data type of the cached data is mapped. If the link mapped by the data type with the buffered data includes the first link, the first MLD may determine that the working state of the station corresponding to the first link is the active state.
  • Step S506 The first MLD sends link state indication information to the second MLD, where the link state indication information is used to indicate that the first link is in an active state.
  • the link state indication information is sent to the second MLD.
  • the link state indication information may be a PS-Poll frame. In an implementation manner, the link state indication information may be sent to the second MLD through the first link.
  • Step S507 The second MLD determines whether the second MLD has cached data corresponding to at least one second data type; the second data type is any data type mapped to the first link.
  • the second MLD may determine that the first link is in the active state according to the link state indication information. In a case where it is determined that the first link is in an active state, the buffer data carrying the third indication information may be sent to the first MLD through the first link.
  • Step S508 The second MLD sends buffered data to the first MLD through the first link, the buffered data includes third indication information; the third indication information is used to indicate whether at least one second data type is buffered in the second MLD Corresponding cache data.
  • Step S509 The first MLD determines, according to the third indication information, whether there is at least one type of cache data corresponding to the second data type cached in the second MLD.
  • step S507 to step S509 please refer to the specific description of step S401 to step S403 in FIG. 4a respectively, which will not be repeated here.
  • the first MLD may be based on the cache condition of the cached data corresponding to at least one data type in the second MLD, and the mapping between the data type supported by the first MLD and the link corresponding to the first MLD Relationship, it is determined that the working status of the station corresponding to the first link is active.
  • the second MLD may determine that the first link is in the active state according to the link state indication information from the first MLD. And when it is determined that the first link is in an active state, the buffer data carrying the third indication information is sent to the first MLD through the first link.
  • FIG. 6a is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application.
  • This method describes in detail how the first MLD determines whether there is cache data corresponding to the third data type in the second MLD according to the fifth indication information.
  • the execution subject of step S601 to step S602 is the second MLD, or the chip in the second MLD
  • the execution subject of step S603 is the first MLD, or the chip in the first MLD.
  • the second MLD and the first MLD are executed.
  • An MLD is an example of the execution subject of the method for determining the data caching situation. The method may include but is not limited to the following steps:
  • Step S601 The second multi-link device MLD determines whether there is cache data corresponding to the third data type in the second MLD.
  • a data type can be mapped to one or more links, and the buffered data corresponding to the data type buffered in the second MLD can be transmitted to the first MLD through any link mapped by the data type.
  • the link between the first MLD and the second MLD includes link 1, link 2, and link 3, and the data type a is mapped to link 1, link 2, and In link 3, the buffered data corresponding to data type a may be transmitted to the first MLD through one or more of links 1, link 2, and link 3.
  • the second MLD determines whether the cache data corresponding to the third data type is cached in the second MLD, which is equivalent to determining whether the cache data corresponding to the third data type cached in the second MLD has been sent.
  • the cache data corresponding to the third data type is cached in the second MLD, which indicates that the cache data corresponding to the third data type has not been sent.
  • the cache data corresponding to the third data type is not cached in the second MLD, which indicates that the cache data corresponding to the third data type has been sent.
  • Step S602 The second MLD sends cache data corresponding to the third data type to the first MLD, where the cache data includes fifth indication information, and the fifth indication information is used to indicate whether the third data type is cached in the second MLD. Cached data.
  • fifth indication information may be carried in the cache data corresponding to the third data type to indicate whether there is cache data corresponding to the third data type in the second MLD (that is, indicating the third data type). Whether the buffer data corresponding to the type has been sent). It should be noted that determining whether the second MLD has cached data corresponding to the third data type in the second MLD refers to: excluding the cache data to which the fifth indication information belongs, whether the second MLD has cached the third data type Corresponding cache data. It should also be noted that each cached data sent by the second MLD to the first MLD carries fifth indication information, and the fifth indication information carried in each cached data is used to indicate whether the cache is cached in the second MLD. The cache data corresponding to the data type to which the data belongs.
  • the fifth indication information may refer to the More Data subfield in the cached data. Specifically, when the second MLD sends the cache data corresponding to the third data type (such as cache data 1) to the first MLD, if the cache data corresponding to the third data type is cached in the second MLD, the data in the cache data 1 More The value of the Data subfield can be 1. If the cache data corresponding to the third data type is not cached in the second MLD, the value of the More Data subfield in cache data 1 may be 0. It should be noted that the fifth indication information refers to the More Data subfield in the cached data only for example, and does not constitute a limitation to the embodiment of the present application. In other feasible implementation manners, the fifth indication information may be other fields in the MAC frame structure of the buffered data.
  • Step S603 The first MLD determines, according to the fifth indication information, whether there is cached data corresponding to the third data type in the second MLD.
  • the first MLD after the first MLD receives the cache data corresponding to the third data type from the second MLD, it can determine whether there is cache data corresponding to the third data type in the second MLD according to the fifth indication information in the cache data. .
  • the fifth indication information refers to the More Data subfield in the cached data
  • the first MLD if the value of the More Data subfield in the cached data is 1, the first MLD can determine that a cache corresponding to the third data type is cached in the second MLD data. If the value of the More Data subfield in the cache data is 0, the first MLD can determine that the cache data corresponding to the third data type is not cached in the second MLD.
  • the first MLD may have multiple sites; after the first MLD determines whether there is cached data corresponding to the third data type in the second MLD, it may be based on whether the third data type is cached in the second MLD The corresponding cache data determines the working status of the station corresponding to the second link among the multiple stations of the first MLD. Wherein, the third data type is mapped to the second link.
  • the first MLD may determine that the working status of the station corresponding to the second link is active State so that the buffered data corresponding to the third data type that has not been sent can be transmitted to the first MLD through the second link.
  • the number of second links may be one or more.
  • the first MLD may determine the first MLD according to at least one of the current power information or service requirement information of the first MLD, and whether the second MLD has cached data corresponding to the third data type.
  • the working status of the station corresponding to the second link among the multiple stations of an MLD please refer to the specific description of step S203 in FIG. 2, which will not be repeated here.
  • the first MLD determines whether the cache data corresponding to the third data type is cached in the second MLD, it can be determined whether the second link is mapped with other data types other than the third data type; and According to whether the second MLD has cached data corresponding to the third data type, and whether the second link is mapped with other data types other than the third data type, determine the second link among the multiple sites of the first MLD The working status of the station corresponding to the road. Specifically, if there is no cached data corresponding to the third data type in the second MLD, but the second link is mapped with other data types other than the third data type, that is, in addition to the third data type, it is mapped to the second data type.
  • Cached data corresponding to other data types of the link may be transmitted through the second link.
  • the first MLD may determine that the working state of the station corresponding to the second link is the active state. If the buffer data corresponding to the third data type is not buffered in the second MLD, the second link is not mapped with data types other than the third data type, that is, no buffer data will be subsequently transmitted through the second link. At this time, the first MLD may determine that the working state of the station corresponding to the second link is the dormant state. In this way, it is beneficial to determine a more suitable working state for the stations in the first MLD, and it is beneficial to reduce power consumption.
  • the first MLD supports data type a and data type b
  • the link between the first MLD and the second MLD includes link 1, link 2.
  • link 3, and link 1 is mapped with data type a and data type b
  • link 2 is mapped with data type b
  • link 3 is mapped with data type b.
  • the white filled square in FIG. 6b represents the cache data corresponding to data type a
  • the gray filled square represents the cache data corresponding to data type b
  • the number in the square is used to uniquely identify a cache data.
  • the last buffered data transmitted on link 1 is buffered data a2
  • the last buffered data transmitted on link 2 is buffered data b4
  • the last buffered data transmitted on link 3 is buffered data b2.
  • the last buffered data (a2) corresponding to data type a buffered in the second MLD is sent through link 1
  • the last buffered data (b4) corresponding to data type b buffered in the second MLD is sent through link 2. send. Therefore, the value of the More Data subfield in the cache data a2 is 0, which means that before the second MLD sends the cache data a2, the second MLD has cached data corresponding to data type a, and the second MLD is sending the cache data. After a2, no cached data corresponding to data type a is cached in the second MLD.
  • the value of the More Data subfield in the buffer data b4 is 0, which means that the second MLD before the buffer data b4 is sent, the second MLD has buffered data corresponding to the data type b, and the second MLD is after the buffer data b4 is sent , There is no cache data corresponding to the data type b in the second MLD.
  • the first MLD may determine the working state of the station corresponding to link 1 as the dormant state (that is, determine the link 1 as the dormant state).
  • the second MLD can still be cached in the second MLD to be sent to In the case of buffering data of the first MLD, part of the link between the first MLD and the second MLD is put in a dormant state.
  • the station corresponding to the link in the dormant state in the first MLD is also in the dormant state. In this way, it is beneficial to reduce power consumption.
  • the first MLD can learn whether the second MLD caches the cache data corresponding to the third data type. However, the first MLD cannot know the caching status of other data types in the second MLD.
  • the buffer data corresponding to the third data type received by the first MLD from the second MLD may further include sixth indication information, and the sixth indication information may be used to indicate whether the second MLD has at least one buffered data Cache data corresponding to the 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.
  • the sixth indication information may indicate the second MLD Whether to cache the cached data to be sent to the first MLD.
  • the fifth indication information in the cache data corresponding to the third data type indicates that the cache data corresponding to the third data type is not cached in the second MLD
  • the cache data corresponding to the third data type is still May include sixth indication information.
  • the fifth indication information in the cache data corresponding to the third data type indicates that the cache data corresponding to the third data type is cached in the second MLD
  • the cache data corresponding to the third data type may not include the sixth indication information.
  • the sixth indication information may refer to the "More Fragment" subfield in the buffered data.
  • the second MLD sends the cache data corresponding to the third data type (such as cache data 1) to the first MLD, and the value of the More Data subfield in the cache data 1 is 0 (that is, the value corresponding to the third data type).
  • the second MLD buffers at least one buffered data corresponding to the fourth data type, the value of the More Fragment subfield in the buffered data 1 may be 1. If the second MLD does not cache any cache data corresponding to the fourth data type, the value of the More Fragment subfield in the cache data 1 may be 0.
  • the sixth indication information refers to the More Fragment subfield in the cache data is only for example, and does not constitute a limitation to the embodiment of the present application. In other feasible implementation manners, the sixth indication information may be other fields in the MAC frame structure of the buffered data.
  • the first MLD receives cached data 1
  • the values of the More Data subfield and the More Fragment subfield in the cached data 1 are both 0, it can indicate that the cached data to be sent to the first MLD is not cached in the second MLD . At this time, all links between the first MLD and the second MLD can be turned into a sleep state to reduce power consumption.
  • the data types supported by the first MLD include management frames and AC_VO
  • the value of the More Data subfield in the buffer data corresponding to AC_VO received by the first MLD is 0, and the value of the More Fragment subfield is 0, it means that the buffer data corresponding to AC_VO and the buffer data corresponding to the management frame have all been sent.
  • the priority of the foregoing fourth data type may be higher than the priority of the third data type.
  • the sixth indication information is used to indicate whether the second MLD buffer has a priority over the third data type.
  • the sixth indication information can indirectly indicate whether the second MLD buffers the data type 1 Corresponding cache data.
  • the sixth indication information indicates that the second MLD does not cache data with a higher priority than the third data type
  • the cache data corresponding to the type may indicate that the second MLD does not cache the cache data corresponding to the aforementioned at least two data types. It can be seen that, through the sixth indication information, the second MLD can indicate a more detailed buffering situation to the first MLD, thereby helping to determine a more suitable working state for the stations in the first MLD and reducing power consumption.
  • the second MLD may determine that the second MLD does not cache the cache data corresponding to the fifth data type, and the fifth data type is any data type among the data types supported by the first MLD;
  • One MLD sends seventh indication information, where the seventh indication information is used to indicate that the second MLD does not cache the cache data corresponding to the fifth data type.
  • the first MLD may determine, according to the seventh indication information, that the second MLD does not cache the cache data corresponding to the fifth data type.
  • the second MLD When the second MLD does not cache the cache data corresponding to one or several data types (such as data type c) supported by the first MLD, the second MLD cannot send the cache data corresponding to the data type c to the second MLD. It is also not possible to use the More Data subfield in the cache data corresponding to the data type c to indicate that the second MLD does not cache the cache data corresponding to the data type c. In other words, the first MLD cannot know that the second MLD does not have cached data corresponding to the data type c. This will cause the first MLD to be unable to determine whether the station corresponding to the link mapped by the data type c can be switched to the dormant state. At this time, if the seventh indication information received by the first MLD may indicate that the second MLD does not cache the cached data corresponding to the data type c, the foregoing problem can be solved.
  • the first MLD in FIG. 6c Taking the scenario diagram of determining the working status of the link shown in FIG. 6c as an example, compared with FIG. 6b, the first MLD in FIG. It can be seen from FIG. 6c that the last cached data corresponding to the data type b cached in the second MLD is b4. Since only the data type b is mapped on the link 2, in addition to the data type b, the link 3 is also mapped with the data type c. Therefore, after receiving b4, the first MLD can determine the working state of the station corresponding to link 2 as the dormant state, but it is impossible to determine whether the working state of the station corresponding to link 3 can be determined as the dormant state.
  • the first MLD receives the seventh indication information indicating that the second MLD does not cache the cached data corresponding to the data type c after receiving b4, then the first MLD receives the first MLD.
  • the working state of the station corresponding to link 3 can be determined as the dormant state.
  • the second MLD sends the seventh indication information after b4 is only for example, and does not constitute a limitation of the present application.
  • the second MLD may also send the seventh indication information before b4, or send b4 and the seventh indication information at the same time.
  • the seventh indication information may be a QoS Null frame
  • the QoS Null frame is a data frame that does not carry a payload (payload)
  • the value of the More Data subfield in the QoS Null frame is 0.
  • the fifth data type indicated by the QoS Null frame may 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 is included in TID8 to TID15, it can be determined that the fifth data type indicated by the QoS Null frame is a management frame.
  • the second MLD sending a QoS Null frame to the first MLD via link 3 is only for example, and does not constitute a limitation of the present application.
  • the second MLD may send a QoS Null frame to the first MLD through any link between the first MLD and the second MLD.
  • the second MLD determines that the second MLD does not have cached data corresponding to any data type mapped to the fourth link, and sends the eighth indication information to the first MLD through 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.
  • the first MLD may determine, according to the eighth indication information, that the second MLD does not cache the cache data corresponding to any data type mapped to the fourth link.
  • the execution process please refer to the specific description in the embodiment shown in FIG. 8, which will not be repeated here.
  • the first MLD in Figure 6d adds supported data types c and d, and both data types c and d are mapped to Link 3. It can be seen from FIG. 6d that the last cached data corresponding to the data type b cached in the second MLD is b4. Since only the data type b is mapped on the link 2, in addition to the data type b, the link 3 is also mapped with the data types c and d.
  • the first MLD can determine the working state of the station corresponding to link 2 as the dormant state, but it is impossible to determine whether the working state of the station corresponding to link 3 can be determined as the dormant state.
  • the first MLD receives b4 through link 3, it indicates that the second MLD is not buffered with any data type corresponding to link 3 (that is, the fourth link).
  • the first MLD may determine the working state of the station corresponding to link 3 as the dormant state.
  • the buffer data may be sent through any of the links mapped by the third data type.
  • the second MLD needs to make sure that at least one of the links mapped by the third data type is in the active state, and then to the second MLD through the active link (such as link 1) mapped with the third data type.
  • An MLD sends the buffered data corresponding to the third data type (that is, step S602).
  • the first MLD may send a PS-Poll frame to the second MLD to indicate that the second MLD link 1 is in an active state.
  • the first MLD may determine the working state of link 1 as the active state when it is determined that the buffer data corresponding to the third data type mapped to link 1 is cached in the second MLD, and send a message to the second MLD for PS-Poll frame indicating link 1 is active.
  • the second MLD may send the first indication information in the embodiment shown in FIG. 3a to the first MLD, and the first MLD may be based on the first indication information and the association identifier of the first MLD and the first indication information.
  • the correspondence between the data types supported by the MLD determines that the second MLD has cached data corresponding to the third data type mapped to the link 1.
  • the embodiments of the present application it is possible to determine whether there is cache data corresponding to the third data type in the second MLD according to the fifth indication information in the cache data corresponding to the third data type. Further, according to whether the cache data corresponding to the third data type is cached in the second MLD, it is beneficial to determine a more suitable working state for the station in the first MLD, and is beneficial to reduce power consumption.
  • FIG. 7 is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application.
  • the execution subject of step S701 to step S702 is the second MLD, or the chip in the second MLD
  • the execution subject of step S703 is the first MLD, or the chip in the first MLD.
  • the second MLD and the first MLD are executed.
  • An MLD is an example of the execution subject of the method for determining the data caching situation. The method may include but is not limited to the following steps:
  • Step S701 The second MLD determines that the second MLD does not have cached data corresponding to the fifth data type, and the fifth data type is any data type among the data types supported by the first MLD.
  • Step S702 The second MLD sends seventh indication information to the first MLD, where the seventh indication information is used to indicate that the second MLD does not cache the cache data corresponding to the fifth data type.
  • Step S703 According to the seventh indication information, the first MLD determines that the second MLD does not cache the cache data corresponding to the fifth data type.
  • step S701 to step S703 please refer to the specific description of step S603 in FIG. 6a, which will not be repeated here.
  • the first MLD may have multiple sites; after the first MLD determines that the second MLD does not cache the cached data corresponding to the fifth data type, it may be based on whether the second MLD does not cache the cache data corresponding to the fifth data type.
  • the data is cached, and the working status of the station corresponding to the third link among the multiple stations of the first MLD is determined, and the fifth data type is mapped to the third link.
  • the first MLD may determine the working state of the station corresponding to the third link as the dormant state.
  • the first MLD may determine, based on one or more items in the related information, and the second MLD that does not cache cached data corresponding to the fifth data type, the The working status of the station corresponding to the three links.
  • Related information may include, but is not limited to: current power information of the first MLD, service demand information of the first MLD, whether the third link is mapped with other data types other than the fifth data type, the priority of the fifth data type, Priorities of data types other than the fifth data type mapped to the third link (in the case where the third link is mapped with other data types other than the fifth data type).
  • FIG. 8 is a schematic flowchart of another method for determining a data caching situation provided by an embodiment of the present application.
  • the execution subject of step S801 to step S802 is the second MLD, or the chip in the second MLD
  • the execution subject of step S803 is the first MLD, or the chip in the first MLD.
  • the second MLD and the first MLD are executed.
  • An MLD is an example of the execution subject of the method for determining the data caching situation. The method may include but is not limited to the following steps:
  • Step S801 The second MLD determines that the second MLD does not cache the cache data corresponding to any data type mapped to the fourth link.
  • the second MLD does not cache the cached data corresponding to any data type mapped to the fourth link, which may indicate that the subsequent second MLD will not send data to the first MLD through the fourth link.
  • the fourth link is link 1, and when link 1 is mapped with data type a and data type b, if the second MLD does not have cached data corresponding to data type a, nor does it have cached data corresponding to data type b If the data is cached, it can be determined that the second MLD does not cache the cached data corresponding to any data type mapped to the link 1 (ie, the fourth link).
  • Step S802 The second MLD sends eighth indication information to the first MLD through the fourth link, where the eighth indication information is used to indicate that the second MLD does not cache any data type corresponding to the fourth link. Cache data.
  • the eighth indication information may be a QoS Null frame
  • the QoS Null frame is a data frame that does not carry a payload
  • the value of the More Data subfield in the QoS Null frame is 0.
  • the QoS Null frame is transmitted to the first MLD through the link 1, it may indicate that the second MLD does not buffer any buffer data corresponding to any data type mapped on the link 1 (used to transmit the QoS Null frame).
  • Step S803 The first MLD determines, according to the eighth indication information, that the second MLD does not cache the cache data corresponding to any data type mapped to the fourth link.
  • the first MLD after the first MLD receives the eighth indication information from the second MLD through the fourth link, it can be determined according to the eighth indication information that the second MLD does not cache the cache data corresponding to any data type mapped to the fourth link .
  • the first MLD may have multiple sites; after the first MLD determines that the second MLD does not cache the cached data corresponding to any data type mapped to the fourth link, it may be based on the second MLD not cached There is cache data corresponding to any data type mapped to the fourth link, and the working status of the station corresponding to the fourth link among the multiple stations of the first MLD is determined. For example, according to the second MLD not having cached data corresponding to any data type mapped to the fourth link, the first MLD may determine the working state of the station corresponding to the fourth link as the dormant state.
  • the first MLD may be based on one or more of the current power information or service requirement information of the first MLD, and the second MLD does not cache any data type corresponding to the fourth link. Buffer data to determine the working status of the station corresponding to the fourth link.
  • the second MLD does not have cached data corresponding to any data type mapped to the fourth link.
  • FIG. 9a is a schematic flowchart of another method for determining a data caching situation according to an embodiment of the present application.
  • This method describes in detail how the first MLD determines, according to the tenth indication information, the caching status of the cached data corresponding to at least one data type mapped to at least one link in the second MLD.
  • the execution subject of step S901 to step S902 is the second MLD, or the chip in the second MLD
  • the execution subject of step S903 is the first MLD, or the chip in the first MLD.
  • the second MLD and the first MLD are executed.
  • An MLD is an example of the execution subject of the method for determining the data caching situation. The method may include but is not limited to the following steps:
  • Step S901 The second MLD determines the buffer status of the buffered data corresponding to the at least one data type mapped to the at least one link corresponding to the first MLD in the second MLD.
  • the second MLD may include multiple cache areas, and each cache area may be used to cache cache data corresponding to one or more links (between the second MLD and the first MLD). If the cache area r is used to cache the cache data corresponding to the link 1, it may indicate that the cache data in the cache area r will be transmitted to the first MLD through the link 1. If the buffer area r is used to buffer the buffer data corresponding to the link 1 and the link 2, it may indicate that the buffer data in the buffer area r can be transmitted to the first MLD through at least one of the link 1 and the link 2. Therefore, the second MLD can determine whether there is cache data in the second MLD for the link corresponding to each cache area by detecting whether each cache area in the second MLD has cache data. One link may be mapped with one or more data types. Further, the second MLD may determine the buffer status of the data type mapped by the link corresponding to each buffer area in the buffer area.
  • the second MLD can determine the cache status of each TID in each cache area .
  • Step S902 The second MLD sends tenth indication information to the first MLD, where the tenth indication information is used to indicate that the buffer data corresponding to at least one data type mapped to the at least one link corresponding to the first MLD is in the second MLD The cache situation.
  • the tenth indication information may refer to the bits occupied by the control type b in the EHT A-control field in the MAC frame.
  • Control type b is a newly added control type.
  • 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.
  • L is the number of links between the first MLD and the MLD.
  • 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 Bit, a bit in the per link structure corresponds to a data type. Specifically, one of the bits may correspond to the management frame, and each of the other 8 bits corresponds to a kind of TID on the link.
  • the value of a bit in the per link structure corresponding to link 1 is 1, it can indicate that the second MLD has buffered data of the data type (such as management frame or TID) corresponding to the bit, and The buffered data will be sent to the first MLD through link 1.
  • the value of a bit in the per link structure corresponding to link 1 is 0, it can indicate that there is no data type (such as management Frame or TID) buffer data.
  • Step S903 The first MLD determines, according to the tenth indication information, the buffering situation of the buffered data corresponding to the at least one data type mapped to the at least one link in the second MLD.
  • the tenth indication information may refer to the bits occupied by the More Data Per TID Per link subfield.
  • the first MLD allocates different buffer areas to each link, and one bit in the per link structure corresponds to one data type.
  • the first MLD receives the tenth indication information from the second MLD, according to the tenth indication information, it can be determined that the cache data corresponding to various data types mapped to each link is cached in the second MLD. For example, when the link between the first MLD and the second MLD includes link 1 and link 2, the schematic diagram of the More Data Per TID Per link subfield may be as shown in FIG. 9b.
  • the More Data Per TID Per link subfield includes two per link structures (link 1 and link 2), and the small square in the figure represents a bit. Among them, each bit in the per link structure corresponding to link 1 corresponds to a data type, and different bits correspond to different data types.
  • the 9 bits in the per link structure corresponding to link 1 (or link 2) correspond to T1D0 to TID7 and management frames, respectively.
  • the value of the first 4 bits in the per link structure corresponding to link 1 is 1, and the value of the last 4 bits is 0, which can indicate that TID0 ⁇ are cached in the buffer area corresponding to link 1 in the second MLD.
  • the cache data corresponding to TID3, but the cache data corresponding to TID4 to TID7 and the management frame are not cached.
  • the value of the first and last bit in the per link structure corresponding to link 2 is 1, and the value of the remaining bits is 0, which can indicate that there are buffers in the buffer area corresponding to link 2 in the second MLD.
  • TID0, the cache data corresponding to the management frame, but the cache data corresponding to TID1 to TID7 are not cached.
  • a per link structure may include one or more bits.
  • the number of bits included in the per link structure may be the same as the number of data types of the link mapping corresponding to the per link structure.
  • the data type is AC
  • the number of bits included in the per link structure may be the same as the TID of the link mapping corresponding to the per link structure, and the number of corresponding ACs is the same.
  • one bit in the per link structure corresponds to one data type (management frame, TID or AC), which is just for example, and one bit in the per link structure can correspond to one or more types of data.
  • Type management frame, TID or AC.
  • the first MLD allocates different buffer areas to each link
  • the bits in the per link structure can correspond to at least two data types.
  • the first MLD receives the tenth indication information from the second MLD, according to the tenth indication information, it is possible to determine the cache conditions of the cache data corresponding to the at least two data types mapped to each link in the second MLD. 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 there are buffers in the buffer area corresponding to link 1 in the second MLD. Cache data corresponding to at least one of TID1 and TID2. The value of the first bit is 0, which may indicate that neither the cache data corresponding to TID1 nor the cache data corresponding to TID2 is cached in the cache area corresponding to link 1 in the second MLD.
  • the first MLD may allocate the same buffer area for at least two links, and one bit in the per link structure corresponds to one data type.
  • the first MLD receives the tenth indication information from the second MLD, according to the tenth indication information, it is possible to determine the cache condition of the cache data corresponding to various data types mapped to the at least two links in the second MLD. For example, when the buffer area r in the second MLD corresponds to link 1 and link 2, and the first bit in the per link structure corresponding to link 1 and link 2 corresponds to TID1.
  • the buffer data corresponding to TID1 is buffered in the buffer area r, and the buffer data may be sent to the first MLD through link 1 and/or link 2. If the value of the first bit is 0, it can indicate that there is no cache data corresponding to TID1 in the cache area r, and neither link 1 and link 2 will transmit the cache data corresponding to TID1.
  • the first MLD may allocate the same buffer area for at least two links, and the bits in the per link structure may correspond to at least two data types.
  • the first MLD receives the tenth indication information from the second MLD, according to the tenth indication information, it can be determined that the cache data corresponding to the at least two data types mapped to the at least two links are cached in the second MLD.
  • the first MLD may have multiple sites; the first MLD may determine the first MLD according to the cache condition of the cache data corresponding to the at least one data type mapped to the at least one link in the second MLD The working status of at least one of the multiple sites. Specifically, the first MLD may determine the working status of each station owned by the first MLD according to the buffering situation of the buffer data corresponding to the various data types mapped to each link in the second MLD.
  • the cache area corresponding to link 1 in the second MLD has cache data corresponding to TID0 to TID3
  • the cache area corresponding to link 2 in the second MLD has cache data corresponding to TID1 and TID7, namely
  • the first MLD can determine that the working states of the link 1 and the link 2 are active. In this way, the buffer data corresponding to the aforementioned TID0 to TID3 can be received through the first link, and the buffer data corresponding to the aforementioned TID1 and TID7 can be received through the link 2.
  • the first MLD may be based on one or more of the current power information or service demand information of the first MLD, and the cache data corresponding to at least one data type mapped to at least one link.
  • the caching situation in the MLD determines the working status of at least one of the multiple sites possessed by the first MLD.
  • the tenth indication information it is possible to determine the buffering situation of the buffered data corresponding to the at least one data type mapped to the at least one link in the second MLD. In this way, the caching situation of the cached data in the second MLD can be determined in more detail, thereby facilitating the determination of a more suitable working state for the stations in the first MLD.
  • the methods provided in the embodiments of the present application are introduced from the perspectives of the first MLD and the second MLD respectively.
  • the first MLD and the second MLD may include a hardware structure and a software module, and the above functions are realized in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • One of the above-mentioned functions can be executed in a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 10 is a schematic structural diagram of a communication device 100 provided by an embodiment of this application.
  • the communication device 100 shown in FIG. 10 may include a communication unit 1001 and a processing unit 1002.
  • the communication unit 1001 may include a sending unit and/or a receiving unit, the sending unit is used to implement a sending function, the receiving unit is used to implement a receiving function, and the communication unit 1001 may implement a sending function and/or a receiving function.
  • the communication unit can also be described as a transceiving unit.
  • the communication device 100 may be a first MLD, a device in the first MLD, or a device that can be matched and used with the first MLD.
  • the communication device 100 When the communication device 100 is the first MLD, it may be the first MLD in the embodiments shown in FIGS. 2-9a.
  • the communication device 100 is the first MLD in the embodiment shown in FIG. 3a or FIG. 5:
  • the communication unit 1001 is configured 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;
  • the processing unit 1002 is configured to determine that the cache data corresponding to at least one data type is in the second MLD according to the first indication information and the correspondence between the association identifier of the first MLD and the data types supported by the first MLD The cache situation.
  • the communication device 100 has multiple sites; the communication unit 1001 may also be configured to determine that at least one of the multiple sites is cached in the second MLD according to the cache condition of cached data corresponding to at least one data type.
  • the communication unit 1001 is further configured to receive second indication information from the second MLD, and the second indication information is used to determine the correspondence between the association identifier and the data type.
  • the second indication information indicates at least one association identifier, and the at least one association identifier corresponds to at least one data type.
  • the communication device 100 may support multiple data types; the second indication information indicates a first association identifier, and the first association identifier corresponds to the first data type among the multiple data types; the processing unit 1002, It is also used to determine the association identifiers corresponding to data types other than the first data type among the multiple data types according to the first association identifier corresponding to the first data type.
  • the communication device 100 is the first MLD in the embodiment shown in FIG. 4a or FIG. 5:
  • the communication unit 1001 is configured to receive buffered data from the second MLD through the first link, the buffered data includes third indication information; the third indication information is used to indicate whether at least one second data type is buffered in the second MLD Corresponding cache data, where the second data type is any data type mapped to the first link;
  • the processing unit 1002 is configured to determine, according to the third indication information, whether there is at least one type of cache data corresponding to the second data type cached in the second MLD.
  • the communication device 100 has multiple sites; the processing unit 1002 is further configured to determine whether the second MLD has cached data corresponding to at least one second data type, and determine whether the multiple sites correspond to the first data type.
  • the processing unit 1002 is configured to determine the working status of the station corresponding to the first link among the multiple stations according to whether there is at least one type of cached data corresponding to the second data type cached in the second MLD, It is specifically used for: if there is at least one type of cache data corresponding to the second data type cached in the second MLD, determining that the working status of the station corresponding to the first link among the multiple stations is active; if there is no cache data in the second MLD If cached data corresponding to any second data type is cached, it is determined that the working state of the station corresponding to the first link among the multiple stations is an active state or a dormant state.
  • the third indication information indicates that at least one buffer data corresponding to the second data type is cached in the second MLD; the communication unit 1001 is further configured to receive fourth indication information from the second MLD; fourth The indication information is used to indicate that no cache data corresponding to any second data type is cached in the second MLD.
  • the communication device 100 is the first MLD in the embodiment shown in FIG. 6a:
  • the communication unit 1001 is configured to receive buffer data corresponding to the third data type from the second MLD, the buffer data includes fifth indication information, and the fifth indication information is used to indicate whether the third data type is buffered in the second MLD Cached data;
  • the processing unit 1002 is configured to determine, according to the fifth indication information, whether there is cache data corresponding to the third data type in the second MLD.
  • the communication device 100 has multiple sites; the processing unit 1002 may also be used to determine whether the second MLD has cached data corresponding to the third data type to determine whether the multiple sites are connected to the second link.
  • the third data type is mapped to the second link; the working state is an active state or a dormant state.
  • the processing unit 1002 may also be used to determine whether the second link is mapped with data types other than the third data type;
  • the processing unit 1002 is configured to determine the working status of the station corresponding to the second link among the multiple stations according to whether the cache data corresponding to the third data type is cached in the second MLD, and is specifically configured to: according to whether the cache data in the second MLD The buffered data corresponding to the third data type is cached, and whether the second link is mapped with other data types other than the third data type, and the working status of the station corresponding to the second link among the multiple stations is determined.
  • the fifth indication information indicates that the cache data corresponding to the third data type is not cached in the second MLD; the cache data corresponding to the third data type received by the communication unit 1001 from the second MLD further includes a sixth indication Information, the sixth indication information is 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 among the data types supported by the communication device 100 type of data.
  • the priority of the fourth data type may be higher than the priority of the third data type.
  • the communication device 100 is the first MLD in the embodiment shown in FIG. 7:
  • the communication unit 1001 is configured to receive seventh indication information from the second MLD, where the seventh indication information is used to indicate that the second MLD does not have cached data corresponding to the fifth data type; the fifth data type is the communication device Any of the supported data types;
  • the processing unit 1002 is configured to determine, according to the seventh indication information, that the second MLD does not have cached data corresponding to the fifth data type.
  • the communication device 100 has multiple sites; the processing unit 1002 is further configured to determine which of the multiple sites corresponds to the third link according to the cache data corresponding to the fifth data type that is not cached in the second MLD The working state of the station, the fifth data type is mapped to the third link; the working state is an active state or a dormant state.
  • the communication device 100 is the first MLD in the embodiment shown in FIG. 8:
  • the communication unit 1001 is configured to receive eighth indication information from the second MLD through the fourth link, where the eighth indication information is used to indicate that the second MLD does not buffer any data type corresponding to the fourth link Cache data;
  • the processing unit 1002 is configured to determine, according to the eighth indication information, that the second MLD does not have cached data corresponding to any data type mapped to the fourth link.
  • the communication device 100 has multiple sites; the processing unit 1002 is further configured to determine whether the second MLD has cached data corresponding to any data type mapped to the fourth link, and determine that the multiple sites The working state of the station corresponding to the fourth link; the working state is an active state or a dormant state.
  • processing unit 100 has multiple sites; the processing unit 1002 is also used to correspond to at least one data type
  • the communication device 100 is the first MLD in the embodiment shown in FIG. 2:
  • the communication unit 1001 is configured to receive ninth indication information from the second MLD, where the ninth indication information is used to indicate the buffer status of the buffered data corresponding to at least one data type supported by the communication device in the second MLD;
  • the processing unit 1002 is configured to determine, according to the ninth indication information, the caching status of the cached data corresponding to at least one data type in the second MLD.
  • the communication device 100 has multiple sites; the processing unit 1002 is further configured to determine the working status of at least one of the multiple sites according to the buffering situation of the buffered data of the communication device in the second MLD; The status is active or dormant.
  • the communication device 100 is the first MLD in the embodiment shown in FIG. 9a:
  • the communication unit 1001 is configured to receive tenth indication information from the second MLD, where the tenth indication information is used to indicate that the buffer data corresponding to at least one data type mapped to at least one link corresponding to the communication device is in the second MLD. Cache situation in
  • the processing unit 1002 is configured to determine, according to the tenth indication information, the buffering situation of the buffered data corresponding to the at least one data type mapped to the at least one link in the second MLD.
  • the communication device 100 has multiple stations; the processing unit 1002 is further configured to determine the multiple stations according to the cache condition of the cached data corresponding to the at least one data type mapped to the at least one link in the second MLD.
  • the working status of at least one of the stations; the working status is active or dormant.
  • FIG. 11 is a schematic structural diagram of another communication device 110 according to an embodiment of the present application.
  • the communication device 110 may be a first MLD, or may be a chip, a chip system, or a processor that supports the first MLD to implement the foregoing method.
  • the device can be used to implement the method described in the foregoing method embodiment, and for details, please refer to the description in the foregoing method embodiment.
  • the communication device 110 may include one or more processors 1101.
  • the processor 1101 may be a general-purpose processor, a special-purpose processor, or the like.
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processor can be used to control communication devices (such as base stations, baseband chips, terminals, terminal chips, DU or CU, etc.), execute computer programs, and process Computer program data.
  • the communication device 110 may also include a transceiver 1105.
  • the transceiver 1105 may be called a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing the transceiver function.
  • the transceiver 1105 may include a receiver and a transmitter.
  • the receiver may be referred to as a receiver or a receiving circuit, etc., to implement a receiving function;
  • the transmitter may be referred to as a transmitter or a transmitting circuit, etc., to implement a transmitting function.
  • the communication device 110 may further include an antenna 1106.
  • the communication device 110 may include one or more memories 1102, and a computer program 1104 may be stored thereon, and the computer program may be executed on the communication device 110, so that the communication device 110 executes the method described in the above method embodiments. Methods.
  • the memory 1102 may also store data. The communication device 110 and the memory 1102 can be provided separately or integrated together.
  • the processor 1101 is configured to execute step S203 in Fig. 2; step S304 in Fig. 3a; step S403 in Fig. 4a; step S504 to step S505 and step S509 in Fig. 5; step S603 in Fig. 6a; Step S703; Step S803 in FIG. 8 or Step S903 in FIG. 9a.
  • the transceiver 1105 is used for receiving the indication information from the second MLD in the embodiment shown in FIG. 2; receiving the first indication information from the second MLD in the embodiment shown in FIG. 3a; and receiving the first indication information from the second MLD in the embodiment shown in FIG. 4a.
  • the processor 1101 may include a transceiver for implementing receiving and sending functions.
  • the transceiver may be a transceiver circuit, or an interface, or an interface circuit.
  • the transceiver circuits, interfaces, or interface circuits used to implement the receiving and transmitting functions can be separate or integrated.
  • the foregoing transceiver circuit, interface, or interface circuit can be used for code/data reading and writing, or the foregoing transceiver circuit, interface, or interface circuit can be used for signal transmission or transmission.
  • the processor 1101 may store a computer program 1103, and the computer program 1103 runs on the processor 1101 to enable the communication device 110 to execute the method described in the foregoing method embodiment.
  • the computer program 1103 may be solidified in the processor 1101.
  • the processor 1101 may be implemented by hardware.
  • the communication device 110 may include a circuit, and the circuit may implement the sending or receiving or communication function in the foregoing method embodiment.
  • the processor and transceiver described in this application can be implemented in integrated circuit (IC), analog IC, radio frequency integrated circuit RFIC, mixed signal IC, application specific integrated circuit (ASIC), printed circuit board ( printed circuit board, PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), nMetal-oxide-semiconductor (NMOS), and P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS nMetal-oxide-semiconductor
  • PMOS bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiment may be the first MLD, but the scope of the communication device described in this application is not limited to this, and the structure of the communication device may not be limited by FIG. 11.
  • the communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • the IC collection may also include storage components for storing data and computer programs;
  • ASIC such as a modem (Modem)
  • the communication device can be a chip or a chip system
  • the chip shown in FIG. 12 includes a processor 1201 and an interface 1202.
  • the number of processors 1201 may be one or more, and the number of interfaces 1202 may be more than one.
  • the interface 1202 is configured 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 association identifier of the first MLD in the second MLD;
  • the processor 1201 is configured to determine, according to the first indication information and the correspondence between the association identifier of the first MLD and the data types supported by the first MLD, that cache data corresponding to at least one data type is in the second MLD The cache situation.
  • the first MLD has multiple sites; the processor 1201 may also be configured to determine that at least one of the multiple sites is at least The working status of a site; the working status is active or dormant.
  • the interface 1202 is also used to receive second indication information from the second MLD, and the second indication information is used to determine the correspondence between the association identifier and the data type.
  • the second indication information indicates at least one association identifier, and the at least one association identifier corresponds to at least one data type.
  • the first MLD may support multiple data types; the second indication information indicates a first association identifier, and the first association identifier corresponds to a first data type among the multiple data types; the processor 1201, It is also used to determine the association identifiers corresponding to data types other than the first data type among the multiple data types according to the first association identifier corresponding to the first data type.
  • the interface 1202 is configured to receive buffered data from the second MLD through the first link, the buffered data includes third indication information; the third indication information is used to indicate whether there is at least one second data type corresponding to the buffer in the second MLD Cached data of, where the second data type is any data type mapped to the first link;
  • the processor 1201 is configured to determine, according to the third indication information, whether there is at least one type of cache data corresponding to the second data type cached in the second MLD.
  • the first MLD has multiple sites; the processor 1201 is further configured to determine whether the second MLD has cached data corresponding to at least one second data type, and determine whether the first MLD is the first one among the multiple sites.
  • the processor 1201 is configured to determine the working status of the station corresponding to the first link among the plurality of stations according to whether there is at least one type of cache data corresponding to the second data type cached in the second MLD, It is specifically used for: if there is at least one type of cache data corresponding to the second data type cached in the second MLD, determining that the working status of the station corresponding to the first link among the multiple stations is active; if there is no cache data in the second MLD If cached data corresponding to any second data type is cached, it is determined that the working state of the station corresponding to the first link among the multiple stations is an active state or a dormant state.
  • the third indication information indicates that at least one type of cache data corresponding to the second data type is cached in the second MLD; the interface 1202 is further configured to receive fourth indication information from the second MLD; and the fourth indication The information is used to indicate that no cache data corresponding to any second data type is cached in the second MLD.
  • the interface 1202 is configured to receive cache data corresponding to the third data type from the second MLD, the cache data includes fifth indication information, and the fifth indication information is used to indicate whether the second MLD has cached data corresponding to the third data type.
  • Cache data ;
  • the processor 1201 is configured to determine, according to the fifth indication information, whether there is cache data corresponding to the third data type in the second MLD.
  • the first MLD has multiple sites; the processor 1201 may also be configured to determine whether the second MLD has cached data corresponding to the third data type, and determine whether the multiple sites are connected to the second link.
  • the third data type is mapped to the second link; the working state is an active state or a dormant state.
  • the processor 1201 may also be used to determine whether the second link is mapped with other data types other than the third data type; the processor 1201 is used to determine whether the third data type is cached in the second MLD
  • the cache data corresponding to the type is specifically used to: according to whether the cache data corresponding to the third data type is cached in the second MLD, and the second link Whether there is a data type other than the third data type is mapped, and the working status of the station corresponding to the second link among the multiple stations is determined.
  • the fifth indication information indicates that the cache data corresponding to the third data type is not cached in the second MLD; the cache data corresponding to the third data type received by the interface 1202 from the second MLD further includes sixth indication information ,
  • the sixth indication information is 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 other than the third data type among the data types supported by the first MLD type.
  • the priority of the fourth data type may be higher than the priority of the third data type.
  • the interface 1202 is configured to receive seventh indication information from the second MLD, where the seventh indication information is used to indicate that the second MLD does not have cached data corresponding to the fifth data type; the fifth data type is the first MLD Any of the supported data types;
  • the processor 1201 is configured to determine, according to the seventh indication information, that the second MLD does not cache the cache data corresponding to the fifth data type.
  • the first MLD has multiple sites; the processor 1201 is further configured to determine which of the multiple sites corresponds to the third link according to the cache data corresponding to the fifth data type that is not cached in the second MLD The working state of the station, the fifth data type is mapped to the third link; the working state is an active state or a dormant state.
  • the interface 1202 is configured to receive eighth indication information from the second MLD through the fourth link, where the eighth indication information is used to indicate that the second MLD does not have a cache corresponding to any data type mapped to the fourth link data;
  • the processor 1201 is configured to determine, according to the eighth indication information, that the second MLD does not have cached data corresponding to any data type mapped to the fourth link.
  • the first MLD has multiple sites; the processor 1201 is further configured to determine whether the second MLD has cached data corresponding to any data type mapped to the fourth link, and determine that the multiple sites are The working state of the station corresponding to the fourth link; the working state is an active state or a dormant state.
  • the interface 1202 is configured to receive ninth indication information from the second MLD, where the ninth indication information is used to indicate the caching status of the cached data corresponding to at least one data type supported by the first MLD in the second MLD;
  • the processor 1201 is configured to determine, according to the ninth indication information, a cache situation of the cache data corresponding to at least one data type in the second MLD.
  • the processor 1201 is further configured to determine the working state of at least one of the multiple sites according to the cache condition of the cached data of the first MLD in the second MLD; the working state is an active state or a dormant state .
  • the interface 1202 is configured to receive tenth indication information from the second MLD, where the tenth indication information is used to indicate that the buffer data corresponding to at least one data type mapped to at least one link corresponding to the first MLD is in the second MLD. Cache situation in
  • the processor 1201 is configured to determine, according to the tenth indication information, a cache situation of the cache data corresponding to the at least one data type mapped to the at least one link in the second MLD.
  • the first MLD has multiple sites; the processor 1201 is further configured to determine the multiple sites according to the cache condition of the cache data corresponding to the at least one data type mapped to the at least one link in the second MLD.
  • the working status of at least one of the stations; the working status is active or dormant.
  • the chip further includes a memory 1203, and the memory 1203 is used to store necessary computer programs and data.
  • FIG. 13 is a schematic structural diagram of another communication device 130 provided by an embodiment of this application.
  • the communication device 130 shown in FIG. 13 may include a communication unit 1301, a processing unit 1302, and a storage unit 1303.
  • the communication unit 1301 may include a sending unit and/or a receiving unit, the sending unit is used to implement a sending function, the receiving unit is used to implement a receiving function, and the communication unit 1301 may implement a sending function and/or a receiving function.
  • the communication unit can also be described as a transceiving unit.
  • the communication device 130 may be a second MLD, a device in the second MLD, or a device that can be matched and used with the second MLD.
  • the communication device 130 is the second MLD, it may be the second MLD in the embodiments shown in FIGS. 2-9a.
  • the communication device 130 is the second MLD in the embodiment shown in FIG. 3a or FIG. 5:
  • the processing unit 1302 is configured to determine the cache condition of the cache data corresponding to at least one data type supported by the first MLD in the storage unit 1303; according to the cache condition of the cache data corresponding to the at least one data type in the storage unit 1303, And the correspondence between the association identifier of the first MLD and the supported data types, and determine the caching situation of the cache data corresponding to the association identifier in the storage unit 1303;
  • the communication unit 1301 is configured to send first indication information to the first MLD; the first indication information is used to indicate the caching status of the cache data corresponding to the associated identifier of the first MLD in the storage unit 1303.
  • the communication unit 1301 is further configured to send second indication information to the first MLD, and the second indication information is used to determine the correspondence between the association identifier of the first MLD and the data type supported by the first MLD relation.
  • the second indication information indicates at least one association identifier, and the at least one association identifier corresponds to at least one data type.
  • the first MLD supports multiple data types; the second indication information indicates a first association identifier, and the first association identifier corresponds to a first data type among the multiple data types.
  • the communication device 130 is the second MLD in the embodiment shown in FIG. 4a or FIG. 5:
  • the processing unit 1302 is configured 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;
  • the communication unit 1301 is configured to send buffered data to the first MLD through the first link, the buffered data includes third indication information; the third indication information is used to indicate whether the storage unit 1303 has at least one type of second The cached data corresponding to the data type.
  • 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 fourth indication information to the first MLD; and the fourth indication The information is used to indicate that no cache data corresponding to any second data type is cached in the storage unit 1303.
  • the communication device 130 is the second MLD in the embodiment shown in FIG. 6a:
  • the processing unit 1302 is configured to determine whether there is cached data corresponding to the third data type in the storage unit 1303;
  • the communication unit 1301 is configured to send buffer data corresponding to the third data type to the first MLD, where the buffer data includes fifth indication information, and the fifth indication information is used to indicate whether the storage unit 1303 has the third data type buffered Corresponding cache data.
  • the fifth indication information indicates that there is no cache data corresponding to the third data type in the storage unit 1303; the cache data corresponding to the third data type sent by the communication unit 1301 to the first MLD further includes a sixth indication Information, the sixth indication information is used to indicate whether the storage unit 1303 has cached data corresponding to at least one fourth data type; the fourth data type is data types supported by the first MLD except for the third data type Any data type of.
  • the priority of the fourth data type may be higher than the priority of the third data type.
  • the communication device 130 is the second MLD in the embodiment shown in FIG. 7:
  • the processing unit 1302 is configured to determine that the storage unit 1303 does not have cached data corresponding to the fifth data type; the fifth data type is any data type among the data types supported by the first MLD;
  • the communication unit 1301 is configured to send seventh indication information to the first MLD, where the seventh indication information is used to indicate that the storage unit 1303 does not have cached data corresponding to the fifth data type.
  • the communication device 130 is the second MLD in the embodiment shown in FIG. 8:
  • the processing unit 1302 is configured to determine that the storage unit 1303 does not cache any cache data corresponding to any data type mapped to the fourth link;
  • the communication unit 1301 is configured to send eighth indication information to the first MLD through the fourth link, where the eighth indication information is used to indicate that the storage unit 1303 does not cache any data type corresponding to the fourth link Cache data.
  • the communication device 130 is the second MLD in the embodiment shown in FIG. 2:
  • the processing unit 1302 is configured to determine the cache condition of the cache data corresponding to at least one data type supported by the first MLD in the storage unit 1303;
  • the communication unit 1301 is configured to send ninth indication information to the first MLD, where the ninth indication information is used to indicate the caching status of the cache data corresponding to at least one data type supported by the first MLD in the storage unit 1303.
  • the communication device 130 is the second MLD in the embodiment shown in FIG. 9a:
  • the processing unit 1302 is configured to determine the buffering situation in the storage unit 1303 of cached data corresponding to at least one data type mapped to at least one link corresponding to the first MLD;
  • the communication unit 1301 is configured to send tenth indication information to the first MLD, where the tenth indication information is used to indicate that buffer data corresponding to at least one data type mapped to at least one link corresponding to the first MLD is stored in the storage unit 1303 The cache situation.
  • FIG. 14 is a schematic structural diagram of another communication device 140 according to an embodiment of the present application.
  • the communication device 140 may be a second MLD, or may be a chip, a chip system, or a processor that supports the second MLD to implement the foregoing method.
  • the device can be used to implement the method described in the foregoing method embodiment, and for details, please refer to the description in the foregoing method embodiment.
  • the communication device 140 may include one or more processors 1401.
  • the processor 1401 may be a general-purpose processor, a special-purpose processor, or the like.
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processor can be used to control communication devices (such as base stations, baseband chips, terminals, terminal chips, DU or CU, etc.), execute computer programs, and process Computer program data.
  • the communication device 140 may also include a transceiver 1405.
  • the transceiver 1405 may be called a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing the transceiver function.
  • the transceiver 1405 may include a receiver and a transmitter.
  • the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function;
  • the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.
  • the communication device 140 may further include an antenna 1406.
  • the communication device 140 may further include one or more memories 1402, on which a computer program 1404 may be stored, and the computer program may be executed on the communication device 140 so that the communication device 140 executes the method described in the above method embodiment.
  • the memory 1402 may also store data.
  • the communication device 140 and the memory 1402 can be provided separately or integrated together.
  • the processor 1401 is configured to execute step S201 in Fig. 2; steps S301 to S302 in Fig. 3a; step S401 in Fig. 4a; steps S501 to S502, and step S507 in Fig. 5; step S601 in Fig. 6a; Fig. 7 Step S701 in Fig. 8 or step S901 in Fig. 9a.
  • the transceiver 1405 is used to perform S202 in Fig. 2; Step S303 in Fig. 3a; Step S402 in Fig. 4a; Step S503 and Step S508 in Fig. 5; Step S602 in Fig. 6a; Step S702 in Fig. 7; Step S802 in 8 or step S902 in FIG. 9a.
  • the processor 1401 may include a transceiver for implementing receiving and sending functions.
  • the transceiver may be a transceiver circuit, or an interface, or an interface circuit.
  • the transceiver circuits, interfaces, or interface circuits used to implement the receiving and transmitting functions can be separate or integrated.
  • the foregoing transceiver circuit, interface, or interface circuit can be used for code/data reading and writing, or the foregoing transceiver circuit, interface, or interface circuit can be used for signal transmission or transmission.
  • the processor 1401 may store a computer program 1403, and the computer program 1403 runs on the processor 1401 to enable the communication device 140 to execute the method described in the foregoing method embodiment.
  • the computer program 1403 may be solidified in the processor 1401.
  • the processor 1401 may be implemented by hardware.
  • the communication device 140 may include a circuit, and the circuit may implement the sending or receiving or communication function in the foregoing method embodiment.
  • the processor and transceiver described in this application can be implemented in integrated circuit (IC), analog IC, radio frequency integrated circuit RFIC, mixed signal IC, application specific integrated circuit (ASIC), printed circuit board ( printed circuit board, PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), nMetal-oxide-semiconductor (NMOS), and P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS nMetal-oxide-semiconductor
  • PMOS bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiment may be the second MLD, but the scope of the communication device described in this application is not limited to this, and the structure of the communication device may not be limited by FIG. 14.
  • the communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • the IC collection may also include storage components for storing data and computer programs;
  • ASIC such as a modem (Modem)
  • the communication device can be a chip or a chip system
  • the chip shown in FIG. 15 includes a processor 1501, an interface 1502, and a memory 1503.
  • the number of processors 1501 may be one or more, the number of interfaces 1502 may be multiple, and the number of memories 1503 may be one or more.
  • the memory 1503 is used to store cached data, as well as necessary computer programs and data.
  • the processor 1501 is configured to determine the cache condition of the cache data corresponding to at least one data type supported by the first MLD in the memory 1503; according to the cache condition of the cache data corresponding to the at least one data type in the memory 1503, and the first MLD A correspondence between the association identifier of the MLD and the supported data types, and the caching situation of the cache data corresponding to the association identifier in the memory 1503 is determined;
  • the interface 1502 is configured to send first indication information to the first MLD; the first indication information is used to indicate the caching status of the cache data corresponding to the associated identifier of the first MLD in the memory 1503.
  • the interface 1502 is also used to send second indication information to the first MLD, and the second indication information is used to determine the correspondence between the association identifier of the first MLD and the data type supported by the first MLD .
  • the second indication information indicates at least one association identifier, and the at least one association identifier corresponds to at least one data type.
  • the first MLD supports multiple data types; the second indication information indicates a first association identifier, and the first association identifier corresponds to a first data type among the multiple data types.
  • the processor 1501 is configured to determine whether cache data corresponding to at least one second data type is cached in the memory 1503; the second data type is any data type mapped to the first link;
  • the interface 1502 is configured to send buffered data to the first MLD through the first link, where the buffered data includes third indication information; the third indication information is used to indicate whether at least one second data type is buffered in the memory 1503 Corresponding cache data.
  • the third indication information indicates that there is at least one type of cache data corresponding to the second data type cached in the memory 1503; the interface 1502 is also used to send fourth indication information to the first MLD; the fourth indication information is used for No cache data corresponding to any second data type is cached in the indicating memory 1503.
  • the processor 1501 is configured to determine whether cache data corresponding to the third data type is cached in the memory 1503;
  • the interface 1502 is configured to send cache data corresponding to the third data type to the first MLD, where the cache data includes fifth indication information, and the fifth indication information is used to indicate whether the memory 1503 has cached data corresponding to the third data type. Cache data.
  • the fifth indication information indicates that the cache data corresponding to the third data type is not cached in the memory 1503; the cache data corresponding to the third data type sent by the interface 1502 to the first MLD further includes sixth indication information.
  • the sixth indication information is used to indicate whether the memory 1503 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 among the data types supported by the first MLD type of data.
  • the priority of the fourth data type may be higher than the priority of the third data type.
  • the processor 1501 is configured to determine that the buffer data corresponding to the fifth data type is not cached in the memory 1503; the fifth data type is any data type among the data types supported by the first MLD;
  • the interface 1502 is configured to send seventh indication information to the first MLD, where the seventh indication information is used to indicate that the memory 1503 does not have cached data corresponding to the fifth data type.
  • the processor 1501 is configured to determine that the memory 1503 does not have cached data corresponding to any data type mapped on the fourth link;
  • the interface 1502 is configured to send eighth indication information to the first MLD through the fourth link, where the eighth indication information is used to indicate that the memory 1503 does not cache any cache data corresponding to any data type mapped on the fourth link .
  • the processor 1501 is configured to determine the cache condition of the cache data corresponding to at least one data type supported by the first MLD in the memory 1503;
  • the interface 1502 is configured to send ninth indication information to the first MLD, where the ninth indication information is used to indicate the caching status of the cache data corresponding to at least one data type supported by the first MLD in the memory 1503.
  • the processor 1501 is configured to determine a cache situation in the memory 1503 of cache data corresponding to at least one data type mapped to at least one link corresponding to the first MLD;
  • the interface 1502 is configured to send tenth indication information to the first MLD, where the tenth indication information is used to indicate the cache data corresponding to at least one data type mapped to the at least one link corresponding to the first MLD in the memory 1503 Condition.
  • the present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer-readable storage medium is executed by a computer, the function of any of the foregoing method embodiments is realized.
  • This application also provides a computer program product, which, when executed by a computer, realizes the functions of any of the foregoing method embodiments.
  • the computer program product includes one or more computer programs.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer program may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer program may be downloaded from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk, SSD)) etc.
  • At least one in this application can also be described as one or more, and the multiple can be two, three, four or more, which is not limited in this application.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C”, and “D”, etc.
  • first”, “Second”, “Third”, “A”, “B”, “C” and “D” there is no order or size order among the technical features.
  • the corresponding relationships shown in the tables in this application can be configured or pre-defined.
  • the value of the information in each table is only an example, and can be configured to other values, which is not limited in this application.
  • the corresponding relationship shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, and so on.
  • the names of the parameters shown in the titles in the above tables may also be other names that can be understood by the communication device, and the values or expressions of the parameters may also be other values or expressions that can be understood by the communication device.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear tables, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables. Wait.
  • the pre-definition in this application can be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, curing, or pre-fired.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Computer And Data Communications (AREA)
  • Measurement Of Mechanical Vibrations Or Ultrasonic Waves (AREA)

Abstract

本申请实施例公开了一种数据缓存情况的确定方法及其装置，该方法包括：第一多链路设备MLD接收来自第二MLD的第一指示信息；根据该第一指示信息，以及该第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况；其中，该第一指示信息用于指示第一MLD的关联标识对应的缓存数据在第二MLD中的缓存情况。通过实施本申请实施例，可以确定数据类型维度的数据缓存情况。本申请实施例可以应用于支持IEEE 802.11下一代WiFi EHT协议，即802.11be等802.11协议的无线局域网系统。

Description

一种数据缓存情况的确定方法及其装置
本申请要求于2020年3月13日提交中国专利局、申请号为202010180304.6、申请名称为“一种数据缓存情况的确定方法及其装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种数据缓存情况的确定方法及其装置。
背景技术
不断提高吞吐率是蜂窝网以及无线局域网(wireless local area network，WLAN)发展演进的持续目标。为了达到极高吞吐率，下一代标准IEEE 802.11be将多链路(multi-link，ML)作为关键技术之一。拥有在多频段(multi-band)发送和接收数据能力的多链路设备(multi-link device，MLD)，可以使用更大的带宽进行数据传输，进而显著提升吞吐率。MLD包括多个站点(station，STA)，每个站点可以与另外一个MLD中的一个站点建立一条链路进行通信。
非接入点(non-access point，non-AP)的站点可以处于活跃状态(active state)或休眠状态(doze state)。在该non-AP站点处于活跃状态的情况下，该non-AP站点对应的链路也处于活跃状态，该non-AP站点与AP站点之间可以通过该链路传输数据；在该non-AP站点处于休眠状态的情况下，该non-AP站点对应的链路也处于休眠状态，该non-AP站点与AP站点之间无法传输数据。
在non-AP站点处于休眠状态的情况下，AP MLD可以对待发送给non-AP站点的数据业务进行缓存，并在该non-AP站点处于活跃状态的情况下，通过该non-AP站点对应的链路将缓存的数据业务发送给该non-AP站点。
但是，non-AP MLD无法获知该non-AP MLD对应的缓存数据在AP MLD中的缓存情况，这样不利于该non-AP MLD准确地确定所关联的链路的工作状态。因此，如何确定non-AP MLD对应的缓存数据在AP MLD中的缓存情况成为亟待解决的技术问题。
发明内容
本申请实施例提供一种数据缓存情况的确定方法及其装置，可以确定数据类型维度的数据缓存情况。
第一方面，本申请实施例提供了一种数据缓存情况的确定方法，该方法包括：第一多链路设备MLD接收来自第二MLD的第一指示信息；该第一指示信息用于指示第一MLD的关联标识对应的缓存数据在第二MLD中的缓存情况；第一MLD根据该第一指示信息，以及第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在该技术方案中，可以确定第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，第一MLD可以具有多个站点；该方法还可以包括：第一MLD根 据至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，确定多个站点中至少一个站点的工作状态；该工作状态为活跃状态或休眠状态。
在该技术方案中，根据缓存数据的数据类型，有利于为第一MLD中的站点确定更加合适的工作状态，从而有利于降低功耗。
在一种实现方式中，该方法还可以包括：第一MLD接收来自第二MLD的第二指示信息，该第二指示信息用于确定第一MLD的关联标识与第一MLD支持的数据类型之间的对应关系。
在一种实现方式中，第二指示信息指示至少一个关联标识，至少一个关联标识对应至少一种数据类型。
在该技术方案中，通过第二指示信息指示至少一种数据类型所对应的至少一个关联标识(associate identifier，AID)，可以更加更加灵活的为第一MLD分配AID。
在一种实现方式中，第一MLD支持多种数据类型；前述第二指示信息指示一个第一关联标识，该第一关联标识与多种数据类型中的第一数据类型相对应；该方法还可以包括：第一MLD根据该第一数据类型对应的第一关联标识，确定多种数据类型中除第一数据类型以外的其他数据类型对应的关联标识。
在该技术方案中，通过在第二指示信息中指示一个AID的方式，可以有效节省信令开销。
第二方面，本申请实施例提供了另一种数据缓存情况的确定方法，该方法包括：第二多链路设备MLD确定第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况；根据至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，以及第一MLD的关联标识与支持的数据类型之间的对应关系，确定关联标识对应的缓存数据在第二MLD中的缓存情况；向第一MLD发送第一指示信息；该第一指示信息用于指示第一MLD的关联标识对应的缓存数据在第二MLD中的缓存情况。
在该技术方案中，通过指示第一MLD的关联标识对应的缓存数据在第二MLD中的缓存情况，有利于第一MLD结合关联标识与所支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，该方法还可以包括：第二MLD向第一MLD发送第二指示信息，该第二指示信息用于确定第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系。
在一种实现方式中，第二指示信息指示至少一个关联标识，至少一个关联标识对应至少一种数据类型。
在该技术方案中，通过第二指示信息指示至少一种数据类型所对应的至少一个关联标识(AID)，可以更加更加灵活的为第一MLD分配AID。
在一种实现方式中，第一MLD支持多种数据类型；该第二指示信息指示一个第一关联标识，该第一关联标识与多种数据类型中的第一数据类型相对应。
在该技术方案中，通过在第二指示信息中指示一个AID的方式，可以有效节省信令开销。
第三方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第一 多链路设备MLD通过第一链路从第二MLD接收缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，其中，第二数据类型为映射于第一链路的任一数据类型；第一MLD根据该第三指示信息，确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
在该技术方案中，通过第三指示信息可以确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，换言之，通过第三指示信息可以确定是否有缓存数据可能通过第一链路传输至第一MLD。
在一种实现方式中，第一MLD具有多个站点；该方法还包括：第一MLD根据第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，确定多个站点中与第一链路对应的站点的工作状态；该工作状态为活跃状态或休眠状态。
在该技术方案中，根据第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，有利于为第一链路对应的站点确定更加合适的工作状态。
在一种实现方式中，第一MLD根据第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，确定多个站点中与第一链路对应的站点的工作状态的具体实施方式可以为：若第二MLD中缓存有至少一种第二数据类型对应的缓存数据，则第一MLD确定多个站点中与第一链路对应的站点的工作状态为活跃状态；若第二MLD中未缓存有任一第二数据类型对应的缓存数据，则第一MLD确定多个站点中与第一链路对应的站点的工作状态为活跃状态或休眠状态。
在该技术方案中，第二MLD中缓存有至少一种第二数据类型对应的缓存数据时，第一链路对应的站点的工作状态为活跃状态。若链路1发生链路拥塞(或干扰等情况)而导致无法传输缓存数据，且该链路1上待传输的缓存数据的数据类型也映射于第一链路，那么在该数据类型对应的缓存数据发送完毕之前，第一链路对应的站点处于活跃状态，即链路1处于休眠状态。因此，第二MLD可以将链路1上待传输的缓存数据调度至第一链路进行传输。通过这种方式，有利于为站点确定更加合适的工作状态，并有利于将第二MLD中的缓存数据成功发送至第一MLD。
在一种实现方式中，第三指示信息指示第二MLD中缓存有至少一种第二数据类型对应的缓存数据；该方法还包括：第一MLD接收来自第二MLD的第四指示信息；该第四指示信息用于指示第二MLD中未缓存有任一第二数据类型对应的缓存数据。
在该技术方案中，第四指示信息可以为服务质量空值(quality of service Null，QoS Null)帧。当第二MLD无法通过第一链路向第二MLD发送缓存数据，也无法通过缓存数据中的第三指示信息以指示第二MLD中未缓存有任一第二数据类型对应的缓存数据时，第一MLD根据来自第二MLD的第四指示信息可以确定第二MLD中未缓存有任一第二数据类型对应的缓存数据。
第四方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第二多链路设备MLD确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据；该第二数据类型为映射于第一链路的任一数据类型；第二MLD通过该第一链路向第一MLD发送缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示该第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
在该技术方案中，通过第三指示信息可以指示第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，换言之，通过第三指示信息可以指示是否有缓存数据可能通过第一链路传输至第一MLD。
在一种实现方式中，该第三指示信息指示第二MLD中缓存有至少一种第二数据类型对应的缓存数据；该方法还可以包括：第二MLD向第一MLD发送第四指示信息；该第四指示信息用于指示该第二MLD中未缓存有任一第二数据类型对应的缓存数据。
在该技术方案中，第四指示信息可以为QoS Null帧。当第二MLD无法通过第一链路向第二MLD发送缓存数据，也无法通过缓存数据中的第三指示信息以指示第二MLD中未缓存有任一第二数据类型对应的缓存数据时，第二MLD通过向第一MLD发送第四指示信息，可以指示第二MLD中未缓存有任一第二数据类型对应的缓存数据。
第五方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第一多链路设备MLD从第二MLD接收第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示第二MLD中是否缓存有该第三数据类型对应的缓存数据；第一MLD根据该第五指示信息，确定该第二MLD中是否缓存有该第三数据类型对应的缓存数据。
在该技术方案中，根据第三数据类型对应的缓存数据中的第五指示信息，可以确定第二MLD中是否缓存有该第三数据类型对应的缓存数据。
在一种实现方式中，第一MLD具有多个站点；该方法还包括：第一MLD根据第二MLD中是否缓存有第三数据类型对应的缓存数据，确定多个站点中与第二链路对应的站点的工作状态，该第三数据类型映射于该第二链路；工作状态为活跃状态或休眠状态。
在该技术方案中，根据第二MLD中是否缓存有第三数据类型对应的缓存数据，有利于为第二链路对应的站点确定更加合适的工作状态。
在一种实现方式中，该方法还包括：第一MLD确定第二链路是否映射有除第三数据类型以外的其他数据类型；第一MLD根据第二MLD中是否缓存有第三数据类型对应的缓存数据，确定多个站点中与第二链路对应的站点的工作状态的具体实施方式可以为：第一MLD根据第二MLD中是否缓存有第三数据类型对应的缓存数据，以及第二链路是否映射有除该第三数据类型以外的其他数据类型，确定多个站点中与该第二链路对应的站点的工作状态。
在一种实现方式中，第五指示信息指示第二MLD中未缓存有第三数据类型对应的缓存数据；第一MLD从第二MLD接收的第三数据类型对应的缓存数据还可以包括第六指示信息，该第六指示信息用于指示第二MLD是否缓存有至少一种第四数据类型对应的缓存数据；该第四数据类型为第一MLD所支持的数据类型中除该第三数据类型以外的任一数据类型。
在该技术方案中，通过第六指示信息，可以确定第二MLD是否缓存有至少一种第四数据类型对应的缓存数据。即通过第六指示信息可以确定第三数据类型以外的其他数据类型对应的缓存数据在第二MLD中的缓存情况，第一MLD可以获知更加详细的缓存情况，从而有利于为第一MLD中的站点确定更加合适的工作状态。
在一种实现方式中，第四数据类型的优先级高于第三数据类型的优先级。
第六方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第二多链路设备MLD确定第二MLD中是否缓存有第三数据类型对应的缓存数据；该第二MLD向第一MLD发送该第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示该第二MLD中是否缓存有第三数据类型对应的缓存数据。
在该技术方案中，根据第三数据类型对应的缓存数据中的第五指示信息，可以确定第二MLD中是否缓存有该第三数据类型对应的缓存数据。
在一种实现方式中，第五指示信息指示第二MLD中未缓存有第三数据类型对应的缓存数据；第二MLD向第一MLD发送的第三数据类型对应的缓存数据还包括第六指示信息，该第六指示信息用于指示第二MLD是否缓存有至少一种第四数据类型对应的缓存数据；该第四数据类型为第一MLD所支持的数据类型中除该第三数据类型以外的任一数据类型。
在该技术方案中，通过第六指示信息，可以指示第二MLD是否缓存有至少一种第四数据类型对应的缓存数据。即通过第六指示信息可以指示第三数据类型以外的其他数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，第四数据类型的优先级高于第三数据类型的优先级。
第七方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第一多链路设备MLD接收来自第二MLD的第七指示信息，该第七指示信息用于指示该第二MLD未缓存有第五数据类型对应的缓存数据；该第五数据类型为第一MLD所支持的数据类型中的任一数据类型；第一MLD根据该第七指示信息，确定第二MLD未缓存有该第五数据类型对应的缓存数据。
在该技术方案中，当第二MLD未缓存有第五数据类型对应的缓存数据时，第二MLD无法向第二MLD发送第五数据类型对应的缓存数据，第一MLD也无法通过第五数据类型对应的缓存数据中的“更多数据(More Data)”子字段以确定第二MLD未缓存有第五数据类型对应的缓存数据。此时，第一MLD根据来自第二MLD的第七指示信息，可以确定第二MLD未缓存有该第五数据类型对应的缓存数据。
在一种实现方式中，第一MLD具有多个站点；该方法还包括：第一MLD根据第二MLD未缓存有第五数据类型对应的缓存数据，确定多个站点中与第三链路对应的站点的工作状态，前述第五数据类型映射于该第三链路；工作状态为活跃状态或休眠状态。
在该技术方案中，根据第二MLD未缓存有第五数据类型对应的缓存数据，有利于为第三链路对应的站点确定更加合适的工作状态。
第八方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第二多链路设备MLD确定该第二MLD未缓存有第五数据类型对应的缓存数据；该第五数据类型为第一MLD所支持的数据类型中的任一数据类型；第二MLD向第一MLD发送第七指示信息，该第七指示信息用于指示该第二MLD未缓存有该第五数据类型对应的缓存数据。
在该技术方案中，当第二MLD未缓存有第五数据类型对应的缓存数据时，第二MLD无法向第二MLD发送第五数据类型对应的缓存数据，也无法通过第五数据类型对应的缓存数据中的More Data子字段以指示第二MLD未缓存有第五数据类型对应的缓存数据。此时，第二MLD通过向第一MLD发送第七指示信息，可以确定第二MLD未缓存有该第五数据类型对应的缓存数据。
第九方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第一多链路设备MLD通过第四链路从第二MLD接收第八指示信息，该第八指示信息用于指示该第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据；第一MLD根据该第八指示信息，确定第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
在该技术方案中，第一MLD根据该第八指示信息，可以确定第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据，即可以确定后续第二MLD不会通过第四链路向第一MLD发送数据。
在一种实现方式中，该第一MLD具有多个站点；该方法还包括：第一MLD根据第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据，确定多个站点中与该第四链路对应的站点的工作状态；工作状态为活跃状态或休眠状态。
在该技术方案中，根据第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据，有利于为第四链路对应的站点确定更加合适的工作状态。
第十方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第二多链路设备MLD确定第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据；第二MLD通过该第四链路向第一MLD发送第八指示信息，该第八指示信息用于指示第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
在该技术方案中，第二MLD可以通过向第一MLD发送第八指示信息，以指示第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据，即指示后续第二MLD不会通过第四链路向第一MLD发送数据。
第十一方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第一多链路设备MLD接收来自第二MLD的第九指示信息，该第九指示信息用于指示第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况；第一MLD根据该第九指示信息，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在该技术方案中，第一MLD根据该第九指示信息，可以确定不止一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，该第一MLD具有多个站点；该方法还包括：第一MLD根据至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，确定多个站点中至少一个站点的工作状态；工作状态为活跃状态或休眠状态。
在该技术方案中，根据至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，有利于为第一MLD中的站点确定更加合适的工作状态。
第十二方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第二多链路设备MLD确定第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况；第二MLD向第一MLD发送第九指示信息，该第九指示信息用于指示第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在该技术方案中，第二MLD可以通过该第九指示信息，向第一MLD指示不止一种数据类型对应的缓存数据在第二MLD中的缓存情况。
第十三方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第 一多链路设备MLD接收来自第二MLD的第十指示信息，该第十指示信息用于指示映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在该第二MLD中的缓存情况；第一MLD根据该第十指示信息，确定映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在该技术方案中，根据第十指示信息，可以确定映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。通过这种方式，可以更加详细的确定缓存数据在第二MLD中的缓存情况。
在一种实现方式中，该第一MLD具有多个站点；该方法还包括：第一MLD根据映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，确定多个站点中至少一个站点的工作状态；工作状态为活跃状态或休眠状态。
在该技术方案中，根据映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，有利于为第一MLD中的站点确定更加合适的工作状态。
第十四方面，本申请实施例提供了又一种数据缓存情况的确定方法，该方法包括：第二多链路设备MLD确定映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况；第二MLD向第一MLD发送第十指示信息，该第十指示信息用于指示映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在该技术方案中，第二MLD可以通过第十指示信息，向第一MLD指示映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。通过这种方式，可以更加详细的指示缓存数据在第二MLD中的缓存情况。
第十五方面，本申请实施例提供了一种通信装置，该通信装置具有实现上述第一方面、第三方面、第五方面、第七方面、第九方面、第十一方面或第十三方面所述的方法示例中第一MLD的部分或全部功能，比如通信装置的功能可具备本申请中的部分或全部实施例中的功能，也可以具备单独实施本申请中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括处理单元和通信单元，所述处理单元被配置为支持通信装置执行上述方法中相应的功能。所述通信单元用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储单元，所述存储单元用于与处理单元和发送单元耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，当通信装置具有实现上述第一方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
通信单元，用于接收来自第二MLD的第一指示信息；该第一指示信息用于指示该通信装置的关联标识对应的缓存数据在第二MLD中的缓存情况；
处理单元，用于根据该第一指示信息，以及第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可 以为存储器。
在一种实现方式中，当通信装置具有实现上述第一方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
收发器，用于接收来自第二MLD的第一指示信息；该第一指示信息用于指示该通信装置的关联标识对应的缓存数据在第二MLD中的缓存情况；
处理器，用于根据该第一指示信息，以及第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，当通信装置具有实现上述第三方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
通信单元，用于通过第一链路从第二MLD接收缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，其中，第二数据类型为映射于第一链路的任一数据类型；
处理单元，用于根据该第三指示信息，确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第三方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
收发器，用于通过第一链路从第二MLD接收缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，其中，第二数据类型为映射于第一链路的任一数据类型；
处理器，用于根据该第三指示信息，确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
在一种实现方式中，当通信装置具有实现上述第五方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
通信单元，用于从第二MLD接收第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示第二MLD中是否缓存有该第三数据类型对应的缓存数据；
处理单元，用于根据该第五指示信息，确定该第二MLD中是否缓存有该第三数据类型对应的缓存数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第五方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
收发器，用于从第二MLD接收第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示第二MLD中是否缓存有该第三数据类型对应的缓存数据；
处理器，用于根据该第五指示信息，确定该第二MLD中是否缓存有该第三数据类型对应的缓存数据。
在一种实现方式中，当通信装置具有实现上述第七方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
通信单元，用于接收来自第二MLD的第七指示信息，该第七指示信息用于指示该第二MLD未缓存有第五数据类型对应的缓存数据；该第五数据类型为该通信装置所支持的数据类型中的任一数据类型；
处理单元，用于根据该第七指示信息，确定第二MLD未缓存有该第五数据类型对应的缓存数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第七方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
收发器，用于接收来自第二MLD的第七指示信息，该第七指示信息用于指示该第二MLD未缓存有第五数据类型对应的缓存数据；该第五数据类型为该通信装置所支持的数据类型中的任一数据类型；
处理器，用于根据该第七指示信息，确定第二MLD未缓存有该第五数据类型对应的缓存数据。
在一种实现方式中，当通信装置具有实现上述第九方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
通信单元，用于通过第四链路从第二MLD接收第八指示信息，该第八指示信息用于指示该第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据；
处理单元，用于根据该第八指示信息，确定第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第九方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
收发器，用于通过第四链路从第二MLD接收第八指示信息，该第八指示信息用于指示该第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据；
处理器，用于根据该第八指示信息，确定第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
在一种实现方式中，当通信装置具有实现上述第十一方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
通信单元，用于接收来自第二MLD的第九指示信息，该第九指示信息用于指示通信装置所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况；
处理单元，用于根据该第九指示信息，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第十一方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
收发器，用于接收来自第二MLD的第九指示信息，该第九指示信息用于指示通信装置所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况；
处理器，用于根据该第九指示信息，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，当通信装置具有实现上述第十三方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
通信单元，用于接收来自第二MLD的第十指示信息，该第十指示信息用于指示映射于通信装置对应的至少一条链路的至少一种数据类型对应的缓存数据在该第二MLD中的缓存情况；
处理单元，用于根据该第十指示信息，确定映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第十三方面所述的方法示例中第一MLD的部分或全部功能时，所述通信装置包括：
收发器，用于接收来自第二MLD的第十指示信息，该第十指示信息用于指示映射于通信装置对应的至少一条链路的至少一种数据类型对应的缓存数据在该第二MLD中的缓存情况；
处理器，用于根据该第十指示信息，确定映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
第十六方面，本申请实施例提供了另一种通信装置，该通信装置具有实现上述第二方面、第四方面、第六方面、第八方面、第十方面、第十二方面或第十四方面所述的方法示例中第二MLD的部分或全部功能，比如通信装置的功能可具备本申请中的部分或全部实施例中的功能，也可以具备单独实施本申请中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括处理单元、存储单元和通信单元，所述处理单元被配置为支持通信装置执行上述方法中相应的功能。所述通信单元用于支持通信装置与其他设备之间的通信。所述存储单元用于与处理单元和发送单元耦合，其保存通信装置必要的计算机程序和数据。所述存储单元用于存储缓存数据。
在一种实现方式中，当通信装置具有实现上述第二方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理单元，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在存储单元中的缓存情况；根据至少一种数据类型对应的缓存数据在存储单元中的缓存情况，以及 第一MLD的关联标识与支持的数据类型之间的对应关系，确定关联标识对应的缓存数据在存储单元中的缓存情况；
通信单元，用于向第一MLD发送第一指示信息；该第一指示信息用于指示第一MLD的关联标识对应的缓存数据在存储单元中的缓存情况。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第二方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理器，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在存储器中的缓存情况；根据至少一种数据类型对应的缓存数据在存储器中的缓存情况，以及第一MLD的关联标识与支持的数据类型之间的对应关系，确定关联标识对应的缓存数据在存储器中的缓存情况；
收发器，用于向第一MLD发送第一指示信息；该第一指示信息用于指示第一MLD的关联标识对应的缓存数据在存储器中的缓存情况。
在一种实现方式中，当通信装置具有实现上述第四方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理单元，用于确定存储单元中是否缓存有至少一种第二数据类型对应的缓存数据；该第二数据类型为映射于第一链路的任一数据类型；
通信单元，用于通过该第一链路向第一MLD发送缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示该存储单元中是否缓存有至少一种第二数据类型对应的缓存数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第四方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理器，用于确定存储器中是否缓存有至少一种第二数据类型对应的缓存数据；该第二数据类型为映射于第一链路的任一数据类型；
收发器，用于通过该第一链路向第一MLD发送缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示该存储器中是否缓存有至少一种第二数据类型对应的缓存数据。
在一种实现方式中，当通信装置具有实现上述第六方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理单元，用于确定存储单元中是否缓存有第三数据类型对应的缓存数据；
通信单元，用于向第一MLD发送该第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示该存储单元中是否缓存有第三数据类型对应的缓存数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第六方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理器，用于确定存储器中是否缓存有第三数据类型对应的缓存数据；
收发器，用于向第一MLD发送该第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示该存储器中是否缓存有第三数据类型对应的缓存数据。
在一种实现方式中，当通信装置具有实现上述第八方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理单元，用于确定存储单元未缓存有第五数据类型对应的缓存数据；该第五数据类型为第一MLD所支持的数据类型中的任一数据类型；
通信单元，用于向第一MLD发送第七指示信息，该第七指示信息用于指示该存储单元未缓存有该第五数据类型对应的缓存数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第八方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理器，用于确定存储器未缓存有第五数据类型对应的缓存数据；该第五数据类型为第一MLD所支持的数据类型中的任一数据类型；
收发器，用于向第一MLD发送第七指示信息，该第七指示信息用于指示该存储器未缓存有该第五数据类型对应的缓存数据。
在一种实现方式中，当通信装置具有实现上述第十方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理单元，用于确定存储单元未缓存有映射于第四链路的任一数据类型对应的缓存数据；
通信单元，用于通过该第四链路向第一MLD发送第八指示信息，该第八指示信息用于指示存储单元未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第十方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理器，用于确定存储器未缓存有映射于第四链路的任一数据类型对应的缓存数据；
收发器，用于通过该第四链路向第一MLD发送第八指示信息，该第八指示信息用于指示存储器未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
在一种实现方式中，当通信装置具有实现上述第十二方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理单元，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在存储单元中的缓存情况；
通信单元，用于向第一MLD发送第九指示信息，该第九指示信息用于指示第一MLD 所支持的至少一种数据类型对应的缓存数据在存储单元中的缓存情况。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第十二方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理器，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在存储器中的缓存情况；
收发器，用于向第一MLD发送第九指示信息，该第九指示信息用于指示第一MLD所支持的至少一种数据类型对应的缓存数据在存储器中的缓存情况。
在一种实现方式中，当通信装置具有实现上述第十四方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理单元，用于确定映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在存储单元中的缓存情况；
通信单元，用于向第一MLD发送第十指示信息，该第十指示信息用于指示映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在存储单元中的缓存情况。
作为示例，处理单元可以为处理器，通信单元可以为收发器或通信接口，存储单元可以为存储器。
在一种实现方式中，当通信装置具有实现上述第十四方面所述的方法示例中第二MLD的部分或全部功能时，所述通信装置包括：
处理器，用于确定映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在存储器中的缓存情况；
收发器，用于向第一MLD发送第十指示信息，该第十指示信息用于指示映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在存储器中的缓存情况。
第十七方面，本发明实施例提供了一种计算机可读存储介质，用于储存为上述第一MLD所用的计算机程序，所述计算机程序运行时，所述第一MLD执行上述第一方面、第三方面、第五方面、第七方面、第九方面、第十一方面或第十三方面的方法。
第十八方面，本发明实施例提供了一种计算机可读存储介质，用于储存为上述第二MLD所用的计算机程序，所述计算机程序运行时，所述第二MLD执行上述第二方面、第四方面、第六方面、第八方面、第十方面、第十二方面或第十四方面的方法。
第十九方面，本申请还提供了一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面、第三方面、第五方面、第七方面、第九方面、第十一方面或第十三方面所述的方法。
第二十方面，本申请还提供了一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面、第四方面、第六方面、第八方面、第十方面、第十二方面或第十四方面所述的方法。
第二十一方面，本申请提供了一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持第一MLD实现第一方面、第三方面、第五方面、第七方面、第九方面、第十一 方面或第十三方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存第一MLD必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第二十二方面，本申请提供了一种芯片系统，该芯片系统包括至少一个处理器、至少一个存储器和接口，用于支持第二MLD实现第二方面、第四方面、第六方面、第八方面、第十方面、第十二方面或第十四方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。所述存储器，用于保存缓存数据，以及第二MLD必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
附图说明
图1是本申请实施例提供的一种通信系统的架构示意图；
图2是本申请实施例提供的一种数据缓存情况的确定方法的流程示意图；
图3a是本申请实施例提供的另一种数据缓存情况的确定方法的流程示意图；
图3b是本申请实施例提供的一种第一MLD-a和第二MLD-b所支持的管理帧和各个AC对应的AID的示意图；
图4a是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图；
图4b是本申请实施例提供的一种第二MLD向第一MLD发送缓存数据的场景示意图；
图5是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图；
图6a是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图；
图6b是本申请实施例提供的一种确定链路的工作状态的场景示意图；
图6c是本申请实施例提供的另一种确定链路的工作状态的场景示意图；
图6d是本申请实施例提供的又一种确定链路的工作状态的场景示意图；
图7是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图；
图8是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图；
图9a是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图；
图9b是本申请实施例提供的一种More Data Per TID Per link子字段的示意图；
图10是本申请实施例提供的一种通信装置的结构示意图；
图11是本申请实施例提供的另一种通信装置的结构示意图；
图12是本申请实施例提供的一种芯片的结构示意图；
图13是本申请实施例提供的又一种通信装置的结构示意图；
图14是本申请实施例提供的又一种通信装置的结构示意图；
图15是本申请实施例提供的另一种芯片的结构示意图。
具体实施方式
为了便于理解，首先介绍本申请涉及的术语。
1、业务标识地图(traffic indication map，TIM)字段
TIM字段可以包括于802.11信标(Beacon)帧携带的TIM元素中。AP MLD可以周期 性地向1个或多个non-AP MLD发送802.11信标帧，通过该信标帧中携带的TIM元素可以确定各个non-AP MLD包括的各个站点对应的缓存数据在该AP MLD中的缓存情况。一个站点对应的缓存数据在该AP MLD中的缓存情况可以指：该AP MLD中是否缓存有待发送给该站点的数据。
non-AP站点可以有2种工作模式，一种是非节能模式，另一种是节能模式。在非节能模式下，无论non-AP站点和AP站点之间是否需要传输数据，该non-AP站点都处于活跃状态。在节能模式下，在non-AP站点和AP站点之间需要传输数据时，该non-AP站点可以处于活跃状态；在non-AP站点和AP站点之间不需要传输数据时，该non-AP站点可以处于休眠状态，这样可以节省non-AP MLD的功耗。
处于节能模式的non-AP站点可以周期性的醒来(即处于活跃状态)接收AP MLD发送的信标帧，以确定AP MLD中是否缓存有待发送给该non-AP站点的数据。如果AP MLD未缓存有该non-AP站点对应的数据，可以将该non-AP站点转换成休眠状态；如果AP MLD缓存有该non-AP站点对应的数据，可以将该non-AP站点转换为活跃状态以接收相应的数据。
802.11信标帧可以包括TIM信标帧或传送业务标识地图(delivery traffic indication map，DTIM)信标帧。TIM信标帧和DTIM信标帧中均携带有TIM元素。TIM元素包括的字段可以可以如表1所示。
表1TIM元素包括的字段
Figure PCTCN2021080254-appb-000001
其中，元素标识符(identifier，ID)字段：用于识别该元素为TIM元素。长度字段：用于指示该TIM元素占据的字节数。DTIM计数字段用于指示距离下个DTIM信标帧到达前还有多少个TIM信标帧出现。DTIM周期字段指示相邻两DTIM信标帧的到达间隔。元素ID字段、长度字段、DTIM计数字段、DTIM周期字段和比特位图控制字段可以分别占据1字节。比特位图控制字段中的比特0可以指示AP发送DTIM信标帧时是否有下行的组播数据业务，比特1～7可以指示部分虚拟比特位图的偏移量，该偏移量以字节(即8比特)为单位。部分虚拟比特即为TIM字段，TIM字段中的每个比特位对应一个关联标识(association identifier，AID)。例如，若偏移量为0，部分虚拟比特位图可以从AID1开始。若偏移量为1，部分虚拟比特位图可以从AID9开始。
2、接入类型(access category，AC)
增强型分布式信道访问(enhanced distributed channel access，EDCA)是一种信道竞争机制，EDCA将数据报文分为4种AC，高优先级的AC占用信道的机会大于低优先级的AC，EDCA有利于高优先级的报文享有优先发送的权利和更多的带宽。按照优先级从高到低的顺序，4种AC分别为：语音(AC_VO)、视频(AC_VI)、背景(AC_BK)、尽力而为(AC_BE)。
3、业务标识符(traffic identifier，TID)
上层实体可以通过TID来区分媒体接入控制(medium access control，MAC)层中的MAC服务数据单元(MAC service data unit，MSDU)所支持的服务质量(quality of service，QoS)。 在EDCA中可以支持8种TID，该8种TID分别为：TID0～TID7。AC与TID具有对应关系，一种AC可以对应一种或多种TID，一种TID对应一种AC。
4、管理帧
管理帧可以用于管理数据包，控制网络等。管理帧可以包括但不限于：信标帧、探测请求(Probe Request)帧、探测响应(Probe Resonse)帧、独立基本服务集(Independent Basic Service Set，IBSS)通知传输指示消息(Announcement Traffic Indication Message，ATIM)帧、取消关联(Disassociation)帧、解除认证(Deauthentication)帧、关联请求(Association Request)帧、重新关联请求(Reassociation Request)帧、身份认证(Authentication)帧、Aciton帧。本申请实施例中提及的管理帧可以指上述任一种或多种管理帧。
其中，信标帧可以用于声明某个网络存在。移动式工作站可以通过Probe Request帧扫描所在区域内有哪些802.11网络。如Probe Request帧所检查的网络与之兼容，该网络用Probe Request帧响应。IBSS工作站为处于休眠状态的接收者缓存帧，在传递期间发送IBSS ATIM帧通知对方有消息待传。Disassociation帧与Deauthentication帧均可以用于结束一段认证关系。移动式工作站找到兼容网络并通过身份验证，便发送Association Request帧以试图加入网络。位于相同扩展服务区域，但在不同基本服务区域间游走的移动式工作站，再次使用分布式系统时，通过Reassociation Request帧以与网络重新关联。Aciton帧用于触发测量动作。
为了更好的理解本申请实施例公开的一种数据缓存情况的确定方法，下面首先对本申请实施例适用的通信系统进行描述。
本申请实施例提供一种应用于无线通信系统的通信方法，该无线通信系统可以为无线局域网(Wireless local area network，WLAN)或蜂窝网，该方法可以由无线通信系统中的通信设备或通信设备中的芯片或处理器实现，该通信设备可以是一种支持多条链路并行进行传输的无线通信设备，例如，称为多链路设备(Multi-link device)或多频段设备(multi-band device)。相比于仅支持单条链路传输的设备来说，多链路设备具有更高的传输效率和更高的吞吐量。
多链路设备包括一个或多个隶属的站点STA(affiliated STA)，隶属的STA是一个逻辑上的站点，可以工作在一条链路上。其中，隶属的站点可以为接入点(Access Point，AP)或非接入点站点(non-Access Point Station,non-AP STA)。为描述方便，本申请将隶属的站点为AP的多链路设备可以称为多链路AP或多链路AP设备或AP多链路设备(AP multi-link device)，隶属的站点为non-AP STA的多链路设备可以称为多链路STA或多链路STA设备或STA多链路设备(STA multi-link device)。为描述方便，“多链路设备包括隶属STA”在本申请实施例中也简要描述为“多链路设备包括STA”。
值得注意的是，多链路设备包括多个逻辑站点，每个逻辑站点工作在一条链路上，但允许多个逻辑站点工作在同一条链路上。下文提到的链路标识表征的是工作在一条链路上的一个站点，也就是说，如果一条链路上有多于1个站点，则需要多于1个链路标识表征他们。下文提到的链路有时也表示工作在该条链路上的站点。
多链路AP设备与多链路STA在数据传输时，可以采用链路标识来标识一条链路或一 条链路上的站点。在通信之前，多链路AP设备与多链路STA设备可以先协商或沟通链路标识与一条链路或一条链路上的站点的对应关系。因此在数据传输中，不需要传输大量的信令信息用来指示链路或链路上的站点，携带链路标识即可，降低了信令开销，提升了传输效率。
多链路设备可以遵循802.11系列协议实现无线通信，例如，遵循极高吞吐率(Extremely High Throughput，EHT)站点，或遵循基于802.11be或兼容支持802.11be的站点，实现与其他设备的通信，当然其他设备可以是多链路设备，也可以不是多链路设备。
示例性的，本申请实施例中的多链路设备可以是单个天线的设备，也可以是多天线的设备。例如，可以是两个以上天线的设备。本申请实施例对于多链路设备包括的天线的数目并不进行限定。在本申请的实施例中，多链路设备可以允许同一接入类型的业务在不同链路上传输，甚至允许相同的数据包在不同链路上传输；也可以不允许同一接入类型的业务在不同链路上传输，但允许不同接入类型的业务在不同的链路上传输。
多链路设备工作的可以频段包括：sub 1GHz，2.4GHz，5GHz，6GHz以及高频60GHz。
示例性的，多链路设备为具有无线通信功能的装置，该装置可以为一个整机的设备，还可以是安装在整机设备中的芯片或处理系统等，安装这些芯片或处理系统的设备可以在这些芯片或处理系统的控制下，实现本申请实施例的方法和功能。例如，本申请实施例中的多链路STA具有无线收发功能，可以为支持802.11系列协议，可以与多链路AP或其他多链路STA或单链路设备进行通信，例如，多链路STA是允许用户与AP通信进而与WLAN通信的任何用户通信设备。例如，多链路STA可以为平板电脑、桌面型、膝上型、笔记本电脑、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、手持计算机、上网本、个人数字助理(Personal Digital Assistant，PDA)、手机等可以联网的用户设备，或物联网中的物联网节点，或车联网中的车载通信装置等，多链路STA还可以为上述这些终端中的芯片和处理系统。本申请实施例中的多链路AP为多链路STA提供服务的装置，可以支持802.11系列协议。例如，多链路AP可以为通信服务器、路由器、交换机、网桥等通信实体，或，所述多链路AP可以包括各种形式的宏基站，微基站，中继站等，当然多链路AP还可以为这些各种形式的设备中的芯片和处理系统，从而实现本申请实施例的方法和功能。并且，多链路设备可以支持高速率低时延的传输，随着无线局域网应用场景的不断演进，多链路设备还可以应用于更多场景中，比如为智慧城市中的传感器节点(比如，智能水表，智能电表，智能空气检测节点)，智慧家居中的智能设备(比如智能摄像头，投影仪，显示屏，电视机，音响，电冰箱，洗衣机等)，物联网中的节点，娱乐终端(比如AR，VR等可穿戴设备)，智能办公中智能设备(比如，打印机，投影仪等)，车联网中的车联网设备，日常生活场景中的一些基础设施(比如自动售货机，商超的自助导航台，自助收银设备，自助点餐机等)。本申请实施例中对于多链路STA和多链路AP的具体形式不做特殊限制，在此仅是示例性说明。其中，802.11协议可以为支持802.11be或兼容802.11be的协议。
虽然本申请实施例主要以部署IEEE 802.11的网络为例进行说明，本领域技术人员容易理解，本申请涉及的各个方面可以扩展到采用各种标准或协议的其它网络，例如，BLUETOOTH(蓝牙)，高性能无线LAN(high performance radio LAN，HIPERLAN)(一 种与IEEE 802.1 1标准类似的无线标准，主要在欧洲使用)以及广域网(WAN)、无线局域网(wireless local area network,WLAN)、个人区域网(personal area network,PAN)或其它现在已知或以后发展起来的网络。因此，无论使用的覆盖范围和无线接入协议如何，本申请提供的各种方面可以适用于任何合适的无线网络。
以下将描述本申请实施例，本申请实施例并不限制权利要求书的保护范围和适用性。本领域技术人员可以在不脱离本申请实施例范围的情况下对本申请涉及的元件的功能和部署进行适应性更改，或酌情省略、替代或添加各种过程或组件。
请参见图1，图1为本申请实施例提供的一种通信系统的架构示意图。该通信系统可包括但不限于一个第一MLD和一个第二MLD，图1所示的设备数量和形态用于举例并不构成对本申请实施例的限定，实际应用中可以包括两个或两个以上的第一MLD，两个或两个以上的第二MLD。图1所示的通信系统以包括一个第一MLD101和一个第二MLD102为例。
其中，第二MLD102可以用于确定第一MLD101所支持的至少一种数据类型对应的缓存数据在第二MLD102中的缓存情况；并向第一MLD101发送指示信息；该指示信息可以用于指示第一MLD101所支持的至少一种数据类型对应的缓存数据在第二MLD102中的缓存情况。
第一MLD101接收到来自第二MLD102的指示信息之后，可以根据该指示信息，确定第一MLD101所支持的至少一种数据类型对应的缓存数据在第二MLD102中的缓存情况。
在本申请实施例中，第一MLD101所支持的数据类型可以包括业务类型和管理帧中的至少一种，其中，业务类型可以指AC或者TID。第一MLD101可以支持一种或多种数据类型。以第一MLD101所支持的数据类型为数据类型1为例，数据类型1对应的缓存数据在第二MLD102中的缓存情况可以指：第二MLD102中是否缓存有待发送给该第一MLD101的缓存数据，且该缓存数据的数据类型为数据类型1。在本申请实施例中，第一MLD101所支持的数据类型，可以在第一MLD101与第二MLD102建立连接的过程中确定。
不同第一MLD101所支持的数据类型可以相同，也可以不同。当图1所示的通信系统包括多个第一MLD101时，第二MLD102可以确定各个第一MLD101所支持的至少一种数据类型对应的缓存数据在第二MLD102中的缓存情况；并向各个第一MLD101发送指示信息。需要说明的是，第二MLD可以向各个第一MLD广播指示信息，此时，各个第一MLD接收到的指示信息是相同的，该指示信息可以指示各个第一MLD101所支持的至少一种数据类型对应的缓存数据在第二MLD102中的缓存情况。或者，第二MLD可以分别向各个第一MLD广播指示信息，此时，各个第一MLD接收到的指示信息是不同的，各个第一MLD接收到的指示信息用于指示该第一MLD101所支持的至少一种数据类型对应的缓存数据在第二MLD102中的缓存情况。需要说明的是，本申请实施例中提及的至少一个可以描述为一个或多个。
当图1所示的通信系统包括多个第二MLD102时，各个第二MLD102(如第二MLD-a和第二MLD-b)可以确定第一MLD101所支持的至少一种数据类型对应的缓存数据在该第二MLD102中的缓存情况，并分别向该第一MLD101发送指示信息。该第一MLD101接收 到的来自第二MLD-a的指示信息可以指示第一MLD101所支持的至少一种数据类型对应的缓存数据在第二MLD-a中的缓存情况。同理，该第一MLD101接收到的来自第二MLD-b的指示信息可以指示第一MLD101所支持的至少一种数据类型对应的缓存数据在第二MLD-b中的缓存情况。
可以理解的是，本申请实施例描述的通信系统是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
下面结合附图对本申请所提供的数据缓存情况的确定方法及其装置进行详细地介绍。
请参见图2，图2是本申请实施例提供的一种数据缓存情况的确定方法的流程示意图。该方法详细描述了第一MLD如何根据来自第二MLD的指示信息，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。其中，步骤S201～步骤S202的执行主体为第二MLD，或者为第二MLD中的芯片，步骤S203的执行主体为第一MLD，或者为第一MLD中的芯片，以下以第二MLD、第一MLD为数据缓存情况的确定方法的执行主体为例进行说明。如图2所示，该方法可以包括但不限于如下步骤：
步骤S201：第二多链路设备MLD确定第一MLD所支持的至少一种数据类型对应的缓存数据在该第二MLD中的缓存情况。
在本申请实施例中，第二MLD可以确定第一MLD所支持的至少一种数据类型对应的缓存数据是否缓存于该第二MLD中。当第一MLD支持一种数据类型时，第二MLD可以确定是否缓存有待发送至该第一MLD的缓存数据，且该缓存数据的数据类型为该第一MLD所支持的数据类型。
当第一MLD支持多种数据类型时，第二MLD可以确定第一MLD所支持的各种数据类型对应的缓存数据是否缓存于该第二MLD中。例如，当第一MLD支持3种数据类型(数据类型1、数据类型2和数据类型3)时，第二MLD可以分别确定数据类型1、数据类型2、数据类型3对应的缓存数据是否缓存于该第二MLD中。在另一种实现方式中，第二MLD可以确定数据类型1对应的缓存数据是否缓存于该第二MLD中，并确定数据类型2和数据类型3中的至少一种数据类型对应的缓存数据是否缓存于该第二MLD中。例如，在第二MLD中，当数据类型1对应的缓存数据缓存于缓存区域a，数据类型2和数据类型3对应的缓存数据缓存于缓存区域b时。若第二MLD检测到缓存区域a中存在缓存单元(bufferable unit，BU)，即表明第二MLD中缓存有数据类型1对应的缓存数据；若第二MLD检测到缓存区域a中不存在缓存单元，即表明第二MLD中未缓存有数据类型1对应的缓存数据。同理，若第二MLD检测到缓存区域b中存在缓存单元，即表明第二MLD中缓存有数据类型2和数据类型3中的至少一种数据类型对应的缓存数据；若第二MLD检测到缓存区域b中不存在缓存单元，即表明第二MLD中未缓存有数据类型2对应的缓存数据，也未缓存有数据类型3对应的缓存数据。
需要说明的是，上述数据类型1、数据类型2、数据类型3对应的缓存数据在第二MLD内所占据的缓存区域仅用于举例，并不构成对本申请实施例的限定。本申请实施例对于第 一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD内如何缓存不作限定。在一种实现方式中，第二MLD可以将第一MLD所支持的至少一种数据类型对应的缓存数据缓存于公共的缓存区域中。或者，第二MLD可以将第一MLD所支持的各种数据类型对应的缓存数据缓存于单独的缓存区域中。或者，第二MLD可以结合公共缓存加独立缓存的方式来缓存第一MLD所支持的数据类型对应的缓存数据。或者，第二MLD可以将第一MLD所支持的业务类型对应的缓存数据缓存于一缓存区域，并将管理帧对应的缓存数据缓存于另一缓存区域。第一MLD和第二MLD之间可以通过多条链路相连接。在一种实现方式中，第二MLD可以确定第一MLD所支持的至少一种数据类型对应的缓存数据会通过哪条链路传输至该第一MLD，进一步的，第二MLD可以将通过同一链路传输的缓存数据缓存于单独的缓存区域中。还需要说明的是，第二MLD可以通过站点向第一MLD发送缓存数据，第二MLD中的站点可以从一个或多个缓存区域中调度缓存数据，并发送至第一MLD。
还需要说明的是，当第二MLD与多个第一MLD具有连接关系时，第二MLD可以分别确定各个第一MLD所支持的至少一种数据类型对应的缓存数据在该第二MLD中的缓存情况。
步骤S202：第二MLD向该第一MLD发送指示信息，该指示信息用于指示该第一MLD所支持的至少一种数据类型对应的缓存数据在该第二MLD中的缓存情况。
具体的，第二MLD确定第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况之后，可以向该第一MLD发送指示信息。其中，该指示信息中的每个比特位可以对应第一MLD所支持的一种或多种数据类型，每个比特位的取值可以指示该比特位对应的数据类型的缓存数据是否缓存于第二MLD中。在本申请实施例中，指示信息还可以称为第九指示信息。
在一种实现方式中，前述指示信息可以指MAC帧中的EHT A-control字段中控制类型a占据的比特位。EHT A-control字段可以支持8种控制类型，即可以通过EHT A-control字段对应的比特位携带8种控制类型的信息。其中，8种控制类型的相关信息可以如表2所示。需要说明的是，EHT A-control字段仅为举例，例如还可以是EHT A-control或HE A-control字段所在的HT control字段，随着标准版本的演进，该字段的名称可能变更，但只要指示相应的功能，则为本申请实施例的范围。
表2 8种控制类型的相关信息
Figure PCTCN2021080254-appb-000002
Figure PCTCN2021080254-appb-000003
表2中，control ID＝7的类型(More Data Per TID)是新增的。需要说明的是，表2中control ID的数值与名称仅用于举例，并不构成对本申请实施例的限定。还需要说明的是，新增的类型为More Data Per TID，是以第一MLD支持的数据类型包括业务类型和管理帧，且业务类型为TID为例。当业务类型为AC时，表2中新增的类型可以为每AC的更多数据(More Data Per AC)。相应的，此时，More Data Per AC可以占据5个比特，其中，4个比特中的每个比特对应一种AC，另外1个比特对应管理帧。
本申请实施例以新增的类型为More Data Per TID为例进行介绍。More Data Per TID子字段可以包括9个比特，其中，8个比特与8种TID对应，该8个比特中的每个比特对应一种TID，另外1个比特对应管理帧。当More Data Per TID子字段中与TID对应的某一个比特位设置为1时，可以表示第二MLD中缓存有该TID对应的缓存数据。当该比特位设置为0时，可以表示第二MLD中未缓存有该TID对应的缓存数据。当More Data Per TID子字段中与管理帧对应的比特位设置为1时，可以表示第二MLD中缓存有管理帧的缓存数据。当该比特位设置为0时，可以表示第二MLD中未缓存有管理帧的缓存数据。
在一种实现方式中，More Data Per TID子字段中的一个比特位可以对应1个或多个TID，此时，More Data Per AC占据的比特数可以小于9。例如，More Data Per TID子字段中的某一个比特位可以对应TID1和TID2，当该比特位设置为1时，可以表示第二MLD中缓存有TID1和TID2中的至少一种TID对应的缓存数据。当该比特位设置为0时，可以表示第二MLD中既未缓存有TID1对应的缓存数据，也未缓存有TID2对应的缓存数据。
在一种实现方式中，第二MLD可以向多个第一MLD发送指示信息，该指示信息可以指示各个第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。例如，第二MLD向第一MLD-a和第一MLD-b发送指示信息时，该指示信息中的一部分比特位可以与第一MLD-a所支持的至少一种数据类型相对应，即该部分比特位的取值用于指示第一MLD-a所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。该指示信息中的另一部分比特位可以与第一MLD-b所支持的至少一种数据类型相对应，即该另一部分比特位的取值用于指示第一MLD-b所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在本申请实施例中，第二MLD与第一MLD之间通过链路传输数据，每条链路在第一MLD中的一个站点和第二MLD中的一个站点之间建立。若第一MLD或者第二MLD中的站点处于休眠状态，则与该站点对应的链路也处于休眠状态，此时，无法通过该链路传输数据，第一MLD中与该链路对应的站点也无法接收数据。在本申请实施例中，第二MLD中的站点可以调度第二MLD中的缓存数据，并将该缓存数据发送至第一MLD中的相应站 点。当第一MLD中的站点处于休眠状态时，无法接收数据。
在一种实现方式中，前述指示信息可以携带于第二MLD向第一MLD发送的缓存数据中，此时，该指示信息可以用于指示(缓存于第二MLD中)第一MLD所支持的至少一种数据类型对应的缓存数据是否发送完毕。具体的，该指示信息可以包括于MAC帧中的EHT A-control字段中。在另一种实现方式中，第二MLD可以周期性地向处于节能模式的站点所属的第二MLD发送指示信息，此时，指示信息可以指示该第二MLD中处于节能模式的站点，在该站点处于休眠状态的过程中，第一MLD是否缓存了待发送至该站点的缓存数据。其中，该指示信息可以由第一MLD中处于活跃状态的站点接收。该指示信息可以携带于控制帧、或管理帧中。
步骤S203：第一MLD根据该指示信息，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
第一MLD接收到来自第二MLD的指示信息之后，可以根据该指示信息，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
具体的，若指示信息中的某比特位的取值为第一数值(如1)，则第一MLD可以确定该比特位对应的数据类型的缓存数据缓存于第二MLD中；若该比特位的取值为第二数值(如0)，则可以确定该比特位对应的数据类型的缓存数据未缓存于第二MLD中。例如，指示信息包括2个比特位(比特位1和比特位2)，第一MLD支持3种数据类型(数据类型1、数据类型2和数据类型3)，且比特位1与数据类型1对应，比特位2与数据类型2和数据类型3对应时。若比特位1的取值为1，则第一MLD可以确定第二MLD中缓存有数据类型1对应的缓存数据；若比特位1的取值为0，则可以确定第二MLD中未缓存有数据类型1对应的缓存数据。若比特位2的取值为1，则第一MLD可以确定第二MLD中缓存有数据类型2或数据类型3中的至少一种数据类型对应的缓存数据；若比特位2的取值为0，则可以确定第二MLD中既未缓存有数据类型2对应的缓存数据，也未缓存有数据类型3对应的缓存数据。其中，第一数值为1，第二数值为0仅用于举例，并不构成对本申请实施例的限定。可选的，第一数值可以为0，第二数值可以为1。
需要说明的是，当第二MLD仅缓存有第一MLD所支持的数据类型中的部分数据类型对应的缓存数据时，指示信息中的比特位可以仅对应第一MLD所支持的数据类型中的部分数据类型。例如，当第一MLD支持3种数据类型(数据类型1、数据类型2和数据类型3)，且第二MLD中缓存有数据类型1对应的缓存数据，未缓存有数据类型2、数据类型3对应的缓存数据时，指示信息可以包括与数据类型1相对应的比特位，不包括与数据类型2和/或数据类型3相对应的比特位。在此情况下，第一MLD接收到该指示信息之后，若该指示信息中与数据类型1对应的比特位为1，则可以表示第二MLD中缓存有数据类型1对应的缓存数据；若该指示信息中与数据类型1对应的比特位为0，则可以表示第二MLD中未缓存有数据类型1对应的缓存数据。该指示信息中不包括与数据类型2和/或数据类型3对应的比特位，第一MLD可以确定第二MLD中未缓存有数据类型2对应的缓存数据，也未缓存有数据类型3对应的缓存数据。
在一种实现方式中，第一MLD可以具有多个站点；第一MLD确定所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况之后，可以根据至少一种数据类型对 应的缓存数据在第二MLD中的缓存情况，确定第一MLD具有的多个站点中至少一个站点的工作状态；工作状态可以为活跃状态或休眠状态。
具体的，第一MLD通过确定指示信息中取值为1的比特位对应的数据类型，可以确定第二MLD中缓存有该数据类型对应的缓存数据。然后，第一MLD可以根据所支持的数据类型与该第一MLD对应的链路之间的映射关系，确定具有缓存数据的数据类型所映射的链路。
在一种实现方式中，第一MLD可以将与具有缓存数据的数据类型所映射的链路对应的站点的工作状态均确定为活跃状态。例如，第一MLD支持的数据类型1对应的缓存数据缓存于第二MLD中，数据类型1映射于链路1和链路2，且链路1、链路2分别与第一MLD中的站点1、站点2对应。此时，第一MLD可以将站点1和站点2的工作状态均确定为活跃状态。在第二MLD中的站点保持活跃状态的情况下，将与具有缓存数据的数据类型所映射的链路对应的站点(第一MLD中的站点)的工作状态确定为活跃状态，可以使得具有缓存数据的数据类型所映射的链路处于活跃状态，进而，第二MLD可以通过该链路将缓存数据发送至第一MLD。
其中，第一MLD对应的链路指该第一MLD与第二MLD之间的链路。需要说明的是，第一MLD支持的数据类型1映射于链路1可以表示：数据类型1对应的缓存数据映射于链路1，即数据类型1对应的缓存数据会通过链路1传输至第一MLD。管理帧可以映射到一条或多条链路上，一种业务类型可以映射到一条或多条链路上。每条链路上可以映射有一种或多种业务类型，还可以映射有管理帧。第一MLD所支持的业务类型(或待发送至第一MLD的管理帧)与该第一MLD对应的链路之间的映射关系可以由第一MLD和第二MLD协商确定。例如，在第一MLD与第二MLD建立连接的过程中确定。当业务类型指TID时，第一MLD所支持的业务类型与该第一MLD对应的链路之间的映射关系可以称为TID-to-link mapping。当业务类型指AC时，根据TID-to-link mapping，以及第一MLD所支持的AC与TID之间的对应关系，可以确定第一MLD所支持的AC与第一MLD对应的链路之间的对应关系(即AC-to-link mapping)。
在另一种实现方式中，第一MLD确定具有缓存数据的数据类型所映射的链路之后，可以根据该第一MLD当前的电量信息，在具有缓存数据的数据类型所映射的链路中确定出需转换为活跃状态的链路，即在与具有缓存数据的数据类型所映射的链路对应的站点中，确定出需转换为活跃状态的站点。其中，电量信息可以包括但不限于剩余电量、是否处于充电模式下中的一项或多项。例如，若第二MLD中缓存有第一MLD所支持的AC_VO对应的缓存数据，AC_VO映射于链路1、链路2和链路3，且第一MLD当前的剩余电量较低，则第一MLD可以选择将链路1、链路2和链路3中的部分链路的工作状态确定为活跃状态，并将链路1、链路2和链路3中的另一部分链路的工作状态确定为休眠状态，这样可以确保数据的接收，还有利于降低功耗。
在又一种实现方式中，第一MLD可以根据该第一MLD的业务需求信息，在具有缓存数据的数据类型所映射的链路中确定出需转换为活跃状态的链路。例如，若第二MLD中缓存有第一MLD所支持的AC_VO和AC_VI对应的缓存数据，AC_VO、AC_VI分别映射于链路1、链路2，且对于第一MLD而言，AC_VO对应的缓存数据的优先级高于AC_VI 对应的缓存数据的优先级，则第一MLD可以将链路1确定为活跃状态，将链路2确定为休眠状态，这样可以确保高优先级数据的接收。又如，若第二MLD中缓存有第一MLD的管理帧，以及第一MLD所支持的AC_VO对应的缓存数据，管理帧、AC_VO分别映射于链路1、链路2，且对于第一MLD而言，管理帧对应的缓存数据的优先级高于AC_VO对应的缓存数据的优先级，则第一MLD可以将链路1确定为活跃状态，将链路2确定为休眠状态，这样可以确保高优先级数据的接收。
在又一种实现方式中，第一MLD可以根据该第一MLD当前的电量信息和业务需求信息，在具有缓存数据的数据类型所映射的链路中确定出需转换为活跃状态的链路。在上述例子中，若第一MLD当前的剩余电量较高，或第一MLD处于充电模式下，则第一MLD可以将链路1和链路2均确定为活跃状态，以及时接收数据。若第一MLD当前的剩余电量较低，和/或，第一MLD未处于充电模式下，则第一MLD可以将链路1确定为活跃状态，将链路2确定为休眠状态，以确保高优先级数据的接收。
需要说明的是，不同设备的业务需求可以相同也可以不同，上述对于第一MLD而言AC_VO对应的缓存数据的优先级高于AC_VI对应的缓存数据的优先级，仅用于举例，并不构成对本申请实施例的限定。在其他情况下或者对于其他MLD设备，AC_VO对应的缓存数据的优先级可以低于AC_VI对应的缓存数据的优先级。通过电量信息和业务需求信息中的至少一种，可以将具有缓存数据的数据类型所映射的链路中的部分链路的工作状态确定为活跃状态，并将剩余链路的工作状态确定为休眠状态。通过这种方式，有利于降低功耗。
还需要说明的是，上述管理帧对应的缓存数据的优先级高于AC_VO对应的缓存数据的优先级仅用于举例，并不构成对本申请实施例的限定。本申请实施例对于管理帧、各个业务类型对应的缓存数据的优先级不作限定。可选的，管理帧对应的缓存数据的优先级可以高于所有业务类型对应的缓存数据的优先级。或者，管理帧对应的缓存数据的优先级可以高于部分业务类型对应的缓存数据的优先级。或者，管理帧对应的缓存数据的优先级可以低于任一业务类型对应的缓存数据的优先级。在本申请实施例中，管理帧对应的缓存数据的优先级、各个业务类型对应的缓存数据的优先级可以通过标准约定，或者，可以由第一MLD和第二MLD协商确定，本申请实施例对此不作限定。
在一种实现方式中，当第二MLD未缓存有某链路所映射的任一数据类型的缓存数据时，本申请实施例对该链路的工作状态不作限定。第一MLD可以将该链路的工作状态确定为休眠状态或者活跃状态。例如，第一MLD的剩余电量较高或第一MLD处于充电模式下时，第一MLD可以确定该链路的工作状态为活跃状态。又如，第一MLD的剩余电量较低，和/或，第一MLD未处于充电模式下时，第一MLD可以确定该链路的工作状态为休眠状态。通过这种方式，有利于降低功耗。
在本申请实施例中，第一MLD确定某链路的工作状态，相当于，第一MLD将该第一MLD中与该链路对应的站点确定为相同的工作状态。在本申请实施例中，第一MLD确定工作状态为活跃状态的站点之后，可以向第二MLD发送指示消息，该指示消息可以指示处于活跃状态的站点。第二MLD接收到该指示消息之后，可以根据处于活跃状态的站点，确定处于活跃状态的链路。进一步的，第二MLD可以根据第一MLD所支持的数据类型与 该第一MLD对应的链路之间的映射关系，将缓存数据调度至相应的处于活跃状态的链路上以发送至第一MLD。
通过实施本申请实施例，可以确定第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。进而，根据缓存数据的数据类型，有利于为站点确定更加合适的工作状态，并有利于降低功耗。
请参见图3a，图3a是本申请实施例提供的一种数据缓存情况的确定方法的流程示意图。该方法详细描述了第一MLD如何根据第一指示信息，以及第一MLD的关联标识与支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。其中，步骤S301～步骤S303的执行主体为第二MLD，或者为第二MLD中的芯片，步骤S304的执行主体为第一MLD，或者为第一MLD中的芯片，以下以第二MLD、第一MLD为数据缓存情况的确定方法的执行主体为例进行说明。如图3a所示，该方法可以包括但不限于如下步骤：
步骤S301：第二MLD确定第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
需要说明的是，步骤S301的执行过程可参见图2中步骤S201的具体描述，此处不再赘述。
步骤S302：第二MLD根据第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，以及第一MLD的关联标识与所支持的数据类型之间的对应关系，确定该第一MLD的关联标识对应的缓存数据在第二MLD中的缓存情况。
具体的，第二MLD确定第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况之后，可以结合第一MLD的AID与所支持的数据类型之间的对应关系，确定该第一MLD的AID对应的缓存数据在第二MLD中的缓存情况。在本申请实施例中，第一MLD可以具有一个或多个关联标识(AID)。第一MLD的一个AID可以与该第一MLD所支持的一种或多种数据类型相对应。
表3第一MLD的AID与AC之间的对应关系
AID AC
AID0 AC_VO
AID1 AC_VI
AID2 AC_BK
AID3 AC_BE
例如，以第一MLD支持的数据类型包括业务类型和管理帧，业务类型为AC为例，当第一MLD所支持的4个AC为AC_VO、AC_VI、AC_BK、AC_BE，第二MLD缓存有第一MLD的管理帧的缓存数据，以及第一MLD所支持的AC_VO、AC_VI对应的缓存数据，第一MLD具有的5个AID为AID0～AID4，且AID4与第一MLD的管理帧对应，第一MLD的其余AID与AC之间的对应关系如表3所示时。第二MLD可以确定缓存有AID0对应的缓存数据，AID1对应的缓存数据，以及AID4对应的缓存数据。
步骤S303：第二MLD向第一MLD发送第一指示信息；该第一指示信息用于指示第 一MLD的关联标识对应的缓存数据在第二MLD中的缓存情况。
第二MLD确定该第一MLD的AID对应的缓存数据在第二MLD中的缓存情况之后，可以向该第一MLD发送第一指示信息。在图2所示实施例中，第二MLD发送给第一MLD的指示信息中的每个比特位可以对应第一MLD所支持的一种或多种数据类型，每个比特位的取值可以指示该比特位对应的数据类型的缓存数据是否缓存于第二MLD中。在本申请实施例中，第二MLD发送给第一MLD的第一指示信息中的每个比特位可以对应第一MLD的一个AID。第一指示信息中的每个比特位的取值可以指示与该比特位对应的AID，所对应的缓存数据是否缓存于第二MLD中，第一MLD进一步结合AID与所支持的数据类型之间的对应关系，可以确定所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。其中，该第一指示信息可以为信标帧中的TIM字段。
步骤S304：第一MLD根据该第一指示信息，以及该第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
具体的，第一MLD接收到来自第二MLD的第一指示信息之后，可以根据该第一指示信息，以及该第一MLD的关联标识(AID)与第一MLD所支持的数据类型之间的对应关系，确定至少一种数据类型的缓存数据在第二MLD中的缓存情况。若TIM字段中的某个比特位的取值为1，且该比特位与AID1对应，则可以表示第二MLD中缓存有AID1对应的缓存数据。若AID1与第一MLD所支持的数据类型1相对应，则可以表示第二MLD中缓存有数据类型1对应的缓存数据。若TIM字段中的某个比特位的取值为0，且该比特位与AID2对应，则可以表示第二MLD中未缓存有AID2对应的缓存数据。若该AID2与第一MLD所支持的数据类型2相对应，则可以表示第二MLD中未缓存有数据类型2对应的缓存数据。
其中，第一MLD的AID与第一MLD所支持的数据类型之间的对应关系可以由第二MLD向第一MLD发送的第二指示信息确定。第二指示信息可以用于确定第一MLD的AID与第一MLD所支持的数据类型之间的对应关系，第二指示信息可以包括于关联响应帧中。需要说明的是，本申请实施例对第二MLD发送第一指示信息和第二指示信息的先后顺序不作限定，对第一MLD接收到第一指示信息和第二指示信息的先后顺序不作限定。只要第一MLD可以根据第一指示信息和第二指示信息，确定第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况即可。优选的，第二MLD可以在发送第一指示信息之前，向第一MLD发送第二指示信息。相应的，对于第一MLD，第二指示信息的接收时刻早于第一指示信息的接收时刻。
在一种实现方式中，第一MLD接收到的第二指示信息可以指示至少一个AID，至少一个AID可以对应第一MLD支持的至少一种数据类型。例如，当数据类型包括管理帧和AC，且第一MLD支持4种AC时，第二指示信息可以包括5个AID，其中1个AID与管理帧对应，另外4个AID与4个AC对应。需要说明的是，本申请实施例对4个AC与第二指示信息中的4个AID之间的对应关系不作限定。例如，4个AC为AC_VO、AC_VI、AC_BK、AC_BE，且4个AID为AID0、AID1、AID2、AID3时，其对应关系可以如表3或表4所示。
表4 4个AID与4个AC之间的对应关系
AID AC
AID0 AC_VI
AID1 AC_VO
AID2 AC_BE
AID3 AC_BK
由表3可知，4个AID与4个AC之间的对应关系，可以按照AID的大小和AC的优先级高低一一对应。由表4可知，4个AID与4个AC之间的对应关系，也可以与AID的大小和AC的优先级高低不相关。还需要说明的是，上述表3和表4中，4个AID连续仅用于举例，并不构成对本申请实施例的限定。在其他可行的实现方式中，第二指示信息指示多个AID时，该多个AID可以连续也可以不连续，换言之，第二MLD可以从可用的AID空间中任意选取多个AID分配给第一MLD。通过第二指示信息指示第一MLD所支持的至少一种数据类型所对应的至少一个AID，可以更加更加灵活的为第一MLD分配AID。
在一种实现方式中，第一MLD可以支持多种数据类型；第二指示信息可以指示一个第一关联标识，该第一关联标识与该多种数据类型中的第一数据类型相对应。第一MLD可以根据该第一数据类型对应的第一关联标识，确定该多种数据类型中除该第一数据类型以外的其他数据类型对应的关联标识。
以数据类型包括管理帧和AC为例，若第二指示信息指示的第一关联标识为AID0，且AID0与第一MLD所支持的管理帧相对应。第一MLD可以根据所支持的管理帧和各种AC的优先级高低，确定AC_VO、AC_VI、AC_BK、AC_BE分别与AID0+1、AID0+2、AID0+3、AID0+4相对应，即第一MLD所支持的4个AC分别与第二指示信息指示的AID0之后的4个连续的AID相对应。或者，AC_VO、AC_VI、AC_BE、AC_BK可以分别与AID0+2、AID0+4、AID0+6、AID0+8相对应，即第一MLD所支持的各种数据类型所对应AID可以不连续。
需要说明的是，上述举例中第二指示信息指示的第一关联标识为AID0，以及AID0与管理帧相对应仅用于举例，并不构成对本申请实施例的限定。例如，第二指示信息指示的第一关联标识可以为AID2，且AID1与第一MLD所支持的4个AC中的AC_VI相对应。此时，第一MLD可以根据所支持的各种数据类型的优先级高低，确定管理帧、AC_VO、AC_BK、AC_BE分别与AID2+1、AID2+2、AID2+3、AID2+4相对应。或者，AC_VO与AID2-1相对应，管理帧与AID2-2相对应，AC_BK、AC_BE分别与AID2+1、AID2+2相对应。第二指示信息指示的一个AID与第一MLD所支持的数据类型中的一种数据类型相对应时，第一MLD基于该AID可以确定所支持的其他数据类型对应的AID。通过在第二指示信息中指示一个AID的方式，可以有效节省信令开销。
在一种实现方式中，当第二指示信息指示至少两个AID时，至少两个AID中的一个AID可以与管理帧对应，剩余的AID与第一MLD所支持的业务类型对应。通过第二指示信息指示管理帧对应的AID和第一MLD所支持的部分业务类型对应的AID，既能有效节省信令开销，也能提高第一MLD确定管理帧对应的AID和所支持的各个业务类型对应的AID的方式。
需要说明的是，第二MLD可以向多个第一MLD分别发送第二指示信息，以便分别为各个第一MLD分配不同的AID。换言之，不同第一MLD具有的AID不同。例如，当2个第一MLD(第一MLD-a和第二MLD-b)均支持管理帧和4种AC(AC_VO(语音)、AC_VI(视频)、AC_BE(尽力而为)、AC_BK(背景))时，第一MLD-a和第二MLD-b所支持的管理帧和各个AC对应的AID的示意图可以如图3b所示。由图3b可知，第一MLD-a的AID为：AID0～AID4，第二MLD-b的AID为AID5～AID8，即第一MLD-a的AID与第二MLD-b的AID不同。
在一种实现方式中，第二MLD为第一MLD分配的AID数量可以与该第一MLD支持的数据类型的数量相同。在第一MLD增加支持的数据类型的情况下，第二MLD再为该第一MLD新支持的数据类型分配新的AID。通过这种方式，可以避免分配不必要的AID。
在一种实现方式中，第二MLD可以为同一个第一MLD所支持的1种或多种数据类型分配一个AID。例如，当第一MLD支持的数据类型为管理帧、AC_VO、AC_VI、AC_BE、AC_BK时，第二MLD可以为管理帧、AC_VO和AC_VI分配一个AID，为AC_BE和AC_BK分配另一个AID。或者，第二MLD可以为管理帧分配一个AID、为AC_VO分配一个AID，为AC_VI、AC_BE和AC_BK分配另一个AID。或者，第二MLD可以为管理帧、AC_VO、AC_VI分别分配一个不同的AID，并为AC_BE和AC_BK分配另一个AID。通过为多种数据类型分配同一AID，可以使得为第一MLD分配的AID数量小于第一MLD支持的数据类型的数量。通过这种方式，可以有效节省AID。
当为多种数据类型分配同一AID时，若在TIM字段中，与该AID对应的比特位的取值为1，则可以表示：第二MLD中缓存有与该AID对应的部分数据类型或者全部数据类型的缓存数据。若在TIM字段中，与该AID对应的比特位的取值为0，则可以表示：第二MLD中未缓存有与该AID对应的任一数据类型的缓存数据。
在一种实现方式中，第一MLD确定所支持的至少一种数据类型的缓存数据在第二MLD中的缓存情况之后，可以根据至少一种数据类型的缓存数据在第二MLD中的缓存情况，确定第一MLD具有的多个站点中至少一个站点的工作状态。在一种实现方式中，第一MLD可以根据该第一MLD当前的电量信息或业务需求信息中的至少一项，以及至少一种数据类型的缓存数据在第二MLD中的缓存情况，确定第一MLD具有的多个站点中至少一个站点的工作状态。其执行过程可参见图2中步骤S203的具体描述，此处不再赘述。
通过实施本申请实施例，可以根据第一指示信息，以及第一MLD的关联标识与支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。进而，根据缓存数据的数据类型，有利于为站点确定更加合适的工作状态，并有利于降低功耗。
请参见图4a，图4a是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图。该方法详细描述了第二MLD如何确定是否缓存有至少一种第二数据类型对应的缓存数据，以及第一MLD如何根据来自第二MLD的第三指示信息，确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。其中，步骤S401～步骤S402的执行主体为第二MLD，或者为第二MLD中的芯片，步骤S403的执行主体为第一MLD，或者为第一 MLD中的芯片，以下以第二MLD、第一MLD为数据缓存情况的确定方法的执行主体为例进行说明。该方法可以包括但不限于如下步骤：
步骤S401：第二多链路设备MLD确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据；该第二数据类型为映射于第一链路的任一数据类型。
在本申请实施例中，一条链路上可以映射有一种或多种数据类型，一种数据类型可以映射于一条或多条链路，映射于某条链路的每种数据类型对应的缓存数据可以通过该链路传输。若第二MLD中缓存有至少一种第二数据类型对应的缓存数据，则可以表示第二MLD中的缓存数据可能通过第一链路传输至第一MLD。若第二MLD中未缓存有任一第二数据类型对应的缓存数据，则可以表示映射于第一链路的每种数据类型对应的缓存数据均发送完毕，换言之，第二MLD中的缓存数据不会通过第一链路传输至第一MLD。第二MLD通过确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，可以确定是否有缓存数据可能通过第一链路传输至第一MLD。其中，第一链路是第一MLD与第二MLD之间的某条链路。
步骤S402：第二MLD通过第一链路向第一MLD发送缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
在本申请实施例中，可以在通过第一链路传输的缓存数据中携带第三指示信息，以指示是否有缓存数据可能通过第一链路传输至第一MLD。需要说明的是，第二MLD确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据是指：除去第三指示信息所属的缓存数据以外，第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
例如，链路1上映射有数据类型a和数据类型b，当第二MLD通过链路1向第一MLD发送缓存数据时，若第二MLD中缓存有数据类型a对应的缓存数据，或缓存有数据类型b对应的缓存数据，则可以表明可能有缓存数据通过链路1传输至第一MLD。若第二MLD中未缓存有数据类型a对应的缓存数据，也未缓存有数据类型b对应的缓存数据，则可以表明不会有缓存数据通过链路1传输至第一MLD。
还需要说明的是，第二MLD通过第一链路向第一MLD发送的每个缓存数据均携带有第三指示信息，每个缓存数据中携带的第三指示信息用于指示第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
缓存数据的MAC帧结构包括帧控制(Frame Control)字段，该Frame Control字段包括More Data子字段，More Data子字段的长度为1比特。在本申请实施例中，第三指示信息可以指缓存数据中的More Data子字段。具体的，第二MLD通过第一链路向第一MLD发送缓存数据时，若第二MLD中缓存有至少一种第二数据类型对应的缓存数据，则该缓存数据中的More Data子字段的取值可以为1。若第二MLD中未缓存有任一第二数据类型对应的缓存数据，则该缓存数据中的More Data子字段的取值可以为0。需要说明的是，第三指示信息指缓存数据中的More Data子字段仅用于举例，并不构成对本申请实施例的限定。在其他可行的实施方式中，第三指示信息可以是缓存数据的MAC帧结构中的其他字段。
步骤S403、第一MLD根据第三指示信息，确定第二MLD中是否缓存有至少一种第 二数据类型对应的缓存数据。
具体的，第一MLD通过第一链路从第二MLD接收到缓存数据之后，可以根据该缓存数据中的第三指示信息，确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。当第三指示信息指缓存数据中的More Data子字段时，若该缓存数据中的More Data子字段的取值为1，第一MLD可以确定第二MLD中缓存有至少一种第二数据类型对应的缓存数据。若该缓存数据中的More Data子字段的取值为0，第一MLD可以确定第二MLD中未缓存有任一第二数据类型对应的缓存数据。例如，当第一链路上映射的数据类型包括管理帧和AC_VO时，若第一MLD通过第一链路接收到的缓存数据中的More Data子字段的取值为1，则表示后续会有管理帧对应的缓存数据和AC_VO对应的缓存数据中的至少一种缓存数据通过第一链路传输至第一MLD。若第一MLD通过第一链路接收到的缓存数据中的More Data子字段的取值为0，则表示后续不会有管理帧对应的缓存数据通过第一链路传输至第一MLD，也不会有AC_VO对应的缓存数据通过第一链路传输至第一MLD。
在一种实现方式中，第一MLD可以具有多个站点；第一MLD确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据之后，可以根据第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，确定第一MLD具有的多个站点中与该第一链路对应的站点的工作状态。
在一种实现方式中，若第二MLD中缓存有至少一种第二数据类型对应的缓存数据，即More Data子字段的取值为1，则第一MLD可以确定与第一链路对应的站点的工作状态为活跃状态；若第二MLD中未缓存有任一第二数据类型对应的缓存数据，即More Data子字段的取值为0，则第一MLD可以确定与第一链路对应的站点的工作状态为活跃状态或休眠状态。
在现有技术中，第二MLD可以包括多个缓存区域，一个缓存区域对应一条链路，不同缓存区域中缓存的缓存数据通过不同的链路传输至第一MLD。缓存数据中的More Data子字段用于指示传输该缓存数据的链路对应的缓存区域中是否缓存有缓存数据。若用于传输该缓存数据的链路(如链路1)对应的缓存区域中未缓存有缓存数据，则该缓存数据中的More Data子字段的取值为0，相应的，第一MLD可以将与链路1对应的站点的工作状态确定为休眠状态。但是，若其他链路(如链路2)上发生链路拥塞或干扰等情况，而导致第一MLD无法通过链路2接收缓存数据时，由于链路1处于休眠状态，因此无法将原本通过链路2传输的缓存数据调度至链路1进行传输。
但是在本申请实施例中，若原本通过链路2传输的缓存数据的数据类型也映射于链路1(即第一链路)，那么在该数据类型对应的缓存数据发送完毕之前，第一MLD不会将与链路1对应的站点的工作状态确定为休眠状态，即链路1不会处于休眠状态。因此，第二MLD可以将该数据类型对应的缓存数据(包括原本通过链路2传输的缓存数据)调度至链路1进行传输。通过实施本申请实施例，有利于为站点确定更加合适的工作状态，并有利于将第二MLD中的缓存数据成功发送至第一MLD。
在另一种实现方式中，第一MLD可以根据该第一MLD当前的电量信息或业务需求信息中的至少一项，以及第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，确定第一MLD具有的多个站点中与该第一链路对应的站点的工作状态。其执行过程可参 见图2中步骤S203的具体描述，此处不再赘述。
在一种实现方式中，在第三指示信息指示第二MLD中缓存有至少一种第二数据类型对应的缓存数据的情况下，第二MLD可以向第一MLD发送第四指示信息；该第四指示信息用于指示第二MLD中未缓存有任一第二数据类型对应的缓存数据。第一MLD接收到该第四指示信息之后，可以确定第二MLD中未缓存有任一第二数据类型对应的缓存数据。即第一MLD接收到该第四指示信息之后，可以确定后续不会有缓存数据通过第一链路传输。
以图4b所示的第二MLD向第一MLD发送缓存数据的场景示意图为例，第一MLD支持数据类型a和数据类型b，第一MLD和第二MLD之间的链路包括链路1和链路2，且链路1映射有数据类型a和数据类型b，链路2映射有数据类型b。图4b中的白色填充方块表示数据类型a对应的缓存数据，灰色填充方块表示数据类型b对应的缓存数据，方块中的数字用于唯一标识一个缓存数据。图4b中，链路1上传输的最后一个缓存数据为缓存数据2，链路2上传输的最后一个缓存数据为缓存数据4。由图4b可知，当第二MLD通过链路1向第一MLD发送缓存数据2时，由于第二MLD中缓存有缓存数据4，且链路1映射有缓存数据4所属的数据类型b。因此，第二MLD可以将缓存数据2中的More Data子字段的取值设置为1。
由于数据类型b映射于链路1和链路2，因此缓存数据4可以通过链路1或者链路2传输。若第二MLD后续通过链路2将缓存数据4发送至第一MLD，此时，由于映射于链路1的数据类型a和数据类型b对应的缓存数据均发送完毕，因此第二MLD无法通过第一链路向第二MLD发送缓存数据，也无法通过缓存数据中的More Data子字段以指示第二MLD中既未缓存有数据类型a对应的缓存数据也未缓存有数据类型b对应的缓存数据。即无法通过缓存数据中的More Data子字段以指示后续不会有缓存数据通过链路1传输至第一MLD。
此时，第二MLD通过向第一MLD发送第四指示信息，可以解决上述问题。第四指示信息可以指示第二MLD中未缓存有映射于链路1的任一数据类型对应的缓存数据，即第四指示信息可以指示第二MLD中既未缓存有数据类型a对应的缓存数据，也未缓存有数据类型b对应的缓存数据。
在一种实现方式中，该第四指示信息可以为QoS Null帧，该QoS Null帧为不携带有效负载(payload)的数据帧，该QoS Null帧中的More Data子字段的取值为0。第二MLD可以通过第一链路向第一MLD发送QoS Null帧。
在一种实现方式中，第一MLD接收到来自第二MLD的第四指示信息之后，可以根据第四指示信息，将第一链路对应的站点的工作状态确定为休眠状态。通过这种方式，有利于降低功耗。在另一种实现方式，第一MLD可以根据当前的电量信息或业务需求信息中的至少一项，以及第四指示信息，确定第一链路对应的站点的工作状态。例如，第一MLD接收到来自第二MLD的第四指示信息之后，若第一MLD当前的剩余电量较低，和/或，第一MLD未处于充电模式下，可以将第一链路对应的站点的工作状态确定为休眠状态。若第一MLD当前的剩余电量较高或第一MLD处于充电模式下，可以将第一链路对应的站点的工作状态确定为活跃状态。
在一种实现方式中，第二MLD通过第一链路向第一MLD发送缓存数据(如缓存数据1)时，若除去该缓存数据1以外，第二MLD中还缓存有至少一种第二数据类型对应的缓存数据，第二MLD可以将该缓存数据1中的More Data子字段的取值设置为0。第一MLD接收到缓存数据1之后，可以将传输该缓存数据1的链路1对应的站点设置为休眠状态，相应的，链路1也处于休眠状态。第二MLD在接收到第一MLD发送的用于指示链路1处于活跃状态的链路状态指示信息之后，可以通过链路1发送数据。在接收到第一MLD发送的用于指示链路1处于活跃状态的链路状态指示信息之前，第二MLD可以不通过链路1发送数据。通过这种方式，在不确定链路1处于活跃状态的情况下，可以避免第二MLD将原本通过其他链路传输的缓存数据调度至链路1进行传输，有利于避免不必要的开销。其中，用于指示链路1处于活跃状态的链路状态指示信息可以为节电轮询(power saving poll，PS-Poll)帧。PS-Poll帧可以用于指示一条链路处于活跃状态。
需要说明的是，第二MLD是在确定第一链路处于活跃状态的情况下，通过第一链路向第一MLD发送缓存数据(即步骤S402)。第一MLD可以向第二MLD发送PS-Poll帧，以指示第二MLD第一链路处于活跃状态。第一MLD可以在确定第二MLD中缓存有需要通过第一链路传输的缓存数据的情况下，将第一链路的工作状态确定为活跃状态，并向第二MLD发送用于指示第一链路处于活跃状态的PS-Poll帧。在一种实现方式中，第二MLD可以向第一MLD发送现有技术中的信标帧，该信标帧中的TIM字段用于指示第一MLD的各个站点的缓存数据在第二MLD中的缓存情况。第一MLD根据该TIM字段、链路与第一MLD的站点之间的对应关系，可以确定第二MLD中是否缓存有需要通过第一链路传输的缓存数据。
在另一种实现方式中，第二MLD可以向第一MLD发送图3a所示实施例中的第一指示信息，第一MLD可以根据该第一指示信息，以及第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。进而根据至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，以及第一MLD所支持的数据类型与链路之间的映射关系，确定第二MLD中是否缓存有需要通过第一链路传输的缓存数据。其执行过程可以参见图5所示实施例。
通过实施本申请实施例，可以根据第三指示信息，确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。进一步，根据第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，有利于为站点确定更加合适的工作状态，并有利于将第二MLD中的缓存数据成功发送至第一MLD。
请参见图5，图5是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图，其中，步骤S501～步骤S503、步骤S507、步骤S508的执行主体为第二MLD，或者为第二MLD中的芯片，步骤S504～步骤S506、步骤S509的执行主体为第一MLD，或者为第一MLD中的芯片，以下以第二MLD、第一MLD为数据缓存情况的确定方法的执行主体为例进行说明。该方法可以包括但不限于如下步骤：
步骤S501：第二MLD确定第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
步骤S502：第二MLD根据第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，以及第一MLD的关联标识与所支持的数据类型之间的对应关系，确定该第一MLD的关联标识对应的缓存数据在第二MLD中的缓存情况。
步骤S503：第二MLD向第一MLD发送第一指示信息；该第一指示信息用于指示第一MLD的关联标识对应的缓存数据在第二MLD中的缓存情况。
步骤S504：第一MLD根据该第一指示信息，以及该第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
需要说明的是，步骤S501～步骤S504的执行过程可分别参见图3a中步骤S301～步骤S304的具体描述，此处不再赘述。
步骤S505：第一MLD根据至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，以及第一MLD所支持的数据类型与第一MLD对应的链路之间的映射关系，确定与第一链路对应的站点的工作状态为活跃状态。
具体的，第一MLD根据至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，以及第一MLD所支持的数据类型与第一MLD对应的链路之间的映射关系，可以确定具有缓存数据的数据类型所映射的链路。若具有缓存数据的数据类型所映射的链路包括第一链路，则第一MLD可以确定与第一链路对应的站点的工作状态为活跃状态。
步骤S506：第一MLD向第二MLD发送链路状态指示信息，该链路状态指示信息用于指示第一链路处于活跃状态。
第一MLD确定与第一链路对应的站点的工作状态为活跃状态之后，可以确定该第一链路的工作状态为活跃状态。在该第一链路的工作状态为活跃状态的情况下，向第二MLD发送链路状态指示信息。其中，链路状态指示信息可以为PS-Poll帧。在一种实现方式中，可以通过第一链路向第二MLD发送链路状态指示信息。
步骤S507：第二MLD确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据；该第二数据类型为映射于第一链路的任一数据类型。
第二MLD接收到链路状态指示信息之后，可以根据链路状态指示信息确定第一链路处于活跃状态。在确定第一链路处于活跃状态的情况下，可以通过第一链路向第一MLD发送携带有第三指示信息的缓存数据。
步骤S508：第二MLD通过第一链路向第一MLD发送缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
步骤S509：第一MLD根据第三指示信息，确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
需要说明的是，步骤S507～步骤S509的执行过程可分别参见图4a中步骤S401～步骤S403的具体描述，此处不再赘述。
在本申请实施例，第一MLD可以根据至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，以及第一MLD所支持的数据类型与第一MLD对应的链路之间的映射关系，确定与第一链路对应的站点的工作状态为活跃状态。第二MLD可以根据来自第一MLD的 链路状态指示信息，确定第一链路处于活跃状态。并在确定第一链路处于活跃状态的情况下，通过第一链路向第一MLD发送携带有第三指示信息的缓存数据。
请参见图6a，图6a是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图。该方法详细描述了第一MLD如何根据第五指示信息，确定第二MLD中是否缓存有第三数据类型对应的缓存数据。其中，步骤S601～步骤S602的执行主体为第二MLD，或者为第二MLD中的芯片，步骤S603的执行主体为第一MLD，或者为第一MLD中的芯片，以下以第二MLD、第一MLD为数据缓存情况的确定方法的执行主体为例进行说明。该方法可以包括但不限于如下步骤：
步骤S601：第二多链路设备MLD确定第二MLD中是否缓存有第三数据类型对应的缓存数据。
在本申请实施例中，一种数据类型可以映射于一条或多条链路，第二MLD中缓存的、数据类型对应的缓存数据可以通过该数据类型所映射的任意链路传输至第一MLD。例如，当第一MLD支持数据类型a，第一MLD与第二MLD之间的链路包括链路1、链路2和链路3，且数据类型a映射于链路1、链路2和链路3时，数据类型a对应的缓存数据可以通过链路1、链路2、链路3中的一条或多条链路传输至第一MLD。
第二MLD确定第二MLD中是否缓存有第三数据类型对应的缓存数据，相当于确定第二MLD中缓存的、第三数据类型对应的缓存数据是否发送完毕。第二MLD中缓存有第三数据类型对应的缓存数据，表示第三数据类型对应的缓存数据未发送完毕。第二MLD中未缓存有第三数据类型对应的缓存数据，表示第三数据类型对应的缓存数据已发送完毕。
步骤S602：第二MLD向第一MLD发送第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示第二MLD中是否缓存有该第三数据类型对应的缓存数据。
在本申请实施例中，可以在第三数据类型对应的缓存数据中携带第五指示信息，以指示是否有第二MLD中是否缓存有该第三数据类型对应的缓存数据(即指示第三数据类型对应的缓存数据是否发送完毕)。需要说明的是，第二MLD确定第二MLD中是否缓存有该第三数据类型对应的缓存数据是指：除去第五指示信息所属的缓存数据以外，第二MLD中是否缓存有第三数据类型对应的缓存数据。还需要说明的是，第二MLD向第一MLD发送的每个缓存数据均携带有第五指示信息，每个缓存数据中携带的第五指示信息用于指示第二MLD中是否缓存有该缓存数据所属的数据类型对应的缓存数据。
在一种实现方式中，第五指示信息可以指缓存数据中的More Data子字段。具体的，第二MLD向第一MLD发送第三数据类型对应的缓存数据(如缓存数据1)时，若第二MLD中缓存有该第三数据类型对应的缓存数据，则缓存数据1中的More Data子字段的取值可以为1。若第二MLD中未缓存有该第三数据类型对应的缓存数据，则缓存数据1中的More Data子字段的取值可以为0。需要说明的是，第五指示信息指缓存数据中的More Data子字段仅用于举例，并不构成对本申请实施例的限定。在其他可行的实施方式中，第五指示信息可以是缓存数据的MAC帧结构中的其他字段。
步骤S603：第一MLD根据该第五指示信息，确定第二MLD中是否缓存有第三数据 类型对应的缓存数据。
具体的，第一MLD从第二MLD接收到第三数据类型对应的缓存数据之后，可以根据该缓存数据中的第五指示信息，确定第二MLD中是否缓存有第三数据类型对应的缓存数据。当第五指示信息指缓存数据中的More Data子字段时，若该缓存数据中的More Data子字段的取值为1，第一MLD可以确定第二MLD中缓存有第三数据类型对应的缓存数据。若该缓存数据中的More Data子字段的取值为0，第一MLD可以确定第二MLD中未缓存有第三数据类型对应的缓存数据。
在一种实现方式中，第一MLD可以具有多个站点；第一MLD确定第二MLD中是否缓存有第三数据类型对应的缓存数据之后，可以根据第二MLD中是否缓存有第三数据类型对应的缓存数据，确定第一MLD具有的多个站点中与第二链路对应的站点的工作状态。其中，第三数据类型映射于该第二链路。例如，若第二MLD中缓存有第三数据类型对应的缓存数据，即第三数据类型对应的缓存数据未发送完毕，则第一MLD可以确定与第二链路对应的站点的工作状态为活跃状态，以便未发送完毕的第三数据类型对应的缓存数据可以通过第二链路传输至第一MLD。其中，第二链路的数量可以为一条或多条。
在另一种实现方式中，第一MLD可以根据该第一MLD当前的电量信息或业务需求信息中的至少一项，以及第二MLD中是否缓存有第三数据类型对应的缓存数据，确定第一MLD具有的多个站点中与第二链路对应的站点的工作状态。其执行过程可参见图2中步骤S203的具体描述，此处不再赘述。
在又一种实现方式中，第一MLD确定第二MLD中是否缓存有第三数据类型对应的缓存数据之后，可以确定第二链路是否映射有除第三数据类型以外的其他数据类型；并根据第二MLD中是否缓存有第三数据类型对应的缓存数据，以及第二链路是否映射有除第三数据类型以外的其他数据类型，确定第一MLD具有的多个站点中与第二链路对应的站点的工作状态。具体的，若第二MLD中未缓存有第三数据类型对应的缓存数据，但是第二链路映射有除第三数据类型以外的其他数据类型，即除第三数据类型以外，映射于第二链路的其他数据类型对应的缓存数据可能通过该第二链路传输。此时，第一MLD可以确定第二链路对应的站点的工作状态为活跃状态。若第二MLD中未缓存有第三数据类型对应的缓存数据，第二链路未映射有除第三数据类型以外的其他数据类型，即后续不会有缓存数据通过第二链路传输。此时，第一MLD可以确定第二链路对应的站点的工作状态为休眠状态。通过这种方式，有利于为第一MLD中的站点确定更加合适的工作状态，并有利于降低功耗。
以图6b所示的确定链路的工作状态的场景示意图为例，第一MLD支持数据类型a和数据类型b，第一MLD和第二MLD之间的链路包括链路1、链路2和链路3，且链路1映射有数据类型a和数据类型b，链路2映射有数据类型b，链路3映射有数据类型b。图6b中的白色填充方块表示数据类型a对应的缓存数据，灰色填充方块表示数据类型b对应的缓存数据，方块中的数字用于唯一标识一个缓存数据。图6b中，链路1上传输的最后一个缓存数据为缓存数据a2，链路2上传输的最后一个缓存数据为缓存数据b4，链路3上传输的最后一个缓存数据为缓存数据b2。
由6b可知，第二MLD中缓存的数据类型a对应的最后一个缓存数据(a2)通过链路 1发送，第二MLD中缓存的数据类型b对应的最后一个缓存数据(b4)通过链路2发送。因此，缓存数据a2中的More Data子字段的取值为0，表示第二MLD在未发送缓存数据a2之前，第二MLD中缓存有数据类型a对应的缓存数据，第二MLD在发送缓存数据a2之后，第二MLD中未缓存有数据类型a对应的缓存数据。缓存数据b4中的More Data子字段的取值为0，表示第二MLD在未发送缓存数据b4之前，第二MLD中缓存有数据类型b对应的缓存数据，第二MLD在发送缓存数据b4之后，第二MLD中未缓存有数据类型b对应的缓存数据。
由于链路2和链路3上仅映射有数据类型b，即链路2和链路3仅用于传输数据类型b对应的缓存数据。因此，第一MLD在接收到b4之后，可以将链路2对应的站点和链路3对应的站点的工作状态均确定为休眠状态(即将链路2、链路3确定为休眠状态)，这样有利于降低功耗。进一步的，第一MLD在接收到a2之后，由于链路1映射的数据类型a对应的最后一个缓存数据(即a2)和数据类型b对应的最后一个缓存数据(即b4)均发送至第一MLD，因此第一MLD可以将链路1对应的站点的工作状态确定为休眠状态(即将链路1确定为休眠状态)。
若缓存数据中的More Data子字段用于指示第二MLD中是否缓存有待发送至第一MLD的缓存数据，则在图6b中，只有在第一MLD接收到第二MLD发送的最后一个缓存单元(即a2)之后，链路1、链路2和链路3才能切换至休眠状态。换言之，在第二MLD中尚缓存有待发送至第一MLD的缓存数据的情况下，链路1、链路2和链路3中的任一链路均不能切换至休眠状态。因此，相较于缓存数据中的More Data子字段用于指示第二MLD中是否缓存有待发送至第一MLD的缓存数据，通过实施本申请实施例，可以在第二MLD中尚缓存有待发送至第一MLD的缓存数据的情况下，使第一MLD和第二MLD之间的部分链路处于休眠状态。相应的，第一MLD中与处于休眠状态的链路对应的站点也处于休眠状态，通过这种方式，有利于降低功耗。
通过缓存数据1中的第五指示信息，第一MLD可以获知第二MLD是否缓存有第三数据类型对应的缓存数据。但是第一MLD无法获知其他数据类型在第二MLD中的缓存情况。在一种实现方式中，第一MLD从第二MLD接收的第三数据类型对应的缓存数据还可以包括第六指示信息，该第六指示信息可以用于指示第二MLD是否缓存有至少一种第四数据类型对应的缓存数据；该第四数据类型为第一MLD所支持的数据类型中除第三数据类型以外的任一数据类型。在第五指示信息指示第二MLD中未缓存有第三数据类型对应的缓存数据的情况下，即在第三数据类型对应的缓存数据发送完毕的情况下，第六指示信息可以指示第二MLD中是否缓存有待发送至第一MLD的缓存数据。
在一种实现方式中，第三数据类型对应的缓存数据中的第五指示信息指示第二MLD中未缓存有第三数据类型对应的缓存数据的情况下，第三数据类型对应的缓存数据还可以包括第六指示信息。第三数据类型对应的缓存数据中的第五指示信息指示第二MLD中缓存有第三数据类型对应的缓存数据的情况下，第三数据类型对应的缓存数据可以不包括第六指示信息。
在一种实现方式中，第六指示信息可以指缓存数据中的“更多帧片(More Fragment)”子字段。具体的，第二MLD向第一MLD发送第三数据类型对应的缓存数据(如缓存数据 1)，且该缓存数据1中的More Data子字段的取值为0(即第三数据类型对应的缓存数据发送完毕)时，若第二MLD缓存有至少一种第四数据类型对应的缓存数据，则缓存数据1中的More Fragment子字段的取值可以为1。若第二MLD未缓存有任一第四数据类型对应的缓存数据，则缓存数据1中的More Fragment子字段的取值可以为0。需要说明的是，第六指示信息指缓存数据中的More Fragment子字段仅用于举例，并不构成对本申请实施例的限定。在其他可行的实施方式中，第六指示信息可以是缓存数据的MAC帧结构中的其他字段。当第一MLD接收到缓存数据1，且缓存数据1中的More Data子字段和More Fragment子字段的取值均为0时，可以表示第二MLD中未缓存有待发送至第一MLD的缓存数据。此时，第一MLD可以将与第二MLD之间的所有链路均转为休眠状态，以降低功耗。例如，当第一MLD支持的数据类型包括管理帧和AC_VO时，若第一MLD接收到的AC_VO对应的缓存数据中的More Data子字段的取值为0，且More Fragment子字段的取值为0，则表示AC_VO对应的缓存数据、管理帧对应的缓存数据均已发送完毕。
在一种实现方式中，前述第四数据类型的优先级可以高于第三数据类型的优先级，此时，第六指示信息用于指示第二MLD是否缓存有比第三数据类型的优先级高的数据类型对应的缓存数据。当第一MLD支持的数据类型中，只有一种数据类型(如数据类型1)的优先级高于第三数据类型时，通过第六指示信息可以间接指示第二MLD是否缓存有该数据类型1对应的缓存数据。当第一MLD支持的数据类型中，有至少两种数据类型的优先级高于第三数据类型时，若第六指示信息指示第二MLD未缓存有比第三数据类型的优先级高的数据类型对应的缓存数据，则可以表示第二MLD未缓存有前述至少两种数据类型对应的缓存数据。可见，通过第六指示信息，第二MLD可以向第一MLD指示更加详细的缓存情况，从而有利于为第一MLD中的站点确定更加合适的工作状态，并有利于降低功耗。
在一种实现方式中，第二MLD可以确定第二MLD未缓存有第五数据类型对应的缓存数据，第五数据类型为第一MLD所支持的数据类型中的任一数据类型；并向第一MLD发送第七指示信息，该第七指示信息用于指示第二MLD未缓存有第五数据类型对应的缓存数据。第一MLD接收到第七指示信息之后，可以根据该第七指示信息，确定第二MLD未缓存有第五数据类型对应的缓存数据。
当第二MLD未缓存有第一MLD所支持的某种或某几种数据类型(如数据类型c)对应的缓存数据时，第二MLD无法向第二MLD发送数据类型c对应的缓存数据，也无法通过数据类型c对应的缓存数据中的More Data子字段以指示第二MLD未缓存有数据类型c对应的缓存数据。也就是说，第一MLD无法获知第二MLD未缓存有数据类型c对应的缓存数据。这样会导致第一MLD无法确定是否能将数据类型c所映射的链路对应的站点切换为休眠状态。此时，若第一MLD接收到的第七指示信息可以指示第二MLD未缓存有数据类型c对应的缓存数据，可以解决上述问题。
以图6c所示的确定链路的工作状态的场景示意图为例，相较于图6b，图6c中的第一MLD增加了支持的数据类型c，并且数据类型c映射于链路3。由图6c可知，第二MLD中缓存的数据类型b对应的最后一个缓存数据为b4。由于链路2上仅映射有数据类型b，链路3除了映射有数据类型b以外，还映射有数据类型c。因此，第一MLD在接收到b4 之后，可以将链路2对应的站点的工作状态确定为休眠状态，而无法确定是否能将链路3对应的站点的工作状态确定为休眠状态。在一种实现方式中，若第一MLD在接收到b4之后，接收到了用于指示第二MLD未缓存有数据类型c对应的缓存数据的第七指示信息，则第一MLD在接收到该第七指示信息之后，可以将链路3对应的站点的工作状态确定为休眠状态。需要说明的是，图6c中，第二MLD在b4之后发送第七指示信息仅用于举例，并不构成对本申请的限定。第二MLD还可以在b4之前发送第七指示信息，或者同时发送b4和第七指示信息。
在一种实现方式中，该第七指示信息可以为QoS Null帧，该QoS Null帧为不携带有效负载(payload)的数据帧，该QoS Null帧中的More Data子字段的取值为0。在本申请实施例中，可以通过该QoS Null帧中的数据类型指示字段以确定该QoS Null帧所指示的第五数据类型。例如，若该QoS Null帧中的数据类型指示字段指示的TID包括于TID8～TID15，则可以确定该QoS Null帧所指示的第五数据类型为管理帧。若该QoS Null帧中的数据类型指示字段指示的TID为TID1，则可以确定该QoS Null帧所指示的第五数据类型为TID1。需要说明的是，图6c中，第二MLD通过链路3向第一MLD发送QoS Null帧仅用于举例，并不构成对本申请的限定。第二MLD可以通过第一MLD与第二MLD之间的任一链路，向第一MLD发送QoS Null帧。
在一种实现方式中，第二MLD确定第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据，并通过该第四链路向第一MLD发送第八指示信息，该第八指示信息用于指示第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据。第一MLD接收到第八指示信息之后，可以根据第八指示信息，确定第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据。其执行过程可参见图8所示实施例中的具体描述，在此不赘述。
以图6d所示的确定链路的工作状态的场景示意图为例，相较于图6b，图6d中的第一MLD增加了支持的数据类型c和d，并且数据类型c和d均映射于链路3。由图6d可知，第二MLD中缓存的数据类型b对应的最后一个缓存数据为b4。由于链路2上仅映射有数据类型b，链路3除了映射有数据类型b以外，还映射有数据类型c和d。因此，第一MLD在接收到b4之后，可以将链路2对应的站点的工作状态确定为休眠状态，而无法确定是否能将链路3对应的站点的工作状态确定为休眠状态。在一种实现方式中，若第一MLD在接收到b4之后，通过链路3接收到了用于指示第二MLD未缓存有映射于链路3(即第四链路)的任一数据类型对应的缓存数据的第八指示信息，则第一MLD在接收到该第八指示信息之后，可以将链路3对应的站点的工作状态确定为休眠状态。
需要说明的是，第二MLD向第一MLD发送第三数据类型对应的缓存数据时，该缓存数据可以通过第三数据类型所映射的链路中的任一链路发送。第二MLD需要在确定第三数据类型所映射的链路中的至少一条链路处于活跃状态的情况下，通过映射有第三数据类型且处于活跃状态的链路(如链路1)向第一MLD发送第三数据类型对应的缓存数据(即步骤S602)。第一MLD可以向第二MLD发送PS-Poll帧，以指示第二MLD链路1处于活跃状态。第一MLD可以在确定第二MLD中缓存有映射于链路1的第三数据类型对应的缓存数据的情况下，将链路1的工作状态确定为活跃状态，并向第二MLD发送用于指示 链路1处于活跃状态的PS-Poll帧。在一种实现方式中，第二MLD可以向第一MLD发送图3a所示实施例中的第一指示信息，第一MLD可以根据该第一指示信息，以及第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系，确定第二MLD中缓存有映射于链路1的第三数据类型对应的缓存数据。
通过实施本申请实施例，可以根据第三数据类型对应的缓存数据中的第五指示信息，确定第二MLD中是否缓存有该第三数据类型对应的缓存数据。进一步，根据第二MLD中是否缓存有该第三数据类型对应的缓存数据，有利于为第一MLD中的站点确定更加合适的工作状态，并有利于降低功耗。
请参见图7，图7是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图。其中，步骤S701～步骤S702的执行主体为第二MLD，或者为第二MLD中的芯片，步骤S703的执行主体为第一MLD，或者为第一MLD中的芯片，以下以第二MLD、第一MLD为数据缓存情况的确定方法的执行主体为例进行说明。该方法可以包括但不限于如下步骤：
步骤S701：第二MLD确定第二MLD未缓存有第五数据类型对应的缓存数据，第五数据类型为第一MLD所支持的数据类型中的任一数据类型。
步骤S702：第二MLD向第一MLD发送第七指示信息，该第七指示信息用于指示第二MLD未缓存有第五数据类型对应的缓存数据。
步骤S703：第一MLD根据该第七指示信息，确定第二MLD未缓存有第五数据类型对应的缓存数据。
需要说明的是，步骤S701～步骤S703的执行过程可参见图6a中步骤S603的具体描述，此处不再赘述。
在一种实现方式中，第一MLD可以具有多个站点；第一MLD确定第二MLD未缓存有第五数据类型对应的缓存数据之后，可以根据第二MLD未缓存有第五数据类型对应的缓存数据，确定第一MLD具有的多个站点中与第三链路对应的站点的工作状态，第五数据类型映射于该第三链路。例如，根据第二MLD未缓存有第五数据类型对应的缓存数据，第一MLD可以将第三链路对应的站点的工作状态确定为休眠状态。
在一种实现方式中，第一MLD可以根据相关信息中的一项或多项，以及第二MLD未缓存有第五数据类型对应的缓存数据，确定第一MLD具有的多个站点中与第三链路对应的站点的工作状态。相关信息可以包括但不限于：第一MLD当前的电量信息，第一MLD的业务需求信息，第三链路是否映射有除第五数据类型以外的其他数据类型，第五数据类型的优先级、除第五数据类型以外映射于第三链路的其他数据类型的优先级(在第三链路映射有除第五数据类型以外的其他数据类型的情况下)。
通过实施本申请实施例，可以根据第七指示信息，确定第二MLD未缓存有第五数据类型对应的缓存数据。
请参见图8，图8是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图。其中，步骤S801～步骤S802的执行主体为第二MLD，或者为第二MLD中的芯片，步 骤S803的执行主体为第一MLD，或者为第一MLD中的芯片，以下以第二MLD、第一MLD为数据缓存情况的确定方法的执行主体为例进行说明。该方法可以包括但不限于如下步骤：
步骤S801：第二MLD确定第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据。
第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据，可以表示后续第二MLD不会通过第四链路向第一MLD发送数据。例如，第四链路为链路1，链路1映射有数据类型a和数据类型b时，若第二MLD即未缓存有数据类型a对应的缓存数据，也未缓存有数据类型b对应的缓存数据，则可以确定第二MLD未缓存有映射于链路1(即第四链路)的任一数据类型对应的缓存数据。
步骤S802：第二MLD通过该第四链路向第一MLD发送第八指示信息，该第八指示信息用于指示第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
在本申请实施例中，该第八指示信息可以为QoS Null帧，该QoS Null帧为不携带有效负载(payload)的数据帧，该QoS Null帧中的More Data子字段的取值为0。QoS Null帧通过链路1传输至第一MLD时，可以指示第二MLD未缓存有映射于(用于传输该QoS Null帧的)链路1的任一数据类型对应的缓存数据。
步骤S803：第一MLD根据第八指示信息，确定第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据。
具体的第一MLD通过第四链路从第二MLD接收第八指示信息之后，可以根据第八指示信息，确定第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据。
在一种实现方式中，第一MLD可以具有多个站点；第一MLD确定第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据之后，可以根据第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据，确定第一MLD具有的多个站点中与第四链路对应的站点的工作状态。例如，根据第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据，第一MLD可以将第四链路对应的站点的工作状态确定为休眠状态。
在一种实现方式中，第一MLD可以根据第一MLD当前的电量信息或业务需求信息中的一项或多项，以及第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据，确定与第四链路对应的站点的工作状态。
通过实施本申请实施例，可以根据第八指示信息，确定第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据。
请参见图9a，图9a是本申请实施例提供的又一种数据缓存情况的确定方法的流程示意图。该方法详细描述了第一MLD如何根据第十指示信息，确定映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。其中，步骤S901～步骤S902的执行主体为第二MLD，或者为第二MLD中的芯片，步骤S903的执行主体为第一MLD，或者为第一MLD中的芯片，以下以第二MLD、第一MLD为数据缓存情况的确定方法的执行主体为例进行说明。该方法可以包括但不限于如下步骤：
步骤S901：第二MLD确定映射于第一MLD对应的至少一条链路的至少一种数据类 型对应的缓存数据在第二MLD中的缓存情况。
在本申请实施例中，第二MLD可以包括多个缓存区域，每个缓存区域可以用于缓存(第二MLD与第一MLD之间的)一条或多条链路对应的缓存数据。若缓存区域r用于缓存链路1对应的缓存数据，可以表示缓存区域r中的缓存数据会通过链路1传输至第一MLD。若缓存区域r用于缓存链路1和链路2对应的缓存数据，可以表示缓存区域r中的缓存数据可以通过链路1和链路2中的至少一条链路传输至第一MLD。因此，第二MLD通过检测第二MLD中的各个缓存区域是否存在缓存数据，即可确定各个缓存区域对应的链路在第二MLD中是否存在缓存数据。一条链路上可以映射有一种或多种数据类型，进一步的，第二MLD可以确定与各缓存区域对应的链路所映射的数据类型在该缓存区域中的缓存情况。
以数据类型为TID为例，当一个缓存区域用于缓存一条链路对应的缓存数据，且第一MLD支持8种TID时，第二MLD可以确定每种TID在每个缓存区域中的缓存情况。
步骤S902：第二MLD向第一MLD发送第十指示信息，该第十指示信息用于指示映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
其中，第十指示信息可以指MAC帧中的EHT A-control字段中控制类型b占据的比特位。关于EHT A-control字段的描述可参见图2所示实施例，在此不赘述。控制类型b是新增的一种控制类型。
当数据类型包括管理帧和TID时，控制类型b可以称为“每条链路每TID的更多数据(More Data Per TID Per link)”。“More Data Per TID Per link”占据的比特数可以为：9*L。其中，L为第一MLD与MLD之间的链路数量。此时，“More Data Per TID Per link”子字段可以包括L个“每条链路(per link)结构”，一个“per link结构”可以对应一条链路，每个per link结构可以包含9个比特位，per link结构中的一个比特位对应一种数据类型。具体的，其中一个比特位可以对应管理帧，另外8个比特中的每个比特位对应链路上的一种TID。当链路1对应的per link结构中的某一个比特位的取值为1时，可以表示第二MLD中缓存有与该比特位对应的数据类型(如管理帧或TID)的缓存数据，且该缓存数据会通过链路1发送至第一MLD。当链路1对应的per link结构中的某一个比特位的取值为0时，可以表示第二MLD中未缓存有会通过链路1发送、且与该比特位对应的数据类型(如管理帧或TID)的缓存数据。
步骤S903：第一MLD根据第十指示信息，确定映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，第十指示信息可以指More Data Per TID Per link子字段占据的比特位。在一种实现方式中，当第一MLD为各条链路分别分配不同的缓存区域，且per link结构中的一个比特位对应一种数据类型时。第一MLD接收来自第二MLD的第十指示信息之后，根据第十指示信息，可以确定映射于各条链路的各种数据类型对应的缓存数据在第二MLD中的缓存情况。例如，第一MLD与第二MLD之间的链路包括链路1和链路2时，More Data Per TID Per link子字段的示意图可以如图9b所示。如图9b所示，More Data Per TID Per link子字段包括两个per link结构(链路1和链路2)，图中小方块表示一个比特位。 其中，链路1对应的per link结构中的每个比特位对应一种数据类型，不同比特位对应不同的数据类型。图9b中，链路1(或链路2)对应的per link结构中的9个比特位分别对应T1D0～TID7、管理帧。链路1对应的per link结构中前4个比特位的取值为1，后4个比特位的取值为0，可以表示第二MLD中与链路1对应的缓存区域中缓存有TID0～TID3对应的缓存数据，而未缓存有TID4～TID7、管理帧对应的缓存数据。链路2对应的per link结构中第1个和最后1个比特位的取值为1，其余比特位的取值为0，可以表示第二MLD中与链路2对应的缓存区域中缓存有TID0、管理帧对应的缓存数据，而未缓存有TID1～TID7对应的缓存数据。
需要说明的是，一个per link结构中包括9个比特位仅用于举例，在其他可行的实现方式中，一个per link结构可以包括一个或多个比特位。例如，per link结构包括的比特位数量可以与该per link结构对应的链路映射的数据类型数量相同。当数据类型为AC时，per link结构包括的比特位数量可以与该per link结构对应的链路映射的TID，所对应的AC数量相同。
还需要说明的是，per link结构中的1个比特位对应一种数据类型(管理帧、TID或AC)仅用于举例，per link结构中的1个比特位可以对应一种或多种数据类型(管理帧、TID或AC)。
在一种实现方式中，当第一MLD为各条链路分别分配不同的缓存区域，且per link结构中的比特位可以对应至少两种数据类型时。第一MLD接收来自第二MLD的第十指示信息之后，根据第十指示信息，可以确定映射于各条链路的至少两种数据类型对应的缓存数据在第二MLD中的缓存情况。例如，当链路1对应的per link结构中的第一比特位对应TID1和TID2，且第一比特位的取值为1，可以表示第二MLD中与链路1对应的缓存区域中缓存有TID1和TID2中的至少一种TID对应的缓存数据。第一比特位的取值为0，可以表示第二MLD中与链路1对应的缓存区域中既未缓存有TID1对应的缓存数据，也未缓存有TID2对应的缓存数据。
在一种实现方式中，当第一MLD可以为至少两条链路分配同一缓存区域，且per link结构中的一个比特位对应一种数据类型时。第一MLD接收来自第二MLD的第十指示信息之后，根据第十指示信息，可以确定映射于至少两条链路的各种数据类型对应的缓存数据在第二MLD中的缓存情况。例如，当第二MLD中的缓存区域r与链路1和链路2，且与链路1和链路2对应的per link结构中的第一个比特位与TID1对应时。若第一比特位的取值为1，可以表示缓存区域r中缓存有TID1对应的缓存数据，该缓存数据可能通过链路1和/链路2发送至第一MLD。若第一比特位的取值为0，可以表示缓存区域r中未缓存有TID1对应的缓存数据，链路1、链路2均不会传输TID1对应的缓存数据。
在一种实现方式中，当第一MLD可以为至少两条链路分配同一缓存区域，且per link结构中的比特位可以对应至少两种数据类型时。第一MLD接收来自第二MLD的第十指示信息之后，根据第十指示信息，可以确定映射于至少两条链路的至少两种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，第一MLD可以具有多个站点；第一MLD可以根据映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，确定第一MLD具 有的多个站点中至少一个站点的工作状态。具体的，第一MLD可以根据映射于各条链路的各种数据类型对应的缓存数据在第二MLD中的缓存情况，确定第一MLD具有的各个站点的工作状态。例如，若第二MLD中与链路1对应的缓存区域中缓存有TID0～TID3对应的缓存数据，第二MLD中与链路2对应的缓存区域中缓存有TID1、TID7对应的缓存数据，即第二MLD缓存有与链路1对应的缓存数据，也缓存有与链路2对应的缓存数据时，第一MLD可以确定链路1和链路2的工作状态为活跃状态。这样可以通过第一链路接收到前述TID0～TID3对应的缓存数据，通过链路2接收到前述TID1、TID7对应的缓存数据。
在一种实现方式中，第一MLD可以根据第一MLD当前的电量信息或业务需求信息中的一项或多项，以及映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，确定第一MLD具有的多个站点中至少一个站点的工作状态。
在本申请实施例中，根据第十指示信息，可以确定映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。通过这种方式，可以更加详细的确定缓存数据在第二MLD中的缓存情况，从而有利于为第一MLD中的站点确定更加合适的工作状态。
上述本申请提供的实施例中，分别从第一MLD、第二MLD的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，第一MLD、第二MLD可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
请参见图10，为本申请实施例提供的一种通信装置100的结构示意图。图10所示的通信装置100可包括通信单元1001和处理单元1002。通信单元1001可包括发送单元和/或接收单元，发送单元用于实现发送功能，接收单元用于实现接收功能，通信单元1001可以实现发送功能和/或接收功能。通信单元也可以描述为收发单元。
通信装置100可以是第一MLD，也可以是第一MLD中的装置，还可以是能够与第一MLD匹配使用的装置。通信装置100为第一MLD时，可以为前述图2～图9a所示实施例中的第一MLD。
通信装置100为图3a或图5所示实施例中的第一MLD：
通信单元1001，用于接收来自第二MLD的第一指示信息；该第一指示信息用于指示该通信装置100的关联标识对应的缓存数据在第二MLD中的缓存情况；
处理单元1002，用于根据该第一指示信息，以及第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，通信装置100具有多个站点；该通信单元1001还可以用于根据至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，确定所述多个站点中至少一个站点的工作状态；工作状态为活跃状态或休眠状态。
在一种实现方式中，通信单元1001还用于接收来自第二MLD的第二指示信息，第二指示信息用于确定关联标识与数据类型之间的对应关系。
在一种实现方式中，第二指示信息指示至少一个关联标识，至少一个关联标识对应至少一种数据类型。
在一种实现方式中，通信装置100可以支持多种数据类型；第二指示信息指示一个第一关联标识，第一关联标识与多种数据类型中的第一数据类型相对应；处理单元1002，还用于根据第一数据类型对应的第一关联标识，确定多种数据类型中除第一数据类型以外的其他数据类型对应的关联标识。
通信装置100为图4a或图5所示实施例中的第一MLD：
通信单元1001，用于通过第一链路从第二MLD接收缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，其中，第二数据类型为映射于第一链路的任一数据类型；
处理单元1002，用于根据该第三指示信息，确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
在一种实现方式中，通信装置100具有多个站点；处理单元1002，还用于根据第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，确定多个站点中与第一链路对应的站点的工作状态；工作状态为活跃状态或休眠状态。
在一种实现方式中，处理单元1002用于根据第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，确定多个站点中与第一链路对应的站点的工作状态时，具体用于：若第二MLD中缓存有至少一种第二数据类型对应的缓存数据，则确定多个站点中与第一链路对应的站点的工作状态为活跃状态；若第二MLD中未缓存有任一第二数据类型对应的缓存数据，则确定多个站点中与第一链路对应的站点的工作状态为活跃状态或休眠状态。
在一种实现方式中，第三指示信息指示第二MLD中缓存有至少一种第二数据类型对应的缓存数据；通信单元1001，还用于接收来自第二MLD的第四指示信息；第四指示信息用于指示第二MLD中未缓存有任一第二数据类型对应的缓存数据。
通信装置100为图6a所示实施例中的第一MLD：
通信单元1001，用于从第二MLD接收第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示第二MLD中是否缓存有该第三数据类型对应的缓存数据；
处理单元1002，用于根据该第五指示信息，确定该第二MLD中是否缓存有该第三数据类型对应的缓存数据。
在一种实现方式中，通信装置100具有多个站点；处理单元1002，还可以用于根据第二MLD中是否缓存有第三数据类型对应的缓存数据，确定多个站点中与第二链路对应的站点的工作状态，第三数据类型映射于第二链路；工作状态为活跃状态或休眠状态。
在一种实现方式中，处理单元1002，还可以用于确定第二链路是否映射有除第三数据类型以外的其他数据类型；
处理单元1002用于根据第二MLD中是否缓存有第三数据类型对应的缓存数据，确定多个站点中与第二链路对应的站点的工作状态时，具体用于：根据第二MLD中是否缓存有第三数据类型对应的缓存数据，以及第二链路是否映射有除第三数据类型以外的其他数据类型，确定多个站点中与第二链路对应的站点的工作状态。
在一种实现方式中，第五指示信息指示第二MLD中未缓存有第三数据类型对应的缓存数据；通信单元1001从第二MLD接收的第三数据类型对应的缓存数据还包括第六指示信息，第六指示信息用于指示第二MLD是否缓存有至少一种第四数据类型对应的缓存数据；第四数据类型为通信装置100所支持的数据类型中除第三数据类型以外的任一数据类型。
在一种实现方式中，第四数据类型的优先级可以高于第三数据类型的优先级。
通信装置100为图7所示实施例中的第一MLD：
通信单元1001，用于接收来自第二MLD的第七指示信息，该第七指示信息用于指示该第二MLD未缓存有第五数据类型对应的缓存数据；该第五数据类型为该通信装置所支持的数据类型中的任一数据类型；
处理单元1002，用于根据该第七指示信息，确定第二MLD未缓存有该第五数据类型对应的缓存数据。
在一种实现方式中，通信装置100具有多个站点；处理单元1002，还用于根据第二MLD未缓存有第五数据类型对应的缓存数据，确定多个站点中与第三链路对应的站点的工作状态，第五数据类型映射于该第三链路；该工作状态为活跃状态或休眠状态。
通信装置100为图8所示实施例中的第一MLD：
通信单元1001，用于通过第四链路从第二MLD接收第八指示信息，该第八指示信息用于指示该第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据；
处理单元1002，用于根据该第八指示信息，确定第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
在一种实现方式中，通信装置100具有多个站点；处理单元1002，还用于根据第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据，确定多个站点中与第四链路对应的站点的工作状态；工作状态为活跃状态或休眠状态。
100具有多个站点；处理单元1002，还用于根据至少一种数据类型对应
通信装置100为图2所示实施例中的第一MLD：
通信单元1001，用于接收来自第二MLD的第九指示信息，该第九指示信息用于指示通信装置所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况；
处理单元1002，用于根据该第九指示信息，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，通信装置100具有多个站点；处理单元1002，还用于根据通信装置的缓存数据在第二MLD中的缓存情况，确定多个站点中至少一个站点的工作状态；工作状态为活跃状态或休眠状态。
通信装置100为图9a所示实施例中的第一MLD：
通信单元1001，用于接收来自第二MLD的第十指示信息，该第十指示信息用于指示映射于通信装置对应的至少一条链路的至少一种数据类型对应的缓存数据在该第二MLD中的缓存情况；
处理单元1002，用于根据该第十指示信息，确定映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，通信装置100具有多个站点；处理单元1002，还用于根据映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，确定多个站点中至少一个站点的工作状态；工作状态为活跃状态或休眠状态。
请参见图11，图11是本申请实施例提供的另一种通信装置110的结构示意图。通信装置110可以是第一MLD，也可以是支持第一MLD实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置110可以包括一个或多个处理器1101。处理器1101可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端、终端芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
通信装置110还可以包括收发器1105。收发器1105可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1105可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。可选的，通信装置110还可以包括天线1106。
可选的，通信装置110中可以包括一个或多个存储器1102，其上可以存有计算机程序1104，所述计算机程序可在通信装置110上被运行，使得通信装置110执行上述方法实施例中描述的方法。可选的，所述存储器1102中还可以存储有数据。通信装置110和存储器1102可以单独设置，也可以集成在一起。
处理器1101用于执行图2中的步骤S203；图3a中的步骤S304；图4a中的步骤S403；图5中步骤S504～步骤S505、步骤S509；图6a中的步骤S603；图7中的步骤S703；图8中的步骤S803或图9a中的步骤S903。
收发器1105用于在图2所示实施例中接收来自第二MLD的指示信息；在图3a所示实施例中接收来自第二MLD的第一指示信息；在图4a所示实施例中接收来自第二MLD的缓存数据；在图5所示实施例中接收来自第二MLD的第一指示信息和缓存数据，向第二MLD发送链路状态指示信息；在图6a所示实施例中接收来自第二MLD的第三数据类型对应的缓存数据；在图7所示实施例中接收来自第二MLD的第七指示信息；在图8所示实施例中接收来自第二MLD的第八指示信息；在图9a所示实施例中接收来自第二MLD的第十指示信息；
在一种实现方式中，处理器1101中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1101可以存有计算机程序1103，计算机程序1103在处理器1101上运行，可使得通信装置110执行上述方法实施例中描述的方法。计算机程序1103可能固化在处理器1101中，该种情况下，处理器1101可能由硬件实现。
在一种实现方式中，通信装置110可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本申请中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是第一MLD，但本申请中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图11的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端、智能终端、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，可参见图12所示的芯片的结构示意图。图12所示的芯片包括处理器1201和接口1202。其中，处理器1201的数量可以是一个或多个，接口1202的数量可以是多个。
对于芯片用于实现图3a或图5所示实施例中的第一MLD的功能的情况：
接口1202，用于接收来自第二MLD的第一指示信息；该第一指示信息用于指示该第一MLD的关联标识对应的缓存数据在第二MLD中的缓存情况；
处理器1201，用于根据该第一指示信息，以及第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，第一MLD具有多个站点；该处理器1201还可以用于根据至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，确定所述多个站点中至少一个站点的工作状态；工作状态为活跃状态或休眠状态。
在一种实现方式中，接口1202还用于接收来自第二MLD的第二指示信息，第二指示信息用于确定关联标识与数据类型之间的对应关系。
在一种实现方式中，第二指示信息指示至少一个关联标识，至少一个关联标识对应至少一种数据类型。
在一种实现方式中，第一MLD可以支持多种数据类型；第二指示信息指示一个第一关联标识，第一关联标识与多种数据类型中的第一数据类型相对应；处理器1201，还用于 根据第一数据类型对应的第一关联标识，确定多种数据类型中除第一数据类型以外的其他数据类型对应的关联标识。
对于芯片用于实现图4a或图5所示实施例中的第一MLD的功能的情况：
接口1202，用于通过第一链路从第二MLD接收缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，其中，第二数据类型为映射于第一链路的任一数据类型；
处理器1201，用于根据该第三指示信息，确定第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据。
在一种实现方式中，第一MLD具有多个站点；处理器1201，还用于根据第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，确定多个站点中与第一链路对应的站点的工作状态；工作状态为活跃状态或休眠状态。
在一种实现方式中，处理器1201用于根据第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，确定多个站点中与第一链路对应的站点的工作状态时，具体用于：若第二MLD中缓存有至少一种第二数据类型对应的缓存数据，则确定多个站点中与第一链路对应的站点的工作状态为活跃状态；若第二MLD中未缓存有任一第二数据类型对应的缓存数据，则确定多个站点中与第一链路对应的站点的工作状态为活跃状态或休眠状态。
在一种实现方式中，第三指示信息指示第二MLD中缓存有至少一种第二数据类型对应的缓存数据；接口1202，还用于接收来自第二MLD的第四指示信息；第四指示信息用于指示第二MLD中未缓存有任一第二数据类型对应的缓存数据。
对于芯片用于实现图6a所示实施例中的第一MLD的功能的情况：
接口1202，用于从第二MLD接收第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示第二MLD中是否缓存有该第三数据类型对应的缓存数据；
处理器1201，用于根据该第五指示信息，确定该第二MLD中是否缓存有该第三数据类型对应的缓存数据。
在一种实现方式中，第一MLD具有多个站点；处理器1201，还可以用于根据第二MLD中是否缓存有第三数据类型对应的缓存数据，确定多个站点中与第二链路对应的站点的工作状态，第三数据类型映射于第二链路；工作状态为活跃状态或休眠状态。
在一种实现方式中，处理器1201，还可以用于确定第二链路是否映射有除第三数据类型以外的其他数据类型；处理器1201用于根据第二MLD中是否缓存有第三数据类型对应的缓存数据，确定多个站点中与第二链路对应的站点的工作状态时，具体用于：根据第二MLD中是否缓存有第三数据类型对应的缓存数据，以及第二链路是否映射有除第三数据类型以外的其他数据类型，确定多个站点中与第二链路对应的站点的工作状态。
在一种实现方式中，第五指示信息指示第二MLD中未缓存有第三数据类型对应的缓存数据；接口1202从第二MLD接收的第三数据类型对应的缓存数据还包括第六指示信息，第六指示信息用于指示第二MLD是否缓存有至少一种第四数据类型对应的缓存数据；第四数据类型为第一MLD所支持的数据类型中除第三数据类型以外的任一数据类型。
在一种实现方式中，第四数据类型的优先级可以高于第三数据类型的优先级。
对于芯片用于实现图7所示实施例中的第一MLD的功能的情况：
接口1202，用于接收来自第二MLD的第七指示信息，该第七指示信息用于指示该第二MLD未缓存有第五数据类型对应的缓存数据；该第五数据类型为该第一MLD所支持的数据类型中的任一数据类型；
处理器1201，用于根据该第七指示信息，确定第二MLD未缓存有该第五数据类型对应的缓存数据。
在一种实现方式中，第一MLD具有多个站点；处理器1201，还用于根据第二MLD未缓存有第五数据类型对应的缓存数据，确定多个站点中与第三链路对应的站点的工作状态，第五数据类型映射于该第三链路；该工作状态为活跃状态或休眠状态。
对于芯片用于实现图8所示实施例中的第一MLD的功能的情况：
接口1202，用于通过第四链路从第二MLD接收第八指示信息，该第八指示信息用于指示该第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据；
处理器1201，用于根据该第八指示信息，确定第二MLD未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
在一种实现方式中，第一MLD具有多个站点；处理器1201，还用于根据第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据，确定多个站点中与第四链路对应的站点的工作状态；工作状态为活跃状态或休眠状态。
对于芯片用于实现图2所示实施例中的第一MLD的功能的情况：
接口1202，用于接收来自第二MLD的第九指示信息，该第九指示信息用于指示第一MLD所支持的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况；
处理器1201，用于根据该第九指示信息，确定至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，处理器1201，还用于根据第一MLD的缓存数据在第二MLD中的缓存情况，确定多个站点中至少一个站点的工作状态；工作状态为活跃状态或休眠状态。
对于芯片用于实现图9a所示实施例中的第一MLD的功能的情况：
接口1202，用于接收来自第二MLD的第十指示信息，该第十指示信息用于指示映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在该第二MLD中的缓存情况；
处理器1201，用于根据该第十指示信息，确定映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况。
在一种实现方式中，第一MLD具有多个站点；处理器1201，还用于根据映射于至少一条链路的至少一种数据类型对应的缓存数据在第二MLD中的缓存情况，确定多个站点中至少一个站点的工作状态；工作状态为活跃状态或休眠状态。
可选的，芯片还包括存储器1203，存储器1203用于存储必要的计算机程序和数据。
请参见图13，为本申请实施例提供的又一种通信装置130的结构示意图。图13所示的通信装置130可包括通信单元1301、处理单元1302和存储单元1303。通信单元1301可包括发送单元和/或接收单元，发送单元用于实现发送功能，接收单元用于实现接收功能， 通信单元1301可以实现发送功能和/或接收功能。通信单元也可以描述为收发单元。
通信装置130可以是第二MLD，也可以是第二MLD中的装置，还可以是能够与第二MLD匹配使用的装置。通信装置130为第二MLD时，可以为前述图2～图9a所示实施例中的第二MLD。
通信装置130为图3a或图5所示实施例中的第二MLD：
处理单元1302，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在存储单元1303中的缓存情况；根据至少一种数据类型对应的缓存数据在存储单元1303中的缓存情况，以及第一MLD的关联标识与支持的数据类型之间的对应关系，确定关联标识对应的缓存数据在存储单元1303中的缓存情况；
通信单元1301，用于向第一MLD发送第一指示信息；该第一指示信息用于指示第一MLD的关联标识对应的缓存数据在存储单元1303中的缓存情况。
在一种实现方式中，通信单元1301，还用于向第一MLD发送第二指示信息，第二指示信息用于确定第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系。
在一种实现方式中，第二指示信息指示至少一个关联标识，至少一个关联标识对应至少一种数据类型。
在一种实现方式中，第一MLD支持多种数据类型；第二指示信息指示一个第一关联标识，第一关联标识与多种数据类型中的第一数据类型相对应。
通信装置130为图4a或图5所示实施例中的第二MLD：
处理单元1302，用于确定存储单元1303中是否缓存有至少一种第二数据类型对应的缓存数据；该第二数据类型为映射于第一链路的任一数据类型；
通信单元1301，用于通过该第一链路向第一MLD发送缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示该存储单元1303中是否缓存有至少一种第二数据类型对应的缓存数据。
在一种实现方式中，第三指示信息指示存储单元1303中缓存有至少一种第二数据类型对应的缓存数据；通信单元1301，还用于向第一MLD发送第四指示信息；第四指示信息用于指示存储单元1303中未缓存有任一第二数据类型对应的缓存数据。
通信装置130为图6a所示实施例中的第二MLD：
处理单元1302，用于确定存储单元1303中是否缓存有第三数据类型对应的缓存数据；
通信单元1301，用于向第一MLD发送该第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示该存储单元1303中是否缓存有第三数据类型对应的缓存数据。
在一种实现方式中，第五指示信息指示存储单元1303中未缓存有第三数据类型对应的缓存数据；通信单元1301向第一MLD发送的第三数据类型对应的缓存数据还包括第六指示信息，第六指示信息用于指示该存储单元1303是否缓存有至少一种第四数据类型对应的缓存数据；该第四数据类型为该第一MLD所支持的数据类型中除第三数据类型以外的任一数据类型。
在一种实现方式中，第四数据类型的优先级可以高于第三数据类型的优先级。
通信装置130为图7所示实施例中的第二MLD：
处理单元1302，用于确定存储单元1303未缓存有第五数据类型对应的缓存数据；该第五数据类型为第一MLD所支持的数据类型中的任一数据类型；
通信单元1301，用于向第一MLD发送第七指示信息，该第七指示信息用于指示该存储单元1303未缓存有该第五数据类型对应的缓存数据。
通信装置130为图8所示实施例中的第二MLD：
处理单元1302，用于确定存储单元1303未缓存有映射于第四链路的任一数据类型对应的缓存数据；
通信单元1301，用于通过该第四链路向第一MLD发送第八指示信息，该第八指示信息用于指示存储单元1303未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
通信装置130为图2所示实施例中的第二MLD：
处理单元1302，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在存储单元1303中的缓存情况；
通信单元1301，用于向第一MLD发送第九指示信息，该第九指示信息用于指示第一MLD所支持的至少一种数据类型对应的缓存数据在存储单元1303中的缓存情况。
通信装置130为图9a所示实施例中的第二MLD：
处理单元1302，用于确定映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在存储单元1303中的缓存情况；
通信单元1301，用于向第一MLD发送第十指示信息，该第十指示信息用于指示映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在存储单元1303中的缓存情况。
请参见图14，图14是本申请实施例提供的又一种通信装置140的结构示意图。通信装置140可以是第二MLD，也可以是支持第二MLD实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置140可以包括一个或多个处理器1401。处理器1401可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端、终端芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
通信装置140还可以包括收发器1405。收发器1405可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1405可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。可选的，通信装置140还可以包括天线1406。
通信装置140还可以包括一个或多个存储器1402，其上可以存有计算机程序1404，所述计算机程序可在通信装置140上被运行，使得通信装置140执行上述方法实施例中描述的方法。可选的，所述存储器1402中还可以存储有数据。通信装置140和存储器1402可以单独设置，也可以集成在一起。
处理器1401用于执行图2中的步骤S201；图3a中的步骤S301～S302；图4a中的步骤 S401；图5中步骤S501～步骤S502、步骤S507；图6a中的步骤S601；图7中的步骤S701；图8中的步骤S801或图9a中的步骤S901。
收发器1405用于执行图2中的S202；图3a中的步骤S303；图4a中的步骤S402；图5中步骤S503、步骤S508；图6a中的步骤S602；图7中的步骤S702；图8中的步骤S802或图9a中的步骤S902。
在一种实现方式中，处理器1401中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1401可以存有计算机程序1403，计算机程序1403在处理器1401上运行，可使得通信装置140执行上述方法实施例中描述的方法。计算机程序1403可能固化在处理器1401中，该种情况下，处理器1401可能由硬件实现。
在一种实现方式中，通信装置140可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本申请中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是第二MLD，但本申请中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图14的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端、智能终端、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，可参见图15所示的芯片的结构示意图。图15所示的芯片包括处理器1501、接口1502和存储器1503。其中，处理器1501的数量可以是一个或多个，接口1502的数量可以是多个，存储器1503的数量可以是一个或多个。存储器1503用于存储缓存数据，以及必要的计算机程序和数据。
对于芯片用于实现图3a或图5所示实施例中的第二MLD的功能的情况：
处理器1501，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在存储器1503中的缓存情况；根据至少一种数据类型对应的缓存数据在存储器1503中的缓存情况，以及第一MLD的关联标识与支持的数据类型之间的对应关系，确定关联标识对应的缓存数据在存储器1503中的缓存情况；
接口1502，用于向第一MLD发送第一指示信息；该第一指示信息用于指示第一MLD的关联标识对应的缓存数据在存储器1503中的缓存情况。
在一种实现方式中，接口1502，还用于向第一MLD发送第二指示信息，第二指示信息用于确定第一MLD的关联标识与第一MLD所支持的数据类型之间的对应关系。
在一种实现方式中，第二指示信息指示至少一个关联标识，至少一个关联标识对应至少一种数据类型。
在一种实现方式中，第一MLD支持多种数据类型；第二指示信息指示一个第一关联标识，第一关联标识与多种数据类型中的第一数据类型相对应。
对于芯片用于实现图4a或图5所示实施例中的第二MLD的功能的情况：
处理器1501，用于确定存储器1503中是否缓存有至少一种第二数据类型对应的缓存数据；该第二数据类型为映射于第一链路的任一数据类型；
接口1502，用于通过该第一链路向第一MLD发送缓存数据，该缓存数据包括第三指示信息；该第三指示信息用于指示该存储器1503中是否缓存有至少一种第二数据类型对应的缓存数据。
在一种实现方式中，第三指示信息指示存储器1503中缓存有至少一种第二数据类型对应的缓存数据；接口1502，还用于向第一MLD发送第四指示信息；第四指示信息用于指示存储器1503中未缓存有任一第二数据类型对应的缓存数据。
对于芯片用于实现图6a所示实施例中的第二MLD的功能的情况：
处理器1501，用于确定存储器1503中是否缓存有第三数据类型对应的缓存数据；
接口1502，用于向第一MLD发送该第三数据类型对应的缓存数据，该缓存数据包括第五指示信息，该第五指示信息用于指示该存储器1503中是否缓存有第三数据类型对应的缓存数据。
在一种实现方式中，第五指示信息指示存储器1503中未缓存有第三数据类型对应的缓存数据；接口1502向第一MLD发送的第三数据类型对应的缓存数据还包括第六指示信息，第六指示信息用于指示该存储器1503是否缓存有至少一种第四数据类型对应的缓存数据；该第四数据类型为该第一MLD所支持的数据类型中除第三数据类型以外的任一数据类型。
在一种实现方式中，第四数据类型的优先级可以高于第三数据类型的优先级。
对于芯片用于实现图7所示实施例中的第二MLD的功能的情况：
处理器1501，用于确定存储器1503未缓存有第五数据类型对应的缓存数据；该第五数据类型为第一MLD所支持的数据类型中的任一数据类型；
接口1502，用于向第一MLD发送第七指示信息，该第七指示信息用于指示该存储器1503未缓存有该第五数据类型对应的缓存数据。
对于芯片用于实现图8所示实施例中的第二MLD的功能的情况：
处理器1501，用于确定存储器1503未缓存有映射于第四链路的任一数据类型对应的 缓存数据；
接口1502，用于通过该第四链路向第一MLD发送第八指示信息，该第八指示信息用于指示存储器1503未缓存有映射于该第四链路的任一数据类型对应的缓存数据。
对于芯片用于实现图2所示实施例中的第二MLD的功能的情况：
处理器1501，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在存储器1503中的缓存情况；
接口1502，用于向第一MLD发送第九指示信息，该第九指示信息用于指示第一MLD所支持的至少一种数据类型对应的缓存数据在存储器1503中的缓存情况。
对于芯片用于实现图9a所示实施例中的第二MLD的功能的情况：
处理器1501，用于确定映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在存储器1503中的缓存情况；
接口1502，用于向第一MLD发送第十指示信息，该第十指示信息用于指示映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在存储器1503中的缓存情况。
本领域技术人员还可以了解到本申请实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本申请实施例保护的范围。
本申请还提供了一种计算机可读存储介质，其上存储有计算机程序，该计算机可读存储介质被计算机执行时实现上述任一方法实施例的功能。
本申请还提供了一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。
本申请中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本申请不做限制。在本申请实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本申请中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本申请并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本申请中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本申请中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (66)

  1. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第一多链路设备MLD接收来自第二MLD的第一指示信息；所述第一指示信息用于指示所述第一MLD的关联标识对应的缓存数据在所述第二MLD中的缓存情况；
    所述第一MLD根据所述第一指示信息，以及所述关联标识与所述第一MLD所支持的数据类型之间的对应关系，确定至少一种所述数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  2. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第二多链路设备MLD确定第一MLD所支持的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况；
    所述第二MLD根据至少一种所述数据类型对应的缓存数据在所述第二MLD中的缓存情况，以及所述第一MLD的关联标识与所述数据类型之间的对应关系，确定所述关联标识对应的缓存数据在所述第二MLD中的缓存情况；
    所述第二MLD向所述第一MLD发送第一指示信息；所述第一指示信息用于指示所述第一MLD的关联标识对应的缓存数据在所述第二MLD中的缓存情况。
  3. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第一多链路设备MLD通过第一链路从第二MLD接收缓存数据，所述缓存数据包括第三指示信息；所述第三指示信息用于指示所述第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，其中，所述第二数据类型为映射于所述第一链路的任一数据类型；
    所述第一MLD根据所述第三指示信息，确定所述第二MLD中是否缓存有至少一种所述第二数据类型对应的缓存数据。
  4. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第二多链路设备MLD确定所述第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据；所述第二数据类型为映射于第一链路的任一数据类型；
    所述第二MLD通过所述第一链路向第一MLD发送缓存数据，所述缓存数据包括第三指示信息；所述第三指示信息用于指示所述第二MLD中是否缓存有至少一种所述第二数据类型对应的缓存数据。
  5. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第一多链路设备MLD从第二MLD接收第三数据类型对应的缓存数据，所述缓存数据包括第五指示信息，所述第五指示信息用于指示所述第二MLD中是否缓存有所述第三数据类型对应的缓存数据；
    所述第一MLD根据所述第五指示信息，确定所述第二MLD中是否缓存有所述第三数据类型对应的缓存数据。
  6. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第二多链路设备MLD确定所述第二MLD中是否缓存有第三数据类型对应的缓存数据；
    所述第二MLD向第一MLD发送所述第三数据类型对应的缓存数据，所述缓存数据包括第五指示信息，所述第五指示信息用于指示所述第二MLD中是否缓存有所述第三数据类型对应的缓存数据。
  7. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第一多链路设备MLD接收来自第二MLD的第七指示信息，所述第七指示信息用于指示所述第二MLD未缓存有第五数据类型对应的缓存数据；所述第五数据类型为所述第一MLD所支持的数据类型中的任一数据类型；
    所述第一MLD根据所述第七指示信息，确定所述第二MLD未缓存有所述第五数据类型对应的缓存数据。
  8. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第二多链路设备MLD确定所述第二MLD未缓存有第五数据类型对应的缓存数据；所述第五数据类型为第一MLD所支持的数据类型中的任一数据类型；
    所述第二MLD向所述第一MLD发送第七指示信息，所述第七指示信息用于指示所述第二MLD未缓存有所述第五数据类型对应的缓存数据。
  9. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第一多链路设备MLD通过第四链路从第二MLD接收第八指示信息，所述第八指示信息用于指示所述第二MLD未缓存有映射于所述第四链路的任一数据类型对应的缓存数据；
    所述第一MLD根据所述第八指示信息，确定所述第二MLD未缓存有映射于所述第四链路的任一数据类型对应的缓存数据。
  10. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第二多链路设备MLD确定所述第二MLD未缓存有映射于第四链路的任一数据类型对应的缓存数据；
    所述第二MLD通过所述第四链路向第一MLD发送第八指示信息，所述第八指示信息用于指示所述第二MLD未缓存有映射于所述第四链路的任一数据类型对应的缓存数据。
  11. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第一多链路设备MLD接收来自第二MLD的第九指示信息，所述第九指示信息用于指示所述第一MLD所支持的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况；
    所述第一MLD根据所述第九指示信息，确定所述至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  12. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第二多链路设备MLD确定第一MLD所支持的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况；
    所述第二MLD向所述第一MLD发送第九指示信息，所述第九指示信息用于指示所述第一MLD所支持的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  13. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第一多链路设备MLD接收来自第二MLD的第十指示信息，所述第十指示信息用于指示映射于所述第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况；
    所述第一MLD根据所述第十指示信息，确定映射于所述至少一条链路的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  14. 一种数据缓存情况的确定方法，其特征在于，所述方法包括：
    第二多链路设备MLD确定映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况；
    所述第二MLD向所述第一MLD发送第十指示信息，所述第十指示信息用于指示映射于所述第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  15. 一种通信装置，其特征在于，所述装置包括收发器和处理器；
    所述收发器，用于接收来自第二MLD的第一指示信息；所述第一指示信息用于指示所述通信装置的关联标识对应的缓存数据在所述第二MLD中的缓存情况；
    所述处理器，用于根据所述第一指示信息，以及所述关联标识与所述通信装置所支持的数据类型之间的对应关系，确定至少一种所述数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  16. 根据权利要求15所述的通信装置，其特征在于，所述通信装置具有多个站点；
    所述处理器，还用于根据至少一种所述数据类型对应的缓存数据在所述第二MLD中的缓存情况，确定所述多个站点中至少一个站点的工作状态；所述工作状态为活跃状态或休眠状态。
  17. 根据权利要求15或16所述的通信装置，其特征在于，
    所述收发器，还用于接收来自所述第二MLD的第二指示信息，所述第二指示信息用于确定所述关联标识与所述数据类型之间的对应关系。
  18. 根据权利要求17所述的通信装置，其特征在于，所述第二指示信息指示至少一个 所述关联标识，至少一个所述关联标识对应至少一种所述数据类型。
  19. 根据权利要求17所述的通信装置，其特征在于，所述通信装置支持多种数据类型；所述第二指示信息指示一个第一关联标识，所述第一关联标识与所述多种数据类型中的第一数据类型相对应；
    所述处理器，还用于根据所述第一数据类型对应的所述第一关联标识，确定所述多种数据类型中除所述第一数据类型以外的其他数据类型对应的关联标识。
  20. 一种通信装置，其特征在于，所述装置包括收发器、处理器和存储器；
    所述处理器，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在所述存储器中的缓存情况；并根据至少一种所述数据类型对应的缓存数据在所述存储器中的缓存情况，以及所述第一MLD的关联标识与所述数据类型之间的对应关系，确定所述关联标识对应的缓存数据在所述存储器中的缓存情况；
    所述收发器，用于向所述第一MLD发送第一指示信息；所述第一指示信息用于指示所述第一MLD的关联标识对应的缓存数据在所述存储器中的缓存情况。
  21. 根据权利要求20所述的通信装置，其特征在于，
    所述收发器，还用于向所述第一MLD发送第二指示信息，所述第二指示信息用于确定所述关联标识与所述第一MLD所支持的数据类型之间的对应关系。
  22. 根据权利要求21所述的通信装置，其特征在于，所述第二指示信息指示至少一个所述关联标识，至少一个所述关联标识对应至少一种所述数据类型。
  23. 根据权利要求21所述的通信装置，其特征在于，所述第一MLD支持多种数据类型；所述第二指示信息指示一个第一关联标识，所述第一关联标识与所述多种数据类型中的第一数据类型相对应。
  24. 一种通信装置，其特征在于，所述装置包括收发器和处理器；
    所述收发器，用于通过第一链路从第二MLD接收缓存数据，所述缓存数据包括第三指示信息；所述第三指示信息用于指示所述第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，其中，所述第二数据类型为映射于所述第一链路的任一数据类型；
    所述处理器，用于根据所述第三指示信息，确定所述第二MLD中是否缓存有至少一种所述第二数据类型对应的缓存数据。
  25. 根据权利要求24所述的通信装置，其特征在于，所述通信装置具有多个站点；
    所述处理器，还用于根据所述第二MLD中是否缓存有至少一种所述第二数据类型对应的缓存数据，确定所述多个站点中与所述第一链路对应的站点的工作状态；所述工作状态为活跃状态或休眠状态。
  26. 根据权利要求25所述的通信装置，其特征在于，
    所述处理器具体用于：若所述第二MLD中缓存有至少一种所述第二数据类型对应的缓存数据，则确定所述多个站点中与所述第一链路对应的站点的工作状态为所述活跃状态；
    若所述第二MLD中未缓存有任一所述第二数据类型对应的缓存数据，则确定所述多个站点中与所述第一链路对应的站点的工作状态为所述活跃状态或所述休眠状态。
  27. 根据权利要求26所述的通信装置，其特征在于，所述第三指示信息指示所述第二MLD中缓存有至少一种所述第二数据类型对应的缓存数据；
    所述收发器，还用于接收来自所述第二MLD的第四指示信息；所述第四指示信息用于指示所述第二MLD中未缓存有任一所述第二数据类型对应的缓存数据。
  28. 一种通信装置，其特征在于，所述装置包括收发器、处理器和存储器；
    所述处理器，用于确定所述存储器中是否缓存有至少一种第二数据类型对应的缓存数据；所述第二数据类型为映射于第一链路的任一数据类型；
    所述收发器，用于通过所述第一链路向第一MLD发送缓存数据，所述缓存数据包括第三指示信息；所述第三指示信息用于指示所述存储器中是否缓存有至少一种所述第二数据类型对应的缓存数据。
  29. 根据权利要求28所述的通信装置，其特征在于，所述第三指示信息指示所述存储器中缓存有至少一种所述第二数据类型对应的缓存数据；
    所述收发器，还用于向所述第一MLD发送第四指示信息；所述第四指示信息用于指示所述存储器中未缓存有任一所述第二数据类型对应的缓存数据。
  30. 一种通信装置，其特征在于，所述装置包括收发器和处理器；
    所述收发器，用于从第二MLD接收第三数据类型对应的缓存数据，所述缓存数据包括第五指示信息，所述第五指示信息用于指示所述第二MLD中是否缓存有所述第三数据类型对应的缓存数据；
    所述处理器，用于根据所述第五指示信息，确定所述第二MLD中是否缓存有所述第三数据类型对应的缓存数据。
  31. 根据权利要求30所述的通信装置，其特征在于，所述通信装置具有多个站点；
    所述处理器，还用于根据所述第二MLD中是否缓存有所述第三数据类型对应的缓存数据，确定所述多个站点中与第二链路对应的站点的工作状态，所述第三数据类型映射于所述第二链路；所述工作状态为活跃状态或休眠状态。
  32. 根据权利要求31所述的通信装置，其特征在于，
    所述处理器，还用于确定所述第二链路是否映射有除所述第三数据类型以外的其他数 据类型；
    所述处理器具体用于：根据所述第二MLD中是否缓存有所述第三数据类型对应的缓存数据，以及所述第二链路是否映射有除所述第三数据类型以外的其他数据类型，确定所述多个站点中与所述第二链路对应的站点的工作状态。
  33. 根据权利要求30或31所述的通信装置，其特征在于，所述第五指示信息指示所述第二MLD中未缓存有所述第三数据类型对应的缓存数据；所述收发器从所述第二MLD接收的所述第三数据类型对应的缓存数据还包括第六指示信息，所述第六指示信息用于指示所述第二MLD是否缓存有至少一种第四数据类型对应的缓存数据；所述第四数据类型为所述通信装置所支持的数据类型中除所述第三数据类型以外的任一数据类型。
  34. 根据权利要求33所述的通信装置，其特征在于，所述第四数据类型的优先级高于所述第三数据类型的优先级。
  35. 一种通信装置，其特征在于，所述装置包括收发器、处理器和存储器；
    所述处理器，用于确定所述存储器中是否缓存有第三数据类型对应的缓存数据；
    所述收发器，用于向第一MLD发送所述第三数据类型对应的缓存数据，所述缓存数据包括第五指示信息，所述第五指示信息用于指示所述存储器中是否缓存有所述第三数据类型对应的缓存数据。
  36. 根据权利要求35所述的通信装置，其特征在于，所述第五指示信息指示所述存储器中未缓存有所述第三数据类型对应的缓存数据；所述收发器向所述第一MLD发送的所述第三数据类型对应的缓存数据还包括第六指示信息，所述第六指示信息用于指示所述存储器是否缓存有至少一种第四数据类型对应的缓存数据；所述第四数据类型为所述第一MLD所支持的数据类型中除所述第三数据类型以外的任一数据类型。
  37. 根据权利要求36所述的通信装置，其特征在于，所述第四数据类型的优先级高于所述第三数据类型的优先级。
  38. 一种通信装置，其特征在于，所述装置包括收发器和处理器；
    所述收发器，用于接收来自第二MLD的第七指示信息，所述第七指示信息用于指示所述第二MLD未缓存有第五数据类型对应的缓存数据；所述第五数据类型为所述通信装置所支持的数据类型中的任一数据类型；
    所述处理器，用于根据所述第七指示信息，确定所述第二MLD未缓存有所述第五数据类型对应的缓存数据。
  39. 根据权利要求38所述的通信装置，其特征在于，所述通信装置具有多个站点；
    所述处理器，还用于根据所述第二MLD未缓存有所述第五数据类型对应的缓存数据， 确定所述多个站点中与第三链路对应的站点的工作状态，所述第五数据类型映射于所述第三链路；所述工作状态为活跃状态或休眠状态。
  40. 一种通信装置，其特征在于，所述装置包括收发器、处理器和存储器；
    所述处理器，用于确定所述存储器未缓存有第五数据类型对应的缓存数据；所述第五数据类型为第一MLD所支持的数据类型中的任一数据类型；
    所述收发器，用于向所述第一MLD发送第七指示信息，所述第七指示信息用于指示所述存储器未缓存有所述第五数据类型对应的缓存数据。
  41. 一种通信装置，其特征在于，所述装置包括收发器和处理器；
    所述收发器，用于通过第四链路从第二MLD接收第八指示信息，所述第八指示信息用于指示所述第二MLD未缓存有映射于所述第四链路的任一数据类型对应的缓存数据；
    所述处理器，用于根据所述第八指示信息，确定所述第二MLD未缓存有映射于所述第四链路的任一数据类型对应的缓存数据。
  42. 根据权利要求41所述的通信装置，其特征在于，所述通信装置具有多个站点；
    所述处理器，还用于根据所述第二MLD未缓存有映射于所述第四链路的任一数据类型对应的缓存数据，确定所述多个站点中与所述第四链路对应的站点的工作状态；所述工作状态为活跃状态或休眠状态。
  43. 一种通信装置，其特征在于，所述装置包括收发器、处理器和存储器；
    所述处理器，用于确定所述存储器未缓存有映射于第四链路的任一数据类型对应的缓存数据；
    所述收发器，用于通过所述第四链路向第一MLD发送第八指示信息，所述第八指示信息用于指示所述存储器未缓存有映射于所述第四链路的任一数据类型对应的缓存数据。
  44. 一种通信装置，其特征在于，所述装置包括收发器和处理器；
    所述收发器，用于接收来自第二MLD的第九指示信息，所述第九指示信息用于指示所述通信装置所支持的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况；
    所述处理器，用于根据所述第九指示信息，确定所述至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  45. 根据权利要求44所述的通信装置，其特征在于，所述通信装置具有多个站点；
    所述处理器，还用于根据所述至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况，确定所述多个站点中至少一个站点的工作状态；所述工作状态为活跃状态或休眠状态。
  46. 一种通信装置，其特征在于，所述装置包括收发器、处理器和存储器；
    所述处理器，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在所述存储器中的缓存情况；
    所述收发器，用于向所述第一MLD发送第九指示信息，所述第九指示信息用于指示所述第一MLD所支持的至少一种数据类型对应的缓存数据在所述存储器中的缓存情况。
  47. 一种通信装置，其特征在于，所述装置包括收发器和处理器；
    所述收发器，用于接收来自第二MLD的第十指示信息，所述第十指示信息用于指示映射于所述通信装置对应的至少一条链路的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况；
    所述处理器，用于根据所述第十指示信息，确定映射于所述至少一条链路的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  48. 根据权利要求47所述的通信装置，其特征在于，所述通信装置具有多个站点；
    所述处理器，还用于根据映射于所述至少一条链路的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况，确定所述多个站点中至少一个站点的工作状态；所述工作状态为活跃状态或休眠状态。
  49. 一种通信装置，其特征在于，所述装置包括收发器、处理器和存储器；
    所述处理器，用于确定映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在所述存储器中的缓存情况；
    所述收发器，用于向所述第一MLD发送第十指示信息，所述第十指示信息用于指示映射于所述第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在所述存储器中的缓存情况。
  50. 一种芯片系统，其特征在于，包括至少一个处理器和接口；
    所述接口，用于接收来自第二MLD的第一指示信息；所述第一指示信息用于指示第一MLD的关联标识对应的缓存数据在所述第二MLD中的缓存情况；
    所述处理器，用于根据所述第一指示信息，以及所述关联标识与所述第一MLD所支持的数据类型之间的对应关系，确定至少一种所述数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  51. 一种芯片系统，其特征在于，包括至少一个存储器、至少一个处理器和接口；
    所述处理器，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在所述存储器中的缓存情况；并根据至少一种所述数据类型对应的缓存数据在所述存储器中的缓存情况，以及所述第一MLD的关联标识与所述数据类型之间的对应关系，确定所述关联标识对应的缓存数据在所述存储器中的缓存情况；
    所述接口，用于向所述第一MLD发送第一指示信息；所述第一指示信息用于指示所述第一MLD的关联标识对应的缓存数据在所述存储器中的缓存情况。
  52. 一种芯片系统，其特征在于，包括至少一个处理器和接口；
    所述接口，用于通过第一链路从第二MLD接收缓存数据，所述缓存数据包括第三指示信息；所述第三指示信息用于指示所述第二MLD中是否缓存有至少一种第二数据类型对应的缓存数据，其中，所述第二数据类型为映射于所述第一链路的任一数据类型；
    所述处理器，用于根据所述第三指示信息，确定所述第二MLD中是否缓存有至少一种所述第二数据类型对应的缓存数据。
  53. 一种芯片系统，其特征在于，包括至少一个存储器、至少一个处理器和接口；
    所述处理器，用于确定所述存储器中是否缓存有至少一种第二数据类型对应的缓存数据；所述第二数据类型为映射于第一链路的任一数据类型；
    所述接口，用于通过所述第一链路向第一MLD发送缓存数据，所述缓存数据包括第三指示信息；所述第三指示信息用于指示所述存储器中是否缓存有至少一种所述第二数据类型对应的缓存数据。
  54. 一种芯片系统，其特征在于，包括至少一个处理器和接口；
    所述接口，用于从第二MLD接收第三数据类型对应的缓存数据，所述缓存数据包括第五指示信息，所述第五指示信息用于指示所述第二MLD中是否缓存有所述第三数据类型对应的缓存数据；
    所述处理器，用于根据所述第五指示信息，确定所述第二MLD中是否缓存有所述第三数据类型对应的缓存数据。
  55. 一种芯片系统，其特征在于，包括至少一个存储器、至少一个处理器和接口；
    所述处理器，用于确定所述存储器中是否缓存有第三数据类型对应的缓存数据；
    所述接口，用于向第一MLD发送所述第三数据类型对应的缓存数据，所述缓存数据包括第五指示信息，所述第五指示信息用于指示所述存储器中是否缓存有所述第三数据类型对应的缓存数据。
  56. 一种芯片系统，其特征在于，包括至少一个处理器和接口；
    所述接口，用于接收来自第二MLD的第七指示信息，所述第七指示信息用于指示所述第二MLD未缓存有第五数据类型对应的缓存数据；所述第五数据类型为第一MLD所支持的数据类型中的任一数据类型；
    所述处理器，用于根据所述第七指示信息，确定所述第二MLD未缓存有所述第五数据类型对应的缓存数据。
  57. 一种芯片系统，其特征在于，包括至少一个存储器、至少一个处理器和接口；
    所述处理器，用于确定所述存储器未缓存有第五数据类型对应的缓存数据；所述第五数据类型为第一MLD所支持的数据类型中的任一数据类型；
    所述接口，用于向所述第一MLD发送第七指示信息，所述第七指示信息用于指示所述存储器未缓存有所述第五数据类型对应的缓存数据。
  58. 一种芯片系统，其特征在于，包括至少一个处理器和接口；
    所述接口，用于通过第四链路从第二MLD接收第八指示信息，所述第八指示信息用于指示所述第二MLD未缓存有映射于所述第四链路的任一数据类型对应的缓存数据；
    所述处理器，用于根据所述第八指示信息，确定所述第二MLD未缓存有映射于所述第四链路的任一数据类型对应的缓存数据。
  59. 一种芯片系统，其特征在于，包括至少一个存储器、至少一个处理器和接口；
    所述处理器，用于确定所述存储器未缓存有映射于第四链路的任一数据类型对应的缓存数据；
    所述接口，用于通过所述第四链路向第一MLD发送第八指示信息，所述第八指示信息用于指示所述存储器未缓存有映射于所述第四链路的任一数据类型对应的缓存数据。
  60. 一种芯片系统，其特征在于，包括至少一个处理器和接口；
    所述接口，用于接收来自第二MLD的第九指示信息，所述第九指示信息用于指示第一MLD所支持的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况；
    所述处理器，用于根据所述第九指示信息，确定所述至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  61. 一种芯片系统，其特征在于，包括至少一个存储器、至少一个处理器和接口；
    所述处理器，用于确定第一MLD所支持的至少一种数据类型对应的缓存数据在所述存储器中的缓存情况；
    所述接口，用于向所述第一MLD发送第九指示信息，所述第九指示信息用于指示所述第一MLD所支持的至少一种数据类型对应的缓存数据在所述存储器中的缓存情况。
  62. 一种芯片系统，其特征在于，包括至少一个处理器和接口；
    所述接口，用于接收来自第二MLD的第十指示信息，所述第十指示信息用于指示映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况；
    所述处理器，用于根据所述第十指示信息，确定映射于所述至少一条链路的至少一种数据类型对应的缓存数据在所述第二MLD中的缓存情况。
  63. 一种芯片系统，其特征在于，包括至少一个存储器、至少一个处理器和接口；
    所述处理器，用于确定映射于第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在所述存储器中的缓存情况；
    所述接口，用于向所述第一MLD发送第十指示信息，所述第十指示信息用于指示映 射于所述第一MLD对应的至少一条链路的至少一种数据类型对应的缓存数据在所述存储器中的缓存情况。
  64. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1、3、5、7、9、11、13中任一项所述的方法；或，执行如权利要求2、4、6、8、10、12、14中任一项所述的方法。
  65. 一种程序，其特征在于，当所述程序在计算机上运行时，使得所述计算机执行如权利要求1、3、5、7、9、11、13中任一项所述的方法；或，执行如权利要求2、4、6、8、10、12、14中任一项所述的方法。
  66. 一种装置，其特征在于，用于执行如权利要求1、3、5、7、9、11、13中任一项所述的方法；或，执行如权利要求2、4、6、8、10、12、14中任一项所述的方法。
PCT/CN2021/080254 2020-03-13 2021-03-11 一种数据缓存情况的确定方法及其装置 WO2021180179A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
KR1020227031880A KR20220143707A (ko) 2020-03-13 2021-03-11 데이터 버퍼 상태를 판정하는 방법, 및 장치
JP2022554753A JP7389266B2 (ja) 2020-03-13 2021-03-11 データ・バッファ・ステータスを決定する方法及び装置
BR112022016925A BR112022016925A2 (pt) 2020-03-13 2021-03-11 Método para determinar status de armazenamento temporário de dados, e aparelho
EP21768886.0A EP4099755A4 (en) 2020-03-13 2021-03-11 METHOD AND APPARATUS FOR DETERMINING DATA CACHING STATE
AU2021236081A AU2021236081B2 (en) 2020-03-13 2021-03-11 Method for determining data buffer status, and apparatus
US17/891,785 US20220394556A1 (en) 2020-03-13 2022-08-19 Method for determining data buffer status, and apparatus
US18/331,196 US20230319640A1 (en) 2020-03-13 2023-06-08 Method for determining data buffer status, and apparatus
JP2023194785A JP2024020422A (ja) 2020-03-13 2023-11-16 データ・バッファ・ステータスを決定する方法及び装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010180304.6 2020-03-13
CN202010180304.6A CN113395731A (zh) 2020-03-13 2020-03-13 一种数据缓存情况的确定方法及其装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/891,785 Continuation US20220394556A1 (en) 2020-03-13 2022-08-19 Method for determining data buffer status, and apparatus

Publications (1)

Publication Number Publication Date
WO2021180179A1 true WO2021180179A1 (zh) 2021-09-16

Family

ID=77616296

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/080254 WO2021180179A1 (zh) 2020-03-13 2021-03-11 一种数据缓存情况的确定方法及其装置

Country Status (8)

Country Link
US (2) US20220394556A1 (zh)
EP (1) EP4099755A4 (zh)
JP (2) JP7389266B2 (zh)
KR (1) KR20220143707A (zh)
CN (3) CN115567973A (zh)
AU (1) AU2021236081B2 (zh)
BR (1) BR112022016925A2 (zh)
WO (1) WO2021180179A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4162735A4 (en) * 2020-06-09 2023-11-29 Panasonic Intellectual Property Corporation of America COMMUNICATION APPARATUS AND COMMUNICATION METHOD FOR MULTI-LINK TRAFFIC INDICATION CARD
CN116963289A (zh) * 2022-04-08 2023-10-27 华为技术有限公司 多链路通信方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107396433A (zh) * 2017-07-31 2017-11-24 中南大学 基于ndn架构的无线局域网节能方法及sta
US20190268221A1 (en) * 2018-02-28 2019-08-29 Qualcomm Incorporated Conditional inheritance in management frame for multiple basic service sets
CN110191449A (zh) * 2019-05-29 2019-08-30 上海庆科信息技术有限公司 通讯模式的切换方法、装置、存储介质、处理器及系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7551948B2 (en) * 2003-07-24 2009-06-23 Cisco Technology, Inc. Uniform power save method for 802.11e stations
JP5072778B2 (ja) 2008-09-02 2012-11-14 株式会社エヌ・ティ・ティ・ドコモ 無線通信基地局、無線通信端末、無線通信システムおよび無線通信制御方法
US9398611B2 (en) * 2012-02-15 2016-07-19 Lg Electronics Inc. Method for accessing channels in wireless communication systems and apparatus for same
US10536948B2 (en) * 2015-06-22 2020-01-14 Qualcomm Incorporated Methods and apparatus for requesting buffer status reports for implementing multiple user uplink medium access control protocols in a wireless network
US10455557B2 (en) * 2016-02-05 2019-10-22 Lg Electronics Inc. Method of supporting for uplink multi-user transmission in wireless area network system
US10791516B1 (en) * 2017-10-13 2020-09-29 Nxp Usa, Inc. Methods and apparatus for allocating physical resources of a wireless network to client devices
SG10201805402YA (en) * 2018-06-22 2020-01-30 Panasonic Ip Corp America Communication apparatus and communication method for low power event monitoring
US11963100B2 (en) * 2018-10-12 2024-04-16 Mediatek Singapore Pte. Ltd. Method and apparatus for multi-band power management in a wireless network
KR20210049694A (ko) * 2019-10-25 2021-05-06 현대자동차주식회사 Wur을 사용한 정보의 송수신 방법

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107396433A (zh) * 2017-07-31 2017-11-24 中南大学 基于ndn架构的无线局域网节能方法及sta
US20190268221A1 (en) * 2018-02-28 2019-08-29 Qualcomm Incorporated Conditional inheritance in management frame for multiple basic service sets
CN110191449A (zh) * 2019-05-29 2019-08-30 上海庆科信息技术有限公司 通讯模式的切换方法、装置、存储介质、处理器及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
LIWEN CHU (NXP): "Multi-Link Power Save", IEEE DRAFT; 11-19-1617-02-00BE-MULTI-LINK-POWER-SAVE, vol. 802.11 EHT; 802.11be, no. 2, 16 January 2020 (2020-01-16), pages 1 - 10, XP068165382 *
MING GAN (HUAWEI): "Power Save for Multi-link", IEEE DRAFT; 11-19-1988-00-00BE-POWER-SAVE-FOR-MULTI-LINK, vol. 802.11 EHT; 802.11be, 11 November 2019 (2019-11-11), pages 1 - 11, XP068164318 *
MINYOUNG PARK (INTEL CORP.): "Multi-link power save operation", IEEE DRAFT; 11-19-1544-05-00BE-MULTI-LINK-POWER-SAVE-OPERATION, vol. 802.11 EHT; 802.11be, no. 5, 16 January 2020 (2020-01-16), pages 1 - 18, XP068165413 *

Also Published As

Publication number Publication date
CN115567972A (zh) 2023-01-03
JP2024020422A (ja) 2024-02-14
JP2023517662A (ja) 2023-04-26
US20220394556A1 (en) 2022-12-08
AU2021236081B2 (en) 2023-12-07
CN115567973A (zh) 2023-01-03
US20230319640A1 (en) 2023-10-05
EP4099755A4 (en) 2023-07-19
EP4099755A1 (en) 2022-12-07
AU2021236081A1 (en) 2022-09-15
BR112022016925A2 (pt) 2022-10-25
JP7389266B2 (ja) 2023-11-29
CN113395731A (zh) 2021-09-14
KR20220143707A (ko) 2022-10-25

Similar Documents

Publication Publication Date Title
WO2021244652A1 (zh) 适用于多链路的组播业务传输方法及装置
WO2022033592A1 (zh) 适用于多链路的关键bss参数管理方法及相关装置
WO2022052708A1 (zh) 无线通信系统中的多链路建立方法及通信装置
US8295216B2 (en) Broadcast and multicast transmission techniques for powersave devices in wireless networks
WO2021180177A1 (zh) 一种应用于多链路通信中的功率节省方法和装置
WO2022028610A1 (zh) 适用于多链路的单播业务指示方法及相关装置
WO2022002221A1 (zh) 多链路建立方法及通信装置
CN115623426B (zh) 适用于多链路的组播业务传输方法及装置
WO2021208903A1 (zh) 一种通信方法和通信装置
KR20080086900A (ko) 추가 전력 절감 멀티-폴 표시
WO2021180179A1 (zh) 一种数据缓存情况的确定方法及其装置
WO2022151912A1 (zh) 传输机会的使用权恢复方法及相关装置
CN117204109A (zh) 通信方法及装置
WO2022002192A1 (zh) 多链路设备的aid分配方法及相关装置
WO2023193666A1 (zh) 多链路通信方法及装置
WO2023185759A1 (zh) 多链路通信方法及装置
TWI821009B (zh) P2p鏈路的信息指示方法及相關裝置
WO2023207223A1 (zh) 多链路的重配置方法及装置
WO2023169421A1 (zh) 一种多链路数据处理方法、装置及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21768886

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
WWE Wipo information: entry into national phase

Ref document number: 2021236081

Country of ref document: AU

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112022016925

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2022554753

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20227031880

Country of ref document: KR

Kind code of ref document: A

Ref document number: 2021236081

Country of ref document: AU

Date of ref document: 20210311

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021768886

Country of ref document: EP

Effective date: 20220831

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112022016925

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20220824