Agent transfer with meta-attributes

Abstract

Embodiments include a station (STA) in a wireless network, the STA comprising a memory and a processor coupled to the memory, the processor configured to receive a first discovery frame from an original STA, the first discovery frame comprising one or more attributes intended for proxy transmission; generate a second discovery frame, the second discovery frame comprising the one or more attributes intended for proxying of the transmission based on the first discovery frame and attaching additional information, wherein the additional information comprises an indication that the one or more attributes are associated with the original STA and that the one or more attributes are being sent through proxy transmission, and wherein the additional information comprises address information of the original STA; and transmit the second discovery frame to one or more other STAs.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to encapsulating the NAN attributes of the original device into the service discovery frame (SDF) of the proxy device using, for example, but not limited to, the Meta Service Descriptor Attribute (SDA). Background Technology

[0002] Since the late 1990s, Wireless Local Area Network (WLAN) technology has evolved towards increasing data rates and continues to grow in various markets such as homes, businesses, and hotspots. WLAN allows devices to access the Internet in the 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz frequency bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 standard family is designed to improve speed and reliability and extend the operational range of wireless networks.

[0003] WLAN devices increasingly need to support a variety of latency-sensitive or real-time applications, such as augmented reality (AR), robotics, artificial intelligence (AI), cloud computing, and autonomous vehicles. To achieve the extremely low latency and extremely high throughput required for such applications, Multi-Link Operation (MLO) has been proposed for WLANs. A WLAN is formed by WLAN devices within a limited area such as a home, school, apartment, or office building. Each WLAN device can have one or more Stations (STAs), such as Access Point (AP) STAs and Non-Access Point (Non-AP) STAs.

[0004] Wi-Fi Awareness (also known as Neighbor Aware Networking (NAN)) is a specification proposed by the Wi-Fi Alliance focusing on self-organizing peer-to-peer (P2P) networking. This specification allows devices to connect to each other to meet specific service-based needs. A key feature of this specification is discovery. NAN discovery can be handled by the NAN discovery engine and can include publishing service advertisements for devices within the NAN network. NAN service advertisements are typically sent multiple times (e.g., periodically) by devices in a NAN cluster. Devices offering / requesting services can conduct service advertisements. Many devices have limited power, so frequent advertising can be an expensive activity.

[0005] There are many ways to advertise services. For example, a NAN device can initiate periodic message postings to solicit subscriptions to one or more services. Alternatively, a NAN device can initiate this by repeatedly (e.g., periodically) sending subscription messages to search for another device offering a specific service. In either case, to increase the likelihood of finding a matching publisher / subscriber, it may be necessary to repeat these messages over an extended period of time.

[0006] The descriptions set forth in the Background section should not be assumed to be prior art simply because they are set forth in the Background section. The Background section may describe aspects or embodiments of this disclosure. Summary of the Invention

[0007] Solution to the problem

[0008] One aspect of this disclosure provides a station (STA) in a wireless network, the STA including a memory and a processor coupled to the memory. The processor is configured to receive a first discovery frame from an original STA, the first discovery frame including one or more attributes intended for proxy transmission. The processor is configured to generate a second discovery frame based on the first discovery frame, the second discovery frame including one or more attributes intended for proxy transmission and appending additional information, wherein the additional information includes indications that one or more attributes are associated with the original STA and that one or more attributes are transmitted via proxy transmission, and wherein the additional information includes address information of the original STA. The processor is configured to send the second discovery frame to one or more other STAs.

[0009] In some embodiments, the second discovery frame includes one or more attributes associated with a different original STA and address information of the different original STA associated with one or more attributes.

[0010] In some embodiments, the second discovery frame includes one or more different original STAs, associated address information for each of the one or more different original STAs, and one or more indexes associated with a corresponding original STA among the one or more different original STAs.

[0011] In some embodiments, the second discovery frame has a unique service identifier for identifying the second discovery frame as having proxy attributes.

[0012] In some embodiments, the second discovery frame includes attributes storing additional information, including indications of one or more attributes associated with the original STA and address information of the original STA.

[0013] In some embodiments, the processor is also configured to repeatedly send a second discovery frame to one or more STAs.

[0014] In some embodiments, one or more attributes are associated with services provided by the original STA to one or more other STAs or services sought by the original STA from one or more other STAs.

[0015] One aspect of this disclosure provides a station (STA) in a wireless network, the STA including a memory and a processor coupled to the memory. The processor is configured to receive a first discovery frame from a proxy STA, including one or more attributes and additional information, wherein the additional information includes an indication that the one or more attributes are associated with an original STA and that the one or more attributes are being transmitted via the proxy, and wherein the additional information includes address information of the original STA. The processor is configured to obtain the address information of the original STA and one or more attributes associated with the original STA from the additional information based on the first discovery frame. The processor is configured to send a second frame to the original STA using the address information.

[0016] In some embodiments, the first discovery frame includes one or more attributes associated with a different original STA and address information of the different original STA associated with one or more attributes.

[0017] In some embodiments, the additional information includes one or more different original STAs, the associated address information of each of the one or more different original STAs, and one or more indexes associated with a corresponding original STA among the one or more different original STAs.

[0018] In some embodiments, the first discovery frame has a unique service identifier for identifying the first discovery frame as having additional information.

[0019] In some embodiments, the first discovery frame includes attributes storing additional information, including indications about one or more attributes being associated with the original STA and address information of the original STA.

[0020] In some embodiments, one or more attributes are associated with services provided by the original STA to one or more other STAs or services sought by the original STA from one or more other STAs. Attached Figure Description

[0021] Figure 1 An example of a wireless network according to an embodiment is shown.

[0022] Figure 2a An example of an AP according to an embodiment is shown.

[0023] Figure 2b An example of a STA according to an embodiment is shown.

[0024] Figure 3 An example of multi-link communication operation according to an embodiment is shown.

[0025] Figure 4The architecture of a Neighbor-Aware Networking (NAN) engine according to an embodiment is shown.

