A traffic identification method that specifies address numbers at each individual point, applicable to multiple links and related equipment sets.

Abstract

Invention details;

Description

Unicast service indication method and related device applicable to multi-link

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on August 7, 2020, with application number 202010791117.1 and application name “Unicast service indication method and related device suitable for multi-links”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to a unicast service indication method applicable to multiple links and related devices. Background Art

[0003] To significantly increase the service transmission rate of wireless local area network (WLAN) systems, the Institute of Electrical and Electronics Engineers (IEEE) 802.11ax standard further utilizes Orthogonal Frequency Division Multiple Access (OFDMA) technology, building upon existing Orthogonal Frequency Division Multiplexing (OFDM) technology. OFDMA technology allows multiple nodes to send and receive data simultaneously, thereby achieving multi-site diversity gain.

[0004] The next-generation Wi-Fi standard, IEEE 802.11be, is known as Extremely High Throughput (EHT), or Wi-Fi 7. Its most important technical goal is to significantly improve peak throughput. IEEE 802.11be WLAN devices support increasing peak throughput and reducing service transmission latency through multiple streams (with a maximum of 16 spatial streams), multiple frequency bands (for example, 2.4 GHz, 5 GHz, and 6 GHz), and the collaboration of multiple channels on the same frequency band. These multiple frequency bands or channels are collectively referred to as multilinks. Next-generation IEEE 802.11 standard stations that support multiple links simultaneously are called multi-link devices (MLDs).

[0005] However, some special access point multi-link devices (for example, all access points (APs) included in the access point multi-link device are APs with a Basic Service Set Identifier (BSSID) of non-transmitted) are unable to send beacon frames to indicate whether the associated station (STA) multi-link device has downlink unicast services. As a result, the associated station multi-link device cannot correctly receive downlink unicast services. Therefore, for these special access point multi-link devices (AP MLDs), how to indicate downlink unicast services has become an urgent problem to be solved.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a unicast service indication method and related apparatus applicable to multi-link, which can help some APs or all APs in a partial AP MLD indicate whether the site multi-link device associated with it has downlink unicast services, so as to assist the site multi-link device to correctly receive downlink unicast services.

[0008] The present application is introduced below from different aspects. It should be understood that the implementation methods and beneficial effects of the following different aspects can be referenced to each other.

[0009] In a first aspect, the present application provides a unicast service indication method applicable to multiple links, which is applied to a first AP MLD, where the first AP is a reporting AP. The unicast service indication method applicable to multiple links includes: the first AP of the first AP MLD generates unicast service indication information and sends the unicast service indication information on a first link. The unicast service indication information is used to indicate whether a non-AP MLD associated with the first AP MLD has downlink unicast service, and whether a non-AP MLD associated with a second AP MLD has downlink unicast service, where the second AP MLD is an AP MLD to which a non-transmitting AP belongs in the multi-BSSID set where the first AP is located. The first link is the working link of the first AP.

[0010] Optionally, the reporting AP may refer to an AP that sends a management frame, which carries information of multiple APs in the AP MLD set co-located with the reporting AP itself. The management frame is, for example, a beacon frame, a probe response frame, etc.

[0011] The unicast service indication information in this solution not only indicates whether the non-AP MLD associated with the first AP MLD has downstream unicast services, but also helps the second AP MLD indicate whether the non-AP MLD associated with the second AP MLD has downstream unicast services. The second AP MLD is the AP MLD of the non-transmitting AP in the multi-BSSID set to which the first AP belongs. This solves the problem where some or all APs in the AP MLD cannot indicate whether the associated non-AP MLD has downstream unicast services, allowing the non-AP MLDs associated with these APs to normally receive downstream unicast services.

[0012] In addition, since all APs in an AP MLD in 802.11be may be non-transmitting APs, this solution can solve the problem that the AP MLD of all non-transmitting APs cannot send unicast service indications, thereby increasing the integrity and diversity of downlink service indications.

[0013] In combination with the first aspect, in a possible implementation, the method further includes: the first AP of the first AP MLD generates and sends association identifier (AID) allocation information, where the AID allocation information carries an AID allocated for the Non-AP MLD, and the AID is different from the AID of the Non-AP MLD associated with the second AP MLD.

[0014] Optionally, the AID allocation information is carried in an association response frame. It is understandable that the AID allocation information can also be carried in other frames.

[0015] Optionally, before the second AP of the first AP MLD sends the association response frame, the method further includes: the first AP of the first AP MLD receives an association request frame, where the association request frame is used to request to establish a multi-link association with the first AP MLD.

[0016] During AID allocation, this solution considers that the first AP MLD helps the second AP MLD indicate whether the non-AP MLD associated with the second AP MLD has downlink unicast services. This ensures that the AID allocated by the first AP MLD to the non-AP MLD associated with it is different from the AID of the non-AP MLD associated with the second AP MLD, thereby avoiding AID ambiguity when indicating downlink unicast services.

[0017] In a second aspect, the present application provides a unicast service indication method applicable to multiple links, which is applied to Non-AP MLD. The unicast service indication method applicable to multiple links includes: the first STA of the Non-AP MLD receives unicast service indication information on the first link where the first STA works, and determines whether the Non-AP MLD has downlink unicast service based on the received unicast service indication information. The unicast service indication information is used to indicate whether the Non-AP MLD associated with the first AP MLD has downlink unicast service, and whether the Non-AP MLD associated with the second AP MLD has downlink unicast service, and the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located.

[0018] Optionally, the reporting AP may refer to an AP that sends a management frame, which carries information of multiple APs in the AP MLD set co-located with the reporting AP itself. The management frame is, for example, a beacon frame, a probe response frame, etc.

[0019] In combination with the second aspect, in a possible implementation, the method further includes: the first STA of the Non-AP MLD receives AID allocation information, and parses the received AID allocation information to obtain the AID allocated for the Non-AP MLD carried in the AID allocation information, where the AID is different from the AID of the Non-AP MLD associated with the second AP MLD.

[0020] Optionally, the AID allocation information is carried in an association response frame. It is understandable that the AID allocation information can also be carried in other frames.

[0021] Optionally, before the first STA of the Non-AP MLD receives the association response frame, the method further includes: the first STA of the Non-AP MLD generates and sends an association request frame, where the association request frame is used to request to establish a multi-link association with the first AP MLD.

[0022] In a third aspect, the present application provides a communication device, which may be a first AP MLD or a chip in the first AP MLD, such as a Wi-Fi chip, or may be a first AP in the first AP MLD, including: a processing unit for generating unicast service indication information, the unicast service indication information being used to indicate whether the Non-AP MLD associated with the first AP MLD has a downlink unicast service, and whether the Non-AP MLD associated with the second AP MLD has a downlink unicast service, the second AP MLD being the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located; a transceiver unit for sending the unicast service indication information on a first link, the first link being a working link of the first AP.

[0023] Optionally, the reporting AP may refer to an AP that sends a management frame, which carries information of multiple APs in the AP MLD set co-located with the reporting AP itself. The management frame is, for example, a beacon frame, a probe response frame, etc.

[0024] In conjunction with the third aspect, in one possible implementation, the processing unit is further configured to generate AID allocation information, where the AID allocation information carries an AID allocated for the Non-AP MLD, where the AID is different from the AID of the Non-AP MLD associated with the second AP MLD; and the transceiver unit is further configured to send the AID allocation information.

[0025] Optionally, the AID allocation information is carried in an association response frame. It is understandable that the AID allocation information can also be carried in other frames.

[0026] Optionally, the transceiver unit is further configured to receive an association request frame, where the association request frame is used to request to establish a multi-link association with the first AP MLD.

[0027] In a fourth aspect, the present application provides a communication device, which may be a Non-AP MLD or a chip in the Non-AP MLD, such as a Wi-Fi chip, or may be a first STA in the Non-AP MLD, including: a transceiver unit for receiving unicast service indication information on a first link on which the first STA operates, the unicast service indication information being used to indicate whether the Non-AP MLD associated with the first AP MLD has a downlink unicast service, and whether the Non-AP MLD associated with the second AP MLD has a downlink unicast service, the second AP MLD being the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located; a processing unit for determining whether the Non-AP MLD has a downlink unicast service based on the received unicast service indication information.

[0028] Optionally, the reporting AP may refer to an AP that sends a management frame, which carries information of multiple APs in the AP MLD set co-located with the reporting AP itself. The management frame is, for example, a beacon frame, a probe response frame, etc.

[0029] In conjunction with the fourth aspect, in one possible implementation, the transceiver unit is further configured to receive AID allocation information; and the processing unit is further configured to parse the received AID allocation information to obtain an AID allocated for the Non-AP MLD carried in the AID allocation information, where the AID is different from the AID of the Non-AP MLD associated with the second AP MLD.

[0030] Optionally, the AID allocation information is carried in an association response frame. It is understandable that the AID allocation information can also be carried in other frames.

[0031] Optionally, the processing unit is further configured to generate an association request frame; and the transceiver unit is further configured to send an association request frame, where the association request frame is used to request to establish a multi-link association with the first AP MLD.

[0032] In one implementation of any of the above aspects, one bit of the unicast service indication information corresponds to a Non-AP MLD, and the one bit of the unicast service indication information is used to indicate whether the corresponding Non-AP MLD has a downlink unicast service. The Non-AP MLD includes a Non-AP MLD associated with the first AP MLD and a Non-AP MLD associated with the second AP MLD.

[0033] In one implementation of any of the above aspects, one bit of the unicast service indication information corresponds to an association identifier (AID), and the one bit of the unicast service indication information is used to indicate whether the non-AP MLD identified by the corresponding AID has a downlink unicast service. The non-AP MLD includes a non-AP MLD associated with the first AP MLD and a non-AP MLD associated with the second AP MLD.

[0034] Optionally, the unicast service indication information is carried in a partial virtual bit map field of a traffic indication map TIM element.

[0035] This solution uses some bits in the partial virtual bitmap field of the TIM element to indicate whether the non-AP MLD associated with the reporting AP's MLD has downlink unicast services and whether the non-AP MLD associated with each second AP MLD has downlink unicast services. Without changing the frame format of the TIM element, one AP MLD helps another AP MLD indicate whether the non-AP MLD associated with the other AP MLD has downlink unicast services, thereby improving the flexibility of downlink unicast service notification.

[0036] In an implementation of any of the above aspects, the association identifiers AIDs corresponding to the bits in the unicast service indication information are different, so as to avoid AID ambiguity when indicating whether the Non-AP MLD has a downlink unicast service.

[0037] In an implementation of any of the above aspects, the unicast service indication information includes a TIM block corresponding to the first AP MLD and a TIM block corresponding to the second AP MLD, the TIM block corresponding to the first AP MLD is used to indicate whether the Non-AP MLD associated with the first AP MLD has a downlink unicast service, and a TIM block corresponding to the second AP MLD is used to indicate whether the Non-AP MLD associated with the second AP MLD has a downlink unicast service.

[0038] Optionally, the unicast service indication information further includes an index of a second AP MLD, and the index of the second AP MLD corresponds one-to-one to a TIM block corresponding to the second AP MLD.

[0039] Optionally, one bit of the TIM block corresponds to a Non-AP MLD, and the one bit of the TIM block is used to indicate whether the corresponding Non-AP MLD has a downlink unicast service.

[0040] Optionally, the association identifiers AIDs corresponding to the bits in the TIM block are different.

[0041] Optionally, the AID space used by the first AP MLD to allocate AIDs to its associated Non-AP MLD and the AID space used by the second AP MLD to allocate AIDs to its associated Non-AP MLD are independent of each other. The AID space here may also refer to a set of AIDs to be allocated.

[0042] This solution provides TIM indications for different AP MLDs in separate blocks, thus avoiding ambiguity in the AIDs of non-AP MLDs associated with different AP MLDs.

[0043] In a fifth aspect, the present application provides a method for allocating an association identifier (AID) of a multi-link device, which is applied to any AP of an AP MLD. The method for allocating an AID of a multi-link device includes: i Generate and send AID allocation information, which carries the AID allocated for the Non-AP MLD. The AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is associated with the AP i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the set circle of the co-located AP MLD set. i Any AP in the AP MLD.

[0044] Optionally, the AID allocation information is carried in an association response frame. It is understandable that the AID allocation information can also be carried in other frames.

[0045] Optional, if the target AP MLD is the same as the AP i Any AP MLD in the AP MLD set of the same location, then the AP MLD and the target AP MLD are both related to the AP i The MLD set of APs with the same location. If the target AP MLD is i Any AP MLD in the set circle of the AP MLD set with the same location, then the AP MLD and the target AP MLD above belong to the AP MLD with the same location. i The MLD set of the co-located APs is in the collection circle, which includes the AP i MLD set of co-located APs and the AP i The MLD set of APs in the same location is excluding AP i The MLD set of APs that are co-located with any AP other than the AP.

[0046] Optionally, before the AP of the AP MLD sends the association response frame, the method further includes: i An association request frame is received, where the association request frame is used to request to establish a multi-link association with the AP MLD.

[0047] This solution considers AP i The AID of the associated Non-AP MLD and the AID of the Non-AP MLD associated with the target AP MLD should be unique, that is, different. This can avoid AID ambiguity when indicating whether the Non-AP MLD has downlink unicast services.

[0048] In a sixth aspect, the present application provides an AID allocation method for a multi-link device, which is applied to any STA of a Non-AP MLD. The AID allocation method for a multi-link device includes: the STA of the Non-AP MLD receives AID allocation information, and parses the AID allocation information to obtain an AID allocated for the Non-AP MLD carried in the AID allocation information, wherein the AID is different from the AID of the Non-AP MLD associated with the target AP MLD, and the target AP MLD is associated with the AP MLD. i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the set circle of the co-located AP MLD set. i Any AP in the AP MLD.

[0049] Optionally, the AID allocation information is carried in an association response frame. It is understandable that the AID allocation information can also be carried in other frames.

[0050] Optional, if the target AP MLD is the same as the AP i Any AP MLD in the AP MLD set of the same location, then the AP MLD and the target AP MLD are both related to the AP i The MLD set of APs with the same location. If the target AP MLD is i Any AP MLD in the set circle of the AP MLD set with the same location, then the AP MLD and the target AP MLD above belong to the AP MLD with the same location. i The MLD set of the co-located APs is in the collection circle, which includes the AP i MLD set of co-located APs and the AP i The MLD set of APs in the same location is excluding AP i The MLD set of APs that are co-located with any AP other than the AP.

[0051] Optionally, before the Non-AP MLD STA receives the association response frame, the method further includes: the Non-AP MLD STA generating and sending an association request frame, where the association request frame is used to request to establish a multi-link association with the AP MLD.

[0052] In a seventh aspect, the present application provides a communication device, which can be an AP MLD or a chip in an AP MLD, such as a Wi-Fi chip, including: a processing unit for generating AID allocation information, wherein the AID allocation information carries an AID allocated for a Non-AP MLD, and the AID is different from the AID of the Non-AP MLD associated with the target AP MLD, and the target AP MLD is associated with the AP MLD. i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the set circle where the co-located AP MLD set is located; the transceiver unit is used to send the association response frame. i Any AP in the AP MLD.

[0053] Optionally, the AID allocation information is carried in an association response frame. It is understandable that the AID allocation information can also be carried in other frames.

