MANAGING A GROUP OF WI-FI-ENABLED WEARABLE OR HANDHELD WIRELESS DEVICES USING A SHARED ADDRESS

This disclosure provides methods, components, devices and systems for managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address. Some aspects more specifically relate to a negotiation of a shared address that corresponds to a group of Wi-Fi-enabled wearable or handheld devices and use of the shared address during a connection setup procedure for the group. In some implementations, by performing the connection setup procedure using the shared address, one wearable or handheld device may perform the connection setup procedure on behalf of the group. Wearable or handheld devices of the group also may exchange packets to indicate, with respect to the shared address, respective link identifiers (IDs) uniquely corresponding to each respective wearable or handheld device of the group, which the wearable or handheld devices of the group may use to differentiate traffic intended for different wearable or handheld devices of the group.

TECHNICAL FIELD

This disclosure relates to wireless communication and, more specifically, to managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address.

DESCRIPTION OF THE RELATED TECHNOLOGY

In some systems, a group of Wi-Fi-enabled wearable devices may deliver or otherwise be associated with a same application. Such a group of Wi-Fi-enabled wearable devices delivering a same application may include wireless earbuds, wireless accessories (such as a watch, a bracelet, and/or a ring), health monitors, and/or gaming sensors or controllers. For example, two wireless earbuds may deliver audio data for a same music application. As another example, two or more gaming sensors and/or controllers may deliver input data (associated with motion and/or controller inputs) for a same video game application. Because each Wi-Fi device generally has its own unique medium access control (MAC) address, each device of a group of Wi-Fi-enabled wearable devices typically performs an independent connection setup procedure to connect with a WLAN. For example, a first wearable device may exchange a first set of frames with a handset, AP, or compute device as part of a first connection setup and a second wearable device may independently exchange a second set of frames with the handset, AP, or compute device as part of a second connection setup. As such, the handset, AP, or compute device may independently provision the first wearable device and the second wearable device with Wi-Fi and internet protocol (IP) connections for subsequent data communication.

SUMMARY

One innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication at a first wearable or handheld wireless device. The method may include communicating, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associated with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device, transmitting, in association with establishing a second wireless communication link with a wireless communication device, one or more second packets indicating the shared address, the first link identifier, and the second link identifier, and receiving, from the wireless communication device via the second wireless communication link, one or more third packets associated with the first link identifier.

Another innovative aspect of the subject matter described in this disclosure can be implemented at a first wearable or handheld wireless device. The first wearable or handheld wireless device may include a processing system that includes processor circuitry and memory circuitry that stores code. The processing system may be configured to cause the first wearable or handheld wireless device to communicate with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associate with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device, transmit, in association with establishing a second wireless communication link with a wireless communication device, one or more second packets indicating the shared address, the first link identifier, and the second link identifier, and receive, from the wireless communication device via the second wireless communication link, one or more third packets associated with the first link identifier.

Another innovative aspect of the subject matter described in this disclosure can be implemented at a first wearable or handheld wireless device. The first wearable or handheld wireless device may include means for communicating, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associated with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device, means for transmitting, in association with establishing a second wireless communication link with a wireless communication device, one or more second packets indicating the shared address, the first link identifier, and the second link identifier, and means for receiving, from the wireless communication device via the second wireless communication link, one or more third packets associated with the first link identifier.

Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication at a first wearable or handheld wireless device. The code may include instructions executable by one or more processors individually or collectively to communicate, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associate with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device, transmit, in association with establishing a second wireless communication link with a wireless communication device, one or more second packets indicating the shared address, the first link identifier, and the second link identifier, and receive, from the wireless communication device via the second wireless communication link, one or more third packets associated with the first link identifier.

Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication at a first wearable or handheld wireless device. The method may include communicating, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associated with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device and receiving, from a wireless communication device via a second wireless communication link, one or more second packets associated with the first link identifier, the second wireless communication link being in association with an establishment using the shared address.

Another innovative aspect of the subject matter described in this disclosure can be implemented at a first wearable or handheld wireless device. The first wearable or handheld wireless device may include a processing system that includes processor circuitry and memory circuitry that stores code. The processing system may be configured to cause the first wearable or handheld wireless device to communicate, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associate with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device and receive, from a wireless communication device via a second wireless communication link, one or more second packets associated with the first link identifier, the second wireless communication link being in association with an establishment using the shared address.

Another innovative aspect of the subject matter described in this disclosure can be implemented at a first wearable or handheld wireless device. The first wearable or handheld wireless device may include means for communicating, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associated with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device and means for receiving, from a wireless communication device via a second wireless communication link, one or more second packets associated with the first link identifier, the second wireless communication link being in association with an establishment using the shared address.

Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication at a first wearable or handheld wireless device. The code may include instructions executable by one or more processors individually or collectively to communicate, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associate with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device and receive, from a wireless communication device via a second wireless communication link, one or more second packets associated with the first link identifier, the second wireless communication link being in association with an establishment using the shared address.

Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication at a wireless communication device. The method may include receiving, in association with establishing a wireless communication link with a first wearable or handheld wireless device, one or more first packets indicating a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and a second wearable or handheld wireless device, a first link identifier corresponding to the first wearable or handheld wireless device, and a second link identifier corresponding to the second wearable or handheld wireless device and transmitting, in accordance with the shared address, one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier.

Another innovative aspect of the subject matter described in this disclosure can be implemented at a wireless communication device. The wireless communication device may include one or more memories storing processor-executable code and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code. The one or more processors may be individually or collectively operable to execute the code to cause the first wearable or handheld wireless device to receive, in association with establishing a wireless communication link with a first wearable or handheld wireless device, one or more first packets indicating a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and a second wearable or handheld wireless device, a first link identifier corresponding to the first wearable or handheld wireless device, and a second link identifier corresponding to the second wearable or handheld wireless device and transmit, in accordance with the shared address, one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier.

Another innovative aspect of the subject matter described in this disclosure can be implemented at a wireless communication device. The wireless communication device may include means for receiving, in association with establishing a wireless communication link with a first wearable or handheld wireless device, one or more first packets indicating a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and a second wearable or handheld wireless device, a first link identifier corresponding to the first wearable or handheld wireless device, and a second link identifier corresponding to the second wearable or handheld wireless device and means for transmitting, in accordance with the shared address, one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier.

Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication at a wireless communication device. The code may include instructions executable by one or more processors individually or collectively to receive, in association with establishing a wireless communication link with a first wearable or handheld wireless device, one or more first packets indicating a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and a second wearable or handheld wireless device, a first link identifier corresponding to the first wearable or handheld wireless device, and a second link identifier corresponding to the second wearable or handheld wireless device and transmit, in accordance with the shared address, one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier.

DETAILED DESCRIPTION

Various aspects relate generally to connection setup procedures and data exchange sequences for wearable devices of a group of Wi-Fi-enabled wearable devices delivering a same or similar application. Some aspects more specifically relate to a negotiation of a shared address that corresponds to a group of Wi-Fi-enabled wearable devices and use of the shared address during a connection setup procedure for the group of Wi-Fi-enabled wearable devices. For example, for a group of Wi-Fi-enabled wearable devices (which may be understood as or equivalently referred to as wearable wireless devices) including a first wearable device and a second wearable device, the first wearable device and the second wearable device may exchange, via a first wireless communication link, one or more packets associated with establishing a shared address that corresponds to an association of (such as a grouping of or set of) the first wearable device and the second wearable device. One of the first wearable device or the second wearable device may then perform a connection setup procedure with a wireless communication device (such as an access point (AP), a handset providing SoftAP functionality, or a compute device) using the shared address. The shared address may be an example of a medium access control (MAC) address or may otherwise be an address usable in place of a MAC address. The connection setup procedure may be associated with establishing a second wireless communication link with the wireless communication device. In accordance with performing the connection setup procedure using the shared address, one wearable device may perform the connection setup procedure on behalf of the group of Wi-Fi-enabled wearable devices (such that other wearable devices in the group of Wi-Fi-enabled wearable devices may refrain from performing a connection setup procedure).

In some examples, the first wearable device and the second wearable device may further exchange the one or more packets to indicate, with respect to the shared address, a first link identifier (ID) corresponding to the first wearable device and a second link ID corresponding to the second wearable device. In such examples, the first wearable device may establish a first block acknowledgment (BA) session in accordance with the shared address and the first link ID and the second wearable device may establish a second BA session in accordance with the shared address and the second link ID. As such, both the first wearable device and the second wearable device may transmit and/or receive packets using the shared address and may determine whether a packet is transmitted to or from the first wearable device or the second wearable device in accordance with a link ID associated with the packet. For example, the first wearable device may receive and decode data packets associated with the first link ID and may refrain from (fully) decoding data packets associated with the second link ID. Likewise, the second wearable device may receive and decode data packets associated with the second link ID and may refrain from (fully) decoding data packets associated with the first link ID.

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some implementations, by establishing a shared address that corresponds to an association of a set of two or more wearable devices, one wearable device may perform a connection setup procedure using the shared address such that other wearable devices of the set can refrain from performing a connection setup procedure, which may reduce connection setup signaling overhead and reduce (re)connection latency by limiting connection setup sequences to one interface. For example, by limiting connection setup sequences to one interface, (re)connection times may be reduced by approximately one-half for a group of two wearable devices (because one of the two wearable devices may refrain from performing a connection setup procedure), by approximately two-thirds for a group of three wearable devices (because two of the three wearable devices may refrain from performing a connection setup procedure), and so on. Further, additional channel access opportunities may become available for other devices in the system in accordance with such a reduction in (re)connection times and (re)connection interfaces, which may alleviate multi-client scheduling and enable denser Wi-Fi systems and/or higher data rates by increasing medium availability through delivery of packets to a single shared address. Moreover, in accordance with establishing a connection on behalf of a group of wearable devices using a shared address, the group of wearable devices may experience timely delivery of data to the group of wearable devices by appearing as a single wireless communication device from a network perspective. For example, an AP may deliver all relevant content to a group of wearable devices in an entirety because the AP may not interrupt service to the group of wearable devices to serve other devices in the system because the group of wearable devices appears as a single wireless communication device. In accordance with reducing connection setup signaling overhead and reducing (re)connection latency, enabling denser Wi-Fi systems and/or higher data rates, and leveraging a shared address to support timely delivery of data, aspects of the described subject matter may be implemented to realize greater reliability, greater spectral efficiency, improved user experience, and greater system capacity, among other benefits.

FIG.1shows a pictorial diagram of an example wireless communication network100. According to some aspects, the wireless communication network100can be an example of a wireless local area network (WLAN) such as a Wi-Fi network (and will hereinafter be referred to as WLAN100). For example, the WLAN100can be a network implementing at least one of the IEEE 802.11 family of wireless communication protocol standards (such as that defined by the IEEE 802.11-2020 specification or amendments thereof including, but not limited to, 802.11ay, 802.11ax, 802.11az, 802.11ba, 802.11bd, 802.11be, 802.11bf, and 802.11bn). The WLAN100may include numerous wireless communication devices such as a wireless AP102and multiple wireless STAs104. While only one AP102is shown inFIG.1, the WLAN100also can include multiple APs102. AP102shown inFIG.1can represent various different types of APs including but not limited to enterprise-level APs, single-frequency APs, dual-band APs, standalone APs, software-enabled APs (soft APs), and multi-link APs. The coverage area and capacity of a cellular network (such as LTE or 5G NR) can be further improved by a small cell which is supported by an AP102serving as a miniature base station. Furthermore, private cellular networks also can be set up through a wireless area network using small cells.

A single AP102and an associated set of STAs104may be referred to as a basic service set (BSS), which is managed by the respective AP102.FIG.1additionally shows an example coverage area108of the AP102, which may represent a basic service area (BSA) of the WLAN100. The BSS may be identified or indicated to users by a service set ID (SSID), as well as to other devices by a basic service set ID (BSSID), which may be a MAC address of the AP102. The AP102may periodically broadcast beacon frames (“beacons”) including the BSSID to enable any STAs104within wireless range of the AP102to “associate” or re-associate with the AP102to establish a respective communication link106(hereinafter also referred to as a “Wi-Fi link”), or to maintain a communication link106, with the AP102. For example, the beacons can include an identification or indication of a primary channel used by the respective AP102as well as a timing synchronization function for establishing or maintaining timing synchronization with the AP102. The AP102may provide access to external networks to various STAs104in the WLAN via respective communication links106.

To establish a communication link106with an AP102, each of the STAs104is configured to perform passive or active scanning operations (“scans”) on frequency channels in one or more frequency bands (such as the 2.4 GHz, 5 GHz, 6 GHz or 60 GHz bands). To perform passive scanning, a STA104listens for beacons, which are transmitted by respective APs102at a periodic time interval referred to as the target beacon transmission time (TBTT) (measured in time units (TUs) where one TU may be equal to 1024 microseconds (μs)). To perform active scanning, a STA104generates and sequentially transmits probe requests on each channel to be scanned and listens for probe responses from APs102. Each STA104may identify, determine, ascertain, or select an AP102with which to associate in accordance with the scanning information obtained through the passive or active scans, and to perform authentication and association operations to establish a communication link106with the selected AP102. The AP102assigns an association ID (AID) to the STA104at the culmination of the association operations, which the AP102uses to track the STA104.

As a result of the increasing ubiquity of wireless networks, a STA104may have the opportunity to select one of many BSSs within range of the STA104or to select among multiple APs102that together form an extended service set (ESS) including multiple connected BSSs. An extended network station associated with the WLAN100may be connected to a wired or wireless distribution system that may allow multiple APs102to be connected in such an ESS. As such, a STA104can be covered by more than one AP102and can associate with different APs102at different times for different transmissions. Additionally, after association with an AP102, a STA104also may periodically scan its surroundings to find a more suitable AP102with which to associate. For example, a STA104that is moving relative to its associated AP102may perform a “roaming” scan to find another AP102having more desirable network characteristics such as a greater received signal strength indicator (RSSI) or a reduced traffic load.

In some implementations, STAs104may form networks without APs102or other equipment other than the STAs104themselves. One example of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may alternatively be referred to as mesh networks or peer-to-peer (P2P) networks. In some implementations, ad hoc networks may be implemented within a larger wireless network such as the WLAN100. In such examples, while the STAs104may be capable of communicating with each other through the AP102using communication links106, STAs104also can communicate directly with each other via direct wireless communication links110. Additionally, two STAs104may communicate via a direct wireless communication link110regardless of whether both STAs104are associated with and served by the same AP102. In such an ad hoc system, one or more of the STAs104may assume the role filled by the AP102in a BSS. Such a STA104may be referred to as a group owner (GO) and may coordinate transmissions within the ad hoc network. Examples of direct wireless communication links110include Wi-Fi Direct connections, connections established by using a Wi-Fi Tunneled Direct Link Setup (TDLS) link, and other P2P group connections.

The APs102and STAs104may function and communicate (via the respective communication links106) according to one or more of the IEEE 802.11 family of wireless communication protocol standards. These standards define the WLAN radio and baseband protocols for the PHY and MAC layers. The APs102and STAs104transmit and receive wireless communication (hereinafter also referred to as “Wi-Fi communication” or “wireless packets”) to and from one another in the form of PHY protocol data units (PPDUs). The APs102and STAs104in the WLAN100may transmit PPDUs over an unlicensed spectrum, which may be a portion of spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz band, the 5 GHz band, the 60 GHz band, the 3.6 GHz band, and the 900 MHz band. Some examples of the APs102and STAs104described herein also may communicate in other frequency bands, such as the 5.9 GHz and the 6 GHz bands, which may support both licensed and unlicensed communication. The APs102and STAs104also can communicate over other frequency bands such as shared licensed frequency bands, where multiple operators may have a license to operate in the same or overlapping frequency band or bands.

Each of the frequency bands may include multiple sub-bands or frequency channels. For example, PPDUs conforming to the IEEE 802.11n, 802.11ac, 802.11ax and 802.11be standard amendments may be transmitted over the 2.4 GHz, 5 GHz or 6 GHz bands, each of which is divided into multiple 20 MHz channels. As such, these PPDUs are transmitted over a physical channel having a minimum bandwidth of 20 MHz, but larger channels can be formed through channel bonding. For example, PPDUs may be transmitted over physical channels having bandwidths of 40 MHz, 80 MHz, 160 or 320 MHz by bonding together multiple 20 MHz channels.

Each PPDU is a composite structure that includes a PHY preamble and a payload in the form of a PHY service data unit (PSDU). The information provided in the preamble may be used by a receiving device to decode the subsequent data in the PSDU. In instances in which PPDUs are transmitted over a bonded channel, the preamble fields may be duplicated and transmitted in each of the multiple component channels. The PHY preamble may include both a legacy portion (or “legacy preamble”) and a non-legacy portion (or “non-legacy preamble”). The legacy preamble may be used for packet detection, automatic gain control and channel estimation, among other uses. The legacy preamble also may generally be used to maintain compatibility with legacy devices. The format of, coding of, and information provided in the non-legacy portion of the preamble is associated with the particular IEEE 802.11 protocol to be used to transmit the payload.

Some wireless communication devices (including both APs102and STAs104) are capable of multi-link operation (MLO). In some implementations, MLO supports establishing multiple different communication links (such as a first link on the 2.4 GHz band, a second link on the 5 GHz band, and the third link on the 6 GHz band) between the STA104and the AP102. Each communication link may support one or more sets of channels or logical entities. In some implementations, each communication link associated with a given wireless communication device may be associated with a respective radio of the wireless communication device, which may include one or more transmit/receive (Tx/Rx) chains, include or be coupled with one or more physical antennas, or include signal processing components, among other components. An MLO-capable device may be referred to as a multi-link device (MHLD). For example, an AP MLD may include multiple APs102each configured to communicate on a respective communication link with a respective one of multiple STAs104of a non-AP MLD (also referred to as a “STA MLD”). The STA MLD may communicate with the AP MLD over one or more of the multiple communication links at a given time.

