Communication method and related device

Abstract

A communication method and a related device are applied to a wireless local area network system supporting an IEEE 802.1 lax next generation Wi-Fi protocol, such as 802.11 be, Wi-Fi 7 or EHT, and 802.11 series protocols such as 802.11 be next generation, Wi-Fi 8, UHR, Wi-Fi AI and the like, and can also be applied to a wireless personal local area network system and a sensing system based on ultra-bandwidth. The AP MLD sends at least one first frame on at least one first link; the first frame indicates the effective starting time of the service identifier and link mapping; when the service identifier and the link mapping indicate that the second link is closed, the time for closing the second link by the AP MLD is not earlier than the time point Tb; when the service identifier and the link mapping indicate that the second link is opened, the time for opening the second link by the AP MLD is not later than the time point Ta; ta is earlier than Tb. The communication reliability can be improved.

Description

Communication method and related device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on June 28, 2023, with application number 202310790310.7, and priority to the Chinese patent application entitled “Communication Methods and Related Devices,” all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and related devices. Background Art

[0003] With the advancement of wireless technology, more and more wireless devices support multi-link communication. For example, they can communicate simultaneously on the 2.4 GHz, 5 GHz, and 6 GHz bands, or on different channels within the same band. This improves the communication rate between wireless devices. Devices that support multi-link communication are commonly referred to as multi-link devices (MLDs).

[0004] Before MLD and MLD can communicate across multiple links, they must first establish multiple links (or associate multiple links). To better manage services, traffic IDs (TIDs) and link mappings (TID-to-link mapping) can be performed to provide differentiated services for different services. Typically, these mappings are carried in the 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 a probe response frame. The effective start time of the indicated 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. It is understandable that the TBTT on a link (for example, link 1) is the time unit (TU) boundary of that link, but it is not necessarily the TU boundary of other links (for example, link 2, link 3, etc.) (This is because the time synchronization function (TSF) timer values ​​of different links are selected independently. When the lower 10 bits of the TSF timer of a link (for example, link 1) are 0, the lower 10 bits of the TSF timer of 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 the TU (1TU = 1024us). As a result, the mapping switch time field in the TID-to-Link Mapping element on one link cannot indicate the TU boundary of another link, nor the TBTT of the other 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-access point multi-link devices (non-AP MLD).

[0006] Summary of the Invention

[0007] The present application provides a communication method and related apparatus, which facilitate reliable communication between an AP MLD and a non-AP MLD.

[0008] In a first aspect, the present application provides a communication method, which is applied to an AP MLD. The AP MLD may be the AP MLD itself, or a module or chip in the AP MLD. The method includes: an AP MLD generates at least one first frame; the AP MLD sends the at least one first frame on at least one first link; wherein the first frame indicates an 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 a time point Tb; or, when the service identifier and link mapping indicates that the second link is opened, the AP MLD opens the second link no later than a time point Ta; Ta is earlier than Tb, and Ta and / or Tb are determined based on a first time and / or a second time, the first time being a target beacon transmission time (TBTT) corresponding to a service indication map (DTIM) beacon frame of a 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 in the first frame sent 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 in the first frame sent on the first link is the second time, and the second time is a time unit (TU) boundary on the first link.

[0009] It is understandable that if, according to the indication of the service identifier and link mapping, no service identifier (TID) is mapped to a link in any direction (including uplink and downlink), then this link will be closed; if, according to the indication of the service identifier and link mapping, there is a service identifier (TID) mapped to a link in any direction (including uplink and downlink), then this link will be opened.

[0010] In this application, if a link (e.g., the second link in this application is used as an example for illustrative purposes) is determined to be shut down based on the service identifier and link mapping, the AP MLD is shut down last (i.e., after the shutdown time of all non-AP MLDs that have established multi-link communication with the AP MLD). This ensures that the AP MLD can normally receive data / information from the non-AP MLD. If a link (e.g., the second link in this application is used as an example for illustrative purposes) is determined to be enabled based on the service identifier and link mapping, the AP MLD is enabled first (i.e., before the startup time of all non-AP MLDs that have established multi-link communication with the AP MLD). This ensures that the AP MLD can normally receive data / information from the non-AP MLD. This solves the problem of unreliable communication between the AP MLD and the non-AP MLD caused by inconsistent understanding of the mapping effective time between the AP MLD and the non-AP MLD.

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

[0012] When the service identifier and link mapping indicates that the second link is enabled, the AP MLD does not initiate transmission to the first non-AP MLD on the second link before Tb.

[0013] In this implementation, if the second link is to be shut down, the AP MLD will not initiate a transmission to the first non-AP MLD over the second link if it is later than Ta. This ensures that the non-AP MLD can normally receive data / information from the AP MLD, thereby improving the reliability of communication between the AP MLD and the non-AP MLD. Similarly, if the second link is to be enabled, the AP MLD will not initiate a transmission to the first non-AP MLD over the second link if it is earlier than Tb. This also ensures that the non-AP MLD can normally receive data / information from the AP MLD, thereby improving the reliability of communication between the AP MLD and the non-AP MLD.

[0014] In a possible implementation, when the service identifier and link mapping indicates that the second link is closed, the AP MLD ends the transmission with the first non-AP MLD on the second link before Ta; or,

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

[0016] In a possible implementation, the AP MLD does not initiate transmission to the first non-AP MLD on the second link when the time is later than Ta and earlier than Tb.

[0017] In this implementation, by restricting the AP MLD from initiating transmissions to the first non-AP MLD on the second link when the AP MLD's time is later than Ta and earlier than Tb (e.g., within [Ta, Tb] or (Ta, Tb)), the non-AP MLD can be guaranteed to normally receive data / information from the AP MLD, thereby improving the reliability of communication between the AP MLD and the non-AP MLD. It should be noted that this implementation is applicable both when the second link is about to be shut down and when the second link is about to be shut down.

[0018] In a possible implementation, the second time is a TU boundary closest to the first time on the first link.

[0019] In this implementation, the second time is the TU boundary closest to the first time on the first link. This can reduce the time interval between Tb and Ta, thereby 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 of this application more diverse and applicable.

[0020] In a possible implementation, the second time is before the first time, and the second time is a TU boundary closest to the first time on the first link.

[0021] In a possible implementation, Ta is the difference between the first time and the length of TU, ​​and Tb is the first time; or,

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

[0023] In a 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.

[0024] In a possible implementation, Ta is a 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.

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

[0026] In a possible implementation, Ta is the first time, and Tb is the sum of the first time and the length of TU; or,

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

[0028] In a 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.

[0029] In a possible implementation, Ta is the first time, and Tb 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 / or the first times.

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

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

[0032] In a possible implementation, the first non-AP MLDs are all non-AP MLDs that have established multi-link communication with the AP MLD.

[0033] In this implementation, when the first non-AP MLD is all non-AP MLDs that have established multi-link communications with the AP MLD, the values ​​of Ta and Tb can be applicable to all non-AP MLDs that have established multi-link communications with the AP MLD, which is simple to operate and has a wide range of applicability.

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

[0035] 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 the non-AP MLD that has established multi-link communication with the AP MLD. This reduces Tb-Ta (i.e., reduces the time interval between Tb and Ta), thereby shortening the time period during which the AP MLD cannot initiate transmission to the non-AP MLD.

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

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

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

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

[0040] In a possible implementation, different first frames indicate different effective start times of the service identifiers and link mappings.

[0041] In a second aspect, the present application provides a communication method, which is applied to a non-AP MLD. The non-AP MLD may be the non-AP MLD itself, or a module or chip within the non-AP MLD. The method includes:

[0042] The non-AP MLD receives at least one first frame on at least one first link, where the first frame indicates a valid start time of a mapping between a service identifier and a link;

[0043] The non-AP MLD determines a target effective start time of a mapping between a service identifier and a link according to the at least one first frame.

[0044] In the present 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-link mapping indicated by each first frame in 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-link mapping. Furthermore, the non-AP MLD can use the selected target effective start time as the time to actually enable or disable a certain link (here, the link to be enabled or disabled can be determined based on the relationship between the service identifier and the link mapping).

[0045] In a possible implementation, different first frames indicate different effective start times of the service identifiers and link mappings.

[0046] In a possible implementation, the non-AP MLD determines, according to the at least one first frame, a valid start time of the service identifier and link mapping, including:

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

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

[0049] In a 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.

[0050] In this implementation, non-AP MLD can select the largest one from multiple different time information as the target effective start time of the service identifier and link mapping, which is conducive to shortening the time interval between Tb and Ta.

[0051] In a 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.

[0052] In this implementation, non-AP MLD can select the smallest one from multiple different time information as the target effective start time of the service identifier and link mapping, which is conducive to shortening the time interval between Tb and Ta.

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

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

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

[0056] In a third aspect, the present application provides a communication device, which may be an AP MLD or a chip in the AP MLD, such as a Wi-Fi chip. The communication device includes: a processing unit, configured to generate at least one first frame; a transceiver unit, configured to send the at least one first frame on at least one first link; wherein the first frame indicates an 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 time when the AP MLD closes the second link is not earlier than a time point Tb; or when the service identifier and link mapping indicates that the second link is opened, the time when the AP MLD opens the second link is not later than a time point Ta; the Ta is earlier than the Tb, the Ta and / or the Tb are determined based on a first time and / or a second time, the first time is a target beacon transmission time TBTT corresponding to a service indication map DTIM beacon frame of a 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 sent 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 sent on the first link is the second time, and the second time is a time unit TU boundary on the first link.

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

[0058] When the service identifier and link mapping indicates that the second link is enabled, the AP MLD does not initiate transmission to the first non-AP MLD on the second link before Tb.

[0059] In a possible implementation, when the service identifier and link mapping indicates that the second link is closed, the AP MLD ends the transmission with the first non-AP MLD on the second link before Ta; or,

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

[0061] In a possible implementation, the AP MLD does not initiate transmission to the first non-AP MLD on the second link when the time is later than Ta and earlier than Tb.

[0062] In a possible implementation, the second time is a TU boundary closest to the first time on the first link.

[0063] In a possible implementation, the second time is before the first time, and the second time is a TU boundary closest to the first time on the first link.

[0064] In a possible implementation, Ta is the difference between the first time and the length of TU, ​​and Tb is the first time; or,

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

[0066] In a 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.

[0067] In a possible implementation, Ta is a 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.

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

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

[0070] In a 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.

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

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

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

[0074] In a possible implementation, the first non-AP MLDs are all non-AP MLDs that have established multi-link communication with the AP MLD.

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

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

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

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

[0079] In a possible implementation, different first frames indicate different effective start times of the service identifiers and link mappings.

[0080] In a fourth aspect, the present application provides a communication device, which may be a non-AP MLD or a chip within 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 a start time at which a service identifier and link mapping takes effect; and a processing unit configured to determine a target start time at which the service identifier and link mapping takes effect based on the at least one first frame.

[0081] In a possible implementation, different first frames indicate different effective start times of the service identifiers and link mappings.

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

[0083] A valid start time of a service identifier and link mapping is determined from the valid start time of at least one service identifier and link mapping indicated by the at least one first frame as the target valid start time of the service identifier and link mapping.

[0084] In a 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.

[0085] In a 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.

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

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

[0088] In a fifth aspect, the present application provides a communication device, which includes a processor, and the processor is used to execute a computer program so that the communication device performs the method as described in any one of the first aspect or the second aspect.

[0089] In one possible design, the communication device may be a chip that implements the method in the first aspect or the second aspect, or a device including a chip.

[0090] In one possible design, the communication device further includes a transceiver, and the processor is coupled to the transceiver.

[0091] In one possible design, the communication device further includes a memory. The processor is coupled to the memory, the memory stores a computer program, and the processor is further configured to call the computer program in the memory.

[0092] In a sixth aspect, the present application provides a communication device, which includes a processor and an interface circuit, the interface circuit being used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor being used to implement a method as described in any one of the first or second aspects through a logic circuit or executing code instructions.

[0093] In a seventh aspect, the present application provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed by a computer, the method as described in any one of the first aspect or the second aspect is implemented.

[0094] In an eighth aspect, the present application provides a computer program product, which, when read and executed by a computer, enables the computer to execute the method described in any one of the first aspect or the second aspect.

[0095] In a ninth aspect, the present application provides a communication system, which includes an AP MLD and a non-AP MLD. The AP MLD can be used to implement any method in the first aspect, and the non-AP MLD is used to implement any method in the second aspect.

[0096] The beneficial effects of the third to ninth aspects can be found in the relevant beneficial effects of the first to second aspects and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0097] FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

