Joint transmission operation in WI-FI networks

Abstract

A method and apparatus for joint transmission operation in a Wi-Fi network. A method of wireless communication performed by a first access point (AP) includes identifying that a first AP and a second AP of a plurality of APs want to perform joint transmission (JTX) with a station associated with the first AP and the second AP. The method also includes initiating a JTX procedure, the JTX procedure including forming a logical AP multilink device (MLD) or a virtual AP MLD with the second AP to perform the JTX.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication systems, and more particularly to joint transmission operations in Wi-Fi networks. Background Art

[0002] Wireless Local Area Network (WLAN) technology allows devices to access the Internet in the 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz frequency bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. The IEEE 802.11 standard family aims to increase speed and reliability and extend the operating range of wireless networks.

[0003] In the past decade, with the growth in the number of personal wireless devices as well as wireless infrastructure, the popularity of indoor positioning has also grown in parallel. Its use cases are rich and include smart homes and buildings, surveillance, disaster management, industry, and healthcare, all of which require wide availability and good accuracy. A key step in most positioning / localization solutions is ranging, which involves identifying the distance (or difference in distance) between a target device and a set of anchor devices with known locations. Accordingly, several ranging techniques have been proposed in Ultra-Wideband (UWB), LiDAR, and WiFi. In fact, WiFi standard groups (such as 802.11 mc and 802.11 az) have been specifically customized to enable accurate WiFi-based ranging via the Fine Timing Measurement (FTM) protocol. Several such FTM methods have been proposed: EDCA-based ranging, Trigger-Based (TB) ranging, non-TB ranging, passive TB ranging, etc. Summary of the Invention

[0004] Technical Solution

[0005] Embodiments of the present disclosure provide methods and apparatuses for joint transmission operations in Wi-Fi networks.

[0006] In one embodiment, a method of wireless communication performed by a first Access Point (AP) includes determining (or identifying) that a first AP and a second AP among a plurality of APs want to perform joint transmission (JTX) with a station (STA) associated with the first AP and the second AP. The method further includes initiating a JTX process that includes forming a logical AP Multi-Link Device (MLD) or a virtual AP MLD with the second AP to perform JTX.

[0007] In another embodiment, a first access point (AP) device includes a transceiver configured to communicate with a corresponding station (STA) over a link. A processor is operably coupled to the transceiver and is configured to: determine (or identify) that a first AP and a second AP among a plurality of APs want to perform joint transmission (JTX) with stations (STAs) associated with the first AP and the second AP; and initiate a JTX process that includes forming a logical AP multi-link device (MLD) or a virtual AP MLD with the second AP to perform JTX.

[0008] Other technical features may be apparent to those skilled in the art from the following drawings, description, and claims.

[0009] Before proceeding with the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with each other. The terms "send," "receive," and "communicate," and their derivatives, cover both direct and indirect communication. The terms "include" and "comprise," and their derivatives, mean including but not limited to. The term "or" is inclusive and means and / or. The phrase "associated with," and its derivatives, mean including, being included within, interconnecting with, containing, being contained within, connected to or with, coupled to or with, capable of communicating with, cooperating with, interlacing, juxtaposing, proximate to, bound to or with, having, having the properties of, having a relationship to or with, and the like. The term "controller" means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or in a combination of hardware and software and / or firmware. The functions associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase "at least one of" when used with a list of items 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 "first" and "second" or "1st" and "2nd" may be used simply to distinguish corresponding components from another component and do not otherwise limit the components (e.g., importance or order). It should be understood that if an element (e.g., a first element) is referred to as being "coupled," "coupled to," "connected to" or "connected with" another element (e.g., a second element), with or without the terms "operably" or "communicatively," it means that the element can be coupled to the other element directly (e.g., wired), wirelessly, or via a third element.

[0010] As used herein, the term "module" may include units implemented in hardware, software, or firmware, and may be used interchangeably with other terms such as "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).

[0011] In addition, the various functions described below may be implemented or supported by one or more computer programs, each formed of 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 appropriate 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 read-only memory (ROM), random access memory (RAM), hard disk drive, compact disk (CD), digital video disk (DVD), or any other type of memory. A "non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transitory electrical signals or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media in which data can be stored and later rewritten, such as rewritable optical disks or erasable memory devices.

[0012] Definitions of 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 the prior as well as future use of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] To more fully understand the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

[0014] Figure 1 An example wireless network in accordance with various embodiments of the present disclosure is shown;

[0015] Figure 2A An example AP in accordance with various embodiments of the present disclosure is shown;

[0016] Figure 2B An example STA in accordance with various embodiments of the present disclosure is shown;

[0017] Figure 3Shows an example of a single AP transmission according to various embodiments of the present disclosure;

[0018] Figure 4 Shows an example of a joint transmission scheme according to various embodiments of the present disclosure;

[0019] Figure 5 Shows an example of simultaneously serving a STA via multiple APs according to various embodiments of the present disclosure;

[0020] Figure 6 Shows an example of channel access according to various embodiments of the present disclosure;

[0021] Figure 7 Shows another example of channel access according to various embodiments of the present disclosure;

[0022] Figure 8 Shows yet another example of channel access according to various embodiments of the present disclosure;

[0023] Figure 9 Shows an example of a joint transmission scheme based on a logical AP MLD established according to various embodiments of the present disclosure;

[0024] Figure 10 Shows an example of a method for forming a logical AP MLD for joint transmission according to various embodiments of the present disclosure;

[0025] Figure 11 Shows an example of establishing the architecture of a logical AP MLD for joint transmission according to various embodiments of the present disclosure;

[0026] Figure 12 Shows an example of dividing shared and non-shared component groups for joint transmission purposes according to various embodiments of the present disclosure;

[0027] Figure 13 Shows an example of establishing a virtual AP for joint transmission according to various embodiments of the present disclosure;

[0028] Figure 14 Shows an example of a method for setting operation parameters of a JTX logical AP MLD according to various embodiments of the present disclosure;

[0029] Figure 15 Shows an example of a method for forming a group of a JTX logical AP MLD according to various embodiments of the present disclosure;

[0030] Figure 16 Shows an example of a method for an AP to join a logical APO MLD for JTX according to various embodiments of the present disclosure;

[0031] Figure 17 An example of a method for an AP to announce a MAC address for communication via a logical AP MLD to participate in JTX according to various embodiments of the present disclosure is shown;

[0032] Figure 18 An example of a method for transmitting management frames by an AP set attached to a logical AP MLD according to various embodiments of the present disclosure is shown;

[0033] Figure 19 An example of a method for a channel probing initiation process according to various embodiments of the present disclosure is shown;

[0034] Figure 20 An example of a method for a channel probing process according to various embodiments of the present disclosure is shown;

[0035] Figure 21 An example of a method for a channel probing feedback collection process according to various embodiments of the present disclosure is shown;

[0036] Figure 22 An example of a method for a channel probing feedback processing process according to various embodiments of the present disclosure is shown;

[0037] Figure 23 An example of a method for a data sharing process for JTX according to various embodiments of the present disclosure is shown;

[0038] Figure 24 An example format of an element according to various embodiments of the present disclosure is shown;

[0039] Figure 25 An example format of a JTX control field format according to various embodiments of the present disclosure is shown;

[0040] Figure 26 An example format of an element that a STA can send to other APs according to various embodiments of the present disclosure is shown;

[0041] Figure 27 An example format of a JTX control frame according to various embodiments of the present disclosure is shown;

[0042] Figure 28 An example operation of using an element according to various embodiments of the present disclosure is shown;

[0043] Figure 29 An example operation 2900 of using an action frame according to various embodiments of the present disclosure is shown;

[0044] Figure 30 An example JTX resource information container (RIC) frame format according to various embodiments of the present disclosure is shown;

[0045] Figure 31 Illustrates an example operation using the RIC according to various embodiments of the present disclosure;

[0046] Figure 32 Illustrates an example operation using request frames and response frames according to various embodiments of the present disclosure;

[0047] Figure 33 Illustrates an example backoff hold time process 3300 according to various embodiments of the present disclosure;

[0048] Figure 34 Illustrates an example TWT SP alignment operation according to various embodiments of the present disclosure;

[0049] Figure 35 Illustrates an example start time boundary operation according to various embodiments of the present disclosure;

[0050] Figure 36 Illustrates another example start time boundary operation according to various embodiments of the present disclosure;

[0051] Figure 37 Illustrates an example start time boundary operation based on a silent element according to various embodiments of the present disclosure;

[0052] Figure 38 Illustrates an example of a dedicated SP for JTX operation according to various embodiments of the present disclosure;

[0053] Figure 39 Illustrates an example depicting a triggered JTX operation according to various embodiments of the present disclosure;

[0054] Figure 40 Illustrates another example depicting a triggered JTX operation according to various embodiments of the present disclosure;

[0055] Figure 41 Illustrates an example operation of shortening the transmission time of an uplink transmission according to various embodiments of the present disclosure;

[0056] Figure 42 Illustrates an example early termination operation for stopping an uplink transmission according to various embodiments of the present disclosure;

[0057] Figure 43 Illustrates an example early termination operation for stopping a downlink transmission according to various embodiments of the present disclosure;

[0058] Figure 44 Illustrates another example early termination operation for stopping a downlink transmission according to various embodiments of the present disclosure; and

[0059] Figure 45 A flowchart illustrating an example of a method for wireless communication performed by a station device according to an embodiment of the present disclosure is shown. Detailed implementation

