WO2024131875A1 - Procédé et appareil pour gérer une configuration de vecteur d'attribution de réseau dans un système à points d'accès multiples - Google Patents

Procédé et appareil pour gérer une configuration de vecteur d'attribution de réseau dans un système à points d'accès multiples Download PDF

Info

Publication number
WO2024131875A1
WO2024131875A1 PCT/CN2023/140498 CN2023140498W WO2024131875A1 WO 2024131875 A1 WO2024131875 A1 WO 2024131875A1 CN 2023140498 W CN2023140498 W CN 2023140498W WO 2024131875 A1 WO2024131875 A1 WO 2024131875A1
Authority
WO
WIPO (PCT)
Prior art keywords
nav
sta
intra
response frame
bss
Prior art date
Application number
PCT/CN2023/140498
Other languages
English (en)
Inventor
Chien-Fang Hsu
Hao-Hua Kang
Original Assignee
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. filed Critical Mediatek Inc.
Publication of WO2024131875A1 publication Critical patent/WO2024131875A1/fr

Links

Definitions

  • the present invention relates to wireless communications, and more particularly, to a method and apparatus for dealing with network allocation vector (NAV) setup in a multi-access-point (MAP) system.
  • NAV network allocation vector
  • MAP multi-access-point
  • APs access points
  • TXOP transmission opportunity
  • TWT target wake time
  • SP target wake time
  • JT joint transmission
  • member APs of the MAP system can perform coordinated frequency division multiple access (FDMA) transmission, where the transmission band is shared by member APs to do concurrent (at least partially overlapped in time) and independent transmission on different subbands.
  • member APs of the MAP system can perform coordinated beamforming (CBF) on the same or partially overlapped frequency band.
  • FDMA coordinated frequency division multiple access
  • CBF coordinated beamforming
  • the NAV is a virtual carrier-sensing mechanism which limits the need for physical carrier-sensing at the air interface in order to save power.
  • the medium access control (MAC) frame header contains a duration field that specifies the transmission time in which the wireless medium will be busy.
  • a non-AP station (STA) listening on the wireless medium reads the duration field and sets its NAV, which is an indicator for the non-AP STA on how long it must defer from accessing the wireless medium.
  • inter-BSS NAV a basic NAV
  • intra-BSS NAV an intra-BSS NAV
  • the basic NAV is a NAV that is maintained and updated by receipt of an inter physical layer protocol data unit (inter-PPDU) or a PPDU that cannot be classified as inter-PPDU or intra-PPDU
  • inter-PPDU inter physical layer protocol data unit
  • intra-BSS NAV is maintained and updated by an intra-PPDU only.
  • One of the objectives of the claimed invention is to provide a method and apparatus for dealing with NAV setup in an MAP system.
  • an exemplary network allocation vector (NAV) setup method includes: after a first access point (AP) of a multi-AP (MAP) system sends a request frame to a second AP of the MAP system to indicate that the first AP intends to share transmission resources with the second AP, in response to receipt of a response frame sent from the second AP to indicate that the second AP accepts to use the transmission resources shared by the first AP, managing at least one of a basic NAV and an intra basic service set (intra-BSS) NAV of a non-AP station (STA) according to the response frame, wherein the non-AP STA is associated with one of the first AP and the second AP.
  • AP access point
  • MAP multi-AP
  • an exemplary network allocation vector (NAV) setup method includes: after a first access point (AP) of a multi-AP (MAP) system sends a request frame to a second AP of the MAP system to indicate that the first AP intends to share transmission resources with the second AP, in response to receipt of a response frame sent from the second AP to indicate that the second AP rejects to use the transmission resources shared by the first AP, managing one of a basic NAV and an intra basic service set (intra-BSS) NAV of a non-AP station (STA) according to the response frame, wherein the non-AP STA is associated with one of the first AP and the second AP.
  • AP access point
  • MAP multi-AP
  • an exemplary non-access-point (non-AP) station STA
  • the exemplary non-AP STA includes a network interface circuit and a control circuit.
  • the network interface circuit is arranged to receive a response frame sent from a second access point (AP) of a multi-AP (MAP) system to indicate that the second AP accepts to use transmission resources shared by a first AP of the MAP system after the first AP sends a request frame to the second AP to indicate that the first AP intends to share the transmission resources with the second AP.
  • AP access point
  • MAP multi-AP
  • the control circuit is arranged to manage at least one of a basic network allocation vector (NAV) and an intra basic service set (intra-BSS) NAV of the non-AP STA according to the response frame, wherein the non-AP STA is associated with one of the first AP and the second AP.
  • NAV basic network allocation vector
  • intra-BSS intra basic service set
  • FIG. 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating a Wi-Fi system according to an embodiment of the present invention.
  • FIG. 3 is a diagram illustrating a first NAV setup scenario according to an embodiment of the present invention.
  • FIG. 4 is a diagram illustrating a second NAV setup scenario according to an embodiment of the present invention.
  • FIG. 5 is a diagram illustrating a third NAV setup scenario according to an embodiment of the present invention.
  • FIG. 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention.
  • the wireless communication system 100 may be a Wi-Fi system compliant with IEEE 802.11ax standard, IEEE 802.11be standard, or a next-generation Wi-Fi standard.
  • the wireless communication system 100 includes a plurality of APs and a plurality of non-AP STAs. For brevity and simplicity, only two APs 102, 104 and one non-AP STA 106 are illustrated in FIG. 1.
  • the APs 102, 104 are member APs of the same MAP system, and the AP 102 is a sharing AP that intends to share its transmission resources with a shared AP (e.g., AP 104) .
  • a shared AP e.g., AP 104
  • the AP 102 uses a frame, such as a multi-user request to send (MU-RTS) frame, to get a TXOP or to continue an existing TXOP, and intends to share the TXOP with other AP (s) of the same MAP system.
  • a frame such as a multi-user request to send (MU-RTS) frame
  • MU-RTS multi-user request to send
  • those APs can do coordination transmission such as joint transmission, coordinated FDMA, or coordinated beamforming.
  • AP and “member AP” may be interchangeable.
  • the AP 102 sends a request frame REQ to the AP 104 to indicate that the AP 102 intends to share its transmission resources to do certain coordination transmission.
  • the AP 104 sends backs a response frame RSP to the AP 102 to accept or reject the sharing request issued by the AP 102.
  • the request frame REQ can be an MU-RTS frame carrying sharing parameters.
  • the sharing parameters may include the sharing method (e.g., coordinated time division multiple access (TDMA) , coordinated orthogonal frequency division multiple access (OFDMA) , joint transmission, or coordinated beamforming) , timing of the shared period (e.g., start time, duration, and end time) , and/or the coordinated beamforming parameters (e.g., target (candidate) STA identifier (ID) and beam change needed indication) .
  • TDMA coordinated time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • joint transmission or coordinated beamforming
  • timing of the shared period e.g., start time, duration, and end time
  • the coordinated beamforming parameters e.g., target (candidate) STA identifier (ID) and beam change needed indication
  • the response frame RSP may be a clear to send (CTS) frame or any other response frame.
  • the response frame RSP may carry indication that explicitly indicates whether the sharing request issued from the AP 102 is accepted or rejected by the AP 104.
  • the action of sending the response frame RSP may implicitly indicate that the sharing request is accepted by the AP 104, if the response frame RSP is not a Contention-Free end (CF-end) frame.
  • the action of not sending the response frame RSP may implicitly indicate that the sharing request is rejected by the AP 104, or may indicate failed receipt of the request frame REQ.
  • the AP 102 can use a Priority Interframe Space (PIFS) recovery procedure to access the wireless medium for follow-up transmission to intra-BSS stations.
  • PIFS Priority Interframe Space
  • the AP 104 may send a CF-end frame as the response frame RSP.
  • the non-AP STA 106 supports the proposed NAV setup scheme, and is a client that can be associated with the MAP system though coordination association.
  • the non-AP STA 106 may be associated with one of the APs 102 and 104 of the MAP system.
  • the non-AP STA 106 includes a processor 112, a memory 114, a control circuit 116, and a network interface circuit 117, where the network interface circuit 117 may be a transceiver including a TX circuit 118 and an RX circuit 120.
  • the memory 114 is arranged to store a program code.
  • the processor 112 is arranged to load and execute the program code to manage the non-AP STA 106.
  • the control circuit 116 is arranged to control wireless communications with an associated AP.
  • the control circuit 116 controls the TX circuit 118 of the network interface circuit 117 to deal with uplink (UL) traffic, and controls the RX circuit 120 of the network interface circuit 117 to deal with downlink (DL) traffic.
  • UL uplink
  • DL downlink
  • the non-AP STA 106 is capable of maintaining two NAVs, including a basic NAV (i.e., inter-BSS NAV) and an intra-BSS NAV.
  • the non-AP STA 106 is a client associated with one AP of the MAP system.
  • the control circuit 116 may manage at least one of the basic NAV and the intra-BSS NAV of the non-AP STA 106 according to the request frame REQ.
  • the control circuit 116 may manage at least one of the basic NAV and the intra-BSS NAV of the non-AP STA 106 according to the response frame RSP.
  • the basic NAV and the intra-BSS NAV With proper setup of the basic NAV and the intra-BSS NAV, the transmission behaviors during the shared period in the MAP system can be well regulated. Further details of the proposed NAV setup scheme are described as below with reference to the accompanying drawings.
  • FIG. 2 is a diagram illustrating a Wi-Fi system according to an embodiment of the present invention.
  • the Wi-Fi system 200 includes multiple APs AP1 and AP2 of the same MAP system, and further includes multiple non-AP STAs STA1, STA2, STA3, STA4.
  • the non-AP STAs STA1 and STA3 are associated with the AP AP1.
  • the non-AP STAs STA2 and STA4 are associated with the AP AP2.
  • the non-AP STA STA3 is a hidden node to the AP AP2.
  • the non-AP STA STA4 is a hidden node to the AP AP1.
  • the AP AP1 may be the AP 102 shown in FIG.
  • the AP AP2 may be the AP 104 shown in FIG. 1. That is, the AP AP1 intends to share its transmission resources with the AP AP2 to do certain coordination transmission.
  • the non-AP STA 106 shown in FIG. 1 may be one of the non-AP STAs STA1-STA4. That is, each of the non-AP STAs STA1-STA4 supports the proposed NAV setup scheme, and may have the same circuit structure shown in FIG. 1.
  • FIG. 3 is a diagram illustrating a first NAV setup scenario according to an embodiment of the present invention.
  • the sharing request is accepted.
  • the AP AP1 sends the request frame REQ to the AP AP2. Since the non-AP STAs STA1 and STA3 are associated with the AP AP1, both of the non-AP STAs STA1 and STA3 can hear the request frame REQ and regard the request frame REQ as an intra-BSS frame. Hence, each of the non-AP STAs STA1 and STA3 sets up its intra-BSS NAV according to the duration information carried in the request frame REQ.
  • the non-AP STA STA2 Since the non-AP STA STA2 is not a hidden node to the AP AP1, the non-AP STA STA2 can hear the request frame REQ. Since the non-AP STA STA2 is not associated with the AP AP1, the non-AP STA STA2 regards the request frame REQ as an inter-BSS frame. Hence, the non-AP STA STA2 sets up its basic NAV according to the duration information carried in the request frame REQ. Since the non-AP STA STA STA4 is a hidden node to the AP AP1, the non-AP STA STA4 cannot hear the request frame REQ. Hence, the non-AP STA STA4 does not set up its basic NAV.
  • the AP AP2 After receiving the request frame REQ from the AP AP1, the AP AP2 sends back the response frame RSP to indicate that the AP AP2 accepts to use the transmission resources shared by the AP AP1. Since the non-AP STA STA1 is not a hidden node to the AP AP2, the non-AP STA STA1 can hear the response frame RSP. Since the response frame RSP explicitly/implicitly indicates that the AP AP2 accepts to use the transmission resources shared by the AP AP1, the non-AP STA STA1 regards AP2’s transmission, including the response frame RSP, as intra-BSS.
  • the non-AP STA STA1 does not need to set up its basic NAV. Since the non-AP STA STA3 is a hidden node to the AP AP2, the non-AP STA STA3 cannot hear the response frame RSP. Hence, the non-AP STA STA3 does not need to set up its basic NAV. Specifically, since the non-AP STA STA3 can only hear the request frame REQ, the non-AP STA STA3 sets up its intra-BSS NAV only.
  • the non-AP STA STA2 Since the non-AP STA STA2 is associated with the AP AP2, the non-AP STA STA2 can hear the response frame RSP. Since the response frame RSP explicitly/implicitly indicates that the AP AP2 accepts to use the transmission resources shared by the AP AP1, the non-AP STA STA2 regards AP1’ transmission as intra-BSS rather than inter-BSS. Hence, according to the response frame RSP indicative of acceptance of the sharing, the non-AP STA STA2 sets up its intra-BSS NAV, and further ceases its basic NAV that was previously set up due to the request frame REQ issued from the AP AP1.
  • the non-AP STA STA2 sets up its intra-BSS NAV, and further ignores its basic NAV that was previously set up due to the request frame REQ issued from the AP AP1. That is, the non-AP STA STA2 may keep the basic NAV that was set up before the response frame RSP is set from the AP AP2, but will ignore it when requiring/being requested for transmission.
  • the non-AP STA STA4 Since the non-AP STA STA4 is associated with the AP AP2, the non-AP STA STA4 can hear the response frame RSP. Since the response frame RSP explicitly/implicitly indicates that the AP AP2 accepts to use the transmission resources shared by the AP AP1, the non-AP STA STA4 regards AP1’ transmission as intra-BSS rather than inter-BSS. Hence, according to the response frame RSP indicative of acceptance of the sharing, the non-AP STA STA4 sets up its intra-BSS NAV. Specifically, since the non-AP STA STA4 can only hear the response frame RSP, the non-AP STA STA4 sets up its intra-BSS NAV only.
  • FIG. 4 is a diagram illustrating a second NAV setup scenario according to an embodiment of the present invention.
  • the sharing request is rejected.
  • the AP AP1 sends the request frame REQ to the AP AP2. Since the non-AP STAs STA1 and STA3 are associated with the AP AP1, both of the non-AP STAs STA1 and STA3 can hear the request frame REQ and regard the request frame REQ as an intra-BSS frame. Hence, each of the non-AP STAs STA1 and STA3 sets up its intra-BSS NAV according to the duration information carried in the request frame REQ.
  • the non-AP STA STA2 Since the non-AP STA STA2 is not a hidden node to the AP AP1, the non-AP STA STA2 can hear the request frame REQ. Since the non-AP STA STA2 is not associated with the AP AP1, the non-AP STA STA2 regards the request frame REQ as an inter-BSS frame. Hence, the non-AP STA STA2 sets up its basic NAV according to the duration information carried in the request frame REQ. Since the non-AP STA STA STA4 is a hidden node to the AP AP1, the non-AP STA STA4 cannot hear the request frame REQ. Hence, the non-AP STA STA4 does not set up its basic NAV.
  • the AP AP2 After receiving the request frame REQ from the AP AP1, the AP AP2 sends back the response frame RSP to indicate that the AP AP2 rejects to use the transmission resources shared by the AP AP1. Since the non-AP STA STA1 is not a hidden node to the AP AP2, the non-AP STA STA1 can hear the response frame RSP. Since the response frame RSP explicitly indicates that the AP AP2 rejects to use the transmission resources shared by the AP AP1, the non-AP STA STA1 realizes that there is no AP2’s transmission during the current TXOP owned by the AP AP1.
  • the non-AP STA STA1 does not need to set up its basic NAV. Since the non-AP STA STA3 is a hidden node to the AP AP2, the non-AP STA STA3 cannot hear the response frame RSP. Hence, the non-AP STA STA3 does not need to set up its basic NAV. Specifically, since the non-AP STA STA3 can only hear the request frame REQ, the non-AP STA STA3 sets up its intra-BSS NAV only.
  • the non-AP STA STA2 Since the non-AP STA STA2 is associated with the AP AP2, the non-AP STA STA2 can hear the response frame RSP. Since the response frame RSP explicitly indicates that the AP AP2 rejects to use the transmission resources shared by the AP AP1, the non-AP STA STA2 realizes that there is no AP2’s transmission during the current TXOP owned by the AP AP1. Hence, according to the response frame RSP indicative of rejection of the sharing, the non-AP STA STA2 does not need to set up its intra-BSS NAV. Specifically, during the current TXOP owned by the AP AP1, the non-AP STA STA2 regards AP1’s transmission as inter-BSS only.
  • the non-AP STA STA4 Since the non-AP STA STA4 is associated with the AP AP2, the non-AP STA STA4 can hear the response frame RSP. Since the response frame RSP explicitly indicates that the AP AP2 rejects to use the transmission resources shared by the AP AP1, the non-AP STA STA4 realizes that there is no AP2’s transmission during the current TXOP owned by the AP AP1. Hence, according to the response frame RSP indicative of rejection of the sharing, the non-AP STA STA4 does not need to set up its intra-BSS NAV. Specifically, the non-AP STA STA4 can only hear the response frame RSP, but does not set up its intra-BSS NAV.
  • FIG. 5 is a diagram illustrating a third NAV setup scenario according to an embodiment of the present invention.
  • the sharing request is rejected.
  • the difference between the third NAV setup scenario and the second NAV setup scenario is that the AP AP2 does not respond to the AP AP1’s REQ as the indication for rejection of the sharing (or indication of failed receipt of the request frame REQ) .
  • the AP AP1 sends the request frame REQ to the AP AP2.
  • both of the non-AP STAs STA1 and STA3 can hear the request frame REQ and regard the request frame REQ as an intra-BSS frame.
  • each of the non-AP STAs STA1 and STA3 sets up its intra-BSS NAV according to the duration information carried in the request frame REQ. Since the non-AP STA STA2 is not a hidden node to the AP AP1, the non-AP STA STA2 can hear the request frame REQ. Since the non-AP STA STA2 is not associated with the AP AP1, the non-AP STA STA2 regards the request frame REQ as an inter-BSS frame.
  • the non-AP STA STA2 sets up its basic NAV according to the duration information carried in the request frame REQ. Since the non-AP STA STA 4 is a hidden node to the AP AP1, the non-AP STA STA4 cannot hear the request frame REQ. Hence, the non-AP STA STA4 does not set up its basic NAV. After receiving the request frame REQ from the AP AP1, the AP AP2 does not send back a response frame. Since no response frame from the AP AP2 can be received by any of the non-AP STAs STA1-STA4, there is no response frame introduced change made to any of the basic NAV and the intra-BSS NAV.

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