[0026] Figure 5 The operation between two devices involved in discovery via a proxy device, according to an embodiment, is illustrated.

[0027] Figure 6 A flowchart illustrating an example process for an agent device, according to an embodiment, to generate an SDF with an additional meta-SDA.

[0028] Figure 7 A flowchart illustrating an example process for connecting a device upon receiving an SDF, according to an embodiment, is shown.

[0029] Figure 8 An exemplary communication between the original device, the agent device, and the connecting device according to an implementation scheme is shown.

[0030] Figure 9 The layout of the proxy meta SDA field according to an embodiment is shown.

[0031] Figure 10 A flowchart illustrating an exemplary process for proxying device operation upon receiving an SDF from the original device, according to one embodiment, is shown.

[0032] Figure 11 A flowchart illustrating an example process for connecting a device upon receiving an SDF, according to an embodiment, is shown.

[0033] Figure 12 An exemplary communication between an original device, a proxy device, and a connecting device according to one embodiment is illustrated.

[0034] In one or more embodiments, not all components depicted in each figure are necessary, and one or more embodiments may include additional components not shown in the figures. Variations in the arrangement and type of components may be made without departing from the scope of this subject matter disclosure. Additional components, different components, or fewer components may be utilized within the scope of this subject matter disclosure. Detailed Implementation

[0035] The detailed description set forth below in conjunction with the accompanying drawings is intended to describe various embodiments and is not intended to represent the only embodiments in which the subject matter can be practiced. Rather, this detailed description includes specific details to provide a thorough understanding of the subject matter of the invention. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the scope of this disclosure. Therefore, the drawings and description are to be considered illustrative rather than restrictive in nature. The same reference numerals denote the same elements.

[0036] The following description pertains to certain implementations for the purpose of describing 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. The examples in this disclosure are based on WLAN communication in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, including the IEEE 802.11be standard and any future revisions to the IEEE 802.11 standard. However, the described embodiments can be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals according to the IEEE 802.11 standard, Bluetooth standard, Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunking Radio (TETRA), Wideband CDMA (W-CDMA), Evolved Data Optimized (EV-DO), 1xEV-DO, EV-DO Rev A, EV-DO Rev B, High-Speed ​​Packet Access (HSPA), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolved High-Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), 5G NR (New Radio), AMPS, or other known signals used for communication within wireless, cellular, or Internet of Things (IoT) networks, such as systems utilizing 3G, 4G, 5G, 6G, or further implementations thereof.

[0037] Depending on the network type, other well-known terms may be used instead of "access point" or "AP," such as "router" or "gateway." For convenience, the term "AP" is used in this disclosure to refer to a network infrastructure component that provides wireless access to remote terminals. In a WLAN, assuming that the AP also contends for the wireless channel, the AP may also be referred to as a STA. Furthermore, depending on the network type, other well-known terms may be used instead of "site" or "STA," such as "mobile station," "subscriber station," "remote terminal," "user equipment," "wireless terminal," or "user equipment." For convenience, the terms "site" and "STA" are used in this disclosure to refer to a remote wireless device that wirelessly accesses an AP or contends for a wireless channel in a WLAN, whether the STA is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer, AP, media player, fixed sensor, television, etc.).

[0038] Multilink Operation (MLO) is a key feature currently being developed by the standards body for next-generation Ultra High Throughput (EHT) Wi-Fi systems in IEEE 802.11be. Wi-Fi devices that support MLO are called Multilink Devices (MLDs). Using MLO, a non-AP MLD can discover, authenticate, associate, and establish multiple links with an AP MLD. Channel access and frame switching can occur on each link between the AP MLD and non-AP MLDs.

[0039] Figure 1 An example of a wireless network 100 according to an embodiment is shown. Figure 1 The illustrated embodiment of the wireless network 100 is for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0040] like Figure 1 As shown, wireless network 100 may include multiple wireless communication devices. Each wireless communication device may include one or more stations (STAs). An STA may be a logical entity that is a separate addressable instance of an interface to the Media Access Control (MAC) layer and Physical (PHY) layer of the wireless medium. STAs may be classified as Access Point (AP) STAs and Non-Access Point (Non-AP) STAs. An AP STA may be an entity that provides access to distribution system services to an associated STA via the wireless medium. A Non-AP STA may be a STA that is not included within an AP-STA. For simplicity, an AP STA may be referred to as an AP, and a Non-AP STA may be referred to as a STA. Figure 1 In the example, APs 101 and 103 are wireless communication devices, each of which may include one or more AP STAs. In such an embodiment, APs 101 and 103 may be AP multilink devices (MLDs). Similarly, STAs 111-114 are wireless communication devices, each of which may include one or more non-AP STAs. In such an embodiment, STAs 111-114 may be non-AP MLDs.

[0041] APs 101 and 103 communicate with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network. AP 101 provides wireless access to network 130 to multiple stations 111-114 in the coverage area 120 of AP 101. APs 101 and 103 can communicate with each other and with STAs using Wi-Fi or other WLAN communication technologies.

[0042] Depending on the network type, other well-known terms may be used instead of "access point" or "AP," such as "router" or "gateway." For convenience, the term "AP" is used in this disclosure to refer to a network infrastructure component that provides wireless access to remote terminals. In a WLAN, assuming that the AP also contends for the wireless channel, the AP may also be referred to as a STA. Furthermore, depending on the network type, other well-known terms may be used instead of "site" or "STA," such as "mobile station," "subscriber station," "remote terminal," "user equipment," "wireless terminal," or "user device." For convenience, the terms "site" and "STA" are used in this disclosure to refer to a remote wireless device that wirelessly accesses an AP or contends for a wireless channel in a WLAN, whether the STA is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer, AP, media player, fixed sensor, television, etc.).

[0043] exist Figure 1 In the diagram, the dashed lines indicate the approximate extent of the coverage areas 120 and 125 of APs 101 and 103, which are shown as approximately circular for illustrative and explanatory purposes. It should be clearly understood that, depending on the configuration of the APs, the coverage areas associated with the APs (such as coverage areas 120 and 125) may have other shapes, including irregular shapes.

