Multi-link communication method and apparatus

Abstract

A multi-link communication method and apparatus are disclosed that can be used in a wireless local area network system supporting 802.11 series protocols, such as the next-generation Wi-Fi protocol of IEEE 802.11ax, e.g., 802.11be, Wi-Fi 7, or EHT, and the next-generation protocol of 802.11be, e.g., Wi-Fi 8, UHR, or Wi-Fi AI, and can also be used in an ultra-bandwidth-based wireless personal local area network system and a sensing system. A transmitting end sends a radio frame. Correspondingly, a receiving end receives and parses the radio frame. The radio frame includes a first element and a second element. The first element includes an expected duration field. The expected duration field can be determined based on the nearest TBTT or TU boundary prior to the transmission time of the radio frame, or can be determined based on a TSF timer. This can ensure that the expected end time of the mapping relationship of the first element is the same as the time when the mapping relationship of the second element is established.

Description

[Technical Field]

[0001] The present application relates to the field of communication technologies, and in particular to a multi-link communication method and apparatus. [Background technology]

[0002] This application claims priority to Chinese Patent Application No. 202211582012.0, entitled "MULTI-LINK COMMUNICATION METHOD AND APPARATUS," filed with the State Intellectual Property Office of China on December 9, 2022, which is incorporated herein by reference in its entirety.

[0003] With the development of wireless technology, more and more wireless devices support multi-link communication. For example, devices support simultaneous communication on the 2.4 GHz frequency band, the 5 GHz frequency band, the 6 GHz frequency band, etc., or communication on different channels on the same frequency band to improve communication rates between devices. The devices are usually called multi-link devices (MLDs). A multi-link device may be an access point device or a station device. A station device may communicate with an access point device after multi-link setup (also called multi-link association).

[0004] In a multilink setup (or multilink association) process, a station in a multilink station device may send an association request frame to an access point in a multilink access point device. The association request frame carries a multilink element (MLE) (also called a multilink information element) for conveying information about the multilink station device and other stations in the device. Similarly, an association response frame returned by the access point to the station may also carry an MLE for conveying information about the multilink access point device and other access points in the device. Furthermore, to better manage traffic, traffic identifier (TID)-to-link mapping may be implemented between multilink devices to provide different services to different traffic. For example, non-critical traffic may be mapped to some of the links, and critical traffic may be mapped to all of the links. Alternatively, different traffic may be mapped to corresponding links based on the rate and latency characteristics of the different links.

[0005] However, in the process of switching traffic identifier-to-link mapping schemes, the effective time of the new mapping scheme usually does not match the end time of the old mapping scheme. Summary of the Invention

[0006] The embodiments of the present application provide a multi-link communication method and apparatus to effectively ensure that the effective time of a new mapping scheme matches the end time of an old mapping scheme.

[0007] According to a first aspect, an embodiment of the present application provides a multi-link communication method, the method comprising: generating a radio frame, the radio frame including a first traffic identifier-to-link mapping element and a second traffic identifier-to-link mapping element, the first traffic identifier-to-link mapping element including an expected duration field, the expected duration field indicating an expected end time of a traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element, the expected duration field being determined based on a most recent target beacon transmission time (TBTT) prior to a transmission time of the radio frame or determined based on a time synchronization function (TSF) timer; a mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established, and an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established; and transmitting a radio frame.

[0008] In this embodiment of the present application, the mapping switch time field in the second traffic identifier-to-link mapping element may be determined based on the TBTT of a future beacon frame (relative to the radio frame). Because the time difference between any two TBTTs on a link is in units of TU, ​​the expected end time indicated by the expected duration field is calculated by using the most recent TBTT prior to the transmission time of the radio frame as the starting point. This can effectively ensure that the expected end time can accurately indicate the establishment time indicated by the mapping switch time field in the second traffic identifier-to-link mapping element.

[0009] In this embodiment of the present application, the time indicated by the expected duration field is changed to an absolute time, for example, set to the system time at the end of the mapping relationship indicated by the first traffic identifier-to-link mapping element, which can effectively ensure that the expected end time indicated by the expected duration field in the first traffic identifier-to-link mapping element can indicate the establishment time indicated by the mapping switch time field in the second traffic identifier-to-link mapping element.

[0010] In a possible implementation, the expected duration field carries the same value as any one of the following: the value of bits 11 to 26 of the TSF timer, the value of bits 11 to 34 of the TSF timer, or the value of bits 11 to 50 of the TSF timer.

[0011] In this embodiment of the present application, the expected duration field in the second traffic identifier-to-link mapping element may be determined based on the TBTT of a future beacon frame, and may be set to the value of bits 11 to 26 of the TSF timer, for example. Thus, the expected duration field in the first traffic identifier-to-link mapping element may be set to the value of bits 11 to 26 of the TSF timer, the value of bits 11 to 34, etc. This can effectively ensure that the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element may be the same as the time when the mapping relationship indicated by the second traffic identifier-to-link mapping element is established.

[0012] In a possible implementation, the first traffic identifier-to-link mapping element is located before the second traffic identifier-to-link mapping element in the radio frame.

[0013] In this embodiment of the present application, after the sequence of the first traffic identifier-to-link mapping element and the second traffic identifier-to-link mapping element is fixed, the receiving end can parse different elements based on the sequence of the two elements to quickly know the time when the mapping relationship indicated by the second traffic identifier-to-link mapping element will be established and the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element.

[0014] According to a second aspect, an embodiment of the present application provides a multi-link communication method, the method comprising: receiving a radio frame, the radio frame including a first traffic identifier-to-link mapping element and a second traffic identifier-to-link mapping element, the first traffic identifier-to-link mapping element including an expected duration field, the expected duration field indicating an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element, the expected duration field being determined based on a most recent target beacon transmission time TBTT prior to the transmission time of the radio frame or determined based on a time synchronization function TSF timer; the second traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established, and the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established; and parsing the radio frame.

[0015] In a possible implementation, the step of parsing the radio frame comprises: determining an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element by using the most recent TBTT prior to the transmission time of the radio frame as a starting point and using the value carried in the expected duration field as the duration, or using the value carried in the expected duration field as the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element.

[0016] In a possible implementation, the expected duration field could be: Carries the same value as any one of the values ​​of bits 11 to 26 of the TSF timer, the values ​​of bits 11 to 34 of the TSF timer, or the values ​​of bits 11 to 50 of the TSF timer.

[0017] In a possible implementation, the first traffic identifier-to-link mapping element is located before the second traffic identifier-to-link mapping element in the radio frame.

[0018] The beneficial effects of the second aspect may be understood with reference to the first aspect.

[0019] According to a third aspect, an embodiment of the present application provides a multi-link communication method, the method comprising: generating a radio frame, the radio frame including a first traffic identifier-to-link mapping element and a second traffic identifier-to-link mapping element, the first traffic identifier-to-link mapping element not including an expected duration field, and the second traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established and an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element, or the first traffic identifier-to-link mapping element including an expected duration field, the second traffic identifier-to-link mapping element not including a mapping switch time field, and the expected duration field indicating an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element and a time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established; and transmitting the radio frame.

[0020] In this embodiment of the present application, the first traffic identifier-to-link mapping element does not include an expected duration field, and the second traffic identifier-to-link mapping element includes a mapping switch time field. Thus, the mapping switch time field may indicate the time when the mapping relationship indicated by the second traffic identifier-to-link mapping element is established and may indicate the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element. For example, the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element may be equal to the time when the mapping relationship indicated by the second traffic identifier-to-link mapping element is established by default. This effectively ensures that the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time when the mapping relationship indicated by the second traffic identifier-to-link mapping element is established.

[0021] In this embodiment of the present application, the first traffic identifier-to-link mapping element includes an expected duration field, and the second traffic identifier-to-link mapping element does not include a mapping switch time field. Therefore, the expected duration field may indicate the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element and the time at which the mapping relationship indicated by the second traffic identifier-to-link mapping element is established. For example, the time at which the mapping relationship indicated by the second traffic identifier-to-link mapping element is established may be equal to the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element by default. This effectively ensures that the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the mapping relationship indicated by the second traffic identifier-to-link mapping element is established.

[0022] In a possible implementation, the first traffic identifier-to-link mapping element is located before the second traffic identifier-to-link mapping element in the radio frame.

[0023] According to a fourth aspect, an embodiment of the present application provides a multi-link communication method, the method comprising: receiving a radio frame, the radio frame including a first traffic identifier-to-link mapping element and a second traffic identifier-to-link mapping element, the first traffic identifier-to-link mapping element not including an expected duration field, and the second traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established and an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element, or the first traffic identifier-to-link mapping element including an expected duration field, the second traffic identifier-to-link mapping element not including a mapping switch time field, and the expected duration field indicating an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element and a time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established; and parsing the radio frame.

[0024] In a possible implementation, the step of parsing the radio frame comprises: when the first traffic identifier-to-link mapping element does not include an expected duration field and the second traffic identifier-to-link mapping element includes a mapping switch time field, determining an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element based on the mapping switch time field, wherein the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established; or When the first traffic identifier-to-link mapping element includes an expected duration field and the second traffic identifier-to-link mapping element does not include a mapping switch time field, the method includes determining, based on the expected duration field, a time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established, wherein the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established.

[0025] In a possible implementation, the first traffic identifier-to-link mapping element is located before the second traffic identifier-to-link mapping element in the radio frame.

[0026] The beneficial effects of the fourth aspect may be understood with reference to the third aspect.

[0027] According to a fifth aspect, an embodiment of the present application provides a multi-link communication method, the method comprising: The method includes receiving a radio frame, the radio frame including a first traffic identifier-to-link mapping element and a second traffic identifier-to-link mapping element, the first traffic identifier-to-link mapping element including an expected duration field, the expected duration field indicating an expected end time of a traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element, and the second traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established; and determining, based on the expected duration field, a time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established, or determining, based on the mapping switch time field, an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element.

[0028] In this embodiment of the present application, the first traffic identifier-to-link mapping element includes an expected duration field, and the second traffic identifier-to-link mapping element includes a mapping switch time field. When the expected end time indicated by the expected duration field does not match the establishment time indicated by the mapping switch time field, the receiving end may use the time at which the mapping relationship indicated by the second traffic identifier-to-link mapping element will be established and the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element based on one of the expected duration field or the mapping switch time field. This effectively ensures that the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the mapping relationship indicated by the second traffic identifier-to-link mapping element will be established.

[0029] In a possible implementation, the step of determining, based on the mapping switch time field, an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element includes: When an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is later than the time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established, the method includes determining an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element based on a mapping switch time field, wherein the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is equal to the time at which the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established.

[0030] In a possible implementation, the first traffic identifier-to-link mapping element is located before the second traffic identifier-to-link mapping element in the radio frame.

[0031] According to a sixth aspect, an embodiment of the present application provides a multi-link communication method, the method comprising: generating a radio frame, the radio frame including a traffic identifier-to-link mapping element, the traffic identifier-to-link mapping element including a mapping switch time field and a first field, the mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the traffic identifier-to-link mapping element is established, the time being determined based on a first target beacon time (TBTT) on the first link, the first field indicating a time difference between the first TBTT on the first link and a time point on the second link corresponding to the first TBTT, the time point being a time point on the second link that is not later than the first TBTT and closest to the first TBTT, and the value of 10 least significant bits of a time synchronization function (TSF) timer for the time point being 0, or the time point being a TBTT on the second link; and sending the radio frame via the second link.

[0032] In this embodiment of the present application, the radio frame includes a time difference between a first TBTT on the first link and a corresponding time point on the second link, so that when the time at which the mapping relationship is established is determined based on the TBTT on the first link, the receiving end on the second link can still accurately determine, based on the radio frame, the time at which the mapping relationship corresponding to the second link is established.

[0033] In a possible implementation, the traffic identifier-to-link mapping element further includes a second field, the second field indicating the presence of the first field.

[0034] In a possible implementation, the value carried in the first field is the value of bits 1 to 10 of the Time Synchronization Function TSF timer of the Basic Service Set BSS corresponding to the second link.

[0035] According to a seventh aspect, an embodiment of the present application provides a multi-link communication method, the method comprising: receiving a wireless frame over a second link, the wireless frame including a traffic identifier-to-link mapping element, the traffic identifier-to-link mapping element including a mapping switch time field and a first field, the mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the traffic identifier-to-link mapping element is established, the time being determined based on a first target beacon time (TBTT) on the first link, the first field indicating a time difference between the first TBTT on the first link and a time point on the second link corresponding to the first TBTT, the time point being a time point on the second link that is not later than the first TBTT and closest to the first TBTT, and the value of 10 least significant bits of a time synchronization function TSF timer for the time point is 0, or the time point is a TBTT on the second link; and parsing the wireless frame.

