EP4662960A1 - Mécanismes de transmission de liaison montante à latence réduite - Google Patents

Mécanismes de transmission de liaison montante à latence réduite

Info

Publication number
EP4662960A1
EP4662960A1 EP24752893.8A EP24752893A EP4662960A1 EP 4662960 A1 EP4662960 A1 EP 4662960A1 EP 24752893 A EP24752893 A EP 24752893A EP 4662960 A1 EP4662960 A1 EP 4662960A1
Authority
EP
European Patent Office
Prior art keywords
data
ulll
stas
ppdu
transmit
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
EP24752893.8A
Other languages
German (de)
English (en)
Inventor
Kai Ying LU
Jianhan Liu
James Chih-Shi Yee
Shuling Feng
Yongho Seok
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.)
Mediatek Inc
MediaTek Inc
Original Assignee
Mediatek Inc
MediaTek Inc
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 Mediatek Inc, MediaTek Inc filed Critical Mediatek Inc
Publication of EP4662960A1 publication Critical patent/EP4662960A1/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/04—Scheduled access
    • H04W74/06—Scheduled access using polling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • the present disclosure is generally related to wireless communications and, more particularly, to data transmission between Wi-Fi stations (STAs) and access points (APs) .
  • STAs Wi-Fi stations
  • APs access points
  • deterministic ultra-low latency data transmissions may be critical for some consumer and autonomous applications.
  • such applications may include augmented reality (AR) /virtual reality (VR) /extended reality (XR) , remote work, factory automation, process automation, robotics, audio/video streaming, etc.
  • AR augmented reality
  • VR virtual reality
  • XR extended reality
  • Current technical trends also show that there is an ever-increasing demand for event-based low latency data delivery, such as for content rendering corresponding to the user’s input/motion (e.g., VR, gaming, etc. ) , event-based vision sensors with varying data rates depending on the perceived scene, or parsing time-critical events such as limit switch, emergency stop, etc.
  • Low latency traffic is generally event-driven and non-static in such applications.
  • STAs stations
  • Such mechanisms may enable an access point (AP) to serve known scheduling requirements for UL transmissions from applications on the STAs.
  • AP access point
  • an AP can use such tools to trigger uplink transmissions when serving applications have known characteristics.
  • event-based applications may have unknown characteristics and their UL data traffic is unpredictable.
  • DL downlink
  • a STA may be unable to send low latency uplink traffic by preempting the medium using a contention-based channel access mechanism.
  • An objective of the present disclosure is to provide schemes, concepts, designs, techniques, methods, and apparatuses pertaining to using soliciting frames to reduce UL transmission latency for communications between Wi-Fi STAs.
  • an apparatus may include a transceiver configured to communicate wirelessly and a processor coupled to the transceiver.
  • the processor may send a soliciting information in a downlink (DL) physical protocol data unit (PPDU) during a transmission opportunity (TXOP) , indicating to allow one or more stations (STAs) associated with the apparatus to send uplink low latency (ULLL) data or one or more requests to transmit ULLL data to the apparatus.
  • the processor may further receive the ULLL data or at least one request to transmit ULLL data from at least one STA of the one or more STAs in response to the soliciting information.
  • the apparatus may be the TXOP holder or TXOP responder.
  • a method may include sending, from an AP, a soliciting information in a DL PPDU during a TXOP, indicating to allow one or more STAs associated with the apparatus to send ULLL data or one or more requests to transmit ULLL data to the AP.
  • the method may also include receiving the ULLL data or at least one request to transmit ULLL data from at least one STA of the one or more STAs in response to the soliciting information.
  • the AP may be the TXOP holder or TXOP responder.
  • a method may include sending, from an access point (AP) , a soliciting information in a DL PPDU during a TXOP, indicating to allow one or more STAs associated with the apparatus to send ULLL data or one or more requests to transmit ULLL data to the AP.
  • the method may also include in response to receiving, at the AP, a subsequent UL transmission that includes at least one request to transmit ULLL data from at least one STA of the one or more STAs following an end of a time period that starts after the sending of the DL PPDU, sending a trigger frame from the AP to solicit additional ULLL data or request to transmit ULLL data from the one or more STAs during the TXOP.
  • the AP may be the TXOP holder or TXOP responder.
  • radio access technologies such as Wi-Fi
  • the proposed concepts, schemes and any variation (s) /derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, Bluetooth, ZigBee, 5th Generation (5G) /New Radio (NR) , Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro, Internet-of-Things (IoT) , Industrial IoT (IIoT) and narrowband IoT (NB-IoT) .
  • Bluetooth ZigBee
  • 5G 5th Generation
  • NR New Radio
  • LTE Long-Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-Advanced Pro Internet-of-Things
  • IoT Industrial IoT
  • NB-IoT narrowband IoT
  • FIG. 1 is a diagram of an example network environment in which various solutions and schemes in accordance with the present disclosure may be implemented.
  • FIG. 2 illustrates the use of a soliciting frame by an AP to reduce UL transmission latency for communications between Wi-Fi STAs and APs.
  • FIG. 3 illustrates that an AP may allocate some resources for ULLL traffic while performing downlink data, control frame, and/or management frame transmission during the DL TXOP in order to reduce the latency of uplink low latency traffic.
  • FIG. 4 illustrates a first implementation of the proposed scheme for using soliciting frames to reduce UL transmission latency for communications between Wi-Fi STAs and APs.
  • FIG. 5 illustrates a second implementation of the proposed scheme for using solicitation frames to reduce UL transmission latency for communications between Wi-Fi STAs and APs.
  • FIG. 6a and 6b illustrate a third implementation of the proposed scheme for using solicitation frames to reduce UL transmission latency for communications between Wi-Fi STAs and APs.
  • FIG. 7a and 7b illustrate a fourth implementation of the proposed scheme for using solicitation frames to reduce UL transmission latency for communications between Wi-Fi STAs and APs.
  • FIG. 8a and 8b illustrate a fifth implementation of the proposed scheme for using solicitation frames to reduce UL transmission latency for communications between Wi-Fi STAs and APs.
  • FIG. 9 is a block diagram of an example communication system in accordance with various implementations of the present disclosure.
  • FIG. 10 is a flowchart of a first example process in accordance with various implementations of the present disclosure.
  • FIG. 11 is a flowchart of a second example process in accordance with various implementations of the present disclosure.
  • Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions that reduce UL transmission latency for communications between Wi-Fi STAs and APs.
  • a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.
  • the various solutions and schemes implement the use of soliciting frames to reduce uplink (UL) transmission latency for communications between Wi-Fi STAs and APs.
  • the various solutions and schemes proposed herein may address or otherwise alleviate issues of STAs failing to meet data delivery quality of service (QoS) requirements for uplink low latency (ULLL) data due to such data being event-driven and non-static.
  • QoS quality of service
  • FIG. 1 illustrates an example network environment 100 in which various solutions and schemes in accordance with the present disclosure may be implemented.
  • FIG. 1 -FIG. 11 illustrate examples of implementation of various proposed schemes in network environment 100 in accordance with the present disclosure. The following description of various proposed schemes is provided with reference to FIG. 1 -FIG. 11.
  • network environment 100 may include multiple STAs (e.g., STA1 102, STA2 104, STAy 106) being associated and communicating wirelessly with an AP 108.
  • the multiple STAs of the network environment 100 may send UL transmissions to the AP and receive DL transmissions from the AP.
  • a soliciting information/frame with ULLL resource unit (RU) allocations may be used by an AP (e.g., AP 108) to solicit hybrid UL orthogonal frequency-division multiple access (OFDMA) transmissions (e.g., ULLL transmissions) from STAs (e.g., STAs 102, 104, 106) .
  • the AP may send a soliciting information/frame 202 via a DL physical protocol data unit (PPDU) to one or more STAs in a TXOP in accordance with the proposed scheme.
  • PPDU physical protocol data unit
  • the soliciting information/frame 202 may contain allocation of one or more ULLL RUs for the one or more STAs to send any ULLL data that the one or more STAs may have to the AP in a subsequent PPDU 204 (e.g., in a trigger-based (TB) uplink (UL) PPDU format) .
  • the soliciting information/frame 202 may contain allocation of one or more ULLL RUs in the subsequent PPDU 204 for the one or more STAs to send one or more requests to transmit ULLL data to the AP.
  • each request by a corresponding STA is for requesting an additional UL resource allocation for sending ULLL data to the AP.
  • the AP may use the soliciting frame 202 to solicit the transmission of ULLL data or requests to transmit ULLL data by allocating one or more low latency specific RUs during a downlink transmission.
  • the specific RUs may occupy the partial or whole bandwidth of the PPDU.
  • the soliciting information may be carried in the Physical Layer (PHY) Header (e.g., signaling field of the PHY Header) of the DL PPDU.
  • PHY Physical Layer
  • the ULLL RUs that are allocated may be aggregated in OFDMA with the RUs allocated for the response frames to the previous downlink transmissions.
  • the TB PPDU 204 may include ULLL RUs allocated to one or more STAs (Part A) and RUs that are allocated for one or more STAs to provide DL response (Part B) , such as acknowledgments to the received DL transmission from the AP.
  • Part A STAs
  • Part B DL response
  • any STA with LL data can randomly or dedicatedly select a ULLL RU to transmit its LL data or to inform AP that it has LL data.
  • the AP may allocate more ULLL RUs to STAs indicating that they have more LL data in one or more subsequent soliciting frames within the same DL TXOP.
  • FIG. 3 illustrates that an AP may allocate some resources for ULLL traffic while performing downlink data, control frame, and/or management frame transmission during the DL TXOP in order to reduce the latency of uplink low latency traffic.
  • a DL multi- user (MU) PPDU 302 that is sent by the AP to STAs (also referred to herein as non-AP STAs) may include a soliciting frame that polls for ULLL traffic from one or more STAs. It is noteworthy that, in some implementations, the one or more STAs may not be in a same group of STAs that are the recipients of the data in the DL MU PPDU 302.
  • the DL-MU PPDU 302 may also include, in addition to the soliciting frame, DL data, one or more control frames, and/or one or more management frames for some associated STAs, which may include at least one STA of the STAs.
  • the one or more STAs being polled for ULLL traffic may not be the same STAs to which the AP sends the data, control frame, and/or one or more management frames in the DL-MU PPDU 302.
  • the soliciting frame may include resource allocation (ULLL RU allocation) for any potential ULLL data transmission or request to transmit ULLD data transmission from one or more STAs.
  • the AP may configure the soliciting frame to allocate one or more dedicated ULLL RUs to one or more specific STAs.
  • the AP may configure the soliciting information/frame to allocate the partial or whole bandwidth of the PPDU to a range of STAs.
  • Each STA of the range of the STAs may be allocated to a specific RU.
  • ULLL RU 1 may be allocated to STA1
  • ULLL RU 2 may be allocated to STA2
  • ULLL RU 3 may be allocated to STA3, etc.
  • the AP may configure the soliciting frame to allocate a predetermined number of ULLL RUs and indicate to the STAs that any STA with ULLL data may randomly select any available ULLL RU to send ULLL data or a request to transmit ULLL data to the AP (which may potentially cause collision) .
  • the acknowledgment response/block acknowledge (Ack/BA) of the DL-MU PPDU 302 that is sent by one or more STAs may be aggregated with ULLL data and/or one or more requests to transmit ULLL data in the frequency domain.
  • FIG. 4 illustrates a first implementation of the proposed scheme in which a specific ack policy (e.g., the HETP ack policy) is supported by the intended recipient STAs of the DL-MU PPDU.
  • the AP may solicit ULLL data or request to transmit ULLL data from one or more STAs by including a soliciting frame 404 in a DL-MU PPDU 402.
  • the soliciting frame 404 may be aggregated in the frequency domain together with one or more aggregated MAC protocol data units (A-MPDUs) for one or more intended DL data recipient STAs (e.g., STA1, STA2, STA3) in the DL-MU PPDU 402.
  • A-MPDUs aggregated MAC protocol data units
  • a signaling field (SIG-B) in a PHY header of the DL-MU PPDU 402 may include a special identifier (STA-ID) (e.g., STA-ID 2048) to indicate that there is a soliciting frame 404 located in a particular RU of the DL-MU PPDU 402.
  • the soliciting frame 404 may allocate one or more ULLL RUs for one or more STAs to send ULLL data or one or more requests to transmit ULLL data to the AP.
  • the ULLL RUs allocated by the soliciting frame 404 may be dedicated ULLL RUs or randomly accessible ULLL RUs.
  • each STA with ULLL data that receives the DL- MU PPDU 402 and discovers the special identifier in the signaling field may decode the soliciting frame 404 to determine a corresponding ULLL RU that is allocated for use. Subsequently, each STA with ULLA data may use the corresponding ULLL RU in a TB UL PPDU 406 to send the ULLL data or a request to transmit ULLL data to the AP.
  • the TB UL PPDU 406 may be sent by the AP following a short interframe space (SIFS) period 408 after the transmission of the DL-MU PPDU 402.
  • SIFS short interframe space
  • a signaling field (SIG-B) in a PHY header of the DL-MU PPDU 402 may indicate RU allocation for ULLL request or data transmission. For example, the whole bandwidth of the TXOP bandwidth is allocated to ULLL request or data transmission.
  • the RU allocation may be identified by a special identifier (STA-ID) (e.g., STA-ID 2048) .
  • STA-ID special identifier
  • each STA with ULLA data may send the ULLL request to transmit ULLL data to the AP SIFS period after the transmission of the DL-MU PPDU 402.
  • each A-MPDU in the DL-MU PPDU 402 may include one or more QoS data frames with ack policy set to a specific ack policy (e.g., “HETP ack” ) , in which the corresponding A-MPDU for each recipient STA may include trigger information (e.g., trigger frame or trigger info in A-control field of an MPDU header) that prompts each recipient STA to respond with a trigger-based ACK/BA.
  • trigger information e.g., trigger frame or trigger info in A-control field of an MPDU header
  • any ULLL data or request to transmit ULLL data from any ULLL STA may be aggregated with trigger-based ACK/BAs sent by the recipient STAs of the DL-MU PPDU 402 in the frequency domain.
  • FIG. 5 illustrates a second implementation of the proposed scheme.
  • the AP may use a block ack request (BAR) frame or a MU-BAR trigger frame 502 in a DL PPDU as a soliciting frame to solicit ULLL data or request to transmit ULLL data from one or more STAs during a DL TXOP controlled by the AP.
  • BAR or the MU-BAR trigger frame 502 is ordinarily sent by the AP to trigger one or more recipient STAs to provide feedback and/or acknowledgment for DL data (e.g., QoS data frames) previously sent by the AP with the DL TXOP.
  • DL data e.g., QoS data frames
  • the BAR or the MU-BAR trigger frame 502 may be modified with ULLL trigger information.
  • the BAR or the MU-BAR trigger frame may include a special identifier (STA-ID) (e.g., STA-ID 2048) to indicate that there is ULLL trigger information located in a particular RU of the DL PPDU 504 that carries the BAR or the MU-BAR trigger frame 502.
  • STA-ID special identifier
  • the ULLL trigger information may allocate one or more ULLL RUs for one or more STAs to send ULLL data or one or more requests to transmit ULLL data to the AP.
  • the ULLL RUs allocated by the BAR or the MU-BAR trigger frame 502 may be dedicated ULLL RUs or randomly accessible ULLL RUs.
  • the trigger information may also identify a range of STAs or one or more association IDs (AIDs) of particular STAs that are to be polled for ULLL transmissions, i.e., identify one or more specific STAs that are permitted to send their ULLL data or request to transmit ULLL data, if any, to the AP during the DL TXOP.
  • AIDs association IDs
  • each STA with ULLL data that receives the BAR or the MU-BAR trigger frame 502 and discovers the special identifier may decode the frame to determine whether the STA is permitted to send ULLL data or a request to transmit ULLL data to the AP, and if so, a corresponding ULLL RU that is allocated for use. Subsequently, each STA with such ULLL data and has permission to do so may use the corresponding ULLL RU in a TB UL PPDU 506 to send the ULLL data or a request to transmit ULLL data to the AP.
  • the TB UL PPDU 506 may be sent by the AP following an end of a SIFS period 508 after the transmission of the BAR or the MU-BAR trigger frame 502.
  • any ULLL data or request to transmit ULL data to the AP from any STA may be aggregated with trigger-based ACK/BAs from the recipient STAs (e.g., STA1-STAy) of the BAR or the MU-BAR trigger frame 502 in the frequency domain.
  • FIG. 6a and 6b illustrate a third implementation of the proposed scheme.
  • the AP may solicit ULLL data or request to transmit ULLL data from one or more STAs by including a soliciting frame 604 in a DL-MU PPDU 602.
  • the soliciting frame 604 may be aggregated in the frequency domain together with one or more A-MPDUs for one or more intended DL data recipient STAs (e.g., STA1, STA2, STA3) in the DL-MU PPDU 602.
  • a signaling field (SIG-B) in a PHY header of the DL-MU PPDU 602 may include a special identifier (STA-ID) (e.g., STA-ID 2048) to indicate that there is a soliciting frame 604 located in a particular RU of the DL-MU PPDU 602.
  • the soliciting frame 604 may allocate one or more ULLL RUs for one or more STAs to send ULLL data or one or more requests to transmit ULLL data to the AP.
  • the ULLL RUs allocated by the soliciting frame 604 may be dedicated ULLL RUs or randomly accessible ULLL RUs.
  • each A-MPDU in the DL-MU PPDU 602 may include QoS data frames with an acknowledgment policy set to Block Ack so that the recipients of the A-MPDU will not transmit Ack/BA immediately after an end of the SIFS period 606 that follows the received DL-MU PPDU 602.
  • the whole TXOP bandwidth may be allocated to ULLL request or data transmission. Any ULLL data or request to transmit ULLL data from any ULLL STA may be sent SIFS period after the transmission of the DL-MU PPDU 602 without aggregating any ACK/BAs from the recipient STAs of the DL-MU PPDU 602.
  • each STA with ULLL data that receives the DL-MU PPDU 602 and discovers the special identifier in the signaling field may decode the soliciting frame 404 to determine a corresponding ULLL RU that is allocated for use. Subsequently, each STA with ULLL data may use the corresponding ULLL RU in a PPDU 608 to send the ULLL data or a request to transmit ULLL data to the AP.
  • the PPDU 608 may be transmitted to the AP in a UL transmission following an end of a SIFS period 606 after the transmission of the DL-MU PPDU 602.
  • the AP may use a MU-BAR trigger frame 610 to request BAs to the DL-MU PPDU 602 from the recipient STAs.
  • the MU-BAR trigger frame 610 may further include ULLL trigger information to solicit for additional ULLL data or request to transmit ULLL data from one or more STAs during the DL TXOP in a process that is similar to the process described with respect to FIG. 5.
  • the MU-BAR trigger frame 610 may be sent by the AP following an end of a SIFS period 612 after the transmission of the PPDU 608.
  • the one or more STAs may use a TB UL PPDU 614 to send the additional ULLL data or the one or more requests to transmit ULLL data to the AP.
  • the TB UL PPDU 614 may be sent by the AP following an end of a SIFS period 616 after the transmission of the MU-BAR trigger frame 610.
  • any additional ULLL data or request to transmit ULL data to the AP from any STA may be aggregated with trigger-based ACK/BAs from the recipient STAs of the DL-MU PPDU 602 in the frequency domain.
  • the AP may alternatively determine at the end of the SIFS period 606 that no ULLL data or request to transmit ULLL data has been received. For example, the AP may make such a determination when the AP fails to receive a PHY-RXSTART. indication primitive during a timeout interval of aSIFSTime + aSlotTime +aRxPHYStartDelay starting at the end of the DL-MU PPDU 602.
  • the AP may wait for a point coordination function inter-frame space (PIFS) period 618 that is longer in time duration than the SIFS period 616 before transmitting a MU-BAR trigger frame 620 to request Acks/BAs to the DL-MU PPDU 602 from the recipient STAs.
  • PIFS point coordination function inter-frame space
  • the MU-BAR trigger frame 620 may result in the recipient STAs (e.g., STA1-STAy) sending trigger-based Acks/BAs 622 to the AP following an end of a SIFS period 624.
  • the MU-BAR trigger frame 620 may further include ULLL trigger information to solicit for additional ULLL data or request to transmit ULLL data from one or more STAs during the DL TXOP in a process that is similar to the process described with respect to FIG. 5.
  • the AP may send a DL data frame to one or more STAs at the end of the PIFS period 618.
  • the AP may send a DL data frame to one or more STAs at the end of the PIFS period 618 that includes a solicitation for ULLL traffic from the recipient STAs, in which the soliciting frame may be sent and function similarly as the soliciting frame 404 described in FIG. 4.
  • FIG. 7a and 7b illustrate a fourth implementation of the proposed scheme.
  • the AP may solicit a request to transmit ULLL data from one or more STAs by including a soliciting frame 704 in a DL-MU PPDU 702.
  • the soliciting frame 704 may be aggregated in the frequency domain together with one or more A-MPDUs for one or more intended DL data recipient STAs (e.g., STA1, STA2, STAy) in the DL-MU PPDU 702.
  • a signaling field (SIG-B) in a PHY header of the DL-MU PPDU 702 may include a special identifier (STA-ID) (e.g., STA-ID 2048) to indicate that there is a soliciting frame 704 located in a particular RU of the DL-MU PPDU 702.
  • the soliciting frame 704 may allocate symbols of a null data packet (NDP) PPDU for one or more STAs to send one or more requests to transmit ULLL data to the AP.
  • NDP null data packet
  • An NDP PPDU only has a PHY header but lacks a medium access control (MAC) payload.
  • MAC medium access control
  • the soliciting frame may allocate a corresponding symbol to each recipient STA of the recipient STAs, in which each symbol may be used by a corresponding recipient STA to indicate whether the STA has a request via a tone. For example, a STA may use a particular tone in a corresponding symbol to indicate that it has a request to transmit ULLL data to the AP.
  • each A-MPDU in the DL-MU PPDU 702 may include QoS data frames with ack policy set to Block Ack so that the recipients of the A-MPDU will not transmit Ack/BA immediately after an end of a SIFS period 706 that follows the received DL-MU PPDU 702.
  • the recipient STAs that receive the DL-MU PPDU 702 and discover the special identifier in the signaling field may decode the soliciting frame 404 to determine a corresponding symbol that is allocated for use. Subsequently, each STA with ULLL data may use a corresponding symbol in an NDP PPDU 708 to indicate to the AP that it has a request to transmit ULLL data to the AP.
  • the NDP PPDU 708 may be transmitted to the AP in a UL transmission following an end of a SIFS period 706 after the transmission of the DL-MU PPDU 702.
  • the AP may identify each ULLL requester STA through the NDP PPDU 708 and use a MU-BAR trigger frame 710 to trigger each ULLL requester STA to send ULLL data to the AP during the DL TXOP via corresponding allocated ULLL RUs.
  • the MU-BAR trigger frame 710 may be sent by the AP following an end of a SIFS period 712 after the transmission of the NDP PPDU 708.
  • each ULL requester STA may use a corresponding ULLL RU in a TB UL PPDU 714 to send the ULLL data or a request to transmit ULLL data to the AP.
  • the TB UL PPDU 714 may be sent by the AP following an end of a SIFS period 716 after the transmission of the MU-BAR trigger frame 710.
  • the AP may further use the MU-BAR trigger frame 710 to request BAs from the recipient STAs.
  • the ULLL data sent by one or more ULLL requester STAs may be aggregated with trigger-based ACK/BAs from the recipient STAs of the MU-BAR trigger frame 710 in the frequency domain.
  • the AP may alternatively determine at the end of the SIFS period 706 that no NDP PPDU 708 with at least one request to transmit ULLL data is received. For example, the AP may make such a determination when the AP fails to receive a PHY-RXSTART. indication primitive during a timeout interval of aSIFSTime + aSlotTime +aRxPHYStartDelay starting at the end of the DL-MU PPDU 702.
  • the AP may wait for a PIFS period 718 that is longer in time duration than the SIFS period 716 before transmitting a MU-BAR trigger frame 720 to request Acks/BAs to the DL-MU PPDU 602 from the recipient STAs.
  • the MU-BAR trigger frame 720 may result in the recipient STAs (e.g., STA1-STAy) sending trigger-based Acks/BAs 722 to the AP following an end of a SIFS period 724.
  • the MU-BAR trigger frame 720 may further include ULLL trigger information to solicit for additional ULLL data or request to transmit ULLL data from one or more STAs during the DL TXOP in a process that is similar to the process described with respect to FIG. 5.
  • the AP may send a DL data frame to one or more STAs at the end of the PIFS period 718.
  • the AP may send a DL data frame to one or more STAs at the end of the PIFS period 718 that includes a solicitation for ULLL traffic from the recipient STAs, in which the soliciting frame may be sent and function similarly as the soliciting frame 404 described in FIG. 4.
  • FIG. 8a and 8b illustrate a fifth implementation of the proposed scheme.
  • the AP may solicit ULLL data or request to transmit ULLL data from one or more STAs by including a soliciting frame 804 in a DL-MU PPDU 802.
  • the soliciting frame 804 may be aggregated in the frequency domain together with one or more A-MPDUs for one or more intended DL data recipient STAs (e.g., STA1, STA2, STAy) in the DL-MU PPDU 802.
  • a signaling field (SIG-B) in a PHY header of the DL-MU PPDU 802 may include a special identifier (STA-ID) (e.g., STA-ID 2048) to indicate that there is a soliciting frame 804 located in a particular RU of the DL-MU PPDU 802.
  • the soliciting frame 804 may allocate one or more ULLL RUs for one or more STAs to send ULLL data or one or more requests to transmit ULLL data to the AP.
  • the ULLL RUs allocated by the soliciting frame 804 may be randomly accessible ULLL RUs.
  • each A-MPDU in the DL-MU PPDU 802 may include QoS data frames with ack policy set to Block Ack so that the recipients of the A-MPDU will not transmit Ack/BA immediately after an end of a SIFS period 806 that follows the received DL-MU PPDU 802.
  • the whole TXOP bandwidth may be allocated to ULLL request or data transmission. Any ULLL data or request to transmit ULLL data from any ULLL STA may be sent SIFS period after the transmission of the DL-MU PPDU 802 without aggregating any ACK/BAs from the recipient STAs of the DL-MU PPDU 802.
  • each STA with ULLL data that receives the DL-MU PPDU 802 and discovers the special identifier in the signaling field may decode the soliciting frame 404 to select a randomly accessible ULLL RU that is allocated for use. Subsequently, each STA with ULLL data may use the corresponding selected ULLL RU in a PPDU 808 to send the ULLL data or a request to transmit ULLL data to the AP.
  • the PPDU 808 may be transmitted to the AP in a UL transmission following an end of a SIFS period 808 after the transmission of the DL-MU PPDU 802.
  • the AP may use a MU-BAR trigger frame 810 to request BAs to the DL-MU PPDU 802 from the recipient STAs.
  • the MU-BAR trigger frame 810 may further include ULLL trigger information to solicit for additional ULLL data or request to transmit ULLL data from one or more STAs during the DL TXOP in a process that is similar to the process described with respect to FIG. 5.
  • the MU-BAR trigger frame 810 may be sent by the AP following an end of a SIFS period 812 after the transmission of the PPDU 808.
  • the one or more STAs may use a TB UL PPDU 814 to send the additional ULLL data or the one or more requests to transmit ULLL data to the AP.
  • the TB UL PPDU 814 may be sent by the AP following an end of a SIFS period 816 after the transmission of the MU-BAR trigger frame 810.
  • any additional ULLL data or request to transmit ULL data to the AP from any STA may be aggregated with trigger-based ACK/BAs from the recipient STAs of the DL-MU PPDU 802 in the frequency domain.
  • the AP may alternatively determine at the end of the SIFS period 806 that no ULLL data or request to transmit ULLL data has been received via the allocated randomly accessible ULLL RUs. For example, the AP may make such a determination when the AP fails to receive a PHY-RXSTART. indication primitive during a timeout interval of aSIFSTime + aSlotTime + aRxPHYStartDelay starting at the end of the DL-MU PPDU 802.
  • the AP may wait for a PIFS period 818 that is longer in time duration than the SIFS period 816 before transmitting a MU-BAR trigger frame 820 to request Acks/BAs to the DL-MU PPDU 802 from the recipient STAs.
  • the MU-BAR trigger frame 820 may result in the recipient STAs sending trigger-based Acks/BAs 822 to the AP following an end of a SIFS period 824.
  • the MU-BAR trigger frame 820 may further include ULLL trigger information to solicit for additional ULLL data or request to transmit ULLL data from one or more STAs during the DL TXOP in a process that is similar to the process described with respect to FIG. 5.
  • the AP may send a DL data frame to one or more STAs at the end of the PIFS period 818.
  • the AP may send a DL data frame to one or more STAs at the end of the PIFS period 818 that includes a solicitation for ULLL traffic from the recipient STAs, in which the soliciting frame may be sent and function similarly as the soliciting frame 404 described in FIG. 4.
  • the soliciting frames that are implemented in accordance with the proposed scheme may be at least one of the following types: (a) a trigger frame with a new trigger type subfield identifying a ULLL trigger for ULLL data or requests to transmit ULLL data; (b) a trigger frame that includes one or more user Info fields that identify a range of associated STAs to poll for ULLL data or requests to transmit ULLL data.
  • the trigger frame type may be at least one of the following trigger variants: (1) a basic trigger frame, (2) an MU-BAR trigger frame, (3) a basic trigger frame with one or more randomly accessible RU allocations, and (4) an NDP feedback report poll (NFRP) trigger frame.
  • NFRP NDP feedback report poll
  • a soliciting frame may indicate one or more ULLL RU allocations in the User Info field.
  • the one or more ULLL allocations may correspond to a specific STA-AID of an associated STA or a range of associated STA that are to be polled for buffered ULLL data and/or requests to transmit ULLL data.
  • a soliciting frame may indicate the ULLL RU access type as one of the following: (1) dedicated RU or (2) randomly selected RU.
  • the soliciting frame may also indicate at least one of the following subfields in User Info field or Trigger Dependent User Info field: (1) starting STA-AID of a range of STA-AIDs; (2) a starting ULLL RU allocation; (3) a number of allocated ULLL RUs; and (4) a number of STAs to be polled.
  • the soliciting frame may be a broadcast addressed trigger frame.
  • FIG. 9 illustrates an example system 900 having at least an example apparatus 910 and an example apparatus 920 in accordance with an implementation of the present disclosure.
  • apparatus 910 and apparatus 920 may perform various functions to implement schemes, techniques, processes, and methods described herein pertaining to using soliciting frames to reduce UL transmission latency for communications between Wi-Fi STAs, including the various schemes described above with respect to various proposed designs, concepts, schemes, systems and methods described above as well as processes described below.
  • apparatus 910 may be implemented in an STA (e.g., STAs 102, 104, 106) and apparatus 920 may be implemented in an AP, such as AP 108.
  • STA e.g., STAs 102, 104, 106
  • AP such as AP 108.
  • Each of apparatus 910 and apparatus 920 may be a part of an electronic apparatus, such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus.
  • each of apparatus 910 and apparatus 920 may be implemented in a smartphone, a smart watch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer.
  • Each of apparatus 910 and apparatus 920 may also be a part of a machine type apparatus, which may be an IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus.
  • each of apparatus 910 and apparatus 920 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker, or a home control center.
  • apparatus 910 and/or apparatus 920 may be implemented in a network node, such as an AP in a WLAN or a mesh device.
  • each of apparatus 910 and apparatus 920 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors.
  • IC integrated-circuit
  • RISC reduced-instruction set computing
  • CISC complex-instruction-set-computing
  • each of apparatus 910 and apparatus 920 may be implemented in or as a STA or an AP.
  • Each of apparatus 910 and apparatus 920 may include at least some of those components shown in FIG. 9 such as a processor 912 and a processor 922, respectively, for example.
  • Each of apparatus 910 and apparatus 920 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device) , and, thus, such component (s) of apparatus 910 and apparatus 920 are neither shown in FIG. 9 nor described below in the interest of simplicity and brevity.
  • components not pertinent to the proposed scheme of the present disclosure e.g., internal power supply, display device and/or user interface device
  • each of processor 912 and processor 922 may be implemented in the form of one or more single-core processors, one or more multi-core processors, one or more RISC processors or one or more CISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 912 and processor 922, each of processor 912 and processor 922 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure.
  • each of processor 912 and processor 922 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure.
  • each of processor 912 and processor 922 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks including those pertaining to using soliciting frames to reduce UL transmission latency for communications between Wi-Fi STAs in accordance with various implementations of the present disclosure.
  • apparatus 910 may also include a transceiver 916 coupled to processor 912.
  • Transceiver 916 may include a transmitter capable of wirelessly transmitting and a receiver capable of wirelessly receiving data.
  • apparatus 920 may also include a transceiver 926 coupled to processor 922.
  • Transceiver 926 may include a transmitter capable of wirelessly transmitting and a receiver capable of wirelessly receiving data.
  • transceiver 916 and transceiver 926 are illustrated as being external to and separate from processor 912 and processor 922, respectively, in some implementations, transceiver 916 may be an integral part of processor 912 as a system on chip (SoC) and/or transceiver 926 may be an integral part of processor 922 as a SoC.
  • SoC system on chip
  • apparatus 910 may further include a memory 914 coupled to processor 912 and capable of being accessed by processor 912 and storing data therein.
  • apparatus 920 may further include a memory 924 coupled to processor 922 and capable of being accessed by processor 922 and storing data therein.
  • RAM random-access memory
  • DRAM dynamic RAM
  • SRAM static RAM
  • T-RAM thyristor RAM
  • Z-RAM zero-capacitor RAM
  • each of memory 914 and memory 924 may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM) , erasable programmable ROM (EPROM) and/or electrically erasable programmable ROM (EEPROM) .
  • ROM read-only memory
  • PROM programmable ROM
  • EPROM erasable programmable ROM
  • EEPROM electrically erasable programmable ROM
  • each of memory 914 and memory 924 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM) , magnetoresistive RAM (MRAM) and/or phase-change memory.
  • NVRAM non-volatile random-access memory
  • Each of apparatus 910 and apparatus 920 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure.
  • a description of capabilities of apparatus 910 or apparatus 920 as an STA (e.g., STAs 102, 104, 106) or an AP, such as AP 108, respectively, is provided below in the context of example processes 1000 and 1100.
  • STA e.g., STAs 102, 104, 106
  • AP such as AP 108
  • FIG. 10 illustrates an example process 1000 in accordance with an implementation of the present disclosure.
  • Process 1000 may represent an aspect of implementing various proposed designs, concepts, schemes, systems, and methods described above. More specifically, process 1000 may represent an aspect of the proposed concepts and schemes pertaining to using soliciting frames to reduce UL transmission latency for communications between Wi-Fi STAs.
  • Process 1000 may include one or more operations, actions, or functions as illustrated by one or more of blocks 1010 and 1020. Although illustrated as discrete blocks, various blocks of process 1000 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process 1000 may be executed in the order shown in FIG. 10 or, alternatively in a different order.
  • Process 1000 may be implemented by or in apparatus 910 and apparatus 920 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 1000 is described below in the context of apparatus 910 implemented in or as a station (e.g., STA 102) and apparatus 920 implemented in or as an AP of a wireless network such as a WLAN in network environment 100 in accordance with one or more of IEEE 802.11 standards. Process 1000 may begin at block 1010.
  • process 1000 may include processor 922 of apparatus 920 that is implemented as an AP sending a soliciting information in a DL PPDU during a TXOP, indicating to allow one or more STAs associated with the apparatus to send uplink low latency (ULLL) data or one or more requests to transmit ULLL data to the apparatus 920.
  • Process 1000 may proceed from 1010 to 1020.
  • process 1000 may include processor 922 receiving the ULLL data or the at least one request to transmit ULLL data from at least one STA of the one or more STAs in response to the soliciting information.
  • the soliciting information in the DL PPDU may be aggregated in a frequency domain with one or more MPDUs or A-MPDUs for one or more DL data recipient STAs associated with the apparatus 920.
  • each A-MPDU may trigger a corresponding DL data recipient STA to provide a corresponding triggered-based acknowledgment of the DL PPDU in the subsequent TB UL PPDU.
  • the soliciting information in the DL PPDU may be in the PHY header of the DL PPDU.
  • the soliciting information may allocate one or more resource units (RUs) for the one or more STAs to send the ULLL data or the one or more requests to transmit ULLL data to the apparatus, and wherein the receiving includes receiving the ULLL data or the at least one request to transmit ULLL data in the one or more RUs.
  • the ULLL data or the at least one request to transmit ULLL data from at least one STA of the one or more STAs may be transmitted in a TB UL PPDU or a NDP that follows the sending of the DL PPDU.
  • the one or more RUs may be a dedicated RU that is allocated to a corresponding STA, or a randomly accessible RU that is selectable by any STA of one or more STAs.
  • the RU allocation by the soliciting information may correspond to a special or reserved STA-AID to indicate that the RU allocation is specific to the ULLL data or the one or more requests to transmit ULLL data.
  • RU allocation by the soliciting information may correspond to a specific STA-AID of an associated STA or a range of STA-AIDs of multiple associated STAs or any associated STA to be polled by the apparatus for the ULLL data or the one or more requests to transmit ULLL data.
  • the soliciting information may indicate at least one of a starting STA-AID of the range of STA-AIDs of the multiple associated STAs, a starting RU allocation, a number of allocated RUs, a range of allocated RUs and the range of STA-AIDs to be polled for the ULLL data or the one or more requests to transmit ULLL data.
  • the soliciting information may be included in a trigger frame that includes a ULLL trigger for ULLL data or requests to transmit ULLL data, or a trigger frame that identifies a range of associated STAs to poll for ULLL data or requests to transmit ULLL data.
  • the trigger frame may be a basic trigger frame, a BAR trigger frame, a MU-BAR trigger frame, a basic trigger frame with one or more randomly accessible RU allocations, or an NDP Feedback Report Poll (NFRP) trigger frame.
  • the BAR trigger frame or the MU-BAR trigger frame may trigger ULLL data or the at least one request to transmit ULLL in the TB UL PPDU integrated in a frequency domain with one or more triggered-based acknowledgments of the data received from the DL PPDU.
  • the NFRP trigger frame may trigger/poll ULLL request to transmit ULLL data in the TB NDP PPDU.
  • FIG. 11 illustrates an example process 1100 in accordance with an implementation of the present disclosure.
  • Process 1100 may represent an aspect of implementing various proposed designs, concepts, schemes, systems, and methods described above. More specifically, process 1100 may represent an aspect of the proposed concepts and schemes pertaining to using soliciting frames to reduce UL transmission latency for communications between Wi-Fi STAs.
  • Process 1100 may include one or more operations, actions, or functions as illustrated by one or more of blocks 1110 and 1120. Although illustrated as discrete blocks, various blocks of process 1100 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process 1100 may be executed in the order shown in FIG. 11 or, alternatively, in a different order.
  • Process 1100 may be implemented by or in apparatus 910 and apparatus 920 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 1100 is described below in the context of apparatus 910 implemented in or as a station (e.g., STA 102) and apparatus 920 implemented in or as an AP of a wireless network such as a WLAN in network environment 100 in accordance with one or more of IEEE 802.11 standards. Process 1100 may begin at block 1110.
  • process 1100 may include processor 922 of apparatus 920 implemented as an AP sending a soliciting information in a DL PPDU during a TXOP, indicating to allow one or more STAs associated with the apparatus to send ULLL data or one or more requests to transmit ULLL data to the AP.
  • Process 1100 may proceed from 1110 to 1120.
  • process 1100 may include processor 922 in response to receiving a subsequent UL transmission that includes the ULLL data or the at least one request to transmit ULLL data from at least one STA of the one or more STAs following an end of a time period that starts after the sending of the DL PPDU, sending a trigger frame from the AP to solicit additional ULLL data or request to transmit ULLL data from the one or more STAs during the TXOP.
  • the soliciting information may allocate one or more RUs for the one or more STAs to send the ULLL data or the one or more requests to transmit ULLL data to the AP, and the receiving the subsequent UL transmission includes receiving the ULLL data or the at least one request to transmit ULLL data from at least one STA of the one or more STAs in the one or more RUs.
  • the ULLL data or the at least one request to transmit ULLL data from at least one STA of the one or more STAs may be transmitted in a TB UL PPDU or a NDP PPDU that follows the sending of the DL PPDU.
  • each of the one or more RUs may be a dedicated RU that is allocated to a corresponding STA, or a randomly accessible RU that is selectable by any STA of the one or more STAs.
  • process 1100 may additionally include processor 922 performing operations that include receiving the additional ULLL data or request to transmit ULLL data from the one or more STAs in a TB PPDU following the sending of the MU-BAR trigger frame.
  • the time period may be a SIFS period and the soliciting frame in the DL PPDU may be aggregated in a frequency domain with one or more MAC protocol data A-MPDUs for one or more DL data recipient STAs associated with the AP, and each A-MPDU may configure a corresponding DL data recipient STA to refrain from providing a corresponding trigger-based acknowledgment of the DL PPDU immediately after the end of the SIFS period.
  • the TB PPDU may further include the corresponding trigger-based acknowledgment of the DL PPDU by the corresponding DL data recipient STA.
  • process 1100 may additionally include processor 922 performing operations that include in response to failing to receive the subsequent UL transmission following the end of the SIFS period, sending, from the AP, an additional frame at the end of a PIFS period that starts after the sending of the DL PPDU, wherein the PIFS period is longer in time duration than the SIFS period.
  • the TB PPDU may further include the corresponding trigger-based acknowledgment of the DL PPDU by the corresponding DL data recipient STA.
  • any two components so associated can also be viewed as being “operably connected” , or “operably coupled” , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable” , to each other to achieve the desired functionality.
  • operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Landscapes

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