Un procédé de configuration de vecteur d'attribution de réseau (NAV) consiste : après qu'un premier point d'accès (AP) d'un système multi-AP (MAP) a envoyé une trame de demande à un second AP du système MAP pour indiquer l'intention du premier AP de partager des ressources de transmission avec le second AP, en réponse à la réception d'une trame de réponse envoyée par le second AP pour indiquer que le second AP accepte d'utiliser les ressources de transmission partagées par le premier AP, à gérer un NAV de base et/ou un NAV d'ensemble de services de base intra (intra-BSS) d'une station (STA) non AP d'après la trame de réponse, dans lequel la STA non AP est associée au premier AP et/ou au second AP.
PCT/CN2023/140498 2022-12-23 2023-12-21 Procédé et appareil pour gérer une configuration de vecteur d'attribution de réseau dans un système à points d'accès multiples WO2024131875A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202263476988P 2022-12-23 2022-12-23
US63/476988 2022-12-23
US202363545215P 2023-10-23 2023-10-23
US63/545215 2023-10-23

Publications (1)

Publication Number Publication Date
WO2024131875A1 true WO2024131875A1 (fr) 2024-06-27

Family

ID=91587716

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/140498 WO2024131875A1 (fr) 2022-12-23 2023-12-21 Procédé et appareil pour gérer une configuration de vecteur d'attribution de réseau dans un système à points d'accès multiples

