Managing set of WI-FI enabled wearable or handheld wireless devices using shared address

Abstract

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

Description

[0001] Cross-referencing

[0002] This patent application claims the benefit of the following patents: U.S. Provisional Patent Application No. 63 / 504,187, filed May 24, 2023, entitled “MANAGING A GROUP OF WI-FI-ENABLED WEARABLE OR HANDHELD WIRELESS DEVICESUSING A SHARED ADDRESS”, filed August 1, 2023, by KUPPA et al.; and U.S. Patent Application No. 18 / 363,640, filed August 1, 2023, entitled “MANAGING A GROUP OF WI-FI-ENABLED WEARABLE OR HANDHELD WIRELESS DEVICESUSING A SHARED ADDRESS”; each of these applications is assigned to the assignee of this application, and the entire contents of these applications are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates to wireless communications, and more specifically to using a shared address to manage a group of Wi-Fi enabled wearable or handheld wireless devices. Background Technology

[0004] A Wireless Local Area Network (WLAN) can be formed by one or more wireless access points (APs) that provide a shared wireless communication medium for use by multiple client devices (also known as wireless stations (STAs)). The basic building block of a WLAN conforming to the IEEE 802.11 family of standards is the Basic Service Set (BSS) managed by the AP. Each BSS is identified by a Basic Service Set Identifier (BSSID) advertised by the AP. The AP periodically broadcasts beacon frames to enable any STA within the AP's wireless range to establish or maintain a communication link with the WLAN.

[0005] In some systems, a group of Wi-Fi-enabled wearable devices may deliver the same application or otherwise be associated with the same application. Such a group of Wi-Fi-enabled wearable devices delivering the same application may include wireless earbuds, wireless accessories (such as watches, bracelets, and / or rings), health monitors, and / or gaming sensors or controllers. For example, two wireless earbuds may deliver audio data for the same music application. Similarly, two or more gaming sensors and / or controllers may deliver input data (associated with motion and / or controller input) for the same video game application. Because each Wi-Fi device typically has its own unique Media Access Control (MAC) address, each device in a group of Wi-Fi-enabled wearable devices typically performs an independent connection setup process to connect to the WLAN. For example, a first wearable device may exchange a first set of frames with a mobile phone, access point (AP), or computing device as part of a first connection setup, and a second wearable device may independently exchange a second set of frames with a mobile phone, AP, or computing device as part of a second connection setup. Therefore, a mobile phone, AP, or computing device can independently supply Wi-Fi and Internet Protocol (IP) connectivity to the first and second wearable devices for subsequent data communication. Summary of the Invention

[0006] The systems, methods, and apparatus disclosed herein each have several innovative aspects, and no single aspect is solely responsible for the desired properties disclosed herein.

[0007] 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: transmitting one or more first packets via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with establishing a shared address corresponding to an association between the wearable or handheld wireless device and at least the first and second wearable or handheld wireless devices, and a first link identifier associated with the shared address corresponding to the first wearable or handheld wireless device and a second link identifier associated with the second wearable or handheld wireless device; transmitting one or more second packets indicating the shared address, the first link identifier, and the second link identifier in association with establishing a second wireless communication link with the wireless communication device; and receiving one or more third packets associated with the first link identifier from the wireless communication device via the second wireless communication link.

[0008] Another inventive aspect of the subject matter described in this disclosure can be implemented in a first wearable or handheld wireless device. The first wearable or handheld wireless device may include a processing system comprising processor circuitry and memory circuitry storing code. The processing system may be configured to cause the first wearable or handheld wireless device to: transmit one or more first packets to at least a second wearable or handheld wireless device via a first wireless communication link, the one or more first packets being associated with a shared address corresponding to an association between the first and second wearable or handheld wireless devices, and 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 associated with the shared address; transmit one or more second packets indicating the shared address, the first link identifier, and the second link identifier in association with the establishment of a second wireless communication link with the wireless communication device; and receive one or more third packets associated with the first link identifier from the wireless communication device via the second wireless communication link.

[0009] Another inventive aspect of the subject matter described in this disclosure can be implemented in a first wearable or handheld wireless device. The first wearable or handheld wireless device may include: components for transmitting one or more first packets via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with a shared address corresponding to an association between the wearable or handheld wireless device and at least the first and second wearable or handheld wireless devices, and 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 associated with the shared address; components for transmitting one or more second packets indicating the shared address, the first link identifier, and the second link identifier in association with establishing a second wireless communication link with the wireless communication device; and components for receiving one or more third packets associated with the first link identifier from the wireless communication device via the second wireless communication link.

[0010] Another inventive 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 individually or jointly by one or more processors to: communicate one or more first packets via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with establishing a shared address corresponding to an association with at least the first and second wearable or handheld wireless devices, and 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 associated with the shared address; transmit one or more second packets indicating the shared address, the first link identifier, and the second link identifier in association with establishing a second wireless communication link with the wireless communication device; and receive one or more third packets associated with the first link identifier from the wireless communication device via the second wireless communication link.

[0011] Another inventive 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: transmitting one or more first packets via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with a shared address corresponding to an association between the wearable or handheld wireless device and at least the first and second wearable or handheld wireless devices, and 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 associated with the shared address; and receiving one or more second packets associated with the first link identifier from the wireless communication device via the second wireless communication link, the second wireless communication link being associated with the establishment using the shared address.

[0012] Another inventive aspect of the subject matter described in this disclosure can be implemented in a first wearable or handheld wireless device. The first wearable or handheld wireless device may include a processing system comprising processor circuitry and memory circuitry storing code. The processing system may be configured to cause the first wearable or handheld wireless device to: transmit one or more first packets via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with a shared address corresponding to an association between the first and second wearable or handheld wireless devices, and a first link identifier associated with the shared address corresponding to the first wearable or handheld wireless device and a second link identifier associated with the second wearable or handheld wireless device; and receive one or more second packets associated with the first link identifier from the wireless communication device via a second wireless communication link associated with the establishment using the shared address.

[0013] Another inventive aspect of the subject matter described in this disclosure can be implemented in a first wearable or handheld wireless device. The first wearable or handheld wireless device may include: components for transmitting one or more first packets to at least a second wearable or handheld wireless device via a first wireless communication link, the one or more first packets being associated with a shared address corresponding to an association between the wearable or handheld wireless device and at least the first and second wearable or handheld wireless devices, and 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 associated with the shared address; and components for receiving one or more second packets associated with the first link identifier from the wireless communication device via a second wireless communication link associated with the establishment using the shared address.

[0014] Another inventive 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 individually or jointly by one or more processors to: communicate one or more first packets via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with establishing a shared address corresponding to an association between the wearable or handheld wireless device and at least the first and second wearable or handheld wireless devices, and 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 associated with the shared address; and receive one or more second packets associated with the first link identifier from the wireless communication device via the second wireless communication link, the second wireless communication link being associated with the establishment using the shared address.

[0015] Another inventive aspect of the subject matter described in this disclosure can be implemented in a method for performing wireless communication at a wireless communication device. The method may include: receiving one or more first packets in association with establishing a wireless communication link with a first wearable or handheld wireless device, the one or more first packets indicating a shared address corresponding to an association of at least one first wearable or handheld wireless device and one 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 one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier according to the shared address.

[0016] Another inventive aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. The wireless communication device may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code. The one or more processors may be capable of operating individually or jointly to execute code to cause a first wearable or handheld wireless device to: receive one or more first packets associated with establishing a wireless communication link with the first wearable or handheld wireless device, the one or more first packets indicating a shared address corresponding to an association of 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 one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier according to the shared address.

[0017] Another inventive aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. The wireless communication device may include: components for receiving one or more first packets in association with establishing a wireless communication link with a first wearable or handheld wireless device, the one or more first packets indicating a shared address corresponding to an association of at least one first wearable or handheld wireless device and one 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 components for transmitting one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier according to the shared address.

[0018] Another inventive 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 individually or jointly by one or more processors to: receive one or more first packets associated with establishing a wireless communication link with a first wearable or handheld wireless device, the one or more first packets indicating a shared address corresponding to an association of at least the first and second wearable or handheld wireless devices, 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 one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier according to the shared address.

[0019] Details of one or more specific embodiments of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. Note that the relative dimensions in the following drawings may not be drawn to scale. Attached Figure Description

[0020] Figure 1 A schematic diagram of an example wireless communication network is shown.

[0021] Figure 2 An example signaling diagram is shown that supports the use of shared addresses to manage a group of Wi-Fi enabled wearable or handheld wireless devices in accordance with some aspects of this disclosure.

[0022] Figure 3 and Figure 4 An example process flow is shown that supports the use of a shared address to manage a group of Wi-Fi enabled wearable or handheld wireless devices in accordance with some aspects of this disclosure.

[0023] Figure 5 An example flowchart is shown that supports the use of a shared address to manage a group of Wi-Fi enabled wearable or handheld wireless devices in accordance with some aspects of this disclosure.

[0024] Figure 6 An example communication timeline is shown that supports the use of a shared address to manage a group of Wi-Fi enabled wearable or handheld wireless devices in accordance with some aspects of this disclosure.

[0025] Figure 7 An example flowchart is shown that supports the use of a shared address to manage a group of Wi-Fi enabled wearable or handheld wireless devices in accordance with some aspects of this disclosure.

[0026] Figures 8 to 10 An example XPAN topology is shown, supporting the use of shared addresses to manage a group of Wi-Fi-enabled wearable or handheld wireless devices, according to some aspects of this disclosure.

[0027] Figure 11 A block diagram of an example wireless communication device is shown, which supports the use of a shared address to manage a group of Wi-Fi-enabled wearable or handheld wireless devices in accordance with some aspects of this disclosure.

[0028] Figure 12 A block diagram of an example wireless communication device is shown, which supports the use of a shared address to manage a group of Wi-Fi-enabled wearable or handheld wireless devices in accordance with some aspects of this disclosure.

[0029] Figures 13 to 15 A flowchart illustrating an example process for managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address, in accordance with some aspects of this disclosure.

[0030] The same reference numerals and names in different figures denote the same elements. Detailed Implementation

[0031] The following description refers to certain specific examples in order to illustrate the innovative aspects of this disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. Some or all of the examples described can be applied in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, or Bluetooth as defined by the Bluetooth Special Interest Group (SIG). ®The described examples can be implemented in any device, system, or network that transmits and receives radio frequency (RF) signals using one or more of the following standards or those published by the 3rd Generation Partnership Project (3GPP): Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)). The examples described can be implemented in any device, system, or network capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Space Division Multiple Access (SDMA), Rate Split Multiple Access (RSMA), Multi-User Shared Access (MUSA), Single-User (SU) Multiple-Input Multiple-Output (MIMO), and Multi-User (MU) MIMO. The examples described can also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of the following wireless personal area networks (WPAN), wireless local area networks (WLAN), wireless wide area networks (WWAN), wireless metropolitan area networks (WMAN), or Internet of Things (IoT) networks.