[0098] FIG2 is a schematic diagram of multi-link communication provided by an embodiment of the present application;

[0099] FIG3a is a schematic diagram of a connection between an AP MLD and a non-AP MLD according to an embodiment of the present application;

[0100] FIG3 b is a schematic diagram of another connection method between an AP MLD and a non-AP MLD provided in an embodiment of the present application;

[0101] FIG3c is a schematic diagram of an antenna of an MLD provided in an embodiment of the present application;

[0102] FIG4a is a schematic diagram of a communication scenario provided in an embodiment of the present application;

[0103] FIG4b is a schematic diagram of another communication scenario provided in an embodiment of the present application;

[0104] FIG5 is a schematic diagram of a frame structure of a TID-to-link mapping element provided in an embodiment of the present application;

[0105] 6 is a schematic diagram of a scenario in which the mapping switch time field in a beacon frame indicates the effective start time of the service identifier and link mapping;

[0106] FIG7 is a flow chart of a communication method according to an embodiment of the present application;

[0107] FIG8a is a schematic diagram of a scenario of Ta and Tb provided in an embodiment of the present application;

[0108] FIG8b is a schematic diagram of another scenario of Ta and Tb provided in an embodiment of the present application;

[0109] FIG8c is another schematic diagram of Ta and Tb provided in an embodiment of the present application;

[0110] FIG8 d is another schematic diagram of Ta and Tb provided in an embodiment of the present application;

[0111] FIG8e is another schematic diagram of Ta and Tb provided in an embodiment of the present application;

[0112] FIG9a is another schematic diagram of Ta and Tb provided in an embodiment of the present application;

[0113] FIG9 b is another schematic diagram of Ta and Tb provided in an embodiment of the present application;

[0114] FIG9c is another schematic diagram of Ta and Tb provided in an embodiment of the present application;

[0115] FIG9 d is another schematic diagram of Ta and Tb provided in an embodiment of the present application;

[0116] FIG9e is another schematic diagram of Ta and Tb provided in an embodiment of the present application;

[0117] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0118] FIG11 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

[0119] FIG12 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0121] The terms "first" and "second" in the specification, claims, and drawings of this application are used only to distinguish different objects and are not used to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to the process, method, product, or device.

[0122] References to "embodiments" herein mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it refer to independent or alternative embodiments that are mutually exclusive of other embodiments. It will be understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0123] In this application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. "Or" means that two relationships can exist, such as only A exists, only B exists; when A and B are not mutually exclusive, it can also mean that three relationships exist, such as only A exists, only B exists, and A and B exist at the same time. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items. For example, at least one 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".

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

[0125] WLAN systems can provide high-speed and 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, corporate offices, sports stadiums and exhibition halls, concert halls, hotel rooms, dormitories, wards, classrooms, supermarkets, squares, streets, production workshops and warehouses, etc. Of course, devices supporting WLAN communication or perception (such as access points or stations) can be sensor nodes in smart cities (such as smart water meters, smart electricity meters, and smart air detection nodes), smart devices in smart homes (such as smart cameras, projectors, display screens, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (such as wearable devices such as augmented reality (AR) and virtual reality (VR)), smart devices in smart offices (such as printers, projectors, speakers, and speakers, etc.), Internet of Vehicles (IoV) devices, infrastructure in daily life scenarios (such as vending machines, self-service navigation kiosks in supermarkets, self-service checkout devices, self-service ordering machines, etc.), and equipment in large sports and music venues. For example, access points and stations can be devices used in the IoV, IoT nodes and sensors in the Internet of Things, smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0126] Although the embodiments of the present application mainly take WLAN as an example, especially networks applied to the IEEE 802.11 series of standards, such as systems that support Wi-Fi 7, which can also be called extremely high-throughput (EHT), and systems that support Wi-Fi 8, which can also be called ultra-high reliability (UHR) or ultra-high reliability and throughput (UHRT). It will be readily understood by those skilled in the art that the various aspects involved in the embodiments of the present application can be extended to other networks that adopt various standards or protocols. For example, Bluetooth, high-performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, mainly used in Europe) and wide area networks (WANs) or other networks now known or developed later. Therefore, regardless of the coverage range and wireless access protocol used, the various aspects provided in the embodiments of the present application can be applied to any suitable wireless network.

[0127] A multi-link device includes one or more subordinate sites, and a subordinate site is a logical site that can operate on a link, a frequency band, or a channel, etc. The subordinate site can be an AP or a non-AP STA. For the convenience of description, the embodiment of the present application can refer to a multi-link device whose subordinate site is an AP as a multi-link AP or a multi-link AP device or an AP multi-link device (AP multi-link device, AP MLD). A multi-link device whose subordinate site is a non-AP STA is referred to as a multi-link STA or a multi-link STA device or a STA multi-link device (STA multi-link device), or a multi-link device whose subordinate site is a non-AP STA is referred to as a multi-link non-AP or a multi-link non-AP device or a non-AP multi-link device (non-AP multi-link device, non-AP MLD). A multi-link device (which can be either a non-AP MLD or an AP MLD here) is a communication device with wireless communication function. The communication device can be a complete device, or it can be a chip or processing system installed in the complete device. The devices installed with these chips or processing systems can implement the methods and functions of the embodiments of the present application under the control of these chips or processing systems.

[0128] A multi-link device can implement wireless communications using the 802.11 family of protocols, such as Extremely High Throughput (EHT), or protocols based on or compatible with 802.11be, thereby enabling communication with other devices. These other devices may or may not be multi-link devices.

[0129] Each logical site can work on a link, allowing multiple logical sites to work on the same link. The link identifier can represent a site working on a link, that is, if there is more than one logical site on a link, more than one link identifier can be used to represent them. The link identifier sometimes also represents the site working on the link. When a multi-link device transmits data with another multi-link device, before communication, the multi-link device and the other multi-link device can first negotiate or communicate the correspondence between the link identifier and a link or a site on a link, or the AP MLD indicates the correspondence between the link identifier and a link or a site on a link through a broadcast management frame, such as a beacon frame. Therefore, during data transmission, a large amount of signaling is not required to be transmitted to indicate the link or the site on the link. Only the link identifier can be carried, which reduces signaling overhead and improves transmission efficiency.

