Key bss parameter management method and related device suitable for multi-link

Abstract

The present application relates to the field of wireless communication, especially to a key BSS parameter management method suitable for multi-link and related devices, such as applied in a wireless local area network supporting 802.11be standard. The method comprises: a first AP of a first AP MLD generates and sends a first frame, used to indicate key BSS parameter update count values corresponding to a plurality of APs of the first AP MLD and key BSS parameter update count values corresponding to a plurality of APs of a second AP MLD, the second AP MLD being an AP MLD to which a non-transmission AP in a multi-BSSID set where the first AP is located belongs. It can help some APs or all APs in part of the AP MLDs to inform the STAs managed thereby whether the key BSS parameters of the BSS managed by the AP are updated, to assist the STAs in receiving the latest key BSS parameters.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a method and related apparatus for managing key BSS parameters in multi-link systems. Background Technology

[0002] To significantly improve the service transmission rate of wireless local area network (WLAN) systems, the IEEE 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.

[0003] 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).

[0004] When the BSS of an AP in an access point multi-link device (AP MLD) is updated, some site multi-link devices or sites may not be able to obtain the latest information of the BSS managed by these APs, thus preventing these site multi-link devices or sites from communicating normally with these special APs. Summary of the Invention

[0005] This application provides a method and related apparatus for managing key BSS parameters in a multi-link system. It can help some or all APs in a partial AP MLD notify the STAs they manage whether the key BSS parameters of the AP (the BSS they manage) have been updated, so as to assist the STAs in receiving the latest key BSS parameters. This allows the STAs to communicate normally with the AP even after the key BSS parameters of the AP have been updated.

[0006] 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.

[0007] Firstly, this application provides a BSS parameter management method applicable to multiple links, applied in a first AP MLD, where the first AP is any reporting AP in the first AP MLD. The BSS parameter management method applicable to multiple links includes: the first AP of the first AP MLD generating a first frame and transmitting the first frame on its operating link. The first frame is used to indicate key basic service set (BSS) parameter update information corresponding to multiple APs of the first AP MLD and key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is an AP MLD belonging to a non-transmitting AP in the multi-basic service set identifier (BSSID) set where the first AP is located. A key BSS parameter update information corresponding to one AP is used to determine whether the BSS managed by that AP has key BSS parameter updates.

[0008] Optionally, the above key BSS parameter update information includes key BSS parameter update count values.

[0009] Optionally, when one or more of the key BSS parameters change, the key BSS parameter update count is incremented by 1.

[0010] This scheme, through the first frame, indicates not only the key BSS parameter update count values ​​corresponding to multiple APs in the first AP MLD, but also the key BSS parameter update count values ​​corresponding to multiple APs in the second AP MLD. This allows one AP to assist in providing the key BSS parameter update count values ​​to multiple APs in another AP MLD, enabling the STA to determine whether there has been a key BSS parameter update by comparing the currently received key BSS parameter update count value with the previously received one. This assists the STA in receiving the latest key BSS parameters and allows the Non-AP MLD associated with the second AP MLD to listen on links where non-transport APs reside within the second AP MLD and function normally. In other words, non-AP MLDs have more listening channel options. Since in 802.11be, it is possible for some or all APs in an AP MLD to be non-transport APs, the scheme provided in this application can solve the problem that some non-transport APs cannot send management frames to notify of key BSS parameter updates, thereby increasing the completeness and diversity of key BSS parameter update indications.

[0011] In conjunction with the first aspect, in one possible implementation, after the first AP of the first AP MLD sends the aforementioned first frame, the method further includes: the first AP of the first AP MLD generating a second frame, the second frame being used to indicate specific key BSS parameters of the plurality of APs of the first AP MLD and specific key BSS parameters of the plurality of APs of the second AP MLD; the first AP of the first AP MLD sending the second frame on its operating link.

[0012] This solution not only helps certain APs in other AP MLDs indicate whether key BSS parameters have been updated, but also helps certain APs in other AP MLDs indicate the latest specific key BSS parameters, which include elements related to channel changes. It can help Non-AP MLDs, while monitoring one or more links (not all links), to promptly obtain information on the operating channel changes of all APs in the AP MLD, ensuring its normal operation.

[0013] Secondly, this application provides a BSS parameter management method applicable to multiple links, applied to a first STA, which can be a single-link STA or a STA in a Non-AP MLD. The first STA and a first AP operate on the same link. The BSS parameter management method applicable to multiple links includes: the first STA of the Non-AP MLD receives a first frame on its operating link, and based on the first frame, determines whether there are key BSS parameter updates for multiple BSS managed by multiple APs in the AP MLD associated with the first STA. The first frame is used to indicate key BSS parameter update information corresponding to multiple APs of the first AP MLD and key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the AP MLD belonging to a non-transmitting AP in the multi-BSSID set where the first AP is located. A key BSS parameter update information corresponding to one AP is used to determine whether there are key BSS parameter updates for the BSS managed by that AP.

[0014] Understandably, when the first STA is a STA in a Non-AP MLD, the AP MLD associated with the first STA can be the AP MLD associated with the Non-AP MLD where the first STA is located.

[0015] Optionally, the above key BSS parameter update information includes key BSS parameter update count values.

[0016] Optionally, when one or more of the key BSS parameters change, the key BSS parameter update count is incremented by 1.

[0017] In conjunction with the second aspect, in one possible implementation, after the first STA of the Non-AP MLD receives the first frame, the method further includes: the first STA of the Non-AP MLD receiving a second frame on its operating link, the second frame being used to indicate specific key BSS parameters of multiple APs of the first AP MLD and specific key BSS parameters of multiple APs of the second AP MLD; the first STA of the Non-AP MLD parsing the second frame to obtain the specific key BSS parameters of multiple APs in the AP MLD associated with the Non-AP MLD.

[0018] 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 or a chip in the first AP, including:

[0019] The processing unit is configured to generate a first frame, which indicates the key basic service set (BSS) parameter update information corresponding to multiple APs of the first AP MLD and the key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the APMLD to which the non-transmitting AP belongs in the set of multiple basic service set identifiers (BSSIDs) where the first AP is located. The key BSS parameter update information corresponding to an AP is used to determine whether there is a key BSS parameter update for the BSS managed by that AP. The transceiver unit is configured to transmit the first frame on the link where the communication device is operating.

[0020] Optionally, the above key BSS parameter update information includes key BSS parameter update count values.

[0021] Optionally, when one or more of the key BSS parameters change, the key BSS parameter update count is incremented by 1.

[0022] In conjunction with the third aspect, in one possible implementation, the aforementioned processing unit is further configured to generate a second frame, which is used to indicate specific key BSS parameters of the plurality of APs of the first AP MLD and specific key BSS parameters of the plurality of APs of the second AP MLD; the aforementioned transceiver unit is further configured to transmit the second frame on its operating link.

[0023] Fourthly, this application provides a communication device, which can be a first STA or a chip in the first STA, such as a Wi-Fi chip. The first STA can be a single-link STA or a STA in a Non-AP MLD. The communication device includes:

[0024] The transceiver unit is configured to receive a first frame on the link where the communication device operates. The first frame indicates key BSS parameter update information corresponding to multiple APs of the first AP MLD and key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the APMLD to which the non-transmitting AP belongs in the set of multiple BSSIDs where the first AP is located. The key BSS parameter update information corresponding to an AP is used to determine whether the BSS managed by that AP has key BSS parameter updates. The processing unit is configured to determine, based on the first frame, whether the multiple BSSs managed by multiple APs in the AP MLD associated with the communication device have key BSS parameter updates.

[0025] Optionally, the above key BSS parameter update information includes key BSS parameter update count values.

[0026] Optionally, when one or more of the key BSS parameters change, the key BSS parameter update count is incremented by 1.

[0027] In conjunction with the fourth aspect, in one possible implementation, the aforementioned transceiver unit is further configured to receive a second frame on its operating link, the second frame indicating specific key BSS parameters of multiple APs in the first AP MLD and specific key BSS parameters of multiple APs in the second AP MLD; the aforementioned processing unit is configured to parse the second frame to obtain specific key BSS parameters of multiple APs in the AP MLD associated with the Non-AP MLD.

[0028] In any of the above implementations, the first frame includes a link identifier field and a multi-link device (MLD) identifier field. The link identifier field is used to indicate the reported AP, and the MLD identifier field is used to indicate the AP MLD where the reported AP is located.

[0029] Optionally, the first frame mentioned above also includes a key BSS parameter count field, which is used to indicate the key BSS parameter update count value.

[0030] In any of the above implementations, the key BSS parameter update count field, the link identifier field, and the MLD identifier field are carried in the simplified neighbor report (RNR) element of the first frame.

[0031] Understandably, the three key BSS parameter update count field, link identifier field, and MLD identifier field are independent and can be carried in the RNR element simultaneously or separately. In other words, the RNR element can carry some of these three fields.

[0032] In any of the above implementations, the Target Transmission Time (TBTT) information field of a beacon frame in the RNR element carries a key BSS parameter update count, a link identifier field, and an MLD identifier field, with one TBTT information field corresponding to one AP.

[0033] In any of the above implementations, the value of the short service set identifier (SSID) field of the AP in the RNR element is obtained based on the SSID of the MLD where the AP is located.

[0034] In any of the above implementations, a specific key BSS parameter of an AP in the second frame includes one or more of the following: a channel change notification element, an extended channel change notification element, a wideband channel change element, and a wideband channel change envelope element.

[0035] In any of the above implementations, the specific key BSS parameter is carried in the multi-link ML element.

[0036] Fifthly, this application provides a method for updating key BSS parameters, applied in a first AP MLD, wherein the second AP is any AP in the first AP MLD. The method for updating key BSS parameters includes: the second AP in the first AP MLD generating a second frame and transmitting the second frame on its operating link. The second frame is used to indicate specific key BSS parameters of multiple APs in the first AP MLD, and / or specific key BSS parameters of multiple APs in the second AP MLD, wherein the second AP MLD is an AP MLD belonging to a non-transmitting AP within a set of multiple BSSIDs to which the second AP resides.

[0037] Optionally, a particular key BSS parameter of an AP in the second frame mentioned above may include one or more of the following: a channel change notification element, an extended channel change notification element, a wideband channel change element, or a wideband channel change envelope element.

[0038] Optionally, the aforementioned specific key BSS parameters can be carried in the multi-link ML element.

[0039] Sixthly, this application provides a method for updating key BSS parameters, applied to a second STA, which can be a single-link STA or a STA in a Non-AP MLD. The second STA and a second AP operate on the same link. The method for updating key BSS parameters includes: the second STA receiving a second frame on its operating link and parsing the second frame to obtain specific key BSS parameters of multiple APs in the AP MLD associated with the second STA. The second frame is used to indicate specific key BSS parameters of multiple APs in the first AP MLD and / or specific key BSS parameters of multiple APs in the second AP MLD, wherein the second AP MLD is an AP MLD belonging to a non-transmitting AP in a multi-BSSID set to which the second AP resides.

[0040] Understandably, when the second STA is a STA in a Non-AP MLD, the AP MLD associated with the second STA can be the AP MLD associated with the Non-AP MLD where the second STA is located.

[0041] Optionally, a particular key BSS parameter of an AP in the second frame mentioned above may include one or more of the following: a channel change notification element, an extended channel change notification element, a wideband channel change element, or a wideband channel change envelope element.

[0042] Optionally, the aforementioned specific key BSS parameters can be carried in the multi-link ML element.

[0043] In a seventh aspect, 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 second AP in the first AP MLD or a chip in the second AP, comprising:

[0044] The processing unit is used to generate a second frame, which is used to indicate specific key BSS parameters of multiple APs of the first AP MLD and / or specific key BSS parameters of multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs in which the second AP is located. The transceiver unit is used to send the second frame on the link where the communication device is operating.