[0036] In a possible implementation, the step of parsing the radio frame comprises: Determining a time at which a traffic identifier-to-link mapping relationship corresponding to the second link is established based on the first field and the time indicated by the mapping switch time field.

[0037] In a possible implementation, the traffic identifier-to-link mapping element further includes a second field, the second field indicating the presence of the first field.

[0038] In a possible implementation, the value carried in the first field is the value of bits 1 to 10 of the Time Synchronization Function TSF timer of the Basic Service Set BSS corresponding to the second link.

[0039] The beneficial effects of the seventh aspect may be understood with reference to the sixth aspect.

[0040] According to an eighth aspect, an embodiment of the present application provides a multi-link communication method, the method comprising: The method includes the steps of: generating a radio frame, the radio frame including a traffic identifier-to-link mapping element, the traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the traffic identifier-to-link mapping element is established, the time precision of which is microseconds; and transmitting the radio frame.

[0041] In this embodiment of the present application, when the time precision of the establishment time indicated by the mapping switching time field is changed to μs, even if the time when the mapping relationship is established is determined based on the TBTT on the first link, the receiving end on the second link can still accurately determine the time when the mapping relationship corresponding to the second link is established based on the radio frame.

[0042] In a possible implementation, the traffic identifier to link mapping element further includes a length field, which indicates the length of the mapping switch time field, and the time precision of the time is microseconds when the value carried in the length field is the first value.

[0043] According to a ninth aspect, an embodiment of the present application provides a multi-link communication method, the method comprising: The method includes receiving a radio frame, the radio frame including a traffic identifier-to-link mapping element, the traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the traffic identifier-to-link mapping element is established, the time precision of which is microseconds, and parsing the radio frame.

[0044] In a possible implementation, the step of parsing the radio frame comprises: Determining the time at which the traffic identifier-to-link mapping relationship is established based on the value conveyed in the mapping switch time field.

[0045] In a possible implementation, the traffic identifier to link mapping element further includes a length field, which indicates the length of the mapping switch time field, and the time precision of the time is microseconds when the value carried in the length field is the first value.

[0046] According to a tenth aspect, an embodiment of the present application provides a communication device configured to perform the method of the first aspect or any one of the possible implementations of the first aspect, wherein the communication device includes a unit for performing the method of the first aspect or any one of the possible implementations of the first aspect.

[0047] According to an eleventh aspect, an embodiment of the present application provides a communication device configured to perform the method of the second aspect or any one of the possible implementations of the second aspect, wherein the communication device includes a unit for performing the method of the second aspect or any one of the possible implementations of the second aspect.

[0048] According to a twelfth aspect, an embodiment of the present application provides a communication device configured to perform the method of the third aspect or any one of the possible implementations of the third aspect, wherein the communication device includes a unit for performing the method of the third aspect or any one of the possible implementations of the third aspect.

[0049] According to a thirteenth aspect, an embodiment of the present application provides a communication device configured to perform the method of the fourth aspect or any one of the possible implementations of the fourth aspect, wherein the communication device includes a unit for performing the method of the fourth aspect or any one of the possible implementations of the fourth aspect.

[0050] According to a fourteenth aspect, an embodiment of the present application provides a communication device configured to perform the method of the fifth aspect or any one of the possible implementations of the fifth aspect, wherein the communication device includes a unit for performing the method of the fifth aspect or any one of the possible implementations of the fifth aspect.

[0051] According to a fifteenth aspect, an embodiment of the present application provides a communication device configured to perform the method of the sixth aspect or any one of the possible implementations of the sixth aspect, wherein the communication device includes a unit for performing the method of the sixth aspect or any one of the possible implementations of the sixth aspect.

[0052] According to a sixteenth aspect, an embodiment of the present application provides a communication device configured to perform the method of the seventh aspect or any one of the possible implementations of the seventh aspect, wherein the communication device includes a unit for performing the method of the seventh aspect or any one of the possible implementations of the seventh aspect.

[0053] According to a seventeenth aspect, an embodiment of the present application provides a communication device configured to perform the method of the eighth aspect or any one of the possible implementations of the eighth aspect, wherein the communication device includes a unit for performing the method of the eighth aspect or any one of the possible implementations of the eighth aspect.

[0054] According to an eighteenth aspect, an embodiment of the present application provides a communication device configured to perform the method of the ninth aspect or any one of the possible implementations of the ninth aspect. The communication device includes a unit for performing the method of the ninth aspect or any one of the possible implementations of the ninth aspect.

[0055] In the tenth to eighteenth aspects, a communication device may include a transceiver unit and a processing unit. For a specific description of the transceiver unit and the processing unit, please refer to the device embodiments shown below.

[0056] According to a nineteenth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to perform the method of any one of the first to ninth aspects or possible implementations of the first to ninth aspects. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method of any one of the first to ninth aspects or possible implementations of the first to ninth aspects is performed.

[0057] In a possible implementation, the memory is located external to the communication device.

[0058] In a possible implementation, the memory is located within the communication device.

[0059] In this embodiment of the present application, the processor and the memory may alternatively be integrated into one device, in other words, the processor and the memory may alternatively be integrated together.

[0060] In a possible implementation, the communication device further includes a transceiver configured to receive or transmit signals.

[0061] According to a twentieth aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface. The logic circuit is coupled to the interface. The logic circuit is configured to generate a radio frame. The interface is configured to output the radio frame.

[0062] According to a twenty-first aspect, an embodiment of the present application provides a communication device. The communication device includes a logic circuit and an interface. The logic circuit is coupled to the interface. The interface is configured to input a radio frame. The logic circuit is configured to process the radio frame.

[0063] For specific descriptions of the twentieth and twenty-first aspects, see the method embodiments set forth below.

[0064] According to a twenty-second aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program that, when run on a computer, performs a method according to any one of the first to ninth aspects or possible implementations of the first to ninth aspects.

[0065] According to a twenty-third aspect, an embodiment of the present application provides a computer program product, the computer program product including a computer program that, when run on a computer, performs the method of any one of the first to ninth aspects or possible implementations of the first to ninth aspects.

[0066] According to a twenty-fourth aspect, an embodiment of the present application provides a computer program, which, when run on a computer, performs the method of any one of the first to ninth aspects or possible implementations of the first to ninth aspects.

[0067] According to a twenty-fifth aspect, an embodiment of the present application provides a wireless communication system, the wireless communication system including a transmitting end and a receiving end, wherein the transmitting end is configured to implement the method of the first aspect or any one of the possible implementations of the first aspect, and the receiving end is configured to implement the method of the second aspect or any one of the possible implementations of the second aspect, or the transmitting end is configured to implement the method of the third aspect or any one of the possible implementations of the third aspect, and the receiving end is configured to implement the method of the fourth aspect or any one of the possible implementations of the fourth aspect. or the receiving end is configured to implement the method of the fifth aspect or any one of the possible implementations of the fifth aspect, or the transmitting end is configured to implement the method of the sixth aspect or any one of the possible implementations of the sixth aspect and the receiving end is configured to implement the method of the seventh aspect or any one of the possible implementations of the seventh aspect, or the transmitting end is configured to implement the method of the eighth aspect or any one of the possible implementations of the eighth aspect and the receiving end is configured to implement the method of the ninth aspect or any one of the possible implementations of the ninth aspect. [Brief explanation of the drawings]

[0068] [Figure 1] 1 is a diagram of the architecture of a communication system according to an embodiment of the present application; [Figure 2a] 1 is a diagram of a connection scheme between a multi-link AP and a multi-link STA according to an embodiment of the present application; [Figure 2b] 1 is a diagram of a connection scheme between a multi-link AP and a multi-link STA according to an embodiment of the present application; [Figure 2c] FIG. 2 is a diagram of an antenna of a multi-link device according to an embodiment of the present application. [Figure 3a] FIG. 1 is a diagram of a communication scenario according to an embodiment of the present application. [Figure 3b] FIG. 1 is a diagram of a communication scenario according to an embodiment of the present application. [Figure 4a]FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 4b] FIG. 2 is a diagram of a timeline according to an embodiment of the present application. [Figure 5] 1 is a schematic flowchart of a multi-link communication method according to an embodiment of the present application; [Figure 6a] FIG. 2 is a diagram of a timeline according to an embodiment of the present application. [Figure 6b-1] FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 6b-2] FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 6c-1] FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 6c-2] FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 6d-1] FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 6d-2] FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 6e-1] FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 6e-2] FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 7] FIG. 2 is a diagram of a timeline according to an embodiment of the present application. [Figure 8a] FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 8b] FIG. 2 is a diagram of the structure of a traffic identifier to link mapping element according to an embodiment of the present application. [Figure 9] 1 is a diagram of the structure of a communication device according to an embodiment of the present application; [Figure 10]1 is a diagram of the structure of a communication device according to an embodiment of the present application; [Figure 11] 1 is a diagram of the structure of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0069] In order to facilitate understanding of the technical solutions of the present application, the present application will be further described with reference to the accompanying drawings as follows.

[0070] Terms such as "first," "second," and the like in the specification, claims, and accompanying drawings of this application are used merely to distinguish between different objects and are not used to describe a particular order. Furthermore, terms such as "comprise," "have," and any other variations thereof are intended to cover a non-exclusive inclusion. 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 instead optionally includes further steps or units that are not listed, or optionally includes further steps or units that are inherent to the process, method, product, or device.

[0071] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described with reference to the embodiment may be included in at least one embodiment of the present application. Phrases appearing in various locations in this specification do not necessarily refer to the same embodiment, nor are they an exclusive, independent, or alternative embodiment of another embodiment. It may be explicitly or implicitly understood by those skilled in the art that an embodiment described herein may be combined with another embodiment.

[0072] In this application, "at least one piece (item)" means one or more, "multiple" means two or more, "at least two pieces (items)" means two, three, or more, and "and / or" is used to describe an association relationship between associated objects and indicates that three relationships may exist. For example, "A and / or B" may indicate three cases: only A is present, only B is present, or both A and B are present, where A and B may be singular or plural. "Or" indicates that two relationships may exist: for example, only A is present, and only B is present. If A and B are not mutually exclusive, it indicates that three relationships exist: for example, only A is present, only B is present, and both A and B are present. The character " / " typically indicates an "or" relationship between associated objects. "At least one item (piece) of" or similar expressions means any combination of these items. For example, at least one item (piece) of a, b, or c may indicate a, b, c, "a and b," "a and c," "b and c," or "a, b, and c."

[0073] The technical solutions provided in the embodiments of the present application may be applied to WLAN systems, such as Wi-Fi. The methods provided in the embodiments of the present application may be applied to IEEE 802.11 series protocols, such as 802.11a / b / g protocol, 802.11n protocol, 802.11ac protocol, 802.11ax protocol, 802.11be protocol, or next-generation protocols. Examples are not listed herein. The technical solutions provided in the embodiments of the present application may also be applied to wireless personal area networks (WPANs) based on UWB technology. The methods provided in the embodiments of the present application may be applied to IEEE 802.15 series protocols, such as 802.15.4a protocol, 802.15.4z protocol, 802.15.4ab protocol, or next-generation UWB WPAN protocols. Examples are not listed herein. The technical solutions provided in the embodiments of the present application may further be applied to other communication systems, for example, internet of things (IoT) systems, vehicle-to-X (V2X) systems, and narrow band internet of things (NB-IoT) systems, and may be applied to devices in internet of vehicles, internet of things nodes, sensors, etc. in internet of things (IoT), smart cameras, smart remote controls, and smart water or electricity meters in smart homes, sensors in smart cities, etc., or may further be applied to long term evolution (LTE) systems, fifth generation (5G) communication systems, new communication systems emerging in future communication developments, etc.

[0074] WLAN systems can provide high-rate and low-latency transmission. With the continuous evolution of WLAN application scenarios, 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, stadium exhibition halls, concert halls, hotel rooms, dormitories, hospital wards, classrooms, supermarkets, squares, streets, production plants, and warehouses. Of course, devices (e.g., access points or stations) supporting WLAN communication or sensing may be sensor nodes (e.g., smart water meters, smart electricity meters, or smart air detection nodes) in a smart city, smart devices (e.g., smart cameras, projectors, displays, televisions, stereos, refrigerators, or washing machines) in a smart home, nodes in the Internet of Things, entertainment terminals (e.g., wearable devices such as augmented reality (AR) or virtual reality (VR) devices), smart devices (e.g., printers, projectors, loudspeakers, or stereos) in a smart office, Internet of Vehicle devices in the Internet of Vehicles, infrastructure in everyday life scenarios (e.g., vending machines, self-service navigation consoles in supermarkets, self-service cash register devices, or self-service ordering machines), devices in large sports and music venues, etc. For example, access points and stations may be devices used in the Internet of Vehicles, Internet of Things nodes, sensors, etc. in the Internet of Things, smart cameras, smart remote controls, and smart water or electricity meters in a smart home, sensors in a smart city, etc.

