Communication methods and related apparatuses

Abstract

A communication method and related apparatus are disclosed, applicable to wireless local area network (WLAN) systems supporting IEEE 802.11ax next-generation Wi-Fi protocols, such as 802.11be, Wi-Fi 7, or EHT, such as 802.11be next-generation, Wi-Fi 8, UHR, Wi-Fi AI, and other 802.11 series protocols. It can also be applied to ultra-bandwidth wireless personal area network (WLAN) systems and sensing systems. The Access Point Management Layer (AP MLD) transmits at least one first frame on at least one first link; the first frame indicates the effective start time of the service identifier and link mapping; when the service identifier and link mapping indicate that the second link is closed, the AP MLD closes the second link no earlier than time point Tb; when the service identifier and link mapping indicate that the second link is open, the AP MLD opens the second link no later than time point Ta; Ta is earlier than Tb. This application can improve communication reliability.

Description

[0001] This application is a divisional application. The original application has the application number 202310790310.7 and the original application date is June 28, 2023. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and related apparatus. Background Technology

[0003] With the development of wireless technology, more and more wireless devices support multi-link communication, such as communicating simultaneously on the 2.4GHz, 5GHz, and 6GHz frequency bands, or communicating simultaneously on different channels within the same frequency band, thereby improving the communication speed between wireless devices. Devices that support multi-link communication are usually called multi-link devices (MLDs).

[0004] Before MLDs can communicate across multiple links, they need to establish (or associate) multiple links. To better manage services, traffic IDs (TIDs) and link mappings (TID-to-link mapping) can be used to provide different services for different services. Typically, the traffic ID and link mapping are carried in the traffic ID and link mapping element (TID-to-Link Mapping element).

[0005] According to the 802.11be standard, an access point multi-link device (AP MLD) can indicate the effective start time of the service identifier and link mapping through the mapping switch time field in the TID-to-Link Mapping element carried in a beacon frame or probe response frame. The effective start time of the service identifier and link mapping can be the target beacon transmission time (TBTT) indicated by the delivery traffic indication map (DTIM) beacon frame of any link. Understandably, the TBTT on a certain link (e.g., link 1) is the time unit (TU) boundary of that link, but it is not necessarily the TU boundary of other links (e.g., link 2, link 3, etc.). This is because the values ​​of the time synchronization function (TSF) timers on different links are selected independently. When the lower 10 bits of the TSF timer on a certain link (e.g., link 1) are 0, the lower 10 bits of the TSF timer on another link are not necessarily 0. The time precision that the mapping switch time field in the TID-to-Link Mapping element can indicate is TU (1TU = 1024us). This means that the mapping switch time field in the TID-to-Link Mapping element on one link cannot indicate the TU boundary on another link, and therefore cannot indicate the TBTT of another link. In other words, the APMLD cannot accurately indicate the effective start time of the service identifier and link mapping, which is not conducive to reliable communication between the AP MLD and the non-accesspoint multi-link device (non-AP MLD). Summary of the Invention

[0006] This application provides a communication method and related apparatus, which facilitates reliable communication between AP MLD and non-AP MLD.

[0007] In a first aspect, this application provides a communication method applied to an AP MLD, which can be the AP MLD itself, or a module or chip within the AP MLD. The method includes: an AP MLD generating at least one first frame; the AP MLD transmitting the at least one first frame on at least one first link; wherein the first frame indicates the effective start time of a service identifier and link mapping; when the service identifier and link mapping indicates that a second link is closed, the AP MLD closes the second link no earlier than time point Tb; or, when the service identifier and link mapping indicates that the second link is open, the AP MLD opens the second link no later than time point Ta; Ta is earlier than Tb, and Ta and / or Tb are determined according to a first time and / or a second time, wherein the first time is the target beacon transmission time TBTT corresponding to the service indication map (DTIM) beacon frame of the third link, when the first link and the third link are the same, the effective start time of the service identifier and link mapping indicated by the first frame transmitted on the first link is the first time, and when the first link and the third link are different, the effective start time of the service identifier and link mapping indicated by the first frame transmitted on the first link is the second time, wherein the second time is the time unit (TU) boundary on the first link.

[0008] Understandably, if, according to the instructions of the service identifier and link mapping, no service identifier (TID) is mapped to a link in any direction (including uplink and downlink), then that link will be closed; if, according to the instructions of the service identifier and link mapping, there exists a service identifier (TID) that is mapped to a link in any direction (including uplink and downlink), then that link will be opened.

[0009] In this application, if a link (for example, the second link is used as an illustrative example) is determined to be closed according to the indication of the service identifier and link mapping, the AP MLD will close latest (i.e., later than the closing time of all non-AP MLDs that have established multi-link communication with this AP MLD). Therefore, it can be guaranteed that the AP MLD can normally receive data / information from non-AP MLDs. Conversely, if a link (for example, the second link is used as an illustrative example) is determined to be opened according to the indication of the service identifier and link mapping, the AP MLD will open earliest (i.e., earlier than the opening time of all non-AP MLDs that have established multi-link communication with this AP MLD). Therefore, it can be guaranteed that the AP MLD can normally receive data / information from non-AP MLDs. Based on this, the problem of unreliable communication between AP MLDs and non-AP MLDs caused by inconsistent understanding of the mapping effective time between AP MLDs and non-AP MLDs can be solved.

[0010] In one possible implementation, when the service identifier and link mapping indicate that the second link is closed, the APMLD, if later than Ta, does not initiate a transmission to the first non-AP MLD on the second link; or,

[0011] When the service identifier and link mapping indicate that the second link is enabled, the AP MLD will not initiate transmission to the first non-AP MLD on the second link if it is earlier than Tb.

[0012] In this implementation, if the second link is shut down, the AP MLD will not initiate transmissions to the first non-AP MLD on the second link if the transmission occurs after Ta. Therefore, the non-AP MLD can still receive data / information from the AP MLD, thus improving the reliability of communication between the AP MLD and the non-AP MLD. Similarly, if the second link is opened, the AP MLD will not initiate transmissions to the first non-AP MLD on the second link if the transmission occurs before Tb. This also ensures that the non-AP MLD can receive data / information from the AP MLD, further improving the reliability of communication between the AP MLD and the non-AP MLD.

[0013] In one possible implementation, when the service identifier and link mapping indicate that the second link is closed, the APMLD terminates its transmission with the first non-AP MLD on the second link before Ta; or,

[0014] When the service identifier and link mapping indicate that the second link is open, the AP MLD can only initiate transmission to the first non-AP MLD on the second link after the Tb.

[0015] In one possible implementation, the AP MLD does not initiate a transmission to the first non-AP MLD on the second link if it is later than Ta but earlier than Tb.

[0016] In this implementation, by restricting the AP MLD from initiating transmissions to the first non-AP MLD on the second link when the data is later than Ta but earlier than Tb (e.g., within [Ta, Tb] or within (Ta, Tb)), it can be guaranteed that the non-AP MLD can normally receive data / information from the AP MLD, thus improving the reliability of communication between the AP MLD and the non-AP MLD. It should be noted that this implementation applies regardless of whether the second link is closed or opened.

[0017] In one possible implementation, the second time is the TU boundary on the first link that is closest to the first time.

[0018] In this implementation, the second time is the TU boundary closest to the first time on the first link, which can reduce the time interval between Tb and Ta, thus shortening the period during which the AP MLD cannot initiate transmissions to the non-AP MLD. It should be noted that different values ​​for Tb and Ta are described below, making the implementation scheme of this application more diverse and applicable.

[0019] In one possible implementation, the second time is prior to the first time, and the second time is the TU boundary on the first link that is closest to the first time.

[0020] In one possible implementation, Ta is the difference between the length of the first time and TU, and Tb is the first time; or...

[0021] Ta is the minimum time among all second times corresponding to all first links of the AP MLD, and Tb is the first time.

[0022] In one possible implementation, Ta is the minimum time among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb is the first time.

[0023] In one possible implementation, Ta is the maximum time among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb is the first time.

[0024] In one possible implementation, the second time is after the first time, and the second time is the TU boundary on the first link that is closest to the first time.

[0025] In one possible implementation, Ta is the first time, and Tb is the sum of the lengths of the first time and TU; or...

[0026] Ta is the first time, and Tb is the maximum time among all the second times corresponding to all the first links of the AP MLD.

[0027] In one possible implementation, Ta is the first time, and Tb is the maximum time among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD.

[0028] In one possible implementation, Ta is the first time, and Tb is the minimum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD.

[0029] In one possible implementation, Ta is the minimum time among all second times and / or the first time corresponding to all first links of the AP MLD, and Tb is the maximum time among all second times and / or the first time corresponding to all first links of the AP MLD.

[0030] In one possible implementation, Ta is the minimum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb is the maximum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD.

[0031] In one possible implementation, the first non-AP MLD is all non-AP MLDs that have established multi-link communication with the AP MLD.

[0032] In this implementation, when the first non-AP MLD is all non-AP MLDs that have established multi-link communication with the AP MLD, the values ​​of Ta and Tb are applicable to all non-AP MLDs that have established multi-link communication with the AP MLD. The operation is simple and the scope of application is wide.

[0033] In one possible implementation, the first non-AP MLD is one of the non-AP MLDs that has established multi-link communication with the AP MLD.

[0034] In this implementation, when the first non-AP MLD is one of the non-AP MLDs that have established multi-link communication with the AP MLD, the values ​​of Ta and Tb are applicable to that non-AP MLD that has established multi-link communication with the AP MLD. This can reduce Tb-Ta (i.e., reduce the time interval between Tb and Ta), making the time period during which the AP MLD cannot initiate transmission to the non-AP MLD shorter.

[0035] In one possible implementation, the TU boundary is the time point when the lower 10 bits of the time synchronization function TSF timer are 0.

[0036] In one possible implementation, the first frame is a beacon frame or a probe response frame.

[0037] In this implementation, when the first frame is a beacon frame or a probe response frame, the first frame can be broadcast so that more non-AP MLDs can receive the first frame.

[0038] In one possible implementation, the effective start time of the service identifier and link mapping is indicated by the mapping switch time field in the first frame.

[0039] In one possible implementation, the effective start time of the service identifier and link mapping indicated by different first frames is different.

[0040] Secondly, this application provides a communication method applied to a non-AP MLD, which can be the non-AP MLD itself, or a module or chip within the non-AP MLD. The method includes:

[0041] The non-AP MLD receives at least one first frame on at least one first link, the first frame indicating the start time of the effective mapping of the service identifier and the link;

[0042] The non-AP MLD determines the target effective start time of the service identifier and link mapping based on the at least one first frame.

[0043] In this application, the non-AP MLD may obtain multiple different time information from multiple first links (i.e., the effective start time of the service identifier and link mapping indicated by each of the multiple first frames). Therefore, the non-AP MLD can select one of the multiple different time information as the target effective start time of the service identifier and link mapping. Furthermore, the non-AP MLD can use the selected target effective start time as the time to actually turn on or off a certain link (here, which link is turned on or off can be determined according to the service identifier and link mapping relationship).

[0044] In one possible implementation, the effective start time of the service identifier and link mapping indicated by different first frames is different.

[0045] In one possible implementation, the non-AP MLD determines the effective start time of the service identifier and link mapping based on the at least one first frame, including:

[0046] The non-AP MLD determines a service identifier and link mapping start time from the start times of at least one service identifier and link mapping indicated by at least one first frame as the target start time of the service identifier and link mapping.

[0047] In this implementation, the non-AP MLD can randomly select one from multiple different time information as the target start time for the service identifier and link mapping, making the implementation flexible.