[0130] The following uses an example in which one of the multi-link devices is an AP MLD and the other multi-link device is a non-AP MLD. In one example, when establishing a basic service set (BSS), the AP MLD sends a management frame, such as a multi-link probe response frame, that carries one or more multi-link elements. The link information field included in the multi-link element can be used to establish a correspondence between a link identifier and a station operating on the link.

[0131] Please refer to Figure 1, which is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application. As shown in Figure 1, the wireless communication system includes at least one AP MLD (such as AP MLD100 in Figure 1) and at least one non-AP MLD (such as non-AP MLD200 and non-AP MLD300 in Figure 1). Optionally, Figure 1 also includes a traditional station that only supports transmission on a single link (such as the single-link non-AP STA400 in Figure 1, also referred to as STA400). Among them, the AP MLD is a device that provides services for the non-AP MLD. The non-AP MLD can communicate with the AP MLD using multiple links, thereby achieving the effect of improving throughput. A STA in the non-AP MLD can also communicate with an AP in the AP MLD through a link. It is understandable that the number of AP MLDs and non-AP MLDs in Figure 1 is only exemplary.

[0132] Optionally, please refer to Figure 2, which is a schematic diagram of multi-link communication provided by an embodiment of the present application. As shown in Figure 2, AP MLD includes AP1, AP2, ..., APn, and non-AP MLD includes STA1, STA2, ..., STAn. The n shown here is a positive integer. AP MLD and non-AP MLD can communicate in parallel using link 1, link 2, ..., link n. STA1 in non-AP MLD establishes an association relationship with AP1 in AP MLD, STA2 in non-AP MLD establishes an association relationship with AP2 in AP MLD, and STAn in non-AP MLD establishes an association relationship with APn in AP MLD, etc. Thus, after establishing an association relationship between one or more STAs in non-AP MLD and one or more APs in AP MLD, communication can be carried out. The operating frequency bands of multi-link devices (including AP MLD and non-AP MLD) may include, but are not limited to, sub 1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high frequency 60 GHz. For example, the methods provided in the embodiments of the present application may be applicable to, but 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 example, V2X may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-network (V2N) communications.

[0133] Figures 3a and 3b illustrate a connection between an AP MLD and a non-AP MLD, as provided in an embodiment of the present application. The 802.11 standard focuses on the 802.11 physical layer (PHY) and medium access control (MAC) layer in multi-link devices. Therefore, Figures 3a and 3b only illustrate the PHY and MAC layers.

[0134] As shown in Figures 3a and 3b, multi-link devices (such as AP MLDs and non-AP MLDs) can include physical layer (PHY) processing circuitry (PHY#1, PHY#2, and PHY#n, as shown in Figure 3a) and medium access control (MAC) layer processing circuitry. The physical layer processing circuitry can be used to process physical layer signals, and the MAC layer processing circuitry can be used to process MAC layer signals. Furthermore, the MAC layer can be divided into a high-MAC layer (high-MAC, as shown in Figure 3a, and high-MAC#1 to high-MAC#n, as shown in Figure 3b) and multiple low-MAC layers (low-MAC#1, low-MAC#2 to low-MAC#n, as shown in Figures 3a and 3b). As shown in Figure 3a, the multiple APs included in an AP MLD are independent of each other in the low-MAC layer and PHY layer, but share the high-MAC layer. The multiple STAs included in a non-AP MLD are independent of each other in the low-MAC layer and PHY layer, but share the high-MAC layer. The high-MAC layer is connected to multiple low-MAC layers, meaning that the high-MAC layer is shared by multiple links. As shown in Figure 3b, the multiple APs included in the AP MLD are independent of each other at the low MAC layer and PHY layer, as well as at the high MAC layer. The multiple STAs of the non-AP MLD device are independent of each other at the low MAC layer and PHY layer, as well as at the high MAC layer. Exemplarily, the high MAC layer primarily performs operations such as the allocation of sequence numbers (SN) and packet numbers (PN) for MAC service data units (MSDUs), as well as encryption and decryption. Exemplarily, the low MAC layer primarily performs operations such as the assembly of MAC protocol data units (MPDUs) for each link, channel access, packet transmission, and packet reception confirmation.

[0135] In Figure 3a, the PHY#1, lower MAC#1, and upper MAC layers in the AP MLD are considered AP#1, the PHY#2, lower MAC#2, and upper MAC layers are considered AP#2, and so on. The PHY#n, lower MAC#n, and upper MAC layers are considered AP#n. This means that the AP MLD includes n AP entities. The situation is similar in non-AP MLD, where the upper MAC layer is also shared by multiple links. The PHY#1, lower MAC#1, and upper MAC layers are considered STA#1, the PHY#2, lower MAC#2, and upper MAC layers are considered STA#2, and so on. The PHY#n, lower MAC#n, and upper MAC layers are considered STA#n. This means that the non-AP MLD includes n STA entities. As shown in Figure 3a, PHY#1 of AP#1 in the AP MLD is connected to PHY#1 of STA#1 in the non-AP MLD, and AP#1 in the AP MLD and STA#1 in the non-AP MLD communicate via a link (link #1 as shown in Figure 3a). PHY#2 of AP#2 in the AP MLD is connected to PHY#2 of STA#2 in the non-AP MLD, and AP#2 in the AP MLD and STA#2 in the non-AP MLD communicate via a link (link #2 as shown in Figure 3a). PHY#n of AP#n in the AP MLD is connected to PHY#n of STA#n in the non-AP MLD, and AP#n in the AP MLD and STA#n in the non-AP MLD communicate via a link (link #n as shown in Figure 3a). For the description of Figure 3b, please refer to Figure 3a and will not be described in detail here.

[0136] Exemplarily, the high MAC layer or the low MAC layer can be implemented by a processor in a chip system of a multi-link device, or can be implemented by different processing modules in a chip system, etc., which will not be listed in the embodiments of the present application. It can be understood that Figures 3a and 3b can be understood as the division of functional modules of a multi-link device. The modules shown in Figures 3a and 3b can be implemented in the form of hardware or in the form of software functional modules. The PHY and MAC layers shown in Figures 3a and 3b can be understood as a division of logical functions, and there can be other division methods in actual implementation. The n shown in Figures 3a and 3b can be equal to 0, or equal to 1, or n is an integer greater than 1, etc.

[0137] For example, the multi-link device in the embodiments of the present application can be a single-antenna device or a multi-antenna device. For example, it can be a device with more than two antennas. The embodiments of the present application do not limit the number of antennas included in the multi-link device. Figure 3c is a schematic diagram of the antennas of the MLD provided in the embodiments of the present application. Figure 3c uses an AP MLD with multiple antennas and a non-AP MLD with a single antenna as an example, but this should not be construed as limiting the embodiments of the present application.

[0138] The frequency bands in which the multi-link device operates may include but are not limited to: sub 1 GHz, 2.4 GHz, 5 GHz, 6 GHz and high frequency 60 GHz. Figures 4a and 4b show two schematic diagrams of a multi-link device communicating with other devices via multiple links in a wireless local area network.

[0139] FIG4 a shows a communication scenario between an AP MLD 101 and a non-AP MLD 102 . The AP MLD 101 includes subordinate APs 101 - 1 and 101 - 2 , and the non-AP MLD 102 includes subordinate STAs 102 - 1 and 102 - 2 . The AP MLD 101 and the non-AP MLD 102 communicate in parallel using links 1 and 2 .

[0140] For example, Figure 4b illustrates a scenario in which 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 101-3; non-AP MLD 102 includes three subordinate STAs: 102-1, 102-2, and 102-3; non-AP MLD 103 includes two subordinate STAs: 103-1 and 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, STA 104 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 to STA 104 and STA 102-1 in non-AP MLD 102 over link 1. AP 101-2 operating in the 5 GHz band in AP MLD 101 can transmit uplink or downlink data with STA 103-1 operating in the 5 GHz band in non-AP MLD 103 via link 2, and can also transmit uplink or downlink data with STA 102-2 operating in the 5 GHz band in non-AP MLD 102 via link 2. AP 101-3 operating in the 6 GHz band in AP MLD 101 can transmit uplink or downlink data with STA 102-3 operating in the 6 GHz band in non-AP MLD 102 via link 3, and can also transmit uplink or downlink data with STA 103-2 in the non-AP MLD via link 3.

[0141] Figure 4a only shows that the AP MLD supports two frequency bands. Figure 4b only illustrates that AP MLD 101 supports three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), each frequency band corresponds to a link, and AP MLD 101 can operate on one or more of Link 1, Link 2, or Link 3. On the AP side or STA side, a link can also be understood as a station operating on that link. In actual applications, the AP MLD and non-AP MLD can also support more or fewer frequency bands, that is, the AP MLD and non-AP MLD can operate on more or fewer links, but this embodiment of the present application does not limit this. Figures 4a and 4b are merely simple schematic diagrams and do not limit the scope of protection of the embodiments of the present application.

[0142] The following is an explanation of the relevant technical features involved in the embodiments of the present application. It should be noted that these explanations are intended to make the embodiments of the present application easier to understand and should not be regarded as limiting the scope of protection claimed by the present application.

[0143] 1. TID-to-link mapping element

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