Abstract

L'invention concerne des techniques se rapportant à la réduction de la latence de transmission de liaison descendante (DL) d'une unité de données de protocole physique pour des communications entre des stations (STA) Wi-Fi et des points d'accès (AP). Un appareil peut envoyer une trame de sollicitation dans une unité de données de protocole physique (PPDU) de liaison descendante (DL) à une ou plusieurs stations (STA) associées à l'appareil pendant une opportunité de transmission DL (TXOP) commandée par l'appareil. La trame de sollicitation peut demander à la ou aux STA d'envoyer des données de faible latence de liaison montante (ULLL) ou une ou plusieurs demandes de transmission de données ULLL à l'appareil. L'appareil peut en outre recevoir les données ULLL ou la ou les requêtes pour transmettre des données ULLL à partir d'au moins une STA de la ou des STA dans une unité PPDU de liaison montante (UL) basée sur un déclencheur (TB) qui suit l'envoi de la PPDU DL.
EP24752893.8A 2023-02-07 2024-02-07 Mécanismes de transmission de liaison montante à latence réduite Pending EP4662960A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363483540P 2023-02-07 2023-02-07
PCT/CN2024/076590 WO2024165038A1 (fr) 2023-02-07 2024-02-07 Mécanismes de transmission de liaison montante à latence réduite