[0060] The following discussion Figures 1 to 45 and the various embodiments used to describe the principles of the present disclosure in this patent document are illustrative only and should not be construed in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0061] The following documents and standards are incorporated by reference into the present disclosure as if fully set forth herein: [1] IEEE std. 802.11-2020, "Wireless Local Area Network Medium Access Control (MAC) and Physical Layer (PHY) Specifications"; [2] IEEE P802.11az / D5.0.

[0062] Figure 1 An example wireless network 100 according to various embodiments of the present disclosure is shown. Figure 1 The illustrated embodiments of the wireless network 100 are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

[0063] The wireless network 100 includes access points (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 networks. The AP 101 provides wireless access to the network 130 for a plurality of stations (STAs) 111 - 114 within the coverage area 120 of the AP 101. The APs 101 - 103 may communicate with each other and with the STAs 111 - 114 using WI-FI or other WLAN communication technologies. The STAs 111 - 114 may communicate with each other using peer-to-peer protocols such as Tunnel Direct Link Setup (TDLS).

[0064] 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 the present disclosure to refer to a network infrastructure component that provides wireless access to remote terminals. In a WLAN, since an AP also competes for wireless channels, an AP may also be referred to as a STA. Additionally, 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 the present disclosure to refer to remote wireless equipment that wirelessly accesses an AP or competes for wireless channels 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.).

[0065] The dashed lines illustrate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that the coverage areas associated with an AP (such as coverage areas 120 and 125) can have other shapes, including irregular shapes, depending on the configuration of the AP and the variations in the radio environment associated with natural and man-made obstacles.

[0066] As described in more detail below, one or more of the APs can include circuitry and / or programming for facilitating coordinated transmission operations in a Wi-Fi network. Although Figure 1 an example of a wireless network 100 is shown, 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 those STAs to network 130. Similarly, each of APs 101 - 103 can communicate directly with network 130 and provide direct wireless broadband access to STAs to network 130. Further, APs 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).

[0067] Figure 2A An example AP 101 according to various embodiments of the present disclosure is shown. Figure 2A The embodiment of AP 101 shown in Figure 1 is for illustrative purposes only, and Figure 2A AP 103 can have the same or similar configuration. However, APs have a wide variety of configurations, and

[0068] AP 101 includes a plurality of antennas 204a - 204n and a plurality of transceivers 209a - 209n. AP 101 also includes a controller / processor 224, a memory 229, and a backhaul or network interface 234. The transceivers 209a - 209n receive incoming radio frequency (RF) signals from the antennas 204a - 204n, such as signals transmitted by STAs 111 - 114 in network 100. The transceivers 209a - 209n down - convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in the transceivers 209a - 209n and / or the controller / processor 224, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The controller / processor 224 may further process the baseband signal.

[0069] The transmit (TX) processing circuitry in the transceivers 209a - 209n and / or the controller / processor 224 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 circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceivers 209a - 209n up - convert the baseband or IF signal to an RF signal transmitted via the antennas 204a - 204n.

[0070] The controller / processor 224 may include one or more processors or other processing devices that control the overall operation of AP 101. For example, the controller / processor 224 may control the transceivers 209a - 209n to receive forward - channel signals and transmit reverse - channel 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 the plurality of 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 sub - carriers for different receivers (e.g., different STAs 111 - 114). The controller / processor 224 may support any of a variety of other functions in AP 101, including facilitating joint transmission operations in a Wi - Fi network. In some embodiments, the controller / processor 224 includes at least one microprocessor or microcontroller. The controller / processor 224 is also capable of running programs and other processes resident in the memory 229, such as an OS. The controller / processor 224 may move data into or out of the memory 229 as needed during the operation of the process.

[0071] The controller / processor 224 is also coupled to a backhaul or network interface 234. The backhaul or network interface 234 allows the AP 101 to communicate with other devices or systems via a backhaul connection or over a network. The interface 234 can support communication over any suitable wired or wireless connection. For example, the interface 234 can allow the AP 101 to communicate via 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 an Ethernet or RF transceiver. The memory 229 is coupled to the controller / processor 224. A portion of the memory 229 can include RAM, and another portion of the memory 229 can include flash memory or other ROM.

[0072] As described in more detail below, the AP 101 can include circuitry and / or programming for facilitating coordinated transmission operations in a Wi-Fi network. Although Figure 2A an example of the AP 101 is shown, various changes can be made to Figure 2A it. For example, the AP 101 can include any number of Figure 2A each of the components shown. As a specific example, the access point can include multiple interfaces 234, and the controller / processor 224 can support routing functions to route data between different network addresses. Alternatively, only one antenna and transceiver path can be included, such as in a conventional AP. Additionally, Figure 2A the various components in

[0073] Figure 2B can be combined, further subdivided, or omitted, and additional components can be added according to specific needs. Figure 2B The embodiment of the STA 111 shown in Figure 1 is for illustration only, and the STAs 111 - 115 in Figure 2B can have the same or similar configurations. However, STAs have a wide variety of configurations, and

[0074] the present disclosure is not limited to any particular implementation of the STA.

[0075] One or more transceivers 210 receive incoming RF signals (e.g., transmitted by AP 101 of network 100) from one or more antennas 205. One or more transceivers 210 down-convert the incoming RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in one or more of transceivers 210 and / or processor 240, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry sends the processed baseband signal to speaker 230 (such as for voice data) or to be processed by processor 240 (such as for web browsing data).

[0076] TX processing circuitry in one or more of transceivers 210 and / or processor 240 receives analog or digital voice data from microphone 220, or other outgoing baseband data (such as web data, email, or interactive video game data) from processor 240. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. One or more transceivers 210 up-convert the baseband or IF signal to an RF signal transmitted via one or more antennas 205.

[0077] Processor 240 may include one or more processors and runs a basic OS program 261 stored in memory 260 to control the overall operation of STA 111. In one such operation, processor 240 controls the reception of forward channel signals and the transmission of reverse channel signals by one or more transceivers 210 according to well-known principles. Processor 240 may also include processing circuitry configured to facilitate joint transmission operations in a Wi-Fi network. In some embodiments, processor 240 includes at least one microprocessor or microcontroller.

[0078] Processor 240 is also capable of running other processes and programs residing in memory 260, such as operations for facilitating joint transmission operations in a Wi-Fi network. Processor 240 may move data into or out of memory 260 as needed for running processes. In some embodiments, processor 240 is configured to run multiple applications 262, such as applications for facilitating joint transmission operations in a Wi-Fi network. Processor 240 may operate multiple applications 262 based on OS program 261 or in response to signals received from an AP. Processor 240 is also coupled to an I / O interface 245, which provides STA 111 with the ability to connect to other devices such as laptop computers and handheld computers. I / O interface 245 is a communication path between these accessories and processor 240.

[0079] The processor 240 is also coupled to an input 250 and a display 255. The input 250 includes, for example, a touch screen, a keyboard, etc. 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 presenting text and / or at least limited graphics such as from a website. The memory 260 is coupled to the processor 240. A portion of the memory 260 can include random access memory (RAM), and another portion of the memory 260 can include flash memory or other read-only memory (ROM).

[0080] Although Figure 2B an example of the STA 111 is shown, various changes can be made Figure 2B thereto. For example, various components in Figure 2B can be combined, further subdivided, or omitted, and additional components can be added according to specific needs. In a specific example, the STA 111 can include any number of (one or more) antennas 205 for MIMO communication with the AP 101. In another example, the STA 111 may not include voice communication, or the 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 Figure 2B the STA 111 is shown configured as a mobile phone or a smart phone, the STA can be configured to operate as other types of mobile or fixed devices.

[0081] Various embodiments of the present disclosure recognize that the growing demand for indoor Wi-Fi connectivity has led to an increase in the number of co-deployed APs in indoor areas. Such multi-AP networks typically employ a limited form of coordination for various network functions, including but not limited to spectrum sharing, interference management, etc. To improve the efficiency of such networks, many multi-AP coordination schemes are available. One such method is to implement joint transmission, where multiple APs pool their antennas together to achieve the effect of a large AP performing multi-user, multi-input, multi-output (MU-MIMO) transmission on the downlink.

[0082] To illustrate the difference between single-AP transmission and joint transmission, consider Figure 3 and Figure 4 the depictions in

[0083] Figure 3 FIG. shows an example of a single-AP transmission 300 according to various embodiments of the present disclosure. Figure 3 The embodiments of the example of the single-AP transmission 300 shown in are for illustrative purposes only. Other embodiments of the example of the single-AP transmission 300 can be used without departing from the scope of the present disclosure.

[0084] As Figure 3 shown, three APs, namely AP1, AP2, and AP3, are deployed in an area and share the same frequency resources (e.g., frequency band, channel, and bandwidth). STA1, STA2, and STA3 are associated with AP1, AP2, and AP3 respectively. Since all APs share the same frequency resources, they can send to their respective STAs one at a time.

[0085] Figure 4 An example of a joint transmission scheme 400 according to various embodiments of the present disclosure is shown. Figure 4 The embodiments of the example of the joint AP transmission 400 shown are for illustrative purposes only. Other embodiments of the example of the joint AP transmission 400 may be used without departing from the scope of the present disclosure.

[0086] In Figure 4 the shown example of joint transmission, AP1, AP2, and AP3 pool their antennas together, thus acting as a large AP with a larger number of antennas. These three APs acting as one large AP perform downlink MU-MIMO transmission to STA1, STA2, and STA3. In a single AP transmission, the medium would be time-shared. However, in the case of joint transmission when the APs send data simultaneously, the network throughput is increased threefold.