[0045] Optionally, a particular key BSS parameter of an AP in the second frame mentioned above may include one or more of the following: a channel change notification element, an extended channel change notification element, a wideband channel change element, or a wideband channel change envelope element.

[0046] Optionally, the aforementioned specific key BSS parameters can be carried in the multi-link ML element.

[0047] Eighthly, this application provides a communication device, which can be a second STA or a chip in the second STA, such as a Wi-Fi chip. The first STA can be a single-link STA, or it can be one of the STAs in a Non-AP MLD. The communication device includes:

[0048] The transceiver unit is used to receive a second frame on the link where the communication device is operating. The second frame is used to indicate specific key BSS parameters of multiple APs of the first AP MLD and / or specific key BSS parameters of multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs where the second AP is located. The processing unit is used to parse the second frame to obtain specific key BSS parameters of multiple APs in the AP MLD associated with the Non-AP MLD.

[0049] Optionally, a particular key BSS parameter of an AP in the second frame mentioned above may include one or more of the following: a channel change notification element, an extended channel change notification element, a wideband channel change element, or a wideband channel change envelope element.

[0050] Optionally, the aforementioned specific key BSS parameters can be carried in the multi-link ML element.

[0051] 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 of the method described in 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.

[0052] Specifically, the processor is used to generate a first frame, which indicates the key basic service set (BSS) parameter update information corresponding to multiple APs of the first AP MLD and the key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple basic service set identifiers (BSSIDs) where the first AP is located. The key BSS parameter update information corresponding to an AP is used to determine whether there is a key BSS parameter update for the BSS managed by that AP. The transceiver is used to send the first frame on the link where the communication device is operating.

[0053] In a tenth aspect, this application provides a communication device, specifically a first STA, including a processor and a transceiver. The processor is configured to support the first STA in performing the corresponding functions of the method described in the second aspect above. The transceiver is used to support communication between the first STA and a first AP MLD, receiving information, frames, data packets, or instructions involved in the above method from the first AP MLD. The second STA may further include a memory coupled to the processor, which stores necessary program instructions and data for the second STA.

[0054] Specifically, the transceiver is used to receive a first frame on the link where the communication device operates. The first frame is used to indicate the key BSS parameter update information corresponding to multiple APs of the first AP MLD and the key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs where the first AP is located. The key BSS parameter update information corresponding to an AP is used to determine whether the BSS managed by the AP has a key BSS parameter update. The processor is used to determine, based on the first frame, whether the multiple BSSs managed by multiple APs in the AP MLD associated with the first STA have key BSS parameter updates.

[0055] Eleventhly, this application provides a communication device, specifically a first AP MLD or a second AP within the first AP MLD, including a processor and a transceiver. The processor is configured to support the first 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 first 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 first AP MLD may further include a memory coupled to the processor, which stores necessary program instructions and data of the first AP MLD.

[0056] Specifically, the processor is used to generate a second frame, which is used to indicate specific key BSS parameters of multiple APs of the first AP MLD and / or specific key BSS parameters of multiple APs of the second AP MLD, wherein the second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs in which the second AP is located; the transceiver is used to send the second frame on the link in which the communication device operates.

[0057] In a twelfth aspect, this application provides a communication device, specifically a second STA, including a processor and a transceiver. The processor is configured to support the second STA in performing the corresponding functions of the method described in the sixth aspect above. The transceiver is used to support communication between the second STA and a first AP MLD, receiving information, frames, data packets, or instructions involved in the above method from the first AP MLD. The second STA may further include a memory coupled to the processor, which stores necessary program instructions and data for the second STA.

[0058] Specifically, the transceiver is used to receive a second frame on its operating link, the second frame being used to indicate specific key BSS parameters of multiple APs in the first AP MLD, and / or specific key BSS parameters of multiple APs in the second AP MLD, the second AP MLD being the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs in which the second AP is located; the processor is used to parse the second frame to obtain specific key BSS parameters of multiple APs in the AP MLD associated with the second STA.

[0059] 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 a first frame, which indicates key basic service set (BSS) parameter update information corresponding to multiple APs of a first AP MLD and key BSS parameter update information corresponding to multiple APs of a second AP MLD. The second AP MLD is an AP MLD belonging to a non-transmitting AP in the multi-basic service set identifier (BSSID) set where the first AP is located. The key BSS parameter update information corresponding to one AP is used to determine whether the BSS managed by that AP has key BSS parameter updates. The input / output interface is used to transmit the first frame on the link where the chip or chip system operates.

[0060] In one possible design, the input / output interface is used to receive a first frame on the link where the chip or chip system operates. The first frame is used to indicate key BSS parameter update information corresponding to multiple APs of the first AP MLD and key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs where the first AP is located. The key BSS parameter update information corresponding to an AP is used to determine whether the BSS managed by that AP has key BSS parameter updates. The processing circuit is used to determine, based on the first frame, whether the multiple BSSs managed by multiple APs in the AP MLD associated with the first STA have key BSS parameter updates.

[0061] In a fourteenth aspect, this application provides a chip or chip system, including an input / output interface and processing circuitry. The processing circuitry generates a second frame indicating specific key BSS parameters of multiple APs in a first AP MLD, and / or specific key BSS parameters of multiple APs in a second AP MLD, wherein the second AP MLD is an AP MLD belonging to a non-transmitting AP in a set of multiple BSSIDs to which the second AP resides; the input / output interface transmits the second frame on the link where the chip or chip system operates.

[0062] In one possible design, the input / output interface is used to receive a second frame on the link where the chip or chip system operates. The second frame is used to indicate specific key BSS parameters of multiple APs in the first AP MLD and / or specific key BSS parameters of multiple APs in the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs in which the second AP is located. The processing circuit is used to parse the second frame to obtain the specific key BSS parameters of multiple APs in the AP MLD associated with the second STA.

[0063] 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 critical BSS parameter management method applicable to multiple links as described in the first or second aspect above.

[0064] 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 method for updating key BSS parameters as described in the fifth or sixth aspect above.

[0065] 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 critical BSS parameter management method applicable to multi-link systems described in the first or second aspect above.

[0066] In an eighteenth aspect, this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the method for updating key BSS parameters as described in the fifth or sixth aspect above.

[0067] Implementing the embodiments of this application can help some APs or all APs in a partial AP MLD to notify the STAs they manage whether the key BSS parameters of the AP (managed BSS) have been updated, so as to assist the STAs in receiving the latest key BSS parameters, thereby enabling the STAs to communicate normally with the AP after the key BSS parameters of the AP are updated. Attached Figure Description

[0068] 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.

[0069] Figure 1 This is a schematic diagram of the structure of an AP MLD and a Non-AP MLD provided in the embodiments of this application;

[0070] Figure 2 This is a schematic diagram of a frame format with multiple BSSID elements provided in an embodiment of this application;

[0071] Figure 3a This is a schematic diagram of the structure of a communication system 100 provided in an embodiment of this application;

[0072] Figure 3b This is a schematic diagram of the structure of a communication system 200 provided in an embodiment of this application;

[0073] Figure 3c This is a schematic diagram of the structure of a communication system 300 provided in an embodiment of this application;

[0074] Figure 4 This is a schematic diagram of the architecture of multiple BSSID sets provided in the embodiments of this application;

[0075] Figure 5 This is a schematic diagram of the frame structure of the TIM frame provided in the embodiments of this application;

[0076] Figure 6 This is a schematic diagram of the frame structure of a management frame provided in an embodiment of this application;

[0077] Figure 7 This is a schematic flowchart of a key BSS parameter management method applicable to multiple links provided in an embodiment of this application;

[0078] Figure 8a This is a schematic diagram of the frame structure of the RNR element provided in the embodiments of this application;

[0079] Figure 8b This is a schematic diagram of the frame structure of a TBTT information field in an RNR element provided in an embodiment of this application;

[0080] Figure 9 This is a schematic flowchart of a method for updating key BSS parameters provided in an embodiment of this application;

[0081] Figure 10a This is a schematic diagram of a frame structure of an ML element provided in an embodiment of this application;

[0082] Figure 10b This is a schematic diagram of the first half of the frame structure of an ML element provided in an embodiment of this application;

[0083] Figure 11a This is a schematic diagram of a frame structure including a channel change notification element provided in an embodiment of this application;

[0084] Figure 11b This is a schematic diagram of the frame structure including the extended channel change notification element provided in the embodiments of this application;

[0085] Figure 11c This is a schematic diagram of a frame structure including wideband channel changing elements provided in an embodiment of this application;

[0086] Figure 11d This is a schematic diagram of the frame structure of the quiet element provided in the embodiments of this application;

[0087] Figure 12 This is a schematic diagram of the frame structure of a non-inherited element provided in an embodiment of this application;

[0088] Figure 13 This is a schematic diagram of the structure of the communication device 1 provided in the embodiments of this application;

[0089] Figure 14 This is a schematic diagram of the structure of the communication device 2 provided in the embodiments of this application;

[0090] Figure 15 This is a schematic diagram of the structure of the communication device 3 provided in the embodiments of this application;

[0091] Figure 16 This is a schematic diagram of the structure of the communication device 4 provided in the embodiments of this application;

[0092] Figure 17 This is a schematic diagram of the structure of the communication device 1000 provided in the embodiments of this application. Detailed Implementation

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

[0094] To better understand the key BSS parameter management method and related apparatus for multi-link systems disclosed in the embodiments of this application, the relevant concepts of the embodiments of this application are first described.

[0095] 1. Multi-link devices

[0096] 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.

[0097] 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 AP as an affiliated site as a multi-link AP, a multi-link AP device, or an AP multi-link device (AP MLD), and a multi-link device with a 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."

[0098] A multi-link device includes one or more affiliated stations (STAs). In other words, a multi-link device can also include multiple logical stations. Each logical station operates on one link, but multiple logical stations are allowed to operate on the same link.

[0099] 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.

[0100] 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.

[0101] 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. Devices 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. It can support the 802.11 series of protocols and can communicate with AP MLDs or other Non-AP MLDs or single-link devices. For example, STAMLD is any user communication device that allows users to communicate with APs and then 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. The Non-AP MLD can also be the chip and processing system in these terminals.

[0102] The AP MLD in this application embodiment is a device that provides services for a 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 this application embodiment. 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-service 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.

[0103] 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.

[0104] 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, the multi-link device in the embodiments of this application 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. See also... Figure 1 , Figure 1 This is a schematic diagram of the structure of an AP MLD and a Non-AP MLD provided in the embodiments of this application. Figure 1 The diagram shows the structure of AP MLD with multiple antennas and Non-AP MLD with a single antenna. The 802.11 standard focuses on the physical layer (PHY) and medium access control (MAC) layer in AP MLD and Non-AP MLD.

[0105] 2. Link Identifier

[0106] 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.

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

[0108] In one example, the management frames sent by the AP MLD when establishing a basic service set (BSS), such as beacon frames, carry an element that includes multiple link identification information fields. These fields indicate the correspondence between a link identifier and a station operating on the corresponding link. The link identification information field includes not only the link identifier but also one or more of the following: Medium Access Control (MAC) address, operation set, and channel number. One or more of these elements can identify a link. For the AP, the AP's MAC address is its BSSID (basic serviceset identifier). In another example, during multi-link device association, the AP MLD and the Non-AP MLD negotiate multiple link identification information fields. Multi-link device association refers to one association between one AP of the AP MLD and one STA of the Non-AP MLD. This association allows multiple STAs of the Non-AP MLD to be associated with multiple APs of the AP MLD, with each STA associated with one AP.

[0109] 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 it operates in, 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 station operating on that link, such as the station's MAC address or its association identifier (AID).

[0110] 3. Multiple Basic Service Set Identifier (BSSID set)

[0111] 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 are 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.