[0145] During the multi-link establishment process, service identifiers and links can be mapped between multi-link devices. For example, the AP MLD can carry this mapping information in beacon frames or probe response frames, allowing all stations to adopt the corresponding mapping method after receiving this mapping information. Carrying this mapping information in beacon frames or probe response frames is also called broadcast TID-link mapping, which can effectively improve signaling transmission efficiency.

[0146] Exemplarily, the mapping information between the service identifier and the link can be carried in a TID-to-link mapping element. Please refer to Figure 5, which is a schematic diagram of the frame structure of the TID-to-link mapping element provided in an embodiment of the present application. As shown in Figure 5, 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 (TID-to-link mapping control), mapping switch time, expected duration (or expected duration, expected duration, expected 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.

[0147] Exemplarily, 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 and 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. The mapping switch time field exists when the TID-to-link mapping element is carried in a beacon frame or a probe response frame. When the above-mentioned mapping relationship has taken effect, the mapping switch time field may not be carried in the beacon frame or the probe response frame.

[0148] 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 accuracy of TBTT is time unit (TU), 1TU = 1024us. Generally speaking, AP MLD will broadcast the value of the time synchronization function (TSF) timer in the beacon frame. After receiving the value of the TSF timer, the non-AP MLD can update its locally maintained system time to the value of the TSF timer, so as to achieve the purpose of making the time of all non-AP MLDs in the BSS the same as that of the AP MLD (i.e., time synchronization).

[0149] 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 time when the new mapping relationship takes effect, that is, 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 (us). For example, the TSF timer corresponding to all non-AP MLDs on a link can be the same, and the TSF timers corresponding to non-AP MLDs on different links can be different.

[0150] Exemplarily, the expected duration field can be used to indicate the expected end time of the mapping relationship between the service identifier and the link, or to indicate the expected end time of the mapping between the service identifier and the link. For example, the expected duration field is used to indicate the effective duration of the service identifier and the link mapping (when the mapping switch time field is carried in the TID-to-link mapping element) or the remaining time (when the mapping switch time field is not carried in the TID-to-link mapping element). The expected duration field is present when the TID-to-link mapping element is carried in a beacon frame or a probe response frame.

[0151] Exemplarily, the link mapping of TID 0 field is used to indicate which links TID 0 is mapped to. For example, the field can carry a bitmap, and each bit in the bitmap can correspond to a link. For example, if the value of a certain bit is 1, it means that TID 0 is mapped to the link corresponding to the certain bit. For another example, if the value of a certain bit is 0, it means that TID 0 is not mapped to the link corresponding to the certain bit. Exemplarily, the length of the above-mentioned bitmap can be equal to the maximum number of links that can be associated between multi-link devices; or, the length of the above-mentioned bitmap can be a fixed value, such as 16 bits; or, the length of the above-mentioned bitmap can be equal to the number of associated links established between multi-link devices, etc. The embodiment of the present application does not limit the setting method of the length of the above-mentioned bitmap. For the description of the link mapping field of other ITDs, please refer to the link mapping of TID 0 field, which will not be described in detail here. The TIDs TID0 to TID7 shown in the embodiments of this application are merely examples. As the standard evolves, more service types may be added, such as TID0 to TID15. Therefore, the embodiments of this application do not limit the number of TID link mapping fields in the TID-to-link mapping element. For example, the number of TID link mapping fields in the TID-to-link mapping element can be the same as the type of TID. For example, if the TIDs are expanded from TID0 to TID7 to TID0 to TID15, the number of TID link mapping fields can be 16.

[0152] When a link has a TID mapped to it, it is considered enabled. When no TID is mapped to a link, it is considered disabled. AP MLD can carry the TID-to-Link Mapping element in beacon frames or probe response frames to enable or disable a link.

[0153] It is understood that for unicast, when the communicating parties negotiate the service identifier-link mapping information, the mapping information generally takes effect immediately. Because the mapping switch time field and the expected duration field need to be sent multiple times in a beacon frame or probe response frame to ensure that one or more non-AP MLDs can receive the TID-to-link mapping element, the mapping switch time field and the expected duration field are usually present when the TID-to-link mapping element is carried in a beacon frame or probe response frame.

[0154] For example, referring to Figure 5 , the TID-to-link mapping control field may include at least one of the following fields: direction, default link mapping (or default link mapping), mapping switch time present, expected duration present, reserved (or reserved), and link mapping presence indicator. Optionally, the TID-to-link mapping control field also includes a link mapping presence indicator field. The TID-to-link mapping control field may be used to carry control information related to the service identifier and link mapping. Exemplarily, the TID-To-link mapping control field is described as follows: the direction field can be used to indicate whether the direction of the service is uplink, downlink, or both uplink and downlink; 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.

[0155] It is understood 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 each established link, the TID-To-link mapping control field may not include a link mapping existence indication, and the TID-to-link mapping element may not include the link mapping field for TID 0 to the link mapping field for TID 7.

[0156] It is understood that the mapping information of the service identifier and the link, the mapping relationship between the service identifier and the link (or simply the mapping relationship), the mapping of the service identifier and the link, etc. involved in the embodiments of the present application can be interchangeable. The mapping relationship between the service identifier and the link indicated by the TID-to-link mapping element involved in the embodiments of the present application can be simply referred to as the mapping relationship (or mapping information) indicated by the TID-to-link mapping element.

[0157] 2. TU Boundary

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

[0159] Based on 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 the probe response frame, where the indicated effective start time of the service identifier and link mapping can be the TBTT indicated by the DTIM beacon frame of any link. It is understandable that the TBTT on a certain link (for example, link 1) is the TU boundary of that link, but it is not necessarily the TU boundary of other links (for example, link 2, link 3, etc.) (this is because the TSF timer values ​​of different links are selected independently. When the lower 10 bits of the TSF timer of a link (for example, link 1) are 0, the lower 10 bits of the TSF timer of another link are not necessarily 0). The time accuracy that the mapping switch time field in the TID-to-Link Mapping element can indicate is TU. As a result, the mapping switch time field in the TID-to-Link Mapping element on one link cannot indicate the TU boundary on another link, nor can it indicate the TBTT of the other link. That is, 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 the non-AP MLD.

[0160] For example, see Figure 6, which illustrates a scenario in which the mapping switch time field in a beacon frame indicates the effective start time of the service identifier and link mapping. As shown in Figure 6, 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, that is, time t0. However, if the AP MLD sends a beacon frame on link 1, the Mapping Switch Time field in the TID-to-Link Mapping element in the beacon frame sent by the AP MLD on link 1 only indicates the TU boundary up to Link 1, such as time t1 (or time t2) in Figure 6. Consequently, the non-AP MLD considers the effective start time of the service identifier and link mapping to be t1 (or t2), which deviates from time t0. Understandably, when this deviation occurs, the AP MLD and the non-AP MLD will have inconsistent understandings of the effective start time of the service identifier and link mapping, resulting in unreliable communication between the AP MLD and the non-AP MLD. For example, if the service identifier and link mapping indicate that a link (e.g., link 3) will be closed, and the non-AP MLD considers the effective start time to be later than the AP MLD's, the AP MLD may have already closed link 3, but the non-AP MLD has not yet closed link 3. In this case, the non-AP MLD may continue to send data or information to the AP MLD, but the AP MLD is unable to respond with an acknowledgment frame, resulting in low communication reliability. For another example, if the service identifier and link mapping indicate that link 3 will be opened, and the non-AP MLD considers the effective start time to be later than the AP MLD's, the AP MLD may have already opened link 3, but the non-AP MLD has not yet opened link 3. If the AP MLD initiates a transmission to the non-AP MLD before the non-AP MLD opens link 3, the non-AP MLD will not be able to properly receive the data or information sent by the AP MLD, resulting in low communication reliability.

[0161] Based on this, the prior art proposes that an offset field can be added to the TID-to-Link Mapping element to indicate an offset value. For example, taking the scenario shown in FIG6 as an example, based on the solution of the prior art, the indicated offset value can be (t0-t1) (or, the indicated offset value can be (t0-t2)). Therefore, when the non-AP MLD receives the TID-to-Link Mapping element in the beacon frame, combined with t1 (or t2) indicated by the Mapping Switch Time field in the TID-to-Link Mapping element and the offset value (t0-t1) (or offset 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 considered by the non-AP MLD is t0. Although this method of the prior art can ensure that the AP MLD and the non-AP MLD have the same understanding of the effective start time of the service identifier and link mapping, the method of adding a new field in the prior art increases the signaling overhead. Therefore, the present application proposes another method that does not require adding a new field to solve the AP problem. This solves the problem of inconsistent understanding of the effective start time of service identifier and link mapping between AP MLD and non-AP MLD, which is conducive to improving the communication reliability between AP MLD and non-AP MLD.

[0162] 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 briefly referred to as the "effective start time", and the "target effective start time of the service identifier and link mapping" can also be briefly referred to as the "target effective start time".

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

[0164] Please refer to Figure 7, which is a flow chart of the communication method provided by an embodiment of the present application. As shown in Figure 7, the communication method includes the following steps S701 to S702. The execution subject of the method shown in Figure 7 can be AP MLD and non-AP MLD, or the execution subject of the method shown in Figure 7 can also be a chip in AP MLD and a chip in non-AP MLD. For the convenience of description, Figure 7 mainly uses AP MLD and non-AP MLD as the execution subject of the method for example. It should be noted that Figure 7 is a schematic flow chart of an embodiment of the method of the present application, showing the detailed communication steps or operations of the method, but these steps or operations are only examples. The embodiment of the present application can also perform other operations or variations of the various operations in Figure 7. In addition, the various steps in Figure 7 can be executed in a different order from that presented in Figure 7, and it is possible that not all operations in Figure 7 need to be executed. Among them:

[0165] S701: An AP MLD may send at least one first frame on at least one first link. Correspondingly, a non-AP MLD may receive at least one first frame on at least one first link.

[0166] Exemplarily, before sending at least one first frame on at least one first link, the AP MLD may further generate the at least one first frame. Therefore, the AP MLD may respectively send a first frame of the at least one first frame on each first link of the at least one first link. That is, for the generated at least one first frame, each first frame in the at least one first frame may be respectively sent via a first link. Optionally, the at least one first link may include a third link.

[0167] Among them, 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. Exemplarily, the effective start time of the service identifier and link mapping indicated by different first frames can be different. 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 example, assume that there are 3 first links, namely link1-1, link1-2, and link1-3, wherein the first frame 1 is sent on link1-1, the first frame 2 is sent on link1-2, and the first frame 3 is sent on link1-3. The first frame 1 indicates the effective start time 1, the first frame 2 indicates the effective start time 2, and the first frame 3 indicates the effective start time 3, wherein the effective start time 1, the effective start time 2 and the effective start time 3 can be different (or different from each other / completely different), that is, the effective start time 1 ≠ the effective start time 2 ≠ the effective start time 3. Optionally, effective start time 1, effective start time 2, and effective start time 3 may be partially the same and partially different, for example, effective start time 1 = effective start time 2 ≠ effective start time 3.

[0168] The first frame may be a beacon frame or a probe response frame, etc., which is not limited in this application. The effective start time of the service identifier and link mapping may be specifically indicated by the mapping switch time field in the first frame. Optionally, the mapping switch time field may be carried in a TID-to-Link mapping element included in the first frame.

[0169] S702: The non-AP MLD determines a target effective start time of a mapping between a service identifier and a link according to at least one first frame.

[0170] 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 from at least one effective start time indicated by the at least one first frame as the target effective start time of the service identifier and link mapping, wherein:

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

[0172] In one implementation manner 2, the non-AP MLD may select a maximum effective start time from at least one effective start time indicated in at least one received first frame as the target effective start time for the service identifier and link mapping. In other words, the target effective start time for the service identifier and link mapping is the maximum effective start time among the at least one obtained effective start time.

[0173] In one implementation manner 3, the non-AP MLD may select a minimum effective start time from at least one effective start time indicated in at least one received first frame as the target effective start time for the service identifier and link mapping. In other words, 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.

[0174] The following details the processing rules proposed in embodiments of the present application to address the issue of inconsistent understanding of the effective start time of service identifier and link mapping between AP MLD and non-AP MLD. The overall concept of this processing rule is: AP MLD determines a time period [Ta, Tb] and ensures that the effective start 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, the following embodiments of the present application will refer to time point Ta as Ta and time point Tb as Tb. Specifically, this includes one or more of the following rules:

[0175] Rule 1: When the service identifier and link mapping in the first frame indicates that a link (for ease of description, this application takes the second link as an example for schematic illustration) is disabled, the AP MLD disables the second link no earlier than Tb.

[0176] Rule 2: When the service identifier and link mapping in the first frame indicates that the second link is enabled, the AP MLD enables the second link no later than Ta.

[0177] Rule 3: When the service identifier and link mapping in the first frame indicate that the second link is closed, the AP MLD does not initiate transmission to the first non-AP MLD on the second link if it is later than Ta.

[0178] Rule 4: When the service identifier and link mapping in the first frame indicates that the second link is enabled, the AP MLD does not initiate transmission to the first non-AP MLD on the second link before Tb.

[0179] Rule 5: When the service identifier and link mapping in the first frame indicate that the second link is closed, the AP MLD terminates transmission of the first non-AP MLD on the second link 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 terminates transmission of the first non-AP MLD on the second link before Ta).

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

[0181] Rule 7: When the AP MLD is later than Ta and earlier than Tb, it does not initiate transmission to the first non-AP MLD on the second link.

[0182] It is understandable that if, according to the indication of the service identifier and link mapping, no service identifier (TID) is mapped to a link in any direction (including uplink and downlink), then this link will be closed; if, according to the indication of the service identifier and link mapping, there is a service identifier (TID) mapped to a link in any direction (including uplink and downlink), then this link will be opened.

[0183] It should be noted that in the embodiments of the present application, "no earlier than" can also be replaced by "later than" or "greater than" or "greater than or equal to". Correspondingly, "no later than" can also be replaced by "earlier than" or "less than" or "less than or equal to", and the present application does not impose any limitation on this.

[0184] It should be noted that the above-mentioned Ta and / or Tb can be determined based on the first time and / or the second time. Among them, the first time is 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 based on the TBTT corresponding to the DTIM beacon frame of the third link. In other words, the first time in the embodiment of the present application can be understood as a reference time. Optionally, the DTIM beacon frame of the aforementioned third link can also be other non-DTIM beacon frames on the third link. There is no restriction here. For the sake of ease of understanding, this application mainly uses the TBTT corresponding to the DTIM beacon frame of the third link as an example for schematic explanation.

[0185] It is understandable that when any of the at least one first link is a third link, the service identifier and link mapping indicated by the first frame sent on the any first link take effect starting at the first time (for example, t0 in FIG6 ); when any of the at least one first link is not a third link, the service identifier and link mapping indicated by the first frame sent on the any first link take effect starting at the second time, and the second time is the TU boundary on the any first link. For the convenience of description, the following text mainly uses a first link among the at least one first link as an example to explain the concept of the second time on the first link involved in this application.

[0186] Optionally, the first understanding of the second time being a TU boundary on the first link is: the second time is a TU boundary on the first link that is closest to the first time (such as t1 or t2 in FIG6 ).

[0187] Optionally, the second understanding of the second time being a TU boundary on the first link is that the second time may be before the first time, and the second time is the TU boundary on the first link closest to the first time (such as t1 in Figure 6).

[0188] Optionally, a third understanding of the second time being a TU boundary on the first link is that 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 (eg, t2 in FIG6 ).

[0189] The following describes the values ​​of Ta and Tb in different situations:

[0190] It should be noted that, in the following description of the present application, the first time (or second time) corresponding to the first link may be understood as: the effective start time of the first frame indication sent by the AP MLD on the first link.

[0191] Case 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 aforementioned "not initiating transmission to the first non-AP MLD on the second link" can be understood as not initiating transmission on the second link to any non-AP MLD that has established multi-link communication with the AP MLD. It should be noted that in Case 1, the values ​​of Ta and Tb apply to all non-AP MLDs that have established multi-link communication with the AP MLD.

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

[0193] Ta and Tb are determined in the following manner: 1.1. Ta is determined based on the first time and the length of the TU, and Tb is determined based on the first time. For example, the length of 1TU is 1024µs. For example, Ta is the difference between the first time and the length of the TU (i.e., Ta = first time - 1TU), and Tb is the first time (i.e., Tb = first time).

[0194] For example, please refer to Figure 8a, which is a scenario diagram of Ta and Tb provided in an embodiment of the present application. As shown in Figure 8a, it is assumed that the effective start time of the service identifier and link mapping is the TBTT corresponding to the DTIM beacon frame on link 2, that is, the time point t0 is used as a reference, that is, the first time is t0. Assume that all the first links of AP MLD are link1-1, link1-2 and link1-3 as shown in Figure 8a. If it is scenario 1, for the first frame sent on link1-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 sent on link1-2, the effective start time of the service identifier and link mapping indicated by the first frame is time point t3, and for the first frame sent on link1-3, the effective start time of the service identifier and link mapping indicated by the first frame is time point t5. That is to say, the first time is t0, and the second time includes t1, t3 and t5. If Ta=first time-1TU, Tb=first time, then the positions of Ta and Tb are the positions of Ta and Tb shown in FIG8a.

[0195] Ta and Tb are determined in accordance with method 1.2: Ta is determined based on the minimum of 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 of all second times corresponding to all first links of the AP MLD (i.e., Ta = the minimum of 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 is any non-AP MLD that has established multi-link communication with the AP MLD.

[0196] For example, please refer to Figure 8b, which is another scenario diagram of Ta and Tb provided in an embodiment of the present application. As shown in Figure 8b, 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, that is, the time point t0, that is, the first time is t0. All the first links of the AP MLD are link1-1, link1-2 and link1-3 as shown in ① in Figure 8b. If it is scenario 1, for the first frame sent on link1-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 sent on link1-2, the effective start time of the service identifier and link mapping indicated by the first frame is time point t3, and for the first frame sent on link1-3, the effective start time of the service identifier and link mapping indicated by the first frame is time point t5. That is to say, the first time is t0, and the second time includes t1, t3 and t5. If Ta=the minimum value of all second times corresponding to all first links of the AP MLD, and Tb=the first time, then the positions of Ta and Tb are as shown in FIG8b , where the minimum value of all second times corresponding to all first links of the AP MLD is t1 (because t1<t3<t5).

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

[0198] Method 2.1 for determining the values ​​of Ta and Tb: Ta is determined based on the first time, and Tb is determined based on the first time and the length of the TU. For example, Ta is the first time (i.e., Ta = the first time), and Tb is the sum of the first time and the length of the TU (i.e., Tb = the first time + 1TU).

[0199] For example, please refer to Figure 8c, which is another scenario diagram of Ta and Tb provided in an embodiment of the present application. As shown in Figure 8c, 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, that is, the time point t0 as a reference, that is, the first time is t0. All the first links of the AP MLD are link1-1, link1-2 and link1-3 as shown in Figure 8c. If it is scenario 2, for the first frame sent on link1-1, the effective start time of the service identifier and link mapping indicated by the first frame is time point t2, for the first frame sent on link1-2, the effective start time of the service identifier and link mapping indicated by the first frame is time point t4, and for the first frame sent on link1-3, the effective start time of the service identifier and link mapping indicated by the first frame is time point t6. That is to say, the first time is t0, and the second time includes t2, t4 and t6. If Ta=first time, Tb=first time+1TU, then the positions of Ta and Tb are the positions of Ta and Tb shown in FIG8 c .

[0200] Ta and Tb are determined in accordance with method 2.2. 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 the AP MLD. For example, Ta is the first time (i.e., Ta = the first time), and Tb is the maximum time among all second times corresponding to all first links of the AP MLD (i.e., Tb = the maximum time among all second times corresponding to all first links of the AP MLD).

[0201] For example, please refer to Figure 8d, which is another scenario diagram of Ta and Tb provided in an embodiment of the present application. As shown in Figure 8d, 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, that is, the time point t0 is used as a reference, that is, the first time is t0. All the first links of the AP MLD are link1-1, link1-2 and link1-3 as shown in Figure 8d. If it is scenario 2, for the first frame sent on link1-1, the effective start time of the service identifier and link mapping indicated by the first frame is time point t2, for the first frame sent on link1-2, the effective start time of the service identifier and link mapping indicated by the first frame is time point t4, and for the first frame sent on link1-3, the effective start time of the service identifier and link mapping indicated by the first frame is time point t6. That is to say, the first time is t0, and the second time includes t2, t4 and t6. If Ta=first time, Tb=first time+1TU, then the positions of Ta and Tb are as shown in FIG8 d , where the maximum value of all second times corresponding to all first links of the AP MLD is t6 (because t2<t4<t6).

[0202] 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):

[0203] Method 3.1 for determining the values ​​of Ta and Tb: Ta is determined based on the minimum time among all second times and / or first times corresponding to all first links of the 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 the AP MLD. For example, Ta is the minimum time among all second times and / or first times corresponding to all first links of the AP MLD (i.e., Ta = the minimum value 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 (i.e., Tb = the maximum value among all second times and / or first times corresponding to all first links of the AP MLD).

[0204] It should be noted that under the value selection method 3.1 of Ta and Tb, the above rule 1 can also be replaced with the description: when the service identifier and link mapping in the first frame indicate that the second link is closed (disabled), the time when the AP MLD closes the second link is not earlier than any time among all the second times and / or first times corresponding to all the first links of the AP MLD.

[0205] Optionally, under the value selection method 3.1 of Ta and Tb, the above rule 2 can also be replaced with the description: 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 time among all the second times and / or first times corresponding to all the first links of the AP MLD.

[0206] Optionally, under the value selection method 3.1 of Ta and Tb, the above rule 3 can also be replaced and described as: when the service identifier and link mapping in the first frame indicate that the second link is closed, the AP MLD does not initiate transmission to the first non-AP MLD on the second link after all second times and / or any time of the first time corresponding to all first links of the AP MLD.

[0207] Optionally, under the value selection method 3.1 for Ta and Tb, the above rule 4 can also be replaced and described as follows: when the service identifier and link mapping in the first frame indicate that the second link is turned on, the AP MLD does not initiate transmission to the first non-AP MLD on the second link before all second times and / or any time among the first times corresponding to all first links of the AP MLD.

[0208] Optionally, under the value selection method 3.1 for Ta and Tb, the above Rule 5 can also be replaced with the following description: 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 all second times and / or first times corresponding to all first links of the AP MLD.

[0209] Optionally, under the value selection method 3.1 of Ta and Tb, the above rule six can also be replaced and described as: when the service identifier and link mapping in the first frame indicate that the second link is turned on, the AP MLD can initiate transmission to the first non-AP MLD on the second link only after all second times and / or any time of the first time corresponding to all first links of the AP MLD.

[0210] For example, please refer to Figure 8e, which is another scenario diagram of Ta and Tb provided in an embodiment of the present application. As shown in Figure 8e, 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, that is, the time point t0 is used as a reference, that is, the first time is t0. All the first links of the AP MLD are link1-1, link1-2 and link1-3 as shown in Figure 8e. If it is scenario 3, for the first frame sent on link1-1, the effective start time of the service identifier and link mapping indicated by the first frame is time point t1 or t2, for the first frame sent on link1-2, the effective start time of the service identifier and link mapping indicated by the first frame is time point t3 or t4, and for the first frame sent on link1-3, the effective start time of the service identifier and link mapping indicated by the 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, the second time includes t1, t3, and t6 as an example. If Ta = the minimum value of all second times corresponding to all first links of the AP MLD, and Tb = the maximum value of all second times corresponding to all first links of the AP MLD, then the positions of Ta and Tb are shown in Figure 8e. The minimum value of all second times corresponding to all first links of the AP MLD is t1 (because t1 < t3 < t6), and the maximum value of all second times corresponding to all first links of the AP MLD is t6 (because t1 < t3 < t6).

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

[0212] Case 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 on the second link to any of the non-AP MLDs that have established multi-link communication with the AP MLD. It should be noted that in Case 2, the values ​​of Ta and Tb apply to a specific non-AP MLD that has established multi-link communication with the AP MLD. In other words, 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. Alternatively, the AP MLD needs to determine the values ​​of Ta and Tb for each non-AP MLD that has established multi-link communication with the AP MLD.

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

[0214] Method I.1 for determining the values ​​of Ta and Tb: Ta is determined based on the minimum of 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 of all second times corresponding to all first links established between the first non-AP MLD and the AP MLD (i.e., Ta = the minimum of 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).

[0215] It is understandable that in scenario I of the second situation, the implementation method for selecting the target effective start time for the service identifier and link mapping by non-AP MLD is not restricted (for example, it can be any of the implementation methods 1 to 3 above). That is, there is no restriction on which specific effective start time is selected by non-AP MLD from the at least one effective start time as the target effective start time. For example, the target effective start time can be any one of the at least one effective start time, or the maximum effective start time of the at least one effective start time, or the minimum effective start time of the at least one effective start time, etc., and no restriction is imposed here.

[0216] For example, please refer to Figure 9a, which is another scenario diagram of Ta and Tb provided in an embodiment of the present application. As shown in Figure 9a, 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, that is, the time point t0, that is, the first time is t0. All first links established between the first non-AP MLD and the AP MLD are link1-1 and link1-2 as shown in Figure 9a. If it is scenario I, for the first frame sent on link1-1, the effective start time of the service identifier and link mapping indicated by the first frame is time point t1, and for the first frame sent on link1-2, the effective start time of the service identifier and link mapping indicated by the first frame is time point t3. In other words, the first time is t0, and the second time includes t1 and t3. The target validation time determined by the non-AP MLD is not limited to which of the at least one validation start time indicated by the received first frame. If Ta = the minimum 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 shown in FIG9a , 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).

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

[0218] Method II.3 for determining the values ​​of Ta and Tb: Ta is determined based on the first time, and Tb is determined based on the maximum of 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 = the first time), and Tb is the maximum of all second times corresponding to all first links established between the first non-AP MLD and the AP MLD (i.e., Tb = the maximum of all second times corresponding to all first links established between the first non-AP MLD and the AP MLD).

