HK40116861A - Method for indicating unicast service suitable for multiple links and related apparatus - Google Patents

Description

Unicast service indication method and related devices applicable to multiple links

This application is a divisional application. The original application has the application number 202010791117.1 and the original application date is August 7, 2020. The entire contents of the original application are incorporated herein by reference.

Technical Field

This application relates to the field of wireless communication technology, and in particular to a unicast service indication method and related apparatus applicable to multiple links.

Background Technology

To significantly improve the service transmission rate of wireless local area network (WLAN) systems, the IEEE (Institute of Electrical and Electronics Engineers) 802.11ax standard, based on the existing Orthogonal Frequency Division Multiplexing (OFDM) technology, further adopts Orthogonal Frequency Division Multiple Access (OFDMA) technology. OFDMA technology supports multiple nodes simultaneously transmitting and receiving data, thereby achieving multi-site diversity gain.

The next-generation WiFi standard, IEEE 802.11be, is known as Extremely High Throughput (EHT) or Wi-Fi 7, and its most important technical goal is to significantly improve peak throughput. WLAN devices conforming to the IEEE 802.11be standard support increasing peak throughput and reducing service transmission latency through multiple streams (maximum spatial streams of 16), multiple frequency bands (e.g., 2.4GHz, 5GHz, and 6GHz bands), and cooperation of multiple channels on the same frequency band. This multi-band or multi-channel approach can be collectively referred to as multi-link. Next-generation IEEE 802.11 standard station equipment that simultaneously supports multiple links is called a multi-link device (MLD).

However, certain special access point multi-link devices (such as those whose access points (APs) are all non-transmitted BSSIDs) cannot indicate whether their associated station (STA) multi-link devices have downlink unicast services by sending beacon frames, resulting in the associated station multi-link devices failing to correctly receive downlink unicast services. Therefore, how to indicate downlink unicast services for these special access point multi-link devices (AP MLDs) has become an urgent problem to be solved.

Summary of the Invention

This application provides a method and related apparatus for indicating unicast services in multi-link systems. It can help some or all APs in a partial AP MLD to indicate whether their associated site multi-link devices have downlink unicast services, thereby assisting the site multi-link devices in correctly receiving downlink unicast services.

The present application is described below from different aspects. It should be understood that the different implementation methods and beneficial effects described below can be referenced from each other.

Firstly, this application provides a unicast service indication method applicable to multiple links, applied in a first AP MLD, where the first AP is a reporting AP. The method includes: the first AP of the first AP MLD generating unicast service indication information and transmitting 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, wherein the second AP MLD is an AP MLD that is not a transport AP in the multi-BSSID set where the first AP resides. The first link is the working link of the first AP.

Optionally, the reporting AP can refer to the AP that sends the management frame, which carries information about multiple APs in the APMLD set that coexists with the reporting AP. This management frame can be, for example, a beacon frame or a probe response frame.

The unicast service indication information in this solution not only indicates whether the Non-AP MLD associated with the first AP MLD has downlink unicast service, but also helps the second AP MLD indicate whether the Non-AP MLD associated with it has downlink unicast service. The second AP MLD is the AP MLD that is not part of the transmission AP in the multi-BSSID set where the first AP is located. This can solve the problem that some or all APs in an AP MLD cannot indicate whether their associated Non-AP MLDs have downlink unicast service, enabling the Non-AP MLDs associated with these APs to receive downlink unicast service normally.

In addition, since there is a possibility that all APs in an AP MLD in 802.11be are non-transport APs, this solution can solve the problem that an AP MLD consisting entirely of non-transport APs cannot send unicast service indications, thereby increasing the completeness and diversity of downlink service indications.

In conjunction with the first aspect, in one possible implementation, the method further includes: the first AP of the first AP MLD generating and sending association identifier (AID) allocation information, which carries an AID assigned to the Non-AP MLD, and the AID is different from the AID of the Non-AP MLD associated with the second AP MLD.

Optionally, the AID allocation information described above is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

Optionally, before the second AP of the first AP MLD sends an association response frame, the method further includes: the first AP of the first AP MLD receiving an association request frame, the association request frame being used to request the establishment of a multi-link association with the first AP MLD.

When allocating AIDs, 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 assigned 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.

Secondly, this application provides a unicast service indication method applicable to multiple links, applied to Non-AP MLDs. This unicast service indication method for multiple links includes: a first STA of the Non-AP MLD receiving unicast service indication information on a first link where the first STA operates, and determining 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 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, wherein the second AP MLD is an AP MLD that is not a transmission AP in the multi-BSSID set where the first AP is located.

Optionally, the reporting AP can refer to the AP that sends the management frame, which carries information about multiple APs in the APMLD set that coexists with the reporting AP. This management frame can be, for example, a beacon frame or a probe response frame.

In conjunction with the second aspect, in one possible implementation, the method further includes: the first STA of the Non-AP MLD receiving AID allocation information and parsing the received AID allocation information to obtain the AID allocated to the Non-AP MLD carried in the AID allocation information, which is different from the AID of the Non-AP MLD associated with the second AP MLD.

Optionally, the AID allocation information described above is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

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 generating and sending an association request frame, which is used to request the establishment of a multi-link association with the first AP MLD.

Thirdly, this application provides a communication device, which can be a first AP MLD or a chip in the first AP MLD, such as a Wi-Fi chip, or it can be a first AP in the first AP MLD, comprising: a processing unit, configured to generate unicast service indication information, the unicast service indication information being 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, the second AP MLD being an AP MLD belonging to a non-transmitting AP in a multi-BSSID set where the first AP is located; and a transceiver unit, configured to transmit the unicast service indication information on a first link, the first link being the working link of the first AP.

Optionally, the reporting AP can refer to the AP that sends the management frame, which carries information about multiple APs in the APMLD set that coexists with the reporting AP. This management frame can be, for example, a beacon frame or a probe response frame.

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

Optionally, the AID allocation information described above is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

Optionally, the aforementioned transceiver unit is also configured to receive an association request frame, which is used to request the establishment of a multi-link association with the first AP MLD.

Fourthly, this application provides a communication device, which can be a Non-AP MLD or a chip in a Non-AP MLD, such as a Wi-Fi chip, or it can be a first STA in a Non-AP MLD, comprising: a transceiver unit, configured to receive unicast service indication information on a first link where the first STA operates, the unicast service indication information being 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, the second AP MLD being an AP MLD that is not a transmission AP in a multi-BSSID set where the first AP is located; and a processing unit, configured to determine whether the Non-AP MLD has downlink unicast service based on the received unicast service indication information.

Optionally, the reporting AP can refer to the AP that sends the management frame, which carries information about multiple APs in the APMLD set that coexists with the reporting AP. This management frame can be, for example, a beacon frame or a probe response frame.

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

Optionally, the AID allocation information described above is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

Optionally, the above processing unit is further configured to generate an association request frame; the above transceiver unit is further configured to send the association request frame, which is used to request the establishment of a multi-link association with the first AP MLD.

In any of the above implementations, one bit of the unicast service indication information corresponds to one Non-AP MLD, and this one bit is used to indicate whether the corresponding Non-AP MLD has downlink unicast service. Here, Non-AP MLDs include Non-AP MLDs associated with the first AP MLD and Non-AP MLDs associated with the second AP MLD.

In any of the above implementations, one bit of the unicast service indication information corresponds to an associated identifier (AID), and this one bit is used to indicate whether the Non-AP MLD identified by the corresponding AID has downlink unicast service. Here, Non-AP MLDs include Non-AP MLDs associated with the first AP MLD and Non-AP MLDs associated with the second AP MLD.

Optionally, the aforementioned unicast service indication information is carried in a portion of the virtual bitmap field of the traffic indication map (TIM) element.

This solution uses partial bits from the virtual bitmap field in the TIM element to indicate whether there is downlink unicast service in the Non-AP MLD associated with the reporting AP's MLD and the Non-AP MLD associated with each second AP MLD. This can be achieved without changing the frame format of the TIM element, allowing one AP MLD to help another AP MLD indicate whether there is downlink unicast service in the Non-AP MLD associated with that other AP MLD, thus improving the flexibility of downlink unicast service notification.

In any of the above implementations, the associated identifier (AID) corresponding to each bit in the unicast service indication information is different. This avoids AID ambiguity when indicating whether there is downlink unicast service in the Non-AP MLD.

In any of the above implementations, 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 there is a downlink unicast service on the Non-AP MLD associated with the first AP MLD, and a TIM block corresponding to the second AP MLD is used to indicate whether there is a downlink unicast service on the Non-AP MLD associated with the second AP MLD.

Optionally, the unicast service indication information mentioned above also includes an index of the second AP MLD, which corresponds one-to-one with the TIM block corresponding to the second AP MLD.

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

Optionally, the associated identifier AID corresponding to each bit in the above TIM block is different.

Optionally, the AID space used by the first AP MLD to allocate AIDs to its associated Non-AP MLDs and the AID space used by the second AP MLD to allocate AIDs to its associated Non-AP MLDs are independent of each other. Here, AID space can also refer to the set of AIDs to be allocated.

This solution provides TIM indications for different AP MLDs in blocks, which can avoid ambiguity in the AIDs of Non-AP MLDs associated with different AP MLDs.

Fifthly, this application provides a method for assigning an associated identifier (AID) to a multi-link device, applicable to any AP in an AP MLD. The method includes: AP _i of the AP MLD generating and sending AID assignment information, the AID assignment information carrying an AID assigned to a 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 any AP MLD within a set of AP MLDs co-located with AP _i , or the target AP MLD is any AP MLD within a set circle containing the set of AP MLDs co-located with AP _i. AP _i is any AP in the AP MLD.

Optionally, the AID allocation information described above is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

Optionally, if the target AP MLD is any AP MLD within the set of AP MLDs co-located with AP _i , then both the target AP MLD and the target AP MLD belong to the set of AP MLDs co-located with AP _i . If the target AP MLD is any AP MLD within the set circle containing the set of AP MLDs co-located with AP _i , then both the target AP MLD and the target AP MLD belong to the set circle containing the set of AP MLDs co-located with AP _i . This set circle includes the set of AP MLDs co-located with AP _i , and the set of AP MLDs co-located with AP _i from the set of AP MLDs co-located with AP i, except for AP _i .

Optionally, before sending the association response frame, the method further includes: AP _i of the AP MLD receiving an association request frame, which is used to request the establishment of a multi-link association with the AP MLD.

This solution considers that the AID of the Non-AP MLD associated with AP _i and the AID of the Non-AP MLD associated with the target AP MLD should be unique, i.e., they should be different from each other. This avoids ambiguity in AID when indicating whether a Non-AP MLD has downlink unicast services.

Sixthly, this application provides an AID allocation method for a multi-link device, applied to any STA of a Non-AP MLD. The AID allocation method for the multi-link device includes: the STA of the Non-AP MLD receiving AID allocation information and parsing the AID allocation information to obtain an AID allocated to the Non-AP MLD carried in the AID allocation information. This AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is any AP MLD within a set of AP MLDs co-located with AP _i , or the target AP MLD is any AP MLD within a set circle containing the set of AP MLDs co-located with AP _i . AP _i is any AP in the AP MLD.

Optionally, the AID allocation information described above is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

Optionally, if the target AP MLD is any AP MLD within the set of AP MLDs co-located with AP _i , then both the target AP MLD and the target AP MLD belong to the set of AP MLDs co-located with AP _i . If the target AP MLD is any AP MLD within the set circle containing the set of AP MLDs co-located with AP _i , then both the target AP MLD and the target AP MLD belong to the set circle containing the set of AP MLDs co-located with AP _i . This set circle includes the set of AP MLDs co-located with AP _i , and the set of AP MLDs co-located with AP _i from the set of AP MLDs co-located with AP i, except for AP _i .