Publications (1)

Publication Number Publication Date
EP4662960A1 true EP4662960A1 (fr) 2025-12-17

Family

ID=92262063

Family Applications (1)

Application Number Title Priority Date Filing Date
EP24752893.8A Pending EP4662960A1 (fr) 2023-02-07 2024-02-07 Mécanismes de transmission de liaison montante à latence réduite

Country Status (3)

Country Link
EP (1) EP4662960A1 (fr)
CN (1) CN120858640A (fr)
WO (1) WO2024165038A1 (fr)

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3236625B1 (fr) * 2014-12-16 2020-07-22 LG Electronics Inc. Procédé de transmission de données dans un système de communication sans fil et dispositif associé
EP3247165B1 (fr) * 2015-02-11 2021-06-30 Huawei Technologies Co., Ltd. Station (sta)
US10116361B2 (en) * 2015-06-02 2018-10-30 Newracom, Inc. Methods for uplink multiuser signaling and transmission
US9762487B2 (en) * 2015-06-02 2017-09-12 Newracom, Inc. ACK policy for uplink and downlink MU PPDU
US20230028874A1 (en) * 2022-08-26 2023-01-26 Juan Fang Ultra-low latency (ull) communications using a dedicated resource unit (ru)

Also Published As

Publication number Publication date
WO2024165038A1 (fr) 2024-08-15
CN120858640A (zh) 2025-10-28

