Method and apparatus for extremely high frequency link setup

Abstract

The first STA receives a beacon frame from the access point (AP) via a first link. Based on the received signal strength indicator (RSSI) of the beacon frame being less than a threshold: the first STA detects a second frame transmitted from the AP to the second STA via a second link; and based on the detection of the second frame, the first STA transmits a third frame to the AP, the third frame including a request to establish the second link between the first STA and the AP.

Description

Cross-reference to related applications

[0001] This application claims priority to U.S. Provisional Application No. 63 / 625,310, filed January 26, 2024, which is hereby incorporated in its entirety by reference. Attached Figure Description

[0002] Examples of several embodiments of the various embodiments of this disclosure are described herein with reference to the accompanying drawings.

[0003] Figure 1 An example wireless communication network in which embodiments of the present disclosure may be implemented is shown.

[0004] Figure 2 This is a block diagram illustrating an example implementation of a station (STA) and an access point (AP).

[0005] Figure 3 An example of the Media Access Control (MAC) frame format is shown.

[0006] Figure 4 An example of a Quality of Service (QoS) empty frame indicating buffer status information is shown.

[0007] Figure 5 An example format of the Physical Layer (PHY) Protocol Data Unit (PPDU) is shown.

[0008] Figure 6 An example is shown, including buffer status reporting by the STA, scheduling by the AP for uplink multi-user (MU) transmissions, and transmissions of scheduled uplink transmissions by the STA.

[0009] Figure 7 An example reference model of a multi-link device (MLD) is shown.

[0010] Figure 8 Examples of AP MLDs and associated non-AP MLDs are shown.

[0011] Figure 9 An example of a multi-link setup between an AP MLD and a non-AP MLD is shown.

[0012] Figure 10 An example of a flow identifier (TID) to link mapping is shown in a multi-link communication environment.

[0013] Figure 11 An example multi-link configuration including an extremely high frequency link is shown between an AP MLD and a non-AP MLD.

[0014] Figure 12An example of an EHF link setup procedure based on the signal strength associated with a non-EHF link is shown.

[0015] Figure 13 An example link setup process according to an embodiment is shown.

[0016] Figure 14 It shows Figure 13 An example of the link setup process is shown.

[0017] Figure 15 It shows Figure 13 Another example of the link setup process shown.

[0018] Figure 16 An example of another link setup process according to an embodiment is shown.

[0019] Figure 17 An example of another link setup process according to an embodiment is shown.

[0020] Figure 18 An example process according to an embodiment is shown.

[0021] Figure 19 An example process according to an embodiment is shown.

[0022] Figure 20 An example process according to an embodiment is shown. Detailed Implementation

[0023] In this disclosure, various embodiments are presented as examples of how the disclosed techniques can be implemented and / or how the disclosed techniques can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention. Alternative embodiments will become apparent to those skilled in the art upon reading this specification. Embodiments of the invention are not to be limited to any of the exemplary embodiments described. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create additional embodiments within the scope of this disclosure. Any diagrams highlighting functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, any actions listed in any flowchart may be reordered or used only optionally in certain embodiments.

[0024] The embodiments can be configured to operate as needed. When certain criteria are met, the disclosed mechanisms can be executed, for example, in stations, access points, radio environments, networks, or combinations thereof. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, service characteristics, or combinations thereof. Various example implementations can be applied when one or more criteria are met. Therefore, example embodiments that selectively implement the disclosed protocols can be implemented.

[0025] In this disclosure, the terms “a” and “an” and similar phrases will be interpreted as “at least one” and “one or more”. Similarly, any term ending with the suffix “(s)” will be interpreted as “at least one” and “one or more”. In this disclosure, the term “may” is interpreted as “may, for example”. In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a variety of suitable possibilities that may or may not be used in one or more of the various embodiments. As used herein, the terms “comprises” and “composes of” enumerate one or more components of the element being described. The terms “comprises” and “includes” are interchangeable and do not exclude the inclusion of unlisted components in the element being described. In contrast, “composes of” provides a complete enumeration of the one or more components of the element being described. As used herein, the term “based on” can be interpreted as “at least partially based on” rather than, for example, “based on only”. As used herein, the term “and / or” indicates any possible combination of the enumerated elements. For example, "A, B and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0026] If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {STA1, STA2} are: {STA1}, {STA2}, and {STA1, STA2}. The phrase “based on” (or equivalently “at least based on”) indicates that the phrase following the term “based on” is an example of one of a variety of suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase “in response to” (or equivalently “at least in response to”) indicates that the phrase following the phrase “in response to” is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase “depends on” (or equivalently “at least depends on”) indicates that the phrase following the phrase “depends on” is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments. The phrase “adopts / uses” (or equivalently “at least adopts / uses”) indicates that the phrase following the phrase “adopts / uses” is an example of one of a variety of suitable possibilities that may or may not be used in one or more different embodiments.

[0027] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can refer to specific settings within the device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Similarly, the term "control messages generated in the device" can mean that the control messages have parameters that can be used to configure specific characteristics in the device or to perform certain actions in the device, regardless of whether the device is in an operational or non-operational state.

[0028] In this disclosure, a parameter (or equivalently referred to as a field or information element: IE) may include one or more information objects, and an information object may include one or more other objects. For example, if parameter (IE)N includes parameter (IE)M, and parameter (IE)M includes parameter (IE)K, and parameter (IE)K includes parameter (information element)J, then, for example, N includes K, and N includes J. In an example embodiment, when one or more messages / frames include multiple parameters, this means that a parameter among the multiple parameters is in at least one of the one or more messages / frames, but not necessarily in every one of the one or more messages / frames.

[0029] Many of the proposed features are described as optional using the word "may" or parentheses. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the group of optional features. This disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways: having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0030] Many elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has defined interfaces to other elements. Modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or combinations thereof, all of which are behaviorally equivalent. For example, a module can be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement modules using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are typically programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure connections between internal hardware modules with limited functionality on the programmable device. The aforementioned techniques are often used in combination to achieve the desired result of functional modules.

[0031] Figure 1 An example wireless communication network in which embodiments of the present disclosure can be implemented is shown.

[0032] like Figure 1 As shown, an example wireless communication network may include an IEEE 802.11 (WLAN) infrastructure network 102. WLAN infrastructure network 102 may include one or more Basic Service Sets (BSS) 110 and 120 and a Distribution System (DS) 130.

[0033] BSS 110-1 and 110-2 each include a set of access points (APs or AP STAs) and at least one station (STA or non-AP STA). For example, BSS 110-1 includes AP 104-1 and STA 106-1, and BSS 110-2 includes AP 104-2 and STAs 106-2 and 106-3. The APs and at least one STA in the BSS perform association procedures for communicating with each other.

[0034] DS 130 can be configured to connect BSS 110-1 and BSS 110-2. Therefore, DS 130 can enable Extended Service Set (ESS) 150. Within ESS 150, APs 104-1 and 104-2 are connected via DS 130 and can have the same Service Set Identifier (SSID).

[0035] The WLAN infrastructure network 102 can be coupled to one or more external networks. For example, such as Figure 1 As shown, WLAN infrastructure network 102 can be connected to another network 108 (e.g., 802.X) via portal 140. Portal 140 can act as a bridge connecting DS 130 of WLAN infrastructure network 102 to the other network 108.

[0036] Figure 1 The example wireless communication network shown may further include one or more self-organizing networks or independent BSSs (IBSSs). A self-organizing network or IBSS is a network of multiple STAs included within each other's communication range. The multiple STAs are configured such that they can communicate with each other using direct peer-to-peer communication (i.e., without through an AP).

[0037] For example, in Figure 1 In this configuration, STAs 106-4, 106-5, and 106-6 can be configured to form a first IBSS 112-1. Similarly, STAs 106-7 and 106-8 can be configured to form a second IBSS 112-2. Since an IBSS does not include an AP, it does not include a centralized management entity. Instead, STAs within an IBSS are managed in a distributed manner. STAs forming an IBSS can be fixed or mobile.

[0038] A STA, serving as a predefined functional medium, may include a Media Access Control (MAC) layer conforming to the IEEE 802.11 standard. The physical layer interface of the radio medium can be used in both AP and non-AP stations (STAs). STAs may also be referred to using various other terms, including mobile terminal, radio device, radio transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, or user. For example, the term "user" may be used to refer to a STA participating in uplink multi-user multiple-input multiple-output (MU MIMO) and / or uplink orthogonal frequency division multiple access (OFDMA) transmissions.

[0039] Physical Layer (PHY) Protocol Data Units (PPDUs) can be composite structures, comprising a PHY preamble and a payload in the form of a PLCP Service Data Unit (PSDU). For example, a PSDU may include a PHY Convergence Protocol (PLCP) preamble and header and / or one or more MAC Protocol Data Units (MPDUs). The information provided in the PHY preamble can be used by the receiving device to decode subsequent data in the PSDU. When the PPDU is transmitted over a bonded channel (a channel formed by channel bonding), the preamble field can be copied and transmitted in each of the multiple component channels. The PHY preamble may include both a traditional portion (or "traditional preamble") and a non-traditional portion (or "non-traditional preamble"). The traditional preamble can be used for purposes such as packet detection, automatic gain control, and channel estimation. The traditional preamble is also typically used to maintain compatibility with legacy devices. The format, encoding, and information provided in the non-traditional portion of the preamble are based on the specific IEEE 802.11 protocol to be used for transmitting the payload.

[0040] A frequency band can include one or more sub-bands or frequency channels. For example, PPDUs conforming to IEEE 802.11n, 802.11ac, 802.11ax, and / or 802.11be standard modifications can be transmitted in 2.4 GHz, 5 GHz, and / or 6 GHz bands, each band can be divided into multiple 20 MHz channels. PPDUs can be transmitted through physical channels with a minimum bandwidth of 20 MHz. Larger channels can be formed through channel bonding. For example, multiple 20 MHz channels can be bonded together to transmit PPDUs through physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz, or 520 MHz.

[0041] Figure 2 This is a block diagram illustrating an example implementation of STA 210 and AP 260. (See diagram for example.) Figure 2As shown, STA 210 may include at least one processor 220, memory 230, and at least one transceiver 240. AP 260 may include at least one processor 270, memory 280, and at least one transceiver 290. Processors 220 / 270 may be operatively connected to memory 230 / 280 and / or transceiver 240 / 290.

[0042] Processors 220 / 270 can implement the functions of the PHY layer, MAC layer, and / or logical link control (LLC) layer of the corresponding device (STA 210 or AP 260). Processors 220 / 270 may include one or more processors and / or one or more controllers. For example, one or more processors and / or one or more controllers may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), logic circuitry, or a chipset.

[0043] Memory 230 / 280 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium, and / or other storage units. Memory 230 / 280 may include one or more non-transitory computer-readable media. Memory 230 / 280 may store computer program instructions or code that can be executed by processor 220 / 270 to perform one or more of the operations / embodiments discussed in this application. Memory 230 / 280 may be implemented (or located) within processor 220 / 270 or external to processor 220 / 270. Memory 230 / 280 may be operatively connected to processor 220 / 270 in various ways known in the art.

[0044] Transceiver 240 / 290 can be configured to transmit / receive radio signals. In embodiments, transceiver 240 / 290 can implement the PHY layer of the corresponding device (STA 210 or AP 260). In embodiments, STA 210 and / or AP 260 can be multi-link devices (MLDs), which are devices capable of operating on multiple links defined by the IEEE 802.11 standard. Therefore, STA 210 and / or AP 260 can each implement multiple PHY layers. One or more of transceivers 240 / 290 can be used to implement multiple PHY layers.

[0045] Figure 3An example format of a MAC frame is shown. In operation, the STA can construct a subset of MAC frames for transmission and can decode a subset of received MAC frames during verification. The specific subset of frames that the STA can construct and / or decode can be determined by the functions supported by the STA. The STA can verify received MAC frames using the Frame Check Sequence (FCS) contained within the frame and can decipher certain fields based on the MAC header of all frames.

[0046] like Figure 3 As shown, a MAC frame includes a MAC header, a variable-length frame body, and a frame check sequence (FCS).

[0047] The MAC header includes a frame control field, an optional duration / ID field, an address field, an optional sequence control field, an optional QoS control field, and an optional HT control field.

[0048] The frame control field includes the following subfields: protocol version, type, subtype, "to DS", "from DS", "more fragments", retry, power management, "more data", "protected frames" and "+HTC".

[0049] The size and placement of the protocol version subfield remain unchanged across all revisions of the IEEE 802.11 standard. For MAC frames, the value of the protocol version subfield is 0.