[0075] The embodiments of the present application are primarily described using WLANs as examples, particularly networks that comply with the IEEE 802.11 series of standards, such as systems that support Wi-Fi 7 and are sometimes referred to as extreme high throughput (EHT) systems, or systems that support Wi-Fi 8 and are sometimes referred to as ultra high reliability (UHR) systems or ultra high reliability and throughput (UHRT) systems. Those skilled in the art will readily understand that various aspects of the embodiments of the present application can be extended to other networks that use various standards or protocols, such as Bluetooth, high-performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, primarily used in Europe), and wide area networks (WANs), or other networks that are known or developed in the future. Therefore, the various aspects provided in the embodiments of the present application are applicable to any suitable wireless network, regardless of the coverage area and wireless access protocol used.

[0076] A multilink device includes one or more affiliated stations. An affiliated station is a logical station and may operate on one link, one frequency band, one channel, etc. An affiliated station may be an AP or a non-AP STA. For ease of explanation, in embodiments of the present application, a multilink device whose affiliated station is an AP may be referred to as a multilink AP, multilink AP device, or AP multilink device (AP MLD). A multilink device whose affiliated station is a non-AP STA may be referred to as a multilink STA, multilink STA device, or STA multilink device, or a multilink device whose affiliated station is a non-AP STA may be referred to as a multilink non-AP, multilink non-AP device, or non-AP multilink device (non-AP MLD). A multilink device (which may be a non-AP MLD or AP MLD in this specification) is a communication device with wireless communication capabilities. The communication device may be an entire device, or a chip, processing system, etc. located within the entire device. A device having a chip or processing system installed therein may implement the methods and functions in the embodiments of the present application under the control of the chip or processing system.

[0077] The multi-link device MLD may implement wireless communication according to an 802.11 series protocol, for example, according to an Extremely High Throughput (EHT) protocol, or according to an 802.11be-based protocol or an 802.11be-compatible protocol, thereby implementing communication with another device, which may or may not be a multi-link device, of course.

[0078] Each logical station may operate on one link, and multiple logical stations are allowed to operate on the same link. A link identifier may represent one station operating on a link. In other words, if there are two or more logical stations on a link, two or more link identifiers may represent those logical stations. A link identifier may also indicate a station operating on a link. When data transmission is performed between a multilink device and another multilink device, the multilink device and the other multilink device may first negotiate or communicate with each other regarding the correspondence between the link identifier and the link or the station on the link before communication, or the AP multilink device may indicate the correspondence between the link identifier and the link or the station on the link based on a broadcast management frame, for example, a beacon frame. Therefore, during data transmission, the link identifier can be conveyed without transmitting a large amount of signaling to indicate the link or the station on the link. This reduces signaling overhead and improves transmission efficiency.

[0079] For the purpose of explanation, the following uses an example in which one of the multilink devices is an AP multilink device and another of the multilink devices is an STA multilink device. In one example, a management frame, such as a multilink probe response frame, sent when the AP multilink device establishes a basic service set (BSS) carries one or more link elements, and the link information field included in the multilink element can be used to establish a correspondence between the link identifier and the station operating on the corresponding link.

[0080] FIG. 1 is a diagram of the architecture of a communication system according to one embodiment of the present application. As shown in FIG. 1, the AP MLD includes AP1, AP2, ..., and APn, and the non-AP MLD includes STA1, STA2, ..., and STAn, where n is a positive integer. The AP MLD and the non-AP MLD may perform parallel communication on Link 1, Link 2, ..., and Link n. STA1 in the non-AP MLD establishes an association relationship with AP1 in the AP MLD. STA2 in the non-AP MLD establishes an association relationship with AP2 in the AP MLD. STAn in the non-AP MLD establishes an association relationship with APn in the AP MLD. Thus, one or more STAs in the non-AP MLD and one or more APs in the AP MLD can communicate after establishing an association relationship. The frequency bands in which the multilink devices (including the AP MLD and the non-AP MLD) operate may include, but are not limited to, sub-1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and the high frequency 60 GHz. For example, the methods provided in the embodiments of the present application are applicable to, but not limited to, single-user uplink / downlink transmission, multi-user uplink / downlink transmission, vehicle-to-everything (V2X, where X may represent anything) communication, and device-to-device (D2D) communication. For example, V2X communication may include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, vehicle-to-network (V2N) communication, etc.

[0081] 2a and 2b are diagrams of a connection scheme between a multi-link AP and a multi-link STA according to 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 a multi-link device. Therefore, FIG. 2a and FIG. 2b show only the PHY and MAC layers as an example.

[0082] As shown in FIG. 2a and FIG. 2b, a multilink device (e.g., a multilink AP and a multilink STA) may include a physical layer (PHY) processing circuit (PHY#1, PHY#2, and PHY#n shown in FIG. 2a) and a medium access control (MAC) layer processing circuit. The physical layer processing circuit may be configured to process physical layer signals, and the MAC layer processing circuit may be configured to process MAC layer signals. Furthermore, the MAC layer may be further divided into a high-MAC layer (e.g., the high-MAC shown in FIG. 2a or the high-MAC#1 to high-MAC#n shown in FIG. 2b) and multiple low-MAC layers (e.g., the low-MAC#1 or low-MAC#2 to low-MAC#n shown in FIG. 2a and FIG. 2b, respectively). As shown in FIG. 2a, multiple APs included in a multilink AP are independent of each other in the lower MAC and PHY layers and share the high-MAC layer. Multiple STAs included in a multi-link STA are independent of each other in the lower MAC layer and PHY, but share an upper MAC layer. The upper MAC layer is separately connected to multiple lower MAC layers; in other words, the upper MAC layer is shared by multiple links. As shown in Figure 2b, multiple APs included in a multi-link AP are independent of each other in the lower MAC layer and PHY, and are also independent of each other in the upper MAC layer. Multiple STAs in a multi-link STA device are independent of each other in the lower MAC layer and PHY, and are also independent of each other in the upper MAC layer. For example, the upper MAC layer mainly completes operations such as allocating, encrypting, and decrypting sequence numbers (SN) and packet numbers (PN) of MAC service data units (MSDUs). For example, the lower MAC layer mainly completes operations such as assembling MAC protocol data units (MPDUs) on each link, channel access, packet transmission, and reception acknowledgment.

[0083] In FIG. 2a, the PHY#1 layer, lower MAC#1 layer, and upper MAC layer in the multi-link AP may be regarded as AP#1, the PHY#2 layer, lower MAC#2 layer, and upper MAC layer may be regarded as AP#2, ..., the PHY#n layer, lower MAC#n layer, and upper MAC layer may be regarded as AP#n. That is, it may be understood that the multi-link AP includes n AP entities. In the multi-link STA, the situation is similar. In particular, the upper MAC layer in the multi-link STA is also shared by multiple links, and the PHY#1 layer, lower MAC#1 layer, and upper MAC layer may be regarded as STA#1, the PHY#2 layer, lower MAC#2 layer, and upper MAC layer may be regarded as STA#2, ..., the PHY#n layer, lower MAC#n layer, and upper MAC layer may be regarded as STA#n. That is, it may be understood that the multi-link STA includes n STA entities. As shown in Figure 2a, PHY #1 of AP #1 in the multilink AP is connected to PHY #1 of STA #1 in the multilink STA, and therefore AP #1 in the multilink AP and STA #1 in the multilink STA communicate with each other over a link (e.g., link #1 shown in Figure 2a). PHY #2 of AP #2 in the multilink AP is connected to PHY #2 of STA #2 in the multilink STA, and therefore AP #2 in the multilink AP and STA #2 in the multilink STA communicate with each other over a link (e.g., link #2 shown in Figure 2a). PHY #n of AP #n in the multilink AP is connected to PHY #n of STA #n in the multilink STA, and therefore AP #n in the multilink AP and STA #n in the multilink STA communicate with each other over a link (e.g., link #n shown in Figure 2a). For an explanation of Figure 2b, please refer to Figure 2a. Details will not be described here.

[0084] For example, the upper MAC layer or the lower MAC layer may be implemented by one processor in the chip system of the multi-link device, or by different processing modules in the chip system. Examples are not listed in the embodiments of the present application. It can be understood that Figures 2a and 2b can be understood as functional module divisions implemented on the multi-link device. The modules shown in Figures 2a and 2b can be implemented in the form of hardware or software functional modules. The PHY layer and MAC layer shown in Figures 2a and 2b can be understood as logical function divisions, and other division schemes can be used in actual implementations. The n shown in Figures 2a and 2b can be equal to 0 or 1, or n can be an integer greater than 1, etc.

[0085] For example, the multilink device in the embodiment of the present application may be a single-antenna device or a multi-antenna device. For example, the multilink device may be a device with three or more antennas. The number of antennas included in the multilink device is not limited in the embodiment of the present application. Figure 2c is an antenna diagram of a multilink device according to this embodiment of the present application. In Figure 2c, an example is used in which the AP MLD is a multi-antenna device and the non-AP MLD is a single-antenna device. This should not be construed as a limitation on this embodiment of the present application.

[0086] The frequency bands in which a 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 3a and 3b are two diagrams of communication between a multi-link device and another device in a wireless local area network over multiple links.

[0087] 3a illustrates a scenario in which an AP MLD 101 communicates with a non-AP MLD 102. The AP MLD 101 includes an affiliated AP 101-1 and an affiliated AP 101-2, and the non-AP MLD 102 includes an affiliated STA 102-1 and an affiliated STA 102-2, and the AP MLD 101 and the non-AP MLD 102 communicate in parallel via link 1 and link 2.

[0088] 3b 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 affiliated AP 101-1 through affiliated AP 101-3, non-AP MLD 102 includes three affiliated stations, i.e., STA 102-1, STA 102-2, and STA 102-3, non-AP MLD 103 includes two affiliated stations, i.e., STA 103-1 and STA 103-2, and STA 104 is a single-link device and includes STA 104-1. AP MLD 101 may separately communicate with non-AP MLD 102 via Link 1, Link 2, and Link 3, with non-AP MLD 103 via Link 2 and Link 3, and with STA 104 via Link 1. In one example, STA 104 operates on the 2.4 GHz frequency band, STA 103-1 operates on the 5 GHz frequency band, and STA 103-2 operates on the 6 GHz frequency band in non-AP MLD 103, and STA 102-1 operates on the 2.4 GHz frequency band, STA 102-2 operates on the 5 GHz frequency band, and STA 102-3 operates on the 6 GHz frequency band in non-AP MLD 102. AP 101-1, operating on the 2.4 GHz frequency band in AP MLD 101, may conduct uplink or downlink data transmission with STA 104 and STA 102-1 in non-AP MLD 102 via link 1. The AP 101-2 operating on the 5 GHz frequency band in the AP MLD 101 may perform uplink or downlink data transmission with the STA 103-1 operating on the 5 GHz frequency band in the non-AP MLD 103 via link 2, and may also perform uplink or downlink data transmission with the STA 102-2 operating on the 5 GHz frequency band in the non-AP MLD 102 via link 2. The AP 101-3 operating on the 6 GHz frequency band in the AP MLD 101 may perform uplink or downlink data transmission with the STA 102-3 operating on the 6 GHz frequency band in the non-AP MLD 102 via link 3, and may also perform uplink or downlink data transmission with the STA 103-2 in the non-AP MLD 103 via link 3.

[0089] FIG. 3a only shows that the AP MLD supports two frequency bands, and FIG. 3b only shows an example in which the AP MLD 101 supports three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), each frequency band corresponding to one link, and the AP MLD 101 may operate on one or more of link 1, link 2, or link 3 for illustration purposes. On the AP side or STA side, a link in this specification may also be understood as a station operating on a link. In practical applications, the AP MLD and non-AP MLD may further support more or fewer frequency bands, that is, the AP MLD and non-AP MLD may operate on more or fewer links. This is not limited in the embodiments of the present application. FIG. 3a and FIG. 3b are merely simple diagrams and do not constitute any limitation on the scope of protection of the embodiments of the present application.

[0090] The following describes in detail the relevant terms in the embodiments of the present application.

[0091] 1. Traffic Identifier to Link Mapping Element

[0092] If no traffic identifier-to-link mapping operation is performed between multilink devices during the multilink setup process, all traffic identifiers are mapped to each established link by default, in other words, all types of traffic can be transmitted on each established link.

[0093] In the multi-link setup process, traffic identifier-to-link mapping can be implemented between multi-link devices. For example, an AP can carry traffic identifier-to-link mapping information in a beacon frame or a probe response frame, so that all stations use a corresponding mapping scheme after receiving the mapping information. The scheme of carrying mapping information in a beacon frame or a probe response frame is also called broadcast TID-to-link mapping. This scheme can effectively improve signaling transmission efficiency.