Optionally, before the STA of the Non-AP MLD receives the association response frame, the method further includes: the STA of the Non-AP MLD generating and sending an association request frame, which is used to request the establishment of a multi-link association with the AP MLD.

Seventhly, this application provides a communication device, which can be an AP MLD or a chip within an AP MLD, such as a Wi-Fi chip, comprising: a processing unit for generating AID allocation information, wherein the AID allocation information carries an AID allocated to a Non-AP MLD, the AID being different from the AID of a Non-AP MLD associated with a target AP MLD, the target AP MLD being any AP MLD within a set of AP MLDs co-located with AP _i , or the target AP MLD being any AP MLD within a set circle containing the set of AP MLDs co-located with AP _i ; and a transceiver unit for transmitting the associated response frame. AP _i is any AP in the AP MLD.

Optionally, the AID allocation information described above is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

Optionally, if the target AP MLD is any AP MLD within the set of AP MLDs co-located with AP _i , then both the target AP MLD and the target AP MLD belong to the set of AP MLDs co-located with AP _i . If the target AP MLD is any AP MLD within the set circle containing the set of AP MLDs co-located with AP _i , then both the target AP MLD and the target AP MLD belong to the set circle containing the set of AP MLDs co-located with AP _i . This set circle includes the set of AP MLDs co-located with AP _i , and the set of AP MLDs co-located with AP _i from the set of AP MLDs co-located with AP i, except for AP _i .

Optionally, the aforementioned transceiver unit is also configured to receive an association request frame, which is used to request the establishment of a multi-link association with the APMLD.

Eighthly, this application provides a communication device, which can be a chip in a Non-AP MLD or a Non-APMLD, such as a Wi-Fi chip, comprising: a transceiver unit for receiving AID allocation information from an AP in an AP MLD; and a processing unit for parsing the received AID allocation information to obtain an AID allocated to the Non-APMLD carried in the AID allocation information, wherein the AID is different from the AID of a Non-AP MLD associated with a target AP MLD, and the target AP MLD is any AP MLD within a set of AP MLDs co-located with AP _i , or the target AP MLD is any AP MLD within a set circle containing the set of AP MLDs co-located with AP _i . AP _i is any AP in the AP MLD.

Optionally, the AID allocation information described above is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

Optionally, if the target AP MLD is any AP MLD within the set of AP MLDs co-located with AP _i , then both the target AP MLD and the target AP MLD belong to the set of AP MLDs co-located with AP _i . If the target AP MLD is any AP MLD within the set circle containing the set of AP MLDs co-located with AP _i , then both the target AP MLD and the target AP MLD belong to the set circle containing the set of AP MLDs co-located with AP _i . This set circle includes the set of AP MLDs co-located with AP _i , and the set of AP MLDs co-located with AP _i from the set of AP MLDs co-located with AP i, except for AP _i .

Optionally, the above-mentioned processing unit is further configured to generate an association request frame; the above-mentioned transceiver unit is further configured to send the association request frame, which is used to request the establishment of a multi-link association with the AP MLD.

Ninthly, this application provides a communication device, specifically a first AP MLD or a first AP within a first AP MLD, including a processor and a transceiver. The processor is configured to support the first AP MLD in performing the corresponding functions described in the method of the first aspect. The transceiver is used to support communication between the first AP MLD and a non-access point multilink device (also called a site multilink device), sending information, frames, data packets, or instructions involved in the above method to the site multilink device. The first AP MLD may further include a memory coupled to the processor, which stores necessary program instructions and data of the first AP MLD.

Specifically, the processor is used to generate unicast service indication information, which indicates whether there is downlink unicast service in the Non-AP MLD associated with the first AP MLD and whether there is downlink unicast service in the Non-AP MLD associated with the second AP MLD, wherein the second AP MLD is the AP MLD that is not the transmission AP 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, wherein the first link is the working link of the first AP.

In a tenth aspect, this application provides a communication apparatus, specifically a first STA in a non-access point multi-link device (also known as a site multi-link device) or a Non-AP MLD, including a processor and a transceiver. The processor is configured to support the site multi-link device in performing the corresponding functions in the method described in the second aspect above. The transceiver is used to support communication between the site multi-link device and the first AP MLD, receiving information, frames, data packets, or instructions involved in the above method from the first AP MLD. The site multi-link device may further include a memory coupled to the processor, which stores necessary program instructions and data for the site multi-link device.

Specifically, the transceiver is used to receive unicast service indication information on the first link where the first STA is operating. 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 the second AP MLD has downlink unicast service. The second AP MLD is an AP MLD that is not a transmission AP in the multi-BSSID set where the first AP is located. The processor is used to determine whether the Non-AP MLD has downlink unicast service based on the received unicast service indication information.

Eleventhly, this application provides a communication device, specifically an AP MLD or an AP _i of an AP MLD, including a processor and a transceiver. The processor is configured to support the AP MLD in performing the corresponding functions of the method described in the fifth aspect above. The transceiver is used to support communication between the AP MLD and a non-access point multilink device (also known as a site multilink device), sending information, frames, data packets, or instructions involved in the above method to the site multilink device. The AP MLD may also include a memory coupled to the processor, which stores necessary program instructions and data of the AP MLD.

Specifically, the processor generates AID allocation information, which carries an AID assigned to a Non-AP MLD. This AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is any AP MLD within the set of AP MLDs co-located with AP _i , or any AP MLD within the set circle containing the set of AP MLDs co-located with AP _i . The transceiver transmits this AID allocation information. This AID allocation information is carried in the associated response frame. Understandably, this AID allocation information can also be carried in other frames. AP _i is any AP in the AP MLD.

Optionally, the transceiver described above is also used to receive association request frames, which are used to request the establishment of a multi-link association with the AP MLD.

In a twelfth aspect, this application provides a communication apparatus, specifically a non-access point multilink device (also known as a site multilink device), including a processor and a transceiver. The processor is configured to support the site multilink device in performing the corresponding functions of the method described in the sixth aspect above. The transceiver is used to support communication between the site multilink device and the AP MLD, receiving information, frames, data packets, or instructions involved in the above method from the AP MLD. The site multilink device may further include a memory coupled to the processor, which stores necessary program instructions and data of the site multilink device.

Specifically, the transceiver receives AID allocation information; the processor parses the received AID allocation information to obtain the AID assigned to the Non-AP MLD carried in the AID allocation information. This AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is any AP MLD within the set of AP MLDs co-located with AP _i , or the target AP MLD is any AP MLD within the set circle containing the set of AP MLDs co-located with AP _i . The AID allocation information is carried in the associated response frame. Understandably, the AID allocation information can also be carried in other frames. AP _i is any AP in the AP MLD.

Optionally, the processor is further configured to generate an association request frame; the transceiver is further configured to send the association request frame, which is used to request the establishment of a multi-link association with the AP MLD.

In a thirteenth aspect, this application provides a chip or chip system, including an input/output interface and a processing circuit. The processing circuit generates unicast service indication information, which indicates 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, wherein the second AP MLD is an AP MLD belonging to a non-transmitting AP in a multi-BSSID set where the first AP is located; the input/output interface is used to send the unicast service indication information on a first link, which is the working link of the first AP.

In one possible design, the input/output interface is used to receive unicast service indication information on the first link. This unicast service indication information indicates whether a Non-AP MLD associated with the first AP MLD has downlink unicast service and whether a Non-AP MLD associated with the second AP MLD has downlink unicast service. The second AP MLD is an AP MLD that is not a transmission AP in the multi-BSSID set where the first AP is located. The processing circuit is used to determine whether the Non-AP MLD has downlink unicast service based on the received unicast service indication information.

In a fourteenth aspect, this application provides a chip or chip system, including an input/output interface and a processing circuit. The processing circuit generates AID allocation information, which carries an AID assigned to a Non-AP MLD. This AID is different from the AID of a Non-AP MLD associated with a target AP MLD. The target AP MLD is any AP MLD within a set of AP MLDs co-located with the reporting AP, or the target AP MLD is any AP MLD within a set circle containing the set of AP MLDs co-located with the reporting _AP . The input/output interface is used to send the associated response frame.

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 the AID carried in the AID allocation information 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 any AP MLD in the set of AP MLDs co-located with the reporting AP, or the target AP MLD is any AP MLD in the set circle of AP MLDs co-located with the AP _i .

In a fifteenth aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the unicast service indication method applicable to multiple links as described in the first or second aspect above.

In a sixteenth aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the AID allocation method for multi-link devices described in the fifth or sixth aspect above.

In a seventeenth aspect, this application provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the unicast service indication method applicable to multiple links as described in the first or second aspect above.

In an eighteenth aspect, this application provides a computer program product containing instructions that, when run on a computer, causes the computer to execute the AID allocation method for multi-link devices described in the fifth or sixth aspect above.

Implementing the embodiments of this application can help certain APs or all APs in a portion of the AP MLD to indicate whether there is downlink unicast service with their associated site multilink device, thereby assisting the site multilink device in correctly receiving downlink unicast service.

Attached Figure Description

To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

Figure 1 is a schematic diagram of the structure of an AP MLD and a Non-AP MLD provided in an embodiment of this application;

Figure 2 is a schematic diagram of a frame format of a TIM element provided in an embodiment of this application;

Figure 3 is a schematic diagram of a frame format with multiple BSSID elements provided in an embodiment of this application;

Figure 4a is a schematic diagram of the structure of a communication system 100 provided in an embodiment of this application;

Figure 4b is a schematic diagram of the structure of a communication system 200 provided in an embodiment of this application;

Figure 4c is a schematic diagram of the structure of a communication system 300 provided in an embodiment of this application;

Figure 5 is a schematic diagram of the architecture of multiple BSSID sets provided in the embodiments of this application;

Figure 6 is a schematic flowchart of a unicast service indication method applicable to multiple links provided in an embodiment of this application;

Figure 7 is a schematic diagram of a partial virtual bitmap field provided in an embodiment of this application;

Figure 8 is a partial frame format diagram of a new element provided in an embodiment of this application;

Figure 9 is a schematic flowchart of the AID allocation method for Non-AP MLD provided in the embodiments of this application;

Figure 10a is a schematic diagram of a set of AP MLDs co-located with APs provided in an embodiment of this application;

Figure 10b is another schematic diagram of the AP MLD set co-located with AP provided in an embodiment of this application;

Figure 10c is another schematic diagram of the AP MLD set co-located with AP provided in the embodiments of this application;

Figure 11 is a schematic diagram of a frame format of the AID element provided in an embodiment of this application;

Figure 12 is another schematic flowchart of a unicast service indication method applicable to multiple links provided in an embodiment of this application;

Figure 13 is a schematic diagram of the structure of the communication device 1 provided in an embodiment of this application;

Figure 14 is a schematic diagram of the structure of the communication device 2 provided in an embodiment of this application;

Figure 15 is a schematic diagram of the structure of the communication device 3 provided in an embodiment of this application;

Figure 16 is a schematic diagram of the structure of the communication device 4 provided in an embodiment of this application;

Figure 17 is a schematic diagram of the structure of the communication device 1000 provided in an embodiment of this application.

Detailed Implementation

The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

To better understand the unicast service indication method and related apparatus applicable to multiple links disclosed in the embodiments of this application, the relevant concepts of the embodiments of this application are first described.

1. Multi-link devices