Similar Documents

Publication Publication Date Title
US12185369B2 (en) Enhanced high-throughput multi-link channel access and operation
US12089254B2 (en) Bandwidth extension indication and negotiation in wireless communications
US12520341B2 (en) Method for sharing multilink in next-generation wireless LAN
US11997523B2 (en) Efficient trigger-based multi-user uplink transmissions in wireless local area networks
US20230319923A1 (en) Enhanced Multi-Link Single-Radio And Multi-Radio Subband Operations In Wireless Communications
WO2024149187A1 (fr) Accès à un canal amélioré pour des transmissions à faible latence
KR20210025098A (ko) 트리거 기반의 다중 사용자 전송들에서 직접 링크 및 다운링크 전송들
CN116896768A (zh) 无线通信方法以及无线通信装置
US20250287363A1 (en) Wide Bandwidth Transmission With Dynamic Subchannel And Subband Operations In Wireless Communications
WO2024165038A1 (fr) Mécanismes de transmission de liaison montante à latence réduite
US11943643B2 (en) Wide bandwidth transmission schemes
WO2025228359A1 (fr) Procédés de communication sans fil
WO2026051939A1 (fr) Schémas de commutation d'opération de sous-bande dynamique dans des communications sans fil
WO2026012397A1 (fr) Schémas de transmission de coordination d'ap multiples dans des communications sans fil
WO2025247374A1 (fr) Schémas de transmission de bande passante partielle dans des communications sans fil
KR102497152B1 (ko) 복수의 단말의 데이터 전송을 관리하는 장치 및 그의 동작 방법
WO2025185462A1 (fr) Réduction de puissance proportionnelle d'accès au canal pour des transmissions à faible latence dans des communications sans fil
WO2025180433A1 (fr) Schémas de transmission de coordination d'ap multiples dans des communications sans fil
WO2025231877A1 (fr) Procédé et appareil permettant de rapporter un rapport d'informations d'état de canal, dispositifs et support
CN121284734A (zh) 预抢占方法、装置以及设备
WO2025148073A1 (fr) Procédé et appareil de détermination de ressources de canal de liaison montante, dispositif, support et produit-programme
CN121619659A (zh) 通信方法和通信装置

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20250821

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR