[go: up one dir, main page]

WO2025144837A1 - Protection d'opportunité de transmission (txop) pour un accès multiple par répartition dans le temps coordonné (ctdma) - Google Patents

Protection d'opportunité de transmission (txop) pour un accès multiple par répartition dans le temps coordonné (ctdma) Download PDF

Info

Publication number
WO2025144837A1
WO2025144837A1 PCT/US2024/061830 US2024061830W WO2025144837A1 WO 2025144837 A1 WO2025144837 A1 WO 2025144837A1 US 2024061830 W US2024061830 W US 2024061830W WO 2025144837 A1 WO2025144837 A1 WO 2025144837A1
Authority
WO
WIPO (PCT)
Prior art keywords
frame
sta
duration
transmitting
receiving
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2024/061830
Other languages
English (en)
Inventor
Leonardo Alisasis LANANTE
Jeongki Kim
Esmael Hejazi Dinan
Serhat Erkucuk
Jiayi Zhang
Tuncer Baykas
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ofinno LLC
Original Assignee
Ofinno LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ofinno LLC filed Critical Ofinno LLC
Publication of WO2025144837A1 publication Critical patent/WO2025144837A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/04—Scheduled access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]

Definitions

  • TXOP Transmission Opportunity
  • CTDMA Coordinated Time Division Multiple Access
  • FIG. 1 illustrates example wireless communication networks in which embodiments of the present disclosure may be implemented.
  • FIG. 2 is a block diagram illustrating example implementations of a station (STA) and an access point (AP).
  • STA station
  • AP access point
  • FIG. 3 illustrates an example multi-AP network.
  • FIG. 4 illustrates Enhanced Distributed Channel Access (EDCA) and Coordinated Orthogonal Frequency Division Multiple Access (COFDMA).
  • EDCA Enhanced Distributed Channel Access
  • COFDMA Coordinated Orthogonal Frequency Division Multiple Access
  • FIG. 5 illustrates an example network that includes a coordinated AP set.
  • FIG. 6 illustrates an example multi-AP operation procedure.
  • FIG. 7 illustrates an example multi-AP sounding phase.
  • FIG. 8 illustrates an example multi-AP downlink data transmission phase.
  • FIG. 9 illustrates an example multi-AP uplink data transmission phase.
  • FIG. 10 illustrates an example trigger frame.
  • FIG. 11 illustrates an example multi-user request to send (MU-RTS) trigger frame.
  • MU-RTS multi-user request to send
  • FIG. 20 illustrates an example of another CTDMA procedure according to an embodiment.
  • STA 1411 may respond to MRTT frame 1420 by transmitting a CTS frame 1421 to AP 1410. Subsequently, STA 1411 may transmit non-TB PPDUs 1422, 1424 comprising one or more data frame to STA 1412 during the first time period indicated in MRTT frame 1420. In an example, STA 1412 may transmit one or more BA frames 1423, 1425 in response to the one or more data frames contained in non-TB PPDUs 1422, 1424 received from STA 1411.
  • FIG. 15 illustrates an example 1500 of an existing CTDMA procedure.
  • example 1500 includes an AP 1502, an AP 1504, a STA 1506, and a STA 1508.
  • APs 1502 and 1504 may form a coordinated AP set or may form part of a multi-AP group.
  • AP 1502 may be the master or sharing AP and AP 1504 may be the slave or shared AP.
  • STA 1506 may be associated with AP 1502 and STA 1508 may be associated with AP 1504.
  • AP 1502 may set the duration field of RTS frame 1510 to protect one or more frames following RTS frame 1510.
  • AP 1502 sets the duration field of RTS frame 1510 such that NAV duration 1528 corresponds to the duration of the TXOP. As such, AP 1502 protects any frame transmission that occurs during the TXOP.
  • AP 1502 may decide to share a portion of the remainderof the TXOP with AP 1504. As such, as shown in FIG. 15, AP 1502 transmits a frame 1518 that allocates a duration 1530 of the TXOP toAP 1504.
  • Frame 1518 may be a multi-AP MRTT frame.
  • AP 1504 may be configured to transmit a frame 1520 accepting allocated duration 1530.
  • Frame 1520 may be a clear to send (CTS) frame.
  • CTS clear to send
  • AP 1504 may use allocated duration 1530 to transmit downlink data and/or receive uplink data to/from one or more associated STAs.
  • AP 1504 uses allocated duration 1530 to send a trigger frame 1522 to STA 1508.
  • Trigger frame 1522 allocates uplink resource units (RUs) to STA 1508.
  • STA 1508 transmits a trigger-based (TB) PPDU 1524 using the allocated uplink RUs to AP 1504.
  • AP 1504 may acknowledge TB PPDU 1524 by transmitting a BA frame 1526 to STA 1508.
  • example 1600 includes an AP 1602, an AP 1604, a STA 1606, and a STA 1608.
  • APs 1602 and 1604 may form a coordinated AP set or may form part of a multi-AP group.
  • AP 1602 may be the master or sharing AP and AP 1604 may be the slave or shared AP.
  • STA 1606 may be associated with AP 1602 and STA 1608 may be associated with AP 1604.
  • example 1600 may also begin with AP 1602 gaining access to the shared channel and transmitting an RTS frame 1610 to STA 1606.
  • RTS frame 1610 may be similar to RTS frame 1510 described above. However, unlike RTS frame 1510, in which the duration field (e.g., Duration/ID field) is set to the duration of the TXOP, in RTS frame 1610, the duration field is set to a NAV duration 1628 that is only a portion of the duration of the TXOP.
  • AP 1602 may select NAV duration 1628 to correspond to an estimated time required for the transmission of one or more frames after RTS frame 1610.
  • AP 1602 sets NAV duration 1628 to correspond to the estimated time required for the transmission of a CTS frame 1612 by STA 1606 to AP 1602, a data frame 1614 by AP 1602 to STA 1606, and a BA frame 1616 by STA 1606 to AP 1602, followed by a frame 1618 by AP 1602 to AP 1604, a frame 1620 by AP 1604 to AP 1602, and a trigger frame 1622 by AP 1604 to STA 1608.
  • the estimated time may include any interframe space between successive frames.
  • STA 1608 sets its basic NAV according to NAV duration 1628. STA 1608 may refrain from transmitting on the shared channel as long as its basic NAV is non-zero, e.g., until the end of NAV duration 1628.
  • CTS frame 1612 may also include a duration field (e.g., Duration/ID field) that indicates a NAV duration (not shown in FIG. 16)
  • the NAV duration indicated in CTS frame 1612 may correspond to a remaining duration of NAV duration 1628 (e.g., NAV duration 1628, minus the duration of a SIFS between RTS frame 1610 and CTS frame 1612, minus the transmission duration of CTS frame 1612).
  • AP 1602 initiates transmission of data frame 1614 to STA 1606.
  • STA 1606 acknowledges reception of data frame 1614 by transmitting BA frame 1616 to AP 1602.
  • AP 1602 transmits frame 1618 to allocate a duration 1630 of the TXOP to AP 1604.
  • Frame 1618 may be a multi-AP MRTT frame.
  • AP 1604 may be configured to transmit frame 1620 accepting allocated duration 1630.
  • Frame 1620 may be a CTS frame.
  • frame 1620 may include a duration field that indicates a NAV duration (not shown in FIG. 16).
  • STA 1608 may set an intra-BSS NAV based on the NAV duration indicated in frame 1620.
  • STA 1608 may set the intra-BSS NAV based on frame 1620 having a receiver address (RA), a transmitter address (TA), or a basic service set identifier (BSSID) field value that is equal to the BSSID of the BSS or the BSSID of any BSS with which STA 1608 is associated (e.g. AP 1604).
  • RA receiver address
  • TA transmitter address
  • BSSID basic service set identifier
  • STA 1608 may not transmit on the shared channel unless triggered by AP 1604.
  • Other STAs not belonging to the BSS of AP 1604 e.g., AP 1602 or STA 1606) may settheirbasic NAVs based on the NAV duration indicated in frame 1620.
  • frame 1620 may provide an incremental TXOP protection that extends the initial TXOP protection provided by RTS frame 1610.
  • AP 1604 may use allocated duration 1630 to transmit downlink data and/or receive uplink data to/from one or more associated STAs. For instance, in example 1600, AP 1604 uses allocated duration 1630 to send trigger frame 1622 to STA 1608. As NAV duration 1628 does notextend beyond trigger frame 1622, STA 1608 may have a basic NAV equal to zero when it receives trigger frame 1622. As such, STA 1608 may be able to respond to trigger frame 1622 by transmitting a TB PPDU 1624 to AP 1604. AP 1604 may acknowledge TB PPDU 1624 by transmitting a BA frame 1626 to STA 1608.
  • AP 1602 may regain control of the TXOP as its basic NAV (set due to frame 1620) will be zero allowing it to access the shared channel. For example, as shown in FIG. 16, AP 1602 may regain control of the TXOP by transmitting a data frame 1632 to STA 1606.
  • a STA 1702 which may be associated with AP 1602, maybe outside of the communication of range of AP 1604 and STA 1608. STA 1702 may thus not hear frame 1620 and may not set its basic NAV based on the NAV duration indicated in frame 1620. STA 1702 may thus access the shared channel to transmit a data frame 1704 to AP 1602, for example, during allocated duration 1630. Data frame 1704 may interfere with the transmission of TB PPDU 1624 and/or BA frame 1626. More importantly, if the transmission of data frame 1704 extends beyond allocated duration 1630, AP 1602 may not be able to regain control of the TXOP at the end of allocated duration 1630.
  • AP 1802 may obtain a TXOP and may wish to allocate a duration 1826 of the TXOP to AP 1804. Rather than using a multi-AP MRTT frame to allocate duration 1826 to AP 1804, AP 1802 transmits a coordinated announcement (CoA) frame 1812 to AP 1804. In addition to indicating allocated duration 1826, CoA frame 1812 instructs AP 1804 to respond to CoA frame 1812 by transmitting a specific control frame (e.g., MU-RTS frame) as the first frame of allocated duration 1826, in order to accept allocated duration 1826.
  • a specific control frame e.g., MU-RTS frame
  • AP 1804 On receiving CoA frame 1812 and wishing to accept allocated duration 1826, AP 1804 transmits an MU-RTS frame 1814 to AP 1802.
  • MU-RTS frame 1814 may indicate a NAV duration corresponding to the remaining duration of allocated duration 1826.
  • STA 1806, associated with AP 1802, may hear MU-RTS frame 1814 and may set its basic NAV based on the NAV duration indicated in MU-RTS frame 1814.
  • CTS frame 1816 On receiving MU-RTS frame 1814, AP 1802 transmits a CTS frame 1816.
  • CTS frame 1816 may indicate a NAV duration corresponding to the remaining duration of allocated duration 1826.
  • CTS frame 1816 may have a receiver address (RA) field set to the address of AP 1804, allowing AP 1804 to ignore the NAV duration indicated in CTS frame 1816.
  • RA receiver address
  • CTS frame 1816 may cause STA 1810 to set its intra-BSS NAV for the remaining during of allocated duration 1826.
  • STA 1810 may be outside the communication range of AP 1804 and STA 1808, STA 1810 may not access the shared channel during allocated duration 1826 and may not interfere with the communication between AP 1804 and STA 1808.
  • AP 1804 may transmit a trigger frame 1818 to STA 1808 allocating uplink RUs to STA 1808.
  • STA 1808 may respond to trigger frame 1818 by transmitting a TB PPDU 1820 to AP 1804.
  • AP 1804 may acknowledge TB PPDU 1820 by transmitting a BA frame 1822 to STA 1808.
  • AP 1802 may regain control of the TXOP without being impeded by STA 1810 which remains silent during allocated duration 1826. For example, as shown in FIG. 18, AP 1802 may regain control of the TXOP by transmitting a data frame 1824 to STA 1806.
  • a disadvantage of Chen’s procedure is that it requires a new TXOP sharing procedure.
  • This new TXOP sharing procedure requires the creation of a new control frame (CoA frame) for a sharing AP to allocate a duration of its TXOP to a shared AP. Further, the new control frame is designed to trigger a new behavior by the shared AP, which includes sending an MU-RTS frame to accept the allocated duration.
  • CoA frame a new control frame
  • Embodiments of the present disclosure address the above-described problems of existing CTDMA procedures.
  • embodiments provide TXS-based TXOP sharing solutions with incremental TXOP protection that solve the problem of a sharing AP losing control of its TXOP after an allocated duration.
  • TXS-based TXOP sharing the proposed solutions can be implemented with minimal modifications to existing IEEE 802.11 standard procedures and control frames. This has the advantage of improved backward and forward computability and of lower implementation complexity.
  • a first AP transmits to a second AP, during a TXOP obtained by the first AP, a first frame comprising: an allocation duration field indicating a first duration, within the TXOP, allocated to the second AP; and an indication of a transmission by the first AP of a second frame within the first duration.
  • the first AP receives from the second AP, and during the first duration, a third frame comprising a duration field indicating a second duration overlapping the first duration.
  • the second duration may be a NAV duration to protect communication by the second AP after the third frame.
  • the first AP transmits the second frame during the second duration.
  • the second frame may include a duration field indicating a third duration overlapping the first duration.
  • the third duration may be a NAV duration and may extend to an end of the first/second duration. This may cause one or more STAs to remain silent during the first/second duration, ensuring protection of the communication by the second AP during the second duration and return of TXOP control to the first AP after the first duration.
  • FIG. 19 illustrates an example 1900 of a CTDMA procedure according to an embodiment.
  • example 1900 includes an AP 1902, an AP 1904, a STA 1906, a STA 1908, and a STA 1932.
  • APs 1902 and 1904 may form a coordinated AP set or may form part of a multi-AP group.
  • AP 1902 may be the master or sharing AP and AP 1904 maybe the slave or shared AP.
  • STAs 1906 and 1932 maybe associated with AP 1902 and STA 1908 may be associated with AP 1904.
  • example 1900 may begin with AP 1902 gaining access to the shared channel and transmitting an RTS frame 1910 to STA 1906.
  • RTS frame 1910 may be similar to RTS frame 1510 described above. However, unlike RTS frame 1510, in which the duration field (e.g., Duration/ID field) is set to the duration of the TXOP, in RTS frame 1910, the duration field is set to a NAV duration 1928 that is only a portion of the duration of the TXOP.
  • AP 1902 may select NAV duration 1928 to correspond to an estimated time required for the transmission of one or more frames after RTS frame 1910.
  • AP 1902 sets NAV duration 1928 to correspond to the estimated time required for the transmission of a CTS frame 1912 by STA 1906 to AP 1902, a data frame 1914 by AP 1902 to STA 1906, and a BA frame 1916 by STA 1906 to AP 1902, followed by an MU-RTS (or an MRTT) frame 1918 by AP 1902 to AP 1904, a CTS frame 1920 by AP 1904 to AP 1902, a CTS frame 1930 by AP 1902 to AP 1904, and a trigger frame 1922 by AP 1904 to STA 1908.
  • the estimated time may include any interframe space between successive frames. In other embodiments, however, AP 1902 may set NAV duration 1928 to be longer or shorter than in example 1900.
  • STA 1908 On receiving RTS frame 1910, STA 1908 sets its basic NAV according to NAV duration 1928. STA 1908 may refrain from transmitting on the shared channel as long as its basic NAV is non-zero, e.g., until the end of NAV duration 1928.
  • CTS frame 1912 may also include a duration field (e.g., Duration/ID field) that indicates a NAV duration (not shown in FIG. 19).
  • the NAV duration indicated in CTS frame 1912 may correspond to a remaining duration of NAV duration 1928 (e.g., NAV duration 1928, minus the duration of a SIFS between RTS frame 1910 and CTS frame 1912, minus the transmission duration of CTS frame 1912).
  • AP 1902 initiates transmission of data frame 1914 to STA 1906.
  • STA 1906 acknowledges reception of data frame 1914 by transmitting BA frame 1916 to AP 1902.
  • RTS frame 1910 and CTAframe 1912 maybe replaced by an initial control frame (ICF) and an initial control response (ICR) frame respectively.
  • the ICF may be a control frame transmitted by an AP (e.g., AP 1902) at the beginning of a TXOP of the AP to announce its intention to share a portion of the TXOP.
  • AP 1902 transmits MU-RTS (or MRTT) frame 1918 to allocate a duration 1934 of the TXOP to AP 1904.
  • a transmitter address (TA) and a receiver address (RA) of MU-RTS (or MRTT) frame 1918 are set to AP 1902 and AP 1904, respectively.
  • MU-RTS (or MRTT) frame 1918 includes an allocation duration field indicating allocated duration 1934.
  • MU-RTS (or MRTT) frame 1918 triggers transmission of CTS frame 1920 by AP 1904, e.g., a SIFS after reception of MU-RTS (or MRTT) frame 1918 by AP 1904.
  • MU-RTS (or MRTT) frame 1918 further includes an indication of a transmission, by AP 1902, of a frame within allocated duration 1934.
  • the frame to be transmitted by AP 1902 within allocated duration 1934 may be CTS frame 1930, transmitted after (e.g., a SIPS after) CTS frame 1920.
  • the indication of the transmission of the frame by AP 1902 may thus indicate to AP 1904 that AP 1902 will transmit CTS frame 1930 after AP 1904 transmits CTS frame 1920. This configures AP 1904 to wait for the transmission of CTS frame 1930 by AP 1902, before proceeding to use allocated duration 1934 for communication with its associated STAs.
  • the indication may be provided in a common info field or in a user info field of MU-RTS (or MRTT) frame 1918.
  • MU-RTS (or MRTT) frame 1918 may include a duration field (e.g., Duration/ID field) that indicates a NAV duration (not shown in FIG. 19).
  • the NAV duration indicated in MU-RTS (or MRTT) frame 1918 may correspond to a duration that overlaps allocated duration 1934 (e.g., allocated duration 1934, minus the transmission duration of MU-RTS (or MRTT) frame 1918).
  • AP 1902 may choose to set the NAV duration to overlap allocated duration 1934 based on its knowledge that AP 1904 intends to use allocated duration 1934.
  • AP 1902 may have knowledge that AP 1904 intends to transmit CTS frame 1920, e.g., a SIFS after MU-RTS (or MRTT) frame 1918.
  • a frame exchange between AP 1902 and AP 1904 may take place before AP 1902 transmits MU-RTS frame 1918.
  • the frame exchange may include a buffer status report poll (BSRP) frame from AP 1902 to AP 1904 and a buffer status report (BSR) frame from AP 1904 to AP 1902.
  • BSRP buffer status report poll
  • BSR buffer status report
  • STA 1908 may setan intra-BSS NAV based on the NAV duration indicated in CTS frame 1920.
  • STA 1908 may set the intra-BSS NAV based on CTS frame 1920 having an RA value that is equal to the BSSID of the BSS or the BSSID of any BSS with which the STA 1908 is associated (e.g. AP 1904). With its intra-BSS NAV set to a non-zero value, STA 1908 may not transmit on the shared channel unless triggered by AP 1904.
  • STAs not belonging to the BSSof AP 1904 may set their basic NAVs based on the NAV duration indicated in CTS frame 1920.
  • CTS frame 1920 may provide an incremental TXOP protection that extends the initial TXOP protection provided by RTS frame 1910.
  • AP 1902 may be configured not to set its basic NAV based on CTS frame 1920. Further, AP 1902 may be configured to transmit CTS frame 1930 in response to CTS frame 1920 (e.g., a SIFS after reception of CTS frame 1920). AP 1904 may not transmit while AP 1902 transmits CTS frame 1930 based on the indication of the transmission by AP 1902 of CTS frame 1930 comprised in MU-RTS (or MRTT) frame 1918.
  • CTS frame 1930 comprises a duration field indicating a duration that overlaps with allocated duration 1934. In an implementation, the duration corresponds to allocated duration 1934. In an implementation, the duration may be a NAV duration corresponding to the remaining duration of allocated duration 1934. In an implementation, the duration may be a NAV duration corresponding to the NAV duration indicated in CTS frame 1920 by AP 1904
  • CTS frame 1930 may comprise an address of AP 1904 and/or a basic service set identifier (BSSID) of a BSS of AP 1904.
  • the address of AP 1904 maybe provided in a receiver address (RA) or a transmitter address (TA) of CTS frame 1930.
  • the BSSID of the BSS of AP 1904 may be provided in a BSSID field of CTS frame 1930.
  • a STA receiving a PPDU carrying CTS frame 1930 may classify the received PPDU as originating from the BSS of AP 1904.
  • STA 1908 may only update its intra-BSS NAV based on CTS frame 1930 and may not set its basic NAV.
  • STA 1932 associated with AP 1902, may set its basic NAV, instead of its intra-BSS NAV, for the remaining of allocated duration 1934 based on CTS frame 1930.
  • STA 1932 may be outside the communication range of AP 1904 and STA 1908, STA 1932 may not access the shared channel during allocated duration 1934 and may not interfere with the communication between AP 1904 and STA 1908.
  • AP 1904 may use allocated duration 1934 to transmit downlink data and/or receive uplink data to/from one or more associated STAs. For instance, in example 1900, AP 1904 uses allocated duration 1934 to send trigger frame 1922 to STA 1908. As NAV duration 1928 does notextend beyond trigger frame 1922, STA 1908 may have a basic NAV equal to zero when it receives trigger frame 1922. As such, STA 1908 may be able to respond to trigger frame 1922 by transmitting a TB PPDU 1924 to AP 1904. AP 1904 may acknowledge TB PPDU 1924 by transmitting a BA frame 1926 to STA 1908.
  • AP 1902 may regain control of the TXOP without being impeded by STA 1932 which remains silent during allocated duration 1934. For example, as shown in FIG. 19, AP 1902 may regain control of the TXOP by transmitting a data frame 1936 to STA 1906.
  • the fourth frame comprises a trigger frame triggering a transmission from a third STA.
  • the fourth frame may be transmitted by the first STA to trigger a transmission from the third STA to the first STA.
  • receiving the second frame in step 2304 comprises receiving the second frame a SIFS after receiving the first frame.
  • receiving the second frame in step 2304 further comprises receiving the second frame based on transmitting a fifth frame to the second STA.
  • the fifth frame comprises a BSR frame.
  • the BSR frame comprises a BSR of the first STA.
  • process 2300 may further comprise receiving, by the first STA from the second STA, a sixth frame and transmitting the fifth frame in response to the sixth frame.
  • the sixth frame comprises a BSRP frame.
  • the second frame comprises a second duration field indicating a third duration overlapping the first duration.
  • the second duration field indicates the first duration.
  • the second frame comprises an address of the first STA or a BSSID of a BSS of the first STA.
  • the second frame comprises an RA field, a TA field, or a BSSID field.
  • the RA, TA, or the BSSID field comprises the address of the first STA or the BSSID of the BSS of the first STA.
  • a first STA transmits to a second STA a first frame during a TXOP obtained by the first STA.
  • the first STA may be a master AP or a sharing AP.
  • the second STA may be a slave AP or a shared AP.
  • the first and second STA may be members of a coordinated AP set or a multi-AP group.
  • the first frame may comprise an allocation duration field indicating a first duration, within the TXOP, allocated to the second STA. Additionally the first frame may comprise an indication of a TXOP sharing mode for the second STA.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Une première station (STA) transmet à une seconde STA une première trame pendant une opportunité de transmission (TXOP) obtenue par la première STA, la première trame comprenant : un champ de durée d'attribution indiquant une première durée, à l'intérieur de la TXOP, attribuée à la seconde STA ; et une indication d'une transmission par la première STA d'une seconde trame dans la première durée. La première STA transmet pendant la première durée la seconde trame.
