Secure access point association

Abstract

A station (STA) receives a first frame from an access point (AP) via a first link, the first frame indicating a second link via which an association procedure with the AP is allowed to be performed. The STA transmits an association request to the AP via the second link.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Provisional Application No. 63 / 530,083, filed August 1, 2023, and U.S. Provisional Application No. 63 / 564,543, filed March 13, 2024, both of which are incorporated herein by reference in their entirety. 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 showing an example implementation of a station (STA) and 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 of a transmission is shown, including buffer status reporting performed by the STA, scheduling performed by the AP for uplink multi-user (MU) transmissions, and scheduled uplink transmissions performed 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 The associated procedure according to the IEEE 802.11 standard is shown.

[0014] Figure 12An example WLAN communication scenario is shown.

[0015] Figure 13 This is an example illustrating the associated procedure according to an embodiment.

[0016] Figure 14 This is an example of an association procedure according to another embodiment.

[0017] Figure 15 This is an example of an association procedure according to another embodiment.

[0018] Figure 16 This is an example of an association procedure according to another embodiment.

[0019] Figure 17 Example operational elements that can be used in the embodiments are 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. Detailed Implementation

[0022] 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 can be made therein without departing from the scope. Alternative embodiments will become apparent to those skilled in the art upon reading this specification. Embodiments of the invention are not 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 exemplary embodiments can be combined to create further 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, actions listed in any flowchart can be reordered or optionally used only in certain embodiments.

[0023] 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, combinations thereof, etc. Example standards may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, combinations thereof, etc. Various example embodiments can be applied when one or more criteria are met. Therefore, it is possible to implement example embodiments that selectively implement the disclosed protocols.

[0024] In this disclosure, “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 “comprising” and “consisting of” enumerate one or more components of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude the inclusion of unlisted components in the element being described. In contrast, “consisting of” provides a complete enumeration of 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.

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

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

[0027] 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 the 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.

[0028] By using the word "may" or parentheses, many of the presented features are described as optional. 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.

[0029] Many of the 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 the defined interface 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 may be 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 frequently programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure connections between relatively few internal hardware modules on a programmable device. The techniques mentioned are often used in combination to achieve the result of functional modules.

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

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

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

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

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

[0035] Figure 1 The example wireless communication network shown may also include one or more self-organizing networks or independent BSSs (IBSSs). A self-organizing network or IBSS is a network of multiple STAs contained 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).

[0036] 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 contain an AP, it does not contain a centralized management entity. Instead, the STAs within an IBSS are managed in a distributed manner. The STAs forming an IBSS can be fixed or mobile.

[0037] A STA, serving as the intended 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.

[0038] A Physical Layer (PHY) Protocol Data Unit (PPDU) can be a composite structure containing a PHY preamble and a payload in the form of a PLCP Service Data Unit (PSDU). For example, a PSDU may contain 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 can contain both a traditional part (or "traditional preamble") and a non-traditional part (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 part of the preamble are based on the specific IEEE 802.11 protocol to be used for transmitting the payload.

[0039] A frequency band can contain one or more sub-bands or frequency channels. For example, PPDUs conforming to the IEEE 802.11n, 802.11ac, 802.11ax, 802.11be, and / or 802.11ad and 802.11ay standards can be transmitted on the 2.4 GHz, 5 GHz, 6 GHz, and / or 60 GHz bands. PPDUs can also be transmitted on physical channels.

[0040] Figure 2 This is a block diagram illustrating example implementations of the STA 210 and AP 260. (As shown...) Figure 2 As 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.

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

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

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

[0044] Figure 3 An 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 in the frame and can interpret certain fields based on the MAC header of all frames.

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

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

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

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

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

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

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

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

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

[0054] 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 from 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.

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

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

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

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

[0059] The sequence control field contains 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 unfragmented MSDUs or MMPDUs, the fragment number is set to 0. The fragment number remains constant throughout all retransmissions of the fragment.

[0060] The QoS control field identifies the Traffic Class (TC) or Traffic Stream (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 transmitting STA. The QoS control field exists in all data frames where the QoS subfield of the subtype subfield is equal to 1.

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

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

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

[0064] 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 contains a QoS control field and an optional HT control field, which may include a Buffer Status Report (BSR) control subfield. A QoS empty frame indicating buffer status information can be transmitted from a STA to an AP.

[0065] The QoS control field 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).

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

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

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

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

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

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

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

[0073] Queue size value QS It 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.

[0074] The queue size subfield contains 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 .

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

[0076] The requested TXOP duration subfield, which can 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.

[0077] The HT control field may contain 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 Category 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.

[0078] 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 of 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 includes all 8 TIDs.

[0079] The values ​​of the incremental TID subfield and the ACI bitmap subfield indicate the number of TIDs that the STA is reporting in the buffer state.

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

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

[0082] 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 by the STA identified by the receive address of a frame containing the BSR control subfield.

[0083] 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 by the STA identified by the receive address of a frame containing the BSR control subfield.

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

[0085] 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 for QoS data frames containing fragments can remain constant even if the amount of queue traffic changes as consecutive fragments are transmitted.

[0086] 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 transfer MSDUs to the peer MAC entity. This type of asynchronous MSDU transfer is performed on a connectionless basis.

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

[0088] A PSDU can contain one or more MPDUs, such as QoS data frames, MMPDUs, MAC control frames, or QoS empty frames. When an MPDU carries a QoS data frame, the frame body of the MPDU can contain an MSDU or an A-MSDU.

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

[0090] The STA can differentiate MSDU delivery based on the specified Traffic Category (TC) or Traffic 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.

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

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

[0093] 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, incremental TID, high-priority AC, and two queue sizes.

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

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

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

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

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

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

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

[0101] STA 1 and / or STA 2 may each contain 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.

[0102] 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 containing multiple QoS empty frames. Each QoS empty frame indicates the queue size for its respective TID (e.g., TID 0 and TID 2) in its corresponding QoS control field. Similarly, STA 2 can respond to a BSRP trigger frame by transmitting an MPDU containing QoS empty frames, which indicate the queue size for TID 2 in their QoS control field.

[0103] 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. If the AP has indicated that it supports receiving the BSR control subfield, then the STA has the 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.

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

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

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

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

[0108] like Figure 7 As shown, an MLD can have a single MAC service access point (MAC-SAP) to the LLC layer, containing 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.

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

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

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

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

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

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

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

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

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

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

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

[0120] 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 / 6 GHz band, and AP 3 operating in the 60 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 / 6 GHz band, and non-AP STA 3 operating in the 60 GHz band.

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

[0122] AP MLD can respond to a requested multilink setup by sending an association response frame to a non-AP STA 1 attached to a 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 non-AP STA 1. The association response frame contains 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 configuring 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).

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

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

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

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

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