[0032] The various aspects generally relate to the connection establishment process and data exchange sequence of a group of Wi-Fi-enabled wearable devices for delivering the same or similar applications. Some aspects more specifically relate to the negotiation of a shared address corresponding to a group of Wi-Fi-enabled wearable devices and the use of the shared address during the connection establishment process of that group of Wi-Fi-enabled wearable devices. For example, for a group of Wi-Fi-enabled wearable devices (which may be understood 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 one or more packets via a first wireless communication link with a shared address associated with establishing an association (such as their cluster or set) between the first wearable device and the second wearable device. One of the first wearable devices or the second wearable device may then use the shared address to perform a connection establishment process with a wireless communication device (such as an access point (AP), a mobile phone providing SoftAP functionality, or a computing device). The shared address may be an example of a Media Access Control (MAC) address, or alternatively, an address that can be used in place of a MAC address. The connection establishment process may be associated with establishing a second wireless communication link with the wireless communication device. By using a shared address to perform the connection setup process, a wearable device can perform the connection setup process on behalf of a group of Wi-Fi enabled wearable devices (so that other wearable devices in the group of Wi-Fi enabled wearable devices can avoid performing the connection setup process).

[0033] In some examples, the first wearable device and the second wearable device may further exchange one or more packets to indicate a first link identifier (ID) corresponding to the first wearable device and a second link ID corresponding to the second wearable device relative to a shared address. In such examples, the first wearable device may establish a first block acknowledgment (BA) session based on the shared address and the first link ID, and the second wearable device may establish a second BA session based on the shared address and the second link ID. Therefore, both the first and second wearable devices can use the shared address to send and / or receive packets, and can determine whether a packet was sent to or from the first or second wearable device based on the 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 avoid (fully) decoding data packets associated with the second link ID. Similarly, the second wearable device may receive and decode data packets associated with the second link ID, and may avoid (fully) decoding data packets associated with the first link ID.

[0034] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some specific embodiments, by establishing a shared address corresponding to an association with a set of two or more wearable devices, a wearable device can use the shared address to perform a connection setup process, allowing other wearable devices in the set to avoid performing connection setup processes. This reduces connection setup signaling overhead and (re)connection latency by limiting the connection setup sequence to one interface. For example, by limiting the connection setup sequence to one interface, (re)connection time can be reduced by approximately half for a set of two wearable devices (because one of the two wearable devices avoids performing the connection setup process), by approximately two-thirds for a set of three wearable devices (because two of the three wearable devices avoid performing the connection setup process), and so on. Furthermore, based on this reduction in (re)connection time and (re)connection interface, additional channel access opportunities can become available to other devices in the system. This can alleviate multi-client scheduling and enable denser Wi-Fi systems and / or higher data rates by increasing media availability through packet delivery to a single shared address. Furthermore, by using a shared address to establish a connection for a group of wearable devices, which may experience timely data delivery to that group of wearable devices because they appear as a single wireless communication device from a network perspective. For example, an access point (AP) can deliver all relevant content to a group of wearable devices as a whole, because the AP may not interrupt service to that group of wearable devices while serving other devices in the system, since the group of wearable devices appears as a single wireless communication device. Various aspects of the described topics can be realized to achieve greater reliability, greater spectral efficiency, improved user experience, and greater system capacity, among other benefits, by reducing connection setup signaling overhead and (re)connection latency, enabling denser Wi-Fi systems and / or higher data rates, and utilizing shared addresses to support timely data delivery.

[0035] Figure 1A schematic diagram of an example wireless communication network 100 is shown. According to some aspects, the wireless communication network 100 may be an example of a wireless local area network (WLAN) (such as a Wi-Fi network) (and will be referred to WLAN 100 below). For example, WLAN 100 may be a network implementing at least one of the IEEE 802.11 wireless communication protocol standard families (such as standards defined by the IEEE 802.11-2020 specification or its revisions, including but not limited to 802.11ay, 802.11ax, 802.11az, 802.11ba, 802.11bd, 802.11be, 802.11bf, and 802.11bn). WLAN 100 may include multiple wireless communication devices, such as wireless AP 102 and multiple wireless STA 104. Although Figure 1 The diagram shows only one AP 102, but the WLAN 100 may also include multiple APs 102. Figure 1 The AP 102 shown can represent various types of APs, including but not limited to enterprise-grade APs, single-band APs, dual-band APs, standalone APs, software-enabled APs (soft APs), and multi-link APs. The coverage and capacity of cellular networks (such as LTE or 5G NR) can be further improved by small cells supported by AP 102, which are used as micro base stations. Furthermore, small cells can also be used to establish dedicated cellular networks via radio area networks.

[0036] Each STA in STA 104 can also be referred to as a mobile station (MS), mobile device, mobile phone, wireless phone, access terminal (AT), user equipment (UE), subscriber station (SS), or subscriber unit, etc. STA 104 can represent various devices such as mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, laptops, tablets, computers, color books, extended reality (XR) headsets, wearable devices, display devices (such as TVs (including smart TVs), computer monitors, navigation systems, etc.), music or other audio or stereo devices, remote control devices (“remote controllers”), printers, kitchen appliances (including smart refrigerators) or other home appliances, remote keys (such as those used for passive keyless entry and start (PKES) systems), Internet of Things (IoT) devices, and vehicles, etc. Various STAs 104 in the network can communicate with each other via AP 102.

[0037] A single AP 102 and its associated set of STA 104s may be referred to as a Basic Service Set (BSS), which is managed by the respective AP 102. Figure 1Additionally, an example coverage area 108 of AP 102 is shown, which may represent the Basic Service Area (BSA) of WLAN 100. The BSA can identify or indicate users via a Service Set ID (SSID) and other devices via a Basic Service Set ID (BSSID), which may be the MAC address of AP 102. AP 102 may periodically broadcast beacon frames (“beacons”) including the BSSID to enable any STA 104 within the wireless range of AP 102 to “associate” or reassociate with AP 102 to establish or maintain a corresponding communication link 106 (also referred to hereinafter as a “Wi-Fi link”) with AP 102. For example, the beacon may include an identifier or indication of the primary channel used by the corresponding AP 102 and a timing synchronization function for establishing or maintaining timing synchronization with AP 102. AP 102 can provide access to external networks to various STAs 104 in the WLAN via the corresponding communication link 106.

[0038] In order to establish a communication link 106 with AP 102, each STA in STA 104 is configured to perform a passive or active scanning operation (“scan”) on a frequency channel in one or more frequency bands (such as 2.4 GHz, 5 GHz, 6 GHz or 60 GHz bands). To perform a passive scan, STA 104 listens for beacons transmitted by the corresponding AP 102 at periodic time intervals (referred to as Target Beacon Transmission Time (TBTT) – measured in units of time (TU), where one TU can be equal to 1024 microseconds (µs)). To perform an active scan, STA 104 generates probe requests and transmits these requests sequentially on each channel to be scanned, and listens for probe responses from AP 102. Each STA 104 can identify, determine, detect, or select an AP 102 to associate with based on the scan information obtained through passive or active scanning, and performs authentication and association operations to establish a communication link 106 with the selected AP 102. At the end of the association operation, AP 102 assigns an Association ID (AID) to STA 104, which AP 102 uses to track STA 104.

[0039] As wireless networks become increasingly prevalent, STA 104 has the opportunity to choose from one of many BSSs within its range or from multiple APs 102 that together form an Extended Service Set (ESS) (comprising multiple connected BSSs). The extended network station associated with WLAN 100 can connect to a wired or wireless distribution system that allows multiple APs 102 to be connected in such an ESS. Therefore, STA 104 can be covered by more than one AP 102 and can be associated with different APs 102 at different times for different transmissions. Additionally, after associating with an AP 102, STA 104 can periodically scan its surroundings to find a more suitable AP 102 to associate with. For example, a STA 104 moving relative to its associated AP 102 can perform a "roaming" scan to find another AP 102 with more desirable network characteristics, such as a larger Received Signal Strength Indicator (RSSI) or reduced traffic load.

[0040] In some implementations, STA 104 may form a network without AP 102 or other equipment besides STA 104 itself. An example of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may also 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 WLAN 100. In such examples, while STA 104 may be able to communicate with each other via AP 102 using communication link 106, STA 104 may also communicate directly with each other via direct wireless communication link 110. Additionally, two STA 104 may communicate via direct wireless communication link 110, regardless of whether the two STA 104 are associated with and served by the same AP 102. In such ad hoc systems, one or more STAs among STA 104 may assume the role played by AP 102 in the BSS. Such STA 104 may be referred to as the group owner (GO) and may coordinate transmissions within the ad hoc network. Examples of direct wireless communication links 110 include Wi-Fi direct connections, connections established by using Wi-Fi Tunneling Direct Link Establishment (TDLS) links, and other P2P group connections.

[0041] AP 102 and STA 104 can operate and communicate (via the corresponding communication link 106) according to one or more of the IEEE 802.11 wireless communication protocol family of standards. These standards define WLAN radio and baseband protocols for the PHY and MAC layers. AP 102 and STA 104 send and receive wireless communications to and from each other in the form of PHY Protocol Data Units (PPDUs) (also referred to below as “Wi-Fi communication” or “wireless packets”). AP 102 and STA 104 in WLAN 100 can send PPDUs on unlicensed spectrum, which can be a portion of the spectrum including bands traditionally used by Wi-Fi technologies, such as the 2.4 GHz band, 5 GHz band, 60 GHz band, 3.6 GHz band, and 900 MHz band. Some examples of AP 102 and STA 104 described herein can also communicate in other bands that can support both licensed and unlicensed communications, such as the 5.9 GHz band and 6 GHz band. AP 102 and STA 104 can also communicate on other frequency bands, such as shared licensed bands, where multiple operators may have licenses to operate in one or more of the same or overlapping frequency bands.

[0042] Each frequency band can include multiple sub-bands or frequency channels. For example, PPDUs conforming to revisions of the IEEE 802.11n, 802.11ac, 802.11ax, and 802.11be standards can be transmitted in 2.4 GHz, 5 GHz, or 6 GHz bands, each of which is divided into multiple 20 MHz channels. Therefore, these PPDUs are transmitted on physical channels with a minimum bandwidth of 20 MHz, but larger channels can be formed through channel bonding. For example, PPDUs can be transmitted on physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz, or 320 MHz by bonding multiple 20 MHz channels together.

[0043] Each PPDU is a composite structure comprising a PHY preamble and a payload in the form of a PHY Service Data Unit (PSDU). The information provided in the preamble can be used by the receiving device to decode subsequent data in the PSDU. In instances where the PPDU is transmitted on a bound channel, the preamble field may be copied 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 can be used for other purposes such as packet detection, automatic gain control, and channel estimation. The legacy preamble is also typically used to maintain compatibility with legacy equipment. The format, decoding, and information provided in the non-legacy portion of the preamble are associated with the specific IEEE 802.11 protocol to be used to transmit the payload.

[0044] Some wireless communication devices (including both AP 102 and STA 104) are capable of multi-link operation (MLO). In some implementations, MLO supports the establishment of multiple different communication links (such as a first link on the 2.4 GHz band, a second link on the 5 GHz band, and a third link on the 6 GHz band) between STA 104 and AP 102. 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 corresponding radio component of the wireless communication device, which may include one or more transmit / receive (Tx / Rx) chains, one or more physical antennas or coupled to such physical antennas, or other components such as signal processing components. Devices with MLO capability may be referred to as multi-link devices (MLDs). For example, an APMLD may include multiple APs 102, each configured to communicate on a corresponding communication link with a corresponding STA among multiple STAs 104 that are not AP MLDs (also referred to as "STA MLDs"). STA MLD can communicate with AP MLD through one or more of multiple communication links at a given time.

[0045] One type of MLO is Multi-Link Aggregation (MLA), where traffic associated with a single STA 104 is transmitted simultaneously and in parallel across multiple communication links to maximize the utilization of available resources, thereby achieving higher throughput. That is, during at least some time durations, transmissions or portions of transmissions can occur simultaneously and in parallel through two or more links. In some implementations, the parallel wireless communication links may support synchronous transmissions. In some other examples, or during some other time durations, transmissions via links may be parallel, but not synchronous or concurrent. In some examples or time durations, two or more of these links may be used for communication between wireless communication devices in the same direction (such as all uplinks or all downlinks). In some other examples or time durations, two or more of these 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 wireless communication device operates in full-duplex mode. Generally, full-duplex operation enables bidirectional communication, where at least one wireless communication device can transmit and receive simultaneously.

[0046] MLA can be implemented in several ways. In some implementations, MLA can be packet-based. For packet-based aggregation, frames of a single service stream (such as all services associated with a given service ID (TID)) can be transmitted concurrently across multiple communication links. In some other examples, MLA can be stream-based. For stream-based aggregation, a single available communication link from among multiple available communication links can be used to transmit each service stream (such as all services associated with a given TID). As an example, a single STA MLD can access a web browser while streaming video in parallel. Services associated with web browser access can be communicated via a first communication link, while services associated with the video stream can be communicated in parallel via a second communication link (such that at least some of the data can be transmitted concurrently on the first channel with the data transmitted on the second channel).

[0047] In some other examples, MLA can be implemented as a hybrid of flow-based and packet-based aggregation. For example, MLD can employ flow-based aggregation when multiple traffic flows are created, and packet-based aggregation in other cases. The determination of switching between MLA techniques or modes may additionally or alternatively be correlated with other metrics, such as time of day, network traffic load, or battery level of wireless communication devices, and other factors or considerations.

[0048] To support MLO technology, the AP MLD and STA MLD can exchange information about supported MLO capabilities (such as supported aggregation types or supported frequency bands, etc.). In some implementations, this exchange can occur via beacon signals, probe requests or responses, association request or response frames, dedicated action frames or Operation Mode Indicators (OMIs), and other examples. In some implementations, the AP MLD can designate a given channel in a given frequency band as an anchor channel (such as a channel on which the AP MLD transmits beacons and other management frames). In such examples, the AP MLD may also transmit beacons (such as beacons containing less information) on other channels for discovery purposes.

[0049] MLO technology offers several benefits to WLANs. For example, MLO can improve user-aware throughput (UPT) (e.g., by rapidly refreshing the per-user transmit queue). Similarly, MLO can improve throughput by improving the utilization of available channels and can increase spectrum utilization (e.g., by increasing the bandwidth-time product). Furthermore, MLO can enable smooth transitions between multi-band radio components (e.g., where each radio component can be associated with a given RF band) or provide a framework for separating control and data channels. Other benefits of MLO include reduced modem power-on time, which can benefit wireless communication devices in terms of power consumption. Another benefit of MLO is increased multiplexing opportunities in the case of a single BSS. For example, multi-link aggregation can increase the number of users per multiplexed transmit serviced by a multi-link AP MLD.

[0050] In some systems, a group of Wi-Fi-enabled wearable devices may deliver the same application or otherwise be associated with the same application. Such a group of Wi-Fi-enabled wearable devices delivering the same application may include wireless earbuds, wireless accessories (such as watches, bracelets, and / or rings), health sensors or monitors, wearable wireless media devices, and / or gaming sensors or controllers. For example, two wireless earbuds may deliver audio data for the same music application. Similarly, two or more gaming sensors and / or controllers may deliver input data (associated with motion and / or controller input) for the same video game application. Because each Wi-Fi device typically has its own unique MAC address, each device in a group of Wi-Fi-enabled wearable devices typically performs an independent connection setup process to connect to the WLAN. In other words, each wearable device in a group of Wi-Fi-enabled wearable devices can be considered a different peer than a mobile phone, computing device, and / or access point (AP) in the WLAN. Computing devices can be equivalently referred to as edge computing devices, network edge devices, or computing nodes, and can be examples of AP 102, STA 104, routers, mobile devices, vehicles, laptops, game consoles, IoT devices, or any other device connected to a network that may have processing and / or computing capabilities. In some scenarios, end devices (such as wearable devices) may rely on edge nodes to process, analyze, and / or perform relatively large computing workloads (such as processing tasks), which would otherwise result in latency and / or power consumption at the end device.

[0051] For example, a first wearable device may exchange a first set of frames with a mobile phone, access point (AP), or computing device as part of a first connection establishment, and a second wearable device may independently exchange a second set of frames with the same mobile phone, AP, or computing device as part of a second connection establishment. Such first and second set of frames may each include one or more frames and / or operations associated with channel scanning, authentication, association, Extensible Authentication Protocol (EAP), EAP over LAN (EAPOL), key exchange, Address Resolution Protocol (ARP), Dynamic Host Configuration Protocol (DHCP), BA negotiation, and / or TWT session establishment sequences. Therefore, the mobile phone, AP, or computing device can independently supply Wi-Fi and Internet Protocol (IP) connectivity to both the first and second wearable devices for subsequent data communication.

[0052] Compared to other communication protocols, this independent provisioning of Wi-Fi-enabled devices (which can be understood as dual-earbud provisioning for a pair of wireless earbuds) effectively multiplies the (re)connection time for a group of wearables by the number of devices in that group, potentially leading to unsatisfactory latency (such as delay) at the end user. For example, in the context of two wireless earbuds, independent provisioning sequences may double the time to start an application or session (and / or double the usage of network resources and bandwidth) compared to some other communication protocols (such as Bluetooth), adversely impacting the user experience.

[0053] Some deployments associated with Extended Personal Area Networks (XPANs) offer flexibility in enabling Wi-Fi-enabled wearables to have or avoid having different IP connectivity. For example, XPAN applications can run on a mobile phone (making the phone typically the service source device), the same or similar application services can be sent to each wearable in a group, and the wearables in the group may largely be co-located. Each of these characteristics supports flexibility in whether a given wearable is expected to have different IP connectivity. For example, such characteristics can enable wearables in a group to avoid having different IP connectivity.

[0054] A group of wearable devices can utilize this feature, and in some implementations, the group of wearable devices can negotiate (e.g., coordinate via signaling exchange between each other through one or more secure peer-to-peer wireless communication links) and select a master (or primary) wearable device within the group, which can then perform signaling exchanges in association with the supply on behalf of the entire group. For example, the group of wearable devices can further establish (e.g., negotiate, instruct, select, or otherwise determine) a shared address corresponding to the group of wearable devices, and the master wearable device can use this shared address in association with the wireless communication link established to the XPAN host. This XPAN host can be a service source device (for point-to-point deployment scenarios) or another wireless communication device along the end-to-end path between the service source device and the master wearable device (e.g., a nearby AP 102 or nearby STA 104 acting as a soft AP for relay deployment scenarios). Depending on the use of the shared address to establish the wireless communication link, the group of wearable devices can appear as a single device to the XPAN host. Similarly, and in specific implementations according to the examples described herein, the XPAN host and / or one or more wearable devices in the group of wearable devices may use a shared address to manage signaling exchange and / or operations associated with connection (re)establishment, data exchange, and connection teardown.

[0055] In some implementations, wearable devices within the group can distinguish services based on a corresponding link ID associated with each wearable device. In other words, for example, communication to or from a wearable device can be associated with a shared address (such as a shared address existing in, for example, the receiver address and / or transmitter address of a packet), and wireless communication devices (such as an XPAN host or any one or more wearable devices) can determine which wearable device a service applies to based on the link ID associated with the service. In some implementations, wearable devices can negotiate and / or assign a unique link ID to each wearable device, and wearable devices can selectively receive packets associated with the link ID corresponding to that wearable device. In some aspects, the link ID can be a TID indicating the type of service or other information (such that, in the example of a wireless earbud, services to and / or from the wireless earbud are distinguished by two separate service types). In some implementations, the group of wearable devices can operate based on a shared address under certain conditions and fall back to another provisioning mechanism (such as a separate provisioning mechanism) when such conditions are not met.

[0056] One or more wireless communication devices (such as an XPAN host and / or one or more wearable devices) can utilize the example implementations described herein to reduce (e.g., reduce by at least half) provisioning overhead involving sequences such as authentication, association, EAP or key exchange, ARP and / or DHCP leases (providing more DHCP range for other wireless communication devices in the system), which can reduce streaming start latency. Furthermore, in examples where MLO is supported, one or more wireless communication devices can use a TID-to-link mapping (T2LM) scheme to multiplex traffic via different frequencies. Additionally or alternatively, the group of wearable devices can perform localized role switching (e.g., one wearable device can disconnect from the channel to perform a scanning process (for itself or as an extended radio component of the XPAN host), while at least one other wearable device continues to transmit and / or receive traffic) without performing an explicit handshake with the XPAN host, which improves system robustness by enabling more flexible operation, including the flexibility to search for another serving device providing greater link conditions.

[0057] Furthermore, 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. Moreover, although described in the example of a wearable device, the techniques of this disclosure are applicable to any set or group of wireless communication devices (such as any set or group of terminal devices) that are associated or related to each other (e.g., serving the same or similar applications). Therefore, any wireless device can perform the described signaling and / or control operations without departing from the scope of this disclosure.

[0058] Figure 2Example signaling diagram 200 is shown, supporting the use of shared addresses to manage a group of Wi-Fi enabled wearable or handheld wireless devices according to some aspects of this disclosure. Signaling diagram 200 can be implemented or is implemented to realize various aspects of WLAN 100. For example, signaling diagram 200 illustrates communication between wireless communication device 202 and a group of wearable devices (including wearable devices 204-a and 204-b) via a wireless communication link 206 (such as a Wi-Fi link). Wearable devices 204-a and 204-b can be understood as part of the same group of wearable devices, depending on whether they serve the same or similar purposes, use cases, and / or applications. In other words, although wearable device 204-a and wearable device 204-b may be two physically different devices, they may serve the same or similar purposes and are understood to be related or associated with each other based on serving the same or similar purposes. Furthermore, although described as wearable devices in the example of signaling diagram 200, wearable device 204-a and / or wearable device 204-b may be equivalent examples of handheld devices (such as game controllers).

[0059] For example, wearable devices 204-a and 204-b could be two wireless earbuds serving the same music application (as illustrated in the example of signaling diagram 200), two controllers or sensors serving the same video game application, or examples of two health monitors tracking similar metrics and / or performing similar functions. Furthermore, although illustrated as including two wearable devices in the example of the signaling diagram, a group of wearable devices could include any number (such as two, three, four, five, etc.) of wearable devices. Wireless communication device 202 could be an example of a service device (such as a source / sink device or AP102). A source / sink device could be a telephone, mobile device, tablet, personal computer, computing device, or game console, as well as other examples of wireless communication devices with data generation and / or data processing capabilities.

[0060] In some deployments, wireless communication device 202 and the group of wearable devices may be part of an XPAN (such as a member or otherwise associated with it). In such deployments, wearable devices 204-a and 204-b may be Wi-Fi enabled (such as Wi-Fi equipped) and may support one or more mechanisms to meet expectations regarding latency, robustness, and power consumption. Depending on whether they are members of, for example, an XPAN, wearable devices 204-a and 204-b may support mechanisms to reduce latency and enable seamless transitions from one serving device to another (such as from AP to AP). For example, wearable devices 204-a and 204-b may support mechanisms to maintain voice calls while allowing users to roam on Wi-Fi AP infrastructure and meeting end-to-end latency targets based on specifications and the ecosystem (such as maintaining user comfort). In addition, wearable devices 204-a and 204-b may support mechanisms that allow users to roam freely around Wi-Fi extenders or mesh network infrastructure with a relatively low probability of service interruption or disconnection, such as during AP-AP transitions.

[0061] However, in some systems, the XPAN host (such as a service source device, AP, or computing device) can use wearable devices 204-a and 204-b as different and separate wireless communication devices. In other words, although wearable devices 204-a and 204-b may be located within the same group of wearable devices serving the same or similar purposes, some Wi-Fi designs may cause wearable devices 204-a and 204-b to communicate as two independent client devices from a network perspective. Due to communicating as two independent client devices, the service device and / or wearable devices may experience increased Wi-Fi (re)connection time (because each of wearable devices 204-a and 204-b may be expected to perform separate connection setup processes, including separate control and management frame switching, effectively doubling the connection time). For example, in an example where each of wearable devices 204-a and 204-b performs separate, independent connection setup, wearable devices 204-a and 204-b can approximately double the network management and control services (and peer management overhead) on the service device.

[0062] In the example where wearable devices 204-a and 204-b are, for example, wireless earbuds, if a user is currently using wearable device 204-a and subsequently removes wearable device 204-b from its case, wearable device 204-b can be expected to perform a complete Wi-Fi reconnection process. This complete Wi-Fi reconnection process may include scanning (active or passive), authentication (which may include authentication request packets and authentication response packets), association (which may include association request packets and association response packets), security key exchange (such as via EAPOL, which may include the exchange of four messages M1, M2, M3, and M4), ARP, and DHCP (which may include DHCP discovery packets, DHCP offer packets, DHCP request packets, and DHCP ACK packets). The complete Wi-Fi reconnection process may take a time proportional to the network congestion level (such as the number of devices in the network). For example, depending on the network congestion level, the complete Wi-Fi reconnection process may take approximately 2 to approximately 5 seconds, which may be undesirable for the end user compared to some other wearable device connection mechanisms.

[0063] Furthermore, since they communicate as two independent client devices with equally independent data streams, the service device and / or wearable device may experience increased latency or jitter for data transmitted to both wearable device 204-a and wearable device 204-b, a larger DHCP lease range granted to each wearable device, and higher power management costs for each wearable device at the service device (because the service device can maintain the power management state of all wearable devices independently to avoid transmissions to wearable devices in a sleep state; such transmissions may be referred to as leaky packet delivery). In some respects, wearable device 204-a and wearable device 204-b may experience increased latency or jitter, especially for data transmitted from AP 102 in a whole-house coverage (WHC) use case. For example, in the WHC use case, AP 102 may lack knowledge about wearable devices 204-a and 204-b (such as belonging to the same group of wearable devices) and may communicate with wearable devices 204-a and 204-b as two independently connected devices, which could cause an interruption or discontinuity in the service between wearable device 204-a and wearable device 204-b.

[0064] In other words, since AP 102 can serve many connected Wi-Fi devices, it can serve wearable device 204-a (e.g., relaying data from the service source device to the wearable device), one or more other client devices, and then wearable device 204-b (e.g., relaying data from the service source device to the wearable device). This can result in time gaps between serving wearable device 204-a and serving wearable device 204-b. To address this potential for increased latency or jitter in the WHC use case (and because both wearable devices can render data simultaneously or otherwise synchronously), wearable devices 204-a and 204-b can use larger buffers to avoid rendering latency between them. This can translate to or otherwise result in higher end-to-end latency, larger memory storage, larger device size, and higher cost at wearable devices 204-a and 204-b. Due to the 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 impair usability, user experience, and / or adoption rates.

[0065] In some implementations, to mitigate or otherwise remedy such latency and / or costs, wireless communication device 202 and the group of wearable devices may support one or more mechanisms associated with using a shared address as part of connection establishment process 208 and data exchange sequence 210. In other words, wireless communication device 202 may manage wearable devices 204-a and 204-b based on a shared address corresponding to their association (such as their grouping), and this management may include signaling exchange associated with connection establishment process 208 (which may also be a reconnection establishment process), data exchange sequence 210, and any connection teardown process. This shared address may alternatively be referred to as or understood as a Virtual Multilink (vML) address, and connection establishment process 208 using such a vML address may be understood as vML-based provisioning, since, for example, using the same shared address and differentiating traffic through other indications or mechanisms can be understood as using multiple “virtual links” relative to “one link” established using the shared address. Similarly, shared addresses and vML addresses are used interchangeably herein (including in the accompanying drawings), and in some respects, the group of wearable devices together can be understood as a vML device (having two or more physically separate devices). In some respects, each distinct group of wearable devices may have a unique shared address corresponding to that group of wearable devices.

[0066] In some implementations, wearable devices 204-a and 204-b may communicate a first set of packets indicating a shared address. For example, wearable devices 204-a and 204-b may send and / or receive the first set of packets as part of negotiation or sharing of a shared address between wearable devices 204-a and 204-b. In some implementations, the shared address may be (e.g., depending on device configuration) the MAC address of the wearable device performing connection establishment procedure 208 on behalf of that group of wearable devices. In some implementations, wearable devices 204-a and 204-b may negotiate which of wearable devices 204-a or 204-b will use the shared address to perform connection establishment procedure 208, and the wearable device performing connection establishment procedure 208 may be understood as acting as the primary device. In some aspects, wearable devices 204-a and 204-b may also negotiate via a first packet set and assign a corresponding link ID (such as a TID or other information indicating the type of service) to each of wearable devices 204-a and 204-b. Wearable devices 204-a and 204-b can use this corresponding link ID to distinguish between data services intended for wearable device 204-a and data services intended for wearable device 204-b. In some specific implementations, the first packet set may indicate a first link ID "a" corresponding to wearable device 204-a and a second link ID "b" corresponding to wearable device 204-b.

[0067] In some implementations, link ID "a" may correspond to a first TID (such as TID6), and link ID "b" may correspond to a second TID (such as TID7). In some aspects, the first TID and the second TID may belong to the same access class. In other aspects, the first TID and the second TID may belong to different access classes. Although described in this example as a "correspondence" between link IDs and TIDs, a one-to-one relationship between link IDs and TIDs may not necessarily exist. For example, multiple TIDs may map to a single link ID and / or a single TID may map to multiple link IDs.

[0068] In some implementations, wearable device 204-a and wearable device 204-b may exchange a first set of packets via a first wireless communication link between wearable device 204-a and wearable device 204-b. This first wireless communication link can be an example of any secure peer-to-peer link. For example, such a first wireless communication link can be a Bluetooth link, a Wi-Fi link, or an ultra-wideband (UWB) link, and any other example of a peer-to-peer link. In some implementations, wearable device 204-a and wearable device 204-b may protect the first wireless communication link to provide a secure harbor for the exchange of sensitive Wi-Fi link-specific information between wearable device 204-a and wearable device 204-b. For example, wearable device 204-a and wearable device 204-b may communicate using specific encryption (such as Advanced Encryption Standard (AES)-128) with Message Integrity Check (MIC) (such as a 4-byte MIC).

[0069] As part of the connection establishment process 208, in an example where wearable device 204-a plays a leading role, wearable device 204-a may communicate (such as sending to and / or receiving from) packet set 212 with wireless communication device 202. For example, wearable device 204-a may send a second packet set to wireless communication device 202 and may receive packets in response to the second packet set to establish a wireless communication link 206 with wireless communication device 202 (which may be referred to herein as a second wireless communication link). Packet set 212 may include one or more packets associated with authentication, one or more packets associated with association, one or more packets associated with EAPOL, one or more packets associated with security key exchange, one or more packets associated with DHCP, and one or more packets associated with adding a BA session. At least one packet in packet set 212 may indicate a shared address, a first link ID “a” corresponding to wearable device 204-a, and a second link ID “b” corresponding to wearable device 204-b.

[0070] In some specific implementations, wearable device 204-a may communicate one or more packets 214 with wearable device 204-b during (and / or before) the connection establishment process 208 to coordinate with wearable device 204-b on how to establish the wireless communication link 206. Additional details relating to this communication between wearable device 204-a and wearable device 204-b are provided below. Figure 5The diagram is illustrated and described. Depending on the use of the shared address for the connection establishment process 208, wearable devices 204-a and 204-b can utilize a single peer control and management message exchange and act as a connected device (such as a connected peer), which can reduce (such as halving) connection establishment time and network control and / or management overhead.

[0071] According to the establishment of the wireless communication link 206, wearable device 204-a (acting as the primary device) can send a packet 216 to wireless communication device 202 indicating a shared address (such as a vML address) and the power management state corresponding to the shared address. In some implementations, wearable device 204-a can coordinate with wearable device 204-b on the power management state, such that the power management state indicated via packet 216 indicates (such as represents) the power management state of both wearable device 204-a and wearable device 204-b. In other words, wearable device 204-a and wearable device 204-b can synchronize their power management states, such that both are simultaneously awake. Wireless communication device 202 can send an ACK 218 to wearable device 204-a upon receiving packet 216, which acknowledges to wearable device 204-a that wireless communication device 202 has successfully received the indication of the power management state corresponding to the shared address. In some aspects, packet 216 can be an empty data packet, such as a QoS empty packet.

[0072] In examples where the power management state corresponding to the shared address indicates that both wearable devices 204-a and 204-b are in a wake-up state (such as in an example where the power management bit in packet 216 is set to 0), wireless communication device 202 can begin data transmission to wearable devices 204-a and 204-b. For example, wireless communication device 202 can transmit packets 220 and 224, each packet including downlink (which may be referred to as DL) data. In some specific implementations, wireless communication device 202 can transmit an indication of a shared address and a link ID in each of packets 220 and 224. For example, packet 220 may include an indication of a shared address and a link ID “a” corresponding to wearable device 204-a, and packet 224 may include an indication of a shared address and a link ID “b” corresponding to wearable device 204-b. In other words, wireless communication device 202 can independently transmit data to both wearable devices 204-a and 204-b via separate link IDs (such as separate TIDs or service types). In some aspects, wireless communication device 202 (such as a service source device) can embed an IP Type of Service (TOS) value mapped to any link ID in packets (such as audio data packets, and the same service priority and classification can be applied to the original audio Ethernet packets that can be used for direct communication between the service source device and the wearable device). In some implementations, the IP TOS value allows service type or priority information to be carried forward and retained across multiple hops between the service source device and the wearable device.

[0073] Therefore, wearable device 204-a can receive and attempt to decode packet 220 based on the indication of link ID "a" included in packet 220, and if successful, wearable device 204-a can send an ACK 222 associated with packet 220 to wireless communication device 202. Similarly, wearable device 204-b can receive and attempt to decode packet 224 based on the indication of link ID "b" included in packet 224, and if successful, wearable device 204-b can send an ACK 226 associated with packet 224 to wireless communication device 202. In some specific implementations, wearable device 204-a can avoid attempting to (fully) decode packet 224 based on the indication of link ID "b" included in packet 224, and wearable device 204-b can avoid attempting to (fully) decode packet 220 based on the indication of link ID "a" included in packet 220. In some aspects, packet 220 may be part of a first data stream for wearable device 204-a, and packet 224 may be part of a second data stream for wearable device 204-b, and the two data streams for wearable device 204-a and wearable device 204-b may be distinguishable by a link ID. In some aspects, wireless communication device 202 may transmit packet 220 and packet 224 via the same frequency channel. In some other aspects (such as in the example where wireless communication device 202 is an MLD), wireless communication device 202 may transmit packet 220 and packet 224 via different frequency channels.

[0074] In some embodiments, packets 220 and 224 may include different information, each including information specific to one of wearable devices 204-a and 204-b. In such embodiments, a service source device (such as wireless communication device 202) may generate the information included in packets 220 and 224 based on which wearable device each of packets 220 and 224 is intended to be sent to. For example, packet 220 may include first information specific to wearable device 204-a, and packet 224 may include second information specific to wearable device 204-b. In some other embodiments, packets 220 and 224 may include some information that at least partially overlaps. For example, wireless communication device 202 may apply a certain amount of data duplication and include both the first and second information in each of packets 220 and 224, which may enable some post-processing operations at the wearable device (such as facilitating the end user's perception of three-dimensional audio).

[0075] Wearable devices 204-a and 204-b can periodically exchange information associated with (desired) power management states, and in an example where at least one of wearable devices 204-a and 204-b indicates an anticipated entry into a sleep state, wearable device 204-a (the master device) can send packets (such as another empty data packet) indicating a shared address and an updated power management state corresponding to the shared address. In an example where at least one of wearable devices 204-a and 204-b indicates an anticipated entry into a sleep state, wearable device 204-a can set a power management bit to 1. Therefore, this group of wearable devices, including at least wearable devices 204-a and 204-b, can use a shared address and differentiate services using different link IDs to manage and organize communication with wireless communication device 202. For example, if a wearable device becomes disconnected and attempts to reconnect, the reconnected wearable device can avoid any additional reconnection signaling overhead (because another link between the group of wearable devices and wireless communication device 202 will likely still be operational and can be used to re-establish the failed "link"). Additionally, depending on the use of a shared address to manage and organize communication, the periodic group-by-group key update exchange can be reduced, for example, by approximately half, for wearable devices 204-a and 204-b.

[0076] Furthermore, although the signaling diagram 200 describes an example of downlink data transmission, the described techniques are equivalently applicable to uplink data transmission. For example, wearable device 204-a may transmit a first set of one or more packets including an indication of a shared address and link ID "a", and wearable device 204-b may transmit a second set of one or more packets including an indication of a shared address and link ID "b". Thus, wireless communication device 202 may receive packets as if they were transmitted by a single wireless communication device, but a service aggregation device (such as a device ultimately responsible for parsing these packets and using the data received via these packets for one or more operations) may decode these packets and anticipate (e.g., identify or otherwise understand) that the data obtained via the first set of packets originates from wearable device 204-a and the data obtained via the second set of packets originates from wearable device 204-b. Furthermore, although illustrated in the example of signaling diagram 200 as a single hop between wireless communication device 202 and the group of wearable devices, the described techniques are applicable to relay or mesh deployments in which data can be relayed across any number of hops to or from the group of wearable devices and service source / sink devices.

[0077] Therefore, according to the example implementations of this disclosure, link identification information (such as information indicating the link ID) can be preserved and carried both point-to-point and via AP 102 (in mesh or enterprise networks). However, the content of some fields may not be carried over multiple hops (because, for example, in some systems, the content of the Signaling (SIG) field and the 802.11 header (including the QoS control field and HT control field) may not be carried over multiple hops), although the understanding of link identification information (such as the semantics of the link identification information) can be applied to both Layer 2 (L2) and Layer 3 (L3). For example, a service type or service can be mapped to a TID in some headers (such as the 802.11 header) and to a Type of Service (TOS) in some other headers (such as the IP header). In some implementations, the service type fields present in the L2 and L3 headers can be mapped to each other, and potential multiple hops across service endpoints are preserved.

[0078] Furthermore, the described technology can be implemented to consider power management for multiple wearable devices individually based on link ID when multiple wearable devices are associated via a shared address (such as through a TWT session). Additionally, in some implementations, wearable devices 204-a and 204-b can support a fallback mechanism to individual provisioning in instances where provisioning based on a shared address fails to meet one or more conditions. This fallback mechanism can be particularly useful for AP-based topologies, and in some implementations, one or both of wearable devices 204-a and 204-b can perform end-to-end QoS compliance testing as part of the fallback mechanism (e.g., by measuring, determining, or otherwise identifying whether a fallback to individual provisioning has been initiated). Furthermore, the described messaging format and exchange are applicable to various deployment scenarios and various types of devices. For example, the described messaging format and exchange can be supported by devices and networks from various manufacturers.

[0079] Furthermore, in a specific implementation where the wireless communication device 202 is capable of multi-link operation (MLO), the wireless communication device 202 may 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 device 202. For example, in an example where the wireless communication device 202 is an MLD capable of operating multiple links (such as a 2.4 GHz link, a 5 GHz link, and / or a 5 GHz link), the wireless communication device 202 may support simultaneous transmission to and / or reception from wearable devices 204-a and 204-b on two different links, the two different links corresponding to two different radio frequency channels. In such an implementation, the wireless communication device 202 may transmit an indication of T2LM, and wearable device 204-a may tune at least one radio component to a first frequency channel to which link ID "a" is mapped, and wearable device 204-b may tune at least one radio component to a second frequency channel to which link ID "b" is mapped. Therefore, wireless communication device 202 can support greater MAC efficiency, achieve more concurrent time on wireless communication device 202, reduce power consumption on each of wearable devices 204-a and 204-b, and reduce latency and / or jitter between data destined for wearable devices, which in turn reduces the memory constraints, size and cost of wearable devices.

[0080] By using shared addresses in the connection establishment process, aspects of this disclosure can be implemented to achieve various addressing formats for various link types. For Ethernet addressing, for example, example packet addressing could be [H SAP [-M - vML-M] and [vML-M - H] SAP -M]. For 802.11 addressing used for point-to-point communication, an example packet addressing could be [vML-M -H]. SAP -M - H SAP -M] and [H SAP -M -vML-M - H SAP -M]. For 802.11 addressing used for communication over an AP, an example packet addressing could be [AP]. X -M - H STA -M - vML-M]、[vML-M - AP X -M - H STA -M]、[AP X -M - vML-M -H STA -M] and [H STA -M - AP X -M - vML-M]. In such examples, H SAP-M can be the address of the service source / sink device used for Ethernet or direct wireless communication, vML-M can be the address of the group of wearable devices, H STA -M can be the address of the service source / sink device used for relaying wireless communications, and the AP X -M can be the address of AP 102 that relays packets between the service source / sink device and the group of wearable devices.