[0094] For example, the traffic identifier-to-link mapping information may be carried in a traffic identifier-to-link mapping element (TID-to-link mapping element). The traffic identifier-to-link mapping element may include at least one of the following fields: an element ID field, a length field, an element ID extension (or referred to as element ID extension) field, a traffic identifier-to-link mapping control field, a mapping switch time field, and an expected duration (or referred to as expected duration, desired duration, expected duration, required duration, etc.) field. Optionally, the traffic identifier-to-link mapping element may further include at least one of the following fields: a link mapping of TID 0 field, ..., and a link mapping of TID 7 field. For the structure of the traffic identifier-to-link mapping element, please refer to Figure 4a. For example, the mapping switch time field may indicate the effective start time (or effective time) of the traffic identifier-to-link mapping, indicate the effective start time (or effective time) of the traffic identifier-to-link mapping relationship, or indicate the time when the traffic identifier-to-link mapping relationship is established. The mapping switch time field is present when the traffic identifier-to-link mapping element is carried in a beacon frame or a probe response frame. When the mapping relationship takes effect, the beacon frame or probe response frame may not carry the mapping switch time field. The expected duration field may indicate the expected end time of the traffic identifier-to-link mapping relationship, or indicate the expected end time of the traffic identifier-to-link mapping.For example, the expected duration field indicates the effective duration of the traffic identifier-to-link mapping (corresponding to the case where the mapping switch time field is carried in the traffic identifier-to-link mapping element) or the remaining time (corresponding to the case where the mapping switch time field is not carried in the traffic identifier-to-link mapping element). The expected duration field is present when the traffic identifier-to-link mapping element is carried in a beacon frame or a probe response frame. The TID0 link mapping field may indicate the link to which TID0 is mapped. For example, the field may carry a bitmap, and each bit in the bitmap may correspond to a link. For example, if the value of a bit is 1, it indicates that TID0 is mapped to the link corresponding to that bit. In another example, if the value of a bit is 0, it indicates that TID0 is not mapped to the link corresponding to that bit. For example, the length of the bitmap may be equal to the maximum number of links that can be associated between multilink devices, the length of the bitmap may be a fixed value, for example, 16 bits, or the length of the bitmap may be equal to the number of associated links established between multilink devices. The manner of setting the length of the bitmap is not limited in the embodiments of the present application. For a description of other link mapping fields of the ITD, please refer to the link mapping field of TID0. Details will not be described here. TID0 to TID7 in this embodiment of the present application are just examples. With the evolution of the standard, there may be more traffic types in the future, for example, TID0 to TID15. Therefore, the number of link mapping fields of TIDs in the traffic identifier-to-link mapping element is not limited in the embodiment of the present application. For example, the number of link mapping fields of TIDs in the traffic identifier-to-link mapping element may be the same as the number of types of TIDs. For example, when the TID is extended from TID0 to TID7 to TID0 to TID15, the number of link mapping fields of TIDs may be equal to 16.

[0095] It can be understood that in a unicast scheme, when two communicating parties negotiate traffic identifier-to-link mapping information, the mapping information typically takes effect immediately. The mapping switch time field and expected duration field need to be sent multiple times in a beacon frame or probe response frame to ensure that one or more STAs can receive the traffic identifier-to-link mapping element. Therefore, the mapping switch time field and expected duration field are typically present when the traffic identifier-to-link mapping element is carried in a beacon frame or probe response frame.

[0096] For example, the traffic identifier-to-link mapping control field may include at least one of the following fields: a direction field, a default link mapping (or referred to as default link mapping) field, a mapping switch time present field, an expected duration present field, and a reserved (or referred to as reserved) field. Optionally, the traffic identifier-to-link mapping control field further includes a link mapping presence indicator field. For the structure of the traffic identifier-to-link mapping control field, see Figure 4a. The traffic identifier-to-link mapping control field may be used to carry control information related to traffic identifier-to-link mapping. For example, the traffic identifier-to-link mapping control field is described as follows: The direction field may indicate whether the traffic direction is uplink, downlink, or uplink / downlink, the default link mapping field may indicate whether a default mapping scheme is used, the mapping switch time present field may indicate whether a mapping switch time field is present, the expected duration present field indicates whether an expected duration field is present, and the link mapping present indicator field indicates which fields are present and which are not present in the link mapping fields of TID0 to TID7.

[0097] It can be understood that when the default link mapping field indicates that a default mapping scheme is used, it indicates that all traffic identifiers may be mapped to each established link by default, the traffic identifier to link mapping control field may not include the link mapping presence indicator field, and the traffic identifier to link mapping elements may not include the link mapping fields for TID0 to TID7.

[0098] It may be understood that in the embodiments of the present application, traffic identifier-to-link mapping information, traffic identifier-to-link mapping relationship (or mapping relationship for short), traffic identifier-to-link mapping, etc. may be interchangeable. The traffic identifier-to-link mapping relationship indicated by the traffic identifier-to-link mapping element in the embodiments of the present application may be simply referred to as the mapping relationship (or mapping information) indicated by the traffic identifier-to-link mapping element, or the mapping relationship indicated by the element (shown in the description of the mapping relationship indicated by the first element shown below, or the description of the mapping relationship indicated by the second element shown below).

[0099] 2. Mapping Switch Time Field

[0100] For example, the value carried in the mapping switch time field may be determined based on the target beacon transmission time (TBTT) of a future delivery traffic indication bitmap (DTIM) beacon frame. The time precision of the TBTT is in time units (TU), where 1 TU = 1024 μs. For example, the difference between the TBTT of two beacon frames may be 100 TU (by way of example only).

[0101] Typically, an AP broadcasts the value of a time synchronization function (TSF) timer in a beacon frame. After receiving the TSF timer value, a STA may update the system time maintained locally by the STA to the TSF timer value, so that the time of all STAs in the BSS is the same as that of the AP (i.e., time synchronization is implemented). For example, the value carried in the mapping switch time field may be set to the value of the 11th to 26th bits of the TSF timer, i.e., TSF[10:25] (bits 10 to 25 of TSF). The TSF timer may be understood as a time value, 64 bits in length, in microseconds (μs). For example, the TSF timers corresponding to all STAs on one link may be the same, and the TSF timers corresponding to STAs on different links may be different. As shown in Figure 3b, the TSF timers of STA 104 and STA 102-1 corresponding to link 1 are the same. In other words, the TSF timer may allow all STAs in a BSS to be time-synchronized, with all STAs maintaining a local TSF timer. For example, the value of the TSF timer may be carried in a timestamp field in a beacon frame.

[0102] It may be understood that the manner of setting the value conveyed in the mapping switch time field shown herein is only an example. See the description below for a description of the value conveyed in the mapping switch time field. The length of the mapping switch time field and the length of the TSF timer described above are only examples and should not be construed as a limitation on the embodiments of the present application. See the description below for a description of the length of the mapping switch time field.

[0103] 3. Expected duration field

[0104] The expected duration field indicates how long the traffic identifier-to-link mapping scheme will continue, and the unit of the expected duration field is TU. For example, the duration indicated by the expected duration field is calculated from the end of the beacon frame. That is, the duration indicated by the expected duration field can be understood as a relative time calculated from the end of the beacon frame.

[0105] It may be appreciated that the manner in which the expected end time indicated by the expected duration field is set forth herein is merely an example, see the description below for a description of another manner in which the expected duration field is set.

[0106] When the mapping scheme needs to be switched, the AP may carry two traffic identifier-to-link mapping elements in a beacon frame, for example, a first traffic identifier-to-link mapping element (hereinafter simply referred to as the first element) and a second traffic identifier-to-link mapping element (hereinafter simply referred to as the second element). The expected duration field in the first element may indicate how long the old mapping relationship (old mapping scheme or old mapping information) will continue, and the mapping switch time field in the second element may indicate the time when a new mapping relationship will be established. Generally, the expected end time of the old mapping relationship needs to be the same as the time when the new mapping relationship is established.

[0107] For example, the value carried in the mapping switch time field may be set to the value of bits 11 to 26 of the TSF timer. Therefore, the value carried in the mapping switch time field may be understood as an integer multiple of TU, ​​or as an integral TU on the timeline shown in FIG. 4b. As shown in FIG. 4b, the black dots shown in FIG. 4b may represent the TBTT of a beacon frame, and the value of the 10 least significant bits of the TSF timer corresponding to the TBTT of a beacon frame may be 0, i.e., TSF[0:9]=0. Generally, the actual transmission time of a beacon frame may be equal to or later than the TBTT of the beacon frame. Therefore, the actual end time of a beacon frame may be later than the TBTT. When the end time of a beacon frame is between two TUs, the expected end time indicated by the expected duration field cannot be calculated from an integer multiple of TU. However, the time accuracy of the time indicated by the expected duration field is TU. Therefore, the duration between the end time of the beacon frame and the effective time of the new mapping relationship may not be an integer multiple of TU. Therefore, the end time indicated by the expected duration field may not be exactly equal to the effective start time indicated by the mapping switch time field. This results in the following problems:

[0108] For example, if the expected end time indicated by the expected duration field is earlier than the establishment time indicated by the mapping switch time field, the old mapping may have ended but the new mapping may not have started. In this case, non-AP MLD may temporarily switch to a third mapping, which results in unnecessary switching overhead. In particular, AP MLD may think that non-AP MLD has switched to the new mapping, but non-AP MLD uses the third mapping, which results in an asymmetric mapping scheme on both sides. For example, if the expected end time indicated by the expected duration field is later than the establishment time indicated by the mapping switch time field, the old mapping may not have ended but the new mapping may have started. In this case, AP MLD and non-AP MLD may use different mapping schemes, which results in an asymmetric mapping scheme on both sides. When the mapping schemes on both sides are asymmetric, station performance may be seriously affected. For example, if the non-AP MLD determines that the link is disabled (also called deactivated) in the mapping scheme considered by the non-AP MLD, the AP MLD may determine that the link is enabled in the mapping scheme considered by the AP MLD and repeatedly attempt to begin transmitting on the link, but may not get a response from the non-AP MLD, causing the AP MLD to believe that the channel is busy and increase the AP MLD's contention window, resulting in a significant increase in channel access delay.

[0109] In this regard, the embodiments of the present application provide a multi-link communication method and apparatus to effectively improve the asymmetric mapping scheme of two communication parties and ensure that the expected termination time of the old mapping relationship is the same as the time when the new mapping relationship is established.

[0110] FIG. 5 is a schematic flowchart of a multilink communication method according to an embodiment of the present application. This method may be applied to the systems shown in FIGS. 1, 2A, and 2B, or to the multilink devices shown in FIGS. 3A and 3B. For ease of explanation, the following describes the method provided in the embodiment of the present application by using a transmitting end and a receiving end as examples. The transmitting end may be understood as a communication device for sending wireless frames, such as an AP MLD, an AP in a multilink device, or an AP associated with an AP MLD. The receiving end may be understood as a communication device for receiving wireless frames, such as a non-AP MLD, an STA in a multilink device, or an STA associated with a non-AP MLD. In the embodiment of the present application, the multilink devices for two communication parties may both be AP MLDs or both STA MLDs, or one multilink device may be an AP MLD and the other multilink device may be an STA MLD. Examples are not listed here. It can be understood that in the embodiments of the present application, the method provided in the embodiments of the present application is described by using two sides, a transmitting end and a receiving end. However, there may be other devices in the process of information transmission between the transmitting end and the receiving end. For example, information between the transmitting end and the receiving end is forwarded by using a forwarding device. Therefore, in the embodiments of the present application, mutual information transfer can be implemented by technical means that can be completed by those skilled in the art, and devices other than the transmitting end and the receiving end are not limited in the embodiments of the present application.

[0111] As shown in FIG. 5, the multi-link communication method includes the following steps:

[0112] 501: A transmitting end sends a radio frame, and a receiving end receives the radio frame correspondingly.

[0113] For example, before sending out a radio frame, the transmitting end may generate the radio frame.

[0114] 502: The receiving end parses the radio frame.

[0115] The following describes in detail the radio frame in the embodiment of the present application and the manner in which the receiving end parses the radio frame.

[0116] In this embodiment of the present application, a radio frame may include at least two traffic identifier-to-link mapping elements. For example, the radio frame may include four elements, where the first two elements may indicate a mapping switch of a BSS corresponding to a transmitted BSSID (the two elements are carried outside the multiple BSSID elements), and the last two elements may indicate a mapping switch of a BSS corresponding to a non-transmitted BSSID (the two elements are carried in the multiple BSSID elements). In another example, the radio frame includes two traffic identifier-to-link mapping elements, for example, a first traffic identifier-to-link mapping element (old mapping relationship) and a second traffic identifier-to-link mapping element (new mapping relationship). For example, when the first element and the second element in the radio frame are located outside the multiple BSSID elements, the switch between the mapping relationship indicated by the first element and the mapping relationship indicated by the second element may be used in the MLD where the transmitted BSSID is located. When the first element and the second element in the radio frame are located in a non-transmitted BSSID profile among the multiple BSSID elements, switching between the mapping relationship indicated by the first element and the mapping relationship indicated by the second element is used in the MLD in which the non-transmitted BSSID corresponding to the non-transmitted BSSID profile is located.