The wireless communication system applicable to the embodiments of this application can be a wireless local area network (WLAN) or a cellular network. The unicast service indication method can be implemented by a communication device in the wireless communication system or a chip or processor in the communication device. The communication device can be a wireless communication device that supports parallel transmission across multiple links, for example, called 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.

A multi-link device includes one or more affiliated STAs, which are logically connected sites that can operate on a single link. The affiliated site can be an access point (AP) or a non-access point station (Non-AP STA). For ease of description, this application refers to a multi-link device with an affiliated AP as a multi-link AP, a multi-link AP device, or an AP multi-link device (AP MLD), and a multi-link device with an affiliated Non-AP STA as a multi-link Non-AP, a multi-link Non-AP device, or a Non-AP multi-link device (Non-AP MLD). For ease of description, "a multi-link device includes affiliated sites" is also briefly described in this embodiment as "a multi-link device includes sites."

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 one link, but multiple logical STAs are allowed to operate on the same link.

Multilink devices can implement wireless communication by following the 802.11 series of protocols. For example, they can follow extremely high throughput (EHT) stations or 802.11be-based or compatible stations to communicate with other devices. Of course, other devices can be multilink devices or not.

For example, the multi-link device in the embodiments of this application can be a single-antenna device or a multi-antenna device. For instance, it can be a device with two or more antennas. The embodiments of this application do not limit the number of antennas included in the multi-link device. In the embodiments of this 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 packets to be transmitted on different links; it can also disallow services of the same access type to be transmitted on different links, but allow services of different access types to be transmitted on different links.

For example, a multi-link device is a device with wireless communication capabilities. This device can be a complete machine or a chip or processing system installed in a complete machine. The device with these chips or processing systems installed can implement the methods and functions of the embodiments of this application under the control of these chips or processing systems. For example, the Non-AP MLD in the embodiments of this application has wireless transceiver capabilities, can support the 802.11 series protocols, and can communicate with AP MLDs or other Non-AP MLDs or single-link devices. For example, STA MLD is any user communication device that allows users to communicate with APs and thus with WLANs. For example, a Non-AP MLD can be a user device that can connect to the Internet, such as a tablet, desktop, laptop, notebook computer, Ultra-mobile Personal Computer (UMPC), handheld computer, netbook, Personal Digital Assistant (PDA), or mobile phone, or an IoT node in the Internet of Things, or an in-vehicle communication device in the Internet of Vehicles. A Non-AP MLD can also be a chip and processing system in the above-mentioned terminals.

The AP MLD in this application embodiment is a device that provides services for Non-AP MLD 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, relay stations, etc. Of course, the AP MLD can also be the chip and processing system in these various forms of devices, thereby realizing the methods and functions of the embodiments of this application. Furthermore, multi-link devices can support high-speed, low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can be applied to more scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-checkout machines, self-ordering machines, etc.). This application embodiment does not impose special restrictions on the specific forms of Non-AP MLD and APMLD; these are merely illustrative examples. The 802.11 protocol can be a protocol that supports or is compatible with 802.11be.

The frequency bands in which multi-link devices can operate may include, but are not limited to: sub 1GHz, 2.4GHz, 5GHz, 6GHz and high frequency 60GHz.

For example, the multi-link device in this application embodiment can be a single-antenna device or a multi-antenna device. For instance, the multi-link device in this application embodiment can be a device with two or more antennas. This application embodiment does not limit the number of antennas included in the multi-link device. Referring to Figure 1, Figure 1 is a structural schematic diagram of an AP MLD and a Non-AP MLD provided in an embodiment of this application. Figure 1 shows a structural schematic 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 portions of the AP MLD and Non-AP MLD.

2. Link Identifier

A link identifier represents a station operating on a link. In other words, if there are more than one station on a link, there will be more than one link identifier to represent them. The link mentioned below may also refer to the station operating on that link.

During data transmission, AP MLDs and Non-AP MLDs can use link identifiers to identify a link or stations on a link. Before communication, AP MLDs and Non-AP MLDs can negotiate or communicate the correspondence between link identifiers and links or stations on links. Therefore, during data transmission, it is not necessary to transmit a large amount of signaling information to indicate links or stations on links; carrying the link identifier is sufficient, reducing signaling overhead and improving transmission efficiency.

In one example, the management frame sent by the AP MLD when establishing a basic service set (BSS), such as a beacon frame, carries an element that includes multiple link identification information fields. The link identification information fields indicate the correspondence between a link identifier and a station operating on the link corresponding to that link identifier. In addition to the link identifier, the link identification information fields also include one or more of the following: Media Access Control (MAC) address, operation set, and channel number. One or more of these can identify a link. For the AP, the AP's MAC address is also its BSSID (basic service set identifier). In another example, during multi-link device association, the AP MLD and Non-AP MLD negotiate multiple link identification information fields. Multi-link device association refers to the association of one AP of AP MLD with one STA of Non-AP MLD. This association can help multiple STAs of Non-AP MLD to be associated with multiple APs of AP MLD respectively, where one STA is associated with one AP.

In subsequent communications, the AP MLD or Non-AP MLD uses a link identifier to represent a station within the Non-AP MLD. The link identifier can also represent one or more attributes of the station, including its MAC address, the operating set, and the channel number. The MAC address can be replaced with the association identifier of the associated AP MLD. Optionally, if multiple stations operate on a single link, the link identifier (a numeric ID) represents not only the operating set and channel number of the link but also the identifier of the stations operating on that link, such as the station's MAC address or association identifier (AID).

3. Business Indicator Bitmap Elements

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 Figure 2, which is a schematic diagram of the frame format of a TIM element according to an embodiment of this application, the frame format of the TIM element field includes:

Element Identifier (ID) field: Used to identify the element shown in Figure 2 as a TIM element.

Length field: Used to indicate the length of the TIM element. The total length after calculating 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.

The DTIM count field indicates how many TIM beacon frames are remaining before the next DTIM beacon frame arrives, even for the current beacon frame carrying this TIM element. In other words, the DTIM count field is a count value that changes. When the value of the DTIM count field is 0, it indicates that the current beacon frame is a DTIM beacon frame; when the value of the DTIM count field is not 0 or is non-zero, it indicates that the current beacon frame is a TIM beacon frame.

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

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

Partial Virtual Bitmap: Each bit in the partial virtual bitmap field corresponds to an association identifier (AID), used to indicate whether the site corresponding to that AID has unicast services. Alternatively, each bit in the partial virtual bitmap field corresponds to a multicast AID, used to indicate whether a group of sites corresponding to the multicast AID has downlink services. The partial virtual bitmap field is a subset of the traffic indication virtual bitmap field, which is 251 bytes long and used to indicate whether the sites corresponding to AID 0 to AID 2007 have downlink services.

The element ID field, length field, DTIM count field, DTIM period field, and bitmap control field each occupy 1 byte.

4. Multiple Basic Service Set Identifier (BSSID set)

A Multiple Basic Service Set (BSSID) set can be understood as a collection of cooperating Access Points (APs). All cooperating APs use the same operating set, channel number, and antenna interface. Within this multiple BSSID set, only one AP has a transmitted BSSID; the others have non-transmitted BSSIDs. Information about the multiple BSSID set (i.e., the multiple BSSID elements) is carried in beacon frames, probe response frames, or neighbor reports sent by APs with transmitted BSSIDs. The BSSID information for APs with non-transmitted BSSIDs is derived by the site from the multiple BSSID elements in the aforementioned beacon frames, probe response frames, or neighbor reports. The BSSID of an AP with a non-transmitted BSSID is calculated by combining the BSSID of the AP transmitting the BSSID with the BSSID Index field in the Multiple BSSID-Index element of its non-transmitted BSSID profile. For details, please refer to the Draft 802.11REVmd_D3.0 protocol.

This set of multiple BSSIDs can also be understood as being composed of multiple APs. Each AP manages one BSS, and different APs can have different SSIDs and permissions, such as security mechanisms or transmission opportunities.

In the multiple BSSID set, only the AP with the BSSID "Transmitted BSSID" can send beacon frames and probe response frames, while the AP with the BSSID "Non-transmitted BSSID" does not send beacon frames. Therefore, if the probe request frame sent by the STA is to an AP with the BSSID "Non-transmitted BSSID" in the multiple BSSID set, then the AP with the BSSID "Transmitted BSSID" in the multiple BSSID set will respond by sending a probe response frame.

In a set of multiple APs with multiple BSSIDs, one AP's BSSID 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 APs with the Non-Transmitted BSSIDs can be called Non-Transmitted APs.

The beacon frame transmitted by the transmitting AP may include multiple BSSID elements. The frame format of the multiple BSSID elements is shown in Figure 3, which is a schematic diagram of the frame format of multiple BSSID elements provided in an embodiment of this application. The multiple BSSID elements include an element ID field, a length field, a maximum BSSID indicator field, and optional sub-element fields. The maximum BSSID indicator field indicates the maximum number N of BSSIDs contained in the multiple BSSID set. The optional sub-element fields include information about the BSSIDs of APs with non-transmitted BSSIDs.

The maximum allowed number of APs in a multi-BSSID set is 2^ ⁿ , where n is the value indicated by the MaxBSSIDIndicator field in the multi-BSSID element shown in Figure 3, and N = 2^ ⁿ . Therefore, bits 1 to 2 ^{^n} -1 of the service indication virtual bitmap field can be assigned to the APs with non-transmitted BSSIDs in this multi-BSSID set to indicate whether the APs with NonTxBSSIDs (identifiers) 1 to 2 ^{^n} -1 have multicast services. The value of NonTxBSSID is equal to the value of the BSSID Index field in the Multiple BSSID-Index element of the Non-transmitted BSSID profile in the multi-BSSID element. The Non-transmitted BSSID profile is in the optional sub-element field.

Although the embodiments of this application are primarily illustrated using a network deploying IEEE 802.11 as an example, those skilled in the art will readily understand that the various aspects of this application can be extended to other networks employing various standards or protocols, such as BLUETOOTH, high-performance radio LAN (HIPERLAN) (a wireless standard similar to IEEE 802.11, primarily used in Europe), and wide area networks (WANs), wireless local area networks (WLANs), personal area networks (PANs), or other networks now known or developed in the future. Therefore, regardless of the coverage area and wireless access protocol used, the various aspects provided in this application can be applied to any suitable wireless network.

Referring to Figure 4a, Figure 4a is a schematic diagram of the structure of a communication system 100 provided in an embodiment of this application. Figure 4a uses a wireless local area network as an example to illustrate a communication system 100 applied in an embodiment of this application. The communication system 100 includes: station 101 and station 102. Station 101 can communicate with station 102 using multiple links, thereby improving throughput. Station 101 can be a multi-link device, and station 102 can be a single-link device or a multi-link device, etc. 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 another scenario, site 101 is an AP MLD, and site 102 is an AP MLD or AP; in yet another scenario, site 101 is a Non-AP MLD, and site 102 is a Non-AP MLD or STA (e.g., a single-link site). Of course, this wireless LAN may also include other devices. The number and types of devices illustrated in Figure 4a are merely exemplary.

Referring to Figure 4b, which is a schematic diagram of a communication system 200 provided in an embodiment of this application. Referring to Figure 4c, which is a schematic diagram of a communication system 300 provided in an embodiment of this application. Figures 4b and 4c respectively show schematic diagrams of the communication systems 200 and 300. The communication systems 200 and 300 are illustrated using a wireless local area network (WLAN) where multi-link devices communicate with other devices through multiple links.