[0054] Optional, if the target AP MLD is the same as the AP i Any AP MLD in the AP MLD set of the same location, then the AP MLD and the target AP MLD are both related to the AP i The MLD set of APs with the same location. If the target AP MLD is i Any AP MLD in the set circle of the AP MLD set with the same location, then the AP MLD and the target AP MLD above belong to the AP MLD with the same location. i The MLD set of the co-located APs is in the collection circle, which includes the AP i MLD set of co-located APs and the AP i The MLD set of APs in the same location is excluding AP i The MLD set of APs that are co-located with any AP other than the AP.

[0055] Optionally, the transceiver unit is further configured to receive an association request frame, where the association request frame is used to request to establish a multi-link association with the AP MLD.

[0056] In an eighth aspect, the present application provides a communication device, which may be a Non-AP MLD or a chip in a Non-AP MLD, such as a Wi-Fi chip, comprising: a transceiver unit for receiving AID allocation information from an AP of an AP MLD; a processing unit for parsing the received AID allocation information to obtain an AID allocated to the Non-AP MLD carried in the AID allocation information, wherein the AID is different from the AID of the Non-AP MLD associated with the target AP MLD, and the target AP MLD is associated with the AP MLD. i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the set circle of the co-located AP MLD set. i Any AP in the AP MLD.

[0057] Optionally, the AID allocation information is carried in an association response frame. It is understandable that the AID allocation information can also be carried in other frames.

[0058] Optional, if the target AP MLD is the same as the AP i Any AP MLD in the AP MLD set of the same location, then the AP MLD and the target AP MLD are both related to the AP i The MLD set of APs with the same location. If the target AP MLD is i Any AP MLD in the set circle of the AP MLD set with the same location, then the AP MLD and the target AP MLD above belong to the AP MLD with the same location. i The MLD set of the co-located APs is in the collection circle, which includes the AP i MLD set of co-located APs and the AP i The MLD set of APs in the same location is excluding AP i The MLD set of APs that are co-located with any AP other than the AP.

[0059] Optionally, the processing unit is further configured to generate an association request frame; and the transceiver unit is further configured to send the association request frame, where the association request frame is used to request to establish a multi-link association with the AP MLD.

[0060] In a ninth aspect, the present application provides a communication device, specifically a first AP MLD or a first AP in the first AP MLD, comprising a processor and a transceiver. The processor is configured to support the first AP MLD in performing the corresponding functions of the method of the first aspect. The transceiver is configured to support communication between the first AP MLD and a non-access point multi-link device (also known as a site multi-link device), and to send information, frames, data packets, or instructions involved in the method to the site multi-link device. The first AP MLD may also include a memory, coupled to the processor, that stores necessary program instructions and data for the first AP MLD.

[0061] Specifically, the processor is used to generate unicast service indication information, which is used to indicate whether the Non-AP MLD associated with the first AP MLD has a downlink unicast service, and whether the Non-AP MLD associated with the second AP MLD has a downlink unicast service, and the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located; the transceiver is used to send the unicast service indication information on the first link, which is the working link of the first AP.

[0062] In a tenth aspect, the present application provides a communication device, specifically a first STA in a non-access point multi-link device (also known as a station multi-link device) or a non-AP MLD, comprising a processor and a transceiver. The processor is configured to support the station multi-link device in performing the corresponding functions of the method of the second aspect described above. The transceiver is configured to support communication between the station multi-link device and the first AP MLD, and to receive information, frames, data packets, or instructions involved in the method described above from the first AP MLD. The station multi-link device may also include a memory, coupled to the processor, that stores necessary program instructions and data for the station multi-link device.

[0063] Specifically, the transceiver is used to receive unicast service indication information on the first link where the first STA works, where the unicast service indication information is used to indicate whether the Non-AP MLD associated with the first AP MLD has a downlink unicast service, and whether the Non-AP MLD associated with the second AP MLD has a downlink unicast service, where the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located; the processor is used to determine whether the Non-AP MLD has a downlink unicast service based on the received unicast service indication information.

[0064] In the eleventh aspect, the present application provides a communication device, specifically an AP MLD or an AP of an AP MLD i, including a processor and a transceiver. The processor is configured to support the AP MLD in performing the corresponding functions of the method of the fifth aspect. The transceiver is configured to support communication between the AP MLD and a non-access point multi-link device (also known as a site multi-link device), and to transmit information, frames, data packets, or instructions involved in the method to the site multi-link device. The AP MLD may also include a memory, coupled to the processor, that stores necessary program instructions and data for the AP MLD.

[0065] Specifically, the processor is used to generate AID allocation information, which carries an AID allocated for the Non-AP MLD. The AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is associated with the AP MLD. i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the set circle where the co-located AP MLD set is located; the transceiver is used to send the AID allocation information. The above AID allocation information is carried in the association response frame. It is understandable that the above AID allocation information can also be carried in other frames. AP i Any AP in the AP MLD.

[0066] Optionally, the transceiver is further configured to receive an association request frame, where the association request frame is used to request to establish a multi-link association with the AP MLD.

[0067] In a twelfth aspect, the present application provides a communication device, specifically a non-access point multi-link device (also referred to as a site multi-link device), comprising a processor and a transceiver. The processor is configured to support the site multi-link device in performing the corresponding functions of the method of the sixth aspect. The transceiver is configured to support communication between the site multi-link device and an AP MLD, and to receive information, frames, data packets, or instructions involved in the method from the AP MLD. The site multi-link device may also include a memory, coupled to the processor, that stores necessary program instructions and data for the site multi-link device.

[0068] Specifically, the transceiver is used to receive AID allocation information; the processor is used to parse the received AID allocation information to obtain the AID allocated for the Non-AP MLD carried in the AID allocation information, the AID is different from the AID of the Non-AP MLD associated with the target AP MLD, and the target AP MLD is associated with the AP i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP iAny AP MLD in the set circle where the co-located AP MLD set is located. The above AID allocation information is carried in the association response frame. It is understandable that the above AID allocation information can also be carried in other frames. i Any AP in the AP MLD.

[0069] Optionally, the processor is further configured to generate an association request frame; and the transceiver is further configured to send the association request frame, where the association request frame is used to request to establish a multi-link association with the AP MLD.

[0070] In a thirteenth aspect, the present application provides a chip or chip system, comprising an input / output interface and a processing circuit. The processing circuit is configured to generate unicast service indication information, the unicast service indication information being configured to indicate whether a non-AP MLD associated with a first AP MLD has downlink unicast service, and whether a non-AP MLD associated with a second AP MLD has downlink unicast service, where the second AP MLD is an AP MLD to which a non-transmitting AP belongs in a multi-BSSID set to which the first AP is located; and the input / output interface is configured to send the unicast service indication information on a first link, where the first link is a working link of the first AP.

[0071] In one possible design, the input-output interface is used to receive unicast service indication information on the first link, where the unicast service indication information is used to indicate whether a Non-AP MLD associated with the first AP MLD has a downlink unicast service, and whether a Non-AP MLD associated with a second AP MLD has a downlink unicast service, where the second AP MLD is an AP MLD to which a non-transmission AP belongs in a multi-BSSID set where the first AP is located; the processing circuit is used to determine whether the Non-AP MLD has a downlink unicast service based on the received unicast service indication information.

[0072] In a fourteenth aspect, the present application provides a chip or chip system, including an input / output interface and a processing circuit. The processing circuit is used to generate AID allocation information, wherein the AID allocation information carries an AID allocated for a Non-AP MLD, wherein the AID is different from the AID of the Non-AP MLD associated with the target AP MLD, and the target AP MLD is any AP MLD in the set of AP MLDs co-located with the reporting AP, or the target AP MLD is an AP MLD associated with the AP MLD. i Any AP MLD in the set circle where the co-located AP MLD set belongs; the input and output interface is used to send the association response frame.

[0073] In one possible design, the input / output interface is used to receive AID allocation information; the processing circuit is used to parse the received AID allocation information to obtain an AID allocated for the Non-AP MLD carried in the AID allocation information, where the AID is different from the AID of the Non-AP MLD associated with the target AP MLD, and the target AP MLD is any AP MLD in the set of AP MLDs co-located with the reporting AP, or the target AP MLD is an AP MLD associated with the AP MLD. i Any AP MLD in the set circle of co-located AP MLD sets.

[0074] In a fifteenth aspect, the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a computer, the computer executes the unicast service indication method applicable to multiple links described in the first aspect or the second aspect.

[0075] In a sixteenth aspect, the present application provides a computer-readable storage medium having instructions stored therein. When the instructions are executed on a computer, the computer executes the method for allocating an association identifier AID of a multi-link device as described in the fifth aspect or the sixth aspect.

[0076] In a seventeenth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the unicast service indication method applicable to multiple links as described in the first aspect or the second aspect.

[0077] In an eighteenth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method for allocating an association identifier (AID) of a multi-link device as described in the fifth aspect or the sixth aspect.

[0078] Implementation of the embodiments of the present application can help some APs or all APs in a partial AP MLD indicate whether the site multi-link device associated therewith has downlink unicast services, thereby assisting the site multi-link device to correctly receive downlink unicast services. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for describing the embodiments.

[0080] FIG1 is a schematic diagram of the structure of an AP MLD and a Non-AP MLD provided in an embodiment of the present application;

[0081] FIG2 is a schematic diagram of a frame format of a TIM element provided in an embodiment of the present application;

[0082] FIG3 is a schematic diagram of a frame format of a multi-BSSID element provided in an embodiment of the present application;

[0083] FIG4a is a schematic structural diagram of a communication system 100 provided in an embodiment of the present application;

[0084] FIG4 b is a schematic structural diagram of a communication system 200 provided in an embodiment of the present application;

[0085] FIG4c is a schematic structural diagram of a communication system 300 provided in an embodiment of the present application;

[0086] FIG5 is a schematic diagram of the architecture of multiple Multiple BSSID sets provided in an embodiment of the present application;

[0087] FIG6 is a schematic flow chart of a unicast service indication method applicable to multiple links provided in an embodiment of the present application;

[0088] FIG7 is a schematic diagram of a partial virtual bitmap field provided in an embodiment of the present application;

[0089] FIG8 is a schematic diagram of a partial frame format of a new element provided in an embodiment of the present application;

[0090] FIG9 is a schematic flow chart of a method for allocating AIDs for Non-AP MLD according to an embodiment of the present application;

[0091] FIG10a is a schematic diagram of an AP MLD set co-located with an AP provided in an embodiment of the present application;

[0092] FIG10 b is another schematic diagram of an AP MLD set co-located with an AP provided in an embodiment of the present application;

[0093] FIG10c is another schematic diagram of an AP MLD set co-located with an AP provided in an embodiment of the present application;

[0094] FIG11 is a schematic diagram of a frame format of an AID element provided in an embodiment of the present application;

[0095] FIG12 is another schematic flow chart of a unicast service indication method applicable to multiple links according to an embodiment of the present application;

[0096] FIG13 is a schematic structural diagram of a communication device 1 provided in an embodiment of the present application;

[0097] FIG14 is a schematic structural diagram of a communication device 2 provided in an embodiment of the present application;

[0098] FIG15 is a schematic structural diagram of a communication device 3 provided in an embodiment of the present application;

[0099] FIG16 is a schematic structural diagram of a communication device 4 provided in an embodiment of the present application;

[0100] FIG17 is a schematic structural diagram of a communication device 1000 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0101] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application.

[0102] In order to better understand the unicast service indication method and related apparatus applicable to multiple links disclosed in the embodiments of the present application, the relevant concepts of the embodiments of the present application are first described.

[0103] 1. Multi-link devices

[0104] The wireless communication system to which the embodiments of the present application are applicable may be a wireless local area network (WLAN) or a cellular network. The unicast service indication method may be implemented by a communication device in the wireless communication system or a chip or processor in the communication device. The communication device may be a wireless communication device that supports parallel transmission of multiple links, for example, a multi-link device (MLD) or a multi-band device. Compared to devices that only support single-link transmission, multi-link devices have higher transmission efficiency and higher throughput.

[0105] A multi-link device includes one or more affiliated stations (affiliated STAs), and an affiliated station is a logical station that can work on a link. Among them, the affiliated station can be an access point (AP) or a non-access point station (Non-AP STA). For the convenience of description, this application refers to a multi-link device whose affiliated station is an AP as a multi-link AP or a multi-link AP device or an AP multi-link device (AP MLD), and a multi-link device whose affiliated station is a Non-AP STA as a multi-link Non-AP or a multi-link Non-AP device or a Non-AP multi-link device (Non-AP multi-link device, Non-AP MLD). For the convenience of description, "a multi-link device includes affiliated stations" is also briefly described as "a multi-link device includes stations" in the embodiments of this application.

[0106] A multi-link device includes one or more affiliated STAs. In other words, a multi-link device can include multiple logical STAs. Each logical STA operates on a link, but multiple logical STAs can operate on the same link.

[0107] A multi-link device can implement wireless communications using the 802.11 family of protocols. For example, it can implement extremely high throughput (EHT) stations or 802.11be-based or 802.11be-compatible stations to communicate with other devices, which may or may not be multi-link devices.

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

[0109] Exemplarily, a multi-link device is a device with wireless communication capabilities. The device can be a complete device or a chip or processing system installed in the complete device. Devices installed with these chips or processing systems can implement the methods and functions of the embodiments of the present application under the control of these chips or processing systems. For example, the non-AP MLD in the embodiments of the present application has wireless transceiver capabilities, can support the 802.11 series of protocols, and can communicate with an AP MLD or other non-AP MLDs or single-link devices. For example, a STA MLD is any user communication device that allows a user to communicate with an AP and then with a WLAN. For example, the non-AP MLD can be a tablet computer, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), mobile phone, or other user devices that can be connected to the Internet, or an IoT node in the Internet of Things, or an in-vehicle communication device in the Internet of Vehicles. The non-AP MLD can also be a chip and processing system in these terminals.