[0087] Various embodiments of the present disclosure recognize that joint transmission promises significant gains in network throughput. However, to achieve the gains, a large amount of coordination is required between the APs. For example, the APs need to coordinate with each other to perform sounding, collection of sounding feedback, and data sharing. An architecture that can effectively achieve such coordination is needed. In addition, various embodiments of the present disclosure recognize that when a STA is served via joint transmission (JTX), it can be served simultaneously via multiple APs.

[0088] Figure 5 An example of a STA being served simultaneously via multiple APs 500 according to various embodiments of the present disclosure is shown. Figure 5 The embodiments of the STA being served simultaneously via multiple APs 500 shown are for illustrative purposes only. Other embodiments of the STA being served simultaneously via multiple APs 500 may be used without departing from the scope of the present disclosure.

[0089] As Figure 5As shown, STA1 is associated with AP1. During JTX, STA1 can also receive frames from AP2 and AP3. Currently, STA1 can be associated with only one AP. However, without an association with AP2 and AP3, STA1 may not know how to handle frames from these APs. In addition, the DS also needs to know the mapping so that it can also route packets of STA1 to AP2 and AP3. This mapping is created based on the association in the standard.

[0090] Various embodiments of the present disclosure recognize that in order to perform joint transmission, all participating APs need to be able to access the channel simultaneously. Channel access for joint transmission based on traditional channel access mechanisms may lead to inefficient operation. Several examples are provided below.

[0091] Suppose AP1, AP2, and AP3 are three APs participating in joint transmission. Suppose the channel access follows a contention-based channel access process. Thus, each of the APs can select a backoff timer and count down to obtain channel access. Since the backoff counter values are selected individually and randomly by each device, the probability that each AP starts competing at the exact same time and also selects the same backoff counter is low. Therefore, it is possible that when one or more of the other APs participating in JTX count down to zero, the backoff counters of one or more APs do not count down to zero.

[0092] Figure 6 An example of channel access 600 according to various embodiments of the present disclosure is shown, where AP2 and AP3 count down to zero simultaneously, while AP1 counts down to zero at a different time from AP2 and AP3. Figure 6 The embodiment of channel access shown, where AP2 and AP3 count down to zero simultaneously while AP1 counts down to zero at a different time from AP2 and AP3, is for illustrative purposes only. Other embodiments of channel access can be used without departing from the scope of the present disclosure, where AP2 and AP3 count down to zero simultaneously while AP1 counts down to zero at a different time from AP2 and AP3.

[0093] Figure 7 Another example of channel access 700 according to various embodiments of the present disclosure is shown, where AP1 has an ongoing downlink transmission to STA1, which is not served by JTX. Figure 7 The embodiment of channel access shown, where AP1 has an ongoing downlink transmission to STA1 while that STA1 is not served by JTX, is for illustrative purposes only. Other embodiments of channel access can be used without departing from the scope of the present disclosure, where AP1 has an ongoing downlink transmission to STA1, which is not served by JTX.

[0094] Figure 8 FIG. 800 shows another example of channel access according to various embodiments of the present disclosure, where each AP can win channel access simultaneously, but wins channel access for different access categories. Figure 8 The embodiment of channel access shown in FIG., i.e., each AP can win channel access simultaneously, but wins channel access for different access categories, is for illustration only. Other embodiments of channel access can be used without departing from the scope of the present disclosure, where each AP can win channel access simultaneously, but wins channel access for different access categories.

[0095] As Figure 6 shown in the example of FIG., AP2 and AP3 count down to zero simultaneously. Unfortunately, AP1 may be unavailable for many reasons. For example, it may not be ready because it has postponed an ongoing uplink transmission from STA1. Thus, the joint transmission cannot start. It is also possible that not all STAs can be served via JTX. Thus, AP1 can have an ongoing downlink transmission to STA1, which is not served via JTX, as Figure 7 shown in FIG.. Similar problems can also occur in trigger-based access. In another example, it is possible that each AP can win the channel simultaneously, but wins the channel for different access categories (ACs), as Figure 8 shown in FIG..

[0096] Therefore, various embodiments of the present disclosure provide mechanisms to facilitate channel access for JTX in Wi-Fi networks. Various embodiments of the present disclosure provide an architecture for implementing joint transmission and provide various processes for implementing joint transmission in this architecture.

[0097] In addition, various embodiments of the present disclosure provide solutions for handling the establishment process of JTX, including: an explicit association-based process and corresponding signaling; an AP-assisted establishment process and corresponding signaling; an association-free establishment process; a negotiation process and corresponding signaling; a disassociation and tear-down process; and a capability advertisement process.

[0098] In addition, various embodiments of the present disclosure provide solutions for handling JTX channel access, including: a process for achieving start-time synchronization of JTX; a process for start-time synchronization based on backoff hold time; a timing synchronization process based on service period and start-time boundary advertisement; a trigger-based channel access mechanism for JTX; a process for stopping ongoing downlink and uplink transmissions to enable JTX; a coordinated channel access competition process for JTX; and a capability advertisement process.

[0099] Figure 9An example of a joint transmission scheme 900 based on logical AP MLD according to various embodiments of the present disclosure is shown. Figure 9 The embodiments of the joint transmission scheme 900 based on logical AP MLD shown in are for illustrative purposes only. Other embodiments of the joint transmission scheme 900 based on logical AP MLD may be used without departing from the scope of the present disclosure.

[0100] According to one embodiment, an AP that wants to perform joint transmission may form an AP MLD for the purpose of joint transmission as shown in Figure 9 The AP MLD may be a logical / virtual entity rather than a physical entity.

[0101] Figure 10 An example of a method 1000 for forming a logical AP MLD for joint transmission according to various embodiments of the present disclosure is shown. Figure 10 The embodiments of the method 1000 for forming a logical AP MLD for joint transmission shown in are for illustrative purposes only. Other embodiments of the method 1000 for forming a logical AP MLD for joint transmission may be used without departing from the scope of the present disclosure.

[0102] As shown in Figure 10 The method 1000 begins at step 1002, where a determination is made as to whether the AP wants to support joint transmission. If the AP does not wish to support joint transmission, no action is required, as shown in step 1004. If the AP wants to support joint transmission, then at step 1006, the AP may form a logical AP MLD for performing joint transmission.

[0103] Figure 11 An example of an architecture establishment 1100 of a logical AP MLD for joint transmission according to various embodiments of the present disclosure is shown. Figure 11 The embodiments of the architecture establishment 1100 of the logical AP MLD for joint transmission shown in are for illustrative purposes only. Other embodiments of the architecture establishment 1100 of the logical AP MLD for joint transmission may be used without departing from the scope of the present disclosure.

[0104] The logical AP MLD may have an architecture including a physical layer, a lower MAC sub-layer, and an upper MAC sub-layer. For the case of two APs, the architecture may be as depicted in Figure 11 shown.

[0105] Figure 12 An example of a division 1200 of a shared component group and a non-shared component group for the purpose of joint transmission according to various embodiments of the present disclosure is shown. Figure 12The example embodiment of the division 1200 of the shared component group and the non - shared component group for the purpose of joint transmission shown is for illustrative purposes only. Other embodiments of the example of the division 1200 of the shared component group and the non - shared component group for the purpose of joint transmission can be used without departing from the scope of the present disclosure.

[0106] The various components of the logical AP MLD can be divided into two groups, namely the shared component group and the non - shared component group. The shared component group can perform functions common to all APs that form the logical AP MLD (e.g., functions in the upper MAC sub - layer). The non - shared component group can perform functions specific to each AP (e.g., functions in the PHY layer).

[0107] The non - shared component group can be hosted on the AP itself (i.e., the physical device). The shared component group can be offloaded to any device that is connected to all APs and can communicate with all APs (e.g., a central controller). An example division of the shared component group and the non - shared component group is as Figure 12 shown.

[0108] According to one embodiment, both the upper MAC sub - layer and the lower MAC sub - layer can be part of the shared component group. Thus, the AP itself can implement the PHY, while all lower MAC sub - layer functions can occur on the device hosting the shared component group. This division can be useful for cases where the network is customized for joint transmission. This can be useful for an implementation where the AP is customized for joint transmission and only carries the necessary physical layer components.

[0109] According to another embodiment, the shared component group can be hosted / implemented on one of the APs participating in the joint transmission. Then, that AP can coordinate with other APs via backhaul or over - the - air.

[0110] Figure 13 An example 1300 of virtual AP establishment for joint transmission according to various embodiments of the present disclosure is shown. Figure 13 The example embodiment of the virtual AP establishment example 1300 for joint transmission shown is for illustrative purposes only. Other embodiments of the virtual AP establishment example 1300 for joint transmission can be used without departing from the scope of the present disclosure.

[0111] According to one embodiment, there can be a master AP and a group of supporting APs that can form a virtual AP. As Figure 13 shown, the master AP can coordinate with the supporting APs for the purpose of joint transmission. This coordination can include but is not limited to sharing data frames, triggering data transmission, etc.

[0112] In another example, the master AP can also carry the shared components of the protocol stack, while the supporting APs, i.e., AP1 - AP3, can carry the non - shared components of the protocol stack. Thus, the combined master AP and supporting APs can operate as a logical AP MLD.

[0113] According to one embodiment, the APs participating in the formation of the logical AP MLD for joint transmission purposes can have the same operating parameters.

[0114] Figure 14 An example of a method 1400 for setting the operating parameters of a JTX logical AP MLD according to various embodiments of the present disclosure is shown. Figure 14 The embodiments of the method 1400 for setting the operating parameters of the JTX logical AP MLD shown are for illustrative purposes only. Other embodiments of the method 1400 for setting the operating parameters of the JTX logical AP MLD can be used without departing from the scope of the present disclosure.