Specifically, Figure 4b illustrates a scenario of communication between an AP MLD and a Non-AP MLD. The AP MLD includes AP1 and AP2, and the Non-AP MLD includes STA1 and STA2. The AP MLD and the Non-AP MLD communicate in parallel using Link 1 and Link 2.

Figure 4c illustrates a scenario where AP MLD601 communicates with Non-AP MLD602, Non-AP MLD603, and STA604. AP MLD601 includes subordinate AP601-1 to AP601-3; Non-AP MLD602 includes three subordinate STA602-1, STA602-2, and STA602-3; Non-AP MLD603 includes two subordinate STA603-1 and STA603-2; STA604-1 and STA604 are single-link devices. AP MLD601 can communicate with Non-AP MLD602 using links 1, 2, and 3 respectively; communicate with Non-AP MLD603 using links 2 and 3; and communicate with STA604 using link 1. In one example, STA604 operates in the 2.4 GHz band; in Non-AP MLD603, STA603-1 operates in the 5 GHz band, and STA603-2 operates in the 6 GHz band; in Non-AP MLD602, STA602-1 operates in the 2.4 GHz band, STA602-2 operates in the 5 GHz band, and STA602-3 operates in the 6 GHz band. AP601-1, operating in the 2.4 GHz band in AP MLD601, can transmit uplink or downlink data with STA604 and STA602-1 in Non-AP MLD602 via Link 1. AP601-2, operating in the 5GHz band of AP MLD601, can transmit uplink or downlink data with STA603-1, operating in the 5GHz band of Non-AP MLD 603, via link 2. It can also transmit uplink or downlink data with STA602-2, operating in the 5GHz band of Non-AP MLD602, via link 2. AP601-3, operating in the 6GHz band of AP MLD601, can transmit uplink or downlink data with STA602-3, operating in the 6GHz band of Non-AP MLD602, via link 3. It can also transmit uplink or downlink data with STA603-2 in the Non-AP MLD via link 3.

Understandably, Figure 4b only shows that the AP MLD supports two frequency bands, and Figure 4c only illustrates that the AP MLD601 supports three frequency bands (2.4GHz, 5GHz, 6GHz), with each frequency band corresponding to one link. The AP MLD601 can operate on one or more links from link 1, link 2, or link 3. On the AP side or STA side, the link here can also be understood as the station operating on that link. In practical 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. This application embodiment does not limit this.

Referring to Figure 5, Figure 5 is a schematic diagram of the architecture of multiple BSSID sets provided in the embodiments of this application. That is, each AP MLD shown in Figure 5 is a collocated AP MLD set.

Among them, 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. Assuming that APs with MAC address identifiers ending in 'x' are Transmitted BSSID APs, APs with MAC address identifiers ending in 'y' or 'z' are Non-Transmitted BSSID APs, and APs with MAC address identifiers ending only in numbers are ordinary APs, which are APs that do not belong to a multi-BSSID set. For example, in Multiple BSSID set 1, the Transmitted BSSID AP is AP1x with MAC address BSSID_1x, and the Non-Transmitted BSSID AP in Multiple BSSID set 1 is AP1y with MAC address BSSID_1y; in Multiple BSSID set 2, the Transmitted BSSID AP is AP2x with MAC address BSSID_2x, and the Non-Transmitted BSSID AP in Multiple BSSID set 2 includes AP2y with address BSSID_2y and AP2z with MAC address BSSID_2z.

The AP MLD set sharing a location with the reporting AP includes the following APs: The reporting AP is the AP that sends a management frame carrying information about several APs, such as a beacon frame or a probe response frame. The reporting APs include both transport APs and regular APs in the BSSID set. The AP MLD set sharing a location with the reporting AP includes the following APs:

(1) All APs belonging to the same AP MLD as the reporting AP, or all APs in the AP MLD where the reporting AP is located.

(2) All APs in the AP MLD where the non-transfer AP is located in the same multi-BSSID set as the reporting AP (or transmission AP); or, all APs in the AP MLD where the non-transfer AP is located in the multi-BSSID set where the reporting AP (or transmission AP) is located.

(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 set of multiple BSSIDs as an AP in the AP MLD where the reporting AP is located; 2) No AP in the AP MLD works on the same link as the reporting AP.

Optionally, in one implementation, an AP MLD includes only one AP.

Optionally, the reporting AP can be a regular AP in the AP MLD (for example, AP3 with MAC address BSSID_3 and AP5 with MAC address BSSID_5 in Figure 5) or a transmission AP in a set of multiple BSSIDs, capable of sending the unicast service indication information described in this application.

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

(1) All APs that are in the same AP MLD1 as AP1x, namely AP1x, AP2y, and AP3;

(2) All APs in AP MLD3 that are non-transmission APs (i.e., AP1y) in the same multi-BSSID set 1 as AP1x are: AP1y, AP2z, and AP4y.

(3) The AP MLD that satisfies conditions 1) and 2) in Figure 5 is AP MLD2, which includes AP2x and AP4x. In AP MLD2, AP2x and AP2y in AP MLD1 are in the same multi-BSSID set 2, and there is no AP in AP MLD2 that is in the same link as AP1x.

Because in a set of multiple BSSIDs, only APs with the BSSID "Transmitted" 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 certain AP MLD are non-transmitted APs (e.g., AP MLD3 in Figure 5), and because the TIM element is carried in the beacon frame, this AP MLD cannot indicate whether the non-AP MLD associated with it has downlink unicast service. Furthermore, as shown in Figure 5, AP2y, operating on link 2, is a non-transmitted AP, and the non-AP MLD operating on link 2 cannot receive downlink unicast service notifications sent to it by its associated AP MLD1.

Therefore, embodiments of this application provide a unicast service indication method applicable to multiple links. By carrying downlink unicast service indications of the AP MLD (Multi-Link Device) to which the reporting AP belongs in the signaling sent by the reporting AP, this method can help the AP MLD to which the non-transmission AP belongs to indicate whether its associated Non-AP MLD has downlink unicast service. The technical solution provided by this application will be described in detail below with reference to more accompanying drawings.

One or more APs within an AP MLD need to send buffer unit (BU) indication information to their associated Non-AP MLD. One bit in this BU indication information corresponds to the AID of a Non-AP MLD. A bit in the BU indication information set to "1" indicates that the AP MLD has downlink unicast service to the Non-AP MLD identified by the corresponding AID; conversely, a bit in the BU indication information set to "0" indicates that the AP MLD does not have downlink unicast service to the Non-AP MLD identified by the corresponding AID.

Multi-link association establishment:

During the multi-link association establishment process, a site in a site MLD and an AP in an AP MLD interact through association request/response frames to establish a multi-link association. That is, multiple sites in a site MLD establish associations with multiple APs in an AP MLD one by one. In the association response frames sent by the APs in the AP MLD, each site MLD is assigned an AID, meaning multiple sites in a site MLD share the same AID. Both the AP MLD and the site MLD contain a unique MLD MAC address. This MLD MAC address is used for indexing at higher MAC layers, such as the data source and destination of IP addresses. In other words, data packets sent by each AP in an AP MLD to the same site MLD are shared.

Example 1

Referring to Figure 6, Figure 6 is a schematic flowchart of a unicast service indication method applicable to multiple links provided in an embodiment of this application. This unicast service indication method applicable to multiple links is illustrated using an example implemented in a communication system composed of an AP MLD and a Non-AP MLD. The 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-transport AP in a set of multiple BSSIDs. The Non-AP MLD includes one or more STAs, and the first STA is any STA in the Non-AP MLD. As described above, a multi-link association can be established between the AP MLD and the Non-AP MLD, and both the first AP and the first STA operate on the first link. As shown in Figure 6, this unicast service indication method applicable to multiple links includes, but is not limited to, the following steps:

S101, the first AP of the first AP MLD generates 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. The second AP MLD is the AP MLD that is not the transmission AP in the multi-BSSID set where the first AP is located.

The aforementioned unicast service indication information may be referred to as a unicast service indication field, a unicast service indication, or a buffer unit (BU) indication, and this application embodiment does not impose any limitation. This unicast service indication information may be carried in a TIM element; for example, as shown in Figure 2, the unicast service indication information may be carried in a portion of the virtual bitmap field of the TIM element.

Specifically, the aforementioned first AP is the reporting AP in a multi-BSSID set, and this first AP belongs to the first AP MLD. Therefore, the first AP of the first AP MLD can generate unicast service indication information, which can include two parts. One part is the unicast service indication information of the first AP MLD itself, used to indicate whether there is downlink unicast service in the Non-AP MLD associated with the first AP MLD; the other part is the unicast service indication information of the AP MLD (i.e., the second AP MLD) in the multi-BSSID set where the first AP is located, which is not associated with the transport AP, used to indicate whether there is downlink unicast service in the Non-AP MLD associated with the second AP MLD on the first link where the first AP is working. In other words, this unicast service indication information not only carries the unicast service indication of the reporting AP (first AP) itself, but also carries the unicast service indications of other AP MLDs in the multi-BSSID set where the reporting AP is located that are not associated with the transport AP. It is understood that the unicast service indication information mentioned in this application includes two parts of indication information, which does not mean that these two parts of indication information are in different fields. These two parts of indication information can be in the same field.

Optionally, the Non-AP MLD associated with the MLD where the reporting AP is located may have the following two possibilities: 1) All Non-AP MLDs that have established multi-link associations with the MLD where the reporting AP is located, wherein the Non-AP MLD may be associated with some APs in the MLD where the reporting AP is located, or it may be associated with all APs; or 2) Non-AP MLDs that are associated with the reporting AP in the MLD where the reporting AP is located, wherein the Non-AP MLD may be associated with some APs in the MLD where the reporting AP is located, or it may be associated with all APs, but the some APs or all APs must include the reporting AP.

Optionally, the Non-APMLD associated with the AP MLD belonging to the non-transport AP in the multi-BSSID set where the reporting AP is located may also have the following two possibilities: 1) It may indicate all Non-AP MLDs that establish multi-link association with the AP MLD belonging to the non-transport AP, wherein the Non-AP MLD may establish association with some APs in the AP MLD belonging to the non-transport AP, or it may establish association with all APs; or 2) It may indicate Non-AP MLDs that are associated with the non-transport AP in the AP MLD belonging to the non-transport AP, wherein the Non-AP MLD may establish association with some APs in the AP MLD belonging to the non-transport AP, or it may establish association with all APs, but the part APs or all APs must include the non-transport AP.

For example, taking Figure 5 above as an example, and taking AP1x with MAC address BSSID_1x as the reporting AP, i.e., the first AP is AP1x, then AP MLD1 in Figure 5 is the first AP MLD, and the link where AP1x works is link 1. The unicast service indication information generated by AP1x not only includes the unicast service indication of AP1x to the Non-AP MLD associated with its MLD, but also has the following two possibilities: 1) It can indicate whether all Non-AP MLDs that have established multi-link association with AP MLD1 have downlink unicast services, where the Non-AP MLD can be associated with some APs in AP MLD1 or with all APs; or, 2) It can indicate whether the Non-AP MLDs associated with AP1x of AP MLD1 have downlink unicast services, where the Non-AP MLD can be associated with some APs in AP MLD1 or with all APs, but the part APs or all APs must include AP1x.

