Multi-link wireless communication connection

Abstract

This disclosure relates to multi-link wireless communication connections. The invention discloses a method that may include establishing a multi-link secure association between a transmitter-on-transmitter medium access control (MAC) logical entity of a transmitter and a receiver-on-receiver MAC logical entity of a receiver. The transmitter may include one or more transmitter links. The receiver may include one or more receiver links.

Description

[0001] This application is a divisional application of Chinese invention patent application No. 202011149948.5, filed on October 23, 2020, entitled "Multi-link Wireless Communication Connection".

[0002] Cross-references to related applications

[0003] This patent application claims the benefit and priority of U.S. Provisional Application No. 62 / 924,934, filed on October 23, 2019, entitled “Multi-link Wireless Communication Connection Method and System,” which is incorporated herein by reference in its entirety. Technical Field

[0004] The field of this disclosure generally relates to wireless communications, including multi-link communications, and more specifically, to their frame and security operations. Background Technology

[0005] Devices called Wireless Access Points (WAPs) are used to establish home, office, and outdoor networks, also known as Wireless Local Area Networks (WLANs). WAPs may include routers. A WAP wirelessly couples all devices on the network (e.g., wireless stations such as computers, printers, televisions, digital video (DVD) players, security cameras, and smoke detectors) to each other and wirelessly couples them to a cable or subscriber line, through which the internet, video, and television are delivered to the home. Most WAPs implement the IEEE 802.11 standard, a competition-based standard used to handle communication between multiple competing devices sharing a wireless communication medium on a chosen communication channel among several communication channels. The frequency range of each communication channel is specified in the corresponding protocol of the implemented IEEE 802.11 protocol, such as "a", "b", "g", "n", "ac", "ad", "ax", "be". Communication follows a hub-and-spoke model, where the WAP is at the hub and the spokes correspond to the wireless links to each "client" device.

[0006] After a single communication channel is selected for the associated home network, access to the shared communication channel relies on a method identified as Collision-Sensed Multiple Access (CSMA). CSMA is a distributed random access method for sharing a single communication medium, which causes contention for the communication link to fall back and retry access when an expected collision is detected on the wireless medium (i.e., if the wireless medium is in use).

[0007] Communication on a single communication medium is identified as "simplex," meaning a one-time communication stream from a single source node to one or more target nodes, where all remaining nodes can "listen" to the main transmission. Starting with the IEEE 802.11ax standard, and specifically with its "Wave 2," the WAP's so-called multi-user (MU) multiple-input multiple-output (MIMO) capability allows for simultaneous discrete communication with more than one target node. Adding MU capability to the standard enables the WAP to communicate simultaneously with single-antenna single-stream or multi-antenna multi-stream transceivers, thereby increasing the available time for discrete MIMO video links to wireless HDTV, computer tablets, and other high-throughput wireless devices whose communication capabilities compete with the WAP's. The IEEE 802.11ax standard incorporates Orthogonal Frequency Division Multiple Access (OFDMA) into the WAP or site capability. OFDMA allows the WAP to communicate simultaneously on the downlink with multiple sites identified as resource elements (across discrete frequency ranges).

[0008] The IEEE 802.11n and 802.11ac standards support the increasing complexity of signal processing required for fully compliant WLAN nodes, including beamforming capabilities for centralized communication of user data. One of the many capabilities of a fully compliant WLAN node, according to either standard, is the ability to focus the signal strength of transmitted communications onto the receiving device. Doing so requires multiple antennas and devices for independently controlling the phase and amplitude of the communication signals transmitted over them.

[0009] The subject matter claimed in this disclosure is not limited to addressing any shortcomings or specific implementations that operate only in environments such as those described above. Rather, this background is provided merely to illustrate an example technical field in which some of the specific implementations described in this disclosure may be practiced. Summary of the Invention

[0010] The method may include establishing a multi-link security association between a transmitter-on-transmitter media access control (MAC) logical entity and a receiver-on-receiver MAC logical entity. The transmitter may include one or more transmitter links. The receiver may include one or more receiver links. Attached Figure Description

[0011] The structure and operation of the exemplary embodiments will be understood by reading the following detailed description and accompanying drawings, wherein similar reference numerals refer to similar components and wherein:

[0012] Figure 1 An exemplary multi-link wireless communication system is shown;

[0013] Figure 2 An exemplary SSID configuration for a multi-link device is shown;

[0014] Figure 3 An exemplary system in which packet numbers (PNs) can be assigned at the MAC level across multiple links is shown;

[0015] Figure 4 An exemplary system is shown in which the PN can be assigned by MAC entities under one or more links;

[0016] Figure 5 An example multi-link frame MAC header is shown;

[0017] Figure 6 A flowchart illustrating an exemplary method for providing multi-link communication is shown;

[0018] Figure 7 A flowchart illustrating an exemplary method for transmitter streams in a multi-link system is shown;

[0019] Figure 8 A flowchart illustrating an exemplary method for receiver streams in a multi-link system is shown;

[0020] Figure 9 A flowchart illustrating an exemplary method by which a transmitter uses a multilink frame format to process BlockACK responses in a multilink system is shown.

[0021] Figure 10 A flowchart is shown of an exemplary method for establishing a multi-link MAC entity relationship at the transmitter for multi-link communication between the transmitter and receiver;

[0022] Figure 11 A flowchart illustrating an exemplary method for establishing a multi-link MAC entity relationship at the receiver for multi-link communication between the transmitter and receiver is shown; and

[0023] Figure 12 An exemplary system diagram is shown according to an exemplary specific implementation. Detailed Implementation

[0024] The following detailed description provides further details of the accompanying drawings and exemplary embodiments of this application. For clarity, reference numerals and descriptions of redundant elements between the drawings have been omitted. The terminology used throughout the specification is provided by way of example and is not intended to be limiting. For example, the use of the term "automatic" may refer to fully automatic or semi-automatic embodiments, which involve user or operator control over certain aspects of the embodiment, depending on the expectations of a person skilled in the art practicing the embodiments of this application.

[0025] Conventional systems are disadvantageous for next-generation multilink communication. For example, traditional wireless communication protocols cannot support the identification of entities with multilink connections. Furthermore, existing headers and frame formats cannot identify each entity in a multilink system. Without identifying each entity in a multilink system, communication may be difficult or impossible. In addition, conventional systems cannot establish per-traffic identifier (TID) aggregation block ACK protocols at the MAC level on multiple links, cannot assign frame sequence numbers (SNs) on the transmitting side of MAC entities on multiple links, and cannot construct block ACK responses and perform Rx window reordering operations on the receiving side of MAC entities on multiple links. Conventional systems also cannot assign PNs and perform replay checks at the lower MAC level.

[0026] In one example, under a conventional PN allocation system, PNs are expected to arrive at the receiver in sequence. This can be problematic in a multi-link system with multiple links, where data may travel across the links at different speeds. For example, PN=10 may be sent via the first link and PN=11 may be sent via the second link. If PN=11 arrives before PN=10, the conventional system may treat PN=10 as a replay and discard it or not transmit it further. Therefore, the conventional method may incorrectly determine that the data is a replay when it is actually valid data.

