Channel announcement in wireless communication system

Abstract

A wireless communication network includes an access point (AP) device and a non-AP device. The AP device may advertisement frames indicating recommended channels for peer-to-peer communications. The non-AP device may perform peer-to-peer communications with one or more other non-AP devices using the recommended channel. The frame may be a beacon frame or a detection response frame.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication systems, and more particularly, to channel announcements in wireless communication systems, such as but not limited to. Background Art

[0002] Since the late 1990s, wireless local area network (WLAN) technology has been evolving towards higher data rates and continues to grow in various markets such as homes, enterprises, and hotspots. WLAN allows devices to access the Internet in the 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. The IEEE 802.11 standard family aims to improve speed and reliability and extend the operating range of wireless networks.

[0003] WLAN devices are increasingly required to support various latency-sensitive applications 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 by these applications, multi-link operation (MLO) has been proposed for WLAN. A WLAN is formed by WLAN devices in a limited area such as a home, school, apartment, or office building. Each WLAN device may have one or more stations (STAs), such as an access point (AP) STA and a non-access point (non-AP) STA.

[0004] MLO can enable a non-AP multi-link device (MLD) to establish multiple links with an AP MLD. Each of the multiple links can independently achieve channel access and frame exchange between the non-AP MLD and the AP MLD, which can reduce latency and increase throughput.

[0005] The descriptions set forth in the background art section should not be considered prior art merely because they are set forth in the background art section. The background section may describe aspects or embodiments of the present disclosure. Summary of the Invention

[0006] Solution to the Problem

[0007] One aspect of the present disclosure provides an AP device in a wireless network. The AP device includes a transceiver, a memory, and a processor coupled to the memory. The processor is configured to generate a frame indicating one or more recommended channels for peer communication. The processor is configured to control the transceiver to send the frame to one or more non-AP devices.

[0008] In some embodiments, the frame is a beacon frame or a probe response frame.

[0009] In some embodiments, the frame includes channel usage elements for one or more recommended channels.

[0010] In some embodiments, the channel usage element includes a usage pattern field indicating the usage of one or more recommended channels.

[0011] In some embodiments, the channel usage element includes a channel field indicating one or more channel numbers of one or more recommended channels and an operation class field indicating one or more operation classes of one or more recommended channels.

[0012] In some embodiments, one or more non-AP devices include at least one non-AP device not associated with the AP device.

[0013] In some embodiments, the frame includes a power constraint element indicating the maximum transmit power of the receiving non-AP device.

[0014] In some embodiments, the frame includes an EDCA parameter set element indicating Enhanced Distributed Channel Access (EDCA) parameters for receiving transmissions of non-AP devices.

[0015] In some embodiments, one or more recommended channels are within the channel set of the AP device for an infrastructure basic service set.

[0016] In some embodiments, one or more recommended channels are outside the channel set of the AP device for an infrastructure basic service set.

[0017] One aspect of the present disclosure provides a non-AP device in a wireless network. The non-AP device includes a transceiver, a memory, and a processor coupled to the memory. The processor is configured to control the transceiver to receive a frame from an AP device indicating one or more recommended channels for peer-to-peer communication. The processor is configured to select a channel from the one or more recommended channels for peer-to-peer communication based on the received frame. The processor is configured to perform peer-to-peer communication with one or more non-AP devices on the selected channel.

[0018] In some embodiments, the frame is a beacon frame or a probe response frame.

[0019] In some embodiments, the frame includes channel usage elements for one or more recommended channels.

[0020] In some embodiments, the channel usage element includes a usage pattern field indicating the usage of one or more recommended channels.

[0021] In some embodiments, the channel usage element includes a channel field indicating one or more channel numbers of one or more recommended channels and an operating class field indicating one or more operating classes of one or more recommended channels.

[0022] In some embodiments, the AP device is not associated with the non-AP device.

[0023] In some embodiments, the frame includes a power constraint element, and the processor is further configured to determine the maximum transmit power based on the power constraint element.

[0024] In some embodiments, the frame includes an Enhanced Distributed Channel Access (EDCA) parameter set element, and the processor is further configured to determine the EDCA parameters for transmission based on the EDCA parameter set element.

[0025] In some embodiments, one or more recommended channels are within the channel set used by the AP device for the infrastructure basic service set.

[0026] In some embodiments, one or more recommended channels are outside the channel set used by the AP device for the infrastructure basic service set. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 Shows an example of a wireless network according to an embodiment.

[0028] Figure 2A Shows an example of an AP according to an embodiment.

[0029] Figure 2B Shows an example of a STA according to an embodiment.

[0030] Figure 3 Shows an example of multi-link communication operation according to an embodiment.

[0031] Figure 4 Shows an example network according to an embodiment.

[0032] Figure 5 Shows an example of a recommended P2P channel according to an embodiment.

[0033] Figure 6 Shows another example of a recommended P2P channel according to an embodiment.

[0034] Figure 7 Shows an example of a recommended P2P channel usage information element according to an embodiment.

[0035] Figure 8 Shows another example format of the channel information field in the channel usage information subelement according to an embodiment.

[0036] Figure 9 A flowchart showing an example process for channel recommendation according to an embodiment.

[0037] Figure 10 A flowchart showing an example process for channel recommendation according to an embodiment.

[0038] Figure 11 A flowchart showing an example process of a channel recommendation process according to an embodiment.

[0039] Figure 12 Another example of a recommended P2P channel usage information element according to an embodiment is shown.

[0040] Figure 13 Another example of a recommended P2P channel usage information element according to an embodiment is shown.

[0041] Figure 14 and Figure 15 Another example of a recommended P2P channel usage information element according to an embodiment is shown.

[0042] Figure 16 Another example of a recommended P2P channel usage information element according to an embodiment is shown.

[0043] In one or more implementations, it may not be necessary to have all the components depicted in each figure, and one or more implementations may include additional components not shown in the figures. Without departing from the scope of the present subject matter disclosure, the arrangement and type of components may vary. Within the scope of the present subject matter disclosure, additional components, different components, or fewer components may be used. Detailed Description

[0044] The following detailed description given in conjunction with the accompanying drawings is intended as a description of various implementations and is not intended to represent the only implementations in which the subject matter technology can be practiced. On the contrary, the detailed description includes specific details for the purpose of providing a thorough understanding of the inventive subject matter. As will be recognized by those skilled in the art, the described implementations can be modified in various ways, all without departing from the scope of the present disclosure. Accordingly, the drawings and description are to be regarded as illustrative rather than restrictive. Like reference numerals denote like elements.