The unicast service indication information generated by AP1x also includes the unicast service indication of the non-transmitting AP (i.e., AP1y) associated with AP MLD3 in the multi-BSSID set 1 where AP1x is located, for the Non-AP MLDs associated with it. There are two possibilities: 1) It can indicate whether all Non-AP MLDs associated with AP MLD3 have downlink unicast services; or 2) It can indicate 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 AP1y on link 1 and AP2z on link 2 of AP MLD3; Non-AP MLD2 is associated with AP1y on link 1, AP2z on link 2, and AP4y on link 4 of AP MLD3; and Non-AP MLD3 is associated with AP2z on link 2 and AP4y on link 4 of AP MLD3. In the first embodiment, the unicast service indication of AP MLD3 to its associated Non-AP MLDs includes whether Non-AP MLD1, Non-AP MLD2, and Non-AP MLD3 have downlink unicast services. In the second embodiment, the unicast service indication of AP MLD3 to its associated Non-AP MLDs includes whether Non-AP MLD1 and Non-AP MLD2 have downlink unicast services.

For example, taking AP2x with MAC address BSSID_2x as the reporting AP, i.e., the first AP is AP2x, then AP MLD2 in Figure 5 is the first AP MLD, and the link where AP2x works is link 2. The unicast service indication information generated by AP2x includes not only the unicast service indication of AP2x to the Non-AP MLD associated with its MLD, but also the unicast service indication of AP MLD1 (belonging to AP2y) to its associated Non-AP MLD, and the unicast service indication of AP MLD3 (belonging to AP2z) to its associated Non-AP MLD.

As an optional embodiment, the reporting AP here is not limited to the AP 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 its own unicast service indication for its associated sites to indicate whether the STA associated with this reporting AP has downlink unicast service, may also carry unicast service indications for other AP MLDs (not belonging to the transport AP) in the multi-BSSID set of this link to indicate whether this AP MLD has downlink unicast service for its associated Non-AP MLDs.

S102, the first AP of the first AP MLD sends the unicast service indication information on the first link, which is the working link of the first AP.

In this embodiment of the application, the unicast service indication information can be carried in management frames, such as beacon frames, TIM frames, etc.; or, the unicast service indication information can also be carried in other frames such as data frames or control frames.

S103, the first STA of the Non-AP MLD receives the unicast service indication information on its first working link.

In this context, the first STA can be a site managed by the first AP or a surrounding site. Sites surrounding the first AP include sites managed by the first AP and unassociated sites. The following description uses AP-managed sites as an example to illustrate the unicast service indication method described in this application embodiment. Optionally, the first STA can be any site in a Non-AP MLD, capable of knowing whether its own Non-AP MLD has downlink unicast services. Optionally, both the first STA and the first AP operate on the first link.

S104, the first STA of the Non-AP MLD determines whether the Non-AP MLD has downlink unicast service based on the unicast service instruction information.

Specifically, the first STA of a Non-AP MLD can parse the received unicast service indication information to determine whether the Non-AP MLD has downlink unicast service. If the unicast service indication information indicates that the Non-AP MLD has downlink unicast service to receive, one station in the Non-AP MLD can wake up from its dormant state and become active, sending a PS-Poll (Power Saving Polling) frame to the AP associated with this station to inform the AP MLD that it is awake and can start receiving downlink unicast service. After receiving the PS-Poll frame, the AP can respond with an acknowledgment frame and then send downlink unicast service to the STA. Alternatively, it can send downlink unicast service directly to the STA after receiving the PS-Poll frame. If the unicast service indication information indicates that the Non-AP MLD does not have downlink unicast service, the station of the Non-AP MLD can continue to be dormant or change from an active state to a dormant state.

Understandably, in the 802.11 protocol, a STA typically has two operating modes: a non-energy-saving mode and an energy-saving mode. When a STA operates in non-energy-saving mode, it remains in an active state (also known as a wake-up state) regardless of whether data is being transmitted. When a STA operates in energy-saving mode, it can remain in an active state when transmitting data with the AP; otherwise, it can remain in a doze state to conserve power. Whether a STA is in energy-saving mode can be determined by sending a frame to the AP. In this frame, the energy-saving bit in the frame control field of the MAC header is set to 1 to inform the AP that the STA is in energy-saving mode; if the energy-saving bit is set to 0, it indicates that the STA is in non-energy-saving mode. For each station in a Non-AP MLD (or site MLD), an energy-saving bit is set separately.

As can be seen, in this embodiment, the unicast service indication information sent by the first AP (i.e., the reporting AP) of the AP MLD can not only indicate whether the Non-AP MLD associated with the first AP MLD has downlink unicast service, but also help the second AP MLD indicate whether the Non-AP MLD associated with it has downlink unicast service. The second AP MLD is the AP MLD belonging to the non-transmitting AP in the multi-BSSID set where the first AP is located. This can solve the problem that some APs or all APs in the AP MLD cannot indicate whether the Non-AP MLD associated with them has downlink unicast service (it is worth noting that non-transmitting APs in the multi-BSSID set cannot transmit beacon frames or probe response frames, resulting in the inability to send downlink unicast service indication), enabling the Non-AP MLD associated with these APs to receive downlink unicast service normally. Since in 802.11be, there is a possibility that all APs in an AP MLD are non-transport APs, the solution provided by the embodiments of this application can solve the problem that an AP MLD that is entirely composed of non-transport APs cannot send unicast service indications, thereby increasing the completeness and diversity of downlink service indications.

As an optional embodiment, before step S101 in FIG6, the following steps may be included: S105, the first AP of the first APMLD generates AID allocation information, which carries an AID allocated to the Non-AP MLD, and this 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 to the Non-AP MLD carried in the AID allocation information. This AID allocation information may be carried in the associated response frame. The AID space (or set of AIDs to be assigned) used by the first AP MLD to allocate AIDs to its associated Non-AP MLDs is the same as the AID space (or set of AIDs to be assigned) used by the second AP MLD to allocate AIDs to its associated Non-AP MLDs. Optionally, the AP MLDs belonging to the non-transmitting APs in the multi-BSSID set where the first AP is located may include one or more AP MLDs.

Optionally, before step S105, the method further includes: the first STA of the Non-AP MLD sending an association request frame to the first AP of the first AP MLD, the association request frame being used to request the establishment of a multi-link association with the first AP MLD. Accordingly, the first AP of the first AP MLD receives the association request frame.

Optionally, steps S105 to S106 can also be performed by the second AP in the first AP MLD, and step S107 can 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 an AID allocated to the Non-AP MLD. This 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 to the Non-AP MLD carried in the AID allocation information. Here, the second AP can be any AP in the first AP MLD, and the second STA can be any STA in the Non-AP MLD.

It is evident that by ensuring that the AID of the Non-AP MLD associated with the first AP MLD is different from the AID of the Non-AP MLD associated with the second AP MLD during AID allocation, AID ambiguity can be avoided when indicating unicast services for the aforementioned Non-AP MLDs.

The above content introduces the unicast service indication method applicable to multiple links provided by the embodiments of this application. The specific implementation of the above unicast service indication information will be described below with reference to the unicast service indication method shown in Figure 6.

(a) In the first implementation, one bit of the aforementioned unicast service indication information corresponds to one Non-AP MLD. The value of each bit indicates whether the corresponding Non-AP MLD has downlink unicast service; or, as stated: each bit indicates whether the corresponding Non-AP MLD has downlink unicast service. Here, Non-AP MLD refers to the Non-AP MLD associated with the first AP MLD and the Non-AP MLD associated with the second AP MLD.

(b) In the second implementation, the aforementioned unicast service indication information is carried in a partial virtual bitmap field of the TIM element. Refer to Figure 7, which is a schematic diagram of a partial virtual bitmap field provided in an embodiment of this application. Figure 7 shows the bits of the partial virtual bitmap field in Figure 2. Taking a partial virtual bitmap field of 251 bytes as an example, each byte includes 8 bits. As shown in Figure 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 corresponding AID has 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. Since each bit in the virtual bitmap field of the TIM element corresponds to an AID, an AID also needs to 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 is the same as 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, the associated AID corresponding to each bit of this unicast service indication information should be unique, i.e., each one should be different.

Accordingly, steps S101-S104 in Figure 6 above can be as follows: The first AP of the first AP MLD generates a TIM element, which includes unicast service indication information. This unicast service 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. The second AP MLD is an AP MLD that is not a transmission AP 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, which is the working link of the first AP; The first STA of the Non-AP MLD receives the TIM element on its working first link; The first STA of the Non-AP MLD determines whether the Non-AP MLD has downlink unicast service based on the TIM element.

The TIM element can be carried in beacon frames or in other management frames, such as TIM frames.

Optionally, the beacon frame carrying the TIM element may also include a special field, where each Non-AP MLD receiving downlink unicast service (the presence of downlink unicast service is indicated by the aforementioned TIM element) has a corresponding special field. This special field can be a multi-link identifier bitmap field or multiple link identifier information fields, which are used to indicate one or more links receiving downlink service. One bit in the aforementioned multi-link identifier bitmap field can correspond to one link. When one or more bits are at the first value, such as 1, it indicates that there is downlink service on the one or more links corresponding to that bit; when one or more bits are at the second value, such as 0, it indicates that there is no downlink service on the one or more links corresponding to that bit. The aforementioned multiple link identifier information fields carry identifier information used to distinguish different links. Understandably, in the TIM element, one bit is still used to indicate whether a Non-AP MLD has downlink unicast service.

Optionally, this special field can also be a traffic identifier (TID) bitmap field, which indicates one or more TIDs corresponding to the received downlink unicast service. Then, 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 be on to receive the downlink unicast service notification.

As can be seen, this implementation method uses some bits in the virtual bitmap field of the beacon frame to indicate whether there is downlink unicast service in the Non-AP MLD associated with the reporting AP and the Non-AP MLD associated with the second AP MLD. Without changing the frame format of the TIM element, one AP MLD helps another AP MLD indicate whether there is downlink unicast service in the Non-AP MLD associated with the other AP MLD, which can improve the flexibility of downlink unicast service notification.

(c) Because one bit of the virtual bitmap field in a TIM element can indicate whether a Non-AP MLD has downlink unicast service, if some Non-AP MLDs associated with different AP MLDs in the same AP MLD set have the same AID, these Non-AP MLDs cannot determine 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 to after receiving the beacon frame. For example, taking Figure 5 above as an example, if the reporting AP is AP1x, assuming that Non-AP MLD 1 is associated with AP1x and AP2y of AP1x in AP MLD 1, and the link where AP1x works 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 AID of Non-AP MLD 1 is the same as the AID of Non-AP MLD 2, then if the downlink unicast service indication for Non-AP MLD in the TIM element sent by reporting AP1x is 1, it can only indicate that at least one Non-AP MLD, Non-AP MLD 1 or Non-AP MLD 2, has downlink unicast service, and it is impossible to know which specific Non-AP MLD has downlink unicast service.

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 the TIM block corresponding to the second AP MLD (this TIM block is used to indicate whether the Non-AP MLD associated with the second AP MLD has downlink unicast service). See Figure 8, which is a partial frame format diagram of a new element provided by an embodiment of this application. As shown in Figure 8, (ID), such as MLD ID, or MLD MAC address, is used together to indicate which AP MLD is used to indicate whether its associated Non-AP MLD has downlink unicast service. In each TIM block, one bit can still be used to indicate whether a Non-AP MLD has downlink unicast service. Each bit in the TIM block can correspond to an AID, so an AID also needs to be assigned to each Non-AP MLD.

In another implementation, a separate TIM block corresponding to the second AP MLD can also be a TIM element with the same structure as existing TIM elements. In this case, the TIM element does not include the identifier of the second AP MLD. The TIM element of the second AP MLD can be located in the nontransmitted Profile corresponding to the nontransmitted BSSID in the Multiple BSSID element of the management frame body. The AP corresponding to the nontransmitted BSSID belongs to the second AP MLD, and the AP corresponding to the nontransmitted BSSID is located in the same Multiple BSSID set as the reporting AP mentioned above.

Here, regarding the third implementation method mentioned above, the AIDs of all Non-AP MLDs associated with the same AP MLD should be unique, i.e., each different, to avoid AID ambiguity. Understandably, here, the identifiers of one or more AP MLDs in a new element sent by the reporting AP should be unique, i.e., each different. Or, here, the identifiers of all AP MLDs within the set of AP MLDs co-located with the reporting AP should also be unique, i.e., each 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 of each other; that is, the AID assigned by the first AP MLD to a certain 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, taking Figure 5 as an example, if AP1x is the reporting AP, and AP MLD1 is the first AP MLD. Assuming Non-AP MLD1 is associated with AP MLD1, and Non-AP MLD2 is associated with AP MLD3 (one of which is a second AP MLD), then 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. Understandably, the "AID space" mentioned in this application can refer to the set of AIDs to be assigned.

Optionally, each TIM block may also carry a link bitmap indicator or a TID bitmap indicator. That is, each TIM block may include a special field, which may be a multi-link identifier bitmap field, multiple link identifier information fields, or a TID bitmap field.

Optionally, the new elements mentioned above can be carried in beacon frames or other management frames, such as TIM frames.

As can be seen, this implementation method, by distinguishing the services of different AP MLDs in the TIM instruction and using the AP MLD ID as the index of the TIM block, can avoid ambiguity in the AID of Non-AP MLDs associated with different AP MLDs.

In order to indicate whether there is downlink unicast service in the Non-AP MLD associated with the first AP (i.e., the reporting AP) and the Non-AP MLD associated with the second AP MLD, the first AP of the first AP MLD also needs to assign an AID to each Non-AP MLD before generating unicast service indication information.

Example 2

Embodiment 2 of this application introduces an AID allocation method for multi-link devices, specifically an AID allocation method for Non-AP MLDs.

Understandably, an AID is an identifier (ID) assigned by the AP to a STA after association, and can be considered as the ID of the associated STA. The AID can be used to identify and distinguish each STA associated with the AP, and can also serve as an index in part of the frame structure, pointing to a specific associated STA. If the AP can support multiple BSSIDs, or if the beacon frame or probe response frame can carry multiple BSSID elements, then the maximum number of BSSIDs that the AP can support is 2^ ⁿ , meaning the range of BSSIDs is [1, 2 ^{^n} - 1]. Therefore, the range of AIDs that the AP can assign to a STA is [2 ^{^n} , 2007]. Here, n can be the value of the maximum BSSID indicator field of the BSSID element. If the AP cannot support multiple BSSIDs, or if the beacon frame or probe response frame cannot carry multiple BSSID elements, then the range of AIDs that the AP can assign to a STA is [1, 2007].

Because a small geographical area may contain various types of users or users supporting multiple services, if different access points (APs) are used within this area, channel interference between different APs is unavoidable as each AP attempts to find a channel with little or no interference. Therefore, IEEE 802.11ax proposes virtualizing one AP to cater to different service types or customer types. Thus, a virtual AP can have one BSSID, meaning a single physical AP can have multiple BSSIDs. In other words, some APs can support multiple BSSIDs.

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

Understandably, in practical applications, Embodiment 2 of this application can be implemented alone or in combination with Embodiment 1 described above, and this application does not limit this. Specifically, Embodiment 2 of this application can be implemented in combination with the second implementation method of the unicast service indication information in Embodiment 1 described above.

Understandably, _similarly , the set of AP MLDs co-located with the aforementioned reporting APs includes the following APs:

(1) All APs that belong to the same AP MLD as AP _i , or all APs in the AP MLD where AP i is located.

(2) All APs in the AP MLD where the non-transporting AP in the same multi-BSSID set as AP _i is located; or, all APs in the AP MLD where the non-transporting AP in the multi-BSSID set of AP _i is located.

(3) All APs in the AP MLD that satisfy the following two conditions: 1) At least one AP in the AP MLD is in the same set of multiple BSSIDs as one AP in the AP MLD where AP _i is located; 2) No AP in the AP MLD works on the same link as AP _i .

Referring to Figure 9, which is a schematic flowchart of the AID allocation method for Non-AP MLD provided in this application embodiment, the AID allocation method includes, but is not limited to, the following steps:

S201, AP _i of AP MLD generates AID allocation information, which carries an AID allocated for the Non-AP MLD. This AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is any AP MLD in the collocated AP MLD set with AP _i , or the target AP MLD is any AP MLD in the set circle of the collocated AP MLD set with AP _i .

S202, AP _i of AP MLD sends the AID allocation information to STA of Non-AP MLD. Correspondingly, STA of Non-AP MLD receives the AID allocation information.

In this embodiment, the AP MLD can be the first AP MLD or the second AP MLD of the aforementioned embodiment one, or other AP MLDs. AP _i is any AP in the AP MLD.

Implementation method A: The target AP MLD is any AP MLD in the set of AP MLDs that co-located with AP _i .

In the embodiments of this application, the "set of AP MLDs co-located with AP _i " refers to all AP MLDs (APs included in the AP MLD) co-located with AP _i . Both the AP MLD and the target AP MLD belong to the set of AP MLDs co-located with AP _i .

Specifically, the AID allocation information mentioned above may carry an AID allocated to the Non-AP MLD. This AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is any AP MLD within the collocated AP MLD set co-located with AP _i . In other words, the AID space/set of AIDs to be allocated used by the AP MLD to allocate AIDs to its associated Non-AP MLDs is the same as the AID space/set of AIDs to be allocated used by the target AP MLD to allocate AIDs to its associated Non-AP MLDs. Understandably, the AID allocated to this Non-AP MLD is also different from the AID of the Non-AP MLDs associated with this AP MLD itself.

Optionally, in this embodiment, the Non-AP MLD associated with the AP MLD itself can be understood in two ways: 1) All Non-AP MLDs that have established 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) Non-AP MLDs that are associated with AP _i in the AP MLD, where the Non-AP MLD can be associated with some APs in the AP MLD or with all APs, but the "some APs" or "all APs" must include AP _i . Here, AP _i refers to the AP in the aforementioned AP MLD that has been assigned an AID.

Referring to Figure 10a, which is a schematic diagram of the set of AP MLDs co-located with AP provided in an embodiment of this application. As shown in Figure 10a, assuming AP _i 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. Thus, 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 also different from 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 should be unique, i.e., they should all be different.

Referring to Figure 10b, which is another schematic diagram of the set of AP MLDs co-located with AP provided in an embodiment of this application. As shown in Figure 10b, assuming AP _i 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. Thus, 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, different from the AID of the Non-AP MLD associated with AP MLD2, and different from 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, 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., they should all be different.

Referring to Figure 10c, which is another schematic diagram of the set of AP MLDs co-located with AP provided in an embodiment of this application. As shown in Figure 10c, assuming AP _i 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. Thus, 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, different from the AID of the Non-AP MLD associated with AP MLD2, and different from 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, 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., they should all be different.

Taking Figure 5 as an example again, assuming AP _i is AP4x, the set of APs sharing the same position with AP4x includes: AP2x, AP4y, AP2z, AP1y, AP4z, AP5, AP1x, AP2y, and AP3. Therefore, the set of AP MLDs sharing the same position with AP4x includes: AP MLD1, AP MLD2, AP MLD3, and AP MLD4. Thus, 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, AP MLD2, AP MLD3, and AP MLD4. In other words, 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, i.e., they should all be different.

Implementation method B: The target AP MLD is any APMLD within the set circle containing the set of AP MLDs co-located with AP _i .

In this embodiment of the application, the "circle of AP MLDs sharing a location with AP _i " includes a portion of AP MLDs sharing a location with AP _i , and another portion of AP MLDs sharing a location with other APs besides the set of AP MLDs sharing a location with AP _i . In other words, the set of AP MLDs sharing a location with AP _i , and the set of AP MLDs sharing a location with AP _i but not AP _i , constitute this circle of locations. Here, both the AP MLD and the target AP MLD belong to the circle of locations containing the set of AP MLDs sharing a location with AP _i .

Specifically, the set circle containing the AP MLDs co-located with AP _i is composed of all APs in the AP MLDs co-located with any AP in the AP MLDs co-located with AP _i (where any AP can be understood again as AP _i ). For example, as shown in Figure 5, assuming AP _i is AP1x, the set of AP MLDs co-located with AP1x includes AP MLD1, AP MLD2, and AP MLD3. And since the set of AP MLDs co-located with AP4x includes AP MLD2, AP MLD3, and AP MLD4, the set circle containing the AP MLDs 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 Non-AP MLD associated with AP MLD2, the Non-AP MLD associated with AP MLD3, and the Non-AP MLD associated with AP MLD4.

As shown in Figure 10a, assuming AP _i is AP1x, the set of AP MLDs co-located with AP1x includes AP MLD1 and APMLD3. Since the set of AP MLDs co-located with AP3y includes AP MLD2 and AP MLD3, the set circle containing the set of AP MLDs co-located with AP1x includes AP MLD1, AP MLD2, and APMLD3. 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.

As shown in Figure 10b, assuming AP _i is AP1x, the set of AP MLDs co-located with AP1x includes AP MLD1, AP MLD2, and AP MLD3. The set circle containing the set of AP MLDs 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.

As shown in Figure 10c, assuming AP _i is AP3x, the set of AP MLDs co-located with AP3x includes AP MLD1, AP MLD2, and AP MLD3. The set circle containing the set of AP MLDs 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.

Similarly to implementation method A, in implementation method B, the AID assigned to the Non-AP MLD is also different from the AID of the Non-AP MLD associated with the APMLD itself.

Optionally, for the AID allocation of a single-link STA, the AID assigned by AP _i to the single-link STA on this link (or the AID of the single-link STA associated with AP _i ) is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is any AP MLD in the set of AP MLDs co-located with AP _i , or the target AP MLD is any AP MLD in the set circle where the set of AP MLDs co-located with AP _i is located.

For example, as shown in Figure 10a above, assuming AP _i is AP1x, and AP1x is on link 1, then the AID of a single-link STA on link 1 is different from the AID of the Non-AP MLD associated with AP MLD1, and also different from the AID of the Non-AP MLD associated with AP MLD3. In other words, the AID of a 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, i.e., different from each other. It can also be understood that, apart from the AID of the single-link STA associated with link 1, the AID of a 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.

Alternatively, as shown in Figure 10a above, assuming AP _i is AP1x and AP1x is on link 1, then the AID of a single-link STA on link 1 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.

Understandably, in wireless communication systems, the default identifier of an AP MLD is 0, and multiple APs within an AP MLD share this identifier (i.e., identifier 0). However, multiple APs within an AP MLD can also have different identifiers.

This is understandable because cross-link TIM indication is possible under the same AP MLD. That is, if AP 1 and AP 2 belong to the same AP MLD, AP 1 can carry AP 2's TIM information in its TIM indication, indicating whether AP 2 has service access to its associated Non-AP MLD. Therefore, the AIDs of multiple Non-AP MLDs associated with the same AP MLD are all different.

Therefore, if the same identification system is used, such as the interval [1, 2007], the identifiers of multiple APs of an AP MLD should be unique, i.e., each should be different; the AIDs of multiple Non-AP MLDs associated with the same AP MLD should also be unique, i.e., each should be different. In the embodiments of this application, the "AID assigned to a Non-AP MLD" is a value selected from the remaining space, and should also be unique. Here, the remaining space refers to the set of values remaining in the interval [1, 2007] excluding values that have already been used and are not allowed to be reused.

Optionally, the AID allocation information described above can be carried in the association response frame or in other frames. Specifically, the AID allocated to the Non-AP MLD in the AID allocation information can be carried in the AID element of the association response frame. Refer to Figure 11, which is a schematic diagram of a frame format of the AID element provided in an embodiment of this application. As shown in Figure 11, the AID element includes a 1-byte element identifier field, a 1-byte length field, and a 2-byte AID field.

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

S203, the STA of the Non-AP MLD parses the received associated response frame to obtain the AID carried in the associated response frame.

Optionally, before step S201, the method further includes step S204, where the STA of the Non-AP MLD generates an association request frame; and step S205, where the STA of the Non-AP MLD sends an association request frame to AP _i of the AP MLD, the association request frame being used to request the establishment of a multi-link association with the AP MLD. Correspondingly, AP _i of the AP MLD receives the association request frame. This association request frame may carry the link identifier of each STA of the Non-AP MLD and information about each STA.

Optionally, after receiving the association request frame, AP _i of the AP MLD can send an acknowledgment frame to the STA of the Non-AP MLD. This acknowledgment frame is used to confirm that AP _i of the AP MLD has received the association request frame.

In this application embodiment, when assigning an AID to a Non-AP MLD, the scheme described in Embodiment 1 above is considered: an APMLD helps another AP MLD indicate whether the Non-AP MLD associated with that other AP MLD has 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 any AP MLD in the set of APMLDs co-located with AP _i , or the target AP MLD is any APMLD in the circle of AP MLDs co-located with AP _i . This avoids the ambiguity of the AID when indicating whether the Non-AP MLD has downlink unicast service.

Example 3

Embodiment 3 of this application addresses the issue of some APs in an APMLD being unable to indicate whether their associated Non-AP MLDs have downlink unicast services by limiting the links on which Non-AP MLDs listen for downlink unicast service indications. Furthermore, in this case, APs in other AP MLDs operating on the same link as these APs do not assist them in sending downlink unicast service indications. For example, taking Figure 5 as an example, 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 service indications on link 2, then AP2y (a non-transmission AP in the multi-BSSID set) in AP MLD1 cannot send downlink service indications. Additionally, the transmission APs in the same multi-BSSID set on the same link do not help send downlink service indications for the MLD where AP2y resides. Therefore, Non-AP MLD1 listening on link 2 cannot receive downlink service indications, meaning it cannot determine whether it has downlink unicast services.

Therefore, Embodiment 3 of this application provides a unicast service indication method applicable to multiple links. Referring to Figure 12, Figure 12 is another schematic flowchart of the unicast service indication method applicable to multiple links provided in this embodiment. As shown in Figure 12, the method includes:

S1. The AP MLD reports that the AP generates a management frame, such as a beacon frame. This beacon frame carries a TIM element, and a portion of the virtual bitmap field of the TIM element is used to indicate whether the Non-AP MLD associated with this AP MLD has downlink unicast service.

S2, AP MLD reporting: The AP sends management frames, such as beacon frames, on the link it is operating on.

The specific frame format of the TIM element can be seen in Figure 2, and the frame format of some virtual bitmap fields can be seen in Figure 7, which will not be described again here.

S3. The STA of the Non-AP MLD listens for management frames, such as beacon frames, on one or more links, including a first link, which is a link operated by a transport AP in a multi-BSSID set of AP MLDs associated with the Non-AP MLD or by an AP that does not belong to a multi-BSSID set.

S4, the STA of the Non-AP MLD parses the management frame, such as the beacon frame, that it hears on the link reporting the AP's operation to determine whether the Non-AP MLD has downlink unicast service.

Specifically, for step S3, in other words, a STA of a Non-AP MLD cannot listen for beacon frames only on links where non-transport APs of a multi-BSSID set reside. A STA of a Non-AP MLD can listen for beacon frames or other management frames on links where transport APs of a multi-BSSID set reside or where APs that do not belong to a multi-BSSID set reside. 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, then Non-AP MLD1 listens for beacon frames on link 1, or listens for beacon frames on links 1 and 2, or links 1 and 3, or link 3. Non-AP MLD1 cannot listen for beacon frames on link 2.

Optionally, the links monitored by a Non-AP MLD cannot include only the links in the associated AP MLD that are not operating with the transport AP. For example, as shown in Figure 5, the links monitored by a 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 cannot be only link 2.

As can be seen, this embodiment of the application limits the link on which the Non-AP MLD listens for downlink unicast service indications, enabling the Non-AP MLD to listen on the link operated by the transmitting AP of the multiple BSSID set or the AP that does not belong to the multiple BSSID set (for ease of description, denoted as the first link). Since the transmitting AP in the AP MLD and the AP that does not belong to the multiple BSSID set can send beacon frames (which carry downlink unicast service indications), the Non-AP MLD can listen for beacon frames on the first link. Therefore, by parsing the beacon frames, it can determine whether the Non-AP MLD itself has downlink unicast service.

The foregoing details the method provided in this application. In order to facilitate better implementation of the above-described solutions in the embodiments of this application, the embodiments of this application also provide corresponding devices or equipment.

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

Referring to FIG13, which is a schematic diagram of the structure of a communication device 1 provided in an embodiment of this application, the communication device 1 includes a processing unit 11 and a transceiver unit 12, as shown in FIG13.

The communication device 1 can be a first AP MLD or a chip within the first AP MLD, such as a Wi-Fi chip, or it can be the first AP within the first AP MLD. The first AP is the reporting AP and belongs to the first AP MLD.

In one design, the processing unit 11 is used to generate unicast service indication information; the transceiver unit 12 is used to send the unicast service indication information on a first link, which is the working link of a first AP. 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, wherein the second AP MLD is an AP MLD that is not a transmission AP in the multi-BSSID set where the first AP is located.

As can be seen, in this 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 service, but also help the second AP MLD indicate whether the Non-AP MLD associated with it has downlink unicast service. The second AP MLD is the AP MLD that is not the transmission AP in the multi-BSSID set where the first AP is located. This can solve the problem that some APs or all APs in the AP MLD cannot indicate whether the Non-AP MLD associated with them has downlink unicast service, so that the Non-AP MLD associated with these APs can receive downlink unicast service normally.

Optionally, the processing unit 11 is further configured to generate AID allocation information, which carries an AID allocated to the Non-AP MLD, and this 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 send the AID allocation information. The AID allocation information is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

Optionally, the transceiver unit 12 is further configured to receive an association request frame, which is used to request the establishment of a multi-link association with the communication device 1.

It should be understood that the communication device 1 in this design can perform the aforementioned embodiment 1, and the above-mentioned operations or functions of each unit in the communication device 1 are respectively to implement 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 described in detail here.

Optionally, the communication device 1 can be an AP MLD or a chip in the AP MLD, such as a Wi-Fi chip, or it can be a reporting AP in the AP MLD.

In another design, the processing unit 11 is used to generate management frames, such as beacon frames, which carry TIM elements. A portion of the virtual bitmap field of the TIM element is used to indicate whether there is downlink unicast service on the Non-AP MLD associated with the AP MLD. The transceiver unit 12 is used to send the management frames, such as beacon frames, on the link where it is operating.

It should be understood that the communication device 1 in this design can perform the aforementioned embodiment 3, and the above-mentioned operations or functions of each unit in the communication device 1 are respectively to realize the corresponding operations of the reporting AP of AP MLD in the aforementioned embodiment 3. For the sake of brevity, they will not be described in detail here.

Referring to Figure 14, which is a schematic diagram of the structure of the communication device 2 provided in an embodiment of this application, the communication device 2 includes a transceiver unit 21 and a processing unit 22.

The communication device 2 can be a Non-AP MLD or a chip in a Non-AP MLD, such as a Wi-Fi chip, or it can be the first STA in a Non-AP MLD.

In one design, the transceiver unit 21 is used to receive unicast service indication information on the first link where the communication device 2 operates; the processing unit 22 is used to determine whether the Non-AP MLD where the communication device 2 is located 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, wherein the second AP MLD is an AP MLD that is not a transmission AP in the multi-BSSID set where the first AP is located.

As can be seen, in the communication device 2, the processing unit 22 can know whether it has downlink unicast service according to the unicast service indication information, so as to ensure that it can receive downlink unicast service.

Optionally, the transceiver unit 21 can also be used to receive AID allocation information; the processing unit 22 can also be used to parse the received AID allocation information to obtain the AID carried in the AID allocation information that is assigned to a Non-AP MLD. This 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 the associated response frame. It is understood that the AID allocation information can also be carried in other frames.

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, the association request frame being used to request the establishment of a multi-link association with the first AP MLD.

It should be understood that the communication device 2 in this design can perform the aforementioned embodiment 1, and the above-mentioned operations or functions of each unit in the communication device 2 are respectively to realize 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 described in detail here.

Optionally, the communication device 2 can be a Non-AP MLD or a chip in a Non-AP MLD, such as a Wi-Fi chip, or it can be any STA in a Non-AP MLD.

In another design, the transceiver unit 21 is used to listen for management frames, such as beacon frames, on one or more links. The one or more links include a first link, which is a link operated by a transmission AP in a multi-BSSID set of AP MLDs associated with the Non-AP MLD or by an AP that does not belong to a multi-BSSID set. The processing unit 22 is used to parse the management frames, such as beacon frames, listened for on the links where the reporting AP is operating, to determine whether the Non-AP MLD has downlink unicast services.

It should be understood that the communication device 2 in this design can perform the aforementioned embodiment 3, and the above-mentioned operations or functions of each unit in the communication device 2 are respectively to realize the corresponding operations of the STA of the Non-AP MLD in the aforementioned embodiment 3. For the sake of brevity, they will not be described in detail here.

Referring to Figure 15, which is a schematic diagram of the structure of the communication device 3 provided in an embodiment of this application. The communication device 3 can 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 Embodiment 2 above, or any AP within an AP MLD. As shown in Figure 15, the communication device 3 includes a processing unit 31 and a transceiver unit 32.

Processing unit 31 is used to generate AID allocation information, which carries an AID allocated to a Non-AP MLD. This AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is any AP MLD within the set of AP MLDs co-located with AP _i , or the target AP MLD is any AP MLD within the set circle containing the set of AP MLDs co-located with AP _i . Transceiver unit 32 is used to send the AID allocation information. AP _i is any AP in the AP MLD.

Optionally, if the target AP MLD is any AP MLD in the set of AP MLDs co-located with AP _i , then both the target AP MLD and the target AP MLD belong to the set of AP MLDs co-located with AP _i .

Optionally, the AID allocation information described above is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

Optionally, the transceiver unit 32 is further configured to receive an association request frame, which is used to request the establishment of a multi-link association with the APMLD.

As can be seen, in the communication device 2, the AID assigned to the Non-AP MLD 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. Here, the target AP MLD is any AP MLD within the set of AP MLDs co-located with AP _i , or any AP MLD within the circle of the set of AP MLDs co-located with AP _i . This avoids AID ambiguity when indicating whether a Non-AP MLD has downlink unicast service.

It should be understood that the communication device 3 described in this application embodiment can correspondingly execute the aforementioned embodiment 2, and the above-mentioned operations or functions of each unit in the communication device 3 are respectively to implement the corresponding operations of AP _i of AP MLD in the aforementioned embodiment 2. For the sake of brevity, they will not be described in detail here.