[0115] As Figure 14 shown, the method 1400 starts at step 1402, where a determination is made as to whether the AP is part of the logical AP MLD for JTX. If the AP is not part of the logical AP MLD for JTX, no action is required, as shown in step 1404. If the AP is part of the logical AP MLD for JTX, then at step 1406, the AP can have the same operating parameters, such as the same frequency band, channel, and bandwidth.

[0116] According to one embodiment, the APs participating in the formation of the logical AP MLD can have the same operating frequency band, channel, and bandwidth. According to this embodiment, the APs participating in the formation of the logical AP MLD can have the same operating frequency band, channel, and bandwidth. Thus, all APs that are part of the logical AP MLD can use the same frequency band, channel, and bandwidth. In one embodiment, the master AP / controller can advertise the operating information by sending a message that can include at least one or more of the information items indicated in Table 1. The message that can include at least one or more of the information items indicated in Table 1 can be, for example, an operating frequency advertisement message.

[0117] [Table 1]

[0118]

[0119] The above - mentioned information items can be sent together or separately. They can be sent as part of any existing frame / element / field / sub - field in the standard, or can be part of a newly defined frame / element / field / sub - field.

[0120] Upon receiving this information from the master AP / controller, the APs participating in JTX can configure their bands and channels to the appropriate configuration.

[0121] Figure 15 An example of a method 1500 for group formation of JTX logical AP MLDs according to various embodiments of the present disclosure is shown. Figure 15 The illustrated embodiment of the method 1500 for group formation of JTX logical AP MLDs is for illustration only. Other embodiments of the method 1500 for group formation of JTX logical AP MLDs may be used without departing from the scope of the present disclosure.

[0122] like Figure 15 As shown, method 1500 begins at step 1502, where a determination is made whether the JTX requires a logical AP MLD. If the JTX does not require a logical AP MLD, no action is required, as shown at step 1504. If the JTX requires a logical AP MLD, then at step 1506, the APs may form a group for the logical AP MLD.

[0123] According to one embodiment, a logical AP MLD may be established in the implementation for the purpose of joint transmission and all APs may permanently become part of it. According to another embodiment, APs that intend to perform joint transmission may create a group and form a group such as Figure 15 Logical AP MLD shown. Therefore, different APs can dynamically join and leave the group.

[0124] According to one embodiment, one of the APs operating as a master AP / controller may send a message to announce the secondary APs that may participate in JTX. The message may not be limited to logical AP MLD establishment, and may also be generally applicable to other establishments (e.g., virtual AP establishment). The message may contain at least one or more of the information items indicated in Table 2 below. Table 2 may indicate the information items that may be present in the announcement message.

[0125] [Table 2]

[0126]

[0127] The above information items may be sent together or separately. They may be sent as part of any existing frame / element / field / subfield in the standard, or may be part of a newly defined frame / element / field / subfield.

[0128] According to one embodiment, an AP that is part of a group can advertise the logical AP MLD in frames (e.g., management frames) that it sends. According to this embodiment, STAs and neighboring APs that receive such frames can discover the logical AP MLD. According to another embodiment, an AP can receive a list of APs that are part of the logical AP MLD via backhaul communication with a shared component group and a device (e.g., a central controller) that hosts the shared component group.

[0129] Figure 16 An example of a method 1600 for an AP to join a logical APO MLD for JTX according to various embodiments of the present disclosure is shown. Figure 16 The illustrated embodiment of the method 1600 for an AP to join a logical APO MLD for JTX is for illustrative purposes only. Other embodiments of the method 1600 for an AP to join a logical APO MLD for JTX may be used without departing from the scope of the present disclosure.

[0130] As Figure 16 shown, the method 1600 begins at step 1602, where a determination is made as to whether the AP intends to join a logical AP MLD for JTX. If the AP has no intention of joining a logical AP MLD for JTX, no action is required, as shown in step 1604. If the AP intends to join a logical AP MLD for JTX, then at step 1606, the AP can send a request frame to one of the APs attached to the logical AP MLD.

[0131] According to one embodiment, an AP interested in joining the group can send a frame to one of the APs that is part of the logical AP MLD / virtual AP to make such an indication, as Figure 16 shown.

[0132] The frame can include one or more information items indicated in Table 3. Table 3 can indicate the information items that can be present in a frame sent by an AP to join a logical AP MLD.

[0133] [Table 3]

[0134]

[0135] Upon receiving the frame, if the logical AP MLD can satisfy the AP's request, one of the APs attached to the logical AP MLD can send a response frame containing the information shown in Table 4 to the AP. Table 4 can indicate the information items that can be present in a frame sent by an AP attached to the logical AP MLD.

[0136] [Table 4]

[0137]

[0138] According to one embodiment, an AP intending to leave the group may notify the shared component group of its intention to leave the group. After that, the AP may leave the group at a specified time.

[0139] Figure 17 An example of method 1700 for an AP participating in JTX via logical AP MLD to announce a MAC address for communication is shown in accordance with various embodiments of the present disclosure. Figure 17 The embodiments of method 1700 for an AP participating in JTX via logical AP MLD to announce a MAC address for communication shown are for illustrative purposes only. Other embodiments of method 1700 for an AP participating in JTX via logical AP MLD to announce a MAC address for communication may be used without departing from the scope of the present disclosure.

[0140] As Figure 17 shown, method 1700 begins at step 1702, where a determination is made as to whether the AP is attached to a logical AP MLD for JTX. If the AP is not attached to a logical AP MLD for JTX, no action is required, as shown in step 1704. If the AP is attached to a logical AP MLD for JTX, then at step 1706, the AP may use the same MAC address as other APs attached to the logical AP MLD.

[0141] According to one embodiment, APs participating in joint transmission via logical AP MLD may announce the same MAC address. Thus, to the STAs, they all appear to be part of one AP with many antennas. Additionally, according to one embodiment, the MAC address may be an address specifically allocated for the purpose of joint transmission. According to another embodiment, the MAC address may be the address of one of the APs that is part of the group. The AP may be required to never leave the group.

[0142] According to another embodiment, APs participating in logical AP MLD may announce different MAC addresses (e.g., their own individual MAC addresses).

[0143] Figure 18 An example of method 1800 for transmitting management frames by a set of APs attached to a logical AP MLD is shown in accordance with various embodiments of the present disclosure. Figure 18 The embodiments of method 1800 for transmitting management frames by a set of APs attached to a logical AP MLD shown are for illustrative purposes only. Other embodiments of method 1800 for transmitting management frames by a set of APs attached to a logical AP MLD may be used without departing from the scope of the present disclosure.

[0144] AsFigure 18 As shown, method 1800 begins at step 1802, where a determination is made as to whether a logical AP MLD for JTX has been formed. If a logical AP MLD for JTX has not been formed, then no action is required, as shown at step 1804. If a logical AP MLD for JTX has been formed, then at step 1806, an AP set selected from the AP MLD can send a management frame.

[0145] According to one embodiment, the management frame can be sent by all APs that are part of the logical AP MLD.

[0146] According to another embodiment, only a selected AP set that is part of the logical AP MLD can send the management frame. Since all APs use the same operating parameters, this can help reduce the overhead of management frame transmissions.

[0147] According to one embodiment, these APs can be determined by a shared component group such that all STAs in the area can receive the management frame.

[0148] Figure 19 An example of method 1900 for a channel probing initiation process according to various embodiments of the present disclosure is shown. Figure 19 The embodiment of method 1900 for the channel probing initiation process shown in is for illustrative purposes only. Other embodiments of method 1900 for the channel probing initiation process can be used without departing from the scope of the present disclosure.

[0149] As Figure 19 shown, method 1900 begins at step 1902, where a determination is made as to whether channel probing needs to be started for JTX. If channel probing does not need to be started for JTX, then no action is required, as shown at step 1904. If channel probing needs to be started for JTX, then at step 1906, the shared component group can send an internal trigger frame to the non-shared component group.

[0150] According to one embodiment, when a channel probing process needs to be initiated, the shared component group / primary AP can send an internal trigger to the non-shared component group for channel probing process initiation, as Figure 19 shown.

[0151] An internal trigger may include the information necessary to initiate a sounding process. For example, if the lower MAC sublayer is part of a shared component group, it may generate NDPA and NDP frames and pass them to the non-shared component group (in this case, which may include the PHY layer) via the internal trigger. The internal trigger may be sent over the backhaul (e.g., if the device implementing the shared component group is a central controller) or it may be sent over the air (e.g., if the device implementing the shared component group is part of one of the APs in an AP). When sent over the air, the information may be sent in a standalone frame or as part of any existing frame in the standard (e.g., an existing trigger frame).

[0152] Figure 20 An example of a method 2000 for a channel sounding process according to various embodiments of the present disclosure is shown. Figure 20 The embodiments of the method 2000 for the channel sounding process shown are for illustrative purposes only. Other embodiments of the method 2000 for the channel sounding process may be used without departing from the scope of the present disclosure.

[0153] As Figure 20 shown, the method 2000 begins at step 2002, where a determination is made as to whether the AP has received an internal trigger. If the AP has not received an internal trigger, no action is required, as shown in step 2004. If the AP has received an internal trigger, then at step 2006, the AP may send a Null Data Packet Announcement (NPDA) frame. Then, at step 2008, the AP may wait for a Short Inter-Frame Space (SIFS). Thereafter, at step 2010, the AP may send a Null Data Packet (NDP).