[0050] The Type and Subtype subfields together identify the function of a MAC frame. There are three frame types: control, data, and management. Each frame type has several defined subtypes. Bits within the subtype subfield are used to indicate specific modifications to the base data frame (subtype 0). For example, in a data frame, the most significant bit (MSB) of the subtype subfield, bit 7 (B7) of the frame control field, is defined as the QoS subfield. When the QoS subfield is set to 1, it indicates a QoS data frame, i.e., a data frame that includes the QoS control field in its MAC header. When set to 1 in the data subtype, the second MSB of the subtype field, bit 6 (B6) of the frame control field, indicates a data frame that does not include a frame body field.

[0051] The “To DS” subfield indicates whether the data frame is directed to the Distribution System (DS). The “From DS” subfield indicates whether the data frame originated from the DS.

[0052] In all data or management frames that have another fragment following the MAC Service Data Unit (MSDU) or MAC Management Protocol Data Unit (MMPDU) carried by the MAC frame, the "More Fragments" subfield is set to 1. In all other frames in which the "More Fragments" subfield exists, the "More Fragments" subfield is set to 0.

[0053] In any data or management frame that is a retransmission of an earlier frame, the retry subfield is set to 1. In all other frames in which the retry subfield exists, it is set to 0. The receiving STA uses this indication to assist in its process of eliminating duplicate frames. These rules do not apply to frames sent by the STA according to the block protocol.

[0054] The power management subfield is used to indicate the power management mode of the STA.

[0055] The “More Data” subfield, in Power Saving (PS) mode, indicates to the STA that a bufferable unit (BU) is buffered at the AP for the STA. The “More Data” subfield is valid in separately addressed data or management frames transmitted by the AP to the STA in PS mode. The “More Data” subfield is set to 1 to indicate that at least one additional buffered BU exists for the STA.

[0056] If the frame body field contains information that has been processed by an cryptographic encapsulation algorithm, the protected frame subfield is set to 1.

[0057] The +HTC subfield indicates that the MAC frame contains the HT control field.

[0058] The Duration / ID field in the MAC header indicates different content depending on the frame type and subtype, as well as the QoS capabilities of the sending STA. For example, in a control frame of the Power Saving Polling (PS-Poll) subtype, the Duration / ID field carries the Association Identifier (AID) of the STA that has transmitted a frame in 14 least significant bits (LSBs), and the two most significant bits (MSBs) are set to 1. In other frames transmitted by the STA, the Duration / ID field contains a duration value (in microseconds) for the receiver to use to update the Network Allocation Vector (NAV). The NAV is a counter indicating to the STA the amount of time during which the STA must postpone access to the shared medium.

[0059] A MAC frame format can contain up to four address fields. These address fields are used to indicate the Basic Service Set Identifier (BSSID), source address (SA), destination address (DA), transport address (TA), and receive address (RA). Some frames may not contain certain address fields. The use of certain address fields can be specified by the relative order of address fields (1-4) within the MAC header, regardless of the address type present in those fields. Specifically, address 1 always identifies the intended receiver of the frame, and address 2 (if present) always identifies the sender of the frame.

[0060] The sequence control field includes two subfields: a sequence number subfield and a fragment number subfield. In a data frame, the sequence number subfield indicates the sequence number of the MSDU (if not in an aggregated MSDU (A-MSDU)) or A-MSDU. In a management frame, the sequence number subfield indicates the sequence number of the frame. The fragment number subfield indicates the number of each fragment of the MSDU or MMPDU. In the first or only fragment of an MSDU or MMPDU, the fragment number is set to 0 and increments by one for each subsequent fragment of that MSDU or MMPDU. In a MAC Protocol Data Unit (MPDU) containing an A-MSDU or in an MPDU containing an unfragmented MSDU or MMPDU, the fragment number is set to 0. The fragment number remains constant throughout all retransmissions of the fragment.

[0061] The QoS control field identifies the service category (TC) or service flow (TS) to which the MAC frame belongs. The QoS control field can also indicate various other QoS-related, A-MSDU-related, and mesh-related information about the frame. This information can vary depending on the frame type, frame subtype, and the type of transport STA. The QoS control field exists in all data frames where the QoS subfield of the subtype subfield is equal to 1.

[0062] The HT control field exists in QoS data frames, QoS empty frames, and management frames, which are determined by the +HTC subfield of the frame control field.

[0063] The frame body field is a variable-length field that contains information specific to each frame type and subtype. The frame body may include one or more MSDUs or MMPDUs. The minimum length of the frame body is 0 octets.

[0064] The FCS field contains a 32-bit Cyclic Redundancy Check (CRC) code. The FCS field value is calculated on all fields of the MAC header and frame body.

[0065] Figure 4 An example of a QoS empty frame indicating buffer status information is shown. A QoS empty frame is a QoS data frame with an empty frame body. A QoS empty frame includes a QoS control field and an optional HT control field, which may contain a Buffer Status Report (BSR) control subfield. A QoS empty frame indicating buffer status information can be transmitted from a STA to an AP.

[0066] QoS control fields may include a Traffic Identifier (TID) subfield, an ACK policy indicator subfield, and a queue size subfield (or a Requested Transmission Opportunity (TXOP) duration subfield).

[0067] The TID subfield identifies the TC or TS that is requesting a TXOP by setting the requested TXOP duration or queue size subfield. The encoding of the TID subfield depends on the access policy (e.g., values ​​0 to 7 are allowed for Enhanced Distributed Channel Access (EDCA) access policies to identify the user priority of the TC or TS).

[0068] The ack policy indicator subfield and other information identify the acknowledgment policy to be followed after the MPDU is delivered (e.g., normal ack, implicit block ack request, no ack, block ack, etc.). The queue size subfield is an 8-bit field that indicates the amount of buffered traffic at the STA used to transmit to the AP identified by the receive address of the frame containing this subfield for a given TC or TS. The queue size subfield is present in the QoS empty frames transmitted by the STA when bit 4 of the QoS control field is set to 1. The AP can use the information contained in the queue size subfield to determine the duration of the TXOP assigned to the STA or to determine the uplink (UL) resources assigned to the STA.

[0069] In frames sent to or from inefficient (non-HE) STAs, the following rules may be applied to queue size values: - The queue size value is the approximate total size of all MSDUs and A-MSDUs (excluding MSDUs or A-MSDUs contained in this QoS data frame) buffered at the STA in the delivery queue for MSDUs and A-MSDUs, rounded up to the nearest multiple of 256 octets, and expressed in units of 256 octets, where the TID value is equal to the value indicated in the TID subfield of the QoS control field.

[0070] - A queue size value of 0 is only used to indicate that there is no buffered traffic in the queue used for the specified TID.

[0071] - For all sizes greater than 64,768 octets, use a queue size value of 254.

[0072] - The queue size value of 255 is used to indicate an unspecified or unknown size.

[0073] In frames sent from HE STA to HE AP, the following rules can be applied to queue size values.

[0074] Queue size value QSIt is the approximate total size of all MSDUs and A-MSDUs buffered at the STA in the delivery queue for MSDUs and A-MSDUs (including MSDUs or A-MSDUs contained in the same PSDU as the frame containing the queue size subfield), represented in octets, where the TID value is equal to the value indicated in the TID subfield of the QoS control field.

[0075] The queue size subfield includes the scaling factor subfield in bits B14 to B15 of the QoS control field and the unscaled value in bits B8 to B13 of the QoS control field. UV The scaling factor subfield provides the scaling factor. SF .

[0076] STA receives data containing scaling factors SF and unscaled values UV Get queue size from QoS control field QS ,as follows: QS = 16 × UV ,if SF Equal to 0; 1024 + 256 × UV ,if SF It equals 1; 17,408 + 2048 × UV ,if SF It equals 2; 148 480 + 32 768 × UV ,if SF Equal to 3 and UV Less than 62; >2 147 328, if SF Equal to 3 and UV Equals 62; not specified or unknown ,if SF Equal to 3 and UV It equals 63.

[0077] The requested TXOP duration subfield, which may be included instead of the queue size subfield, indicates to the sending STA the duration, in 32 microseconds (µs), required for the next TXOP for the specified TID. The requested TXOP duration subfield is set to 0 to indicate that no TXOP is requested for the specified TID in the current service period (SP). The requested TXOP duration subfield is set to a non-zero value to indicate the requested TXOP duration in increments of 32 µs within the range of 32 µs to 8160 µs.

[0078] The HT control field may include a BSR control subfield, which may contain buffer status information for UL MU operations. The BSR control subfield may be formed by the following: the Access Class Index (ACI) bitmap subfield of the HT control field, the incremental TID subfield, the ACI high subfield, the scaling factor subfield, the queue size high subfield, and the queue size full subfield.

[0079] The ACI bitmap subfield indicates the access class (AC) for reporting buffer status (e.g., B0: Best Effort (AC_BE); B1: Background (AC_BK); B2: Video (AC_VI); B3: Voice (AC_VO), etc.). Each bit of the ACI bitmap subfield is set to 1 to indicate that the buffer status for the corresponding AC is included in the queue size full subfield, and is otherwise set to 0. However, if the ACI bitmap subfield is 0 and the incremental TID subfield is 3, then the buffer status is included for all 8 TIDs.

[0080] The values ​​of the ΔTID subfield and the ACI bitmap subfield indicate the number of TIDs that the STA is reporting in the buffer status.

[0081] The ACI high subfield indicates the ACI of the AC indicated by the BSR in the queue size high subfield. The ACI to AC mapping is defined as ACI value 0 mapping to AC_BE, ACI value 1 mapping to AC_BK, ACI value 2 mapping to AC_VI, and ACI value 3 mapping to AC_VO.

[0082] The scaling factor subfield indicates the units of the queue size height and the queue size full subfield. SF It is represented by an octet.

[0083] The queue size high subfield indicates the amount of buffered traffic for the AC identified by the ACI high subfield. SF The octet is intended for use with the STA identified by the receiver address of the frame containing the BSR control subfield.

[0084] The queue size full subfield indicates the amount of buffered traffic for all ACs identified by the ACI bitmap subfield. SF The octet is intended for use with the STA identified by the receiver address of the frame containing the BSR control subfield.

[0085] The queue size values ​​in the queue size high and queue size full subfields are the total size of all MSDUs and A-MSDUs buffered at the STA in the delivery queues for MSDUs and A-MSDUs associated with the AC, as specified in the ACI high and ACI bitmap subfields respectively, rounded up. SF The closest multiple of an octet.

[0086] The queue size value of 254 in both the queue size high and queue size full subfields indicates that the amount of buffered traffic is greater than 254 × SF Eight-bit byte. The queue size value of 255 in both the queue size high and queue size full subfields indicates that the amount of buffered traffic is unspecified or unknown. The queue size value of a QoS data frame containing fragments can remain constant, even if the amount of queued traffic changes as consecutive fragments are transmitted.

[0087] The MAC service provides peer entities with the ability to exchange MSDUs. To support this service, the local MAC uses an underlying PHY-level service to transmit MSDUs to the peer MAC entity. This type of asynchronous MSDU transmission is performed on a connectionless basis.

[0088] Figure 5 An example format for a PPDU is shown. As shown in the figure, a PPDU may include a PHY preamble, a PHY header, a PSDU, and a tail and padding bits.

[0089] A PSDU may include one or more MPDUs, such as a QoS data frame, an MMPDU, a MAC control frame, or a QoS empty frame. When an MPDU carries a QoS data frame, the frame body of the MPDU may include an MSDU or an A-MSDU.

[0090] By default, MSDU delivery is done on a best-effort basis. That is, there is no guarantee that the transmitted MSDU will be successfully delivered. However, QoS facilities use Service Identifiers (TIDs) to specify differentiated services based on each MSDU.

[0091] The STA can differentiate MSDU delivery based on the specified service category (TC) or service flow (TS) of each MSDU. The MAC sublayer entity determines the user priority (UP) of the MSDU based on the TID value provided with the MSDU. The QoS facility supports eight UP values. The UP values ​​range from 0 to 7 and form an ordered priority sequence, where 1 is the lowest value, 7 is the highest value, and 0 falls between 2 and 3.

[0092] MSDUs with a specific UP are referred to as belonging to the traffic class with that UP. The UP can be provided directly in the UP parameter at the Media Access Control Service Access Point (MAC SAP) along with each MSDU. A-MPDUs can include MPDUs with different TID values.

[0093] The STA can deliver Buffer Status Reports (BSRs) to help the AP allocate UL MU resources. The STA can deliver a BSR implicitly (unrequested BSR) in the QoS control field or BSR control subfield of any frame transmitted to the AP, or explicitly (requested BSR) in a frame sent to the AP in response to a BSRP trigger frame.

[0094] The buffer status reported in the QoS control field includes the queue size value for a given TID. The buffer status reported in the BSR control field includes the ACI bitmap, ΔTID, high-priority AC, and both queue sizes.

[0095] The STA can report the buffer status of transmitted QoS empty frames and QoS data frames to the AP in the QoS control field, and report the buffer status of transmitted QoS empty frames, QoS data frames and management frames in the BSR control subfield (if present), as defined below.

[0096] The STA can report the queue size for a given TID in the queue size subfield of the QoS control field of the transmitted QoS data frame or QoS empty frame; the STA can set the queue size subfield to 255 to indicate an unknown / unspecified queue size for the TID. The STA can aggregate multiple QoS data frames or QoS empty frames in the A-MPDU to report the queue size for different TIDs.

[0097] If the AP has indicated that it supports receiving the BSR control subfield, then the STA can report the buffer status in the BSR control subfield of the transmitted frame.

[0098] The High Efficiency (HE) STA can report the queue size of the preferred AC, indicated by the ACI high subfield, in the queue size high subfield of the BSR control subfield. The STA can set the queue size high subfield to 255 to indicate an unknown / unspecified queue size for the AC.

[0099] The HE STA can report the queue size of the AC, as indicated by the ACI bitmap subfield, in the queue size full subfield of the BSR control subfield. The STA can set the queue size full subfield to 255 to indicate those ACs with unknown / unspecified BSRs.

[0100] Figure 6An example is shown, including buffer status reporting by the STA, scheduling by the AP for uplink multi-user (MU) transmissions, and transmissions of scheduled uplink transmissions by the STA.

[0101] As shown in the figure, the AP can request the buffer status of one or more associated STAs (STA 1 and STA 2) by sending a Buffer Status Report Polling (BSRP) trigger frame. Upon receiving the BSRP trigger frame, if the BSRP trigger frame contains 12 LSBs of the STA AID in the User Information field, then STA 1 and / or STA 2 can each generate a trigger-based (TB) PPDU.

[0102] STA 1 and / or STA 2 may each include one or more QoS empty frames in a TB PPDU. The one or more QoS empty frames may contain one or more QoS control fields or one or more BSR control subfields.

[0103] As previously described, the QoS control field may include a queue size subfield where the STA has a queue size to report to the AP using the TID. For example, as Figure 6 As shown, STA 1 can respond to a BSRP trigger frame from the AP by transmitting an A-MPDU that includes multiple QoS empty frames. Each QoS empty frame indicates the queue size of the corresponding TID in its respective QoS control field, such as TID0 and TID2. Similarly, STA 2 can respond to a BSRP trigger frame by transmitting an MPDU that includes QoS empty frames, which indicate the queue size of TID2 in its QoS control field.

[0104] The BSR control subfield may include a queue size full subfield indicating the queue size of the AC as indicated by the ACI bitmap subfield, wherein if the AP has indicated that it supports receiving the BSR control subfield, then the STA has a queue size to report to the AP. The STA sets the incremental TID, scaling factor, ACI high, and queue size high subfields of the BSR control subfield.

[0105] Upon receiving a BSR from STA 1 and STA 2, the AP can transmit a basic trigger frame to allocate UL MU resources to STA 1 and STA 2. In response, STA 1 can transmit a TB PPDU containing QoS data frames with TID 0 and TID 2, and STA 2 can transmit a TB PPDU containing one or more QoS data frames with TID 0. The AP can acknowledge the TB PPDUs transmitted from STA 1 and STA 2 by sending a multi-STA block ack frame.

[0106] Figure 7An example reference model of a multi-link device (MLD) is shown.

[0107] An MLD is an entity capable of managing communication over multiple links. An MLD can be a logical entity and can have more than one affiliated station (STA). An MLD can be an Access Point MLD (AP MLD), where the STAs affiliated with the MLD are AP STAs (or APs). An MLD can also be a Non-Access Point MLD (Non-AP MLD), where the STAs affiliated with the MLD are non-AP STAs (or STAs).

[0108] Depending on the capabilities of both the communication AP MLD and non-AP MLD, communication across different frequency bands / channels can occur simultaneously or at different times.

[0109] like Figure 7 As shown, an MLD can have a single MAC service access point (MAC-SAP) to the LLC layer, including MAC data services. An MLD can support multiple MAC sub-layers coordinated through a Sub-Layer Management Entity (SME). Each AP STA (or non-AP STA) attached to an AP MLD (or non-AP MLD) has a different MAC address within the MLD.

[0110] The SME is responsible for coordinating the MAC sublayer management entity (MLME) of the MLD's affiliated STA to maintain a single robust Secure Network Association (RSNA) key management entity and a single IEEE 802.1X authenticator or provider for multi-link operation (MLO).

[0111] Multi-Link Operation (MLO) procedures allow a pair of MLDs to discover, synchronize, (de-)authenticate, (re)associate, disassociate, and manage resources on any common frequency band or channel supported by both MLDs. The authenticator and MAC-SAP of an AP MLD can be identified by the same AP MLD MAC address. The supplier and MAC-SAP of a non-AP MLD can be identified by the same non-AP MLD MAC address.

[0112] Figure 8 Examples of AP MLDs and associated non-AP MLDs are shown.

[0113] As shown in the figure, the AP MLD has two affiliated APs (AP1 and AP2), and the non-AP MLD has two affiliated STAs (STA1 and STA2). The AP MLD and the non-AP MLD can be communicatively coupled by two links (Link 1 and Link 2). Link 1 is established between AP1 and STA1, and Link 2 is established between AP2 and STA2.

[0114] Typically, the MAC addresses of the MLD and its associated STAs are different from each other. For example, such as Figure 8 As shown, AP MLD can have a MAC address. M AP 1 can have a MAC address w And AP2 can have a MAC address. x Similarly, non-AP MLDs can have MAC addresses. P STA 1 can have a MAC address y And STA2 can have a MAC address. z .

[0115] like Figure 8 As shown, for each MLD, the MAC sublayer can be further divided into the upper MLD MAC sublayer and the lower MLD MAC sublayer. The upper MLD MAC sublayer performs functions common to all links. The lower MLD MAC sublayer performs functions local to each link. Some functions require joint processing from both the upper MLD MAC sublayer and the lower MLD MAC sublayer.

[0116] The upper MAC sublayer of the MLD can include the following functions: - Authentication, association, and re-association (between AP MLD and non-AP MLD); - Distribution of security associations (e.g., Paired Master Key Security Association (PMKSA), Paired Transient Key Security Association (PTKSA)) and Group Time Key (GTK) / Integrity GTK (IGTK) / Beacon IGTK (BIGTK); - Assign the sequence number (SN) / packet number (PN) of the frame encrypted by the pairwise transient key (PTK) of the unicast frame; -Use PTK to encrypt / decrypt unicast frames; - Select the lower MAC sublayer of MLD (TID to link mapping) for transmission; - Reorder packets to ensure ordered delivery for each Block Ack session; - A Block Ack scoreboard for individually addressed frames (in cooperation with the lower MLD MAC sublayer); optionally, the upper MLD MAC sublayer delivers Block Ack records on a link to the lower MLD MAC sublayer for other links; and - MLD-level management information exchange / instruction via the lower MAC sublayer of MLD. The lower MAC sublayer functionality of MLD can include: - Link-specific GTK / IGTK / BIGTK maintenance (between APs attached to AP MLDs and STAs attached to non-AP MLDs). - Link-specific encryption / decryption / integrity protection and PN assignment using GTK / IGTK / BIGTK (between APs attached to AP MLDs and STAs attached to non-AP MLDs); - Link-specific management information exchange / instructions (e.g., beacons); - Link-specific control information exchange / indication (e.g., RTS / CTS, acknowledgments, etc.); - Power saving status and modes; - MAC address filtering for frame reception; and - A Block Ack scoreboard for separately addressed frames (in cooperation with the upper MAC sublayer of MLD); optionally, the lower MAC sublayer of MLD receives Block Ack records on other links from the upper MAC sublayer of MLD.

[0117] Multilink (re)configuration between a non-AP MLD and an AP MLD can involve the exchange of (re)association request / response frames. The exchange of (re)association request / response frames for multilink configuration can include two frames carrying basic multilink elements.

[0118] In a (re)association request frame, the non-AP MLD indicates the link requested for (re)configuration, along with the capabilities and operating parameters of the requested link. A non-AP MLD can request (re)configuration of links with a subset of APs attached to an AP MLD. The link requested for (re)configuration, along with the capabilities and operating parameters of the requested link, is independent of the existing configuration links and their capabilities and operating parameters with the associated AP MLD.

[0119] In the (re)association response frame, the AP MLD can indicate the accepted and rejected requested links for (re)reconfiguration, as well as the capabilities and operating parameters of the requested links. The AP MLD can accept a subset of the links requested for (re)reconfiguration. The (re)association response frame is sent to the non-AP STA attached to the non-AP MLD that sent the (re)association request frame.

[0120] The MLD that requests or accepts multi-link (re)configuration of any two links ensures that each link is located on a different non-overlapping channel. After a successful multi-link (re)configuration between a non-AP MLD and an AP MLD, the non-AP MLD and APMLD configure the link used for multi-link operation, and the non-AP MLD is (re)associated with the AP MLD. For each configured link, the corresponding non-AP STA attached to the non-AP MLD is in the same association state as the non-AP MLD and is associated with the corresponding AP attached to the APMLD. For each configured link, functionality between the non-AP STA and its associated AP is enabled, unless the functionality has been extended to the MLD level or otherwise specified.

[0121] Figure 9 An example of a multi-link setup between an AP MLD and non-AP MLDs is shown. As illustrated, the AP MLD has three affiliated APs: AP 1 operating in the 2.4 GHz band, AP 2 operating in the 5 GHz band, and AP 3 operating in the 6 GHz band. The non-AP MLD has three affiliated STAs: non-AP STA 1 operating in the 2.4 GHz band, non-AP STA 2 operating in the 5 GHz band, and non-AP STA 3 operating in the 6 GHz band.

[0122] A non-AP MLD can initiate multi-link setup by sending an association request frame from non-AP STA 1 to AP 1, which is attached to the AP MLD. In the association request frame, the transmitter address (TA) field is set to the MAC address of non-AP STA 1, and the receiver address (RA) field is set to the MAC address of AP 1. The association request frame includes basic multi-link elements, indicating the MLD MAC address of the non-AP MLD and complete information for non-AP STA 1, non-AP STA 2, and non-AP STA 3. The association request frame can request the setup of three links between the non-AP MLD and the AP MLD (a link between AP 1 and non-AP STA 1, a link between AP 2 and non-AP STA 2, and a link between AP 3 and non-AP STA 3).

[0123] AP MLD can respond to a requested multilink setup by sending an association response frame to a non-AP STA 1 attached to the non-AP MLD. In the association response frame, the TA field is set to the MAC address of AP 1, and the RA field is set to the MAC address of the non-AP STA 1. The association response frame includes basic multilink elements indicating the MLD MAC address of AP MLD and complete information for AP 1, AP 2, and AP 3. The association response frame signals successful multilink setup by indicating the setup of the three links between the non-AP MLD and AP MLD (link 1 between AP 1 and non-AP STA 1, link 2 between AP 2 and non-AP STA 2, and link 3 between AP 3 and non-AP STA 3).

[0124] By default, all TIDs at non-AP MLDs are mapped to all configured links on both the uplink and downlink. The TID-to-link mapping mechanism allows AP MLDs and non-AP MLDs that have performed or are performing multi-link configurations to specify how UL and DL QoS traffic corresponding to different TIDs (e.g., between 0 and 7) can be assigned to configured links. In negotiated TID-to-link mapping, TIDs can be mapped to a set of links, which is a subset of configured links, ranging from a single configured link to all configured links.

[0125] If at least one TID is mapped to a set link in either the DL or UL, that link is defined as enabled for non-APMLDs, and if no TID is mapped to that link in either the DL or UL, it is defined as disabled. At any given time, a TID is always mapped to at least one set link in both the DL and UL, meaning that a change in TID-to-link mapping is only valid and successful if it does not result in a set of mapped links consisting of zero set links.

[0126] By default, all configured links are enabled. If a link is enabled for a non-AP MLD, the link can be used to exchange individually addressed frames, depending on the power state of the non-AP STA operating on that link. Only MSDUs or A-MSDUs with a TID mapped to the link can be transmitted on that link in the direction corresponding to the TID-to-link mapping (DL / UL). In DL and UL, individually addressed management and control frames can be transmitted on any enabled link between a non-AP MLD's affiliated STA and the corresponding AP of the AP MLD.