[0110] The AP MLD in the embodiments of the present application is a device that provides services for non-AP MLDs and can support the 802.11 series of protocols. For example, the AP MLD can be a communication entity such as a communication server, router, switch, or bridge. Alternatively, the AP MLD can include various forms of macro base stations, micro base stations, and relay stations. Of course, the AP MLD can also be the chip and processing system in these various forms of devices, thereby implementing the methods and functions of the embodiments of the present application. In addition, multi-link devices can support high-speed and low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can also be applied to more scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air detection nodes), smart devices in smart homes (e.g., smart cameras, projectors, display screens, TVs, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (e.g., wearable devices such as AR and VR), smart devices in smart offices (e.g., printers, projectors, etc.), Internet of Vehicles devices in the Internet of Vehicles, and some infrastructure in daily life scenarios (e.g., vending machines, self-service navigation counters in supermarkets, self-service cash registers, self-service ordering machines, etc.). In the embodiments of the present application, there is no special restriction on the specific forms of Non-AP MLD and AP MLD, which are only illustrative. Among them, the 802.11 protocol can be a protocol that supports 802.11be or is compatible with 802.11be.

[0111] The frequency bands in which the multi-link device operates may include but are not limited to: sub 1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high frequency 60 GHz.

[0112] Exemplarily, the multi-link device in the embodiment of the present application can be a single-antenna device or a multi-antenna device. For example, the multi-link device in the embodiment of the present application can be a device with more than two antennas. The embodiment of the present application does not limit the number of antennas included in the multi-link device. Referring to Figure 1, Figure 1 is a structural diagram of an AP MLD and a Non-AP MLD provided in an embodiment of the present application. Figure 1 shows a structural diagram of an AP MLD with multiple antennas and a Non-AP MLD with a single antenna. The 802.11 standard focuses on the physical layer (PHY) and media access control (MAC) layer parts in the AP MLD and Non-AP MLD.

[0113] 2. Link identification

[0114] A link identifier represents a station operating on a link. That is, if there is more than one station on a link, more than one link identifier represents them. The link mentioned below sometimes also refers to the station operating on that link.

[0115] During data transmission, AP MLD and non-AP MLD can use link identifiers to identify a link or a station on a link. Before communication begins, AP MLD and non-AP MLD can negotiate or communicate the mapping between link identifiers and links or stations on a link. Therefore, data transmission eliminates the need to transmit large amounts of signaling information to identify links or stations on a link; simply carrying the link identifier suffices, reducing signaling overhead and improving transmission efficiency.

[0116] In one example, a management frame, such as a beacon frame, sent by an AP MLD when establishing a basic service set (BSS) carries an element that includes multiple link identification information fields. The link identification information field can indicate the correspondence between a link identifier and a station operating on the link corresponding to the link identifier. The link identification information field includes not only the link identifier but also one or more of the following information: a media access control (MAC) address, an operation set, and a channel number. One or more of the MAC address, operation set, and channel number can indicate a link. For an AP, the AP's MAC address is also the AP's BSSID (basic service set identifier). In another example, during the multi-link device association process, the AP MLD and the non-AP MLD negotiate multiple link identification information fields. Multi-link device association refers to an association between an AP MLD AP and a non-AP MLD STA. This association allows multiple STAs in the non-AP MLD to associate with multiple APs in the AP MLD, where each STA associates with one AP.

[0117] In subsequent communications, the AP MLD or Non-AP MLD will use the link identifier to represent a station in the Non-AP MLD. The link identifier can also represent one or more attributes of the station's MAC address, operating set, and channel number. The MAC address can be replaced with the association identifier of the AP MLD after association. Optionally, if multiple stations work on a link, the link identifier (a numerical ID) represents not only the operating set and channel number of the link, but also the station identifier working on the link, such as the station's MAC address or the station's association identifier (AID).

[0118] 3. Business indication bitmap element

[0119] Both the traffic indication map (TIM) beacon frame and the delivery traffic indication map (DTIM) beacon frame carry a traffic indication map (TIM) element. Referring to FIG. 2 , FIG. 2 is a schematic diagram of a frame format of a TIM element provided in an embodiment of the present application. As shown in FIG. 2 , the frame format of the TIM element field includes:

[0120] Element identifier (ID) field: used to identify the element shown in FIG2 as a TIM element.

[0121] Length field: used to indicate the length of the TIM element. The total length after counting this field is the total length of the DTIM count field, DTIM period field, bitmap control field and part of the virtual bitmap field, in bytes.

[0122] The DTIM Count field indicates how many TIM beacon frames remain between the current beacon frame carrying the TIM element and the arrival of the next DTIM beacon frame. This DTIM Count field is a variable count value. When the DTIM Count field is 0, the current beacon frame is a DTIM beacon frame. When the DTIM Technology field is non-zero or non-zero, the current beacon frame is a TIM beacon frame.

[0123] The DTIM period field indicates the duration of the DTIM beacon frame, i.e., the arrival interval, which is measured in TIM beacon frame periods. For example, if the DTIM period is set to 1, the DTIM count in each TIM element field is equal to 0, meaning that every beacon frame is a DTIM beacon frame.

[0124] Bitmap control field: As shown in Figure 2, bit 0 in the Bitmap control field indicates whether the access point (AP) sends multicast data services after sending a DTIM beacon frame. In other words, if bit 0 in the Bitmap control field in the DTIM beacon frame indicates whether the AP buffers multicast services, and the multicast services are not sent using a multicast AID, bits 1 to 7 in the Bitmap control field indicate the offset of the partial virtual bitmap, which is expressed in bytes (i.e., 8 bits).

[0125] Partial Virtual Bitmap: Each bit in the Partial Virtual Bitmap field corresponds to an association identifier (AID), indicating whether the station corresponding to the AID has unicast services. Alternatively, each bit in the Partial Virtual Bitmap field corresponds to a multicast AID, indicating whether a group of stations corresponding to the multicast AID has downlink services. The Partial Virtual Bitmap field is a portion of the bits in the Traffic Indication Virtual Bitmap field. The Traffic Indication Virtual Bitmap field is 251 bytes long and indicates whether stations corresponding to AIDs 0 to 2007 have downlink services.

[0126] Among them, the element ID field, length field, DTIM count field, DTIM period field and bitmap control field each occupy 1 byte.

[0127] 4. Multiple BSSID set

[0128] The Multiple Basic Service Set Identifier (MSSID) set (also called the Multiple BSSID set) can be understood as a set of cooperating APs. All cooperating APs use the same operation set, channel number, and antenna interface. In this Multiple BSSID set, there is only one AP with a Transmitted BSSID, and the other APs are all APs with a Non-transmitted BSSID. The information of the Multiple BSSID set (that is, the Multiple BSSID element) is carried in the beacon frame or probe response frame or neighbor report sent by the Transmitted BSSID AP. The BSSID information of the Non-transmitted BSSID AP is derived by the station through the above-mentioned beacon frame or probe response frame, or the Multiple BSSID element in the neighbor report. The BSSID of the non-transmitted BSSID AP is calculated using the BSSID of the transmitting AP and the BSSID Index field in the Multiple BSSID-Index element of its non-transmitted BSSID profile. For details, see Draft 802.11REVmd_D3.0.

[0129] The multi-BSSID set can also be understood as consisting of multiple APs. Each AP manages a BSS, and different APs can have different SSIDs and permissions, such as security mechanisms or transmission opportunities.

[0130] In a multiple BSSID set, only APs with a Transmitted BSSID can send beacon frames and Probe Response frames. APs with a Non-Transmitted BSSID do not send beacon frames. Therefore, if a STA sends a Probe Request frame to an AP with a Non-Transmitted BSSID in the multiple BSSID set, the AP with a Transmitted BSSID in the multiple BSSID set will respond by sending a Probe Response frame.

[0131] Among the multiple APs in the multi-BSSID set, the BSSID of one AP is configured as a transmitted BSSID, and the AP with the transmitted BSSID can be called a transmitted AP; the BSSIDs of the other APs are configured as non-transmitted BSSIDs, and the AP with the non-transmitted BSSID can be called a non-transmitted AP.

[0132] The beacon frame sent by the transmitting AP may include a multi-BSSID element. The frame format of the multi-BSSID element is shown in Figure 3, which is a schematic diagram of the frame format of a multi-BSSID element provided in an embodiment of the present application. The multi-BSSID element includes an element ID field, a length field, a maximum BSSID indication field, and an optional sub-element field. The maximum BSSID indication field is used to indicate the maximum number N of BSSIDs included in the multi-BSSID set, and the optional sub-element field includes information about the BSSID of the AP of the non-transmitted BSSID.

[0133] The maximum number of APs allowed in a multi-BSSID set is 2 n , n is the value indicated by the MaxBSSID Indicator field in the multi-BSSID element shown in Figure 3, N = 2 n Therefore, the service indication virtual bitmap field bit 1 to bit 2 can be n -1 is assigned to the APs of the non-transmitting BSSIDs in the multi-BSSID set to indicate that the NonTxBSS ID (identifier) ​​is 1 to 2. n -1 indicates whether the AP with the non-transmitting BSSID has multicast services. The value of NonTxBSS ID is equal to the value of the BSSID Index field in the Multiple BSSID-Index element of the Non-transmitted BSSID profile in the Multiple BSSID element. The Non-transmitted BSSID profile is in the optional sub-element field.

[0134] Although the embodiments of the present application are mainly described by taking a network deploying IEEE 802.11 as an example, it will be readily understood by those skilled in the art that the various aspects involved in the present application can be extended to other networks that adopt various standards or protocols, for example, BLUETOOTH, high performance wireless LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, mainly used in Europe) and wide area network (WAN), wireless local area network (WLAN), personal area network (PAN) or other networks now known or developed in the future. Therefore, regardless of the coverage range and wireless access protocol used, the various aspects provided in the present application can be applied to any suitable wireless network.

[0135] Referring to Figure 4a, Figure 4a is a schematic diagram of the structure of a communication system 100 provided in an embodiment of the present application. Figure 4a uses a wireless local area network as an example to introduce a communication system 100 applied in an embodiment of the present application. The communication system 100 includes: a station 101 and a station 102. Station 101 can communicate with station 102 using multiple links, thereby achieving the effect of improving throughput. Station 101 can be a multi-link device, and station 102 can be a single-link device or a multi-link device. In one scenario, station 101 is an AP MLD, and station 102 is a non-AP MLD or a station (e.g., a single-link station). In another scenario, station 101 is a non-AP MLD, and station 102 is an AP (e.g., a single-link AP) or an AP MLD. In yet another scenario, station 101 is an AP MLD, and station 102 is an AP MLD or an AP; in yet another scenario, station 101 is a non-AP MLD, and station 102 is a non-AP MLD or a STA (e.g., a single-link station). Of course, the wireless local area network may also include other devices. The number and types of devices shown in FIG4a are only exemplary.

[0136] See Figure 4b, which is a schematic diagram of the structure of a communication system 200 provided in an embodiment of the present application. See Figure 4c, which is a schematic diagram of the structure of a communication system 300 provided in an embodiment of the present application. Figures 4b and 4c respectively illustrate the structures of communication system 200 and communication system 300. Communication system 200 and communication system 300 are exemplified by a multi-link device communicating with other devices via multiple links in a wireless local area network.

[0137] Specifically, FIG4b shows a scenario of communication between an AP MLD and a Non-AP MLD. The AP MLD includes subordinate AP1 and AP2, and the Non-AP MLD includes subordinate STA1 and STA2. The AP MLD and the Non-AP MLD communicate using link 1 and link 2 in parallel.

[0138] Figure 4c shows a scenario where AP MLD 601 communicates with non-AP MLD 602, non-AP MLD 603, and STA 604. AP MLD 601 includes subordinate APs 601-1 to 601-3. Non-AP MLD 602 ​​includes three subordinate STAs 602-1, STA 602-2, and STA 602-3. Non-AP MLD 603 includes two subordinate STAs 603-1 and STA 603-2. STA 604-1 and STA 604 are single-link devices. AP MLD 601 can communicate with non-AP MLD 602 ​​using links 1, 2, and 3, respectively; communicate with non-AP MLD 603 using links 2 and 3; and communicate with STA 604 using link 1. In one example, STA 604 operates in the 2.4 GHz band; in non-AP MLD 603, STA 603-1 operates in the 5 GHz band, and STA 603-2 operates in the 6 GHz band; in non-AP MLD 602, STA 602-1 operates in the 2.4 GHz band, STA 602-2 operates in the 5 GHz band, and STA 602-3 operates in the 6 GHz band. AP 601-1 in AP MLD 601, which operates in the 2.4 GHz band, can transmit uplink or downlink data to STA 604 and STA 602-1 in non-AP MLD 602 ​​over link 1. AP601-2, operating in the 5 GHz band in AP MLD601, can transmit uplink or downlink data with STA603-1, operating in the 5 GHz band in non-AP MLD603, over link 2. It can also transmit uplink or downlink data with STA602-2, operating in the 5 GHz band in non-AP MLD602, over link 2. AP601-3, operating in the 6 GHz band in AP MLD601, can transmit uplink or downlink data with STA602-3, operating in the 6 GHz band in non-AP MLD602, over link 3. It can also transmit uplink or downlink data with STA603-2, operating in the non-AP MLD, over link 3.

[0139] It is understandable that Figure 4b only shows that the AP MLD supports two frequency bands, and Figure 4c only uses the example of AP MLD601 supporting three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), each frequency band corresponding to a link, and AP MLD601 being able to operate on one or more links among link 1, link 2, or link 3. On the AP side or STA side, the link here can also be understood as a station operating on that link. In actual applications, the AP MLD and non-AP MLD can also support more or fewer frequency bands, that is, the AP MLD and non-AP MLD can operate on more or fewer links, but this embodiment of the application is not limited to this.

[0140] 5 , which is a schematic diagram of the architecture of multiple Multiple BSSID sets provided by an embodiment of the present application. In other words, the AP MLDs shown in FIG5 are collocated AP MLD sets.

[0141] BSSID-1x, BSSID-1y, BSSID-2x, BSSID-2y, BSSID-2z, BSSID-4x, BSSID-4y, BSSID-4z, BSSID-3, and BSSID-5 are MAC address identifiers used to identify the corresponding APs. An AP whose MAC address ends in x is a Transmitted BSSID AP, an AP whose MAC address ends in y or z is a Non-Transmitted BSSID AP, and an AP whose MAC address ends in only numbers is a Standard AP, which is not part of a multi-BSSID set. For example, the Transmitted BSSID AP in Multiple BSSID set 1 is AP1x with a MAC address identifier of BSSID_1x, and the Non-Transmitted BSSID AP in Multiple BSSID set 1 is AP1y with a MAC address identifier of BSSID_1y; the Transmitted BSSID AP in Multiple BSSID set 2 is AP2x with a MAC address identifier of BSSID_2x, and the Non-Transmitted BSSID APs in Multiple BSSID set 2 include AP2y with an address identifier of BSSID_2y and AP2z with a MAC address identifier of BSSID_2z.

[0142] The MLD set of APs co-located with a reporting AP includes the following APs: A reporting AP is an AP that sends management frames that carry information about multiple APs, such as beacon frames and probe response frames. Reporting APs include transmitting APs and normal APs in the BSSID set. The MLD set of APs co-located with a reporting AP includes the following APs:

[0143] (1) All APs that belong to the same AP MLD as the reporting AP, or all APs in the same AP MLD as the reporting AP.

[0144] (2) All APs in the AP MLD of the non-transmitting APs in the same multi-BSSID set as the reporting AP (or transmitting AP); or, all APs in the AP MLD of the non-transmitting APs in the multi-BSSID set where the reporting AP (or transmitting AP) is located.

[0145] (3) All APs in an AP MLD that meet the following two conditions: 1) At least one AP in the AP MLD is in the same multi-BSSID set as an AP in the AP MLD where the reporting AP is located; and 2) No AP in the AP MLD is operating on the same link as the reporting AP.

[0146] Optionally, in one implementation, an AP MLD includes only one AP.

[0147] Optionally, the reporting AP can be an ordinary AP in the AP MLD (taking Figure 5 as an example, such as AP3 with MAC address identifier BSSID_3 and AP5 with MAC address identifier BSSID_5) or a transmission AP in a multi-BSSID set, which can send the unicast service indication information described in this application.

[0148] For example, using AP1x in Figure 5 as the reporting AP, the AP MLD set co-located with AP1x includes the following APs:

[0149] (1) All APs in the same AP MLD1 as AP1x, namely AP1x, AP2y, and AP3;

[0150] (2) All APs in AP MLD3 where the non-transmitting AP (i.e., AP1y) in the same multi-BSSID set 1 as AP1x are located are: AP1y, AP2z, and AP4y;

[0151] (3) In FIG5 , the AP MLD that satisfies the above conditions 1) and 2) is AP MLD2, which includes AP2x and AP4x. AP2x in AP MLD2 and AP2y in AP MLD1 are in the same multi-BSSID set 2, and no AP in AP MLD2 is in the same link with AP1x.