[0154] Upon receiving an internal trigger, an affiliated AP may send an NDPA frame, followed by an NDP frame, as Figure 20 shown. The duration between the reception of the internal trigger frame and the start of the NDPA frame may be a fixed value (e.g., SIFS) or may be a value specified in the internal trigger itself.

[0155] According to another embodiment, upon receiving an internal trigger, one of the APs may send another trigger frame over the air to other APs affiliated with the logical APMLD for calculating parameters to enable joint transmission (e.g., CFO estimation, SFO for synchronization, etc.).

[0156] Figure 21 An example of a method 2100 for a channel sounding feedback collection process according to various embodiments of the present disclosure is shown. Figure 21The embodiment of method 2100 for channel sounding feedback collection process shown is for illustration only. Other embodiments of method 2100 for channel sounding feedback collection process may be used without departing from the scope of the present disclosure.

[0157] As Figure 21 shown, method 2100 begins at step 2102, where a determination is made as to whether sounding feedback needs to be collected. If sounding feedback does not need to be collected, no action is required, as shown in step 2104. If sounding feedback needs to be collected, then at step 2106, the shared component group may send an internal trigger frame to the AP that will collect the feedback. Then, at step 2108, the AP may collect feedback from its STAs in the order specified in the trigger frame. Thereafter, at step 2110, the AP may provide the feedback to the shared component group.

[0158] According to one embodiment, when channel sounding feedback (e.g., BF feedback, CQI feedback) needs to be collected from STAs after a sounding process, the shared component group / master AP may send another internal trigger frame to the AP (one of the APs that collect feedback or all APs if they collect their feedback). Then, the AP may collect feedback from the STAs in the order specified in the internal trigger frame. This process may be as Figure 21 shown.

[0159] The internal trigger may be sent via the backhaul (e.g., if the device implementing the shared component group is a central controller) or it may be sent over the air (e.g., if the device implementing the shared component group is part of one of the APs). When sent over the air, the information may be sent in a standalone frame or as part of any existing frame in the standard (e.g., an existing trigger frame).

[0160] Figure 22 Shows an example of method 2200 for channel sounding feedback processing process according to various embodiments of the present disclosure. Figure 22 The embodiment of method 2200 for channel sounding feedback processing process shown is for illustration only. Other embodiments of method 2200 for channel sounding feedback processing process may be used without departing from the scope of the present disclosure.

[0161] As Figure 22As shown, method 2200 begins at step 2202, where a determination is made as to whether channel sounding feedback is complete. If the channel sounding feedback is not complete, no action is required, as shown at step 2204. If the channel sounding feedback is complete, then at step 2206, the AP may pass the feedback information to the shared component group. Then, at step 2208, the shared component group may calculate the operating parameters (e.g., the steering matrix). Thereafter, at step 2210, the shared component group may provide the calculated parameters to the AP for JTX.

[0162] Upon receiving the feedback, the AP may send the information to the shared component group, and then the shared component group may calculate the operating parameters (e.g., steering matrix calculation) required to perform the joint transmission. Then, the shared component group may send the information to the AP.

[0163] Figure 23 An example of method 2300 for a data sharing process for JTX according to various embodiments of the present disclosure is shown. Figure 23 The embodiments of method 2300 for the data sharing process for JTX shown in are for illustrative purposes only. Other embodiments of method 2300 for the data sharing process for JTX may be used without departing from the scope of the present disclosure.

[0164] As Figure 23 As shown, method 2300 begins at step 2302, where a determination is made as to whether data needs to be shared for JTX. If data does not need to be shared for JTX, no action is required, as shown at step 2304. If data needs to be shared for JTX, then at step 2306, the shared component group may send data to the AP.

[0165] For the purpose of joint transmission, the participating APs need to share the data of the STAs with each other. According to one embodiment, for the purpose of JTX, the shared component group / master AP may share the data of the STAs, where the STAs are part of a multi-user group to be served on the downlink via JTX. The shared component group / master AP may share the data with all APs before the channel sounding process begins (e.g., after sending the first internal trigger frame) or at a later time point (e.g., after the sounding feedback has been collected by the devices). Sharing the data at a later time point may be useful if the lower MAC sublayer is part of the shared component group.

[0166] According to one embodiment, upon completion of data sharing, the master AP may send a trigger message to the supporting APs to start JTX. The trigger message may include at least one or more of the information items shown in Table 5. Table 5 may indicate the information items that may be present in the trigger message.

[0167] [Table 5]

[0168]

[0169] The above information items can be sent together or individually. They can be sent as part of any existing frame / element / field / subfield in the standard, or can be part of a newly defined frame / element / field / subfield.

[0170] The trigger can also be used for the purpose of achieving synchronization between supporting APs for performing joint transmission.

[0171] According to one embodiment, an AP that can form a logical AP MLD with other nearby APs or an AP that has already formed a logical AP MLD with other APs for JTX can advertise this capability in the management frames it sends (e.g., beacons, probe response frames, etc.). This information can help STAs discover the frames and associate with them for joint transmission. The advertisement can be via an information item that can indicate the capability of the AP to support JTX. For example, there can be a capability bit / flag that can be set to a predetermined value (e.g., 1) for indication and set to another predetermined value (e.g., 0) to indicate the absence of support.

[0172] According to another embodiment, the logical AP MLD framework can be torn down for various reasons. For example, backhaul latency prevents the operation of joint transmission using the logical AP MLD. In such a scenario, the APs can fallback to their local stacks and tear down the logical AP MLD by sending a notification frame to the STAs. Based on the notification frame, the STAs can disassociate from the logical AP MLD and associate with the local stacks operating on the APs.

[0173] Embodiments in the present disclosure can also be applied to other multi-AP coordination schemes (e.g., coordinated beamforming).

[0174] According to one embodiment, a STA participating in JTX can explicitly associate with all APs participating in JTX. This explicit association can establish the mapping required for the DS to route the STA's packets to all APs. Thus, the STA can be served by all APs via JTX.

[0175] According to one embodiment, an AP can send a frame to a STA to notify the STA of other APs that the STA can be served by that other AP via JTX. The frame sent from the AP to the STA can contain at least one or more of the information items described in Table 6. Table 6 can indicate the information items that can be present in the frame sent from the AP to the STA.

[0176] [Table 6]

[0177]

[0178] The above information can be present in a newly defined frame or any existing frame in the standard. Here are a few examples. The above information can also be in a single frame or split across multiple frames.

[0179] According to another embodiment, when a STA performs an association with multiple APs, it can indicate to those APs that the association is only for the purpose of JTX. However, the primary AP or default AP with which the STA remains associated for non-JTX operations (along with JTX operations) can still be the initial AP. The STA can make such an indication to the other APs by sending a frame that can include at least one or more of the information items indicated in Table 7. Table 7 can indicate the information items that can be present in a frame sent by the STA to an AP.

[0180] [Table 7]

[0181]

[0182] The above information can be present in a newly defined frame or any existing frame in the standard. Here are a few examples. The above information can also be in a single frame or split across multiple frames.

[0183] Figure 24 An example format of element 2400 according to various embodiments of the present disclosure is shown. Figure 24 The embodiments of the example format of element 2400 shown are for illustrative purposes only. Other embodiments of the example format of element 2400 can be used without departing from the scope of the present disclosure.

[0184] According to one example, the above information in Table 6 can be carried in one element. The element can have a format as Figure 24 shown.

[0185] Figure 25 An example format of the JTX control field format 2500 according to various embodiments of the present disclosure is shown. Figure 25 The embodiments of the example format of the JTX control field format 2500 shown are for illustrative purposes only. Other embodiments of the example format of the JTX control field format 2500 can be used without departing from the scope of the present disclosure.

[0186] The AP count subfield can indicate the number of APs whose identifiers are included in the AP list field.

[0187] If a response from the STA is required when the association with other APs is completed, the response requirement subfield can be set to the value 1, otherwise 0.

[0188] The AP list can carry the AP identifier (e.g., AP MAC address) of each AP that is participating or can participate in JTX for a specific STA.

[0189] Figure 26 Illustrates an example format of element 2600 that a STA according to various embodiments of the present disclosure can send to other APs. Figure 26 The embodiments of the example format of element 2600 that the STA shown in can send to other APs are for illustration only. Other embodiments of the example format of element 2600 that the STA can send to other APs can be used without departing from the scope of the present disclosure.

[0190] According to one example, the information in Table 7 can be carried in an element within an element. The element can have a format as Figure 26 shown.

[0191] Figure 27 Illustrates an example format of the JTX control frame 2700 according to various embodiments of the present disclosure. Figure 27 The embodiments of the example format of the JTX control frame 2700 shown in are for illustration only. Other embodiments of the example format of the JTX control frame 2700 can be used without departing from the scope of the present disclosure.

[0192] The JTX control frame can have a format as Figure 27 shown. The AP count subfield can indicate the number of APs whose identifiers are listed in the JTX AP list.

[0193] If the STA wants the AP to notify the default AP identified in the default AP identifier field in Figure 26 that the STA has completed the association with the AP for JTX purposes, the response request subfield can be set to 1. Otherwise, the subfield can be set to 0.

[0194] The default AP identifier field indicates the default AP associated with the STA. The JTX AP list lists other APs that the STA intends to associate with or has associated with for JTX purposes.

[0195] Figure 26 The reception of the element in can indicate to the receiving AP that the STA is associated with the AP only for the purpose of JTX transmission.

[0196] The above elements can be carried in any frame in the standard. Example operations of using the above elements in association request and response frames can be as Figure 28 shown.