[0127] If the link is disabled for a non-AP MLD, the link may not be used to exchange separately addressed frames between the affiliated STA of the non-AP MLD and the corresponding AP of the AP MLD.

[0128] If a TID is mapped in the UL to a set of enabled links of a non-AP MLD, the non-AP MLD can use any link within that set of enabled links to transmit an MSDU or A-MSDU that is individually addressed to that TID.

[0129] If a TID is mapped in the DL to a set of enabled links of a non-AP MLD, the non-AP MLD can retrieve the individually addressed BU buffered at the AP MLD for the corresponding TID, either the MSDU or A-MSDU, on any link in that set of enabled links. Conversely, the AP MLD can use any link within that set of enabled links to transmit the individually addressed MSDU or A-MSDU corresponding to the TID, depending on the power state of the non-AP STA on each used link.

[0130] If the default mode is used, non-AP MLDs can retrieve BUs buffered by AP MLDs on any configured link, although AP MLDs may recommend links.

[0131] A non-AP MLD can retrieve a buffered BU, which is an MMPDU buffered at the AP MLD on any enabled link. The AP MLD can use any enabled link to transmit separately addressed buffered management frames that do not measure MMPDUs, depending on the power state of the non-AP STAs on the link used.

[0132] If a STA attached to a non-AP MLD is in active mode on a link with a set of TIDs mapped for DL ​​transmission, its associated AP attached to the AP MLD may transmit to the STA: MSDUs / A-MSDUs of the set of mapped TIDs of the non-AP MLD; and MMPDUs of the measurement MMPDUs that are not of the non-AP MLD or its attached STA, unless the frame is transmitted to another STA attached to the same non-AP MLD and in active mode.

[0133] As described above, in the default mapping mode, all TIDs are mapped to all configuration links of DL and UL, and all configuration links are enabled. If TID-to-link mapping negotiation for different mappings does not occur, fails, or is torn down, non-AP MLDs and AP MLDs performing multi-link configurations should operate in this mode.

[0134] In the multilink (re)setup procedure, if the AP MLD has indicated support for TID-to-link mapping negotiation, a non-APMLD can initiate TID-to-link mapping negotiation by including a TID-to-link mapping element in the (re)association request frame.

[0135] Upon receiving a (re)association request frame containing a TID-to-link mapping element, the AP MLD may respond to the (re)association request frame according to the following rules: The AP MLD may accept the requested TID-to-link mapping indicated in the TID-to-link mapping element of the received (re)association request frame only if the AP MLD accepts multi-link (re)configuration for all links requesting mapping at least one TID. In this case, the non-AP MLD does include the TID-to-link mapping element in the (re)association response frame. Otherwise, the non-AP MLD indicates rejection of the proposed TID-to-link mapping by including a TID-to-link mapping element suggesting a preferred TID-to-link mapping in the (re)association response frame.

[0136] After a successful multilink (re)configuration, in order to negotiate a new TID-to-link mapping, the initiating MLD can send a separately addressed TID-to-link mapping request frame to the responding MLD that has indicated support for TID-to-link mapping negotiation.

[0137] Upon receiving a separately addressed TID-to-link mapping request frame, the responding MLD sends a separately addressed TID-to-link mapping response frame to the initiating MLD according to the following rules: The responding MLD may accept the requested TID-to-link mapping indicated in the TID-to-link mapping element of the received TID-to-link mapping request frame by transmitting the TID-to-link mapping response frame. Otherwise, the responding MLD may indicate a rejection of the proposed TID-to-link mapping in the TID-to-link mapping response frame. The responding MLD may suggest a preferred TID-to-link mapping in the TID-to-link mapping response frame by including a TID-to-link mapping element in the TID-to-link mapping response frame.

[0138] MLDs can recommend preferred TID-to-link mappings to their peer MLDs by sending a non-requested TID-to-link mapping response frame that includes TID-to-link mapping elements.

[0139] When a peer MLD indicates a preferred TID-to-link mapping, the MLD can consider this preferred TID-to-link mapping when initiating a new TID-to-link mapping. Additionally, the AP MLD can consider traffic flows attached to non-AP MLDs, as well as the capabilities and constraints of non-AP MLDs (if any).

[0140] When two MLDs negotiate a TID-to-link mapping, either MLD can tear down the negotiated TID-to-link mapping by sending a separately addressed TID-to-link mapping teardown frame. After teardown, the MLD operates in the default mapping mode.

[0141] When an MLD successfully negotiates a TID-to-link mapping with its peer MLD, both the MLD and the peer MLD update the uplink and / or downlink TID-to-link mapping information based on the negotiated TID-to-link mapping.

[0142] When an MLD has successfully negotiated uplink and / or downlink TID-to-link mappings with its peer MLD, the link mapping field in the TID-to-link mapping element... n position i When set to 0, TID n It should not be mapped to a link ID in the uplink and / or downlink. i Associated links. When an MLD has successfully negotiated uplink and / or downlink TID-to-link mappings with its peer MLD, the link mapping field in the TID-to-link mapping element... n position i When set to 1, TID n Mapped to link IDs in the uplink and / or downlink i Related links.

[0143] Figure 10 An example of TID-to-link mapping in a multi-link communication environment is shown. As illustrated, the multi-link communication environment includes an AP MLD with three affiliated APs and a non-AP MLD with three affiliated STAs.

[0144] During or after multi-link setup, non-AP MLDs and AP MLDs can negotiate TID-to-link mappings. TID-to-link mappings map the TIDs at the non-AP MLDs in the UL and DL to establish a link between the AP MLD and the non-AP MLD. For example, as... Figure 10 As shown, TID-to-link mapping maps TIDs 0-6 from both UL and DL to link 1, and TID 7 from both UL and DL to link 2. Therefore, links 1 and 2 are enabled, and link 3 is disabled. TID-to-link mapping negotiation can be performed by exchanging association request / response frames or TID-to-link mapping request / response frames between non-AP MLDs and AP MLDs.

[0145] Envisioning future IEEE 802.11 devices supporting communication over extremely high frequency (EHF) links. EHF links could include links within millimeter-wave (mmWave) bands (e.g., RF frequency bands from 30 to 300 GHz). For example, EHF links are expected to include 60 GHz links (e.g., links in the frequency range of 57 to 71 GHz). While the communication range on EHF links may be shorter than that on non-EHF links (e.g., 2.4, 5, and 6 GHz), EHF links are expected to support greater bandwidth than non-EHF links, and therefore be more suitable for low-latency and wide-bandwidth communication.

[0146] Figure 11 An example multi-link configuration including an EHF link is shown between an AP MLD and a non-AP MLD. As shown, the AP MLD has four affiliated APs: AP 1 operating in the 2.4 GHz band, AP 2 operating in the 5 GHz band, AP 3 operating in the 6 GHz band, and AP 4 operating in the 60 GHz band. The non-AP MLD has four affiliated STAs: non-AP STA 1 operating in the 2.4 GHz band, non-AP STA 2 operating in the 5 GHz band, non-AP STA 3 operating in the 6 GHz band, and non-AP STA 4 operating in the 60 GHz band.

[0147] Non-AP MLDs can perform multi-link (re)configuration (as referenced above). Figure 9 As described, multiple links with the APMLD are (re)configured. After a successful multi-link (re)configuration between a non-AP MLD and an AP MLD, the non-AP MLD becomes associated with the AP MLD, and multiple links are configured between the non-AP MLD and the AP MLD. More specifically, for each configured link, the corresponding non-AP STA attached to the non-AP MLD becomes associated with the corresponding AP attached to the AP MLD. For example, in Figure 11In this configuration, the AP MLD can perform multi-link (re)configuration to set up multiple links from multiple links, including a first link (link 1), a second link (link 2), a third link (link 3), and a fourth link (link 4). In the example, links 1, 2, 3, and 4 can correspond to a 2.4 GHz link, a 5 GHz link, a 6 GHz link, and a 60 GHz link, respectively. The 2.4 GHz, 5 GHz, and 6 GHz links are non-EHF links, while the 60 GHz link is an EHF link. At the end of the multi-link (re)configuration, the non-AP MLD is associated with the AP MLD, and links 1, 2, and 3 are set between the non-AP MLD and the AP MLD. Specifically, non-AP STA 1 is associated with AP 1, non-AP STA 2 is associated with AP 2, and non-AP STA 3 is associated with AP 3.

[0148] In one example, a non-AP MLD can request settings for links 1, 2, and 3 in a multi-link (re)configuration, and the AP MLD can accept the request, resulting in the settings of links 1, 2, and 3. In another example, a non-AP MLD can request settings for links 1, 2, 3, and 4, and the AP MLD can accept settings for links 1, 2, and 3 but not for link 4. Therefore, link 4 can remain unconfigured, as... Figure 11 As shown in the diagram. Link configuration can then be enabled by mapping to each of one or more TIDs, as referenced above. Figure 10 As described.

[0149] In the example, a non-AP MLD can cause the following when executed: Figure 11 After the settings of links 1, 2, and 3 shown in the diagram are (re)configured, a request for the settings of link 4 is made to the AP MLD. In an implementation, a non-AP MLD can request link reconfiguration of the ML settings by sending a link reconfiguration request frame to the AP MLD. The non-AP MLD can send the link reconfiguration request frame from an attached non-AP STA to the corresponding AP attached to the AP MLD. To indicate support for link reconfiguration, the AP MLD can set the link reconfiguration operation support subfield to 1 in the MLD capability and operation subfield of the basic multi-link element transmitted by the AP MLD. The link reconfiguration request frame may contain a reconfigured multi-link element containing a per-STA profile sub-element for each attached non-AP STA that the non-AP MLD is requesting to be added to or removed from its ML settings. For example, in Figure 11In the reconfiguration multilink element contained in the link reconfiguration request frame from a non-AP MLD, there may be a Per-STA profile sub-element for non-AP STA 4. The Per-STA profile sub-element for non-AP STA 4 may contain, for example: a link ID subfield, which is set to the link identifier of AP 4 operating on the link 4 that the non-AP MLD is requesting to add; an NSTR (Not Simultaneous Transmit and Receive) indicator bitmap presence bit, which is set to 1 if there is at least one NSTR link pair containing link 4 for the non-AP MLD; a STA MAC address subfield in the STA information field, which is set to the STA MAC address of non-AP STA 4; and an STA profile field, which contains the complete profile of non-AP STA 4.

[0150] After receiving a link reconfiguration request frame from a non-AP MLD, the AP MLD can respond with a link reconfiguration response frame. The AP MLD can verify the OCI elements contained in the link reconfiguration request frame before sending the link reconfiguration response frame to the non-AP MLD. The AP MLD can send the link reconfiguration response frame via the same link on which the AP MLD received the link reconfiguration request frame. If the AP MLD accepts the addition of one or more links, the AP MLD can include a basic multi-link element in the link reconfiguration response frame, which contains a Per-STA profile sub-element for each AP operating on the links accepted by the AP MLD for use in the ML settings of the non-AP MLD. For example, in Figure 11 If the AP MLD accepts the addition of link 4, the AP MLD may include a basic multilink element in the link reconfiguration response frame, which includes a Per-STA profile sub-element for AP 4.

[0151] After sending a link reconfiguration response frame indicating the SUCCESS status for adding a link to a non-AP MLD and receiving an acknowledgment of the response frame from the non-AP MLD, the AP MLD will consider the link to have been added to the ML settings of the associated non-AP MLD.

[0152] AP MLD may reject a request to add a link if any of the following conditions are met: - The non-AP STA attached to the non-AP MLD corresponding to the link does not support all rates in the BSBasicRateSet parameter and all member selectors in the BSMembershipSelectorSet parameter of the AP attached to the AP MLD corresponding to the link in the MLME-START.request primitive.

[0153] - The non-AP STA associated with the non-AP MLD corresponding to the link does not support all MCS in the basic HT-MCS set field of the HT operation parameters of the AP associated with the AP MLD (if it exists) corresponding to the link in the MLME-START.request primitive.

[0154] - The non-AP STA associated with the non-AP MLD corresponding to the link does not support all APs associated with the AP MLD corresponding to the link (if they exist) as indicated by the basic VHT-MCS and NSS set fields of the VHT operation parameters in the MLME-START.request primitive.<VHT-MCS, NSS> tuple.

[0155] - The non-AP STA attached to the non-AP MLD corresponding to the link does not support all the basic HE-MCS and NSS set fields of the HE operation parameters indicated by the AP attached to the AP MLD corresponding to the link in the MLME-START.request primitive.<HE-MCS, NSS> tuple.