[0152] Because in a multi-BSSID set, only APs with Transmitted BSSIDs can send beacon frames and probe response frames, while APs with Non-transmitted BSSIDs do not send beacon frames. Therefore, if all APs in a particular AP MLD are Non-transmitted APs (for example, AP MLD3 in Figure 5), and because the TIM element is carried in beacon frames, this AP MLD cannot indicate whether the Non-AP MLD associated with it has downlink unicast services. Furthermore, for example, in the case of AP MLD1 in Figure 5, AP2y operating on Link 2 is a Non-transmitting AP. Therefore, the Non-AP MLD operating on Link 2 cannot receive downlink unicast service notifications sent by its associated AP MLD1.

[0153] Therefore, an embodiment of the present application provides a multi-link unicast service indication method. In this method, the signaling sent by the reporting AP carries the downlink unicast service indication of the AP MLD to which the non-transmitting AP belongs. This helps the AP MLD to which the non-transmitting AP belongs indicate whether its associated non-AP MLD has downlink unicast services. The technical solution provided by this application will be described in detail below with reference to more figures.

[0154] One or more APs in an AP MLD need to send buffer unit (BU) indication information to the associated non-AP MLD. One bit in the BU indication information corresponds to the AID of a non-AP MLD. If a bit in the BU indication information is set to "1", it indicates that the AP MLD has downlink unicast services for the non-AP MLD identified by the AID corresponding to the bit. Conversely, if a bit in the BU indication information is set to "0", it indicates that the AP MLD does not have downlink unicast services for the non-AP MLD identified by the AID corresponding to the bit.

[0155] Multi-link association establishment:

[0156] During the multi-link association establishment process, a site in the site MLD and an AP in the AP MLD exchange association request / association response frames to establish a multi-link association. This means that multiple sites in the site MLD are associated with multiple APs in the AP MLD. In the association response frames sent by the APs in the AP MLD, each site MLD is assigned an AID, meaning that multiple sites in the site MLD share the same AID. Both the AP MLD and the site MLD contain a unique MLD MAC address, which is used as an index for the data source and destination at the MAC layer, such as IP. This means that packets sent by each AP in the AP MLD to the same site MLD are shared.

[0157] Example 1

[0158] Refer to Figure 6, which is a schematic flow chart of a unicast service indication method applicable to multiple links provided in an embodiment of the present application. The unicast service indication method applicable to multiple links is described by taking its implementation in a communication system composed of AP MLD and Non-AP MLD as an example. Among them, AP MLD includes one or more APs, and the first AP is any reporting AP in the AP MLD. Optionally, the reporting AP is not a non-transmitting AP in a multi-BSSID set. Non-AP MLD includes one or more STAs, and the first STA is any STA in the Non-AP MLD. As described above, AP MLD can establish a multi-link association with Non-AP MLD, and the first AP and the first STA both work on the first link. As shown in Figure 6, the unicast service indication method applicable to multiple links includes but is not limited to the following steps:

[0159] S101, the first AP of the first AP MLD generates unicast service indication information, where the unicast service indication information is used to indicate whether the Non-AP MLD associated with the first AP MLD has a downlink unicast service, and whether the Non-AP MLD associated with the second AP MLD has a downlink unicast service. The second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located.

[0160] The unicast service indication information may be referred to as a unicast service indication field, a unicast service indication, or a buffer unit (BU) indication, which is not limited in the embodiment of the present application. The unicast service indication information may be carried in a TIM element, for example, as shown in the TIM element field of FIG2 , and the unicast service indication information may be carried in a partial virtual bitmap field.

[0161] Specifically, the first AP is a reporting AP in a multi-BSSID set and belongs to a first AP MLD. Therefore, the first AP of the first AP MLD can generate unicast service indication information. This unicast service indication information can include two parts of indication information. One part of the indication information is the first AP MLD's own unicast service indication information, which is used to indicate whether the non-AP MLD associated with the first AP MLD has downlink unicast services. The other part of the indication information is the unicast service indication information of the AP MLD (i.e., the second AP MLD) to which the non-transmitting AP in the multi-BSSID set to which the first AP belongs belongs, which is used to indicate whether the non-AP MLD associated with the second AP MLD on the first link operating with the first AP has downlink unicast services. In other words, the unicast service indication information carries not only the unicast service indication of the reporting AP (the first AP) itself, but also the unicast service indications of the AP MLDs to which other non-transmitting APs in the multi-BSSID set to which the reporting AP belongs. It should be understood that the reference herein to unicast service indication information including two parts of indication information does not mean that the two parts of indication information are in different fields; the two parts of indication information can be in the same field.

[0162] Optionally, the Non-AP MLD associated with the MLD where the reporting AP is located has the following two possibilities: 1) all Non-AP MLDs that establish multi-link associations with the MLD where the reporting AP is located, where the Non-AP MLD can be associated with some APs in the MLD where the reporting AP is located, or can be associated with all APs; or, 2) the Non-AP MLD that is associated with the reporting AP of the MLD where the reporting AP is located, where the Non-AP MLD can be associated with some APs in the MLD where the reporting AP is located, or can be associated with all APs, but the some APs or all APs must include the reporting AP.

[0163] Optionally, the Non-AP MLD associated with the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the reporting AP is located also has the following two possibilities: 1) it can indicate all Non-AP MLDs that establish multi-link associations with the AP MLD to which the non-transmission AP belongs, where the Non-AP MLD can be associated with some APs in the AP MLD to which the non-transmission AP belongs, or can be associated with all APs; or, 2) it can indicate the Non-AP MLD that is associated with the non-transmission AP of the AP MLD to which the non-transmission AP belongs, where the Non-AP MLD can be associated with some APs in the AP MLD to which the non-transmission AP belongs, or can be associated with all APs, but the some APs or all APs must include the non-transmission AP.

[0164] For example, in Figure 5 , where AP1x, whose MAC address is BSSID_1x, is the reporting AP, that is, AP1x is the first AP. AP MLD1 in Figure 5 is the first AP MLD, and the link on which AP1x operates is Link 1. The unicast service indication information generated by AP1x not only includes unicast service indications for the non-AP MLDs associated with its MLD, but also has the following two possibilities: 1) it may indicate whether all non-AP MLDs associated with AP MLD1 have downlink unicast services. These non-AP MLDs may be associated with some or all APs in AP MLD1. Alternatively, 2) it may indicate whether non-AP MLDs associated with AP1x in AP MLD1 have downlink unicast services. These non-AP MLDs may be associated with some or all APs in AP MLD1. However, these partial or all APs must include AP1x.

[0165] The unicast service indication information generated by AP1x also includes unicast service indications from AP MLD3, the non-transmitting AP (i.e., AP1y) in multi-BSSID set 1 to which AP1x belongs, for its associated Non-AP MLDs. This information can be either: 1) indicating whether all Non-AP MLDs associated with AP MLD3 have downlink unicast services; or 2) indicating whether the Non-AP MLDs associated with AP1y in the same multi-BSSID set as AP1x have downlink unicast services. For example, Non-AP MLD1 is associated with AP MLD3's AP1y on link 1 and AP2z on link 2; Non-AP MLD2 is associated with AP MLD3's AP1y on link 1, AP2z on link 2, and AP4y on link 4; and Non-AP MLD3 is associated with AP MLD3's AP2z on link 2 and AP4y on link 4. In the first embodiment, AP MLD3's unicast service indication for its associated Non-AP MLD includes whether Non-AP MLD1, Non-AP MLD2, and Non-AP MLD3 have downlink unicast services. In the second embodiment, AP MLD3's unicast service indication for its associated Non-AP MLD includes whether Non-AP MLD1 and Non-AP MLD2 have downlink unicast services.

[0166] For another example, taking AP2x with a MAC address identifier of BSSID_2x as the reporting AP, that is, AP2x as the first AP, AP MLD2 in Figure 5 is the first AP MLD, and the link on which AP2x operates is Link 2. The unicast service indication information generated by AP2x includes not only the unicast service indication from AP2x to the Non-AP MLD associated with its MLD, but also the unicast service indication from AP MLD1 to which AP2y belongs to the Non-AP MLD associated with it, and the unicast service indication from AP MLD3 to which AP2z belongs to the Non-AP MLD associated with it.

[0167] As an optional embodiment, the reporting AP is not limited to the APs in the AP MLD; that is, the reporting AP can be a single-link device. The unicast service indication information generated by the reporting AP, in addition to carrying the reporting AP's own unicast service indication for its associated STAs, indicates whether the STA associated with the reporting AP has downlink unicast services. It can also carry the unicast service indications of the AP MLDs of other non-transmitting APs in the multi-BSSID set of the link, indicating whether the AP MLD has downlink unicast services for its associated non-AP MLD.

[0168] S102: A first AP of a first AP MLD sends the unicast service indication information on a first link, where the first link is a working link of the first AP.

[0169] In an embodiment of the present application, the above-mentioned unicast service indication information can be carried in a management frame, such as a beacon frame, a TIM frame, etc.; or, the unicast service indication information can also be carried in other frames such as a data frame or a control frame.

[0170] S103: The first STA of the Non-AP MLD receives the unicast service indication information on its first working link.

[0171] The first STA may be a station managed by the first AP or a surrounding station. The stations surrounding the first AP include stations managed by the first AP and unassociated stations. The following uses stations managed by the AP as an example to illustrate the unicast service indication method described in the embodiment of the present application. Optionally, the first STA may be any station in a Non-AP MLD and may be informed of whether the Non-AP MLD to which it belongs has downlink unicast services. Optionally, both the first STA and the first AP operate on the first link.

[0172] S104: The first STA of the Non-AP MLD determines whether the Non-AP MLD has a downlink unicast service according to the unicast service indication information.

[0173] Specifically, the first STA of the Non-AP MLD can parse the received unicast service indication information to determine whether the Non-AP MLD has downlink unicast services. If the unicast service indication information indicates that the Non-AP MLD has downlink unicast services to receive, a station in the Non-AP MLD can wake up from a dormant state and become active. It then sends a PS-Poll (power-saving polling) frame to the AP associated with this station, notifying the AP MLD to which the AP belongs that it is awake and can begin receiving downlink unicast services. After receiving the PS-Poll frame, the AP can respond with an acknowledgment frame and then send downlink unicast services to the STA. Alternatively, after receiving the PS-Poll frame, it can directly send downlink unicast services to the STA. If the unicast service indication information indicates that the Non-AP MLD has no downlink unicast services, the station in the Non-AP MLD can continue to sleep or transition from an active state to a dormant state.

[0174] As you can understand, in the 802.11 protocol, STAs typically have two operating modes: non-energy-saving mode and energy-saving mode. When operating in non-energy-saving mode, the STA is in an active state (also called an awake state) regardless of whether it is transmitting data. When operating in energy-saving mode, the STA can be in an active state when transmitting data with the AP; when not transmitting data with the AP, the STA can be in a doze state to save power. Whether the STA is in energy-saving mode can be determined by sending a frame to the AP with the energy-saving bit in the frame control field of the MAC header of the frame set to 1 to inform the AP that the STA is in energy-saving mode, or setting the energy-saving bit in the frame control field of the MAC header of the frame to 0 to inform the AP that the STA is in non-energy-saving mode. Corresponding to Non-AP MLD (or station MLD), each station in the Non-AP MLD sets a energy-saving bit.

[0175] As can be seen, in this embodiment of the present application, the unicast service indication information sent by the first AP (i.e., the reporting AP) in the AP MLD not only indicates whether the non-AP MLD associated with the first AP MLD has downlink unicast services, but also helps the second AP MLD indicate whether the non-AP MLD associated with the second AP MLD has downlink unicast services. The second AP MLD is the AP MLD to which the non-transmitting APs in the multi-BSSID set to which the first AP belongs. This resolves the issue where some or all APs in the AP MLD are unable to indicate whether their associated non-AP MLDs have downlink unicast services (notably, non-transmitting APs in the multi-BSSID set cannot transmit beacon frames or probe response frames, resulting in an inability to send downlink unicast service indications). This allows the non-AP MLDs associated with these APs to normally receive downlink unicast services. Since 802.11be may have all APs in an AP MLD as non-transmitting APs, the solution provided in this embodiment of the present application resolves the issue where an AP MLD consisting entirely of non-transmitting APs cannot send unicast service indications, thereby increasing the integrity and diversity of downlink service indications.

[0176] As an optional embodiment, before step S101 in FIG. 6 , the following steps may be further included: S105: The first AP of the first AP MLD generates AID allocation information, which carries the AID allocated for the non-AP MLD. The AID is different from the AID of the non-AP MLD associated with the second AP MLD. S106: The first AP of the first AP MLD sends the AID allocation information. Accordingly, the first STA of the non-AP MLD receives the AID allocation information. S107: The first STA of the non-AP MLD parses the received AID allocation information to obtain the AID allocated for the non-AP MLD carried in the AID allocation information. The AID allocation information may be carried in an association response frame. The AID space (or set of AIDs to be allocated) used by the first AP MLD to allocate AIDs to its associated non-AP MLD and the AID space (or set of AIDs to be allocated) used by the second AP MLD to allocate AIDs to its associated non-AP MLD are the same. Optionally, the AP MLD to which the non-transmission APs in the multi-BSSID set where the first AP is located belongs includes one or more AP MLDs.

[0177] Optionally, before step S105, the method further includes: the first STA of the Non-AP MLD sends an association request frame to the first AP of the first AP MLD, wherein the association request frame is used to request to establish a multi-link association with the first AP MLD. Accordingly, the first AP of the first AP MLD receives the association request frame.

[0178] Optionally, steps S105 to S106 may also be performed by the second AP in the first AP MLD, and step S107 may also be performed by the second STA of the Non-AP MLD. Specifically, the second AP of the first AP MLD generates AID allocation information, which carries the AID allocated for the Non-AP MLD. The AID is different from the AID of the Non-AP MLD associated with the second AP MLD. The second AP of the first AP MLD sends the AID allocation information. Correspondingly, the second STA of the Non-AP MLD receives the AID allocation information. The second STA of the Non-AP MLD parses the received AID allocation information to obtain the AID allocated for the Non-AP MLD carried in the AID allocation information. The second AP is any AP in the first AP MLD, and the second STA is any STA in the Non-AP MLD.

[0179] It can be seen that when allocating AIDs, making the AID of the Non-AP MLD associated with the first AP MLD different from the AID of the Non-AP MLD associated with the second AP MLD can avoid AID ambiguity when indicating unicast services of the Non-AP MLD.

[0180] The above content introduces the unicast service indication method applicable to multiple links provided in the embodiment of the present application. The specific implementation method of the above unicast service indication information will be described below in conjunction with the unicast service indication method shown in Figure 6.

[0181] (a) In the first implementation, one bit of the unicast service indication information corresponds to a non-AP MLD. The value of each bit indicates whether the corresponding non-AP MLD has downlink unicast service. Alternatively, each bit indicates whether the corresponding non-AP MLD has downlink unicast service. The non-AP MLDs here refer to the non-AP MLD associated with the first AP MLD and the non-AP MLD associated with the second AP MLD.

[0182] (b) In the second implementation, the unicast service indication information is carried in the partial virtual bitmap field of the TIM element. Referring to FIG. 7 , FIG. 7 is a schematic diagram of a partial virtual bitmap field provided in an embodiment of the present application. FIG. 7 illustrates the individual bits of the partial virtual bitmap field in FIG. 2 . Taking the partial virtual bitmap field as an example, which is 251 bytes, each byte includes 8 bits. As shown in FIG. 7 , byte 0 includes bits 0 to 7, byte 1 includes bits 8 to 15, and so on. Byte 250 includes bits 2000 to 2007. Each bit of the unicast service indication information corresponds to an AID of a Non-AP MLD. Each bit of the unicast service indication information is used to indicate whether the Non-AP MLD identified by the AID corresponding to the bit has a downlink unicast service. It is understood that the Non-AP MLD here refers to the Non-AP MLD associated with the first AP MLD and the Non-AP MLD associated with the second AP MLD. Because each bit in the partial virtual bitmap field of the TIM element corresponds to an AID, an AID must also be assigned to the non-AP MLD. Furthermore, because the AID space (or set of AIDs to be assigned) used by the first AP MLD to assign AIDs to its associated non-AP MLDs and the AID space (or set of AIDs to be assigned) used by the second AP MLD to assign AIDs to its associated non-AP MLDs are the same, the association identifier AID corresponding to each bit of the unicast service indication information must be unique, i.e., different.

[0183] Accordingly, steps S101 to S104 in the above-mentioned Figure 6 can be: the first AP of the first AP MLD generates a TIM element, where the TIM element includes unicast service indication information, where the unicast service information is used to indicate whether the Non-AP MLD associated with the first AP MLD has a downlink unicast service, and whether the Non-AP MLD associated with the second AP MLD has a downlink unicast service, where the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located; the first AP of the first AP MLD sends the TIM element on the first link, where the first link is the working link of the first AP; the first STA of the Non-AP MLD receives the TIM element on the first link on which it works; the first STA of the Non-AP MLD determines, based on the TIM element, whether the Non-AP MLD has a downlink unicast service.

[0184] The TIM element may be carried in a beacon frame or in other management frames, such as a TIM frame.

[0185] Optionally, the beacon frame carrying the TIM element may also include a special field, wherein for each Non-AP MLD that receives downlink unicast services (whether there is downlink unicast service is indicated by the above-mentioned TIM element), there is a corresponding special field. The special field can be a multi-link identification bitmap field or multiple link identification information fields, and the multi-link bitmap field or multiple link information fields are used to indicate one or more links that receive downlink services. One bit of the above-mentioned multi-link identification bitmap field can correspond to one link. When the value of one or more bits is a first value, such as 1, it indicates that there is downlink service on the one or more links corresponding to the one or more bits; when the value of one or more bits is a second value, such as 0, it indicates that there is no downlink service on the one or more links corresponding to the one or more bits. The above-mentioned multiple link identification information fields carry identification information for distinguishing different links. It can be understood that in the TIM element, one bit is still used to indicate whether a Non-AP MLD has downlink unicast service.

[0186] Optionally, the special field may also be a traffic identifier (TID) bitmap field, which is used to indicate that the received downlink unicast service corresponds to one or more TIDs. Based on the TID to Link mapping negotiated between the Non-AP MLD and the AP MLD, the Non-AP MLD knows which link the station should use to receive the downlink unicast service notification.

[0187] It can be seen that this implementation method indicates whether the Non-AP MLD associated with the MLD where the reporting AP is located has a downlink unicast service and whether the Non-AP MLD associated with the second AP MLD has a downlink unicast service through some bits in the partial virtual bit map field in the beacon frame. The frame format of the TIM element can be kept unchanged, and one AP MLD can help another AP MLD indicate whether the Non-AP MLD associated with the other AP MLD has a downlink unicast service, thereby improving the flexibility of downlink unicast service notification.

[0188] (c) Because one bit in the virtual bitmap field of some of the TIM elements can indicate whether a Non-AP MLD has downlink unicast services, if some Non-AP MLDs associated with different AP MLDs in the same co-located AP MLD set have the same AID, upon receiving a beacon frame, these Non-AP MLDs cannot determine to which STA or Non-AP MLD the downlink unicast service indication and / or link bitmap indication / TID bitmap indication carried in the beacon frame belongs. For example, using Figure 5 above, if the reporting AP is AP1x, and Non-AP MLD 1 is associated with AP1x and AP2y of AP MLD 1 where AP1x is located, and the link on which AP1x operates is link 1, then the non-transmitting AP on link 1 is AP1y. If Non-AP MLD 2 is associated with AP1y, AP2z, and 4y in AP MLD 3 where AP1y is located, and the AIDs of Non-AP MLD 1 and Non-AP MLD 2 are the same, then if the downlink unicast service indication for the Non-AP MLD in the TIM element sent by reporting AP1x is 1, it only indicates that at least one of Non-AP MLD 1 and Non-AP MLD 2 has downlink unicast services. It is impossible to determine which Non-AP MLD has downlink unicast services.

[0189] Therefore, in the third implementation, the unicast service indication information is indicated according to the AP MLD. Specifically, the second AP MLD co-located with the reporting AP corresponds to a separate TIM block, such as a partial virtual bitmap field. These TIM blocks can form a new element. This new element can carry the unicast service indication information. The new element includes at least a TIM block corresponding to the second AP MLD (the TIM block is used to indicate whether the non-AP MLD associated with the second AP MLD has a downlink unicast service). See Figure 8, which is a schematic diagram of a partial frame format of a new element provided in an embodiment of the present application. As shown in Figure 8, (ID), such as MLD ID, or MLD MAC address, is used to indicate which AP MLD is used to indicate whether its associated non-AP MLD has a downlink unicast service. In each TIM block, one bit can still be used to indicate whether a non-AP MLD has a downlink unicast service. Each bit in the TIM block can correspond to an AID, so an AID needs to be assigned to each non-AP MLD.

[0190] In another implementation, a separate TIM block corresponding to the second AP MLD can also be a TIM element with a structure consistent with the existing TIM element. In this case, the TIM element does not include the identifier of the second AP MLD. The TIM element for the second AP MLD can be located in the nontransmitted profile corresponding to the non-transmitting BSSID in the Multiple BSSID element in the management frame body, where the AP corresponding to the non-transmitting BSSID belongs to the second AP MLD and is in the same multiple BSSID set as the reporting AP mentioned in the previous paragraph.

[0191] Here, for the third implementation described above, the AIDs of all non-AP MLDs associated with the same AP MLD should be unique, that is, different, to avoid AID ambiguity. It is understood that the identifiers of one or more AP MLDs in the new element sent by the reporting AP should be unique, that is, different. Alternatively, the identifiers of all AP MLDs within the set of AP MLDs co-located with the reporting AP should also be unique, that is, different. In other words, the AID space used by the first AP MLD to assign AIDs to its associated non-AP MLDs and the AID space used by the second AP MLD to assign AIDs to its associated non-AP MLDs are independent. That is, the AID assigned by the first AP MLD to a non-AP MLD associated with it can be the same as the AID assigned by the second AP MLD to its associated non-AP MLD. For example, in Figure 5, if AP1x is the reporting AP, AP MLD1 is the first AP MLD. Assuming that Non-AP MLD1 is associated with AP MLD1, and Non-AP MLD2 is associated with AP MLD3 (one of the second AP MLDs), the AID assigned by AP MLD1 to Non-AP MLD1 can be the same as the AID assigned by AP MLD3 to Non-AP MLD2. It is understood that the "AID space" mentioned in this application can refer to the set of AIDs to be allocated.

[0192] Optionally, a link bitmap indication or a TID bitmap indication may also be carried in each TIM block. That is, each TIM block may include a special field, which may be a multi-link identification bitmap field or a multiple link identification information field, or a TID bitmap field.

[0193] Optionally, the new element may be carried in a beacon frame or in other management frames, such as a TIM frame.

[0194] It can be seen that in the TIM indication, this implementation can avoid ambiguity in the AIDs of Non-AP MLDs associated with different AP MLDs by distinguishing services of different AP MLDs and using the AP MLD ID as the index of the TIM block.

[0195] In order to indicate whether the Non-AP MLD associated with the first AP (i.e., the reporting AP) has downlink unicast services and whether the Non-AP MLD associated with the second AP MLD has downlink unicast services, before the first AP of the first AP MLD generates unicast service indication information, it is also necessary to allocate an AID to each Non-AP MLD.

[0196] Example 2

[0197] The second embodiment of the present application introduces a method for allocating an AID for a multi-link device, specifically, a method for allocating an AID for a Non-AP MLD.

[0198] It is understandable that AID is the identifier (ID) assigned by AP to the associated STA after association, which can be regarded as the ID of the associated STA. AID can be used to identify and distinguish each STA associated with the AP, and can be used as an index in some frame structures to point to a specific associated STA. If the AP can support multiple BSSIDs, or the beacon frame or probe response frame can carry multiple BSSID elements (multiple BSSID elements), the maximum number of BSSIDs that the AP can support is 2 n , indicating that the range of BSSID is [1, 2 n -1], then the range of AIDs that the AP can assign to STAs is [2 n , 2007]. Where n is the value of the max BSSID indicator field of the BSSID element. If the AP does not support multiple BSSIDs, or beacon frames or probe response frames cannot carry multiple BSSID elements, the AP can assign an AID in the range [1, 2007] to the STA.

[0199] Because a small area may host a variety of user types or services, using different APs within this small area will inevitably lead to channel interference between different APs, as each AP will attempt to find a channel with minimal or no interference. Therefore, IEEE 802.11ax proposes using a single AP to create multiple virtual APs to serve different service types or client types. Therefore, a virtual AP can have a single BSSID, meaning that a single physical AP can have multiple BSSIDs. In other words, some APs can support multiple BSSIDs.

[0200] It is also understandable that multiple STAs included in a Non-AP MLD may share the same AID, that is, a Non-AP MLD has only one AID.

[0201] It is understandable that, in practical applications, the second embodiment of the present application can be implemented alone or in combination with the first embodiment, and this application does not limit this. Specifically, the second embodiment of the present application can be implemented in combination with the second implementation method of the unicast service indication information in the first embodiment.

[0202] It is understandable that the AP MLD aggregation of the above-mentioned reporting AP is the same as that of any AP (for ease of description, AP i For example, the co-located AP MLD set includes the following APs:

[0203] (1) With AP i All APs that belong to the same AP MLD, or all APs in the AP MLD where APi is located.

[0204] (2) With AP i All APs in the AP MLD of the non-transmitting AP in the same multi-BSSID set; or i All APs in the AP MLD where the non-transmitting APs in the multi-BSSID set are located.

[0205] (3) All APs that meet the following two conditions of AP MLD, where the two conditions are: 1) There is at least one AP in the AP MLD that is compatible with AP i An AP in the AP MLD is in the same multi-BSSID set; 2) There is no AP in the AP MLD with AP i Work on the same link.

[0206] Refer to Figure 9, which is a schematic flow chart of the AID allocation method for Non-AP MLD provided in an embodiment of the present application. As shown in Figure 9, the AID allocation method includes but is not limited to the following steps:

[0207] S201, AP MLD AP i Generate AID allocation information, which carries the AID allocated for the Non-AP MLD. The AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is associated with the AP i Any AP MLD in the collocated AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the set circle of co-located AP MLD sets.

[0208] S202, AP MLD AP i The AID allocation information is sent to the STA of the Non-AP MLD. Correspondingly, the STA of the Non-AP MLD receives the AID allocation information.

[0209] The AP MLD in the embodiment of the present application may be the first AP MLD or the second AP MLD or other AP MLDs in the above-mentioned embodiment 1. i Any AP in the AP MLD.

[0210] Implementation A: The target AP MLD is the same as the AP i Any AP MLD in the co-located AP MLD set.

[0211] Among them, the "with AP" mentioned in the embodiment of this application i In the AP MLD set of co-located APs, all AP MLDs (APs included in the AP MLD) and AP i The AP MLD and target AP MLD both belong to the same AP. i A collection of co-located AP MLDs.

[0212] Specifically, the AID allocation information may carry the AID allocated for the Non-AP MLD, which is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is associated with the AP MLD. iAny AP MLD in the collocated AP MLD set. In other words, the AID space / AID set used by the AP MLD to allocate AIDs to its associated non-AP MLD is the same as the AID space / AID set used by the target AP MLD to allocate AIDs to its associated non-AP MLD. It is understandable that the AID allocated to the non-AP MLD is also different from the AID of the non-AP MLD associated with the AP MLD itself.

[0213] Optionally, in the embodiment of the present application, the Non-AP MLD associated with the AP MLD itself can be understood in two ways: 1) All Non-AP MLDs that establish multi-link associations with the AP MLD, where the Non-AP MLD can be associated with some APs in the AP MLD or with all APs. 2) APs associated with the AP MLD i There is an associated Non-AP MLD, where the Non-AP MLD can be associated with some APs in the AP MLD or with all APs, but the part or all APs must include AP i Here, AP i Refers to the AP to which the AID is assigned in the AP MLD.

[0214] See Figure 10a, which is a schematic diagram of an AP MLD set co-located with an AP provided by an embodiment of the present application. As shown in Figure 10a, assuming that AP i If it is AP1x, the set of APs co-located with AP1x includes AP2y, AP1y, AP2x, AP3y, and AP4y. Therefore, the set of AP MLDs co-located with AP1x includes AP MLD1 and AP MLD3. Therefore, the AID assigned to this Non-AP MLD, carried in the AID allocation information, is different from the AID of the Non-AP MLD associated with AP MLD1 and the AID of the Non-AP MLD associated with AP MLD3. In other words, the AID of the Non-AP MLD associated with AP MLD1 and the AID of the Non-AP MLD associated with AP MLD3 must be unique and different.

[0215] See Figure 10b, which is another schematic diagram of an AP MLD set co-located with an AP provided by an embodiment of the present application. As shown in Figure 10b, assuming that AP iIf it is AP1x, the set of APs co-located with AP1x includes: AP2y, AP3x, AP1y, AP2z, AP4y, AP2x, and AP4x. Therefore, the set of AP MLDs co-located with AP1x includes: AP MLD1, AP MLD2, and AP MLD3. Therefore, the AID assigned to this Non-AP MLD, carried in the AID allocation information, is different from the AID of the Non-AP MLD associated with AP MLD1, the AID of the Non-AP MLD associated with AP MLD2, and the AID of the Non-AP MLD associated with AP MLD3. In other words, the AIDs of the Non-AP MLDs associated with AP MLD1, AP MLD2, and AP MLD3 should be unique.

[0216] See Figure 10c, which is another schematic diagram of an AP MLD set co-located with an AP provided in an embodiment of the present application. As shown in Figure 10c, assuming that AP i If it is AP3x, the set of APs co-located with AP3x includes: AP1x, AP2y, AP2x, AP4x, AP1y, and AP2z. Therefore, the set of AP MLDs co-located with AP3x includes: AP MLD1, AP MLD2, and AP MLD3. Therefore, the AID assigned to this Non-AP MLD, carried in the AID allocation information, is different from the AID of the Non-AP MLD associated with AP MLD1, the AID of the Non-AP MLD associated with AP MLD2, and the AID of the Non-AP MLD associated with AP MLD3. In other words, the AIDs of the Non-AP MLD associated with AP MLD1, the AID of the Non-AP MLD associated with AP MLD2, and the AID of the Non-AP MLD associated with AP MLD3 should be unique, i.e., different.

[0217] Taking Figure 5 above as an example, suppose AP iIf AP4x is AP4x, the set of APs co-located with AP4x includes AP2x, AP4y, AP2z, AP1y, AP4z, AP5, AP1x, AP2y, and AP3. Therefore, the set of AP MLDs co-located with AP4x includes AP MLD1, AP MLD2, AP MLD3, and AP MLD4. Therefore, the AID assigned to this Non-AP MLD in the AID allocation information is different from the AID of the Non-AP MLD associated with AP MLD1, the AID of the Non-AP MLD associated with AP MLD2, the AID of the Non-AP MLD associated with AP MLD3, and the AID of the Non-AP MLD associated with AP MLD4. That is, the AID of the Non-AP MLD associated with AP MLD1, the AID of the Non-AP MLD associated with AP MLD2, the AID of the Non-AP MLD associated with AP MLD3, and the AID of the Non-AP MLD associated with AP MLD4 should be unique, that is, different.

[0218] Implementation method B: The target AP MLD is the same as the AP i Any AP MLD in the set circle of co-located AP MLD sets.

[0219] Among them, the "with AP" mentioned in the embodiment of this application i In the "collection circle" where the AP MLD collection of the same location is located, some AP MLDs are related to APs. i The other AP MLDs are located in the same location as the APs. i APs that are not part of the co-located AP MLD set are co-located with other APs. i The MLD set of co-located APs and the AP i The MLD set of APs in the same location is excluding AP i The AP MLD set of other APs co-located with AP excluding AP 1 constitutes the set circle. Here, AP MLD and target AP MLD both belong to AP 2 and AP 3. i The AP MLD clusters of the same location are within the cluster circle.

[0220] Specifically, with AP i The cluster circle of the co-located AP MLD set is the same as the AP i Any AP in the co-located AP MLD is composed of all APs in the co-located AP MLD set (wherein any AP can be understood as AP again). i For example, as shown in Figure 5, assume that AP iIf it is AP1x, the AP MLD set co-located with AP1x includes AP MLD1, AP MLD2, and AP MLD3. Furthermore, because the AP MLD set co-located with AP4x in the AP MLD set co-located with AP1x includes AP MLD2, AP MLD3, and AP MLD4, the set circle of the AP MLD set co-located with AP1x includes AP MLD1, AP MLD2, AP MLD3, and AP MLD4. Therefore, the AID assigned by AP1x to this non-AP MLD is different from the AID of the non-AP MLD associated with AP MLD1, the AID of the non-AP MLD associated with AP MLD2, the AID of the non-AP MLD associated with AP MLD3, and the AID of the non-AP MLD associated with AP MLD4.

[0221] As shown in Figure 10a, assuming that AP i If it is AP1x, the AP MLD set co-located with AP1x includes AP MLD1 and AP MLD3. Furthermore, because the AP MLD set co-located with AP3y in the AP MLD set co-located with AP1x includes AP MLD2 and AP MLD3, the set circle of the AP MLD set co-located with AP1x includes AP MLD1, AP MLD2, and AP MLD3. Therefore, the AID assigned by AP1x to this non-AP MLD is different from the AID of the non-AP MLD associated with AP MLD1, the AID of the non-AP MLD associated with AP MLD2, and the AID of the non-AP MLD associated with AP MLD3.

[0222] As shown in Figure 10b, assuming that AP i If it is AP1x, the AP MLD set co-located with AP1x includes AP MLD1, AP MLD2, and AP MLD3. The set circle of the AP MLD set co-located with AP1x also includes AP MLD1, AP MLD2, and AP MLD3. Therefore, the AID assigned by AP1x to this non-AP MLD is different from the AID of the non-AP MLD associated with AP MLD1, the AID of the non-AP MLD associated with AP MLD2, and the AID of the non-AP MLD associated with AP MLD3.

[0223] As shown in Figure 10c, assuming that AP iIf it is AP3x, the AP MLD set co-located with AP3x includes AP MLD1, AP MLD2, and AP MLD3. The set circle of the AP MLD set co-located with AP1x also includes AP MLD1, AP MLD2, and AP MLD3. Therefore, the AID assigned by AP1x to this non-AP MLD is different from the AID of the non-AP MLD associated with AP MLD1, the AID of the non-AP MLD associated with AP MLD2, and the AID of the non-AP MLD associated with AP MLD3.

[0224] Similar to implementation mode A, in implementation mode B, the AID allocated to the Non-AP MLD is also different from the AID of the Non-AP MLD associated with the AP MLD itself.

[0225] Optionally, for single-link STA AID allocation, AP i AID assigned to the single-link STA on this link (or with AP i The AID of the single-link STA associated with the target AP MLD is different from the AID of the Non-AP MLD associated with the target AP MLD. i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the set circle of co-located AP MLD sets.

[0226] For example, as shown in FIG10a above, assuming that AP i If it is AP1x, and AP1x is on link 1, then the AID of the single-link STA on link 1 is different from the AID of the Non-AP MLD associated with AP MLD1, and is also different from the AID of the Non-AP MLD associated with AP MLD3. In other words, the AID of the single-link STA on link 1, the AID of the Non-AP MLD associated with AP MLD1, and the AID of the Non-AP MLD associated with AP MLD3 should be unique, that is, different. It can also be understood that, in addition to the AID of the single-link STA associated with link 1, the AID of the single-link STA associated with link 2 can be the same as the AID of a Non-AP MLD associated with the target AP MLD.

[0227] Alternatively, as shown in FIG10a above, assuming that AP iIf it is AP1x, and AP1x is on link 1, the AID of the single-link STA on link 1, the AID of the Non-AP MLD associated with AP MLD1, the AID of the Non-AP MLD associated with AP MLD2, and the AID of the Non-AP MLD associated with AP MLD3 are all different.

[0228] It is understandable that in a wireless communication system, the default identifier of the AP MLD is 0, and multiple APs in the AP MLD share this identifier (ie, identifier 0). However, multiple APs in the AP MLD may also have different identifiers.

[0229] It's also understandable that cross-link TIM indications can be performed under the same AP MLD. That is, if AP 1 and AP 2 belong to the same AP MLD, AP 1 can include AP 2's TIM information in its TIM indication, indicating whether AP 2 has services for its associated Non-AP MLD. Therefore, the AIDs of multiple Non-AP MLDs associated with the same AP MLD are different.

[0230] Therefore, if the same identification system is used, such as the interval [1, 2007], the identifiers of multiple APs in an AP MLD must be unique, that is, different. The AIDs of multiple non-AP MLDs associated with the same AP MLD must also be unique, that is, different. In this embodiment of the application, the "AID assigned to the non-AP MLD" is a value selected from the remaining space and must also be unique. The remaining space here refers to the set of values ​​remaining in the interval [1, 2007], excluding values ​​that have already been used and cannot be reused.

[0231] Optionally, the AID allocation information may be carried in an association response frame or in other frames. Specifically, the AID allocated to the Non-AP MLD in the AID allocation information may be carried in an AID element of the association response frame. Referring to FIG. 11 , FIG. 11 is a schematic diagram of a frame format of an AID element provided in an embodiment of the present application. As shown in FIG. 11 , the AID element includes a 1-byte element identification field, a 1-byte length field, and a 2-byte AID field.

[0232] Optionally, the association response frame may also carry information such as the link identifier of each AP. The association response frame is used to confirm the establishment of a multi-link association with the Non-AP MLD.

[0233] S203: The Non-AP MLD STA parses the received association response frame to obtain the AID carried in the association response frame.

[0234] Optionally, before step S201, the method further includes step S204, wherein the STA of the Non-AP MLD generates an association request frame; and step S205, wherein the STA of the Non-AP MLD sends an association request frame to the AP of the AP MLD. i Send an association request frame, which is used to request to establish a multi-link association with the AP MLD. i An association request frame is received, wherein the association request frame may carry the link identifier of each STA of the Non-AP MLD and information of each STA.

[0235] Optional, AP MLD AP i After receiving the association request frame, the STA can send a confirmation frame to the Non-AP MLD STA. The confirmation frame is used to confirm the AP MLD AP i An association request frame is received.

[0236] When allocating an AID to a Non-AP MLD, the embodiment of the present application considers the solution described in the first embodiment above: an AP MLD helps another AP MLD to indicate whether the Non-AP MLD associated with the other AP MLD has a downlink unicast service. Therefore, the AID is not the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is the AID of the Non-AP MLD associated with the AP MLD. i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the co-located AP MLD set circle avoids AID ambiguity when indicating whether the Non-AP MLD has downlink unicast services.

[0237] Example 3

[0238] Embodiment 3 of the present application addresses the problem of certain APs in an AP MLD being unable to indicate whether their associated Non-AP MLDs have downlink unicast traffic by limiting the links on which the Non-AP MLD listens for downlink unicast traffic indications. Furthermore, in this case, APs in other AP MLDs operating on the same link as these APs do not assist these APs in sending downlink unicast traffic indications. For example, in FIG5 , if AP1x is a reporting AP, and Non-AP MLD1 is associated with AP2y and AP3 of AP MLD1, if Non-AP MLD1 only listens for downlink unicast traffic indications on link 2, AP2y (a non-transmitting AP in the multi-BSSID set) in AP MLD1 cannot send downlink traffic indications. Furthermore, transmitting APs in the same multi-BSSID set on the same link do not assist in sending downlink traffic indications for the MLD to which AP2y belongs. Consequently, Non-AP MLD1, which is listening on link 2, cannot receive the downlink traffic indication, meaning that Non-AP MLD1 cannot determine whether it has downlink unicast traffic.

[0239] Therefore, the third embodiment of the present application provides a unicast service indication method applicable to multiple links. See Figure 12, which is another schematic flow chart of the unicast service indication method applicable to multiple links provided in the embodiment of the present application. As shown in Figure 12, the method includes:

[0240] S1. AP MLD reporting: The AP generates a management frame, such as a beacon frame, which carries a TIM element. Part of the virtual bitmap field of the TIM element is used to indicate whether the Non-AP MLD associated with the AP MLD has a downlink unicast service.

[0241] S2. AP MLD reporting: The AP sends a management frame, such as a beacon frame, on the link on which it works.

[0242] The specific frame format of the TIM element may refer to FIG2 , and the frame format of some virtual bitmap fields may refer to FIG7 , which will not be described in detail here.

[0243] S3. The STA of the Non-AP MLD listens to the management frame, such as a beacon frame, on one or more links. The one or more links include a first link, which is a link on which the transmission AP of the multi-BSSID set in the AP MLD associated with the Non-AP MLD or the AP that does not belong to the multi-BSSID set works.

[0244] S4, the STA of the Non-AP MLD parses the management frame, such as the beacon frame, detected on the link reporting the AP operation, and determines whether the Non-AP MLD has a downlink unicast service.

[0245] Specifically, regarding step S3, in other words, a Non-AP MLD STA cannot listen for beacon frames only on links where non-transmitting APs in a multi-BSSID set are located. A Non-AP MLD STA can listen for beacon frames or other management frames on links where a transmitting AP in a multi-BSSID set or an AP that is not part of a multi-BSSID set is located. For example, taking Figure 5 as an example, if AP1x is a reporting AP, assume that Non-AP MLD1 is associated with AP1x, AP2y, and AP3 of AP MLD1. If AP1x sends a beacon frame on link 1, Non-AP MLD1 listens for beacon frames on link 1, or listens for beacon frames on links 1 and 2, or link 1 and 3, or link 3. Non-AP MLD1 cannot listen for beacon frames on link 2.

[0246] Optionally, the links monitored by the Non-AP MLD must include more than just the links on which non-transmitting APs operate in the associated AP MLD. For example, as shown in Figure 5, the links monitored by the Non-AP MLD can include Link 1 and Link 2, or Link 1 and 3, or Link 2 and Link 3, or Link 1, Link 2, and Link 3; but not just Link 2.

[0247] It can be seen that the embodiment of the present application limits the link on which the Non-AP MLD listens for downlink unicast service indications, so that the Non-AP MLD listens on the link (for ease of description, denoted as the first link) on which the transmitting AP of the multi-BSSID set or the AP that does not belong to the multi-BSSID set in the AP MLD associated with the Non-AP MLD works. Because the transmitting AP in the AP MLD and the AP that does not belong to the multi-BSSID set can send beacon frames (which carry downlink unicast service indications), the Non-AP MLD can listen to the beacon frames on the first link, and thus determine whether the Non-AP MLD itself has downlink unicast services by parsing the beacon frames.

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

[0249] The embodiment of the present application can divide the functional modules of the multi-link device according to the above-mentioned method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The communication device of the embodiment of the present application will be described in detail below with reference to Figures 13 to 17. The communication device is an access point of an access point multi-link device or a site of a site multi-link device. Further, the communication device can be a device in an AP MLD; or, the communication device is a device in an STA MLD.

[0250] In the case of using an integrated unit, see Figure 13 , which is a schematic diagram of the structure of a communication device 1 provided in an embodiment of the present application. As shown in Figure 13 , the communication device 1 includes: a processing unit 11 and a transceiver unit 12 .

[0251] The communication device 1 may be a first AP MLD or a chip in the first AP MLD, such as a Wi-Fi chip, or may be a first AP in the first AP MLD. The first AP is a reporting AP and belongs to the first AP MLD.

[0252] In one design, the processing unit 11 is configured to generate unicast service indication information; and the transceiver unit 12 is configured to send the unicast service indication information on a first link, where the first link is a working link of the first AP. The unicast service indication information is configured to indicate whether a non-AP MLD associated with the first AP MLD has downlink unicast service, and whether a non-AP MLD associated with a second AP MLD has downlink unicast service, where the second AP MLD is an AP MLD to which a non-transmitting AP in a multi-BSSID set to which the first AP belongs.

[0253] As can be seen, in the communication device 1, the unicast service indication information generated by the processing unit 11 can not only indicate whether the non-AP MLD associated with the first AP MLD has downlink unicast services, but also help the second AP MLD indicate whether the non-AP MLD associated with the second AP MLD has downlink unicast services. The second AP MLD is the AP MLD to which the non-transmitting AP in the multi-BSSID set to which the first AP belongs. This can solve the problem that some or all APs in the AP MLD cannot indicate whether the non-AP MLD associated with them has downlink unicast services, so that the non-AP MLD associated with these APs can normally receive downlink unicast services.

[0254] Optionally, the processing unit 11 is further configured to generate AID allocation information, where the AID allocation information carries an AID allocated for the Non-AP MLD, where the AID is different from the AID of the Non-AP MLD associated with the second AP MLD. The transceiver unit 12 is further configured to transmit the AID allocation information. The AID allocation information is carried in an association response frame. It is understood that the AID allocation information may also be carried in other frames.

[0255] Optionally, the transceiver unit 12 is further configured to receive an association request frame, where the association request frame is used to request to establish a multi-link association with the communication device 1 .

[0256] It should be understood that the communication device 1 in this design can execute the aforementioned embodiment 1, and the above-mentioned operations or functions of each unit in the communication device 1 are respectively for realizing the corresponding operations of the first AP of the first AP MLD in the aforementioned embodiment 1. For the sake of brevity, they will not be repeated here.

[0257] Optionally, the communication device 1 may be an AP MLD or a chip in the AP MLD, such as a Wi-Fi chip, or may be a reporting AP in the AP MLD.

[0258] In another design, the processing unit 11 is used to generate a management frame, such as a beacon frame, which carries a TIM element. Part of the virtual bitmap field of the TIM element is used to indicate whether the Non-AP MLD associated with the AP MLD has a downlink unicast service; the transceiver unit 12 is used to send the management frame, such as a beacon frame, on the link on which it works.

[0259] It should be understood that the communication device 1 in this design can execute the aforementioned embodiment three, and the above operations or functions of each unit in the communication device 1 are respectively for realizing the corresponding operations of the AP MLD reporting AP in the aforementioned embodiment three. For the sake of brevity, they will not be repeated here.

[0260] 14 , which is a schematic diagram of the structure of a communication device 2 provided in an embodiment of the present application. As shown in FIG14 , the communication device 2 includes a transceiver unit 21 and a processing unit 22 .

[0261] The communication device 2 may be a Non-AP MLD or a chip in the Non-AP MLD, such as a Wi-Fi chip, or may be a first STA in the Non-AP MLD.

[0262] In one design, the transceiver unit 21 is configured to receive unicast service indication information on the first link in which the communication device 2 operates; and the processing unit 22 is configured to determine, based on the received unicast service indication information, whether the Non-AP MLD in which the communication device 2 is located has downlink unicast service. The unicast service indication information is used to indicate whether the Non-AP MLD associated with the first AP MLD has downlink unicast service, and whether the Non-AP MLD associated with the second AP MLD has downlink unicast service, where the second AP MLD is an AP MLD to which a non-transmitting AP in the multi-BSSID set in which the first AP is located belongs.

[0263] It can be seen that in the communication device 2, the processing unit 22 can obtain whether it has a downlink unicast service according to the unicast service indication information, so as to ensure that it can receive the downlink unicast service.

[0264] Optionally, the transceiver unit 21 may further be configured to receive AID allocation information; the processing unit 22 may further be configured to parse the received AID allocation information to obtain an AID assigned to the non-AP MLD carried in the AID allocation information, wherein the AID is different from the AID of the non-AP MLD associated with the target AP MLD, and the target AP MLD is any AP MLD in the set of AP MLDs co-located with the first AP. The AID allocation information is carried in an association response frame. It is understood that the AID allocation information may also be carried in other frames.

[0265] Optionally, the processing unit 22 is further configured to generate an association request frame; the transceiver unit 21 is further configured to send the association request frame to the second AP of the first AP MLD, where the association request frame is used to request to establish a multi-link association with the first AP MLD.

[0266] It should be understood that the communication device 2 in this design can execute the aforementioned embodiment 1, and the above operations or functions of each unit in the communication device 2 are respectively for implementing the corresponding operations of the first STA of the Non-AP MLD in the aforementioned embodiment 1. For the sake of brevity, they will not be repeated here.

[0267] Optionally, the communication device 2 may be a Non-AP MLD or a chip in a Non-AP MLD, such as a Wi-Fi chip, or may be any STA in a Non-AP MLD.

[0268] In another design, the transceiver unit 21 is used to listen to the management frame, such as a beacon frame, on one or more links, and the one or more links include a first link, which is the link where the transmission AP of the multi-BSSID set in the AP MLD associated with the Non-AP MLD or the AP that does not belong to the multi-BSSID set works; the processing unit 22 is used to parse the management frame, such as the beacon frame, heard on the link where the reporting AP works, to determine whether the Non-AP MLD has a downlink unicast service.

[0269] It should be understood that the communication device 2 in this design can execute the aforementioned embodiment three, and the above operations or functions of each unit in the communication device 2 are respectively for implementing the corresponding operations of the Non-AP MLD STA in the aforementioned embodiment three. For the sake of brevity, they will not be repeated here.

[0270] Referring to Figure 15 , Figure 15 is a schematic diagram of the structure of a communication device 3 provided in an embodiment of the present application. The communication device 3 may be an AP MLD or a chip within an AP MLD, such as a Wi-Fi chip. Optionally, the communication device 3 corresponds to the AP MLD described in the second embodiment, or any AP within the AP MLD. As shown in Figure 15 , the communication device 3 includes a processing unit 31 and a transceiver unit 32.

[0271] The processing unit 31 is configured to generate AID allocation information, wherein the AID allocation information carries an AID allocated for the Non-AP MLD, the AID being different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is associated with the AP MLD. i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the set circle where the AP MLD set at the same location is located; the transceiver unit 32 is used to send the AID allocation information. i Any AP in the AP MLD.

[0272] Optional, if the target AP MLD is the same as the AP i Any AP MLD in the AP MLD set of the same location, then the AP MLD and the target AP MLD are both related to the AP i A collection of co-located AP MLDs.

[0273] Optionally, the AID allocation information is carried in an association response frame. It is understandable that the AID allocation information can also be carried in other frames.

[0274] Optionally, the transceiver unit 32 is further configured to receive an association request frame, where the association request frame is used to request to establish a multi-link association with the AP MLD.

[0275] It can be seen that in the communication device 2, the AID assigned by the Non-AP MLD carried in the AID allocation information generated by the processing unit 31 is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD here is the AID assigned by the Non-AP MLD. i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the co-located AP MLD set circle. This avoids AID ambiguity when indicating whether a Non-AP MLD has downlink unicast services.

[0276] It should be understood that the communication device 3 described in the embodiment of the present application can be executed in accordance with the aforementioned embodiment 2, and the above operations or functions of each unit in the communication device 3 are respectively for implementing the AP MLD of the aforementioned embodiment 2. i For the sake of brevity, the corresponding operations are not described here.

[0277] Referring to Figure 16 , Figure 16 is a schematic diagram of the structure of a communication device 4 provided in an embodiment of the present application. The communication device 4 can be a non-AP MLD or a chip within a non-AP MLD, such as a Wi-Fi chip. Optionally, the communication device 4 corresponds to the non-AP MLD described in the second embodiment, or any STA within the non-AP MLD. As shown in Figure 16 , the communication device 4 includes a transceiver unit 41 and a processing unit 42.

[0278] The transceiver unit 41 is used to receive AID allocation information from the access point of the AP MLD; the processing unit 42 is used to parse the received AID allocation information to obtain the AID allocated for the Non-AP MLD carried in the AID allocation information. The AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is associated with the AP MLD. i Any AP MLD in the co-located AP MLD set, or the target AP MLD is the same as the AP i Any AP MLD in the set circle of the co-located AP MLD set. i Any AP in the AP MLD.

[0279] Optional, if the target AP MLD is the same as the AP iAny AP MLD in the AP MLD set of the same location, then the AP MLD and the target AP MLD are both related to the AP i A collection of co-located AP MLDs.

[0280] Optionally, the AID allocation information is carried in an association response frame. It is understandable that the AID allocation information can also be carried in other frames.

[0281] Optionally, the processing unit 42 is further configured to generate an association request frame; the transceiver unit 41 is further configured to send the association request frame, where the association request frame is used to request to establish a multi-link association with the AP MLD.

[0282] It should be understood that the communication device 4 described in the embodiment of the present application can execute the aforementioned embodiment 2, and the above operations or functions of each unit in the communication device 4 are respectively for implementing the corresponding operations of the STA of the Non-AP MLD in the aforementioned embodiment 2. For the sake of brevity, they will not be repeated here.

[0283] The above describes the AP MLD and non-AP MLD embodiments of the present application. The following describes possible product forms of these AP MLD and non-AP MLD. It should be understood that any product that has the functions of the AP MLD described in Figures 13 or 15, or any product that has the functions of the non-AP MLD described in Figures 14 or 16, falls within the scope of protection of the present application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the AP MLD and non-AP MLD embodiments of the present application to these examples.

[0284] As a possible product form, the AP MLD and Non-AP MLD described in the embodiments of the present application can be implemented by a general bus architecture.

[0285] Referring to Figure 17, Figure 17 is a schematic diagram of the structure of a communication device 1000 provided in an embodiment of the present application. The communication device 100 can be an AP MLD or a Non-AP MLD, or a device therein. As shown in Figure 17, the communication device 1000 includes a processor 1001 and a transceiver 1002 that is internally connected and communicates with the processor. The processor 1001 is a general-purpose processor or a dedicated processor. For example, it can be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminals, terminal chips, DUs or CUs, etc.), execute computer programs, and process computer program data. The transceiver 1002 can be called a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement transceiver functions. The transceiver 1002 can include a receiver and a transmitter. The receiver can be called a receiver or a receiving circuit, etc., and is used to implement a receiving function; the transmitter can be called a transmitter or a transmitting circuit, etc., and is used to implement a transmitting function. Optionally, the communication device 1000 may further include an antenna 1003 .