[0112] 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.

[0113] 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 that multiple BSSID set will respond by sending a probe response frame.

[0114] 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.

[0115] The beacon frame sent by the transmission AP may include multiple BSSID elements, and the frame format of the multiple BSSID elements is as follows: Figure 2 As shown, Figure 2 This is a schematic diagram of a frame format for a multi-BSSID element provided in an embodiment of this application. The multi-BSSID element includes 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 multi-BSSID set, and the optional sub-element fields include information about the BSSIDs of APs with non-transmitted BSSIDs.

[0116] The maximum allowed number of APs in a multi-BSSID set is 2^n, where n is... Figure 2 The MaxBSSIDIndicator field in the multi-BSSID element, as shown, indicates a value where N = 2^n. 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 NonTxBSS IDs (identifiers) from 1 to 2^n-1 have multicast services. The value of the NonTxBSS ID is equal to the value of the BSSID Index field in the Multiple BSSID-Index element of the Non-transmitted BSSID profile within the multi-BSSID element. The Non-transmitted BSSID profile is located in the optional sub-element field.

[0117] 4. Key BSS parameters

[0118] For example, key BSS parameters may include one or more of the following: including a Channel Switch Announcement element, including an Extended Channel Switch Announcement element, and changing enhanced distributed channel access.The following are the modification elements for the EDCA parameters element, including the inclusion of a Quiet element, modification of the DSSS parameter set, modification of the CF parameter set element, modification of the HT operation element, including the inclusion of a Widebandwidth Channel Switch element, including the inclusion of a Channel Switch Wrapper element, including the inclusion of an Operating Mode Notification element, including the QuietChannel element, modification of the VHT (very high throughput) operation element, modification of the HE (high efficient) operation element, insertion of a Broadcast TWT element, including the inclusion of the BSS Color Change Announcement element, and modification of MU. The EDCA parameter set element and the Spatial Reuse parameter set element are also considered. One or more of the above key BSS parameters can also be listed as key parameters of the link.

[0119] 5. Specific key BSS parameters

[0120] Specific key BSS parameters can refer to parameters related to channel changes within the key BSS parameters. Specifically, specific key BSS parameters include one or more of the following: inclusion of a ChannelSwitch Announcement element, inclusion of an Extended Channel Switch Announcement element, inclusion of a Wide Bandwidth Channel Switch element, and inclusion of a Channel Switch Wrapper element.

[0121] 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.

[0122] See Figure 3a , Figure 3a This is a schematic diagram of the structure of a communication system 100 provided in an embodiment of this application. Figure 3aTaking a wireless local area network (WLAN) as an example, this application describes a communication system 100. The communication system 100 includes a station 101 and a station 102. Station 101 and station 102 can communicate via 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 yet another scenario, station 101 is an AP MLD, and station 102 is an AP MLD or an AP; in yet another scenario, station 101 is a Non-AP MLD, and station 102 is a Non-AP MLD or a STA (e.g., a single-link station). Of course, this WLAN may also include other devices. Figure 3a The number and type of devices shown are merely illustrative.

[0123] See Figure 3b , Figure 3b This is a schematic diagram of the structure of a communication system 200 provided in an embodiment of this application. See also... Figure 3c , Figure 3c This is a schematic diagram of the structure of a communication system 300 provided in an embodiment of this application. Figure 3b , Figure 3c Schematic diagrams of communication system 200 and communication system 300 are shown respectively. Communication system 200 and communication system 300 are illustrated using the example of multi-link devices communicating with other devices through multiple links in a wireless local area network.

[0124] Specifically, Figure 3b A scenario of communication between AP MLD and Non-AP MLD is shown. AP MLD includes AP1 and AP2, and Non-AP MLD includes STA1 and STA2. AP MLD and Non-AP MLD communicate in parallel using Link 1 and Link 2.

[0125] Figure 3cThis diagram 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 STAs: STA602-1, STA602-2, and STA602-3; Non-AP MLD603 includes two subordinate STAs: STA603-1 and STA603-2; STA604-1 and STA604 are single-link devices. AP MLD601 can communicate with Non-AP MLD602 via links 1, 2, and 3; communicate with Non-AP MLD603 via links 2 and 3; and communicate with STA604 via 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 in AP MLD601, operating in the 2.4 GHz band, 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 within AP MLD601, can transmit uplink or downlink data with STA603-1, operating in the 5GHz band within Non-AP MLD 603, via link 2. It can also transmit uplink or downlink data with STA602-2, operating in the 5GHz band within Non-AP MLD602, via link 2. Similarly, AP601-3, operating in the 6GHz band within AP MLD601, can transmit uplink or downlink data with STA602-3, operating in the 6GHz band within Non-AP MLD602, via link 3. It can also transmit uplink or downlink data with STA603-2 within the Non-AP MLD via link 3.

[0126] Understandable Figure 3b Only two frequency bands are shown to be supported by the AP MLD. Figure 3cThis illustration uses the AP MLD601, which supports three frequency bands (2.4GHz, 5GHz, and 6GHz), with each 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 or STA side, this link can also be understood as the station operating on that link. In practical applications, AP MLDs and Non-AP MLDs can support more or fewer frequency bands, meaning they can operate on more or fewer links. This embodiment does not limit this.

[0127] See Figure 4 , Figure 4 This is a schematic diagram of the architecture of multiple BSSID sets provided in the embodiments of this application. That is to say, Figure 4 The AP MLDs shown are collocated AP MLD sets.

[0128] 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.

[0129] 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, which carries information about multiple APs, such as a beacon frame or probe response frame. Reporting APs include both transport APs and regular APs from the multiple BSSID set. The AP MLD set sharing a location with the reporting AP includes the following APs:

[0130] (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.

[0131] (2) All APs in the AP MLD where the non-transmission 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-transmission AP is located in the multi-BSSID set where the reporting AP (or transmission AP) is located.

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

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

[0134] Optionally, the reporting AP can be a regular AP in the AP MLD (as shown in the image). Figure 4 For example, AP3 with MAC address BSSID_3 and AP5 with MAC address BSSID_5, or a transmission AP in a set of multiple BSSIDs, can send the unicast service indication information described in this application.

[0135] For example, with Figure 4 Taking AP1x as the reporting AP as an example, the APs co-located with AP1x in the MLD set include the following APs:

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

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

[0138] (3) Figure 4The AP MLD that satisfies conditions 1) and 2) above 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 on the same link as AP1x.

[0139] In the 802.11 protocol, a STA typically has two operating modes: non-energy-saving mode and 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 remains in an active state when transmitting data with the AP; otherwise, it remains 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. Setting the energy-saving bit in the frame control field of the MAC header to 1 indicates that the STA is in energy-saving mode, while setting it to 0 indicates that the STA is in non-energy-saving mode.

[0140] Understandably, the terms "data transmission" and "transmitted data" used in this application refer to communication in general, and "data" refers to communication information in general, not limited to data information, but also signaling information, etc.

[0141] In either Wireless Network Management (WNM) or Target Wake-Up Time (TWT) power-saving mechanisms, a STA can communicate a wake-up cycle with the Access Point (AP). At the beginning of each wake-up cycle, the AP sends a broadcast Traffic Indication Map (TIM) frame to multiple corresponding STAs. This TIM frame is much shorter than a Beacon frame. The TIM elements in the TIM frame inform the multiple STAs whether there is a corresponding downlink service indication. Because the TIM frame is much shorter than the Beacon frame, the STA can achieve power saving. In the WNM power-saving mechanism, the TIM Broadcast Interval field in the TIM request frame sent by the STA or the TIM response from the AP indicates the wake-up cycle. Alternatively, in the TWT power-saving mechanism, the wake-up cycle corresponds to the TWT wake-up interval. The TWT wake-up interval is calculated using the decimal part of the TWT wake-up duration and the TWT wake-up interval exponent field in the TWT element. Specifically, TWT wake-up interval = decimal part of TWT wake-up duration * 2 (TWT wake-up interval exponent).

[0142] Optional, see Figure 5 , Figure 5 This is a schematic diagram of the frame structure of the TIM frame provided in an embodiment of this application. For example... Figure 5 As shown, the frame carrier in a TIM frame may include at least one of the following: a type field, an unprotected WNM behavior field, a timestamp field, a beacon check field, a TIM element field, and a link identification information field. The unprotected WNM behavior field indicates different behavior values. The timestamp field indicates clock information. The TIM element field indicates whether the STA or Non-APMLD identified by the AID has downlink traffic. The link identification information field indicates the specific link. The beacon check field indicates the BSS where the link indicated by the link identification information field resides, or whether the AP indicated by the link identification information field has updated critical BSS parameters; alternatively, the beacon check field indicates whether the link indicated by the link identification information field has updated critical parameters.

[0143] For example, if the BSS containing the link indicated by the Link Identification Information field has a critical BSS parameter update, or if the link indicated by the Link Identification Information field has a critical parameter update, then the value of the Beacon check field is incremented by 1. The aforementioned BSS parameters can also be understood as link parameters. Correspondingly, critical BSS parameters can be understood as critical link parameters.

[0144] For example, the Non-AP MLD remembers the values ​​of the Beacon check fields for each link received last time. If the Beacon check field value for a recently received link differs from the value of the Beacon check field value for the same link received last time, the Non-AP MLD will receive a beacon frame sent by the AP MLD on that link. Alternatively, the Non-AP MLD can send a probe request frame on any link. This probe request frame requests the latest critical BSS parameters for one or more APs. The probe request frame includes the link identifiers for one or more APs, and optionally, the MLD identifier of the MLD where the AP is located, such as the MLD MAC address or MLD sequence number of the AP MLD. After receiving the probe request frame, the AP MLD replies with an acknowledgment frame, and then sends a probe response frame to the Non-AP MLD. This probe response frame includes the latest critical BSS parameters for one or more APs requested by the Non-AP MLD. The Non-AP MLD receives this and replies with an acknowledgment frame. In this probe response frame, the value of the Beacon check field for one or more APs has changed. Understandably, the beacon frame carries the latest critical BSS parameters for this link.

[0145] Understandably, since the TIM frame includes a link identification information field, when using the TIM frame, even if a Non-AP MLD includes multiple STAs within a BSS, only one AID is needed. By combining the link identification information and the AID, it is possible to determine which station on the link indicated by the link identification information field has downlink service.

[0146] It is also understandable that the Beacon check field and link identification information field included in the TIM frame can be placed in other management frames. These multiple fields (referring to the Beacon check field and link identification information field) can be used individually to notify the BSS where the link indicated by the link identification information field resides whether there are any changes / updates to critical BSS parameters. The above method can also be used to address whether there are changes / updates to critical BSS parameters for multiple BSSs where multiple links reside. For example, the management frame can include the number of links, n Beacon check fields, and n link identification information fields, where n is indicated by the number of links. Another example is that the management frame can include a link identification bitmap and n Beacon check fields, optionally including a length field for the link identification bitmap, where n is the number of links in the link identification bitmap set to the first value (e.g., 1). One or more Beacon check fields are initialized to 0. See one implementation example. Figure 6 , Figure 6 This is a schematic diagram of the frame structure of a management frame provided in an embodiment of this application. For example... Figure 6 As shown, the frame carrier of this management frame includes: a type field, an unprotected WNM behavior field, a link number field, a Beacon check field, a TIM element field, and a link identification information field. When the number of links indicated by the link number field is multiple, each / every link has a Beacon check field, a TIM element field, and a link identification information field. Optionally, the frame carrier of this management frame may also include one or more timestamp fields. Figure 6 The management frame shown can be used to indicate whether multiple sites on the link indicated by each link identification information field have downlink traffic.

[0147] In summary, as mentioned above Figure 4 As shown, some APs (such as non-transport APs in the same set of multiple BSSIDs) cannot send management frames. Therefore, these APs cannot notify their associated STAs / Non-AP MLDs whether critical BSS parameters of the BSS managed by these APs have been updated by sending management frames, such as beacon frames or probe response frames. As a result, the STAs / Non-AP MLDs associated with these APs and listening on the links where these APs are working are unaware that these APs have updated critical BSS parameters. Consequently, after these APs update their critical BSS parameters, the STAs / Non-AP MLDs associated with these APs cannot function properly or cannot communicate with these APs.

[0148] Therefore, this application provides a method for managing key BSS parameters applicable to multiple links. This method allows one AP MLD to assist another AP MLD in notifying multiple APs of that other AP MLD whether their key BSS parameters have been updated, thus solving the problem that some APs cannot notify of key BSS parameter updates. It also assists STAs in receiving the latest key BSS parameters, ensuring that after multiple APs of another AP MLD update their key BSS parameters, the Non-AP MLD associated with that other AP MLD can still function normally. The technical solution provided in this application will be described in detail below with reference to more accompanying drawings.

[0149] Example 1

[0150] Embodiment 1 of this application introduces a method for managing key BSS parameters applicable to multiple links. Specifically, it involves an update indication of key BSS parameters applicable to multiple links. This method can indicate not only the update count values ​​of key BSS parameters for multiple APs in a first AP MLD (this value is located in the reduced neighbor report (RNR) element), but also the update count values ​​of key BSS parameters for multiple APs in a second AP MLD. This allows non-AP MLDs associated with the second AP MLD to listen on links where the non-transmitting APs of the second AP MLD are located and to function normally; in other words, non-AP MLDs have more listening channel options.

[0151] Each reporting AP in the first AP MLD needs to send the key BSS parameter update count values ​​corresponding to multiple APs in the first AP MLD to the Non-AP MLD associated with the first AP MLD, or to surrounding sites (surrounding sites include sites managed by the reporting AP and unassociated sites). It also needs to send the key BSS parameter update count values ​​corresponding to multiple APs in the second AP MLD. For ease of description, Embodiment 1 of this application uses a reporting AP in the first AP MLD as an example.

[0152] See Figure 7 , Figure 7 This is a schematic flowchart illustrating a key BSS parameter management method applicable to multiple links provided in this application embodiment. 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 the multiple BSSID set. The first STA can be a single-link STA or any STA in the Non-AP MLD. For ease of description, the following description uses the first STA in the Non-AP MLD as an example. The first AP and the first STA operate on the same link. Figure 7 As shown, the association method applicable to multi-link devices includes, but is not limited to, the following steps:

[0153] S101, the first AP of the first AP MLD generates a first frame. This first frame is used to indicate the key BSS parameter update information corresponding to multiple APs of the first AP MLD and the key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the AP MLD that does not belong to the transmission AP in the multi-BSSID set where the first AP is located. Among them, the key BSS parameter update information corresponding to an AP is used to determine whether there is a key BSS parameter update for the BSS managed by that AP.

[0154] The first AP mentioned above can be any reporting AP in the first AP MLD, and the reporting AP can be the AP that sends management frames (such as beacon frames or probe response frames). The key BSS parameter update information mentioned above includes key BSS parameter update count values.

[0155] The first frame mentioned above can be a management frame, such as a beacon frame, probe response frame, or other management frame. This first frame can be used to indicate the key BSS parameter update count values ​​for multiple APs within the first AP MLD (here, multiple APs refer to all APs within the first AP MLD, or all APs within the first AP MLD excluding the first AP, or some APs), and the key BSS parameter update count values ​​for multiple APs within the second AP MLD (here, multiple APs refer to all APs within the second AP MLD, or some APs). The second AP MLD is the AP MLD belonging to the non-transmitting AP in the multi-BSSID set where the first AP resides. Optionally, when one or more key BSS parameters change, the key BSS parameter update count value is incremented by 1.

[0156] A critical BSS parameter update count value corresponding to an AP can be used to determine whether there are critical BSS parameter updates for the BSS managed by that AP. This critical BSS parameter update count value can be a natural number and is initialized to 0. When the critical BSS parameter of a BSS managed by an AP changes, the critical BSS parameter update count value corresponding to that AP increases by 1. Since there are multiple AP critical BSS parameter update count values, each critical BSS parameter update count value corresponds one-to-one with an AP's identifier. The AP's identifier can be the AP's MAC address, the AP's link identifier, or a combination of the AP's operating set, channel number, and BSSID. This critical BSS parameter update count value can be carried in the reduced neighbor report element (RNR element) of the first frame. The reduced neighbor report element is described below.

[0157] Optionally, in addition to the critical BSS parameter update count field, the RNR element in this embodiment may also include a link identifier field and an AP MLD identifier field (such as an MLD ID field). The link identifier field indicates a specific AP or site whose link is operational. Understandably, the link identifier field may be called a link identifier information field or a link identifier bitmap field (a bitmap used to indicate the link identifiers of multiple APs), and this embodiment does not limit its usage. The critical BSS parameter update count field indicates the critical BSS parameter update count value. Understandably, the critical BSS parameter update count field may be called a critical BSS parameter update field, and this embodiment does not limit its usage. The AP MLD identifier field can be used to identify a specific AP MLD. Understandably, the AP MLD identifier field may be an MLDID field, an MLD index field, or an MLD sequence number field, etc., and its name is not limited.

[0158] Because the RNR element includes a link identifier field and an identifier field of the AP MLD (such as the MLD ID field), when using the RNR element, even if each AP MLD includes multiple APs, each AP MLD has an identifier. By combining the link identifier information and the identifier information of the AP MLD, it is possible to determine which AP on the link indicated by the link identifier field has the critical BSS parameter updated.

[0159] Understandably, for a site to associate with an access point (AP), it first needs to detect the AP's existence through scanning. Scanning typically takes two forms: active scanning and passive scanning.

[0160] Passive scanning refers to a site receiving management frames sent by the AP on a channel, such as beacon frames, association response frames, reassociation response frames, authentication frames, and probe response frames. For example, a site may hop between different channels to search for beacon frames sent by the AP. Once a site obtains the AP's control information via beacon frames, it can further obtain additional information from the AP by interacting with probe request and probe response frames.

[0161] Active scanning refers to a site actively sending a broadcast probe request frame even if it does not hear a Beacon frame. If the AP that receives the probe request frame meets certain conditions, it can initiate random channel access to reply with a probe response frame.

[0162] During the scanning process, in order to assist the site in scanning quickly, the AP will carry a simplified neighbor reporting element in the management frame, such as the beacon frame and the probe response frame, to avoid the site scanning the channel continuously and reduce the site's scanning time.

[0163] APs carry simplified neighbor reporting elements in management frames, such as beacon frames and probe response frames. During site scanning, the AP receives management frames sent by the APs, obtains information about surrounding APs based on the simplified neighbor reporting elements, and then selects appropriate APs to associate with.

[0164] Specifically, the simplified neighbor reporting element typically carries one or more Neighbor AP information fields, used to describe one or more neighbor APs and their respective BSS information. See also Figure 8a , Figure 8a This is a schematic diagram of the frame structure of the RNR element provided in an embodiment of this application. For example... Figure 8a As shown, the simplified neighbor reporting element may include some or all of the following fields: the target beacon transmission time (TBTT) information header field, the operating class field, the channel number field, and one or more TBTT informationset fields. The TBTT informationset field includes one or more TBTT information fields, with one TBTT information field corresponding to one neighbor AP.

[0165] The TBTT header field carries at least one of the following information:

[0166] The TBTT information Field Type indicates the type of TBTT information. Together with the TBTT information length field, it indicates the format of the TBTT information field.

[0167] Filtered neighbor AP field: Indicates whether the SSIDs of all BSSs carried in the Neighbor AP information field match the SSIDs in the probe request frame.

[0168] 1 bit reserved (Reserved field).

[0169] The TBTT information count field indicates the number of TBTT information fields contained in the TBTT information collection.

[0170] The TBTT information Length field indicates the length of each TBTT information field. The specific information format for different lengths is shown in Table 1 below.

[0171] Table 1

[0172]

[0173] The following describes the specific format of the TBTT information field when the TBTT information length is 12 bytes.

[0174] The Neighbor AP TBTT offset field indicates the offset of the neighbor AP's Beacon transmission time from that of the reporting AP.

[0175] The BSSID (BSS Identifier) ​​field indicates the BSS identifier corresponding to this neighboring AP.

[0176] The Short SSID field indicates the service set identifier to which the neighboring AP belongs.

[0177] The BSS Parameter field indicates relevant parameters of the neighboring AP.

[0178] Optionally, in addition to the TBTT bias field, BSSID field, Short SSID field, and BSS parameter field of the neighboring AP, a TBTT information field in the RNR element of this application embodiment also includes at least one of the following: key BSS parameter update count value field, link ID field, and multi-link device identifier (MLD ID) field.

[0179] See Figure 8b , Figure 8b This is a schematic diagram of the frame structure of a TBTT information field in an RNR element provided in an embodiment of this application. For example... Figure 8bAs shown, a TBTT information field of this RNR element includes at least one of the following fields: TBTT bias field of the neighboring AP, BSSID field, Short SSID field, BSS parameter field, critical BSS parameter update count value field, link ID field, and multi-link device identifier (MLD ID) field. Understandably, Figure 8b This is just an example; the order of the key BSS parameter update count field, link ID field, and MLD ID field included in this TBTT information field, as well as whether there are other fields between them, are not limited.

[0180] Understandably, the three key BSS parameter update count field, link identifier field, and MLD identifier field are independent and can be carried in the RNR element simultaneously or separately. In other words, the RNR element can carry some of these three fields.

[0181] The key BSS parameter update count field indicates the key BSS parameter update count value. The link identifier field indicates the specific link. The MLD ID field indicates the specific AP MLD. Understandably, since one TBTT information field corresponds to one AP, and one AP manages one BSS, each TBTT information field carries an MLD ID field and a link identifier field. Therefore, when using the first frame, even if an AP MLD includes multiple APs within a BSS, the different APs in the AP MLD can be distinguished by combining the link indicated by the link identifier field and the MLD indicated by the MLD ID field. In other words, the link identifier field combined with the MLD ID field can uniquely identify an AP.

[0182] The BSS Parameter field is used to indicate relevant parameters of the neighboring AP. Specifically, the relevant parameters of the neighboring AP include the following information:

[0183] The OCT recommended field indicates that the neighboring AP expects to exchange management type MPDUs with it via the OCT mechanism.

[0184] Same SSID (Same Service Set Identifier) ​​field: Indicates whether the neighboring AP and the reporting AP have the same SSID.

[0185] The Multiple BSSID field indicates whether the neighboring AP belongs to a set of multiple BSSIDs.

[0186] The Transmitted BSSID field further indicates whether the neighboring AP is a Transmitted BSSID or a non-transmitted BSSID if the neighboring AP is part of a multiple BSSID set.

[0187] The "Member Of ESS With 2.4 / 5GHz Co-Located AP" field indicates whether the neighboring AP is co-located with a 2.4 / 5GHz AP (i.e., not a 6GHz only AP) and is a member of an extended service set.

[0188] The Unsolicited Probe Response Active field indicates whether the neighboring AP has enabled active probe response.

[0189] Co-located AP field: Indicates whether the neighboring AP and the reporting AP are co-located.

[0190] It should be noted that, in the embodiments of this application, the AP described in the Neighbor Report element or the Reduced Neighbor Report element is the reported access point (AP). Subsequent references to neighbor APs can be understood as reported APs. The AP that sends the Neighbor Report element or the Reduced Neighbor Report element is the reporting access point (AP).

[0191] The above content introduced the RNR element. The following section explains the second AP MLD.

[0192] Optionally, the second AP MLD mentioned above is the AP MLD belonging to the non-transmitting AP in the multi-BSSID set where the first AP is located.

[0193] For example, with Figure 4 For example, assuming AP1x is the first AP, the first AP sends a management frame, such as a beacon frame or probe response frame, carrying an RNR element. The RNR element carries the key BSS parameter update counts for multiple APs in the first AP MLD and the key BSS parameter update counts for multiple APs in the second AP MLD. Since AP MLD1 is the first AP MLD, then AP MLD3 is the second AP MLD. Therefore, the first frame includes the key BSS parameter update counts corresponding to multiple APs in AP MLD1, such as the key BSS parameter update counts corresponding to AP2y and AP3; it also includes the key BSS parameter update counts corresponding to multiple APs in AP MLD3, such as the key BSS parameter update counts corresponding to AP1y, AP2z, and AP4y. Optionally, the management frame sent by the first AP may also include the key BSS parameter update count value corresponding to AP1x. The key BSS parameter update count value of AP1x is located in the MLD common information of the multi-link (ML) element or in the EHT operation element. The MLD common information field in the ML element or the EHT operation element also carries the link identifier of the first AP, i.e., AP1x.

[0194] For example, still using Figure 4 For example, assuming AP2x is the first AP, AP MLD2 is the first AP MLD, then AP MLD1 and AP MLD3 are both second AP MLDs. Therefore, this first frame includes the key BSS parameter update counts corresponding to multiple APs of AP MLD2, such as the key BSS parameter update count corresponding to AP4x; it also includes the key BSS parameter update counts corresponding to multiple APs of AP MLD1, such as the key BSS parameter update counts corresponding to AP1x, AP2y, and AP3; and it also includes the key BSS parameter update counts corresponding to multiple APs of AP MLD3, such as the key BSS parameter update counts corresponding to AP1y, AP2z, and AP4y. Optionally, the management frame sent by the first AP may also include the key BSS parameter update count value corresponding to AP2x. The key BSS parameter update count value of AP2x is located in the ML element or the MLD common information field or the EHT operation element. The MLD common information field in the ML element or the EHT operation element also carries the link identifier of the first AP, i.e., AP2x.

[0195] For example, with Figure 4 For example, assuming AP4x is the first AP, AP MLD2 is the first AP MLD, then AP MLD3 and AP MLD4 are both second AP MLDs. Therefore, this first frame includes the key BSS parameter update counts corresponding to multiple APs of AP MLD2, such as the key BSS parameter update counts corresponding to AP2x; it also includes the key BSS parameter update counts corresponding to multiple APs of AP MLD3, such as the key BSS parameter update counts corresponding to AP1y, AP2z, and AP4y; and it also includes the key BSS parameter update counts corresponding to multiple APs of AP MLD4, such as the key BSS parameter update counts corresponding to AP4z and AP5. Optionally, the management frame sent by the first AP may also include the key BSS parameter update count value corresponding to AP4x. The key BSS parameter update count value of AP4x is located in the MLD public information of the ML element or in the EHT operation element. The MLD public information field in the ML element or the EHT operation element also carries the link identifier of the first AP, i.e., AP4x.

[0196] For example, with Figure 4 For example, assuming AP3 is the first AP, AP MLD1 is the first AP MLD, and there is no second AP MLD. Therefore, the first frame includes the key BSS parameter update count values ​​corresponding to multiple APs of AP MLD1, such as the key BSS parameter update count values ​​corresponding to AP1x and AP2y. Optionally, the management frame sent by the first AP also includes the key BSS parameter update count value corresponding to AP3. The BSS parameter update count value of AP3 is located in the ML element or MLD common information or EHT operation element. The MLD common information field in the ML element or the EHT operation element also carries the link identifier of the first AP3.

[0197] S102, the first AP of the first AP MLD sends the first frame on its working link.

[0198] Specifically, the first AP of the first AP MLD needs to send the aforementioned first frame on its operating link to the Non-AP MLD associated with it, or to sites surrounding the first AP. Sites surrounding the first AP include sites managed by the first AP and unassociated sites. The following uses AP-managed sites as an example to illustrate the key BSS parameter management method applicable to multiple links described in this application embodiment. It is understood that the first frame can be sent via broadcast or multicast.

[0199] It is also understood that the Non-AP MLD associated with the first AP MLD in the embodiments of this application has two meanings: (1) all Non-AP MLDs that have established multi-link associations with the first AP MLD, wherein the Non-AP MLD may be associated with some APs in the first AP MLD or with all APs; (2) Non-AP MLDs that are associated with the first AP of the first AP MLD, wherein the Non-AP MLD may be associated with some APs in the first AP MLD or with all APs, but the some APs or all APs must include the first AP. Wherein, the first AP is the reporting AP.

[0200] S103, the first STA of the Non-AP MLD receives the first frame on its working link.

[0201] The first STA can be a site managed by the first AP or a nearby site, and can be informed whether the BSS to which the first STA belongs has updated key BSS parameters. The first STA and the first AP operate on the same link / frequency band / channel.

[0202] S104, the first STA of the Non-AP MLD determines, based on the first frame, whether there are any critical BSS parameter updates for multiple BSS managed by multiple APs in the AP MLD associated with the Non-AP MLD.

[0203] Specifically, after receiving the first frame, the first STA of the Non-AP MLD can parse it to obtain the key BSS parameter update counts corresponding to multiple APs of the first AP MLD and the key BSS parameter update counts corresponding to multiple APs of the second AP MLD. The Non-AP MLD parses from the first frame the M key BSS parameter update counts corresponding to the M APs (these M APs are associated with the Non-AP MLD) in the APMLD associated with it. For each of these M APs, the Non-AP MLD compares the currently received key BSS parameter update count with the previously received key BSS parameter update count; or compares whether the currently received key BSS parameter update count is the same as the previously received key BSS parameter update count. If the currently received key BSS parameter update count is different from the previously received key BSS parameter update count, then the Non-AP MLD determines that the BSS managed by this AP has key BSS parameter updates. Optionally, if the received critical BSS parameter update count value is different from the previously received critical BSS parameter update count value, the Non-AP MLD can listen for beacon frames on the link where this AP is operating. The beacon frame carries the latest critical BSS parameters for this AP. Alternatively, a STA of the Non-AP MLD can also obtain the latest critical BSS parameters for the AP by sending a probe request frame, as described above.

[0204] If the critical BSS parameter update count value received this time is the same as the critical BSS parameter update count value received last time, it means that the BSS managed by this AP has no critical BSS parameter updates, and Non-AP MLD can leave it alone.

[0205] Optionally, Non-AP MLD will record the key BSS parameter update count values ​​corresponding to each link received last time.

[0206] For example, with Figure 4For example, assume the first AP is AP1x, AP MLD1 is the first AP MLD, and AP MLD3 is the second AP MLD. Assume Non-AP MLD1 is associated with AP1y, AP2z, and AP4y of AP MLD3, and M equals 3. The APs associated with Non-AP MLD1 are AP1y, AP2z, and AP4y. The first frame includes the key BSS parameter update counts corresponding to AP1x, AP2y, and AP3 of AP MLD1; it also includes the key BSS parameter update counts corresponding to AP1y, AP2z, and AP4y of AP MLD3. That is, N equals 6. Non-AP MLD1 parses from the first frame the three key BSS parameter update counts corresponding to AP1y, AP2z, and AP4y in AP MLD3 associated with Non-AP MLD1. For AP1y, Non-AP MLD2 compares the received critical BSS parameter update count for AP1y with the previously received critical BSS parameter update count for AP1y. If they are different, it indicates that the BSS managed by AP1y has had its critical BSS parameters updated. Non-AP MLD1 can listen for beacon frames carrying the latest critical BSS parameters on link 1 where AP1y resides. For AP2z, Non-AP MLD1 compares the received critical BSS parameter update count for AP2z with the previously received critical BSS parameter update count for AP2z. If they are different, it indicates that the BSS managed by AP2z has had its critical BSS parameters updated. Non-AP MLD1 can listen for beacon frames carrying the latest critical BSS parameters on link 2 where AP2z resides. For AP4y, Non-AP MLD1 compares the newly received critical BSS parameter update count value for AP4y with the previously received critical BSS parameter update count value for AP4y. If they are different, it indicates that the BSS managed by AP4y has had its critical BSS parameters updated. Non-AP MLD1 can then listen for beacon frames carrying the latest critical BSS parameters on link 4 where AP4y resides.

[0207] For example, suppose Non-AP MLD2 is associated with AP1y and AP4y of AP MLD3. In this case, M equals 2, and the APs associated with Non-AP MLD2 are AP1y and AP4y. Therefore, for AP1y, Non-AP MLD2 compares the currently received key BSS parameter update count value corresponding to AP1y with the previously received key BSS parameter update count value corresponding to AP1y. If they are different, it means that the BSS managed by AP1y has had a key BSS parameter update. Non-AP MLD2 can listen for beacon frames carrying the latest key BSS parameters on link 1 where AP1y is located. For AP4y, Non-AP MLD2 compares the currently received key BSS parameter update count value corresponding to AP4y with the previously received key BSS parameter update count value corresponding to AP4y. If they are different, it means that the BSS managed by AP4y has had a key BSS parameter update. Non-AP MLD2 can listen for beacon frames carrying the latest key BSS parameters on link 4 where AP4y is located.

[0208] Understandably, when the first STA is a single-link STA, and the first STA switches from one link to another, the first STA can use the method of the embodiments of this application to obtain the key BSS parameter update count value.

[0209] As can be seen, the embodiments of this application, by sending the first frame from the first AP, not only indicate the key BSS parameter update count values ​​corresponding to multiple APs in the first AP MLD, but also indicate the key BSS parameter update count values ​​corresponding to multiple APs in the second AP MLD. This allows one AP to help provide the key BSS parameter update count values ​​corresponding to multiple APs in another AP MLD, so that the STA can determine whether there is a key BSS parameter update based on the comparison between the key BSS parameter update count value received this time and the key BSS parameter update count value received last time. This can assist the STA in receiving the latest key BSS parameters, and enable the Non-AP MLD associated with the second AP MLD to listen on the link where the non-transmission AP in the second AP MLD is located and still work normally. In other words, for the non-AP MLD, there are more listening channel options. Since in 802.11be, it is possible that some or all APs in an AP MLD are non-transmission APs, the solution provided by the embodiments of this application can solve the problem that some non-transmission APs cannot send management frames to notify key BSS parameter updates, thereby increasing the completeness and diversity of key BSS parameter update indication.

[0210] As an optional embodiment, the method for each Non-AP MLD to obtain the initial value of the key BSS parameter update count for multiple APs of its associated AP MLD is as follows:

[0211] 1. During the association phase, the association response frame sent by one AP in the AP MLD carries the key BSS parameter update count values ​​of multiple APs in that AP MLD at that time.

[0212] 2. When a STA in a Non-AP MLD requests to switch to another link, the channel handover signaling implicitly instructs the AP MLD to request the updated critical BSS parameter counts of the AP operating on that link. The associated AP MLD must include the latest updated critical BSS parameter counts of the AP currently operating on the other link in the response frame replied by the STA on the corresponding link.

[0213] The channel handover signaling includes the link identifier of the AP that the STA wants to switch to. For example, with Figure 4 For example, suppose STA1 in Non-AP MLD1 requests a switch from Link 1 to Link 2, and the channel handover signaling includes the link identifier of Link 2. Assuming Non-AP MLD1 is associated with AP MLD, this channel handover signaling implicitly requests the key BSS parameter update count value of AP2y, which is currently operating on Link 2, from AP MLD1. The response frame returned by AP MLD1 on Link 1 corresponding to STA1 must carry the latest key BSS parameter update count value of AP2y, which is now operating on Link 2.

