US20210112615A1

US20210112615A1 - Multi-link device data continuity

Info

Publication number: US20210112615A1
Application number: US17/127,668
Authority: US
Inventors: Po-Kai Huang; Daniel Bravo; Ofer Schreiber; Arik Klein; Laurent Cariou; Robert Stacey
Original assignee: Individual
Current assignee: Intel Corp
Priority date: 2020-12-18
Filing date: 2020-12-18
Publication date: 2021-04-15

Abstract

This disclosure describes systems, methods, and devices related to multi-link device (MLD) data continuity. An MLD device may set up one or more links with a station multi-link device (STA MLD), wherein the STA MLD comprises one or more logical entities defining separate station devices. The MLD device may transmit a data packet associated with a traffic identifier (TID) to the STA MLD. The MLD device may determine that the data packet was not received by the STA MLD. The MLD device may retransmit the data packet to the STA MLD. The MLD device may increment a retransmit counter every time the data packet is retransmitted. The MLD device may refrain from transmitting a second data packet until the data packet is dropped or successfully received by the STA MLD.

Description

TECHNICAL FIELD

This disclosure generally relates to systems and methods for wireless communications and, more particularly, to multi-link device (MLD) data continuity.

BACKGROUND

Wireless devices are becoming widely prevalent and are increasingly requesting access to wireless channels. The Institute of Electrical and Electronics Engineers (IEEE) is developing one or more standards that utilize Orthogonal Frequency-Division Multiple Access (OFDMA) in channel allocation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a network diagram illustrating an example network environment for multi-link device (MLD) data continuity, in accordance with one or more example embodiments of the present disclosure.

FIG. 2 depicts an illustrative schematic diagram for a multi-link device (MLD) between two logical entities, in accordance with one or more example embodiments of the present disclosure.

FIG. 3 depicts an illustrative schematic diagram for a multi-link device (MLD) between AP with logical entities and a non-AP with logical entities, in accordance with one or more example embodiments of the present disclosure.

FIG. 4 depicts an illustrative schematic diagram for a traditional single link operation, in accordance with one or more example embodiments of the present disclosure.

FIG. 5 illustrates a flow diagram of a process for an illustrative MLD data continuity system, in accordance with one or more example embodiments of the present disclosure.

FIG. 6 illustrates a functional diagram of an exemplary communication station that may be suitable for use as a user device, in accordance with one or more example embodiments of the present disclosure.

FIG. 7 illustrates a block diagram of an example machine upon which any of one or more techniques (e.g., methods) may be performed, in accordance with one or more example embodiments of the present disclosure.

FIG. 8 is a block diagram of a radio architecture in accordance with some examples.

FIG. 9 illustrates an example front-end module circuitry for use in the radio architecture of FIG. 8, in accordance with one or more example embodiments of the present disclosure.

FIG. 10 illustrates an example radio IC circuitry for use in the radio architecture of FIG. 8, in accordance with one or more example embodiments of the present disclosure.