Referring to Figure 16, which is a schematic diagram of the structure of the communication device 4 provided in an embodiment of this 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 Embodiment 2 above, or any STA within a Non-AP MLD. As shown in Figure 16, the communication device 4 includes a transceiver unit 41 and a processing unit 42.

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 carried in the AID allocation information that is allocated to the Non-AP MLD. This AID is different from the AID of the Non-AP MLD associated with the target AP MLD. The target AP MLD is any AP MLD in the set of AP MLDs co-located with AP _i , or the target AP MLD is any AP MLD in the set circle of AP MLDs co-located with AP _i . AP _i is any AP in the AP MLD.

Optionally, if the target AP MLD is any AP MLD in the set of AP MLDs co-located with AP _i , then both the target AP MLD and the target AP MLD belong to the set of AP MLDs co-located with AP _i .

Optionally, the AID allocation information described above is carried in the associated response frame. It is understood that the AID allocation information may also be carried in other frames.

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, which is used to request the establishment of a multi-link association with the AP MLD.

It should be understood that the communication device 4 described in this application embodiment can perform the aforementioned embodiment 2, and the above-mentioned operations or functions of each unit in the communication device 4 are respectively to implement 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 described in detail here.

The above describes the AP MLD and Non-AP MLD of the embodiments of this application. The following describes possible product forms of the AP MLD and Non-AP MLD. It should be understood that any product with the functionality of the AP MLD described in Figure 13 or Figure 15, or any product with the functionality of the Non-AP MLD described in Figure 14 or Figure 16, falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the AP MLD and Non-AP MLD of the embodiments of this application to these examples.

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

Referring to Figure 17, Figure 17 is a schematic diagram of the structure of a communication device 1000 provided in an embodiment of this application. The communication device 1000 can be an AP MLD or a Non-AP MLD, or a device thereof. As shown in Figure 17, the communication device 1000 includes a processor 1001 and a transceiver 1002 internally connected and communicating with the processor. The processor 1001 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminals, terminal chips, DUs or CUs, etc.), execute computer programs, and process data from the computer programs. The transceiver 1002 can be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement transceiver functions. The transceiver 1002 can include a receiver and a transmitter. The receiver can be referred to as a receiver or receiving circuit, etc., and is used to implement a receiving function; the transmitter can be referred to as a transmitter or transmitting circuit, etc., and is used to implement a transmitting function. Optionally, the communication device 1000 may also include an antenna 1003.

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

The processor 1001, transceiver 1002, and memory 1004 can be connected via a communication bus.

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: the processor 1001 can be used to perform step S101 in FIG6 and/or other processes of the technology described herein; the transceiver 1002 can be used to perform step S102 in FIG6 and/or other processes of the technology described herein.

In one design, the communication device 1000 can be used to perform the function of the first STA of the Non-AP MLD in the aforementioned embodiment: the processor 1001 can be used to perform step S104 in FIG6 and/or other processes of the technology described herein; the transceiver 1002 can be used to perform step S103 in FIG6 and/or other processes of the technology described herein.

In one design, the communication device 1000 can be used to perform the AP function of the AP MLD in the aforementioned embodiment 2: the processor 1001 can be used to perform step S201 in FIG9 and/or other processes of the technology described herein; the transceiver 1002 can be used to perform step S202 in FIG9 and/or other processes of the technology described herein.

In one design, the communication device 1000 can be used to perform the STA function of the Non-AP MLD in the aforementioned embodiment 2: the processor 1001 can be used to perform steps S203 and S204 in FIG9 and/or other processes of the technology described herein; the transceiver 1002 can be used to perform step S205 in FIG9 and/or other processes of the technology described herein.

In one design, the communication device 1000 can be used to perform the reporting AP function of the AP MLD in the aforementioned embodiment three: the processor 1001 can be used to perform step S1 in FIG12 and/or other processes of the technology described herein; the transceiver 1002 can be used to perform step S2 in FIG12 and/or other processes of the technology described herein.

In one design, the communication device 1000 can be used to perform the STA function of the Non-AP MLD in the aforementioned embodiment three: the processor 1001 can be used to perform step S4 in FIG12 and/or other processes of the technology described herein; the transceiver 1002 can be used to perform step S3 in FIG12 and/or other processes of the technology described herein.

In any of the above designs, the 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 receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or it may be used for transmitting or relaying signals.

In any of the above designs, the processor 1001 may store instructions, which may be computer programs. These computer programs, running on the processor 1001, cause the communication device 1000 to execute the methods described in the above method embodiments. The computer program may be embedded in the processor 1001; in this case, the processor 1001 may be implemented in hardware.

In one implementation, the communication device 1000 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

The scope of the communication device described in this application is not limited thereto, and the structure of the communication device is not limited to Figure 17. The communication device can be a standalone device or part of a larger device. For example, the communication device can be:

(1) Independent integrated circuit IC, or chip, or chip system or subsystem;

(2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

(3) ASIC, such as modem;

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

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

(6) Others, etc.

As one possible product form, the AP MLD and Non-AP MLD described in the embodiments of this application can be implemented by a common processor.

The general-purpose processor implementing the AP MLD includes processing circuitry and an input/output interface internally connected and communicating with the processing circuitry. In one design, the general-purpose processor can be used to perform the functions of the first AP in the first AP MLD of the aforementioned embodiment. Specifically, the processing circuitry is used to perform step S101 in FIG6 and/or other processes of the technology described herein; the input/output interface is used to perform step S102 in FIG6 and/or other processes of the technology described herein.

In another design, the general-purpose processor can be used to perform the AP function of the AP MLD in the aforementioned embodiment 2. Specifically, the processing circuit is used to perform step S201 in FIG9 and/or other processes of the technology described herein; the input/output interface is used to perform step S202 in FIG9 and/or other processes of the technology described herein.

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

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

In another design, the general-purpose processor can be used to perform the STA function of the Non-AP MLD in the aforementioned embodiment 2. Specifically, the processing circuit is used to perform steps S203 and S204 in FIG9 and/or other processes of the technology described herein; the input/output interface is used to perform step S205 in FIG9 and/or other processes of the technology described herein.

In another design, the general-purpose processor can be used to perform the STA function of the Non-AP MLD in the aforementioned embodiment three. Specifically, the processing circuit is used to perform step S4 in FIG12 and/or other processes of the technology described herein; the input/output interface is used to perform step S3 in FIG12 and/or other processes of the technology described herein.

As a possible product form, the AP MLD and Non-AP MLD described in the embodiments of this application can also be implemented using 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 capable of performing the various functions described throughout this application.

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

This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, the electronic device performs the method in any of the foregoing embodiments.

This application also provides a computer program product that, when run on a computer, causes the computer to perform the methods in any of the foregoing embodiments.

This application also provides a communication device, which can exist in the form of a chip. 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 can execute the method in any of the foregoing embodiments.

This application also provides a wireless communication system including an AP MLD and a Non-AP MLD, which can perform the methods in any of the foregoing embodiments.

The steps of the methods or algorithms described in this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist 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, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a core network interface device. Of course, the processor and storage medium can also exist as discrete components in the core network interface device.

Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code 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. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims (21)

1. A method for allocating association identifiers (AIDs) for multi-link devices, characterized in that it includes: Access point multi-link device (AP MLD) generates associated identifier (AID) allocation information for access point AP _i . The AID allocation information carries an AID allocated for 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 any AP MLD in the set of AP MLDs co-located with AP _i , or the target AP MLD is any AP MLD in the set circle of the set of AP MLDs co-located with AP _i . AP _i of the AP MLD sends the associated response frame. 2. The method according to claim 1, wherein the AID allocation information is carried in the associated response frame. 3. The method according to claim 1 or 2, wherein both the AP MLD and the target AP MLD belong to the set of AP MLDs co-located with AP _i ; Alternatively, both the AP MLD and the target AP MLD belong to the set circle containing the set of AP MLDs co-located with AP _i . The set circle includes the set of AP MLDs co-located with AP _i , and the set of AP MLDs co-located with any AP other than AP _i in the set of AP MLDs co-located with AP _i . 4. The method according to claim 1 or 2, wherein the AID space used by the AP MLD to allocate an AID to its associated Non-AP MLD is the same as the AID space used by the target AP MLD to allocate an AID to its associated Non-AP MLD. 5. A method for allocating association identifiers (AIDs) for multi-link devices, characterized in that it includes: Non-AP MLD sites receive associated identifier (AID) allocation information; The Non-AP MLD site parses the received AID allocation information to obtain the AID allocated to 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 any AP MLD in the set of AP MLDs co-located with AP _i , or the target AP MLD is any AP MLD in the set circle of the set of AP MLDs co-located with AP _i . 6. The method according to claim 5, wherein the AID allocation information is carried in the associated response frame. 7. The method according to claim 5 or 6, wherein a Non-AP MLD comprises multiple sites that share the same AID. 8. The method according to claim 1 or 2, wherein the AID space to which the AID assigned to the Non-AP MLD belongs is the same as the AID space to which the AID assigned to the Non-AP MLD associated with the target AP MLD belongs. 9. A communication device, characterized in that it is applied in an AP MLD, comprising: The processing unit is used to generate associated identifier AID allocation information, wherein the AID allocation information carries an AID allocated for a non-access point multi-link device (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 being any AP MLD within the set of AP MLDs co-located with AP _i , or the target AP MLD being any AP MLD within the set circle of the set of AP MLDs co-located with AP _i ; The transceiver unit is used to send the associated response frame. 10. The communication device according to claim 9, wherein the AID allocation information is carried in the associated response frame. 11. The communication device according to claim 9 or 10, wherein both the AP MLD and the target AP MLD belong to the set of AP MLDs co-located with AP _i ; Alternatively, both the AP MLD and the target AP MLD belong to the set circle containing the set of AP MLDs co-located with AP _i . The set circle includes the set of AP MLDs co-located with AP _i , and the set of AP MLDs co-located with any AP other than APi in the set of AP MLDs co-located with AP _i . 12. The communication device according to claim 9 or 10, wherein the AID space used by the AP MLD to allocate an AID to its associated Non-AP MLD is the same as the AID space used by the target AP MLD to allocate an AID to its associated Non-AP MLD. 13. A communication device, characterized in that it is applied in a Non-AP MLD (Non-Access Point Multilink Device), comprising: The transceiver unit is used to receive the associated identifier (AID) allocation information; The processing unit is configured to parse the received AID allocation information to obtain the AID carried in the AID allocation information for the 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 AP _i , or the target AP MLD is any AP MLD in the set circle of the set of AP MLDs co-located with AP _i . 14. The communication device according to claim 13, wherein the AID allocation information is carried in the associated response frame. 15. The communication device according to claim 13 or 14, wherein a Non-AP MLD comprises multiple stations that share the same AID. 16. The communication device according to claim 13 or 14, wherein the AID space to which the AID assigned to the Non-AP MLD belongs is the same as the AID space to which the AID assigned to the Non-AP MLD associated with the target AP MLD belongs. 17. A computer-readable storage medium, characterized in that the computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-4, or cause the computer to perform the method as described in any one of claims 5-8. 18. A computer program product comprising instructions, characterized in that, when the instructions are executed on a computer, the computer performs the method as described in any one of claims 1-4; and the computer performs the method as described in any one of claims 5-8. 19. A chip or chip system, characterized in that it includes an input/output interface and a processing circuit, wherein the input/output interface is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform the method as claimed in any one of claims 1-4; causing the computer to perform the method as claimed in any one of claims 5-8. 20. An access point multi-link device, characterized in that it includes a first access point and a second access point, wherein the first access point is used to implement the method of any one of claims 1-4. 21. A non-access point multi-link device, characterized in that it comprises a plurality of stations, wherein one station is used to implement the method of any one of claims 5-8.