[0219] It is understandable that in Scenario II of the second situation, there is no restriction on the implementation method for selecting the target effective start time for the service identifier and link mapping by non-AP MLD (for example, it can be any of the implementation methods 1 to 3 above). That is, there is no restriction on which specific effective start time is selected by non-AP MLD from the at least one effective start time as the target 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 the at least one effective start time, or the target effective start time can be the minimum effective start time among the at least one effective start time, and the like. No restriction is imposed here.

[0220] For example, please refer to Figure 9b, which is another scenario diagram of Ta and Tb provided in an embodiment of the present application. As shown in Figure 9b, 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, that is, the time point t0, that is, the first time is t0. All the first links established between the first non-AP MLD and the AP MLD are link1-1 and link1-2 as shown in Figure 9b. If it is scenario II, for the first frame sent on link1-1, the effective start time of the service identifier and link mapping indicated by the first frame is time point t2, and for the first frame sent on link1-2, the effective start time of the service identifier and link mapping indicated by the first frame is time point t4. That is to say, the first time is t0, and the second time includes t2 and t4. The target validation time determined by the non-AP MLD is not limited to which of the at least one validation start time indicated by the received first frame. If Ta = the first time, and Tb = the maximum value of 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 shown in FIG9b , 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).

[0221] 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 non-AP MLD determines the target effective start time of the service identifier-link mapping based on Implementation 1 above:

[0222] Method III.1 for determining the values ​​of Ta and Tb: 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 the AP MLD, and 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 the 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 the AP MLD (i.e., Ta = the minimum value of 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 (i.e., Tb = the maximum value of all second times and / or first times corresponding to all first links established between the first non-AP MLD and the AP MLD).

[0223] It is understandable that in scenario III of the second situation, the implementation method for selecting the target effective start time for the service identifier and link mapping by non-AP MLD is not restricted (for example, it can be any of the implementation methods 1 to 3 above). That is, there is no restriction on which specific effective start time is selected by non-AP MLD from the at least one effective start time as the target 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 the at least one effective start time, or the target effective start time can be the minimum effective start time among the at least one effective start time, and the like. No restriction is imposed here.

[0224] For example, please refer to Figure 9c, which is another scenario diagram of Ta and Tb provided in an embodiment of the present application. As shown in Figure 9c, 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, that is, time point t0, that is, the first time is t0. All first links established between the first non-AP MLD and the AP MLD are link1-1 and link1-2 as shown in Figure 9c. If it is scenario III, for the first frame sent on link1-1, the effective start time of the service identifier and link mapping indicated by the first frame is time point t1 or t2, and for the first frame sent on link1-2, the effective start time of the service identifier and link mapping indicated by the 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, the second time includes t1 and t4 as an example. The target validation time determined by the non-AP MLD is not limited to which of the at least one validation start time indicated by the received first frame. If Ta = the minimum value of all second times corresponding to all first links established between the first non-AP MLD and the AP MLD, and Tb = the maximum value of 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 shown in FIG9c . 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<t4), and 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 t1<t4).

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