One type of MLO is multi-link aggregation (MLA), where traffic associated with a single STA104is simultaneously transmitted across multiple communication links in parallel to maximize the utilization of available resources to achieve higher throughput. That is, during at least some duration of time, transmissions or portions of transmissions may occur over two or more links in parallel at the same time. In some implementations, the parallel wireless communication links may support synchronized transmissions. In some other examples, or during some other durations of time, transmissions over the links may be parallel, but not be synchronized or concurrent. In some examples or durations of time, two or more of the links may be used for communication between the wireless communication devices in the same direction (such as all uplink or all downlink). In some other examples or durations of time, two or more of the links may be used for communication in different directions. For example, one or more links may support uplink communication and one or more links may support downlink communication. In such examples, at least one of the wireless communication devices operates in a full duplex mode. Generally, full duplex operation enables bi-directional communication where at least one of the wireless communication devices may transmit and receive at the same time.

MLA may be implemented in a number of ways. In some implementations, MLA may be packet-based. For packet-based aggregation, frames of a single traffic flow (such as all traffic associated with a given traffic ID (TID)) may be sent concurrently across multiple communication links. In some other examples, MLA may be flow-based. For flow-based aggregation, each traffic flow (such as all traffic associated with a given TID) may be sent using a single one of multiple available communication links. As an example, a single STA MLD may access a web browser while streaming a video in parallel. The traffic associated with the web browser access may be communicated over a first communication link while the traffic associated with the video stream may be communicated over a second communication link in parallel (such that at least some of the data may be transmitted on the first channel concurrently with data transmitted on the second channel).

In some other examples, MLA may be implemented as a hybrid of flow-based and packet-based aggregation. For example, an MLD may employ flow-based aggregation in situations in which multiple traffic flows are created and may employ packet-based aggregation in other situations. The determination to switch among the MLA techniques or modes may additionally, or alternatively, be associated with other metrics (such as a time of day, traffic load within the network, or battery power for a wireless communication device, among other factors or considerations).

To support MLO techniques, an AP MLD and a STA MLD may exchange supported MLO capability information (such as supported aggregation type or supported frequency bands, among other information). In some implementations, the exchange of information may occur via a beacon signal, a probe request or probe response, an association request or an association response frame, a dedicated action frame, or an operating mode indicator (OMI), among other examples. In some implementations, an AP MLD may designate a given channel in a given band as an anchor channel (such as the channel on which it transmits beacons and other management frames). In such examples, the AP MLD also may transmit beacons (such as ones which may contain less information) on other channels for discovery purposes.

MLO techniques may provide multiple benefits to a WLAN. For example, MLO may improve user perceived throughput (UPT) (such as by quickly flushing per-user transmit queues). Similarly, MLO may improve throughput by improving utilization of available channels and may increase spectral utilization (such as increasing the bandwidth-time product). Further, MLO may enable smooth transitions between multi-band radios (such as where each radio may be associated with a given RF band) or enable a framework to set up separation of control channels and data channels. Other benefits of MLO include reducing the ON time of a modem, which may benefit a wireless communication device in terms of power consumption. Another benefit of MLO is the increased multiplexing opportunities in the case of a single BSS. For example, multi-link aggregation may increase the quantity of users per multiplexed transmission served by the multi-link AP MLD.

In some systems, a group of Wi-Fi-enabled wearable devices may deliver or otherwise be associated with a same application. Such a group of Wi-Fi-enabled wearable devices delivering a same application may include wireless earbuds, wireless accessories (such as a watch, a bracelet, and/or a ring), health sensors or monitors, wearable wireless media devices, and/or gaming sensors or controllers. For example, two wireless earbuds may deliver audio data for a same music application. As another example, two or more gaming sensors and/or controllers may deliver input data (associated with motion and/or controller inputs) for a same video game application. Because each Wi-Fi device generally has its own unique MAC address, each device of a group of Wi-Fi-enabled wearable devices typically performs an independent connection setup procedure to connect with a WLAN. In other words, each wearable device of a group of Wi-Fi-enabled wearable devices may be seen as a distinct peer device to a handset, a compute device, and/or an AP in the WLAN. A compute device may be equivalently referred to as an edge compute device, a network edge device, or a compute node, and may be an example of an AP102, a STA104, a router, a mobile device, a vehicle, a laptop, a gaming console, an IoT device, or any other device connected to the network that may have processing and/or computational capabilities. In some scenarios, an end device (such as a wearable device) may rely on an edge node to process, analyze, and/or execute relatively larger computing workloads (such as processing tasks) that may otherwise result in delays and/or power consumption at the end device.

For example, a first wearable device may exchange a first set of frames with a handset, AP, or compute device as part of a first connection setup and a second wearable device may independently exchange a second set of frames with the handset, AP, or compute device as part of a second connection setup. Such first and second sets of frames may each include one or more frames and/or operations associated with a channel scan, authentication, association, an extensible authentication protocol (EAP), an EAP over LAN (EAPOL), a key exchange, an address resolution protocol (ARP), a dynamic host configuration protocol (DHCP), a BA negotiation, and/or a TWT session setup sequence. As such, the handset, AP, or compute device may independently provision the first wearable device and the second wearable device with Wi-Fi and internet protocol (IP) connections for subsequent data communication.

Such an independent provisioning of Wi-Fi-enabled devices (which may be understood as dual-bud provisioning for a pair of wireless earbuds) may effectively multiply a (re)connection time for a group of wearable devices by a quantity of devices in the group of wearable devices as compared to other communication protocols, which may lead to an unsatisfactory amount of delay (such as latency) at an end user. For example, in the context of two wireless earbuds, an independent provisioning sequence may double the time of an application or session start (and/or double a usage and bandwidth of network resources) and adversely impact a user experience compared to some other communication protocols, such as a Bluetooth protocol.

Some deployments associated with an extended personal area network (XPAN) may have flexibility in terms of enabling Wi-Fi-enabled wearable devices to have or avoid having distinct IP connectivity. For example, XPAN applications may run at a handset (such that a handset is frequently a traffic source device), a same or similar application traffic may be transmitted to each wearable device of a group of wearable devices, and wearable devices of a group of wearable devices may be mostly collocated, and each of such characteristics may support flexibility in terms of whether a given wearable device is expected to have distinct IP connectivity. For example, such characteristics may enable wearable devices of a group of wearable devices to avoid having distinct IP connectivity.

A group of wearable devices may leverage such characteristics and, in some implementations, the group of wearable devices may negotiate (such as coordinate, via signaling exchange(s) amongst each other via one or more secure peer-to-peer wireless communication links) and select a master (or primary) wearable device of the group of wearable devices, and such a master wearable device may perform signaling exchanges in association with provisioning on behalf of the entire group of wearable devices. For example, the group of wearable devices may further establish (such as negotiate, indicate, select, or otherwise determine) a shared address that corresponds to the group of wearable devices and the master wearable device may use the shared address in association with establishing a wireless communication link to an XPAN host. Such an XPAN host may be a traffic source device (for point-to-point deployment scenarios) or another wireless communication device along an end-to-end path between the traffic source device and the master wearable device (such as a nearby AP102or a nearby STA104functioning as a soft AP for relay deployment scenarios). In accordance with establishing the wireless communication link using the shared address, the group of wearable devices may appear as one device to the XPAN host. Likewise, and in accordance with the example implementations described herein, an XPAN host and/or one or more wearable devices of the group of wearable devices may use the shared address to manage signaling exchanges and/or operations associated with connection (re)setup, data exchange, and connection teardown.

In some implementations, wearable devices of the group of wearable devices may differentiate traffic in accordance with respective link IDs corresponding to each respective wearable device. In other words, for example, communication to or from the wearable devices may be associated with the shared address (such that the shared address may be present in, for example, a receiver address and/or a transmitter address of packets) and wireless communication devices (such as any one or more of an XPAN host or a wearable device) may determine to which wearable device traffic is applicable to in accordance with a link ID associated with the traffic. In some implementations, the wearable devices may negotiate and/or assign unique link IDs to each wearable device and a wearable device may selectively receive packets associated with a link ID corresponding to that wearable device. In some aspects, a link ID may be a TID or other information indicative of a traffic class (such that, in the example of wireless earbuds, traffic to and/or from the wireless earbuds is differentiated over two traffic classes, respectively). In some implementations, the group of wearable devices may operate in accordance with the shared address under some conditions and may fall back to another provisioning mechanism (such as an independent provisioning mechanism) when such conditions are not met.

One or more wireless communication devices (such as an XPAN host and/or one or more wearable devices) may leverage the example implementations described herein to reduce (such as by at least one-half) provisioning overhead involving sequences such as authentication, association, EAP or key exchange, ARP, and/or DHCP lease (providing more DHCP scope for other wireless communication devices in the system), which may reduce streaming start latencies. Further, in examples in which MLO is supported, the one or more wireless communication devices may use a TID-to-link-mapping (T2LM) scheme to multiplex traffic via different frequencies. Additionally, or alternatively, the group of wearable devices may perform localized role switches (such as one wearable device may go off-channel for a scan procedure (for itself or as an extended radio for an XPAN host) while at least one other wearable device continues to transmit and/or receive traffic) without performing an explicit handshake with an XPAN host, which may increase system robustness by enabling more flexible operation (including flexibility to search for another serving device that provides greater link conditions).

Further, various messages are described herein as packets. A packet may include a header portion and/or a data portion. A packet may be an example of a frame, may be included within a frame, or may include a frame. Further, although described in the example of wearable devices, the techniques of the present disclosure may be applicable to any set or group of wireless communication devices (such as any set or group of end devices) that have an association or relation to each other (by, for example, serving a same or similar application). As such, any wireless device may perform the described signaling and/or control operations without exceeding the scope of the present disclosure.

FIG.2shows an example signaling diagram200that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The signaling diagram200may implement or be implemented to realize aspects of the WLAN100. For example, the signaling diagram200illustrates communication between a wireless communication device202and a group of wearable devices (including a wearable device204-aand a wearable device204-b) via a wireless communication link206(such as a Wi-Fi link). The wearable device204-aand the wearable device204-bmay be understood as being part of a same group of wearable devices in accordance with the wearable device204-aand the wearable device204-bserving a same or similar purpose, a same or similar use case, and/or a same or similar application. In other words, although the wearable device204-aand the wearable device204-bmay be two physically distinct devices, the wearable device204-aand the wearable device204-bmay serve a same or similar purpose and be understood as related to associated to each other in accordance with serving the same or similar purpose. Further, although described in the example of the signaling diagram200as wearable devices, the wearable device204-aand/or the wearable device204-bmay equivalently be examples of handheld devices (such as a gaming controller).

For example, the wearable device204-aand the wearable device204-bmay be examples of two wireless earbuds serving a same music application (as illustrated in the example of the signaling diagram200), two controllers or sensors serving a same video game application, or two health monitors tracking similar metrics and/or performing similar functions. Further, although illustrated in the example of the signaling diagram as including two wearable devices, a group of wearable devices may include any quantity of wearable devices, such as two, three, four, five, and so on. The wireless communication device202may be an example of a serving device, such as a traffic source/sink device or an AP102. A traffic source/sink device may be a phone, mobile device, a tablet, a personal computer, a compute device, or a gaming console, among other examples of a wireless communication device having data generation and/or data processing capabilities.

In some deployments, the wireless communication device202and the group of wearable devices may be part of (such as members of or otherwise connected to) an XPAN. In such deployments, the wearable device204-aand the wearable device204-bmay be Wi-Fi-enabled (such as Wi-Fi equipped) and may support one or more mechanisms to meet expectations of latency, robustness, and power consumption. In accordance with being members of an XPAN, for example, the wearable device204-aand the wearable device204-bmay support mechanisms to reduce latency and achieve seamless transitions from one serving device to another serving device (such as from AP to AP). For example, the wearable device204-aand the wearable device204-bmay support mechanisms to keep voice calls at a latency at which users may continue to engage in the voice call while roaming on a Wi-Fi AP infrastructure and meeting specification- and ecosystem-based end-to-end latency targets (such as while maintaining user comfort). Further, the wearable device204-aand the wearable device204-bmay support mechanisms to allow a user to freely roam around a Wi-Fi extender or mesh network infrastructure with a relatively low likelihood of breaks or drops in service (such as in audio) during, for example, an AP-AP transition.

In some systems, however, an XPAN host (such as a traffic source device, an AP, or a compute device) may serve the wearable device204-aand the wearable device204-bas distinct and separate wireless communication devices. In other words, although the wearable device204-aand the wearable device204-bmay be in a same group of wearable devices serving a same or similar purpose, some Wi-Fi designs may result in the wearable device204-aand the wearable device204-bbeing communicated to as two independent client devices from the network perspective. In accordance with being communicated to as two independent client devices, a serving device and/or the wearable devices may experience increased Wi-Fi (re)connection times (as each of the wearable device204-aand the wearable device204-bmay be expected to perform separate connection setup procedures, including separate control and management frame exchanges, effectively doubling connection time). For example, in examples in which each of the wearable device204-aand the wearable device204-bperform a separate, individual connection setup, the wearable device204-aand the wearable device204-bmay approximately double network management and control traffic (along with peer management overhead) on the serving device.

In an example in which the wearable device204-aand the wearable device204-bare wireless earbuds, for instance, if a user is currently using the wearable device204-aand subsequently takes the wearable device204-bout of a case, the wearable device204-bmay be expected to perform a complete Wi-Fi reconnection process. Such a complete Wi-Fi reconnection process may include scanning (active or passive), authentication (which may include an authentication request packet and an authentication response packet), association (which may include an association request packet and an association response packet), security key exchange (such as via an EAPOL, which may include an exchange of four messages M1, M2, M3, and M4), an ARP, and a DHCP (which may include a DHCP discover packet, a DHCP offer packet, a DHCP request packet, and a DHCP ACK packet). The complete Wi-Fi reconnection process may take an amount of time proportional to a network congestion level (such as an amount of devices in the network). For example, the complete Wi-Fi reconnection process may take between approximately 2 seconds and approximately 5 seconds in accordance with the network congestion level, which may be unsatisfactory to an end user as compared to some other wearable device connection mechanisms.

Further, in accordance with being communicated to as two independent client devices and likewise having independent data streams, a serving device and/or the wearable devices also may experience increased delay or jitter for data sent to both the wearable device204-aand the wearable device204-b, larger DHCP lease scope granted of each wearable device, and higher power management costs of each wearable device at the serving device (as the serving device may maintain a power management state of all wearable devices individually to avoid transmissions to a wearable device in a sleep state; such transmissions may be referred to as leaky packet delivery). In some aspects, the wearable device204-aand the wearable device204-bmay experience increased delay or jitter especially for data sent from an AP102in a whole home coverage (WHC) use case. For example, in a WHC use case, an AP102may lack knowledge that the wearable device204-aand the wearable device204-bare related (such as belong to a same group of wearable devices) and may communicate with the wearable device204-aand the wearable device204-bas two independent connected devices, which may cause interruptions or discontinuity between service of the wearable device204-aand service of the wearable device204-b.

In other words, because APs102may serve many connected Wi-Fi devices, an AP102may serve (such as relay data from a traffic source device to) the wearable device204-a, serve one or more other client devices, and then serve (such as relay data from the traffic source device to) the wearable device204-b, which may result in a time gap between service of the wearable device204-aand service of the wearable device204-b. To address such a possibility for increased delay or jitter in WHC use cases (and because both wearable devices may render data at the same time or otherwise in synchronization), the wearable device204-aand the wearable device204-bmay use larger buffers to avoid a rendering delay between the wearable device204-aand the wearable device204-b, which may translate or otherwise result in higher end-to-end latency, larger memory storage space, larger device size, and cost at the wearable device204-aand the wearable device204-b. Due to a small form factor and/or low target cost of some wearable devices (such as health monitors and wireless earbuds), such large memory or buffers may compromise usability, user experience, and/or adoption.

In some implementations, to mitigate or otherwise remedy such latency and/or costs, the wireless communication device202and the group of wearable devices may support one or more mechanisms associated with using a shared address as part of a connection setup procedure208and a data exchange sequence210. In other words, the wireless communication device202may manage the wearable device204-aand the wearable device204-bin accordance with a shared address corresponding to an association of (such as a grouping of) the wearable device204-aand the wearable device204-b, and such management may include signaling exchanges associated with the connection setup procedure208(which also may be a reconnection setup procedure), the data exchange sequence210, and any connection teardown procedure. Such a shared address may alternatively be referred to or understood as a virtual multi-link (vML) address and the connection setup procedure208using such a vML address may be understood as vML-based provisioning as, for example, using a same shared address and differentiating traffic by other indications or mechanisms may be understood as using multiple “virtual links” with respect to the “one link” that is established using the shared address. Likewise, a shared address and a vML address may be used interchangeably herein, including in the drawings, and, in some aspects, the group of wearable devices together may be understood as a vML device (with two or more physically separated devices). In some aspects, each different group of wearable devices may have a unique shared address corresponding to that group of wearable devices.

In some implementations, the wearable device204-aand the wearable device204-bmay communicate a first set of packets indicating the shared address. For example, the wearable device204-aand the wearable device204-bmay transmit and/or receive the first set of packets as part of a negotiation or sharing of the shared address between the wearable device204-aand the wearable device204-b. In some implementations, the shared address may be (such as in accordance with device configurations) a MAC address of the wearable device that performs the connection setup procedure208on behalf of the group of wearable devices. In some implementations, the wearable device204-aand the wearable device204-bmay negotiate which of the wearable device204-aor the wearable device204-bis to perform the connection setup procedure208using the shared address, and the wearable device that performs the connection setup procedure208may be understood as functioning in a master role. In some aspects, the wearable device204-aand the wearable device204-balso may negotiate and assign a respective link ID (such as a TID or other information indicative of a traffic class) to each of the wearable device204-aand the wearable device204-bvia the first set of packets, which the wearable device204-aand the wearable device204-bmay use to differentiate between data traffic intended for the wearable device204-aand data traffic intended for the wearable device204-b. In some implementations, the first set of packets may indicate a first link ID “a” corresponding to the wearable device204-aand a second link ID “b” corresponding to the wearable device204-b.

In some implementations, the link ID “a” may correspond to a first TID (such as a TID6) and the link ID “b” may correspond to a second TID (such as a TID7). In some aspects, the first TID and the second TID may be of a same access category. In some other aspects, the first TID and the second TID may be of different access categories. Although described in this example as there being a “correspondence” between a link ID and a TID, there may not necessarily be a one-to-one relationship between link ID and TID. For example, multiple TIDs may map to a single link ID and/or a single TID may map to multiple link IDs.