[0048] In one possible implementation, the target effective start time of the service identifier and link mapping is the maximum effective start time among the effective start times of the at least one service identifier and link mapping.

[0049] In this implementation, the non-AP MLD can select the largest one from multiple different time information as the target start time for the service identifier and link mapping, which helps to reduce the time interval between Tb and Ta.

[0050] In one possible implementation, the target effective start time of the service identifier and link mapping is the minimum effective start time among the effective start times of the at least one service identifier and link mapping.

[0051] In this implementation, the non-AP MLD can select the smallest one from multiple different time information as the target start time for the service identifier and link mapping, which helps to reduce the time interval between Tb and Ta.

[0052] In one possible implementation, the first frame is a beacon frame or a probe response frame.

[0053] In this implementation, when the first frame is a beacon frame or a probe response frame, the first frame can be broadcast so that more non-AP MLDs can receive the first frame.

[0054] In one possible implementation, the effective start time of the service identifier and link mapping is indicated by the mapping switch time field in the first frame.

[0055] Thirdly, this application provides a communication device, which may be an AP MLD or a chip in an AP MLD, such as a Wi-Fi chip. The communication device includes: a processing unit for generating at least one first frame; and a transceiver unit for transmitting the at least one first frame on at least one first link; wherein the first frame indicates the effective start time of a service identifier and link mapping; when the service identifier and link mapping indicates that a second link is closed, the AP MLD closes the second link no earlier than time point Tb; or, when the service identifier and link mapping indicates that the second link is open, the AP MLD opens the second link no later than time point Ta; Ta is earlier than Tb, and Ta and / or Tb are determined according to a first time and / or a second time, wherein the first time is the target beacon transmission time TBTT corresponding to the service indication map (DTIM) beacon frame of the third link; when the first link and the third link are the same, the effective start time of the service identifier and link mapping indicated by the first frame transmitted on the first link is the first time; when the first link and the third link are different, the effective start time of the service identifier and link mapping indicated by the first frame transmitted on the first link is the second time, and the second time is the time unit TU boundary on the first link.

[0056] In one possible implementation, when the service identifier and link mapping indicate that the second link is closed, the APMLD, if later than Ta, does not initiate a transmission to the first non-AP MLD on the second link; or,

[0057] When the service identifier and link mapping indicate that the second link is open, the AP MLD will not initiate transmission to the first non-AP MLD on the second link if it is earlier than Tb.

[0058] In one possible implementation, when the service identifier and link mapping indicate that the second link is closed, the APMLD terminates its transmission with the first non-AP MLD on the second link before Ta; or,

[0059] When the service identifier and link mapping indicate that the second link is open, the AP MLD can only initiate transmission to the first non-AP MLD on the second link after the Tb.

[0060] In one possible implementation, the AP MLD does not initiate a transmission to the first non-AP MLD on the second link if it is later than Ta but earlier than Tb.

[0061] In one possible implementation, the second time is the TU boundary on the first link that is closest to the first time.

[0062] In one possible implementation, the second time is prior to the first time, and the second time is the TU boundary on the first link that is closest to the first time.

[0063] In one possible implementation, Ta is the difference between the length of the first time and TU, and Tb is the first time; or...

[0064] Ta is the minimum time among all second times corresponding to all first links of the AP MLD, and Tb is the first time.

[0065] In one possible implementation, Ta is the minimum time among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb is the first time.

[0066] In one possible implementation, Ta is the maximum time among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb is the first time.

[0067] In one possible implementation, the second time is after the first time, and the second time is the TU boundary on the first link that is closest to the first time.

[0068] In one possible implementation, Ta is the first time, and Tb is the sum of the lengths of the first time and TU; or, Ta is the first time, and Tb is the maximum time among all second times corresponding to all first links of the AP MLD.

[0069] In one possible implementation, Ta is the first time, and Tb is the maximum time among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD.

[0070] In one possible implementation, Ta is the first time, and Tb is the minimum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD.

[0071] In one possible implementation, Ta is the minimum time among all second times and / or first times corresponding to all first links of the AP MLD, and Tb is the maximum time among all second times and / or first times corresponding to all first links of the AP MLD.

[0072] In one possible implementation, Ta is the minimum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb is the maximum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD.

[0073] In one possible implementation, the first non-AP MLD is all non-AP MLDs that have established multi-link communication with the AP MLD.

[0074] In one possible implementation, the first non-AP MLD is one of the non-AP MLDs that has established multi-link communication with the AP MLD.

[0075] In one possible implementation, the TU boundary is the time point when the lower 10 bits of the time synchronization function TSF timer are 0.

[0076] In one possible implementation, the first frame is a beacon frame or a probe response frame.

[0077] In one possible implementation, the effective start time of the service identifier and link mapping is indicated by the mapping switch time field in the first frame.

[0078] In one possible implementation, the effective start time of the service identifier and link mapping indicated by different first frames is different.

[0079] Fourthly, this application provides a communication device, which can be a non-AP MLD or a chip in a non-AP MLD, such as a Wi-Fi chip. The communication device includes: a transceiver unit configured to receive at least one first frame on at least one first link, the first frame indicating the effective start time of a service identifier and link mapping; and a processing unit configured to determine a target effective start time of the service identifier and link mapping based on the at least one first frame.

[0080] In one possible implementation, the effective start time of the service identifier and link mapping indicated by different first frames is different.

[0081] In one possible implementation, when determining the effective start time of the service identifier and link mapping based on the at least one first frame, the processing unit is configured to:

[0082] The effective start time of a service identifier and link mapping is determined from the effective start times of at least one service identifier and link mapping indicated by at least one first frame as the target effective start time of the service identifier and link mapping.

[0083] In one possible implementation, the target effective start time of the service identifier and link mapping is the maximum effective start time among the effective start times of the at least one service identifier and link mapping.

[0084] In one possible implementation, the target effective start time of the service identifier and link mapping is the minimum effective start time among the effective start times of the at least one service identifier and link mapping.

[0085] In one possible implementation, the first frame is a beacon frame or a probe response frame.

[0086] In one possible implementation, the effective start time of the service identifier and link mapping is indicated by the mapping switch time field in the first frame.

[0087] Fifthly, this application provides a communication device including a processor for executing a computer program, causing the communication device to perform the method as described in any one of the first or second aspects.

[0088] In one possible design, the communication device may be a chip implementing the method in the first or second aspect, or a device containing a chip.

[0089] In one possible design, the communication device also includes a transceiver. The processor and the transceiver are coupled.

[0090] In one possible design, the communication device also includes a memory. A processor is coupled to the memory, which stores a computer program; the processor is also used to invoke the computer program in the memory.

[0091] In a sixth aspect, this application provides a communication device including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor is used to implement the method as described in any one of the first or second aspects through logic circuits or execution code instructions.

[0092] In a seventh aspect, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed by a computer, implement the method as described in any one of the first or second aspects.

[0093] Eighthly, this application provides a computer program product that, when read and executed by a computer, causes the computer to perform the method described in any one of the first or second aspects.

[0094] Ninthly, this application provides a communication system including an AP MLD and a non-AP MLD, wherein the AP MLD can be used to implement the method described in any one of the first aspects above, and the non-AP MLD is used to implement the method described in any one of the second aspects above.

[0095] The beneficial effects of aspects three through nine can be found in the relevant beneficial effects described in aspects one through two, and will not be repeated here. Attached Figure Description

[0096] Figure 1 This is a schematic diagram of the architecture of the wireless communication system provided in the embodiments of this application;

[0097] Figure 2 This is a schematic diagram of multi-link communication provided in an embodiment of this application;

[0098] Figure 3a This is a schematic diagram illustrating a connection method between an AP MLD and a non-AP MLD provided in an embodiment of this application;

[0099] Figure 3b This is a schematic diagram illustrating another connection method between an AP MLD and a non-AP MLD provided in an embodiment of this application;

[0100] Figure 3c This is a schematic diagram of the antenna for the MLD provided in the embodiments of this application;

[0101] Figure 4a This is a schematic diagram of a communication scenario provided in an embodiment of this application;

[0102] Figure 4b This is a schematic diagram of another communication scenario provided in an embodiment of this application;

[0103] Figure 5 This is a schematic diagram of the frame structure of the TID-to-link mapping element provided in the embodiments of this application;

[0104] Figure 6 This is a schematic diagram illustrating a scenario where the mapping switch time field in the beacon frame indicates the start time of the effective mapping between the service identifier and the link.

[0105] Figure 7 This is a flowchart illustrating the communication method provided in an embodiment of this application;

[0106] Figure 8a This is a schematic diagram of a scenario involving Ta and Tb provided in an embodiment of this application;

[0107] Figure 8b This is another scenario diagram illustrating Ta and Tb provided in the embodiments of this application;

[0108] Figure 8c This is another schematic diagram of Ta and Tb provided in the embodiments of this application;

[0109] Figure 8d This is another schematic diagram of Ta and Tb provided in the embodiments of this application;

[0110] Figure 8e This is another schematic diagram of Ta and Tb provided in the embodiments of this application;

[0111] Figure 9a This is another schematic diagram of Ta and Tb provided in the embodiments of this application;

[0112] Figure 9b This is another schematic diagram of Ta and Tb provided in the embodiments of this application;

[0113] Figure 9c This is another schematic diagram of Ta and Tb provided in the embodiments of this application;

[0114] Figure 9d This is another schematic diagram of Ta and Tb provided in the embodiments of this application;

[0115] Figure 9e This is another schematic diagram of Ta and Tb provided in the embodiments of this application;

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

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

[0118] Figure 12 This is a schematic diagram of the structure of another communication device provided in the embodiments of this application. Detailed Implementation

[0119] To facilitate understanding of the technical solution of this application, the application will be further described below with reference to the accompanying drawings.

[0120] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are used only to distinguish different objects and not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0121] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0122] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. "Or" indicates that there can be two relationships, such as only A exists or only B exists; when A and B are not mutually exclusive, it can also mean that there are three relationships, such as only A exists, only B exists, or both A and B exist simultaneously. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".

[0123] The technical solutions provided in this application can be applied to WLAN systems, such as Wi-Fi. The methods provided in this application can be applied to the IEEE 802.11 series protocols, such as 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, 802.11be, or next-generation protocols, etc., which will not be listed here. The technical solutions provided in this application can also be applied to wireless personal area networks (WPANs) based on ultra-wideband (UWB) technology. The methods provided in this application can be applied to the IEEE 802.15 series protocols, such as 802.15.4a, 802.15.4z, or 802.15.4ab, or a future generation of UWB WPAN protocols, etc., which will not be listed here. The technical solutions provided in this application can also be applied to other types of communication systems, such as Internet of Things (IoT) systems, Vehicle-to-X (V2X) systems, narrowband Internet of Things (NB-IoT) systems, devices applied in V2X systems, IoT nodes and sensors in IoT systems, smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities. Alternatively, they can also be applied to Long Term Evolution (LTE) systems, 5th-generation (5G) communication systems, and new communication systems that will emerge in the future development of communication.

[0124] WLAN systems can provide high-speed, low-latency transmission. As WLAN application scenarios continue to evolve, WLAN systems will be applied to more scenarios or industries, such as the Internet of Things industry, the Internet of Vehicles industry, the banking industry, enterprise offices, stadiums and exhibition halls, concert halls, hotel rooms, dormitories, hospital wards, classrooms, shopping malls, squares, streets, production workshops and warehouses, etc. Of course, devices supporting WLAN communication or sensing (such as access points or sites) can be sensor nodes in smart cities (such as smart water meters, smart electricity meters, and smart air quality monitoring nodes), smart devices in smart homes (such as smart cameras, projectors, displays, televisions, speakers, refrigerators, and washing machines), nodes in the Internet of Things (IoT), entertainment terminals (such as wearable devices for augmented reality (AR) and virtual reality (VR), etc.), smart devices in smart offices (such as printers, projectors, loudspeakers, and speakers), connected vehicle devices in the Internet of Vehicles (IoV), infrastructure in daily life scenarios (such as vending machines, self-service navigation kiosks in supermarkets, self-checkout machines, and self-ordering machines), and equipment in large sports and music venues. For example, access points and sites can be devices used in the Internet of Vehicles (IoV), IoT nodes and sensors in the IoT, smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0125] Although the embodiments of this application primarily use WLAN as an example, especially networks applied to the IEEE 802.11 series of standards, such as systems supporting Wi-Fi 7 (also known as extremely high-throughput, EHT) or Wi-Fi 8 (also known as ultra-high reliability, UHR) or ultra-high reliability and throughput, UHRT, those skilled in the art will readily understand that the various aspects involved in the embodiments of this application can be extended to other networks employing various standards or protocols. For example, Bluetooth, high-performance radio LAN (HIPERLAN) (a wireless standard similar to IEEE 802.11, primarily used in Europe), and wide area networks (WANs) or other networks now known or to be developed in the future. Therefore, regardless of the coverage area and wireless access protocol used, the various aspects provided in the embodiments of this application can be applied to any suitable wireless network.

[0126] A multi-link device includes one or more affiliated sites. The affiliated sites are logical sites and can operate on a single link, frequency band, or channel. The affiliated site can be an Access Point (AP) or a non-AP STA. For ease of description, embodiments of this application may refer to a multi-link device with an AP as an affiliated site as a multi-link AP, a multi-link AP device, or an AP multi-link device (AP MLD). A multi-link device with a non-AP STA as an affiliated site is referred to as a multi-link STA, a multi-link STA device, or a STA multi-link device (STA multi-link device), or a multi-link non-AP, a multi-link non-AP device, or a non-AP multi-link device (non-AP MLD). A multi-link device (which can be either a non-AP MLD or an AP MLD) is a communication device with wireless communication capabilities. The communication device can be a complete machine, or it can be a chip or processing system installed in the complete machine. The device with these chips or processing systems installed can implement the methods and functions of the embodiments of this application under the control of these chips or processing systems.

[0127] Multilink devices can implement wireless communication by following the 802.11 series of protocols, such as Extremely High Throughput (EHT), or 802.11be-based or compatible with 802.11be, thereby enabling communication with other devices, which may or may not be multilink devices.

[0128] Each logical station can operate on one link, allowing multiple logical stations to operate on the same link. A link identifier can represent a single station operating on a link; that is, if there are more than one logical station on a link, more than one link identifier can be used to represent them. Sometimes, the link identifier also represents the station operating on that link. When a multi-link device transmits data with another multi-link device, before communication, the two devices can negotiate or communicate the mapping between link identifiers and a link or stations on that link. Alternatively, the AP MLD can indicate the mapping between link identifiers and a link or stations on that link through broadcast management frames, such as beacon frames. Therefore, in data transmission, it is possible to avoid transmitting a large amount of signaling to indicate links or stations on links; only the link identifier needs to be carried, reducing signaling overhead and improving transmission efficiency.

[0129] The following example illustrates this using one of the aforementioned multi-link devices as an AP MLD and the other as a non-AP MLD. In one example, when the AP MLD establishes a basic service set (BSS), the management frames it sends, such as multi-link probe response frames, carry one or more multi-link elements. The link information fields included in these multi-link elements can be used to establish a correspondence between a link identifier and a station operating on that link.