[0045] For purposes of describing innovative aspects of the present disclosure, the following description is directed to certain implementations. However, those of ordinary skill in the art will readily recognize that the teachings herein can be applied in many different ways. The examples in the present disclosure are based on WLAN communication according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, including the IEEE 802.11be standard and any future revisions to the IEEE 802.11 standards. 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 standards, Bluetooth standards, Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband CDMA (W-CDMA), Evolution-Data Optimized (EV-DO), 1xEV-DO, EV-DO Release A, EV-DO Release 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 New Radio (NR), AMPS, or other known signals for communication within a wireless, cellular, or Internet of Things (IoT) network (such as a system utilizing 3G technology, 4G technology, 5G technology, 6G technology, or further implementations thereof).

[0046] Depending on the network type, other well-known terms (such as "router" or "gateway") can be used instead of "access point" or "AP". For convenience, the term "AP" is used in the present disclosure to refer to the network infrastructure component that provides wireless access to remote terminals. In a WLAN, assuming that the AP also competes for the wireless channel, the AP can also be referred to as a STA. Additionally, depending on the network type, other well-known terms (such as "mobile station", "subscriber station", "remote terminal", "user equipment", "wireless terminal", or "user device") can be used instead of "station" or "STA". For convenience, the terms "station" and "STA" are used in the present disclosure to refer to a remote wireless device that wirelessly accesses an AP or competes for the wireless channel in a WLAN, regardless of 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.).

[0047] Multi-Link Operation (MLO) is a key feature currently being developed by standard organizations in IEEE 802.11be for next-generation Extremely High Throughput (EHT) Wi-Fi systems. Wi-Fi devices that support MLO are called Multi-Link Devices (MLDs). With MLO, non-AP MLDs can discover, authenticate, associate, and establish multiple links with AP MLDs. Channel access and frame exchange are possible on each link between an AP MLD and a non-AP MLD.

[0048] 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 the present disclosure.

[0049] As Figure 1 shown, the 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 an individually addressable instance of the Media Access Control (MAC) layer and Physical (PHY) layer interfaces to 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 distributed system services for associated STAs via the wireless medium. A non-AP STA may be an STA that is not included within an AP-STA. For simplicity of description, an AP STA may be referred to as an AP, and a non-AP STA may be referred to as an STA. In Figure 1 the example, APs 101 and 103 are wireless communication devices, and each wireless communication device may include one or more AP STAs. In such an embodiment, APs 101 and 103 may be AP Multi-Link Devices (MLDs). Similarly, STAs 111 - 114 are wireless communication devices, and each wireless communication device may include one or more non-AP STAs. In such an embodiment, STAs 111 - 114 may be non-AP MLDs.

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

[0051] Depending on the network type, other well-known terms (such as "router" or "gateway") may be used instead of "access point" or "AP". 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 competes for the wireless channel, the AP can also be referred to as a STA. Additionally, depending on the network type, other well-known terms (such as "mobile station", "subscriber station", "remote terminal", "user equipment", "wireless terminal", or "user device") may be used instead of "station" or "STA". For convenience, the terms "station" and "STA" are used in this disclosure to refer to a remote wireless device that wirelessly accesses an AP or competes for the 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.).

[0052] In Figure 1 it, the dashed lines illustrate the approximate extents of the coverage areas 120 and 125 of APs 101 and 103, which are shown as approximately circular for purposes of illustration and explanation. It should be clearly understood that depending on the configuration of the AP, the coverage area associated with the AP (such as coverage areas 120 and 125) can have other shapes, including irregular shapes.

[0053] As described in more detail below, one or more of the APs can include circuitry and / or programs for managing multi-user multiple-input multiple-output (MU-MIMO) and orthogonal frequency-division multiple access (OFDMA) channel sounding in a WLAN. Although Figure 1 shows an example of a wireless network 100, various changes can be made to Figure 1 it. For example, the wireless network 100 can include any number of APs and any number of STAs in any suitable arrangement. Additionally, AP 101 can communicate directly with any number of STAs and provide wireless broadband access to the network 130 to these STAs. Similarly, each of APs 101 and 103 can communicate directly with the network 130 and provide direct wireless broadband access to the network 130 to the STAs. Further, AP 101 and / or 103 can provide access to other or additional external networks (such as an external telephone network or other types of data networks).

[0054] Figure 2A shows an example of AP 101 according to an embodiment. Figure 2A The illustrated embodiment of AP 101 is for purposes of illustration, and Figure 1 AP 103 can have the same or similar configuration. However, APs have a wide variety of configurations, and Figure 2AThe scope of the present disclosure is not limited to any particular implementation of the AP.

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

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

[0057] 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 well-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 the outgoing signals in a desired direction. The controller / processor 224 may also support OFDMA operations, where outgoing signals are assigned to different subsets of subcarriers for different recipients (e.g., different STAs 111 - 114). In the AP 101, the controller / processor 224 may support any one of a variety of other functions, including a combination of DLMU - 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 residing in the memory 229, such as the OS. The controller / processor 224 may move data into or out of the memory 229 as needed for the processes being executed.

[0058] 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 via a network. The interface 234 may support communication via any suitable wired or wireless connection. For example, the interface 234 may allow the AP 101 to communicate via a wired or wireless local area network or via a wired or wireless connection to a larger network, such as the Internet. The interface 234 may include any suitable structure that supports communication via a wired or wireless connection, such as Ethernet or an RF transceiver. The memory 229 is coupled to the controller / processor 224. A portion of the memory 229 may include random access memory (RAM), while another portion of the memory 229 may include flash memory or other read-only memory (ROM).

[0059] As described in more detail below, the AP 101 may include circuitry and / or programming for managing the channel sounding process in a WLAN. Although Figure 2A one example of the AP 101 is shown, various changes may be made to Figure 2A it. For example, the AP 101 may include any number of Figure 2AEach of the components shown. As a specific example, the AP can include multiple interfaces 234, and the controller / processor 224 can support routing functions to route data between different network addresses. As another example, although shown as including a single instance of the TX processing circuit 214 and a single instance of the RX processing circuit 219, the AP 101 can include multiple instances of each component (such as one for each RF transceiver). Alternatively, as in a traditional AP, only one antenna and one RF transceiver path may be included. Additionally, Figure 2A The various components in

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