[0027] This disclosure addresses these and other shortcomings of conventional systems by providing a framework and improved methods for implementing multilink communication. This document describes aspects related to multilink security association (SA), frame MAC headers for multilinks, various transmit and receive processes, and systems to improve functionality, performance, and compatibility in resolving failures in conventional systems. In some embodiments, multilink entities (e.g., transmitters or receivers) may include two or more links operating on different frequency bands. Each link may include a link-specific PHY and a lower MAC layer. In at least one embodiment, a unified upper MAC layer interface with individual link-specific lower MACs can provide a unified MAC service access point (SAP) to the logical link control (LLC) and upper layers. In at least one embodiment, one or more multilink upper MAC entities can provide SAP and LLC services to data forwarding paths, allocation systems, and networking upper-layer protocol stacks. One or more multilink upper MAC entities may each have a discrete identifier that can be used to identify the multilink upper MAC entity as the destination or source of frames traversing the multilink data path. In at least one implementation, multilink frames belonging to a specific TID can be flexibly scheduled to be transmitted on any or each of the links belonging to or associated with the multilink entity.

[0028] Security associations can be established for each link under multi-link MAC. In at least one implementation, transmitter / receiver associations are established at the MAC entity level on multiple links, and security associations (SA) are established at the MAC entity level on multiple links using paired master keys (PMK). Furthermore, at the MAC level under each link, security associations can be established based on the PMK at the MAC entity level on multiple links.

[0029] Exemplary aspects of multi-link implementation include providing MAC entities and their identifiers on each SSID multi-link; security associations between MAC entities on multiple links; key exchange for Paired Transient Key Security Association (PTKSA) and Group Transient Key Security Association (GTKSA) on each link; transmitter-side PN number allocation; and receiver-side replay inspection procedures, transmitter-side BlockACK window management, receiver-side BlockACK window reordering management, and BlockACK retry procedures at the MAC level on multiple links. Additional aspects may include establishing a per-TID aggregated BlockACK agreement between transmitter-side and receiver-side multi-link MAC entities; performing frame sequence number allocation for multi-link frames at the transmitter-side multi-link MAC entity; performing receiver-side window reordering operations at the receiver-side multi-link MAC entity; and performing BlockACK and frame retry procedures at the MAC level on multiple links.

[0030] To carry multilink information such as transmitter-side multilink MAC entity IDs and receiver-side multilink MAC entity IDs, a new frame MAC header format can be used. As provided herein, the multilink frame MAC header format distinguishes multilink frames from existing frame formats (e.g., prior to IEEE 802.11be). Exemplary aspects of the multilink frame MAC header enable the identification of receiver-side and transmitter-side multilink MAC entities. Multilink MAC layer processing can be applied based on configuration options for specific multilink MAC entities.

[0031] Figure 1An exemplary multi-link wireless communication system 100 is illustrated. The multi-link wireless communication system 100 may include an Internet Protocol (IP) / Transmission Control Protocol (TCP) / User Datagram Protocol (UDP) network stack 105. The system may include a transmitter IP / TCP / UDP network stack 105a and a receiver IP / TCP / UDP network stack 105b. The transmitter IP / TCP / UDP network stack 105a may be associated with a transmitter multi-link MAC entity 110, which may be associated with a transmitter such as an access point (AP). A receiver such as a station (STA) may include a receiver multi-link MAC entity 115. The transmitter multi-link MAC entity 110 and the receiver multi-link MAC entity 115 may be associated with each other to enable multi-link communication between the transmitter and the receiver. The transmitter multi-link MAC entity 110 and the receiver multi-link MAC entity 115 may be logical entities.

[0032] A transmitter may include one or more radio components. Each radio component may be associated with one or more downlink MAC entities (which may be referred to herein as downlink MAC entities or downlink MAC links). Multiple uplink MAC entities may use one or more downlink MAC entities to coordinate communication on the radio components. Figure 1 As shown, the transmitter multi-link on-MAC entity 110 is coupled to three links: transmitter link-down MAC entity 120a, transmitter link-down MAC entity 120b, and transmitter link-down MAC entity 120n (collectively referred to as transmitter link-down MAC entity 120). The transmitter multi-link on-MAC entity 110 can interface with the transmitter link-down MAC entity 120. Any number of transmitter link-down MAC entities 120 can be included in the multi-link wireless communication system 100.

[0033] As shown in the figure, the receiver multi-link on-MAC entity 115 is coupled to three links: receiver link-down MAC entity 125a, receiver link-down MAC entity 125b, and receiver link-down MAC entity 125n (collectively referred to as receiver link-down MAC entity 125). The receiver multi-link on-MAC entity 115 can interface with the receiver link-down MAC entity 125. Any number of receiver link-down MAC entities 125 can be included in the multi-link wireless communication system 100. In at least one embodiment, there may be more or fewer transmitter link-down MAC entities 120 than there may be receiver link-down MAC entities 125.

[0034] In one example, transmitter link-under MAC entity 120 may include a 2.4 GHz link, a 5 GHz link, or a 6 GHz link. For example, transmitter link-under MAC entity 120a includes a 2.4 GHz link, transmitter link-under MAC entity 120b includes a 5 GHz link, and transmitter link-under MAC entity 120n includes a 6 GHz link. Similarly, receiver link-under MAC entity 125 may include any one of a 2.4 GHz link, a 5 GHz link, or a 6 GHz link.

[0035] A security association (SA) can be created at multi-link MAC entity 130 between transmitter multi-link MAC entity 110 and receiver multi-link MAC entity 115. In one example, an SA can be established between transmitter multi-link MAC entity 110 and receiver multi-link MAC entity 115 using authentication protocols such as 802.1x, pre-shared key (PSK), peer synchronization authentication (SAE), etc. The result of establishing an SA at multi-link MAC level 130 may include mutually derived PMKs. This PMK can be used to derive per-link PTKSAs, for example, through a 4-way key exchange process.

[0036] At MAC level 135, transmitter link MAC entity 120 and receiver link MAC entity 125 may be associated on a per-link basis, such as using at least one of PTKSA and / or GTKSA.

[0037] Regarding per-link PTKSA, once a multi-link SA is established at MAC level 130 across multiple links via mutually derived PMKs, then at the next MAC level 135, and on a per-link basis, the PTKSA 4-way key exchange procedure can be invoked to derive the per-link PTK[link]. An exemplary algorithm for generating the per-link PTK[link] is provided, where the input parameters are: PMK, AP_per_Link_nonce, STA_per_Link_nonce, AP_per_Link_MAC_address, and STA_per_Link_MAC_address.

[0038] PTK[link] = KDF(PMK, AP_Lower_MAC[link], AP_nonce[link],

[0039] STA_Lower_MAC[link], STA_nonce[link])

[0040] Regarding per-link GTKSA, during the PTKSA 4-way key exchange, the per-link GTK[link] can be initially delivered to the receiver. The MAC entity under each link arrives at the receiver, and the subsequent GTK[link] re-entry process can be performed through the per-link 2-way key exchange.

[0041] Therefore, from one or both of the PTKSA and GTKSA, the transmitter link-down MAC entity 120 can be associated with the corresponding receiver link-down MAC entity 125, thereby forming a link pair. The links in the link pair can be of the same type. For example, a link pair may include two 5GHz links. Each link pair may include a separate PTK and GTK. In one example, transmitter link-down MAC entity 120a and receiver link-down MAC entity 125a may form a first link pair, transmitter link-down MAC entity 120b and receiver link-down MAC entity 125b may form a second link pair, and transmitter link-down MAC entity 120n and receiver link-down MAC entity 125n may form an "nth" link pair.