[0128] 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 a BU buffered at the AP MLD for a separately addressed MSDU or A-MSDU corresponding to the TID 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 a separately addressed MSDU or A-MSDU corresponding to the TID, depending on the power state of the non-AP STA on each used link.

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

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

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

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

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

[0134] 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 indeed include the TID-to-link mapping element in its (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 in its (re)association response frame that suggests a preferred TID-to-link mapping.

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

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

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

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

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

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

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

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

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

[0144] Figure 11 Example 1100 illustrates the associated procedure according to the IEEE 802.11 standard. (As shown...) Figure 11 As shown, Example 1100 includes AP MLD 1102 and non-AP MLD 1104. AP MLD 1102 and non-AP MLD can each operate on multiple links (e.g., link 1 and link 2).

[0145] Example 1100 may begin with AP MLD 1102 transmitting a beacon frame 1106 via Link 1. Beacon frame 1106 announces the presence of AP MLD 1102 and contains the information needed for a non-AP MLD to associate with AP MLD 1102. In this example, non-AP MLD 1104 may transmit a probe request frame 1108 via Link 1 to discover nearby IEEE 802.11 networks. Probe request frame 1108 may indicate the supported data rates and 802.11 capabilities of non-AP MLD 1104. Upon receiving probe request frame 1108, AP MLD 1102 may check to determine if AP MLD 1102 has at least one data rate commonly supported by non-AP MLD 1104. If a common data rate exists, then AP MLD 1102 may transmit a probe response frame 1110 via Link 1, advertising the SSID, supported data rates, encryption type (if required), and other 802.11 capabilities of AP MLD 1102. Upon receiving a probe response frame 1110, non-AP MLD 1104 checks its compatibility with AP MLD 1102. If compatible, it attempts to authenticate with AP MLD 1102 by sending an authentication request frame 1112 via link 1. AP MLD 1102 can then respond to non-AP MLD 1104 via link 1 with an authentication response frame 1114 for non-AP MLD 1104 to initiate association. Subsequently, non-AP MLD 1104 transmits an association request frame 1116 to AP MLD 1102 via link 1. The association request frame 1116 contains the selected encryption type and other compatible IEEE 802.11 capabilities. If the elements of the association request frame 1116 match the capabilities of AP MLD 1102, then AP MLD 1102 creates an association ID for non-AP MLD 1104 and responds to non-AP MLD 1104 via Link 1 with an association response frame 1118. The association response frame 1118 contains a success message authorizing network access for non-AP MLD 1104.

[0146] like Figure 11 As shown, once initiated via Link 1, the entire association process proceeds via Link 1 until non-AP MLD 1104 is associated with AP MLD 1102. AP MLD 1102 and non-AP MLD 1104 do not use Link 2 to complete the association process.

[0147] Figure 12An example WLAN communication scenario is illustrated, including AP MLD 1202, non-AP MLD 1204, and non-AP MLD 1206. AP MLD 1202 can be located within geographic area 1212. For example, geographic area 1212 can be a walled structure, such as a room, office, apartment, or building. Non-AP MLD 1204 can also be located within geographic area 1212, while non-AP MLD 1206 can be located outside geographic area 1212.

[0148] In this example, the AP MLD 1202 can support multiple links. These multiple links can include a first link and a second link. In this example, the first link can be a 2.4 GHz link or a 5 / 6 GHz link. Using the first link, the AP MLD 1202 can have a communication range of 1210, such as... Figure 12 As shown in the diagram. Specifically, using the first link, the signal transmitted by AP MLD 1202 can propagate outside geographical area 1212 and is not blocked by physical barriers (e.g., walls) of geographical area 1212. Therefore, both non-AP MLD 1204 and non-AP MLD 1206 can communicate with AP MLD 1202 via the first link.

[0149] In the example, the second link could be a 60 GHz link or an infrared / visible light frequency link. Using the second link, the APMLD 1202 can have a communication range of 1208, such as... Figure 12 As shown in the diagram. Specifically, using the second link, the signal transmitted by AP MLD 1202 cannot propagate outside geographic area 1212 because the signal may be blocked by physical barriers (e.g., walls) of geographic area 1212. Therefore, only non-AP MLD 1204 can communicate with AP MLD 1202 via the second link.

[0150] In this example, AP MLD 1202 may support a private BSS. Access to the private BSS may be limited to authorized users. Authorized users can be those located only within geographic area 1212. Since non-AP MLD 1206 can be located outside geographic area 1212, non-AP MLD 1206 can be an unauthorized user. However, since non-AP MLD 1206 can hear signals transmitted by AP MLD 1202 via the first link, non-AP MLD 1206 can attempt to associate with AP MLD 1202. For example, non-AP MLD 1206 can hear beacon frames transmitted by AP MLD 1202 via the first link and can transmit association request frames to AP MLD 1202 via the first link.

[0151] Typically, before sending an association request frame to the AP MLD 1202, the non-AP MLD 1206 must perform an authentication procedure with the AP MLD 1202 (as described above). Figure 11 (As described in [the original text]). However, the fact that a non-AP MLD 1206 is an unauthorized user may not prevent it from successfully authenticating, because the existing authentication process does not perform authorization checks. Therefore, a non-AP MLD 1206 may be able to associate with an AP MLD 1202. This association may pose a security risk to the private BSS supported by the AP MLD 1202. For example, as an unauthorized user, a non-AP MLD 1206 could be a malicious user, such as an eavesdropper or hacker.

[0152] As further described below, embodiments of this disclosure address the aforementioned problems that may occur in existing IEEE 802.11 networks. In one aspect, the AP can transmit a first frame to the STA via a first link, the first frame indicating permission for an association procedure with the AP to be performed via a second link. The AP can receive an association request from the STA via the second link and can transmit an association response to the STA via the second link. In embodiments, the second link may correspond to a 60 GHz link. Therefore, association with the AP can be limited to STAs located within a specific geographical area, thereby increasing network security.

[0153] Figure 13 Example 1300 of the associated procedure according to an embodiment is shown. Figure 13 As shown, Example 1300 includes AP 1302 and STA 1304. AP 1302 and / or STA 1304 may include MLDs. Therefore, AP 1302 and / or STA 1304 can operate on multiple links (e.g., a first link, a second link). The first link may correspond to a 2.4 GHz or 5 / 6 GHz link. The second link may correspond to a 60 GHz link. At the beginning of Example 1300, STA 1304 may be unassociated with another AP or associated with it, and may be desirable to associate it with AP 1302.

[0154] like Figure 13 As shown, Example 1300 may begin with AP 1302 transmitting frame 1306 via a first link. Frame 1306 may be a beacon frame or a probe response frame.

[0155] In an embodiment, frame 1306 may indicate links on which association procedures with AP 1302 are permitted to be executed. In an embodiment, the multiple links on which AP 1302 operates may be divided between links on which the STA can execute association procedures with AP 1302 and links on which the STA cannot execute association procedures with AP 1302. In an implementation, when the STA attempts to execute an association procedure via a link on which association procedures are not permitted to be executed, the STA may not receive a response (e.g., an association response frame) from AP 1302.

[0156] In Example 1300, the first link may be a link on which the associated procedures with AP 1302 are not permitted to be executed, and the second link may be a link on which the associated procedures with AP 1302 are permitted to be executed. Therefore, in Example 1300, frame 1306 may indicate the second link as a link on which the associated procedures with AP 1302 are permitted to be executed.

[0157] In one embodiment, the second link may be part of a set of dedicated links used to perform association procedures with AP 1302. That is, only links from the set of dedicated links can be used to perform association procedures with AP 1302. In one embodiment, the set of dedicated links includes only the second link. In an embodiment where the second link corresponds to a 60 GHz link and the AP is located within a wall structure, association with the AP can be limited to STAs located within the wall structure. This can improve network security as described above. In another embodiment, the set of dedicated links includes a first link and a second link. In yet another embodiment, the set of dedicated links includes a second link and a third link (…). Figure 13 (Not shown in the text).

[0158] In an embodiment, frame 1306 includes a link identifier field. The link identifier field may indicate one or more links that allow the execution of associated procedures with AP 1302 via them. In example 1300, the link identifier field may include an identifier of a second link. In another example, the link identifier field may further include an identifier of a first link.

[0159] In another embodiment, in addition to or alternatively to a link identifier, frame 1306 may include an association flag indicating whether association procedures with AP 1302 are permitted via a first link. In another embodiment, an association flag indicating that association procedures with AP 1302 are not permitted via the first link indicates that association procedures with AP 1302 are permitted via a second link. For example, when the association flag indicates that association procedures with AP 1302 are not permitted via the first link, the second link may be the default link for association. In another embodiment, when the association flag indicates that association procedures with AP 1302 are not permitted via the first link, the default link for association may be a third link (…). Figure 13 (Not shown in the text).

[0160] In Example 1300, a link identifier and / or association flag can indicate a second link as a link that allows association procedures with AP 1302 to be performed via it. Therefore, STA 1304 can initiate an association procedure with AP 1302 via a second link by transmitting an association request frame 1308 to AP 1302 via the second link. AP 1302 can respond to association request frame 1308 by transmitting an association response frame 1310 to STA 1304. In another embodiment, the association procedure may further include STA 1304 transmitting an authentication request frame to AP 1302 before transmitting association request frame 1308, and AP 1302 responding to STA 1304 with an authentication response frame.

[0161] Subsequently, in the example, AP 1302 can transmit the corresponding data frames 1312 and 1314 to STA 1304 via the first and second links. For example... Figure 13 As shown, data frames 1312 and 1314 can overlap in time.

[0162] In another embodiment, frame 1306 may further include a beacon flag. The beacon flag indicates whether a STA wishing to associate with AP 1302 via the link must wait for a beacon frame (or probe response frame) on the link before initiating an association procedure with AP 1302. For example, in example 1300, if the link identifier and / or association flag in frame 1306 indicates a second link as a link through which association procedures with AP 1302 are permitted, then the beacon flag may indicate whether the STA must wait for a beacon frame (or probe response frame) from AP 1302 on the second link before initiating an association procedure with AP 1302.

[0163] In Example 1300, the beacon flag can be set to 0 in frame 1306. Therefore, as... Figure 13As shown and described above, STA 1304 can initiate an association procedure with AP 1302 via the second link without waiting for a beacon frame (or probe response frame) from AP 1302 via the second link. Conversely, as... Figure 14 As shown in Example 1400, when the beacon flag is set to 1 in frame 1306, STA 1304 can wait to hear beacon frame 1402 (or probe response frame) from AP 1302 via the second link before initiating an association procedure with AP 1302.

[0164] Figure 15 Example 1500 of an association procedure according to another embodiment is shown. Figure 15 As shown, Example 1500 includes AP 1502 and STA 1504. AP 1502 and / or STA 1504 may include MLDs. Therefore, AP 1502 and / or STA 1504 can operate on multiple links (e.g., a first link, a second link). The first link may correspond to a 2.4 GHz or 5 / 6 GHz link. The second link may correspond to a 60 GHz link. At the beginning of Example 1500, STA 1504 may be unassociated with another AP or associated with it, and may be desirable to associate it with AP 1502.

[0165] like Figure 15 As shown, Example 1500 can begin with AP 1502 transmitting frame 1506 via a first link. Frame 1506 can be a beacon frame or a probe response frame.

[0166] In an embodiment, frame 1506 may indicate links on which association procedures with AP 1502 are permitted to be executed. In an embodiment, the multiple links on which AP 1502 operates may be divided between links on which the STA can execute association procedures with AP 1502 and links on which the STA cannot execute association procedures with AP 1502. In an implementation, when the STA attempts to execute an association procedure via a link on which association procedures are not permitted to be executed, the STA may not receive a response (e.g., an association response frame) from AP 1502.

[0167] In Example 1500, the first link may be a link on which association procedures with AP 1502 are permitted to be executed, and the second link may be a link on which association procedures with AP 1502 are not permitted to be executed. Therefore, in Example 1500, frame 1506 may indicate the first link as a link on which association procedures with AP 1502 are permitted to be executed.

[0168] In one embodiment, the first link may be part of a set of dedicated links for performing association procedures with AP 1502. That is, the association procedures with AP 1502 may be performed using only one link from the set of dedicated links. In one embodiment, the set of dedicated links includes only the first link. In another embodiment, the set of dedicated links includes both the first and second links. In yet another embodiment, the set of dedicated links includes both the second and third links. Figure 15 (Not shown in the text).

[0169] In an embodiment, frame 1506 includes a link identifier field. The link identifier field may indicate one or more links that allow the execution of associated procedures with AP 1502 via them. In example 1500, the link identifier field may include an identifier of a first link. In another example, the link identifier field may further include an identifier of a second link.

[0170] In another embodiment, in addition to or alternatively to a link identifier, frame 1506 may include an association flag indicating whether association procedures with AP 1502 are permitted via a first link. In another embodiment, an association flag indicating that association procedures with AP 1502 are not permitted via the first link indicates that association procedures with AP 1502 are permitted via a second link. For example, when the association flag indicates that association procedures with AP 1502 are not permitted via the first link, the second link may be the default link for association. In another embodiment, when the association flag indicates that association procedures with AP 1502 are not permitted via the first link, the default link for association may be a third link (…). Figure 15 (Not shown in the text).

[0171] In Example 1500, the link identifier and / or association flag can indicate the first link as a link that allows the execution of association procedures with AP 1502 via it.

[0172] In an embodiment, frame 1506 may include a token flag indicating the presence or absence of an association token. The association token may be included in a frame transmitted by AP 1502 via a first link, a second link, or a third link.

[0173] In an embodiment, frame 1506 may further include a token link identifier field. The token link identifier field may indicate one or more links through which frames containing associated tokens are transmitted.

[0174] In Example 1500, frame 1506 contains a token flag set to 1, indicating the presence of an associated token. Frame 1506 further includes a token link identifier field, which includes an identifier for the second link. Therefore, AP 1502 can transmit frame 1508 containing the associated token via the second link. Frame 1508 can be a beacon frame or a probe response frame.

[0175] In the example, STA 1504 can receive frame 1508 and retrieve the association token from frame 1508. STA 1504 can then initiate an association procedure with AP 1502 via the first link by transmitting an association request frame 1510, including the association token, to AP 1502 via the first link. AP 1502 can respond to association request frame 1510 by transmitting an association response frame 1512 to STA 1504. In another embodiment, the association procedure may further include STA 1504 transmitting an authentication request frame to AP 1502 before transmitting association request frame 1510, and AP 1502 responding to STA 1504 with an authentication response frame.

[0176] Subsequently, in the example, AP 1502 can transmit the corresponding data frames 1514 and 1516 to STA 1504 via the first and second links. For example... Figure 15 As shown, data frames 1514 and 1516 can overlap in time.

[0177] Figure 16 Example 1600 illustrates another associated procedure according to an embodiment. For example... Figure 16 As shown, Example 1600 includes AP 1602 and STA 1604. AP 1602 and / or STA 1604 may include MLDs. Therefore, AP 1602 and / or STA 1604 may be able to operate on multiple links (e.g., a first link, a second link). The first link may correspond to a 2.4 GHz or 5 / 6 GHz link. The second link may correspond to a 60 GHz link. At the beginning of Example 1600, STA 1604 may be unassociated with another AP or associated with it, and may be desirable to associate it with AP 1602.

[0178] like Figure 16 As shown, Example 1600 may begin with AP 1602 transmitting frame 1606 via a first link. Frame 1606 may be a beacon frame or a probe response frame.

[0179] In an embodiment, frame 1606 may indicate links on which association procedures with AP 1602 are permitted to be executed. In an embodiment, the multiple links on which AP 1602 operates may be divided between links on which the STA can execute association procedures with AP 1602 and links on which the STA cannot execute association procedures with AP 1602. In an implementation, when the STA attempts to execute an association procedure via a link on which association procedures are not permitted, the STA may not receive a response (e.g., an association response frame) from AP 1602.

[0180] In Example 1600, the first link may be a link on which association procedures with AP 1602 are permitted to be executed, and the second link may be a link on which association procedures with AP 1602 are not permitted to be executed. Therefore, in Example 1600, frame 1606 may indicate the first link as a link on which association procedures with AP 1602 are permitted to be executed.

[0181] In one embodiment, the first link may be part of a set of dedicated links for performing association procedures with AP 1602. That is, only links from the set of dedicated links can be used to perform association procedures with AP 1602. In one embodiment, the set of dedicated links includes only the first link. In another embodiment, the set of dedicated links includes both the first and second links. In yet another embodiment, the set of dedicated links includes both the second and third links. Figure 16 (Not shown in the text).

[0182] In an embodiment, frame 1606 includes a link identifier field. The link identifier field may indicate one or more links that allow the execution of associated procedures with AP 1602 via them. In example 1600, the link identifier field may include an identifier of a first link. In another example, the link identifier field may further include an identifier of a second link.

[0183] In another embodiment, in addition to or alternatively to a link identifier, frame 1606 may include an association flag indicating whether association procedures with AP 1602 are permitted via a first link. In another embodiment, an association flag indicating that association procedures with AP 1602 are not permitted via the first link indicates that association procedures with AP 1602 are permitted via a second link. For example, when the association flag indicates that association procedures with AP 1602 are not permitted via the first link, the second link may be the default link for association. In another embodiment, when the association flag indicates that association procedures with AP 1602 are not permitted via the first link, the default link for association may be a third link (…). Figure 16 (Not shown in the text).

[0184] In Example 1600, the link identifier and / or association flag can indicate the first link as a link that allows the execution of association procedures with AP 1602 via it.

[0185] In an embodiment, frame 1606 may include a token flag indicating the presence or absence of an association token. The association token may be included in a frame transmitted by AP 1602 via a first link, a second link, or a third link.

[0186] In an embodiment, frame 1606 may further include a token link identifier field. The token link identifier field may indicate one or more links through which frames containing associated tokens are transmitted.

[0187] In an embodiment, frame 1606 may further indicate whether STA 1604 needs to transmit a probe request to AP 1602 to obtain an association token from AP 1602. In an embodiment, frame 1606 may include a probe request flag for this indication.

[0188] In Example 1600, frame 1606 contains a token flag set to 1, indicating the presence of an associated token. Frame 1606 further includes a token link identifier field, which includes an identifier for the second link and a probe request flag set to 1.

[0189] Therefore, after receiving frame 1606, STA 1604 can initiate an association procedure with AP 1602 via the first link by transmitting a probe request frame 1608 via the second link (indicated by the token link identifier in frame 1606). AP 1602 responds to probe request frame 1608 with a probe response frame 1610 including the association token. Upon receiving probe response frame 1610, STA 1604 retrieves the association token and transmits an association request frame 1612 containing the association token via the second link (indicated as the association link in frame 1606). AP 1602 can respond to association request frame 1612 by transmitting association response frame 1614 to STA 1604. In another embodiment, the association procedure may further include STA 1604 transmitting an authentication request frame to AP 1602 before transmitting association request frame 1612, and AP 1602 responding to STA 1604 with an authentication response frame.

[0190] In another embodiment, frame 1606 may indicate whether STA 1604 needs to transmit a request to AP 1602 to obtain an association token from AP 1602. In this embodiment, frame 1606 may include a request flag for this indication ( Figure 16(Not shown in the image). In one embodiment, STA 1604 may transmit a frame requesting an association token via a second link upon receiving frame 1606 with the request flag set to 1. In another embodiment, AP 1602 responds to the frame requesting the association token with a response frame including the association token. Upon receiving the response frame, STA 1604 retrieves the association token and transmits an association request frame 1612 containing the association token via the second link (indicated as the association link in frame 1606). AP 1602 may respond to the association request frame 1612 by transmitting an association response frame 1614 to STA 1604. In another embodiment, the association procedure may further include STA 1604 transmitting an authentication request frame to AP 1602 before transmitting the association request frame 1612, and AP 1602 responding to STA 1604 with an authentication response frame.

[0191] Subsequently, in the example, AP 1602 can transmit the corresponding data frames 1616 and 1618 to STA 1604 via the first and second links. For example... Figure 16 As shown, data frames 1616 and 1618 can overlap in time.

[0192] Figure 17 Example operation elements that can be used in the embodiments are shown. As shown, the example operation element may include an element ID field, a length field, an element ID extension, a UHR operation parameter field, a security association parameter field 1702, and other fields.

[0193] The element ID field and (if present) the element ID extended field identify the element being operated on.

[0194] The length field indicates the number of octets in the element, excluding the element ID and the length field.

[0195] The UHR operation parameter field provides operation information based on a specific PHY layer (UHR).

[0196] Security association parameter field 1702 may include association flag field 1704, association link field 1706, beacon flag field 1708, token flag field 1710, token link field 1712, and probe request flag field 1714. These fields respectively contain the association flag, association link, beacon flag, token flag, token link, and probe request flag described above. As those skilled in the art will understand based on the teachings herein, when one of the security association parameters (e.g., beacon flag, probe request flag, etc.) is not present in a particular embodiment, the corresponding field in security association parameter field 1702 may also be absent.

[0197] Figure 18An example process 1800 according to an embodiment is illustrated. Example process 1800 is provided for illustrative purposes only and is not intended to limit the embodiment. Process 1800 may be performed by an STA, such as STA 1304, 1504, or 1604. STAs may include non-AP MLDs.

[0198] Step 1802 includes the STA receiving a first frame from the AP via a first link, the first frame indicating a second link that allows the execution of association procedures with the AP via it. The first link may correspond to a 2.4 GHz or 5 / 6 GHz link. The second link may correspond to a 60 GHz link. The STA may be able to operate on multiple links including the first link and the second link.

[0199] In an embodiment, the first frame includes a beacon frame or a probe response frame.

[0200] In one embodiment, the first frame includes a link identifier field. The link identifier field may indicate one or more links that allow the execution of associated procedures with the AP via them. In another embodiment, the link identifier field includes an identifier for a second link.

[0201] In one embodiment, the first frame includes a flag indicating whether execution of an associated procedure with the AP is permitted via the first link.

[0202] In an embodiment, a flag indicating that execution of the association procedure with the AP is not permitted via the first link indicates that execution of the association procedure with the AP is permitted via the second link.

[0203] In this embodiment, the first frame includes a beacon flag. The beacon flag indicates whether a STA wishing to associate with the AP via the link must wait for a beacon frame (or probe response frame) on the link before initiating an association procedure with the AP.

[0204] In one embodiment, the first frame may include a token flag indicating the presence or absence of an associated token. The associated token may be included in a frame transmitted by the AP via a first link, a second link, or a third link.

[0205] In an embodiment, the first frame may further include a token link identifier field. The token link identifier field may indicate one or more links through which frames containing associated tokens are transmitted.

[0206] In one embodiment, the first frame includes a probe request flag indicating whether the STA needs to send a probe request frame to obtain an association token from the AP. In another embodiment, the first frame includes a request flag indicating whether the STA needs to send a frame requesting to obtain an association token from the AP.

[0207] In an embodiment, the second link is part of a set of dedicated links used to execute associated procedures with the AP.

[0208] In one embodiment, a set of dedicated links includes only the second link. In an embodiment where the second link corresponds to a 60 GHz link and the AP is located within a wall structure, the association with the AP may be limited to STAs located within the wall structure. In another embodiment, a set of dedicated links includes both a first link and a second link.

[0209] Step 1804 involves transmitting the association request to the AP MLD via the STA through the second link.

[0210] In one embodiment, process 1800 may further include receiving an association response from the AP. In another embodiment, process 1800 may further include transmitting an authentication request frame to the AP and receiving an authentication response frame from the AP.

[0211] Figure 19 An example process 1900 according to an embodiment is shown. Example process 1900 is provided for illustrative purposes only and is not intended to limit the embodiment. Process 1900 may be performed by an AP, such as AP 1302, 1502, or 1602. The AP may be an AP MLD.

[0212] Step 1902 involves transmitting a first frame to the STA via the AP through a first link, the first frame indicating a second link that allows the execution of associated procedures with the AP via it. The first link may correspond to a 2.4 GHz or 5 / 6 GHz link. The second link may correspond to a 60 GHz link. The AP may be able to operate on multiple links that include the first link and the second link.

[0213] In an embodiment, the first frame includes a beacon frame or a probe response frame.

[0214] In one embodiment, the first frame includes a link identifier field. The link identifier field may indicate one or more links that allow the execution of associated procedures with the AP via them. In another embodiment, the link identifier field includes an identifier for a second link.

[0215] In one embodiment, the first frame includes a flag indicating whether execution of an associated procedure with the AP is permitted via the first link.

[0216] In an embodiment, a flag indicating that execution of the association procedure with the AP is not permitted via the first link indicates that execution of the association procedure with the AP is permitted via the second link.

[0217] In this embodiment, the first frame includes a beacon flag. The beacon flag indicates whether a STA wishing to associate with the AP via the link must wait for a beacon frame (or probe response frame) on the link before initiating an association procedure with the AP.

[0218] In one embodiment, the first frame may include a token flag indicating the presence or absence of an associated token. The associated token may be included in a frame transmitted by the AP via a first link, a second link, or a third link.

[0219] In an embodiment, the first frame may further include a token link identifier field. The token link identifier field may indicate one or more links through which frames containing associated tokens are transmitted.

[0220] In one embodiment, the first frame includes a probe request flag that indicates whether the STA needs to send a probe request frame to obtain an association token from the AP.

[0221] In an embodiment, the second link is part of a set of dedicated links used to execute associated procedures with the AP.

[0222] In one embodiment, a set of dedicated links includes only the second link. In another embodiment, a set of dedicated links includes both the first and second links.

[0223] Step 1904 includes receiving an association request from the STA via the AP through a second link.

[0224] In one embodiment, process 1900 may further include transmitting an associated response to the STA. In another embodiment, process 1900 may further include receiving an authentication request frame from the STA and transmitting an authentication response frame to the STA.

Claims

1. A method comprising: The station multilink device (STA MLD) receives a beacon frame from the access point multilink device (AP MLD) via a first link. The beacon frame indicates permission to execute an association procedure with the AP MLD via a second link. The association request frame is transmitted to the AP MLD via the second link through the STA MLD; as well as The associated response frame is received from the AP MLD via the second link through the STA MLD.

2. A method comprising: The station STA receives a first frame from the access point AP via a first link, the first frame indicating permission to execute a second link associated with the AP via it; as well as The association request is transmitted from the STA to the AP via the second link.

3. The method of claim 2, wherein the AP includes an AP multi-link device (AP MLD).

4. The method according to any one of claims 2 to 3, wherein the first frame comprises a beacon frame or a probe response frame.

5. The method according to any one of claims 2 to 4, wherein the second link is part of a set of dedicated links for performing the associated procedure with the AP.

6. The method of claim 5, wherein the set of dedicated links includes only the second link.

7. The method of claim 5, wherein the set of dedicated links includes the first link and the second link.

8. The method according to any one of claims 2 to 7, wherein the association procedure includes transmitting the association request to the AP.

9. The method of claim 8, wherein the association procedure further includes receiving an association response from the AP.

10. The method according to any one of claims 8 to 9, wherein the association procedure further comprises: Transmit the authentication request frame to the AP, and Receive authentication response frames from the AP.

11. The method according to any one of claims 2 to 10, wherein the first frame includes a link identifier field.

12. The method of claim 11, wherein the link identifier field includes the identifier of the second link.

13. The method according to any one of claims 11 to 12, wherein the link identifier field further includes an identifier of the first link.

14. The method of any one of claims 2 to 10, wherein the first frame includes a flag indicating whether execution of the association procedure with the AP is permitted via the first link.

15. The method of claim 14, wherein the flag indicating that execution of the association procedure with the AP is not permitted via the first link indicates that execution of the association procedure with the AP is permitted via the second link.

16. The method according to any one of claims 2 to 15, further comprising: The STA receives a second frame from the AP via the second link, wherein the transmission of the association request includes transmitting the association request in response to the second frame.

17. The method of claim 16, wherein the second frame comprises a beacon frame or a probe response frame.

18. The method of any one of claims 2 to 15, wherein the transmission of the association request includes transmitting the association request in response to the first frame.

19. The method of any one of claims 2 to 18, wherein the first frame indicates the presence or absence of an association token in another frame transmitted via the second link through the AP.

20. The method of claim 19, wherein the other frame transmitted via the AP through the second link includes the association token, and wherein the association request includes the association token.

21. The method according to any one of claims 2 to 20, wherein the first frame includes a beacon flag.

22. The method of claim 21, wherein the beacon flag indicates whether a STA associated with the AP via a link must wait for a beacon frame or probe response frame on the link before initiating the association procedure with the AP.

23. The method according to any one of claims 2 to 22, wherein the first link corresponds to a 2.4 GHz or 5 GHz link.

24. The method of claim 23, wherein the second link corresponds to a 60 GHz link.

25. A method comprising: The beacon frame is transmitted from the access point multilink device (AP MLD) to the station multilink device (STA) via a first link. The beacon frame indicates that a second link is permitted to execute the associated procedure with the AP MLD. The AP MLD receives an association request frame from the STA MLD via the second link; as well as The associated response frame is transmitted from the AP MLD to the STA MLD via the second link.

26. A method comprising: The first frame is transmitted to the station STA via the access point AP through the first link. The first frame indicates permission to execute the associated procedure with the AP via the second link. as well as The AP receives the association request from the STA via the second link.

27. The method of claim 26, wherein the AP includes an AP multi-link device (AP MLD).

28. The method according to any one of claims 26 to 27, wherein the first frame comprises a beacon frame or a probe response frame.

29. The method of any one of claims 26 to 28, wherein the second link is part of a set of dedicated links for performing the associated procedure with the AP.

30. The method of claim 29, wherein the set of dedicated links comprises only the second link.

31. The method of claim 29, wherein the set of dedicated links includes the first link and the second link.

32. The method according to any one of claims 26 to 31, wherein the association procedure includes receiving the association request from the STA.

33. The method of claim 32, wherein the association procedure further includes transmitting an association response to the STA.

34. The method according to any one of claims 32 to 33, wherein the association procedure further comprises: Receive authentication request frame from the STA, and The authentication response frame is transmitted to the STA.

35. The method according to any one of claims 26 to 34, wherein the first frame includes a link identifier field.

36. The method of claim 35, wherein the link identifier field includes an identifier of the second link.

37. The method according to any one of claims 35 to 36, wherein the link identifier field further includes an identifier of the first link.

38. The method of any one of claims 26 to 34, wherein the first frame includes a flag indicating whether execution of the association procedure with the AP is permitted via the first link.

39. The method of claim 38, wherein the flag indicating that execution of the association procedure with the AP is not permitted via the first link indicates that execution of the association procedure with the AP is permitted via the second link.

40. The method according to any one of claims 26 to 39, further comprising: The second frame is transmitted from the AP to the STA via the second link, wherein the reception of the association request includes receiving the association request in response to the second frame.

41. The method of claim 40, wherein the second frame comprises a beacon frame or a probe response frame.

42. The method of any one of claims 26 to 39, wherein receiving the association request includes receiving the association request in response to the first frame.

43. The method of any one of claims 26 to 42, wherein the first frame indicates the presence or absence of an associated token in a beacon frame transmitted via the second link through the AP.

44. The method of claim 43, wherein the beacon frame transmitted via the second link through the AP includes the association token, and wherein the association request includes the association token.

45. The method according to any one of claims 26 to 44, wherein the first frame includes a beacon flag.

46. ​​The method of any one of claims 45, wherein the beacon flag indicates whether a STA associated with the AP via a link must wait for a beacon frame or probe response frame on the link before initiating the association procedure with the AP.

47. The method according to any one of claims 2 to 46, wherein the first link corresponds to a 2.4 GHz or 5 GHz link.

48. The method of claim 47, wherein the second link corresponds to a 60 GHz link.

49. 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 48.

50. 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 48.

Images