[0197] Figure 28 Illustrates an example operation 2800 of using elements according to various embodiments of the present disclosure. Figure 28The example operation 2800 of using the element shown is for illustration only. Other embodiments of the example operation 2800 of using the element may be used without departing from the scope of the present disclosure.

[0198] As Figure 28 shown, the STA starts the association process with AP1. When receiving an association request frame from the STA, the AP sends an association response frame carrying the element. The AP list in the element indicates AP2 and AP3 as the APs that can participate in JTX together with AP1. When receiving the association response frame carrying the element from AP1, the STA starts another association process with AP2 and AP3. In this association request frame, the STA can send an association request frame containing the element (described in Table 4) to AP2 and AP3. When receiving the element, AP2 and AP3 can understand that the target of the association is only for the purpose of JTX, and AP1 listed in the default AP identifier field of the element is the default AP with which the STA is associated. When this process is completed, the STA can be associated with AP1 for both JTX purposes and non-JTX purposes, and be associated with AP2 and AP3 only for JTX purposes. Thus, the DS can also forward the relevant packets of the STA to AP2 and AP3.

[0199] If needed, the AP can obtain the STA association ID from the default AP. Alternatively, the AP can assign an ID to the STA only for the purpose of JTX.

[0200] The above element can also be carried in other management frames such as action frames after the association is completed. The example action frame format can be as shown in Table 8. Table 8 can indicate the action frame format for JTX.

[0201] [Table 8]

[0202]

[0203] The category field indicates the category of the action frame.

[0204] The protected action field can enable the distinction of the protected action frame format.

[0205] The dialog token can be a non-zero value, which can be selected by the sender of the frame to identify the request / response transaction.

[0206] The reason code can indicate the reason for sending the frame, for example, as a request from the AP to the STA to request the STA to associate / connect with other APs for the purpose of JTX.

[0207] The JTX element can be Figure 24 or Figure 26 the element shown.

[0208] Figure 29 Illustrates an example operation 2900 using action frames according to various embodiments of the present disclosure. Figure 29 The embodiments of the example operation 2900 using action frames shown are for illustrative purposes only. Other embodiments of the example operation 2900 using action frames may be used without departing from the scope of the present invention.

[0209] As depicted, upon completion of the association, AP1 sends an action frame containing the Figure 24 elements in to indicate to the STA that it should connect to AP2 and AP3 for the purpose of JTX. The intention of AP1 to send the elements can be conveyed via a cause code. Upon receiving the elements, the STA may send another response in the action frame. The response may carry the same conversation token as the request, such that AP1 can understand its corresponding request. Then the STA may send a request action frame carrying the Figure 26 elements in to AP2 and AP3. AP2 and AP3 can understand the intention of the STA to send the action frame from the cause code listed in those frames. Upon completion of this process, the STA can be associated with AP1 for both JTX and non-JTX purposes, and associated with AP2 and AP3 only for JTX purposes. Thus, the DS can also forward relevant packets of the STA to AP2 and AP3.

[0210] According to one embodiment, a STA intending to participate in JTX can notify the AP of its intention to participate in JTX during the association. The STA can send an information item as part of the association process, which can indicate the intention of the STA to participate in JTX after the association. For example, a bit / flag can be set to a predetermined value (e.g., 1) to indicate the participation intention, and set to another predetermined value (e.g., 0) to indicate non-participation.

[0211] According to one embodiment, after being associated with an AP, the AP can assist the STA in associating / connecting with other APs participating in JTX. According to this embodiment, after the completion of the association process, the AP can notify other APs that can participate in JTX for this STA.

[0212] The frame sent by the AP can contain at least one or more of the information items indicated in Table 9. Table 9 can indicate the information items that can be present in the frame sent by the AP.

[0213] [Table 9]

[0214]

[0215] The above (one or more) information items may exist in a single frame or be split across multiple frames. The above information items may be carried in newly defined frames or in any existing frames in the standard. Some examples may be as follows.

[0216] Figure 30 An example JTX Resource Information Container (RIC) frame format 3000 according to various embodiments of the present disclosure is shown. Figure 30 The illustrated embodiments of the example JTX RIC frame format 3000 are for illustrative purposes only. Other embodiments of the example JTX RIC frame format 3000 may be used without departing from the scope of the present disclosure.

[0217] In one example, the information item may be carried in a new Resource Information Container (RIC). The RIC may have a format as Figure 30 shown.

[0218] The information container may include resource descriptor elements as described in Table 10. Table 10 may indicate the JTX RDE description.

[0219] [Table 10]

[0220]

[0221] The JTX RIC descriptor may include the information shown in Table 11. Table 11 may indicate the resource descriptor definition details.

[0222] [Table 11]

[0223]

[0224] Figure 31 An example operation 3100 using the RIC according to various embodiments of the present disclosure is shown. Figure 31 The illustrated embodiments of the example operation 3100 using the RIC are for illustrative purposes only. Other embodiments of the example operation 3100 using the RIC may be used without departing from the scope of the present disclosure.

[0225] As Figure 31 shown, when the association with the STA is completed, the AP1 acting as the default AP sends a frame carrying the RIC to AP2 and AP3, and the RIC provides the information items for the request frame indicated in Table 8. When receiving the request frame, each AP sends a frame carrying the response RIC. After the connection to the STA is established at each AP, the JTX establishment process is completed.

[0226] According to one embodiment, the device may perform only authentication as part of its initial establishment and skip association. Thus, each STA frame may be mapped by the DS to each AP in the network. As a result, each AP may have the STA frame. The AP that can hear the STA may serve it via JTX.

[0227] According to one embodiment, there may be a negotiation process. As part of the negotiation process, the STA may indicate to the AP that it wants to participate in JTX. Thereafter, the AP and / or the STA may perform the necessary establishment for JTX (by using any process described in this disclosure).

[0228] During negotiation, an entity (which may be an AP or an STA) may send a negotiation request frame to another entity (STA or AP). Upon receiving the negotiation request frame, the other entity may send a negotiation response frame to provide its response to the requesting entity.

[0229] The request frame may contain at least one or more of the information items indicated in Table 12. Table 12 may indicate the information items that may be present in the negotiation request frame.

[0230] [Table 12]

[0231]

[0232] The above information may be present in a single frame or more than one frame. The above information items may be carried in a newly defined frame or in any existing frame in the standard.

[0233] The response frame may contain at least one or more of the information items indicated in Table 13. Table 13 may indicate the information items that may be present in the negotiation response frame.

[0234] [Table 13]

[0235]

[0236] The above information may be present in a single frame or more than one frame. The above information items may be carried in a newly defined frame or in any existing frame in the standard.

[0237] Figure 32 An example operation 3200 using request frames and response frames according to various embodiments of the present disclosure is shown. Figure 32 The embodiments of the example operation 3200 using request frames and response frames shown are for illustration only. Other embodiments of the exemplary operation 3200 using request and response frames may be used without departing from the scope of the present disclosure.

[0238] The example operations of the request frame and the response frame may be as Figure 32As shown, the AP sends a negotiation request frame to the STA, providing an indication that the request is for JTX establishment. The STA sends a response frame. When receiving a response frame indicating a positive response, the JTX establishment process can be started (e.g., such as those described above in this disclosure).

[0239] When the STA disassociates from its default AP, the AP or the STA can start a teardown process for JTX establishment. If the AP starts the teardown process, the AP can send a RIC to other APs in the JTX establishment to notify them of the disassociation and start the teardown. If the STA starts the teardown process, the STA can notify the disassociation to another AP in the JTX establishment and initiate the teardown.

[0240] According to one embodiment, an AP / AP MLD or a STA / non-AP MLD that supports JTX or any process for JTX described in this disclosure can advertise their support for the features and / or processes in one or more frames they send. If an AP / AP MLD supports JTX or any process for JTX, it can advertise its capabilities in one or more frames it sends. In one example, these frames can be management frames such as beacons, probe responses, (re)association responses, etc. There can be fields (e.g., bits) that can take a predetermined value (e.g., 1) to indicate support and can take another predetermined value (e.g., 0) to indicate lack of support. If a STA / non-AP MLD supports JTX or any process for JTX, it can advertise its capabilities in one or more frames it sends. In one example, these frames can be management frames such as probe requests, (re)association requests, etc. There can be fields (e.g., bits) that can take a predetermined value (e.g., 1) to indicate support and can take another predetermined value (e.g., 0) to indicate lack of support.

[0241] The above processes can also be used for any applicable non-JTX related purposes and should not be considered limited to JTX.

[0242] When applicable, the above processes can also be used in architectures such as a logical AP MLD architecture.

[0243] The information items indicated in this disclosure can be carried in any frame in the standard.

[0244] Although the description in this disclosure is given in the context of an AP and a STA, it is also applicable to multi-link operations.

[0245] Figure 33 An example backoff hold time process 3300 according to various embodiments of this disclosure is shown. Figure 33The illustrated example of the backoff hold time process 3300 is for illustration only. Other embodiments of the example backoff hold time process 3300 may be used without departing from the scope of the present disclosure.

[0246] According to one embodiment, a backoff hold time process may be followed for JTX. According to this embodiment, one or more APs participating in JTX may keep their backoff counters at zero in order to be able to access the channel simultaneously. Thus, when an AP's backoff counter reaches zero, it may choose not to transmit and keep its backoff at zero, and then initiate a transmission when the backoff counters of other APs also reach zero. When following this process, each of the APs may ensure that the EDCA rules for each of the APs allow them to access the medium when issuing a PHY-TXSTART.request for that particular link. If the medium of one of the APs becomes busy, the AP may ensure that it can make the medium idle again (e.g., by using the process described in Section 4), or it may start a new backoff process using the EDCA rules. Alternatively, the AP may also postpone the transmission.