[0117] The following describes in detail a method for ensuring that the end time of the old mapping relationship is the same as the effective time of the new mapping relationship when a radio frame includes two traffic identifier-to-link mapping elements.

[0118] Method 1

[0119] The first element includes an expected duration field, which indicates an expected end time of the mapping relationship indicated by the first element, and may be determined based on a most recent TBTT prior to the transmission time of the radio frame. The second element includes a mapping switch time field, which indicates a time when the mapping relationship indicated by the second element will be established.

[0120] In this embodiment of the present application, the nearest TBTT before the transmission time of the radio frame may be understood as a TBTT earlier than the transmission time of the radio frame, and the TBTT may be understood as being closest to the transmission time of the radio frame with respect to another TBTT (a TBTT other than the above nearest TBTT). As shown in Figure 6a, the black dot in Figure 6a may represent the TBTT, and the dashed line portion may represent the transmission time of the radio frame. In this case, the TBTT (or TU boundary) that is before the transmission time of the radio frame and closest to the transmission time of the radio frame is the second black dot in Figure 6a.

[0121] In this embodiment of the present application, it can be understood that if the transmission time of the radio frame is exactly at the TBTT (or TU boundary), this may be a special case of the nearest TBTT (or TU boundary) before the transmission time of the radio frame. If the transmission time of the radio frame is exactly at the TBTT (or TU boundary), the expected duration field can be determined based on the transmission time of the radio frame. For example, the duration (or remaining duration) of the mapping relationship indicated by the first element is determined by using the transmission time of the radio frame as a starting point.

[0122] For example, the expected duration field may be determined based on the nearest TU boundary prior to the transmission time of the radio frame, which may be understood as the time corresponding to when the values ​​of the 10 least significant bits of the TSF timer are 0, or the TU boundary may be understood as TSF[0:9]=0.

[0123] For example, the time accuracy of the expected end time indicated by the expected duration field may be TU. The expected end time indicated by the expected duration field is calculated from the nearest TBTT (or the nearest TU boundary) before the transmission time of the radio frame, and the time indicated by the expected duration field is in units of TU. Therefore, compared with the scheme in which the time indicated by the expected duration field is determined based on the end time of the beacon frame, this scheme is a mapping relationship, and can effectively ensure that the expected end time determined based on the expected duration field is an integer multiple of TU, ​​and can ensure that the expected end time indicated by the expected duration field is the same as the establishment time indicated by the mapping switch time field.

[0124] For example, the structure of a traffic identifier-to-link mapping element may be shown in Figures 6b-1 and 6b-2. The expected duration field in the first element may be determined based on a TBTT or TU boundary prior to the transmission time of the radio frame, and the mapping switch time field in the second element may be determined based on a TBTT of a future beacon frame. Optionally, the expected duration field in the second element shown in Figures 6b-1 and 6b-2 may also be determined based on the nearest TBTT or TU boundary prior to the transmission time of the radio frame. For a description of other fields in the elements shown in Figures 6b-1 and 6b-2, see Figure 4a, etc. The mapping switch time field in the second element shown in Figures 6b-1 and 6b-2 may be determined based on a TBTT of a future beacon frame and may be set to TSF[10:25], for example.

[0125] In Scheme 1, after receiving a radio frame, the receiving end determines the first element and the second element based on the positions of the first element and the second element in the radio frame. For example, the first element may be located before the second element in the radio frame. Of course, the positional relationship between the first element and the second element described in this specification is only an example. For ease of explanation, the following describes the radio frame in this embodiment of the present application by using an example in which the first element is located before the second element.

[0126] In Manner 1, after receiving a radio frame, the receiving end may determine the expected end time of the mapping relationship indicated by the first element based on the expected duration field in the first element, and may determine the time when the mapping relationship indicated by the second element is established based on the mapping switch time field in the second element. For example, the receiving end may determine the expected end time of the traffic identifier-to-link mapping relationship indicated by the first element by using the nearest TBTT or TU boundary before the transmission time of the radio frame as the starting point and using the value carried in the expected duration field in the first element as the duration (duration, remaining duration, etc.). The manner in which the receiving end parses another field in the radio frame is not limited in the embodiments of the present application.

[0127] In this embodiment of the present application, since the difference between any two TBTTs on a link is in units of TUs, when the time indicated by the expected duration field is calculated by using the most recent TBTT point before the transmission time of the radio frame as the starting point, the effective time indicated by the mapping switch time field in the second element can be accurately indicated.

[0128] Method 2

[0129] The first element includes an expected duration field, the expected duration field indicating an expected end time of the mapping relationship indicated by the first element, the time indicated by the expected duration field being determined based on a TSF timer, and the second element includes a mapping switch time field, the mapping switch time field indicating a time when the mapping relationship indicated by the second element will be established.

[0130] The fact that the time indicated by the Expected Duration field is determined based on a TSF timer can also be understood as follows: The expected end time indicated by the Expected Duration field is determined based on the value of a TSF timer of the BSS corresponding to the outgoing link, and the outgoing link is used to send the radio frame. When the time indicated by the Expected Duration field is determined based on the end time of the beacon frame, the time indicated by the Expected Duration field is a relative time. When the Expected Duration field is determined based on a TSF timer, the time indicated by the Expected Duration field can be understood as an absolute time.

[0131] For example, the value conveyed in the expected duration field may be any one of the following:

[0132] The value carried in the Expected Duration field may be the same as the value of bits 11 through 26 of the TSF timer, e.g., TSF[10:25]. Thus, the time indicated by the Expected Duration field is set in the same manner as the time indicated by the Mapping Switch Time field. In this case, the length of the Expected Duration field may be two octets.

[0133] The value carried in the Expected Duration field may be the same as the value of bits 11 through 34 of the TSF timer, e.g., TSF[10:33]. Therefore, the time indicated by the Expected Duration field may be greater than the time indicated by the Mapping Switch Time field. This effectively ensures that the end time of the traffic identifier-to-link mapping relationship may be greater than the effective time. In this case, the length of the Expected Duration field may be 3 octets.

[0134] The value carried in the Expected Duration field may be the same as the value of bits 11 through 50 of the TSF timer, e.g., TSF[10:49]. Therefore, the time indicated by the Expected Duration field may be greater than the time indicated by the Mapping Switch Time field. This effectively ensures that the end time of the traffic identifier-to-link mapping relationship may be greater than the effective time. In this case, the length of the Expected Duration field may be 4 octets.

[0135] It can be understood that the value carried in the expected duration field starts from the 11th bit of the TSF timer because the time indicated by the 1st to 10th bits of the TSF timer is smaller than 1 TU. Therefore, starting from the 11th bit of the TSF timer can effectively ensure that the time indicated by the expected duration field is greater than 1 TU. The above relationship between the value carried in the expected duration field and the TSF timer is only an example. For example, the value carried in the expected duration field can alternatively be the value of the 11th to 40th bits of the TSF timer. Examples are not listed in the embodiments of this application.

[0136] For example, the structure of a traffic identifier-to-link mapping element may be shown in Figures 6c-1 and 6c-2. The time indicated by the expected duration field is changed to absolute time, e.g., set to the system time at the end of the mapping relationship indicated by the first element. This can effectively ensure that the time indicated by the expected duration field in the first element can indicate the effective time indicated by the mapping switch time field in the second element. Optionally, the expected duration field in the second element shown in Figures 6c-1 and 6c-2 may also be determined based on a TSF timer. For example, the value carried in the mapping switch time field in the second element may be determined based on the TBTT of a future DTIM beacon frame (e.g., at a time later than the radio frame). For example, the time precision of the effective time indicated by the mapping switch time field in the second element may be TU or μs. For descriptions of other fields in the elements shown in Figures 6c-1 and 6c-2, please refer to Figure 4a, etc.

[0137] In Scheme 2, after receiving a radio frame, the receiving end determines the first element and the second element based on the positions of the first element and the second element in the radio frame.

[0138] In Scheme 2, after receiving a radio frame, the receiving end may determine an expected end time of the mapping relationship indicated by the first element based on the expected duration field in the first element, and may determine a time when the mapping relationship indicated by the second element is established based on the mapping switch time field in the second element. For example, the receiving end may use the value carried in the expected duration field in the first element as the expected end time of the traffic identifier-to-link mapping relationship indicated by the first element. The manner in which the receiving end parses other fields in the radio frame is not limited in the embodiments of the present application.

[0139] In this embodiment of the present application, the time indicated by the expected duration field is changed to an absolute time, for example, set to the system time at the end of the mapping relationship indicated by the first traffic identifier-to-link mapping element, which can effectively ensure that the expected end time indicated by the expected duration field in the first traffic identifier-to-link mapping element can indicate the establishment time indicated by the mapping switch time field in the second traffic identifier-to-link mapping element.

[0140] Method 3

[0141] For example, as shown in Figures 6d-1 and 6d-2, the first element does not include an expected duration field, and the second element includes a mapping switch time field, where the mapping switch time field in the second element indicates the time when the mapping relationship indicated by the second element is established and the expected end time of the mapping relationship indicated by the first element. For example, the expected end time of the mapping relationship indicated by the first element may be equal to the establishment time indicated by the mapping switch time field in the second element by default. For a description of the other fields in the elements shown in Figures 6d-1 and 6d-2, see Figure 4a.

[0142] Optionally, the expected duration field in the second element may be determined based on the nearest TBTT or TU boundary before the transmission time of the radio frame. For example, the expected end time of the mapping relationship indicated by the second element is calculated by using the nearest TBTT or TU boundary before the transmission time of the radio frame as a starting point. Optionally, the expected duration field in the second element may be determined based on a TSF timer. Optionally, the expected duration field in the second element may be determined based on the end time of a beacon frame. For example, the expected end time of the mapping relationship indicated by the second element is calculated by using the end time of a beacon frame as a starting point. Optionally, the mapping switch time field in the second element and / or the first element may be determined based on the TBTT of a future beacon frame. For example, the time precision of the effective time indicated by the mapping switch time field is TU. Optionally, the time precision of the effective time indicated by the mapping switch time field in the second element and / or the first element may be μs. Optionally, the length of the mapping switch time field is 2 octets, 4 octets, etc. For a description of the mapping switch time field, see the terminology above or see the description of the mapping switch time field below.

[0143] In Scheme 3, after receiving a radio frame, the receiving end may determine the first element and the second element based on the positions of the first element and the second element in the radio frame. For example, after receiving a radio frame, if the receiving end finds that the first element does not include an expected duration field and the second element includes a mapping switch time field, the receiving end may use the establishment time indicated by the mapping switch time field in the second element as the expected end time of the mapping relationship indicated by the first element.

[0144] In this embodiment of the present application, the first traffic identifier-to-link mapping element does not include an expected duration field, and the second traffic identifier-to-link mapping element includes a mapping switch time field. Thus, the mapping switch time field may indicate the time when the mapping relationship indicated by the second traffic identifier-to-link mapping element is established and may indicate the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element. For example, the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element may be equal to the time when the mapping relationship indicated by the second traffic identifier-to-link mapping element is established by default. This effectively ensures that the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time when the mapping relationship indicated by the second traffic identifier-to-link mapping element is established.

[0145] Method 4

[0146] For example, as shown in Figures 6e-1 and 6e-2, the first element includes an expected duration field, the second element does not include a mapping switch time field, and the expected duration field in the first element indicates the time when the mapping relationship indicated by the second element is established and the expected end time of the mapping relationship indicated by the first element. For example, the time when the mapping relationship indicated by the second element is established may be equal to the expected end time indicated by the expected duration field in the first element by default. For a description of the other fields in the elements shown in Figures 6e-1 and 6e-2, see Figure 4a.

[0147] Optionally, the expected duration field in the first element and / or the expected duration field in the second element may be determined based on the nearest TBTT or TU boundary before the transmission time of the radio frame. For example, the expected end time of the mapping relationship indicated by the first element and / or the expected end of the mapping relationship indicated by the second element is calculated by using the nearest TBTT or TU boundary before the transmission time of the radio frame as a starting point. Optionally, the expected duration field in the first element and / or the expected duration field in the second element may be determined based on a TSF timer. Optionally, the expected duration field in the first element and / or the expected duration field in the second element may be determined based on the end time of the beacon frame. For example, the expected end time of the mapping relationship indicated by the first element and / or the expected end time of the mapping relationship indicated by the second element is calculated by using the end time of the beacon frame as a starting point. Optionally, the time precision of the effective time indicated by the mapping switch time field in the first element is TU or μs. Optionally, the length of the mapping switch time field in the first element is 2 octets, 4 octets, etc. For a description of the mapping switch time field, see the terminology above or see the description of the mapping switch time field below.