[0061] Figure 2B An example of the STA 111 according to an embodiment is shown. Figure 2B The embodiment of the STA 111 shown is for illustrative purposes, and Figure 1 the STAs 111 - 114 Figure 2B may have the same or similar configurations. However, STAs have a wide variety of configurations, and

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

[0063] The RF transceiver 210 receives an incoming RF signal transmitted by the AP of the network 100 from the antenna 205. The RF transceiver 210 down-converts the incoming RF signal to generate an IF or baseband signal. The IF or baseband signal is sent to the RX processing circuit 225, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuit 225 sends the processed baseband signal to the speaker 230 (such as for voice data) or the controller / processor 240 for further processing (such as for web browsing data).

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

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

[0066] 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 a WLAN. The controller / processor 240 can move data into or out of the memory 260 as needed by the processes being executed. In some embodiments, the controller / processor 240 is configured to execute multiple applications 262, such as an application for channel sounding, which includes feedback calculations based on received null data packet announcements (NDPAs) and null data packets (NDPs), and transmitting a beamforming feedback report in response to a trigger frame (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.

[0067] The controller / processor 240 is also coupled to an input 250 (such as a touch screen) and a display 255. An operator of the STA 111 can use the input 250 to input data into the STA 111. The display 255 can be a liquid crystal display, a light-emitting diode display, or other display capable of rendering text and / or at least limited graphics (such as from a website). The memory 260 is coupled to the controller / processor 240. A portion of the memory 260 can include RAM, while another portion of the memory 260 can include flash memory or other ROM.

[0068] Although Figure 2B an example of the STA 111 is shown, various changes can be made to Figure 2B it. For example, Figure 2B the various components in Figure 2B can be combined, further subdivided, or omitted, and additional components can be added according to specific needs. In a particular example, the STA 111 can include any number of antennas 205 for MIMO communication with the AP 101. In another example, the STA 111 may not include voice communication, or the controller / processor 240 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Additionally, although

[0069] as Figure 2BAs shown, in some embodiments, the STA 111 may be a non-AP MLD including multiple STAs 203a - 203n. Each of the STAs 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 of the STAs 203a - 203n may communicate independently with the controller / processor 240 and other components of the non-AP MLD 111. Figure 2B It is shown that each of the STAs 203a - 203n has a separate antenna, but each of the STAs 203a - 203n may share the antenna 205 without the need for a separate antenna. Each of the STAs 203a - 203n may represent the physical (PHY) layer and the lower media access control (MAC) layer.

[0070] Figure 3 An example of multi-link communication operation according to an embodiment is shown. The multi-link communication operation may be used for the IEEE 802.11be standard and any future revisions to the IEEE 802.11 standard. In Figure 3 the AP MLD 310 may be Figure 1 the wireless communication devices 101 and 103 in Figure 1 and the non-AP MLD 220 may be one of the wireless communication devices 111 - 114 in

[0071] As Figure 3 shown, the AP MLD 310 may include multiple attached APs, for example, including AP 1, AP 2, and AP 3. Each attached AP may include a PHY interface (link 1, link 2, or link 3) to the wireless medium. The AP MLD 310 may include a single MAC service access point (SAP) 318 through which the attached APs of the AP MLD 310 communicate with the higher layer (layer 3 or network layer). Each attached AP of the AP MLD 310 may have a MAC address (lower MAC address) different from any other attached AP of the AP MLD 310. The AP MLD 310 may have an MLD MAC address (upper MAC address), and the attached APs share a single MAC SAP 318 to layer 3. Thus, the attached APs share a single IP address, and layer 3 identifies the AP MLD 310 by assigning a single IP address.

[0072] The non - AP MLD 320 may include multiple associated STAs. For example, it includes STA 1, STA 2, and STA 3. Each associated STA may include a PHY interface (Link 1, Link 2, or Link 3) to the wireless medium. The non - AP MLD 320 may include a single MAC SAP 328 through which the associated STAs of the non - AP MLD 320 communicate with the higher layer (Layer 3 or the network layer). Each associated STA of the non - AP MLD 320 may have a MAC address (lower - layer MAC address) different from any other associated STA of the non - AP MLD 320. The non - AP MLD 320 may have an MLD MAC address (upper - layer MAC address), and the associated STAs share the single MAC SAP 328 to Layer 3. Thus, the associated STAs share a single IP address, and Layer 3 identifies the non - AP MLD 320 by assigning a single IP address.

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

[0074] Figure 4 An example network according to an embodiment is shown. Figure 4 The network depicted is for purposes of explanation and illustration. Figure 4 It does not limit the scope of the present disclosure to any particular implementation.

[0075] In Figure 4 STA 410 is a non - AP station associated with AP 430, and STA 420 is a non - AP station not associated with AP 430. In addition, the solid lines between the stations represent the uplink or downlink to AP 430, while the dashed lines between the stations represent direct links.

[0076] Next-generation WLAN systems need to provide better support for low-latency applications. Nowadays, it is not uncommon to have a large number of devices operating on the same network. Multiple of these devices can tolerate latency, but still compete or contend for the same time and frequency resources as devices running low-latency applications. In some cases, within an infrastructure basic service set (BSS), the AP, which acts as a network controller, may not have sufficient control over unregulated or unmanaged traffic that contends with low-latency traffic. In some embodiments, an infrastructure BSS is a basic service set that includes one AP and one or more non-APs, while an independent BSS is a basic service set in which stations communicate with each other without the need for a centralized AP. Some unregulated or unmanaged traffic in the AP's BSS that interferes with latency-sensitive traffic may originate from uplink, downlink, or direct-link communications within the infrastructure BSS managed by the AP. Another source of interference may be transmissions from adjacent infrastructure overlapping basic service sets (OBSS), while other sources of interference may come from adjacent independent BSSs or P2P networks. Therefore, next-generation WLAN systems need mechanisms to more effectively handle unmanaged traffic when prioritizing low-latency traffic in the network. In a WLAN network, if STAs 410 and 420 use a predetermined or recommended channel for uplink, downlink, and direct-link communications within their network or an adjacent network, the management of BSS traffic can be significantly enhanced, thereby supporting latency-sensitive applications in the network. However, there is currently no mechanism to address this problem.

[0077] The present disclosure provides improved mechanisms for more efficiently managing traffic in a network. It also explains how an AP allocates and announces channels for direct-link and UL / DL communications. Such allocation can help reduce interference with low-latency traffic originating from direct-link communications and UL / DL link communications from its own BSS or OBSS.

[0078] In some embodiments, an AP may announce or advertise channels recommended for peer-to-peer (P2P) communications in its BSS. These channels can be considered more favorable for P2P communications than other available channels and may be referred to as "recommended P2P channels" or "recommended channels" in the present disclosure.

[0079] In some embodiments, by including relevant information in a beacon frame or a probe response frame, an AP can announce or advertise the recommended P2P channels in its BSS. Additionally, broadcast frames, multicast frames, or group-addressed frames can also be used to announce the recommended P2P channels.

[0080] Assign channels for P2P communication and group P2P transmissions into these recommended P2P channels, so that the AP can effectively reduce the uncontrolled interference from the channels used for infrastructure BSS operations (e.g., uplink / downlink communication). This can enable the AP to manage its network more effectively and ensure the QoS requirements for STAs within its BSS. From the perspective of the STA, it is most beneficial for STAs that plan to establish an independent BSS (e.g., a P2P group) or change the operating channel used for their P2P operations to receive relevant information about the recommended channels for P2P or independent BSS operations from the AP and use these recommended channels. Using the recommended channels can reduce interference from the infrastructure network. For example, if an STA randomly selects a channel to initiate a P2P group, that channel may overlap with one of the channels used by a nearby AP for its BSS operations. Therefore, compared with the channels recommended by the AP for P2P communication, such random channel selection will encounter significantly more interference from the infrastructure network.

[0081] In an embodiment, the AP that advertises a channel as a recommended P2P channel can ensure that the AP does not use the recommended P2P channel as an operating channel in its infrastructure BSS. This can encourage non-AP STAs participating in P2P communication to use the recommended channel because it is not used for traffic delivery in the infrastructure network.

[0082] In an embodiment, the AP that advertises a channel as a recommended P2P channel can still use the channel for traffic delivery in the infrastructure network. However, the AP may attempt to minimize transmissions on that channel. In some implementations, the AP can ensure that only trigger-enabled transmissions are allowed on the recommended channel. In some implementations, the AP can use the recommended channel for delay-sensitive traffic or priority access traffic, such as traffic related to national security or disaster management. Other applications that limit the use of the recommended channel are also possible. In an embodiment, if a channel is used for dynamic frequency selection (DFS) or radar purposes, the AP may not advertise that channel as a recommended P2P channel.

[0083] In an embodiment, when the AP advertises a channel used for DFS or radar purposes as a recommended P2P channel and a non-AP STA uses that channel for P2P communication, the non-AP STA can ensure that the P2P communication does not cause interference to DFS or radar applications. In some implementations, non-AP STAs participating in P2P communication can employ low-power communication (such as short-range communication) instead of the standard power level used for P2P communication.

[0084] In an embodiment, a recommended P2P channel may belong to a set of channels used by an AP for its infrastructure BSS operation. In the present disclosure, this P2P channel may be referred to as an "infrastructure P2P channel" or an "infra P2P channel". Although the P2P channel is part of the operating channels of the AP, during channel advertisement, the AP may not use this channel for its BSS operation. However, the AP can use this channel in a larger scope by performing a BSS channel switching operation.

[0085] In an embodiment, a recommended P2P channel may not belong to a set of channels used by the AP for its BSS operation. This P2P channel may be referred to as a "non-Infrastructure P2P channel" or a "non-Infra P2P channel". When a STA intending to participate in P2P communication uses this channel, the STA may not encounter interference from the infrastructure network.

[0086] Figure 5 An example of a recommended P2P channel according to an embodiment is shown. Figure 5 The channel types depicted are for illustrative purposes only and do not limit the scope of the present disclosure to any particular implementation of the recommended P2P channel.

[0087] In Figure 5In the example, the AP has 8 available channels from channel 1 to channel 8 in its operating link. Channels 1, 2, 5, and 8 are used for the AP's uplink (UL) and downlink (DL) communications. Channels 4 and 6 are DFS channels for special activities such as radar, defense, or weather-related activities. To minimize interference from P2P traffic on the UL / DL channels, the AP can recommend channels 3 and 7 for P2P communications. Channel 3 is for the infrastructure P2P channel. It can be assigned for P2P communications even if it is part of the AP's operating channel set. For example, a tunneled direct link setup (TDLS) peer STA can use channel 3 for TDLS channel switching, moving from the base channel to an off-channel for TDLS. In some embodiments, the off-channel can be a channel that does not overlap with the channel used by the AP to which the TDLS STA is associated, and the base channel is the primary channel of the BSS of the AP to which the TDLS STA is associated. Channel 7 is for the non-infrastructure P2P channel. This channel is not part of the AP's operating channel set. For example, an STA can use this channel to initiate a Wi-Fi direct P2P group.

[0088] In an embodiment, the AP advertising the P2P channel may not distinguish between the infrastructure P2P channel and the non-infrastructure P2P channel. The AP can simply allocate one channel intended to accommodate all P2P transmissions, regardless of whether the channel is an infrastructure P2P channel or a non-infrastructure P2P channel. This channel can be referred to as a "hybrid P2P channel".

[0089] In another embodiment, another recommended P2P channel can be defined. During the time of P2P channel advertisement, the recommended P2P channel can also be being used by the AP for its infrastructure BSS. This P2P channel can be referred to as a "coexistence P2P channel". This is particularly important for concurrent P2P devices that need to maintain an association with both the infrastructure network (e.g., for Internet connection) and the P2P group simultaneously and may prefer not to switch channels to communicate between the two networks, for example, for power saving.

[0090] Figure 6 Another example of a recommended P2P channel according to an embodiment is shown. Figure 6 The channel types depicted are for illustrative purposes only and do not limit the scope of the present disclosure to any particular implementation of the recommended P2P channel.

[0091] In Figure 6In an example, the AP has 8 available channels from channel 1 to channel 8 in its operating link. Channels 1, 2, 5, and 8 are used for the uplink (UL) and downlink (DL) communications of the AP. Channels 4 and 6 are DFS channels for special activities such as radar, defense, or weather-related activities. To minimize the interference from P2P traffic on the UL / DL channels, the AP can recommend channels 3 and 7 for P2P communications. Channel 3 is used for the hybrid P2P channel, and channel 7 is used for the coexistence P2P channel.

[0092] In an embodiment, a STA that supports this feature and receives a recommendation or advertisement from a beacon frame or a probe response frame may not use any other channels except the recommended channels. In other words, the STA can exclusively use the recommended channels and avoid using any other channels. In another embodiment, a STA that supports this feature and receives a recommendation or advertisement from a beacon frame or a probe response frame may decide to follow or ignore the recommendation. Even if the STA supports the channel recommendation feature and receives relevant and necessary information from the AP, the STA can choose to use another channel outside the recommended channel set of the AP for P2P communication.

[0093] In an embodiment, if an AP STA or a non-AP STA supports the P2P channel recommendation process described in this disclosure, it may set the dot11ChannelRecommendationSupported MIB variable to 1. Otherwise, it may set the dot11ChannelRecommendationSupported MIB variable to 0. In another embodiment, if an AP STA or a non-AP STA supports the P2P channel recommendation process described in this disclosure, it may set the channel recommendation support field in the extended capabilities element to 1. Otherwise, it may set the channel recommendation support field in the extended capabilities element to 0.

[0094] In an embodiment, an AP that supports the channel recommendation process may advertise or announce the recommended channels by including the recommended P2P channel usage information element in a beacon frame or a probe response frame.

[0095] Figure 7 An example of the recommended P2P channel usage information element according to an embodiment is shown. Figure 7 The example format depicted is for purposes of explanation and illustration. The example format does not limit the scope of this disclosure to any particular implementation.

[0096] Refer to Figure 7, the recommended P2P channel usage information element 700 may include an element ID field, a length field, and a channel usage information list field. The element ID field may include information for identifying the recommended P2P channel usage information element 700. The length field may indicate the length of the recommended P2P channel usage information element 700. The channel usage information list field may include one or more channel usage information subelements. In some embodiments, each of the channel usage information subelements may be associated with a corresponding one of the one or more recommended channels indicated by the recommended P2P channel usage information element 700. In some implementations, the number of channel usage information subelements may be the same as the number of recommended channels.

[0097] A possible form of the channel usage information subelement may include a subelement ID field, a length field, a channel information field, a country string field, a power constraint element field, an Enhanced Distributed Channel Access (EDCA) parameter set element field, a transmit power set element field, and a Timeout Interval element field.

[0098] The subelement ID field may include information for identifying the channel usage information subelement. The length field may indicate the length of the channel usage information subelement.

[0099] The channel information field may include recommended P2P channel related information. Specifically, the channel information field may include a usage mode field, an operation class field, and a channel field. The usage mode field may include information for identifying a value indicating the usage of the recommended P2P channel. Table 1 below provides an example encryption of the usage mode field. The usage mode field may be interpreted as a recommendation from the AP on how to use the recommended P2P channel. The operation class field may indicate an operation class value. The operation class may be interpreted in the context of the country specified in the beacon frame. The channel field may indicate a channel number, which may be interpreted in the context of the indicated operation class. The channel number may indicate a recommended channel for peer-to-peer communication.

[0100] [Table 1]

[0101]

[0102]

[0103] The country string field may be a value included in the dot11CountryString attribute. When receiving this subelement, the receiving STA may set the value of dot11CountryString to the value included in this field.

[0104] The power constraint element field may be optional. It may include zero or one power constraint element. The power constraint element may include information necessary to allow a receiving STA to determine its local maximum transmit power.

[0105] The EDCA parameter set element field includes zero or one EDCA parameter set element. The EDCA parameter set element may provide information required for a receiving STA to correctly operate the Quality of Service (QoS) facility during the contention period.

[0106] The transmit power envelope element field may include zero or more transmit power envelope elements. The transmit power envelope element may provide the local or specified maximum transmit power for various transmission bandwidths or channels within the bandwidth of the BSS.

[0107] The timeout interval element field may include zero or one timeout interval element. The timeout interval element may include information on the time interval and timeout. The timeout interval element may indicate the duration for which the P2P channel recommendation remains valid (as indicated in the corresponding channel usage information subelement in the recommended P2P channel usage information element).

[0108] In an embodiment, the information carried on the power constraint element field, EDCA parameter set element field, transmit power envelope element field, and timeout interval element field in the channel usage information subelement is for the receiving STA. In other words, if a STA intends to use the recommended channel in the corresponding channel usage information subelement for P2P communication, these parameters are recommended for use by the STA.

[0109] In another embodiment, the information carried on the power constraint element field, EDCA parameter set element field, transmit power envelope element field, and timeout interval element field in the channel usage information subelement is used to indicate that an AP may use these parameters for the channel indicated by the corresponding channel usage information subelement.

[0110] Figure 8 Another example format of the channel information field in the channel usage information subelement according to an embodiment is shown.

[0111] Reference Figure 8 , the channel information field may include a usage mode field, an operation class field, a channel field, and a type field. Except for the type field, Figure 8 each field in the channel information field depicted in Figure 7The corresponding fields in the channel information field depicted are the same or similar. The type field may indicate the recommended P2P channel type. Table 2 below provides an example encoding of the type field. The STA can use the type subfield as a measure of the expected interference in the advertised P2P channels. Thus, this form can help the STA decide which recommended P2P channel to select for their P2P communication.

[0112] [Table 2]

[0113] Value Information 1 Infrastructure P2P 2 Non-Infrastructure P2P 3 Hybrid P2P 4 Coexistence P2P

[0114] Figure 9 FIG. shows a flowchart of an example process for channel recommendation according to an embodiment. For purposes of explanation and illustration, example process 900 may be performed by Figure 4 AP 430. Although one or more operations are described or shown in a particular order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations during at least partially overlapping time periods.

[0115] Process 900 may begin at operation 901. In operation 901, the AP that supports the channel recommendation process may set the dot11ChannelRecommendationSupprted value to 1. Then, process 900 proceeds to operation 903.

[0116] In operation 903, the AP may determine the advertised or recommended channels to assist non-AP STAs in P2P communication in the network. In an embodiment, the AP may assist non-AP STAs in establishing a non-infrastructure channel TDLS direct link or selecting a frequency band and channel for an independent BSS or P2P group. Then, process 900 proceeds to operation 905.

[0117] In operation 905, the AP may advertise relevant information about the recommended channels for P2P communication via a beacon frame or a probe response frame. In an embodiment, the relevant information may be included in the recommended P2P channel usage element depicted in Figure 7 the beacon frame or the probe response frame.

[0118] Figure 10 FIG. shows a flowchart of an example process for channel recommendation according to an embodiment. For purposes of explanation and illustration, example process 1000 may be performed by Figure 4 non-AP STA 410, particularly when the non-AP STA intends to switch the channel of an existing P2P link. Although one or more operations are described or shown in a particular order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations during at least partially overlapping time periods.

[0119] Procedure 1000 may start from operation 1001. In operation 1001, a non-AP STA that supports the channel recommendation procedure may set the dot11ChannelRecommendationSupprted value to 1. Then, procedure 1000 proceeds to operation 1003.

[0120] In operation 1003, when the non-AP STA operates on a P2P link (e.g., the basic channel TDSL direct link), the non-AP STA may determine to switch to another operating channel for P2P communication (e.g., the non-basic channel TDLS direct link). In other words, the non-AP STA may move from the basic channel TDSL direct link to the non-basic channel TDLS direct link. Then, procedure 1000 proceeds to operation 1005.

[0121] In operation 1005, the non-AP STA may listen for beacon frames or probe response frames sent by the AP of the control infrastructure BSS, and may receive in the beacon frames or probe response frames Figure 7 the recommended P2P channel usage element depicted in. Then, procedure 1000 proceeds to operation 1007.

[0122] In operation 1007, the non-AP STA may select a channel from the recommended channels indicated in the recommended P2P channel usage element in the beacon frame or probe response frame, and initiate a channel switch for P2P communication.

[0123] Figure 11 FIG. shows a flowchart of an example procedure of a channel recommendation procedure according to an embodiment. For purposes of explanation and illustration, example procedure 1100 may be executed by Figure 4 the non-AP STA 410 or 420 in, especially when the non-AP STA intends to establish a non-infrastructure P2P group. Although one or more operations are described or shown in a particular 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.

[0124] Procedure 1100 may start from operation 1101. In operation 1101, a non-AP STA that supports the channel recommendation procedure may set the dot11ChannelRecommendationSupprted value to 1. Then, procedure 1100 proceeds to operation 1003.

[0125] In operation 1103, a non-AP STA that intends to form a P2P group may determine that it does not have enough information to select an operating channel for the P2P group. Then, procedure 1100 proceeds to operation 1105.

[0126] In operation 1105, a non-AP STA can listen for beacon frames or probe response frames sent by an AP in the vicinity that controls the infrastructure BSS in the vicinity of the non-AP STA, and can receive within the beacon frame or probe response frame Figure 7 the recommended P2P channel usage element depicted therein. Then, process 1100 proceeds to operation 1107.

[0127] In operation 1107, the non-AP STA can select a channel from the recommended channels indicated in the recommended P2P channel usage element in the beacon frame or probe response frame, and initiate forming a P2P group to perform P2P communication.

[0128] Figure 12 Another example of the recommended P2P channel usage information element 1200 according to an embodiment is shown. Figure 12 The example format depicted therein is for illustrative purposes only. The example format does not limit the scope of the present disclosure to any particular implementation.

[0129] Referring Figure 12 to, the recommended P2P channel usage information element 1200 may include an element ID field, a length field, a control field, a power constraint element field, an EDCA parameter set element field, a transmit power envelope element field, a timeout interval element field, and a channel information list field. In some aspects, Figure 12 each field in the recommended P2P channel usage information element 1200 depicted therein may be the same as or similar to the corresponding field or sub-field in the recommended P2P channel usage information element 700 depicted in Figure 7 and Figure 8 depicted therein. Examples of the differences are described below.

[0130] The control field may include a power constraint element presence field, an EDCA parameter set element presence field, a transmit power envelope element presence field, a timeout interval element presence field, and a channel number information field.

[0131] The power constraint element presence field may indicate whether the power constraint element field is present in the recommended P2P channel usage information element 1200. When the power constraint element presence field is set to 1, it may indicate that the power constraint element field is present. Otherwise, it is set to 0.

[0132] The EDCA parameter set element presence field may indicate whether the EDCA parameter set element field is present in the recommended P2P channel usage information element 1200. When the EDCA parameter set element presence field is set to 1, it may indicate that the EDCA parameter set element field is present. Otherwise, it is set to 0.

[0133] The Transmit Power Envelope Element Presence field may indicate whether the Transmit Power Envelope Element field is present in the recommended P2P Channel Usage Information Element 1200. When the Transmit Power Envelope Element Presence field is set to 1, it may indicate that the Transmit Power Envelope Element field is present. Otherwise, it is set to 0.

[0134] The Timeout Interval Element Presence field may indicate whether the Timeout Interval Element field is present in the recommended P2P Channel Usage Information Element 1200. When the Timeout Interval Element Presence field is set to 1, it may indicate that the Timeout Interval Element field is present. Otherwise, it is set to 0.

[0135] The Channel Number Information field may indicate how many channels are recommended in the recommended P2P Channel Usage Information Element 1200. In some implementations, the Channel Number Information field may also indicate the number of Channel Information fields included in the Channel Information List field within the recommended P2P Channel Usage Information Element 1200.

[0136] The Channel Information List field may include one or more Channel Information fields. Each Channel Information field may include a Usage Mode field, an Operation Class field, a Channel field, a Country String field, and a Type field. These fields are the same as or similar to the corresponding fields or sub - fields in the recommended P2P Channel Usage Information Element 700 depicted in Figure 7 and Figure 8 In some embodiments, each of the Channel Information fields may be associated with a respective one of the one or more recommended channels indicated by the recommended P2P Channel Usage Information Element 1200. In some implementations, the number of Channel Information fields may be the same as the number of recommended channels.

[0137] In the example of

[0138] In Figure 12 the example, the Power Constraint Element field, the EDCA Parameter Set Element field, the Transmit Power Envelope Element field, and the Timeout Interval Element field may be common to all the recommended channels indicated by the recommended P2P Channel Usage Information Element 1200, while Figure 7 the fields depicted in

[0139] Figure 13 shows another example of the recommended P2P Channel Usage Information Element 1300 according to an embodiment. Figure 13 The example format depicted in

[0140] In Figure 13Among them, the recommended P2P channel usage information element 1300 may include an element ID field, a length field, a control field, a power constraint element field, an EDCA parameter set element field, a transmit power envelope element field, a timeout interval element field, and a channel usage element field. In some aspects, each field and sub-field in the recommended P2P channel usage information element 1300 may be the same as or similar to the corresponding field or sub-field in the recommended P2P channel usage information elements 700 and 1200 depicted in Figure 7 , Figure 8 and Figure 12 , and examples of the differences are described below.

[0141] The channel usage element field may include one or more channel usage element sub-fields. Each channel usage element sub-field may include an element ID field, a length field, a usage mode field, and a channel entry field.

[0142] The element ID field may include information for identifying the channel usage element sub-field, and the length field may indicate the length of the channel usage element sub-field. The usage mode field may be interpreted as a recommendation from the AP on how to use the recommended P2P channel. In some embodiments, the usage mode field may indicate the use of the recommended channels provided in Table 1 above.

[0143] The channel entry field may include one or more operation class and channel fields. Each operation class and channel field may include an operation class field and a channel field. The operation class field may indicate an operation class value. The operation class may be interpreted in the context of the country specified in the beacon frame. The channel field may indicate a channel number, which may be interpreted in the context of the indicated operation class. The channel number may indicate the recommended channel for peer-to-peer communication.

[0144] Refer to Figure 13 , the recommended P2P channel usage information element 1300 may include one or more channel usage element sub-fields, which is an example of the difference from the previous example.

[0145] In an embodiment, when advertising the recommended P2P channel, the AP may indicate how long the channel recommendation is valid. This indication may be achieved by including a timeout interval element in the recommended P2P channel usage information element. In another embodiment, an alternative mechanism may be used for this purpose, such as indicating the end time of the recommendation. This may include specifying a timing synchronization function (TSF) value or the duration of the recommendation validity, for example, with respect to the transmission time of the beacon frame or the probe response frame containing the corresponding recommendation.

[0146] In an embodiment, a first AP that is affiliated with an AP MLD and operates on a first link may advertise or announce a recommended P2P channel for a second link on which a second AP affiliated with the same AP MLD is operating, via a beacon frame or a probe response frame.

[0147] In an embodiment, when a first AP that is affiliated with an AP MLD and operates on a first link advertises or announces a recommended P2P channel corresponding to another AP affiliated with the same AP MLD, the first AP may indicate the link for the P2P channel recommendation or another AP (operating on that link). In some implementations, to indicate the link for the recommendation, the first AP may include a link ID subfield in the recommended P2P channel usage information element. In some aspects, possible formats of the recommended P2P channel usage information element are shown in Figure 14 and Figure 15 which are respectively based on Figure 12 and Figure 13 .

[0148] Figure 14 and Figure 15 show another example of recommended P2P channel usage information elements 1400 and 1500 according to an embodiment. Figure 14 The example formats depicted in Figure 12 are for illustrative purposes only. The example formats do not limit the scope of the present disclosure to any particular implementation. In some aspects, each field and subfield in the recommended P2P channel usage information element 1400 may be the same as or similar to the corresponding field or subfield in the recommended P2P channel usage information element 1200 depicted in Figure 13 and examples of the differences are described below. In some aspects, each field or subfield in the recommended P2P channel usage information element 1500 may be the same as or similar to the corresponding field or subfield in the recommended P2P channel usage information element 1300 depicted in

[0149] Refer to Figure 14 , compared with the control field of Figure 12 , the control field may further include a link ID field and a reserved field. The link ID field indicates one or more links for the P2P channel recommendation.

[0150] Refer to Figure 15 , compared with the control field of Figure 13 , the control field may further include a link ID field and a reserved field. The link ID subfield indicates one or more links for the P2P channel recommendation.

[0151] In some implementations, a link ID bitmap may be used to indicate the links for which channel information for P2P recommendations is provided. A possible example is as Figure 16 shown.

[0152] Figure 16 Another example of a recommended P2P channel usage information element 1600 according to an embodiment is shown. Figure 16 The example format depicted is for illustrative purposes only. The example format does not limit the scope of the present disclosure to any particular implementation. In some aspects, each field and sub - field in the recommended P2P channel usage information element 1600 may be the same as or similar to the corresponding field or sub - field in the Figures 12 - 15 recommended P2P channel usage information element, and examples of the differences are described below.

[0153] In Figure 16 , the recommended P2P channel usage information element 1600 may include an element ID field, a length field, a link ID bitmap field, and a link information list field. The link ID bitmap field may indicate the links for which P2P channel recommendations are provided. If the i - th bit position in the link ID bitmap field is set to 1, it may indicate that there is a P2P channel recommendation for the i - th link. Otherwise, it may indicate that there is no P2P channel recommendation for that link.

[0154] The link information list field may include one or more link information sub - fields. In some implementations, the number of link information sub - fields may be equal to the number of "1" values in the link ID bitmap field. The order of the link information sub - fields corresponding to different links may be the same as the order of the "1" values in the link ID bitmap sub - field. In some implementations, when the link ID bitmap field is set to '1001010000000000', the first link information sub - field may correspond to link 1, the second link information sub - field may correspond to link 4, and the third link information sub - field may correspond to link 6.

[0155] In Figure 16 's example, each link information list sub - field may include a control field, a power constraint element field, an EDCA parameter set element field, a transmit power envelope element field, a timeout interval element field, and a channel information list field.

[0156] In some embodiments, as an alternative frame format to the Figure 16 shown frame format, the control field may be placed in parallel with the link ID bitmap sub - field. In some embodiments, the power constraint element field, the EDCA parameter set element field, the transmit power envelope element field, and the timeout interval element field may be common for the channel recommendations of all links for which their information is carried in the recommended P2P channel usage information element.

[0157] In some embodiments, P2P channel recommendation information, such as the information carried in a recommended P2P channel usage information element, may be encrypted to be unprotected in a beacon frame or a probe response frame. This will allow STAs not associated with an AP to still scan the beacon or probe response frame and extract the channel recommendation information.

[0158] In some embodiments, after receiving channel recommendation information from an AP, if a non-AP STA determines that no recommended channels are suitable for P2P communication purposes, the non-AP STA may request the AP to modify the recommendation by sending a message. Such a modification may involve opening or allocating a new channel for P2P communication. When receiving such a request from a non-AP STA, the AP may decide whether to allocate a new channel for P2P communication or perform load balancing within an existing channel. Otherwise, the AP may ignore the request to modify. In some embodiments, if the AP receives such a request from at least a threshold number of non-AP STAs in the network, the AP respects the request.

[0159] In some embodiments, an AP attached to a non-simultaneous transmit and receive (NSTR) mobile AP MLD and operating on a primary link may advertise recommended P2P channels on behalf of other APs attached to the same NSTR mobile AP MLD and operating on non-primary links.

[0160] In some embodiments, a first AP operating in a first BSS may coordinately determine recommended P2P channels with nearby APs operating in other BSSs in a multi-AP coordination form. Alternatively, the first AP may coordinate channel selection with other APs operating under the same extended service set (ESS). This means that a centralized controller controlling the APs in the ESS may evaluate the entire enterprise network situation and accordingly decide on the recommended channels.

[0161] Unless otherwise specified, an element recited in the singular form does not mean one and only one, but one or more. For example, "a" module may refer to one or more modules. Without further limitation, an element beginning with "a", "an", "the", or "said" does not exclude the presence of additional identical elements.

[0162] The title and subtitle (if any) are for convenience only and do not limit the present invention. The term "exemplary" is used to mean serving as an example or illustration. In terms of the use of terms such as "comprising", "having", etc., such terms are intended to be inclusive in a manner similar to the way the term "including" is construed when used as a transitional word in a claim. Relative terms such as first and second may be used to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between these entities or actions.

[0163] Phrases such as on the one hand, that aspect, on the other hand, some aspects, one or more aspects, one implementation, that implementation, another implementation, some implementations, one or more implementations, one embodiment, that embodiment, another embodiment, some embodiments, one or more embodiments, one configuration, that configuration, another configuration, some configurations, one or more configurations, the subject technology, the disclosure, the present disclosure, and other variations thereof are for convenience and do not mean that the disclosures associated with these phrases are necessary for the subject technology, nor do they mean that these disclosures apply to all configurations of the subject. The disclosures associated with these phrases may apply to all configurations, or one or more configurations. The disclosures associated with these phrases may provide one or more examples. Phrases such as on the one hand or some aspects may refer to one or more aspects, and vice versa, and the same applies to the other aforementioned phrases.

[0164] The phrase "at least one of" following a list of items and the terms "and" or "or" separating any of the items modify the entire list rather than each member of the list. The phrase "at least one of" does not require the selection of at least one item; rather, the phrase allows any one item including at least one, and / or any combination of items including at least one, and / or the meaning of each item including at least one. 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 A, B, and C.

[0165] It should be understood that the specific order or hierarchy of the disclosed steps, operations, or processes are illustrations of exemplary methods. Unless explicitly stated otherwise, it should be understood that the specific order or hierarchy of steps, operations, or processes may be performed in a different order. Some of the steps, operations, or processes may be performed simultaneously, or may be performed as part of one or more other steps, operations, or processes. The accompanying method claims (if any) present the elements of the various steps, operations, or processes in an exemplary order and are not meant to be limited to the specific order or hierarchy presented. These may be performed serially, linearly, in parallel, or in a different order. 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.

[0166] The present disclosure is intended to enable any person skilled in the art to practice the various aspects described herein. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject technology. The present disclosure provides various examples of the subject technology, and the subject technology is not limited to these examples. Those skilled in the art will readily appreciate various modifications to these aspects, and the principles described herein may be applied to other aspects.

[0167] All structural and functional equivalents of the elements of the various aspects described in this disclosure that are known or later will be known to those of ordinary skill in the art are hereby expressly incorporated by reference herein and are intended to be covered by the claims. Additionally, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. No element of any claim is intended to be subject to the provisions of 35 U.S.C. § 112, paragraph 6, unless the element is expressly recited using the phrase "means for... " (or a similar phrase), or in the case of a method claim, the element is recited using the phrase "step for... " (or a similar phrase).

[0168] Herein, the title, background art, brief description of the drawings, abstract, and drawings are incorporated into the present disclosure and are illustrative examples of the present disclosure, rather than restrictive descriptions. It should be understood at the time of filing that they are not to be used to limit the scope or meaning of the claims. Additionally, in the detailed description, it can be seen that the description provides illustrative examples and, for the purpose of simplifying the present disclosure, various features are combined together in various implementations. This method of disclosure should not be construed as reflecting an intention that the claimed subject matter requires more features than are expressly recited in each claim. Rather, as reflected in the appended claims, the inventive subject matter lies in less than all of the features of a single disclosed configuration or operation. The appended claims are hereby incorporated into the detailed description, with each claim standing on its own as a separately claimed subject matter.

[0169] The claims are not intended to be limited to the aspects described herein, but rather cover the full scope consistent with the language of the claims and include all legal equivalents. Nevertheless, no claim is intended to cover subject matter that fails to meet the requirements of the applicable patent laws, nor should they be construed in such a way.

Claims

1. An access point AP device in a wireless network, the AP device comprising: Transceiver; Memory; and a processor, coupled to the memory, the processor being configured to: generating a frame indicating one or more recommended channels for peer to peer communications; and The transceiver is controlled to transmit the frame to one or more non-AP devices.

2. The AP device according to claim 1, wherein: The frame is a beacon frame or a ping response frame.

3. The AP device according to claim 1, wherein: The frame includes a channel usage element for the one or more recommended channels.

4. The AP device according to claim 3, wherein: The channel usage element includes a usage mode field indicating usage of the one or more recommended channels.

5. The AP device according to claim 3, wherein: The channel usage element includes a channel field indicating one or more channel numbers of the one or more recommended channels and an operation category field indicating one or more operation categories of the one or more recommended channels.

6. The AP device according to claim 1, wherein: The one or more non-AP devices include at least one non-AP device that is not associated with the AP device.

7. The AP device according to claim 1, wherein: The frame includes a power constraint element indicating a maximum transmit power for a receiving non-AP device.

8. The AP device according to claim 1, wherein: The frame includes an EDCA parameter set element indicating Enhanced Distributed Channel Access, EDCA parameters for receiving transmissions of non-AP devices.

9. The AP device according to claim 1, wherein: The one or more recommended channels are within a set of channels used by the AP device for an infrastructure basic service set.

10. The AP device according to claim 1, wherein: The one or more recommended channels are outside a set of channels used by the AP device for an infrastructure basic service set.

11. A non-access point AP device in a wireless network, the non-AP device comprising: Transceiver; Memory; and a processor, coupled to the memory, the processor being configured to: controlling the transceiver to receive a frame from an AP device indicating one or more recommended channels for peer-to-peer communication; selecting, based on the received frame, a channel from the one or more recommended channels for the peer to peer communication; and The peer-to-peer communications with one or more non-AP devices are performed over the selected channel.

12. The non-AP device according to claim 11, wherein: The frame is a beacon frame or a ping response frame.

13. The non-AP device according to claim 11, wherein: The frame includes a channel usage element for the one or more recommended channels.

14. The non-AP device according to claim 13, wherein: The channel usage element includes a usage mode field indicating usage of the one or more recommended channels.

15. The non-AP device according to claim 13, wherein: The channel usage element includes a channel field indicating one or more channel numbers of the one or more recommended channels and an operation category field indicating one or more operation categories of the one or more recommended channels.

Images