[0044] As described in more detail below, one or more APs in an AP may include circuitry and / or programming for the management of MU-MIMO and OFDMA channel detection in a WLAN. Although Figure 1 An example of a wireless network 100 is shown, but more details can be found on other wireless networks. Figure 1 Various modifications can be made. For example, wireless network 100 can include any number of APs and any number of STAs in any suitable arrangement. Furthermore, AP 101 can communicate directly with any number of STAs and provide these STAs with wireless broadband access to network 130. Similarly, each AP 101 and 103 can communicate directly with network 130 and provide STAs with direct wireless broadband access to network 130. Additionally, AP 101 and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0045] Figure 2a An example of AP 101 according to an embodiment is shown. Figure 2a The embodiment of AP 101 shown is for illustrative purposes, and Figure 1 AP 103 can have the same or similar configuration. However, APs have a wide variety of configurations, and Figure 2a This disclosure is not intended to limit the scope to any particular implementation of AP.

[0046] like Figure 2a As shown, AP 101 may include multiple antennas 204a-204n, multiple radio frequency (RF) transceivers 209a-209n, transmit (TX) processing circuitry 214, and receive (RX) processing circuitry 219. AP 101 may also include a controller / processor 224, a memory 229, and a backhaul or network interface 234. RF transceivers 209a-209n receive incoming RF signals from antennas 204a-204n, such as signals transmitted by STAs in network 100. RF transceivers 209a-209n down-convert the incoming RF signals to generate intermediate (IF) or baseband signals. The IF or baseband signals are sent to RX processing circuitry 219, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 219 sends the processed baseband signals to controller / processor 224 for further processing.

[0047] TX processing circuit 214 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller / processor 224. TX processing circuit 214 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. RF transceivers 209a-209n receive the outgoing processed baseband or IF signals from TX processing circuit 214 and up-convert the baseband or IF signals into RF signals transmitted via antennas 204a-204n.

[0048] The controller / processor 224 may include one or more processors or other processing devices that control the overall operation of the AP 101. For example, the controller / processor 224 may control the RF transceivers 209a-209n, the RX processing circuitry 219, and the TX processing circuitry 214 to receive uplink signals and transmit downlink signals according to known principles. The controller / processor 224 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 224 may support beamforming or directional routing operations, where outgoing signals from multiple antennas 204a-204n are weighted differently to effectively direct outgoing signals to a desired direction. The controller / processor 224 may also support OFDMA operations, where outgoing signals are assigned to different subcarrier subsets for different receivers (e.g., different STAs 111-114). Various other functions may be supported in the AP 101 via the controller / processor 224, including combinations of DL MU-MIMO and OFDMA in the same transmission opportunity. In some embodiments, the controller / processor 224 may include at least one microprocessor or microcontroller. The controller / processor 224 is also capable of executing programs and other processes, such as an operating system, residing in the memory 229. The controller / processor 224 may move data into or out of the memory 229 as needed for the execution process.

[0049] The controller / processor 224 is also coupled to a backhaul or network interface 234. The backhaul or network interface 234 allows the AP 101 to communicate with other devices or systems via a backhaul connection or over a network. Interface 234 can support communication via any suitable wired or wireless connection. For example, interface 234 can allow the AP 101 to communicate with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. Interface 234 can include any suitable structure that supports communication via a wired or wireless connection, such as an Ethernet or RF transceiver. Memory 229 is coupled to the controller / processor 224. A portion of memory 229 can include RAM, and another portion of memory 229 can include flash memory or other ROM.

[0050] As described in more detail below, AP 101 may include circuitry and / or procedures for managing the channel detection process in a WLAN. Although Figure 2a An example of AP 101 is shown, but it is possible to compare it with other versions. Figure 2a Various changes can be made. For example, AP101 can include any number of... Figure 2aEach component shown. As a specific example, the AP may include multiple interfaces 234, and the controller / processor 224 may support routing functionality to route data between different network addresses. As another example, although shown as a single instance including TX processing circuitry 214 and a single instance including RX processing circuitry 219, AP 101 may include multiple instances of each (e.g., one for each RF transceiver). Alternatively, only one antenna and RF transceiver path may be included, as in a conventional AP. Moreover, Figure 2a The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0051] like Figure 2a As shown, in some embodiments, AP 101 may be an AP MLD comprising multiple APs 202A-202N. Each AP 202a-202n is attached to AP MLD 101 and includes multiple antennas 204a-204n, multiple radio frequency (RF) transceivers 209a-209n, transmit (TX) processing circuitry 214, and receive (RX) processing circuitry 219. Each AP 202a-202n may communicate independently with the controller / processor 224 and other components of AP MLD 101. Figure 2a The diagram shows that each AP 202a-202n has multiple antennas individually, but each AP 202a-202n can share multiple antennas 204a-204n without requiring separate multiple antennas. Each AP 202a-202n can represent the physical (PHY) layer and the lower media access control (MAC) layer.

[0052] Figure 2b An example of STA 111 according to an embodiment is shown. Figure 2b The embodiment of STA 111 shown is for illustrative purposes, and Figure 1 STAs 111-114 can have the same or similar configurations. However, STAs appear in a wide variety of configurations, and Figure 2b This disclosure is not intended to limit the scope of any particular implementation of STA.

[0053] like Figure 2b As shown, STA 111 may include one or more antennas 205, an RF transceiver 210, a TX processing circuit 215, a microphone 220, and an RX processing circuit 225. STA 111 may also include a speaker 230, a controller / processor 240, an input / output (I / O) interface (IF) 245, a touchscreen 250, a display 255, and a memory 260. The memory 260 may include an operating system (OS) 261 and one or more applications 262.

[0054] RF transceiver 210 receives incoming RF signals transmitted by the AP of network 100 from antenna 205. RF transceiver 210 down-converts the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 225 sends the processed baseband signals to speaker 230 (e.g., for voice data) or to controller / processor 240 for further processing (e.g., for web browsing data).