In some implementations, the wearable device204-aand the wearable device204-bmay exchange the first set of packets via a first wireless communication link between the wearable device204-aand the wearable device204-b, which may be an example of any secure peer-to-peer link. For example, such a first wireless communication link may be a Bluetooth link, a Wi-Fi link, or an ultra-wideband (UWB) link, among any other example of a peer-to-peer link. In some implementations, the wearable device204-aand the wearable device204-bmay secure the first wireless communication link to provide a safe haven for an exchange of sensitive Wi-Fi link-specific information between the wearable device204-aand the wearable device204-b. For example, the wearable device204-aand the wearable device204-bmay communicate using a specific encryption (such as advanced encryption standard (AES)-128) with a message integrity check (MIC) (such as a 4-byte MIC).

As part of the connection setup procedure208, in examples in which the wearable device204-atakes the role of master, the wearable device204-amay communicate a set of packets212with (such as transmit to and/or receive from) the wireless communication device202. For example, the wearable device204-amay transmit a second set of packets to the wireless communication device202and may receive packets responsive to the second set of packets to establish the wireless communication link206(which may sometimes be referred to herein as a second wireless communication link) with the wireless communication device202. The set of packets212may include one or more packets associated with authentication, one or more packets associated with association, one or more packets associated with an EAPOL, one or more packets associated with a security key exchange, one or more packets associated with a DHCP, and one or more packets associated with adding a BA session. At least one of the set of packets212may indicate the shared address, the first link ID “a” corresponding to the wearable device204-a, and the second link ID “b” corresponding to the wearable device204-b.

In some implementations, the wearable device204-amay communicate one or more packets214with the wearable device204-bduring (and/or prior to) the connection setup procedure208to coordinate with the wearable device204-bon how the wireless communication link206is set up. Additional details relating to such communication between the wearable device204-aand the wearable device204-bare illustrated by and described with reference toFIG.5. In accordance with use of the shared address for the connection setup procedure208, the wearable device204-aand the wearable device204-bmay leverage single peer control and management message exchanges and appear as one connected device (such as one connected peer), which may reduce (such as halve) connection setup times and network control and/or management overhead.

In accordance with establishing the wireless communication link206, the wearable device204-a(functioning in the master role) may transmit a packet216to the wireless communication device202indicating the shared address (such as the vML address) and indicating a power management state corresponding to the shared address. In some implementations, the wearable device204-amay coordinate with the wearable device204-bon the power management state such that the power management state indicated via the packet216is indicative of (such as representative of) both a power management state of the wearable device204-aand the wearable device204-b. In other words, the wearable device204-aand the wearable device204-bmay synchronize power management states such that both are in an awake state at a same time. The wireless communication device202may transmit an ACK218to the wearable device204-ain accordance with receiving the packet216, which may confirm to the wearable device204-athat the wireless communication device202successfully received the indication of the power management state corresponding to the shared address. In some aspects, the packet216may be a null data packet, such as a QoS NULL packet.

In examples in which the power management state corresponding to the shared address indicates that both the wearable device204-aand the wearable device204-bare in an awake state (such as in examples in which a power management bit in the packet216is set to 0), the wireless communication device202may begin a data transmission to the wearable device204-aand the wearable device204-b. For example, the wireless communication device202may transmit a packet220and a packet224, each including downlink (which may be referred to as DL) data. In some implementations, the wireless communication device202may transmit an indication of the shared address and a link ID in each of the packet220and the packet224. For example, the packet220may include an indication of the shared address and the link ID “a” corresponding to the wearable device204-aand the packet224may include an indication of the shared address and the link ID “b” corresponding to the wearable device204-b. In other words, the wireless communication device202may send data to both the wearable device204-aand the wearable device204-bindependently over separate link IDs (such as separate TIDs or traffic classes). In some aspects, the wireless communication device202(such as a traffic source device) may embed an IP type of service (TOS) value mapped to either link ID in the packets (such as in audio data packets, and a same traffic priority and classification may be applied for raw audio ethernet packets, which may be used for direct communication between a traffic source device and the wearable devices). In some implementations, the IP TOS value may enable traffic class or priority information to be carried forward and retained across multiple hops between a traffic source device and the wearable devices.

As such, the wearable device204-amay receive and attempt to decode the packet220in accordance with the packet220including the indication of the link ID “a” and, if successful, the wearable device204-amay transmit an ACK222to the wireless communication device202associated with the packet220. Similarly, the wearable device204-bmay receive and attempt to decode the packet224in accordance with the packet224including the indication of the link ID “b” and, if successful, the wearable device204-bmay transmit an ACK226to the wireless communication device202associated with the packet224. In some implementations, the wearable device204-amay refrain from attempting to (fully) decode the packet224in accordance with the packet224including the indication of the link ID “b” and the wearable device204-bmay refrain from attempting to (fully) decode the packet220in accordance with the packet220including the indication of the link ID “a.” In some aspects, the packet220may be part of a first data stream for the wearable device204-aand the packet224may be part of a second data stream for the wearable device204-band the two data streams for the wearable device204-aand the wearable device204-bmay be differentiated over link IDs. In some aspects, the wireless communication device202may transmit the packet220and the packet224via a same frequency channel. In some other aspects (such as in examples in which the wireless communication device202is an MLD), the wireless communication device202may transmit the packet220and the packet224via different frequency channels.

In some implementations, the packet220and the packet224may include different information, each including information specific to one of the wearable device204-aand the wearable device204-b. In such implementations, a traffic source device (such as the wireless communication device202) may generate the information included in the packet220and the packet224in accordance with to which wearable device each of the packet220and the packet224are intended. For example, the packet220may include first information specific to the wearable device204-aand the packet224may include second information specific to the wearable device204-b. In some other implementations, the packet220and the packet224may include some at least partially overlapping information. For example, the wireless communication device202may apply some amount of duplication of data and include both the first information and the second information in each of the packet220and the packet224, which may enable some post-processing operations at the wearable devices (such as to facilitate a perception of 3-dimensional audio for an end user).

The wearable device204-aand the wearable device204-bmay periodically exchange information associated with a (desired) power management state and, in examples in which at least one of the wearable device204-aand the wearable device204-bindicates an expectation to enter a sleep state, the wearable device204-a(the master) may transmit a packet (such as another null data packet) indicating the shared address and an updated power management state corresponding to the shared address. In examples in which at least one of the wearable device204-aand the wearable device204-bindicates an expectation to enter a sleep state, the wearable device204-amay set a power management bit to 1. As such, the group of wearable devices including at least the wearable device204-aand the wearable device204-bmay manage and organize communication with the wireless communication device202using the shared address and differentiating traffic using differing link IDs. For example, if a wearable device becomes disconnected and attempts to reconnect, the reconnecting wearable device may avoid any additional reconnection signaling overhead (as another link between the group of wearable devices and the wireless communication device202will likely still be operation and can be used to re-establish the “link” that went down). Additionally, in accordance with using the shared address to manage and organize communication, periodic groupwise rekey exchanges may be reduced by, for example, approximately one-half for the wearable device204-aand the wearable device204-b.

Further, although described in the example of downlink data transmission with reference to the signaling diagram200, the described techniques may be equivalently applicable to uplink data transmission. For example, the wearable device204-amay transmit a first set of one or more packets including an indication of the shared address and the link ID “a” and the wearable device204-bmay transmit a second set one or more packets including an indication of the shared address and the link ID “b.” As such, the wireless communication device202may receive the packets as if the packets were sent by a single wireless communication device, but a traffic sink device (such as a device ultimately responsible for parsing the packets and using data received via the packets for one or more operations) may decode the packets and expect (such as identify or otherwise understand) that data obtained via the first set of packets originated at the wearable device204-aand that data obtained via the second set of packets originated at the wearable device204-b. Further, although illustrated in the example of the signaling diagram200as a single hop between the wireless communication device202and the group of wearable devices, the described techniques may be applicable to relay or mesh deployments in which data may be relayed to or from the group of wearable devices and a traffic source/sink device over any quantity of hops.

As such, in accordance with the example implementations of the present disclosure, link identity information (such as information indicative of a link ID) may be retained and carried over both point-to-point and over AP(s)102(in a mesh or enterprise network). A content of some fields, however, may not be carried over multiple hops (as, for example, content of signal (SIG) fields and 802.11 headers, including a QoS control field and an HT control field, may not be carried over multiple hops in some systems), although an understanding of link identify information (such as a semantics of link identify information) may apply to both Layer 2 (L2) and Layer 3 (L3). For example, a traffic class or service may map to a TID in some headers (such as an 802.11 header) and to a type of service (TOS) in some other headers (such as in an IP header). In some implementations, traffic class fields present in L2 and L3 headers may be mapped to each other and retained across potentially multiple hops between traffic endpoints.

Further, the described techniques may be implemented to account for power management of multiple wearable devices individually while the wearable devices are associated through a shared address, such as via a TWT session setup in accordance with link ID. Further, in some implementations, the wearable device204-aand the wearable device204-bmay support a fallback mechanism to individual provisioning in examples in which shared address-based provisioning fails to satisfy one or more conditions. Such a fallback mechanism may be especially useful for over-the-AP topologies and, in some implementations, one or both of the wearable device204-aand the wearable device204-bmay perform an end-to-end QoS conformance test as part of the fallback mechanism (such as to measure, determine, or otherwise identify whether to initiate a fallback to individual provisioning). Further, the described messaging formats and exchanges may be applicable to various types of deployment scenarios and to various types of devices. For example, the described messaging formats and exchanges may be supported by devices and networks of various manufacturers.

Further, in implementations in which the wireless communication device202is capable of multi-link operation (MLO), the wireless communication device202may use a T2LM scheme or other link mapping scheme to map each TID or link ID (such as each wearable device) to a specific link of the wireless communication device202. For example, in examples in which the wireless communication device202is an MLD able to operate multiple links (such as a 2.4 GHz link, a 5 GHz link, and/or a 5 GHz link), the wireless communication device202may support simultaneous transmission to and/or reception from the wearable device204-aand the wearable device204-bon two different links, the two different link corresponding to two different radio frequency channels. In such implementations, the wireless communication device202may transmit an indication of the T2LM and the wearable device204-amay tune at least one radio to a first frequency channel to which the link ID “a” is mapped and the wearable device204-bmay tune at least one radio to a second frequency channel to which the link ID “b” is mapped. As such, the wireless communication device202may support greater MAC efficiency, enable more concurrency time on the wireless communication device202, reduce power consumption on each of the wearable device204-aand the wearable device204-b, and reduce delay and/or jitter between data to the wearable devices, which may in turn reduce memory constraints, size, and cost of the wearable devices.

In accordance with using a shared address for a connection setup procedure, aspects of the present disclosure may be implemented to realize various addressing formats for various link types. For ethernet addressing, for example, an example addressing of packets may be [HSAP-M-vML-M] and [vML-M-HSAP-M]. For 802.11 addressing for point-to-point communication, an example addressing of packets may be [vML-M-HSAP-M-HSAP-M] and [HSAP-M-vML-M-HSAP-M]. For 802.11 addressing for over-the-AP communication, an example addressing of packets may be [APX-M-HSTA-M-vML-M], [vML-M-APX-M-HSTA-M], [APX-M-vML-M-HSTA-M], and [HSTA-M-APX-M-vML-M]. In such examples, HSAP-M may be an address of a traffic source/sink device for ethernet or direct wireless communication, vML-M may be an address of the group of wearable devices, HSTA-M may be an address of a traffic source/sink device for relayed wireless communication, and APX-M may be an address of an AP102via which packets are relayed between a traffic source/sink device and the group of wearable devices.

FIG.3shows an example process flow300that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The process flow300may implement or be implemented to realize or facilitate aspects of the WLAN100and the signaling diagram200. For example, the process flow300illustrates communication between a STA104(which may be an example of a traffic source/sink device), the wearable device204-a, the wearable device204-b, and an AP102(which may be an example of a QoS AP102). The wireless communication device202illustrated by and described with reference toFIG.2may be an example of the STA104or the AP102. In some implementations, the wearable device204-aand the wearable device204-bmay be associated with a same group of wearable devices and may use a shared address to perform a connection setup procedure with the STA104(for point-to-point communication) or the AP102(for over-the-AP relay communication), such as a connection setup procedure208as illustrated by and described with reference toFIG.2.

In the following description of the process flow300, the operations may be performed (such as reported or provided) in a different order than the order shown, or the operations performed by the example devices may be performed in different orders or at different times. For example, specific operations also may be left out of the process flow300, or other operations may be added to the process flow300. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

At302, the wearable device204-aand the wearable device204-bmay communicate (such as transmit and/or receive) one or more packets in accordance with establishing (such as setting up) a first wireless communication link. The first wireless communication link may be a secure peer-to-peer link, such as a Bluetooth link, a Wi-Fi link, or a UWB link.

At304, the wearable device204-aand the wearable device204-bmay communicate (such as transmit and/or receive) one or more packets in accordance with a negotiation of a primary link and/or a negotiation of a shared address (such as a vML address). For example, the wearable device204-aand the wearable device204-bmay exchange one or more packets indicating which of the wearable device204-aand the wearable device204-bis to take a master role and perform a connection setup procedure and/or may exchange one or more packets indicating a shared address that is to be used for the connection setup procedure. In some aspects, the same set of frames or different sets of frames may indicate which wearable device is to take the master role and the shared address. The primary link may be understood as the link or device via which the connection setup procedure is to be performed on behalf of other link(s) or device(s) of the group of wearable devices. Additionally, in some implementations, the wearable device204-aand the wearable device204-bmay communicate one or more packets indicating, with respect to the shared address, a link ID “a” corresponding to the wearable device204-aand a link ID “b” corresponding to the wearable device204-b. For example, the wearable device204-aand the wearable device204-bmay transmit and/or receive packets in accordance with a negotiation (such as coordination) of link ID assignments. As such, the wearable device204-aand the wearable device204-bmay use the same shared address (such as a same transmitter address or receiver address) and instead differentiate traffic in accordance with respective (and unique) link IDs.