[0148] In Scheme 4, after receiving a radio frame, the receiving end may determine the first element and the second element based on the positions of the first element and the second element in the radio frame. For example, after receiving a radio frame, if the receiving end finds that the first element includes an expected duration field and the second element does not include a mapping switch time field, the receiving end may use the expected end time indicated by the expected duration field in the first element as the time when the mapping relationship indicated by the second element is established.

[0149] In this embodiment of the present application, the first traffic identifier-to-link mapping element includes an expected duration field, and the second traffic identifier-to-link mapping element does not include a mapping switch time field. Therefore, the expected duration field may indicate the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element and the time at which the mapping relationship indicated by the second traffic identifier-to-link mapping element is established. For example, the time at which the mapping relationship indicated by the second traffic identifier-to-link mapping element is established may be equal to the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element by default. This effectively ensures that the expected end time of the mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the mapping relationship indicated by the second traffic identifier-to-link mapping element is established.

[0150] Method 5

[0151] The first element includes an expected duration field that indicates an expected end time of the mapping relationship indicated by the first element, and the second element includes a mapping switch time field that indicates a time when the mapping relationship indicated by the second element will be established.

[0152] In one example, the expected duration field in the first element may further indicate a time when the mapping relationship indicated by the second element will be established. In other words, the time when the mapping relationship indicated by the second element will be established may be determined based on the expected duration field in the first element. If the expected end time of the mapping relationship indicated by the first element overlaps with the time when the mapping relationship indicated by the second element will be established, the receiving end may determine the time when the mapping relationship indicated by the second element will be established and the expected end time of the mapping relationship indicated by the first element based on the expected duration field in the first element. That is, the receiving end may ignore the mapping switch time field in the second element.

[0153] In another example, the mapping switch time field in the second element may further indicate an expected end time of the mapping relationship indicated by the first element. In other words, the expected end time of the mapping relationship indicated by the first element may be determined based on the mapping switch time field in the second element. If the expected end time of the mapping relationship indicated by the first element overlaps with the time when the mapping relationship indicated by the second element is established, the receiving end may determine the time when the mapping relationship indicated by the second element is established and the expected end time of the mapping relationship indicated by the first element based on the mapping switch time field in the second element. That is, the receiving end may ignore the expected duration field in the first element.

[0154] In yet another example, when the end time of a traffic identifier-to-link mapping relationship indicated by a first traffic identifier-to-link mapping element is later than the effective time of a traffic identifier-to-link mapping relationship indicated by a second traffic identifier-to-link mapping element, the end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element may be equal to the effective time of the traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element. In other words, when the end time of a mapping relationship indicated by a first element is later than the start time of a mapping relationship indicated by a second element, the effective time of the mapping relationship indicated by the first element overlaps with the effective time of the mapping relationship indicated by the second element. Therefore, when the effective times of two mapping information overlap in time, the mapping relationship corresponding to the later start time (e.g., the time when a new mapping relationship is established) and end time (e.g., the expected end time of the old mapping relationship) may be used as the new traffic identifier-to-link mapping relationship. After receiving the radio frame, the receiving end may determine the first element and the second element based on the positions of the first element and the second element in the radio frame. For example, after receiving the radio frame, if the receiving end finds that the end time of the mapping relationship indicated by the first element is later than the effective time of the mapping relationship indicated by the second element, the receiving end may use the effective time of the mapping information of the second element as the end time of the mapping relationship indicated by the first element.

[0155] In yet another example, when the effective time of the mapping relationship indicated by a first element overlaps with the effective time of the mapping relationship indicated by a second element, the time at which the mapping relationship indicated by the second element is established may be fixedly used as the expected end time of the mapping relationship indicated by the first element, or the expected end time of the mapping relationship indicated by the first element may be fixedly used as the time at which the mapping relationship indicated by the second element is established.

[0156] Optionally, in Method 5, the second element may further include an expected duration field, which indicates an expected end time of the mapping relationship indicated by the second element.

[0157] The radio frame in this embodiment of the present application may include a beacon frame, a probe response frame, etc. For example, the radio frame may include a capability information element and a timestamp field in addition to a traffic identifier-to-link mapping element. The timestamp field may be used to carry the value of a TSF timer (also called a TSF timer).

[0158] In this embodiment of the present application, Schemes 1 to 5 can effectively ensure that the expected end time of the mapping relationship indicated by the first element is the same as the time when the mapping relationship indicated by the second element is established, which effectively improves the asymmetric mapping scheme of two communicating parties.

[0159] Generally, different links between multilink devices may correspond to different mapping relationships. For example, in a multilink device, a traffic identifier on a first link may be different from a traffic identifier on a second link. Although different links between multilink devices may correspond to different traffic identifiers, the effective time of the mapping relationship indicated by the traffic identifier-to-link mapping element is the same. In this case, if the mapping relationship can be determined based on the TBTT on another link, the time indicated by the mapping switch time field in the traffic identifier-to-link mapping element sent on the current link may not be accurately synchronized with the TBTT on the other link. In other words, the mapping relationship is determined based on the TBTT on the other link. However, when the traffic identifier-to-link mapping element is received on the current link, the receiving end still uses the TBTT on the current link as a reference, and therefore the time at which the mapping relationship on the current link is established does not match the time at which the mapping relationship on the other link is established. As shown in FIG. 7, the time indicated by the mapping switch time field in the traffic identifier-to-link mapping element is determined based on the first TBTT on the first link. However, when the receiving end corresponding to the second link receives the traffic identifier-to-link mapping element, the obtained time indicated by the mapping switch time field is different from the first TBTT on the first link, so the receiving end corresponding to the second link cannot accurately know the time when the mapping relationship is established based on the mapping switch time field.

[0160] In this regard, the embodiments of the present application further provide a multi-link communication method and apparatus: When the effective time of the mapping relationship is determined based on the TBTT on another link, the time when the mapping relationship on the current link is established can be accurately indicated.

[0161] For the procedure of the multi-link communication method in this embodiment of the present application, please refer to Figure 5. Details will not be described here. The difference between the method provided in this embodiment of the present application and the method shown in Figure 5 lies in that in this embodiment of the present application, the transmitting end can send a radio frame based on the second link, and correspondingly, the receiving end can receive a radio frame based on the second link.

[0162] The following describes in detail the radio frame and the mapping switch time field in this embodiment of the present application. For example, the radio frame in this embodiment of the present application includes a traffic identifier-to-link mapping element, and the traffic identifier-to-link mapping element includes a mapping switch time field, and the mapping switch time field indicates the time when the traffic identifier-to-link mapping relationship is established, and the establishment time is determined based on the TBTT on the first link. For descriptions of other elements in the radio frame, beacon frame, and probe response frame, please refer to the above descriptions.

[0163] Method 6

[0164] The traffic identifier-to-link mapping element further includes a first field, which indicates a time difference (also referred to as a time difference, offset difference, offset, etc.) between a first TBTT on a first link and a time point on a second link corresponding to the first TBTT. The time point may be no later than the first TBTT and is a time point on the second link closest to the first TBTT. Figure 7 is used as an example. The time point on the second link, no later than the first TBTT, and closest to the first TBTT, for which the values ​​of the 10 least significant bits of the TSF timer (e.g., the first bit to the tenth bit, or TSF[0:9]) are equal to 0, can be understood as the position of the second black dot (i.e., the TU boundary) on the second link shown in Figure 7. For example, the time precision of the time difference indicated by the first field is μs. For example, when the time point is the time point where the value of the 10 least significant bits of the TSF timer is equal to 0 and is closest to the first TBTT, the value carried in the first field may be the value of the 10 least significant bits of the value of the TSF timer of the BSS corresponding to the second link, for example, TSF[0:9]. When the time point is the TBTT on the second link, the time difference between the TBTT on the first link and the TBTT on the second link may be long, so the specific length of the first field is not limited in the embodiments of the present application.

[0165] Based on the first field and the time indicated by the mapping switch time field, the receiving end on the second link may know the number of microseconds before the time indicated by the mapping switch time field (the time point on the second link corresponding to the first TBTT) that the mapping relationship will be established. For example, after receiving a radio frame, the receiving end may determine the time that the mapping relationship will be established based on the time indicated by the mapping switch time field and the time difference indicated by the first field, such that the time that the mapping relationship on the second link is established may match the time that the mapping relationship on the first link is established. For example, when the mapping switch time field is determined based on the first TBTT, the value carried in the mapping switch time field may be the value of bits 11 to 26 (by way of example only) of the TSF timer corresponding to the first TBTT on the first link. Upon receiving the mapping switch time field, the receiving end may determine the first TBTT on the first link instead of the TBTT on the second link based on the TSF timer indicated by the mapping switch time field. Therefore, the receiving end may determine the time at which the mapping relationship is established based on the first field and the time indicated by the mapping switch time field.

[0166] For example, the structure of a traffic identifier-to-link mapping element may be shown in FIG. 8a. For example, the first field may be referred to as a mapping switch time extension field, an offset field, etc. The specific name of the first field is not limited in the embodiments of the present application. Optionally, the traffic identifier-to-link mapping element may further include a second field, and the second field may indicate whether the first field is present in the traffic identifier-to-link mapping element. For example, the second field may be referred to as a mapping switch time extension present field, an offset present field, etc. The specific name of the second field is not limited in the embodiments of the present application. For example, the length of the second field may be 1 bit. For example, if the value of the second field is 1, it may indicate that the first field is present in the traffic identifier-to-link mapping element, or if the value of the second field is 0, it may indicate that the first field is not present in the traffic identifier-to-link mapping element. Of course, the values ​​and meanings of the fields described herein are merely examples and should not be construed as limitations on the embodiments of the present application. Please refer to FIG. 4a for a description of the traffic identifier to link mapping elements shown in FIG. 8a.

[0167] It may be understood that the method illustrated in Scheme 6 may be applied when a radio frame includes one traffic identifier-to-link mapping element, or when a radio frame includes at least two traffic identifier-to-link mapping elements, for example, a first element and a second element. When two elements are included, referring to Scheme 1 described above, if the first element includes an expected duration field and a first field, the expected duration field is determined based on the nearest TBTT or TU boundary before the transmission time of the radio frame, and the TBTT or TU boundary is determined based on the first link. The first field indicates a time difference between a time point corresponding to the second link and the TBTT or TU boundary. For example, after receiving a radio frame, the receiving end may determine the expected end time of the mapping relationship indicated by the first element by using the nearest TBTT or TU boundary before the transmission time of the radio frame as the starting point and the value carried in the expected duration field and the time difference indicated by the first element as the duration. As shown in FIG. 7, the expected end time determined based on the nearest TBTT or TU boundary before the transmission time of the radio frame and the expected duration field in the first element is the time point corresponding to the first TBT shown in FIG. 7. However, to stay consistent with the expected end time of the mapping relationship on the first link, the receiving end must further determine the expected end time of the mapping relationship indicated by the first element, i.e., the time corresponding to the first TBTT shown in FIG. 7, based on the first field. For example, the second element may include a mapping switch time field and a first field. See Scheme 6 for a description of the mapping switch time field and the first field.

[0168] In this embodiment of the present application, the radio frame includes a time difference between a first TBTT on the first link and a corresponding time point on the second link, so that when the time at which the mapping relationship is established is determined based on the TBTT on the first link, the receiving end on the second link can still accurately determine, based on the radio frame, the time at which the mapping relationship corresponding to the second link is established.

[0169] It can be understood that Scheme 6 provided in this embodiment of the present application can be combined with any one or more of Schemes 1 to 5.

[0170] Method 7

[0171] The time precision of the effective time indicated by the mapping switch time field is μs. For example, the length of the mapping switch time field may be 4 octets. Because the TSF timers of all STAs on the link in a multilink device are synchronized with those of the AP, when the time precision of the effective time indicated by the mapping switch time field is μs, the mapping switch time field may be determined based on the TSF timer (or may be determined based on the value of the TSF timer). For example, the value carried in the mapping switch time field may start from the 0th bit of the TSF timer. For example, a radio frame may include a traffic identifier-to-link mapping element, which may include a mapping switch time field, and the mapping switch time field may be determined based on the TSF timer of the BSS corresponding to the second link. In another example, a radio frame may include two elements, and at least one of the two elements may include the mapping switch time field. For a description of a radio frame including two elements, see Schemes 1 to 5 above. Optionally, when the time precision of the effective time indicated by the mapping switch time field is μs, the time precision of the effective time indicated by the expected duration field may also be μs (e.g., from the 0th bit of the TSF timer value). For example, the traffic identifier to link mapping element further includes a third field, which indicates the time precision of the expected duration field. For a description of the third field, see the following description of the length field. Details will not be described here.

[0172] In this embodiment of the present application, when the time precision of the establishment time indicated by the mapping switching time field is changed to μs, even if the time when the mapping relationship is established is determined based on the TBTT on the first link, the receiving end on the second link can still accurately determine the time when the mapping relationship corresponding to the second link is established based on the radio frame.

[0173] Method 8

[0174] The traffic identifier-to-link mapping element further includes a length field, which indicates the length of the mapping switch time field. When the value carried in the length field is a first value (e.g., 2), the time precision of the establishment time indicated by the mapping switch time field is microseconds, e.g., the length is 4 octets. When the value carried in the length field is a second value (e.g., 1), the time precision of the establishment time indicated by the mapping switch time field is TU, e.g., the length is 2 octets. When the value carried in the length field is a third value (e.g., 0), the length of the mapping switch time field may be 0 or may be absent.

[0175] It can be understood that when the time precision of the establishment time indicated by the mapping switch time field is μs, refer to Scheme 7 above.

[0176] As shown in Figure 8b, the length field may also be referred to as the mapping switch time size field. In other words, the mapping switch time existence field in Figure 4a is reused as the mapping switch time size field. For a description of the other fields in Figure 8b, please refer to Figure 4a. Details will not be described here. For example, the traffic identifier to link mapping element further includes a third field, which indicates the time accuracy of the expected duration field. For a description of the third field, please refer to the description of the length field. Details will not be described here.

[0177] The method illustrated in Scheme 8 may be applied when a radio frame includes one traffic identifier-to-link mapping element, or when a radio frame includes at least two traffic identifier-to-link mapping elements, e.g., a first element and a second element. For example, the first element includes an expected duration field, where the expected duration field indicates an expected end time of the mapping relationship corresponding to the first element, and the expected end time is determined based on the first link. The second element includes a mapping switch time field and a length field. The mapping switch time field indicates a time when the mapping relationship corresponding to the second element is established, and the establishment time is determined based on the first link. For example, when the time precision of the mapping switch time field is μs, the time precision of the expected duration field may also be μs.

[0178] It may be understood that the first link and the second link shown in this embodiment of the present application are merely examples. For example, the second link may be understood as any link other than the first link between the multi-link devices.

[0179] In this embodiment of the present application, the time precision of the establishment time indicated by the mapping switch time field can be changed based on different scenario requirements. For example, when the mapping relationship is established based on another link, the time precision can be μs, or when the mapping relationship is established based on the current link, the time precision can be TU.

[0180] Method 9

[0181] The difference between the TSF timers on different links is set to an integer multiple of TU. When the values ​​of the TSF timers of the BSSs corresponding to different links are each an integer multiple of TU, ​​the mapping switch time field can indicate the first TBTT of the first link. Therefore, the receiving end can effectively know the establishment time when the mapping relationship corresponding to the second link is established based on the mapping switch time field.

[0182] It may be understood that the methods shown in Scheme 6 to Scheme 9 may be applied when a radio frame includes one traffic identifier-to-link mapping element, or when a radio frame includes at least two traffic identifier-to-link mapping elements, for example, a first element and a second element. When two elements are included, Scheme 6 to Scheme 9 may be further combined with Scheme 1 to Scheme 5. The specific combination schemes will not be described again here.

[0183] In the above methods 6 to 9, the time at which the mapping relationship on the current link is established can also be accurately indicated when the mapping relationship is determined based on the time of the TBTT on another link.

[0184] The following describes a communication device provided in an embodiment of the present application.

[0185] In the present application, the communication device is divided into functional modules based on the above method embodiment. For example, functional modules corresponding to functions may be obtained through division, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware or in the form of a software functional module. It should be noted that in the present application, the module division is merely an example and represents a logical function division. In actual implementation, other division methods may be used. The following describes in detail the communication device in the embodiment of the present application with reference to Figures 9 to 11.

[0186] 9 is a diagram of a structure of a communication device according to an embodiment of the present application. As shown in FIG. 9, the communication device includes a processing unit 901 and a transceiver unit 902. The transceiver unit 902 may implement corresponding communication functions, and the processing unit 901 is configured to perform data processing. The transceiver unit 902 may also be referred to as a communication interface, a communication unit, etc.

[0187] In some embodiments of the present application, a communication device may be configured to perform the actions performed by the transmitting end in the above method embodiments. In this case, the communication device may be the transmitting end or a component (e.g., a chip or a system) that may be disposed in the transmitting end. The transceiver unit 902 is configured to perform the receiving / transmitting-related operations of the transmitting end in the above method embodiments. The processing unit 901 is configured to perform the processing-related operations of the transmitting end in the above method embodiments.

[0188] In some embodiments of the present application, the communication device may be the transmitting end or the chip described above, and the chip may be disposed in the transmitting end. In other words, the communication device may be configured to perform the steps, functions, etc. performed by the transmitting end in the method embodiments (including Scheme 1 to Scheme 9).

[0189] The processing unit 901 is configured to generate radio frames. The transceiver unit 902 is configured to output the radio frames.

[0190] Optionally, the communication device may further include a storage unit. The storage unit may be configured to store instructions and / or data. The processing unit 901 may read the instructions and / or data in the storage unit to enable the communication device to implement the above method embodiments.

[0191] In some other embodiments of the present application, a communication device may be configured to perform the actions performed by the receiving end in the above method embodiments. In this case, the communication device may be the receiving end or a component that may be disposed in the receiving end. The transceiver unit 902 is configured to perform the receiving / transmitting-related operations of the receiving end in the above method embodiments. The processing unit 901 is configured to perform the processing-related operations of the receiving end in the above method embodiments. In other words, the communication device may be configured to perform the steps, functions, etc. performed by the receiving end in the method embodiments (including Scheme 1 to Scheme 9).

[0192] The transceiver unit 902 is configured to input a radio frame. The processing unit 901 is configured to parse the radio frame.

[0193] It can be understood that for a specific description of parsing the radio frame by the processing unit 901, please refer to the above method embodiments, and details will not be described here.

[0194] Optionally, the communication device may further include a storage unit. The storage unit may be configured to store instructions and / or data. The processing unit 901 may read the instructions and / or data in the storage unit to enable the communication device to implement the above method embodiments.

[0195] It can be understood that the specific descriptions of the transceiver unit and the processing unit described in the embodiments of the present application are merely examples. For the specific functions, steps performed, etc. of the transceiver unit and the processing unit, please refer to the above method embodiments. Details will not be described here.

[0196] For descriptions of the radio frame, the mapping switching time field, the expected duration field, the first element, the second element, etc. in the above embodiments, please refer to the descriptions in the above method embodiments, and details will not be described here.

[0197] The above describes a communication device in an embodiment of the present application. The following describes possible product forms of the communication device. It should be understood that any product in any form having the functions of the communication device described in Fig. 9 falls within the protection scope of the embodiment of the present application. It should be further understood that the following description is merely an example and does not limit the product form of the communication device in the embodiment of the present application.

[0198] In a possible implementation, in the communication device shown in FIG. 9, the processing unit 901 may be one or more processors. The transceiver unit 902 may be a transceiver, or the transceiver unit 902 may be a sending unit and a receiving unit. The sending unit may be a transmitter, and the receiving unit may be a receiver. The sending unit and the receiving unit may be integrated into one component, for example, a transceiver. In this embodiment of the present application, the processor and the transceiver may be combined, etc. The manner of connection between the processor and the transceiver is not limited in the embodiment of the present application. In the process of implementing the above method, the information sending process in the above method may be understood as a process of outputting the information by the processor. When outputting the information, the processor outputs the information to the transceiver, and as a result, the transceiver transmits the information. After the information is output by the processor, other processes may need to be performed on the information before it arrives at the transceiver. Similarly, the information receiving process in the above method may be understood as a process of receiving the input information by the processor. When the processor receives the input information, the transceiver receives the information and inputs the information to the processor. Furthermore, after the transceiver receives the information, other processing may need to be performed on the information before it is input to the processor.

[0199] As shown in FIG. 10, a communications device 100 includes one or more processors 1020 and a transceiver 1010 .

[0200] In some embodiments of the present application, the communication device may be configured to perform the steps, functions, etc. performed by the transmitting end in the method embodiments (including Scheme 1 to Scheme 9).

[0201] The processor 1020 is configured to generate the radio frames. The transceiver 1010 is configured to transmit the radio frames.

[0202] For example, the transceiver 1010 is further configured to receive an acknowledgement frame.

[0203] In some other embodiments of the present application, the communication device may be configured to perform the steps, functions, etc. performed by the receiving end in the method embodiments (including Scheme 1 to Scheme 9).

[0204] The transceiver 1010 is configured to receive radio frames. The processor 1020 is configured to parse the radio frames.

[0205] It can be understood that the specific descriptions of the transceiver and the processor described in the embodiments of the present application are merely examples. For the specific functions of the transceiver and the processor, the steps performed, etc., please refer to the above method embodiments. Details will not be described here.

[0206] For descriptions of the radio frame, the mapping switching time field, the expected duration field, the first element, the second element, etc. in the above embodiments, please refer to the descriptions in the above method embodiments, and details will not be described here.

[0207] In each implementation of the communication apparatus shown in Figure 10, the transceiver may include a receiver and a transmitter. The receiver is configured to perform receiving functions (or operations), and the transmitter is configured to perform transmitting functions (or operations). The transceiver is configured to communicate with another device / apparatus over a transmission medium.

[0208] Optionally, the communication device 100 may further include one or more memories 1030 configured to store program instructions and / or data. The memory 1030 is coupled to the processor 1020. A coupling in this embodiment of the present application may be an indirect coupling or communication connection between devices, units, or modules, and may be in an electrical, mechanical, or other form, used for information exchange between the devices, units, or modules. The processor 1020 may cooperate with the memory 1030. The processor 1020 may execute program instructions stored in the memory 1030. Optionally, at least one of the one or more memories may be included in the processor.

[0209] The specific connection medium between the transceiver 1010, the processor 1020, and the memory 1030 is not limited in the embodiment of the present application. In this embodiment of the present application, in FIG. 10, the memory 1030, the processor 1020, and the transceiver 1010 are connected to each other via a bus 1040. The bus is shown by a bold line in FIG. 10. The manner of connection between the other components is described by way of example only and is not limited thereto. The bus may be classified into an address bus, a data bus, a control bus, etc. For ease of representation, the bus is shown by only one bold line in FIG. 10. However, this does not mean that there is only one bus or only one type of bus.

[0210] In this embodiment 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, or a discrete hardware component, which may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, any conventional processor, etc. The steps of the methods disclosed in relation to the embodiments of the present application may be directly implemented and performed by a hardware processor, or may be implemented and performed by using a combination of hardware and software modules in the processor.

[0211] In this embodiment of the present application, the memory may include, but is not limited to, a non-volatile memory, such as a hard disk drive (HDD) or solid-state drive (SSD), a random access memory (RAM), an erasable programmable read-only memory (EPROM), a read-only memory (ROM), or a compact disc read-only memory (CD-ROM). The memory is any storage medium that can be used to carry or store program code in the form of instructions or data structures and that can be read and / or written by a computer (e.g., a communication device described in this application). The memory in the embodiment of the present application may alternatively be a circuit or any other device capable of implementing a storage function and configured to store program instructions and / or data.

[0212] For example, the processor 1020 is primarily configured to process communication protocols and communication data, control the entire communication device, execute software programs, and process data of the software programs. The memory 1030 is primarily configured to store software programs and data. The transceiver 1010 may include a control circuit and an antenna. The control circuit is primarily configured to convert between baseband signals and radio frequency signals and process the radio frequency signals. The antenna is primarily configured to receive and transmit radio frequency signals in the form of electromagnetic waves. The input / output device, for example, a touch screen, a display, or a keyboard, is primarily configured to receive data input by a user and output data to the user.

[0213] After the communication device is powered on, the processor 1020 can read the software program in the memory 1030, 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 1020 performs baseband processing on the data to be sent and then outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal in the form of electromagnetic waves through an 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 to a baseband signal, and outputs the baseband signal to the processor 1020. The processor 1020 converts the baseband signal to data and processes the data.

[0214] In another implementation, the radio frequency circuitry and antenna may be located independently of the processor that performs the baseband processing, for example, in a distributed scenario, the radio frequency circuitry and antenna may be located independently and remote from the communication device.

[0215] It can be understood that the communication device described in the embodiment of the present application may further have more components than those shown in FIG. 10 , etc. This is not limited in the embodiment of the present application. The above-described method implemented by the processor and the transceiver is merely an example. For specific steps implemented by the processor and the transceiver, please refer to the method described above.

[0216] In another possible implementation, in the communication device shown in FIG. 9, the processing unit 901 may be one or more logic circuits, and the transceiver unit 902 may be an input / output interface, also referred to as a communication interface, interface circuit, interface, etc. Alternatively, the transceiver unit 902 may be a sending unit and a receiving unit. The sending unit may be an output interface, and the receiving unit may be an input interface. The sending unit and the receiving unit are integrated into one unit, for example, an input / output interface. As shown in FIG. 11, the communication device shown in FIG. 11 includes a logic circuit 1101 and an interface 1102. In other words, the processing unit 901 may be implemented via the logic circuit 1101, and the transceiver unit 902 may be implemented via the interface 1102. The logic circuit 1101 may be a chip, a processing circuit, an integrated circuit, a system on chip (SoC), etc. The interface 1102 may be a communication interface, an input / output interface, a pin, etc. For example, FIG. 11 illustrates an example in which the communication device is a chip. The chip includes a logic circuit 1101 and an interface 1102 .

[0217] In the embodiment of the present application, the logic circuit and the interface may further be coupled to each other, and the specific manner of connection between the logic circuit and the interface is not limited in the embodiment of the present application.

[0218] In some embodiments of the present application, the communication device may be configured to perform the steps, functions, etc. performed by the transmitting end in the method embodiments (including Scheme 1 to Scheme 9).

[0219] The logic circuit 1101 is configured to generate radio frames. The interface 1102 is configured to output the radio frames.

[0220] In some other embodiments of the present application, the communication device may be configured to perform the steps, functions, etc. performed by the receiving end in the method embodiments (including Scheme 1 to Scheme 9).

[0221] The interface 1102 is configured to input a radio frame. The logic circuit 1101 is configured to parse the radio frame.

[0222] It can be understood that the specific descriptions of the logic circuits and interfaces described in the embodiments of the present application are merely examples. For the specific functions, steps performed, etc. of the logic circuits and interfaces, please refer to the above method embodiments. Details will not be described here.

[0223] For descriptions of the radio frame, the mapping switching time field, the expected duration field, the first element, the second element, etc. in the above embodiments, please refer to the descriptions in the above method embodiments, and details will not be described here.

[0224] It can be understood that the communication device described in this embodiment of the present application can implement the method provided in the embodiment of the present application in the form of hardware or software, which is not limited in the embodiment of the present application.

[0225] An embodiment of the present application further provides a wireless communication system, which includes a transmitting end and a receiving end, and the transmitting end and the receiving end can be configured to implement the method in any of the above embodiments.

[0226] Furthermore, the present application further provides a computer program, which is used to implement the actions and / or processes performed by the transmitting end in the methods provided in the present application.

[0227] The present application further provides a computer program, which is used to implement the actions and / or processes performed by the receiving end in the methods provided in the present application.

[0228] The present application further provides a computer-readable storage medium that stores computer code, which, when run on a computer, enables the computer to perform the operations and / or processes performed by the sending end in the methods provided herein.

[0229] The present application further provides a computer-readable storage medium that stores computer code, which, when run on a computer, enables the computer to perform the operations and / or processes performed by the receiving end in the methods provided herein.

[0230] The present application further provides a computer program product, which includes computer code or a computer program, which, when run on a computer, performs the operations and / or processes performed by the sending end in the methods provided herein.

[0231] The present application further provides a computer program product, which includes computer code or a computer program that, when run on a computer, performs the operations and / or processes performed by a receiving end in the methods provided herein.

[0232] In some embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical functional division. In actual implementation, other division methods may exist. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. Furthermore, the shown or described mutual couplings or direct couplings or communication connections may be implemented via some interfaces. Indirect couplings or communication connections between devices or units may be implemented in electrical, mechanical, or other forms.

[0233] The units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, and may be located in one location or distributed over multiple network units. Some or all of the units may be selected based on actual requirements to achieve the technical effects of the solutions provided in the embodiments of the present application.

[0234] Furthermore, the functional units in the embodiments of the present application may be integrated into one processing unit, each unit may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0235] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or a portion contributing to the prior art, or all or part of the technical solution, may be implemented in the form of a software product. The computer software product is stored in a readable storage medium and includes a plurality of instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method described in the embodiments of the present application. The readable storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0236] The above description is merely a specific implementation of the present application and does not limit the scope of protection of the present application. Any variations or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed in the present application shall fall within the scope of protection of the present application. Therefore, the scope of protection of the present application should be subject to the scope of protection of the claims.

Claims

1. 1. A multi-link communication method, the method comprising: generating a radio frame, the radio frame including a first traffic identifier-to-link mapping element and a second traffic identifier-to-link mapping element, the first traffic identifier-to-link mapping element including an expected duration field, the expected duration field indicating an expected end time of a traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element, the expected duration field being determined based on a most recent target beacon transmission time TBTT that precedes a transmission time of the radio frame or a target beacon transmission time TBTT at which the transmission time of the radio frame is at; the second traffic identifier-to-link mapping element includes a mapping switch time field, the mapping switch time field indicating a time at which a new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established, and the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established; transmitting the radio frame; A multi-link communication method comprising:

2. The value conveyed in the expected duration field is: The values ​​of bits 11 to 26 of the TSF timer; the value of bits 11 through 34 of the TSF timer; or The values ​​of the 11th to 50th bits of the TSF timer The method of claim 1, wherein the method is the same as any one of

3. 3. The method of claim 1, wherein the first traffic identifier-to-link mapping element is located before the second traffic identifier-to-link mapping element in the radio frame.

4. 1. A multi-link communication method, the method comprising: receiving a radio frame, the radio frame including a first traffic identifier-to-link mapping element and a second traffic identifier-to-link mapping element, the first traffic identifier-to-link mapping element including an expected duration field, the expected duration field indicating an expected end time of a traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element, the expected duration field being determined based on a most recent target beacon transmission time TBTT that precedes a transmission time of the radio frame or a target beacon transmission time TBTT at which the transmission time of the radio frame is at; the second traffic identifier-to-link mapping element includes a mapping switch time field, the mapping switch time field indicating a time at which a new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established, and the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established; parsing the radio frame; A multi-link communication method comprising:

5. The step of parsing the radio frame comprises: determining the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element by using the most recent TBTT prior to the transmission time of the radio frame as a starting point and using the value carried in the expected duration field as a remaining duration; or using the value conveyed in the expected duration field as the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element. The method of claim 4, comprising:

6. 1. A multi-link communication method, the method comprising: generating a radio frame, the radio frame including a first traffic identifier-to-link mapping element and a second traffic identifier-to-link mapping element, the first traffic identifier-to-link mapping element not including an expected duration field, and the second traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time at which a new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established and an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element, or the first traffic identifier-to-link mapping element including an expected duration field, the second traffic identifier-to-link mapping element not including a mapping switch time field, and the expected duration field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element will be established; transmitting the radio frame; A multi-link communication method comprising:

7. 1. A multi-link communication method, the method comprising: receiving a radio frame, the radio frame including a first traffic identifier-to-link mapping element and a second traffic identifier-to-link mapping element, the first traffic identifier-to-link mapping element not including an expected duration field, and the second traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time at which a new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established and an expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element, or the first traffic identifier-to-link mapping element including an expected duration field, the second traffic identifier-to-link mapping element not including a mapping switch time field, and the expected duration field indicating a time at which a new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established; parsing the radio frame; A multi-link communication method comprising:

8. The step of parsing the radio frame comprises: when the first traffic identifier-to-link mapping element does not include the expected duration field and the second traffic identifier-to-link mapping element includes the mapping switch time field, determining the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element based on the mapping switch time field, wherein the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established; or determining, when the first traffic identifier-to-link mapping element includes the expected duration field and the second traffic identifier-to-link mapping element does not include the mapping switch time field, the time at which the new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established based on the expected duration field, wherein the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is the same as the time at which the new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established. The method of claim 7, comprising:

9. 1. A multi-link communication method, the method comprising: receiving a radio frame, the radio frame including a first traffic identifier-to-link mapping element and a second traffic identifier-to-link mapping element, the first traffic identifier-to-link mapping element including an expected duration field, the expected duration field indicating an expected end time of a traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element, and the second traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time when a new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established; determining the time at which the new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element will be established based on the expected duration field, or determining the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element based on the mapping switch time field; A multi-link communication method comprising:

10. determining the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element based on the mapping switch time field; determining, based on the mapping switch time field, the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element when the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is later than the time at which the new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established, wherein the expected end time of the traffic identifier-to-link mapping relationship indicated by the first traffic identifier-to-link mapping element is equal to the time at which the new traffic identifier-to-link mapping relationship indicated by the second traffic identifier-to-link mapping element is established.

10. The method of claim 9, comprising:

11. 1. A multi-link communication method, the method comprising: generating a radio frame, the radio frame including a traffic identifier-to-link mapping element, the traffic identifier-to-link mapping element including a mapping switch time field and a first field, the mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the traffic identifier-to-link mapping element is established, the time being determined based on a first target beacon time (TBTT) on a first link, the first field indicating a time difference between the first TBTT on the first link and a time point on a second link corresponding to the first TBTT, the time point being no later than the first TBTT and a time point on the second link closest to the first TBTT, and a value of 10 least significant bits of a time synchronization function (TSF) timer for the time point being 0, or the time point being a TBTT on the second link; transmitting the radio frame over the second link; A multi-link communication method comprising:

12. 12. The method of claim 11, wherein the traffic identifier-to-link mapping element further comprises a second field, the second field indicating the presence of the first field.

13. 13. The method of claim 11 or 12, wherein the value carried in the first field is the value of bits 1 to 10 of the Time Synchronization Function TSF timer of a Basic Service Set BSS corresponding to the second link.

14. 1. A multi-link communication method, the method comprising: receiving a radio frame over a second link, the radio frame including a traffic identifier-to-link mapping element, the traffic identifier-to-link mapping element including a mapping switch time field and a first field, the mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the traffic identifier-to-link mapping element is established, the time being determined based on a first target beacon time (TBTT) on a first link, the first field indicating a time difference between the first TBTT on the first link and a time point on the second link corresponding to the first TBTT, the time point being a time point on the second link that is not later than the first TBTT and closest to the first TBTT, and the value of 10 least significant bits of a time synchronization function (TSF) timer for the time point being 0, or the time point being a TBTT on the second link; parsing the radio frame; A multi-link communication method comprising:

15. The step of parsing the radio frame comprises: determining a time at which a traffic identifier-to-link mapping relationship corresponding to the second link is established based on the first field and the time indicated by the mapping switch time field; 15. The method of claim 14, comprising:

16. 1. A multi-link communication method, the method comprising: generating a radio frame, the radio frame including a traffic identifier-to-link mapping element, the traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the traffic identifier-to-link mapping element is established, the time having a time precision of microseconds; transmitting the radio frame; A multi-link communication method comprising:

17. 17. The method of claim 16, wherein the traffic identifier-to-link mapping element further includes a length field, the length field indicating a length of the mapping switch time field, and the time precision of the time is microseconds when a value carried in the length field is a first value.

18. 1. A multi-link communication method, the method comprising: receiving a radio frame, the radio frame including a traffic identifier-to-link mapping element, the traffic identifier-to-link mapping element including a mapping switch time field, the mapping switch time field indicating a time at which a traffic identifier-to-link mapping relationship indicated by the traffic identifier-to-link mapping element is established, the time having a time precision of microseconds; parsing the radio frame; A multi-link communication method comprising:

19. The step of parsing the radio frame comprises: determining the time at which the traffic identifier-to-link mapping relationship is established based on a value conveyed in the mapping switch time field.

20. The method of claim 18, comprising:

20. The method comprises: When the transmission time of the radio frame is at the TBTT, the expected duration field is determined based on the transmission time of the radio frame.

3. The method of claim 1 or 2, further comprising:

21. A communication device comprising a unit adapted to carry out a method according to any one of claims 1 to 20.

22. A communication device comprising a processor and a memory, the memory configured to store instructions; The processor is configured to execute the instructions to perform the method of any one of claims 1 to 20. Communication equipment.

23. a communication device comprising a logic circuit and an interface, said logic circuit coupled to said interface; The interface is configured to input and / or output code instructions, and the logic circuit is configured to execute the code instructions to perform the method of any one of claims 1 to 20. Communication equipment.

24. 21. A computer-readable storage medium configured to store a computer program which, when executed, performs the method of any one of claims 1 to 20.

25. A computer program which, when executed, performs the method of any one of claims 1 to 20.

26. 13. A communication system comprising a transmitting end and a receiving end, wherein the transmitting end is configured to perform the method of any one of claims 1 to 3 and the receiving end is configured to perform the method of claim 4 or 5, or the transmitting end is configured to perform the method of claim 6 and the receiving end is configured to perform the method of claim 7 or 8, or the receiving end is configured to perform the method of claim 9 or 10, or the transmitting end is configured to perform the method of any one of claims 11 to 13 and the receiving end is configured to perform the method of claim 14 or 15, or the transmitting end is configured to perform the method of claim 16 or 17 and the receiving end is configured to perform the method of claim 18 or 19.

Images