[0226] Method IV.1 for determining the values ​​of Ta and Tb: 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 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 first time (i.e., Tb = the first time).

[0227] It is understandable that in scenario IV of the second situation, 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 non-AP MLD is the maximum effective start time among the at least one obtained effective start time.

[0228] For example, please refer to Figure 9d, which is another scenario diagram of Ta and Tb provided in an embodiment of the present application. As shown in Figure 9d, 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, that is, the time point t0, that is, the first time is t0. All first links established between the first non-AP MLD and the AP MLD are link1-1 and link1-2 as shown in Figure 9d. If it is scenario IV, for the first frame sent on link1-1, the effective start time of the service identifier and link mapping indicated by the first frame is time point t1, and for the first frame sent on link1-2, the effective start time of the service identifier and link mapping indicated by the first frame is time point t3. That is to say, the first time is t0, and the second time includes t1 and t3. If the target validation time determined by the non-AP MLD is the maximum validation time (i.e., t3) among at least one validation start time indicated in the received first frame (t1 and t3 as shown in FIG9d ), and 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 shown in FIG9d , 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).

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

[0230] Ta and Tb are determined using method 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 = 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 (i.e., Tb = the minimum value of all second times and / or first times).

[0231] It is understandable that in scenario V of the second situation, 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 non-AP MLD is the minimum effective start time among the at least one obtained effective start time.

[0232] For example, please refer to Figure 9e, which is another scenario diagram of Ta and Tb provided in an embodiment of the present application. As shown in Figure 9e, 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, that is, the time point t0, that is, the first time is t0. All first links established between the first non-AP MLD and the AP MLD are link1-1 and link1-2 as shown in Figure 9e. If it is scenario V, for the first frame sent on link1-1, the effective start time of the service identifier and link mapping indicated by the first frame is time point t2, and for the first frame sent on link1-2, the effective start time of the service identifier and link mapping indicated by the first frame is time point t4. That is to say, the first time is t0, and the second time includes t2 and t4. If the target validation time determined by the non-AP MLD is the minimum validation time (i.e., t2) among at least one validation start time indicated in the received first frame (t2 and t4 as shown in FIG. 9e ), and if Ta = the first time, and Tb = the minimum value of 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 shown in FIG. 9e , 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).

[0233] 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" in the embodiments of this application, a specific example is provided below. For example, assuming that 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 the N first links, and all first links established between the first non-AP MLD and the AP MLD can be understood as the M first links, where N is a positive integer greater than or equal to M.

[0234] In the present application, if a link (for example, the second link is used as an example in this application for schematic illustration) is to be shut down, the AP MLD is shut down the latest (i.e., later than the shutdown 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 in this application for schematic illustration) is to be opened, the AP MLD is opened the earliest (i.e., earlier than the startup 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 the non-AP MLD caused by inconsistent understanding of the mapping effective time between the AP MLD and the non-AP MLD can be solved.

[0235] The above content elaborates on the method of the present application in detail. In order to facilitate better implementation of the above scheme of the embodiment of the present application, the embodiment of the present application also provides corresponding devices or equipment.

[0236] The present application divides the functional modules of the communication device according to the above-mentioned method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in this application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The communication device of the embodiment of the present application will be described in detail below with reference to Figures 10 to 12.

[0237] Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in Figure 10, 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 to process data. For example, the transceiver unit 1002 can also be referred to as a communication interface or a communication unit.

[0238] In some embodiments of the present application, the communication device can be used to execute the actions performed by the AP MLD in the above method embodiment. In this case, the communication device can be an AP MLD or a component that can be configured in the AP MLD (such as a chip or system, etc.), the transceiver unit 1002 is used to execute the AP MLD transmission and reception related operations in the above method embodiment, and the processing unit 1001 is used to execute the AP MLD processing related operations in the above method embodiment.

[0239] In some embodiments of the present application, the communication device may be the AP MLD or chip shown above, and the chip may be provided in the AP MLD. That is, the communication device may be used to execute the steps or functions performed by the AP MLD in the above method embodiments.

[0240] The processing unit 1001 is configured to generate at least one first frame; the transceiver unit 1002 is configured to send the at least one first frame on at least one first link.

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

[0242] In other embodiments of the present application, the communication device can be used to execute 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 a non-AP MLD. The transceiver unit 1002 is used to execute operations related to the transmission and reception of the non-AP MLD in the above method embodiments, and the processing unit 1001 is used to execute operations related to the processing of the non-AP MLD in the above method embodiments. In other words, the communication device can be used to execute the steps or functions performed by the non-AP MLD in the above method embodiments.

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

[0244] It is understandable that the specific description of the processing unit 1001 parsing the first frame to determine the target effective start time can be referred to the method embodiment shown above, and will not be described in detail here.

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

[0246] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above-mentioned method embodiment and will not be described in detail here.

[0247] In the above embodiments, the descriptions of the first frame, the first time, the second time, Ta, Tb, etc. can also refer to the introduction in the above method embodiments, and will not be described in detail here.

[0248] The above describes the communication device according to the embodiment of the present application. The following describes possible product forms of the communication device. It should be understood that any product having the functions of the communication device described in FIG. 10 falls within the scope of protection of the embodiment of the present application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the communication device according to the embodiment of the present application to these examples.

[0249] In one possible implementation, in the communication device shown in Figure 10, the processing unit 1001 can be one or more processors, the transceiver unit 1002 can be a transceiver, or the transceiver unit 1002 can also be a sending unit and a receiving unit, the sending unit can be a transmitter, the receiving unit can be a receiver, and the sending unit and the receiving unit are integrated into a single device, such as a transceiver. In the embodiment of the present application, the processor and the transceiver can be coupled, etc., and the embodiment of the present application does not limit the connection method between the processor and the transceiver. During the execution of 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 it can be transmitted by the transceiver. After being output by the processor, the above information may also 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 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 be processed further before being input into the processor.

[0250] As shown in FIG. 11 , the communication device 110 includes one or more processors 1120 and a transceiver 1110 .

[0251] In some embodiments of the present application, the communication device may be used to execute the steps or functions performed by the AP MLD in the above method embodiments.

[0252] The processor 1120 is configured to generate at least one first frame; and the transceiver 1110 is configured to send the at least one first frame on at least one first link.

[0253] In other embodiments of the present application, the communication device may be used to execute the steps or functions performed by the non-AP MLD in the above method embodiments.

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

[0255] It will be understood that the specific descriptions of the transceiver and processor shown in the embodiments of the present application are merely examples. For the specific functions or execution steps of the transceiver and processor, reference may be made to the above-mentioned method embodiments, which will not be described in detail here.

[0256] In the above embodiments, the descriptions of the first frame, the first time, the second time, Ta, Tb, etc. can also refer to the introduction in the above method embodiments, and will not be described in detail here.

[0257] In various implementations of the communication device shown in FIG11 , the transceiver may include a receiver and a transmitter, wherein the receiver is configured to perform a receiving function (or operation) and the transmitter is configured to perform a transmitting function (or operation). The transceiver is configured to communicate with other devices / devices via a transmission medium.

[0258] 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 the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used 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 one or more memories may be included in the processor.

[0259] The specific connection medium between the transceiver 1110, processor 1120, and memory 1130 is not limited in the embodiments of the present application. In Figure 11, the memory 1130, processor 1120, and transceiver 1110 are connected via a bus 1140. The bus is represented by a bold line in Figure 11. The connection methods between other components are merely schematic and are not limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 11 only uses a single bold line, but this does not mean that there is only one bus or only one type of bus.

[0260] In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present application may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor, etc.

[0261] In the embodiment of the present application, memory may include but is not limited to non-volatile memories 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 portable read-only memory (CD-ROM), etc. Memory is any storage medium that can be used to carry or store program code in the form of instructions or data structures, and can be read and / or written by a computer (such as the communication device shown in the present application), but is not limited thereto. The memory in the embodiment of the present application can also be a circuit or other arbitrarily capable of realizing a storage function, for storing program instructions and / or data.

[0262] Illustratively, the processor 1120 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process software program data. The memory 1130 is primarily used to store software programs and data. The transceiver 1110 may include a control circuit and an antenna. The control circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0263] 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 sent wirelessly, the processor 1120 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency 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.