At306, in examples in which the wearable device204-ais indicated or otherwise selected to take the primary role and perform the connection setup procedure, the wearable device204-amay perform a scanning operation. Such a scanning operation may include one or both of passive scanning and active scanning and the wearable device204-amay perform the scanning operation to discover a wireless communication device with which to connect to obtain internet or network access. In some implementations, the wearable device204-amay discover the STA104(such as the traffic source/sink device). In some other examples, the wearable device204-amay discover the AP102(such as a wireless communication device along a relay path between the traffic source/sink device and the wearable device204-a.

At308, in examples in which the wearable device204-adiscovers the STA104in accordance with the scanning operation, the wearable device204-aand the STA104may exchange one or more authentication packets. For example, the wearable device204-amay transmit an authentication request to the STA104and the STA104may transmit an authentication response corresponding to the authentication request. In some implementations, the wearable device204-aand the STA104may include an indication of the shared address in both of the authentication request and the authentication response in accordance with the shared address-based provisioning.

At310, the wearable device204-aand the STA104may communicate one or more association packets. For example, the wearable device204-amay transmit an association request to the STA104and the STA104may transmit an association response corresponding to the association request. In some implementations, the wearable device204-aand the STA104may include an indication of the shared address in both of the association request and the association response in accordance with the shared address-based provisioning.

At312, the wearable device204-aand the STA104may communicate one or more packets associated with an ARP negotiation. In accordance with the ARP negotiation, the wearable device204-amay receive an indication of a gateway and a domain name system (DNS) server associated with communication with the STA104. In some implementations, the wearable device204-aand the STA104may include an indication of the shared address in the one or more packets associated with the ARP negotiation in accordance with the shared address-based provisioning.

At314, the wearable device204-aand the STA104may communicate one or more packets associated with a DHCP negotiation. In some aspects, the one or more packets associated with the DHCP negotiation may indicate, to the wearable device204-a, an IP address. In some implementations, the IP address may correspond to the group of wearable devices in accordance with the shared address-based provisioning. In accordance with the packet exchanges at308,310,312, and314, the wearable device204-amay establish a second wireless communication link with the STA104. In some implementations, the wearable device204-amay establish the second wireless communication link for both the wearable device204-aand the wearable device204-bin accordance with using the shared address. Additionally, in some implementations, the wearable device204-amay provide an indication of the link ID “a” (corresponding to the wearable device204-a) and the link ID “b” (corresponding to the wearable device204-b) via any one or more of the packet exchanges at308,310,312, and314. In implementations in which the STA104is a traffic source device, the STA104may use the indication of the link ID “a” to generate and deliver first data packets specific to the wearable device204-aand may use the link ID “b” to generate and deliver second data packets specific to the wearable device204-b.

At316, the wearable device204-aand the wearable device204-bmay communicate one or more packets in accordance with the wearable device204-aestablishing the second wireless communication link with the STA104. In some aspects, such one or more packets may indicate, to the wearable device204-b, information indicative of a pairwise transient key (PTK), a group temporary key (GTK), a gateway IP, a DNS server IP, and a DHCP IP handshake. In some implementations, the wearable device204-aand the wearable device204-bmay negotiate (such as coordinate) on such security keys and/or IP addresses and the wearable device204-amay establish the second wireless communication link in accordance with the negotiation. In some aspects, such negotiation may be associated with respective capabilities of the wearable device204-aand the wearable device204-b.

At318, in accordance with establishing the second wireless communication link, the wearable device204-amay communicate one or more packets with the STA104to establish a first BA session between the wearable device204-aand the STA104. For example, one of the wearable device204-aand the STA104may transmit an ADDBA request to the other of the wearable device204-aand the STA104, and the other of the wearable device204-aand the STA104may transmit an ADDBA response corresponding to the ADDBA request. In some implementations, the wearable device204-aand the STA104may include the link ID “a” (along with the shared address) in the ADDBA request and ADDBA response to establish the first BA session specifically for the wearable device204-a.

At320, in accordance with the wearable device204-aestablishing the second wireless communication link with the STA104, the wearable device204-bmay communicate one or more packets with the STA104to establish a second BA session between the wearable device204-band the STA104. For example, one (such as a data transmitter) of the wearable device204-band the STA104may transmit an ADDBA request to the other of the wearable device204-band the STA104, and the other of the wearable device204-band the STA104may transmit an ADDBA response corresponding to the ADDBA request. In some implementations, the wearable device204-band the STA104may include the link ID “b” (along with the shared address) in the ADDBA request and ADDBA response to establish the second BA session specifically for the wearable device204-b. In other words, in accordance with the wearable device204-aestablishing the second wireless communication link, the wearable device204-aand the wearable device204-bmay each establish separate BA sessions for data transmission, and each of the wearable device204-aand the wearable device204-bmay individually acknowledge received data.

At322, in some implementations, the wearable device204-aand the STA104may communicate one or more packets associated with a TWT session setup. In other words, the STA104may transmit, to the wearable device204-a, information indicative of a first schedule of communication time intervals during which the wearable device204-aand the STA104may communicate packets associated with the link ID “a.” For example, one (such as a data transmitter) of the wearable device204-aand the STA104may transmit a TWT setup request to the other of the wearable device204-aand the STA104, and the other of the wearable device204-aand the STA104may transmit TWT setup response corresponding to the TWT setup request, each of the TWT setup request and the TWT setup response including an indication of the shared address and the link ID “a.” In some implementations, the wearable device204-aand the STA104may establish a TWT schedule for communication associated with the link ID “a” in examples in which both wireless communication devices support TWT operation. Additionally, or alternatively, the wearable device204-aand the STA104may communicate in accordance with a unscheduled automatic power save delivery (U-APSD) mechanism.

At324, in some implementations, the wearable device204-band the STA104may communicate one or more packets associated with a TWT session setup. In other words, the STA104may transmit, to the wearable device204-b, information indicative of a second schedule of communication time intervals during which the wearable device204-band the STA104may communicate packets associated with the link ID “b.” For example, one (such as a data transmitter) of the wearable device204-band the STA104may transmit a TWT setup request to the other of the wearable device204-band the STA104, and the other of the wearable device204-band the STA104may transmit TWT setup response corresponding to the TWT setup request, each of the TWT setup request and the TWT setup response including an indication of the shared address and the link ID “b.” In some implementations, the wearable device204-band the STA104may establish a TWT schedule for communication associated with the link ID “b” in examples in which both wireless communication devices support TWT operation. As such, the STA104may establish separate TWT sessions for each link ID (such as for each TID or traffic class and, in turn, for each wearable device of a group of wearable devices). Additionally, or alternatively, the wearable device204-band the STA104may communicate in accordance with a U-APSD mechanism.

At326, in alternative examples in which the wearable device204-adiscovers the AP102in accordance with the scanning operation, the wearable device204-aand the AP102may exchange one or more authentication packets. For example, the wearable device204-amay transmit an authentication request to the AP102and the AP102may transmit an authentication response corresponding to the authentication request. In some implementations, the wearable device204-aand the AP102may include an indication of the shared address in both of the authentication request and the authentication response in accordance with the shared address-based provisioning.

At328, the wearable device204-aand the AP102may communicate one or more association packets. For example, the wearable device204-amay transmit an association request to the AP102and the AP102may transmit an association response corresponding to the association request. In some implementations, the wearable device204-aand the AP102may include an indication of the shared address in both of the association request and the association response in accordance with the shared address-based provisioning.

At330, the wearable device204-aand the AP102may communicate one or more packets associated with an ARP negotiation. In accordance with the ARP negotiation, the wearable device204-amay receive an indication of a gateway and a domain name system (DNS) server associated with communication with the AP102. In some implementations, the wearable device204-aand the AP102may include an indication of the shared address in the one or more packets associated with the ARP negotiation in accordance with the shared address-based provisioning.

At332, the wearable device204-aand the AP102may communicate one or more packets associated with a DHCP negotiation. In some aspects, the one or more packets associated with the DHCP negotiation may indicate, to the wearable device204-a, an IP address. In some implementations, the IP address may correspond to the group of wearable devices in accordance with the shared address-based provisioning. In accordance with the packet exchanges at326,328,330, and332, the wearable device204-amay establish a second wireless communication link with the AP102(as part of a relay path between the STA104and the group of wearable devices). In some implementations, the wearable device204-amay establish the second wireless communication link for both the wearable device204-aand the wearable device204-bin accordance with using the shared address. Additionally, in some implementations, the wearable device204-amay provide an indication of the link ID “a” (corresponding to the wearable device204-a) and the link ID “b” (corresponding to the wearable device204-b) via any one or more of the packet exchanges at326,328,330, and332. The AP102may relay such information to the STA104and the STA104may use the indication of the link ID “a” to generate and deliver (via the AP102) first data packets specific to the wearable device204-aand may use the link ID “b” to generate and deliver (via the AP102) second data packets specific to the wearable device204-b.

At334, the wearable device204-aand the wearable device204-bmay communicate one or more packets in accordance with the wearable device204-aestablishing the second wireless communication link with the AP102. In some aspects, such one or more packets may indicate, to the wearable device204-b, information indicative of a PTK, a GTK, a gateway IP, a DNS server IP, and a DHCP IP handshake. In some implementations, the wearable device204-aand the wearable device204-bmay negotiate (such as coordinate) on such security keys and/or IP addresses and the wearable device204-amay establish the second wireless communication link in accordance with the negotiation. In some aspects, such negotiation may be associated with respective capabilities of the wearable device204-aand the wearable device204-b.

At336, the wearable device204-amay perform a QoS conformance test with the AP102, which may be indicative of whether a relay path between the STA104and the wearable device204-avia the AP102is able to support QoS-based traffic prioritization. In accordance with the QoS conformance test, the wearable device204-aand the STA104may exchange, via the AP102, one or more packets to test whether QoS-based traffic prioritization is maintained (such as preserved) across each hop of the multi-hop relay path. For example, the wearable device204-aand the STA104may exchange, via the AP102, one or more internet control message protocol (ICMP) packets, such as ICMP Echo request and/or response packets, to test the QoS conformance of the end-to-end relay path between the STA104and the wearable device204-a. In examples in which a responsive ICMP packet, such as an ICMP Echo response, is received at the same priority at which a corresponding request was sent, the end-to-end relay path may successfully pass the QoS conformance test. Otherwise, the end-to-end relay path may fail the QoS conformance test. Additional details relating how the wearable device204-amay track information associated with which APs102pass the QoS conformance test and which APs102result in a failure of the QoS conformance test are illustrated by and described in more detail with reference toFIGS.4and5.

At338, in examples in which the end-to-end relay path passes the QoS conformance test, the wearable device204-amay proceed with shared address-based provisioning and communicate one or more packets with the AP102to establish a first BA session between the wearable device204-aand the AP102. For example, one of the wearable device204-aand the AP102may transmit an ADDBA request to the other of the wearable device204-aand the AP102, and the other of the wearable device204-aand the AP102may transmit an ADDBA response corresponding to the ADDBA request. In some implementations, the wearable device204-aand the AP102may include the link ID “a” (along with the shared address) in the ADDBA request and ADDBA response to establish the first BA session specifically for the wearable device204-a. As part of the first BA session, the wearable device204-amay employ TWT-based transmission and/or reception or may employ early receive termination to manage power consumption at the wearable device204-a(depending on a capability of, for example the AP102).

At340, the wearable device204-bmay likewise proceed with shared address-based provisioning and communicate one or more packets with the AP102to establish a second BA session between the wearable device204-band the AP102. For example, one of the wearable device204-band the AP102may transmit an ADDBA request to the other of the wearable device204-band the AP102, and the other of the wearable device204-band the AP102may transmit an ADDBA response corresponding to the ADDBA request. In some implementations, the wearable device204-band the AP102may include the link ID “b” (along with the shared address) in the ADDBA request and ADDBA response to establish the second BA session specifically for the wearable device204-b. As part of the second BA session, the wearable device204-bmay employ TWT-based transmission and/or reception or may employ early receive termination to manage power consumption at the wearable device204-b(depending on a capability of, for example the AP102).

FIG.4shows an example process flow400that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The process flow400may implement or be implemented to realize or facilitate aspects of the WLAN100, the signaling diagram200, or the process flow300. For example, the process flow400illustrates communication between a STA104(which may be an example of a traffic source/sink device), the wearable device204-a, the wearable device204-b, an AP102(which may be an example of a non-QoS AP). The wireless communication device202illustrated by and described with reference toFIG.2may be an example of the STA104or the AP102. In some implementations, the wearable device204-aand the wearable device204-bmay be associated with a same group of wearable devices and may fall back from using a shared address to using individual addresses to perform a connection setup procedure with the AP102(for over-the-AP relay communication) in examples in which the AP102is a non-QoS AP. For example, the process flow400illustrates communication between the wearable device204-a, the wearable device204-b, and the AP102in examples in which the AP102fails a QoS conformance test.

In the following description of the process flow400, the operations may be performed (such as reported or provided) in a different order than the order shown, or the operations performed by the example devices may be performed in different orders or at different times. For example, specific operations also may be left out of the process flow400, or other operations may be added to the process flow400. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

At402, the wearable device204-amay transmit an indication of the target AP102to the wearable device204-b. In some implementations, the wearable device204-amay transmit the indication of the target AP102to the wearable device204-bin accordance with measuring, receiving an indication, or otherwise determining that the AP102is a non-QoS AP (which the wearable device204-amay determine at336with reference toFIG.3). In accordance with communicating the indication of the target AP102, the wearable device204-aand the wearable device204-bmay proceed in accordance with an individual provisioning mechanism according to which each of the wearable device204-aand the wearable device204-bperform separate connection setup procedures with the AP102.

At404, for example, the wearable device204-aand the AP102may exchange one or more authentication packets. For example, the wearable device204-amay transmit an authentication request to the AP102and the AP102may transmit an authentication response corresponding to the authentication request. In some implementations, the wearable device204-aand the AP102may include an indication of a first device-specific address (such as a MAC address specific to the wearable device204-a) in both of the authentication request and the authentication response in accordance with the individual provisioning, the first device-specific address being specific to the wearable device204-a.

At406, the wearable device204-band the AP102may communicate one or more authentication packets. For example, the wearable device204-bmay transmit an authentication request to the AP102and the AP102may transmit an authentication response corresponding to the authentication request. In some implementations, the wearable device204-band the AP102may include an indication of a second device-specific address (such as a MAC address specific to the wearable device204-b) in both of the authentication request and the authentication response in accordance with the individual provisioning, the second device-specific address being specific to the wearable device204-b.

At408, the wearable device204-aand the AP102may communicate one or more association packets. For example, the wearable device204-amay transmit an association request to the AP102and the AP102may transmit an association response corresponding to the association request. In some implementations, the wearable device204-aand the AP102may include an indication of the first device-specific address in both of the association request and the association response in accordance with the individual provisioning.

At410, the wearable device204-band the AP102may communicate one or more association packets. For example, the wearable device204-bmay transmit an association request to the AP102and the AP102may transmit an association response corresponding to the association request. In some implementations, the wearable device204-band the AP102may include an indication of the second device-specific address in both of the association request and the association response in accordance with the individual provisioning.

At412, the wearable device204-aand the AP102may communicate one or more packets associated with an ARP negotiation. In some implementations, the wearable device204-aand the AP102may include an indication of the first device-specific address in the one or more packets associated with the ARP negotiation in accordance with the individual provisioning.

At414, the wearable device204-band the AP102may communicate one or more packets associated with an ARP negotiation. In some implementations, the wearable device204-band the AP102may include an indication of the second device-specific address in the one or more packets associated with the ARP negotiation in accordance with the individual provisioning.

At416, the wearable device204-aand the AP102may communicate one or more packets associated with a DHCP negotiation. In some aspects, the one or more packets associated with the DHCP negotiation may indicate, to the wearable device204-a, a first IP address. In some implementations, the first IP address may correspond exclusively to the wearable device204-ain accordance with the individual provisioning.

At418, the wearable device204-band the AP102may communicate one or more packets associated with a DHCP negotiation. In some aspects, the one or more packets associated with the DHCP negotiation may indicate, to the wearable device204-b, a second IP address. In some implementations, the second IP address may correspond exclusively to the wearable device204-bin accordance with the individual provisioning.

In accordance with performing separate connection setup procedures, the wearable device204-aand the wearable device204-bmay communicate with the AP102as two distinct devices. In some implementations, the wearable device204-aand the wearable device204-bmay manage power consumption by individually setting a power management bit to 0 or 1 (within, for example, a QoS NULL packet) to indicate a respective power management state.

FIG.5shows an example flowchart500that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The flowchart500may implement or be implemented to realize or facilitate aspects of the WLAN100, the signaling diagram200, the process flow300, or the process flow400. For example, one or more wearable devices, such as the wearable device wearable device204-aor the wearable device wearable device204-b, may perform operations associated with the flowchart500to measure, receive an indication, or otherwise determine whether to employ a shared address-based provisioning mechanism (which may be referred to as vML-based provisioning) or an individual provisioning mechanism.

At502, the wearable device may determine whether a first wireless communication link is established with at least one other wearable device of a group of wearable devices. In some implementations, for example, a group of wearable devices may establish the first wireless communication link for communication between two or more wearable devices and may use the first wireless communication link to exchange (such as transmit and/or receive) control traffic between the two or more wearable devices. Such control traffic may include a first set of packets that wearable devices exchange to negotiate, select, and/or assign a shared address and respective link IDs corresponding to each respective wearable device. For example, a set of wearable devices may piggyback additional Wi-Fi information (such as information pertaining to an XPAN) that is common to (such as applicable to) the set of wearable devices over the first wireless communication link. Such a first wireless communication link may be an example of any peer-to-peer link and may function as a “backhaul” link between two or more wearable devices. In examples in which a group of wearable devices are wireless earbuds, the first wireless communication link may be a Bluetooth link (such as a BLE link) and the wireless earbuds may perform BLE control exchanges via the first wireless communication link. In examples in which the first wireless communication link is not established, the wearable device may determine to employ an individual provisioning mechanism (at504).

At506, in examples in which the first wireless communication link is established, the wearable device may determine whether a wireless communication device with which the wearable device establishes a second wireless communication link is a traffic source/sink device or another wireless communication device (such as an AP102) along a relay path between the traffic source/sink device and the wearable device. Direct communication between the wearable device and the traffic source/sink device may be referred to as point-to-point communication and indirect communication between the wearable device and the traffic source/sink device via another wireless communication device may be referred to as over-the-AP communication.

At508, in examples in which the communication is over-the-AP, the wearable device may perform one or more operations associated with a candidate AP selection. For example, the wearable device may select a candidate AP102for routing traffic between the wearable device and the traffic source/sink device.

At510, the wearable device may determine whether the candidate AP102supports wireless multi-media (WMM). In examples in which the candidate AP102does not support WMM, the wearable device may employ an individual provisioning mechanism (at504).

At512, in examples in which the candidate AP102supports WMM or in examples in which the communication is point-to-point, the wearable device may negotiate primary and secondary roles with other wearable devices in the group of wearable devices. In some implementations, the wearable device may perform such negotiation by communicating (such as transmitting and/or receiving) one or more packets with other wearable devices in the group via, for example, the first wireless communication link (such as via at least one first wireless communication link).

At514, the wearable device may further negotiate a shared address corresponding to an association of the wearable device and the other wearable devices in the group of wearable devices. Such a shared address may be understood and equivalently referred to herein as a vML address.

At516, the wearable device may further negotiate one or more aspects associated with a scanning operation, authentication, association, EAPOL and/or security keys, ARP, and/or DHCP. In other words, for example, the wearable devices may negotiate (such as coordinate) one or more aspects associated with how a second wireless communication link with the wireless communication device is to be established.

At518, the wearable device may determine whether the wireless communication device with which the second wireless communication link is established is present in a vML whitelist or a vML blacklist. In other words, the wearable device may determine whether the wireless communication device is present in a first list of devices (such as the vML whitelist) for which shared address-based provisioning is allowed or in a second list of devices (such as the vML blacklist) for which shared address-based provisioning is not allowed. In some implementations, the wearable device may determine whether the wireless communication device is present in one of the first list of devices or the second list of devices in accordance with searching one or both lists for an ID (or some other identification information) associated with the wireless communication device. In examples in which the wireless communication device is present in the second list of devices, the wearable device may employ an individual provisioning mechanism (at504).

At520, in examples in which the wireless communication device is present in the first list of devices, the wearable device may employ shared address-based provisioning (such as vML-based provisioning).

Alternatively, at522, in examples in which the wireless communication device is not present in either the first list of devices or the second list of devices, the wearable device may perform or otherwise participate in a QoS conformance test associated with whether an end-to-end path between the wearable device and a traffic source/sink device supports QoS-based traffic prioritization. At524, in examples in which the end-to-end path fails the QoS conformance test, the wearable device may add the wireless communication device to the second list of devices (such as the vML blacklist). At526, in examples in which the end-to-end path passes the QoS conformance test, the wearable device may add the wireless communication device to the first list of devices (such as the vML whitelist). In accordance with such a maintenance of the first list of devices and the second list of devices, the wearable device may refrain from repeating a QoS conformance test for a wireless communication device for which a previous QoS conformance test has already been performed. In some aspects, the wearable device may maintain the first list of devices and the second list of devices for as long as the wearable device is connected to the internet (such as until the wearable device is placed into a case, runs out of battery, or otherwise disconnects). In some other aspects, the wearable device may maintain the first list of devices and the second list of devices for a threshold time period, at which time the wearable device may refresh (such as purge) the lists and subsequently build out the lists again by performing fresh QoS conformance tests.

FIG.6shows an example communication timeline600that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The communication timeline600may implement or be implemented to realize or facilitate aspects of the WLAN100, the signaling diagram200, the process flow300, the process flow400, or the flowchart500. For example, the communication timeline600illustrates communication between the wearable device204-band the wireless communication device202, which may be examples of corresponding devices illustrated by and described with reference toFIGS.2-4. In some implementations, the communication timeline600illustrates how the wearable device204-bmay perform link ID-based early receive termination (to save battery power).

For example, in implementations in which wearable devices of a group of wearable devices perform link ID-based early termination, a wearable device may decode or parse a portion (such as a frame header) of a packet to determine whether the packet is intended for the wearable device or another wearable device of the group. In some implementations, link ID-based early termination may be an alternative to link ID-based TWT sessions in accordance with a capability of the wireless communication device202. For example, some APs102may not support TWT session setup or U-APSD, due to which link ID-based delivery over a negotiated time window may not be feasible.

Further, because power management states (which also may be referred to as power management modes) may be defined at a peer level (such as for each shared address), all wearable devices of a group of wearable devices may enter a given power management state at the same time and, because an AP102may deliver packets associated with all link IDs during a same awake time, each wearable device may employ an early receive termination in accordance with which link ID a given packet is associated with. In some implementations, for example, a wearable device may determine whether a packet is intended for itself or another wearable device in accordance with a link ID (such as TID or traffic class) associated with the packet. As such, the wearable device may decode packets associated with a link ID corresponding to itself and may refrain from decoding packets associated with a different link ID. In some implementations, each wearable device of a group of wearable devices may support or be configured in accordance with hardware to terminate packet reception in accordance with a programmed link ID value (such as a programmed TID or traffic class).

For example, as illustrated in the example of the communication timeline600, the wearable device204-bmay receive a packet220including a frame header indicating the link ID “a,” which, in accordance with previous negotiation, the wearable device204-bmay determine as corresponding to the wearable device204-aand not the wearable device204-b. As such, the wearable device204-bmay refrain from decoding a data portion of the packet220and instead achieve some amount of power savings. For further example, the wearable device204-bmay receive a packet224including a frame header indicating the link ID “b,” which, in accordance with previous negotiation, the wearable device204-bmay determine as corresponding to the wearable device204-b. As such, the wearable device204-bmay decode a data portion of the packet224and, in examples in which the decoding is successful, may transmit an ACK226associated with the packet224to the wireless communication device202. In some implementations, the wearable device204-bmay obtain an indication of the link ID associated with a given packet in accordance with a TID value in the frame header, such as a TID value in a QoS Control field of the frame header.

FIG.7shows an example flowchart700that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The flowchart700may implement or be implemented to realize or facilitate aspects of the WLAN100, the signaling diagram200, the process flow300, the process flow400, the flowchart500, or the communication timeline600. For example, the flowchart700illustrates one or more operations that one or more wearable devices of a group of wearable devices may perform to maintain reliable transmission and/or reception of data. In some implementations, for example, a group of wearable devices may operate in accordance with an independent links mode702according to which each wearable device of the group receives and acknowledges packets associated with its unique link ID and a master link mode704according to which one wearable device receives and acknowledges packets associated with its own unique link ID as well as packets associated with another link ID corresponding to another wearable device of the group. The group of wearable devices may transition or switch between the independent links mode702and the master link mode704in accordance with whether one or more link quality metrics satisfy one or more conditions.

For example, while a group of wearable devices may be collocated and within approximately a same or similar distance from a traffic source/sink device or another wireless communication device along a multi-hop relay path, each wearable device may be a distinct physical device and, likewise, may have differing link conditions. For example, different wearable devices of a group of wearable devices may have different channel states and/or different signal-to-interference plus noise ratio (SINR) measurements, which may lead to considerations on a link-by-link basis associated with downlink rate adaptation and receive signal strength indicator (RSSI) monitoring.

In implementations in which a group of wearable devices are connected to an MLO-capable wireless communication device, each link of the MLO-capable wireless communication device may monitor downlink rate adaptation and RSSI via, for example, packet error rate (PER) tracking for rate adaptation on a link-by-link basis. Additionally, a connected wireless communication device may perform beamforming on each link or frequency independently, such as in accordance with coordinated beamforming (CBF) generation by each wearable device independently and steering from the connected wireless communication device to each wearable device (which may appear as two links of a same MLD for an MLO-capable wireless communication device).

Alternatively, in implementations in which a group of wearable devices are not connected to an MLO-capable wireless communication device, each wearable device may track and detect asymmetry in link condition (such as on a link ID-by-link ID basis) and the group of wearable devices may switch between the independent links mode702and the master link mode704when link quality metrics indicate or suggest a link asymmetry large enough to cause a measurable different in link quality. In other words, the group of wearable devices may switch to the master link mode704during an asymmetry period (such as a time period during which a first link of a first wearable device of the group is associated with first link quality metrics more than a threshold different than second link quality metrics associated with a second link of a second wearable device of the group).

At706, for example, each wearable device of a group of wearable devices may receive data (such as packets) associated with an assigned link ID and may transmit feedback information (such as an ACK) independently.

At708, each wearable device of the group of wearable devices may monitor one or more of an average RSSI, a quantity of retries (such as downlink and/or uplink retries), or a quantity of duplicate ACKs associated with communication between that wearable device and the wireless communication device to which the group of wearable devices is connected.

At710, each wearable device of the group of wearable devices may determine whether a corresponding link is associated with an unreliable link budget. In examples in which no wearable device of the group of wearable devices detects an unreliable link budget, each wearable device of the group of wearable devices may continue monitoring the average RSSI, the quantity of retries, or the quantity of duplicate ACKs between that wearable device and the wireless communication device to which the group of wearable devices is connected (at708). In some implementations, the group of wearable devices may periodically share information associated with average RSSIs, quantities of retries, and/or quantities of duplicate ACKs with each other via at least one first wireless communication link between wearable devices of the group of wearable devices.

At712, in examples in which at least one wearable device detects an unreliable link budget, the group of wearable devices (or at least a subset of the group of wearable devices) may transition from the independent links mode702to the master link mode704and a wearable device with a relatively larger RSSI may take the role of master in accordance with the transition. For example, a first wearable device may take the role of master with respect to a second wearable device that detects an unreliable link budget. In some implementations, a wearable device may detect an unreliable link budget in accordance with measuring a delta between, for example, a first average RSSI measured by the first wearable device and a second average RSSI measured by the second wearable device. In other words, in examples in which the delta between the average RSSIs of the first wearable device and the second wearable device exceeds a threshold, one or both of the first wearable device and the second wearable device may detect an asymmetric link budget and may trigger or identify an unreliable link budget condition for the second wearable device (such as the wearable device with the smaller RSSI). In some other implementations, one or both of the first wearable device and the second wearable device may trigger or identify an unreliable link budget condition in examples in which a quantity of retries (such as downlink retries for packets from a traffic source device or a relay wireless communication device) and/or duplicate ACKs (for packets received by a wearable device but for which corresponding ACKs are unsuccessfully received by a traffic source device or a relay wireless communication device) increase above a threshold, and/or in examples in which an absolute RSSI for a wearable device falls below a threshold.

At714, the first wearable device (such as the master) may receive and decode first packets associated with its own link ID as well as second packets associated with a link ID corresponding to the second wearable device and may forward (such as relay) data received via the second packets to the second wearable device via the first wireless communication link between the first wearable device and the second wearable device. The second wearable device may receive the data from the first wearable device and may transmit feedback information associated with the data to the first wearable device, which the first wearable device may transmit, via one or more BAs, to the wireless communication device to which the group of wearable devices is connected. In other words, the first wearable device may transmit one or more ACKs on behalf of the second wearable device, in addition to transmitting one or more ACKs for packets associated with the link ID corresponding to the first wearable device.

At716, both the first wearable device and the second wearable device may continue monitoring an average RSSI, a quantity of retries, and/or a quantity of duplicate ACKs while operating in accordance with the master link mode704. In some implementations, the group of wearable devices may periodically share information associated with average RSSIs, quantities of retries, and/or quantities of duplicate ACKs with each other via at least one first wireless communication link between wearable devices of the group of wearable devices.

At718, each wearable device of the group of wearable devices (including, notably, the second wearable device) may determine whether a corresponding link is associated with an unreliable link budget. In examples in which at least one wearable devices does not have a reliable link budget (such as in examples in which the second wearable device still detects an unreliable link budget), the first wearable device may continue operating as a master and may continue receiving packets associated with multiple different link IDs (for forwarding to one or more wearable devices still suffering from an unreliable link budget). Alternatively, in examples in which all wearable devices of the group of wearable devices detect a reliable link budget (in examples in which link conditions at the second wearable device improve), the group of wearable devices may transition from the master link mode704to the independent links mode702. Further, independent of the group of wearable devices switching between the independent links mode702and the master link mode704, the wireless communication device to which the group of wearable devices is connected by perform rate adaptation on a link-by-link (such as TID-by-TID) basis.

In some implementations, in the master link mode704, a master wearable device may stay awake for more time, forward data to at least one other wearable device, and send ACK(s) on behalf of at least one other wearable device. As such, the master wearable device may experience relatively greater power consumption in the master link mode704and, in some implementations, may support one or more mechanisms to mitigate how long the group of wearable devices is in the master link mode704. For example, to facilitate a switching from the master link mode704to the independent links mode702, a master wearable device may transmit an indication of a recommended coding rate, such as a recommend modulation and coding scheme (MCS), for a wearable device suffering from an unreliable link budget. In such examples, the recommended coding rate may be for both communication between the master wearable device and the wireless communication device and communication between the wearable device suffering from the unreliable link budget and the wireless communication device.

The master wearable device may indicate the recommended coding rate via various packet types, such as via a QoS null packet or any type of management frame sent to the wireless communication device. In some implementations, via which field the master wearable device indicates the recommended coding rate may vary in accordance with a capability of the master wearable device and/or of the wireless communication device. For high throughput (HT), for example, the master wearable device may indicate the recommended coding rate in an MCS feedback (MFB)/antenna selection (ASELC) field in a link adaptation control field in HT control. For very high throughput (VHT), the master wearable device may indicate the recommended coding rate in a VHT-MCS field in the MFB field in the VHT variant HT control field. For high efficiency (HE), the master wearable device may indicate the recommended coding rate in an HE-MCS field in an HE link adaptation (HLA) control field. For extremely high throughput (EHT), the master wearable device may indicate the recommended coding rate in an EHT-MCS field in the EHT link adaptation (ELA) control field. The wireless communication device receiving the indication of the recommended coding rate may update one or more link parameters (such as an MCS value) for communication with the master wearable device and one or more other wearable devices in the group of wearable devices in accordance with the indication.

FIG.8shows example XPAN topologies800,801, and802that support managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The XPAN topologies800,801, and802may implement or be implemented to realize or facilitate aspects of the WLAN100, the signaling diagram200, the process flow300, the process flow400, the flowchart500, the communication timeline600, or the flowchart700. For example, each of the XPAN topologies800,801, and802illustrate example deployment scenarios of one or more STAs104, one or more APs102, the wearable device204-a, and the wearable device204-b.

As illustrated by the XPAN topology800, the AP102may communicate with the STA104via a link803and the STA104may communicate with the wearable device204-aand the wearable device204-bvia a link804-aand a link804-b, respectively. The link803may be an example of a 2.4 GHz link and the link804-aand the link804-bmay be examples of 5 GHz links. The STA104also may communicate with the wearable device204-avia a link806, which may be an example of a Bluetooth link. The wearable device204-aand the wearable device204-bmay communicate with each other via a link808, which may be an example of a Bluetooth link. The link804-aand the link804-bmay be examples of XPAN links and the XPAN topology800may be an example of an XPAN direct link.

As illustrated by the XPAN topology801, the AP102may communicate with the STA104via the link803and the AP102may communicate with the wearable device204-aand the wearable device204-bvia a link810-aand a link810-b, respectively. The link803, the link810-a, and the link810-bmay be examples of 5 GHz links. The STA104may communicate with the wearable device204-avia a link806, which may be an example of a Bluetooth link. The wearable device204-aand the wearable device204-bmay communicate with each other via the link808, which may be an example of a Bluetooth link. In some implementations, the wearable device204-bmay support a mirroring technology and may attempt to “sniff” packets sent via the link806via a mirroring link812. The link803, the link810-a, and the link810-bmay be examples of XPAN links and the XPAN topology801may be an example of an XPAN infrastructure link on standby.

As illustrated by the XPAN topology802, the AP102may communicate with the STA104via the link803and the AP102may communicate with the wearable device204-aand the wearable device204-bvia the link810-aand the link810-b, respectively. The link803, the link810-a, and the link810-bmay be examples of 5 GHz links. The wearable device204-aand the wearable device204-bmay communicate with each other via the link808, which may be an example of a Bluetooth link. The STA104may lack a direct link between the STA104and the earbuds. Instead, the AP102may control the system or relay packets and messages between the earbuds and the STA104. The link803, the link810-a, and the link810-bmay be examples of XPAN links and the XPAN topology802may be an example of an XPAN infrastructure deployment.

FIG.9shows example XPAN topologies900and901that support managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The XPAN topologies900and901may implement or be implemented to realize or facilitate aspects of the WLAN100, the signaling diagram200, the process flow300, the process flow400, the flowchart500, the communication timeline600, or the flowchart700. For example, each of the XPAN topologies900and901illustrate example deployment scenarios of one or more STAs104, one or more APs102, the wearable device204-a, and the wearable device204-b.

As illustrated by the XPAN topology900, the AP102may communicate with the STA104-bvia a link902and the AP102may communicate with the wearable device204-aand the wearable device204-bvia a link904-aand a link904-b, respectively. The link902, the link904-a, and the link904-bmay be examples of 5 GHz links. The STA104-amay communicate with the wearable device204-avia a link906, which may be an example of a Bluetooth link. The wearable device204-aand the wearable device204-bmay communicate with each other via the link908, which may be an example of a Bluetooth link. In some implementations, the wearable device204-bmay support a mirroring technology and may attempt to “sniff” packets sent via the link806via a mirroring link910. The link902, the link904-a, and the link904-bmay be examples of XPAN links and the XPAN topology900may be an example of a Bluetooth+XPAN (infrastructure) dual link.

As illustrated by the XPAN topology901, the AP102may lack a connection to other devices. In such examples, the STA104-amay communicate with the wearable device204-avia the link906and the wearable device204-aand the wearable device204-bmay communicate with each other via the link908, and each of the link906and the link908may be examples of Bluetooth links. In some implementations, the wearable device204-bmay support a mirroring technology and may attempt to “sniff” packets sent via the link806via a mirroring link910. The STA104-bmay communicate with the wearable device204-aand the wearable device204-bvia a link912-aand a link912-b, respectively. The link912-aand the link912-bmay be examples of 5 GHz links. The link912-aand the link912-bmay be examples of XPAN links and the XPAN topology901may be an example of a Bluetooth+XPAN (direct) dual link.

FIG.10shows example XPAN topologies1000and1001that support managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The XPAN topologies1000and1001may implement or be implemented to realize or facilitate aspects of the WLAN100, the signaling diagram200, the process flow300, the process flow400, the flowchart500, the communication timeline600, or the flowchart700. For example, each of the XPAN topologies1000and1001illustrate example deployment scenarios of one or more STAs104, one or more APs102, the wearable device204-a, and the wearable device204-b.

As illustrated by the XPAN topology1000, the AP102may communicate with the STA104-bvia a link1002and may communicate with the STA104-avia a link1004. The link1002and the link1004may be examples of 5 GHz links. The AP102also may communicate with the wearable device204-aand the wearable device204-bvia a link1006-aand a link1006-b, respectively. The link1006-aand the link1006-bmay be examples of 5 GHz links. The wearable device204-aand the wearable device204-bmay communicate with each other via a link1008, which may be an example of a Bluetooth link. The link1002, the link1004, the link1006-a, and the link1006-bmay be examples of XPAN links and the XPAN topology1000may be an example of an XPAN+XPAN dual link.

As illustrated by the XPAN topology1001, the AP102may communicate with the STA104-bvia the link1002and may communicate with the STA104-avia the link1004. The link1002and the link1004may be examples of 5 GHz links. The STA104-amay communicate with the wearable device204-aand the wearable device204-bvia a link1010-aand a link1010-b, respectively. The link1010-aand the link1010-bmay be examples of 5 GHz links. The wearable device204-aand the wearable device204-bmay communicate with each other via the link1008, which may be an example of a Bluetooth link. The link1002, the link1004, the link1010-a, and the link1010-bmay be examples of XPAN links and the XPAN topology1001may be an example of an XPAN direct dual link.

FIG.11shows a block diagram of an example wireless communication device that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address. In various examples, the wireless communication device can be a chip, SoC, chipset, package or device that may include: one or more modems (such as, a Wi-Fi (IEEE 802.11) modem or a cellular modem such as 3GPP 4G LTE or 5G compliant modem); one or more processors, processing blocks or processing elements (collectively “at least one processor”); one or more radios (collectively “at least one radio”); and one or more memories or memory blocks (collectively “at least one memory”). In some implementations, the at least one processor may include multiple processors, and the at least one memory may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions described herein (as part of a processing system).

In some implementations, the wireless communication device can be a device for use in a STA or a wearable device, such as STA104described with reference toFIG.1or one or both of a wearable device204-aand a wearable device204-bas described with reference toFIG.2. In some aspects, a STA104may be an example of a wearable device. In some other examples, the wireless communication device can be a STA that includes such a chip, SoC, chipset, package or device as well as multiple antennas. The wireless communication device is capable of transmitting and receiving wireless communication in the form of, for example, wireless packets. For example, the wireless communication device can be configured or operable to transmit and receive packets in the form of physical layer PPDUs and MPDUs conforming to one or more of the IEEE 802.11 family of wireless communication protocol standards. In some implementations, the wireless communication device also includes or can be coupled with at least one application processor which may be further coupled with at least one memory. In some implementations, the wireless communication device further includes a user interface (UI) (such as a touchscreen or keypad) and a display, which may be integrated with the UI to form a touchscreen display. In some implementations, the wireless communication device may further include one or more sensors such as, for example, one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors.

The wireless communication device includes a peer communication component1105, a connection setup component1110, and a link ID-based communication component1115. Portions of one or more of the peer communication component1105, the connection setup component1110, and the link ID-based communication component1115may be implemented at least in part in hardware or firmware. For example, one or more of the peer communication component1105, the connection setup component1110, and the link ID-based communication component1115may be implemented at least in part by at least one modem. In some implementations, at least some of the peer communication component1105, the connection setup component1110, and the link ID-based communication component1115are implemented at least in part by at least one processor and as software stored in at least one memory. For example, portions of one or more of the peer communication component1105, the connection setup component1110, and the link ID-based communication component1115can be implemented as non-transitory instructions (or “code”) executable by the at least one processor to perform the functions or operations of the respective module.

In some implementations, the at least one processor may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the wireless communication device). For example, a processing system of the wireless communication device may refer to a system including the various other components or subcomponents of the wireless communication device, such as the at least one processor, or at least one transceiver, or at least one communication manager, or other components or combinations of components of the wireless communication device. The processing system of the wireless communication device may interface with other components of the wireless communication device, and may process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of the wireless communication device may include a processing system, a first interface to output information and a second interface to obtain information. In some implementations, the first interface may refer to an interface between the processing system of the chip or modem and a transmitter, such that the wireless communication device may transmit information output from the chip or modem. In some implementations, the second interface may refer to an interface between the processing system of the chip or modem and a receiver, such that the wireless communication device may obtain information or signal inputs, and the information may be passed to the processing system. A person having ordinary skill in the art will readily recognize that the first interface also may obtain information or signal inputs, and the second interface also may output information or signal outputs.