[0042] In operation, MAC Protocol Data Unit (MPDU) sequence number (SN) allocation, BlockACK window management, MPDU Rx window reordering, and BlockACK response can be processed at MAC level 130 on multiple links. MPDU packet number (PN) allocation, encryption, decryption, and replay checking can be processed at MAC level 135 off-link. In at least one embodiment, PN may include an integer (e.g., 48 bits) for replay checking purposes.

[0043] The transmitter multilink on-MAC entity 110 can construct frames for transmission through the multilink system 100. In at least one embodiment, the transmitter multilink on-MAC entity can encapsulate packets that can be received from the source. Packets from the source may include a header with various information, including destination address, source address, type, Quality of Service (QoS) flags, etc. The transmitter multilink on-MAC entity can encapsulate packets from the source into a multilink frame format and assign various fields to the multilink header, such as receiver multilink entity ID (MLE ID 1), transmitter multilink entity ID (MLE ID 2), address 1 field (RA = receiver LinkX MAC address), address 2 field (TA = transmitter LinkX MAC address), TID that can be mapped from the QoS flags in the packet header from the source, and a sequence number (SN) that may include the next SN from the Tx BlockACK window.

[0044] To improve throughput, MPDUs belonging to the same TID can be transmitted over multiple links. In at least one implementation, the transmitter side at MAC level 135 can perform the allocation of MPDUs to different links. The same PN space can be used across all links, or each link can have a separate PN space.

[0045] The transmitter-link MAC entity can assign a monotonically increasing PN to each MPDU and can apply encryption to the MPDU. The transmitter-link MAC entity can transmit the MPDU as a single MPDU (S-MPDU) or an aggregated MPDU (A-MPDU).

[0046] The receiver-link-based MAC entity can receive MPDUs. The receiver-link-based MAC 135 can merge MPDUs arriving from different links, perform cyclic redundancy check (CRC), decryption, Rx replay operations, perform block ACK operations, MPDU reordering, etc. In at least one implementation, the receiver-link-based MAC entity can pass MPDUs to the receiver multi-link on-line MAC entity, and the receiver multi-link on-line MAC entity can send a block ACK (partial or complete state) to the transmitter multi-link on-line MAC entity. The receiver multi-link on-line MAC entity can release frames to the next stage of the forwarding path or release them to the receiver IP / TCP / UDP network stack 105b.

[0047] In at least one embodiment, the merged acknowledgment can be transmitted from the receiver side of lower MAC level 135 to the transmitter side of lower MAC level 135 via either link. In at least one embodiment, the BlockACK frame can merge acknowledgments of MPDUs received via different links. The BlockACK frame can be transmitted via either link. In at least one embodiment, a failed MPDU can be retransmitted on the same link or on a different link than the one used for the original transmission.

[0048] Figure 2 An exemplary SSID configuration for a multi-link device (e.g., an AP) is shown. A multi-link device can be configured with one or more SSIDs. For example, a particular multi-link device can be configured with one or more on-link MAC entities, each of which can be associated with a unique SSID. Each of the one or more on-link MAC entities can be associated with one or more off-link MAC entities.

[0049] As shown in the figure, a multilink device can be configured with three SSIDs, each associated with a corresponding multilink on-MAC entity. Each of the three multilink on-MAC entities shown can be configured for a unique SSID. For example, a first multilink on-MAC entity 200 with the numeric identifier "1" can be associated with SSID1 210 and any number of off-link MAC entities (e.g., off-link MAC entities 205a, 205b, and 205n). A second multilink on-MAC entity 220 with the numeric identifier "2" can be associated with SSID2 230 and any number of off-link MAC entities (e.g., off-link MAC entities 225a, 225b, and 225n). A third multilink on-MAC entity 240 with the numeric identifier "3" can be associated with SSID3 250 and any number of off-link MAC entities (e.g., off-link MAC entities 245a, 245b, and 245n). Although three SSIDs are shown, a multilink device can be configured for any number of SSIDs. In at least one implementation, a second transmitter on-MAC logical entity can be instantiated for the second SSID.

[0050] In at least one implementation, MAC entities on a multi-link can be identified by their respective numerical identifiers. Alternatively, MAC entities on a multi-link can have MAC addresses that can be represented to a distributed system (DS) or network stack. In one example, a MAC entity on a multi-link can use the address of a MAC entity on an associated link, or it can use a unique MAC address, such as one assigned by a network system administrator. The identifiers of one or more MAC entities on a multi-link can also be used for Basic Service Set (BSS) operations, such as association and security association procedures as described herein.

[0051] Figure 3 An exemplary system 300 is illustrated, wherein packet numbers (PNs) can be assigned at a multi-link MAC level, which may include a transmitter multi-link MAC entity 110. System 300 may additionally include a transmitter-link-under-MAC entity 120, a receiver-link-under-MAC entity 125, and a receiver multi-link MAC entity 115. In at least one embodiment, the PN may be assigned at the transmitter multi-link MAC entity 110, and replay checks may be performed at the receiver multi-link MAC entity 115. In at least one embodiment, the PN may be assigned in a monotonic order. System 300 operates within the multi-link security association and per-link PTKSA and GTKSA frameworks described herein. In at least one embodiment, the PN may be assigned in a monotonic order. Each link or link pair may have a separate PN space.

[0052] System 300 can receive one or more MAC Service Data Units (MPDUs) with a specific TID (e.g., MPDUs 305, 310, 315, and 320). The transmitter multi-link MAC entity 110 may include a PN manager 325. The PN manager 325 can assign a PN to each MPDU. As shown, the system can receive MPDU 305, and the PN manager 325 can assign PN=M to MPDU 305. Similarly, the PN manager 325 can assign PN=M+1 to MPDU 310, PN=M+2 to MPDU 315, and PN=M+N to MPDU 320. In at least one embodiment, each of MPDUs 305, 310, 315, and 320 is associated with the same TID. MPDUs 305, 310, 315, and 320 can be transmitted from the transmitter to the receiver using different links. For example, and as shown in the figure, MPDU 305 can be transmitted to receiver link-down MAC entity 125a via transmitter link-down MAC entity 120a. Similarly, MPDU 310 can be transmitted to receiver link-down MAC entity 125b via transmitter link-down MAC entity 120b, and MPDU 315 can be transmitted to receiver link-down MAC entity 125n via transmitter link-down MAC entity 120n. In this way, system 300 can provide multi-link transmission of MPDUs.

[0053] In at least one embodiment, transmissions between transmitter link-under MAC entity 120 and receiver link-under MAC entity 125 may be encrypted, such as using a PTK with a symmetric cipher. In at least one embodiment, the transmitter and receiver link-under MAC entity pair (e.g., transmitter link-under MAC entity 120a and receiver link-under MAC entity 125a) may share a link-specific PTK that can be used to encrypt and decrypt traffic between the two links in the link pair.

[0054] In at least one embodiment, the receiver multi-link MAC entity 115 may use a PN assigned by the transmitter multi-link MAC entity 110 to perform a replay check on one or more of MPDUs 305, 310, 315, and 320. The receiver multi-link MAC entity 115 may include a replay manager 330 capable of performing replay checks. Replay attacks typically involve intercepting valid data. The valid data is then replayed or delayed in an attempt to gain access to the system. As a way to thwart replay attacks, the replay manager 330 may check the order of the PNs of the MPDUs. A failed replay check may indicate a security vulnerability. For a PN allocation scheme that increments the PN number for each subsequent MPDU, the replay manager 330 may discard any PN with a lower PN than the most recent MPDU.

[0055] Figure 4 An exemplary system 400 is illustrated, in which a PN can be assigned to an MPDU at one or more link-under MAC entities. System 400 may include a transmitter multi-link on-MAC entity 110, a transmitter link-under MAC entity 120, a receiver link-under MAC entity 125, and a receiver multi-link on-MAC entity 115. The transmitter link-under MAC entity 120 may assign PNs, such as on a per-link basis. System 400 may operate within the multi-link security association and per-link PTKSA and GTKSA frameworks described herein. In at least one embodiment, PNs may be assigned in a monotonic order. Each link or link pair may have a separate PN space. In at least one embodiment, per-link PTKSA and GTKSA details are not shared with the multi-link on-MAC layer 130. In a multi-link environment, PNs assigned at one or more link-under MAC entities may provide advantages over PNs assigned at multi-link on-MAC entities due to increased capabilities for more accurate replay checks and reordering, as described in this document.

[0056] System 400 can receive one or more MPDUs 405, 410, 415, and 420 with a specific TID. Transmitter multilink on-MAC entity 110 can pass MPDUs 405, 410, 415, and 420 to transmitter link-down MAC entity 120. Each of transmitter link-down MAC entities 120 can include a corresponding PN manager 455. As shown, MPDUs 425 and 440 can be passed to transmitter link-down MAC entity 120a, where PN manager 455a can assign PN=M to MPDU 425 and assign PN=M+1 to MPDU 440. Similarly, MPDUs 430 and 445 can be passed by transmitter multilink on-MAC entity 110 to transmitter link-down MAC entity 120b. PN manager 455b can assign PN=K to MPDU 430 and assign PN=K+1 to MPDU 445. MPDUs 435 and 450 can be passed from the transmitter multi-link on-MAC entity 110 to the transmitter link-down MAC entity 120n. The PN manager 455n can assign PN=J to MPDU 435 and PN=J+1 to MPDU 450. In at least one embodiment, MPDUs 405, 410, 415, and 420 can be passed to the transmitter link-down MAC entity 120 by placing them in different links based on their respective channel access conditions. At a given time, if a particular link has channel access, an MPDU can be transmitted from that link for transmission. Alternatively, MPDUs 405, 410, 415, and 420 can be passed from the transmitter multi-link on-MAC entity 110 to the transmitter link-down MAC entity 120 by placing them in different links based on various parameters such as link bandwidth capacity, interference conditions, etc. For example, a link with a higher bandwidth capacity (above a bandwidth capacity threshold) and / or a lower interference level (below an interference threshold) can be used to transmit more MPDUs. Links with lower bandwidth capacity (e.g., below the bandwidth capacity threshold) or higher interference (e.g., above the interference threshold) can be used to send fewer MPDUs.

[0057] MPDUs 425, 430, 435, 440, 445, and 450 can be transmitted to corresponding receiver under-link MAC entities 125 via the respective transmitter under-link MAC entity 120. In at least one embodiment, the transmission between transmitter under-link MAC entity 120 and receiver under-link MAC entity 125 can be encrypted, such as using a PTK with a symmetric cipher. In at least one embodiment, the transmitter and receiver under-link MAC entity pair (e.g., transmitter under-link MAC entity 120a and receiver under-link MAC entity 125a) can share a link-specific PTK that can be used to encrypt and decrypt traffic between the two links in the link pair.

[0058] On the receiver side, replay checks can be performed at the receiver of each link-based MAC entity. In at least one embodiment, replay checks can be performed on a per-link or per-link-pair basis. Each of the receiver link-based MAC entities 125 may include a corresponding replay manager 460. As shown, receiver link-based MAC entity 125a may include replay manager 460a, receiver link-based MAC entity 125b may include replay manager 460b, and receiver link-based MAC entity 125n may include replay manager 460n.

[0059] Because the PN manager 255 allocates PNs on a per-link basis at the transmitter's per-link MAC entity, each link can maintain its own monotonically increasing PN[link] space, and the risk of false alarms is reduced. For example, false alarms can be introduced when MPDUs are transmitted through different links with different speeds and PHY rates. Those different speeds can cause MPDUs with higher PNs to arrive before other valid MPDUs with lower PNs. In this case, valid MPDUs with lower PNs will be considered replays and discarded. The above-mentioned false alarms are prevented by performing PN allocation and replay checks on a per-link basis. Therefore, replay checks can be performed by the corresponding replay manager 460 at the receiver's MAC level 135 on a per-link basis.

[0060] Once a replay check has been performed at the replay manager 460, the receiver link-down MAC entity 125 can pass the MPDU to the receiver multi-link-up MAC entity 115.

[0061] The receiver multi-link MAC entity 115 may include a reordering manager 464. The reordering manager 464 performs reordering operations to ensure that MPDUs received over various links are in order. To check the order of MPDUs, the reordering manager 464 may identify a sequence number (SN) assigned to each MPDU by the transmitter multi-link MAC entity 110. If any of the SNs is out of order, the reordering manager 464 may reorder the MPDUs so that they are sent to the destination address in the correct order.

[0062] Figure 5 An exemplary multilink frame MAC header 500 is illustrated. The multilink frame MAC header 500 can be constructed by the MAC entities on the transmitter multilink during the encapsulation process. To facilitate communication over a multilink system, the MAC header 500 can include identification of each point in the multilink system, enabling frames to be appropriately processed (e.g., for replay checks and reordering operations) and forwarded from the source device to the final destination device. These identifications of each point in the multilink system are carried in the multilink frame MAC header 500. These identifications in the multilink frame MAC header 500 may identify some or all of the following: transmitter multilink MAC entity ID, receiver multilink MAC entity ID, per-link transmitter address (TA), per-link receiver address (RA), source address (SA) of the frame, and destination address (DA).

[0063] In at least one implementation, the transmitter multilink on-MAC entity can encapsulate packets that can be received from the source. Packets from the source may include a destination address, source address, type, Quality of Service (QoS) flags, etc. The transmitter multilink on-MAC entity can encapsulate packets from the source into a multilink frame format and assign various fields to the multilink MAC header, such as the receiver multilink entity ID (MLE ID 1), the transmitter multilink entity ID (MLE ID 2), the address 1 field (RA = receiver LinkX MAC address), the address 2 field (TA = transmitter LinkX MAC address), a TID that can be mapped from the QoS flags in the packet header from the source, and a sequence number (SN) that may include the next SN from the Tx BlockACK window. The SN can be used for Rx reordering, such as to ensure that frames associated with the same TID are released in order.

[0064] The multilink frame MAC header 500 may include a frame control field 505. The frame control field 505 may provide a "protocol version" field that can be used to inform the device of the protocol used in the multilink frame MAC header 500. For example, the protocol version field may indicate a specific wireless protocol, such as having a value of 00b (which may indicate a previous MAC header format) or a value of 01b (which may indicate a multilink MAC header format where one or both of the MLE ID 1 and MLE ID 2 fields are present). In one exemplary implementation, the protocol version field of the frame control field 505 may include any value used to indicate the use of a multilink frame MAC header.