[0214] When the critical BSS parameter update count value received from the AP is different from the previously received critical BSS parameter update count value, in addition to obtaining the latest critical BSS parameters by receiving beacon frames and sending probe requests, the locally stored critical BSS parameter update count value also needs to be updated to the critical BSS parameter update count value received this time.

[0215] As another optional embodiment, an AP MLD has a common SSID; alternatively, each AP has a unique SSID. During the neighbor AP or AP MLD discovery phase, to enable the Non-AP MLD to quickly discover and associate with the best AP MLD, this includes quickly discovering the preferred SSID. For the reported AP (i.e., neighbor AP) in the AP MLD, the Short SSID field of each reported AP (i.e., neighbor AP) in the RNR element of this embodiment carries a Short SSID calculated based on the SSID of the AP MLD to which the reported AP (neighbor AP) belongs. The Short SSID calculation method can refer to the 802.11-2016 protocol.

[0216] It is understood that the embodiments of this application can be implemented individually or in combination. Figure 7 The methods shown are examples of embodiments, and the embodiments of this application are not limited thereto.

[0217] As can be seen, compared with directly carrying the shortSSID of the reported AP in the RNR element, the Non-AP MLD of this application embodiment can quickly select the best APMLD for association during the discovery phase by using the short SSID of the AP MLD where the reported AP is located, thus improving the association efficiency.

[0218] As another optional embodiment, the first frame described above may also be used to indicate specific key BSS parameters of multiple APs in the first AP MLD and specific key BSS parameters of multiple APs in the second AP MLD. The specific key BSS parameters are BSS parameters related to channel changes. Specific key BSS parameters may include one or more of the following: channel change notification elements, extended channel change notification elements, wideband channel change elements, and wideband channel change envelope elements.

[0219] Example 2

[0220] Embodiment 2 of this application provides a method for updating key BSS parameters, applied in a multi-link device, and describes how to update key BSS parameters. It is understood that in practical applications, Embodiment 2 of this application can be implemented alone or in combination with the aforementioned Embodiment 1; this application does not limit this.

[0221] See Figure 9 , Figure 9 This is a schematic flowchart illustrating a method for updating key BSS parameters provided in an embodiment of this application. The AP MLD includes one or more APs, and the second AP is any AP within the AP MLD. The second AP may or may not be a reporting AP. The second STA may be a single-link STA or any STA within a Non-AP MLD. For ease of description, the following description uses the second STA in a Non-AP MLD as an example. The second AP and the second STA operate on the same link. Figure 9 As shown, the method for updating key BSS parameters includes, but is not limited to, the following steps:

[0222] S201, the second AP of the first AP MLD generates a second frame, which is used to indicate specific key BSS parameters of multiple APs of the first AP MLD and / or specific key BSS parameters of multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs where the second AP is located.

[0223] The second frame mentioned above can be a management frame, such as a beacon frame, or other frames. This second frame can be the same frame as the first frame in the aforementioned embodiment one, or it can be a different frame; this application does not limit this. This second frame can be used to indicate specific key BSS parameters for multiple APs in the first AP MLD (here, multiple APs refer to all APs in the first AP MLD, or all APs within the first AP MLD except for the first AP, or some APs), and / or specific key BSS parameters for multiple APs in the second AP MLD (here, multiple APs refer to all APs within the second AP MLD, or some APs).

[0224] The aforementioned key BSS parameters may include one or more of the following: inclusion of a Channel Switch Announcement element, inclusion of an Extended Channel Switch Announcement element, inclusion of a Wide Bandwidth Channel Switch element, and inclusion of a Channel Switch Wrapper element. If any or some of these four elements change / are updated, and the site is not notified in time (possibly because the site did not receive the updated elements), the site will be unable to find the corresponding AP in the AP MLD, thus preventing communication with that AP. Therefore, these key BSS parameters are required.

[0225] Optionally, this specific key BSS parameter may also include one or more of the following: including a quiet element, including a quiet channel element. Optionally, this specific key BSS parameter may also include one or more of the following: changing EDCA parameter elements, modifying the DSSS parameter set, modifying the CF parameter set elements, modifying HT operation elements, including operation mode notification elements, modifying VHT operation elements, modifying HE operation elements, inserting broadcast TWT elements, including BSS color change notification elements, modifying MU EDCA parameter set elements, and modifying spatial multiplexing parameter set elements. One or more of the above specific key BSS parameters may also be listed as key parameters of the link.

[0226] Optionally, the aforementioned specific key BSS parameters can be carried in the AP information of the multi-link (ML) element in the second frame. The specific key BSS parameters for each AP are carried in the respective AP information of the ML element.

[0227] The following section introduces the multi-link elements.

[0228] See Figure 10a , Figure 10a This is a schematic diagram of a frame structure of an ML element provided in an embodiment of this application. For example... Figure 10a As shown, the ML element includes: a common control field, MLD common information, and one or more optional sub-elements. Optionally, the MLD common information includes an MLD MAC address field, and optionally, an authentication algorithm field and a link ID field. The MLD MAC address field indicates the address of the MLD, which identifies an MLD. Optionally, the MLD address is the MLD's MAC address, which can also be described as identifying an AP MLD management entity. The MAC address of this AP MLD can be the same as or different from the MAC addresses of any of the n APs included in the AP MLD. For example, the MAC address of this AP MLD can be a common MAC address that identifies the AP MLD.

[0229] Optionally, the public control field may include an MLD MAC address presence field (or MLD MAC address occurrence field or MLD MAC address occurrence identifier), used to indicate whether an MLD MAC address field exists in the MLD public information. Optionally, the public control field may also include an authentication algorithm occurrence field, used to indicate whether an authentication algorithm field exists in the MLD public information. Optionally, the aforementioned "occurrence field" may include 1 bit, with a first value indicating the corresponding field's presence and a second value indicating the corresponding field's absence. For example, the first value is 1, and the second value is 0. Optionally, the public control field may also include a link ID occurrence field, used to indicate whether a link ID field exists in the MLD public information.

[0230] Optionally, an ML element may also include one or more sub-elements, each sub-element describing information about an AP in an AP MLD. The content of each sub-element includes the link identifier of the AP. Optionally, each sub-element may also include AP-related fields, such as the SSID field, timestamp field, beacon interval field, and elements related to the AP. These AP elements may include BSS load elements, EHT capability elements, and EHT operation elements.

[0231] See Figure 10b , Figure 10b This is a schematic diagram of the first half of the frame structure of the ML element provided in the embodiments of this application. For example... Figure 10b As shown, Figure 10b The first half of the ML element is shown, excluding the sub-elements of AP information in the AP MLD. The first half of the ML element includes: a common control field and MLD common information. The common control field includes one or more of the following: MLD MAC address occurrence field, Link ID occurrence field, MLD sequence number occurrence field, and sub-element occurrence field. Optional fields include an authentication algorithm occurrence field. The MLD MAC address occurrence field indicates whether the MLD common information includes an MLD MAC address field. The Link ID occurrence field indicates whether the MLD common information includes a Link ID field. The MLD sequence number occurrence field indicates whether the MLD common information includes an MLD sequence number field. These fields can be indicated by a single bit (e.g., 1 indicates presence, 0 indicates absence), or by two values ​​for each field (the first value indicating presence, the second indicating absence).

[0232] Optional, Figure 10a The first half of the ML element shown (here referring to) Figure 10a The public control fields and MLD public information shown can also be used... Figure 10b The first half of the ML element shown (here referring to) Figure 10bThe replacement of the public control field and MLD public information shown can be used by the AP MLD to provide further detailed information to the site's Non-AP MLD, such as in the probe response frame or association response frame. Optionally, the public control field includes an MLD public information presence field to indicate whether the MLD public information appears, or whether fields other than the MLD MAC address or MLD sequence number in the MLD public information appear, to help further reduce duplicate information (assuming the Non-AP MLD has already obtained the authentication algorithm and link identifier). In the beacon frame, to avoid excessive content in the beacon frame and to avoid duplication with the information of each AP in the RNR element, the beacon frame only needs to carry the MLD public information in the ML element, or a portion of the fields in the MLD public information. In this case, the public control field includes a sub-element presence field to indicate that the sub-elements in the ML element that indicate specific information about multiple APs do not appear, such as... Figure 10b As shown.

[0233] If the reporting AP belongs to a multi-BSSID set, the reporting AP also needs to send multi-BSSID elements, including a non-transmitted profile indicating information about one or more non-transmitted APs. If a non-transmitted AP comes from an AP MLD, then... Figure 10b The first half of the ML element shown or Figure 10a The complete ML element shown can also be placed in the information of this non-transmitting AP.

[0234] The following section will introduce several elements included in specific key BSS parameters.

[0235] See Figure 11a , Figure 11a This is a schematic diagram of a frame structure including a channel change notification element provided in an embodiment of this application. For example... Figure 11aAs shown, the data includes channel change notification elements, including: a Channel Switch Mode field, a New Channel Number field, and a Channel Switch Count field. The Channel Switch Mode field indicates any restrictions on transmission until a channel switch. The New Channel Number field indicates the channel number the STA will switch to. The Channel Switch Count field indicates the number of target beacon transmission times (TBTTs) until the STA sends the Channel Switch Count field switches to the new channel. A Channel Switch Count field set to 1 indicates that the switch occurs immediately before the next TBTT. A Channel Switch Count field set to 0 indicates that the switch occurs any time after the frame containing the Channel Switch Count field is transmitted.

[0236] See Figure 11b , Figure 11b This is a schematic diagram of the frame structure including the extended channel change notification element provided in an embodiment of this application. For example... Figure 11bAs shown, the extended channel change notification element includes: a Channel SwitchMode field, a New Operating Class field, a New Channel Number field, and a Channel Switch Count field. The Channel SwitchMode field indicates the transmission restrictions before the channel switch. The New Operating Class field indicates the number of the operating class the station will switch to after the channelswitch. The New Channel Number field indicates the channel number the station will switch to. The Channel Switch Count field indicates how many TBTTs are required from sending this element to switching to the channel; a setting of 0 indicates the change will occur before the next TBTT, while a setting of 1 indicates it can occur at any time after sending the element.

[0237] See Figure 11c , Figure 11c This is a schematic diagram of a frame structure including wideband channel changing elements provided in an embodiment of this application. For example... Figure 11c As shown, this includes wide-bandwidth channel change elements, including: a New Channel Width field, a New Channel Center Frequency Segment 0 field, and a New Channel Center Frequency Segment 1 field. The New Channel Width field defines the BSS bandwidth. New Channel Center Frequency Segment 0 defines a channel center frequency for a BSS bandwidth of 20, 40, 80, 160, or 80+80MHz. New Channel Center Frequency Segment 1 defines a channel center frequency for a BSS bandwidth of 160 or 80+80MHz.

[0238] See Figure 11d , Figure 11d This is a schematic diagram of the frame structure of the quiet element provided in the embodiments of this application. For example... Figure 11dAs shown, the Quiet element includes the following fields: Quiet Count, QuietPeriod, Quiet Duration, and Quiet Offset. The QuietCount field is set to the number of TBTTs until the beacon interval during which the next quiet interval starts. The QuietPeriod field is set to the number of beacon intervals between the start of the periodic quiet intervals defined by this Quiet element. A QuietPeriod field set to 0 indicates that no periodic quiet interval is defined. The Quiet Duration field sets the length of the quiet interval in TUs. The Quiet Offset field sets the offset in TUs between the start of the quiet interval and the TBTT specified by the Quiet Count field. The value of the Quiet Offset field is less than one beacon frame interval.

[0239] Understandably, after the silencing element takes effect, the AP no longer communicates with the STA, and the STA remains silent so that the STA can perform other operations.

[0240] Optionally, the aforementioned second AP MLD is the AP MLD belonging to the non-transmitting AP within the multi-BSSID set where the second AP resides. Specifically, the meaning of the second AP MLD can be found in the relevant description in the aforementioned Embodiment 1.