[0081] Figure 3 Example process flow 300 is illustrated, supporting the use of a shared address to manage a group of Wi-Fi-enabled wearable or handheld wireless devices according to some aspects of this disclosure. Process flow 300 can be implemented or is implemented to implement or facilitate aspects of WLAN 100 and signaling diagram 200. For example, process flow 300 illustrates communication between STA 104 (which may be an example of a service source / sink device), wearable devices 204-a and 204-b, and AP 102 (which may be an example of a QoS AP 102). Figure 2 The wireless communication device 202 illustrated and described with reference to this figure may be an example of a STA 104 or an AP 102. In some specific implementations, wearable devices 204-a and 204-b may be associated with the same group of wearable devices and may use a shared address to perform a connection establishment process with the STA 104 (for point-to-point communication) or the AP 102 (for relay communication on the AP), such as by... Figure 2 The connection establishment process 208 described in this figure is illustrated and can be referenced.

[0082] In the following description of process flow 300, operations (such as reporting or providing) may be performed in a different order than those shown, or operations performed by the example device may be performed in a different order or at different times. For example, a particular operation may be omitted from process flow 300, or other operations may be added to process flow 300. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously.

[0083] At 302, wearable devices 204-a and 204-b may communicate (e.g., send and / or receive) one or more packets based on the establishment (e.g., setting up) of 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.

[0084] At 304, wearable devices 204-a and 204-b may communicate (e.g., send and / or receive) one or more packets based on negotiation of the primary link and / or negotiation of a shared address (such as a vML address). For example, wearable devices 204-a and 204-b may exchange one or more packets indicating which of them should assume the primary role and perform the connection establishment procedure, and / or may exchange one or more packets indicating the shared address to be used in the connection establishment procedure. In some aspects, the same set of frames or different sets of frames may indicate which wearable device should assume the primary role and the shared address. The primary link can be understood as the link or device through which other links or devices representing this group of wearable devices perform the connection establishment procedure. Additionally, in some implementations, wearable devices 204-a and 204-b may transmit one or more packets that indicate a link ID "a" corresponding to wearable device 204-a and a link ID "b" corresponding to wearable device 204-b relative to a shared address. For example, wearable devices 204-a and 204-b may send and / or receive packets based on negotiation (such as coordination) assigned by the link ID. Therefore, wearable devices 204-a and 204-b may use the same shared address (such as the same transmitter address or receiver address) and alternatively distinguish services based on the corresponding (and unique) link ID.

[0085] At point 306, in an example where wearable device 204-a is instructed or otherwise selected to assume a primary role and perform the connection establishment process, wearable device 204-a may perform a scanning operation. This scanning operation may include one or both passive and active scanning, and wearable device 204-a may perform the scanning operation to discover wireless communication devices with which to connect to obtain internet or network access. In some specific implementations, wearable device 204-a may discover STA 104 (such as a source / sink device). In some other examples, wearable device 204-a may discover AP 102 (such as a wireless communication device along a relay path between the source / sink device and wearable device 204-a).

[0086] At point 308, in the example where wearable device 204-a discovers STA 104 based on a scanning operation, wearable device 204-a and STA 104 may exchange one or more authentication packets. For example, wearable device 204-a may send an authentication request to STA 104, and STA 104 may send an authentication response corresponding to the authentication request. In some implementations, wearable device 204-a and STA 104 may include an indication of a shared address in both the authentication request and the authentication response based on a shared address-based provisioning.

[0087] At 310, wearable device 204-a and STA 104 may communicate one or more association packets. For example, wearable device 204-a may send an association request to STA 104, and STA 104 may send an association response corresponding to the association request. In some implementations, wearable device 204-a and STA 104 may include an indication of a shared address in both the association request and the association response, based on a shared address-based provisioning.

[0088] At 312, wearable device 204-a and STA 104 may communicate one or more packets associated with ARP negotiation. According to the ARP negotiation, wearable device 204-a may receive indications of the gateway and Domain Name System (DNS) server associated with and related to communication with STA 104. In some implementations, wearable device 204-a and STA 104 may include indications of a shared address in one or more packets associated with ARP negotiation based on the availability of a shared address.

[0089] At 314, wearable device 204-a and STA 104 may communicate one or more packets associated with DHCP negotiation. In some aspects, one or more packets associated with DHCP negotiation may indicate an IP address to wearable device 204-a. In some embodiments, the IP address may correspond to the group of wearable devices based on the provision of shared addresses. Wearable device 204-a may establish a second wireless communication link with STA 104 based on packet switching at 308, 310, 312, and 314. In some embodiments, wearable device 204-a may establish a second wireless communication link for both wearable device 204-a and wearable device 204-b based on the use of shared addresses. Additionally, in some embodiments, wearable device 204-a may provide indications of link ID "a" (corresponding to wearable device 204-a) and link ID "b" (corresponding to wearable device 204-b) via any or more of the packet switching at 308, 310, 312, and 314. In the specific implementation where STA 104 is the service source device, STA 104 can use the indication of link ID "a" to generate and deliver a first data packet specific to wearable device 204-a, and can use link ID "b" to generate and deliver a second data packet specific to wearable device 204-b.

[0090] At 316, wearable devices 204-a and 204-b can communicate one or more packets by establishing a second wireless communication link with STA 104 based on wearable device 204-a. In some aspects, such one or more packets can indicate information to wearable device 204-b indicating 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, wearable devices 204-a and 204-b can negotiate (such as coordinate) such security keys and / or IP addresses, and wearable device 204-a can establish a second wireless communication link based on this negotiation. In some aspects, such negotiation can be associated with the corresponding capabilities of wearable devices 204-a and 204-b.

[0091] At point 318, in order to establish a second wireless communication link, wearable device 204-a may communicate one or more packets with STA 104 to establish a first BA session between wearable device 204-a and STA 104. For example, one of wearable device 204-a and STA 104 may send an ADDBA request to the other of wearable device 204-a and STA 104, and the other of wearable device 204-a and STA 104 may send an ADDBA response corresponding to the ADDBA request. In some specific implementations, wearable device 204-a and STA 104 may include a link ID "a" (and a shared address) in the ADDBA request and ADDBA response to establish a first BA session dedicated to wearable device 204-a.

[0092] At 320, based on the establishment of a second wireless communication link between wearable device 204-a and STA 104, wearable device 204-b may communicate one or more packets with STA 104 to establish a second BA session between wearable device 204-b and STA 104. For example, one of wearable device 204-b and STA 104 (such as a data transmitter) may send an ADDBA request to the other of wearable device 204-b and STA 104, and the other of wearable device 204-b and STA 104 may send an ADDBA response corresponding to the ADDBA request. In some specific implementations, wearable device 204-b and STA 104 may include a link ID "b" (and a shared address) in the ADDBA request and ADDBA response to establish a second BA session dedicated to wearable device 204-b. In other words, based on the establishment of a second wireless communication link by wearable device 204-a, wearable device 204-a and wearable device 204-b can each establish separate BA sessions for data transmission, and each of wearable device 204-a and wearable device 204-b can independently confirm the received data.

[0093] At 322, in some specific implementations, wearable device 204-a and STA 104 may communicate one or more packets associated with TWT session establishment. In other words, STA 104 may send information to wearable device 204-a indicating a first scheduling of a communication time interval during which wearable device 204-a and STA 104 may communicate packets associated with link ID "a". For example, one of wearable device 204-a and STA 104 (such as a data transmitter) may send a TWT establishment request to the other of wearable device 204-a and STA 104, and the other of wearable device 204-a and STA 104 may send a TWT establishment response corresponding to the TWT establishment request, each of the TWT establishment request and TWT establishment response including an indication of a shared address and link ID "a". In some specific implementations, in examples where both wireless communication devices support TWT operation, wearable device 204-a and STA 104 can establish TWT scheduling for communication associated with link ID "a". Additionally or alternatively, wearable device 204-a and STA 104 can communicate according to an untimed automatic power-saving delivery (U-APSD) mechanism.

[0094] At 324, in some specific implementations, wearable device 204-b and STA 104 may communicate one or more packets associated with TWT session establishment. In other words, STA 104 may send information to wearable device 204-b indicating a second scheduling interval during which wearable device 204-b and STA 104 may communicate packets associated with link ID "b". For example, one of wearable device 204-b and STA 104 (such as a data transmitter) may send a TWT establishment request to the other of wearable device 204-b and STA 104, and the other of wearable device 204-b and STA 104 may send a TWT establishment response corresponding to the TWT establishment request, each of the TWT establishment request and TWT establishment response including indications of a shared address and link ID "b". In some specific implementations, in examples where both wireless communication devices support TWT operation, wearable device 204-b and STA 104 can establish TWT scheduling for communication associated with link ID "b". Therefore, STA 104 can establish separate TWT sessions for each link ID (such as for each TID or service type and subsequently for each wearable device in a set of wearable devices). Additionally or alternatively, wearable device 204-b and STA 104 can communicate according to a U-APSD mechanism.

[0095] At point 326, in an alternative example where wearable device 204-a discovers AP 102 based on a scanning operation, wearable device 204-a and AP 102 may exchange one or more authentication packets. For example, wearable device 204-a may send an authentication request to AP 102, and AP 102 may send an authentication response corresponding to the authentication request. In some implementations, wearable device 204-a and AP 102 may include indications of the shared address in both the authentication request and the authentication response based on a shared address-based provisioning.

[0096] At 328, wearable device 204-a and AP 102 can communicate one or more association packets. For example, wearable device 204-a can send an association request to AP 102, and AP 102 can send an association response corresponding to the association request. In some implementations, wearable device 204-a and AP 102 can include indications of the shared address in both the association request and the association response, based on a shared address-based provisioning.