[0065] Figures 6 to 11 A flowchart illustrating an exemplary method related to multi-link communication is shown. The method may be executed by processing logic, which may include hardware (circuit, dedicated logic, etc.), software (such as software running on a general-purpose computer system or a dedicated machine), or a combination of both. This processing logic may be included in any transmitter (e.g., AP) or receiver (e.g., STA) or another computer system or device. However, another system or combination of systems may be used to execute the method. For simplicity of explanation, the methods described herein are depicted and described as a series of actions. However, actions according to this disclosure may be performed in various orders and / or simultaneously, and with other actions not presented and described herein. Furthermore, not all actions shown are available for implementing the method according to the disclosed subject matter. Moreover, those skilled in the art will understand and recognize that the method may alternatively be represented as a series of interrelated states via a state diagram or events. Additionally, the methods disclosed in this specification can be stored on an article of manufacture (such as a non-transitory computer-readable medium) to facilitate the transfer and assignment of such methods to a computing device. As used herein, the term article of manufacture is intended to cover a computer program accessible from any computer-readable device or storage medium. Although shown as discrete boxes, depending on the specific implementation desired, the individual boxes can be divided into additional boxes, combined into fewer boxes, or eliminated.

[0066] Figure 6 A flowchart of an exemplary method 600 for providing multi-link communication is shown. Method 600 may begin at block 605, where processing logic may select a transmitter with multi-link capability from a list of available transmitters based on beacon announcement information indicating that the transmitter has multi-link support. In at least one embodiment, the beacon announcement information may include identifiers and / or link types of the available transmitter links.

[0067] At block 610, processing logic can establish a multi-link relationship between the transmitter multi-link MAC entity of the transmitter and the receiver multi-link MAC entity of the receiver. In at least one embodiment, the multi-link relationship can be used to determine multiple links available for multi-link use.

[0068] At block 615, the processing logic may establish a multi-link security association between a transmitter multi-link MAC entity of the transmitter and a receiver multi-link MAC entity of the receiver. In at least one embodiment, the transmitter may include a first transmitter link and a second transmitter link, and the receiver may include a first receiver link and a second receiver link. In at least one embodiment, establishing a multi-link security association between the transmitter multi-link MAC entity of the transmitter and the receiver multi-link MAC entity of the receiver includes mutually deriving PMKs.

[0069] At block 620, processing logic may establish a secure association for each link pair in a multi-link system at the lower MAC level. For example, the transmitter and receiver may include one or more corresponding links of the same type that can be paired for communication. For example, a transmitter 5GHz link may be paired with a receiver 5GHz link. In at least one embodiment, a first transmitter link may be associated with a first receiver link at the lower MAC level via a PTKSA, which is created using a four-way key exchange using mutually derived PMKs, a first transmitter link random number, a first receiver link random number, a first transmitter link address, and a first receiver link address. In at least one embodiment, the secure association for each link pair in the multi-link system at the lower MAC level may also include a GTKSA, which is derived during the four-way key exchange and established using a bidirectional key exchange at the lower MAC level and between the first transmitter link and the first receiver link. In at least one embodiment, establishing a secure association for each link pair in the multi-link system at the lower MAC level may include associating a first transmitter link with a first receiver link at the lower MAC level, and associating a second transmitter link with a second receiver link at the lower MAC level.

[0070] At block 625, processing logic can transmit and receive secure communications on one or more links of the relationship. In at least one implementation, communications can be secured using each derived PTK with a symmetric cryptography (e.g., CCMP, GCMP, etc.). Thus, method 600 can provide aspects related to multi-link secure associations at both the upper and lower MAC levels to improve functionality, performance, and compatibility in resolving failures in conventional systems.

[0071] Figure 7 A flowchart illustrating an exemplary method 700 for a transmitter stream in a multi-link system is shown. Method 700 may begin at block 705, where processing logic may include, for example, receiving packets from an allocation system. Packets may include destination address, source address, type, Quality of Service (QoS) tags, etc.

[0072] At box 710, the processing logic can pass packets to a multi-link MAC entity, such as multi-link MAC entity 110. At box 715, the processing logic can select the link for transmitting packets.

[0073] At box 720, the processing logic can encapsulate packets into MSDU or A-MSDU subframes and assign various fields that may be included in the multilink MAC header. At box 725, the processing logic can aggregate two or more MSDU or A-MSDU subframes into an aggregated MAC service data unit (A-MSDU).

[0074] At block 730, the processing logic may construct a MAC Service Data Unit (MSDU) with a multilink MAC header. At block 735, the processing logic may populate the multilink MAC header with various data. In at least one embodiment, the processing logic may populate the multilink MAC header with the following: Receiver Multilink Entity ID (MLE ID 1), Transmitter Multilink Entity ID (MLE ID 2), Address 1 field (RA = MAC address under Receiver LinkX), Address 2 field (TA = MAC address under Transmitter LinkX), TID that can be mapped from the QoS tag in the packet header from the source, and a sequence number (SN) that may include the next SN from the Tx BlockACK window.

[0075] At block 740, the processing logic can send an MPDU with a multi-link MAC header to the link selected at block 715. In at least one embodiment, the processing logic can send the MPDU to the transmitter link-down MAC.

[0076] At block 745, the processing logic may assign a packet number (PN) to an MPDU. In at least one embodiment, the PN is assigned at the transmitter link-under MAC. In at least one embodiment, the PN is assigned at the MAC entity on the multi-link. At block 750, the processing logic may transmit the MPDU to the receiver link associated with the selected link. In at least one embodiment, the MPDU may be aggregated in an A-MPDU. In at least one embodiment, the MPDU and / or A-MPDU may be transmitted from the transmitter link-under MAC to the receiver link-under MAC in a Physical Layer Convergence Protocol Data Unit (PPDU). Therefore, method 700 can improve functionality, performance, and compatibility by providing benefits for resolving faults in conventional systems. Such benefits can be provided to transmitters in multi-link systems to support the identification of entities with multi-link connections, provide headers and frame formats to identify each entity in the multi-link system, establish a per-TID aggregation BlockACK protocol at the MAC level on the multi-link, and assign a frame SN at the transmitter side of the MAC entity on the multi-link.

[0077] Figure 8 A flowchart illustrating an exemplary method 800 for a receiver stream in a multi-link system is shown. Method 800 may begin at block 805, where processing logic may receive an MPDU at a receiver link-down MAC entity, which may include receiver link-down MAC entity 125. The MPDU received at the receiver link-down MAC entity may be included in... Figure 7 The MPDU (or A-MPDU) transmitted by the MAC entity under the transmitter link.

[0078] At block 810, the processing logic performs a CRC check to verify the integrity of the packet at the receiver. The receiver calculates the CRC value on the received MPDU and compares the calculated value with the frame check sequence of the MPDU. If the values ​​do not match, the MPDU can be considered corrupted. At block 815, the processing logic decrypts the MPDU using the receiver's offline MAC.

[0079] At box 820, the processing logic can perform a replay check on the receiver link-down MAC. At box 825, the processing logic can send the MPDU to the receiver multi-link MAC entity, such as multi-link MAC entity 115.