[0241] S202, the second AP of the first AP MLD sends the second frame on its working link.

[0242] Specifically, the second AP of the first AP MLD needs to send the aforementioned second frame on its operating link to the Non-AP MLD associated with the first AP MLD, or to sites surrounding the second AP. Sites surrounding the second AP include sites managed by the second AP and unassociated sites. Understandably, the second frame can be sent via broadcast, multicast, or unicast.

[0243] S203, the second STA of the Non-AP MLD receives the second frame on its working link.

[0244] The second STA can be a site managed by the second AP or a nearby site, and can obtain specific key BSS parameters of multiple APs in the MLD associated with the first STA. The second STA operates on the same link / frequency band / channel as the second AP.

[0245] S204, the second STA of the Non-AP MLD parses the second frame to obtain specific key BSS parameters of multiple APs in the APMLD associated with the Non-AP MLD.

[0246] Specifically, after the second STA of the Non-AP MLD receives the second frame, it can parse the second frame and extract specific key BSS parameters from the ML elements of the second frame for K APs (where K is a positive integer) in the AP MLD associated with the Non-AP MLD. For each of these K APs, the Non-AP MLD can adjust the channel information of the STA corresponding to that AP according to the specific key BSS parameters of each AP.

[0247] For example, with Figure 4For example, assuming AP2x is the second AP, AP MLD2 is the first AP MLD, and AP MLD1 and AP MLD3 are both second AP MLDs. Assuming Non-AP MLD1 is associated with AP1x and AP2y of AP MLD1, and K equals 2, the APs associated with Non-AP MLD1 are AP1x and AP2y. The second frame carries specific key BSS parameters for multiple APs (either all or some) in AP MLD1, AP MLD2, and AP MLD3. For instance, the second frame carries specific key BSS parameters for all APs in AP MLD1, as well as for all APs in AP MLD2 and AP MLD3. Therefore, for AP1x in AP MLD1, assuming the specific key BSS parameters of AP1x indicate that the station needs to switch to channel number 9, Non-AP MLD1 will switch the STA corresponding to AP1x to the channel with channel number 9 for communication, according to the indication of the specific key BSS parameters of AP1x. For AP2y in AP MLD1, assuming that the specific key BSS parameter of AP2y indicates that the operation set to be transformed is A, then Non-AP MLD1 will transform the STA corresponding to AP2y from the current operation set to the operation set identified by operation set A according to the specific key BSS parameter of AP2y.

[0248] Understandably, Embodiment 2 of this application is described using one AP in the AP MLD as an example. In practical applications, each AP in the AP MLD can perform... Figure 9 Steps S201 to S202 are shown.

[0249] Understandably, the second STA can be a single-link STA or one of the STAs in a Non-AP MLD. When the second STA is a single-link STA, and it switches from one link to another, it can use the method described in this application to obtain specific key BSS parameters.

[0250] As can be seen, in this implementation, the second frame sent by one AP of the AP MLD not only explicitly carries specific key BSS parameters of multiple APs of that AP MLD, but also explicitly carries specific key BSS parameters of multiple APs of other AP MLDs. These specific key BSS parameters include elements related to channel changes. This can help the Non-AP MLD to promptly obtain the working channel change status of all APs of the AP MLD while listening to one or more links (not all links), enabling it to function normally.

[0251] As an optional implementation, when a STA in a Non-AP MLD requests to switch to another link, the channel handover signaling implicitly indicates that it needs to request specific key BSS parameters of the AP operating on that link from the AP MLD, or explicitly carries specific signaling instructions indicating the specific key BSS parameters required, such as using one or more element IDs, optionally also carrying one or more element ID extensions, or directly reusing non-inherited elements in the 802.11-2016 protocol to request parameters of the corresponding element within that non-inherited element. The response frame replied by the associated AP MLD on the link corresponding to the STA must carry the latest specific BSS parameters of the AP currently operating on the other link.

[0252] Optionally, the signaling for channel switching may also include the AP's identifier, such as the link identifier; and the identifier of the MLD to which the AP is located, such as the MLD sequence number or the MLD's MAC address.

[0253] See Figure 12 , Figure 12 This is a schematic diagram of the frame structure of a non-inherited element provided in an embodiment of this application. For example... Figure 12 As shown, a non-inherited element includes an element ID, a length, an element ID extension, one or more element IDs, and one or more element ID extensions. The element ID and element ID extension indicate that the element is a non-inherited element. The length indicates the length following the element's length field. One or more element IDs, optionally, and one or more element ID extensions indicate one or more specific element contents requested. The element ID extensions only appear together when the element ID value is 255; otherwise, the element ID can independently indicate an element.

[0254] 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.

[0255] 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 as a software functional module. 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 following will combine... Figures 13 to 17 The communication device according to the embodiments of this application is described in detail. The communication device is an access point of an access point multi-link device or a site of a non-access point multi-link device. Further, the communication device can be a device in an AP MLD; or, the communication device can be a device in a Non-AP MLD.

[0256] In the case of using integrated units, see Figure 13 , Figure 13 This is a schematic diagram of the communication device 1 provided in an embodiment of this application. 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 a first AP within the first AP MLD or a chip within the first AP. The first AP is a reporting AP and belongs to the first AP MLD. For example... Figure 13 As shown, the communication device 1 includes a processing unit 11 and a transceiver unit 12.

[0257] Processing unit 11 is used to generate a first frame, which indicates the key BSS parameter update information corresponding to multiple APs of the first AP MLD and the key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the AP MLD that does not belong to the transmission AP in the set of multiple BSSIDs where the first AP is located. The key BSS parameter update information corresponding to an AP is used to determine whether the BSS managed by the AP has key BSS parameter updates. Transceiver unit 12 is used to send the first frame on the link where the communication device 1 is operating.

[0258] Optionally, the critical BSS parameter update information includes the critical BSS parameter update count value.

[0259] As can be seen, in this communication device 1, the first frame generated by the processing unit 11 can not only indicate the key BSS parameter update count values ​​corresponding to multiple APs of the first AP MLD, but also indicate the key BSS parameter update count values ​​corresponding to multiple APs of the second AP MLD. This enables one AP to help provide multiple APs of another AP MLD with their corresponding key BSS parameter update count values, so that the STA can determine whether there is a key BSS parameter update based on the comparison between the key BSS parameter update count value received this time and the key BSS parameter update count value received last time. This can assist the STA in receiving the latest key BSS parameters, and also enable the Non-AP MLD associated with the second AP MLD to listen on the link where the non-transmitting AP is located in the second AP MLD and still work normally.

[0260] Optionally, the processing unit 11 is further configured to generate a second frame, which is used to indicate specific key BSS parameters of the multiple APs of the first AP MLD and specific key BSS parameters of the multiple APs of the second AP MLD; the transceiver unit 12 is further configured to transmit the second frame on the link where the communication device 1 is operating.

[0261] It should be understood that the communication device 1 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.

[0262] See Figure 14 , Figure 14 This is a schematic diagram of the communication device 2 provided in an embodiment of this application. The communication device 2 can be a first STA or a chip within the first STA, such as a Wi-Fi chip. The first STA can be a single-link STA, or it can be a STA in a Non-AP MLD. Figure 14 As shown, the communication device 2 includes a transceiver unit 21 and a processing unit 22.

[0263] The transceiver unit 21 is configured to receive a first frame on the link where the communication device 2 is operating. The first frame is configured to indicate the key BSS parameter update information corresponding to multiple APs of the first AP MLD and the key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs where the first AP is located. The key BSS parameter update information corresponding to an AP is used to determine whether the BSS managed by the AP has a key BSS parameter update. The processing unit 22 is configured to determine, based on the first frame, whether the multiple BSSs managed by multiple APs in the AP MLD associated with the communication device 2 have key BSS parameter updates.

[0264] Optionally, the critical BSS parameter update information includes the critical BSS parameter update count value.

[0265] As can be seen, in the communication device 2, the processing unit 22 can update the count value of the key BSS parameters indicated by the first frame to know whether the key BSS parameters of its own BSS have been updated, thereby ensuring that it can receive the latest key BSS parameters.

[0266] Optionally, the transceiver unit 21 is further configured to receive a second frame on the link where the communication device 2 is operating. The second frame is used to indicate specific key BSS parameters of multiple APs in the first AP MLD and specific key BSS parameters of multiple APs in the second AP MLD. The processing unit 22 is further configured to parse the second frame to obtain specific key BSS parameters of multiple APs in the AP MLD associated with the communication device 2.

[0267] It should be understood that the communication device 2 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.

[0268] See Figure 15 , Figure 15 This is a schematic diagram of the communication device 3 provided in an embodiment of this application. The communication device 3 can be a first AP MLD or a chip within the first AP MLD, such as a Wi-Fi chip, or it can be a second AP within the first AP MLD or a chip within the second AP. The second AP can be any AP within the first AP MLD. For example... Figure 15 As shown, the communication device 3 includes a processing unit 31 and a transceiver unit 32.

[0269] Processing unit 31 is used to generate a second frame, which is used to indicate specific key BSS parameters of multiple APs of the first AP MLD and / or specific key BSS parameters of multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs where the second AP is located. Transceiver unit 32 is used to send the second frame on the link where the communication device 3 is operating.

[0270] As can be seen, in the communication device 3, the second frame generated by the processing unit 31 not only explicitly carries specific key BSS parameters of multiple APs of the AP MLD, but also explicitly carries specific key BSS parameters of multiple APs of other AP MLDs. These specific key BSS parameters include elements related to channel changes. This can help the Non-AP MLD to promptly obtain the working channel change status of all APs of the AP MLD while listening to one or more links (not all links), enabling it to function normally.

[0271] 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 the second AP of the first AP MLD in the aforementioned embodiment 2. For the sake of brevity, they will not be described in detail here.

[0272] See Figure 16 , Figure 16 This is a schematic diagram of the communication device 4 provided in an embodiment of this application. The communication device 4 can be a second STA or a chip within a second STA, such as a Wi-Fi chip. The second STA can be a single-link STA, or it can be one of the STAs in a Non-AP MLD. Figure 16 As shown, the communication device 4 includes a transceiver unit 41 and a processing unit 42.

[0273] The transceiver unit 41 is used to receive a second frame on the link where the communication device 4 is operating. The second frame is used to indicate specific key BSS parameters of multiple APs of the first AP MLD and / or specific key BSS parameters of multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs where the second AP is located. The processing unit 42 is used to parse the second frame to obtain specific key BSS parameters of multiple APs in the AP MLD associated with the second STA.

[0274] As can be seen, in the communication device 4, the processing unit 42 parses the second frame to obtain the latest key BSS parameters of multiple APs in the AP MLD associated with its own MLD. It can perform corresponding processing based on the received latest key BSS parameters to ensure normal communication.

[0275] It should be understood that the communication device 4 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 4 are respectively to realize the corresponding operations of the second STA of the Non-AP MLD in the aforementioned embodiment 2. For the sake of brevity, they will not be described in detail here.

[0276] The above describes the AP MLD and STA according to embodiments of this application. The following describes the possible product forms of the AP MLD and STA. It should be understood that any product possessing the above-described features... Figure 13 or Figure 15 Any product in any form that possesses the aforementioned AP MLD functionality, Figure 14 or Figure 16 Any product in any form that incorporates the functionality of the STA described herein falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the AP MLD and STA in the embodiments of this application to these specific examples.

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