[0156] - The non-AP STA associated with the non-AP MLD corresponding to the link does not support all the basic EHT-MCS and NSS set fields of the EHT operation parameters indicated by the AP associated with the AP MLD corresponding to the link in the MLME-START.request primitive.<EHT-MCS, NSS> tuple.

[0157] - If a non-AP STA associated with a non-AP MLD corresponding to the link has the same MAC address as a non-AP STA associated with an AP associated with an AP MLD corresponding to the link (whether it is associated with a non-AP MLD or not).

[0158] When a non-AP STA attached to a non-AP MLD receives one or more of the following, the non-AP MLD can discover the APMLD and its associated APs (including associated APs operating on the EHF link): - A basic multilink element carried in a beacon frame or probe response frame (which is not a multilink probe response), the beacon frame or probe response frame being transmitted by an AP attached to an AP MLD or by an AP corresponding to the transmitted BSSID that is in the same set of multiple BSSIDs as at least one of the APs attached to an AP MLD.

[0159] - A multilink probe response, which comes from an AP attached to an AP MLD or an AP corresponding to the transmitted BSSID in the same set of multiple BSSIDs as at least one of the APs attached to an AP MLD, carrying a basic multilink element with the entire profile of one or more reported APs.

[0160] - One or more of the beacon frames, probe response frames, or FILS discovery frames transmitted by an AP (reporting AP), wherein the frame carries a Reduced Neighbor Reporting Element, which includes an MLD parameter subfield in the TBTT information field corresponding to one or more reported APs. Non-AP MLDs infer the relationship between one or more reported APs and the reporting AP by decoding the APMLD ID subfield of the MLD parameter subfield in the Reduced Neighbor Reporting Element and following the rules described in 35.3.4.1 (AP Behavior).

[0161] - Management frames carrying neighbor report elements. Non-AP MLDs determine whether two or more APs reported in different neighbor report elements containing basic multilink sub-elements are attached to the same AP MLD based on the MLD MAC address subfield of the common information field of the basic multilink element. If the reported APs carry the same value in the MLD MAC address field of the common information field of the basic multilink element, then the reported APs are attached to the same AP MLD.

[0162] Non-AP MLDs can use the information they collect from the Reduced Neighbor Reporting Element, Neighbor Reporting Element, or Basic Multilink Element to decide whether to perform ML settings with the AP MLD.

[0163] While a non-AP MLD may be able to discover that the AP MLD supports an EHF link, the non-AP MLD may further need to determine whether it can reach the AP MLD via the EHF link in order to communicate with the AP MLD via the EHF link. In one approach, the AP MLD may be configured to transmit beacon frames via the EHF link. A beacon frame may be referred to as an "optical beacon." The AP MLD may periodically transmit the optical beacon. In an implementation, the non-AP MLD may use the optical beacon to make EHF link reachability decisions. That is, the non-AP MLD may determine whether it can reach the AP MLD via the EHF link based on whether the non-AP MLD can detect the optical beacon (e.g., having an SNR above a threshold). The optical beacon may or may not be used for association between the AP MLD and the non-AP MLD. The optical beacon may or may not be used for BSS management.

[0164] In another approach, EHF link reachability can be based on signal strength on one or more non-EHF links, rather than using beacon frames on the EHF link. Figure 12Example 1200 of an EHF link setup procedure based on signal strength associated with a non-EHF link is shown. Figure 12 As shown, Example 1200 includes AP MLD 1202 and STA MLD (or non-AP MLD) 1204. AP MLD 1202 has two affiliated APs: AP 1202-1 operating in the 5 GHz band and AP 1202-2 operating in the 60 GHz band. STA MLD 1204 has two affiliated STAs (or non-AP STAs): STA1204-1 operating in the 5 GHz band and STA 1204-2 operating in the 60 GHz band.

[0165] In Example 1200, the STA MLD 1204 can perform multi-link (re)configuration (as referenced above). Figure 9 As described, this results in the establishment of a non-EHF link in the 5 GHz band between AP MLD 1202 and STA MLD 1204. Upon completion of the multi-link (re)configuration, STA MLD 1204 becomes associated with AP MLD 1202. Specifically, STA 1204-1, attached to STA MLD 1204, becomes associated with AP 1202-1, attached to AP MLD 1202.

[0166] according to Figure 12 The EHF link setup procedure for STA MLD 1204 allows it to receive beacon (or other) frames from AP MLD 1202 via a non-EHF link, compare the Received Signal Strength Indicator (RSSI) of the beacon frame with a threshold, and determine whether an EHF link can be established with AP MLD 1202 based on the comparison. Specifically, in one implementation, STA MLD 1204 can be configured to determine that it can establish an EHF link with AP MLD 1202 when the RSSI of the beacon frame is greater than the threshold. In another implementation, STA MLD 1204 can be configured to determine that it can not establish an EHF link with AP MLD 1202 when the RSSI of the beacon frame is not greater than the threshold. That is, it can be assumed that STA MLD 1204 can reach AP MLD 1202 via an EHF link when the RSSI of a beacon frame via a non-EHF link is greater than the threshold.

[0167] For example, such as Figure 12As shown, STA MLD 1204 can receive beacon frame 1206 transmitted by AP MLD 1202 via AP 1202-1 through a non-EHF link (5GHz link) via STA 1204-1. STA MLD 1204 can determine the RSSI of beacon frame 1206 and can compare the RSSI of beacon frame 1206 with a threshold. The threshold can be pre-configured or indicated in beacon frame 1206. In Example 1200, it is assumed that the RSSI of beacon frame 1206 is greater than the threshold. Therefore, STA MLD 1204 can determine that it can set up an EHF link (60 GHz link) with AP MLD 1202.

[0168] In Example 1200, based on determining that it can establish an EHF link with AP MLD 1202, STA MLD 1204 may decide to establish an EHF link with AP MLD 1202. In an implementation, STA MLD 1204 may transmit frame 1208 (e.g., via a non-EHF link), which includes a request to add an EHF link with AP MLD 1202. Frame 1208 may include a link reconfiguration request frame as described above. Assuming the conditions for adding an EHF link are met (as described above), AP MLD 1202 may accept STA MLD 1204's request to add an EHF link. In an implementation, AP MLD 1202 may transmit frame 1210, thereby accepting the request to add an EHF link with STA MLD 1204. Frame 1210 may include a link reconfiguration response frame as described above. In an implementation, STA MLD 1204 may acknowledge ( Figure 12 (Not shown) is sent to AP MLD 1202. Upon receiving an acknowledgment, AP MLD 1202 considers the EHF link (60 GHz link) to have been added to the ML settings of STA MLD 1204, and STA 1204-2 becomes associated with AP 1202-2. In the example, AP MLD 1202 can use the EHF link to transmit data frame 1212 to STA MLD 1204, and STA MLD 1204 can acknowledge the data frame by transmitting BA frame 1214 to AP MLD 1202.

[0169] However, in some cases, Figure 12The EHF link setup procedure may unduly restrict the ability of non-AP MLDs to utilize EHF links. For example, due to inaccurate threshold settings and / or environmental changes, adding an EHF link to a non-AP MLD may be unnecessarily prevented (because the RSSI measured on the non-EHF link is not greater than the threshold). This may still occur even though the non-AP MLD can actually reach the AP MLD via the EHF link.

[0170] As further discussed, embodiments of this disclosure address this problem. In one aspect, the STA can be configured to receive a beacon frame from the AP via a first link. The first link can be a non-EHF link. Based on the beacon frame's RSSI being less than or equal to a threshold, the STA can be configured to attempt to detect a second frame transmitted by the AP via a second link. The second link can be an EHF link. Based on the detection of the second frame, the STA can be configured to transmit a third frame to the AP, the third frame including a request to establish (or add) a second link between the STA and the AP. The second frame can be a frame transmitted by the AP via the second link to another STA. Based on the beacon frame's RSSI being greater than a threshold, the STA can be configured to transmit a fourth frame, the fourth frame including a request to establish (or add) a second link between the STA and the AP.

[0171] In another embodiment, the AP may be configured to receive a first frame from the STA via a first link and transmit a second frame indicating the link establishment status of the STA based on the first frame to the STA. The first link may be an EHF link. The link establishment status of the STA may include the establishment status of the first link. The link establishment status of the STA based on the first frame may be based on the RSSI of the first frame at the AP. In one embodiment, the establishment status of the first link indicates that a first link is established between the STA and the AP based on the RSSI of the first frame being greater than a threshold. In another embodiment, the establishment status of the first link indicates that a first link is not established between the STA and the AP based on the RSSI of the first frame being less than or equal to a threshold.

[0172] Figure 13 An example link setup procedure 1300 according to an embodiment is illustrated. The link setup procedure 1300 is provided for illustrative purposes only and does not limit the embodiments of this disclosure. The link setup procedure 1300 can be used by a STA to add an EHF link to a multi-link (ML) setup with an AP. The STA can be a STA MLD (or a non-AP MLD). The STA can be associated with the AP via a first link in the multi-link setup. The first link can be a non-EHF link (e.g., a 2.4, 5, or 6 GHz link). The STA and AP can support operation on a second link. The second link can be an EHF link (e.g., a 60 GHz link).

[0173] like Figure 13As shown, process 1300 begins at step 1302, which includes receiving a first frame from the AP via a first link. The first frame may include a beacon frame or an action frame.

[0174] Next, step 1304 includes determining whether the RSSI of the first frame is greater than a threshold. The threshold may be pre-configured or indicated in the first frame or another frame. The threshold may be based on a carrier sensing threshold associated with the first link. In embodiments, the carrier sensing threshold may be based on the minimum modulation and write-code rate sensitivity of the first link. In example embodiments, the carrier sensing threshold associated with the first link may be equal to -82 dBm, -72 dBm, or -62 dBm. In embodiments, the threshold may be set to be greater than or equal to the carrier sensing threshold associated with the first link.

[0175] If the answer in step 1304 is yes, then process 1300 proceeds to step 1310, which includes transmitting a second frame to the AP. The second frame includes a request to establish or add a second link between the STA and the AP. The second frame may be transmitted via either the first link or the second link.

[0176] In an embodiment, the request to establish a second link between the STA and the AP includes a request to add the second link to the ML setup between the AP and the STA. In an implementation, the second frame may include a link reconfiguration request frame as described above. In an implementation, the second frame may include a reconfiguration multi-link element as described above. The AP may respond to the second frame by transmitting a link reconfiguration response frame as described above.

[0177] In another embodiment, process 1300 may include a multilink setup process performed by the STA, including a second link. Therefore, step 1310 may be part of the multilink setup process. In an embodiment, the second frame may include a basic ML element that includes link information for the second link. In an embodiment, the second frame may be a (re)association request frame. The AP may respond to the second frame by transmitting a (re)association response frame as described above.

[0178] In another embodiment, the AP may respond to the second frame by transmitting a beacon frame indicating the link establishment status of the STA. The link establishment status of the STA may indicate whether a second link is established (or added) between the STA and the AP. In this embodiment, the beacon frame includes information elements that include the link establishment status of the STA.

[0179] In one embodiment, process 1300 may further include mapping a TID to a second link. In another embodiment, the second frame may include a request to map the second link to a TID. In yet another embodiment, the second frame may include a TID-to-link mapping request frame.

[0180] If the answer in step 1304 is no, then process 1300 proceeds to step 1308, which includes determining whether a third frame from the AP has been detected on the second link. The third frame may be transmitted by the AP to the STA or another STA. The third frame may be a data frame or a control frame. In an example implementation, the third frame may be a CTS-to-itself frame.

[0181] In one embodiment, detecting the third frame includes detecting the preamble of the PPDU carrying the third frame. The PPDU may include a BSS color field indicating a BSS color value associated with the AP or a transport address field indicating the address of the AP. In another embodiment, detecting the third frame may further include detecting the uplink / downlink (UL / DL) field of the PPDU, the uplink / downlink field indicating that the PPDU is a DL PPDU.

[0182] In an embodiment, such as Figure 13 As shown, process 1300 may optionally include step 1306 before step 1308. That is, the STA may perform step 1306 before performing step 1308. Step 1306 includes transmitting a frame to the AP via a first link, the frame including a request for the AP to transmit a third frame via a second link. For example, the frame transmitted in step 1306 may include an action frame or a QoS empty frame. The AP may respond to the frame transmitted in step 1306 by transmitting the third frame.

[0183] If the answer in step 1308 is no, then process 1300 returns to step 1302 as described above. Otherwise, process 1300 proceeds to step 1310 as described above.

[0184] Figure 14 It shows Figure 13 Example 1400 of the link setup process is shown. Example 1400 is provided for illustrative purposes only and does not limit the embodiments of this disclosure. Figure 14 As shown, Example 1400 includes AP MLD 1402 and STAMLD (or non-AP MLD) 1404. AP MLD 1402 has two affiliated APs: AP 1402-1 operating in the 5 GHz band and AP 1402-2 operating in the 60 GHz band. STA MLD 1404 has two affiliated STAs (or non-AP STAs): STA 1404-1 operating in the 5 GHz band and STA 1404-2 operating in the 60 GHz band.

[0185] In Example 1400, the STA MLD 1404 can perform multi-link (re)configuration (as referenced above). Figure 9As described, this results in the establishment of a non-EHF link in the 5 GHz band between AP MLD 1402 and STA MLD 1404. Upon completion of the multi-link (re)configuration, STA MLD 1404 becomes associated with AP MLD 1402. Specifically, STA 1404-1, attached to STA MLD 1404, becomes associated with AP 1402-1, attached to AP MLD 1402.

[0186] STA MLD 1404 can be configured to execute Figure 13 The illustrated link setup process establishes or adds an EHF link with AP MLD 1402. Specifically, STA MLD 1404 can be configured to receive beacon (or other) frames from AP MLD 1402 via a non-EHF link, compare the RSSI of the beacon frame with a threshold, and determine the appropriate operation for setting up an EHF link with AP MLD 1402 based on the comparison. Specifically, in an embodiment, when the RSSI of the beacon frame is not greater than the threshold, STA MLD 1404 can be configured to determine that it can set up an EHF link with AP MLD 1402 if a frame from AP MLD 1402 is detected via an EHF link. On the other hand, when the RSSI of the beacon frame is greater than the threshold, STA MLD 1404 can be configured to determine that it can set up an EHF link with AP MLD 1402 without first detecting a frame from AP MLD 1402 via an EHF link.

[0187] For example, such as Figure 14 As shown, STA MLD 1404 can receive beacon frame 1406 transmitted by AP MLD 1402 via AP 1402-1 over a non-EHF link (5GHz link) via STA 1404-1. STA MLD 1404 can determine the RSSI of beacon frame 1406 and compare the RSSI of beacon frame 1406 with a threshold. The threshold can be pre-configured or indicated in beacon frame 1406.

[0188] In Example 1400, for illustrative purposes, it is assumed that the RSSI of beacon frame 1406 is not greater than a threshold. Therefore, STAMLD 1404 can determine that it can set up an EHF link (60 GHz link) with AP MLD 1402 if a frame from AP MLD 1402 is detected via the EHF link.

[0189] Based on the determination that an EHF link with AP MLD 1402 can be established by detecting frames from AP MLD 1402 via the EHF link, STA MLD 1404 may attempt to detect frames from AP MLD 1402 via the EHF link. In one embodiment, detecting frames from the AP includes detecting a preamble carrying the PPDU of the frame. The PPDU may include a BSS color field indicating a BSS color value associated with the AP or a transport address field indicating the address of the AP. In another embodiment, detecting frames from the AP may further include detecting an uplink / downlink (UL / DL) field of the PPDU, the uplink / downlink field indicating that the PPDU is a DL PPDU.

[0190] In Example 1400, assume that AP MLD 1402 transmits frame 1408 via an EHF link after transmitting beacon frame 1406. For example, frame 1408 may be transmitted to another STA. Frame 1408 may be a data frame or a control frame. For illustrative purposes, assume that STA MLD 1404 detects frame 1408.

[0191] Based on the detection of frame 1408 from AP MLD 1402, STA MLD 1404 may transmit frame 1410 (e.g., via a non-EHF link), which includes a request to add an EHF link with AP MLD 1402. Frame 1410 may include a link reconfiguration request frame as described above. In an embodiment, frame 1410 may include an indication that STA MLD 1404 has detected a frame (e.g., frame 1408) transmitted by AP MLD 1402 via an EHF link. Assuming the conditions for adding an EHF link are met (as described above), then AP MLD 1402 may accept STA MLD 1404's request to add an EHF link. In an implementation, AP MLD 1402 may transmit frame 1412, thereby accepting the request to add an EHF link with STA MLD 1404. Frame 1412 may include a link reconfiguration response frame as described above. In an implementation, STA MLD 1404 may acknowledge ( Figure 14 (Not shown in the image) is sent to AP MLD 1402. Upon receiving the acknowledgment, AP MLD 1402 can assume that the EHF link (60GHz link) has been added to the ML settings of STA MLD 1404, and STA 1404-2 becomes associated with AP 1402-2.

[0192] Figure 15 It shows Figure 13 Another example 1500 of the link setup process is shown. Example 1500 is provided for illustrative purposes only and does not limit the embodiments of this disclosure. Figure 15 As shown, Example 1500 includes AP MLD 1502 and STA MLD (or non-AP MLD) 1504. AP MLD 1502 has two auxiliary APs: AP 1502-1 operating in the 5 GHz band and AP 1502-2 operating in the 60 GHz band. STA MLD 1504 has two auxiliary STAs (or non-AP STAs): STA 1504-1 operating in the 5 GHz band and STA 1504-2 operating in the 60 GHz band.

[0193] In Example 1500, the STA MLD 1504 can perform multi-link (re)configuration (as referenced above). Figure 9 As described, this results in the establishment of a non-EHF link in the 5 GHz band between AP MLD 1502 and STA MLD 1504. Upon completion of the multi-link (re)configuration, STA MLD 1504 becomes associated with AP MLD 1502. Specifically, STA 1504-1, attached to STA MLD 1504, becomes associated with AP 1502-1, attached to AP MLD 1502.

[0194] STA MLD 1504 can be configured to execute Figure 13 The illustrated link setup process (including optional step 1306) establishes or adds an EHF link with AP MLD 1502. Specifically, STA MLD 1504 can be configured to receive beacon (or other) frames from AP MLD 1502 via a non-EHF link, compare the RSSI of the beacon frame with a threshold, and determine the appropriate operation for setting up an EHF link with AP MLD 1502 based on the comparison. Specifically, in an embodiment, when the RSSI of the beacon frame is not greater than the threshold, STA MLD 1504 can be configured to determine that it can set up an EHF link with AP MLD 1502 if a frame from AP MLD 1502 is detected via an EHF link. On the other hand, when the RSSI of the beacon frame is greater than the threshold, STA MLD 1504 can be configured to determine that it can set up an EHF link with AP MLD 1502 without first detecting a frame from AP MLD 1502 via an EHF link. In an embodiment, STA MLD 1504 may be further configured to transmit frames to AP MLD 1502 via a non-EHF link, wherein the frame request is transmitted by AP MLD 1502 via an EHF link for detection by STA MLD 1504. In response to a frame from STA MLD 1504, AP MLD 1502 may be configured to transmit a frame via an EHF link for detection by STA MLD 1504.

[0195] For example, such as Figure 15 As shown, STA MLD 1504 can receive beacon frame 1506 transmitted by AP MLD 1502 via AP 1502-1 over a non-EHF link (5GHz link) via STA 1504-1. STA MLD 1504 can determine the RSSI of beacon frame 1506 and compare the RSSI of beacon frame 1506 with a threshold. The threshold can be pre-configured or indicated in beacon frame 1506.

[0196] In Example 1500, for illustrative purposes, it is assumed that the RSSI of beacon frame 1506 is not greater than a threshold. Therefore, STAMLD 1504 can determine that it can set up an EHF link (60 GHz link) with AP MLD 1502 if a frame from AP MLD 1502 is detected via the EHF link.

[0197] Based on the detection of a frame from AP MLD 1502 via an EHF link, and determining that it can establish an EHF link with AP MLD 1502, STA MLD 1504 can transmit frame 1514 to AP MLD 1502. This frame includes a request for AP MLD 1502 to transmit a frame via the EHF link for detection by STA MLD 1504. Frame 1514 can be transmitted via a non-EHF link or an EHF link. For example, frame 1514 can be an action frame or a QoS empty frame.

[0198] Upon receiving frame 1514 from STA MLD 1504, AP MLD 1502 may transmit frame 1508 via the EHF link. For example, frame 1508 may be a beacon frame (e.g., an optical beacon) or a probe response frame.

[0199] For illustrative purposes, it is assumed that STA MLD 1504 detects frame 1508. In one embodiment, detecting a frame from the AP includes detecting a preamble carrying the PPDU of the frame. The PPDU may include a BSS color field indicating a BSS color value associated with the AP or a transport address field indicating the address of the AP. In another embodiment, detecting a frame from the AP may further include detecting an uplink / downlink (UL / DL) field of the PPDU, the uplink / downlink field indicating that the PPDU is a DLPPDU.

[0200] Based on the detection of frame 1508 from AP MLD 1502, STA MLD 1504 may transmit frame 1510 (e.g., via a non-EHF link), which includes a request to add an EHF link with AP MLD 1502. Frame 1510 may include a link reconfiguration request frame as described above. In an embodiment, frame 1510 may include an indication that STA MLD 1504 has detected a frame (e.g., frame 1508) transmitted by AP MLD 1502 via an EHF link. Assuming the conditions for adding an EHF link are met (as described above), AP MLD 1502 may accept STA MLD 1504's request to add an EHF link. In an implementation, AP MLD 1502 may transmit frame 1512, which accepts the request to add an EHF link with STA MLD 1504. Frame 1512 may include a link reconfiguration response frame as described above. In an implementation, STA MLD 1504 may acknowledge ( Figure 15 (Not shown in the image) is sent to AP MLD 1502. Upon receiving the acknowledgment, AP MLD 1502 can assume that the EHF link (60 GHz link) has been added to the ML settings of STA MLD 1504, and STA 1504-2 becomes associated with AP 1502-2.

[0201] Figure 16 Example 1600 of another link setup process according to an embodiment is shown. Example 1600 is provided for illustrative purposes only and does not limit the embodiments of this disclosure. Figure 16 As shown, Example 1600 includes AP MLD 1602 and STAMLD (or non-AP MLD) 1604. AP MLD 1602 has two auxiliary APs: AP 1602-1 operating in the 5 GHz band and AP 1602-2 operating in the 60 GHz band. STA MLD 1604 has two auxiliary STAs (or non-AP STAs): STA 1604-1 operating in the 5 GHz band and STA 1604-2 operating in the 60 GHz band.

[0202] In Example 1600, the STA MLD 1604 can perform multi-link (re)configuration (as referenced above). Figure 9As described, this results in the establishment of a non-EHF link in the 5 GHz band between AP MLD 1602 and STA MLD 1604. Upon completion of the multi-link (re)configuration, STA MLD 1604 becomes associated with AP MLD 1602. Specifically, STA 1604-1, attached to STA MLD 1604, becomes associated with AP 1602-1, attached to AP MLD 1602.

[0203] according to Figure 16 In the link setup process, STA MLD 1604 can be configured to receive beacon (or other) frames from AP MLD 1602 via a non-EHF link, compare the RSSI of the beacon frame with a threshold, and determine the appropriate operation for setting up an EHF link with AP MLD 1602 based on the comparison. Specifically, in an embodiment, when the RSSI of the beacon frame is not greater than the threshold, STA MLD 1604 can be configured to determine that it can set up an EHF link with AP MLD 1602 if a frame from AP MLD 1602 is detected via an EHF link. On the other hand, when the RSSI of the beacon frame is greater than the threshold, STA MLD 1604 can be configured to determine that it can set up an EHF link with AP MLD 1602 without first detecting a frame from AP MLD 1602 via an EHF link. In one embodiment, STA MLD 1604 may be further configured to transmit a frame requesting transmission of a frame from AP MLD 1602 via an EHF link for detection by STA MLD 1604 to AP MLD 1602 via a non-EHF link. In another embodiment, STA MLD 1604 may be configured to attempt to detect a frame transmitted by AP MLD 1602 via an EHF link. Based on the detection of a frame transmitted by AP MLD 1602 via an EHF link, STA MLD 1604 may be configured to transmit a frame requesting the addition of an EHF link to AP MLD 1602. In yet another embodiment, STA MLD 1604 may be further configured to receive a frame from AP MLD 1602 via a non-EHF link in response to a frame requesting transmission of a frame by AP MLD 1602 via an EHF link, thus adding an EHF link to STA MLD 1604. In this embodiment, the STA MLD 1604 can be configured not to transmit frames requesting the addition of an EHF link to the APMLD 1602.

[0204] according to Figure 16During the link setup process, AP MLD 1602 can be configured to transmit beacon (or other) frames via a non-EHF link. The beacon frame may indicate a threshold. AP MLD 1602 can be further configured to receive frames from STA MLD 1604 via a non-EHF link requesting that AP MLD 1602 transmit frames via an EHF link for detection by STA MLD 1604. In an embodiment, AP MLD 1602 can be configured to determine the RSSI of frames received from STA MLD 1604 via a non-EHF link, and determine the establishment status of the EHF link based on the RSSI of frames received from STA MLD 1604 via a non-EHF link. In one embodiment, the establishment status of the EHF link is indicated by a second threshold: if the RSSI of a frame received via a non-EHF link is greater than a second threshold, an EHF link is established between STA MLD 1604 and AP MLD 1602; and if the RSSI of a frame received via a non-EHF link is less than or equal to the second threshold, an EHF link is not established between STA MLD 1604 and AP MLD 1602. The second threshold may be the same as or different from the threshold indicated in the beacon frame. In one embodiment, AP MLD 1602 may be configured to transmit frames (e.g., beacon frames) indicating the establishment status of the EHF link with STA MLD 1604. In another embodiment, AP MLD 1602 may be further configured to transmit frames via an EHF link for detection by STA MLD 1604 based on the RSSI of a frame received from STA MLD 1604 via a non-EHF link being less than or equal to the second threshold.

[0205] For example, such as Figure 16 As shown, STA MLD 1604 can receive beacon frame 1606 transmitted by AP MLD 1602 via AP 1602-1 over a non-EHF link (5GHz link) via STA 1604-1. STA MLD 1604 can determine the RSSI of beacon frame 1606 and compare the RSSI of beacon frame 1606 with a threshold. The threshold can be pre-configured or indicated in beacon frame 1606.

[0206] In Example 1600, for illustrative purposes, it is assumed that the RSSI of beacon frame 1606 is not greater than a threshold. Therefore, STAMLD 1604 can determine that it can set up an EHF link (60 GHz link) with AP MLD 1602 if a frame from AP MLD 1602 is detected via the EHF link.

[0207] Based on the detection of a frame from AP MLD 1602 via an EHF link, and determining that it can establish an EHF link with AP MLD 1602, STA MLD 1604 can transmit frame 1608 to AP MLD 1602. This frame includes a request for AP MLD 1602 to transmit a frame via the EHF link for detection by STA MLD 1604. Frame 1608 can be transmitted via a non-EHF link or an EHF link. For example, frame 1608 can be an action frame or a QoS empty frame.

[0208] Upon receiving frame 1608 from STA MLD 1604, STA MLD 1604 can be configured to determine the RSSI of frame 1608 and, based on the RSSI of frame 1608, determine the establishment status of the EHF link between AP MLD 1602 and STA MLD 1604. Specifically, AP MLD 1602 can determine to establish an EHF link between STA MLD 1604 and AP MLD 1602 based on the RSSI of frame 1608 being greater than a second threshold, and determine not to establish an EHF link between STA MLD 1604 and AP MLD 1602 based on the RSSI of frame 1608 being less than or equal to the second threshold.

[0209] In Example 1600, it is assumed that the RSSI of frame 1608 is greater than a second threshold. Therefore, AP MLD 1602 can determine to establish an EHF link between STA MLD 1604 and AP MLD 1602. AP MLD 1602 can transmit beacon frame 1610, which indicates the establishment status of the EHF link between STA MLD 1604 and AP MLD 1602, and specifically, indicates that STA MLD 1604 is associated with AP MLD 1602 on the EHF link. Upon receiving beacon frame 1610, STA MLD 1604 can determine to add an EHF link with AP MLD 1602. STA MLD 1604 can then begin data communication with AP MLD 1602 using the EHF link.

[0210] In another example (now in) Figure 16 In the example shown above, the RSSI of frame 1608 may not exceed the second threshold. Therefore, in response to frame 1608, AP MLD 1602 can transmit the frame via the EHF link for detection by STA MLD 1604. Based on the detection of the frame via the EHF link, STA MLD 1604 can transmit a frame including a request to add or establish an EHF link, as described above. Figure 15As described in the description. In the implementation, AP MLD 1602 may also transmit beacon frame 1610 before or after transmitting frames via the EHF link. Beacon frame 1610 indicates the establishment status of the EHF link between STA MLD 1604 and AP MLD 1602. Depending on the transmission time of beacon frame 1610, the EHF link may be indicated as established or not established between STA MLD 1604 and AP MLD 1602.

[0211] Figure 17 Example 1700 of another link setup process according to an embodiment is shown. Example 1700 is provided for illustrative purposes only and does not limit the embodiments of this disclosure. Figure 17 As shown, Example 1700 includes AP MLD 1702 and STAMLD (or non-AP MLD) 1704. AP MLD 1702 has two auxiliary APs: AP 1702-1 operating in the 5 GHz band and AP 1702-2 operating in the 60 GHz band. STA MLD 1704 has two auxiliary STAs (or non-AP STAs): STA 1704-1 operating in the 5 GHz band and STA 1704-2 operating in the 60 GHz band.

[0212] In Example 1700, the STA MLD 1704 can perform multi-link (re)configuration (as referenced above). Figure 9 As described, this results in the establishment of a non-EHF link in the 5 GHz band between AP MLD 1702 and STA MLD 1704. Upon completion of the multi-link (re)configuration, STA MLD 1704 becomes associated with AP MLD 1702. Specifically, STA 1704-1, attached to STA MLD 1704, becomes associated with AP 1702-1, attached to AP MLD 1702.

[0213] according to Figure 17In the link setup process, STA MLD 1704 can be configured to receive beacon (or other) frames from AP MLD 1702 via a non-EHF link, compare the RSSI of the beacon frame with a threshold, and determine the appropriate operation to set up an EHF link with AP MLD 1602 based on the comparison. Specifically, in an embodiment, when the RSSI of the beacon frame is not greater than the threshold, STA MLD 1604 can be configured to transmit a first frame to AP MLD 1602 via an EHF link, the first frame including a request to add an EHF link with AP MLD 1702. In response to the first frame, STA MLD 1604 can be configured to receive a second frame from AP MLD 1702 via an EHF link. The second frame can indicate whether the request to add an EHF link is accepted or rejected. On the other hand, when the RSSI of the beacon frame is greater than a threshold, the STA MLD 1604 can be configured to transmit a first frame to the AP MLD 1602 via a non-EHF link. This first frame includes a request to add an EHF link with the AP MLD 1702. In response to the first frame, the STA MLD 1604 can be configured to receive a second frame from the AP MLD 1702 via a non-EHF link. The second frame can indicate whether the request to add an EHF link is accepted or rejected.

[0214] according to Figure 17 During the link setup process, AP MLD 1702 can be configured to transmit beacon (or other) frames via a non-EHF link. The beacon frame may indicate a threshold. AP MLD 1702 can be further configured to receive a first frame from STA MLD 1704 via an EHF link, the first frame including a request to add or establish an EHF link between STA MLD 1704 and AP MLD 1702. In an embodiment, based on detecting and / or decoding the first frame from STA MLD 1704, AP MLD 1702 can be configured to transmit a second frame to STA MLD 1704 via an EHF link, the second frame accepting a request to add or establish an EHF link between STA MLD 1704 and AP MLD 1702.

[0215] For example, such as Figure 17 As shown, STA MLD 1704 can receive beacon frame 1706 transmitted by AP MLD 1702 via AP 1702-1 over a non-EHF link (5GHz link) via STA 1704-1. STA MLD 1704 can determine the RSSI of beacon frame 1706 and compare the RSSI of beacon frame 1706 with a threshold. The threshold can be pre-configured or indicated in beacon frame 1706.

[0216] In Example 1700, for illustrative purposes, it is assumed that the RSSI of beacon frame 1706 is not greater than a threshold. Therefore, STAMLD 1704 can transmit frame 1708 to AP MLD 1702 via an EHF link, the frame including a request to add or establish an EHF link between STAMLD 1704 and APMLD 1702. For example, frame 1708 may include an association request frame. In Example 1700, for illustrative purposes, it is assumed that AP MLD 1702 is capable of detecting and / or decoding frame 1708. Based on the detection and / or decoding of frame 1708, AP MLD 1702 can transmit frame 1710 to STAMLD 1704 via an EHF link, the frame accepting a request to add or establish an EHF link between STAMLD 1704 and AP MLD 1702. When transmitting frame 1710, AP MLD1702 can assume that the EHF link (60 GHz link) has been added to the ML settings of STA MLD 1704, and STA 1704-2 becomes associated with AP 1702-2.

[0217] In another example (not in) Figure 17 As shown in the diagram, AP MLD 1702 may not detect and / or decode frame 1708. Therefore, AP MLD 1702 may not transmit any frames in response to frame 1708. STA MLD 1704 is still not associated with AP MLD 1702 via the EHF link.

[0218] Figure 18 An example process 1800 according to an embodiment is illustrated. Example process 1800 is provided for illustrative purposes only and does not limit the embodiments of this disclosure. Example process 1800 may be executed by an STA, such as STA MLD 1404 or STA MLD 1504. Figure 18 As shown, example process 1800 may include steps 1802 and 1804.

[0219] Step 1802 includes receiving a first frame from the AP and via a first link. For example, the first frame may be a beacon frame or an action frame. The first link may be a non-EHF link. For example, the first link may be a link below 7 GHz (e.g., 2.4 GHz, 5 GHz, or 6 GHz).

[0220] Step 1804 includes transmitting a second frame to the AP based on the following: the Received Signal Strength Indicator (RSSI) of the first frame; and the detection of a third frame from the AP via the second link. The second link may be an EHF link. For example, the second link may be a 60 GHz link.

[0221] In an embodiment, transmitting a second frame based on the RSSI of the first frame includes determining that the RSSI of the first frame is less than a threshold. In an implementation, the threshold is greater than or equal to a carrier sense threshold associated with the first link. For example, the carrier sense threshold is one of -82 dBm, -72 dBm, and -62 dBm. In an implementation, the first frame indicates the threshold.

[0222] In one embodiment, the request to establish a second link between the STA and the AP includes a request to add the second link to the multi-link (ML) setup between the AP and the STA. In another embodiment, the second frame includes a link reconfiguration request frame. In yet another embodiment, the second frame includes a reconfiguration multi-link (ML) element.

[0223] In an embodiment, process 1800 may further include performing a multilink setup process including a second link. In an embodiment, step 1804 may be part of the multilink setup process. In an implementation, the second frame includes a basic multilink (ML) element that includes link information for the second link. In an implementation, the second frame may be a (re)association request frame.

[0224] In one embodiment, process 1800 may further include mapping a Traffic Identifier (TID) to a second link. In another embodiment, the second frame includes a TID-to-link mapping request frame. The TID-to-link mapping request frame may contain a TID-to-link mapping request to map the second link to a TID.

[0225] In one embodiment, detecting the third frame includes detecting a preamble carrying a PPDU (Portable Component Distribution Unit) of the third frame, the PPDU including a BSS color field indicating a BSS color value associated with the AP. In another embodiment, detecting the third frame includes detecting a preamble carrying a PPDU of the third frame, the PPDU including a transport address field indicating the address of the AP. In yet another embodiment, detecting the third frame further includes detecting an uplink / downlink (UL / DL) field of the PPDU, the uplink / downlink field indicating that the PPDU is a DL PPDU.

[0226] In one embodiment, the third frame is transmitted from the AP to another STA. In another embodiment, the third frame includes a CTS-to-itself frame. In another embodiment, the third frame includes a data frame.

[0227] In an embodiment, process 1800 may further include transmitting a fourth frame from the STA to the AP via the first link, the fourth frame including a request to transmit the third frame. The fourth frame may include an action frame or a QoS empty frame.

[0228] In one embodiment, process 1800 may further include the STA receiving a fifth frame from the AP, the fifth frame indicating a response to the second frame. In one embodiment, the fifth frame includes a link reconfiguration response frame. In another embodiment, the fifth frame includes a (re)association response frame. In yet another embodiment, the fifth frame includes a beacon frame indicating the link establishment status of the STA. The beacon frame may include information elements that include the link establishment status of the STA. The link establishment status of the STA may indicate whether a second link is established between the STA and the AP.

[0229] Figure 19 An example process 1900 according to an embodiment is illustrated. Example process 1900 is provided for illustrative purposes only and does not limit the embodiments of this disclosure. Example process 1900 may be executed by an AP, such as AP MLD 1402 or AP MLD 1502. Figure 19 As shown, example process 1900 may include steps 1902 and 1904.

[0230] Step 1902 includes receiving a first frame from the STA, the first frame including an indication detected by the STA of a second frame transmitted by the AP via a first link. The first link may be an EHF link. For example, the first link may be a 60 GHz link.

[0231] In one embodiment, the first frame includes a request to establish a first link between the STA and the AP. In another embodiment, the request to establish the first link between the STA and the AP includes a request to add the first link to a multi-link (ML) configuration between the AP and the STA. In yet another embodiment, the first frame includes a link reconfiguration request frame. In yet another embodiment, the first frame includes a reconfiguration multi-link (ML) element.

[0232] In an embodiment, process 1900 may further include performing a multilink setup process including a first link. In an embodiment, step 1902 may be part of the multilink setup process. In an implementation, the first frame includes a basic multilink (ML) element, which includes link information of the first link. In an implementation, the first frame may be a (re)association request frame.

[0233] In one embodiment, process 1900 may further include mapping a Traffic Identifier (TID) to a first link. In another embodiment, the first frame includes a TID-to-link mapping request frame. The TID-to-link mapping request frame may contain a TID-to-link mapping request to map the first link to a TID.

[0234] In this embodiment, receiving the first frame includes receiving the first frame via a first link or a second link. The second link may be a non-EHF link. For example, the second link may be a link below 7 GHz (e.g., 2.4 GHz, 5 GHz, or 6 GHz).

[0235] In one embodiment, detecting the second frame by the STA includes detecting a preamble carrying a PPDU of the second frame, the PPDU including a BSS color field indicating a BSS color value associated with the AP. In another embodiment, detecting the second frame by the STA includes detecting a preamble carrying a PPDU of the second frame, the PPDU including a transport address field indicating the address of the AP. In yet another embodiment, detecting the second frame by the STA further includes detecting an uplink / downlink (UL / DL) field of the PPDU, the uplink / downlink field indicating that the PPDU is a DL PPDU.

[0236] In one embodiment, the second frame is transmitted from the AP to another STA. In another embodiment, the second frame includes a CTS-to-itself frame. In another embodiment, the second frame includes a data frame.

[0237] In an embodiment, process 1900 may further include the AP receiving a fourth frame from the STA, the fourth frame including a request to transmit the second frame. The fourth frame may include an action frame or a QoS empty frame.

[0238] Step 1904 includes transmitting a third frame to the STA based on the indication, the third frame indicating the establishment of a first link between the STA and the AP. In one embodiment, the third frame includes a link reconfiguration response frame. In another embodiment, the third frame includes a beacon frame indicating the link establishment status of the STA. The beacon frame may include information elements that include the link establishment status of the STA. The link establishment status of the STA may indicate whether a first link is established between the STA and the AP.

[0239] Figure 20 An example process 2000 according to an embodiment is illustrated. Example process 2000 is provided for illustrative purposes only and does not limit the embodiments of this disclosure. Example process 2000 can be executed by an AP, such as AP MLD 1602. Figure 20 As shown, example process 2000 may include steps 2002 and 2004.

[0240] Step 2002 involves receiving a first frame from the STA and via a first link. The first link may be a non-EHF link. For example, the first link may be a link below 7 GHz (e.g., 2.4 GHz, 5 GHz, or 6 GHz). For example, the first frame may be an action frame or a QoS empty frame.

[0241] Step 2004 involves transmitting a second frame, indicating the link establishment status of the STA based on the first frame, to the STA. The link establishment status of the STA may include the establishment status of a second link. The second link may be an EHF link. For example, the second link may be a 60 GHz link. For example, the second frame may be a beacon frame or a probe response frame.

[0242] In one embodiment, the link establishment status of the STA based on the first frame includes the link establishment status of the STA based on the RSSI of the first frame at the AP. In another embodiment, the establishment status of the second link indicates that a second link is established between the STA and the AP based on the RSSI of the first frame being greater than a threshold. In yet another embodiment, the establishment status of the second link indicates that a second link is not established between the STA and the AP based on the RSSI of the first frame being less than or equal to a threshold.

Claims

1. A method comprising: The first station (STA) receives beacon frames from the access point (AP) via the first link. as well as Based on the beacon frame's Received Signal Strength Indicator (RSSI) being less than a threshold: The first STA detects the second frame transmitted from the AP to the second STA via the second link; as well as Based on the detection of the second frame, the first STA transmits a third frame to the AP, the third frame including a request to establish the second link between the first STA and the AP.

2. A method comprising: The STA receives the first frame from the access point AP via the first link; as well as The STA transmits a second frame to the AP based on the following: the second frame includes a request to establish a second link between the STA and the AP: The Received Signal Strength Indicator (RSSI) of the first frame; as well as The third frame from the AP is detected via the second link.

3. The method of claim 2, wherein transmitting the second frame based on the RSSI of the first frame includes determining that the RSSI of the first frame is less than a threshold.

4. The method of claim 3, wherein the threshold is greater than or equal to a carrier sensing threshold associated with the first link.

5. The method of claim 4, wherein the carrier sensing threshold is one of -82 dBm, -72 dBm, and -62 dBm.

6. The method according to any one of claims 3 to 5, wherein the first frame indicates the threshold.

7. The method according to any one of claims 2 to 6, wherein the request to establish the second link between the STA and the AP includes a request to add the second link to a multi-link ML configuration between the AP and the STA.

8. The method according to any one of claims 2 to 7, wherein the second frame includes reconfiguring multi-link ML elements.

9. The method according to any one of claims 2 to 8, wherein the second frame includes a link reconfiguration request frame.

10. The method according to any one of claims 2 to 6, further comprising performing a multi-link setup including the second link.

11. The method according to any one of claims 2 to 6 and 10, wherein the second frame includes a basic multi-link ML element, the basic multi-link element including link information of the second link.

12. The method according to any one of claims 2 to 6, 10 and 11, further comprising mapping a traffic identifier to the second link.

13. The method according to any one of claims 2 to 6 and 10 to 12, wherein the second frame includes a TID to link mapping request frame.

14. The method according to any one of claims 2 to 13, wherein the third frame is transmitted by the AP to another STA.

15. The method of claim 14, wherein the third frame comprises a data frame.

16. The method according to any one of claims 2 to 13, further comprising transmitting a fourth frame from the STA to the AP via the first link, the fourth frame including a request to transmit the third frame.

17. The method of claim 16, wherein the fourth frame comprises an action frame or a Quality of Service (QoS) empty frame.

18. The method according to any one of claims 2 to 17, further comprising the STA receiving a fifth frame from the AP, the fifth frame indicating a response to the second frame.

19. The method of claim 18, wherein the fifth frame includes a link reconfiguration response frame.

20. The method of claim 18, wherein the fifth frame includes a beacon frame indicating the link establishment status of the STA.

21. The method of claim 20, wherein the beacon frame includes an information element, the information element including the link establishment status of the STA.

22. The method according to any one of claims 20 to 21, wherein the link establishment status of the STA indicates whether a second link is established between the STA and the AP.

23. The method according to any one of claims 2 to 22, wherein detecting the third frame includes detecting a preamble of a Physical Layer Protocol Data Unit (PPDU) carrying the third frame, the PPDU including a Basic Service Set (BSS) color field indicating a BSS color value associated with the AP.

24. The method of claim 23, wherein detecting the third frame further comprises detecting the uplink / downlink UL / DL field of the PPDU, the uplink / downlink field indicating that the PPDU is a DL PPDU.

25. The method according to any one of claims 2 to 22, wherein detecting the third frame includes detecting a preamble of a Physical Layer Protocol Data Unit (PPDU) carrying the third frame, the PPDU including a transport address field indicating the address of the AP.

26. The method according to any one of claims 2 to 25, wherein the third frame comprises a CTS-to-itself frame.

27. The method according to any one of claims 2 to 26, wherein the first frame comprises a beacon frame or an action frame.

28. The method according to any one of claims 2 to 27, wherein the first link comprises a link below 7 GHz.

29. The method according to any one of claims 2 to 28, wherein the second link comprises a 60 GHz link.

30. A method comprising: The station STA receives a first frame from the access point AP via a first link, wherein the received signal strength indicator (RSSI) of the first frame is less than a threshold. The second frame is transmitted from the STA to the AP via the second link, the second frame including a request to establish the second link between the STA and the AP; as well as The STA receives a third frame from the AP, the third frame indicating a response to the second frame.

31. A method comprising: The first frame is transmitted from the access point (AP) to the first station (STA) via the first link; The AP receives a second frame from the second STA, the second frame including: The indication of the first frame is detected by the second STA; and The request to establish the first link between the second STA and the AP; and The AP transmits a third frame to the second STA based on the instruction, the third frame indicating the establishment of the first link between the second STA and the AP.

32. A method comprising: The access point (AP) receives a first frame from a slave station (STA), the first frame including an indication detected by the STA of a second frame transmitted by the AP via a first link; as well as The AP transmits a third frame to the STA based on the instruction, the third frame indicating the establishment of the first link between the STA and the AP.

33. The method of claim 32, wherein the first frame includes a request to establish the first link between the STA and the AP.

34. The method of claim 33, wherein the request to establish the first link between the STA and the AP includes a request to add the first link to a multi-link ML configuration between the AP and the STA.

35. The method of any one of claims 32 to 34, wherein the first frame includes reconfiguring multi-link ML elements.

36. The method of claim 33, wherein the first frame includes a link reconfiguration request frame.

37. The method of claim 36, further comprising performing a multi-link setup including the first link.

38. The method according to any one of claims 36 to 37, wherein the first frame includes a basic multi-link ML element, the basic multi-link element including link information of the first link.

39. The method according to any one of claims 36 to 38, further comprising mapping a traffic identifier to the first link.

40. The method of any one of claims 36 to 39, wherein the first frame includes a TID-to-link mapping request frame.

41. The method of any one of claims 32 to 40, wherein receiving the first frame includes receiving the first frame via the first link or the second link.

42. The method according to any one of claims 32 to 41, wherein transmitting the third frame includes transmitting the third frame via the first link or the second link.

43. The method according to any one of claims 32 to 42, wherein the second frame is transmitted by the AP to the second STA.

44. The method of claim 43, wherein the second frame comprises a data frame.

45. The method according to any one of claims 32 to 44, further comprising the AP receiving a fourth frame from the STA, the fourth frame including a request to transmit the second frame.

46. ​​The method of claim 45, wherein the fourth frame comprises an action frame or a Quality of Service (QoS) empty frame.

47. The method of any one of claims 32 to 46, wherein the third frame includes a link reconfiguration response frame.

48. The method according to any one of claims 32 to 46, wherein the third frame includes a beacon frame indicating the link establishment status of the STA.

49. The method of claim 48, wherein the beacon frame includes an information element, the information element including the link establishment status of the STA.

50. The method according to any one of claims 48 to 49, wherein the link establishment status of the STA indicates whether the first link is established between the STA and the AP.

51. The method of any one of claims 32 to 50, wherein detecting the second frame by the STA includes detecting a preamble of a Physical Layer Protocol Data Unit (PPDU) carrying the second frame, the PPDU including a Basic Service Set (BSS) color field indicating a BSS color value associated with the AP.

52. The method of claim 51, wherein detecting the second frame by the STA further comprises detecting the uplink / downlink UL / DL field of the PPDU, the uplink / downlink field indicating that the PPDU is a DLPPDU.

53. The method according to any one of claims 32 to 50, wherein detecting the second frame by the STA includes detecting a preamble of a Physical Layer Protocol Data Unit (PPDU) carrying the second frame, the PPDU including a transport address field indicating the address of the AP.

54. The method according to any one of claims 32 to 53, wherein the third frame comprises a CTS-to-itself frame.

55. The method according to any one of claims 41 to 42, wherein the first link comprises a 60 GHz link.

56. The method according to any one of claims 41 to 42 or 55, wherein the second link comprises a link below 7 GHz.

57. A method comprising: The first frame is received by the access point AP slave station STA via the first link; as well as The AP transmits a second frame to the STA indicating the link establishment status based on the first frame, wherein the link establishment status of the STA includes the establishment status of a second link.

58. The method of claim 57, wherein the link establishment state of the STA is based on the Received Signal Strength Indicator (RSSI) of the first frame at the AP.

59. The method of claim 58, wherein the establishment status of the second link indicates the establishment of the second link between the STA and the AP based on the RSSI of the first frame being greater than a threshold.

60. The method of claim 58, wherein the establishment status of the second link indicates that the second link is not established between the STA and the AP based on the RSSI of the first frame being less than or equal to a threshold.

61. An apparatus comprising: One or more processors; as well as A memory that stores instructions, which, when executed by the one or more processors, cause the device to perform the method according to any one of claims 1 to 60.

62. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1 to 60.

Images