[0097] At 330, wearable device 204-a and AP 102 may communicate one or more packets associated with ARP negotiation. According to the ARP negotiation, wearable device 204-a may receive indications of the gateway and Domain Name System (DNS) server associated with communication with AP 102. In some implementations, wearable device 204-a and AP 102 may include indications of a shared address in one or more packets associated with ARP negotiation based on the availability of a shared address.

[0098] At 332, wearable device 204-a and AP 102 may communicate one or more packets associated with DHCP negotiation. In some aspects, one or more packets associated with DHCP negotiation may indicate an IP address to wearable device 204-a. In some implementations, the IP address may correspond to the group of wearable devices based on the provision of shared addresses. Based on packet switching at 326, 328, 330, and 332, wearable device 204-a may establish a second wireless communication link with AP 102 (as part of a relay path between STA 104 and the group of wearable devices). In some implementations, wearable device 204-a may establish a second wireless communication link for both wearable device 204-a and wearable device 204-b based on the use of shared addresses. Additionally, in some implementations, wearable device 204-a may provide indications of link ID "a" (corresponding to wearable device 204-a) and link ID "b" (corresponding to wearable device 204-b) via any or more of the packet switching at 326, 328, 330, and 332. AP 102 may relay this information to STA 104, and STA 104 may use the indication of link ID "a" to generate and deliver (via AP 102) a first data packet specific to wearable device 204-a, and may use link ID "b" to generate and deliver (via AP 102) a second data packet specific to wearable device 204-b.

[0099] At 334, wearable devices 204-a and 204-b can communicate one or more packets by establishing a second wireless communication link with AP102 based on wearable device 204-a. In some aspects, such one or more packets can instruct wearable device 204-b on information indicating PTK, GTK, gateway IP, DNS server IP, and DHCP IP handshakes. In some implementations, wearable devices 204-a and 204-b can negotiate (such as coordinate) such security keys and / or IP addresses, and wearable device 204-a can establish a second wireless communication link based on this negotiation. In some aspects, such negotiation can be associated with the corresponding capabilities of wearable devices 204-a and 204-b.

[0100] At 336, wearable device 204-a can perform a QoS compliance test with AP 102, which indicates whether the relay path between STA 104 and wearable device 204-a via AP 102 can support QoS-based service prioritization. According to the QoS compliance test, wearable device 204-a and STA 104 can exchange one or more packets via AP 102 to test whether QoS-based service prioritization is maintained (e.g., preserved) at each hop across the multi-hop relay path. For example, wearable device 204-a and STA 104 can exchange one or more Internet Control Message Protocol (ICMP) packets (such as ICMP echo request and / or response packets) via AP 102 to test the QoS compliance of the end-to-end relay path between STA 104 and wearable device 204-a. In an example where response ICMP packets (such as ICMP echo responses) are received with the same priority as the transmission of the corresponding request, the end-to-end relay path successfully passes the QoS compliance test. Otherwise, the end-to-end relay path may fail the QoS compliance test. Figure 4 and Figure 5 Additional details related to how wearable device 204-a can track information associated with which APs 102 pass the QoS compliance test and which APs 102 cause the QoS compliance test to fail are shown and described in more detail with reference to these figures.

[0101] At point 338, in an example where the end-to-end relay path passes the QoS compliance test, wearable device 204-a can continue with shared address-based provisioning and communicate one or more packets with AP 102 to establish a first BA session between wearable device 204-a and AP 102. For example, one of wearable device 204-a and AP 102 can send an ADDBA request to the other of wearable device 204-a and AP 102, and the other of wearable device 204-a and AP 102 can send an ADDBA response corresponding to the ADDBA request. In some implementations, wearable device 204-a and AP 102 can include the link ID "a" (and the shared address) in the ADDBA request and ADDBA response to establish a first BA session dedicated to wearable device 204-a. As part of the first BA session, wearable device 204-a may employ TWT-based transmission and / or reception, or may employ early reception termination to manage power consumption at wearable device 204-a (depending on the capabilities of, for example, AP 102).

[0102] At point 340, wearable device 204-b can also continue to provide power based on the shared address and communicate one or more packets with AP 102 to establish a second BA session between wearable device 204-b and AP 102. For example, one of wearable device 204-b and AP 102 can send an ADDBA request to the other of wearable device 204-b and AP 102, and the other of wearable device 204-b and AP 102 can send an ADDBA response corresponding to the ADDBA request. In some implementations, wearable device 204-b and AP 102 can include the link ID "b" (and the shared address) in the ADDBA request and ADDBA response to establish a second BA session dedicated to wearable device 204-b. As part of the second BA session, wearable device 204-b can use TWT-based transmission and / or reception, or it can use early receive termination to manage power consumption at wearable device 204-b (depending on, for example, the capabilities of AP 102).

[0103] Figure 4 Example process flow 400 is illustrated, supporting the use of a shared address to manage a group of Wi-Fi-enabled wearable or handheld wireless devices according to some aspects of this disclosure. Process flow 400 can be implemented or is implemented to implement or facilitate aspects of WLAN 100, signaling diagram 200, or process flow 300. For example, process flow 400 illustrates communication between STA 104 (which may be an example of a service source / sink device), wearable device 204-a, wearable device 204-b, and AP 102 (which may be an example of a non-QoS AP). Figure 2 The wireless communication device 202 illustrated and described with reference to this figure may be an example of STA 104 or AP 102. In some specific implementations, wearable devices 204-a and 204-b may be associated with the same group of wearable devices, and in an example where AP 102 is a non-QoS AP, the connection establishment process with AP 102 (for relay communication on the AP) may fall back from using a shared address to using a separate address. For example, process flow 400 illustrates communication between wearable devices 204-a, wearable devices 204-b and AP 102 in an example where AP 102 fails the QoS compliance test.

[0104] In the following description of process flow 400, operations (such as reporting or providing) may be performed in a different order than those shown, or operations performed by the example device may be performed in a different order or at different times. For example, a particular operation may be omitted from process flow 400, or other operations may be added to process flow 400. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously.

[0105] At position 402, wearable device 204-a can send an indication of the target AP 102 to wearable device 204-b. In some specific implementations, wearable device 204-a can determine that AP 102 is a non-QoS AP based on measurements, received indications, or other means (wearable device 204-a can refer to...). Figure 3 (A determination is made at 336) to send an instruction to the target AP 102 to the wearable device 204-b. Based on the instruction to the target AP 102, wearable devices 204-a and 204-b can continue according to a separate supply mechanism, each of which performs a separate connection establishment process with AP 102 according to the separate supply mechanism.

[0106] At 404, for example, wearable device 204-a and AP 102 may exchange one or more authentication packets. For example, wearable device 204-a may send an authentication request to AP 102, and AP 102 may send an authentication response corresponding to the authentication request. In some specific implementations, wearable device 204-a and AP 102 may, depending on a separate provision, include in both the authentication request and the authentication response an indication of a first device-specific address (such as a MAC address specific to wearable device 204-a).

[0107] At 406, wearable device 204-b and AP 102 may communicate one or more authentication packets. For example, wearable device 204-b may send an authentication request to AP 102, and AP 102 may send an authentication response corresponding to the authentication request. In some implementations, wearable device 204-b and AP 102 may, depending on a separate provision, include in both the authentication request and the authentication response an indication of a second device-specific address (such as a MAC address specific to wearable device 204-b).

[0108] At 408, wearable device 204-a and AP 102 may communicate one or more association packets. For example, wearable device 204-a may send an association request to AP 102, and AP 102 may send an association response corresponding to the association request. In some implementations, wearable device 204-a and AP 102 may, depending on individual availability, include an indication of a first device-specific address in both the association request and the association response.

[0109] At 410, wearable device 204-b and AP 102 may communicate one or more association packets. For example, wearable device 204-b may send an association request to AP 102, and AP 102 may send an association response corresponding to the association request. In some implementations, wearable device 204-b and AP 102 may, depending on a separate provision, include an indication of a second device-specific address in both the association request and the association response.

[0110] At 412, wearable device 204-a and AP 102 may communicate one or more packets associated with ARP negotiation. In some specific implementations, wearable device 204-a and AP 102 may, depending on individual availability, include an indication of a first device-specific address in one or more packets associated with ARP negotiation.

[0111] At 414, wearable device 204-b and AP 102 may communicate one or more packets associated with ARP negotiation. In some specific implementations, wearable device 204-b and AP 102 may, depending on a separate provision, include an indication of a second device-specific address in one or more packets associated with ARP negotiation.

[0112] At 416, wearable device 204-a and AP 102 can communicate one or more packets associated with DHCP negotiation. In some aspects, one or more packets associated with DHCP negotiation can indicate a first IP address to wearable device 204-a. In some implementations, the first IP address may exclusively correspond to wearable device 204-a based on a separate supply.

[0113] At 418, wearable device 204-b and AP 102 can communicate one or more packets associated with DHCP negotiation. In some aspects, one or more packets associated with DHCP negotiation can indicate a second IP address to wearable device 204-b. In some implementations, the second IP address can exclusively correspond to wearable device 204-b based on a separate supply.

[0114] Depending on the separate connection setup process, wearable devices 204-a and 204-b can communicate with AP 102 as two distinct devices. In some implementations, wearable devices 204-a and 204-b can manage power consumption by individually setting their power management bits to 0 or 1 (e.g., within QoS empty packets) to indicate the corresponding power management status.

[0115] Figure 5 An example flowchart 500 is shown that supports the use of shared addresses to manage a group of Wi-Fi-enabled wearable or handheld wireless devices according to some aspects of this disclosure. Flowchart 500 may be implemented or implemented to implement or facilitate aspects of WLAN 100, signaling diagram 200, process flow 300, or process flow 400. For example, one or more wearable devices (such as wearable device 204-a or wearable device 204-b) may perform operations associated with flowchart 500 to measure, receive indications, or otherwise determine whether a shared address-based provisioning mechanism (which may be referred to as vML-based provisioning) or a separate provisioning mechanism is employed.

[0116] At point 502, the wearable device may determine whether to establish a first wireless communication link with at least one other wearable device in a group of wearable devices. In some specific implementations, for example, a group of wearable devices may establish a first wireless communication link for communication between two or more wearable devices, and may use the first wireless communication link to exchange (such as sending and / or receiving) control traffic between the two or more wearable devices. Such control traffic may include a first set of packets exchanged by the wearable devices to negotiate, select, and / or assign a shared address and a corresponding link ID corresponding to each respective wearable device. For example, the group of wearable devices may piggyback on the first wireless communication link additional Wi-Fi information (such as information related to XPAN) that is public to the group of wearable devices (such as information applicable to the group of wearable devices). Such a first wireless communication link may be an example of any peer-to-peer link and may act as a “backhaul” link between two or more wearable devices. In an example where one group of wearable devices is a wireless earbud, the first wireless communication link may be a Bluetooth link (such as a BLE link), and the wireless earbud may perform BLE control exchange via the first wireless communication link. In an example where a first wireless communication link is not established, the wearable device may determine to employ a separate supply mechanism (at 504).

[0117] At point 506, in the example where a first wireless communication link is established, the wearable device can determine whether the wireless communication device establishing the second wireless communication link with the wearable device is a source / sink device or another wireless communication device (such as AP 102) along a relay path between the source / sink device and the wearable device. Direct communication between the wearable device and the source / sink device can be referred to as point-to-point communication, and indirect communication between the wearable device and the source / sink device via another wireless communication device can be referred to as AP-on-AP communication.

[0118] At point 508, in the example where communication is on an AP, the wearable device can perform one or more operations associated with the selection of a candidate AP. For example, the wearable device can select candidate AP 102 for routing traffic between the wearable device and the service source / sink device.

[0119] At 510, the wearable device can determine whether candidate AP 102 supports Wireless Multimedia (WMM). In examples where candidate AP 102 does not support WMM, the wearable device can employ a separate provisioning mechanism (at 504).

[0120] At point 512, in an example where candidate AP 102 supports WMM or in an example where communication is point-to-point, the wearable device can negotiate primary and secondary roles with other wearable devices in the group. In some implementations, the wearable device can perform this negotiation by communicating (e.g., sending and / or receiving) one or more packets with other wearable devices in the group via, for example, a first wireless communication link (e.g., via at least one first wireless communication link).

[0121] At point 514, the wearable device can further negotiate a shared address corresponding to the association between the wearable device and other wearable devices in the group. This shared address can be understood as, and is equivalently referred to herein as, a vML address.

[0122] At point 516, the wearable device may further negotiate one or more aspects associated with scanning operations, authentication, association, EAPOL and / or security keys, ARP and / or DHCP. In other words, for example, the wearable device may negotiate (such as coordinate) one or more aspects associated with how to establish a second wireless communication link with the wireless communication device.

[0123] At point 518, the wearable device can determine whether the wireless communication device with which it establishes a second wireless communication link exists in a vML whitelist or a vML blacklist. In other words, the wearable device can determine whether the wireless communication device exists in a first device list (such as a vML whitelist) that allows provisioning based on shared addresses, or in a second device list (such as a vML blacklist) that does not allow provisioning based on shared addresses. In some implementations, the wearable device can determine whether the wireless communication device exists in either the first or second device list by searching for an ID (or some other identifying information) associated with the wireless communication device in one or both lists. In the example where the wireless communication device exists in the second device list, the wearable device can employ a separate provisioning mechanism (at point 504).

[0124] At 520, in an example where the wireless communication device exists in the first device list, the wearable device may employ a shared address-based provisioning (such as vML-based provisioning).

[0125] Alternatively, at 522, in an example where the wireless communication device is not present in either the first device list or the second device list, the wearable device may perform or otherwise participate in a QoS compliance test related to whether the end-to-end path between the wearable device and the service source / sink device supports QoS-based service prioritization. At 524, in an example where the end-to-end path fails the QoS compliance test, the wearable device may add the wireless communication device to the second device list (such as a vML blacklist). At 526, in an example where the end-to-end path passes the QoS compliance test, the wearable device may add the wireless communication device to the first device list (such as a vML whitelist). Based on this maintenance of the first and second device lists, the wearable device can avoid repeating QoS compliance tests for wireless communication devices for which previous QoS compliance tests have already been performed. In some aspects, the wearable device may maintain the first and second device lists as long as it is connected to the Internet (e.g., until the wearable device is placed in a case, the battery is depleted, or it is otherwise disconnected). In some other respects, wearable devices can maintain a first device list and a second device list for a threshold period of time, at which point the wearable device can refresh (such as clear) the list and then rebuild the list by performing a completely new QoS compliance test.

[0126] Figure 6An example communication timeline 600 is shown that supports the use of a shared address to manage a group of Wi-Fi-enabled wearable or handheld wireless devices according to some aspects of this disclosure. Communication timeline 600 may be implemented or implemented to implement or facilitate aspects of WLAN 100, signaling diagram 200, process flow 300, process flow 400, or flowchart 500. For example, communication timeline 600 illustrates communication between wearable device 204-b and wireless communication device 202, which may be via... Figures 2 to 4 Examples of the corresponding devices described in these figures are illustrated and referenced. – In some specific implementations, communication timeline 600 illustrates how wearable device 204-b can perform early receive termination based on link ID (to save battery power).

[0127] For example, in a specific implementation where a wearable device in a group of wearable devices performs link ID-based early termination, the wearable device may decode or parse a portion of a packet (such as a frame header) to determine whether the packet is intended for that wearable device or another wearable device in the group. In some implementations, depending on the capabilities of the wireless communication device 202, link ID-based early termination may be an alternative to link ID-based TWT sessions. For example, some APs 102 may not support TWT session establishment or U-APSD, and because of this, link ID-based delivery within the negotiated time window may not be feasible.

[0128] Furthermore, since power management states (which may also be referred to as power management modes) can be defined at different levels (such as for each shared address), all wearables in a group can simultaneously enter a given power management state, and since AP 102 can deliver packets associated with all link IDs during the same wake-up time, each wearable can adopt early reception termination based on which link ID a given packet is associated with. In some implementations, for example, a wearable can determine whether a packet is intended for itself or another wearable based on the link ID (such as TID or service type) associated with the packet. Therefore, a wearable can decode packets associated with its own corresponding link ID and can avoid decoding packets associated with different link IDs. In some implementations, each wearable in a group can support or be hardware-configured to terminate packet reception based on a programmed link ID value (such as a programmed TID or service type).

[0129] For example, as illustrated in the example of communication timeline 600, wearable device 204-b may receive packet 220 including a frame header indicating link ID "a," which, according to prior negotiation, wearable device 204-b may determine corresponds to wearable device 204-a rather than wearable device 204-b. Therefore, wearable device 204-b may avoid decoding the data portion of packet 220 and instead achieve a certain amount of power saving. In another example, wearable device 204-b may receive packet 224 including a frame header indicating link ID "b," which, according to prior negotiation, wearable device 204-b may determine corresponds to wearable device 204-b. Therefore, wearable device 204-b may decode the data portion of packet 224, and in examples where decoding is successful, may send an ACK 226 associated with packet 224 to wireless communication device 202. In some implementations, wearable device 204-b can obtain an indication of the link ID associated with a given packet based on the TID value in the frame header (such as the TID value in the QoS control field of the frame header).

[0130] Figure 7 An example flowchart 700 is shown, supporting the use of shared addresses to manage a group of Wi-Fi-enabled wearable or handheld wireless devices according to some aspects of this disclosure. Flowchart 700 may be implemented or implemented to implement or facilitate aspects of WLAN 100, signaling diagram 200, process flow 300, process flow 400, flowchart 500, or communication timeline 600. For example, flowchart 700 illustrates one or more operations that one or more wearable devices in a group can perform to maintain reliable transmission and / or reception of data. In some specific implementations, for example, a group of wearable devices may operate according to an independent link mode 702 and a master link mode 704, in which each wearable device in the group receives and acknowledges packets associated with its unique link ID, and in the master link mode, a wearable device receives and acknowledges packets associated with its own unique link ID and packets associated with another link ID corresponding to another wearable device in the group. This group of wearable devices can switch between independent link mode 702 and main link mode 704 based on whether one or more link quality metrics meet one or more conditions.

[0131] For example, while a group of wearable devices may be co-located and within approximately the same or similar distance from the source / sink device or another wireless communication device along a multi-hop relay path, each wearable device may be a different physical device and may also have different link conditions. For instance, different wearable devices within a group may have different channel states and / or different signal-to-interference-plus-noise ratio (SINR) measurements, which may lead to link-by-link considerations associated with downlink rate adaptation and Received Signal Strength Indicator (RSSI) monitoring.

[0132] In a specific implementation where a group of wearable devices are connected to a wireless communication device with MLO capability, each link of the MLO-capable wireless communication device can achieve link-by-link rate adaptation via, for example, packet error rate (PER) tracking to monitor downlink rate adaptation and RSSI. Additionally, the connected wireless communication devices can independently (e.g., based on coordinated beamforming (CBF) generated independently by each wearable device and directed from the connected wireless communication devices to each wearable device (for MLO-capable wireless communication devices, this can manifest as two links with the same MLD)) perform beamforming on each link or frequency.

[0133] Alternatively, in an implementation where one group of wearable devices is not connected to a wireless communication device with MLO capability, each wearable device can track and detect asymmetry in link conditions (e.g., on a per-link ID basis), and when a link quality metric indicates or suggests that the link asymmetry is large enough to cause a measurable difference in link quality, the group of wearable devices can switch between an independent link mode 702 and a primary link mode 704. In other words, the group of wearable devices can switch to primary link mode 704 during periods of asymmetry (such as the time period during which a first link of a first wearable device in the group is associated with a first link quality metric, and the difference between the first link quality metric and a second link quality metric associated with a second link of a second wearable device in the group exceeds a threshold).

[0134] At 706, for example, each of a group of wearable devices can receive data (such as packets) associated with an assigned link ID and can independently send feedback information (such as ACKs).

[0135] At 708, each of the group of wearable devices can monitor one or more of the following associated with communication between the wearable device and the wireless communication devices to which the group of wearable devices are connected: average RSSI, number of retries (such as downlink retries and / or uplink retries), or number of replicated ACKs.

[0136] At 710, each wearable device in the group can determine whether the corresponding link is associated with an unreliable link budget. In an example where no wearable device in the group detects an unreliable link budget, each wearable device in the group can continue to monitor the average RSSI, number of retries, or number of replicated ACKs between itself and the wireless communication device to which the group of wearable devices is connected (at 708). In some implementations, the group of wearable devices can periodically share information associated with the average RSSI, number of retries, and / or number of replicated ACKs with each other via at least one first wireless communication link between the wearable devices in the group.