[0080] At box 830, the processing logic determines whether to use a partial-state BlockACK or a full-state BlockACK. In response to determining that a partial-state BlockACK should be used ("Yes" at box 830), at box 835, the processing logic responds to the transmitter's MAC entity via the partial-state BlockACK. At box 840, the processing logic can run Rx reordering on multiple MPDUs to determine if the MPDUs were received in the correct order. In at least one implementation, the Rx reordering operation can be performed on a per-link basis, meaning a separate Rx reordering operation is performed at each link in the system. If an MPDU is found to be out of order during the Rx reordering operation, the processing logic can reorder the MPDUs to the correct order.

[0081] At box 845, the processing logic can decapsulate the MPDU and / or deaggregate the A-MSDU to generate packets (which may include...). Figure 7 (The packet received at box 705). At box 850, the processing logic can send the packet to, for example, another device or network stack.

[0082] In response to determining that a full-state BlockACK is used ("No" at box 830), the processing logic can run Rx reordering at box 855. At box 860, the processing logic can respond to the transmitter link-under MAC entity with a partial-state BlockACK and proceed to boxes 845 and 850.

[0083] Therefore, method 800 can improve functionality, performance, and compatibility by providing the benefit of resolving faults in conventional systems. Such benefits can be provided to receivers in multi-link systems to perform per-link replay checks at the lower MAC level, build BlockACK responses, and perform Rx window reordering operations at the receiver's MAC level.

[0084] Figure 9 A flowchart illustrating an exemplary method 900 for a transmitter to process a BlockACK response using a multi-link frame format in a multi-link system is shown. Method 900 may begin at block 905, where processing logic may receive a BlockACK from a receiver's downlink MAC entity (e.g., receiver downlink MAC entity 125) at a transmitter downlink MAC entity (e.g., transmitter downlink MAC entity 120). In a multi-link system, method 900 may be executed independently for each link in the multi-link system.

[0085] At block 910, the processing logic can determine the associated transmitter multilink MAC entity. In at least one embodiment, the transmitter multilink MAC entity can be determined based on the BlockACK frame multilink MAC header, which may include values ​​for identifying the transmitter multilink MAC entity associated with the BlockACK. In one example, Figure 5 The MLE ID 1 shown may include a value used to identify the MAC entity on the transmitter multilink. At box 915, the processing logic may send a BlockACK to the associated multilink MAC entity identified at box 910.

[0086] At box 920, the processing logic can handle BlockACK at the MAC entity on the transmitter multilink. Handling BlockACK may include withdrawing all acknowledged MPDUs and advancing the Tx BlockACK window.

[0087] At box 925, the processing logic can determine whether any unacknowledged MPDUs exist. If no unacknowledged MPDUs exist ("No" at box 925), the processing logic can proceed to box 905.

[0088] When at least one unacknowledged MPDU exists (marked "Yes" at block 925), at block 930, the processing logic may instruct the downlink MAC to retransmit any unacknowledged MPDU. In at least one embodiment, the processing logic may notify the transmitter downlink MAC of the unacknowledged MPDU, and the transmitter downlink MAC may request the unacknowledged MPDU from the receiver downlink MAC. The receiver downlink MAC may send the unacknowledged MPDU to the transmitter downlink MAC, and at block 935, the processing logic may receive the unacknowledged MPDU at the multi-link uplink MAC entity.

[0089] Figure 10 A flowchart is shown of an exemplary method 1000 for establishing a multilink MAC entity relationship at the transmitter for multilink communication between the transmitter and receiver. Method 1000 may begin at block 1005, where processing logic may receive a broadcast probe request from the receiver having a multilink indicator (e.g., SSID, wildcard, etc.). At block 1010, the processing logic may determine, based on the probe request, that the receiver is multilink capable.

[0090] At block 1015, the processing logic may transmit a probe response frame indicating the MAC entity identifier on the multi-link of the transmitter. At block 1020, the processing logic may receive an authentication trigger from the receiver. In at least one embodiment, the authentication trigger may include an open-mode authentication trigger.

[0091] At block 1025, the processing logic may transmit an authentication response. In at least one embodiment, the authentication response may include an open-mode authentication response. At block 1030, the processing logic may receive an association request from a receiver. In at least one embodiment, the association request may include the receiver's multi-link MAC entity identifier. At block 1035, the processing logic may transmit an association response including the transmitter's multi-link MAC entity ID.

[0092] Figure 11 A flowchart of an exemplary method 1100 for establishing a multilink on-MAC entity relationship at a receiver for multilink communication between a transmitter and a receiver is shown. Method 1100 may begin at block 1105, where processing logic may initiate a probe request that informs the transmitter that the receiver has multilink support and a receiver multilink on-MAC entity ID. At block 1110, the processing logic may receive a probe response from the transmitter that has the transmitter multilink on-MAC entity ID.

[0093] At block 1115, the processing logic may transmit a first authentication frame addressed to the MAC entity ID on the transmitter multilink. At block 1120, the processing logic may receive a second authentication frame addressed to the MAC entity ID on the receiver multilink. At block 1125, the processing logic may transmit an association request for the MAC entity ID on the transmitter multilink. At block 1130, the processing logic may receive an association response for the MAC entity ID on the receiver multilink.

[0094] An exemplary transmission path / chain includes the following discrete and shared components. The WiFi Media Access Control (WMAC) component includes: hardware queues for each downlink and uplink communication stream; encryption and decryption circuitry for encrypting and decrypting the downlink and uplink communication streams; media access circuitry for performing Free Channel Assessment (CCA) and making exponential random backoff and retransmission decisions; and packet processor circuitry for packet processing of the transmitted and received communication streams. The WMAC component has access to a node table that lists each node / site on the WLAN, the site's capabilities, the corresponding encryption key, and the priority associated with its communication services.

[0095] Each probe or data packet used for wireless transmission to one or more stations on the transmit path component is framed within a frame. Next, each stream is encoded and scrambled in an encoder and scrambler, and then demultiplexed into individual streams in a demultiplexer. The subsequent streams undergo interleaving and mapping in their corresponding counterparts in an interleaving mapper. Next, all transmissions are spatially mapped using a spatial mapping matrix (SMM) in a spatial mapper. The spatially mapped streams from the spatial mapper are input to an inverse discrete Fourier transform (IDFT) component for conversion from the frequency domain to the time domain in the AFT and RF stages, as well as for subsequent transmissions.

[0096] In the AFT RF phase, each IDFT is coupled to a corresponding link in the transmit path / chain for wireless transmission over an associated link in the MIMO antenna array. Specifically, each IDFT is coupled to an associated link of: a digital-to-analog converter (DAC) for converting digital transmissions to analog transmissions, a filter, an upconverter coupled to a common voltage controlled oscillator (VCO) for upconverting the transmission to the appropriate center frequency of the selected channel, and a power amplifier for setting the transmission power level on the MIMO antenna array.

[0097] The receive path / chain comprises the following discrete and shared components. During the AFE-RF phase, RF processing, including down-conversion, is performed on the communication received on the MIMO antenna array of the WAP. There are six receive paths, each comprising the following discrete and shared components: a low-noise amplifier (LNA) for amplifying the received signal under the control of analog gain control (AGC) (not shown) to set the amount of amplification of the received signal; a downconverter coupled to the VCO for down-converting the received signal; a filter for bandpass filtering the received signal; and an analog-to-digital converter (ADC) for digitizing the down-converted signal. In one embodiment, an optional sampler at the output of the ADC allows sampling of the received WiFi signal in the time domain for subsequent WiFi spatial diagnostics performed by the processor and non-volatile memory. The digital output from each ADC is passed to a corresponding discrete Fourier transform (DFT) component in the baseband portion of the WiFi phase for conversion from the time domain to the frequency domain.