The wireless communication device may support wireless communication at a first wearable or handheld wireless device in accordance with examples as disclosed herein. The peer communication component1105is capable of, configured to, or operable to support a means for communicating, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associated with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device. The connection setup component1110is capable of, configured to, or operable to support a means for transmitting, in association with establishing a second wireless communication link with a wireless communication device, one or more second packets indicating the shared address, the first link identifier, and the second link identifier. The link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving, from the wireless communication device via the second wireless communication link, one or more third packets associated with the first link identifier.

In some implementations, to support communicating the one or more first packets with at least the second wearable or handheld wireless device via the first wireless communication link, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting one or more of the one or more first packets to, and receiving one or more of the one or more first packets from, the second wearable or handheld wireless device in accordance with a negotiation of the shared address with the second wearable or handheld wireless device.

In some implementations, to support communicating the one or more first packets with at least the second wearable or handheld wireless device via the first wireless communication link, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting one or more of the one or more first packets to, and receiving one or more of the one or more first packets from, the second wearable or handheld wireless device in accordance with an assignment of the first link identifier to the first wearable or handheld wireless device and the second link identifier to the second wearable or handheld wireless device.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, to the wireless communication device, a fourth packet in association with an establishment of a first block acknowledgment session between the wireless communication device and the first wearable or handheld wireless device, the fourth packet including an indication of the first link identifier. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, to the wireless communication device, one or more block acknowledgments associated with the one or more third packets.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, to the wireless communication device, a fourth packet indicating the shared address and a power management state corresponding to the shared address.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for receiving, from the second wearable or handheld wireless device via the first wireless communication link, a fifth packet indicating that the second wearable or handheld wireless device is in the power management state, where transmitting the fourth packet indicating the power management state is in association with receiving the fifth packet.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for communicating, with at least the second wearable or handheld wireless device via the first wireless communication link, one or more fourth packets in accordance with a negotiation of one or more of: one or more security keys associated with communication with the wireless communication device, a dynamic host configuration protocol address, or one or more address resolution protocol tables, where the first wearable or handheld wireless device establishes the second wireless communication link in accordance with the negotiation.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving, from the wireless communication device, information indicative of a schedule of communication time intervals corresponding to the first link identifier. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for monitoring the second wireless communication link in accordance with the schedule of the communication time intervals, where receiving the one or more third packets is in association with monitoring the second wireless communication link.