PCT/US2024/061830 2023-12-26 2024-12-24 Protection d'opportunité de transmission (txop) pour un accès multiple par répartition dans le temps coordonné (ctdma) Pending WO2025144837A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202363614715P 2023-12-26 2023-12-26
US63/614,715 2023-12-26
US202463622642P 2024-01-19 2024-01-19
US63/622,642 2024-01-19

Publications (1)

Publication Number Publication Date
WO2025144837A1 true WO2025144837A1 (fr) 2025-07-03

Family

ID=94283656

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/061830 Pending WO2025144837A1 (fr) 2023-12-26 2024-12-24 Protection d'opportunité de transmission (txop) pour un accès multiple par répartition dans le temps coordonné (ctdma)

Country Status (1)

Country Link
WO (1) WO2025144837A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210120548A1 (en) * 2020-03-04 2021-04-22 Cheng Chen Multi-ap resource sharing
EP3820225A1 (fr) * 2019-11-11 2021-05-12 INTEL Corporation Coordination de points d'accès multiples des horaires de temps de réveil cible
WO2022173251A1 (fr) * 2021-02-10 2022-08-18 주식회사 윌러스표준기술연구소 Procédé de communication sans fil utilisant de multiples liaisons et terminal de communication sans fil utilisant le procédé

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3820225A1 (fr) * 2019-11-11 2021-05-12 INTEL Corporation Coordination de points d'accès multiples des horaires de temps de réveil cible
US20210120548A1 (en) * 2020-03-04 2021-04-22 Cheng Chen Multi-ap resource sharing
WO2022173251A1 (fr) * 2021-02-10 2022-08-18 주식회사 윌러스표준기술연구소 Procédé de communication sans fil utilisant de multiples liaisons et terminal de communication sans fil utilisant le procédé
US20240049304A1 (en) * 2021-02-10 2024-02-08 Wilus Institute Of Standards And Technology Inc. Wireless communication method using multi-link, and wireless communication terminal using same

