TDLS discovery and establishment for multi-link operation
P2P communication links between multi-link devices (MLDs) are solved by discovering and establishing P2P direct links on multiple links that are not defined in existing specifications. Establishing problems, achieving efficient P2P communication between MLDs.
Patent Information
- Application Number
- CN202380033094.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-06-27
- Filing Date
- 2023-07-06
- Publication Date
- 2024-11-08
AI Technical Summary
Enhanced multi-link single radio (EMLSR) operation for peer-to-peer (P2P) communication between multi-link devices (MLDs), especially the establishment of channel direct links and The discovery and establishment process of multiple P2P direct links.
A method and device are provided to discover and establish multiple links on multiple links by generating and sending a message containing link information between MLDs to indicate a P2P direct link intended to be established. P2P direct links, including using TDLS multi-link elements in TDLS discovery request frames, establishment request frames, and confirmation frames, conveying link instructions and information.
The discovery and establishment of multiple P2P direct links between MLDs is realized, and the undefined processes in the existing specifications are filled, and efficient P2P communication between MLDs is supported.
Smart Images

Figure CN118923196A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to peer-to-peer (P2P) communications in a wireless communication system including a multi-link device (MLD). Embodiments of the present disclosure relate to methods and apparatus for facilitating discovery and establishment of multiple P2P direct links for P2P communications between MLDs in a wireless local area network (WLAN) communication system. Background Art
[0002] WLAN technology allows devices to access the Internet in the 2.4GHz, 5GHz, 6GHz, or 60GHz frequency bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 family of standards is designed to increase speed, reliability, and extend the operating range of wireless networks.
[0003] Next generation Extremely High Throughput (EHT) WI-FI systems (e.g., IEEE 802.11be) support multiple operating bands (called links) on which access points (APs) and non-access point (non-AP) devices can communicate with each other. Therefore, both AP and non-AP devices are able to communicate on different bands / links, which is called Multi-Link Operation (MLO). WI-FI devices that support MLO are called MLDs. Using MLO, non-AP MLDs can discover, authenticate, associate, and establish multiple links with AP MLDs. On each link established between AP MLDs and non-AP MLDs, channel access and frame exchange are possible. The component of MLD responsible for transmission and reception on one link is called a station (STA). Summary of the invention
[0004] Solution to the problem
[0005] Embodiments of the present disclosure provide methods and apparatus for facilitating discovery and establishment of multiple P2P direct links for P2P communication between MLDs in a WLAN communication system.
[0006] In one embodiment, a first non-AP MLD is provided. The first non-AP MLD is configured to form a link with an AP of an AP MLD, and at least one processor operably coupled to a first STA. The at least one processor is configured to generate a first message, the first message including information indicating that one or more of the links are one or more target links on which the first non-AP MLD intends to establish one or more P2P direct links with a second non-AP MLD, wherein a second STA of the second non-AP MLD is associated with an AP of the AP MLD on the one or more target links. Each of the first STAs is configured to form a link with one of the APs, and one of the first STAs is configured to send a first message to a corresponding AP of the APs on a first link formed with the corresponding AP in the link.
[0007] In another embodiment, a method of wireless communication performed by a first non-AP MLD is provided, the first non-AP MLD including first STAs configured to form a link with an AP of an AP MLD, each of the first STAs being configured to form a link with one of the APs. The method includes the steps of generating a first message including information indicating that one or more of the links are one or more target links on which the first non-AP MLD intends to establish one or more P2P direct links with a second non-AP MLD, wherein a second STA of the second non-AP MLD is associated with an AP of the AP MLD on the one or more target links, and sending the first message to the corresponding AP of the AP on the first link formed with the corresponding AP of the link.
[0008] In another embodiment, an AP MLD is provided. The AP MLD includes an AP and at least one processor, the AP is configured to form a first link with a first STA of a first non-AP MLD and a second link with a second STA of a second non-AP MLD, and the at least one processor is operably coupled to the AP. A first AP in the APs is configured to receive a first message from one of the first STAs on one of the first links, the first message including information indicating that one or more of the first links are one or more target links on which the first non-AP MLD intends to establish one or more P2P direct links with the second non-AP MLD. The second STA of the second non-AP MLD is associated with the AP on the one or more target links. The at least one processor is configured to determine that the first message is intended for the second non-AP MLD. The first AP in the APs is configured to send a first message to one of the second STAs on one of the second links.
[0009] In another embodiment, a method of wireless communication performed by an AP MLD is provided, the AP MLD including an AP configured to form a first link with a first STA of a first non-AP MLD and a second link with a second STA of a second non-AP MLD. The method includes the steps of receiving a first message from one of the first STAs on one of the first links, determining that the first message is intended for the second non-AP MLD, and sending the first message to one of the second STAs on one of the second links. The first message includes information indicating that one or more of the first links are one or more target links on which the first non-AP MLD intends to establish one or more peer-to-peer (P2P) direct links with the second non-AP MLD. The second STA of the second non-AP MLD is associated with the AP on the one or more target links.
[0010] Other technical features may be apparent to those skilled in the art from the following drawings, descriptions and claims.
[0011] Before the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document. The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives include direct and indirect communication. The terms "include" and "comprise" and their derivatives mean including but not limited to this. The term "or" is inclusive, meaning and / or. The phrase "associated with..." and its derivatives mean including, included in, interconnected with, included in, connected to or connected with, coupled to or coupled with, communicable with, collaborate with, interweave, juxtapose, approach, bind to or bind with, have, have the property of, have a relationship with, etc. The term "controller" means any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or a combination of hardware and software and / or firmware. The functions associated with any particular controller may be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of..." means that different combinations of one or more of the listed items may be used, and only one item in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. As used herein, terms such as "1st" and "2nd" or "first" and "second" can be used to simply distinguish the corresponding component from another component, and do not limit the component in other aspects (e.g., importance or order). It should be understood that if an element (e.g., a first element) is referred to as "coupled with another element (e.g., a second element)", "coupled to another element", "connected to another element" or "connected to another element" with or without the term "operably" or "communicatively", it means that the element can be coupled to another element directly (e.g., wired), wirelessly or via a third element.
[0012] As used herein, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with other terms (e.g., "logic," "logic block," "component," or "circuit"). A module may be a single integrated component or its smallest unit or part suitable for performing one or more functions. For example, according to an embodiment, a module may be implemented in the form of an application specific integrated circuit (ASIC).
[0013] In addition, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or a portion thereof, suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD), or any other type of memory. "Non-transitory" computer-readable media do not include wired, wireless, optical, or other communication links that transmit temporary electrical or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite data later, such as rewritable optical disks or erasable memory devices.
[0014] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:
[0016] FIG1 illustrates an example wireless network according to various embodiments of the present disclosure;
[0017] FIG2A illustrates an example AP according to various embodiments of the present disclosure;
[0018] FIG2B illustrates an example STA according to various embodiments of the present disclosure;
[0019] 3 and 4 illustrate an example process for discovering a single TDLS peer STA according to an embodiment of the present disclosure;
[0020] 5 and 6 illustrate an example process for establishing a single TDLS direct link according to an embodiment of the present disclosure;
[0021] 7 and 8 illustrate an example process for establishing multiple TDLS direct links using multiple TDLS discovery request frames according to an embodiment of the present disclosure;
[0022] FIG. 9 shows an example format of a TDLS multi-link element according to an embodiment of the present disclosure;
[0023] FIG. 10 shows an example format of a per-STA profile subelement of a link information field of a TDLS multilink element according to an embodiment of the present disclosure;
[0024] FIG. 11 illustrates an example process for multiple TDLS discovery for non-AP MLD; and
[0025] FIG. 12 illustrates an example process for facilitating discovery and establishment of multiple TDLS direct links for P2P communication between MLDs according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0026] FIG. 1 to FIG. 12 discussed below and the various embodiments used to describe the principles of the present disclosure in this patent document are intended only as illustrations and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any suitably arranged system or device.
[0027] Embodiments of the present disclosure recognize that enhanced multi-link single radio (EMLSR) operations (e.g., tunneled direct linksetup (TDLS)) for P2P communications are not defined in the current IEEE 802.11be specification. Therefore, when a non-AP MLD is communicating with its associated AP MLD and operating in EMLSR mode, it is unclear based on the latest IEEE 802.11be specification whether it is possible for the non-AP MLD to establish one or more peer links with another peer non-AP MLD. Even if it is possible, there is no defined process for P2P establishment when operating in EMLSR mode.
[0028] Embodiments of the present disclosure also recognize that if two non-AP MLDs have established a peer link on one or more links between the two non-AP MLDs, there is no defined procedure for initiating (or activating) EMLSR mode for P2P communication between two non-AP MLDs. The operating procedures of EMLSR for P2P communication are also not defined in the current 802.11be specification.
[0029] Therefore, embodiments of the present disclosure provide methods and apparatus for facilitating discovery and establishment of multiple P2P direct links for P2P communication between MLDs (or peer MLDs).
[0030] FIG1 illustrates an example wireless network 100 according to various embodiments of the present disclosure. The embodiment of the wireless network 100 shown in FIG1 is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.
[0031] The wireless network 100 includes APs 101 and 103. The 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. The AP 101 provides wireless access to the network 130 for a plurality of STAs 111-114 within a coverage area 120 of the AP 101. The APs 101 and 103 may communicate with each other and with the STAs 111-114 using Wi-Fi or other WLAN communication technologies.
[0032] 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 a remote terminal. In a WLAN, assuming that the AP also competes for a wireless channel, the AP may also be referred to as a STA (e.g., APSTA). In addition, depending on the network type, other well-known terms may be used instead of "station" or "STA", such as "mobile station", "subscriber station", "remote terminal", "user equipment", "wireless terminal" or "user device". For convenience, the terms "station" and "STA" are used in this disclosure to refer to remote wireless equipment that wirelessly accesses an AP or competes for a wireless channel in a WLAN, whether the STA is a mobile device (such as a mobile phone or smart phone) or is generally considered to be a fixed device (such as a desktop computer, AP, media player, fixed sensor, TV, etc.). This type of STA may also be referred to as a non-AP STA.
[0033] In various embodiments of the present disclosure, each of the APs 101 and 103 and each of the STAs 111-114 may be an MLD. In such an embodiment, the APs 101 and 103 may be AP MLDs, and the STAs 111-114 may be non-AP MLDs. Each MLD is attached to more than one STA. For ease of explanation, an AP MLD is described herein as being attached to more than one AP (e.g., more than one AP STA), and a non-AP MLD is described herein as being attached to more than one STA (e.g., more than one non-AP STA).
[0034] Dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with APs, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the AP and variations in the radio environment associated with natural and man-made obstacles.
[0035] As described in more detail below, one or more of the APs may include circuits and / or programming for facilitating discovery and establishment of multiple P2P direct links for P2P communication between MLDs in the WLAN. Although FIG. 1 shows an example of a wireless network 100, various changes may be made to FIG. 1. For example, the wireless network 100 may include any number of APs and any number of STAs in any suitable arrangement. In addition, the AP 101 may communicate directly with any number of STAs and provide wireless broadband access to the network 130 to these STAs. Similarly, each of the APs 101 and 103 may communicate directly with the network 130 and provide direct wireless broadband access to the network 130 to the STAs. In addition, the APs 101 and / or 103 may provide access to other or additional external networks (such as an external telephone network or other types of data networks).
[0036] FIG. 2A shows an example AP 101 according to various embodiments of the present disclosure. The embodiment of the AP 101 shown in FIG. 2A is for illustration only, and the AP 103 of FIG. 1 may have the same or similar configuration. In the embodiments discussed below, the AP 101 is an AP MLD. However, the AP has a wide variety of configurations, and FIG. 2A does not limit the scope of the present disclosure to any particular implementation of the AP.
[0037] The AP MLD 101 is attached to a plurality of APs 202a-202n (which may be referred to as, for example, AP1-APn). Each of the attached APs 202a-202n includes a plurality of antennas 204a-204n, a plurality of radio frequency (RF) transceivers 209a-209n, a transmit (TX) processing circuit 214, and a receive (RX) processing circuit 219. The AP MLD 101 also includes a controller / processor 224, a memory 229, and a backhaul or network interface 234.
[0038] The illustrated components of each subordinate AP 202a-202n may represent the physical (PHY) layer and the lower media access control (LMAC) layer in the open systems interconnection (OSI) networking model. In such an embodiment, the illustrated components of the AP MLD 101 represent a single upper MAC (UMAC) layer and other higher layers in the OSI model, which are shared by all subordinate APs 202a-202n.
[0039] For each satellite AP 202a-202n, an RF transceiver 209a-209n receives an incoming RF signal from an antenna 204a-204n, such as a signal transmitted by a STA in the network 100. In some embodiments, each satellite AP 202a-202n operates at a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), and thus the incoming RF signal received by each satellite AP may be at a different RF frequency. The RF transceiver 209a-209n down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is 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.
[0040] For each of the attached APs 202a-202n, the TX processing circuitry 214 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 224. The TX processing circuitry 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 signals from the TX processing circuitry 214 and up-convert the baseband or IF signals to RF signals that are transmitted via the antennas 204a-204n. In embodiments where each of the attached APs 202a-202n operates at a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), the outgoing RF signals transmitted by each of the attached APs may be at different RF frequencies.
[0041] The controller / processor 224 may include one or more processors or other processing devices that control the overall operation of the AP MLD 101. For example, the controller / processor 224 may control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers 209a-209n, the RX processing circuit 219, and the TX processing circuit 214 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, in which the output signals from the multiple antennas 204a-204n are weighted differently to effectively direct the outgoing signals in the desired direction. The controller / processor 224 may also support orthogonal frequency division multiplexing (OFDMA) operations, in which the outgoing signals are assigned to different subcarrier subsets of different recipients (e.g., different STAs 111-114). The controller / processor 224 may support any of a variety of other functions in the AP MLD 101, including facilitating the discovery and establishment of multiple P2P direct links for P2P communication between MLDs in the WLAN. In some embodiments, the controller / processor 224 includes 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 an operating system (OS). The controller / processor 224 may move data into or out of the memory 229 as required by the executed process.
[0042] The controller / processor 224 is also coupled to a backhaul or network interface 234. The backhaul or network interface 234 allows the AP MLD 101 to communicate with other devices or systems over a backhaul connection or over a network. The interface 234 can support communication over any suitable wired or wireless connection. For example, the interface 234 can allow the AP MLD 101 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 234 includes any suitable structure that supports communication over 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 a random access memory (RAM), and another portion of the memory 229 may include flash memory or other random access memory (ROM).
[0043] As described in more detail below, the AP MLD 101 may include circuits and / or programming for facilitating the discovery and establishment of multiple P2P direct links for P2P communication between MLDs in a WLAN. Although FIG. 2A shows an example of the AP MLD 101, various changes may be made to FIG. 2A. For example, the AP MLD 101 may include any number of each component shown in FIG. 2A. As a specific example, the AP MLD 101 may include multiple interfaces 234, and the controller / processor 224 may support routing functions to route data between different network addresses. As another specific example, although each of the attached APs 202a-202n is shown as including a single instance of the TX processing circuit 214 and a single instance of the RX processing circuit 219, the APMLD 101 may include multiple instances of each AP (such as one for each RF transceiver) in one or more of the attached APs 202a-202n. Alternatively, in one or more of the attached APs 202a-202n, such as in a traditional AP, only one antenna and RF transceiver path may be included. Furthermore, various components in FIG. 2A may be combined, further subdivided, or omitted, and additional components may be added according to particular needs.
[0044] FIG. 2B illustrates an example STA 111 according to various embodiments of the present disclosure. The embodiment of STA 111 shown in FIG. 2B is for illustration only, and STAs 111-115 of FIG. 1 may have the same or similar configurations. In the embodiments discussed below, STA 111 is a non-AP MLD. However, STAs have a variety of configurations, and FIG. 2B does not limit the scope of the present disclosure to any particular implementation of a STA.
[0045] The non-AP MLD 111 is attached to a plurality of STAs 203a-203n (which may be referred to as, for example, STA1-STAn). Each attached STA 203a-203n includes an antenna 205, an RF transceiver 210, a TX processing circuit 215, and a receive (RX) processing circuit 225. The non-AP MLD 111 also includes a microphone 220, 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 includes an OS 261 and one or more applications 262.
[0046] The illustrated components of each dependent STA 203a-203n may represent the PHY layer and LMAC layer in the OSI networking model. In such an embodiment, the illustrated components of the non-AP MLD 111 represent a single UMAC layer and other higher layers in the OSI model, which are shared by all dependent STAs 203a-203n.
[0047] For each affiliated STA 203a-203n, the RF transceiver 210 receives an incoming RF signal sent by the AP of the network 100 from the antenna 205. In some embodiments, each affiliated STA 203a-203n operates at a different bandwidth (e.g., 2.4GHz, 5GHz, or 6GHz), and thus the incoming RF signal received by each affiliated STA can be at a different RF frequency. The RF transceiver 210 down-converts the input 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 to the controller / processor 240 for further processing (such as for web browsing data).
[0048] For each affiliated STA 203a-203n, the TX processing circuit 215 receives analog or digital voice data from the microphone 220, or receives other outgoing baseband data (such as web data, email, or interactive video game data) from the controller / processor 240. 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 that is transmitted via the antenna 205. In an embodiment where each affiliated STA 203a-203n operates at a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), the outgoing RF signal transmitted by each affiliated STA can be at a different RF frequency.
[0049] 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 non-AP MLD 111. In one such operation, the main controller / processor 240 controls the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver 210, the RX processing circuit 225, and the TX processing circuit 215 according to well-known principles. The main controller / processor 240 may also include a processing circuit configured to facilitate the discovery and establishment of multiple P2P direct links for P2P communication between MLDs in the WLAN. In some embodiments, the controller / processor 240 includes at least one microprocessor or microcontroller.
[0050] The controller / processor 240 is also capable of executing other processes and programs resident in the memory 260, such as operations for facilitating the discovery and establishment of multiple P2P direct links for P2P communication between MLDs in the WLAN. The controller / processor 240 can move data into or out of the memory 260 as needed for the execution process. In some embodiments, the controller / processor 240 is configured to execute multiple applications 262, such as applications for facilitating the discovery and establishment of multiple P2P direct links for P2P communication between MLDs in the WLAN. The controller / processor 240 can operate multiple applications 262 based on the OS program 261 or in response to a signal received from the AP. The main controller / processor 240 is also coupled to the I / O interface 245, which provides the non-AP MLD 111 with the ability to connect to other devices such as laptops and handheld computers. The I / O interface 245 is a communication path between these accessories and the main controller 240.
[0051] The controller / processor 240 is also coupled to a touch screen 250 and a display 255. An operator of the non-AP MLD 111 can use the touch screen 250 to input data into the non-AP MLD 111. The display 255 can be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website. A memory 260 is coupled to the controller / processor 240. A portion of the memory 260 can include RAM, and another portion of the memory 260 can include flash memory or other ROM.
[0052] Although FIG. 2B shows an example of a non-AP MLD 111, various changes may be made to FIG. 2B. For example, various components in FIG. 2B may be combined, further subdivided, or omitted, and additional components may be added as needed. In a specific example, one or more of the affiliated STAs 203a-203n may include any number of antennas 205 for multiple-input multiple-output (MIMO) communications with the AP 101. In another example, the non-AP MLD 111 may not include voice communications, or the controller / processor 240 may be divided into multiple processors, such as one or more central processing units (CPUs) or one or more graphics processing units (GPUs). In addition, although FIG. 2B shows a non-AP MLD 111 configured as a mobile phone or smart phone, the non-AP MLD may be configured to operate as other types of mobile or fixed devices.
[0053] 3 and 4 illustrate an example process for discovering a single channel direct link setup (TDLS) peer STA according to an embodiment of the present disclosure. In this example, the AP MLD (MLD_A) may be the AP MLD 101, and the non-AP MLD (MLD_S) may be the non-AP MLD 111. Although the AP MLD 101 is shown as having two subordinate APs (AP1 and AP2), and the non-AP MLD 111 is shown as a non-AP MLD having two subordinate non-AP STAs (STA1 and STA2), it should be understood that the process may be applied to a suitable MLD having any number of subordinate APs or STAs. For ease of explanation, it should be understood that in the further embodiments below, references to the AP MLD and the non-AP MLD refer to the AP MLD 101 and the non-AP MLD 111, respectively.
[0054] Figures 3 and 4 show a scenario where TDLS discovery is initiated by a non-AP MLD (MLD_S). MLD_S has performed multi-link establishment with an APMLD (MLD_A). As described above, MLD_S has two subordinate STAs—STA1 and STA2. STA3 cannot perform multi-link operation and is not subordinate to the non-AP MLD. MLD_A has two subordinate APs—AP1 and AP2—where AP1 operates on link 1 and AP2 operates on link 2. STA1 and STA3 operate on link 1 and are associated with AP1. STA2 operates on link 2 and is associated with AP2.
[0055] In this example, MLD_S initiates TDLS discovery by sending two TDLS discovery request frames (which are data frames) because it does not know which link STA3 is operating on and whether STA3 is attached to MLD or a STA not attached to MLD. The first TDLS discovery request frame shown in Figure 3 includes the BSSID field in the link identifier (LI) element set to the basic service set identifier (BSSID) of AP1, and the second TDLS discovery request frame shown in Figure 4 includes this field set to the BSSID of AP2. Both frames include their A3 (destination address (DA)) set to the STA3 MAC address and the To DS (To Distribution System (DS)) subfield of the frame control field set to 1.
[0056] The TDLS Discovery Request frame can be sent on Link 1 (via STA1, as represented by the solid line) or Link 2 (via STA2, as represented by the dashed line). When the TDLS Discovery Request frame is received at the AP MLD (i.e., via AP1 or AP2), it routes the frame to STA3 via AP1 by setting the From DS subfield of the Frame Control field to 1 and setting A3 (Source Address (SA)) to the non-AP MLD address (i.e., MLD_S).
[0057] STA3 discards the TDLS discovery request frame whose BSSID field of its LI element is set to the BSSID of AP2 because it does not recognize the BSSID. STA3 recognizes the BSSID set to AP1 and responds with a TDLS discovery response frame as a management frame (or mgmt frame) in which the receiver address (RA) is set to MLD_S and both the To DS and From DS subfields are set to 0. The TDLS STA attached to MLD_S receives the TDLS discovery response frame sent on the TDLS direct link. The TDLS initiator STA address field and the TDLS responder STA address field contained in the LI element (represented as LI in Figures 3 and 4) are carried in the TDLS discovery request frame and the TDLS discovery response frame and are set to MLD_S and STA3, respectively.
[0058] 5 and 6 illustrate an example process for establishing a single TDLS direct link according to an embodiment of the present disclosure. In this example, the AP MLD (MLD_A) may be the AP MLD 101, and the non-AP MLDs (MLD_S and MLD_R) may be the non-AP MLD 111. Although the AP MLD 101 is shown as having two subordinate APs (AP1 and AP2), and the non-AP MLD 111 is shown as having two subordinate non-AP STAs (STA1 and STA2, and STA3 and STA4), it should be understood that the process may be applied to a suitable MLD having any number of subordinate APs or STAs.
[0059] Figures 5 and 6 show a scenario of establishing a single link TDLS direct link between two non-AP MLDs that have performed multi-link establishment with the same AP MLD. MLD_S has two subordinate STAs, STA1 and STA2, and MLD_R has two subordinate STAs, STA3 and STA4. MLD_A has two subordinate APs, AP1 and AP2, where AP1 operates on link 1 and AP2 operates on link 2. STA1 and STA3 operate on link 1 and are associated with AP1. STA2 and STA4 operate on link 2 and are associated with AP2.
[0060] The examples of Figures 5 and 6 assume that two non-AP MLDs have performed TDLS discovery, and the initiating non-AP MLD (in this example, MLD_S) has decided to perform a single link TDLS establishment for Link 1. As shown, the TDLS Setup Request frame is sent by the non-AP MLD, MLD_S, via its subordinate STA1 to MLD_R via its subordinate STA3. The BSSID field in the LI element identifies the intended link for establishing the TDLS direct link.
[0061] As described above, there is currently no defined process for discovering and establishing multiple P2P direct links (e.g., TDLS direct links) between two non-AP MIDs. Various embodiments of the present disclosure herein below provide a framework and mechanism for implementing the discovery and establishment of multiple TDLS direct links between two non-AP MLDs (such as MLD_S and MLD_R of FIGS. 5 and 6 ).
[0062] According to one embodiment, when a non-AP MLD intends to establish multiple TDLS direct links with another non-AP MLD (ie, a peer non-AP MLD), the non-AP MLD may first attempt to discover STAs affiliated with the peer non-AP MLD operating on those multiple links.
[0063] 7 and 8 illustrate an example process for establishing multiple TDLS direct links using multiple TDLS discovery request frames according to an embodiment of the present disclosure. According to one embodiment shown in FIG7 , a first non-AP MLD that intends to establish multiple TDLS direct links with a second non-AP MLD may send multiple TDLS discovery request frames to the second non-AP MLD. Each TDLS discovery request frame may include a link identifier (ID) indicating a different AP corresponding to a different link on which the first non-AP MLD intends to establish a TDLS direct link.
[0064] According to one embodiment shown in FIG. 8 , a second non-AP MLD that receives a plurality of TDLS discovery request frames from a first non-AP MLD—each TDLS discovery request frame indicating a different link on which the first non-AP MLD operates (via the link ID information of the TDLS discovery request frame)—may send a plurality of TDLS discovery response frames in response—each TDLS discovery response frame corresponding to a link on which the first non-AP MLD operates.
[0065] According to one embodiment, in a scenario where the non-AP MLD intends to establish multiple TDLS direct links on multiple links on which the non-AP MLD is operating, the non-AP, when acting as a TDLS initiator, may include a TDLS multi-link element in a TDLS discovery request frame and a TDLS setup request frame that it sends. The TDLS multi-link element included in the TDLS discovery request frame or the TDLS setup request frame may convey an indication of a link on which the non-AP MLD intends to establish a TDLS direct link and information about the link.
[0066] According to one such embodiment, a TDLS discovery request frame or a TDLS setup request frame sent by a non-AP MLD may include one or more link information fields. According to one embodiment, when a non-AP MLD intends to establish multiple TDLS direct links on multiple links on which the non-AP MLD operates, the non-AP MLD as a TDLS initiator may include multiple link information fields in a TDLS multilink element included in the TDLS discovery request frame or the TDLS setup request frame.
[0067] The link information field may include link specific indications and information related to links established corresponding to multiple TDLS direct links.
[0068] Figure 9 shows an example format of a TDLS multilink element 900 according to an embodiment of the present disclosure. The example of Figure 9 further shows an example format of a multilink control field 902 of the TDLS multilink element and a presence bitmap subfield of the multilink control field 902, a common information field 904 of the TDLS multilink element, and link ID information and MLD capability and operation subfields of the common information field 904.
[0069] According to one embodiment, the link ID subfield of the common information field 904 of the TDLS multilink element may indicate the link ID of the link that transmits the frame including the TDLS multilink element 900 .
[0070] According to one embodiment, the link information field 906 of the TDLS multi-link element 900 may include zero or more per-STA profile sub-elements, each corresponding to a different link on which the non-AP MLD operates.
[0071] According to one embodiment, when there is no per-STA profile in the link information field in the TDLS multilink element, a TDLS discovery request frame, a TDLS discovery response frame, a TDLS setup request frame, a TDLS setup response frame, or a TDLS setup confirmation frame including the TDLS multilink element may be used to discover, establish, or confirm a single TDLS direct link. In this case, the intended link for which the frame is sent (for discovering a TDLS peer STA on the link, or for establishing a TDLS direct link on the link, or for confirming the establishment of a TDLS direct link) may be determined by the LI element included in the corresponding frame.
[0072] According to one embodiment, when there are one or more per-STA profile sub-elements in the link information field of the TDLS multilink element included in the TDLS discovery request frame, the TDLS discovery request frame is sent by the TDLS initiator to discover TDLS peer STAs on one or more links on which the non-APMLD is operating.
[0073] FIG. 10 shows an example format of a per-STA profile sub-element 1000 of the link information field of a TDLS multilink element according to an embodiment of the present disclosure. In this example, the per-STA profile sub-element 1000 is a sub-element of the link information field 906 of the TDLS multilink element 900. The per-STA profile sub-element 1000 may include a STA control field 1002 and a STA information field 1004, an example format of which is shown in FIG. 10. Each per-STA profile sub-element may indicate and include information related to different links on which the non-AP MLD intends to discover a TDLS peer STA. The per-STA profile sub-element of the link information field of the TDLS multilink element may include information such as discussed below, but it should be understood that this is merely an example.
[0074] The STA Control field 1002 may include different subfield presence indicators, such as an indication of whether the MAC address of the STA attached to the non-AP MLD and operating on the link targeted by the TDLS discovery exists in the STA MAC Address Presence subfield. The STA Control field 1002 may also include an LI in the Link ID subfield to identify the link targeted by the TDLS discovery, and an indication of whether the per-STA profile in the Full Profile subfield is a full profile (the definition of the full profile of the TDLS multilink element may be similar to the definition of the full profile of the Basic Multilink element).
[0075] The STA information field 1004 may include a STA information length subfield indicating the length of the STA information field 1004 and a STA MAC address field specifying a MAC address of a STA operating on a link for TDLS discovery.
[0076] 11 illustrates an example process 1100 for multiple TDLS discovery for non-AP MLD. The example process 1100 uses a TDLS multi-link element to discover TDLS peer STAs on multiple links.
[0077] Using the TDLS Multi-link element included in the TDLS Discovery Response frame as part of the TDLS discovery process on multiple links may be similar to using the TDLS Multi-link element included in the TDLS Discovery Request frame to discover multiple TDLS peer STAs on multiple links.
[0078] Using the TDLS multi-link element included in the TDLS setup request frame on multiple links as part of the TDLS setup request process may be similar to using the TDLS multi-link element included in the TDLS discovery request frame to discover multiple TDLS peer STAs on multiple links.
[0079] Using the TDLS Multi-link element included in the TDLS Setup Response frame on multiple links as part of the TDLS Setup Response procedure may be similar to using the TDLS Multi-link element included in the TDLS Discovery Request frame to discover multiple TDLS peer STAs on multiple links.
[0080] Using the TDLS multi-link element included in the TDLS setup confirm frame on multiple links as part of the TDLS setup confirm process may be similar to using the TDLS multi-link element included in the TDLS discovery request frame to discover multiple TDLS peer STAs on multiple links.
[0081] FIG. 12 illustrates an example process 1200 for facilitating discovery and establishment of multiple TDLS direct links for P2P communication between MLDs according to an embodiment of the present disclosure. Process 1200 is discussed as being performed by a first peer non-AP MLD, but it should be understood that a corresponding second peer non-AP MLD performs a corresponding process. In addition, for convenience, process 1200 is discussed as being performed by a WI-FI non-AP MLD including a first STA, each first STA including a transceiver configured to form a link with a corresponding AP attached to a WI-FI AP MLD. However, it should be understood that any suitable wireless communication device may perform these processes.
[0082] 12 , process 1200 begins with a first non-AP MLD generating a first message including information indicating that one or more links are target links on which the first non-AP MLD intends to establish a P2P direct link (e.g., a TDLS direct link) with a second STA of a second non-AP MLD, where the second STA is associated with a corresponding AP of an AP MLD on the target link (step 1205). The information in the first message may indicate to the second non-AP MLD that the first non-AP MLD intends to establish a P2P direct link with the second STA of the second non-AP MLD on the one or more target links.
[0083] In some embodiments, the information in the first message is a multilink element (e.g., a TDLS multilink element) including link-specific information related to each of the target links. In some embodiments, the multilink element may include a link ID of one target link, the link ID indicating that the first non-AP MLD intends to establish a single P2P direct link on the one target link, where the one target link is different from the link on which the first message is sent.
[0084] In some embodiments, the multilink element may include a per-STA profile corresponding to each of the target links, respectively. Each per-STA profile may include a link ID of the corresponding target link, the link ID indicating that the first non-AP MLD intends to establish a P2P direct link on the corresponding target link. Each per-STA profile may include a MAC address of a second STA operating on the corresponding target link.
[0085] The first message may be one of the following: a TDLS discovery request frame, a TDLS discovery response frame, a TDLS setup request frame, a TDLS setup response frame, or a TDLS setup confirmation frame.
[0086] Next, the first non-AP MLD transmits a first message to the corresponding AP of the AP MLD via the transceiver of the first STA among the first STAs on a link between the first STA among the first STAs and the corresponding AP (step 1210 ).
[0087] Finally, the first non-AP MLD receives a response message corresponding to the first message from one of the second STAs of the second non-AP MLD on one of the target links (step 1215). The response message may include information about the target link.
[0088] The above flow charts illustrate example methods or processes that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods or processes shown in the flow charts. For example, although shown as a series of steps, various steps can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.
[0089] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover these changes and modifications that fall within the scope of the appended claims. The description in this application should not be interpreted as implying that any particular element, step or function is an essential element that must be included in the scope of the claims. The scope of the patent subject matter is defined by the claims.
Claims
1. A first non-access point (AP) multi-link device (MLD), include: The first station (STA), is configured to form a link with the AP of AP MLD; as well as at least one processor operably coupled to the first STA, the at least one processor configured to generate a first message, the first message including information indicating that one or more of the links are one or more target links on which the first non-AP MLD intends to establish one or more peer-to-peer (P2P) direct links with a second non-AP MLD, wherein a second STA of the second non-AP MLD is associated with an AP of the AP MLD on the one or more target links, Each of the first STAs is configured to form a link with one of the APs, and one of the first STAs is configured to send a first message to a corresponding AP among the APs on a first link formed with the corresponding AP among the links.
2. The first non-AP MLD according to claim 1, in: In response to the first message, one of the first STAs is further configured to receive a second message from one of the second STAs on one of the one or more target links, and The second message includes information about the one or more target links.
3. A method of wireless communication performed by a first non-access point (AP) multi-link device (MLD), the first non-access point (AP) multi-link device (MLD) comprising first stations (STAs) configured to form a link with an AP of the AP MLD, each of the first STAs being configured to form a link with one of the APs, the method include: generating a first message including information indicating that one or more of the links are one or more target links on which the first non-AP MLD intends to establish one or more peer-to-peer (P2P) direct links with a second non-AP MLD, wherein a second STA of the second non-AP MLD is associated with an AP of the AP MLD on the one or more target links; and A first message is sent to a corresponding AP among the APs over a first link formed with a corresponding AP among the links.
4. The first non-AP MLD according to claim 1 or the method according to claim 3, in, The information included in the first message is a multilink element including link specific information associated with each of the one or more target links.
5. The first non-AP MLD according to claim 1 or the method according to claim 3, in: The information included in the first message is a multilink element, the multilink element including a link identifier (ID) of one target link, the link identifier (ID) indicating that the first non-AP MLD intends to establish a single P2P direct link on the one target link, and The one target link is different from the first link on which the first message is sent.
6. The first non-AP MLD according to claim 1 or the method according to claim 3, in, The information included in the first message is a multilink element including one or more per-STA profiles corresponding to each of the one or more target links, respectively.
7. The first non-AP MLD or the method according to claim 6, in, Each of the one or more per-STA profiles includes a link identifier (ID) of a corresponding target link, the link identifier (ID) indicating that the first non-APMLD intends to establish a P2P direct link on the corresponding target link.
8. The first non-AP MLD or the method according to claim 6, in, Each of the one or more per-STA profiles includes a media access control (MAC) address of one of the second STAs operating on the corresponding target link.
9. The first non-AP MLD according to claim 1 or the method according to claim 6, in, The information included in the first message indicates to the second non-AP MLD that the first non-AP MLD intends to establish the one or more P2P direct links with the second STA of the second non-AP MLD over the one or more target links.
10. The method according to claim 3, further comprising: include: receiving a response message corresponding to the first message from one of the second STAs of the second non-AP MLD on one of the target links, The response message includes information about the target link.
11. The first non-AP MLD according to claim 1 or the method according to claim 3, in, The first message is one of a Tunneled Direct Link Setup (TDLS) discovery request frame, a TDLS discovery response frame, a TDLS setup request frame, a TDLS setup response frame, or a TDLS setup confirmation frame.
12. An access point (AP) multi-link device (MLD), include: An AP configured to form a first link with a first station (STA) of a first non-AP MLD and a second link with a second STA of a second non-AP MLD; as well as at least one processor operably coupled to the AP, wherein a first AP among the APs is configured to receive a first message from one of the first STAs on one of the first links, the first message including information indicating that one or more of the first links are one or more target links on which the first non-AP MLD intends to establish one or more peer-to-peer (P2P) direct links with the second non-AP MLD, The second STA of the second non-AP MLD is associated with the AP on the one or more target links, wherein the at least one processor is configured to determine that the first message is for a second non-AP MLD, and The first AP among the APs is configured to send the first message to one of the second STAs on one of the second links.
13. The AP MLD according to claim 12, in, The information included in the first message is a multilink element including link specific information associated with each of the one or more target links.
14. A method of wireless communication performed by an access point (AP) multi-link device (MLD), the AP multi-link device (MLD) comprising an AP configured to form a first link with a first station (STA) of a first non-AP MLD and a second link with a second STA of a second non-AP MLD, the method include: receiving a first message from one of the first STAs on one of the first links; Determining that the first message is for a second non-AP MLD; as well as sending the first message to one of the second STAs on one of the second links, wherein the first message includes information indicating that one or more of the first links are one or more target links on which the first non-AP MLD intends to establish one or more peer-to-peer (P2P) direct links with the second non-AP MLD, and The second STA of the second non-AP MLD is associated with the AP on the one or more target links.
15. The method according to claim 14, in, The information included in the first message is a multilink element including link specific information associated with each of the one or more target links.