In some implementations, each of the one or more third packets includes a respective frame header indicating the first link identifier, and the link ID-based communication component1115is capable of, configured to, or operable to support a means for decoding data portions of the one or more third packets in accordance with frame headers of the one or more third packets indicating the first link identifier. In some implementations, each of the one or more third packets includes a respective frame header indicating the first link identifier, and the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving one or more fourth packets each including a respective frame header indicating the second link identifier. In some implementations, each of the one or more third packets includes a respective frame header indicating the first link identifier, and the link ID-based communication component1115is capable of, configured to, or operable to support a means for refraining from decoding data portions of the one or more fourth packets in accordance with frame headers of the one or more fourth packets indicating the second link identifier.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving, from the wireless communication device, information indicative of a first mapping of the first link identifier to the second wireless communication link and a second mapping of the second link identifier to a third wireless communication link. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for tuning at least one radio to the second wireless communication link in accordance with the first mapping, where receiving the one or more third packets is in association with tuning the at least one radio to the second wireless communication link, and where the second wireless communication link is associated with a first frequency channel and the third wireless communication link is associated with a second frequency channel different than the first frequency channel.

In some implementations, the connection setup component1110is capable of, configured to, or operable to support a means for receiving an indication that the wireless communication device is capable of quality of service-based traffic flow prioritization. In some implementations, the connection setup component1110is capable of, configured to, or operable to support a means for establishing the second wireless communication link with the wireless communication device using the shared address in accordance with the wireless communication device being capable of the quality of service-based traffic flow prioritization.

In some implementations, to support receiving the indication that the wireless communication device is capable of the quality of service-based traffic flow prioritization, the connection setup component1110is capable of, configured to, or operable to support a means for receiving identification information of the wireless communication device, where the identification information indicates that the wireless communication device is present in a first list of devices for which use of the shared address is allowed and absent from a second list of devices for which use of the shared address is not allowed.

In some implementations, a presence of the identification information of the wireless communication device in either the first list of devices or the second list of devices is indicative of a previous quality of service conformance test for the wireless communication device. In some implementations, being present in the first list of devices is indicative of a successful quality of service conformance test and being present in the second list of devices is indicative of an unsuccessful quality of service conformance test.

In some implementations, to support receiving the indication that the wireless communication device is capable of the quality of service-based traffic flow prioritization, the connection setup component1110is capable of, configured to, or operable to support a means for receiving a packet indicating that an end-to-end path between a traffic source device and the first wearable or handheld wireless device is capable of the quality of service-based traffic flow prioritization, where the wireless communication device is the traffic source device or another wireless communication device along the end-to-end path.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for communicating, with the second wearable or handheld wireless device via the first wireless communication link, information indicative of one or more link quality metrics pertaining to first communication between the first wearable or handheld wireless device and the wireless communication device and second communication between the second wearable or handheld wireless device and the wireless communication device.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for receiving an indication that a link quality metric pertaining to the second communication between the second wearable or handheld wireless device and the wireless communication device fails to satisfy a condition. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving one or more fourth packets including the second link identifier in accordance with the link quality metric failing to satisfy the condition. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, to the second wearable or handheld wireless device via the first wireless communication link, data received via the one or more fourth packets in accordance with the one or more fourth packets including the second link identifier.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for receiving, from the second wearable or handheld wireless device via the first wireless communication link, feedback information associated with the data. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, to the wireless communication device, one or more block acknowledgments associated with the one or more fourth packets, the one or more block acknowledgments indicating the feedback information received from the second wearable or handheld wireless device.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for receiving an indication that the link quality metric pertaining to the second communication between the second wearable or handheld wireless device and the wireless communication device satisfies the condition. In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for refraining from decoding any packets including the second link identifier in accordance with the link quality metric satisfying the condition, where the first wearable or handheld wireless device temporarily receives the one or more fourth packets including the second link identifier while the link quality metric fails to satisfy the condition.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, to the wireless communication device in accordance with the link quality metric failing to satisfy the condition, information indicative of a recommended coding rate.

In some implementations, the recommended coding rate is for both the first communication between the first wearable or handheld wireless device and the wireless communication device and the second communication between the second wearable or handheld wireless device and the wireless communication device.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting an indication that a link quality metric pertaining to the first communication between the first wearable or handheld wireless device and the wireless communication device fails to satisfy a condition. In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for receiving data from the second wearable or handheld wireless device via the first wireless communication link in accordance with the link quality metric failing to satisfy the condition. In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting, to the second wearable or handheld wireless device via the first wireless communication link, feedback information associated with the data.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting an indication that the link quality metric pertaining to the first communication between the first wearable or handheld wireless device and the wireless communication device satisfies the condition. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving, via the second wireless communication link, packets including the first link identifier in accordance with the link quality metric satisfying the condition, where reception of any packets via the second wireless communication link is temporarily paused while the link quality metric fails to satisfy the condition.

In some implementations, the connection setup component1110is capable of, configured to, or operable to support a means for receiving an indication of a handover of the first wearable or handheld wireless device from the wireless communication device to a second wireless communication device. In some implementations, the connection setup component1110is capable of, configured to, or operable to support a means for receiving an indication that the second wireless communication device is incapable of quality of service-based traffic flow prioritization. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, in association with establishing a third wireless communication link with the second wireless communication device, one or more fourth packets indicating a device-specific address, the third wireless communication link being exclusively for the first wearable or handheld wireless device in accordance with the one or more fourth packets indicating the device-specific address.

In some implementations, the first link identifier and the second link identifier are associated with a same channel access category.

In some implementations, the one or more third packets include indications of a first type of service for the first wearable or handheld wireless device, the first type of service being mapped to the first link identifier.

In some implementations, the one or more second packets include one or more of an authentication frame, an association frame, an address resolution protocol frame, a dynamic host configuration protocol frame, an extensible authentication protocol over local area network frame, a key handshake frame, and an add block acknowledgment frame.

In some implementations, communication of the one or more first packets with the second wearable or handheld wireless device indicates, to the second wearable or handheld wireless device, to refrain from separately establishing a wireless communication link with the wireless communication device.

In some implementations, the first wireless communication link is a secure peer-to-peer link and the second wireless communication link is a wireless local area network link.

In some implementations, the wireless communication device is a traffic source device, an access point, or a compute device.

Additionally, or alternatively, the wireless communication device may support wireless communication at a first wearable or handheld wireless device in accordance with examples as disclosed herein. In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for communicating, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associated with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving, from a wireless communication device via a second wireless communication link, one or more second packets associated with the first link identifier, the second wireless communication link being in association with an establishment using the shared address.

In some implementations, to support communicating the one or more first packets with at least the second wearable or handheld wireless device via the first wireless communication link, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting one or more of the one or more first packets to, and receiving one or more of the one or more first packets from, the second wearable or handheld wireless device in accordance with a negotiation of the shared address with the second wearable or handheld wireless device.

In some implementations, to support communicating the one or more first packets with at least the second wearable or handheld wireless device via the first wireless communication link, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting one or more of the one or more first packets to, and receiving one or more of the one or more first packets from, the second wearable or handheld wireless device in accordance with an assignment of the first link identifier to the first wearable or handheld wireless device and the second link identifier to the second wearable or handheld wireless device.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, to the wireless communication device, a third packet in association with an establishment of a first block acknowledgment session between the wireless communication device and the first wearable or handheld wireless device, the third packet including an indication of the first link identifier. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, to the wireless communication device, one or more block acknowledgments associated with the one or more second packets.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for communicating, with at least the second wearable or handheld wireless device via the first wireless communication link, one or more third packets in accordance with a negotiation of one or more of: one or more security keys associated with communication with the wireless communication device, a dynamic host configuration protocol address, or one or more address resolution protocol tables, where the second wearable or handheld wireless device establishes the second wireless communication link in accordance with the negotiation.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving, from the wireless communication device, information indicative of a schedule of communication time intervals corresponding to the first link identifier. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for monitoring the second wireless communication link in accordance with the schedule of the communication time intervals, where receiving the one or more second packets is in association with monitoring the second wireless communication link.

In some implementations, each of the one or more second packets includes a respective frame header indicating the first link identifier, and the link ID-based communication component1115is capable of, configured to, or operable to support a means for decoding data portions of the one or more second packets in accordance with frame headers of the one or more second packets indicating the first link identifier. In some implementations, each of the one or more second packets includes a respective frame header indicating the first link identifier, and the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving one or more third packets each including a respective frame header indicating the second link identifier. In some implementations, each of the one or more second packets includes a respective frame header indicating the first link identifier, and the link ID-based communication component1115is capable of, configured to, or operable to support a means for refraining from decoding data portions of the one or more third packets in accordance with frame headers of the one or more third packets indicating the second link identifier.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving, from the wireless communication device, information indicative of a first mapping of the first link identifier to the second wireless communication link and a second mapping of the second link identifier to a third link. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for tuning at least one radio to the second wireless communication link in accordance with the first mapping, where receiving the one or more second packets is in association with tuning the at least one radio to the second wireless communication link, and where the second wireless communication link is associated with a first frequency channel and the third link is associated with a second frequency channel different than the first frequency channel.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for communicating, with the second wearable or handheld wireless device via the first wireless communication link, information indicative of one or more link quality metrics pertaining to first communication between the first wearable or handheld wireless device and the wireless communication device and second communication between the second wearable or handheld wireless device and the wireless communication device.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for receiving an indication that a link quality metric pertaining to the second communication between the second wearable or handheld wireless device and the wireless communication device fails to satisfy a condition. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving one or more third packets including the second link identifier in accordance with the link quality metric failing to satisfy the condition. In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting, to the second wearable or handheld wireless device via the first wireless communication link, data received via the one or more third packets in accordance with the one or more third packets including the second link identifier.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for receiving, from the second wearable or handheld wireless device via the first wireless communication link, feedback information associated with the data. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, to the wireless communication device, one or more block acknowledgments associated with the one or more third packets, the one or more block acknowledgments indicating the feedback information received from the second wearable or handheld wireless device.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for receiving an indication that the link quality metric pertaining to the second communication between the second wearable or handheld wireless device and the wireless communication device satisfies the condition. In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for refraining from decoding any packets including the second link identifier in accordance with the link quality metric satisfying the condition, where the first wearable or handheld wireless device temporarily receives the one or more third packets including the second link identifier while the link quality metric fails to satisfy the condition.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, to the wireless communication device in accordance with the link quality metric failing to satisfy the condition, information indicative of a recommended coding rate.

In some implementations, the recommended coding rate is for both the first communication between the first wearable or handheld wireless device and the wireless communication device and the second communication between the second wearable or handheld wireless device and the wireless communication device.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting an indication that a link quality metric pertaining to the first communication between the first wearable or handheld wireless device and the wireless communication device fails to satisfy a condition. In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for receiving data from the second wearable or handheld wireless device via the first wireless communication link in accordance with the link quality metric failing to satisfy the condition. In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting, to the second wearable or handheld wireless device via the first wireless communication link, feedback information associated with the data.

In some implementations, the peer communication component1105is capable of, configured to, or operable to support a means for transmitting an indication that the link quality metric pertaining to the first communication between the first wearable or handheld wireless device and the wireless communication device satisfies the condition. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving, via the second wireless communication link, packets including the first link identifier in accordance with the link quality metric satisfying the condition, where reception of any packets via the second wireless communication link is temporarily paused while the link quality metric fails to satisfy the condition.

In some implementations, the connection setup component1110is capable of, configured to, or operable to support a means for receiving an indication of a handover, of the association of the wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, from the wireless communication device to a second wireless communication device. In some implementations, the connection setup component1110is capable of, configured to, or operable to support a means for receiving an indication that the second wireless communication device is incapable of quality of service-based traffic flow prioritization. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, in association with establishing a third wireless communication link with the second wireless communication device, one or more third packets indicating a device-specific address, the third wireless communication link being exclusively for the first wearable or handheld wireless device in accordance with the one or more third packets indicating the device-specific address.

In some implementations, the first link identifier and the second link identifier are associated with a same channel access category.

In some implementations, the one or more second packets include indications of a first type of service for the first wearable or handheld wireless device, the first type of service being mapped to the first link identifier.

In some implementations, communication of the one or more first packets with the second wearable or handheld wireless device indicates, to the first wearable or handheld wireless device, to refrain from separately establishing a wireless communication link with the wireless communication device.

In some implementations, the first wireless communication link is a secure peer-to-peer link and the second wireless communication link is a wireless local area network link.

In some implementations, the wireless communication device is a traffic source device, an access point, or a compute device.

Additionally, or alternatively, the wireless communication device may support wireless communication at a wireless communication device in accordance with examples as disclosed herein. In some implementations, the connection setup component1110is capable of, configured to, or operable to support a means for receiving, in association with establishing a wireless communication link with a first wearable or handheld wireless device, one or more first packets indicating a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and a second wearable or handheld wireless device, a first link identifier corresponding to the first wearable or handheld wireless device, and a second link identifier corresponding to the second wearable or handheld wireless device. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting, in accordance with the shared address, one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving a first indication of the first link identifier via a first packet in association with a first establishment of a first block acknowledgment session between the wireless communication device and the first wearable or handheld wireless device. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving a second indication of the second link identifier via a second packet in association with a second establishment of a second block acknowledgment session between the wireless communication device and the second wearable or handheld wireless device.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting first information indicative of a first schedule of first communication time intervals corresponding to the first link identifier, where transmitting the one or more second packets associated with the first link identifier is associated with the first schedule of the first communication time intervals. In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting second information indicative of a second schedule of second communication time intervals corresponding to the second link identifier, where transmitting the one or more third packets associated with the second link identifier is associated with the second schedule of the second communication time intervals.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for receiving, from the first wearable or handheld wireless device, a packet indicating the shared address and a power management state corresponding to the shared address, where transmitting the one or more second packets and the one or more third packets is associated with the power management state.

In some implementations, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting information indicative of a first mapping of the first link identifier to a first wireless communication link and a second mapping of the second link identifier to a second wireless communication link, where the first wireless communication link is associated with a first frequency channel and the second wireless communication link is associated with a second frequency channel different than the first frequency channel.

In some implementations, to support transmitting the one or more second packets and the one or more third packets, the link ID-based communication component1115is capable of, configured to, or operable to support a means for transmitting the one or more second packets via the first wireless communication link within a first communication time interval and the one or more third packets via the second wireless communication link within a second communication time interval, where the first communication time interval and the second communication time interval at least partially overlap in time.

In some implementations, the connection setup component1110is capable of, configured to, or operable to support a means for transmitting, to the first wearable or handheld wireless device, an indication that the wireless communication device is capable of quality of service-based traffic flow prioritization. In some implementations, the connection setup component1110is capable of, configured to, or operable to support a means for establishing the wireless communication link using the shared address in accordance with the wireless communication device being capable of the quality of service-based traffic flow prioritization.