[0055] TX processing circuitry 215 receives analog or digital voice data from microphone 220, or other outgoing baseband data (such as web data, email, or interactive video game data) from controller / processor 240. TX processing circuitry 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 210 receives the processed outgoing baseband or IF signal from TX processing circuitry 215 and up-converts the baseband or IF signal into an RF signal transmitted via antenna 205.

[0056] The controller / processor 240 may include one or more processors and executes a basic OS program 261 stored in memory 260 to control the overall operation of STA 111. In one such operation, the controller / processor 240 controls the RF transceiver 210, RX processing circuitry 225, and TX processing circuitry 215 to receive downlink signals and transmit uplink signals according to known principles. The controller / processor 240 may also include processing circuitry configured to provide management of the channel detection process in the WLAN. In some embodiments, the controller / processor 240 may include at least one microprocessor or microcontroller.

[0057] The controller / processor 240 is also capable of executing other processes and programs residing in the memory 260, such as operations for managing channel sounding processes in the WLAN. The controller / processor 240 can move data into or out of the memory 260 as needed for the execution of the process. In some embodiments, the controller / processor 240 is configured to execute multiple applications 262, such as applications for channel sounding, including feedback calculations based on received empty data packet advertisements (NDPA) and empty data packets (NDP), and sending beamforming feedback reports in response to trigger frames (TF). The controller / processor 240 can operate the multiple applications 262 based on the OS program 261 or in response to signals received from the AP. The controller / processor 240 is also coupled to an I / O interface 245, which provides the STA 111 with the ability to connect to other devices such as laptops and handheld computers. The I / O interface 245 is the communication path between these accessories and the main controller / processor 240.

[0058] The controller / processor 240 is also coupled to input 250 (e.g., a touchscreen) and display 255. An operator of STA 111 can use input 250 to input data into STA 111. Display 255 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text and / or at least limited graphics (such as from a website). Memory 260 is coupled to the controller / processor 240. A portion of memory 260 may include random access memory (RAM), and another portion of memory 260 may include flash memory or other read-only memory (ROM).

[0059] although Figure 2b An example of STA 111 is shown, but it is possible to compare it with other models. Figure 2b Make various changes. For example, Figure 2b The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. In a specific example, STA 111 may include any number of antennas 205 for MIMO communication with AP 101. In another example, STA 111 may not include voice communication, or the controller / processor 240 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although... Figure 2b The STA 111 is shown configured as a mobile phone or smartphone, but the STA can be configured to operate as other types of mobile or fixed devices.

[0060] like Figure 2bAs shown, in some embodiments, STA 111 may be a non-AP MLD comprising multiple STAs 203A-203N. Each STA 203a-203n is attached to the non-AP MLD 111 and includes an antenna 205, an RF transceiver 210, a TX processing circuit 215, and an RX processing circuit 225. Each STA 203a-203n may independently communicate with the controller / processor 240 and other components of the non-AP MLD 111. Figure 2b It is shown that each STA 203a-203n has a separate antenna, but each STA 203a-203n can share antenna 205 without requiring a separate antenna. Each STA 203a-203n can represent the physical (PHY) layer and the lower medium access control (MAC) layer.

[0061] Figure 3 An example of multi-link communication operation according to an embodiment is shown. Multi-link communication operation can be used in the IEEE 802.11be standard and any future revisions of the IEEE 802.11 standard. Figure 3 In the middle, AP MLD 310 can be Figure 1 Wireless communication devices 101 and 103 are included, and the non-AP MLD 220 can be... Figure 1 One of the wireless communication devices 111-114 in the series.

[0062] like Figure 3 As shown, AP MLD 310 may include multiple auxiliary APs, such as AP 1, AP 2, and AP 3. Each auxiliary AP may include a PHY interface to the wireless medium (Link 1, Link 2, or Link 3). AP MLD 310 may include a single MAC Service Access Point (SAP) 318 through which the auxiliary APs of AP MLD 310 communicate with higher layers (Layer 3 or network layer). Each auxiliary AP of AP MLD 310 may have a different MAC address (lower MAC address) than any other auxiliary AP of AP MLD 310. AP MLD 310 may have an MLD MAC address (upper-layer MAC address), and the auxiliary APs share a single MAC SAP 318 to Layer 3. Therefore, the auxiliary APs share a single IP address, and Layer 3 identifies AP MLD 310 by assigning a single IP address.

[0063] A non-AP MLD 320 may include multiple affiliated STAs, such as STA 1, STA 2, and STA 3. Each affiliated STA may include a PHY interface to the wireless medium (Link 1, Link 2, or Link 3). A non-AP MLD 320 may include a single MAC SAP 328, through which affiliated STAs communicate with higher layers (Layer 3 or network layer). Each affiliated STA of a non-AP MLD 320 may have a different MAC address (lower MAC address) than any other affiliated STA of the non-AP MLD 320. A non-AP MLD 320 may have an MLD MAC address (upper MAC address), and the affiliated STAs share the single MAC SAP 328 to Layer 3. Therefore, affiliated STAs share a single IP address, and Layer 3 identifies the non-AP MLD 320 by assigning this single IP address.

[0064] AP MLD 310 and non-AP MLD 320 can establish multiple links between their associated APs and STAs. In this example, AP 1 and STA 1 can establish Link 1, operating in the 2.4 GHz band. Similarly, AP 2 and STA 2 can establish Link 2, operating in the 5 GHz band, and AP 3 and STA 3 can establish Link 3, operating in the 6 GHz band. Each link can independently enable channel access and frame exchange between AP MLD 310 and non-AP MLD 320, which can increase data throughput and reduce latency. When associated with an AP MLD on a set of links (link establishment), each non-AP device is assigned a unique Association Identifier (AID).

[0065] Figure 4 The architecture of a NAN engine according to an embodiment is shown. The NAN engine may include a NAN discovery engine module, a ranging module, a NAN data engine module, a NAN scheduler module, a NAN media access control (MAC) layer module, and an 802.11 PHY layer module.