[0098] The receive processing in the baseband stage includes the following shared and discrete components: an equalizer for suppressing channel impairments, coupled to the output of the DFT. In one embodiment, whether equalized or unbalanced, the received WiFi signal from the DFT output in the frequency domain is provided to a processor and a non-volatile memory. The received WiFi stream at the output of the equalizer undergoes demapping and deinterleaving in a corresponding number of demappers and deinterleavers. Next, the received stream is multiplexed in a multiplexer and decoded and descrambled in decoder and descrambler components, and then deframed in a deframer. The received communication is then passed to a WMAC component, where it is decrypted by decryption circuitry and placed in the appropriate upstream hardware queue for uploading to the Internet.

[0099] Computer-readable storage media may refer to tangible media, such as, but not limited to, optical discs, magnetic disks, read-only memory, random access memory, solid-state devices, and drives, or any other type of tangible or non-transitory media suitable for storing electronic information. Computer-readable signal media may include media such as carrier waves. The algorithms and displays presented herein are not inherently related to any particular computer or other device. Computer programs may refer to pure software implementations that involve instructions to perform the desired operations of the implementation.

[0100] Various general-purpose systems can be used with the programs and modules illustrated in this document, or it may prove convenient to construct more specialized devices to perform the desired methodological operations. Furthermore, no particular programming language is referenced in the description of the exemplary embodiments. It should be understood that the teachings of the exemplary embodiments described herein can be implemented using various programming languages. The instructions of the programming language can be executed by one or more processing devices, such as a central processing unit (CPU), processor, or controller.

[0101] The components and processes disclosed herein may be implemented individually or in combination of the following: hardware, circuitry, firmware, software, or a processor executing computer program code; and transmit and receive path components coupled to the wireless transceiver without departing from the scope of the claimed disclosure.

[0102] The subject matter techniques are illustrated, for example, according to the various aspects described below. For convenience, various examples of aspects of the subject matter techniques are described as numbered embodiments (1, 2, 3, etc.). These are provided by way of example and do not limit the subject matter techniques. Unless the context otherwise requires, aspects of the various embodiments described herein may be omitted, substituted for aspects of other embodiments, or combined with aspects of other embodiments. For example, one or more aspects of Embodiment 1 below may be omitted, substituted for one or more aspects of another embodiment (e.g., Embodiment 2) or multiple embodiments, or combined with aspects of another embodiment. The following is a non-limiting overview of some exemplary embodiments presented herein.

[0103] Example 1 includes a method that may include establishing a multi-link security association between a transmitter-on-transmitter media access control (MAC) logical entity of a transmitter and a receiver-on-receiver MAC logical entity of a receiver. The transmitter may include a first transmitter link and a second transmitter link. The receiver may include a first receiver link and a second receiver link.

[0104] In a specific implementation of Embodiment 1, the first data includes at least one of the following: frames, packets, MAC Service Data Units (MSDUs), Aggregated MSDUs (A-MSDUs), or MAC Protocol Data Units (MPDUs). In a specific implementation of Embodiment 1, providing the first data to the first receiver link via the first transmitter link includes updating a frame control field to indicate a multi-link protocol version. In a specific implementation of Embodiment 1, the transmitter on-board MAC logical entity is associated with a first Service Set Identifier (SSID). In a specific implementation of Embodiment 1, the method further includes instantiating a second transmitter on-board MAC logical entity for a second SSID.

[0105] Example 2 includes a method that may include establishing a multi-link security association between a media access control (MAC) logical entity on a transmitter and a MAC logical entity on a receiver. The transmitter may include a first transmitter link and a second transmitter link. The receiver may include a first receiver link and a second receiver link. The method may include receiving first data from the first transmitter link at the first receiver link. The method may include receiving second data from the second transmitter link at the second receiver link.

[0106] In a specific implementation of Example 2, the first data includes at least one of the following: frame, packet, MAC Service Data Unit (MSDU), Aggregated MSDU (A-MSDU), or MAC Protocol Data Unit (MPDU).

[0107] In another specific implementation of Example 2, the method further includes receiving a first identifier associated with the first data and a second identifier associated with the second data.

[0108] In another specific implementation of Example 2, the method further includes performing a reordering operation, which includes using a first identifier and a second identifier to determine that the first data is expected to arrive before the second data, determining that the second data arrives at the receiver before the first data, and reordering the first data and the second data to place the first data before the second data.

[0109] In another specific implementation of Example 2, the method further includes performing a replay check at the receiver at the lower MAC level.

[0110] In another specific implementation of Example 2, a first replay check is performed on the first data received via the first receiver link, wherein a second replay check is performed on the second data received via the second receiver link.

[0111] Figure 12 A block diagram of an exemplary computing system 2002, according to at least one specific embodiment of the present disclosure, is shown, which can be used to perform or direct the execution of the one or more operations described herein. The computing system 2002 may include a processor 2050, a memory 2052, and a data storage device 2054. The processor 2050, memory 2052, and data storage device 2054 are communicatively coupled.

[0112] Generally, processor 2050 may include any suitable special-purpose or general-purpose computer, computing entity, or processing device comprising various computer hardware or software modules, and may be configured to execute instructions stored on any suitable computer-readable storage medium. For example, processor 2050 may include a microprocessor, microcontroller, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or any other digital or analog circuit configured to interpret and / or execute computer-executable instructions and / or process data. Although shown as a single processor, processor 2050 may include any number of processors configured to individually or jointly perform any number of operations described in this disclosure or to direct the execution of said operations.

[0113] In some embodiments, processor 2050 may be configured to interpret and / or execute computer-executable instructions and / or process data stored in memory 2052, data storage device 2054, or both. In some embodiments, processor 2050 may retrieve computer-executable instructions from data storage device 2054 and load the computer-executable instructions into memory 2052. After loading the computer-executable instructions into memory 2052, processor 2050 may execute the computer-executable instructions.

[0114] Memory 2052 and data storage device 2054 may include computer-readable storage media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable storage media may include any available media accessible by a general-purpose or special-purpose computer, such as processor 2050. By way of example, and not limitation, such computer-readable storage media may include tangible or non-transitory computer-readable storage media, including random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), optical disc read-only memory (CD-ROM) or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, flash memory devices (e.g., solid-state memory devices), or any other storage medium that can be used to carry or store specific program code in the form of computer-executable instructions or data structures and is accessible by a general-purpose or special-purpose computer. Combinations of the above may also be included within the scope of computer-readable storage media. Computer-executable instructions may include, for example, instructions and data configured to cause processor 2050 to perform an operation or a set of operations.

[0115] Some parts of the specific implementation refer to different modules configured to perform operations. One or more modules may include code and routines configured to cause a computing system to perform one or more of the operations described therewith. Alternatively or alternatively, one or more modules may be implemented using hardware, including any number of processors, microprocessors (e.g., to perform or control the execution of one or more operations), DSPs, FPGAs, ASICs, or any suitable combination of two or more of these. Alternatively or alternatively, one or more modules may be implemented using a combination of hardware and software. In this disclosure, operations described as being performed by a particular module may include operations that the particular module may instruct a corresponding system (e.g., a corresponding computing system) to perform. Furthermore, the depiction of different modules is for the purpose of explaining the concepts described in this disclosure and is not restrictive. Additionally, one or more modules may be configured to perform more, fewer, and / or different operations than those described above, such that modules can be combined or depicted in the different ways.