[0286] Optionally, the communication device 1000 may include one or more memories 1004, on which instructions may be stored. The instructions may be computer programs. The computer programs may be executed on the communication device 1000 to enable the communication device 1000 to perform the methods described in the above method embodiments. Optionally, the memories 1004 may also store data. The communication device 1000 and the memories 1004 may be provided separately or integrated together.

[0287] The processor 1001 , the transceiver 1002 , and the memory 1004 may be connected via a communication bus.

[0288] In one design, the communication device 1000 can be used to perform the functions of the first AP of the first AP MLD in the aforementioned embodiment one: the processor 1001 can be used to execute step S101 in Figure 6 and / or other processes for the technology described in this document; the transceiver 1002 can be used to execute step S102 in Figure 6 and / or other processes for the technology described in this document.

[0289] In one design, the communication device 1000 can be used to perform the functions of the first STA of the Non-AP MLD in the aforementioned embodiment one: the processor 1001 can be used to execute step S104 in Figure 6 and / or other processes for the technology described in this document; the transceiver 1002 can be used to execute step S103 in Figure 6 and / or other processes for the technology described in this document.

[0290] In one design, the communication device 1000 can be used to perform the functions of the AP of the AP MLD in the aforementioned embodiment 2: the processor 1001 can be used to execute step S201 in Figure 9 and / or other processes for the technology described in this document; the transceiver 1002 can be used to execute step S202 in Figure 9 and / or other processes for the technology described in this document.

[0291] In one design, the communication device 1000 can be used to perform the functions of the STA of the Non-AP MLD in the aforementioned embodiment 2: the processor 1001 can be used to execute steps S203 and S204 in Figure 9 and / or other processes for the technology described in this document; the transceiver 1002 can be used to execute step S205 in Figure 9 and / or other processes for the technology described in this document.

[0292] In one design, the communication device 1000 can be used to perform the AP reporting function of the AP MLD in the aforementioned embodiment three: the processor 1001 can be used to execute step S1 in Figure 12 and / or other processes for the technology described in this document; the transceiver 1002 can be used to execute step S2 in Figure 12 and / or other processes for the technology described in this document.

[0293] In one design, the communication device 1000 can be used to perform the functions of the STA of the Non-AP MLD in the aforementioned embodiment three: the processor 1001 can be used to perform step S4 in Figure 12 and / or other processes for the technology described in this document; the transceiver 1002 can be used to perform step S3 in Figure 12 and / or other processes for the technology described in this document.

[0294] In any of the above designs, processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0295] In any of the above designs, processor 1001 may store instructions, which may be computer programs. The computer programs, when executed on processor 1001, may cause communication device 1000 to perform the methods described in the above method embodiments. The computer programs may be embedded in processor 1000, in which case processor 1001 may be implemented by hardware.

[0296] In one implementation, the communication device 1000 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0297] The scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited to FIG. 17 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0298] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0299] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

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

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

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

[0303] (6)Others, etc.

[0304] As a possible product form, the AP MLD and Non-AP MLD described in the embodiments of the present application can be implemented by a compatible processor.

[0305] A general-purpose processor implementing an AP MLD includes processing circuitry and an input / output interface for internal communication with the processing circuitry. In one design, the general-purpose processor can be used to perform the functions of the first AP of the first AP MLD described in the first embodiment. Specifically, the processing circuitry is used to perform step S101 in Figure 6 and / or other processes used in the techniques described herein; the input / output interface is used to perform step S102 in Figure 6 and / or other processes used in the techniques described herein.

[0306] In another design, the general-purpose processor can be used to perform the AP functions of the AP MLD in the second embodiment. Specifically, the processing circuit is used to perform step S201 in Figure 9 and / or other processes used in the technology described herein; the input and output interface is used to perform step S202 in Figure 9 and / or other processes used in the technology described herein.

[0307] In another design, the general-purpose processor can be used to perform the AP MLD reporting function described in the third embodiment. Specifically, the processing circuit is used to perform step S1 in Figure 12 and / or other processes used in the technology described herein; the input and output interface is used to perform step S2 in Figure 12 and / or other processes used in the technology described herein.

[0308] A general-purpose processor implementing Non-AP MLD includes processing circuitry and an input / output interface internally connected to and communicating with the processing circuitry. In one design, the general-purpose processor can be used to perform the functions of the first STA of Non-AP MLD described in the first embodiment. Specifically, the processing circuitry is used to execute step S104 in Figure 6 and / or other processes used in the techniques described herein; the input / output interface is used to execute step S103 in Figure 6 and / or other processes used in the techniques described herein.

[0309] In another design, the general-purpose processor can be used to perform the functions of the Non-AP MLD STA in the second embodiment. Specifically, the processing circuit is used to perform steps S203 and S204 in Figure 9 and / or other processes used in the technology described herein; the input and output interface is used to perform step S205 in Figure 9 and / or other processes used in the technology described herein.

[0310] In another design, the general-purpose processor can be used to perform the functions of the Non-AP MLD STA in the aforementioned embodiment 3. Specifically, the processing circuit is used to perform step S4 in Figure 12 and / or other processes used in the techniques described herein; and the input / output interface is used to perform step S3 in Figure 12 and / or other processes used in the techniques described herein.

[0311] As a possible product form, the AP MLD and Non-APMLD described in the embodiments of the present application can also be implemented using the following: one or more FPGAs (field programmable gate arrays), PLDs (programmable logic devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits that can perform the various functions described throughout this application.

[0312] It should be understood that the communication devices of various product forms mentioned above have any functions of AP MLD or Non-APMLD in the above method embodiments, which will not be described in detail here.

[0313] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program code is stored. When the processor executes the computer program code, the electronic device executes the method in any of the aforementioned embodiments.

[0314] An embodiment of the present application further provides a computer program product, which, when executed on a computer, enables the computer to execute the method in any of the aforementioned embodiments.

[0315] An embodiment of the present application also provides a communication device, which can exist in the form of a chip product. The structure of the device includes a processor and an interface circuit. The processor is used to communicate with other devices through a receiving circuit, so that the device executes the method in any of the aforementioned embodiments.

[0316] An embodiment of the present application further provides a wireless communication system, including an AP MLD and a Non-AP MLD. The AP MLD and the Non-AP MLD can execute the method in any of the aforementioned embodiments.

[0317] The steps of the method or algorithm described in conjunction with the disclosure of this application can be implemented in hardware or by executing software instructions by a processor. The software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, mobile hard disks, read-only compact disks (CD-ROMs), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a core network interface device. Of course, the processor and the storage medium can also exist in the core network interface device as discrete components.

[0318] Those skilled in the art will appreciate that, in one or more of the examples above, the functions described herein can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer-readable storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0319] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of this application. It should be understood that the above description is only the specific implementation methods of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of this application should be included in the scope of protection of this application.

Claims