[0137] At 712, in an example where 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 an independent link mode 702 to a master link mode 704, and the wearable device with a relatively larger RSSI may assume a master role according to this transition. For example, a first wearable device may assume a master role relative to a second wearable device that has detected an unreliable link budget. In some implementations, the wearable device may detect the unreliable link budget based on the increment 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 an example where the increment between the average RSSI of the first wearable device and the average RSSI of the second wearable device exceeds a threshold, one or both of the first and second wearable devices may detect an asymmetric link budget, and an unreliable link budget condition may be triggered or identified for the second wearable device (such as a wearable device with a smaller RSSI). In some other specific implementations, where the number of retries (such as downlink retries for packets from the source device or relay wireless communication device) and / or duplicate ACKs (for packets received by the wearable device but whose corresponding ACKs were not successfully received by the source device or relay wireless communication device) increases above a threshold, and / or where the absolute RSSI of the wearable device decreases below a threshold, one or both of the first and second wearable devices may trigger or identify an unreliable link budget condition.

[0138] At point 714, a first wearable device (such as a master device) can receive and decode a first packet associated with its own link ID and a second packet associated with the link ID corresponding to the second wearable device, and can forward (e.g., relay) data received via the second packet to the second wearable device via a first wireless communication link between the first and second wearable devices. The second wearable device can receive data from the first wearable device and can send feedback information associated with the data to the first wearable device, which the first wearable device can send to wireless communication devices to which the group of wearable devices is connected via one or more BAs. In other words, in addition to sending one or more ACKs for packets associated with the link ID corresponding to the first wearable device, the first wearable device can also send one or more ACKs on behalf of the second wearable device.

[0139] At 716, both the first and second wearable devices can continue to monitor the average RSSI, number of retries, and / or number of replicated ACKs while operating according to the main link mode 704. In some embodiments, the group of wearable devices can periodically share information associated with the average RSSI, number of retries, and / or number of replicated ACKs with each other via at least one first wireless communication link between the wearable devices in the group.

[0140] At 718, each wearable device in the group (particularly including the second wearable device) can determine whether the corresponding link is associated with an unreliable link budget. In an example where at least one wearable device does not have a reliable link budget (such as in an example where the second wearable device still detects an unreliable link budget), the first wearable device can continue to operate as the master device and can continue to receive packets associated with multiple different link IDs (for forwarding to one or more wearable devices still suffering from an unreliable link budget). Alternatively, in an example where all wearable devices in the group detect a reliable link budget (such as in an example where the link condition at the second wearable device improves), the group of wearable devices can switch from master link mode 704 to independent link mode 702. Furthermore, independent of the group of wearable devices switching between independent link mode 702 and master link mode 704, the wireless communication devices to which the group of wearable devices are connected perform rate adaptation on a per-link (such as per-TID) basis.

[0141] In some implementations, in master link mode 704, the master wearable device can remain awake for a longer period, forward data to at least one other wearable device, and transmit ACKs on behalf of at least one other wearable device. Therefore, the master wearable device may experience relatively high power consumption in master link mode 704, and in some implementations, one or more mechanisms may be supported to mitigate the duration of this group of wearable devices in master link mode 704. For example, to facilitate switching from master link mode 704 to standalone link mode 702, the master wearable device may send an indication of a recommended decoding rate (such as a recommended modulation and decoding scheme (MCS)) for wearable devices suffering from unreliable link budgets. In such examples, the recommended decoding rate can be used for both communication between the master wearable device and the wireless communication device, and communication between the wearable device suffering from unreliable link budgets and the wireless communication device.

[0142] The primary wearable device can indicate the recommended decoding rate via various packet types, such as via QoS empty packets or any type of management frame transmitted to the wireless communication device. In some specific implementations, which field the primary wearable device indicates the recommended decoding rate via can vary depending on the capabilities of the primary wearable device and / or the wireless communication device. For High Throughput (HT), for example, the primary wearable device can indicate the recommended decoding rate in the MCS Feedback (MFB) / Antenna Selection (ASELC) field within the Link Adaptation Control field in HT Control. For Very High Throughput (VHT), the primary wearable device can indicate the recommended decoding rate in the VHT-MCS field within the MFB field in the VHT Variant HT Control field. For High Efficiency (HE), the primary wearable device can indicate the recommended decoding rate in the HE-MCS field within the HE Link Adaptation (HLA) Control field. For Extremely High Throughput (EHT), the primary wearable device can indicate the recommended decoding rate in the EHT-MCS field within the EHT Link Adaptation (ELA) Control field. A wireless communication device that receives an indication of a recommended decoding rate can update one or more link parameters (such as MCS values) for communication with the main wearable device and one or more other wearable devices in the group of wearable devices based on the indication.

[0143] Figure 8Example XPAN topologies 800, 801, and 802 are illustrated, supporting the use of shared addresses to manage a group of Wi-Fi-enabled wearable or handheld wireless devices according to some aspects of this disclosure. XPAN topologies 800, 801, and 802 can be implemented or are implemented to implement or facilitate aspects of WLAN 100, signaling diagram 200, process flow 300, process flow 400, flowchart 500, communication timeline 600, or flowchart 700. For example, each of XPAN topologies 800, 801, and 802 illustrates an example deployment scenario of one or more STAs 104, one or more APs 102, wearable devices 204-a and 204-b.

[0144] As illustrated in XPAN topology 800, AP 102 can communicate with STA 104 via link 803, and STA 104 can communicate with wearable devices 204-a and 204-b via links 804-a and 804-b, respectively. Link 803 can be an example of a 2.4 GHz link, and links 804-a and 804-b can be examples of 5 GHz links. STA 104 can also communicate with wearable device 204-a via link 806, which can be an example of a Bluetooth link. Wearable devices 204-a and 204-b can communicate with each other via link 808, which can be an example of a Bluetooth link. Links 804-a and 804-b can be examples of XPAN links, and XPAN topology 800 can be an example of a direct XPAN link.

[0145] As illustrated in XPAN topology 801, AP 102 can communicate with STA 104 via link 803, and AP 102 can communicate with wearable devices 204-a and 204-b via links 810-a and 810-b, respectively. Links 803, 810-a, and 810-b can be examples of 5GHz links. STA 104 can communicate with wearable device 204-a via link 806, which can be an example of a Bluetooth link. Wearable devices 204-a and 204-b can communicate with each other via link 808, which can also be an example of a Bluetooth link. In some implementations, wearable device 204-b may support mirroring technology and may attempt to "sniff" packets transmitted via link 806 via mirror link 812. Links 803, 810-a, and 810-b can be examples of XPAN links, and XPAN topology 801 can be an example of a standby XPAN infrastructure link.

[0146] As illustrated in XPAN topology 802, AP 102 can communicate with STA 104 via link 803, and AP 102 can communicate with wearable devices 204-a and 204-b via links 810-a and 810-b, respectively. Links 803, 810-a, and 810-b can be examples of 5GHz links. Wearable devices 204-a and 204-b can communicate with each other via link 808, which can be an example of a Bluetooth link. STA 104 may lack a direct link between STA 104 and the earpiece. Alternatively, AP 102 can control the system or relay packets and messages between the earpiece and STA 104. Links 803, 810-a, and 810-b can be examples of XPAN links, and XPAN topology 802 can be an example of XPAN infrastructure deployment.

[0147] Figure 9 Example XPAN topologies 900 and 901 are illustrated, supporting the use of shared addresses to manage a group of Wi-Fi-enabled wearable or handheld wireless devices according to some aspects of this disclosure. XPAN topologies 900 and 901 can be implemented or are implemented to implement or facilitate aspects of WLAN 100, signaling diagram 200, process flow 300, process flow 400, flowchart 500, communication timeline 600, or flowchart 700. For example, each of XPAN topologies 900 and 901 exemplifies an example deployment scenario of one or more STAs 104, one or more APs 102, wearable devices 204-a and 204-b.

[0148] As illustrated in the XPAN topology 900, AP 102 can communicate with STA 104-b via link 902, and AP 102 can communicate with wearable devices 204-a and 204-b via links 904-a and 904-b respectively. Links 902, 904-a, and 904-b can be examples of 5GHz links. STA 104-a can communicate with wearable device 204-a via link 906, which can be an example of a Bluetooth link. Wearable devices 204-a and 204-b can communicate with each other via link 908, which can also be an example of a Bluetooth link. In some implementations, wearable device 204-b may support mirroring technology and may attempt to "sniff" packets transmitted via link 806 via mirror link 910. Links 902, 904-a, and 904-b can be examples of XPAN links, and XPAN topology 900 can be an example of a Bluetooth + XPAN (infrastructure) dual-link.

[0149] As shown in XPAN topology 901, AP 102 may lack connectivity to other devices. In such an example, STA 104-a can communicate with wearable device 204-a via link 906, and wearable devices 204-a and 204-b can communicate with each other via link 908, with each of links 906 and 908 being an example of a Bluetooth link. In some implementations, wearable device 204-b may support mirroring technology and may attempt to "sniff" packets transmitted via link 806 via mirror link 910. STA 104-b can communicate with wearable devices 204-a and 204-b respectively via links 912-a and 912-b. Links 912-a and 912-b may be examples of 5GHz links. Links 912-a and 912-b may be examples of XPAN links, and XPAN topology 901 may be an example of a Bluetooth + XPAN (direct) dual-link setup.

[0150] Figure 10 Example XPAN topologies 1000 and 1001 are illustrated, supporting the use of shared addresses to manage a group of Wi-Fi-enabled wearable or handheld wireless devices according to some aspects of this disclosure. XPAN topologies 1000 and 1001 can be implemented or are implemented to implement or facilitate aspects of WLAN 100, signaling diagram 200, process flow 300, process flow 400, flowchart 500, communication timeline 600, or flowchart 700. For example, each of XPAN topologies 1000 and 1001 illustrates an example deployment scenario of one or more STAs 104, one or more APs 102, wearable devices 204-a and 204-b.

[0151] As illustrated in XPAN topology 1000, AP 102 can communicate with STA 104-b via link 1002, and with STA 104-a via link 1004. Links 1002 and 1004 can be examples of 5GHz links. AP 102 can also communicate with wearable devices 204-a and 204-b via links 1006-a and 1006-b, respectively. Links 1006-a and 1006-b can be examples of 5GHz links. Wearable devices 204-a and 204-b can communicate with each other via link 1008, which can be an example of a Bluetooth link. Links 1002, 1004, 1006-a, and 1006-b can be examples of XPAN links, and XPAN topology 1000 can be an example of XPAN+XPAN dual-link architecture.

[0152] As illustrated in XPAN topology 1001, AP 102 can communicate with STA 104-b via link 1002, and with STA 104-a via link 1004. Links 1002 and 1004 can be examples of 5GHz links. STA 104-a can communicate with wearable devices 204-a and 204-b via links 1010-a and 1010-b, respectively. Links 1010-a and 1010-b can be examples of 5GHz links. Wearable devices 204-a and 204-b can communicate with each other via link 1008, which can be an example of a Bluetooth link. Links 1002, 1004, 1010-a, and 1010-b can be examples of XPAN links, and XPAN topology 1001 can be an example of XPAN direct dual-link architecture.

[0153] Figure 11 A block diagram of an example wireless communication device is shown that supports the use of a shared address to manage a group of Wi-Fi-enabled wearable or handheld wireless devices. 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 a 3GPP 4G LTE or 5G compatible modem)); one or more processors, processing blocks, or processing elements (collectively, “at least one processor”); one or more radio components (collectively, “at least one radio component”); and one or more memories or memory blocks (collectively, “at least one memory”). In some specific implementations, at least one processor may include multiple processors, and at least one memory may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (as part of a processing system).

[0154] In some specific implementations, the wireless communication device may be provided in a STA or wearable device (such as a reference). Figure 1 The STA 104 described or as referenced Figure 2The device described is used by one or both of the wearable devices 204-a and 204-b. In some aspects, STA 104 may be an example of a wearable device. In some other examples, the wireless communication device may be an STA including such a chip, SoC, chipset, package, or device, and multiple antennas. The wireless communication device is capable of transmitting and receiving wireless communications, for example, in the form of wireless packets. For example, the wireless communication device may be configured or capable of operating to transmit and receive packets in the form of physical layer PPDUs and MPDUs conforming to one or more of the IEEE 802.11 wireless communication protocol family of standards. In some embodiments, the wireless communication device also includes at least one application processor or may be coupled to at least one application processor, which may be further coupled to at least one memory. In some embodiments, the wireless communication device also includes a user interface (UI) (such as a touchscreen or keypad) and a display that may be integrated with the UI to form a touchscreen display. In some embodiments, the wireless communication device may also include one or more sensors, such as, for example, one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors.

[0155] The wireless communication device includes a peer-to-peer communication component 1105, a connection establishment component 1110, and a link ID-based communication component 1115. A portion of one or more of the peer-to-peer communication component 1105, the connection establishment component 1110, and the link ID-based communication component 1115 may be implemented at least partially in hardware or firmware. For example, one or more of the peer-to-peer communication component 1105, the connection establishment component 1110, and the link ID-based communication component 1115 may be implemented at least partially by at least one modem. In some embodiments, at least some of the peer-to-peer communication component 1105, the connection establishment component 1110, and the link ID-based communication component 1115 are implemented at least partially by at least one processor and are implemented as software stored in at least one memory. For example, a portion of one or more of the peer-to-peer communication component 1105, the connection establishment component 1110, and the link ID-based communication component 1115 may be implemented as non-transitory instructions (or "code") executable by at least one processor to perform the function or operation of the corresponding module.

[0156] In some implementations, at least one processor may be a component of a processing system. A processing system generally refers to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs that can be passed to other systems or, for example, components of a wireless communication device. For example, a processing system for a wireless communication device may refer to a system that includes various other components or sub-components of the wireless communication device, such as 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 a wireless communication device may interface with other components of the wireless communication device and may process information (such as inputs or signals) received from other components or output such information to other components. For example, a chip or modem of a wireless communication device may include a processing system, a first interface for outputting information, and a second interface for receiving information. In some implementations, the first interface may refer to the interface between the processing system of the chip or modem and a transmitter, allowing the wireless communication device to transmit information output from the chip or modem. In some implementations, the second interface may refer to the interface between the processing system of the chip or modem and a receiver, allowing the wireless communication device to receive information or signal input, and such information can be passed to the processing system. Those skilled in the art will readily recognize that the first interface can also receive information or signal input, and the second interface can also output information or signal output.

[0157] The wireless communication device can support wireless communication at a first wearable or handheld wireless device according to the examples disclosed herein. Peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: transmitting one or more first packets via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with a shared address corresponding to an association between the wearable or handheld wireless device and at least the first and second wearable or handheld wireless devices, and 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 associated with the shared address. Connection establishment component 1110 is capable of, configured to, or operable to support components for performing the following operations: transmitting one or more second packets indicating the shared address, the first link identifier, and the second link identifier in association with establishing a second wireless communication link with the wireless communication device. The link ID-based communication component 1115 is capable of, configured to perform, or operable to support components for performing the following operations: receiving one or more third packets associated with a first link identifier from a wireless communication device via a second wireless communication link.

[0158] In some specific implementations, in order to support the transmission of one or more first packets with at least a second wearable or handheld wireless device via a first wireless communication link, the peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: sending one or more first packets to the second wearable or handheld wireless device and receiving one or more first packets from the second wearable or handheld wireless device, based on negotiation of a shared address with the second wearable or handheld wireless device.

[0159] In some specific implementations, in order to support the transmission of one or more first packets with at least a second wearable or handheld wireless device via a first wireless communication link, the peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: sending one or more of the first packets to the second wearable or handheld wireless device and receiving one or more of the first packets from the second wearable or handheld wireless device, based on the assignment of a first link identifier to the first wearable or handheld wireless device and a second link identifier to the second wearable or handheld wireless device.

[0160] In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: sending a fourth packet to the wireless communication device associated with the 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 a first link identifier. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: sending one or more block acknowledgments associated with one or more third packets to the wireless communication device.

[0161] In some specific implementations, the link ID-based communication component 1115 is capable of, configured to perform, or operable to support components for performing the following operations: sending a fourth packet to the wireless communication device indicating a shared address and a power management state corresponding to the shared address.

[0162] In some implementations, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: receiving a fifth packet from a second wearable or handheld wireless device via a first wireless communication link, indicating that the second wearable or handheld wireless device is in a power management state, wherein sending a fourth packet indicating the power management state is associated with receiving the fifth packet.

[0163] In some implementations, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: transmitting one or more fourth packets via a first wireless communication link to at least a second wearable or handheld wireless device based on negotiation of one or more of the following: and one or more security keys, Dynamic Host Configuration Protocol addresses, or one or more Address Resolution Protocol tables associated with communication with the wireless communication device, wherein the first wearable or handheld wireless device establishes the second wireless communication link based on the negotiation.

[0164] In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving information from the wireless communication device indicating a scheduling of a communication time interval corresponding to a first link identifier. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: monitoring a second wireless communication link according to the scheduling of the communication time interval, wherein receiving one or more third packets is associated with monitoring the second wireless communication link.

[0165] In some embodiments, each of the one or more third packets includes a corresponding frame header indicating a first link identifier, and the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: decoding the data portion of the one or more third packets based on the first link identifier indicated by the frame header of the one or more third packets. In some embodiments, each of the one or more third packets includes a corresponding frame header indicating a first link identifier, and the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving one or more fourth packets, each including a corresponding frame header indicating a second link identifier. In some embodiments, each of the one or more third packets includes a corresponding frame header indicating a first link identifier, and the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: avoiding decoding the data portion of the one or more fourth packets by indicating a second link identifier based on the frame header of the one or more fourth packets.

[0166] In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving information from a wireless communication device indicating a first mapping from a first link identifier to a second wireless communication link and a second mapping from a second link identifier to a third wireless communication link. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: tuning at least one radio component to the second wireless communication link according to the first mapping, wherein receiving one or more third packets is associated with tuning at least one radio component to the second wireless communication link, and wherein 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 from the first frequency channel.

[0167] In some implementations, the connection establishment component 1110 is capable of, configured to, or operable to support components for performing the following operations: receiving an instruction from the wireless communication device that it can perform quality-of-service (QoS) based traffic flow prioritization. In some implementations, the connection establishment component 1110 is capable of, configured to, or operable to support components for performing the following operations: establishing a second wireless communication link with the wireless communication device using a shared address, based on the wireless communication device's ability to perform QoS based traffic flow prioritization.

[0168] In some specific implementations, in order to support the receiving wireless communication device in performing service flow prioritization based on quality of service, the connection establishment component 1110 is capable of, configured to perform, or operable to support the component for performing the following operation: receiving identification information of the wireless communication device, wherein the identification information indicates that the wireless communication device exists in a first device list that allows the use of shared addresses and does not exist in a second device list that does not allow the use of shared addresses.

[0169] In some implementations, the presence of identification information for a wireless communication device in a first device list or a second device list indicates a previous quality of service (QoS) compliance test for the wireless communication device. In some implementations, presence in the first device list indicates a successful QoS compliance test, and presence in the second device list indicates an unsuccessful QoS compliance test.

[0170] In some specific implementations, in order to support the receiving wireless communication device being able to perform quality-of-service (QoS) based traffic flow prioritization, the connection establishment component 1110 is capable of, configured to perform, or operable to support the component for performing the following operation: receiving packets indicating that QoS-based traffic flow prioritization is possible on an end-to-end path between a traffic source device and a first wearable or handheld wireless device, wherein the wireless communication device is the traffic source device or another wireless communication device along the end-to-end path.

[0171] In some implementations, the peer-to-peer communication component 1105 is capable of, configured to perform, or operable to support components for performing the following operations: conveying information relating to one or more link quality metrics to a second wearable or handheld wireless device via a first wireless communication link, relating to a first communication between the first wearable or handheld wireless device and the wireless communication device, and a second communication between the second wearable or handheld wireless device and the wireless communication device.

[0172] In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication that a link quality metric related to a second communication between a second wearable or handheld wireless device and a wireless communication device has failed to meet a condition. In some embodiments, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving one or more fourth packets including a second link identifier based on a link quality metric failure to meet a condition. In some embodiments, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: transmitting data received via one or more fourth packets to a second wearable or handheld wireless device via a first wireless communication link based on one or more fourth packets including a second link identifier.

[0173] In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: receiving data-associated feedback information from a second wearable or handheld wireless device via a first wireless communication link. In some embodiments, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: sending one or more block acknowledgments associated with one or more fourth packets to the wireless communication device, the one or more block acknowledgments indicating feedback information received from the second wearable or handheld wireless device.

