METHOD FOR MANAGING CRITICAL SERVICE SET PARAMETERS, FIRST ACCESS POINT, FIRST ACCESS POINT MULTIPATH DEVICE, AND CHIP OR CHIP SYSTEM

Abstract

The invention relates to the field of wireless communication, and specifically to a method for managing critical Basic Service Set (BSS) parameters applicable to multiple transmissions and related communication devices, access point multi-link devices (AP MLDs), non-access point multi-link devices (non-AP MLDs), computer-readable recording devices, chips or systems, such as, wireless local area networks supporting the 802.11be standard. The method involves: the first Access Point (AP) in the first MLD AP creates and transmits the first frame, which indicates the critical BSS parameter update counter values ​​corresponding to the APs in the first MLD AP and the critical BSS parameter update counter values ​​corresponding to the APs in the second MLD AP, and the second MLD AP is the MLD AP that does not transmit in the multi-BSSID set including the first AP.This allows some or all APs within a number of MLD APs to notify the STAs managed by those APs whether the critical BSS parameters of the BSSs managed by those APs are updated, to assist the STAs in receiving the latest critical BSS parameters.

Description

Key BSS parameter management method and related device applicable to multi-link

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

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

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

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

[0005] When the BSS of an AP in an access point multilink device (AP MLD) is updated, some station multilink devices or stations may be unable to obtain the latest information about the BSS managed by these APs, thereby causing these station multilink devices or stations to be unable to communicate normally with these special APs.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a key BSS parameter management method and related devices suitable for multi-links, which can help some APs or all APs in some AP MLDs to notify the STAs they manage whether the key BSS parameters of the AP (the BSS it manages) have been updated, so as to assist the STAs in receiving the latest key BSS parameters, so that after the key BSS parameters of the AP are updated, the STAs can also communicate normally with it.

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

[0009] In a first aspect, the present application provides a BSS parameter management method applicable to multiple links, which is applied to 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: a first AP of the first AP MLD generates a first frame and sends the first frame on the link on which it works. 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 a second AP MLD, wherein the second AP MLD is an AP MLD to which non-transmitting APs belong in a multi-basic service set identifier (BSSID) set where the first AP is located, and key BSS parameter update information corresponding to an AP is used to determine whether a BSS managed by the AP has a key BSS parameter update.

[0010] Optionally, the above-mentioned key BSS parameter update information includes a key BSS parameter update count value.

[0011] Optionally, when one or more parameters in the key BSS parameters change, the key BSS parameter update count value is increased by 1.

[0012] This solution uses the first frame to indicate not only the critical BSS parameter update counts corresponding to multiple APs in the first AP MLD but also the critical BSS parameter update counts corresponding to multiple APs in the second AP MLD. This allows one AP to provide the critical BSS parameter update counts corresponding to multiple APs in another AP MLD. This allows STAs to determine whether there have been any critical BSS parameter updates by comparing the currently received critical BSS parameter update count with the previously received critical BSS parameter update count. This helps STAs receive the latest critical BSS parameters and enables non-AP MLDs associated with the second AP MLD to listen on links containing non-transmitting APs in the second AP MLD and function normally. In other words, non-AP MLDs have more listening channel options. Because 802.11be may allow some or all APs in an AP MLD to be non-transmitting APs, the solution provided by this embodiment of the application solves the problem of some non-transmitting APs being unable to send management frames to notify critical BSS parameter updates, thereby increasing the completeness and diversity of critical BSS parameter update indications.

[0013] In combination with the first aspect, in a possible implementation, after the first AP of the first AP MLD sends the above-mentioned first frame, the method also includes: the first AP of the first AP MLD generates a second frame, where the second frame is 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; and the first AP of the first AP MLD sends the second frame on the link on which it works.

[0014] 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. This helps non-AP MLDs promptly learn about the working channel changes of all APs in the AP MLD while monitoring one or more links (not all links), allowing them to operate normally.

[0015] In a second aspect, the present application provides a BSS parameter management method applicable to multiple links, which is applied to a first STA, which can be a single-link STA or a STA in a non-AP multi-link device (MLD). The first STA operates on a link with a first AP. The BSS parameter management method applicable to multiple links includes: the first STA of the non-AP MLD receives a first frame on the link on which it operates, and determines, based on the first frame, whether multiple BSSs managed by multiple APs in an AP MLD associated with the first STA have key BSS parameter updates. The first frame is used to indicate key BSS parameter update information corresponding to multiple APs in the first AP MLD, and key BSS parameter update information corresponding to multiple APs in a second AP MLD. The second AP MLD is an AP MLD to which a non-transmitting AP belongs in the multi-BSSID set to which the first AP belongs. The key BSS parameter update information corresponding to one AP is used to determine whether the BSS managed by the one AP has a key BSS parameter update.

[0016] It is understandable that when the first STA is a STA in a Non-AP MLD, the AP MLD associated with the first STA may be an AP MLD associated with the Non-AP MLD where the first STA is located.

[0017] Optionally, the above-mentioned key BSS parameter update information includes a key BSS parameter update count value.

[0018] Optionally, when one or more parameters in the key BSS parameters change, the key BSS parameter update count value is increased by 1.

[0019] In combination 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 receives a second frame on the link on which it works, 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 parses the second frame to obtain specific key BSS parameters of multiple APs in the AP MLD associated with the Non-AP MLD.

[0020] In a third aspect, the present application provides a communication device, which may be a first AP MLD or a chip in the first AP MLD, such as a Wi-Fi chip, or may be a first AP in the first AP MLD or a chip in the first AP, including:

[0021] A processing unit is configured to generate a first frame, where the first frame is configured 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, where the second AP MLD is an AP MLD to which a non-transmission AP belongs in a multiple basic service set identifier (BSSID) set where the first AP is located, wherein key BSS parameter update information corresponding to an AP is used to determine whether a BSS managed by the AP has a key BSS parameter update; and a transceiver unit is configured to send the first frame on a link where the communication device operates.

[0022] Optionally, the above-mentioned key BSS parameter update information includes a key BSS parameter update count value.

[0023] Optionally, when one or more parameters in the key BSS parameters change, the key BSS parameter update count value is increased by 1.

[0024] In combination with the third aspect, in one possible implementation, the above-mentioned processing unit is also used to generate a second frame, which is 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 above-mentioned transceiver unit is also used to send the second frame on the link on which it works.

[0025] In a fourth aspect, the present application provides a communication device, which may be a first STA or a chip in the first STA, such as a Wi-Fi chip. The first STA may be a single-link STA or a STA in a Non-AP Multi-Link Layer (MLD) mode. The communication device includes:

[0026] A transceiver unit is configured to receive a first frame on a link where the communication device operates, the first frame being configured 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 a second AP MLD, wherein the second AP MLD is an AP MLD to which a non-transmission AP belongs in a multi-BSSID set where the first AP is located, wherein key BSS parameter update information corresponding to an AP is used to determine whether a BSS managed by the AP has key BSS parameter updates; and a processing unit is configured to determine, based on the first frame, whether multiple BSSs managed by multiple APs in the AP MLD associated with the communication device have key BSS parameter updates.

[0027] Optionally, the above-mentioned key BSS parameter update information includes a key BSS parameter update count value.

[0028] Optionally, when one or more parameters in the key BSS parameters change, the key BSS parameter update count value is increased by 1.

[0029] In combination with the fourth aspect, in one possible implementation, the above-mentioned transceiver unit is further used to receive a second frame on the link on which it works, where the second frame is 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 above-mentioned 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.

[0030] In an implementation of any of the above aspects, the first frame includes a link identification field and a multi-link device MLD identification field. The link identification field is used to indicate the reported AP, and the MLD identification field is used to indicate the AP MLD where the reported AP is located.

[0031] Optionally, the first frame further includes a key BSS parameter count value field, and the key BSS parameter update count value field is used to indicate a key BSS parameter update count value.

[0032] In an implementation manner of any of the above aspects, the key BSS parameter update count value field, the link identifier field, and the MLD identifier field are carried in a Reduced Neighbor Report RNR element of the first frame.

[0033] It is understandable that the three fields, namely the key BSS parameter update count field, the link identifier field, and the MLD identifier field, are independent and can be carried in the RNR element at the same time or at different times. In other words, the RNR element can carry some of these three fields.

[0034] In one implementation of any of the above aspects, a beacon frame target transmission time TBTT information field in the above RNR element carries a key BSS parameter update count value, a link identification field, and an MLD identification field, and one TBTT information field corresponds to one AP.

[0035] In an implementation manner of any of the above aspects, 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.

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

[0037] In an implementation manner of any of the above aspects, the specific key BSS parameters are carried in a multi-link ML element.

[0038] In a fifth aspect, the present application provides a method for updating key BSS parameters, which is applied to a first AP MLD, where a 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 generates a second frame and transmits 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 a second AP MLD, where the second AP MLD is an AP MLD to which non-transmitting APs belong in a multi-BSSID set to which the second AP belongs.

[0039] Optionally, the 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 wide bandwidth channel change element, and a wide bandwidth channel change envelope element.

[0040] Optionally, the above-mentioned specific key BSS parameters are carried in a multi-link ML element.

[0041] In a sixth aspect, the present application provides a method for updating key BSS parameters, which is applied to a second STA, where the second STA can be a single-link STA or a STA in a Non-AP MLD. The second STA and the second AP operate on a link. The method for updating key BSS parameters includes: the second STA receives a second frame on the link on which it operates, and parses 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 of the first AP MLD and / or specific key BSS parameters of multiple APs of the second AP MLD, where the second AP MLD is the AP MLD to which the non-transmitting AP belongs in the multi-BSSID set where the second AP is located.

[0042] It is understandable that when the second STA is a STA in the Non-AP MLD, the AP MLD associated with the second STA may be the AP MLD associated with the Non-AP MLD where the second STA is located.

[0043] Optionally, the 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 wide bandwidth channel change element, and a wide bandwidth channel change envelope element.

[0044] Optionally, the above-mentioned specific key BSS parameters are carried in a multi-link ML element.

[0045] In a seventh aspect, the present application provides a communication device, which may be a first AP MLD or a chip in the first AP MLD, such as a Wi-Fi chip, or may be a second AP in the first AP MLD or a chip in the second AP, including:

[0046] a processing unit, configured to generate a second frame, wherein 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 a second AP MLD, wherein the second AP MLD is an AP MLD to which a non-transmitting AP belongs in a multi-BSSID set where the second AP is located; and a transceiver unit, configured to send the second frame on a link where the communication device operates.

[0047] Optionally, the 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 wide bandwidth channel change element, and a wide bandwidth channel change envelope element.

[0048] Optionally, the above-mentioned specific key BSS parameters are carried in a multi-link ML element.

[0049] In an eighth aspect, the present application provides a communication device, which may be a second STA or a chip in the second STA, such as a Wi-Fi chip. The first STA may be a single-link STA or a STA in a Non-AP Multi-Link Layer (MLD) mode. The communication device includes:

[0050] The transceiver unit is configured to receive a second frame on a link on which the communication device operates, the second frame being configured to indicate specific key BSS parameters of multiple APs of the first AP MLD and / or specific key BSS parameters of multiple APs of a second AP MLD, where the second AP MLD is an AP MLD to which a non-transmitting AP belongs in a multi-BSSID set where the second AP is located; and the 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.

[0051] Optionally, the 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 wide bandwidth channel change element, and a wide bandwidth channel change envelope element.

[0052] Optionally, the above-mentioned specific key BSS parameters are carried in a multi-link ML element.

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

[0054] Specifically, the processor is used to generate a first frame, which is used to indicate 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-transmission AP belongs in the multiple basic service set identifier BSSID set where the first AP is located, wherein a 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 transceiver is used to send the first frame on the link where the communication device works.

[0055] In a tenth aspect, the present application provides a communication device, specifically a first STA, comprising a processor and a transceiver. The processor is configured to support the first STA in performing the corresponding functions of the method of the second aspect. The transceiver is configured to support communication between the first STA and a first AP MLD, and to receive information, frames, data packets, or instructions involved in the method from the first AP MLD. The second STA may also include a memory coupled to the processor to store program instructions and data necessary for the second STA.

[0056] Specifically, the transceiver is used to receive a first frame on the link where the communication device works, and 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, and the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located, wherein a 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 multiple BSSs managed by multiple APs in the AP MLD associated with the first STA have a key BSS parameter update.

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

[0058] 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, and the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the second AP is located; the transceiver is used to send the second frame on the link where the communication device works.

[0059] In a twelfth aspect, the present application provides a communication device, specifically a second STA, comprising a processor and a transceiver. The processor is configured to support the second STA in performing the corresponding functions of the method of the sixth aspect. The transceiver is configured to support communication between the second STA and a first AP MLD, and to receive information, frames, data packets, or instructions involved in the method from the first AP MLD. The second STA may also include a memory coupled to the processor to store necessary program instructions and data for the second STA.

[0060] Specifically, the transceiver is used to receive a second frame on the link on which it works, where 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, where the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where 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.

[0061] In a thirteenth aspect, the present application provides a chip or chip system, comprising an input / output interface and a processing circuit. The processing circuit is configured to generate a first frame, the first frame being configured to indicate 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 being an AP MLD to which non-transmitting APs belong in a multi-basic service set identifier (BSSID) set to which the first AP belongs, wherein key BSS parameter update information corresponding to an AP is used to determine whether a BSS managed by the AP has a key BSS parameter update; and the input / output interface is configured to send the first frame on a link on which the chip or chip system operates.

[0062] 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, where 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, where the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located, where 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; and the processing circuit is used to determine, based on the first frame, whether multiple BSSs managed by multiple APs in the AP MLD associated with the first STA have a key BSS parameter update.

[0063] In a fourteenth aspect, the present application provides a chip or chip system, comprising an input / output interface and a processing circuit. The processing circuit is configured to generate a second frame, the second frame being configured to indicate specific key BSS parameters of multiple APs in the first AP MLD and / or specific key BSS parameters of multiple APs in a second AP MLD, the second AP MLD being an AP MLD to which non-transmitting APs belong in a multi-BSSID set to which the second AP belongs; and the input / output interface being configured to transmit the second frame on a link on which the chip or chip system operates.

[0064] 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, where 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 a second AP MLD, where the second AP MLD is the AP MLD to which the non-transmitting AP belongs in the multi-BSSID set where the second AP is located; and the processing circuit 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.

[0065] In a fifteenth aspect, the present application provides a computer-readable storage medium having instructions stored therein. When the instructions are executed on a computer, the computer executes the key BSS parameter management method applicable to multiple links described in the first aspect or the second aspect.

[0066] In the sixteenth aspect, the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a computer, the computer executes the method for updating key BSS parameters described in the fifth aspect or the sixth aspect.

[0067] In a seventeenth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the key BSS parameter management method applicable to multiple links as described in the first aspect or the second aspect.

[0068] In an eighteenth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method for updating key BSS parameters described in the fifth aspect or the sixth aspect.

[0069] Implementing the embodiments of the present application can help some APs or all APs in some AP MLDs to notify the STAs they manage whether the key BSS parameters of the AP (the BSS it manages) have been updated, so as to assist the STAs in receiving the latest key BSS parameters, so that after the key BSS parameters of the AP are updated, the STAs can also communicate normally with it. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

[0077] FIG5 is a schematic diagram of a frame structure of a TIM frame provided in an embodiment of the present application;

[0078] FIG6 is a schematic diagram of a frame structure of a management frame provided in an embodiment of the present application;

[0079] 7 is a schematic flow chart of a key BSS parameter management method applicable to multiple links provided in an embodiment of the present application;

[0080] FIG8a is a schematic diagram of the frame structure of the RNR element provided in an embodiment of the present application;

[0081] FIG8b is a schematic diagram of the frame structure of a TBTT information field in the RNR element provided in an embodiment of the present application;

[0082] FIG9 is a schematic flow chart of a method for updating key BSS parameters provided in an embodiment of the present application;

[0083] FIG10a is a schematic diagram of a frame structure of an ML element provided in an embodiment of the present application;

[0084] FIG10 b is a schematic diagram of the first half of the frame structure of the ML element provided in an embodiment of the present application;

[0085] FIG11a is a schematic diagram of a frame structure including a channel change notification element provided in an embodiment of the present application;

[0086] FIG11b is a schematic diagram of a frame structure including an extended channel change notification element provided in an embodiment of the present application;

[0087] FIG11c is a schematic diagram of a frame structure including a wide bandwidth channel change element provided in an embodiment of the present application;

[0088] FIG11d is a schematic diagram of a frame structure of a quiet element provided in an embodiment of the present application;

[0089] FIG12 is a schematic diagram of a frame structure of a non-inherited element provided in an embodiment of the present application;

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

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

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

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

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

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

[0096] In order to better understand the key BSS parameter management method and related devices applicable to multiple links disclosed in the embodiments of the present application, the relevant concepts of the embodiments of the present application are first described.

[0097] 1. Multi-link devices

[0098] The wireless communication system to which the embodiments of the present application are applicable may be a wireless local area network (WLAN) or a cellular network. The unicast service indication method may be implemented by a communication device in the wireless communication system or a chip or processor in the communication device. The communication device may be a wireless communication device that supports parallel transmission of multiple links, such as 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.

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

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

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

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

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

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

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

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

[0107] 2. Link identification

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

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

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

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

[0112] 3. Multiple BSSID set

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

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

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

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

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

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

[0119] 4. Key BSS parameters

[0120] Exemplarily, the key BSS parameters may include one or more of the following: including a channel switch announcement element, including an extended channel switch announcement element, changing enhanced distributed channel access,EDCA parameters element, Inclusion of a Quiet element, Modification of the DSSS Parameter Set, Modification of the CF Parameter Set element, Modification of the HT Operation element, Inclusion of a Wide Bandwidth Channel Switch element, Inclusion of a Channel Switch Wrapper element, Inclusion of an Operating Mode Notification element, Inclusion of a Quiet Channel element, Modification of the VHT (very high throughput) Operation element, Modification of the HE (high efficiency) Operation element, Insertion of a Broadcast TWT element, Inclusion of the BSS Color Change Announcement element, Modification of the MU EDCA parameter set element MU EDCA Parameter Set element), Modification of the Spatial Reuse Parameter Set element. One or more of the above key BSS parameters can also be listed as key parameters of the link.

[0121] 5. Specific key BSS parameters

[0122] The specific key BSS parameters may refer to parameters related to channel changes among the key BSS parameters. Specifically, the specific key BSS parameters 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.

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

[0124] Refer to Figure 3a, which is a schematic diagram of the structure of a communication system 100 provided in an embodiment of the present application. Figure 3a uses a wireless local area network as an example to introduce a communication system 100 applied in an embodiment of the present application. The communication system 100 includes: a station 101 and a station 102. Station 101 can communicate with station 102 using multiple links, thereby achieving the effect of improving throughput. Station 101 can be a multi-link device, and station 102 can be a single-link device or a multi-link device. In one scenario, station 101 is an AP MLD, and station 102 is a non-AP MLD or a station (such as a single-link station). In another scenario, station 101 is a non-AP MLD, and station 102 is an AP (such as 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 (such as a single-link station). Of course, the wireless local area network may also include other devices. The number and types of devices shown in FIG3a are only exemplary.

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

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

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

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

[0129] Referring to Figure 4, Figure 4 is a schematic diagram of the architecture of multiple Multiple BSSID sets provided by an embodiment of the present application. In other words, the AP MLDs shown in Figure 4 are collocated AP MLD sets.

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

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

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

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

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

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

[0136] Optionally, the reporting AP can be a common AP in the AP MLD (taking FIG. 4 as an example, such as AP3 with MAC address identifier BSSID_3 and AP5 with MAC address identifier BSSID_5) or a transmission AP in a multi-BSSID set, capable of sending the unicast service indication information described in this application.

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

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

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

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

[0141] In the 802.11 protocol, STAs typically have two operating modes: non-energy-saving mode and energy-saving mode. When a STA is operating in non-energy-saving mode, it is in an active state (also called an awake state) regardless of whether it is transmitting data. When a STA is operating in energy-saving mode, it can be in an active state when transmitting data with the AP; when there is no data transmission between the STA and the AP, the STA can be in a doze state to save power. Whether a STA is in energy-saving mode can be determined by sending a frame to the AP with the energy-saving bit in the frame control field of the MAC header of the frame set to 1 to inform the AP that the STA is in energy-saving mode, or setting the energy-saving bit in the frame control field of the MAC header of the frame to 0 to inform the AP that the STA is in non-energy-saving mode.

[0142] It is understandable that the "data transmission" and "transmission data" mentioned in this application generally refer to communication, where "data" generally refers to communication information, and is not limited to data information, but can also be signaling information, etc.

[0143] In an energy-saving mechanism based on wireless network management (WNM) or a target wake up time (TWT), a STA can communicate a wake-up period with an AP. At the beginning of each wake-up period, the AP sends a broadcast traffic indication map (TIM) frame to the corresponding multiple STAs. The TIM frame is much shorter than the beacon frame. The TIM element included in the TIM frame is used to inform multiple STAs whether there are corresponding downlink service indications. Since the TIM frame is much shorter than the beacon frame, the STA can achieve energy-saving effects. In the WNM energy-saving mechanism, the TIM Broadcast Interval field in the TIM request frame sent by the STA or the TIM response replied by the AP is used to indicate the wake-up period. Alternatively, in the TWT energy-saving mechanism, the wake-up period corresponds to the TWT wake-up interval in the TWT mechanism, wherein the TWT wake-up interval is calculated by the TWT wake-up duration decimal field and the TWT wake-up interval index field in the TWT element. Specifically, the TWT wake-up interval = TWT wake-up duration decimal * 2 (TWT wake-up interval index).

[0144] Optionally, refer to Figure 5, which is a schematic diagram of the frame structure of a TIM frame provided in an embodiment of the present application. As shown in Figure 5, the frame carrier in the TIM frame may include at least one of the following: a type field, an unprotected WNM behavior field, a timestamp field, a beacon frame Beacon check field, a TIM element field, and a link identification information field. Among them, the unprotected WNM behavior field is used to indicate different behavior values. The timestamp field is used to indicate clock information. The TIM element field is used to indicate whether the STA or Non-AP MLD identified by the AID has downlink business. The link identification information field is used to indicate a specific link. The beacon frame Beacon check field is used to indicate the BSS where the link indicated by the link identification information field is located or to indicate whether the AP indicated by the link identification information field has a key BSS parameter update, or the beacon frame Beacon check field is used to indicate whether the link indicated by the link identification information field has a key parameter update.

[0145] For example, if the BSS where the link indicated by the Link Identification Information field is located has a key BSS parameter update, or if the link indicated by the Link Identification Information field has a key parameter update, the value of the Beacon Check field is increased by 1. The above-mentioned BSS parameters can also be understood as link parameters. Accordingly, key BSS parameters can be understood as key link parameters.

[0146] Exemplarily, the Non-AP MLD remembers the value of the Beacon Check field for each link it last received. If the value of the Beacon Check field for a link it recently received differs from the value of the Beacon Check field for the link it last received, the Non-AP MLD will receive a beacon frame from the AP MLD on that link. Alternatively, the Non-AP MLD can send a probe request frame on any link, requesting the latest key BSS parameters for one or more APs. The probe request frame includes the link identifiers of one or more APs and, optionally, the MLD identifier of the MLD where the AP resides, such as the AP MLD's MLD MAC address or MLD sequence number. After receiving the probe request frame, the AP MLD responds with an acknowledgment frame and then sends a probe response frame to the Non-AP MLD. The probe response frame includes the latest key BSS parameters for the one or more APs requested by the Non-AP MLD. The Non-AP MLD responds with an acknowledgment frame. The value of the Beacon Check field for the AP or APs in the probe response frame has changed. It can be understood that the beacon frame carries the latest key BSS parameters of the link.

[0147] It is understandable that since the TIM frame includes a link identification information field, when using the TIM frame, within a BSS, even if the Non-AP MLD includes multiple STAs, only one AID is required. Combined with the link identification information and the AID, it can be determined which station working on the link indicated by the link identification information field has downlink business.

[0148] It is also understandable that the Beacon check field and link identification information field included in the TIM frame can also be placed in other management frames, and the multiple fields (here referring to the Beacon check field and the link identification information field) can be used alone to notify the BSS where the link indicated by the link identification information field is located whether there is a key BSS parameter change / update. The above method can also be used to determine whether there is a key BSS parameter change / update for multiple BSSs where multiple links are located. For example, the management frame includes the number of links, n Beacon check fields, and n link identification information fields, where n is indicated by the link number field. For another example, the management frame includes a link identification bit map, and n Beacon check fields, and optionally includes a length field of the link identification bit map, where n is the number of link identification bit maps set to the first value (such as 1). The value of one or more Beacon check fields is initialized to 0. In one implementation, see Figure 6, which is a schematic diagram of the frame structure of a management frame provided in an embodiment of the present application. As shown in Figure 6, the frame carrier of the 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 link number field indicates multiple links, each link includes a Beacon check field, a TIM element field, and a link identification information field. Optionally, the frame carrier of the management frame may also include one or more timestamp fields. The management frame shown in Figure 6 can be used to indicate whether multiple stations operating on the link indicated by each link identification information field have downlink traffic.

[0149] In summary, as shown in FIG4 , some APs (such as non-transmitting APs in the same multi-BSSID set) cannot send management frames; therefore, these APs cannot send management frames, such as beacon frames or probe response frames, to notify the STAs / Non-AP MLDs associated with them and whether the BSSs managed by these APs have updated key BSS parameters. As a result, the STAs / Non-AP MLDs associated with these APs and listening on the links where these APs work are unaware that these APs have updated key BSS parameters. As a result, after these APs update key BSS parameters, the STAs / Non-AP MLDs associated with these APs cannot work properly or cannot communicate with these APs.

[0150] Therefore, embodiments of the present application provide a method for managing key BSS parameters applicable to multiple links. This method can help one AP MLD help another AP MLD notify multiple APs of the other AP MLD of updates to key BSS parameters, thereby resolving the issue of certain APs being unable to notify key BSS parameter updates. This method can assist STAs in receiving the latest key BSS parameters, enabling non-AP MLDs associated with the other AP MLD to continue functioning normally after multiple APs of the other AP MLD update their key BSS parameters. The technical solution provided by this application will be described in detail below with reference to more figures.

[0151] Example 1

[0152] The first embodiment of the present application introduces a method for managing key BSS parameters applicable to multiple links, specifically relating to a method for indicating key BSS parameter updates applicable to multiple links. The method not only indicates the key BSS parameter update counts for multiple APs of a first AP MLD (this value is located in a reduced neighbor report (RNR) element), but also indicates the key BSS parameter update counts for multiple APs of a second AP MLD. This allows a non-AP MLD associated with the second AP MLD to listen on the link where the second AP MLD's non-transmitting AP resides and function normally. In other words, the non-AP MLD has more listening channel options.

[0153] Each reporting AP in the first AP MLD needs to send the key BSS parameter update counts corresponding to multiple APs in the first AP MLD to the non-AP MLD associated with the first AP MLD or to surrounding stations (surrounding stations include stations managed by the reporting AP and unassociated stations). It also needs to send the key BSS parameter update counts corresponding to multiple APs in the second AP MLD. For ease of description, the first embodiment of the present application uses a reporting AP in the first AP MLD as an example.

[0154] Refer to Figure 7, which is a schematic flow chart of a key BSS parameter management method applicable to multiple links provided in an embodiment of the present application. Among them, 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-transmitting AP in the multi-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 takes the first STA in the Non-AP MLD as an example. The first AP and the first STA work on the same link. As shown in Figure 7, the association method applicable to multi-link devices includes but is not limited to the following steps:

[0155] S101: A first AP of a first AP MLD generates a first frame. The first frame is used to indicate key BSS parameter update information corresponding to multiple APs in the first AP MLD and key BSS parameter update information corresponding to multiple APs in a second AP MLD. The second AP MLD is an AP MLD to which non-transmitting APs in a multi-BSSID set to which the first AP belongs. Key BSS parameter update information corresponding to an AP is used to determine whether a BSS managed by the AP has key BSS parameter updates.

[0156] The first AP may be any reporting AP in the first AP MLD, and the reporting AP may be an AP that sends a management frame (such as a beacon frame or a probe response frame). The key BSS parameter update information includes a key BSS parameter update count value.

[0157] The first frame may be a management frame, such as a beacon frame, a probe response frame, or other management frame. The first frame may be used to indicate the key BSS parameter update count values ​​corresponding to multiple APs of the first AP MLD (the multiple APs herein refer to all APs of the first AP MLD, or all APs other than the first AP in the first AP MLD, or some APs) and the key BSS parameter update count values ​​corresponding to multiple APs of the second AP MLD (the multiple APs herein refer to all APs in the second AP MLD, or some APs). The second AP MLD is the AP MLD to which non-transmitting APs belong in the multi-BSSID set to which the first AP belongs. Optionally, when one or more of the key BSS parameters change, the key BSS parameter update count value increases by 1.

[0158] A key BSS parameter update count value corresponding to an AP can be used to determine whether the BSS managed by the AP has a key BSS parameter update. The key BSS parameter update count value can be a natural number, and the key BSS parameter update count value is initialized to 0. When the key BSS parameter of the BSS managed by an AP changes, the key BSS parameter update count value corresponding to the AP increases by 1. Since there are multiple key BSS parameter update count values ​​for APs, each key BSS parameter update count value corresponds to an AP identifier, and the AP 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. The key 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 introduced below.

[0159] Optionally, in addition to the key BSS parameter update count value field, the RNR element of the embodiment of the present application may also include a link identification field and an AP MLD identification field (such as an MLD ID field). The link identification field is used to indicate an AP or station working on a specific link. It is understandable that the link identification field can be called a link identification information field, or a link identification bitmap field (a bitmap used to indicate link identifiers corresponding to multiple APs), which is not limited in the embodiment of the present application. The key BSS parameter update count value field is used to indicate the key BSS parameter update count value. It is understandable that the key BSS parameter update count value field can be called a key BSS parameter update field, which is not limited in the embodiment of the present application. The AP MLD identification field can be used to identify a specific AP MLD. It is understandable that the AP MLD identification field can be an MLD ID field, an MLD index field, an MLD sequence number field, etc., and its name is not limited.

[0160] Because the RNR element includes the link identifier field and the identification field of the AP MLD (such as the MLD ID field), when the RNR element is used, 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 operating on the link indicated by the link identifier field has a key BSS parameter update.

[0161] As you can see, in order for a station to associate with an AP, it must first detect the presence of the AP through scanning. Scanning generally takes two forms: active scanning and passive scanning.

[0162] Passive scanning involves a station 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 station switches between different channels to search for beacon frames sent by the AP. Once a station obtains the AP's regulatory information through beacon frames, it can further exchange probe request and probe response frames to obtain additional information from the AP.

[0163] Active scanning means that a station can actively send a broadcast probe request frame without hearing a Beacon frame. The AP that receives the probe request frame can initiate random channel access to reply with a probe response frame if certain conditions are met.

[0164] During the scanning process, to assist stations in performing quick scanning, the AP carries simplified neighbor report elements in management frames, such as beacon frames and probe response frames, to prevent stations from continuously scanning channels and reduce the scanning time.

[0165] APs carry simplified neighbor report elements in management frames, such as beacon frames and probe response frames. During site scanning, stations receive management frames sent by APs, obtain information about surrounding APs based on the simplified neighbor report elements in the frames, and then select an appropriate AP for association.

[0166] Specifically, the simplified neighbor report element generally carries one or more neighbor AP information (Neighbor AP information) fields, which are used to describe information about one or more neighbor APs and the BSS to which they belong. See Figure 8a, which is a schematic diagram of the frame structure of the RNR element provided in an embodiment of the present application. As shown in Figure 8a, the simplified neighbor report element may include some or all of the following fields: the target beacon transmission time (TBTT) information header field (TBTT information Header field), the operating class field, the channel number field, and one or more TBTT information set fields. The TBTT information set field includes one or more TBTT information fields, and one TBTT information field corresponds to one neighbor AP.

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

[0168] The TBTT information Field Type field indicates the type of TBTT information and, together with the TBTT information length field, indicates the format of the TBTT information field.

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

[0170] 1-bit reserved (Reserved field).

[0171] TBTT information count field: indicates the number of TBTT information fields contained in the TBTT information set.

[0172] TBTT information length field: indicates the length of each TBTT information field. The specific information format carried under different lengths is shown in Table 1 below:

[0173] Table 1

[0174]

[0175] The specific format of the TBTT information field when the TBTT information length is 12 bytes is given below.

[0176] Neighbor AP TBTT offset field: indicates the offset between the Beacon transmission time of the neighbor AP and the reporting AP.

[0177] BSSID (BSS Identifier) ​​field: indicates the BSS identifier corresponding to the neighbor AP.

[0178] Short SSID (Short Service Set Identifier) ​​field: indicates the service set identifier to which the neighboring AP belongs.

[0179] BSS Parameter field: indicates the relevant parameters of the neighboring AP.

[0180] Optionally, a TBTT information field in the RNR element of an embodiment of the present application includes, in addition to the TBTT offset field, BSSID field, Short SSID field, and BSS parameter field of the neighbor AP, at least one of a key BSS parameter update count value field, a link identifier (link ID) field, and a multi-link device identifier (MLD ID) field.

[0181] Refer to Figure 8b, which is a schematic diagram of the frame structure of a TBTT information field in the RNR element provided in an embodiment of the present application. As shown in Figure 8b, a TBTT information field of the RNR element includes at least one of the following fields: a TBTT offset field of a neighboring AP, a BSSID field, a Short SSID field, a BSS parameter field, a key BSS parameter update count field, a link identifier (link ID) field, and a multi-link device identifier (MLD ID) field. It is understandable that Figure 8b is only an example, and the order of the key BSS parameter update count field, the link ID field, and the MLD ID field included in the TBTT information field, as well as whether there are other fields between them, are not limited.

[0182] It is understandable that the three fields, namely the key BSS parameter update count field, the link identifier field, and the MLD identifier field, are independent and can be carried in the RNR element at the same time or at different times. In other words, the RNR element can carry some of these three fields.

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

[0184] The BSS Parameter field is used to indicate the parameters related to the neighbor AP. Specifically, the parameters related to the neighbor AP include the following information:

[0185] OCT recommended (recommended channel tunnel mechanism) field: indicates that the neighboring AP expects to exchange management type MPDUs with it through the OCT mechanism.

[0186] Same SSID (Same Service Set Identifier) ​​field: indicates whether the neighbor AP and the reporting AP have the same SSID.

[0187] Multiple BSSID (Multiple Basic Service Set Identifier) ​​field: Indicates whether the neighbor AP is part of a multiple BSSID set.

[0188] Transmitted BSSID (Transmitted Basic Service Set Identifier) ​​field: If the neighbor AP is part of a multiple BSSID set, it further indicates whether the neighbor AP is a Transmitted BSSID or a non-transmitted BSSID.

[0189] Member Of ESS With 2.4 / 5GHz Co-Located AP (Co-located with a 2.4 / 5GHz AP and a member of an extended service set) field: Indicates whether the neighbor AP is co-located with a 2.4 / 5GHz AP (that is, whether it is a 6GHz only AP) and is a member of an extended service set.

[0190] Unsolicited Probe Response Active field: indicates whether the neighbor AP has enabled unsolicited probe response.

[0191] Co-located AP field: indicates whether the neighbor AP is co-located with the reporting AP.

[0192] It should be noted that, in the embodiments of the present application, the AP described in a Neighbor Report element or a Reduced Neighbor Report element is a reported AP (reported access point (AP): An AP that is described in an element such as a Neighbor Report element or a Reduced Neighbor Report element.), and the neighbor AP mentioned subsequently may be understood as a reported AP. The AP that transmits a Neighbor Report element or a Reduced Neighbor Report element is a reporting AP (reporting access point (AP): An AP that is transmitting an element, such as a Neighbor Report element or a Reduced Neighbor Report element, describing a reported AP).

[0193] The above content introduces the RNR element. The second AP MLD is described below.

[0194] Optionally, the second AP MLD is an AP MLD to which a non-transmission AP belongs in the multi-BSSID set where the first AP is located.

[0195] For example, using Figure 4 as an example, assuming that AP1x is the first AP, the first AP sends a management frame, such as a beacon frame or a probe response frame, carrying an RNR element. The RNR element carries the key BSS parameter update counts for multiple APs in a first AP MLD and the key BSS parameter update counts for multiple APs in a second AP MLD. AP MLD1 is the first AP MLD, and 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, and 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 also includes a key BSS parameter update count value corresponding to AP1x. The key BSS parameter update count value of AP1x is located in the MLD public information of the multi-link (ML) element or 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., AP1x.

[0196] For another example, still using Figure 4 as an example, assuming that AP2x is the first AP, AP MLD2 is the first AP MLD, and AP MLD1 and AP MLD3 are both second AP MLDs. Therefore, the first frame includes key BSS parameter update counts corresponding to multiple APs of AP MLD2, such as the key BSS parameter update count corresponding to AP4x; key BSS parameter update counts corresponding to multiple APs of AP MLD1, such as the key BSS parameter update count corresponding to AP1x, AP2y, and AP3; and key BSS parameter update counts corresponding to multiple APs of AP MLD3, such as the key BSS parameter update count corresponding to AP1y, AP2z, and AP4y. Optionally, the management frame sent by the first AP also includes a key BSS parameter update count value corresponding to AP2x, and the key BSS parameter update count value of AP2x is located in the MLD public information of the ML element or 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., AP2x.

[0197] For another example, using Figure 4 as an example, assuming that AP4x is the first AP, AP MLD2 is the first AP MLD, and AP MLD3 and AP MLD4 are both second AP MLDs. Therefore, the 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 AP2x; 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 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 also includes a key BSS parameter update count value corresponding to AP4x, and the key BSS parameter update count value of AP4x is located in the MLD public information of the ML element or 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.

[0198] For another example, using Figure 4 as an example, assuming AP3 is the first AP, AP MLD1 is the first AP MLD, and no second AP MLD exists. Therefore, the first frame 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 and AP2y. Optionally, the management frame sent by the first AP also includes the key BSS parameter update count corresponding to AP3. The BSS parameter update count of AP3 is located in the MLD Common Information field of the ML element or the EHT Operation element. The MLD Common Information field of the ML element or the EHT Operation element also carries the link identifier of the first AP3.

[0199] S102: The first AP of the first AP MLD sends the first frame on its working link.

[0200] Specifically, the first AP of the first AP MLD needs to send the above-mentioned first frame on the link on which it is operating to the non-AP MLD associated with the first AP MLD, or to the stations surrounding the first AP. The stations surrounding the first AP include stations managed by the first AP and unassociated stations. The following uses the stations managed by the AP as an example to illustrate the key BSS parameter management method applicable to multiple links described in the embodiment of the present application. It is understood that the first frame can be sent in a broadcast or multicast manner.

[0201] It is also understandable that the Non-AP MLD associated with the first AP MLD involved in the embodiments of the present application has two meanings: (1) all Non-AP MLDs that establish multi-link associations with the first AP MLD, wherein the Non-AP MLD can be associated with some APs in the first AP MLD or with all APs; (2) Non-AP MLD associated with the first AP of the first AP MLD, wherein the Non-AP MLD can be associated with some APs in the first AP MLD or with all APs, but the part of APs or all APs must include the first AP. The first AP is the reporting AP.

[0202] S103: The first STA of the Non-AP MLD receives the first frame on its working link.

[0203] The first STA may be a station managed by the first AP or a surrounding station, and it is possible to learn whether the BSS to which the first STA belongs has key BSS parameter updates. The first STA and the first AP operate on the same link / frequency band / channel.

[0204] S104: The first STA of the Non-AP MLD determines, based on the first frame, whether key BSS parameters of multiple BSSs managed by multiple APs in the AP MLD associated with the Non-AP MLD are updated.

[0205] Specifically, after receiving the first frame, the first STA of the Non-AP MLD can parse the first frame to obtain the key BSS parameter update counts corresponding to multiple APs in the first AP MLD and the key BSS parameter update counts corresponding to multiple APs in the second AP MLD. The Non-AP MLD parses the first frame to obtain M key BSS parameter update counts corresponding to M APs in the AP MLD associated with the Non-AP MLD (these M APs are associated with the Non-AP MLD). For each of the 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 the currently received key BSS parameter update count with the previously received key BSS parameter update count to see if they are the same. If the currently received key BSS parameter update count is different from the previously received key BSS parameter update count, the Non-AP MLD determines that a key BSS parameter update has occurred in the BSS managed by this AP. Optionally, if the key BSS parameter update count received this time is different from the key BSS parameter update count received last time, the Non-AP MLD can listen for beacon frames on the link where the AP operates. These beacon frames carry the latest key BSS parameters for the AP. Alternatively, a STA in the Non-AP MLD can obtain the latest key BSS parameters for the AP by sending a probe request frame as described above.

[0206] If the key BSS parameter update count value received this time is the same as the key BSS parameter update count value received last time, it means that the BSS managed by this AP has not had any key BSS parameter update, and Non-AP MLD does not process it.

[0207] Optionally, Non-AP MLD records the key BSS parameter update count value corresponding to each link received last time.

[0208] For example, using Figure 4 as an example, assume that the first AP is AP1x, AP MLD1 is the first AP MLD, and AP MLD3 is the second AP MLD. Assume that Non-AP MLD1 is associated with AP1y, AP2z, and AP4y of AP MLD3, and M is 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 is 6. Non-AP MLD1 parses the first frame to extract the three key BSS parameter update counts corresponding to AP1y, AP2z, and AP4y of AP MLD3, which is associated with Non-AP MLD1. For AP1y, Non-AP MLD2 compares the key BSS parameter update count received for AP1y with the key BSS parameter update count received last time for AP1y to see if they are the same. If they are not the same, the BSS managed by AP1y has had its key BSS parameters updated. Non-AP MLD1 can listen for beacon frames carrying the latest key BSS parameters on link 1 where AP1y is located. For AP2z, Non-AP MLD1 compares the key BSS parameter update count received for AP2z with the key BSS parameter update count received last time for AP2z to see if they are the same. If they are not the same, the BSS managed by AP2z has had its key BSS parameters updated. Non-AP MLD1 can listen for beacon frames carrying the latest key BSS parameters on link 2 where AP2z is located. For AP4y, Non-AP MLD1 compares the key BSS parameter update count received for AP4y with the key BSS parameter update count received last time for AP4y to see if they are the same. If they are not the same, it indicates that the BSS managed by AP4y has updated key BSS parameters. Non-AP MLD1 can listen for beacon frames carrying the latest key BSS parameters on link 4 where AP4y is located.

[0209] For another example, suppose Non-AP MLD2 is associated with AP MLD3's AP1y and AP4y. 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 key BSS parameter update count received for AP1y with the key BSS parameter update count received for AP1y last time. If they are not identical, it indicates 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 key BSS parameter update count received for AP4y with the key BSS parameter update count received for AP4y last time. If they are not identical, it indicates 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.

[0210] It is understandable that when the first STA is a single-link STA, when the first STA switches from one link to another link, the first STA can adopt the method of the embodiment of the present application to obtain the key BSS parameter update count value.

[0211] As can be seen, in this embodiment of the present application, by transmitting the first frame from the first AP, which indicates not only the key BSS parameter update counts corresponding to multiple APs in the first AP MLD but also the key BSS parameter update counts corresponding to multiple APs in the second AP MLD, an AP can help provide the key BSS parameter update counts corresponding to multiple APs in another AP MLD. This allows a STA to determine whether a key BSS parameter update has occurred by comparing the currently received key BSS parameter update count with the previously received key BSS parameter update count. This assists STAs in receiving the latest key BSS parameters and enables non-AP MLDs associated with the second AP MLD to listen on links containing non-transmitting APs in the second AP MLD and function normally. In other words, non-AP MLDs have more listening channel options. In 802.11be, some or all APs in an AP MLD may be non-transmitting APs. Therefore, the solution provided by this embodiment of the present application solves the problem of some non-transmitting APs being unable to send management frames to notify key BSS parameter updates, thereby increasing the completeness and diversity of key BSS parameter update indications.

[0212] As an optional embodiment, the method for each Non-AP MLD to obtain the initial values ​​of the key BSS parameter update counts of multiple APs of the AP MLD associated with it is as follows:

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

[0214] 2. When a STA in the Non-AP MLD requests to switch to another link, the channel switch signaling implicitly requests the AP MLD for the key BSS parameter update count of the AP operating on the other link. The AP MLD sends a response frame on the link corresponding to the STA, which must carry the latest key BSS parameter update count of the AP operating on the other link.

[0215] The channel switch signaling includes the link identifier of the AP to which the STA is switching. For example, in Figure 4, assuming that STA1 in Non-AP MLD1 requests to switch from link 1 to link 2, the channel switch signaling includes the link identifier of link 2. Assuming that Non-AP MLD1 is associated with AP MLD, the channel switch signaling implicitly requests the key BSS parameter update count of AP2y operating on link 2 from AP MLD1. The response frame sent by AP MLD1 on link 1 corresponding to STA1 must carry the latest key BSS parameter update count of AP2y currently operating on link 2.

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

[0217] As another optional embodiment, an AP MLD has a common SSID, and optionally, each AP has a separate SSID. During the neighbor AP or AP MLD discovery phase, in order for the Non-AP MLD to find the best AP MLD as quickly as possible and perform association, this includes finding the preferred SSID as quickly as possible. 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 the embodiment of the present application carries: a Short SSID calculated based on the SSID of the AP MLD where the reported AP (neighbor AP) is located. The Short SSID calculation method can refer to the 802.11-2016 protocol.

[0218] It is understandable that the embodiments of the present application can be implemented independently or in combination with the method shown in Figure 7, and the embodiments of the present application are not limited to this.

[0219] It can be seen that compared with directly carrying the shortSSID of the reported AP itself in the RNR element, the Non-AP MLD in the embodiment of the present application can quickly select the best AP MLD for association through the short SSID of the AP MLD where the reported AP is located during the discovery phase, thereby improving association efficiency.

[0220] As another optional embodiment, the first frame 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. The specific key BSS parameters may include one or more of the following: a channel change notification element, an extended channel change notification element, a wide bandwidth channel change element, and a wide bandwidth channel change envelope element.

[0221] Example 2

[0222] The second embodiment of the present application provides a method for updating key BSS parameters, which is applied to a multi-link device and describes how to update key BSS parameters. It is understandable that in actual applications, the second embodiment of the present application can be implemented alone or in combination with the above-mentioned first embodiment, and this application does not limit this.

[0223] Refer to Figure 9, which is a schematic flow chart of a method for updating key BSS parameters provided by an embodiment of the present application. The AP MLD includes one or more APs, the second AP is any AP in the AP MLD, and the second AP can be a reporting AP or not. The second STA can be a single-link STA or any STA in the Non-AP MLD. For ease of description, the following description takes the second STA in the Non-AP MLD as an example. The second AP and the second STA work on the same link. As shown in Figure 9, the method for updating key BSS parameters includes but is not limited to the following steps:

[0224] S201: A second AP of a first AP MLD generates a second frame, where 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 a second AP MLD. The second AP MLD is an AP MLD to which a non-transmitting AP belongs in a multi-BSSID set where the second AP is located.

[0225] The second frame may be a management frame, such as a beacon frame, or other frame. The second frame may be the same frame as the first frame of the first embodiment, or a different frame, and this is not limited in this embodiment of the present application. The second frame may be used to indicate specific key BSS parameters of multiple APs of the first AP MLD (the multiple APs here are all APs of the first AP MLD, or all APs in the first AP MLD except the first AP, or some APs) and / or specific key BSS parameters of multiple APs of the second AP MLD (the multiple APs here are all APs in the second AP MLD, or some APs).

[0226] The above-mentioned specific 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 all or some of the above four elements are changed or updated and the station is not notified in a timely manner (possibly because the station has not received the updated elements), the station will be unable to find the corresponding AP in the AP MLD and thus unable to communicate with the corresponding AP in the AP MLD. Therefore, it is necessary to carry specific key BSS parameters.

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

[0228] Optionally, the above-mentioned specific key BSS parameters may be carried in the AP information of the multi-link (ML) element of the second frame. The specific key BSS parameters of each AP are carried in the respective AP information of the ML element.

[0229] The following is an introduction to the multi-link elements.

[0230] Refer to Figure 10a, which is a frame structure diagram of the ML element provided in an embodiment of the present application. As shown in Figure 10a, 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 includes an authentication algorithm field and a link ID field. The MLD MAC address field is used to indicate the address of the MLD, which is used to identify an MLD. Optionally, the address of the MLD is the MAC address of the MLD, or it can be said that the MAC address is used to identify an AP MLD management entity. The MAC address of the AP MLD can be the same as one of the MAC addresses of the n APs included in the AP MLD, or it can be different from the MAC addresses of the n APs. For example, the MAC address of the AP MLD is a common MAC address that can identify the AP MLD.

[0231] Optionally, the public control field may include an MLD MAC address presence field (also called an MLD MAC address occurrence field or an MLD MAC address occurrence identifier), which is used to indicate whether the MLD MAC address field exists in the MLD public information. Optionally, the public control field also includes an authentication algorithm occurrence field, which is used to indicate whether the authentication algorithm field exists in the MLD public information. Optionally, the above-mentioned "occurrence field" may include 1 bit, with a first value indicating that the corresponding field exists, and a second value indicating that the corresponding field does not exist. For example, the first value is 1 and the second value is 0. Optionally, the public control field also includes a link ID occurrence field, which is used to indicate whether the link ID field exists in the MLD public information.

[0232] Optionally, an ML element also includes one or more sub-elements, each of which describes information about an AP in an AP MLD. Each sub-element includes the link identifier of the AP. Optionally, each sub-element also includes fields related to the AP, such as the SSID field, the timestamp field, the beacon interval field, and elements related to the AP, such as the BSS load element, the EHT capability element, and the EHT operation element.

[0233] Refer to Figure 10b, which is a schematic diagram of the frame structure of the first half of the ML element provided in an embodiment of the present application. As shown in Figure 10b, Figure 10b shows the first half of the ML element, which does not include the AP information sub-element 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 or all of the MLD MAC address presence field, the Link ID presence field, the MLD sequence number presence field, and the sub-element presence fields. Optionally, it includes the authentication algorithm presence field. The MLD MAC address presence field is used to indicate whether the MLD common information includes the MLD MAC address field. The Link ID presence field is used to indicate whether the MLD common information includes the Link ID field. The MLD sequence number presence field is used to indicate whether the MLD common information includes the MLD sequence number field. The above fields can each be indicated by a single bit, for example, 1 indicates presence and 0 indicates absence, or by two values ​​in a single field, with the first value indicating presence and the second value indicating absence.

[0234] Optionally, the first half of the ML element shown in Figure 10a (herein, the common control field and MLD common information shown in Figure 10a) can be replaced with the first half of the ML element shown in Figure 10b (herein, the common control field and MLD common information shown in Figure 10b). This can be used by the AP MLD to provide further detailed information to the non-AP MLD, such as in a probe response frame or an association response frame. Optionally, the common control field includes an MLD common information presence field, which indicates whether the MLD common information, or specifically, whether fields other than the MLD MAC address or MLD sequence number in the MLD common information, are present. This helps further reduce duplicate information (assuming the non-AP MLD has already learned the authentication algorithm and link identifier). In a beacon frame, to avoid excessive content and duplicate information about each AP in the RNR element, the beacon frame only needs to carry the MLD common information in the ML element, or some fields in the MLD common information. In this case, the common control field includes a sub-element presence field to indicate that sub-elements in the ML element that indicate specific information about multiple APs are not present, as shown in Figure 10b.

[0235] If the reporting AP belongs to a multi-BSSID set, it must also send a multi-BSSID element, including a non-transmitted profile, indicating information about one or more non-transmitting APs. If a non-transmitting AP is part of an AP MLD, the first half of the ML element (as shown in Figure 10b) or the full ML element (as shown in Figure 10a) can also be included in the non-transmitting AP's information.

[0236] The following describes several elements of specific key BSS parameters.

[0237] Refer to Figure 11a, which is a schematic diagram of a frame structure including a channel change notification element provided in an embodiment of the present application. As shown in Figure 11a, a channel change notification element is included, including: a channel switch mode field, a new channel number field, and a channel change count field. Among them, the channel switch mode field indicates the transmission restrictions before the channel change (The Channel Switch Mode field indicates any restrictions on transmission until a channel switch). The new channel number field is used to indicate the channel number to which the station is to change (The New Channel Number field is set to the number of the channel to which the STA is moving). 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.

[0238] Refer to Figure 11b, which is a schematic diagram of the frame structure including the extended channel change notification element provided by an embodiment of the present application. As shown in Figure 11b, the extended channel change notification element includes: a channel switch mode (Channel Switch Mode) field, a new operating class (New Operating Class) field, a new channel number (New Channel Number) field, and a channel change count (Channel Switch Count) field. Among them, the channel change mode field indicates the transmission restriction before the channel change. The New Operating Class field is used to indicate the operating set to which the station is to switch (The New Operating Class field is set to the number of the operating class after the channel switch). The New Channel Number field is used to indicate the channel number to which the station is to switch. The Channel Change Count field is used to indicate how many TBTTs it takes for the station to send the element to switch to the channel. Setting it to 0 means that the change occurs before the next TBTT, and setting it to 1 means that it may occur at any time after sending the element.

[0239] Referring to Figure 11c, Figure 11c is a schematic diagram of a frame structure including a wide bandwidth channel change element provided in an embodiment of the present application. As shown in Figure 11c, the wide bandwidth channel change element includes: a New Channel Width field, a New Channel Center Frequency Segment 0 field, and a New Channel Center Frequency Segment 1 field. Among them, the New Channel Width field defines the BSS bandwidth (New Channel Width define BSS bandwidth). New Channel Center Frequency Segment 0 defines a channel center frequency for a 20, 40, 80, 160, or 80+80MHz BSS bandwidth (New Channel Center Frequency Segment 0 Defines a channel center frequency for a 20, 40, 80, 160, or 80+80MHz BSS). New Channel Center Frequency Segment 1 Defines a channel center frequency for a 160 or 80+80MHz BSS bandwidth.

[0240] See Figure 11d, which is a schematic diagram of the frame structure of the Quiet element provided in an embodiment of the present application. As shown in Figure 11d, the Quiet element includes: a Quiet Count field, a Quiet Period field, a Quiet Duration field, and a Quiet Offset field. The Quiet Count field is set to the number of TBTTs until the beacon frame interval during which the next quiet interval starts. The Quiet Period field is set to the number of beacon frame intervals between the start of the periodic quiet intervals defined by this Quiet element. The Quiet Period field is set to 0, indicating that no periodic quiet interval is defined. The Quiet Duration field is set to the duration of the quiet interval, expressed in TUs. The Quiet Offset field is set to the offset of the start of the quiet interval from the TBTT specified by the Quiet Count field, expressed in TUs. The value of the Quiet Offset field is less than one beacon interval.

[0241] It is understandable that after the silence element takes effect, the AP no longer communicates with the STA, and the STA remains in a silent state so that the STA can perform other operations.

[0242] Optionally, the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the second AP is located. Specifically, the meaning of the second AP MLD may refer to the relevant description in the aforementioned embodiment 1.

[0243] S202: The second AP of the first AP MLD sends the second frame on its working link.

[0244] The second AP of the first AP MLD needs to send the second frame on its operating link to the non-AP MLD associated with the first AP MLD, or to stations surrounding the second AP. Stations surrounding the second AP include stations managed by the second AP and unassociated stations. It is understood that the second frame can be sent via broadcast, multicast, or unicast.

[0245] S203: The second STA of the Non-AP MLD receives the second frame on its working link.

[0246] The second STA may be a station managed by the second AP or a surrounding station, and may obtain specific key BSS parameters of multiple APs in the AP MLD associated with the MLD where the first STA is located. The second STA and the second AP operate on the same link / frequency band / channel.

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

[0248] Specifically, after receiving the second frame, the second STA of the non-AP MLD can parse the second frame and parse the ML element of the second frame to obtain specific key BSS parameters of K APs (these K APs are associated with the non-AP MLD, and K is a positive integer) in the AP MLD associated with the non-AP MLD. For the specific key BSS parameters of each AP in the K APs, the non-AP MLD can adjust the channel information of the STA corresponding to each AP according to the specific key BSS parameters of each AP.

[0249] For example, using Figure 4 as an example, assume that AP2x is the second AP, AP MLD2 is the first AP MLD, and AP MLD1 and AP MLD3 are both second AP MLDs. Assuming that Non-AP MLD1 is associated with AP1x and AP2y of AP MLD1, and K is 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 of them) in AP MLD1, AP MLD2, and AP MLD3. For example, the second frame carries specific key BSS parameters for all APs in AP MLD1, as well as those in AP MLD2 and AP MLD3. Therefore, for AP1x in AP MLD1, assuming that AP1x's specific key BSS parameters indicate that the station should switch to channel number 9, Non-AP MLD1, in accordance with AP1x's specific key BSS parameters, switches the STA corresponding to AP1x to channel number 9 for communication. For AP2y in AP MLD1, assuming that the specific key BSS parameter of AP2y indicates that the operation set to which the station is to be switched is A, then Non-AP MLD1 will switch the STA corresponding to AP2y from the current operation set to the operation set identified by operation set A according to the indication of the specific key BSS parameter of AP2y.

[0250] It is understandable that the second embodiment of the present application is described by taking one AP in the AP MLD as an example. In actual applications, each AP in the AP MLD may execute steps S201 to S202 shown in FIG. 9 .

[0251] It is understandable that the second STA can be a single-link STA, or can be a STA in a Non-AP MLD. When the second STA is a single-link STA, when the second STA switches from one link to another link, the second STA can use the method of the embodiment of the present application to obtain specific key BSS parameters.

[0252] It can be seen that in the implementation of the present application, the second frame sent by an AP of the AP MLD not only explicitly carries the specific key BSS parameters of multiple APs of the AP MLD, but also explicitly carries the specific key BSS parameters of multiple APs of other AP MLDs. The specific key BSS parameters include elements related to channel changes. This can help the Non-AP MLD to promptly learn about the working channel changes of all APs of the AP MLD while monitoring one or more links (not all links), so that it can operate normally.

[0253] As an optional embodiment, when a STA in a Non-AP MLD requests to switch to another link, the channel switching signaling implicitly requests the AP MLD for specific key BSS parameters of the AP operating on the link, or explicitly carries specific signaling to indicate the specific required key BSS parameters, such as using one or more element IDs, optionally carrying one or more element ID extensions, or directly reusing non-inherited elements in the 802.11-2016 protocol to request parameters of corresponding elements in the non-inherited elements. The response frame sent by the associated AP MLD on the link corresponding to the STA must carry the latest special BSS parameters of the AP operating on the other link.

[0254] Optionally, the channel switching signaling further includes an identifier of the AP, such as a link identifier; and an identifier of the MLD where the AP is located, such as an MLD sequence number or a MAC address of the MLD.

[0255] Refer to Figure 12, which is a schematic diagram of the frame structure of a non-inherited element provided in an embodiment of the present application. As shown in Figure 12, the 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 the element ID extension are used to indicate that the element is a non-inherited element. The length is used to indicate the length after the element length field. One or more element IDs, optionally and one or more element ID extensions are used to indicate one or more specific element contents requested. Among them, the element ID extension number only appears together when the value of the element ID is 255, otherwise the element ID can independently indicate an element.

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

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

[0258] When using an integrated unit, see Figure 13, which is a schematic diagram of the structure of a communication device 1 provided in an embodiment of the present application. 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 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. As shown in Figure 13, the communication device 1 includes a processing unit 11 and a transceiver unit 12.

[0259] The processing unit 11 is used to generate a first frame, where 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, where the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located, wherein key BSS parameter update information corresponding to an AP is used to determine whether a BSS managed by the AP has a key BSS parameter update; the transceiver unit 12 is used to send the first frame on the link where the communication device 1 works.

[0260] Optionally, the key BSS parameter update information includes a key BSS parameter update count value.

[0261] It can be seen that in the 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 can enable one AP to help provide multiple APs of another AP MLD with indications of 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 can enable the Non-AP MLD associated with the second AP MLD to listen on the link where the non-transmitting AP in the second AP MLD is located and operate normally.

[0262] Optionally, the above-mentioned processing unit 11 is also used to generate a second frame, which is 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 above-mentioned transceiver unit 12 is also used to send the second frame on the link where the communication device 1 works.

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

[0264] Referring to Figure 14 , Figure 14 is a schematic diagram of the structure of a communication device 2 provided in an embodiment of the present application. The communication device 2 may be a first STA or a chip within the first STA, such as a Wi-Fi chip. The first STA may be a single-link STA or a STA in a Non-AP Multi-Level Ledger (MLD) mode. As shown in Figure 14 , the communication device 2 includes a transceiver unit 21 and a processing unit 22.

[0265] The transceiver unit 21 is used to receive a first frame on the link where the communication device 2 works, where 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, where the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the first AP is located, where 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 used to determine, based on the first frame, whether multiple BSSs managed by multiple APs in the AP MLD associated with the communication device 2 have a key BSS parameter update.

[0266] Optionally, the key BSS parameter update information includes a key BSS parameter update count value.

[0267] It can be seen that in the communication device 2, the processing unit 22 can know whether the BSS to which it belongs has a key BSS parameter update according to the key BSS parameter update count value indicated in the first frame, thereby ensuring that it can receive the latest key BSS parameters.

[0268] Optionally, the above-mentioned transceiver unit 21 is also used to receive a second frame on the link where the communication device 2 works, and the second frame is 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 above-mentioned processing unit 22 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 2.

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

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

[0271] The processing unit 31 is 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, where the second AP MLD is the AP MLD to which the non-transmission AP belongs in the multi-BSSID set where the second AP is located; the transceiver unit 32 is used to send the second frame on the link where the communication device 3 works.

[0272] As can be seen, in the communication device 3, the second frame generated by the processing unit 31 not only explicitly carries the specific key BSS parameters of multiple APs of the AP MLD, but also explicitly carries the specific key BSS parameters of multiple APs of other AP MLDs. The specific key BSS parameters include elements related to channel changes. This helps the non-AP MLD to promptly learn about the working channel changes of all APs of the AP MLD while monitoring one or more links (not all links), so that it can operate normally.

[0273] It should be understood that the communication device 3 described in the embodiment of the present application can correspond to the execution of the aforementioned embodiment 2, and the above operations or functions of each unit in the communication device 3 are respectively for realizing 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 repeated here.

[0274] Referring to Figure 16 , Figure 16 is a schematic diagram of the structure of a communication device 4 provided in an embodiment of the present application. The communication device 4 can be a second STA or a chip within the second STA, such as a Wi-Fi chip. The second STA can be a single-link STA or a STA in a Non-AP Multi-Level Ledger (MLD) mode. As shown in Figure 16 , the communication device 4 includes a transceiver unit 41 and a processing unit 42.

[0275] The transceiver unit 41 is used to receive a second frame on the link where the communication device 4 works, where 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, where the second AP MLD is the AP MLD to which the non-transmitting AP belongs in the multi-BSSID set 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.

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

[0277] It should be understood that the communication device 4 described in the embodiment of the present application can execute the aforementioned embodiment 2, and the above-mentioned operations or functions of each unit in the communication device 4 are respectively for implementing 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 repeated here.

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

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

[0280] Referring to Figure 17, Figure 17 is a structural diagram of a communication device 1000 provided in an embodiment of the present application. The communication device 1000 can be an AP MLD or STA, or a device therein. As shown in Figure 17, the communication device 1000 includes a processor 1001 and a transceiver 1002 connected to and communicating with the processor. The processor 1001 is a general-purpose processor or a dedicated processor, etc. For example, it can be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminals, terminal chips, DUs or CUs, etc.), execute computer programs, and process computer program data. The transceiver 1002 can be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing transceiver functions. The transceiver 1002 may include a receiver and a transmitter. The receiver can be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter can be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function. Optionally, the communication device 1000 may further include an antenna 1003 and / or a radio frequency unit (not shown). The antenna 1003 and / or the radio frequency unit may be located inside the communication device 1000 or may be separated from the communication device 1000, that is, the antenna 1003 and / or the radio frequency unit may be remotely or distributedly deployed.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0296] (6)Others, etc.

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

[0298] The general processor for implementing AP MLD includes a processing circuit and an input and output interface connected to and communicating with the processing circuit.

[0299] In one design, the general-purpose processor can be used to perform the functions of the first AP of the first AP MLD in the first embodiment. Specifically, the processing circuit is used to perform step S101 in Figure 7 and / or other processes used in the techniques described herein; the input / output interface is used to perform step S102 in Figure 7 and / or other processes used in the techniques described herein.

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

[0301] The general processor for implementing the Non-AP MLD includes a processing circuit and an input / output interface connected to and communicating with the processing circuit.

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method for managing critical Basic Service Set (BSS) parameters applicable to multiple links, characterized in that, including: A first access point (AP) of a first access point multi-link device (AP MLD) generates a first frame, which is used to indicate the key basic service set (BSS) parameter update information corresponding to multiple APs of the first AP MLD respectively, and the key BSS parameter update information corresponding to multiple APs of a second AP MLD respectively. 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. Among them, a 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 the AP; The first AP of the first AP MLD sends the first frame on the link where it works.

2. A method for managing critical BSS parameters applicable to multiple links, characterized in that, including: A first station (STA) of a first non-access point multi-link device (Non-AP MLD) receives a first frame on the link where it works. The first frame is used to indicate the key BSS parameter update information corresponding to multiple APs of a first AP MLD respectively, and the key BSS parameter update information corresponding to multiple APs of a second AP MLD respectively. 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. Among them, a 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 the AP; The first STA of the first Non-AP MLD determines whether there is a key BSS parameter update for multiple BSSs managed by multiple APs in the AP MLD associated with the first STA according to the first frame.

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

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

5. The method according to claim 2 or 3, characterized in that, The key BSS parameter update information includes a 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, which is different from the key BSS parameter update count value of the second AP received by the first Non-AP MLD last time, then one STA of the first Non-AP MLD obtains the latest key BSS parameters of the second AP by sending a probe request frame.

6. The method according to claim 3, characterized in that, The method further includes: If the key BSS parameter update count value corresponding to one 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 received by the first Non-AP MLD last time, then the first Non-AP MLD updates the key BSS parameter update count value stored locally corresponding to the AP to the key BSS parameter update count value indicated by the first frame.

7. The method according to claim 1 or 2, characterized in that, The key BSS parameter update information includes a key BSS parameter update count value.

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

9. The method according to any one of claims 1 - 8, characterized in that, The first frame includes a link identification field and a multi-link device (MLD) identification field. The link identification field is used to indicate the reported AP, and the MLD identification field is used to indicate the AP MLD where the reported AP is located.

10. The method according to claim 8 or 9, characterized in that, The key BSS parameter update count value field, the link identification field, and the MLD identification field are carried in the reduced neighbor report (RNR) element of the first frame.

11. The method according to claim 10, characterized in that, One beacon frame target transmission time (TBTT) information field in the RNR element carries a key BSS parameter update count value, a link identification field, and an MLD identification field. One TBTT information field corresponds to one AP.

12. The method according to claim 10 or 11, 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.

13. The method according to any one of claims 1 - 9, characterized in that, The first frame is any one of the following: a beacon frame, a probe response frame, and an association response frame.

14. The method according to claim 1, characterized in that, The association response frame sent by one AP in the first AP MLD carries the key BSS parameter update count values of multiple APs at this time.

15. The method according to claim 1, any one of claims 7 - 14, characterized in that, The method further includes: The first AP of the first AP MLD generates a second frame, which is used to indicate the specific key BSS parameters of multiple APs of the first AP MLD and the specific key BSS parameters of multiple APs of the second AP MLD; The first AP of the first AP MLD sends the second frame on the link where it operates.

16. The method according to any one of claims 2 - 13, characterized in that, The method further includes: The first STA receives a second frame on the link where it operates, and the second frame is used to indicate the specific key BSS parameters of multiple APs of the first AP MLD and the specific key BSS parameters of multiple APs of the second AP MLD; The first STA parses the second frame to obtain the specific key BSS parameters of multiple APs in the AP MLD associated with the Non-AP MLD.

17. The method according to claim 15 or 16, characterized in that, One of the specific key BSS parameters of an AP in the second frame includes one or more of the following: including a channel change notification element, including an extended channel change notification element, including a wide bandwidth channel change element, including a wide bandwidth channel change envelope element.

18. The method according to any one of claims 15 - 17, characterized in that, One of the specific key BSS parameters of an AP in the second frame further includes one or more of the following: including a silent element, including a silent channel element.

19. The method according to any one of claims 15 - 18, characterized in that, The specific key BSS parameter is carried in a multi-link ML element.

20. A communication device, characterized in that, Including: A processing unit for generating a first frame, the first frame being used to indicate 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 being the AP MLD to which a non-transmitting AP in a multi-basic service set identifier BSSID set where the first AP in the first AP MLD belongs belongs. Among them, a 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 the AP. A transceiver unit for sending the first frame on a link where the first AP operates.

21. A communication device, characterized in that, Including: A transceiver unit for receiving a first frame on a link where the communication device operates, the first frame being 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 a second AP MLD, the second AP MLD being the AP MLD to which a non-transmitting AP in a multi-BSSID set where the first AP belongs belongs. Among them, a 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 the AP. A processing unit for determining, according to the first frame, whether there is a key BSS parameter update for multiple BSSs managed by multiple APs in the AP MLD associated with the communication device.

22. The communication device according to claim 21, characterized in that, The key BSS parameter update information includes a key BSS parameter update count value, and the communication device records the key BSS parameter update count value corresponding to each link received last time.

23. The communication device according to claim 21 or 22, characterized in that, The key BSS parameter update information includes a key BSS parameter update count value; The transceiver unit is further configured to, when the communication device receives a key BSS parameter update count value corresponding to a second AP in the AP MLD associated with the communication device and the key BSS parameter update count value of the second AP received by the communication device last time are different, receive a beacon frame of the second AP, and the latest key BSS parameter of the second AP is carried in the beacon frame.

24. The communication device according to claim 21 or 22, characterized in that, The key BSS parameter update information includes a key BSS parameter update count value; The transceiver unit is further configured to, when the communication device receives a key BSS parameter update count value corresponding to a 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 received by the communication device last time, send a probe request frame to obtain the latest key BSS parameters of the second AP.

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

26. The communication device according to claim 20 or 21, characterized in that, The key BSS parameter update information includes a key BSS parameter update count value.

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

28. The communication device according to any one of claims 20 - 27, characterized in that, The first frame includes a link identification field and a multi-link device (MLD) identification field. The link identification field is used to indicate the reported AP, and the MLD identification field is used to indicate the AP MLD where the reported AP is located.

29. The communication device according to claim 27 or 28, characterized in that, The key BSS parameter update count value field, the link identification field, and the MLD identification field are carried in the reduced neighbor report (RNR) element of the first frame.

30. The communication device according to claim 29, wherein One beacon frame target transmission time (TBTT) information field in the RNR element carries a key BSS parameter update count value, a link identification field, and an MLD identification field. One TBTT information field corresponds to one AP.

31. The communication device according to claim 29 or 30, wherein 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.

32. The method according to any one of claims 20 - 31, wherein The first frame is any one of the following: a beacon frame, a probe response frame, and an association response frame.

33. The communication device according to claim 20, wherein The association response frame sent by an AP in the first AP MLD carries the current key BSS parameter update count values of multiple APs.

34. The communication device according to any one of claims 20, 26 - 33, wherein The processing unit is further configured to generate a second frame, which is used to indicate the specific key BSS parameters of multiple APs in the first AP MLD and the specific key BSS parameters of multiple APs in the second AP MLD; The transceiver unit is further configured to send the second frame on the link where the communication device operates.

35. The communication device according to any one of claims 21 - 32, wherein The transceiver unit is further configured to receive a second frame on the link where the communication device operates. The second frame is used to indicate the specific key BSS parameters of multiple APs in the first AP MLD and the specific key BSS parameters of multiple APs in the second AP MLD; The processing unit is further configured to parse the second frame to obtain the specific key BSS parameters of multiple APs in the AP MLD associated with the Non-AP MLD.

36. The communication device according to claim 34 or 35, wherein One of the specific key BSS parameters of an AP in the second frame includes one or more of the following: including a channel change notification element, including an extended channel change notification element, including a wide bandwidth channel change element, including a wide bandwidth channel change envelope element.

37. The method according to any one of claims 34 - 36, wherein One of the specific key BSS parameters of an AP in the second frame further includes one or more of the following: including a silent element, including a silent channel element.

38. The communication device according to any one of claims 34 - 37, wherein The specific key BSS parameter is carried in a multi-link ML element.

39. A communication device, wherein Including a processor and a transceiver, the transceiver is used for receiving and transmitting information or frames, and the processor is used to execute the method according to any one of claims 1-19.

40. A computer-readable storage medium, wherein Instructions are stored in the computer-readable storage medium, and when the instructions are run on a computer, the computer is caused to execute the method according to any one of claims 1-19.

41. A computer program product comprising instructions, wherein When the instructions are run on a computer, the computer is caused to execute the method according to any one of claims 1-19.

42. A chip or chip system, wherein Including an input-output interface and a processing circuit, the input-output interface is used for receiving code instructions and transmitting them to the processing circuit, and the processing circuit is used to run the code instructions to execute the method according to any one of claims 1-19.

Images