[0130] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application. Figure 1 As shown, the wireless communication system includes at least one AP MLD (such as...) Figure 1 AP MLD100 and at least one non-AP MLD (such as Figure 1 (The non-AP MLD200 and non-AP MLD300 are optional). Figure 1 This also includes traditional sites that only support transmission over a single link (such as...). Figure 1 The single-link non-AP STA400 (also known as STA400) is used in this context. The AP MLD provides services to the non-AP MLD. Multiple links can be used between the non-AP MLD and the AP MLD to improve throughput. A STA within a non-AP MLD can also communicate with an AP within an AP MLD via a single link. Understandably... Figure 1 The number of AP MLDs and non-AP MLDs is merely illustrative.

[0131] Optional, please see Figure 2 , Figure 2 This is a schematic diagram of multi-link communication provided in an embodiment of this application. For example... Figure 2As shown, the AP MLD includes AP1, AP2, ..., APn, and the non-AP MLD includes STA1, STA2, ..., STAN. Here, n is a positive integer. AP MLDs and non-AP MLDs can communicate in parallel using links 1, 2, ..., n. STA1 in the non-AP MLD establishes an association with AP1 in the AP MLD, STA2 in the non-AP MLD establishes an association with AP2 in the AP MLD, STAN in the non-AP MLD establishes an association with APn in the AP MLD, and so on. Thus, communication can occur after one or more STAs in the non-AP MLD establish an association with one or more APs in the AP MLD. The operating frequency bands of multi-link devices (including AP MLDs and non-AP MLDs) can include, but are not limited to: sub-1GHz, 2.4GHz, 5GHz, 6GHz, and high-frequency 60GHz. For example, the methods provided in this application embodiment can be applied to, but are not limited to: single-user uplink / downlink transmission, multi-user uplink / downlink transmission, vehicle-to-everything (V2X, where X can represent anything), and device-to-device (D2D). For instance, the V2X can include: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-network (V2N) communication, etc.

[0132] Figure 3a and Figure 3b This is a schematic diagram illustrating a connection method between an AP MLD and a non-AP MLD provided in an embodiment of this application. The 802.11 standard focuses on the 802.11 physical layer (PHY) and medium access control (MAC) layer portions of multi-link devices; therefore... Figure 3a and Figure 3b The PHY and MAC layers are shown only as examples.

[0133] like Figure 3a and Figure 3b As shown, multi-link devices (such as AP MLD and non-AP MLD) may include physical layer (PHY) processing circuitry (such as... Figure 3aThe PHY#1, PHY#2, and PHY#n shown are the medium access control (MAC) layer processing circuits. The physical layer processing circuits can be used to process physical layer signals, and the MAC layer processing circuits can be used to process MAC layer signals. Furthermore, the MAC layer can be further divided into a high-MAC layer (such as...). Figure 3a The high MAC shown, such as Figure 3b The diagram shows high MAC #1 to high MAC #n and multiple low-MAC layers (such as...). Figure 3a and Figure 3b The diagram shows low MAC#1, low MAC#2 to low MAC#n. Figure 3a As shown, in an AP MLD, multiple APs operate independently at the low MAC layer and PHY, sharing the high MAC layer. Similarly, in a non-AP MLD, multiple STAs operate independently at the low MAC layer and PHY, sharing the high MAC layer. The high MAC layer is connected to multiple low MAC layers, meaning the high MAC layer is shared by multiple links. Figure 3b As shown, the multiple APs in an AP MLD are independent of each other at both the low MAC layer and PHY layer, and also at the high MAC layer. Similarly, the multiple STAs in a non-APMLD device are independent of each other at both the low MAC layer and PHY layer, and also at the high MAC layer. For example, the high MAC layer primarily handles the allocation of sequence numbers (SN) and packet numbers (PN) for MAC service data units (MSDUs), as well as encryption and decryption operations. For example, the low MAC layer primarily handles the assembly of MAC protocol data units (MPDUs) for each link, channel access, packet transmission, and reception acknowledgment.

[0134] exist Figure 3aIn an AP MLD, the PHY#1 layer, low MAC#1 layer, and high MAC layer can be considered as AP#1, the PHY#2 layer, low MAC#2 layer, and high MAC layer can be considered as AP#2, ..., the PHY#n layer, low MAC#n layer, and high MAC layer can be considered as AP#n. This means the AP MLD can be understood as containing n AP entities. In a non-AP MLD, the situation is similar; the high MAC layer is also shared by multiple links. The PHY#1 layer, low MAC#1 layer, and high MAC layer are considered as STA#1, the PHY#2 layer, low MAC#2 layer, and high MAC layer are considered as STA#2, ..., the PHY#n layer, low MAC#n layer, and high MAC layer are considered as STA#n. This means the non-AP MLD can be understood as containing n STA entities. For example... Figure 3a As shown, PHY#1 of AP#1 in the AP MLD and PHY#1 of STA#1 in the non-AP MLD are connected, and AP#1 in the AP MLD and STA#1 in the non-AP MLD are connected via a link (e.g., Figure 3a The link shown (#1) enables communication; the PHY#2 of AP#2 in the AP MLD and the PHY#2 of STA#2 in the non-AP MLD are connected, and AP#2 in the AP MLD and STA#2 in the non-AP MLD are connected via a link (such as... Figure 3a The link shown (#2) enables communication; the PHY#n of AP#n in the AP MLD and the PHY#n of STA#n in the non-AP MLD are connected, and the AP#n in the AP MLD and the STA#n in the non-AP MLD are connected via a link (such as...). Figure 3a The link shown (#n) enables communication. Regarding... Figure 3b The explanation can be found here. Figure 3a This will not be elaborated upon here.

[0135] For example, the high MAC layer or the low MAC layer can be implemented by a processor in the chip system of a multi-link device, or they can be implemented by different processing modules in a single chip system, etc., which will not be listed in the embodiments of this application. It is understood that... Figure 3a and Figure 3b This can be understood as dividing multi-link devices into functional modules. Figure 3a and Figure 3b The modules shown can be implemented in hardware or as software functional modules. Figure 3a and Figure 3b The PHY and MAC layers shown can be understood as a division of logical functions, but in actual implementation there may be other ways of division. Figure 3a and Figure 3bThe n shown can be equal to 0, or equal to 1, or an integer greater than 1, etc.

[0136] For example, the multi-link device in the embodiments of this application can be a single-antenna device or a multi-antenna device. For instance, it can be a device with two or more antennas. The embodiments of this application do not limit the number of antennas included in the multi-link device. Figure 3c This is a schematic diagram of the antenna for the MLD provided in the embodiments of this application. Figure 3c The example used is AP MLD with multiple antennas and non-AP MLD with a single antenna, but it should not be construed as a limitation on the embodiments of this application.

[0137] The frequency bands in which multi-link devices can operate may include, but are not limited to: sub 1GHz, 2.4GHz, 5GHz, 6GHz and high frequency 60GHz. Figure 4a , Figure 4b Two schematic diagrams are shown illustrating how multi-link devices in a wireless local area network communicate with other devices through multiple links.

[0138] Figure 4a A scenario of communication between AP MLD101 and non-AP MLD 102 is shown. AP MLD101 includes AP101-1 and AP101-2, and non-AP MLD 102 includes STA102-1 and STA102-2. AP MLD101 and non-AP MLD 102 communicate in parallel using link 1 and link 2.

[0139] For example, Figure 4bThe diagram illustrates a scenario where AP MLD 101 communicates with non-AP MLD 102, non-AP MLD 103, and STA 104. AP MLD 101 includes subordinate APs 101-1 to AP101-3; non-AP MLD 102 includes three subordinate STAs: STA 102-1, STA 102-2, and STA 102-3; non-AP MLD 103 includes two subordinate STAs: STA 103-1 and STA 103-2; and STA 104 is a single-link device, including STA 104-1. AP MLD 101 can communicate with non-AP MLD 102 using links 1, 2, and 3 respectively; communicate with non-AP MLD 103 using links 2 and 3; and communicate with STA 104 using link 1. In one example, STA104 operates in the 2.4 GHz band; in non-AP MLD 103, STA 103-1 operates in the 5 GHz band, and STA 103-2 operates in the 6 GHz band; in non-AP MLD 102, STA 102-1 operates in the 2.4 GHz band, STA 102-2 operates in the 5 GHz band, and STA 102-3 operates in the 6 GHz band. AP 101-1 in AP MLD 101, operating in the 2.4 GHz band, can transmit uplink or downlink data with STA 104 and STA 102-1 in non-AP MLD 102 via Link 1. AP 101-2, operating in the 5GHz band within AP MLD 101, can transmit uplink or downlink data with STA103-1, operating in the 5GHz band within non-AP MLD 103, via link 2. It can also transmit uplink or downlink data with STA102-2, operating in the 5GHz band within non-AP MLD 102, via link 2. Similarly, AP 101-3, operating in the 6GHz band within AP MLD 101, can transmit uplink or downlink data with STA102-3, operating in the 6GHz band within non-AP MLD 102, via link 3. It can also transmit uplink or downlink data with STA 103-2 within the non-AP MLD via link 3.

[0140] Figure 4a Only two frequency bands are shown to be supported by the AP MLD. Figure 4bThis illustration focuses on the AP MLD 101, which supports three frequency bands (2.4GHz, 5GHz, and 6GHz), with each band corresponding to one link. The AP MLD 101 can operate on one or more links from Link 1, Link 2, or Link 3. On the AP or STA side, a link can also be understood as a station operating on that link. In practical applications, AP MLDs and non-AP MLDs can support more or fewer frequency bands, meaning they can operate on more or fewer links. This embodiment does not impose any limitations on this. Figure 4a and Figure 4b This is merely a simple illustration and does not constitute any limitation on the scope of protection of the embodiments of this application.

[0141] The relevant technical features involved in the embodiments of this application are explained below. It should be noted that these explanations are for the purpose of making the embodiments of this application easier to understand, and should not be regarded as a limitation on the scope of protection claimed by this application.

[0142] 1. Service Identifier and Link Mapping Element (TID-to-link mapping element)

[0143] If no service identifier and link mapping operation is performed between the multi-link devices during the multi-link establishment process, then by default all service identifiers are mapped to each established link, meaning that each established link can transmit all service types.

[0144] During the establishment of multiple links, service identifiers can be mapped to links between the devices on those links. For example, the AP MLD can carry the mapping information between service identifiers and links in beacon frames or probe response frames, allowing all stations to adopt the appropriate mapping method upon receiving this information. Carrying this mapping information through beacon frames or probe response frames is also known as a broadcast mapping between TIDs and links, which can effectively improve signaling transmission efficiency.

[0145] For example, the mapping information between service identifiers and links can be carried in the TID-to-link mapping element. See also... Figure 5 , Figure 5 This is a schematic diagram of the frame structure of the TID-to-link mapping element provided in an embodiment of this application. For example... Figure 5As shown, the TID-to-link mapping element may include at least one of the following fields: element ID, length, element ID extension (or element ID extension), service identifier and link mapping control, mapping switch time, and expected duration (or expected duration, desired duration, required duration, etc.). Optionally, the TID-to-link mapping element may also include at least one of the following fields: link mapping of TID 0, ..., link mapping of TID 7.

[0146] For example, the mapping switch time field can be used to indicate the effective start time (or effective time, mapping effective time, etc.) of the service identifier-to-link mapping, or to indicate the effective start time (or effective time, mapping effective time, etc.) of the mapping relationship between the service identifier and the link, or to indicate the time when the mapping relationship between the service identifier and the link is established. This mapping switch time field exists when the TID-to-link mapping element is carried in the beacon frame or probe response frame. When the above mapping relationship has already taken effect, the beacon frame or probe response frame may not carry the mapping switch time field.

[0147] Furthermore, the value carried by the mapping switch time field can be determined based on the target beacon transmission time (TBTT) of a future delivery traffic indication map (DTIM) beacon frame. Optionally, TBTT can also be described as the target transmission time. The time precision of TBTT is in time units (TU), 1TU = 1024µs. Generally, the AP MLD broadcasts the value of the time synchronization function (TSF) timer in the beacon frame. After receiving the TSF timer value, the non-AP MLD can update its locally maintained system time to the TSF timer value, so as to achieve the purpose of time synchronization (i.e., time synchronization) between all non-AP MLDs in this BSS and the AP MLD.

[0148] For example, the value carried by the mapping switch time field can be set to bits 11 to 26 of the TSF timer corresponding to the new mapping relationship when it takes effect, i.e., TSF[10:25] (bits 10 to 25 of the TSF). The TSF timer can be understood as a time value with a length of 64 bits and a unit of microseconds (µs). For example, the TSF timers corresponding to all non-AP MLDs on a link can be the same, while the TSF timers corresponding to non-AP MLDs on different links can be different.

[0149] For example, the expected duration field can be used to indicate the expected end time of the service identifier-link mapping relationship, or to indicate the expected end time of the service identifier-link mapping. For instance, the expected duration field can be used to indicate the effective duration of the service identifier-link mapping (when the TID-to-link mapping element carries a mapping switch time field), or the remaining time (when the TID-to-link mapping element does not carry a mapping switch time field). The expected duration field exists when the TID-to-link mapping element is carried in a beacon frame or probe response frame.

[0150] For example, the "link mapping of TID 0" field indicates which links TID 0 is mapped to. This field can carry a bitmap, where each bit corresponds to a link. A bit value of 1 indicates that TID 0 is mapped to the link corresponding to that bit. Conversely, a bit value of 0 indicates that TID 0 is not mapped to the link corresponding to that bit. For example, the length of the bitmap can be equal to the maximum number of links that can be associated between multiple link devices; or, the length can be a fixed value, such as 16 bits; or, the length can be equal to the number of established association links between multiple link devices, etc. This application embodiment does not limit the method of setting the length of the bitmap. For explanations of link mapping fields for other ITDs, please refer to the "link mapping of TID 0" field; details will not be provided here. The TID0 to TID7 examples shown in this application are merely examples. As the standard evolves, more service types may emerge, such as TID0 to TID15. Therefore, this application does not limit the number of link mapping fields for a TID in a TID-to-link mapping element. For instance, the number of link mapping fields for a TID in this TID-to-link mapping element can be the same as the number of TID types. For example, when the TID is expanded from TID0 to TID7 to TID0 to TID15, the number of link mapping fields for the TID can be equal to 16.

[0151] When a link has a TID mapped to it, it can be understood as the link being enabled; when no TID is mapped to a link, it can be understood as the link being disabled. AP MLDs can enable or disable a link by carrying a TID-to-Link Mapping element in beacon frames or probe response frames.

[0152] Understandably, for unicast, when the communicating parties negotiate the mapping information between the service identifier and the link, this mapping information generally takes effect immediately. Since the mapping switch time and expected duration fields need to be sent multiple times in the beacon frame or probe response frame to ensure that one or more non-AP MLDs can receive the TID-to-link mapping element, these fields typically exist when the TID-to-link mapping element is carried in the beacon frame or probe response frame.

[0153] For example, please refer to the following: Figure 5The TID-To-link mapping control field may include at least one of the following fields: direction, default link mapping, mapping switch time present, expected duration present, reserved, and link mapping presence indicator. Optionally, the TID-To-link mapping control field may also include a link mapping presence indicator field. The TID-To-link mapping control field can be used to carry control information related to the service identifier and link mapping. For example, the TID-To-link mapping control field is described as follows: the direction field can be used to indicate whether the service direction is uplink, downlink, or both; the default link mapping field can be used to indicate whether the default mapping method is used; the mapping switch time present field can be used to indicate whether the mapping switch time field exists; the expected duration present field is used to indicate whether the expected duration field exists; and the link mapping presence indicator field is used to indicate which of the eight fields (link mapping of TID 0 to link mapping of TID 7) exist and which do not.

[0154] It is understandable that when the default link mapping field is used to indicate the use of the default mapping method, it means that by default all service identifiers can be mapped to every established link. The TID-To-link mapping control field may not include the link mapping existence indication, and the TID-to-link mapping element may not include the link mapping fields from TID 0 to TID 7.

[0155] It is understood that the mapping information between service identifiers and links, the mapping relationship between service identifiers and links (or simply the mapping relationship), and the mapping between service identifiers and links involved in the embodiments of this application can be substituted for each other. The mapping relationship between service identifiers and links indicated by the TID-to-link mapping element involved in the embodiments of this application can be simply referred to as the mapping relationship (or mapping information) indicated by the TID-to-link mapping element.

[0156] 2. TU boundary

[0157] In this embodiment of the application, the TU boundary is the time point when the lower 10 bits of the TSF timer are 0.

[0158] As can be seen from the above introduction, the current AP MLD can indicate the effective start time of the service identifier and link mapping through the mapping switch time field in the TID-to-Link Mapping element carried in the beacon frame or probe response frame. The effective start time of the service identifier and link mapping can be the TBTT indicated by the DTIM beacon frame of any link. Understandably, the TBTT on a certain link (e.g., link 1) is the TU boundary of that link, but it is not necessarily the TU boundary of other links (e.g., link 2, link 3, etc.). This is because the values ​​of the TSF timers on different links are selected independently. When the lower 10 bits of the TSF timer on a certain link (e.g., link 1) are 0, the lower 10 bits of the TSF timer on another link are not necessarily 0. The mapping switch time field in the TID-to-Link Mapping element can only indicate the time precision of TU. This means that the mapping switch time field in the TID-to-Link Mapping element on one link cannot indicate the TU boundary on another link, and therefore cannot indicate the TBTT of another link. In other words, the AP MLD cannot accurately indicate the effective start time of the service identifier and link mapping, which is not conducive to reliable communication between the AP MLD and non-AP MLD.

[0159] For example, see Figure 6 , Figure 6 This is a schematic diagram illustrating a scenario where the mapping switch time field in the beacon frame indicates the start time of the effective mapping between the service identifier and the link. For example... Figure 6As shown, if the AP MLD considers the effective start time of the service identifier and link mapping to be the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0. However, if the AP MLD sends a beacon frame on link 1, then the Mapping Switch Time field in the TID-to-Link Mapping element of the beacon frame sent by the AP MLD on link 1 can only indicate the TU boundary of link 1, for example... Figure 6 The timing of the service identifier and link mapping, such as time point t1 (or t2), can lead to the non-AP MLD interpreting the effective start time as t1 (or t2), which deviates from the actual time point t0. Understandably, when this deviation occurs, the AP MLD and non-AP MLD will have inconsistent understandings of the effective start time, resulting in unreliable communication between them. For example, suppose the service identifier and link mapping indicate the closure of a link (e.g., link3), and the non-AP MLD interprets the effective start time as later than the AP MLD. In this case, the AP MLD may have already closed link3, but the non-AP MLD has not. The non-AP MLD may continue to send data or information to the AP MLD, but the AP MLD will be unable to reply with acknowledgment frames, thus causing communication reliability issues. For example, suppose the service identifier and link mapping indicate that a link3 will be opened, and the effective start time perceived by the non-AP MLD is later than that perceived by the AP MLD. In this case, the AP MLD has already opened link3, but the non-AP MLD has not yet opened link3. When the AP MLD initiates transmission to the non-AP MLD before the non-AP MLD has opened link3, the non-AP MLD will not be able to receive the data or information sent by the AP MLD normally, resulting in low communication reliability.

[0160] Based on this, existing technologies propose adding an offset field to the TID-to-Link Mapping element to indicate the deviation value, for example, using Figure 6Taking the scenario shown as an example, based on the existing technology, the indicated deviation value can be (t0-t1) (or (t0-t2)). Therefore, when the non-AP MLD receives the TID-to-Link Mapping element in the beacon frame, combined with the t1 (or t2) indicated by the Mapping Switch Time field in the TID-to-Link Mapping element, and the deviation value (t0-t1) (or deviation value (t0-t2)) indicated by the offset field, the actual effective start time can be determined to be t0. That is, the effective start time of the service identifier and link mapping as perceived by the non-AP MLD is t0. Although the existing technology can ensure that the AP MLD and non-AP MLD have a consistent understanding of the effective start time of the service identifier and link mapping, the existing technology's method of adding a field increases the signaling overhead. Therefore, this application proposes another method that does not require adding a field and can solve the problem of inconsistent understanding of the effective start time of the service identifier and link mapping between the AP MLD and non-AP MLD, thereby improving the communication reliability between the AP MLD and non-AP MLD.

[0161] It should be noted that in the following embodiments of this application, "the effective start time of the service identifier and link mapping" can also be abbreviated as "effective start time", and "the target effective start time of the service identifier and link mapping" can also be abbreviated as "target effective start time".

[0162] The communication method and communication device provided in this application are described in detail below:

[0163] Please see Figure 7 , Figure 7 This is a flowchart illustrating the communication method provided in an embodiment of this application. Figure 7 As shown, the communication method includes the following steps S701 to S702. Figure 7 The method shown can be implemented by either AP MLD or non-AP MLD, or... Figure 7 The method shown can be executed by a chip in an AP MLD or a chip in a non-AP MLD. For ease of description, Figure 7 This explanation primarily uses AP MLD and non-AP MLD as examples of the methods' execution. It should be noted that... Figure 7 This is a schematic flowchart illustrating an embodiment of the method of this application, showing the detailed communication steps or operations of the method. However, these steps or operations are merely examples, and other operations may be performed in the embodiments of this application. Figure 7 Variations of various operations within it. Furthermore, Figure 7Each step in the process can be followed separately according to... Figure 7 The different orders presented may be executed, and it is possible that they are not intended to be executed. Figure 7 All operations within. Among them:

[0164] S701 and AP MLD can transmit at least one first frame on at least one first link. Correspondingly, non-APMLD can receive at least one first frame on at least one first link.

[0165] For example, before transmitting at least one first frame on at least one first link, the AP MLD may also generate the at least one first frame. Therefore, the AP MLD may transmit one first frame of the at least one first frame on each of the at least one first link. That is, for the at least one first frame generated, each first frame in the at least one first frame may be transmitted through one first link respectively. Optionally, the at least one first link may include a third link.

[0166] The first frame can indicate the effective start time of the service identifier and link mapping, and the at least one first frame can indicate at least one effective start time. For example, different first frames can indicate different effective start times for the service identifier and link mapping. Here, different effective start times can be understood as completely different effective start times or partially different effective start times; this application does not impose any restrictions on this. For instance, suppose there are three first links, link1-1, link1-2, and link1-3. First frame 1 is sent on link1-1, first frame 2 is sent on link1-2, and first frame 3 is sent on link1-3. First frame 1 indicates effective start time 1, first frame 2 indicates effective start time 2, and first frame 3 indicates effective start time 3. Effective start time 1, effective start time 2, and effective start time 3 can be different (or mutually different / completely different), i.e., effective start time 1 ≠ effective start time 2 ≠ effective start time 3. Optionally, effective start time 1, effective start time 2 and effective start time 3 can be partially the same and partially different. For example, effective start time 1 = effective start time 2 ≠ effective start time 3.

[0167] The first frame mentioned above can specifically be a beacon frame or a probe response frame, etc., and this application does not impose any restrictions on it. The effective start time of the service identifier and link mapping can be indicated by the mapping switch time field in the first frame. Optionally, the mapping switch time field can be carried in the TID-to-Link mapping element included in the first frame.

[0168] S702, non-AP MLD determines the target effective start time of service identifier and link mapping based on at least one first frame.

[0169] In some feasible implementations, the non-AP MLD determining the target effective start time of the service identifier and link mapping based on at least one first frame can be understood as follows: the non-AP MLD can determine an effective start time as the target effective start time of the service identifier and link mapping from at least one effective start time indicated by at least one first frame, wherein:

[0170] In one implementation, the non-AP MLD can randomly select an effective start time from at least one effective start time indicated by at least one first frame received as the target effective start time for the service identifier-link mapping. Alternatively, the non-AP MLD can select any one of the at least one effective start time indicated by at least one first frame received.

[0171] In one implementation, the non-AP MLD can select the maximum effective start time from at least one effective start time indicated by at least one received first frame as the target effective start time for the service identifier-link mapping. That is, the target effective start time for the service identifier-link mapping is the maximum effective start time among the at least one effective start time obtained.

[0172] In one implementation, the non-AP MLD can select the minimum effective start time from at least one effective start time indicated by at least one received first frame as the target effective start time for the service identifier and link mapping. That is, the target effective start time for the service identifier and link mapping is the minimum effective start time among the at least one obtained effective start time.

[0173] The following details the processing rules proposed in this application to address the inconsistency in the understanding of the effective start time of service identifiers and link mappings between AP MLDs and non-AP MLDs. The general idea of ​​these processing rules is as follows: APMLDs determine a time period [Ta, Tb], and ensure that the effective time selected by any non-AP MLD falls within this time period, where time point Ta is earlier than time point Tb. For ease of description, this application will refer to time point Ta as Ta and time point Tb as Tb in the following embodiments. Specifically, it includes one or more of the following rules:

[0174] Rule 1: When the service identifier and link mapping in the first frame indicate that a certain link (for ease of description, this application uses the second link as an example for illustration) is disabled, the AP MLD shall disable the second link no earlier than Tb.

[0175] Rule 2: When the service identifier and link mapping in the first frame indicate that the second link is enabled, the AP MLD shall enable the second link no later than Ta.

[0176] Rule 3: When the service identifier and link mapping in the first frame indicate that the second link is closed, the AP MLD will not initiate transmission to the first non-AP MLD on the second link if the transmission is later than Ta. Rule 4: When the service identifier and link mapping in the first frame indicate that the second link is open, the AP MLD will not initiate transmission to the first non-AP MLD on the second link if the transmission is earlier than Tb.

[0177] Rule 5: When the service identifier and link mapping in the first frame indicate that the second link is closed, the transmission with the first non-AP MLD on the second link shall end before Ta (i.e., when the service identifier and link mapping in the first frame indicate that the second link is closed, the AP MLD shall end the transmission with the first non-AP MLD on the second link before Ta).

[0178] Rule 6: When the service identifier and link mapping in the first frame indicate that the second link is open, transmission can only be initiated on the second link to the first non-AP MLD if it is later than Tb (i.e., when the service identifier and link mapping in the first frame indicate that the second link is open, the AP MLD can only be initiated on the second link to the first non-AP MLD if it is after Tb).

[0179] Rule 7: If the AP MLD is later than Ta but earlier than Tb, it shall not initiate a transmission to the first non-AP MLD on the second link.

[0180] Understandably, if, according to the instructions of the service identifier and link mapping, no service identifier (TID) is mapped to a link in any direction (including uplink and downlink), then that link will be closed; if, according to the instructions of the service identifier and link mapping, there exists a service identifier (TID) that is mapped to a link in any direction (including uplink and downlink), then that link will be opened.

[0181] It should be noted that in the embodiments of this application, "not earlier than" can also be replaced with descriptions such as "later than", "greater than", or "greater than or equal to". Correspondingly, "not later than" can also be replaced with descriptions such as "earlier than", "less than", or "less than or equal to", and this application does not impose any restrictions on this.

[0182] It should be noted that the aforementioned Ta and / or Tb can be determined based on the first time and / or the second time. The first time refers to the TBTT corresponding to the DTIM beacon frame of the third link. In other words, the effective time of the service identifier and link mapping is referenced to the TBTT corresponding to the DTIM beacon frame of the third link. Furthermore, the first time in this embodiment can be understood as a reference time. Optionally, the aforementioned DTIM beacon frame of the third link can also be other non-DTIM beacon frames on the third link; this is not limited here. For ease of understanding, this application mainly uses the TBTT corresponding to the DTIM beacon frame of the third link as an example for illustrative explanation.

[0183] Understandably, when any one of the first links is a third link, the effective start time of the service identifier and link mapping indicated by the first frame sent on that first link is the first time (e.g., Figure 6 In the context of t0), when any of the at least one first link is not a third link, the effective start time of the service identifier and link mapping indicated by the first frame transmitted on that first link is the second time, which is the TU boundary on that first link. For ease of description, the following explanation will mainly use one of the at least one first links as an example to illustrate the concept of the second time on that first link involved in this application.

[0184] Optionally, the first interpretation of the second time as the TU boundary on the first link is: the second time is the TU boundary on the first link that is closest to the first time (e.g., Figure 6 (t1 or t2 in the text).

[0185] Optionally, a second interpretation of the second time as the TU boundary on the first link is: the second time can be prior to the first time, and the second time is the TU boundary on the first link closest to the first time (e.g., Figure 6 (t1 in the middle).

[0186] Optionally, a third interpretation of the second time as the TU boundary on the first link is: the second time is after the first time, and the second time is the TU boundary on the first link closest to the first time (e.g., Figure 6 (t2 in the middle).

[0187] The values ​​of Ta and Tb are explained below for different situations:

[0188] It should be noted that the first time (or second time) corresponding to the first link in this application can be understood as: the effective start time of the first frame sent by the AP MLD on the first link.

[0189] Scenario 1: The first non-AP MLD is all non-AP MLDs that have established multi-link communication with the AP MLD. In other words, the statement "do not initiate transmissions to the first non-AP MLD on the second link" can be understood as: do not initiate transmissions to any non-AP MLD that has established multi-link communication with the AP MLD on the second link. It should be noted that in Scenario 1, the values ​​of Ta and Tb apply to all non-AP MLDs that have established multi-link communication with the AP MLD.

[0190] Scenario 1: When the second time is before the first time (i.e., the second time is less than the first time), and the TU boundary on the first link is closest to the first time:

[0191] The values ​​of Ta and Tb are determined as follows: 1.1 Ta is determined based on the first time and the length of TU, ​​and Tb is determined based on the first time. For example, the length of 1TU is 1024µs. For instance, Ta is the difference between the length of the first time and the length of TU (i.e., Ta = first time - 1TU), and Tb is the first time (i.e., Tb = first time).

[0192] For example, please see Figure 8a , Figure 8a This is a schematic diagram of a scenario involving Ta and Tb provided in an embodiment of this application. For example... Figure 8a As shown, it is assumed that the effective start time of the service identifier and link mapping is based on the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0, meaning the first time is t0. It is assumed that all first links of the AP MLD are as follows... Figure 8a The diagram shows links 1-1, 1-2, and 1-3. In scenario 1, for the first frame transmitted on link 1-1, the effective start time of the service identifier and link mapping indicated by this first frame is time point t1; for the first frame transmitted on link 1-2, the effective start time of the service identifier and link mapping indicated by this first frame is time point t3; and for the first frame transmitted on link 1-3, the effective start time of the service identifier and link mapping indicated by this first frame is time point t5. That is, the first time is t0, and the second time includes t1, t3, and t5. If Ta = first time - 1TU, and Tb = first time, then the positions of Ta and Tb are as follows: Figure 8a The locations of Ta and Tb are shown.

[0193] The values ​​of Ta and Tb are determined as follows: 1.2. Ta is determined based on the minimum time among all second times corresponding to all first links of the AP MLD, and Tb is determined based on the first time. For example, Ta is the minimum time among all second times corresponding to all first links of the AP MLD (i.e., Ta = the minimum value among all second times corresponding to all first links of the AP MLD), and Tb is the first time (i.e., Tb = the first time). Optionally, the first non-AP MLD refers to all non-AP MLDs that have established multi-link communication with the AP MLD.

[0194] For example, please see Figure 8b , Figure 8b This is another scenario diagram illustrating Ta and Tb provided in the embodiments of this application. For example... Figure 8b As shown, it is assumed that the effective start time of the service identifier and link mapping is based on the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0, meaning the first time is t0. All first links of the AP MLD are as follows: Figure 8b ① shows links 1-1, 1-2, and 1-3. In scenario 1, for the first frame sent on link 1-1, the effective start time of the service identifier and link mapping indicated by this first frame is time point t1; for the first frame sent on link 1-2, the effective start time of the service identifier and link mapping indicated by this first frame is time point t3; and for the first frame sent on link 1-3, the effective start time of the service identifier and link mapping indicated by this first frame is time point t5. That is, the first time is t0, and the second times include t1, t3, and t5. If Ta = the minimum value among all second times corresponding to all first links in the AP MLD, and Tb = the first time, then the positions of Ta and Tb are as follows: Figure 8b The locations of Ta and Tb are shown, where the minimum value of all second times corresponding to all first links of AP MLD is t1 (because t1 < t3 < t5).

[0195] Scenario 2: When the second time is after the first time (i.e., the second time is greater than the first time), and the TU boundary on the first link is closest to the first time:

[0196] 2.1 The values ​​of Ta and Tb are determined based on the first time, and Tb is determined based on the first time and the length of TU. For example, Ta is the first time (i.e., Ta = first time), and Tb is the sum of the lengths of the first time and TU (i.e., Tb = first time + 1TU).

[0197] For example, please see Figure 8c , Figure 8cThis is another schematic diagram illustrating Ta and Tb provided in the embodiments of this application. For example... Figure 8c As shown, it is assumed that the effective start time of the service identifier and link mapping is based on the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0, meaning the first time is t0. All first links of the AP MLD are as follows: Figure 8c The diagram shows links 1-1, 1-2, and 1-3. In scenario 2, for the first frame transmitted on link 1-1, the effective start time of the service identifier and link mapping indicated by this first frame is time point t2; for the first frame transmitted on link 1-2, the effective start time of the service identifier and link mapping indicated by this first frame is time point t4; and for the first frame transmitted on link 1-3, the effective start time of the service identifier and link mapping indicated by this first frame is time point t6. That is, the first time is t0, and the second time includes t2, t4, and t6. If Ta = the first time and Tb = the first time + 1TU, then the positions of Ta and Tb are as follows: Figure 8c The locations of Ta and Tb are shown.

[0198] 2.2. The values ​​of Ta and Tb are determined as follows: Ta is determined based on the first time, and Tb is determined based on the maximum time among all second times corresponding to all first links of AP MLD. For example, Ta is the first time (i.e., Ta = first time), and Tb is the maximum time among all second times corresponding to all first links of AP MLD (i.e., Tb = the maximum value among all second times corresponding to all first links of AP MLD).

[0199] For example, please see Figure 8d , Figure 8d This is another schematic diagram illustrating Ta and Tb provided in the embodiments of this application. For example... Figure 8d As shown, it is assumed that the effective start time of the service identifier and link mapping is based on the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0, meaning the first time is t0. All first links of the AP MLD are as follows: Figure 8dThe diagram shows links 1-1, 1-2, and 1-3. In scenario 2, for the first frame transmitted on link 1-1, the effective start time of the service identifier and link mapping indicated by this first frame is time point t2; for the first frame transmitted on link 1-2, the effective start time of the service identifier and link mapping indicated by this first frame is time point t4; and for the first frame transmitted on link 1-3, the effective start time of the service identifier and link mapping indicated by this first frame is time point t6. That is, the first time is t0, and the second time includes t2, t4, and t6. If Ta = the first time and Tb = the first time + 1TU, then the positions of Ta and Tb are as follows: Figure 8d The locations of Ta and Tb are shown, where the maximum value of all second times corresponding to all first links of AP MLD is t6 (because t2 < t4 < t6).

[0200] Scenario 3: When the second time is the TU boundary closest to the first time on the first link (i.e., the second time may be greater than or less than the first time):

[0201] 3.1 The values ​​of Ta and Tb are determined as follows: Ta is determined based on the minimum time among all second times and / or first times corresponding to all first links of AP MLD, and Tb is determined based on the maximum time among all second times and / or first times corresponding to all first links of AP MLD. For example, Ta is the minimum time among all second times and / or first times corresponding to all first links of AP MLD (i.e., Ta = the minimum value among all second times and / or first times corresponding to all first links of AP MLD), and Tb is the maximum time among all second times and / or first times corresponding to all first links of AP MLD (i.e., Tb = the maximum value among all second times and / or first times corresponding to all first links of AP MLD).

[0202] It should be noted that, under this method of taking the values ​​of Ta and Tb 3.1, the above rule one can also be described as follows: when the service identifier and link mapping in the first frame indicate that the second link is disabled, the time when the AP MLD disables the second link is no earlier than any of the second times and / or first times corresponding to all the first links of the AP MLD.

[0203] Optionally, under this method of taking the values ​​of Ta and Tb 3.1, the above rule two can also be described as follows: when the service identifier and link mapping in the first frame indicate that the second link is enabled, the time when the AP MLD enables the second link is no later than any of the second times and / or first times corresponding to all the first links of the AP MLD.

[0204] Optionally, under this method of taking the values ​​of Ta and Tb 3.1, the above rule 3 can also be described as follows: When the service identifier and link mapping in the first frame indicate that the second link is closed, the AP MLD will not initiate transmission to the first non-AP MLD on the second link after any of the second times and / or first times corresponding to all the first links of the AP MLD.

[0205] Optionally, under this method of taking the values ​​of Ta and Tb 3.1, the above rule four can also be described as follows: When the service identifier and link mapping in the first frame indicate that the second link is open, the AP MLD shall not initiate transmission to the first non-AP MLD on the second link before any time in any of the second times and / or first times corresponding to all the first links of the AP MLD.

[0206] Optionally, under this method of taking the values ​​of Ta and Tb 3.1, the above rule five can also be described as follows: When the service identifier and link mapping in the first frame indicate that the second link is closed, the AP MLD ends the transmission with the first non-AP MLD on the second link before any of the second times and / or first times corresponding to all the first links of the AP MLD.

[0207] Optionally, under this method of taking the values ​​of Ta and Tb 3.1, the above rule six can also be described as follows: When the service identifier and link mapping in the first frame indicate that the second link is open, the AP MLD can only initiate transmission to the first non-AP MLD on the second link after any of the second times and / or first times corresponding to all the first links of the AP MLD.

[0208] For example, please see Figure 8e , Figure 8e This is another schematic diagram illustrating Ta and Tb provided in the embodiments of this application. For example... Figure 8e As shown, it is assumed that the effective start time of the service identifier and link mapping is based on the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0, meaning the first time is t0. All first links of the AP MLD are as follows: Figure 8eThe diagram shows links 1-1, 1-2, and 1-3. In scenario 3, for the first frame transmitted on link 1-1, the effective start time of the service identifier and link mapping indicated by this first frame is time point t1 or t2. For the first frame transmitted on link 1-2, the effective start time of the service identifier and link mapping indicated by this first frame is time point t3 or t4. For the first frame transmitted on link 1-3, the effective start time of the service identifier and link mapping indicated by this first frame is time point t5 or t6. That is, the first time is t0, and the second time includes one of t1 and t2, one of t3 and t4, and one of t5 and t6. Here, we take the example of the second time including t1, t3, and t6. If Ta = the minimum value among all second times corresponding to all first links of AP MLD, and Tb = the maximum value among all second times corresponding to all first links of AP MLD, then the positions of Ta and Tb are as follows: Figure 8e The positions of Ta and Tb are shown. The minimum value of all second times corresponding to all first links of AP MLD is t1 (because t1 < t3 < t6), and the maximum value of all second times corresponding to all first links of AP MLD is t6 (because t1 < t3 < t6).

[0209] Understandably, in scenarios 1 to 3 of the above situation one, there is no restriction on the implementation method of selecting the target effective start time of service identifier and link mapping for all non-AP MLDs that have established multi-link communication with AP (for example, non-AP MLDs can adopt any of the above implementation methods 1 to 3). That is, there is no restriction on which effective start time the non-AP MLD specifically selects as the target effective start time from at least one effective start time. For example, the target effective start time can be any one of the at least one effective start time, or the target effective start time can be the maximum effective start time among at least one effective start time, or the target effective start time can be the minimum effective start time among at least one effective start time, etc.

[0210] Scenario 2: The first non-AP MLD is one of the non-AP MLDs that have established multi-link communication with the AP MLD. In other words, the phrase "not initiating transmission to the first non-AP MLD on the second link" can be understood as: not initiating transmission to any one of the non-AP MLDs that have established multi-link communication with the AP MLD on the second link. It should be noted that in Scenario 2, the values ​​of Ta and Tb are specific to a particular non-AP MLD that has established multi-link communication with the AP MLD. That is, the AP MLD can determine a separate time range [Ta, Tb] for each non-AP MLD that has established multi-link communication with the AP MLD, or it can be described as the AP MLD needing to determine the values ​​of Ta and Tb for each non-AP MLD that has established multi-link communication with the AP MLD.

[0211] Scenario I: When the second time is before the first time (i.e., the second time is less than the first time), and the TU boundary on the first link is closest to the first time:

[0212] The values ​​of Ta and Tb are determined in the following ways: I.1. Ta is determined based on the minimum time among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb is determined based on the first time. For example, Ta is the minimum time among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD (i.e., Ta = the minimum value among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD), and Tb is the first time (i.e., Tb = the first time).

[0213] Understandably, in Scenario I of Case 2, the implementation method of the non-AP MLD selecting the target effective start time of the service identifier and link mapping is not restricted (for example, it can be any of the above implementation methods 1 to 3). That is, the non-AP MLD does not restrict which effective start time it specifically selects as the target effective start time from at least one effective start time. For example, the target effective start time can be any one of the at least one effective start time, or the target effective start time can be the maximum effective start time among at least one effective start time, or the target effective start time can be the minimum effective start time among at least one effective start time, etc. There are no restrictions here.

[0214] For example, please see Figure 9a , Figure 9a This is another schematic diagram illustrating Ta and Tb provided in the embodiments of this application. For example... Figure 9aAs shown, it is assumed that the effective start time of the service identifier and link mapping is referenced to the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0, meaning the first time is t0. All first links established between the first non-AP MLD and the first AP MLD are as follows: Figure 9a The diagram shows links 1-1 and 1-2. In scenario I, for the first frame transmitted on link 1-1, the effective start time of the service identifier and link mapping indicated by the first frame is time point t1; for the first frame transmitted on link 1-2, the effective start time of the service identifier and link mapping indicated by the first frame is time point t3. That is, the first time is t0, and the second time includes t1 and t3. It is not restricted that the target effective time determined by the non-AP MLD is any of the at least one effective start time indicated by the received first frame. If Ta = the minimum value among all second times corresponding to all first links established between the first non-AP MLD and the APMLD, and Tb = the first time, then the positions of Ta and Tb are as follows: Figure 9a The locations of Ta and Tb are shown, where the minimum value of all second times corresponding to all first links established between the first non-AP MLD and the AP MLD is t1 (because t1 < t3).

[0215] Scenario II: When the second time is after the first time (i.e., the second time is greater than the first time), and the TU boundary on the first link is closest to the first time:

[0216] II.3. The values ​​of Ta and Tb are determined based on the first time, and Tb is determined based on the maximum time among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD. For example, Ta is the first time (i.e., Ta = first time), and Tb is the maximum time among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD (i.e., Tb = the maximum value among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD).

[0217] Understandably, in scenario II of case two, the implementation method of the non-AP MLD selecting the target effective start time of the service identifier and link mapping is not restricted (for example, it can be any of the above implementation methods 1 to 3). That is, the non-AP MLD does not restrict which effective start time it specifically selects as the target effective start time from at least one effective start time. For example, the target effective start time can be any one of the at least one effective start time, or the target effective start time can be the maximum effective start time among at least one effective start time, or the target effective start time can be the minimum effective start time among at least one effective start time, etc. There are no restrictions here.

[0218] For example, please see Figure 9b , Figure 9b This is another schematic diagram illustrating Ta and Tb provided in the embodiments of this application. For example... Figure 9b As shown, it is assumed that the effective start time of the service identifier and link mapping is referenced to the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0, meaning the first time is t0. All first links established between the first non-AP MLD and the first AP MLD are as follows: Figure 9b The diagram shows links 1-1 and 1-2. In scenario II, for the first frame transmitted on link 1-1, the effective start time of the service identifier and link mapping indicated by this first frame is time point t2; for the first frame transmitted on link 1-2, the effective start time of the service identifier and link mapping indicated by this first frame is time point t4. That is, the first time is t0, and the second time includes t2 and t4. It is not restricted that the target effective time determined by the non-AP MLD is any of the at least one effective start time indicated by the received first frame. If Ta = the first time, and Tb = the maximum value among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, then the positions of Ta and Tb are as follows: Figure 9b The locations of Ta and Tb are shown, where the maximum value of all second times corresponding to all first links established between the first non-AP MLD and the AP MLD is t4 (because t2 < t4).

[0219] Scenario III: When the second time is the TU boundary closest to the first time on the first link (i.e., the second time may be greater than or less than the first time), and the non-AP MLD determines the target effective start time of the service identifier and link mapping based on the above implementation method 1:

[0220] The values ​​of Ta and Tb are determined in the following manner: 1. Ta is determined based on the minimum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and AP MLD. Tb is determined based on the maximum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and AP MLD. For example, Ta is the minimum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and AP MLD (i.e., Ta = the minimum value among all second times and / or first times corresponding to all first links established between the first non-AP MLD and AP MLD), and Tb is the maximum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and AP MLD (i.e., Tb = the maximum value among all second times and / or first times corresponding to all first links established between the first non-AP MLD and AP MLD).

[0221] Understandably, in scenario III of case two, the implementation method of the non-AP MLD selecting the target effective start time of the service identifier and link mapping is not restricted (for example, it can be any of the above implementation methods 1 to 3). That is, the non-AP MLD does not restrict which effective start time it specifically selects as the target effective start time from at least one effective start time. For example, the target effective start time can be any one of the at least one effective start time, or the target effective start time can be the maximum effective start time among at least one effective start time, or the target effective start time can be the minimum effective start time among at least one effective start time, etc. There are no restrictions here.

[0222] For example, please see Figure 9c , Figure 9c This is another schematic diagram illustrating Ta and Tb provided in the embodiments of this application. For example... Figure 9c As shown, it is assumed that the effective start time of the service identifier and link mapping is referenced to the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0, meaning the first time is t0. All first links established between the first non-AP MLD and the first AP MLD are as follows: Figure 9cThe diagram shows links 1-1 and 1-2. In scenario III, for the first frame sent on link 1-1, the effective start time of the service identifier and link mapping indicated by this first frame is time point t1 or t2. For the first frame sent on link 1-2, the effective start time of the service identifier and link mapping indicated by this first frame is time point t3 or t4. That is, the first time is t0, and the second time includes one of t1 and t2, and one of t3 and t4. Here, we take the example where the second time includes both t1 and t4. It is not restricted that the target effective time determined by the non-AP MLD is any of the at least one effective start time indicated by the received first frame. If Ta = the minimum value among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb = the maximum value among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, then the positions of Ta and Tb are as follows: Figure 9c The positions of Ta and Tb are shown. The minimum value of all second times corresponding to all first links established between the first non-AP MLD and AP MLD is t1 (because t1 < t4), and the maximum value of all second times corresponding to all first links established between the first non-AP MLD and AP MLD is t4 (because t1 < t4).

[0223] Scenario IV: When the second time is before the first time (i.e., the second time is less than the first time), and the TU boundary on the first link is closest to the first time:

[0224] The values ​​of Ta and Tb are determined as follows: IV.1. Ta is determined based on the maximum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb is determined based on the first time. For example, Ta is the maximum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD (i.e., Ta = the maximum value among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD), and Tb is the first time (i.e., Tb = the first time).

[0225] Understandably, in scenario IV of case two, the non-AP MLD can determine the target effective start time of the service identifier and link mapping based on the above implementation method 2. That is, the target effective start time determined by the non-AP MLD is the maximum effective start time among at least one effective start time obtained.

[0226] For example, please see Figure 9d , Figure 9d This is another schematic diagram illustrating Ta and Tb provided in the embodiments of this application. For example... Figure 9d As shown, it is assumed that the effective start time of the service identifier and link mapping is referenced to the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0, meaning the first time is t0. All first links established between the first non-AP MLD and the first AP MLD are as follows: Figure 9d The examples show links 1-1 and 1-2. In scenario IV, for the first frame transmitted on link 1-1, the effective start time of the service identifier and link mapping indicated by that first frame is time point t1; for the first frame transmitted on link 1-2, the effective start time of the service identifier and link mapping indicated by that first frame is time point t3. That is, the first time is t0, and the second time includes t1 and t3. Wherein, if the target effective time determined by the non-AP MLD is at least one effective start time indicated by the received first frame (e.g., ...), then... Figure 9d Given the maximum effective time (i.e., t3) in t1 and t3, if Ta = the maximum value of all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb = the first time, then the positions of Ta and Tb are as follows: Figure 9d The locations of Ta and Tb are shown, where the maximum value of all second times corresponding to all first links established between the first non-AP MLD and the AP MLD is t3 (because t1 < t3).

[0227] Scenario V: When the second time is after the first time (i.e., the second time is greater than the first time), and the TU boundary on the first link is closest to the first time:

[0228] The values ​​of Ta and Tb are determined in the following manner: V.1. Ta is determined based on the first time, and Tb is determined based on the minimum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD. For example, Ta is the first time (i.e., Ta = first time), and Tb is the minimum time among all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD (i.e., Tb = the minimum value among all second times and / or first times).

[0229] Understandably, in scenario V of case two, the non-AP MLD can determine the target effective start time of the service identifier and link mapping based on the above implementation method 3. That is, the target effective start time determined by the non-AP MLD is the minimum effective start time among the at least one effective start time obtained.

[0230] For example, please see Figure 9e , Figure 9e This is another schematic diagram illustrating Ta and Tb provided in the embodiments of this application. For example... Figure 9e As shown, it is assumed that the effective start time of the service identifier and link mapping is referenced to the TBTT corresponding to the DTIM beacon frame on link 2, i.e., time point t0, meaning the first time is t0. All first links established between the first non-AP MLD and the first AP MLD are as follows: Figure 9e The examples show links 1-1 and 1-2. In scenario V, for the first frame transmitted on link 1-1, the effective start time of the service identifier and link mapping indicated by this first frame is time point t2; for the first frame transmitted on link 1-2, the effective start time of the service identifier and link mapping indicated by this first frame is time point t4. That is, the first time is t0, and the second time includes t2 and t4. Wherein, if the target effective time determined by the non-AP MLD is at least one effective start time indicated by the received first frame (e.g., ...), then... Figure 9e Given the minimum effective time (i.e., t2) in t2 and t4, if Ta = the first time and Tb = the minimum value among all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, then the positions of Ta and Tb are as follows: Figure 9e The locations of Ta and Tb are shown, where the minimum value of all second times corresponding to all first links established between the first non-AP MLD and the AP MLD is t2 (because t2 < t4).

[0231] Understandably, to further distinguish the meaning of "all first links of the AP MLD" and "all first links established between the first non-AP MLD and the AP MLD" described in the embodiments of this application, a specific example is provided below. For example, suppose the AP MLD operates on N first links, and M first links are established between the first non-AP MLD and the AP MLD. Then, all first links of the AP MLD can be understood as these N first links, and all first links established between the first non-AP MLD and the AP MLD can be understood as these M first links, where N is a positive integer greater than or equal to M.

[0232] In this application, if a link (for example, the second link is used as an example for illustration) is to be closed, the AP MLD will be closed latest (i.e., later than the closing time of all non-AP MLDs that have established multi-link communication with the AP MLD); if a link (for example, the second link is used as an example for illustration) is to be opened, the AP MLD will be opened earliest (i.e., earlier than the opening time of all non-AP MLDs that have established multi-link communication with the AP MLD). Based on this, the problem of unreliable communication between the AP MLD and non-AP MLDs caused by the inconsistent understanding of the mapping effective time between the AP MLD and non-AP MLDs can be solved.

[0233] The foregoing details the method of this application. To facilitate better implementation of the above-described solutions in the embodiments of this application, corresponding apparatus or devices are also provided.

[0234] This application divides the communication device into functional modules according to the above-described method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and represents only one logical functional division; other division methods may be used in actual implementation. The following will combine... Figures 10 to 12 The communication device of the embodiments of this application is described in detail.

[0235] Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application, such as... Figure 10 As shown, the communication device includes a processing unit 1001 and a transceiver unit 1002. The transceiver unit 1002 can implement corresponding communication functions, and the processing unit 1001 is used for data processing. The transceiver unit 1002 can also be referred to as a communication interface or a communication unit, etc.

[0236] In some embodiments of this application, the communication device can be used to perform the actions performed by the AP MLD in the above method embodiments. In this case, the communication device can be the AP MLD or a component (such as a chip or system) that can be configured in the AP MLD. The transceiver unit 1002 is used to perform the transceiver-related operations of the AP MLD in the above method embodiments, and the processing unit 1001 is used to perform the AP MLD processing-related operations in the above method embodiments.

[0237] In some embodiments of this application, the communication device may be the AP MLD or a chip shown above, and the chip may be disposed in the AP MLD. That is, the communication device may be used to perform the steps or functions performed by the AP MLD in the method embodiments above.

[0238] Processing unit 1001 is used to generate at least one first frame; transceiver unit 1002 is used to transmit the at least one first frame on at least one first link.

[0239] Optionally, the communication device may further include a storage unit, which can be used to store instructions and / or data. The processing unit 1001 can read the instructions and / or data in the storage unit so that the communication device can implement the aforementioned method embodiments.

[0240] In other embodiments of this application, the communication device can be used to perform the actions performed by the non-AP MLD in the above method embodiments. In this case, the communication device can be a non-AP MLD or a component configurable in the non-AP MLD. The transceiver unit 1002 is used to perform the transceiver-related operations of the non-AP MLD in the above method embodiments, and the processing unit 1001 is used to perform the processing-related operations of the non-AP MLD in the above method embodiments. That is, the communication device can be used to perform the steps or functions performed by the non-AP MLD in the above method embodiments.

[0241] The transceiver unit 1002 is used to receive at least one first frame on at least one first link; the processing unit 1001 is used to determine the target effective start time of the service identifier and link mapping based on the at least one first frame.

[0242] It is understood that the specific explanation of how the processing unit 1001 parses the first frame to determine the target's effective start time can be found in the method embodiment shown above, and will not be described in detail here.

[0243] Optionally, the communication device may further include a storage unit, which can be used to store instructions and / or data. The processing unit 1001 can read the instructions and / or data in the storage unit so that the communication device can implement the aforementioned method embodiments.

[0244] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above method embodiments, which will not be described in detail here.

[0245] In the previous embodiments, the descriptions of the first frame, first time, second time, Ta, Tb, etc. can be found in the above method embodiments, and will not be described in detail here.

[0246] The communication device according to embodiments of this application has been described above. The following describes possible product forms of the communication device. It should be understood that any device possessing the above-described features... Figure 10 Any form of the communication device described herein falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the form of the communication device in the embodiments of this application to this specific example.

[0247] In one possible implementation, Figure 10 In the communication device shown, the processing unit 1001 can be one or more processors, and the transceiver unit 1002 can be a transceiver, or the transceiver unit 1002 can also be a transmitting unit and a receiving unit. The transmitting unit can be a transmitter, and the receiving unit can be a receiver. The transmitting unit and the receiving unit are integrated into one device, such as a transceiver. In the embodiments of this application, the processor and the transceiver can be coupled, etc., and the connection method between the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information in the above method can be understood as the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be understood as the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to undergo other processing before being input into the processor.

[0248] like Figure 11 As shown, the communication device 110 includes one or more processors 1120 and transceivers 1110.

[0249] In some embodiments of this application, the communication device can be used to perform the steps or functions performed by the AP MLD in the above method embodiments.

[0250] Processor 1120 is configured to generate at least one first frame; transceiver 1110 is configured to transmit the at least one first frame on at least one first link.

[0251] In other embodiments of this application, the communication device can be used to perform steps or functions performed by the non-AP MLD in the above method embodiments.

[0252] Transceiver 1110 is configured to receive at least one first frame on at least one first link; processor 1120 is configured to determine the target effective start time of the service identifier and link mapping based on the at least one first frame.

[0253] It is understood that the specific descriptions of the transceiver and processor shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver and processor, please refer to the above method embodiments, which will not be described in detail here.

[0254] In the previous embodiments, the descriptions of the first frame, first time, second time, Ta, Tb, etc. can be found in the above method embodiments, and will not be described in detail here.

[0255] exist Figure 11 In various implementations of the communication apparatus shown, the transceiver may include a receiver for performing a receiving function (or operation) and a transmitter for performing a transmitting function (or operation). The transceiver is also used to communicate with other devices / appliances via a transmission medium.

[0256] Optionally, the communication device 110 may further include one or more memories 1130 for storing program instructions and / or data, etc. The memory 1130 is coupled to the processor 1120. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 1120 may operate in conjunction with the memory 1130. The processor 1120 may execute program instructions stored in the memory 1130. Optionally, at least one of the above-mentioned memories may be included in the processor.

[0257] This application embodiment does not limit the specific connection medium between the transceiver 1110, processor 1120, and memory 1130. This application embodiment... Figure 11 The memory 1130, processor 1120, and transceiver 1110 are connected via a bus 1140, and the bus is in Figure 11 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 11 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0258] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0259] In this application embodiment, the memory may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM), etc. Memory is any storage medium capable of carrying or storing program code in the form of instructions or data structures, and capable of being read and / or written by a computer (such as the communication device shown in this application), but is not limited to this. The memory in this application embodiment may also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0260] For example, processor 1120 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process data from the software programs. Memory 1130 is mainly used to store software programs and data. Transceiver 1110 may include control circuitry and an antenna. The control circuitry is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0261] When the communication device is powered on, the processor 1120 can read the software program in the memory 1130, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1120 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1120. The processor 1120 converts the baseband signal into data and processes the data.