FIG. 11 illustrates an example baseband processing circuitry for use in the radio architecture of FIG. 8, in accordance with one or more example embodiments of the present disclosure.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, algorithm, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.
Under multi-link framework, there is a question of whether individual addressed data or group addressed data without negotiated block acknowledgment (ACK) can be transmitted across links. Individual addressed data is data that is sent to one device at a time. Group addressed data is data that is sent to a plurality of devices at a time. There are two ways to transmit data. With block acknowledgment negotiation or without block acknowledgment negotiation. Block acknowledgment negotiation means that the transmitting device can send the data to the receiving device out of order. For example aggregating multiple data portions and sending them to the receiving device. In case one of the data portions is missed and only the rest of the data portions are received, the receiving device can wait to receive the portion that was missed. However without block acknowledgment negotiation, the transmitting device cannot transmit data in blocks or multiple portions. For example, the transmitting device may send a first portion of data, wait until finishing, then send a second portion of data.
If the individual addressed data or group addressed data without negotiated block ACK can be transmitted across links of an multi-link device (MLD), there is also a question how to detect duplicate data packets. It should be noted that due to the existence of legacy station device (STA) for different links, group addressed data that is actually broadcast needs to be transmitted across links to accommodate legacy STAs. It is not clear if same or different sequence number (SN) space will be used for this case.
There is no previous solution to enable data continuity under the framework of multi-link for data stream without block ACK negotiation.
Example embodiments of the present disclosure relate to systems, methods, and devices for a MLD data continuity without block acknowledgment (ACK) negotiation.
In one or more embodiments, a MLD data continuity system may facilitate at least two options for either individual addressed data or group addressed data without negotiated block ACK.
For individual addressed data without negotiated block ACK, a MLD data continuity system may allow the data to be transmitted across links and enhance a duplicate detection mechanism. Alternatively, the MLD data continuity system may only allow the data to be transmitted in one link at one time.
In one or more embodiments, MLD data continuity may enable the duplicate detection mechanism for individual addressed data under multiple links.
In one or more embodiments, for group addressed data without negotiated block ACK, due to the reason that group addressed data needs to be transmitted across links for legacy STAs, group addressed data is transmitted across links. The MLD data continuity system may facilitate that the same SN space may be used for transmitting group addressed data across links.
The MLD data continuity system may facilitate that different SN space is used for transmitting group addressed data across links and multi-link non-AP logical entity only takes group addressed from one link.
In one or more embodiments, MLD data continuity may enable the duplicate detection mechanism for group addressed data under both options.
In one or more embodiments, it is possible that there may be a transient period of deleting block acknowledgment (BA) and renegotiating BA, in the transient period, it may be possible to continue to transmit individual addressed data without negotiated block ACK rather than limiting the transmission.
In one or more embodiments, without enabling individual addressed data without negotiated block ACK to transmit across links, a mechanism is needed to identify the link that can be used for this transmission.
In one or more embodiments, avoiding taking duplicate group addressed data across links preserve the existing operation of discarding duplicate group addressed data.
The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, algorithms, etc., may exist, some of which are described in greater detail below. Example embodiments will now be described with reference to the accompanying figures.
FIG. 1 is a network diagram illustrating an example network environment of MLD data continuity, according to some example embodiments of the present disclosure. Wireless network 100 may include one or more user devices 120 and one or more access points(s) (AP) 102, which may communicate in accordance with IEEE 802.11 communication standards. The user device(s) 120 may be mobile devices that are non-stationary (e.g., not having fixed locations) or may be stationary devices.
In some embodiments, the user devices 120 and the AP 102 may include one or more computer systems similar to that of the functional diagram of FIG. 6 and/or the example machine/system of FIG. 7.
One or more illustrative user device(s) 120 and/or AP(s) 102 may be operable by one or more user(s) 110. It should be noted that any addressable unit may be a station (STA). An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of-service (QoS) STA, a dependent STA, and a hidden STA. The one or more illustrative user device(s) 120 and the AP(s) 102 may be STAs. The one or more illustrative user device(s) 120 and/or AP(s) 102 may operate as a personal basic service set (PBSS) control point/access point (PCP/AP). The user device(s) 120 (e.g., 124, 126, or 128) and/or AP(s) 102 may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static device. For example, user device(s) 120 and/or AP(s) 102 may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an Ultrabook™ computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (IoT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a “carry small live large” (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an “origami” device or computing device, a device that supports dynamically composable computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a set-top-box (STB), a blu-ray disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list.
As used herein, the term “Internet of Things (IoT) device” is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection. An IoT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like. An IoT device can have a particular set of attributes (e.g., a device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the IoT network. IoT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the IoT network may be comprised of a combination of “legacy” Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.).
The user device(s) 120 and/or AP(s) 102 may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3GPP standards.
Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to communicate with each other via one or more communications networks 130 and/or 135 wirelessly or wired. The user device(s) 120 may also communicate peer-to-peer or directly with each other with or without the AP(s) 102. Any of the communications networks 130 and/or 135 may include, but not limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks. Further, any of the communications networks 130 and/or 135 may have any suitable communication range associated therewith and may include, for example, global networks (e.g., the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs). In addition, any of the communications networks 130 and/or 135 may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.
Any of the user device(s) 120 (e.g., user devices 124, 126, 128) and AP(s) 102 may include one or more communications antennas. The one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the user device(s) 120 (e.g., user devices 124, 126 and 128), and AP(s) 102. Some non-limiting examples of suitable communications antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, or the like. The one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the user devices 120 and/or AP(s) 102.
Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like). Each of the multiple antenna arrays may be used for transmission and/or reception in a particular respective direction or range of directions. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional transmission towards one or more defined transmit sectors. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional reception from one or more defined receive sectors.
MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming. In some embodiments, in performing a given MIMO transmission, user devices 120 and/or AP(s) 102 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming.
Any of the user devices 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user device(s) 120 and AP(s) 102 to communicate with each other. The radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols. The radio components may further have hardware and/or software instructions to communicate via one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. In certain example embodiments, the radio component, in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g. 802.11b, 802.11g, 802.11n, 802.11ax), 5 GHz channels (e.g. 802.11n, 802.11ac, 802.11ax), or 60 GHZ channels (e.g. 802.11ad, 802.11ay). 800 MHz channels (e.g. 802.11ah). The communications antennas may operate at 28 GHz and 40 GHz. It should be understood that this list of communication channels in accordance with certain 802.11 standards is only a partial list and that other 802.11 standards may be used (e.g., Next Generation Wi-Fi, or other standards). In some embodiments, non-Wi-Fi protocols may be used for communications between devices, such as Bluetooth, dedicated short-range communication (DSRC), Ultra-High Frequency (UHF) (e.g. IEEE 802.11af, IEEE 802.22), white band frequency (e.g., white spaces), or other packetized radio communications. The radio component may include any known receiver and baseband suitable for communicating via the communications protocols. The radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and digital baseband.
In one embodiment, and with reference to FIG. 1, AP 102 may facilitate MLD data continuity 142 with one or more user devices 120.
In FIG. 1, there is shown that each of the user devices (STAs) is considered as an MLD, where the user device may comprise one or more logical entity devices. For example, it is shown that an AP MLD 102 may comprise AP1, . . . , AP N, where N is a positive integer and that STA MLD 124 may comprise STA 1, . . . , STA M, where M is a positive integer. The idea of using MLD is that a device (e.g., an AP STA or an STA MLD) can operate with multi-links and determine locally which link to use, without having to commit to using a specific link all the time.
It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.
FIG. 2 depicts an illustrative schematic diagram for a multi-link device (MLD) between two logical entities, in accordance with one or more example embodiments of the present disclosure.
Referring to FIG. 2, there are shown two multi-link logical entities on either side which includes multiple STAs that can set up links with each other. A multi-link logical entity may be a logical entity that contains one or more STAs. The logical entity has one MAC data service interface and primitives to the logical link control (LLC) and a single address associated with the interface, which can be used to communicate on the distribution system medium (DSM). It should be noted that a Multi-link logical entity allows STAs within the multi-link logical entity to have the same MAC address. It should also be noted that the exact name can be changed. A distribution system (DS) is a system to interconnect a set of networks. A DSM is used by the DS system for communicating between the set of networks (e.g., the internet). Each link may represent different bands.
In this example of FIG. 2, the multi-link logical entity 1 and multi-link logical entity 2 may be two separate physical devices, where each one comprises a number of virtual or logical devices. For example, multi-link logical entity 1 may comprise three STAs, STA1.1, STA1.2, and STA1.3 and multi-link logical entity 2 that may comprise three STAs, STA2.1, STA2.2, and STA2.3. The example shows that logical device STA1.1 is communicating with logical device STA2.1 over link 1, that logical device STA1.2 is communicating with logical device STA2.2 over link 2, and that device STA1.3 is communicating with logical device STA2.3 over link 3.
FIG. 3 depicts an illustrative schematic diagram for a multi-link device (MLD) between AP with logical entities and a non-AP with logical entities, in accordance with one or more example embodiments of the present disclosure.
Referring to FIG. 3, there are shown two multi-link logical entities on either side which includes multiple STAs that can set up links with each other. For infrastructure framework, a multi-link AP logical entity may include APs (e.g., AP1, AP2, and AP3) on one side, and multi-link non-AP logical entity, which may include non-APs (STA1, STA2, and STA3) on the other side. The detailed definition is shown below. Multi-link AP logical entity (AP MLLE also can be referred to as AP MLD): A multi-link logical entity, where each STA within the multi-link logical entity is an EHT AP. It should be noted that the term MLLE and MLD are interchangeable and indicate the same type of entity. Throughout this disclosure, MLLE may be used but anywhere the MLLE term is used, it can be replaced with MLD. Multi-link non-AP logical entity (non-AP MLLE, also can be referred to as non-AP MLD): A multi-link logical entity, where each STA within the multi-link logical entity is a non-AP EHT STA. It should be noted that this framework is a natural extension from the one link operation between two STAs, which are AP and non-AP STA under the infrastructure framework (e.g., when an AP is used as a medium for communication between STAs).
In the example of FIG. 3, the multi-link AP logical entity and multi-link non-AP logical entity may be two separate physical devices, where each one comprises a number of virtual or logical devices. For example, the multi-link AP logical entity may comprise three APs, AP1 operating on 2.4 GHz, AP2 operating on 5 GHz, and AP3 operating on 6 GHz. Further, the multi-link non-AP logical entity may comprise three non-AP STAs, STA1 communicating with AP1 on link 1, STA2 communicating with AP2 on link 2, and STA3 communicating with AP3 on link 3.
The multi-link AP logical entity is shown in FIG. 3 to have access to a distribution system (DS), which is a system used to interconnect a set of BSSs to create an extended service set (ESS). The multi-link AP logical entity is also shown in FIG. 3 to have access a distribution system medium (DSM), which is the medium used by a DS for BSS interconnections. Simply put, DS and DSM allow the AP to communicate with different BSSs.
It should be understood that although the example shows three logical entities within the multi-link AP logical entity and the three logical entities within the multi-link non-AP logical entity, this is merely for illustration purposes and that other numbers of logical entities with each of the multi-link AP and non-AP logical entities may be envisioned.
FIG. 4 depicts an illustrative schematic diagram for a traditional single link operation, in accordance with one or more example embodiments of the present disclosure.
Referring to FIG. 4, there are shown data transmission without block ACK negotiation in a traditional way as opposed to using MLD.
Under traditional single link operation, when the link is setup through association, each STA can send individual addressed data for any TID without BA negotiation to each other.
In WLAN, packets can be a stream of video, voice, or data which each has different priority to be served by an AP device. Traffic Identifier (TID) is an identifier used to classify a packet in Wireless LAN. A QoS-enabled MAC layer of 802.11 protocol stack uses the TIDs to classify and prioritizes processing of incoming or outgoing frames. When a device (e.g., an AP or an STA) receives an 802.11 frame with TID set for audio, for example, the priority is given higher than a data frame for best effort purpose.
The data stream of each TID (for individual addressed data) is sent by the transmitter in order since the receiver cannot do reorder for “out of order” data packets. Specifically, each transmitter sends one data packet with sequence number x until it is acknowledged or dropped due to too many retry, then the transmitter continues with sending the sequence number larger than x.
In one or more embodiments, a MLD data continuityMLD data continuity system may facilitate that for group addressed data without block ACK negotiation (i.e., GCR-BA), there are three methods:
1) Groupcast without retries. In this case, group addressed data are just transmitted in sequence without retransmission.
2) Groupcast with retries (GCR): a) Direct Multicast Service (DMS). In this case, group addressed data are converted to individual addressed data.
3) GCR unsolicited retry: In this case, group addressed data with sequence number x are retried for a fixed amount of times without any acknowledgement before moving on to the next group addressed data with sequence number larger than x.
A retry rule for retry and duplicate detection without block ACK negotiation is described as follows: based on retransmit procedures, a short retry counter (SRC) is associated with each MAC service data unit (MSDU) or MAC management protocol data unit (MMPDU). Then a retry continues for each failing frame exchange until the transmission is successful or until the retry limit is reached, whichever occurs first. For example, a QoS STA may maintain a short retry counter for each MSDU, A-MSDU, or MMPDU that belongs to a TC that requires acknowledgment, and one retry limit. If the retry counter limit is reached, then the data will stop been retransmitted.
After transmitting a frame that requires an immediate acknowledgment, the STA may perform either of the acknowledgment procedures, as appropriate, (Acknowledgment procedure). The short retry counter for an MSDU or A-MSDU that is not part of a block ACK agreement or for an MMPDU may be incremented every time transmission fails for that MSDU, A-MSDU, or MMPDU, including of an associated RTS.
All retransmission attempts by a non-DMG STA for an MPDU with the Type subfield equal to Data or Management that is not sent under a block ACK agreement and that has failed the acknowledgment procedure one or more times may be made with the Retry subfield set to 1.
Retries for failed transmission attempts may continue until one or more of the following conditions occurs:

- The short retry count for the MSDU, A-MSDU, or MMPDU is equal to dot11ShortRetryLimit.
- The short drop-eligible retry count for the MSDU, A-MSDU, or MMPDU is equal to dot11ShortDEIRetryLimit.
- The long drop-eligible retry count for the MSDU, A-MSDU, or MMPDU is equal to dot11LongDEIRetryLimit.
- The unsolicited retry count for the A-MSDU is equal to dot11UnsolicitedRetryLimit.

When any of these limits is reached, retry attempts may cease, and the MSDU, A-MSDU, or MMPDU may be discarded.
With the exception of a frame belonging to a TID for which block ACK agreement is set up, a QoS STA may not initiate the transmission of any Management or Data frame to a specific RA while the transmission of another Management or Data frame with the same RA and having been assigned its sequence number from the same sequence counter has not yet completed to the point of success, retry fail, or other MAC discard (e.g., lifetime expiration). The lifetime expiration of an MAC service data unit (MSDU) lifetime indicate that if the lifetime of the data expires, then the data is dropped.
Typically, receiver caches, the receiver records at least the most recent cache entry per <Address 2, TID> pair in this cache. Each entry is indexed by: <Address 2, TID, sequence number, fragment number>.
Then the receiver STA may discard the frame if the Retry subfield of the Frame Control field is 1 and it matches an entry in the cache.
Note that for individual addressed data, there are independent sequence number space for different TIDs. Then for group addressed data, there is one sequence number space for all TIDs shared together with non-QoS data.
Also note that the receiver record does not differentiate individual addressed, where A1 is the individual address, or group addressed, where A1 is multicast address or broadcast address. The reason is that the transmitter will always move on sequence number space if finishing the current transmission.
In one or more embodiments, a MLD data continuity system may have shared SN space for individual addressed data of a specific TID intended for a multi-link logical entity. The address to the other side on each link is the address of the corresponding STA of peer multi-link logical entity. Although the address of peer STA could be different in different link, they are all to the same multi-link logical entity.
In one or more embodiments, a MLD data continuityMLD data continuity may facilitate a mechanism for duplicate detection at the receiving device.
In one or more embodiments, in Option 1, a MLD data continuity system may facilitate a multi-link logical entity and have a common receiver cache record for duplicate detection. Address 2 in the index is replaced by the corresponding address of the multi-link logical entity of the transmitter STA. Note that different receiver cache record under shared SN space without synchronization among STAs in a multi-link logical entity can cause the STAs in different link to take duplicate packets. Specifically, the record may show one packet as duplicate in one link and not duplicate in another link. As a result, same duplicate detection record across link is required when SN space is shared.
In one or more embodiments, in Option 2, the receiver adopts the same procedure of duplicate detection with BA agreement by maintaining a window with [Expected SN, expected SN+2{circumflex over ( )}11]. Expected SN is equal to latest received SN plus 1. The operation considers mod 2{circumflex over ( )}12. The Receiver drops all MPDUs with SN that is not in the window. The transmitter can send a special frame to move the expected SN of the receiver. The frame can reuse block acknowledgement request (BAR) frame.
In one or more embodiments, a MLD data continuity system may extend the following short retry counter maintenance to a multi-link logical entity as described here: “A multi-link logical entity affiliated with QoS STAs may maintain a short retry counter for each MSDU, A-MSDU, or MMPDU intended for a multi-link logical entity that belongs to a TC that requires acknowledgment.”
Note that this may not just be based on RA because addresses of different STAs in different link may be different.
In one or more embodiments, a MLD data continuity system may modify the retransmission rule without block ACK agreement to multi-link as follows:
“With the exception of a frame belonging to a TID for which block ACK agreement is set up, a multi-link logical entity with QoS EHT STAs may not initiate the transmission of any Management or Data frame to a specific peer multi-link logical entity with QoS EHT STAs while the transmission of another Management or Data frame to the specific peer multi-link logical entity with EHT QoS STAs and having been assigned its sequence number from the same sequence counter has not yet completed to the point of success in any of the links, retry fail without success in any of the links, or other MAC discard (e.g., lifetime expiration).”
Note that this cannot be just based on RA because addresses of different STAs in different link may be different. Further detailed proposal may be shown below for individual addressed frame without block ACK agreement for two options:
In one or more embodiments, in Option 1, a MLD data continuityMLD data continuity system may allow the individually addressed frames of a TID without block ACK agreement to be transmitted across links with the detailed operation listed below:

- Retry bit of MPDU transmission is always set for all transmission.
- Initially, MPDU of a TID with SN x can be sent in any of the links.
- MPDU of the TID with following SN can be sent on the link for which it has been acknowledged.
- MPDU of the TID with following SN can be sent on the link for which an acknowledgement of SN x has not been received, if specific conditions are satisfied. One condition can be that a certain amount of time has passed. This time can be the processing delay of the link getting acknowledgement. This time can be explicitly indicated by the multi-link logical entity. This time can be implicitly indicated based on a predefined parameters. Another condition can be that the corresponding multi-link logical entity of the receiver indicated specifically in a separate frame to allow further transmission of MPDU of the TID with the following SN. Another condition can be that the corresponding multi-link logical entity of the transmitter sends a frame to check if the peer multi-link logical entity is available for reception of a frame with following SN value in different link.