[0066] The NAN discovery engine can be responsible for discovering devices and / or services available on devices for specific services by publishing and subscribing to messages. Publishing messages can advertise one or more services offered by NAN devices, and subscribing messages can advertise the willingness of devices to participate in providing one or more services.

[0067] The ranging module estimates the distance between NAN devices that support ranging capabilities. In addition to service discovery mechanisms, ranging can be used to estimate the distance to NAN devices providing specific services. The NAN data engine module provides NAN data link (NDL) capabilities that can be used to establish data links between NAN devices. The NAN scheduler module establishes, maintains, and terminates Wi-Fi radio resource scheduling for NAN operations. The NAN scheduler module is also responsible for coordinating concurrent NAN and non-NAN operations. The NAN MAC layer module processes and handles NAN beacon frames and NAN service discovery frames. The 802.11 PHY layer module provides data transmission services to higher layers.

[0068] As described, NAN discovery is performed by the NAN discovery engine (e.g., such as...). Figure 4 (As shown) handles and is responsible for discovering devices (or services available on devices) for a specific service by publishing and / or subscribing to messages. Publishing messages can advertise services provided by NAN devices or make them discoverable, and subscribing messages can advertise the willingness to participate in or request publishing messages from devices providing services.

[0069] There are various ways to complete a publish / subscribe handshake. For example, a NAN device can initiate periodic publish messages to request a subscription or follow-up to one or more services. Conversely, a NAN device can alternatively initiate this by repeatedly (e.g., periodically) sending subscription messages to search for another device offering a specific service. In either case, to increase the likelihood of finding a matching publisher / subscriber, it may be necessary to repeatedly send these messages over an extended period. Proxy devices can publish / subscribe on behalf of one or more other devices. This can provide certain benefits, including saving channel congestion (e.g., in cases where multiple devices use a single proxy) or allowing the original device to save power.

[0070] Figure 5Operation between two devices participating in discovery via a proxy device according to an embodiment is illustrated. These devices may include an originating device, which may be a device that wants to send its publish and / or subscribe messages via the proxy device. The proxy device may be a device that transmits publish and / or subscribe messages 505 on behalf of the originating device. The connecting device may be a device that wants to subscribe to (or follow up on) a service of the originating device or publish a service to the originating device. For example, the connecting device may be the originating device receiving a subscription message 503 sent by the proxy device on its behalf. As shown, the originating device may communicate with the proxy device, including transmitting SDF 501. The proxy device may send a proxy transmission 503 to the connecting device, which may include sending an SDF derived from the SDF received from the originating device. Accordingly, the originating device may communicate with the connecting device 505 (e.g., publishing, subscribing to, or following up on message transmission).

[0071] According to embodiments of this disclosure, a method can be provided for a proxy device to encapsulate the attributes of the original device into a proxy transmission, so that the connected device can identify whether the received attributes come from the proxy device or the original device, and can also directly transmit follow-up messages to the original device.

[0072] When a connected device receives an SDF containing information about a service of interest, it may want to respond with a follow-up message. Typically, the connected device can use the address present in the header field of the incoming SDF to determine the destination of the follow-up message. However, in cases where a proxy device is used to send attributes on behalf of the originating device, the address present in the header field of the incoming SDF may include the proxy device's address instead of the originating device's address. If the connected device performs a follow-up addressing on that address, the originating device will not receive the message correctly. Therefore, the connected device may need the correct address of the originating device and may need the ability to identify whether the message originated indirectly through a proxy device or directly from the originating device.

[0073] In some embodiments, the proxy device may provide the connected device with one or more pieces of information embedded in the transmitted SDF to indicate the proxy's transmission and allow the connected device to connect to the originating device. Specifically, the proxy device may provide an indication that some or all of the SDF and the attributes included within it are sent to the connected device via the proxy. The proxy device may also provide a method for the connected device to determine the source address of each attribute.

[0074] In some implementations, the proxy device may add meta-attributes to encapsulate information into the SDF, including indications of whether the SDF is being sent via a proxy and / or address information of the originating device. In some embodiments, including the meta-attributes themselves within the SDF attribute list may be an indication that the SDF includes attributes of the proxy. In some implementations, the meta-attributes may also include information about which other attributes in the SDF are being sent by the proxy device and from which originating device they originate.

[0075] Figure 6 A flowchart illustrating an example operational process by which a proxy device generates an SDF with Attached Meta Service Descriptor (SDA) attributes, according to an embodiment, is shown. While one or more operations are described or illustrated in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods. Figure 6 The flowchart depicted in the diagram illustrates the process in agent devices (such as...) Figure 5 The operations performed in the proxy device shown are as follows. Specifically, when one or more attributes received are intended for use in proxy transmission, the proxy device may include one or more attributes of the original device into its own SDF and attach proxy meta SDA attributes before transmitting the SDF. Process 600 begins in operation 601.

[0076] In Operation 601, the agent device receives the first SDF from the originator device.

[0077] In operation 603, the proxy device generates a second SDF that includes one or more attributes from the first SDF of the originating device. In some embodiments, the attributes included in the second SDF may include those attributes to be transmitted by the proxy, which may be configured during setup between the originating device and the proxy device.

[0078] In operation 605, the proxy device attaches a proxy metadata SDA to a second SDF. In some embodiments, the proxy metadata SDA may include the SDF and an indication that one or more attributes included in the SDF are being sent to the connected device via the proxy. In some embodiments, the proxy metadata SDA may include address information of the originating device associated with one or more attributes, thereby providing the connected device with a way to determine the originating address of each attribute.

[0079] In Operation 607, the agent device sends a second SDF.

[0080] Figure 7A flowchart illustrating an example process of connecting a device upon receiving an SDF, according to an embodiment, is shown. Although one or more operations are described or illustrated in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods. Figure 7 The flowchart depicted in the diagram illustrates the connection of devices (such as...) Figure 5 The operation performed in the connected device shown in the diagram. Process 700 begins in operation 701.

[0081] In Operation 701, the connected device receives an SDF.