In some implementations, to support transmitting the indication that the wireless communication device is capable of the quality of service-based traffic flow prioritization, the connection setup component1110is capable of, configured to, or operable to support a means for transmitting identification information of the wireless communication device, where the identification information indicates that the wireless communication device is present in a first list of devices for which use of the shared address is allowed and absent from a second list of devices for which use of the shared address is not allowed.

In some implementations, a presence of the identification information of the wireless communication device in either the first list of devices or the second list of devices is indicative of a previous quality of service conformance test for the wireless communication device. In some implementations, being present in the first list of devices is indicative of a successful quality of service conformance test and being present in the second list of devices is indicative of an unsuccessful quality of service conformance test.

In some implementations, to support transmitting the indication that the wireless communication device is capable of the quality of service-based traffic flow prioritization, the connection setup component1110is capable of, configured to, or operable to support a means for transmitting a packet indicating that an end-to-end path between a traffic source device and the first wearable or handheld wireless device is capable of the quality of service-based traffic flow prioritization, where the wireless communication device is the traffic source device or another wireless communication device along the end-to-end path.

In some implementations, the first link identifier and the second link identifier are association with a same channel access category.

In some implementations, the one or more second packets include indications of a first type of service for the first wearable or handheld wireless device, the first type of service being mapped to the first link identifier, and the one or more third packets include indications of a second type of service for the second wearable or handheld wireless device, the second type of service being mapped to the second link identifier.

In some implementations, each packet of the one or more second packets includes first information that is specific to the first wearable or handheld wireless device and each packet of the one or more third packets includes second information that is specific to the second wearable or handheld wireless device.

In some implementations, each packet of the one or more second packets and the one or more third packets includes both first information that is specific to the first wearable or handheld wireless device and second information that is specific to the second wearable or handheld wireless device.

In some implementations, the one or more first packets include one or more of an authentication frame, an association frame, an address resolution protocol frame, a dynamic host configuration protocol frame, an extensible authentication protocol over local area network frame, a key handshake frame, and an add block acknowledgment frame.

In some implementations, the wireless communication device is a traffic source device.

FIG.12shows a block diagram of an example wireless communication device that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address. In various examples, the wireless communication device can be a chip, SoC, chipset, package or device that may include: one or more modems (such as, a Wi-Fi (IEEE 802.11) modem or a cellular modem such as 3GPP 4G LTE or 5G compliant modem); one or more processors, processing blocks or processing elements (collectively “at least one processor”); one or more radios (collectively “at least one radio”); and one or more memories or memory blocks (collectively “at least one memory”). In some implementations, the at least one processor may include multiple processors, and the at least one memory may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions described herein (as part of a processing system).

In some implementations, the wireless communication device can be a device for use in an AP, a STA, or any other device that may function as a traffic source/sink device, such as AP102or a STA104as described with reference toFIG.1or a wireless communication device202as described with reference toFIG.2. In some other examples, the wireless communication device can be an AP that includes such a chip, SoC, chipset, package or device as well as multiple antennas. The wireless communication device is capable of transmitting and receiving wireless communication in the form of, for example, wireless packets. For example, the wireless communication device can be configured or operable to transmit and receive packets in the form of physical layer PPDUs and MPDUs conforming to one or more of the IEEE 802.11 family of wireless communication protocol standards. In some implementations, the wireless communication device also includes or can be coupled with at least one application processor which may be further coupled with at least one memory. In some implementations, the wireless communication device further includes at least one external network interface that enables communication with a core network or backhaul network to gain access to external networks including the Internet.

The wireless communication device includes a connection setup component1205and a link ID-based communication component1210. Portions of one or more of the connection setup component1205and the link ID-based communication component1210may be implemented at least in part in hardware or firmware. For example, one or more of the connection setup component1205and the link ID-based communication component1210may be implemented at least in part by at least one modem. In some implementations, at least some of the connection setup component1205and the link ID-based communication component1210are implemented at least in part by at least one processor and as software stored in at least one memory. For example, portions of one or more of the connection setup component1205and the link ID-based communication component1210can be implemented as non-transitory instructions (or “code”) executable by the at least one processor to perform the functions or operations of the respective module.

In some implementations, the at least one processor may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the wireless communication device). For example, a processing system of the wireless communication device may refer to a system including the various other components or subcomponents of the wireless communication device, such as the at least one processor, or at least one transceiver, or at least one communication manager, or other components or combinations of components of the wireless communication device. The processing system of the wireless communication device may interface with other components of the wireless communication device, and may process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of the wireless communication device may include a processing system, a first interface to output information and a second interface to obtain information. In some implementations, the first interface may refer to an interface between the processing system of the chip or modem and a transmitter, such that the wireless communication device may transmit information output from the chip or modem. In some implementations, the second interface may refer to an interface between the processing system of the chip or modem and a receiver, such that the wireless communication device may obtain information or signal inputs, and the information may be passed to the processing system. A person having ordinary skill in the art will readily recognize that the first interface also may obtain information or signal inputs, and the second interface also may output information or signal outputs.

The wireless communication device may support wireless communication at a wireless communication device in accordance with examples as disclosed herein. The connection setup component1205is capable of, configured to, or operable to support a means for receiving, in association with establishing a wireless communication link with a first wearable or handheld wireless device, one or more first packets indicating a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and a second wearable or handheld wireless device, a first link identifier corresponding to the first wearable or handheld wireless device, and a second link identifier corresponding to the second wearable or handheld wireless device. The link ID-based communication component1210is capable of, configured to, or operable to support a means for transmitting, in accordance with the shared address, one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier.

In some implementations, the link ID-based communication component1210is capable of, configured to, or operable to support a means for receiving a first indication of the first link identifier via a first packet in association with a first establishment of a first block acknowledgment session between the wireless communication device and the first wearable or handheld wireless device. In some implementations, the link ID-based communication component1210is capable of, configured to, or operable to support a means for receiving a second indication of the second link identifier via a second packet in association with a second establishment of a second block acknowledgment session between the wireless communication device and the second wearable or handheld wireless device.

In some implementations, the link ID-based communication component1210is capable of, configured to, or operable to support a means for transmitting first information indicative of a first schedule of first communication time intervals corresponding to the first link identifier, where transmitting the one or more second packets associated with the first link identifier is associated with the first schedule of the first communication time intervals. In some implementations, the link ID-based communication component1210is capable of, configured to, or operable to support a means for transmitting second information indicative of a second schedule of second communication time intervals corresponding to the second link identifier, where transmitting the one or more third packets associated with the second link identifier is associated with the second schedule of the second communication time intervals.

In some implementations, the link ID-based communication component1210is capable of, configured to, or operable to support a means for receiving, from the first wearable or handheld wireless device, a packet indicating the shared address and a power management state corresponding to the shared address, where transmitting the one or more second packets and the one or more third packets is associated with the power management state.

In some implementations, the link ID-based communication component1210is capable of, configured to, or operable to support a means for transmitting information indicative of a first mapping of the first link identifier to a first wireless communication link and a second mapping of the second link identifier to a second wireless communication link, where the first wireless communication link is associated with a first frequency channel and the second wireless communication link is associated with a second frequency channel different than the first frequency channel.

In some implementations, to support transmitting the one or more second packets and the one or more third packets, the link ID-based communication component1210is capable of, configured to, or operable to support a means for transmitting the one or more second packets via the first wireless communication link within a first communication time interval and the one or more third packets via the second wireless communication link within a second communication time interval, where the first communication time interval and the second communication time interval at least partially overlap in time.

In some implementations, the connection setup component1205is capable of, configured to, or operable to support a means for transmitting, to the first wearable or handheld wireless device, an indication that the wireless communication device is capable of quality of service-based traffic flow prioritization. In some implementations, the connection setup component1205is capable of, configured to, or operable to support a means for establishing the wireless communication link using the shared address in accordance with the wireless communication device being capable of the quality of service-based traffic flow prioritization.

In some implementations, to support transmitting the indication that the wireless communication device is capable of the quality of service-based traffic flow prioritization, the connection setup component1205is capable of, configured to, or operable to support a means for transmitting identification information of the wireless communication device, where the identification information indicates that the wireless communication device is present in a first list of devices for which use of the shared address is allowed and absent from a second list of devices for which use of the shared address is not allowed.

In some implementations, a presence of the identification information of the wireless communication device in either the first list of devices or the second list of devices is indicative of a previous quality of service conformance test for the wireless communication device. In some implementations, being present in the first list of devices is indicative of a successful quality of service conformance test and being present in the second list of devices is indicative of an unsuccessful quality of service conformance test.

In some implementations, to support transmitting the indication that the wireless communication device is capable of the quality of service-based traffic flow prioritization, the connection setup component1205is capable of, configured to, or operable to support a means for transmitting a packet indicating that an end-to-end path between a traffic source device and the first wearable or handheld wireless device is capable of the quality of service-based traffic flow prioritization, where the wireless communication device is the traffic source device or another wireless communication device along the end-to-end path.

In some implementations, the first link identifier and the second link identifier are association with a same channel access category.

In some implementations, the one or more second packets include indications of a first type of service for the first wearable or handheld wireless device, the first type of service being mapped to the first link identifier, and the one or more third packets include indications of a second type of service for the second wearable or handheld wireless device, the second type of service being mapped to the second link identifier.

In some implementations, each packet of the one or more second packets includes first information that is specific to the first wearable or handheld wireless device and each packet of the one or more third packets includes second information that is specific to the second wearable or handheld wireless device.

In some implementations, each packet of the one or more second packets and the one or more third packets includes both first information that is specific to the first wearable or handheld wireless device and second information that is specific to the second wearable or handheld wireless device.

In some implementations, the one or more first packets include one or more of an authentication frame, an association frame, an address resolution protocol frame, a dynamic host configuration protocol frame, an extensible authentication protocol over local area network frame, a key handshake frame, and an add block acknowledgment frame.

In some implementations, the wireless communication device is a traffic source device.

FIG.13shows a flowchart illustrating an example process1300that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The operations of the process1300may be an example of a method implemented by a wearable device or its components. For example, the process1300may be performed by a wireless communication device, such as the wireless communication device described with reference toFIG.11, operating as or within a wireless STA. In some implementations, the process1300may be performed by a wireless STA, such as one of the STAs104described with reference toFIG.1.

In some implementations, in block1305, the wireless STA may communicating, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associated with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device. The operations of block1305may be performed in accordance with examples as disclosed herein. In some implementations, aspects of the operations of block1305may be performed by a peer communication component1105as described with reference toFIG.11.

In some implementations, in block1310, the wireless STA may transmit, in association with establishing a second wireless communication link with a wireless communication device, one or more second packets indicating the shared address, the first link identifier, and the second link identifier. The operations of block1310may be performed in accordance with examples as disclosed herein. In some implementations, aspects of the operations of block1310may be performed by a connection setup component1110as described with reference toFIG.11.

In some implementations, in block1315, the wireless STA may receive, from the wireless communication device via the second wireless communication link, one or more third packets associated with the first link identifier. The operations of block1315may be performed in accordance with examples as disclosed herein. In some implementations, aspects of the operations of block1315may be performed by a link ID-based communication component1115as described with reference toFIG.11.

FIG.14shows a flowchart illustrating an example process1400that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address according to some aspects of the present disclosure. The operations of the process1400may be an example of a method implemented by a wearable device or its components. For example, the process1400may be performed by a wireless communication device, such as the wireless communication device described with reference toFIG.11, operating as or within a wireless STA. In some implementations, the process1400may be performed by a wireless STA, such as one of the STAs104described with reference toFIG.1.

In some implementations, in block1405, the wireless STA may communicating, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associated with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device. The operations of block1405may be performed in accordance with examples as disclosed herein. In some implementations, aspects of the operations of block1405may be performed by a peer communication component1105as described with reference toFIG.11.

In some implementations, in block1410, the wireless STA may receive, from a wireless communication device via a second wireless communication link, one or more second packets associated with the first link identifier, the second wireless communication link being in association with an establishment using the shared address. The operations of block1410may be performed in accordance with examples as disclosed herein. In some implementations, aspects of the operations of block1410may be performed by a link ID-based communication component1115as described with reference toFIG.11.

FIG.15shows a flowchart illustrating an example process1500that supports managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address in accordance with one or more aspects of the present disclosure. The operations of the process1500may be implemented by a STA or an AP or its components. For example, the operations of the process1500may be performed by a traffic source/sink device as described with reference toFIG.12. In some implementations, a STA or an AP may execute a set of instructions to control the functional elements of the wireless STA or the wireless AP to perform the described functions. Additionally, or alternatively, the wireless STA or the wireless AP may perform aspects of the described functions using special-purpose hardware.

In some implementations, in block1505, the wireless STA or the wireless AP may receive, in association with establishing a wireless communication link with a first wearable or handheld wireless device, one or more first packets indicating a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and a second wearable or handheld wireless device, a first link identifier corresponding to the first wearable or handheld wireless device, and a second link identifier corresponding to the second wearable or handheld wireless device. The operations of block1505may be performed in accordance with examples as disclosed herein. In some implementations, aspects of the operations of block1505may be performed by a connection setup component1205as described with reference toFIG.12.

In some implementations, in block1510, the wireless STA or the wireless AP may transmit, in accordance with the shared address, one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier. The operations of block1510may be performed in accordance with examples as disclosed herein. In some implementations, aspects of the operations of block1510may be performed by a link ID-based communication component1210as described with reference toFIG.12.

Clause 1: A method for wireless communication at a first wearable or handheld wireless device, including: communicating, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associated with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device; transmitting, in association with establishing a second wireless communication link with a wireless communication device, one or more second packets indicating the shared address, the first link identifier, and the second link identifier; and receiving, from the wireless communication device via the second wireless communication link, one or more third packets associated with the first link identifier.

Clause 2: The method of clause 1, where communicating the one or more first packets with at least the second wearable or handheld wireless device via the first wireless communication link includes: transmitting one or more of the one or more first packets to, and receiving one or more of the one or more first packets from, the second wearable or handheld wireless device in accordance with a negotiation of the shared address with the second wearable or handheld wireless device.

Clause 3: The method of any of clauses 1 through 2, where communicating the one or more first packets with at least the second wearable or handheld wireless device via the first wireless communication link includes: transmitting one or more of the one or more first packets to, and receiving one or more of the one or more first packets from, the second wearable or handheld wireless device in accordance with an assignment of the first link identifier to the first wearable or handheld wireless device and the second link identifier to the second wearable or handheld wireless device.

Clause 4: The method of any of clauses 1 through 3, further including: transmitting, to the wireless communication device, a fourth packet in association with an establishment of a first block acknowledgment session between the wireless communication device and the first wearable or handheld wireless device, the fourth packet including an indication of the first link identifier; and transmitting, to the wireless communication device, one or more block acknowledgments associated with the one or more third packets.

Clause 5: The method of any of clauses 1 through 4, further including: transmitting, to the wireless communication device, a fourth packet indicating the shared address and a power management state corresponding to the shared address.

Clause 6: The method of clause 5, further including: receiving, from the second wearable or handheld wireless device via the first wireless communication link, a fifth packet indicating that the second wearable or handheld wireless device is in the power management state, where transmitting the fourth packet indicating the power management state is in association with receiving the fifth packet.

Clause 7: The method of any of clauses 1 through 6, further including: communicating, with at least the second wearable or handheld wireless device via the first wireless communication link, one or more fourth packets in accordance with a negotiation of one or more of: one or more security keys associated with communication with the wireless communication device, a dynamic host configuration protocol address, or one or more address resolution protocol tables, where the first wearable or handheld wireless device establishes the second wireless communication link in accordance with the negotiation.

Clause 8: The method of any of clauses 1 through 7, further including: receiving, from the wireless communication device, information indicative of a schedule of communication time intervals corresponding to the first link identifier; and monitoring the second wireless communication link in accordance with the schedule of the communication time intervals, where receiving the one or more third packets is in association with monitoring the second wireless communication link.

Clause 9: The method of any of clauses 1 through 8, where each of the one or more third packets includes a respective frame header indicating the first link identifier, the method further including: decoding data portions of the one or more third packets in accordance with frame headers of the one or more third packets indicating the first link identifier; receiving one or more fourth packets each including a respective frame header indicating the second link identifier; and refraining from decoding data portions of the one or more fourth packets in accordance with frame headers of the one or more fourth packets indicating the second link identifier.

Clause 10: The method of any of clauses 1 through 9, further including: receiving, from the wireless communication device, information indicative of a first mapping of the first link identifier to the second wireless communication link and a second mapping of the second link identifier to a third wireless communication link; and tuning at least one radio to the second wireless communication link in accordance with the first mapping, where receiving the one or more third packets is in association with tuning the at least one radio to the second wireless communication link, and where the second wireless communication link is associated with a first frequency channel and the third wireless communication link is associated with a second frequency channel different than the first frequency channel.

Clause 11: The method of any of clauses 1 through 10, further including: receiving an indication that the wireless communication device is capable of quality of service-based traffic flow prioritization; and establishing the second wireless communication link with the wireless communication device using the shared address in accordance with the wireless communication device being capable of the quality of service-based traffic flow prioritization.

Clause 12: The method of clause 11, where receiving the indication that the wireless communication device is capable of the quality of service-based traffic flow prioritization includes: receiving identification information of the wireless communication device, where the identification information indicates that the wireless communication device is present in a first list of devices for which use of the shared address is allowed and absent from a second list of devices for which use of the shared address is not allowed.

Clause 13: The method of clause 12, where a presence of the identification information of the wireless communication device in either the first list of devices or the second list of devices is indicative of a previous quality of service conformance test for the wireless communication device, being present in the first list of devices is indicative of a successful quality of service conformance test and being present in the second list of devices is indicative of an unsuccessful quality of service conformance test.

Clause 14: The method of any of clauses 11 through 13, where receiving the indication that the wireless communication device is capable of the quality of service-based traffic flow prioritization includes: receiving a packet indicating that an end-to-end path between a traffic source device and the first wearable or handheld wireless device is capable of the quality of service-based traffic flow prioritization, where the wireless communication device is the traffic source device or another wireless communication device along the end-to-end path.