In one or more embodiments, in Option 2, a MLD data continuityMLD data continuity system may facilitate to only allow the individually addressed frames of a TID without block ACK agreement to be transmitted in a single link. Specific signaling is required for indicating which link is allowed to take individually addressed traffic for each TID without negotiated BA. The signaling allows changes for the link that is allowed to take individual addressed traffic without negotiated BA. The signaling can allow different links for taking individual addressed traffic without negotiated BA for different TIDs.
The above two options can be expanded to individual addressed not non-QoS data.
In one or more embodiments, a MLD data continuity system may facilitated further detailed proposal for group addressed frame or not QoS individual addressed data without block ACK agreement for two options:
Option 1: Multi-link AP logical entity uses shared SN space for the group addressed frame or not QoS individual addressed data transmitted across links.
Specifically, a transmitter sequence number spaces, SNS1 may be expanded to transmission of multi-link AP logical entity across links.
In one or more embodiments, a MLD data continuity system may revise the duplicate detection mechanism for group addressed traffic by dropping MPDUs with SN for group addressed frame outside a window equal to [expected SN, expected SN+threshold).
The calculation in the window considers mod operation of 4096.
A separate window can be provided for individual addressed not QoS data.
Multi-link AP logical entity makes sure that it has SN difference across links bounded at any time (ILatest_transmitted_SN_in_link_i−latest_transmitted_SN_in_link_jl mod 4096<4096−threshold).
Due to the reason that non-QoS data shared the same SN space as group addressed data, this means that non-QoS data to one multi-link logical entity also uses the same SN space across links.
An alternative option is to determine that STA may maintain at least two records for not QoS data transmission:
One for individual addressed not QoS data Indexed by: <I, Address 2, sequence number, fragment number>.
One for group addressed not QoS data Indexed by: <G, Address 2, sequence number, fragment number>.
Option 2: Multi-link AP logical entity uses different SN space for the group addressed frame transmitted or not QoS individual addressed data in different links
On the receiver side, to simplify the operation, a multi-link non-AP logical entity may be maintained and may only take the group addressed frame without block ACK agreement in one link at one time for either option above.
Two additional conditions for switching can be described below:
A Duplicate condition can be added for the switching of the links that take group addressed frame: At one time, if there is a group traffic not transmitted in the potential group addressed link but transmitted in current group addressed link, then the multi-link non-AP logical entity may not switch the group addressed link without duplicate detection mechanism.
A Missing condition can be added for the switching of the links that take group addressed frame: At one time, if there is a group traffic transmitted in the potential group addressed link but not transmitted in current group addressed link, then the multi-link non-AP logical entity should not switch the group addressed link (may not). It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.
FIG. 5 illustrates a flow diagram of illustrative process 500 for a MLD data continuity system, in accordance with one or more example embodiments of the present disclosure.
At block 502, a device (e.g., the user device(s) 120 and/or the AP 102 of FIG. 1) may set up one or more links with a station multi-link device (STA MLD), wherein the STA MLD may comprise one or more logical entities defining separate station devices.
At block 504, the device may transmit a data packet associated with a traffic identifier (TID) to the STA MLD. The data packet is retransmitted until the retransmit counter reaches exceeds a retransmit threshold or until a lifetime timer of the data packet expires. The data packet associated with TID is sent without negotiating a block acknowledgment agreement with the STA MLD. The data packet is sent on any of the one or more links that are set up with the STA MLD. The data packet is transmitted using a first sequence number (SN) in a sequence number space associated with the TID for the STA MLD. The data packet is individually addressed to the STA MLD. The data packet is addressed to a group of station devices. The data packet is transmitted across the one or more links when the data packet is addressed to a group of station devices. The data packet is transmitted with individual addressed data without negotiated block acknowledgment.
At block 506, the device may determine that the data packet was not received by the STA MLD.
At block 508, the device may retransmit the data packet to the STA MLD.
At block 510, the device may increment a retransmit counter every time the data packet is retransmitted.
At block 512, the device may refrain from transmitting a second data packet until the data packet is dropped or successfully received by the STA MLD.
It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.
FIG. 6 shows a functional diagram of an exemplary communication station 600, in accordance with one or more example embodiments of the present disclosure. In one embodiment, FIG. 6 illustrates a functional block diagram of a communication station that may be suitable for use as an AP 102 (FIG. 1) or a user device 120 (FIG. 1) in accordance with some embodiments. The communication station 600 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.
The communication station 600 may include communications circuitry 602 and a transceiver 610 for transmitting and receiving signals to and from other communication stations using one or more antennas 601. The communications circuitry 602 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication station 600 may also include processing circuitry 606 and memory 608 arranged to perform the operations described herein. In some embodiments, the communications circuitry 602 and the processing circuitry 606 may be configured to perform operations detailed in the above figures, diagrams, and flows.
In accordance with some embodiments, the communications circuitry 602 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 602 may be arranged to transmit and receive signals. The communications circuitry 602 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 606 of the communication station 600 may include one or more processors. In other embodiments, two or more antennas 601 may be coupled to the communications circuitry 602 arranged for sending and receiving signals. The memory 608 may store information for configuring the processing circuitry 606 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 608 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 608 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.
In some embodiments, the communication station 600 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
In some embodiments, the communication station 600 may include one or more antennas 601. The antennas 601 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.
In some embodiments, the communication station 600 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.
Although the communication station 600 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication station 600 may refer to one or more processes operating on one or more processing elements.
Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. In some embodiments, the communication station 600 may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
FIG. 7 illustrates a block diagram of an example of a machine 700 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed. In other embodiments, the machine 700 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 700 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 700 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environments. The machine 700 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station. Further, while only a single machine is illustrated, the term “machine” may also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), or other computer cluster configurations.
Examples, as described herein, may include or may operate on logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations when operating. A module includes hardware. In an example, the hardware may be specifically configured to carry out a specific operation (e.g., hardwired). In another example, the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the executions units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating. In this example, the execution units may be a member of more than one module. For example, under operation, the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time.
The machine (e.g., computer system) 700 may include a hardware processor 702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 704 and a static memory 706, some or all of which may communicate with each other via an interlink (e.g., bus) 708. The machine 700 may further include a power management device 732, a graphics display device 710, an alphanumeric input device 712 (e.g., a keyboard), and a user interface (UI) navigation device 714 (e.g., a mouse). In an example, the graphics display device 710, alphanumeric input device 712, and UI navigation device 714 may be a touch screen display. The machine 700 may additionally include a storage device (i.e., drive unit) 716, a signal generation device 718 (e.g., a speaker), a MLD data continuity device 719, a network interface device/transceiver 720 coupled to antenna(s) 730, and one or more sensors 728, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The machine 700 may include an output controller 734, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)). The operations in accordance with one or more example embodiments of the present disclosure may be carried out by a baseband processor. The baseband processor may be configured to generate corresponding baseband signals. The baseband processor may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with the hardware processor 702 for generation and processing of the baseband signals and for controlling operations of the main memory 704, the storage device 716, and/or the MLD data continuity device 719. The baseband processor may be provided on a single radio card, a single chip, or an integrated circuit (IC).
The storage device 716 may include a machine readable medium 722 on which is stored one or more sets of data structures or instructions 724 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 724 may also reside, completely or at least partially, within the main memory 704, within the static memory 706, or within the hardware processor 702 during execution thereof by the machine 700. In an example, one or any combination of the hardware processor 702, the main memory 704, the static memory 706, or the storage device 716 may constitute machine-readable media.
The MLD data continuity device 719 may carry out or perform any of the operations and processes (e.g., process 500) described and shown above.
It is understood that the above are only a subset of what the MLD data continuity device 719 may be configured to perform and that other functions included throughout this disclosure may also be performed by the MLD data continuity device 719.
While the machine-readable medium 722 is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 724.
Various embodiments may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.
The term “machine-readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 700 and that cause the machine 700 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memories and optical and magnetic media. In an example, a massed machine-readable medium includes a machine-readable medium with a plurality of particles having resting mass. Specific examples of massed machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
The instructions 724 may further be transmitted or received over a communications network 726 using a transmission medium via the network interface device/transceiver 720 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), plain old telephone (POTS) networks, wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, among others. In an example, the network interface device/transceiver 720 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 726. In an example, the network interface device/transceiver 720 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term “transmission medium” may be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 700 and includes digital or analog communications signals or other intangible media to facilitate communication of such software.
The operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed.
FIG. 8 is a block diagram of a radio architecture 105A, 105B in accordance with some embodiments that may be implemented in any one of the example AP 102 and/or the example STA 120 of FIG. 1. Radio architecture 105A, 105B may include radio front-end module (FEM) circuitry 804 a-b, radio IC circuitry 806 a-b and baseband processing circuitry 808 a-b. Radio architecture 105A, 105B as shown includes both Wireless Local Area Network (WLAN) functionality and Bluetooth (BT) functionality although embodiments are not so limited. In this disclosure, “WLAN” and “Wi-Fi” are used interchangeably.
FEM circuitry 804 a-b may include a WLAN or Wi-Fi FEM circuitry 804 a and a Bluetooth (BT) FEM circuitry 804 b. The WLAN FEM circuitry 804 a may include a receive signal path comprising circuitry configured to operate on WLAN RF signals received from one or more antennas 801, to amplify the received signals and to provide the amplified versions of the received signals to the WLAN radio IC circuitry 806 a for further processing. The BT FEM circuitry 804 b may include a receive signal path which may include circuitry configured to operate on BT RF signals received from one or more antennas 801, to amplify the received signals and to provide the amplified versions of the received signals to the BT radio IC circuitry 806 b for further processing. FEM circuitry 804 a may also include a transmit signal path which may include circuitry configured to amplify WLAN signals provided by the radio IC circuitry 806 a for wireless transmission by one or more of the antennas 801. In addition, FEM circuitry 804 b may also include a transmit signal path which may include circuitry configured to amplify BT signals provided by the radio IC circuitry 806 b for wireless transmission by the one or more antennas. In the embodiment of FIG. 8, although FEM 804 a and FEM 804 b are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of an FEM (not shown) that includes a transmit path and/or a receive path for both WLAN and BT signals, or the use of one or more FEM circuitries where at least some of the FEM circuitries share transmit and/or receive signal paths for both WLAN and BT signals.
Radio IC circuitry 806 a-b as shown may include WLAN radio IC circuitry 806 a and BT radio IC circuitry 806 b. The WLAN radio IC circuitry 806 a may include a receive signal path which may include circuitry to down-convert WLAN RF signals received from the FEM circuitry 804 a and provide baseband signals to WLAN baseband processing circuitry 808 a. BT radio IC circuitry 806 b may in turn include a receive signal path which may include circuitry to down-convert BT RF signals received from the FEM circuitry 804 b and provide baseband signals to BT baseband processing circuitry 808 b. WLAN radio IC circuitry 806 a may also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WLAN baseband processing circuitry 808 a and provide WLAN RF output signals to the FEM circuitry 804 a for subsequent wireless transmission by the one or more antennas 801. BT radio IC circuitry 806 b may also include a transmit signal path which may include circuitry to up-convert BT baseband signals provided by the BT baseband processing circuitry 808 b and provide BT RF output signals to the FEM circuitry 804 b for subsequent wireless transmission by the one or more antennas 801. In the embodiment of FIG. 8, although radio IC circuitries 806 a and 806 b are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of a radio IC circuitry (not shown) that includes a transmit signal path and/or a receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuitries where at least some of the radio IC circuitries share transmit and/or receive signal paths for both WLAN and BT signals.
Baseband processing circuitry 808 a-b may include a WLAN baseband processing circuitry 808 a and a BT baseband processing circuitry 808 b. The WLAN baseband processing circuitry 808 a may include a memory, such as, for example, a set of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the WLAN baseband processing circuitry 808 a. Each of the WLAN baseband circuitry 808 a and the BT baseband circuitry 808 b may further include one or more processors and control logic to process the signals received from the corresponding WLAN or BT receive signal path of the radio IC circuitry 806 a-b, and to also generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuitry 806 a-b. Each of the baseband processing circuitries 808 a and 808 b may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with a device for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 806 a-b.
Referring still to FIG. 8, according to the shown embodiment, WLAN-BT coexistence circuitry 813 may include logic providing an interface between the WLAN baseband circuitry 808 a and the BT baseband circuitry 808 b to enable use cases requiring WLAN and BT coexistence. In addition, a switch 803 may be provided between the WLAN FEM circuitry 804 a and the BT FEM circuitry 804 b to allow switching between the WLAN and BT radios according to application needs. In addition, although the antennas 801 are depicted as being respectively connected to the WLAN FEM circuitry 804 a and the BT FEM circuitry 804 b, embodiments include within their scope the sharing of one or more antennas as between the WLAN and BT FEMs, or the provision of more than one antenna connected to each of FEM 804 a or 804 b.
In some embodiments, the front-end module circuitry 804 a-b, the radio IC circuitry 806 a-b, and baseband processing circuitry 808 a-b may be provided on a single radio card, such as wireless radio card 802. In some other embodiments, the one or more antennas 801, the FEM circuitry 804 a-b and the radio IC circuitry 806 a-b may be provided on a single radio card. In some other embodiments, the radio IC circuitry 806 a-b and the baseband processing circuitry 808 a-b may be provided on a single chip or integrated circuit (IC), such as IC 812.
In some embodiments, the wireless radio card 802 may include a WLAN radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments, the radio architecture 105A, 105B may be configured to receive and transmit orthogonal frequency division multiplexed (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals over a multicarrier communication channel. The OFDM or OFDMA signals may comprise a plurality of orthogonal subcarriers.
In some of these multicarrier embodiments, radio architecture 105A, 105B may be part of a Wi-Fi communication station (STA) such as a wireless access point (AP), a base station or a mobile device including a Wi-Fi device. In some of these embodiments, radio architecture 105A, 105B may be configured to transmit and receive signals in accordance with specific communication standards and/or protocols, such as any of the Institute of Electrical and Electronics Engineers (IEEE) standards including, 802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, 802.11n-2009, 802.11ac, 802.11ah, 802.11ad, 802.11 ay and/or 802.11ax standards and/or proposed specifications for WLANs, although the scope of embodiments is not limited in this respect. Radio architecture 105A, 105B may also be suitable to transmit and/or receive communications in accordance with other techniques and standards.
In some embodiments, the radio architecture 105A, 105B may be configured for high-efficiency Wi-Fi (HEW) communications in accordance with the IEEE 802.11ax standard. In these embodiments, the radio architecture 105A, 105B may be configured to communicate in accordance with an OFDMA technique, although the scope of the embodiments is not limited in this respect.
In some other embodiments, the radio architecture 105A, 105B may be configured to transmit and receive signals transmitted using one or more other modulation techniques such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)), time-division multiplexing (TDM) modulation, and/or frequency-division multiplexing (FDM) modulation, although the scope of the embodiments is not limited in this respect.
In some embodiments, as further shown in FIG. 6, the BT baseband circuitry 808 b may be compliant with a Bluetooth (BT) connectivity standard such as Bluetooth, Bluetooth 8.0 or Bluetooth 6.0, or any other iteration of the Bluetooth Standard.
In some embodiments, the radio architecture 105A, 105B may include other radio cards, such as a cellular radio card configured for cellular (e.g., SGPP such as LTE, LTE-Advanced or 7G communications).
In some IEEE 802.11 embodiments, the radio architecture 105A, 105B may be configured for communication over various channel bandwidths including bandwidths having center frequencies of about 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of about 2 MHz, 4 MHz, 5 MHz, 5.5 MHz, 6 MHz, 8 MHz, 10 MHz, 20 MHz, 40 MHz, 80 MHz (with contiguous bandwidths) or 80+80 MHz (160 MHz) (with non-contiguous bandwidths). In some embodiments, a 920 MHz channel bandwidth may be used. The scope of the embodiments is not limited with respect to the above center frequencies however.
FIG. 9 illustrates WLAN FEM circuitry 804 a in accordance with some embodiments. Although the example of FIG. 9 is described in conjunction with the WLAN FEM circuitry 804 a, the example of FIG. 9 may be described in conjunction with the example BT FEM circuitry 804 b (FIG. 8), although other circuitry configurations may also be suitable.
In some embodiments, the FEM circuitry 804 a may include a TX/RX switch 902 to switch between transmit mode and receive mode operation. The FEM circuitry 804 a may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 804 a may include a low-noise amplifier (LNA) 906 to amplify received RF signals 903 and provide the amplified received RF signals 907 as an output (e.g., to the radio IC circuitry 806 a-b (FIG. 8)). The transmit signal path of the circuitry 804 a may include a power amplifier (PA) to amplify input RF signals 909 (e.g., provided by the radio IC circuitry 806 a-b), and one or more filters 912, such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters, to generate RF signals 915 for subsequent transmission (e.g., by one or more of the antennas 801 (FIG. 8)) via an example duplexer 914.
In some dual-mode embodiments for Wi-Fi communication, the FEM circuitry 804 a may be configured to operate in either the 2.4 GHz frequency spectrum or the 5 GHz frequency spectrum. In these embodiments, the receive signal path of the FEM circuitry 804 a may include a receive signal path duplexer 904 to separate the signals from each spectrum as well as provide a separate LNA 906 for each spectrum as shown. In these embodiments, the transmit signal path of the FEM circuitry 804 a may also include a power amplifier 910 and a filter 912, such as a BPF, an LPF or another type of filter for each frequency spectrum and a transmit signal path duplexer 904 to provide the signals of one of the different spectrums onto a single transmit path for subsequent transmission by the one or more of the antennas 801 (FIG. 8). In some embodiments, BT communications may utilize the 2.4 GHz signal paths and may utilize the same FEM circuitry 804 a as the one used for WLAN communications.
FIG. 10 illustrates radio IC circuitry 806 a in accordance with some embodiments. The radio IC circuitry 806 a is one example of circuitry that may be suitable for use as the WLAN or BT radio IC circuitry 806 a/806 b (FIG. 8), although other circuitry configurations may also be suitable. Alternatively, the example of FIG. 10 may be described in conjunction with the example BT radio IC circuitry 806 b.
In some embodiments, the radio IC circuitry 806 a may include a receive signal path and a transmit signal path. The receive signal path of the radio IC circuitry 806 a may include at least mixer circuitry 1002, such as, for example, down-conversion mixer circuitry, amplifier circuitry 1006 and filter circuitry 1008. The transmit signal path of the radio IC circuitry 806 a may include at least filter circuitry 1012 and mixer circuitry 1014, such as, for example, up-conversion mixer circuitry. Radio IC circuitry 806 a may also include synthesizer circuitry 1004 for synthesizing a frequency 1005 for use by the mixer circuitry 1002 and the mixer circuitry 1014. The mixer circuitry 1002 and/or 1014 may each, according to some embodiments, be configured to provide direct conversion functionality. The latter type of circuitry presents a much simpler architecture as compared with standard super-heterodyne mixer circuitries, and any flicker noise brought about by the same may be alleviated for example through the use of OFDM modulation. FIG. 10 illustrates only a simplified version of a radio IC circuitry, and may include, although not shown, embodiments where each of the depicted circuitries may include more than one component. For instance, mixer circuitry 1014 may each include one or more mixers, and filter circuitries 1008 and/or 1012 may each include one or more filters, such as one or more BPFs and/or LPFs according to application needs. For example, when mixer circuitries are of the direct-conversion type, they may each include two or more mixers.
In some embodiments, mixer circuitry 1002 may be configured to down-convert RF signals 907 received from the FEM circuitry 804 a-b (FIG. 8) based on the synthesized frequency 1005 provided by synthesizer circuitry 1004. The amplifier circuitry 1006 may be configured to amplify the down-converted signals and the filter circuitry 1008 may include an LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals 1007. Output baseband signals 1007 may be provided to the baseband processing circuitry 808 a-b (FIG. 8) for further processing. In some embodiments, the output baseband signals 1007 may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1002 may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
In some embodiments, the mixer circuitry 1014 may be configured to up-convert input baseband signals 1011 based on the synthesized frequency 1005 provided by the synthesizer circuitry 1004 to generate RF output signals 909 for the FEM circuitry 804 a-b. The baseband signals 1011 may be provided by the baseband processing circuitry 808 a-b and may be filtered by filter circuitry 1012. The filter circuitry 1012 may include an LPF or a BPF, although the scope of the embodiments is not limited in this respect.
In some embodiments, the mixer circuitry 1002 and the mixer circuitry 1014 may each include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion respectively with the help of synthesizer 1004. In some embodiments, the mixer circuitry 1002 and the mixer circuitry 1014 may each include two or more mixers each configured for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1002 and the mixer circuitry 1014 may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuitry 1002 and the mixer circuitry 1014 may be configured for super-heterodyne operation, although this is not a requirement.
Mixer circuitry 1002 may comprise, according to one embodiment: quadrature passive mixers (e.g., for the in-phase (I) and quadrature phase (Q) paths). In such an embodiment, RF input signal 907 from FIG. 10 may be down-converted to provide I and Q baseband output signals to be sent to the baseband processor.
Quadrature passive mixers may be driven by zero and ninety-degree time-varying LO switching signals provided by a quadrature circuitry which may be configured to receive a LO frequency (fLO) from a local oscillator or a synthesizer, such as LO frequency 1005 of synthesizer 1004 (FIG. 10). In some embodiments, the LO frequency may be the carrier frequency, while in other embodiments, the LO frequency may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the zero and ninety-degree time-varying switching signals may be generated by the synthesizer, although the scope of the embodiments is not limited in this respect.
In some embodiments, the LO signals may differ in duty cycle (the percentage of one period in which the LO signal is high) and/or offset (the difference between start points of the period). In some embodiments, the LO signals may have an 85% duty cycle and an 80% offset. In some embodiments, each branch of the mixer circuitry (e.g., the in-phase (I) and quadrature phase (Q) path) may operate at an 80% duty cycle, which may result in a significant reduction is power consumption.
The RF input signal 907 (FIG. 9) may comprise a balanced signal, although the scope of the embodiments is not limited in this respect. The I and Q baseband output signals may be provided to low-noise amplifier, such as amplifier circuitry 1006 (FIG. 10) or to filter circuitry 1008 (FIG. 10).
In some embodiments, the output baseband signals 1007 and the input baseband signals 1011 may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals 1007 and the input baseband signals 1011 may be digital baseband signals. In these alternate embodiments, the radio IC circuitry may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry.
In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, or for other spectrums not mentioned here, although the scope of the embodiments is not limited in this respect.
In some embodiments, the synthesizer circuitry 1004 may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1004 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. According to some embodiments, the synthesizer circuitry 1004 may include digital synthesizer circuitry. An advantage of using a digital synthesizer circuitry is that, although it may still include some analog components, its footprint may be scaled down much more than the footprint of an analog synthesizer circuitry. In some embodiments, frequency input into synthesizer circuitry 1004 may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. A divider control input may further be provided by either the baseband processing circuitry 808 a-b (FIG. 8) depending on the desired output frequency 1005. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table (e.g., within a Wi-Fi card) based on a channel number and a channel center frequency as determined or indicated by the example application processor 810. The application processor 810 may include, or otherwise be connected to, one of the example secure signal converter 101 or the example received signal converter 103 (e.g., depending on which device the example radio architecture is implemented in).
In some embodiments, synthesizer circuitry 1004 may be configured to generate a carrier frequency as the output frequency 1005, while in other embodiments, the output frequency 1005 may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the output frequency 1005 may be a LO frequency (fLO).
FIG. 11 illustrates a functional block diagram of baseband processing circuitry 808 a in accordance with some embodiments. The baseband processing circuitry 808 a is one example of circuitry that may be suitable for use as the baseband processing circuitry 808 a (FIG. 8), although other circuitry configurations may also be suitable. Alternatively, the example of FIG. 10 may be used to implement the example BT baseband processing circuitry 808 b of FIG. 8.
The baseband processing circuitry 808 a may include a receive baseband processor (RX BBP) 1102 for processing receive baseband signals 1009 provided by the radio IC circuitry 806 a-b (FIG. 8) and a transmit baseband processor (TX BBP) 1104 for generating transmit baseband signals 1011 for the radio IC circuitry 806 a-b. The baseband processing circuitry 808 a may also include control logic 1106 for coordinating the operations of the baseband processing circuitry 808 a.
In some embodiments (e.g., when analog baseband signals are exchanged between the baseband processing circuitry 808 a-b and the radio IC circuitry 806 a-b), the baseband processing circuitry 808 a may include ADC 1110 to convert analog baseband signals 1109 received from the radio IC circuitry 806 a-b to digital baseband signals for processing by the RX BBP 1102. In these embodiments, the baseband processing circuitry 808 a may also include DAC 1112 to convert digital baseband signals from the TX BBP 1104 to analog baseband signals 1111.
In some embodiments that communicate OFDM signals or OFDMA signals, such as through baseband processor 808 a, the transmit baseband processor 1104 may be configured to generate OFDM or OFDMA signals as appropriate for transmission by performing an inverse fast Fourier transform (IFFT). The receive baseband processor 1102 may be configured to process received OFDM signals or OFDMA signals by performing an FFT. In some embodiments, the receive baseband processor 1102 may be configured to detect the presence of an OFDM signal or OFDMA signal by performing an autocorrelation, to detect a preamble, such as a short preamble, and by performing a cross-correlation, to detect a long preamble. The preambles may be part of a predetermined frame structure for Wi-Fi communication.
Referring back to FIG. 8, in some embodiments, the antennas 801 (FIG. 8) may each comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result. Antennas 801 may each include a set of phased-array antennas, although embodiments are not so limited.
Although the radio architecture 105A, 105B is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.
The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. The terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device. The device may be either mobile or stationary.
As used within this document, the term “communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed. The term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.
As used herein, unless otherwise specified, the use of the ordinal adjectives “first,” “second,” “third,” etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.
The term “access point” (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art. Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards.
Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like.
Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multi-standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.
Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra-wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, long term evolution (LTE), LTE advanced, enhanced data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks.
The following examples pertain to further embodiments.
Example 1 may include an multi-link device (MLD) device comprising processing circuitry coupled to storage, the processing circuitry configured to: set up one or more links with a station multi-link device (STA MLD), wherein the STA MLD comprises one or more logical entities defining separate station devices; transmit a data packet associated with a traffic identifier (TID) to the STA MLD; determine that the data packet was not received by the STA MLD; retransmit the data packet to the STA MLD; increment a retransmit counter every time the data packet may be retransmitted; and refrain from transmitting a second data packet until the data packet may be dropped or successfully received by the STA MLD.
Example 2 may include the MLD device of example 1 and/or some other example herein, wherein the data packet may be retransmitted until the retransmit counter reaches exceeds a retransmit threshold or until a lifetime timer of the data packet expires.
Example 3 may include the MLD device of example 2 and/or some other example herein, wherein the data packet associated with TID may be sent without negotiating a block acknowledgment agreement with the STA MLD.
Example 4 may include the MLD device of example 2 and/or some other example herein, wherein the data packet may be sent on any of the one or more links that are set up with the STA MLD.
Example 5 may include the MLD device of example 1 and/or some other example herein, wherein the data packet may be transmitted using a first sequence number (SN) in a sequence number space associated with the TID for the STA MLD.
Example 6 may include the MLD device of example 1 and/or some other example herein, wherein the data packet may be individually addressed to the STA MLD.
Example 7 may include the MLD device of example 1 and/or some other example herein, wherein the data packet may be addressed to a group of station devices.
Example 8 may include the MLD device of example 1 and/or some other example herein, wherein the data packet may be transmitted across the one or more links when the data packet may be addressed to a group of station devices.
Example 9 may include the MLD device of example 1 and/or some other example herein, wherein the frame may be transmitted with individual addressed data without negotiated block acknowledgment.
Example 10 may include a non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors of a first multi-link device (MLD) result in performing operations comprising: setting up one or more links with a second MLD, wherein the MLD comprises one or more logical entities defining separate devices; identifying a data packet received from the second MLD associated with a traffic identifier (TID); maintaining a first record associated with the data packet, wherein the record comprises a first address of the first MLD, the TID, and a sequence number of the data packet; determining that the data packet has a retry bit set and the first record matches an existing record; dropping the data packet based on the retry bit and the first record matching the existing record.
Example 11 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, wherein the data packet associated with TID may be received without negotiating a block acknowledgment agreement with the STA MLD.
Example 12 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, wherein the data packet may be received on any of the one or more links that are set up with the first MLD.
Example 13 may include the non-transitory computer-readable medium of example 11 and/or some other example herein, wherein the data packet comprises a first sequence number (SN) in a sequence number space associated with the TID for the first MLD.
Example 14 may include the non-transitory computer-readable medium of example 11 and/or some other example herein, wherein the data packet may be individually addressed from the first MLD.
Example 15 may include the non-transitory computer-readable medium of example 11 and/or some other example herein, wherein the data packet may be addressed to a group of station devices.
Example 16 may include the non-transitory computer-readable medium of example 11 and/or some other example herein, wherein the data packet may be received across the one or more links when the data packet may be addressed to a group of station devices.
Example 17 may include a method comprising: setting, by one or more processors, by one or more processors, up one or more links with a station multi-link device (STA MLD), wherein the STA MLD comprises one or more logical entities defining separate station devices; transmitting a data packet associated with a traffic identifier (TID) to the STA MLD; determining that the data packet was not received by the STA MLD; retransmitting the data packet to the STA MLD; incrementing a retransmit counter every time the data packet may be retransmitted; and refraining from transmitting a second data packet until the data packet may be dropped or successfully received by the STA MLD.
Example 18 may include the method of example 17 and/or some other example herein, wherein the data packet may be retransmitted until the retransmit counter reaches exceeds a retransmit threshold or until a lifetime timer of the data packet expires.
Example 19 may include the method of example 18 and/or some other example herein, wherein the data packet associated with TID may be sent without negotiating a block acknowledgment agreement with the STA MLD.
Example 20 may include the method of example 18 and/or some other example herein, wherein the data packet may be sent on any of the one or more links that are set up with the STA MLD.
Example 21 may include the method of example 17 and/or some other example herein, wherein the data packet may be transmitted using a first sequence number (SN) in a sequence number space associated with the TID for the STA MLD.
Example 22 may include the method of example 17 and/or some other example herein, wherein the data packet may be individually addressed to the STA MLD.
Example 23 may include the method of example 17 and/or some other example herein, wherein the data packet may be addressed to a group of station devices.
Example 24 may include an apparatus comprising means for: setting up one or more links with a station multi-link device (STA MLD), wherein the STA MLD comprises one or more logical entities defining separate station devices; transmitting a data packet associated with a traffic identifier (TID) to the STA MLD; determining that the data packet was not received by the STA MLD; retransmitting the data packet to the STA MLD; incrementing a retransmit counter every time the data packet may be retransmitted; and refraining from transmitting a second data packet until the data packet may be dropped or successfully received by the STA MLD.
Example 25 may include the apparatus of example 24 and/or some other example herein, wherein the data packet may be retransmitted until the retransmit counter reaches exceeds a retransmit threshold or until a lifetime timer of the data packet expires.
Example 26 may include the apparatus of example 25 and/or some other example herein, wherein the data packet associated with TID may be sent without negotiating a block acknowledgment agreement with the STA MLD.
Example 27 may include the apparatus of example 25 and/or some other example herein, wherein the data packet may be sent on any of the one or more links that are set up with the STA MLD.
Example 28 may include the apparatus of example 24 and/or some other example herein, wherein the data packet may be transmitted using a first sequence number (SN) in a sequence number space associated with the TID for the STA MLD.
Example 29 may include the apparatus of example 24 and/or some other example herein, wherein the data packet may be individually addressed to the STA MLD.
Example 30 may include the apparatus of example 24 and/or some other example herein, wherein the data packet may be addressed to a group of station devices.
Example 31 may include the apparatus of example 24 and/or some other example herein, wherein the data packet may be transmitted across the one or more links when the data packet may be addressed to a group of station devices.
Example 32 may include the apparatus of example 24 and/or some other example herein, wherein the frame may be transmitted with individual addressed data without negotiated block acknowledgment.
Example 33 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-32, or any other method or process described herein.
Example 34 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-32, or any other method or process described herein.
Example 35 may include a method, technique, or process as described in or related to any of examples 1-32, or portions or parts thereof.
Example 36 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-32, or portions thereof.
Example 45 may include a method of communicating in a wireless network as shown and described herein.
Example 46 may include a system for providing wireless communication as shown and described herein.
Example 47 may include a device for providing wireless communication as shown and described herein.
Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subject-matter which can be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other features in the claims. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims.
The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations.
These computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, certain implementations may provide for a computer program product, comprising a computer-readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.
Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.
Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

What is claimed is:

1. An multi-link device (MLD), the MLD device comprising processing circuitry coupled to storage, the processing circuitry configured to:

set up one or more links with a station multi-link device (STA MLD), wherein the STA MLD comprises one or more logical entities defining separate station devices;

transmit a data packet associated with a traffic identifier (TID) to the STA MLD;

determine that the data packet was not received by the STA MLD;

retransmit the data packet to the STA MLD;

increment a retransmit counter every time the data packet is retransmitted; and

refrain from transmitting a second data packet until the data packet is dropped or successfully received by the STA MLD.

2. The MLD device of claim 1, wherein the data packet is retransmitted until the retransmit counter reaches exceeds a retransmit threshold or until a lifetime timer of the data packet expires.

3. The MLD device of claim 2, wherein the data packet associated with TID is sent without negotiating a block acknowledgment agreement with the STA MLD.

4. The MLD device of claim 2, wherein the data packet is sent on any of the one or more links that are set up with the STA MLD.

5. The MLD device of claim 1, wherein the data packet is transmitted using a first sequence number (SN) in a sequence number space associated with the TID for the STA MLD.

6. The MLD device of claim 1, wherein the data packet is individually addressed to the STA MLD.

7. The MLD device of claim 1, wherein the data packet is addressed to a group of station devices.

8. The MLD device of claim 1, wherein the data packet is transmitted across the one or more links when the data packet is addressed to a group of station devices.

9. The MLD device of claim 1, wherein the frame is transmitted with individual addressed data without negotiated block acknowledgment. A non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors of a first multi-link device (MLD) result in performing operations comprising:

setting up one or more links with a second MLD, wherein the MLD comprises one or more logical entities defining separate devices;

identifying a data packet received from the second MLD associated with a traffic identifier (TID);

maintaining a first record associated with the data packet, wherein the record comprises a first address of the first MLD, the TID, and a sequence number of the data packet;

determining that the data packet has a retry bit set and the first record matches an existing record;

dropping the data packet based on the retry bit and the first record matching the existing record.

11. The non-transitory computer-readable medium of claim 10, wherein the data packet associated with TID is received without negotiating a block acknowledgment agreement with the STA MLD.

12. The non-transitory computer-readable medium of claim 10, wherein the data packet is received on any of the one or more links that are set up with the first MLD.

13. The non-transitory computer-readable medium of claim 12, wherein the data packet comprises a first sequence number (SN) in a sequence number space associated with the TID for the first MLD.

14. The non-transitory computer-readable medium of claim 10, wherein the data packet is individually addressed from the first MLD.

15. The non-transitory computer-readable medium of claim 10, wherein the data packet is addressed to a group of station devices.

16. The non-transitory computer-readable medium of claim 10, wherein the data packet is received across the one or more links when the data packet is addressed to a group of station devices.

17. A method comprising:

setting, by one or more processors, by one or more processors, up one or more links with a station multi-link device (STA MLD), wherein the STA MLD comprises one or more logical entities defining separate station devices;

transmitting a data packet associated with a traffic identifier (TID) to the STA MLD;

determining that the data packet was not received by the STA MLD;

retransmitting the data packet to the STA MLD;

incrementing a retransmit counter every time the data packet is retransmitted; and

refraining from transmitting a second data packet until the data packet is dropped or successfully received by the STA MLD.

18. The method of claim 17, wherein the data packet is retransmitted until the retransmit counter reaches exceeds a retransmit threshold or until a lifetime timer of the data packet expires.

19. The method of claim 18, wherein the data packet associated with TID is sent without negotiating a block acknowledgment agreement with the STA MLD.

20. The method of claim 18, wherein the data packet is sent on any of the one or more links that are set up with the STA MLD.