[0264] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.

[0265] It is understood that the communication device shown in the embodiment of the present application may also have more components than those in Figure 11, and the embodiment of the present application is not limited to this. The method performed by the processor and transceiver shown above is only an example. For the specific steps performed by the processor and transceiver, please refer to the method described above.

[0266] In another possible implementation, in the communication device shown in Figure 10, the processing unit 1001 can be one or more logic circuits, and the transceiver unit 1002 can be an input / output interface, or also called a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver unit 1002 can also be a sending unit and a receiving unit, the sending unit can be an output interface, and the receiving unit can be an input interface, and the sending unit and the receiving unit are integrated into one unit, such as an input / output interface. As shown in Figure 12, the communication device shown in Figure 12 includes a logic circuit 1201 and an interface 1202. That is, the above-mentioned processing unit 1001 can be implemented with a logic circuit 1201, and the transceiver unit 1002 can be implemented with an interface 1202. Among them, the logic circuit 1201 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface 1202 can be a communication interface, an input / output interface, a pin, etc. For example, Figure 12 is illustrated using the above-mentioned communication device as a chip, and the chip includes a logic circuit 1201 and an interface 1202.

[0267] In the embodiment of the present application, the logic circuit and the interface may also be coupled to each other. The embodiment of the present application does not limit the specific connection method between the logic circuit and the interface.

[0268] In some embodiments of the present application, the communication device may be used to execute the steps or functions performed by the AP MLD in the above method embodiments.

[0269] The logic circuit 1201 is configured to generate at least one first frame; and the interface 1202 is configured to send the at least one first frame on at least one first link.

[0270] In some further embodiments of the present application, the communication device may be used to execute the steps or functions performed by the non-AP MLD in the above method embodiments.

[0271] The interface 1202 is configured to receive at least one first frame on at least one first link; the logic circuit 1201 is configured to determine a target effective start time of the mapping between the service identifier and the link according to the at least one first frame.

[0272] It can be understood that the specific description of the logic circuit and interface shown in the embodiments of the present application is only an example. For the specific functions or execution steps of the logic circuit and interface, please refer to the above-mentioned method embodiment and will not be described in detail here.

[0273] In the above embodiments, the descriptions of the first frame, the first time, the second time, Ta, Tb, etc. can also refer to the introduction in the above method embodiments, and will not be described in detail here.

[0274] It can be understood that the communication device shown in the embodiment of the present application can implement the method provided in the embodiment of the present application in the form of hardware, or can implement the method provided in the embodiment of the present application in the form of software, etc., and the embodiment of the present application is not limited to this.

[0275] An embodiment of the present application further provides a wireless communication system, which includes an AP MLD and a non-AP MLD. The AP MLD and the non-AP MLD can be used to execute the method in any of the aforementioned embodiments.

[0276] In addition, the present application also provides a computer program, which is used to implement the operations and / or processing performed by the AP MLD in the method provided by the present application.

[0277] The present application also provides a computer program, which is used to implement the operations and / or processing performed by the non-AP MLD in the method provided in the present application.

[0278] The present application also provides a computer-readable storage medium having computer code stored therein. When the computer code is executed on a computer, the computer is enabled to execute the operations and / or processes performed by the AP MLD in the method provided in the present application.

[0279] The present application also provides a computer-readable storage medium having computer code stored therein. When the computer code is executed on a computer, the computer executes the operations and / or processing performed by the non-AP MLD in the method provided in the present application.

[0280] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program runs on a computer, the operations and / or processes performed by the AP MLD in the method provided by the present application are executed.

[0281] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program runs on a computer, the operations and / or processing performed by the non-AP MLD in the method provided by the present application are executed.

[0282] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0283] The units described as separate components may or may not be physically separate, and 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 may be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of the present application.

[0284] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0285] If the integrated unit is implemented in the form of 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 the present application is essentially 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, and the computer software product is stored in a readable storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned readable storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other media that can store program code.

[0286] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: include: The access point multi-link device AP MLD generates at least one first frame; The AP MLD sends the 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 (TID-to-Link Mapping); When the service identifier and link mapping indicates that the 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 enabled, the AP MLD enables the second link no later than time point Ta; The Ta is earlier than the Tb, and the Tb is determined according to a first time, where the first time is a target beacon transmission time TBTT corresponding to a service indication map DTIM beacon frame of the third link.

2. The method according to claim 1, characterized in that: The method comprises: 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 the first time; 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 a second time, and the second time is a 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 indicates that the second link is closed, the AP MLD does not initiate transmission to the first non-access point multi-link device non-AP MLD on the second link later than Ta; or, When the service identifier and link mapping indicates that the second link is started, the AP MLD does not initiate transmission to the first non-AP MLD on the second link before Tb.

4. The method according to any one of claims 1 to 3, characterized in that When the service identifier and link mapping indicates that the second link is closed, the AP MLD ends the transmission with the first non-AP MLD on the second link before Ta; or, When the service identifier and link mapping indicates that the second link is enabled, the AP MLD can initiate transmission to the first non-AP MLD on the second link only after Tb; The first non-AP MLDs are all non-AP MLDs that have established multi-link communication with the AP MLD.

5. The method according to claim 1, characterized in that The AP MLD does not initiate transmission to the first non-access point multi-link device non-AP MLD on the second link when the time is later than the Ta and earlier than the Tb.

6. The method according to any one of claims 1 to 5, characterized in that: The second time is a TU boundary closest to the first time on the first link.

7. The method according to any one of claims 1 to 6, characterized in that: The second time is before the first time, and the second time is a TU boundary closest to the first time on the first link.

8. The method according to claim 7, characterized in that The Ta is the difference between the first time and the length of TU, ​​and the Tb is determined according to the first time, specifically, the Tb is the first time; or, The Ta is the minimum time among all the second times corresponding to all the first links of the AP MLD, and the Tb is the first time.

9. The method according to claim 7, characterized in that: Ta is all second time points corresponding to all first links established between the first non-AP MLD and the AP MLD The minimum time in the interval, Tb is the first time.

10. The method according to claim 7, characterized in that The Ta is a maximum time among all second times and / or the first times corresponding to all the first links established between the first non-AP MLD and the AP MLD, and the Tb is the first time.

11. The method according to any one of claims 1 to 6, characterized in that: The second time is after the first time, and the second time is a TU boundary closest to the first time on the first link.

12. The method according to claim 11, characterized in that The Ta is the first time, and the Tb is the sum of the first time and the length of TU; or, The Ta is the first time, and the Tb is the maximum time of all second times corresponding to all the first links of the AP MLD.

13. The method according to claim 11, characterized in that The Ta is the first time, and the Tb is the maximum time of all second times corresponding to all the first links established between the first non-AP MLD and the AP MLD.

14. The method according to claim 11, characterized in that The Ta is the first time, and the Tb is the minimum time among all second times corresponding to all the first links established between the first non-AP MLD and the AP MLD and / or the first times.

15. The method according to any one of claims 1 to 6, characterized in that: The Ta is the minimum time among all the second times corresponding to all the first links of the AP MLD and / or the first time, and the Tb is the maximum time among all the second times corresponding to all the first links of the AP MLD and / or the first time.

16. The method according to any one of claims 1 to 6, characterized in that: The Ta is the minimum time of all second times and / or the first times corresponding to all the first links established between the first non-AP MLD and the AP MLD, and the Tb is the maximum time of all second times and / or the first times corresponding to all the first links established between the first non-AP MLD and the AP MLD.

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

18. The method according to any one of claims 1 to 17, characterized in that: The TU boundary is the time point when the lower 10 bits of the time synchronization function TSF timer are 0.

19. The method according to any one of claims 1 to 18, characterized in that: The first frame is a beacon frame or a probe response frame.

20. The method according to any one of claims 1 to 19, 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.

21. The method according to any one of claims 1 to 20, characterized in that: The service identifiers and link mappings indicated by different first frames have different effective start times.

22. A communication method, characterized in that: include: The non-access point multi-link device non-AP MLD receives at least one first frame on at least one first link, where the first frame indicates a starting time when a mapping between a service identifier and a link takes effect; The non-AP MLD determines a target effective start time of a mapping between a service identifier and a link according to the at least one first frame.

23. The method according to claim 22, characterized in that The service identifiers and link mappings indicated by different first frames have different effective start times.

24. The method according to claim 22 or 23, characterized in that The non-AP MLD determines, according to the at least one first frame, a starting time at which the mapping of the service identifier and the link takes effect, including: The non-AP MLD determines a valid start time of a service identifier and link mapping from the valid start time of at least one service identifier and link mapping indicated by the at least one first frame as the target valid start time of the service identifier and link mapping.

25. The method according to claim 24, characterized in that 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.

26. The method according to claim 25, characterized in that 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.

27. The method according to any one of claims 22 to 26, characterized in that: The first frame is a beacon frame or a probe response frame.

28. The method according to any one of claims 22 to 27, 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.

29. A communication device, comprising a unit or module for executing the method according to any one of claims 1 to 21, or comprising a unit or module for executing the method according to any one of claims 22 to 28.

30. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1-21 through a logic circuit or execute code instructions, or to implement the method as described in any one of claims 22-28.

Images