[0174] In some implementations, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication that a link quality metric is satisfied in relation to a second communication between a second wearable or handheld wireless device and a wireless communication device. In some implementations, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: avoiding decoding any packet including a second link identifier based on a link quality metric satisfaction condition, wherein the first wearable or handheld wireless device temporarily receives one or more fourth packets including the second link identifier when the link quality metric fails to satisfy the condition.

[0175] In some specific implementations, the link ID-based communication component 1115 is capable of, configured to perform, or operable to support components for performing the following operations: sending information indicating a recommended decoding rate to the wireless communication device based on the failure of a link quality metric to meet a condition.

[0176] In some specific implementations, the recommended decoding rate is used for both the first communication between a first wearable or handheld wireless device and a wireless communication device, and the second communication between a second wearable or handheld wireless device and a wireless communication device.

[0177] In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: transmitting an indication that a link quality metric related to a first communication between a first wearable or handheld wireless device and a wireless communication device has failed to meet a condition. In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: receiving data from a second wearable or handheld wireless device via a first wireless communication link based on the link quality metric failing to meet a condition. In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: sending data-related feedback information to the second wearable or handheld wireless device via the first wireless communication link.

[0178] In some implementations, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: transmitting an indication that a link quality metric related to a first communication between a first wearable or handheld wireless device and a wireless communication device meets a condition. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving packets including a first link identifier via a second wireless communication link based on a link quality metric meeting condition, wherein reception of any packet via the second wireless communication link is temporarily suspended if the link quality metric fails to meet the condition.

[0179] In some embodiments, the connection establishment component 1110 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication of handover of a first wearable or handheld wireless device from a wireless communication device to a second wireless communication device. In some embodiments, the connection establishment component 1110 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication that the second wireless communication device is unable to perform quality-of-service (QoS) based traffic flow prioritization. In some embodiments, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: in association with establishing a third wireless communication link with the second wireless communication device, transmitting one or more fourth packets indicating a device-specific address, wherein the third wireless communication link is exclusively used for the first wearable or handheld wireless device based on the device-specific address indicated by the one or more fourth packets.

[0180] In some specific implementations, the first link identifier and the second link identifier are associated with the same channel access category.

[0181] In some implementations, one or more third packets include an indication of a first type of service for a first wearable or handheld wireless device, which is mapped to a first link identifier.

[0182] In some implementations, one or more second groups include one or more of the following: authentication frames, association frames, address resolution protocol frames, dynamic host configuration protocol frames, Scalable Authentication Protocol (LAN) frames, key handshake frames, and add block acknowledgment frames.

[0183] In some implementations, one or more first packets are transmitted to the second wearable or handheld wireless device to instruct the second wearable or handheld wireless device to avoid establishing a wireless communication link with the wireless communication device separately.

[0184] In some specific 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.

[0185] In some specific implementations, wireless communication equipment is a service source device, an access point, or a computing device.

[0186] Additionally or alternatively, the wireless communication device may support wireless communication at a first wearable or handheld wireless device according to examples disclosed herein. In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: transmitting one or more first packets via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with a shared address corresponding to an association between a wearable or handheld wireless device that includes at least the first and second wearable or handheld wireless devices, and 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 associated with the shared address. In some embodiments, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving one or more second packets associated with the first link identifier from the wireless communication device via a second wireless communication link associated with the establishment using the shared address.

[0187] In some specific implementations, in order to support the transmission of one or more first packets with at least a second wearable or handheld wireless device via a first wireless communication link, the peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: sending one or more first packets to the second wearable or handheld wireless device and receiving one or more first packets from the second wearable or handheld wireless device, based on negotiation of a shared address with the second wearable or handheld wireless device.

[0188] In some specific implementations, in order to support the transmission of one or more first packets with at least a second wearable or handheld wireless device via a first wireless communication link, the peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: sending one or more of the first packets to the second wearable or handheld wireless device and receiving one or more of the first packets from the second wearable or handheld wireless device, based on the assignment of a first link identifier to the first wearable or handheld wireless device and a second link identifier to the second wearable or handheld wireless device.

[0189] In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: sending a third packet to the wireless communication device associated with the 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 a first link identifier. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: sending one or more block acknowledgments associated with one or more second packets to the wireless communication device.

[0190] In some implementations, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: communicating one or more third packets via a first wireless communication link to at least a second wearable or handheld wireless device based on negotiation of one or more of the following: and one or more security keys, Dynamic Host Configuration Protocol addresses, or one or more Address Resolution Protocol tables associated with communication with the wireless communication device, wherein the second wearable or handheld wireless device establishes the second wireless communication link according to the negotiation.

[0191] In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving information from the wireless communication device indicating a scheduling of a communication time interval corresponding to a first link identifier. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: monitoring a second wireless communication link according to the scheduling of the communication time interval, wherein receiving one or more second packets is associated with monitoring the second wireless communication link.

[0192] In some embodiments, each of the one or more second packets includes a corresponding frame header indicating a first link identifier, and the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: decoding the data portion of one or more second packets based on the first link identifier indicated by the frame header of the one or more second packets. In some embodiments, each of the one or more second packets includes a corresponding frame header indicating a first link identifier, and the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving one or more third packets, each including a corresponding frame header indicating a second link identifier. In some embodiments, each of the one or more second packets includes a corresponding frame header indicating a first link identifier, and the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: avoiding decoding the data portion of one or more third packets by indicating a second link identifier based on the frame header of the one or more third packets.

[0193] In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving information from a wireless communication device indicating a first mapping from a first link identifier to a second wireless communication link and a second mapping from a second link identifier to a third link. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: tuning at least one radio component to a second wireless communication link according to the first mapping, wherein receiving one or more second packets is associated with tuning at least one radio component to the second wireless communication link, and wherein the second wireless communication link is associated with a first frequency channel, and the third link is associated with a second frequency channel different from the first frequency channel.

[0194] In some implementations, the peer-to-peer communication component 1105 is capable of, configured to perform, or operable to support components for performing the following operations: conveying information relating to one or more link quality metrics to a second wearable or handheld wireless device via a first wireless communication link, relating to a first communication between the first wearable or handheld wireless device and the wireless communication device, and a second communication between the second wearable or handheld wireless device and the wireless communication device.

[0195] In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication that a link quality metric related to a second communication between a second wearable or handheld wireless device and a wireless communication device has failed to meet a condition. In some embodiments, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving one or more third packets including a second link identifier based on a link quality metric failure to meet a condition. In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: transmitting data received via one or more third packets to a second wearable or handheld wireless device via a first wireless communication link based on one or more third packets including a second link identifier.

[0196] In some implementations, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: receiving feedback information associated with data from a second wearable or handheld wireless device via a first wireless communication link. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: sending one or more block acknowledgments associated with one or more third packets to the wireless communication device, the one or more block acknowledgments indicating feedback information received from the second wearable or handheld wireless device.

[0197] In some implementations, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication that a link quality metric is satisfied in relation to a second communication between a second wearable or handheld wireless device and a wireless communication device. In some implementations, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: avoiding decoding any packets including a second link identifier based on a link quality metric satisfaction condition, wherein the first wearable or handheld wireless device temporarily receives one or more third packets including the second link identifier when the link quality metric fails to satisfy the condition.

[0198] In some specific implementations, the link ID-based communication component 1115 is capable of, configured to perform, or operable to support components for performing the following operations: sending information indicating a recommended decoding rate to the wireless communication device based on the failure of a link quality metric to meet a condition.

[0199] In some specific implementations, the recommended decoding rate is used for both the first communication between a first wearable or handheld wireless device and a wireless communication device, and the second communication between a second wearable or handheld wireless device and a wireless communication device.

[0200] In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: transmitting an indication that a link quality metric related to a first communication between a first wearable or handheld wireless device and a wireless communication device has failed to meet a condition. In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: receiving data from a second wearable or handheld wireless device via a first wireless communication link based on the link quality metric failing to meet a condition. In some embodiments, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: sending data-related feedback information to the second wearable or handheld wireless device via the first wireless communication link.

[0201] In some implementations, the peer-to-peer communication component 1105 is capable of, configured to, or operable to support components for performing the following operations: transmitting an indication that a link quality metric related to a first communication between a first wearable or handheld wireless device and a wireless communication device meets a condition. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving packets including a first link identifier via a second wireless communication link based on a link quality metric meeting condition, wherein reception of any packet via the second wireless communication link is temporarily suspended if the link quality metric fails to meet the condition.

[0202] In some embodiments, the connection establishment component 1110 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication of a handover of association between a wearable or handheld wireless device, including at least a first wearable or handheld wireless device and a second wearable or handheld wireless device, from a wireless communication device to a second wireless communication device. In some embodiments, the connection establishment component 1110 is capable of, configured to, or operable to support components for performing the following operations: receiving an indication that the second wireless communication device is unable to perform quality-of-service (QoS) based traffic flow prioritization. In some embodiments, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: in association with establishing a third wireless communication link with the second wireless communication device, transmitting one or more third packets indicating a device-specific address, wherein the third wireless communication link is exclusively used for the first wearable or handheld wireless device based on the one or more third packets indicating the device-specific address.

[0203] In some specific implementations, the first link identifier and the second link identifier are associated with the same channel access category.

[0204] In some implementations, one or more second groups include an indication of a first type of service for a first wearable or handheld wireless device, the first type of service being mapped to a first link identifier.

[0205] In some implementations, one or more first packets are transmitted to the first wearable or handheld wireless device to instruct it to avoid establishing a wireless communication link with the wireless communication device separately.

[0206] In some specific 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.

[0207] In some specific implementations, wireless communication equipment is a service source device, an access point, or a computing device.

[0208] Additionally or alternatively, the wireless communication device may support wireless communication at the wireless communication device according to the examples disclosed herein. In some embodiments, the connection establishment component 1110 is capable of, configured to, or operable to support components for performing the following operations: receiving one or more first packets associated with establishing a wireless communication link with a first wearable or handheld wireless device, the one or more first packets indicating a shared address corresponding to an association of at least the first and second wearable or handheld wireless devices, 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 embodiments, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: transmitting one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier based on the shared address.

[0209] In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving a first indication of a first link identifier via a first packet associated with the first establishment of a first block confirmation session between the wireless communication device and a first wearable or handheld wireless device. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: receiving a second indication of a second link identifier via a second packet associated with the second establishment of a second block confirmation session between the wireless communication device and a second wearable or handheld wireless device.

[0210] In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: transmitting first information indicating a first schedule for a first communication time interval corresponding to a first link identifier, wherein transmitting one or more second packets associated with the first link identifier is associated with the first schedule for the first communication time interval. In some implementations, the link ID-based communication component 1115 is capable of, configured to, or operable to support components for performing the following operations: transmitting second information indicating a second schedule for a second communication time interval corresponding to a second link identifier, wherein transmitting one or more third packets associated with the second link identifier is associated with the second schedule for the second communication time interval.

[0211] In some specific implementations, the link ID-based communication component 1115 is capable of, configured to perform, or operable to support components for performing the following operations: receiving packets from a first wearable or handheld wireless device indicating a shared address and a power management state corresponding to the shared address, wherein one or more second packets and one or more third packets are associated with the power management state.

[0212] In some specific implementations, the link ID-based communication component 1115 is capable of, configured to perform, or operable to support components for performing the following operations: transmitting information indicating a first mapping from a first link identifier to a first wireless communication link and a second mapping from a second link identifier to a second wireless communication link, wherein 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 from the first frequency channel.

[0213] In some specific implementations, in order to support the transmission of one or more second packets and one or more third packets, the link ID-based communication component 1115 is capable of, configured to perform, or operable to support components for performing the following operations: transmitting one or more second packets via a first wireless communication link in a first communication time interval and transmitting one or more third packets via a second wireless communication link in a second communication time interval, wherein the first and second communication time intervals overlap at least partially in time.

[0214] In some embodiments, the connection establishment component 1110 is capable of, configured to, or operable to support components for performing the following operations: transmitting an indication to a first wearable or handheld wireless device that the wireless communication device is capable of quality-of-service (QoS)-based traffic flow prioritization. In some embodiments, the connection establishment component 1110 is capable of, configured to, or operable to support components for performing the following operations: establishing a wireless communication link using a shared address based on the wireless communication device's capability for QoS-based traffic flow prioritization.

[0215] In some specific implementations, in order to support the transmitting wireless communication device in making indications of service flow prioritization based on quality of service, the connection establishment component 1110 is capable of, configured to perform, or operable to support components for performing the following operations: transmitting identification information of the wireless communication device, wherein the identification information indicates that the wireless communication device exists in a first device list that allows the use of shared addresses and does not exist in a second device list that does not allow the use of shared addresses.

[0216] In some implementations, the presence of identification information for a wireless communication device in a first device list or a second device list indicates a previous quality of service (QoS) compliance test for the wireless communication device. In some implementations, presence in the first device list indicates a successful QoS compliance test, and presence in the second device list indicates an unsuccessful QoS compliance test.

[0217] In some specific implementations, in order to support the transmission of instructions by wireless communication devices to perform quality-of-service (QoS)-based traffic flow prioritization, the connection establishment component 1110 is capable of, configured to perform, or operable to support components for performing the following operations: transmitting packets indicating that the end-to-end path between the traffic source device and the first wearable or handheld wireless device is capable of QoS-based traffic flow prioritization, wherein the wireless communication device is the traffic source device or another wireless communication device along the end-to-end path.

[0218] In some specific implementations, the first link identifier and the second link identifier are associated with the same channel access category.

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

[0220] In some implementations, each of one or more second groups includes first information specific to the first wearable or handheld wireless device, and each of one or more third groups includes second information specific to the second wearable or handheld wireless device.

[0221] In some implementations, each of one or more second groups and one or more third groups includes both first information specific to the first wearable or handheld wireless device and second information specific to the second wearable or handheld wireless device.

[0222] In some implementations, one or more first groups include one or more of the following: authentication frames, association frames, address resolution protocol frames, dynamic host configuration protocol frames, Scalable Authentication Protocol (LAN) frames, key handshake frames, and add block acknowledgment frames.

[0223] In some specific implementations, wireless communication equipment is the service source equipment.

[0224] Figure 12A block diagram of an example wireless communication device is shown that supports the use of a shared address to manage a group of Wi-Fi-enabled wearable or handheld wireless devices. 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 a 3GPP 4G LTE or 5G compatible modem)); one or more processors, processing blocks, or processing elements (collectively, “at least one processor”); one or more radio components (collectively, “at least one radio component”); and one or more memories or memory blocks (collectively, “at least one memory”). In some specific implementations, at least one processor may include multiple processors, and at least one memory may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (as part of a processing system).

[0225] In some specific implementations, the wireless communication device can be a device used in an AP, STA, or any other device that can act as a service source / sink device (such as references). Figure 1 The described AP 102 or STA 104, or as referenced Figure 2 The described wireless communication device 202. In some other examples, the wireless communication device may be an AP including such a chip, SoC, chipset, package, or device, and multiple antennas. The wireless communication device is capable of transmitting and receiving wireless communications, for example, in the form of wireless packets. For example, the wireless communication device may be configured or be able to operate to transmit and receive packets in the form of physical layer PPDUs and MPDUs conforming to one or more of the IEEE 802.11 wireless communication protocol standard family. In some embodiments, the wireless communication device also includes at least one application processor or may be coupled to at least one application processor, which may be further coupled to at least one memory. In some embodiments, the wireless communication device also includes at least one external network interface that enables communication with a core network or backhaul network to obtain access to external networks, including the Internet.

[0226] The wireless communication device includes a connection establishment component 1205 and a link ID-based communication component 1210. A portion of one or more of the connection establishment component 1205 and the link ID-based communication component 1210 may be implemented at least partially in hardware or firmware. For example, one or more of the connection establishment component 1205 and the link ID-based communication component 1210 may be implemented at least partially by at least one modem. In some embodiments, at least some of the connection establishment component 1205 and the link ID-based communication component 1210 are implemented at least partially by at least one processor and are implemented as software stored in at least one memory. For example, a portion of one or more of the connection establishment component 1205 and the link ID-based communication component 1210 may be implemented as non-transitory instructions (or "code") executable by at least one processor to perform the function or operation of the corresponding module.

[0227] In some implementations, at least one processor may be a component of a processing system. A processing system generally refers to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs that can be passed to other systems or, for example, components of a wireless communication device. For example, a processing system for a wireless communication device may refer to a system that includes various other components or sub-components of the wireless communication device, such as 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 a wireless communication device may interface with other components of the wireless communication device and may process information (such as inputs or signals) received from other components or output such information to other components. For example, a chip or modem of a wireless communication device may include a processing system, a first interface for outputting information, and a second interface for receiving information. In some implementations, the first interface may refer to the interface between the processing system of the chip or modem and a transmitter, allowing the wireless communication device to transmit information output from the chip or modem. In some implementations, the second interface may refer to the interface between the processing system of the chip or modem and a receiver, allowing the wireless communication device to receive information or signal input, and such information can be passed to the processing system. Those skilled in the art will readily recognize that the first interface can also receive information or signal input, and the second interface can also output information or signal output.

[0228] The wireless communication device can support wireless communication at the wireless communication device according to the examples disclosed herein. Connection establishment component 1205 is capable of, configured to, or operable to support components for performing the following operations: receiving one or more first packets associated with establishing a wireless communication link with a first wearable or handheld wireless device, the one or more first packets indicating a shared address corresponding to an association of at least the first and second wearable or handheld wireless devices, 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. Link ID-based communication component 1210 is capable of, configured to, or operable to support components for performing the following operations: transmitting one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier based on the shared address.

[0229] In some implementations, the link ID-based communication component 1210 is capable of, configured to, or operable to support components for performing the following operations: receiving a first indication of a first link identifier via a first packet associated with the first establishment of a first block confirmation session between the wireless communication device and a first wearable or handheld wireless device. In some implementations, the link ID-based communication component 1210 is capable of, configured to, or operable to support components for performing the following operations: receiving a second indication of a second link identifier via a second packet associated with the second establishment of a second block confirmation session between the wireless communication device and a second wearable or handheld wireless device.

[0230] In some implementations, the link ID-based communication component 1210 is capable of, configured to, or operable to support components for performing the following operations: transmitting first information indicating a first schedule for a first communication time interval corresponding to a first link identifier, wherein one or more second packets associated with the first link identifier are associated with the first schedule for the first communication time interval. In some implementations, the link ID-based communication component 1210 is capable of, configured to, or operable to support components for performing the following operations: transmitting second information indicating a second schedule for a second communication time interval corresponding to a second link identifier, wherein one or more third packets associated with the second link identifier are associated with the second schedule for the second communication time interval.

[0231] In some specific implementations, the link ID-based communication component 1210 is capable of, configured to perform, or operable to support components for performing the following operations: receiving packets from a first wearable or handheld wireless device indicating a shared address and a power management state corresponding to the shared address, wherein one or more second packets and one or more third packets are associated with the power management state.

[0232] In some specific implementations, the link ID-based communication component 1210 is capable of, configured to perform, or operable to support components for performing the following operations: transmitting information indicating a first mapping from a first link identifier to a first wireless communication link and a second mapping from a second link identifier to a second wireless communication link, wherein 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 from the first frequency channel.

[0233] In some specific implementations, in order to support the transmission of one or more second packets and one or more third packets, the link ID-based communication component 1210 is capable of, configured to perform, or operable to support components for performing the following operations: transmitting one or more second packets via a first wireless communication link in a first communication time interval and transmitting one or more third packets via a second wireless communication link in a second communication time interval, wherein the first and second communication time intervals overlap at least partially in time.

[0234] In some implementations, the connection establishment component 1205 is capable of, configured to, or operable to support components for performing the following operations: transmitting an indication to a first wearable or handheld wireless device that the wireless communication device is capable of quality-of-service (QoS)-based traffic flow prioritization. In some implementations, the connection establishment component 1205 is capable of, configured to, or operable to support components for performing the following operations: establishing a wireless communication link using a shared address based on the wireless communication device's ability to perform QoS-based traffic flow prioritization.

[0235] In some specific implementations, in order to support the transmitting wireless communication device in making indications of service flow prioritization based on quality of service, the connection establishment component 1205 can perform, is configured to perform, or is operable to support components for performing the following operations: transmitting identification information of the wireless communication device, wherein the identification information indicates that the wireless communication device exists in a first device list that allows the use of shared addresses and does not exist in a second device list that does not allow the use of shared addresses.