[0082] In operation 703, the connecting device determines whether the SDF includes a proxy metadata SDA. Specifically, when receiving the SDF, the connecting device may first need to evaluate whether each attribute was sent via a proxy. Including a proxy metadata SDA in the received SDF can indicate that one or more attributes were sent via a proxy.

[0083] In operation 703, if a proxy metadata SDA is included, the process proceeds to operation 705, where the connected device parses (or extracts) the proxy metadata SDAs of one or more NAN management interfaces (NMIs) of the originating device, along with a list of attributes corresponding to each NMI. In this way, the connected device can determine which attributes originate from which devices.

[0084] In operation 707, the connected device performs standard NAN operation. If, in operation 703, the connected device determines that the SDF does not include the agent element SDA, the process proceeds to operation 707.

[0085] Figure 8 An exemplary communication between an original device, a proxy device, and a connecting device according to an embodiment is illustrated. Specifically, the original device has an NMI address “AA-AA-AA-AA-AA-AA”, the proxy device has an NMI address “BB-BB-BB-BB-BB-BB”, and the connecting device has an NMI address “CC-CC-CC-CC-CC-CC”. Figure 8 The various communications during the four different discovery windows (DW) are shown.

[0086] As described, the originating device broadcasts 805 during the first discovery window (DW) 801 an SDF 803 with a published SDA for service_A, shown as “SDA{Publish,service_A}”. In this example, the SDA and associated attribute 2… attribute_n are intended to be proxied by the proxy device. The proxy device creates SDF 8011, which includes the originating device's SDA and attribute_2… attribute_n, as well as a new meta-attribute, the proxy meta-SDA, shown as “SDA{proxy_meta}” in SDF 811, and begins repeatedly transmitting SDF 811, including sending SDF 807 during DW 809 and SDF 813 during DW 815. In some embodiments, the proxy meta SDA may include address information of the originating device associated with one or more attributes (e.g., NMI: AA-AA-AA-AA-AA-AA), thereby providing the connected device with a way to determine the source address of each attribute.

[0087] The connected device does not receive SDF transmission 807 during DW 809, but receives SDF transmission 813 during DW 815, identifies the proxy meta SDA, and extracts the original device NMI and related attributes of the service_a SDA. Then, the connected device sends a follow-up transmission 817 of SDF 819 during DW 821 to address service_a to the original device (i.e., NMI A1: AA-AA-AA-AA-AA-AA) instead of the proxy device.

[0088] In some embodiments, the proxy metadata SDA itself may conform to a standardized SDA format. In some embodiments, the distinguishing features of the proxy metadata SDA may lie in the service ID field and the service information field, such as... Figure 9 As shown in the embodiment.