Similar Documents

Publication Publication Date Title
US20240260017A1 (en) Multi-access point primary channel switching
US20240349345A1 (en) Triggered TXOP Sharing (TXS) Power Save
EP4422288A1 (fr) Transmission de châssis de déclenchement articulé
TW202504373A (zh) 緩衝區報告發送、接收方法及裝置
US20240340700A1 (en) Multi-Access Point Offloading Based on Traffic Category
WO2025144837A1 (fr) Protection d'opportunité de transmission (txop) pour un accès multiple par répartition dans le temps coordonné (ctdma)
WO2010110619A2 (fr) Procédé et appareil de planification de ressources de support sans fil
WO2024259272A1 (fr) Coordination de points d'accès multiples assistée par station
US20250267708A1 (en) Multi-ap transmission scheme selection
US20250105893A1 (en) Multi-Access Point Coordinated Beamforming
US20250324455A1 (en) Period for multi-access point communication
US20250193926A1 (en) Coordinated Spatial Reuse
WO2025207506A1 (fr) Annulation de transition de station
WO2025245221A1 (fr) Sélection de liaison pendant une procédure d'itinérance
US20250365770A1 (en) Channel switching method
WO2025034443A1 (fr) Commande de configuration d'unité de ressources pour réutilisation spatiale coordonnée
WO2025111332A1 (fr) Coordination de préemption pour communication à points d'accès multiples
WO2025245324A1 (fr) Retour d'opportunité de transmission (txop)
WO2024206625A1 (fr) Partage d'unités de ressources distribuées
US20250317912A1 (en) Cross-link request to send (rts)-clear to send (cts)
WO2025111322A1 (fr) Formation de faisceau coordonnée à points d'accès multiples
WO2025104180A1 (fr) Procédure de troncature d'accès multiple par répartition dans le temps coordonnée (ctdma)
WO2025024618A1 (fr) Commande de formation de faisceau pour réutilisation spatiale coordonnée
WO2025199296A1 (fr) Notification entre points d'accès
WO2024259069A1 (fr) Coordination de multiples points d'accès pour transfert de station

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24837817

Country of ref document: EP

Kind code of ref document: A1