[0236] In some implementations, the presence of identification information for a wireless communication device in a first device list or a second device list indicates a previous quality of service (QoS) compliance test for the wireless communication device. In some implementations, presence in the first device list indicates a successful QoS compliance test, and presence in the second device list indicates an unsuccessful QoS compliance test.

[0237] In some specific implementations, in order to support the transmission of instructions by wireless communication devices to perform quality-of-service (QoS)-based traffic flow prioritization, the connection establishment component 1205 is capable of, configured to perform, or operable to support components for performing the following operations: transmitting packets indicating that an end-to-end path between a traffic source device and a first wearable or handheld wireless device is capable of QoS-based traffic flow prioritization, wherein the wireless communication device is either the traffic source device or another wireless communication device along the end-to-end path.

[0238] In some specific implementations, the first link identifier and the second link identifier are associated with the same channel access category.

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

[0240] In some implementations, each of one or more second groups includes first information specific to the first wearable or handheld wireless device, and each of one or more third groups includes second information specific to the second wearable or handheld wireless device.

[0241] In some implementations, each of one or more second groups and one or more third groups includes both first information specific to the first wearable or handheld wireless device and second information specific to the second wearable or handheld wireless device.

[0242] In some implementations, one or more first groups include one or more of the following: authentication frames, association frames, address resolution protocol frames, dynamic host configuration protocol frames, Scalable Authentication Protocol (LAN) frames, key handshake frames, and add block acknowledgment frames.

[0243] In some specific implementations, wireless communication equipment is the service source equipment.

[0244] Figure 13A flowchart illustrating an example process 1300 for managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address, according to some aspects of this disclosure, is shown. The operation of process 1300 can be an example of a method implemented by a wearable device or a component thereof. For example, process 1300 can be performed by a wireless communication device (such as reference _____) operating as a wireless STA or within a wireless STA. Figure 11 The process 1300 may be performed by a wireless STA (such as the described wireless communication device). In some specific implementations, process 1300 may be performed by a wireless STA (such as the reference STA). Figure 1 The STA described in STA 104 is used to perform this action.

[0245] In some implementations, in block 1305, a wireless STA may communicate one or more first packets via a first wireless communication link to at least a second wearable or handheld wireless device. These one or more first packets are associated with a shared address corresponding to an association between a wearable or handheld wireless device and at least a first wearable or handheld wireless device and a second wearable or handheld wireless device, and with the shared address associated with 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. Operation of block 1305 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1305 may be provided by reference to [reference needed]. Figure 11 The described peer-to-peer communication component 1105 is used to perform this.

[0246] In some implementations, in block 1310, the wireless STA may transmit one or more second packets indicating a shared address, a first link identifier, and a second link identifier in association with establishing a second wireless communication link with the wireless communication device. Operation of block 1310 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1310 may be provided by reference to [reference needed]. Figure 11 The described connection establishment component 1110 is used to perform this.

[0247] In some implementations, in block 1315, the wireless STA may receive one or more third packets associated with a first link identifier from the wireless communication device via a second wireless communication link. Operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be provided by reference to... Figure 11 The described link ID-based communication component 1115 is used to perform this.

[0248] Figure 14A flowchart illustrating an example process 1400 for managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address, according to some aspects of this disclosure, is shown. The operation of process 1400 can be an example of a method implemented by a wearable device or a component thereof. For example, process 1400 can be performed by a wireless communication device (such as reference _____) operating as a wireless STA or within a wireless STA. Figure 11 The process 1400 may be performed by a wireless STA (such as the described wireless communication device). In some specific implementations, process 1400 may be performed by a wireless STA (such as the reference STA). Figure 1 The STA described in STA 104 is used to perform this action.

[0249] In some implementations, in block 1405, a wireless STA may communicate one or more first packets via a first wireless communication link to at least a second wearable or handheld wireless device. These one or more first packets are associated with a shared address corresponding to an association between a wearable or handheld wireless device and at least a first wearable or handheld wireless device and a second wearable or handheld wireless device, and a first link identifier associated with the shared address corresponding to the first wearable or handheld wireless device and a second link identifier associated with the second wearable or handheld wireless device. Operation of block 1405 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1405 may be provided by reference to [reference needed]. Figure 11 The described peer-to-peer communication component 1105 is used to perform this.

[0250] In some implementations, in block 1410, the wireless STA may receive one or more second packets associated with a first link identifier from the wireless communication device via a second wireless communication link associated with the establishment of a shared address. Operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference needed]. Figure 11 The described link ID-based communication component 1115 is used to perform this.

[0251] Figure 15 A flowchart illustrating an example process 1500 for managing a group of Wi-Fi-enabled wearable or handheld wireless devices using a shared address, in accordance with one or more aspects of this disclosure. Operation of process 1500 may be implemented by a STA or AP or a component thereof. For example, operation of process 1500 may be implemented by, as referenced... Figure 12 The described service source / sink device is used to perform the functions. In some specific implementations, the STA or AP can execute a set of instructions to control the functional elements of the wireless STA or wireless AP to perform the described functions. Additionally or alternatively, the wireless STA or wireless AP may use dedicated hardware to perform aspects of the described functions.

[0252] In some implementations, in block 1505, a wireless STA or wireless AP may receive one or more first packets in association with establishing a wireless communication link with a first wearable or handheld wireless device. These one or more first packets indicate a shared address corresponding to an association between a wearable or handheld wireless device and at least a 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. Operation of block 1505 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1505 may be provided by reference to [reference needed]. Figure 12 The described connection establishment component 1205 is used to perform this.

[0253] In some implementations, in block 1510, a wireless STA or wireless AP may transmit one or more second packets associated with a first link identifier and one or more third packets associated with a second link identifier, based on a shared address. Operation of block 1510 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to [reference needed]. Figure 12 The described link ID-based communication component 1210 is used to perform this.

[0254] Specific implementation examples are described in the following numbered clauses:

[0255] Clause 1: A method for wireless communication at a first wearable or handheld wireless device, the method comprising: communicating one or more first packets to at least a second wearable or handheld wireless device via a first wireless communication link, the one or more first packets being associated with establishing a shared address corresponding to an association of at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and 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 associated with the shared address; transmitting one or more second packets indicating the shared address, the first link identifier and the second link identifier in association with establishing a second wireless communication link with the wireless communication device; and receiving one or more third packets associated with the first link identifier from the wireless communication device via the second wireless communication link.

[0256] Clause 2: The method according to Clause 1, wherein transmitting the one or more first packets via the first wireless communication link to at least the second wearable or handheld wireless device comprises: sending one or more of the one or more first packets to the second wearable or handheld wireless device according to an agreement with the second wearable or handheld wireless device on the shared address, and receiving one or more of the one or more first packets from the second wearable or handheld wireless device.

[0257] Clause 3: The method according to any one of Clauses 1 to 2, wherein transmitting the one or more first packets via the first wireless communication link to at least the second wearable or handheld wireless device comprises: sending one or more of the one or more first packets to the second wearable or handheld wireless device according to the 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, and receiving one or more of the one or more first packets from the second wearable or handheld wireless device.

[0258] Clause 4: The method according to any one of Clauses 1 to 3, the method further comprising: sending to the wireless communication device a fourth packet associated with the 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 sending to the wireless communication device one or more block acknowledgments associated with the one or more third packets.

[0259] Clause 5: The method according to any one of Clauses 1 to 4, the method further comprising: sending to the wireless communication device a fourth packet indicating the shared address and a power management state corresponding to the shared address.

[0260] Clause 6: The method according to Clause 5 further comprises: receiving, via the first wireless communication link, a fifth packet indicating that the second wearable or handheld wireless device is in the power management state, wherein sending the fourth packet indicating the power management state is associated with receiving the fifth packet.

[0261] Clause 7: The method according to any one of Clauses 1 to 6 further comprises: communicating one or more fourth packets via the first wireless communication link to at least the second wearable or handheld wireless device according to an agreement on one or more of the following: and one or more security keys, dynamic host configuration protocol addresses, or one or more address resolution protocol tables associated with communication with the wireless communication device, wherein the first wearable or handheld wireless device establishes the second wireless communication link according to the agreement.

[0262] Clause 8: The method according to any one of Clauses 1 to 7, the method further comprising: receiving from the wireless communication device information indicating a scheduling of a communication time interval corresponding to the first link identifier; and monitoring the second wireless communication link according to the scheduling of the communication time interval, wherein receiving the one or more third packets is associated with monitoring the second wireless communication link.

[0263] Clause 9: The method according to any one of Clauses 1 to 8, wherein each of the one or more third packets includes a corresponding frame header indicating the first link identifier, the method further comprising: decoding the data portion of the one or more third packets by indicating the first link identifier according to the frame header of the one or more third packets; receiving one or more fourth packets, each including a corresponding frame header indicating the second link identifier; and indicating the second link identifier according to the frame header of the one or more fourth packets to avoid decoding the data portion of the one or more fourth packets.

[0264] Clause 10: The method according to any one of Clauses 1 to 9, the method further comprising: receiving from the wireless communication device information indicating a first mapping from the first link identifier to the second wireless communication link and a second mapping from the second link identifier to a third wireless communication link; and tuning at least one radio component to the second wireless communication link according to the first mapping, wherein receiving the one or more third packets is associated with tuning the at least one radio component to the second wireless communication link, and wherein 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 from the first frequency channel.

[0265] Clause 11: The method according to any one of Clauses 1 to 10, the method further comprising: receiving an indication that the wireless communication device is capable of performing quality-of-service (QoS)-based traffic flow prioritization; and, based on the wireless communication device's capability to perform the QoS-based traffic flow prioritization, using the shared address to establish a second wireless communication link with the wireless communication device.

[0266] Clause 12: The method according to Clause 11, wherein receiving the indication that the wireless communication device is capable of performing the quality-of-service-based traffic prioritization comprises: receiving identification information of the wireless communication device, wherein the identification information indicates that the wireless communication device exists in a first list of devices allowed to use the shared address and does not exist in a second list of devices not allowed to use the shared address.

[0267] Clause 13: According to the method of Clause 12, the presence of the identification information of the wireless communication device in the first device list or the second device list indicates a previous quality of service compliance test for the wireless communication device, its presence in the first device list indicates a successful quality of service compliance test, and its presence in the second device list indicates an unsuccessful quality of service compliance test.

[0268] Clause 14: The method according to any one of Clauses 11 to 13, wherein receiving the indication that the wireless communication device is capable of performing the quality-of-service (QoS)-based traffic flow prioritization comprises: receiving a packet indicating that the end-to-end path between the service source device and the first wearable or handheld wireless device is capable of performing the QoS-based traffic flow prioritization, wherein the wireless communication device is the service source device or another wireless communication device along the end-to-end path.

[0269] Clause 15: The method according to any one of Clauses 1 to 14, the method further comprising: conveying information via the first wireless communication link to the second wearable or handheld wireless device information relating to a first communication between the first wearable or handheld wireless device and the wireless communication device and a second communication between the second wearable or handheld wireless device and the wireless communication device.

[0270] Clause 16: The method according to Clause 15 further comprises: receiving an indication that a link quality metric related to the second communication between the second wearable or handheld wireless device and the wireless communication device has failed to meet a condition; receiving one or more fourth packets including the second link identifier based on the failure of the link quality metric to meet the condition; and transmitting data received via the one or more fourth packets to the second wearable or handheld wireless device via the first wireless communication link based on the one or more fourth packets including the second link identifier.

[0271] Clause 17: The method according to Clause 16 further comprises: receiving feedback information associated with the data from the second wearable or handheld wireless device via the first wireless communication link; and sending one or more block acknowledgments associated with the one or more fourth packets to the wireless communication device, the one or more block acknowledgments indicating the feedback information received from the second wearable or handheld wireless device.

[0272] Clause 18: The method according to any one of Clauses 16 to 17, the method further comprising: receiving an indication that the link quality metric relating to the second communication between the second wearable or handheld wireless device and the wireless communication device satisfies the condition; and avoiding decoding any packet including the second link identifier based on the link quality metric satisfying the condition, wherein the first wearable or handheld wireless device temporarily receives the one or more fourth packets including the second link identifier when the link quality metric fails to satisfy the condition.

[0273] Clause 19: The method according to any one of Clauses 16 to 18, the method further comprising: sending information indicating a recommended decoding rate to the wireless communication device based on the failure of the link quality metric to meet the condition.

[0274] Clause 20: The method according to Clause 19, wherein the recommended decoding rate is used 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.

[0275] Clause 21: The method according to any one of Clauses 15 to 20, the method further comprising: sending an indication that a link quality metric related to the first communication between the first wearable or handheld wireless device and the wireless communication device has failed to meet a condition; receiving data from the second wearable or handheld wireless device via the first wireless communication link based on the failure of the link quality metric to meet the condition; and sending feedback information associated with the data to the second wearable or handheld wireless device via the first wireless communication link.

[0276] Clause 22: The method according to Clause 21 further includes: sending an indication that the link quality metric relating to the first communication between the first wearable or handheld wireless device and the wireless communication device satisfies the condition; and receiving a packet including the first link identifier via the second wireless communication link based on the link quality metric satisfying the condition, wherein reception of any packet via the second wireless communication link is temporarily suspended if the link quality metric fails to satisfy the condition.

[0277] Clause 23: The method according to any one of Clauses 1 to 22, the method further comprising: receiving an indication of handover of the first wearable or handheld wireless device from the wireless communication device to the second wireless communication device; receiving an indication that the second wireless communication device is unable to perform quality-of-service-based traffic flow prioritization; and transmitting one or more fourth packets indicating a device-specific address in association with establishing a third wireless communication link with the second wireless communication device, the third wireless communication link being exclusively used for the first wearable or handheld wireless device according to the device-specific address indicated by the one or more fourth packets.

[0278] Clause 24: The method according to any one of Clauses 1 to 23, wherein the first link identifier and the second link identifier are associated with the same channel access class.

[0279] Clause 25: The method according to any one of Clauses 1 to 24, wherein the one or more third packets include an indication 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.

[0280] Clause 26: The method according to any one of Clauses 1 to 25, wherein the one or more second groups include one or more of the following: authentication frames, association frames, address resolution protocol frames, dynamic host configuration protocol frames, Scalable Authentication Protocol frames on LAN, key handshake frames, and add block acknowledgment frames.

[0281] Clause 27: The method according to any one of Clauses 1 to 26, wherein the first packet is communicated to the second wearable or handheld wireless device to instruct the second wearable or handheld wireless device to avoid establishing a wireless communication link with the wireless communication device alone.

[0282] Clause 28: The method according to any one of Clauses 1 to 27, wherein 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.

[0283] Clause 29: The method according to any one of Clauses 1 to 28, wherein the wireless communication device is a service source device, an access point, or a computing device.

[0284] Clause 30: A method for wireless communication at a first wearable or handheld wireless device, the method comprising: transmitting one or more first packets to at least a second wearable or handheld wireless device via a first wireless communication link, the one or more first packets being associated with a shared address corresponding to an association of at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and 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 associated with the shared address; and receiving one or more second packets associated with the first link identifier from the wireless communication device via a second wireless communication link, the second wireless communication link being associated with the establishment using the shared address.

[0285] Clause 31: The method according to Clause 30, wherein transmitting the one or more first packets via the first wireless communication link to at least the second wearable or handheld wireless device comprises: sending one or more of the one or more first packets to the second wearable or handheld wireless device in accordance with an agreement with the second wearable or handheld wireless device on the shared address, and receiving one or more of the one or more first packets from the second wearable or handheld wireless device.

[0286] Clause 32: The method according to any one of Clauses 30 to 31, wherein transmitting the one or more first packets via the first wireless communication link to at least the second wearable or handheld wireless device comprises: sending one or more of the one or more first packets to the second wearable or handheld wireless device according to the 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, and receiving one or more of the one or more first packets from the second wearable or handheld wireless device.

[0287] Clause 33: The method according to any one of Clauses 30 to 32, the method further comprising: sending to the wireless communication device a third packet associated with the 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 sending to the wireless communication device one or more block acknowledgments associated with the one or more second packets.

[0288] Clause 34: The method according to any one of Clauses 30 to 33 further comprises: communicating one or more third packets via the first wireless communication link to at least the second wearable or handheld wireless device according to an agreement on one or more of the following: and one or more security keys, dynamic host configuration protocol addresses, or one or more address resolution protocol tables associated with communication with the wireless communication device, wherein the second wearable or handheld wireless device establishes the second wireless communication link according to the agreement.

[0289] Clause 35: The method according to any one of Clauses 30 to 34, the method further comprising: receiving from the wireless communication device information indicating a scheduling of a communication time interval corresponding to the first link identifier; and monitoring the second wireless communication link according to the scheduling of the communication time interval, wherein receiving the one or more second packets is associated with monitoring the second wireless communication link.

[0290] Clause 36: The method according to any one of Clauses 30 to 35, wherein each of the one or more second packets includes a corresponding frame header indicating the first link identifier, the method further comprising: decoding the data portion of the one or more second packets by indicating the first link identifier according to the frame header of the one or more second packets; receiving one or more third packets, each including a corresponding frame header indicating the second link identifier; and indicating the second link identifier according to the frame header of the one or more third packets to avoid decoding the data portion of the one or more third packets.

[0291] Clause 37: The method according to any one of Clauses 30 to 36, the method further comprising: receiving from the wireless communication device information indicating a first mapping from the first link identifier to the second wireless communication link and a second mapping from the second link identifier to a third link; and tuning at least one radio component to the second wireless communication link according to the first mapping, wherein receiving the one or more second packets is associated with tuning the at least one radio component to the second wireless communication link, and wherein the second wireless communication link is associated with a first frequency channel, and the third link is associated with a second frequency channel different from the first frequency channel.

[0292] Clause 38: The method according to any one of Clauses 30 to 37 further comprises: conveying information via the first wireless communication link to the second wearable or handheld wireless device information relating to a first communication between the first wearable or handheld wireless device and the wireless communication device and a second communication between the second wearable or handheld wireless device and the wireless communication device.

[0293] Clause 39: The method according to Clause 38 further comprises: receiving an indication that a link quality metric related to the second communication between the second wearable or handheld wireless device and the wireless communication device has failed to meet a condition; receiving one or more third packets including the second link identifier based on the failure of the link quality metric to meet the condition; and transmitting data received via the one or more third packets to the second wearable or handheld wireless device via the first wireless communication link based on the one or more third packets including the second link identifier.

[0294] Clause 40: The method according to Clause 39 further comprises: receiving feedback information associated with the data from the second wearable or handheld wireless device via the first wireless communication link; and sending one or more block acknowledgments associated with the one or more third packets to the wireless communication device, the one or more block acknowledgments indicating the feedback information received from the second wearable or handheld wireless device.

[0295] Clause 41: The method according to any one of Clauses 39 to 40, the method further comprising: receiving an indication that the link quality metric relating to the second communication between the second wearable or handheld wireless device and the wireless communication device satisfies the condition; and avoiding decoding any packet including the second link identifier based on the link quality metric satisfying the condition, wherein the first wearable or handheld wireless device temporarily receives the one or more third packets including the second link identifier when the link quality metric fails to satisfy the condition.

[0296] Clause 42: The method according to any one of Clauses 39 to 41, the method further comprising: sending information indicating a recommended decoding rate to the wireless communication device based on the failure of the link quality metric to meet the condition.

[0297] Clause 43: The method according to Clause 42, wherein the recommended decoding rate is used 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.

[0298] Clause 44: The method according to any one of Clauses 38 to 43, the method further comprising: sending an indication that a link quality metric related to the first communication between the first wearable or handheld wireless device and the wireless communication device has failed to meet a condition; receiving data from the second wearable or handheld wireless device via the first wireless communication link based on the failure of the link quality metric to meet the condition; and sending feedback information associated with the data to the second wearable or handheld wireless device via the first wireless communication link.

[0299] Clause 45: The method according to Clause 44 further comprises: sending an indication that the link quality metric relating to the first communication between the first wearable or handheld wireless device and the wireless communication device satisfies the condition; and receiving a packet including the first link identifier via the second wireless communication link based on the condition that the link quality metric satisfies the condition, wherein reception of any packet via the second wireless communication link is temporarily suspended if the link quality metric fails to satisfy the condition.