[0247] An example may be as Figure 33 shown. AP1, AP2, and AP3 are three APs performing JTX. Each AP is competing for channel access. When the backoff counter of AP1 reaches zero, the backoff counters of AP2 and AP3 have not reached zero. AP1 may keep the backoff counter at zero in order to be able to perform JTX with AP2 and AP3. When the backoff counter of AP2 reaches zero, AP2 may also keep the backoff counter to be able to perform JTX with AP1 and AP3. When the backoff counter of AP3 reaches zero, JTX may be initiated.

[0248] APs may understand the remaining backoff counters of other APs by exchanging information with each other. Thus, each AP may provide and / or request the remaining backoff counters at other APs. This may be done using an over-the-air process or by exchanging information over a backhaul / wired network (e.g., via a central controller).

[0249] When requesting information over the air, it may be done by the transmission of a frame that may include at least one or more information items indicated in Table 14, and may be done in a cross-link manner, i.e., in the case of MLO operation, information may be exchanged on other links of the AP MLD. Table 14 may indicate the information items that may exist for backoff counter information exchange.

[0250] [Table 14]

[0251]

[0252] The above information may be present in one frame or distributed across multiple frames. The above information may be present in existing frames or frames newly defined in the standard.

[0253] The AP can also increase the likelihood of being able to access the channel simultaneously by following some mechanisms to ensure that they have a higher chance of obtaining channel access at the same time.

[0254] Figure 34 An example TWT SP alignment operation 3400 according to various embodiments of the present disclosure is shown. Figure 34 The illustrated embodiments of the example TWT SP alignment operation 3400 are for illustrative purposes only. Other embodiments of the example TWT SP alignment operation 3400 may be used without departing from the scope of the present disclosure.

[0255] According to one embodiment, each AP can ensure that its TWT service period (SP) is aligned in time with the TWT service periods of other APs to increase the likelihood of synchronous JTX transmissions in those SPs. This can increase the likelihood of synchronizing the JTX start time of each AP with the JTX start times of other APs. To achieve this, each AP can send their SP start times to other APs participating in the JTX. Since the TSF timers at different APs may be different, the APs participating in the JTX can synchronize their TSF timers so that they can correctly exchange and interpret timing-related information. Alternatively, each AP can correct the start time of the SP provided or announced by other APs. An example can be depicted in Figure 9 where the SPs are synchronized to increase the likelihood of being able to access the channel for JTX simultaneously. This can apply to TWT or its variants (e.g., rTWT, bTWT, etc.).

[0256] Figure 35 An example start time boundary operation 3500 according to various embodiments of the present disclosure is shown. Figure 35 The illustrated embodiments of the example start time boundary operation 3500 in are for illustrative purposes only. Other embodiments of the example start time boundary operation 3500 may be used without departing from the scope of the present disclosure.

[0257] According to another embodiment, a JTX start time boundary can be defined and announced. The APs can coordinate with each other and determine the start time boundary. The JTX can start at the start time boundary. Other devices can stop their transmissions before the start time boundary. If the JTX does not start within a certain amount of time (e.g., a predetermined waiting time) after the start time boundary, other non-JTX transmissions can be initiated. An example can be as Figure 35As shown, STA1 is sending to AP1 and finishes its transmission before the start time boundary. At the start time boundary, AP1, AP2, and AP3 start the JTX process.

[0258] Figure 36 Another example start time boundary operation 3600 according to various embodiments of the present disclosure is shown. Figure 36 The embodiments of the example start time boundary operation 3600 shown in are for illustration only. Other embodiments of the example start time boundary operation 3600 may be used without departing from the scope of the present disclosure.

[0259] In Figure 36 In another example shown in, at the start time boundary, the backlog is not available for JTX. Therefore, after a threshold of waiting time has elapsed after the start time boundary, other non-JTX transmissions are initiated.

[0260] To announce the start time, the AP can announce the start time in the frames it sends (e.g., management frames such as beacons). Devices receiving such frames can understand the start time boundaries and follow them.

[0261] Figure 37 An example silence element-based start time boundary operation 3700 according to various embodiments of the present disclosure is shown. Figure 37 The embodiments of the example silence element-based start time boundary operation 3700 shown in are for illustration only. Other embodiments of the example silence element-based start time boundary operation 3700 may be used without departing from the scope of the present disclosure.

[0262] In one embodiment, the AP can create a start time boundary by creating a silent period using silence elements (such as those announced in beacons). The duration of the silent period in such an announcement can be set as the waiting time. Additionally, there can be an indication that can indicate that the silence element is creating a start time boundary for JTX, so that the STA can stay awake for reception. An example is as Figure 37 shown.

[0263] Figure 38 An example 3800 of a dedicated SP for JTX operation according to various embodiments of the present disclosure is shown. Figure 38 The embodiments of the example 3800 of the dedicated SP for JTX operation shown in are for illustration only. Other embodiments of the example 3800 of the dedicated SP for JTX operation may be used without departing from the scope of the present disclosure.

[0264] According to one embodiment, there may be dedicated TWT (rTWT, bTWT, etc.) scheduling for JTX. During the establishment of such a TWT, an indication that the TWT scheduling is intended for JTX may be provided to the receiver. All APs can ensure that they have the same TWT scheduling in their own BSS for JTX. The scheduling may be created via communication between APs. An example may be as Figure 38 shown.

[0265] According to another embodiment, during the rTWT SP, the JTX AP may ignore the silent period and start JTX at the start boundary of the SP.

[0266] Figure 39 An example depicting the triggered JTX operation 3900 according to various embodiments of the present disclosure is shown. Figure 39 The embodiment showing the example of the triggered JTX operation 3900 shown in

[0267] is for illustration only. Other embodiments showing the example of the triggered JTX operation 3900 may be used without departing from the scope of the present disclosure. Figure 39 An example where the entire TXOP is shared with other APs is shown in

[0268] Figure 40 Another example depicting the triggered JTX operation 4000 according to various embodiments of the present disclosure is shown. Figure 40 The embodiment showing the example of the triggered JTX operation 4000 shown in

[0269] As shown in the example, when winning channel access, AP1 sends control frames to AP2 and AP3. This may be a single control frame, or AP1 may send two control frames, one to AP2 and the other to AP3, as Figure 40 shown.

[0270] Upon receiving the control frame, AP1, AP2, and AP3 utilize the entire TXOP for JTX operations. The control frame may be a newly defined frame or any existing frame in the standard (e.g., MU-RTS TXS frame). The control frame may contain at least one or more of the information items indicated in Table 15. Table 15 may indicate the information items that may be present in the control frame.

[0271] [Table 15]

[0272]

[0273] Figure 41 Illustrates an example operation 4100 for shortening the transmission time of an uplink transmission according to various embodiments of the present disclosure. Figure 41 The illustrated embodiments of the example operation 4100 for shortening the transmission time of an uplink transmission are for illustrative purposes only. Other embodiments of the example operation 4100 for shortening the transmission time of an uplink transmission may be used without departing from the scope of the present disclosure.

[0274] According to one embodiment, to start JTX across multiple APs, some of the APs may need to stop their ongoing downlink or uplink transmissions to participate in JTX.

[0275] According to one embodiment, if an AP is close to the JTX transmission start time and receives a transmission request for an uplink transmission, the AP can reduce the TXOP in its response such that the transmission ends before the JTX start time or the expected start time. An example is as Figure 16 shown. As depicted, the STA sends an RTS to the AP, and the duration field of the RTS indicates that the transmission time does not end before the JTX start time. The AP can respond with a CTS with a reduced duration field such that the new transmission time ends before the JTX start time. Thus, the AP can shorten the transmission time of the uplink transmission to end before the JTX start time.

[0276] Figure 42 Illustrates an example early termination operation 4200 for stopping an uplink transmission according to various embodiments of the present disclosure. Figure 42 The illustrated embodiments of the example early termination operation 4200 for stopping an uplink transmission are for illustrative purposes only. Other embodiments of the example early termination operation 4200 for stopping an uplink transmission may be used without departing from the scope of the present disclosure.

[0277] According to one embodiment, the STA can divide its transmission into smaller PPDUs, which can be sent at a certain inter - frame interval (jIFS). If the transmission does not end before the JTX transmission start time, the AP can send a frame after the completion of the nearest PPDU to stop the uplink transmission. An example can be as Figure 42 shown. As depicted, the AP sends a BA before the start of PPDU5 to end the uplink transmission before the JTX start time.

[0278] Figure 43 Illustrates an example early termination operation 4300 for stopping a downlink transmission according to various embodiments of the present disclosure.Figure 43 The embodiment of the exemplary early termination operation 4300 for stopping the downlink transmission shown in [Fig.] is for illustrative purposes only. Other embodiments of the exemplary early termination operation 4300 for stopping the downlink transmission may be used without departing from the scope of the present disclosure.

[0279] According to one embodiment, the AP may divide its transmission into smaller PPDUs and insert a PPDU end marker at the end of the PPDU closest to the start time of the JTX transmission. When receiving a PPDU with a PPDU end marker, the STA sends a BA to end the transmission early. An example is shown Figure 43 as

[0280] Figure 44 Fig. shows another exemplary early termination operation 4400 for stopping the downlink transmission according to various embodiments of the present disclosure. Figure 44 The embodiment of the exemplary early termination operation 4400 for stopping the downlink transmission shown in [Fig.] is for illustrative purposes only. Other embodiments of the exemplary early termination operation 4400 for stopping the downlink transmission may be used without departing from the scope of the present disclosure.