Clause 15: The method of any of clauses 1 through 14, further including: communicating, with the second wearable or handheld wireless device via the first wireless communication link, information indicative of one or more link quality metrics pertaining to first communication between the first wearable or handheld wireless device and the wireless communication device and second communication between the second wearable or handheld wireless device and the wireless communication device.

Clause 16: The method of clause 15, further including: receiving an indication that a link quality metric pertaining to the second communication between the second wearable or handheld wireless device and the wireless communication device fails to satisfy a condition; receiving one or more fourth packets including the second link identifier in accordance with the link quality metric failing to satisfy the condition; and transmitting, to the second wearable or handheld wireless device via the first wireless communication link, data received via the one or more fourth packets in accordance with the one or more fourth packets including the second link identifier.

Clause 17: The method of clause 16, further including: receiving, from the second wearable or handheld wireless device via the first wireless communication link, feedback information associated with the data; and transmitting, to the wireless communication device, one or more block acknowledgments associated with the one or more fourth packets, the one or more block acknowledgments indicating the feedback information received from the second wearable or handheld wireless device.

Clause 18: The method of any of clauses 16 through 17, further including: receiving an indication that the link quality metric pertaining to the second communication between the second wearable or handheld wireless device and the wireless communication device satisfies the condition; and refraining from decoding any packets including the second link identifier in accordance with the link quality metric satisfying the condition, where the first wearable or handheld wireless device temporarily receives the one or more fourth packets including the second link identifier while the link quality metric fails to satisfy the condition.

Clause 19: The method of any of clauses 16 through 18, further including: transmitting, to the wireless communication device in accordance with the link quality metric failing to satisfy the condition, information indicative of a recommended coding rate.

Clause 20: The method of clause 19, where the recommended coding rate is for both the first communication between the first wearable or handheld wireless device and the wireless communication device and the second communication between the second wearable or handheld wireless device and the wireless communication device.

Clause 21: The method of any of clauses 15 through 20, further including: transmitting an indication that a link quality metric pertaining to the first communication between the first wearable or handheld wireless device and the wireless communication device fails to satisfy a condition; receiving data from the second wearable or handheld wireless device via the first wireless communication link in accordance with the link quality metric failing to satisfy the condition; and transmitting, to the second wearable or handheld wireless device via the first wireless communication link, feedback information associated with the data.

Clause 22: The method of clause 21, further including: transmitting an indication that the link quality metric pertaining to the first communication between the first wearable or handheld wireless device and the wireless communication device satisfies the condition; and receiving, via the second wireless communication link, packets including the first link identifier in accordance with the link quality metric satisfying the condition, where reception of any packets via the second wireless communication link is temporarily paused while the link quality metric fails to satisfy the condition.

Clause 23: The method of any of clauses 1 through 22, further including: receiving an indication of a handover of the first wearable or handheld wireless device from the wireless communication device to a second wireless communication device; receiving an indication that the second wireless communication device is incapable of quality of service-based traffic flow prioritization; and transmitting, in association with establishing a third wireless communication link with the second wireless communication device, one or more fourth packets indicating a device-specific address, the third wireless communication link being exclusively for the first wearable or handheld wireless device in accordance with the one or more fourth packets indicating the device-specific address.

Clause 24: The method of any of clauses 1 through 23, where the first link identifier and the second link identifier are associated with a same channel access category.

Clause 25: The method of any of clauses 1 through 24, where the one or more third packets include indications of a first type of service for the first wearable or handheld wireless device, the first type of service being mapped to the first link identifier.

Clause 26: The method of any of clauses 1 through 25, where the one or more second packets include one or more of an authentication frame, an association frame, an address resolution protocol frame, a dynamic host configuration protocol frame, an extensible authentication protocol over local area network frame, a key handshake frame, and an add block acknowledgment frame.

Clause 27: The method of any of clauses 1 through 26, where communication of the one or more first packets with the second wearable or handheld wireless device indicates, to the second wearable or handheld wireless device, to refrain from separately establishing a wireless communication link with the wireless communication device.

Clause 28: The method of any of clauses 1 through 27, where the first wireless communication link is a secure peer-to-peer link and the second wireless communication link is a wireless local area network link.

Clause 29: The method of any of clauses 1 through 28, where the wireless communication device is a traffic source device, an access point, or a compute device.

Clause 30: A method for wireless communication at a first wearable or handheld wireless device, including: communicating, with at least a second wearable or handheld wireless device via a first wireless communication link, one or more first packets associated with establishing a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and, associated with the shared address, a first link identifier corresponding to the first wearable or handheld wireless device and a second link identifier corresponding to the second wearable or handheld wireless device; and receiving, from a wireless communication device via a second wireless communication link, one or more second packets associated with the first link identifier, the second wireless communication link being in association with an establishment using the shared address.

Clause 31: The method of clause 30, where communicating the one or more first packets with at least the second wearable or handheld wireless device via the first wireless communication link includes: transmitting one or more of the one or more first packets to, and receiving one or more of the one or more first packets from, the second wearable or handheld wireless device in accordance with a negotiation of the shared address with the second wearable or handheld wireless device.

Clause 32: The method of any of clauses 30 through 31, where communicating the one or more first packets with at least the second wearable or handheld wireless device via the first wireless communication link includes: transmitting one or more of the one or more first packets to, and receiving one or more of the one or more first packets from, the second wearable or handheld wireless device in accordance with an assignment of the first link identifier to the first wearable or handheld wireless device and the second link identifier to the second wearable or handheld wireless device.

Clause 33: The method of any of clauses 30 through 32, further including: transmitting, to the wireless communication device, a third packet in association with an establishment of a first block acknowledgment session between the wireless communication device and the first wearable or handheld wireless device, the third packet including an indication of the first link identifier; and transmitting, to the wireless communication device, one or more block acknowledgments associated with the one or more second packets.

Clause 34: The method of any of clauses 30 through 33, further including: communicating, with at least the second wearable or handheld wireless device via the first wireless communication link, one or more third packets in accordance with a negotiation of one or more of: one or more security keys associated with communication with the wireless communication device, a dynamic host configuration protocol address, or one or more address resolution protocol tables, where the second wearable or handheld wireless device establishes the second wireless communication link in accordance with the negotiation.

Clause 35: The method of any of clauses 30 through 34, further including: receiving, from the wireless communication device, information indicative of a schedule of communication time intervals corresponding to the first link identifier; and monitoring the second wireless communication link in accordance with the schedule of the communication time intervals, where receiving the one or more second packets is in association with monitoring the second wireless communication link.

Clause 36: The method of any of clauses 30 through 35, where each of the one or more second packets includes a respective frame header indicating the first link identifier, the method further including: decoding data portions of the one or more second packets in accordance with frame headers of the one or more second packets indicating the first link identifier; receiving one or more third packets each including a respective frame header indicating the second link identifier; and refraining from decoding data portions of the one or more third packets in accordance with frame headers of the one or more third packets indicating the second link identifier.

Clause 37: The method of any of clauses 30 through 36, further including: receiving, from the wireless communication device, information indicative of a first mapping of the first link identifier to the second wireless communication link and a second mapping of the second link identifier to a third link; and tuning at least one radio to the second wireless communication link in accordance with the first mapping, where receiving the one or more second packets is in association with tuning the at least one radio to the second wireless communication link, and where the second wireless communication link is associated with a first frequency channel and the third link is associated with a second frequency channel different than the first frequency channel.

Clause 38: The method of any of clauses 30 through 37, further including: communicating, with the second wearable or handheld wireless device via the first wireless communication link, information indicative of one or more link quality metrics pertaining to first communication between the first wearable or handheld wireless device and the wireless communication device and second communication between the second wearable or handheld wireless device and the wireless communication device.

Clause 39: The method of clause 38, further including: receiving an indication that a link quality metric pertaining to the second communication between the second wearable or handheld wireless device and the wireless communication device fails to satisfy a condition; receiving one or more third packets including the second link identifier in accordance with the link quality metric failing to satisfy the condition; and transmitting, to the second wearable or handheld wireless device via the first wireless communication link, data received via the one or more third packets in accordance with the one or more third packets including the second link identifier.

Clause 40: The method of clause 39, further including: receiving, from the second wearable or handheld wireless device via the first wireless communication link, feedback information associated with the data; and transmitting, to the wireless communication device, one or more block acknowledgments associated with the one or more third packets, the one or more block acknowledgments indicating the feedback information received from the second wearable or handheld wireless device.

Clause 41: The method of any of clauses 39 through 40, further including: receiving an indication that the link quality metric pertaining to the second communication between the second wearable or handheld wireless device and the wireless communication device satisfies the condition; and refraining from decoding any packets including the second link identifier in accordance with the link quality metric satisfying the condition, where the first wearable or handheld wireless device temporarily receives the one or more third packets including the second link identifier while the link quality metric fails to satisfy the condition.

Clause 42: The method of any of clauses 39 through 41, further including: transmitting, to the wireless communication device in accordance with the link quality metric failing to satisfy the condition, information indicative of a recommended coding rate.

Clause 43: The method of clause 42, where the recommended coding rate is for both the first communication between the first wearable or handheld wireless device and the wireless communication device and the second communication between the second wearable or handheld wireless device and the wireless communication device.

Clause 44: The method of any of clauses 38 through 43, further including: transmitting an indication that a link quality metric pertaining to the first communication between the first wearable or handheld wireless device and the wireless communication device fails to satisfy a condition; receiving data from the second wearable or handheld wireless device via the first wireless communication link in accordance with the link quality metric failing to satisfy the condition; and transmitting, to the second wearable or handheld wireless device via the first wireless communication link, feedback information associated with the data.

Clause 45: The method of clause 44, further including: transmitting an indication that the link quality metric pertaining to the first communication between the first wearable or handheld wireless device and the wireless communication device satisfies the condition; and receiving, via the second wireless communication link, packets including the first link identifier in accordance with the link quality metric satisfying the condition, where reception of any packets via the second wireless communication link is temporarily paused while the link quality metric fails to satisfy the condition.

Clause 46: The method of any of clauses 30 through 45, further including: receiving an indication of a handover, of the association of the wearable or handheld wireless devices including at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, from the wireless communication device to a second wireless communication device; receiving an indication that the second wireless communication device is incapable of quality of service-based traffic flow prioritization; and transmitting, in association with establishing a third wireless communication link with the second wireless communication device, one or more third packets indicating a device-specific address, the third wireless communication link being exclusively for the first wearable or handheld wireless device in accordance with the one or more third packets indicating the device-specific address.

Clause 47: The method of any of clauses 30 through 46, where the first link identifier and the second link identifier are associated with a same channel access category.

Clause 48: The method of any of clauses 30 through 47, where the one or more second packets include indications of a first type of service for the first wearable or handheld wireless device, the first type of service being mapped to the first link identifier.

Clause 49: The method of any of clauses 30 through 48, where communication of the one or more first packets with the second wearable or handheld wireless device indicates, to the first wearable or handheld wireless device, to refrain from separately establishing a wireless communication link with the wireless communication device.

Clause 50: The method of any of clauses 30 through 49, where the first wireless communication link is a secure peer-to-peer link and the second wireless communication link is a wireless local area network link.

Clause 51: The method of any of clauses 30 through 50, where the wireless communication device is a traffic source device, an access point, or a compute device.

Clause 52: A method for wireless communication at a wireless communication device, including: receiving, in association with establishing a wireless communication link with a first wearable or handheld wireless device, one or more first packets indicating a shared address corresponding to an association of wearable or handheld wireless devices including at least the first wearable or handheld wireless device and a second wearable or handheld wireless device, a first link identifier corresponding to the first wearable or handheld wireless device, and a second link identifier corresponding to the second wearable or handheld wireless device; and transmitting, in accordance with the shared address, one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier.

Clause 53: The method of clause 52, further including: receiving a first indication of the first link identifier via a first packet in association with a first establishment of a first block acknowledgment session between the wireless communication device and the first wearable or handheld wireless device; and receiving a second indication of the second link identifier via a second packet in association with a second establishment of a second block acknowledgment session between the wireless communication device and the second wearable or handheld wireless device.

Clause 54: The method of any of clauses 52 through 53, further including: transmitting first information indicative of a first schedule of first communication time intervals corresponding to the first link identifier, where transmitting the one or more second packets associated with the first link identifier is associated with the first schedule of the first communication time intervals; and transmitting second information indicative of a second schedule of second communication time intervals corresponding to the second link identifier, where transmitting the one or more third packets associated with the second link identifier is associated with the second schedule of the second communication time intervals.

Clause 55: The method of any of clauses 52 through 54, further including: receiving, from the first wearable or handheld wireless device, a packet indicating the shared address and a power management state corresponding to the shared address, where transmitting the one or more second packets and the one or more third packets is associated with the power management state.

Clause 56: The method of any of clauses 52 through 55, further including: transmitting information indicative of a first mapping of the first link identifier to a first wireless communication link and a second mapping of the second link identifier to a second wireless communication link, where the first wireless communication link is associated with a first frequency channel and the second wireless communication link is associated with a second frequency channel different than the first frequency channel.

Clause 57: The method of clause 56, where transmitting the one or more second packets and the one or more third packets includes: transmitting the one or more second packets via the first wireless communication link within a first communication time interval and the one or more third packets via the second wireless communication link within a second communication time interval, where the first communication time interval and the second communication time interval at least partially overlap in time.

Clause 58: The method of any of clauses 52 through 57, further including: transmitting, to the first wearable or handheld wireless device, an indication that the wireless communication device is capable of quality of service-based traffic flow prioritization; and establishing the wireless communication link using the shared address in accordance with the wireless communication device being capable of the quality of service-based traffic flow prioritization.

Clause 59: The method of clause 58, where transmitting the indication that the wireless communication device is capable of the quality of service-based traffic flow prioritization includes: transmitting identification information of the wireless communication device, where the identification information indicates that the wireless communication device is present in a first list of devices for which use of the shared address is allowed and absent from a second list of devices for which use of the shared address is not allowed.

Clause 60: The method of clause 59, where a presence of the identification information of the wireless communication device in either the first list of devices or the second list of devices is indicative of a previous quality of service conformance test for the wireless communication device, being present in the first list of devices is indicative of a successful quality of service conformance test and being present in the second list of devices is indicative of an unsuccessful quality of service conformance test.

Clause 61: The method of any of clauses 58 through 60, where transmitting the indication that the wireless communication device is capable of the quality of service-based traffic flow prioritization includes: transmitting a packet indicating that an end-to-end path between a traffic source device and the first wearable or handheld wireless device is capable of the quality of service-based traffic flow prioritization, where the wireless communication device is the traffic source device or another wireless communication device along the end-to-end path.

Clause 62: The method of any of clauses 52 through 61, where the first link identifier and the second link identifier are association with a same channel access category.

Clause 63: The method of any of clauses 52 through 62, where the one or more second packets include indications of a first type of service for the first wearable or handheld wireless device, the first type of service being mapped to the first link identifier, and the one or more third packets include indications of a second type of service for the second wearable or handheld wireless device, the second type of service being mapped to the second link identifier.

Clause 64: The method of any of clauses 52 through 63, where each packet of the one or more second packets includes first information that is specific to the first wearable or handheld wireless device and each packet of the one or more third packets includes second information that is specific to the second wearable or handheld wireless device.

Clause 65: The method of any of clauses 52 through 64, where each packet of the one or more second packets and the one or more third packets includes both first information that is specific to the first wearable or handheld wireless device and second information that is specific to the second wearable or handheld wireless device.

Clause 66: The method of any of clauses 52 through 65, where the one or more first packets include one or more of an authentication frame, an association frame, an address resolution protocol frame, a dynamic host configuration protocol frame, an extensible authentication protocol over local area network frame, a key handshake frame, and an add block acknowledgment frame.

Clause 67: The method of any of clauses 52 through 66, where the wireless communication device is a traffic source device.

Clause 68: A first wearable or handheld wireless device, including a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configuring to cause the first wearable or handheld wireless device to perform a method of any of clauses 1 through 29.

Clause 69: An apparatus for wireless communication at a first wearable or handheld wireless device, including at least one means for performing a method of any of clauses 1 through 29.

Clause 70: A non-transitory computer-readable medium storing code for wireless communication at a first wearable or handheld wireless device, the code including instructions executable by one or more processors individually or collectively to perform a method of any of clauses 1 through 29.

Clause 71: A first wearable or handheld wireless device, including a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configuring to cause the first wearable or handheld wireless device to perform a method of any of clauses 30 through 51.

Clause 72: An apparatus for wireless communication at a first wearable or handheld wireless device, including at least one means for performing a method of any of clauses 30 through 51.

Clause 73: A non-transitory computer-readable medium storing code for wireless communication at a first wearable or handheld wireless device, the code including instructions executable by one or more processors individually or collectively to perform a method of any of clauses 30 through 51.

Clause 74: A wireless communication device, including a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configuring to cause the wireless communication to perform a method of any of clauses 52 through 67.

Clause 75: An apparatus for wireless communication at a wireless communication device, including at least one means for performing a method of any of clauses 52 through 67.

Clause 76: A non-transitory computer-readable medium storing code for wireless communication at a wireless communication device, the code including instructions executable by one or more processors individually or collectively to perform a method of any of clauses 52 through 67.

As used herein, the term “determine” or “determining” encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), inferring, ascertaining, or measuring. Also, “determining” can include receiving (such as receiving information), accessing (such as accessing data stored in memory), or transmitting (such as transmitting information). Also, “determining” can include resolving, selecting, obtaining, choosing, establishing and other such similar actions.

As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c. As used herein, “or” is intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, “a or b” may include a only, b only, or a combination of a and b.

As used herein, “based on” is intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, “based on” may be used interchangeably with “based at least in part on,” “associated with”, or “in accordance with” unless otherwise explicitly indicated. Specifically, unless a phrase refers to “based on only ‘a,’” or the equivalent in context, whatever it is that is “based on ‘a,’” or “based at least in part on ‘a,’” may be based on “a” alone or based on a combination of “a” and one or more other factors, conditions or information.

Various modifications to the examples described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the examples shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.