[0262] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0263] It is understood that the communication device shown in the embodiments of this application may also have more than Figure 11 This application does not limit the use of other components or other related elements. The methods performed by the processor and transceiver shown above are merely examples; the specific steps performed by the processor and transceiver can be found in the methods described above.

[0264] In another possible implementation Figure 10 In the communication device shown, the processing unit 1001 can be one or more logic circuits, and the transceiver unit 1002 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver unit 1002 can also be a transmitting unit and a receiving unit; the transmitting unit can be an output interface, and the receiving unit can be an input interface, integrated into one unit, such as an input / output interface. Figure 12 As shown, Figure 12 The communication device shown includes logic circuitry 1201 and interface 1202. That is, the processing unit 1001 can be implemented using logic circuitry 1201, and the transceiver unit 1002 can be implemented using interface 1202. The logic circuitry 1201 can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface 1202 can be a communication interface, input / output interface, pins, etc. For example, Figure 12 Taking the aforementioned communication device as an example, the chip includes a logic circuit 1201 and an interface 1202.

[0265] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method between the logic circuit and the interface is not limited in this embodiment.

[0266] In some embodiments of this application, the communication device can be used to perform the steps or functions performed by the AP MLD in the above method embodiments.

[0267] Logic circuit 1201 is used to generate at least one first frame; interface 1202 is used to transmit the at least one first frame on at least one first link.