[0281] In another embodiment, instead of inserting a PPDU end marker as shown in the example in Figure 44 [Fig.], the AP may send another frame (e.g., a control frame) to indicate the early completion of the downlink transmission.

[0282] According to one embodiment, when competing for JTX, if different APs obtain channel access for different ACs, one AC may be selected among all the APs to perform JTX. The AC may be selected based on criteria such as the AC having high-priority frames in its queue (e.g., frames that can first exceed their delay bounds), the AC of frames with the most stringent QoS requirements, etc.

[0283] According to one embodiment, when an AP wins channel access, it may notify other APs, and they may stop their ongoing uplink or downlink transmissions and join the JTX transmission.

[0284] According to one embodiment, when competing for channel access to perform JTX, one of the APs in the AP can perform the contention and backoff processes on behalf of the other APs. When the AP completes its backoff process, if the channel is idle for all APs, JTX can be initiated. If the channel is not idle for at least one or more APs, all APs can postpone for a period of time equal to the maximum of the channel busy times among all APs. According to one embodiment, the backoff timer can be maintained at the central controller, and each of the individual APs can report their channel status to the central controller. When the channel is idle for all APs, the central controller can issue a trigger to the APs to initiate JTX. This can be useful in the case of implementing a logical AP MLD architecture with a part of the protocol stack operating at the central controller.

[0285] According to one embodiment, an AP / AP MLD or STA / non-AP MLD that supports JTX or any process for JTX described in this disclosure can advertise its support for the feature and / or process in one or more frames it transmits. If an AP / AP MLD supports JTX or any process for JTX, it can advertise its capabilities in one or more frames it transmits. In one example, these frames can be management frames such as beacons, probe responses, (re)association responses, etc. There can be fields (e.g., bits) that can take a predetermined value (e.g., 1) to indicate support and can take another predetermined value (e.g., 0) to indicate lack of support. If a STA / non-AP MLD supports JTX or any process for JTX, it can advertise its capabilities in one or more frames it transmits. In one example, these frames can be management frames such as probe requests, (re)association requests, etc. There can be fields (e.g., bits) that can take a predetermined value (e.g., 1) to indicate support and can take another predetermined value (e.g., 0) to indicate lack of support.

[0286] Those skilled in the art will understand that the above processes can also be used for any applicable non-JTX related purposes and should not be considered limited to JTX. Additionally, when applicable, the above processes can also be used in architectures such as the logical AP MLD architecture. Further, the information items indicated in this disclosure can be carried in any frame in the standard. Even further, the embodiments in this disclosure do not apply solely to logical AP MLD and generally can apply to any establishment involving joint transmission.

[0287] Figure 45 A flowchart of a method 4500 for wireless communication performed by a first AP device according to an embodiment of the present disclosure is shown. Figure 45The example method 4500 shown is for illustration only. Other embodiments of the example method 4500 may be used without departing from the scope of the present disclosure.

[0288] As Figure 45 shown, the method 4500 begins at step 4502, where a first AP device determines that the first AP and other APs among a plurality of APs want to perform joint transmission (JTX) with a station (STA) associated with the first AP and the other APs. At step 4504, the first AP device initiates a JTX process that includes forming a logical AP multi-link device (MLD) or a virtual AP MLD with the other APs to perform JTX.

[0289] In one embodiment, the AP device divides the logical AP MLD into (i) a shared component group configured to perform functions common to the APs forming the logical AP MLD, and (ii) a non-shared component group configured to perform functions specific to each AP forming the logical AP MLD; or divides the virtual AP MLD into (i) a shared component group configured to perform functions common to the APs forming the virtual AP MLD, and (ii) a non-shared component group configured to perform functions specific to each AP forming the virtual AP MLD.

[0290] In one embodiment, the AP device determines to initiate a channel sounding process for JTX; and sends a trigger frame to the non-shared component group to initiate the channel sounding process.

[0291] In one embodiment, the AP device determines to collect channel sounding feedback from STAs associated with the first AP and the other APs; sends a second trigger frame to one or more of the other APs that will collect the channel sounding feedback; and receives information associated with the channel sounding feedback from one or more of the other APs.

[0292] In one embodiment, the AP device sends a message associated with the operating parameters of the other APs to the other APs.

[0293] In one embodiment, the operating parameters of the first AP and the other APs are the same, and the operating parameters include frequency resources, which include one or more of a frequency band, a channel, and a bandwidth.

[0294] In one embodiment, the AP device sends a message to a plurality of APs, the message associated with: forming an AP group from the plurality of APs to form a logical AP MLD or a virtual AP MLD and that can participate in JTX.

[0295] In one embodiment, the AP device receives a message requesting to join a group from one or more of the multiple APs; and sends a response approving or rejecting the request to join the group to one or more of the multiple APs.

[0296] In one embodiment, the AP device shares data of STAs associated with the first AP and other APs with other APs; and after sharing the data of the STAs, sends a message to other APs to start JTX.

[0297] In one embodiment, the AP device receives a management frame from an AP among the multiple APs, and the management frame indicates the ability of the AP among the multiple APs to form a logical AP MLD or a virtual AP MLD for JTX.

[0298] The above flowcharts illustrate example methods that can be implemented in accordance with the principles of the present disclosure, and various changes can be made to the methods shown in the flowcharts. For example, although shown as a series of steps, the various steps can overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps can be omitted or replaced by other steps.

[0299] Although the present disclosure has been described with example embodiments, various changes and modifications can be suggested to those skilled in the art. The present disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims. None of the descriptions in this application should be construed as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A method for wireless communication performed by a first access point (AP), the method comprising: Identifying that the first AP and the second AP among a plurality of APs want to perform joint transmission (JTX) with stations (STAs) associated with the first AP and the second AP; And Initiating a JTX process, the JTX process including forming a logical AP multi-link device (MLD) or a virtual AP MLD with the second AP to perform JTX.

2. The method according to claim 1, wherein, Initiating the JTX process includes: Dividing the logical AP MLD into a shared component group and a non-shared component group, the shared component group being configured to perform functions common to the APs forming the logical AP MLD, and the non-shared component group being configured to perform functions specific to each AP forming the logical AP MLD; or Dividing the virtual AP MLD into a shared component group and a non-shared component group, the shared component group being configured to perform functions common to the APs forming the virtual AP MLD, and the non-shared component group being configured to perform functions specific to each AP forming the virtual AP MLD.

3. The method according to claim 2, further comprising: Determining to initiate a channel sounding process for JTX; And Sending a trigger frame to the non-shared component group to initiate the channel sounding process.

4. The method according to claim 3, further comprising: Determining to collect channel sounding feedback from STAs associated with the first AP and the second AP; Sending a second trigger frame to one or more second APs among the second APs that will collect the channel sounding feedback; And Receiving information associated with the channel sounding feedback from the one or more APs among the second APs.

5. The method according to claim 1, wherein, Initiating the JTX process further includes sending a message associated with the operating parameters of the second AP to the second AP.

6. The method according to claim 5, wherein The operating parameters of the first AP and the second AP are the same, and the operating parameters include frequency resources, and the frequency resources include one or more of a frequency band, a channel, and a bandwidth.

7. The method according to claim 1, further comprising sending a message to the plurality of APs, the message being associated with: forming an AP group from the plurality of APs to form the logical AP MLD or the virtual AP MLD and being able to participate in JTX.

8. The method according to claim 7, further comprising: Receiving a message from one or more APs among the plurality of APs requesting to join the group; And Sending a response approving or rejecting the request to join the group to the one or more APs among the plurality of APs.

9. The method according to claim 1, further comprising: Sharing data of the STAs associated with the first AP and the second AP with the second AP; And After sharing the data of the STAs, sending a message to the second AP to start JTX.

10. The method according to claim 1 further comprises: Receiving a management frame from an AP among the plurality of APs, the management frame indicating the ability of the AP among the plurality of APs to form a logical AP MLD or a virtual AP MLD for JTX.

11. A first access point (AP) device, comprising: A transceiver configured to communicate with a corresponding station (STA) via a link; And A processor operably coupled to the transceiver, the processor being configured to: Identify that the first AP and the second AP among multiple APs want to perform joint transmission (JTX) with stations (STAs) associated with the first AP and the second AP; And Initiate a JTX process, the JTX process including forming a logical AP multi-link device (MLD) or a virtual AP MLD with the second AP to perform JTX.

12. The first AP device according to claim 11, wherein, To initiate the JTX process, the processor is configured to: Divide the logical AP MLD into a shared component group and a non-shared component group, the shared component group being configured to perform functions common to the APs forming the logical AP MLD, and the non-shared component group being configured to perform functions specific to each AP forming the logical AP MLD; or Divide the virtual AP MLD into a shared component group and a non-shared component group, the shared component group being configured to perform functions common to the APs forming the virtual AP MLD, and the non-shared component group being configured to perform functions specific to each AP forming the virtual AP MLD.

13. The first AP device according to claim 12, wherein, The processor is configured to: Determine to initiate a channel sounding process for JTX; And Control the transceiver to send a trigger frame to the non-shared component group to initiate the channel sounding process.

14. The first AP device according to claim 13, wherein, The processor is configured to: Determine to collect channel sounding feedback from STAs associated with the first AP and other APs; And Control the transceiver to: Send a second trigger frame to one or more second APs in the second AP that will collect the channel sounding feedback; And Receive information associated with the channel sounding feedback from the one or more second APs in the second AP.

15. The first AP device according to claim 11, wherein, The processor is configured to execute one of the methods described in claims 5 to 10.

Images