[0089] Figure 9The layout of the proxy meta SDA fields according to an embodiment is shown. As illustrated, the proxy meta SDA may include a service ID field, a service information field, and one or more other fields that may conform to a standard SDA format. The service ID field may be based on a unique service name and may be used to identify the SDF as including attributes of the proxy. In some embodiments, the service ID should be a unique bit sequence that can be used to identify the SDF as including attributes of the proxy. The service ID may also indicate to the receiving device that the service information field may need to be parsed differently than a typical SDA. For example, instead of blindly passing the service information field to the application layer, the firmware may need to parse the service information field of the proxy meta SDA itself to resolve potential follow-up message delivery addressing or adjust discovery event triggering criteria, and other operations. The service information field may include one or more origin devices (e.g., origin device #1 to origin device #n), and each origin device may include metadata including a device NMI address and an index of associated attributes. Specifically, for each origin device that sends attributes of the proxy through the proxy device, there may be an NMI address of the origin device and an indication of the associated attributes. The indication of associated attributes may be implemented using various techniques, including but not limited to binary bitmaps of all attributes in the SDF, and other techniques.

[0090] In some embodiments, instead of using SDA attributes, an attribute may be defined and used to store metadata about one or more origin device addresses and associated attributes. This attribute may be referred to herein as a Proxy Meta Attribute (PMA). In some embodiments, the PMA may follow the standard format of NAN attributes, including a unique attribute ID field and a length field. Similar to the Proxy Meta SDA utilized according to several embodiments, the PMA may be included in a proxy device SDF that includes attributes of one or more proxies. The PMA may include a structure for storing various information about each origin device carried by the proxy device's SDF, such as information about the origin device's NMI address and indications of attributes associated with the origin device.

[0091] Figure 10 A flowchart illustrating an exemplary process of proxying device operations upon receiving an SDF from the originating device, according to an embodiment, is shown. Although one or more operations are described or illustrated in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods. Figure 10 The flowchart depicted in the diagram illustrates the process in agent devices (such as...) Figure 5 The operations performed in the agent device shown.

[0092] Specifically, when one or more attributes for proxy transmission are received, the proxy device can include the attributes of the original device in its own SDF and attach a PMA containing metadata related to these attributes before transmitting the SDF.

[0093] Process 1000 begins in operation 1001. In operation 1001, the agent device receives the first SDF from the originator device.

[0094] In operation 1003, the proxy device generates a second SDF that includes one or more attributes from the first SDF of the originating device. In some implementations, the attributes included in the second SDF may include those attributes to be transmitted by the proxy, which may be configured during setup between the originating device and the proxy device.

[0095] In operation 1005, the proxy device attaches proxy meta attributes to the second SDF. In some embodiments, the proxy meta attributes may include the SDF and an indication that one or more attributes included within the SDF are being sent to the connected device via the proxy. In some embodiments, the proxy meta attributes may include address information of the originating device associated with the various attributes, thereby providing the connected device with a means to determine the originating address of each attribute.

[0096] Figure 11 A flowchart illustrating an example process of connecting a device upon receiving an SDF, according to an embodiment, is shown. Although one or more operations are described or illustrated in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods. Figure 11 The flowchart depicted illustrates the connection of devices (such as...) Figure 5 The operations performed in the connected device shown in the figure.

[0097] This process may resemble several embodiments that may use a “proxy meta” SDA, but a PMA can replace the “proxy meta” SDA and can be used to identify the SDF including attributes sent through the proxy and to encapsulate metadata about each originating device with proxy attributes in the proxy device’s SDF. Process 1100 begins in operation 1101.

[0098] In operation 1101, the connected device receives an SDF.

[0099] In operation 1103, the connecting device determines whether the SDF includes proxy meta attributes. Specifically, when receiving the SDF, the connecting device may first need to evaluate whether each attribute was sent via a proxy. Including proxy meta attributes in the received SDF can indicate that one or more attributes were sent via a proxy.

[0100] In operation 1103, if proxy meta attributes are included, the process proceeds to operation 1105, where the connected device parses (or extracts) one or more proxy meta attributes of the NMI, as well as attributes from the included originating devices. In this way, the connected device can know which attributes originate from which devices.

[0101] In operation 1107, the connecting device performs standard NAN operation. If, in operation 1103, the connecting device determines that the SDF does not include agent meta attributes, then processing proceeds to operation 1107.

[0102] Figure 12 An exemplary communication between an original device, a proxy device, and a connecting device according to one embodiment is illustrated. This communication example is similar to... Figure 8 However, SDF includes proxy meta attributes instead of proxy meta SDA. Specifically, the originator device has the NMI address "AA-AA-AA-AA-AA-AA", the proxy device has the NMI address "BB-BB-BB-BB-BB-BB", and the connected device has the NMI address "CC-CC-CC-CC-CC-CC".

[0103] As shown, the originating device broadcasts SDF 1203 1205 during DW 1201 with the published SDA of service_A, shown as “SDA{Publish, service_A}”. In this example, the SDA and associated Attribute2…Attribute_n are intended to be proxied by the proxy device. The proxy device creates SDF 1209, which includes the originating device's SDA and Attribute_2…Attribute_n, as well as the proxy meta-attribute (PMA) (illustrated as “PMA”), and begins repeatedly transmitting SDF 1209, including SDF transmission 1207 during DW 1211 and SDF transmission 1213 during DW 1215. The connected device does not receive SDF transmission 1207 during DW 1211, but receives SDF transmission 1213 during DW 1215, identifies the proxy meta-attribute, and extracts the originating device NMI and associated attributes of the service_a SDA. During DW 1219, the connected device then transmits 1217 a follow-up SDF 1221 that addresses the original device (i.e., with NMI A1: AA-AA-AA-AA-AA-AA) to the non-proxy device's SDA (follow-up, service_A).

[0104] According to embodiments of this disclosure, a proxy device may be provided that can send publish and / or subscribe messages on behalf of one or more other original devices, which can improve channel congestion, thereby allowing multiple devices to use a single proxy to send messages. Further benefits may include allowing original devices to save power by using the resources of the proxy device to periodically send messages on their behalf.

[0105] Unless otherwise specified, references to singular elements are not intended to indicate one and only one, but rather one or more. For example, a “one” module can refer to one or more modules. In the absence of further constraints, elements preceded by “a,” “an,” “the,” or “the” do not preclude the presence of additional identical elements.

[0106] Titles and subtitles (if any) are used for convenience only and do not limit the invention. The terms "exemplary" are used to indicate that they are intended as examples or illustrations. Within the scope of the use of terms such as "comprising," "having," etc., such terms are intended to be inclusive in a manner similar to the term "comprising," as "comprising" is interpreted when used as a transitional word in the claims. Relational terms such as "first" and "second" may be used to distinguish one entity or action from another without necessarily requiring or implying any actual such relationship or order between these entities or actions.

[0107] Phrases such as aspect, that aspect, on the other hand, some aspects, one or more aspects, implementation, that implementation, another implementation, some implementations, one or more implementations, embodiment, that embodiment, another embodiment, some embodiments, one or more embodiments, configuration, that configuration, another configuration, some configurations, one or more configurations, subject matter, disclosure, this disclosure, other variations thereof, etc., are used for convenience and do not imply that disclosures associated with such phrases are essential to the subject matter, or that such disclosures apply to all configurations of the subject matter. Disclosures associated with such phrases may apply to all configurations or one or more configurations. Disclosures associated with such phrases may provide one or more examples. Phrases such as aspect or some aspects may refer to one or more aspects, and vice versa, and this similarly applies to other foregoing phrases.

[0108] The phrase "at least one" preceding a series of items, separated by the terms "and" or "or," modifies the list as a whole, rather than each member of the list. The phrase "at least one of..." does not require the selection of at least one item; rather, it allows for the inclusion of at least one of any one item, and / or at least one of any combination of items, and / or at least one of each item. For example, each of the phrases "at least one of A, B, and C" or "at least one of A, B, or C" refers to only A, only B, or only C; any combination of A, B, and C; and / or at least one of each of A, B, and C.

[0109] As described herein, any electronic device and / or part thereof according to any example embodiment may include, be included in, and / or be implemented by one or more processors and / or combinations of processors. A processor is a circuit that performs processing.

[0110] A processor may include processing circuitry, which may more specifically include, but is not limited to, a central processing unit (CPU), an MPU, a system-on-a-chip (SoC), an integrated circuit (IC), an arithmetic logic unit (ALU), a graphics processing unit (GPU), an application processor (AP), a digital signal processor (DSP), a microcomputer, a field-programmable gate array (FPGA) and programmable logic unit, a microprocessor, an application-specific integrated circuit (ASIC), a neural network processing unit (NPU), an electronic control unit (ECU), an image signal processor (ISP), etc. In some example embodiments, the processing circuitry may include: a non-transitory computer-readable storage device (e.g., memory), such as a DRAM device, storing a program of instructions; and a processor (e.g., a CPU) configured to execute the program of instructions to implement all or some of the functions and / or methods performed by any means, system, module, unit, controller, circuit, architecture, and / or portions thereof according to any example embodiment and / or any part of any example embodiment. Instructions may be stored in memory and / or partitioned among multiple memories.

[0111] Different processors can execute different functions and / or parts of functions. For example, processor 1 can execute functions A and B, and processor 2 can execute function C; or processor 1 can execute a portion of function A, while processor 2 can execute the remainder of function A, and also execute functions B and C. Different processors can be dynamically configured to execute different processes. For example, at one time, processor 1 can execute function A, and at another time, processor 2 can execute function A. Processors can reside on different processing circuits (e.g., client-side processors and server-side processors, device-side processors and cloud computing processors, etc.).

[0112] It should be understood that the specific order or hierarchy of the disclosed steps, operations, or processes is an illustration of exemplary methods. Unless otherwise expressly stated, it should be understood that the specific order or hierarchy of steps, operations, or processes may be performed in a different order. Some steps, operations, or processes may be performed simultaneously, or may be performed as part of one or more other steps, operations, or processes. The appended method claims (if any) present elements of various steps, operations, or processes in a sample order, but this does not imply limitation to the specific order or hierarchy presented. These may be performed serially, linearly, in parallel, or in different orders. It should be understood that the described instructions, operations, and systems can generally be integrated together in a single software / hardware product or packaged into multiple software / hardware products.

[0113] This disclosure is provided to enable any person skilled in the art to practice the various aspects described herein. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring the concept of the subject matter. This disclosure provides various examples of the subject matter, and the subject matter is not limited to these examples. Various modifications to these aspects will be apparent to those skilled in the art, and the principles described herein can be applied to other aspects.

[0114] All structural and functional equivalents of the various aspects described throughout this disclosure, which are now or hereafter known to a person skilled in the art, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. No claim element is to be interpreted pursuant to paragraph 6 of §112 unless it is expressly stated using the phrase “means for…” or, in the case of a method claim, using the phrase “steps for…”.

[0115] The title, background information, description of the drawings, abstract, and figures are incorporated herein by reference and are provided as illustrative examples rather than as limiting descriptions. It should be understood at the time of filing that they are not intended to limit the scope or meaning of the claims. Furthermore, in the detailed description, it will become apparent that the description provides illustrative examples and that various features are combined in various embodiments for the purpose of simplifying the disclosure. The approach of this disclosure should not be construed as reflecting an intention to require more features than expressly recited in each claim. Rather, as reflected in the following claims, the inventive subject matter lies in all features of fewer than those in a single disclosure configuration or operation. The appended claims are incorporated herein by reference, wherein each claim is independently claimed as a separate subject matter.

[0116] The claims are not intended to be limited to the aspects described herein, but rather to conform to the full scope consistent with the language claims and to include all legal equivalents. Nevertheless, no claim is intended to include subject matter that does not meet the requirements of applicable patent law, nor should they be interpreted in this manner.

Claims

1. A station (STA) in a wireless network, the STA comprising: Memory; and A processor coupled to memory, the processor being configured to: Receive a first discovery frame from the original STA. The first discovery frame includes one or more attributes intended for use in proxy transport. A second discovery frame is generated, comprising one or more attributes intended for proxy transmission based on the first discovery frame and appended with additional information, wherein the additional information includes one or more attributes associated with the original STA and an indication that one or more attributes are being transmitted via proxy transmission, and wherein the additional information includes the address information of the original STA; and Send a second discovery frame to one or more other STAs.

2. The STA according to claim 1, wherein, The second discovery frame includes one or more attributes associated with different original STAs, as well as address information of the different original STAs associated with one or more attributes.

3. The STA according to claim 1, wherein, The second discovery frame includes one or more different original STAs, the associated address information of each of the one or more different original STAs, and one or more indexes associated with a corresponding original STA among the one or more different original STAs.

4. The STA according to claim 1, wherein, The second discovery frame has a unique service identifier for identifying the second discovery frame as having an agent attribute.

5. The STA according to claim 1, wherein, The second discovery frame includes attributes that store additional information, including indications of one or more attributes associated with the original STA and the address information of the original STA.

6. The STA according to claim 1, wherein, The processor is also configured to repeatedly send a second discovery frame to one or more STAs.

7. The STA according to claim 1, wherein, The attribute in one or more of the attributes is associated with a service provided by the original STA to one or more other STAs or a service sought by the original STA from one or more other STAs.

8. A station (STA) in a wireless network, the STA comprising: Memory; and A processor coupled to the memory, the processor being configured to: A first discovery frame is received from the proxy STA, comprising one or more attributes and additional information, wherein the additional information includes an indication that one or more attributes are associated with the original STA and that one or more attributes are being transmitted via the proxy, and wherein the additional information includes the address information of the original STA; and Based on the first discovery frame, the address information of the original STA and one or more attributes associated with the original STA are obtained from the supplementary information; and The second frame is sent to the original STA using the address information.

9. The STA according to claim 8, wherein, The first discovery frame includes one or more attributes associated with different original STAs and address information of the different original STAs associated with one or more attributes.

10. The STA according to claim 8, wherein, The additional information includes one or more different original STAs, the associated address information of each original STA in the one or more different original STAs, and one or more indexes associated with a corresponding original STA in the one or more different original STAs.

11. The STA according to claim 8, wherein, The first discovery frame has a unique service identifier for identifying the first discovery frame as having additional information.

12. The STA according to claim 8, wherein, The first discovery frame includes attributes that store additional information, including indications of one or more attributes associated with the original STA and the address information of the original STA.

13. The STA according to claim 8, wherein, The attribute in one or more of the attributes is associated with a service provided by the original STA to one or more other STAs or a service sought by the original STA from one or more other STAs.

14. A computer-implemented method for communication by a station (STA) in a wireless network, comprising: Receive a first discovery frame from the original STA. The first discovery frame includes one or more attributes intended for use in proxy transport. A second discovery frame is generated, comprising one or more attributes intended for proxy transmission based on the first discovery frame and appended with additional information, wherein the additional information includes one or more attributes associated with the original STA and an indication that one or more attributes are being transmitted via proxy transmission, and wherein the additional information includes the address information of the original STA; and Send a second discovery frame to one or more other STAs.

15. The computer-implemented method according to claim 14, wherein, The second discovery frame includes one or more attributes associated with different original STAs and address information of the different original STAs associated with one or more attributes.

Images