[0300] Clause 46: The method according to any one of Clauses 30 to 45, the method further comprising: receiving an indication of the handover of the association of the wearable or handheld wireless device, which includes at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, from the wireless communication device to the second wireless communication device; receiving an indication that the second wireless communication device is unable to perform quality-of-service-based traffic flow prioritization; and transmitting one or more third packets indicating a device-specific address in association with the establishment of a third wireless communication link with the second wireless communication device, the third wireless communication link being exclusively used for the first wearable or handheld wireless device according to the device-specific address indicated by the one or more third packets.

[0301] Clause 47: The method according to any one of Clauses 30 to 46, wherein the first link identifier and the second link identifier are associated with the same channel access class.

[0302] Clause 48: The method according to any one of Clauses 30 to 47, wherein the one or more second packets include an indication 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.

[0303] Clause 49: The method according to any one of Clauses 30 to 48, wherein the first wearable or handheld wireless device communicates the one or more first packets to the first wearable or handheld wireless device to instruct it to avoid establishing a wireless communication link with the wireless communication device alone.

[0304] Clause 50: The method according to any one of Clauses 30 to 49, wherein 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.

[0305] Clause 51: The method according to any one of Clauses 30 to 50, wherein the wireless communication device is a service source device, an access point, or a computing device.

[0306] Clause 52: A method for performing wireless communication at a wireless communication device, the method comprising: receiving one or more first packets in association with establishing a wireless communication link with a first wearable or handheld wireless device, the one or more first packets indicating a shared address corresponding to an association of at least one wearable or handheld wireless device including 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 one or more second packets associated with the first link identifier and one or more third packets associated with the second link identifier according to the shared address.

[0307] Clause 53: The method according to Clause 52 further includes: receiving a first indication of the first link identifier via a first packet associated with a first establishment of a first block confirmation 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 associated with a second establishment of a second block confirmation session between the wireless communication device and the second wearable or handheld wireless device.

[0308] Clause 54: The method according to any one of Clauses 52 to 53, the method further comprising: sending first information indicating a first schedule for a first communication time interval corresponding to the first link identifier, wherein the sending of the one or more second packets associated with the first link identifier is associated with the first schedule for the first communication time interval; and sending second information indicating a second schedule for a second communication time interval corresponding to the second link identifier, wherein the sending of the one or more third packets associated with the second link identifier is associated with the second schedule for the second communication time interval.

[0309] Clause 55: The method according to any one of Clauses 52 to 54, the method further comprising: 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, wherein the transmission of the one or more second packets and the one or more third packets is associated with the power management state.

[0310] Clause 56: The method according to any one of Clauses 52 to 55, the method further comprising: transmitting information indicating a first mapping from the first link identifier to a first wireless communication link and a second mapping from the second link identifier to a second wireless communication link, wherein 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 from the first frequency channel.

[0311] Clause 57: The method according to Clause 56, wherein sending the one or more second packets and the one or more third packets comprises: sending the one or more second packets via the first wireless communication link during a first communication time interval, and sending the one or more third packets via the second wireless communication link during a second communication time interval, wherein the first communication time interval and the second communication time interval at least partially overlap in time.

[0312] Clause 58: The method according to any one of Clauses 52 to 57, the method further comprising: sending to the first wearable or handheld wireless device an indication that the wireless communication device is capable of performing quality-of-service (QoS)-based traffic prioritization; and establishing the wireless communication link using the shared address based on the wireless communication device's capability to perform the QoS-based traffic prioritization.

[0313] Clause 59: The method according to Clause 58, wherein sending the indication that the wireless communication device is capable of performing the quality-of-service-based service flow prioritization includes: sending identification information of the wireless communication device, wherein the identification information indicates that the wireless communication device exists in a first list of devices allowed to use the shared address and does not exist in a second list of devices not allowed to use the shared address.

[0314] Clause 60: The method according to Clause 59, wherein the presence of the identification information of the wireless communication device in the first device list or the second device list indicates a previous quality of service compliance test for the wireless communication device, its presence in the first device list indicates a successful quality of service compliance test, and its presence in the second device list indicates an unsuccessful quality of service compliance test.

[0315] Clause 61: The method according to any one of Clauses 58 to 60, wherein sending the indication that the wireless communication device is capable of performing the quality-of-service (QoS)-based traffic flow prioritization comprises: sending a packet indicating that the end-to-end path between the service source device and the first wearable or handheld wireless device is capable of performing the QoS-based traffic flow prioritization, wherein the wireless communication device is the service source device or another wireless communication device along the end-to-end path.

[0316] Clause 62: The method according to any one of Clauses 52 to 61, wherein the first link identifier and the second link identifier are associated with the same channel access class.

[0317] Clause 63: The method according to any one of Clauses 52 to 62, wherein the one or more second packets include an indication 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 an indication 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.

[0318] Clause 64: The method according to any one of Clauses 52 to 63, wherein each of the one or more second groups includes first information specific to the first wearable or handheld wireless device, and each of the one or more third groups includes second information specific to the second wearable or handheld wireless device.

[0319] Clause 65: The method according to any one of Clauses 52 to 64, wherein each of the one or more second groups and the one or more third groups includes both first information specific to the first wearable or handheld wireless device and second information specific to the second wearable or handheld wireless device.

[0320] Clause 66: The method according to any one of Clauses 52 to 65, wherein the one or more first packets include one or more of the following: authentication frames, association frames, address resolution protocol frames, dynamic host configuration protocol frames, Scalable Authentication Protocol frames for local area networks, key handshake frames, and add block acknowledgment frames.

[0321] Clause 67: The method according to any one of Clauses 52 to 66, wherein the wireless communication device is a service source device.

[0322] Clause 68: A first wearable or handheld wireless device, the first wearable or handheld wireless device including a processing system, the processing system including processor circuitry and memory circuitry storing code, the processing system being configured to cause the first wearable or handheld wireless device to perform a method according to any one of Clauses 1 to 29.

[0323] Clause 69: An apparatus for wireless communication at a first wearable or handheld wireless device, the apparatus comprising at least one component for performing the method according to any one of Clauses 1 to 29.

[0324] 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 that can be executed individually or jointly by one or more processors to perform the method according to any one of Clauses 1 to 29.

[0325] Clause 71: A first wearable or handheld wireless device, the first wearable or handheld wireless device including a processing system, the processing system including processor circuitry and memory circuitry storing code, the processing system being configured to cause the first wearable or handheld wireless device to perform a method according to any one of Clauses 30 to 51.

[0326] Clause 72: An apparatus for wireless communication at a first wearable or handheld wireless device, the apparatus comprising at least one component for performing a method according to any one of Clauses 30 to 51.

[0327] 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 that can be executed individually or jointly by one or more processors to perform the method according to any one of Clauses 30 to 51.

[0328] Clause 74: A wireless communication device comprising a processing system including processor circuitry and memory circuitry storing code, the processing system being configured to cause the wireless communication to perform a method according to any one of Clauses 52 to 67.

[0329] Clause 75: An apparatus for performing wireless communication at a wireless communication device, the apparatus comprising at least one component for performing the method according to any one of Clauses 52 to 67.

[0330] Clause 76: A non-transitory computer-readable medium storing code for wireless communication at a wireless communication device, the code including instructions that can be executed individually or jointly by one or more processors to perform the method according to any one of Clauses 52 to 67.

[0331] As used herein, the term "determine" encompasses a wide variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), reasoning, discovery, or measurement. Additionally, "determine" can include receiving (such as receiving information), accessing (such as accessing data stored in memory), or sending (such as sending information). Furthermore, "determine" can include parsing, selecting, obtaining, choosing, building, and other similar actions.

[0332] As used herein, the phrase “at least one of” in a list of items refers to any combination of those items, including a single member. As an example, “at least one of: a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc. As used herein, “or” is intended to be interpreted as inclusive unless otherwise explicitly stated. For example, “a or b” could include only a, only b, or a combination of a and b.

[0333] As used herein, unless otherwise explicitly indicated, “based on” is intended to be interpreted in an inclusive sense. For example, unless otherwise explicitly indicated, “based on” may be used interchangeably with “at least partially based on,” “associated with,” or “according to.” Specifically, unless the phrase in the context refers to “based solely on 'one'” or an equivalent, it may be based solely on “one” or on a combination of “one” and one or more other factors, conditions, or information, whether it is “based on 'one'” or “at least partially based on 'one'.”

[0334] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, a “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and subsequent reference to “the component” in a claim may be understood to be equivalent to reference to “at least one of the one or more components.”

[0335] The various exemplary components, logic units, logic blocks, modules, circuits, operations, and algorithmic processes described in conjunction with the examples disclosed herein can be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed in this specification and their structural equivalents. This interchangeability of hardware, firmware, and software has been generally described in terms of its functionality and exemplified in the various exemplary components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.

[0336] Various modifications to the examples described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the examples shown herein, but are to be granted the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0337] Additionally, the various features described in this specification in the context of individual examples may also be implemented in combination in a single specific embodiment. Conversely, the various features described in the context of a single specific embodiment may also be implemented individually or in any suitable sub-combination in multiple examples. Thus, although features may be described above as functioning in a particular combination, and even initially claimed in this way, one or more features from the claimed combination may be removed from the combination in some cases, and the claimed combination may involve sub-combinations or variations of sub-combinations.

[0338] Similarly, although operations are depicted in a specific order in the diagrams, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the accompanying figures may schematically depict one or more example processes in the form of flowcharts or flow diagrams. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some environments, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the examples described above should not be construed as requiring such separation in all examples, but rather should be understood as meaning that the described program components and systems can generally be integrated together in a single software product or encapsulated in multiple software products.

Claims

1. A first wearable or hand-held wireless device, the first wearable or hand-held wireless device comprising: a processing system comprising a processor circuit and a memory circuit storing code, the processing system configured to cause the first wearable or hand-held wireless device to: communicate, via a first wireless communication link, one or more first packets with at least a second wearable or hand-held wireless device, the one or more first packets associated with a shared address corresponding to establishment of an association with wearable or hand-held wireless devices including at least the first wearable or hand-held wireless device and the second wearable or hand-held wireless device, and a first link identifier corresponding to the first wearable or hand-held wireless device and a second link identifier corresponding to the second wearable or hand-held wireless device associated with the shared address; transmit, in association with establishment of 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, via the second wireless communication link, one or more third packets from the wireless communication device associated with the first link identifier.

2. The first wearable or hand-held wireless device of claim 1, wherein to communicate, via the first wireless communication link, the one or more first packets with at least the second wearable or hand-held wireless device, the processing system is further configured to cause the first wearable or hand-held wireless device to: transmit and receive one or more of the one or more first packets to and from the second wearable or hand-held wireless device in accordance with negotiation of the shared address with the second wearable or hand-held wireless device.

3. The first wearable or hand-held wireless device of claim 1, wherein to communicate, via the first wireless communication link, the one or more first packets with at least the second wearable or hand-held wireless device, the processing system is further configured to cause the first wearable or hand-held wireless device to: transmit and receive one or more of the one or more first packets to and from the second wearable or hand-held wireless device in accordance with assignment of the first link identifier to the first wearable or hand-held wireless device and the second link identifier to the second wearable or hand-held wireless device.

4. The first wearable or hand-held wireless device of claim 1, wherein the processing system is further configured to cause the first wearable or hand-held wireless device to: transmit, to the wireless communication device, a fourth packet associated with establishment of a first block acknowledgement session between the wireless communication device and the first wearable or hand-held wireless device, the fourth packet including an indication of the first link identifier; and transmit, to the wireless communication device, a fifth packet associated with establishment of a second block acknowledgement session between the wireless communication device and the first wearable or hand-held wireless device, the fifth packet including an indication of the second link identifier. Send one or more block acknowledgments associated with the one or more third packets to the wireless communication device.

5. The first wearable or handheld wireless device of claim 1, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: Send a fourth packet to the wireless communication device, indicating the shared address and the power management status corresponding to the shared address.

6. The first wearable or handheld wireless device of claim 5, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: A fifth packet indicating that the second wearable or handheld wireless device is in the power management state is received from the second wearable or handheld wireless device via the first wireless communication link, wherein the sending of the fourth packet indicating the power management state is associated with the receiving of the fifth packet.

7. The first wearable or handheld wireless device of claim 1, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: One or more fourth packets are communicated via the first wireless communication link to at least the second wearable or handheld wireless device based on one or more of the following: and one or more security keys, Dynamic Host Configuration Protocol (DHCP) addresses, or one or more Address Resolution Protocol (ARP) tables associated with communication with the wireless communication device, wherein the first wearable or handheld wireless device establishes the second wireless communication link according to the negotiation.

8. The first wearable or handheld wireless device of claim 1, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: Receive from the wireless communication device information indicating the scheduling of the communication time interval corresponding to the first link identifier; and The second wireless communication link is monitored according to the schedule of the communication time interval, wherein receiving the one or more third packets is associated with monitoring the second wireless communication link.

9. The first wearable or handheld wireless device of claim 1, wherein each of the one or more third packets includes a corresponding frame header indicating the first link identifier, and the processing system is further configured to cause the first wearable or handheld wireless device to: The data portion of the one or more third packets is decoded based on the first link identifier indicated in the frame header of the one or more third packets; Receive one or more fourth packets, each including a corresponding frame header indicating the second link identifier; and The second link identifier is indicated in the frame header of the one or more fourth packets to avoid decoding the data portion of the one or more fourth packets.

10. The first wearable or handheld wireless device of claim 1, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: Receive from the wireless communication device information indicating a first mapping from the first link identifier to the second wireless communication link and a second mapping from the second link identifier to the third wireless communication link; and At least one radio component is tuned to the second wireless communication link according to the first mapping, wherein receiving the one or more third packets is associated with tuning the at least one radio component to the second wireless communication link, and wherein 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 from the first frequency channel.

11. The first wearable or handheld wireless device of claim 1, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: The wireless communication device receives an instruction that it can perform service flow prioritization based on quality of service; and Based on the fact that the wireless communication device is capable of performing the quality-of-service-based service flow prioritization, the shared address is used to establish the second wireless communication link with the wireless communication device.

12. The first wearable or handheld wireless device of claim 11, wherein, in order to receive the indication that the wireless communication device is capable of performing the quality-of-service-based traffic prioritization, the processing system is further configured to cause the first wearable or handheld wireless device to: The identification information of the wireless communication device is received, wherein the identification information indicates that the wireless communication device exists in a first list of devices that are allowed to use the shared address, and does not exist in a second list of devices that are not allowed to use the shared address.

13. The first wearable or handheld wireless device of claim 12, wherein the presence of the identification information of the wireless communication device in the first device list or the second device list indicates a previous quality of service compliance test for the wireless communication device, wherein presence in the first device list indicates a successful quality of service compliance test, and presence in the second device list indicates an unsuccessful quality of service compliance test.

14. The first wearable or handheld wireless device of claim 11, wherein, in order to receive the indication that the wireless communication device is capable of performing the quality-of-service (QoS)-based traffic prioritization, the processing system is further configured to cause the first wearable or handheld wireless device to: The receiving instruction indicates that the end-to-end path between the service source device and the first wearable or handheld wireless device is capable of the packetization based on the quality of service (QoS) priority of the service flow, wherein the wireless communication device is the service source device or another wireless communication device along the end-to-end path.

15. The first wearable or handheld wireless device of claim 1, wherein the one or more second packets comprise one or more of the following: authentication frames, association frames, address resolution protocol frames, dynamic host configuration protocol frames, Scalable Authentication Protocol frames over LAN frames, key handshake frames, and add block confirmation frames.

16. A first wearable or handheld wireless device, the first wearable or handheld wireless device comprising: A processing system, including processor circuitry and memory circuitry for storing code, is configured to enable the first wearable or handheld wireless device to: One or more first packets are transmitted via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with a shared address corresponding to an association between a wearable or handheld wireless device and at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and 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 associated with the shared address. as well as Receive one or more second packets associated with the first link identifier from a wireless communication device via a second wireless communication link, the second wireless communication link being associated with the establishment using the shared address.

17. The first wearable or handheld wireless device of claim 16, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: The first wireless communication link is used to communicate with the second wearable or handheld wireless device information relating to one or more link quality metrics related to a first communication between the first wearable or handheld wireless device and the wireless communication device, and a second communication between the second wearable or handheld wireless device and the wireless communication device.

18. The first wearable or handheld wireless device of claim 17, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: Receive an indication that a link quality metric related to the second communication between the second wearable or handheld wireless device and the wireless communication device has failed to meet a condition; If the link quality metric fails to meet the condition, one or more third packets including the second link identifier will be received. as well as Data received via the one or more third packets is transmitted to the second wearable or handheld wireless device via the first wireless communication link, based on the second link identifier included in the one or more third packets.

19. The first wearable or handheld wireless device of claim 18, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: Receive feedback information associated with the data from the second wearable or handheld wireless device via the first wireless communication link; and Send one or more block acknowledgments associated with the one or more third packets to the wireless communication device, the one or more block acknowledgments indicating the feedback information received from the second wearable or handheld wireless device.

20. The first wearable or handheld wireless device of claim 18, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: Receive an indication that the link quality metric relating to the second communication between the second wearable or handheld wireless device and the wireless communication device meets the condition; and Decoding any packet including the second link identifier is avoided based on the condition that the link quality metric meets, wherein the first wearable or handheld wireless device temporarily receives the one or more third packets including the second link identifier when the link quality metric fails to meet the condition.

21. The first wearable or handheld wireless device of claim 18, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: If the link quality metric fails to meet the condition, information indicating a recommended decoding rate is sent to the wireless communication device.

22. The first wearable or handheld wireless device of claim 21, wherein the recommended decoding rate is used 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.

23. The first wearable or handheld wireless device of claim 17, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: Sending an indication that the link quality metric related to the first communication between the first wearable or handheld wireless device and the wireless communication device failed to meet the conditions; Data is received from the second wearable or handheld wireless device via the first wireless communication link if the link quality metric fails to meet the condition. as well as Feedback information associated with the data is sent to the second wearable or handheld wireless device via the first wireless communication link.

24. The first wearable or handheld wireless device of claim 23, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: Sending an indication that the link quality metric related to the first communication between the first wearable or handheld wireless device and the wireless communication device meets the condition; and Packets including the first link identifier are received via the second wireless communication link based on the condition that the link quality metric meets the condition, wherein reception of any packet via the second wireless communication link is temporarily suspended if the link quality metric fails to meet the condition.

25. The first wearable or handheld wireless device of claim 16, wherein the processing system is further configured to cause the first wearable or handheld wireless device to: Receive an instruction for the transfer of the association of the wearable or handheld wireless device, which includes at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, from the wireless communication device to the second wireless communication device; Receive an indication that the second wireless communication device is unable to perform quality-of-service (QoS)-based traffic prioritization; and 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 are transmitted, the third wireless communication link being exclusively used for the first wearable or handheld wireless device based on the device-specific address indicated by the one or more third packets.

26. The first wearable or handheld wireless device of claim 16, wherein the first link identifier and the second link identifier are associated with the same channel access class.

27. A method for wireless communication at a first wearable or handheld wireless device, the method comprising: One or more first packets are transmitted via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with a shared address corresponding to an association between a wearable or handheld wireless device and at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and 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 associated with the shared address. One or more second packets indicating the shared address, the first link identifier, and the second link identifier are transmitted in association with the establishment of a second wireless communication link with the wireless communication device; as well as Receive one or more third packets associated with the first link identifier from the wireless communication device via the second wireless communication link.

28. The method of claim 27, wherein transmitting the one or more first packets via the first wireless communication link to at least the second wearable or handheld wireless device comprises: Based on the negotiation with the second wearable or handheld wireless device regarding the shared address, send one or more first packets of the one or more first packets to the second wearable or handheld wireless device and receive one or more first packets of the one or more first packets from the second wearable or handheld wireless device.

29. A method for wireless communication at a first wearable or handheld wireless device, the method comprising: One or more first packets are transmitted via a first wireless communication link to at least a second wearable or handheld wireless device, the one or more first packets being associated with a shared address corresponding to an association between a wearable or handheld wireless device and at least the first wearable or handheld wireless device and the second wearable or handheld wireless device, and 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 associated with the shared address. as well as Receive one or more second packets associated with the first link identifier from a wireless communication device via a second wireless communication link, the second wireless communication link being associated with the establishment using the shared address.

30. The method of claim 29, wherein transmitting the one or more first packets via the first wireless communication link to at least the second wearable or handheld wireless device comprises: Based on the negotiation with the second wearable or handheld wireless device regarding the shared address, send one or more first packets of the one or more first packets to the second wearable or handheld wireless device and receive one or more first packets of the one or more first packets from the second wearable or handheld wireless device.

Images