Country Status (1)

Country Link
WO (1) WO2024131875A1 (fr)

Similar Documents

Publication Publication Date Title
US10582566B2 (en) Method and apparatus for triggering uplink data in wireless LAN
US10841924B2 (en) Basic bandwidth device on secondary channel
US20220141785A1 (en) Multi-link communication method and apparatus
US10194468B2 (en) Wireless channel reservation
US11700546B2 (en) Multi-user wireless communication method and wireless communication terminal using same
US9161260B2 (en) Method and apparatus for space division multiple access for wireless local area network system
US20230308155A1 (en) Apparatus and methods for multi-ap joint transmission and reception
EP2702823B1 (fr) Appareil et procédé d'accès à un canal dans un système de réseau local sans fil
US20240155684A1 (en) Wireless communication method and wireless communication terminal
MX2007001704A (es) Metodo y sistema para controlar el acceso a un medio de comunicacion inalambrica.
JP2008532332A (ja) 無線チャネルによって接続される複数の局及び１つのアクセスポイントを含む通信ネットワークにおける無線チャネルにアクセスする方法及び無線通信ネットワーク
EP3534650B1 (fr) Procédé de transmission de trame de réveil, et procédé, dispositif et équipement destinés à transmettre une première trame après le réveil d'un noeud
US9609678B2 (en) Method and apparatus for asynchronous Direct Link Setup in WLAN system
JP2017505082A (ja) 無線ｌａｎシステムにおいて下りリンク用チャネルを含む無線チャネルを設定する方法及びそのための装置
CN113632580A (zh) 随机接入过程中消息3的cot共享指示符
US20240049304A1 (en) Wireless communication method using multi-link, and wireless communication terminal using same
WO2024131875A1 (fr) Procédé et appareil pour gérer une configuration de vecteur d'attribution de réseau dans un système à points d'accès multiples
KR20170062719A (ko) 고효율 무선랜에서 상향링크 다중 사용자 전송을 지원하기 위한 채널 액세스 방법 및 장치
US11737141B2 (en) Method and apparatus of setting protection frames for protecting transmission of preamble punctured physical layer protocol data unit
WO2023152843A1 (fr) Dispositif de communication sans fil et procédé de communication sans fil
US20230254735A1 (en) Radio communication apparatus and radio communication method
EP4376478A1 (fr) Procédé et appareil de communication nstr dans un système de communication prenant en charge de multiples liaisons
US20240107604A1 (en) Network allocation vector (nav) operation in multi-access point (ap) coordination
US20240237066A9 (en) Low latency support in mmwave link
US20240137982A1 (en) Low latency support in mmwave link