[0116] Some parts of the specific implementation are presented based on algorithms and symbolic representations of operations within a computer. These algorithmic descriptions and symbolic representations are means used by those skilled in the art of data processing to communicate their innovative essence to others skilled in the art. An algorithm is a series of configured operations that produce a desired ending state or result. In exemplary implementations, the operations performed require a tangible number of physical manipulations to achieve a tangible result.

[0117] Unless otherwise specified, it is obvious from the discussion that the use of terms such as detection, determination, analysis, identification, scanning, etc., throughout the description may include the actions and processes of computer systems or other information processing devices that manipulate and transform data representing physical (electronic) quantities in the registers and memories of the computer system into other data representing physical quantities in the memory or registers or other information storage, transmission, or display devices of the computer system.

[0118] The example implementation may also involve means for performing the operations described herein. This means may be specifically constructed for the desired purpose, or it may include one or more general-purpose computers selectively activated or reconfigured by one or more computer programs. Such computer programs may be stored in a computer-readable medium, such as a computer-readable storage medium or a computer-readable signal medium. Computer-executable instructions may include, for example, instructions and data that cause a general-purpose computer, a special-purpose computer, or a special-purpose processing device (e.g., one or more processors) to perform or control the performance of certain functions or groups of functions.

[0119] Although the subject matter has been described in language specific to structural features and / or methodological actions, it should be understood that the subject matter configured in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

[0120] Exemplary devices may include a wireless access point (WAP) or site and incorporate a VLSI processor and program code for support. Example transceivers are coupled via an integrated modem to one of a cable, fiber optic, or digital subscriber backbone connection to the Internet to support wireless communication over a wireless local area network (WLAN), such as IEEE 802.11 compliant communication. The WiFi phase includes a baseband phase, as well as an analog front-end (AFE) phase and a radio frequency (RF) phase. In the baseband section, wireless communication transmitted to or received from each user / client / site is processed. The AFE and RF sections process up-conversion on each transmit path of the wireless transmission initiated in the baseband. The RF section also processes down-conversion of signals received on the receive path and passes them to the baseband for further processing.

[0121] An exemplary device may be a multiple-input multiple-output (MIMO) device that supports up to N×N discrete communication streams via N antennas. In the example, the MIMO device signal processing unit may be implemented as N×N. In various specific implementations, the value of N can be 4, 6, 8, 12, 16, etc. Extended MIMO operation enables the use of up to 2N antennas to communicate with another similarly equipped wireless system. It should be noted that even if the system does not have the same number of antennas, an extended MIMO system can communicate with other wireless systems, but may not utilize some antennas of one station, thus reducing optimal performance.

[0122] Channel state information (CSI) from any device described herein can be extracted independently of changes in channel state parameters and used for spatial diagnostic services of the network, such as motion detection, proximity detection, and location. These spatial diagnostic services can be used for applications such as WLAN diagnostics, home security, health monitoring, smart home facility control, elderly care, vehicle tracking and monitoring, home or mobile entertainment, and automotive infotainment.

[0123] Unless the specific arrangements described herein are mutually exclusive, the various embodiments described herein can be combined, in whole or in part, to enhance system functionality and / or create complementary functions. Similarly, aspects of the embodiments can be implemented through independent arrangements. Therefore, the above description has been given by way of example only and can be modified in detail within the scope of this invention.

[0124] Regarding the use of virtually any plural or singular terminology herein, those skilled in the art can convert from plural to singular or vice versa, depending on the context or application to which it applies. For clarity, various singular / plural arrangements may be explicitly described herein. Unless otherwise stated, references to elements in singular form are not intended to mean "one and only one," but rather "one or more." Furthermore, nothing disclosed herein is intended for public use, whether or not such disclosure is explicitly stated in the foregoing description.

[0125] Generally, the terms used herein, particularly in the appended claims (e.g., the body of the appended claims), are generally expected to be "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "including but not limited to," etc.). Additionally, in cases where conventions such as "at least one of A, B, and C" are used, such constructs generally imply the conventions that should be understood by one of those skilled in the art (e.g., "a system having at least one of A, B, and C" would include, but is not limited to, systems including A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B, and C together, etc.). Furthermore, phrases presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to include one term, any one of the terms, or both terms. For example, the phrase "A or B" would be understood to include the possibility of "A" or "B" or "A and B."

[0126] Furthermore, the use of terms such as "first," "second," and "third" does not necessarily imply a specific order or quantity of elements herein. Generally, the terms "first," "second," and "third" are used to distinguish different elements as general identifiers. Unless otherwise stated, the terms "first," "second," and "third" should not be construed as implying a specific order. Similarly, if the terms "first," "second," and "third" indicate a specific number of elements, they should not be construed as implying a specific number of elements.

[0127] The invention may be embodied in other specific forms without departing from the spirit or essential characteristics of the invention. The specific embodiments described are to be considered exemplary in all respects only and not restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All variations within the meaning and scope of the equivalents of the claims are covered within the scope of the claims.

Claims

1. A method comprising: A multi-link security association is established between the transmitter's on-transmitter media access control (MAC) logical entity and the receiver's on-receiver MAC logical entity, wherein the transmitter includes a first transmitter link and a second transmitter link, and the receiver includes a first receiver link and a second receiver link.

2. The method according to claim 1, further comprising: Associate the first transmitter link with the first receiver link at the lower MAC level; as well as The second transmitter link is associated with the second receiver link at the lower MAC level.

3. The method of claim 2, wherein the first transmitter link includes at least one of a 2.4 GHz link, a 5 GHz link, or a 6 GHz link, and wherein the first receiver link is a link of the same type as the first transmitter link.

4. The method of claim 2, wherein the output for establishing the multi-link security association between the MAC logic entity on the transmitter and the MAC logic entity on the receiver includes mutually derived pairwise master keys PMK.

5. The method of claim 4, wherein the first transmitter link is associated with the first receiver link at the lower MAC level via a pairwise transient key security association (PTKSA), the PTKSA being created using a four-way key exchange that uses the PMK, a first transmitter link random number, a first receiver link random number, a first transmitter link address, and a first receiver link address.

6. The method of claim 4, wherein the first transmitter link is associated with the first receiver link at the lower MAC level via a Group Transient Key Security Association (GTKSA), the GTKSA being derived during the four-way key exchange and established using a two-way key exchange at the lower MAC level and between the first transmitter link and the first receiver link.

7. The method according to claim 1, further comprising: First data is provided to the first receiver link via the first transmitter link; as well as The second data is provided to the second receiver link via the second transmitter link.

8. The method of claim 7, further comprising assigning a first identifier to the first data and assigning a second identifier to the second data.

9. The method of claim 8, wherein the first identifier is assigned to the first data at the lower MAC level at the transmitter.

10. The method of claim 7, wherein providing the first data to the first receiver link via the first transmitter link comprises: Construct multi-link MAC frames; Update the MAC header to include the MAC logical entity identifier on the transmitter, the MAC logical entity identifier on the receiver, the transmitter address per link (TA), the receiver address per link (RA), the source address (SA), and the destination address (DA).

Images