[0268] In some other embodiments of this application, the communication device can be used to perform steps or functions performed by the non-AP MLD in the above method embodiments.

[0269] Interface 1202 is used to receive at least one first frame on at least one first link; logic circuit 1201 is used to determine the target effective start time of the service identifier and link mapping based on the at least one first frame.

[0270] It is understood that the specific descriptions of the logic circuits and interfaces shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the logic circuits and interfaces, please refer to the above method embodiments, which will not be described in detail here.

[0271] In the previous embodiments, the descriptions of the first frame, first time, second time, Ta, Tb, etc. can be found in the above method embodiments, and will not be described in detail here.

[0272] It is understood that the communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form or in software form, etc., and the embodiments of this application do not limit it in this way.

[0273] This application also provides a wireless communication system, which includes an AP MLD and a non-AP MLD, which can be used to perform the methods in any of the foregoing embodiments.

[0274] In addition, this application also provides a computer program for implementing the operations and / or processes performed by the AP MLD in the method provided in this application.

[0275] This application also provides a computer program for implementing the operations and / or processes performed by a non-AP MLD in the method provided in this application.

[0276] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by the AP MLD in the method provided in this application.

[0277] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform operations and / or processes performed by non-APMLD in the method provided in this application.

[0278] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by APMLD in the method provided in this application to be executed.

[0279] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by a non-AP MLD in the method provided in this application to be executed.

[0280] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0281] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.

[0282] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0283] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A communication method, characterized in that, include: The Access Point Multilink Device (AP MLD) generates the first frame; The AP MLD transmits the first frame on at least one first link; The first frame indicates the start time of the effective date of the Service Identifier-to-Link Mapping (TID-to-Link Mapping); The AP MLD closes or opens the second link based on the service identifier and link mapping; When the service identifier and link mapping indicate that the second link is closed, the AP MLD closes the second link no earlier than time point Tb, where Tb is the target beacon transmission time (TBTT) corresponding to the service indication map (DTIM) beacon frame of the third link; or... When the service identifier and link mapping indicate that the second link is enabled, the AP MLD enables the second link no later than time point Ta; Ta is earlier than Tb and is the difference between the length of Tb and the time unit TU.

2. The method according to claim 1, characterized in that, The method includes: When the first link and the third link are the same, the effective start time of the service identifier and link mapping indicated by the first frame sent on the first link is Tb; or When the first link and the third link are different, the effective start time of the service identifier and link mapping indicated by the first frame sent on the first link is the time unit TU boundary on the first link.

3. The method according to claim 1 or 2, characterized in that, When the service identifier and link mapping indicate that the second link is closed, the AP MLD, if later than Ta, will not initiate a transmission on the second link to the first non-access point multi-link device (non-AP MLD); or, When the service identifier and link mapping indicate that the second link is open, the AP MLD will not initiate transmission to the first non-AP MLD on the second link if it is earlier than Tb.

4. The method according to claim 1 or 2, characterized in that, When the service identifier and link mapping indicate that the second link is closed, the AP MLD terminates its transmission with the first non-AP MLD on the second link before the Ta; or, When the service identifier and link mapping indicate that the second link is enabled, the AP MLD can only initiate transmission to the first non-AP MLD on the second link after the Tb; The first non-AP MLD is all non-AP MLDs that have established multi-link communication with the AP MLD.

5. The method according to claim 1, characterized in that, If the AP MLD is later than Ta but earlier than Tb, it will not initiate a transmission to the first non-access point multi-link device (non-AP MLD) on the second link.

6. The method according to claim 1, characterized in that, The first non-AP MLD is any one of the non-AP MLDs that has established multi-link communication with the AP MLD.

7. The method according to claim 2, characterized in that, The TU boundary is the time point when the lower 10 bits of the time synchronization function TSF timer are 0.

8. The method according to claim 1 or 2, characterized in that, The first frame is a beacon frame or a probe response frame.

9. The method according to claim 1 or 2, characterized in that, The effective start time of the service identifier and link mapping is indicated by the mapping switch time field in the first frame.

10. The method according to claim 1 or 2, characterized in that, The effective start time of the service identifier and link mapping indicated in the first frame is different.

11. A communication device, characterized in that, include: The generation module is used to generate the first frame; A sending module, configured to send the first frame on at least one first link; The first frame indicates the start time of the effective date of the Service Identifier-to-Link Mapping (TID-to-Link Mapping); The processing module is used to close or open the second link based on the service identifier and link mapping; When the service identifier and link mapping indicate that the second link is closed, the processing module closes the second link no earlier than time point Tb, where Tb is the target beacon transmission time (TBTT) corresponding to the DTIM beacon frame of the third link; or... When the service identifier and link mapping indicate that the second link is enabled, the processing module enables the second link no later than time point Ta; Ta is earlier than Tb and is the difference between the lengths of Tb and TU.

12. The communication device according to claim 11, characterized in that, When the first link and the third link are the same, the effective start time of the service identifier and link mapping indicated by the first frame sent by the sending module on the first link is Tb; or When the first link and the third link are not the same, the effective start time of the service identifier and link mapping indicated by the first frame sent by the sending module on the first link is the time unit (TU) boundary on the first link.

13. The communication device according to claim 11 or 12, characterized in that, When the service identifier and link mapping indicate that the second link is closed, the sending module, if later than Ta, will not initiate transmission on the second link to the first non-access point multi-link device (non-AP MLD); or, When the service identifier and link mapping indicate that the second link is open, the sending module does not initiate transmission to the first non-AP MLD on the second link before the Tb.

14. The communication device according to claim 11 or 12, characterized in that, When the service identifier and link mapping indicate that the second link is closed, the sending module terminates the transmission with the first non-AP MLD on the second link before Ta; or, When the service identifier and link mapping indicate that the second link is open, the sending module can only initiate transmission to the first non-AP MLD on the second link after the Tb; The first non-AP MLD is all non-AP MLDs that have established multi-link communication with the AP MLD.

15. The communication device according to claim 11, characterized in that, If the sending module is later than Ta but earlier than Tb, it will not initiate a transmission to the first non-access point multi-link device (non-AP MLD) on the second link.

16. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device, and the processor is used to implement the method as described in any one of claims 1-10 through logic circuits or execution code instructions.

Images