DEPCT6603 / 05 / 25661. A method for identifying addressably identifiable traffic on a multilink segment comprising: Using the first AP access point of a multilink device at the first APMLD access point, it generates addressably identifiable traffic information. This addressably identifiable traffic information is used to indicate whether a non-AP MLD multilink device connected to the first APMLD has downtime traffic, and whether a non-AP MLD connected to a second APMLD has downtime traffic. The second APMLD is an APMLD that is not passed through the multi-service set identifier (BSSID) of which the first AP is a part; and using the first AP of the first APMLD to send addressably identifiable traffic information on the first segment, where the first segment is the active segment of the first AP.2.The point-by-point addressed traffic indication method applicable to multilinks comprises: using the first STA station of a non-AP multilink device (non-AP MLD) to receive point-by-point addressed traffic indication information on the first link where the first STA is operating; where this point-by-point addressed traffic indication information is used to indicate whether the non-AP MLD connected to the first AP MLD has point-by-point addressed traffic during the down phase, and whether the non-AP MLD connected to the second AP MLD has point-by-point addressed traffic during the down phase, and that the second AP MLD is an AP MLD that is not traversed in the multi-BSSID series in which the first AP is located; and using the first STA of the non-AP MLD, based on the point-by-point addressed traffic indication information, to determine whether the non-AP MLD has point-by-point addressed traffic during the down phase.

1. One of the methods under Claim 1 or 2, where one bit of the individually addressed traffic information corresponds to one AID link identifier, the bit of the individually addressed traffic information is used to indicate whether the non-AP MLD identified by the corresponding AID has individually addressed traffic during the down period, and the non-AP MLD is either the non-AP MLD associated with the first APMLD or the non-AP MLD associated with the second APMLD.

4. One of the methods under Claim 1 through 3, where the corresponding AID link identifiers of the individually addressed traffic information bits are different from each other.

5. One of the methods under Claim 1 through 4, where the individually addressed traffic information is carried over in a partial virtual bit map field of a TIM element.

6. One of the methods under Claim 1 through 4, where the individually addressed traffic information is located in a TIM frame or TIM frame. 7.

8. Any one of the methods under Claims 1 through 7 where the AID space used by the first APMLD to allocate AID to a non-AP MLD associated with the first APMLD and the AID space used by the second APMLD to allocate AID to a non-AP MLD associated with the second APMLD are the same. 9.

10. Method according to claim 1 or 2, where the point-identified addressable traffic information comprises a traffic TIM block corresponding to the first APMLD and one TIM block corresponding to the second APMLD; the TIM block corresponding to the first APMLD is used to indicate whether the non-AP MLD associated with the first APMLD has point-identified addressable traffic during the down phase, and one TIM block corresponding to the second APMLD is used to indicate whether the non-AP MLD associated with the second APMLD has point-identified addressable traffic during the down phase.

11. Method according to claim 9, where the point-identified addressable traffic information also comprises the index of the second APMLD, and the index of the second APMLD has a one-to-one correspondence with the corresponding TIM block of the second APMLD.

12. Method according to claim 9 or 10, where one non-AP MLD corresponds to one bit of one of the TIM blocks, and the bits of that TIM block are used to indicate whether the non-AP MLD has point-identified addressable traffic during the down phase.

13. Any one of the methods under claims 9 through 11 where the AID space used by the first APMLD to allocate AID to a non-AP MLD associated with the first APMLD and the AID space used by the second APMLD to allocate AID to a non-AP MLD associated with the second APMLD are independent of each other.

13. Any one of the methods under claims 1 and 3 through 8 where the method also includes: using the first AP of the first APMLD to generate AID association identifier allocation information where that AID allocation information carries the AID allocated to a non-AP MLD and that AID is different from the AID of the non-AP MLD associated with the second APMLD; and using the first AP of the first APMLD to send the AID allocation information.

14. Any one of the methods under claims 2 through 8 where the method also includes: using the first STA of a non-AP MLD to receive the AID allocation information; and using the first STA of a non-AP MLD to enumerate the received AID allocation information to learn that that AID allocation information carries the AID allocated to a non-AP MLD and that AID is different from the AID of the non-AP MLD associated with the second APMLD. 15.The method for allocating AID link identifiers to multiple linked devices consists of: using the APMLD's API to generate AID link identifier allocation information, where this AID allocation information carries the AID allocated to a non-AP MLD, this AID is different from the AID of the non-AP MLD linked to the target APMLD, and the target APMLD can be any APMLD in the API's concatenated APMLD set or any APMLD in a group of sets containing the API's concatenated APMLD sets; and using the APMLD's API to send a link response frame.The method for allocating AID link identifiers to multiple linked devices includes: using a non-AP MLD station to receive AID allocation information; and using a non-AP MLD station to enumerate the received AID allocation information to learn that the AID allocation information carries the AID allocated to the non-AP MLD, where that AID is different from the AID of the non-AP MLD associated with the target APMLD, and that target APMLD can be any APMLD in a set of APMLDs placed together in the APi, or the target APMLD can be any APMLD in a group of sets containing other APMLDs.

17. Method 15 or 16, whereby the AID allocation information is carried in the link response framework.

18. Method 15 to 17, whereby both APMLD and APMLD target are part of an APMLD placed set; or both APMLD and APMLD target are part of a set group containing an APMLD placed set of APi, and that set group consists of an APMLD placed set of APi and an APMLD placed set of any AP other than the APi in the APMLD placed set of APi. 19.

20. According to any one of the claims 15 through 18, multiple stations incorporated into a non-AP MLD share the same AID.

21. According to any one of the claims 15 through 19, the AID space used by the APMLD to allocate AID to a non-AP MLD associated with the APMLD and the AID space used by the target APMLD to allocate AID to a non-AP MLD associated with the target APMLD are the same.

22. The method for allocating an AID link identifier to multiple incorporated link devices includes: the use of the first AP of the first APMLD generates AID allocation information, whereby this AID allocation information carries the AID allocated to a non-AP MLD, the AID space used by the first APMLD to allocate AID to a non-AP MLD associated with the first APMLD, and the AID space used by the second APMLD to allocate AID to a non-AP MLD associated with the second APMLD, which are independent of each other, and the second APMLD is an APMLD to which APs not passed in multiple BSSID sets to which the first AP is included are part; and the use of the first AP of the first APMLD transmits the AID allocation information.The method for allocating AID link identifiers to multiple link devices consists of: using the first STA of a non-AP MLD to receive AID allocation information where the non-AP MLD is associated with the first APMLD; and using the first STA of the non-AP MLD to enumerate the received AID allocation information to learn that the AID allocation information carries the AID allocated to the non-AP MLD, where the AID space of which the AID is a part and the AID space used by the second APMLD to allocate AID to the non-AP MLD associated with the second APMLD are independent of each other, and the second APMLD is the APMLD in which the AP that is not passed in the multiple BSSID basic service set identifiers, in which the first AP of the first APMLD associated with the first STA of the non-AP MLD, is a part.23.

24. One of the methods under claim 21 through 23 where the AID allocation information is carried in the AID allocation information and allocated to a non-AP MLD is different from the AID allocated by a second APMLD to a non-AP MLD linked to the second APMLD; or the AID carried in the AID allocation information and allocated to a non-AP MLD is the same as the AID allocated by a second APMLD to a non-AP MLD linked to the second APMLD.

25. One of the methods under claim 21 through 23 where the AID allocation information is carried in the link response frame.

26. A method for identifying individually addressed traffic applicable to multiple links which includes: using AP reports of APMLD to generate a management frame where the management frame includes TIM elements and virtual bitmap fields; some parts of the TIM elements are used to indicate whether a non-AP MLD linked to APMLD has individually addressed traffic during the down period; and using AP reports of APMLD to send the management frame on the active link of the AP report.A method for identifying point-by-point addressed traffic applicable to multiple links comprised of: using a non-AP MLD to listen to the management framework on one or more links where one or more links comprise a first link, which is the link through which the AP is passed in a multi-BSSID set of APs; the non-AP MLD associated with that AP is running on it, or an AP that is not part of a multi-BSSID set is running on it; the management framework comprises a TIM element; and some virtual bitmap fields of the TIM element are used to indicate whether the non-AP MLD associated with that AP has point-by-point addressed traffic during the down period; and using a non-AP MLD to enumerate the management framework obtained through listening on the link through which the reporting AP is running on it to determine whether the non-AP MLD has point-by-point addressed traffic during the down period.27.The communication equipment used with APMLD one consists of: a processing unit configured to generate point-by-point addressed traffic information, where this point-by-point addressed traffic information is used to indicate whether a non-AP MLD associated with APMLD one has point-by-point addressed traffic during the down phase, and whether a non-AP MLD associated with APMLD second has point-by-point addressed traffic during the down phase, and APMLD second is the APMLD of which APs not being passed through multiple BSSID series in which AP one is included; and a transceiver unit configured to transmit point-by-point addressed traffic information over the first link, where the first link is the active link of AP one.28.The communication equipment used with non-AP MLDs consists of: a transceiver unit configured to receive point-by-point addressed traffic information on the first link where the first STA operates; this point-by-point addressed traffic information is used to indicate whether the non-AP MLD connected to the first APMLD has point-by-point addressed traffic on the down range, and whether the non-AP MLD connected to the second APMLD has point-by-point addressed traffic on the down range, and that the second APMLD is the APMLD of which the non-transmitting AP in the multi-BSSID series of which the first AP is a part; and a processor unit configured to make a decision, based on the point-by-point addressed traffic information, whether the non-AP MLD has point-by-point addressed traffic on the down range.29.The communication suite under claim 27 or 28, where one bit of addressed traffic information corresponds to one AID link identifier, the bit of addressed traffic information is used to indicate whether the non-AP MLD identified by the corresponding AID has addressed traffic during the down period, and whether that non-AP MLD is a non-AP MLD associated with APMLD one or a non-AP MLD associated with APMLD two.

30. The communication suite under claim 27 to 29, where the corresponding AID link identifiers of the addressed traffic information bits are distinct from each other.

31. The method under claim 27 to 30, where the addressed traffic information is carried over in a partial virtual bit map field of a TIM element.

32. The method under claim 27 to 30, where the addressed traffic information is contained within the TIM frame or TIM frame.33.

34. Any one of the methods under Claims 27 through 33 where the AID space used by the first APMLD to allocate AID to a non-AP MLD associated with the first APMLD and the AID space used by the second APMLD to allocate AID to a non-AP MLD associated with the second APMLD are the same. 35.The communications equipment under claim 27 or 28, where point-specific addressed traffic information is provided, consists of a traffic map block (TIM) corresponding to the first APMLD and a second TIM block corresponding to the second APMLD. The TIM block corresponding to the first APMLD is used to indicate whether a non-AP MLD associated with the first APMLD has point-specific addressed traffic during the downstream phase, and the second TIM block corresponding to the second APMLD is used to indicate whether a non-AP MLD associated with the second APMLD has point-specific addressed traffic.

36. The communications equipment under claim 35 where the traffic information identified by an addressed point during the drop includes an index of the second APMLD and that index of the second APMLD has a one-to-one correspondence with the corresponding TIM block of the second APMLD.

37. The communications equipment under claim 35 or 36 where one non-AP MLD corresponds to one bit of one of the TIM blocks and that bit of the TIM block is used to indicate whether the non-AP MLD has traffic identified by an addressed point during the drop. 38.

39. A communication setup under any of Claims 35 through 37 where the AID space used by the first APMLD to allocate AID to a non-AP MLD associated with the first APMLD and the AID space used by the second APMLD to allocate AID to a non-AP MLD associated with the second APMLD are independent of each other.

40. A communication setup under any of Claims 27 and 29 through 34 where the processor unit is also configured to generate AID link identifier allocation information where that AID allocation information carries an AID allocated to a non-AP MLD and that AID is different from the AID of the non-AP MLD associated with the second APMLD; and the transceiver unit is also configured to transmit AID allocation information.

41. A communication setup under any of Claims 28 through 34 where the transceiver unit is also configured to receive AID allocation information; and the processor unit is also configured to enumerate the received AID allocation information to learn that the AID allocation information carries an AID allocated to a non-AP MLD and that AID is different from the AID of the non-AP MLD associated with the second APMLD.The communication equipment used with APMLD consists of: a processing unit configured to generate AID link identifier allocation information, where the AID allocation information carries the AID allocated to a non-AP MLD; this AID is different from the AID of the non-AP MLD associated with the target APMLD; and the target APMLD can be any APMLD in the APi-launched APMLD suite or any APMLD within a suite containing the APi-launched APMLD suite; and a transceiver unit configured to transmit 42 link response frames.The communication equipment used with a non-AP MLD consists of: a transceiver unit configured to receive AID allocation information; and a processing unit configured to enumerate the received AID allocation information to learn that the AID allocation information carries the AID allocated to the non-AP MLD, where the AID is different from the AID of the non-AP MLD associated with the target APMLD, and the target APMLD can be any APMLD in the APi's consolidated APMLD set, or the target APMLD can be any APMLD in the set containing the APi's consolidated APMLD set.

43. The communication equipment under claim 41 or 42 where the AID allocation information is carried in the link response frame.44.

45. Under any of the claims 41 to 44, multiple stations incorporated into a single non-AP MLD share the same AID.

46. Under any of the claims 41 to 45, the AID space used by the APMLD to allocate AID to non-AP MLDs associated with the APMLD and the AID space used by the target APMLD to allocate AID to non-AP MLDs associated with the target APMLD are the same. 47.The communication equipment consists of a processor and a transceiver, where the processor is configured to generate point-by-point addressed traffic information. This point-by-point addressed traffic information is used to indicate whether a non-AP MLD associated with the first APMLD has point-by-point addressed traffic during the down phase, and whether a non-AP MLD associated with a second APMLD has point-by-point addressed traffic during the down phase. The second APMLD is an APMLD that is not passed through the multiple Basic Service Set Identifiers (BSSIDs) of which the first AP is a part; and the transceiver is configured to transmit point-by-point addressed traffic information over the first link, which is the active link of the first AP.48.The communication equipment consists of a processor and a transceiver, where the transceiver is configured to receive point-by-point addressed traffic information on the first link where the first STA operates; this point-by-point addressed traffic information is used to indicate whether a non-AP MLD associated with the first APMLD has down-point addressed traffic, and whether a non-AP MLD associated with a second APMLD has down-point addressed traffic, and the second APMLD is an APMLD that is not traversed by multiple BSSIDs in which the first AP is a part; and the processor is configured to determine, based on the point-by-point addressed traffic information, whether a non-AP MLD has down-point addressed traffic.49.The communication equipment consists of a processor and a transceiver, where the processor is configured to generate AID allocation information. This AID allocation information carries the AID allocated to a non-AP MLD. This AID differs from the AID of a non-AP MLD linked to a target APMLD, and the target APMLD can be any APMLD within a set of APi-contained APMLDs or any APMLD within a group containing a set of APi-contained APMLDs. The transceiver is configured to transmit a 50 link response frame.A communication device consisting of a processor and a transceiver, where the transceiver is configured to receive AID allocation information; and the processor is configured to enumerate the received AID allocation information to learn that the AID allocation information carries an AID allocated to a non-AP MLD, where the AID differs from the AID of a non-AP MLD linked to a target APMLD, and the target APMLD can be any APMLD in a set of APi-containing APMLDs, or the target APMLD can be any APMLD in a set containing a set of APi-containing APMLDs.

51. A computer-readable storage medium that stores instructions, and when those instructions are executed on a computer, the computer is opened to execute one of the methods of claims 1 through 26.

52. A computer program product consisting of instructions, and when those instructions are executed on a computer, the computer is opened to execute one of the methods of claims 1 through 26. 53.A chip or a chip system which contains an input / output interface and a processing circuit, where the input / output interface is configured to receive code instructions and transmit those code instructions to the processing circuit, and the processing circuit is configured to execute the code instructions to perform any of the claims 1 through 26;

Images