[0278] See Figure 17 , Figure 17 This is a schematic diagram of the structure of the communication device 1000 provided in an embodiment of this application. The communication device 1000 can be an AP MLD or a STA, or a device thereof. Figure 17As shown, 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, such as a baseband processor or a central processing unit (CPU). The baseband processor can process communication protocols and communication data, while the CPU can control the communication device (e.g., base station, baseband chip, terminal, terminal chip, DU or CU, etc.), execute computer programs, and process data from the computer programs. The transceiver 1002, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 1002 can include a receiver and a transmitter. The receiver, also known as a receiver circuit, is used to implement a receiving function; the transmitter, also known as a transmitter or transmitting circuit, is used to implement a transmitting function. Optionally, the communication device 1000 may also include an antenna 1003 and / or a radio frequency unit (not shown in the figure). The antenna 1003 and / or radio frequency unit may be located inside the communication device 1000 or separate from the communication device 1000, that is, the antenna 1003 and / or radio frequency unit may be deployed remotely or in a distributed manner.

[0279] 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.

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

[0281] In one design, the communication device 1000 can be used to perform the functions of the first AP in the first AP MLD of the aforementioned embodiment 1: the processor 1001 can be used to perform... Figure 7 Step S101 and / or other processes used in the technology described herein; transceiver 1002 can be used to perform Figure 7 Step S102 and / or other processes used in the techniques described herein.

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

[0283] In one design, the communication device 1000 can be used to perform the function of the second AP of the first AP MLD in the aforementioned embodiment two: the processor 1001 can be used to perform... Figure 9 Step S201 and / or other processes used in the technology described herein; transceiver 1002 can be used to perform Figure 9 Step S202 and / or other processes used in the techniques described herein.

[0284] In one design, the communication device 1000 can be used to perform the STA function of the Non-AP MLD in the aforementioned embodiment two: the processor 1001 can be used to perform... Figure 9 Step S204 and / or other processes used in the technology described herein; transceiver 1002 can be used to perform Figure 9 Step S203 and / or other processes used in the techniques described herein.

[0285] 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.

[0286] 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.

[0287] In one implementation, the communication device 1000 may include circuitry capable of transmitting, receiving, or communicating in any of the foregoing 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.

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

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

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

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

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

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

[0294] (6) Others, etc.

[0295] As a possible product form, the AP MLD and STA described in the embodiments of this application can be implemented by a general-purpose processor.

[0296] A general-purpose processor for implementing AP MLD includes processing circuitry and input / output interfaces that are internally connected and communicate with the processing circuitry.

[0297] 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 circuit is used to perform... Figure 7 Step S101 and / or other processes used in the techniques described herein; the input / output interface is used to perform Figure 7 Step S102 and / or other processes used in the techniques described herein.

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

[0299] A general-purpose processor for implementing Non-AP MLD includes processing circuitry and input / output interfaces that are internally connected and communicate with the processing circuitry.

[0300] In one design, the general-purpose processor can be used to perform the function of the first STA of the Non-AP MLD in the aforementioned embodiment. Specifically, the processing circuit is used to perform... Figure 7 Step S104 and / or other processes used in the techniques described herein; the input / output interface is used to perform Figure 7 Step S103 and / or other processes used in the techniques described herein.

[0301] In another design, the general-purpose processor can be used to perform the second STA function of the Non-AP MLD in the aforementioned embodiment two. Specifically, the processing circuit is used to perform... Figure 9 Step S204 and / or other processes used in the techniques described herein; the input / output interface is used to perform Figure 9 Step S203 and / or other processes used in the techniques described herein.

[0302] As a possible product form, the AP MLD and STA described in the embodiments of this application can also be implemented using the following: one or more FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

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

[0304] 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.

[0305] 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.

[0306] 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.

[0307] This application also provides a wireless communication system including a first AP MLD and a STA, which can perform the methods in any of the foregoing embodiments.

[0308] 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.

[0309] 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.

[0310] 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

1. A method for managing key BSS parameters applicable to multi-link systems, characterized in that, include: The first station STA of the first non-access point multi-link device (Non-AP MLD) receives a first frame on its working link. The first frame is used to indicate the key BSS parameter update information corresponding to multiple APs of the first AP MLD and the key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located. The key BSS parameter update information corresponding to an AP is used to determine whether the BSS managed by the AP has key BSS parameter updates. Based on the first frame, the first STA of the first Non-AP MLD determines whether there are any critical BSS parameter updates for multiple BSS managed by multiple APs in the AP MLD associated with the first STA.

2. The method according to claim 1, characterized in that, The key BSS parameter update information includes key BSS parameter update count values, and the first Non-AP MLD records the key BSS parameter update count values ​​corresponding to each link received last time.

3. The method according to claim 1 or 2, characterized in that, The key BSS parameter update information includes the key BSS parameter update count value; The method further includes: If the first STA of the first Non-AP MLD receives a key BSS parameter update count value corresponding to the second AP in the AP MLD associated with the first Non-AP MLD, and this value is different from the key BSS parameter update count value of the second AP previously received by the first Non-AP MLD, then the station associated with the second AP in the first Non-AP MLD receives a beacon frame from the second AP, the beacon frame carrying the latest key BSS parameters of the second AP.

4. The method according to claim 1 or 2, characterized in that, The key BSS parameter update information includes the key BSS parameter update count value; The method further includes: If the first STA of the first Non-AP MLD receives a key BSS parameter update count value corresponding to the second AP in the AP MLD associated with the first Non-AP MLD, and this value is different from the key BSS parameter update count value of the second AP that the first Non-AP MLD last received, then one STA of the first Non-AP MLD obtains the latest key BSS parameter of the second AP by sending a probe request frame.

5. The method according to claim 2, characterized in that, The method further includes: If the key BSS parameter update count value corresponding to an AP of the first AP MLD indicated in the first frame is different from the key BSS parameter update count value corresponding to the AP that the first Non-AP MLD last received, then the first Non-AP MLD will update the key BSS parameter update count value corresponding to the AP that is stored locally to the key BSS parameter update count value corresponding to the AP indicated in the first frame.

6. The method according to claim 2, characterized in that, When one of the key BSS parameters changes, the key BSS parameter update count is incremented by 1.

7. The method according to claim 1, characterized in that, The first frame includes a link identifier field and a multi-link device (MLD) identifier field. The link identifier field is used to indicate the reported AP, and the MLD identifier field is used to indicate the AP MLD where the reported AP is located.

8. The method according to claim 7, characterized in that, The key BSS parameter update count value field, carrying the key BSS parameter update count value, the link identifier field, and the MLD identifier field are carried in the simplified neighbor report (RNR) element of the first frame.

9. The method according to claim 8, characterized in that, The RNR element contains a beacon frame target transmission time (TBTT) information field that carries a key BSS parameter update count, a link identifier field, and an MLD identifier field.

10. The method according to claim 9, characterized in that, The value of the Short Service Set Identifier (SSID) field of the AP in the RNR element is obtained based on the SSID of the MLD where the AP is located.

11. The method according to claim 1, characterized in that, The first frame is any one of the following: a beacon frame, a probe response frame, or a correlation response frame.

12. The method according to claim 1, characterized in that, The method further includes: The first STA receives a second frame on its operating link, the second frame being used to indicate specific key BSS parameters of multiple APs of the first AP MLD and specific key BSS parameters of multiple APs of the second AP MLD; The first STA parses the second frame to obtain specific key BSS parameters of multiple APs in the AP MLD associated with the Non-AP MLD.

13. The method according to claim 12, characterized in that, In the second frame, a specific key BSS parameter of an AP includes one or more of the following: a channel change notification element, an extended channel change notification element, a wideband channel change element, and a wideband channel change envelope element.

14. The method according to claim 12, characterized in that, The specific key BSS parameter of an AP in the second frame also includes one or more of the following: including a silence element, including a silence channel element.

15. The method according to claim 12, characterized in that, The specific key BSS parameters are carried in the multi-link ML elements.

16. A communication device, characterized in that, include: The transceiver unit is used to receive a first frame on the link where the communication device is operating. The first frame is used to indicate the key BSS parameter update information corresponding to multiple APs of the first AP MLD and the key BSS parameter update information corresponding to multiple APs of the second AP MLD. The second AP MLD is the AP MLD to which the non-transmitting AP belongs in the set of multiple BSSIDs where the first AP is located. The key BSS parameter update information corresponding to an AP is used to determine whether the BSS managed by the AP has key BSS parameter updates. The processing unit is configured to determine, based on the first frame, whether there are any updates to key BSS parameters for multiple BSS managed by multiple APs in the AP MLD associated with the communication device.

17. The communication device according to claim 16, characterized in that, The key BSS parameter update information includes key BSS parameter update count values, and the communication device records the key BSS parameter update count values ​​corresponding to each link received last time.

18. The communication device according to claim 16, characterized in that, The key BSS parameter update information includes the key BSS parameter update count value; The transceiver unit is further configured to receive a beacon frame of the second AP when the communication device receives a key BSS parameter update count value corresponding to the second AP in the AP MLD associated with the communication device, which is different from the key BSS parameter update count value of the second AP previously received by the communication device. The beacon frame carries the latest key BSS parameters of the second AP.

19. The communication device according to claim 16 or 17, characterized in that, The key BSS parameter update information includes the key BSS parameter update count value; The transceiver unit is further configured to send a probe request frame to obtain the latest key BSS parameters of the second AP when the communication device receives a key BSS parameter update count value corresponding to the second AP in the AP MLD associated with the communication device, which is different from the key BSS parameter update count value of the second AP previously received by the communication device.

20. The communication device according to claim 19, characterized in that, The processing unit is further configured to: When the key BSS parameter update count value corresponding to an AP of the first AP MLD indicated by the first frame is different from the key BSS parameter update count value corresponding to the AP that was last received by the communication device, the key BSS parameter update count value corresponding to the AP stored locally is updated to the key BSS parameter update count value corresponding to the AP indicated by the first frame.

21. The communication device according to claim 19, characterized in that, When one or more of the key BSS parameters change, the key BSS parameter update count is incremented by 1.

22. The communication device according to claim 21, characterized in that, The key BSS parameter update count value field, carrying the key BSS parameter update count value, the link identifier field, and the MLD identifier field are carried in the simplified neighbor report (RNR) element of the first frame.

23. The communication device according to claim 22, characterized in that, The RNR element contains a Beacon Frame Target Transmission Time (TBTT) information field, which carries a key BSS parameter update count, a link identifier field, and an MLD identifier field. Each TBTT information field corresponds to one AP.

24. The communication device according to claim 16, characterized in that, The first frame is any one of the following: a beacon frame, a probe response frame, or a correlation response frame.

25. The communication device according to claim 16, characterized in that, The transceiver unit is also configured to receive a second frame on the link where the communication device is operating. The second frame is used to indicate specific key BSS parameters of the multiple APs of the first AP MLD and specific key BSS parameters of the multiple APs of the second AP MLD. The processing unit is also used to parse the second frame to obtain specific key BSS parameters of multiple APs in the AP MLD associated with the communication device.

26. The communication device according to claim 25, characterized in that, In the second frame, a specific key BSS parameter of an AP includes one or more of the following: a channel change notification element, an extended channel change notification element, a wideband channel change element, and a wideband channel change envelope element.

27. The communication device according to claim 25, characterized in that, The specific key BSS parameter of an AP in the second frame also includes one or more of the following: including a silence element, including a silence channel element.

28. The communication device according to claim 25, characterized in that, The specific key BSS parameters are carried in the multi-link ML elements.

29. A communication device, characterized in that, It includes a processor and a transceiver, the transceiver being used to send and receive information or frames, and the processor being used to perform the method as described in any one of claims 1-15.

30. 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-15.

31. A computer program product containing instructions, characterized in that, When the instructions are executed on a computer, the computer causes the computer to perform the method as described in any one of claims 1-15.

32. A chip, 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 described in any one of claims 1-15.

33. A first non-access point multi-link device (non-AP MLD), characterized in that, It includes a first STA and a second STA, wherein the first STA is used to implement the method as described in any one of claims 1-15.

Images