WO2022251117A1 - Restricted target wait time (r-twt) operations and parameters - Google Patents
Restricted target wait time (r-twt) operations and parameters Download PDFInfo
- Publication number
- WO2022251117A1 WO2022251117A1 PCT/US2022/030546 US2022030546W WO2022251117A1 WO 2022251117 A1 WO2022251117 A1 WO 2022251117A1 US 2022030546 W US2022030546 W US 2022030546W WO 2022251117 A1 WO2022251117 A1 WO 2022251117A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- twt
- bit
- broadcast
- sta
- parameter set
- Prior art date
Links
- 230000011664 signaling Effects 0.000 claims abstract description 61
- 230000005540 biological transmission Effects 0.000 claims abstract description 46
- 238000000034 method Methods 0.000 claims description 101
- 238000004891 communication Methods 0.000 claims description 65
- 101100172132 Mus musculus Eif3a gene Proteins 0.000 claims description 17
- 230000004044 response Effects 0.000 claims description 16
- 230000007246 mechanism Effects 0.000 claims description 11
- 238000010586 diagram Methods 0.000 description 27
- 230000006870 function Effects 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 10
- 230000008901 benefit Effects 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 101150081243 STA1 gene Proteins 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 101100161473 Arabidopsis thaliana ABCB25 gene Proteins 0.000 description 5
- 101100096893 Mus musculus Sult2a1 gene Proteins 0.000 description 5
- OVGWMUWIRHGGJP-WVDJAODQSA-N (z)-7-[(1s,3r,4r,5s)-3-[(e,3r)-3-hydroxyoct-1-enyl]-6-thiabicyclo[3.1.1]heptan-4-yl]hept-5-enoic acid Chemical compound OC(=O)CCC\C=C/C[C@@H]1[C@@H](/C=C/[C@H](O)CCCCC)C[C@@H]2S[C@H]1C2 OVGWMUWIRHGGJP-WVDJAODQSA-N 0.000 description 4
- 101000988961 Escherichia coli Heat-stable enterotoxin A2 Proteins 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 229920000491 Polyphenylsulfone Polymers 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 229940102240 option 2 Drugs 0.000 description 2
- 235000010443 alginic acid Nutrition 0.000 description 1
- 229920000615 alginic acid Polymers 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000004622 sleep time Effects 0.000 description 1
- 230000003595 spectral effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
- H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
-
- 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]
- H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
-
- 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 technology of this disclosure pertains generally to use of Target Wake Time (TWT) on WLAN stations, and more particularly to setting a Reserved TWT mode and its various parameters for enhanced TWT use.
- TWT Target Wake Time
- TWT Target Wake Time
- access points can increase device sleep time toward conserving battery life. This aspect is especially beneficial in roles such as Internet-of-Things (loT).
- LoT Internet-of-Things
- TWT also provides a mechanism by which wireless access points and similar devices negotiate specific times to access the medium, which aids spectral efficiency.
- TWT is primarily directed at power savings and does not specifically address real time latency reductions.
- R-TWT Restricted Target Wait Time
- R-TWT Service Period SP
- parameters to indicate whether R-TWT SP can be extended parameters to indicate whether multiple overlapped R-TWT SPs on different links can be started; parameters to indicate whether spatial reuse is required during R-TWT SP; parameters to indicate whether to use Quiet element to protect R-TWT SP.
- the disclosed technologies describe use of reserved bits in the Broadcast TWT parameter set field to establish R-TWT parameter setting. For example, using reserved bits 5 through 7 of the Broadcast TWT Recommendation subfield and bit 15 (B15) in the Request type field of a broadcast TWT parameter set field for R-TWT parameter setting.
- B15 bit 15
- several of these additional parameters are described for enhancing R-TWT signaling.
- the present disclosure is applicable to Wireless Local Area
- WLANs Wireless Local Area Networks
- 802.11 802.11 ax
- RTA Real-Time Application
- MLD Multi-Link Device
- FIG. 1 is a hardware block diagram of wireless station (STA) hardware according to at least one embodiment of the present disclosure.
- FIG. 2 is a hardware block diagram of a station configuration, such as contained in Multi-Link Device (MLD) hardware, according to at least one embodiment of the present disclosure.
- MLD Multi-Link Device
- FIG. 3 is a data field diagram of a Broadcast TWT Parameter Set field which is utilized according to at least one embodiment of the present disclosure.
- FIG. 4 is a data field diagram of a Broadcast TWT Information subfield which is utilized according to at least one embodiment of the present disclosure.
- FIG. 5 is a data field diagram of a Request Type subfield from the broadcast TWT parameter set field as utilized according to at least one embodiment of the present disclosure.
- FIG. 6 is a flow diagram of selecting options in which each reserved bit represents an R-TWT setting according to at least one embodiment of the present disclosure.
- FIG. 7 is a flow diagram of identifying if the received Broadcast TWT Parameter Set field indicates use of a first R-TWT signaling option according to at least one embodiment of the present disclosure.
- FIG. 8 is a flow diagram of identifying if the received Broadcast TWT Parameter Set field indicates use of a second R-TWT signaling option according to at least one embodiment of the present disclosure.
- FIG. 9 is a data field diagram of a Request Type subfield in a Broadcast TWT Recommendation field using a first R-TWT signaling option according to at least one embodiment of the present disclosure.
- FIG. 10 is a data field diagram of using a reserved bit in the
- FIG. 11 is a data field diagram of setting All SCS (Stream
- Classification Service for not allowed as utilized according to at least one embodiment of the present disclosure.
- FIG. 12 is a data field diagram of indicating that the Link ID Bitmap is Present as utilized according to at least one embodiment of the present disclosure.
- FIG. 13 is a flow diagram of performing overlapped R-TWT SPs on multiple links according to at least one embodiment of the present disclosure.
- FIG. 14 is a communication diagram of a first example of overlapped R-TWT on multiple links (ML) utilized according to at least one embodiment of the present disclosure.
- FIG. 15 is a communication diagram of a second example of overlapped R-TWT on ML utilized according to at least one embodiment of the present disclosure.
- FIG. 16 is a communication diagram of a third example of overlapped R-TWT on ML utilized according to at least one embodiment of the present disclosure.
- FIG. 17 is a communication diagram of a fourth example of overlapped R-TWT on ML utilized according to at least one embodiment of the present disclosure.
- FIG. 18 is a communication diagram of an example of extending R- TWT SP according to at least one embodiment of the present disclosure.
- FIG. 19 is a communication diagram of an example in which R-TWT extension is not allowed according to at least one embodiment of the present disclosure.
- FIG. 20 is a communication diagram of setting Parameterized Spatial Reuse Reception (PSRR) to allow Parameterized Spatial Reuse (PSR), according to at least one embodiment of the present disclosure.
- PSRR Parameterized Spatial Reuse Reception
- PSR Parameterized Spatial Reuse
- FIG. 21 is a communication diagram of a first example of using quiet element according to at least one embodiment of the present disclosure.
- FIG. 22 is a communication diagram of a second example of using quiet element according to at least one embodiment of the present disclosure.
- Broadcast TWT (B-TWT) signaling as defined in IEEE 802.11 ax can also be adapted to support Restricted TWT (R-TWT) signaling.
- R-TWT Restricted TWT
- One specific value (e.g., 4) of the Broadcast TWT Recommendation subfield of the Broadcast TWT Parameter Set field can be utilized to indicate the signaling is for R-TWT as defined in Draft P802.11be D1.31.
- B-TWT allows an AP, such as the TWT scheduling AP, to schedule a TWT Service Period (SP) to exchange frames with other stations (STAs) which are TWT scheduled STAs (or the members of the TWT).
- SP Service Period
- STAs stations which are TWT scheduled STAs (or the members of the TWT).
- An individual STA may have membership in broadcast TWT as the result of negotiation with the scheduling AP.
- a TWT scheduled STA should not transmit frames to the TWT scheduling AP outside of broadcast TWT SPs and should not transmit frames that are not contained within High-Efficiency (HE) Trigger-Based (TB) PPDUs to the TWT scheduling AP within trigger- enabled broadcast TWT SPs, except that the STA can transmit frames within negotiated individual TWT SPs as defined in 26.8.2 (e.g., Individual TWT agreements)” as per Draft P802.11ax_D8.0.
- HE High-Efficiency
- TB Trigger-Based
- the R-TWT SP can be scheduled and informed in the same manner as B-TWT SP. If the signaling is for R-TWT, then the TWT SP in the signaling is scheduled for R-TWT. Otherwise, the TWT SP in the signaling is scheduled for B-TWT.
- R-TWT can be implemented in a variety of 802.11 hardware configurations, the following being provided by way of example and not limitation.
- FIG. 1 illustrates an example embodiment 10 of STA hardware configured for executing the protocol of the present disclosure.
- An external I/O connection 14 preferably couples to an internal bus 16 of circuitry 12 upon which are connected a CPU 18 and memory (e.g., RAM) 20 for executing a program(s) which implement the communication protocol.
- the host machine accommodates at least one modem 22 to support communications coupled to at least one RF module 24, 28 each connected to one or multiple antennas 29, 26a, 26b, 26c through 26n.
- An RF module with multiple antennas allows for performing beamforming during transmission and reception. In this way, the STA can transmit signals using multiple sets of beam patterns.
- Bus 14 allows connecting various devices to the CPU, such as to sensors, actuators and so forth.
- Instructions from memory 20 are executed on processor 18 to execute a program which implements the communications protocol, which is executed to allow the STA to perform the functions of an access point (AP) station or a regular station (non-AP STA).
- AP access point
- non-AP STA non-AP STA
- the programming is configured to operate in different modes (TXOP holder, TXOP share participant, source, intermediate, destination, first AP, other AP, stations associated with the first AP, stations associated with other AP, coordinator, coordinatee, AP in an OBSS, STA in an OBSS, and so forth), depending on what role it is performing in the current communication context.
- the STA HW is shown configured with at least one modem, and associated RF circuitry for providing communication on at least one band.
- the present disclosure is primarily directed at the sub 6 GHz band.
- the present disclosure can be configured with multiple modems 22, with each modem coupled to an arbitrary number of RF circuits. In general, using a larger number of RF circuits will result in broader coverage of the antenna beam direction. It should be appreciated that the number of RF circuits and number of antennas being utilized is determined by hardware constraints of a specific device. A portion of the RF circuitry and antennas may be disabled when the STA determines it is unnecessary to communicate with neighboring STAs.
- the RF circuitry includes frequency converter, array antenna controller, and so forth, and is connected to multiple antennas which are controlled to perform beamforming for transmission and reception. In this way the STA can transmit signals using multiple sets of beam patterns, each beam pattern direction being considered as an antenna sector.
- MLD multi-link device
- FIG. 2 illustrates an example embodiment 40 of a Multi-Link Device (MLD) hardware configuration.
- MLD Multi-Link Device
- Multiple STAs are affiliated with an MLD, with each STA operating on a link of a different frequency.
- the MLD has external I/O access to applications, this access connects to a MLD management entity 48 having a CPU 62 and memory (e.g., RAM) 64 to allow executing a program(s) that implement communication protocols at the MLD level.
- the MLD can distribute tasks to, and collect information from, each affiliated station to which it is connected, exemplified here as STA 1 42, STA 244 through to STA N 46 and the sharing of information between affiliated STAs.
- each STA of the MLD has its own CPU 50 and memory (RAM) 52, which are coupled through a bus 58 to at least one modem 54 which is connected to at least one RF circuit 56 which has one or more antennas.
- the RF circuit has multiple antennas 60a, 60b, 60c through 60n, such as in an antenna array.
- the modem in combination with the RF circuit and associated antenna(s) transmits/receives data frames with neighboring STAs.
- the RF module includes frequency converter, array antenna controller, and other circuits for interfacing with its antennas.
- each STA of the MLD does not necessarily require its own processor and memory, as the STAs may share resources with one another and/or with the MLD management entity, depending on the specific MLD implementation. It should be appreciated that the above MLD diagram is given by way of example and not limitation, whereas the present disclosure can operate with a wide range of MLD implementations.
- FIG. 3 illustrates an example embodiment 110 of a Broadcast TWT
- the fields are shown as Request Type, Target Wake Time, Nominal Minimum TWT Wake Duration, TWT Wake Interval Mantissa and Broadcast TWT Information as described in IEEE 802.11 ax (Draft P802.11ax_D8.0).
- FIG. 4 illustrates an example embodiment 130 of a Broadcast TWT Information (Info) subfield.
- the fields are shown as Reserved, Broadcast TWT ID (identification), and Broadcast TWT Persistence.
- FIG. 5 illustrates an example embodiment 150 of a Request Type field in a broadcast TWT parameter set field.
- the fields are shown as TWT Request, TWT Setup Command, Trigger, Last Broadcast Parameter Set, Flow Type, Broadcast TWT Recommendation, TWT Wake Interval Exponent, and a Reserved field.
- the Broadcast TWT Recommendation subfield provides an indication for R-TWT.
- the traffic flow could be identified by SCS ID, Traffic Identifier (TID), Real-Time Application (RTA) ID, or User Priority (UP).
- RTA ID can be an ID that represents one or more low latency traffic streams
- R-TWT signaling frames carry TSPEC elements to specify that only the traffic under the Traffic Specification (TSPEC) element during the R-TWT signaling can be transmitted during R-TWT SPs.
- TSPEC Traffic Specification
- SCS Stream Classification Service
- a R-TWT SP is not started at its scheduled start time. If a R-TWT SP is started late, the R-TWT SP may be extended after its scheduled end time.
- this parameter can require the scheduling AP of the R-TWT to use Parameterized Spatial Reuse Transmission (PSRT) or Parameterized Spatial Reuse Reception (PSRR) Physical Layer
- PLCP Protocol Convergence Procedure
- PPDU Protocol Data Unit
- the scheduling AP can schedule quiet intervals to prevent channel contention from the STAs which are not members of the R-TWT SP. Those STAs can enter quiet mode during the R-TWT SP after receiving a quiet element command from the scheduling AP.
- bits B0 ⁇ B2 are reserved.
- FIG. 6 illustrates an example embodiment 170 of options in which each reserved bit represents an R-TWT setting. It will be noted that the definition of each reserved bit for R-TWT signaling is predetermined in the protocol. In this flow diagram the protocol should choose either optionl or option2.
- This flowchart describes a STA can set the parameters in the broadcast TWT Parameter Set field for R-TWT signaling.
- the STA may be a TWT scheduling AP or an individual STA.
- the flow diagram depicts the STA reusing 172 the
- the STA sets 176 the most significant bit of the Broadcast TWT Recommendation subfield to a first state (e.g., "1") to indicate that the signaling is for R-TWT, as well as the other bits for R-TWT parameter setting. Then at block 180 the STA uses other reserved bits in the Broadcast TWT Parameters set field for R- TWT parameter setting.
- a first state e.g., "1”
- the STA sets 178 the Broadcast TWT Recommendation subfield to a value greater than or equal to 4, to indicate the signaling is for a different type of R-TWT, after which execution reaches block 180 as previously described.
- FIG. 7 illustrates an example embodiment 190 describing a STA identifying whether the received Broadcast TWT Parameter Set field indicates R-TWT signaling when Optionl from FIG. 6 is used. It should be appreciated that the STA could be a TWT scheduling AP or an individual STA.
- Broadcast TWT Parameter Set field after which a check 194 is made to determine if the most significant bit of the Broadcast TWT Recommendation subfield is set to the first state (e.g., "1").
- block 200 is reached for a Broadcast TWT Parameter set field in B-TWT signaling.
- FIG. 8 illustrates an example embodiment 210 describing a STA identifying whether the received Broadcast TWT Parameter Set field indicates R-TWT signaling when Option 2 from FIG. 6 is used.
- This flowchart explains how the STA identifies whether the received broadcast TWT Parameter Set field is for R-TWT signaling when Option 2 from FIG. 6 is used. It will be appreciated that the STA can be a TWT scheduling AP or an individual STA.
- the flow diagram depicts a STA receiving 212 a
- Broadcast TWT Parameter Set field with a check 214 being made on the Broadcast TWT Recommendation subfield to determine if its value is equal to or greater than a set value, which is "4" in providing compatibility with existing subfield values. If the value is not equal to or greater than this set value, then it has been determined 220 that B-TWT signaling is to be performed.
- FIG. 9 illustrates an example embodiment 230 of the Request Type field in a Broadcast TWT Recommendation subfield showing an Option 1 example in which each reserved bit represents an R-TWT set.
- the request type field in a Broadcast TWT parameter set field only contains B7 to B15.
- the extra bits can be added in the request type field or any places in the Broadcast TWT parameter set field for the R-TWT parameter setting. It should be noted that the position of each bit parameter can be changed.
- the R-TWT indication subfield is at bit 9 (B9) of the Request Type field (or the most significant bit) in a broadcast TWT parameter set field.
- the R-TWT indication provides one bit indication for indicating whether the signaling is for R-TWT or B-TWT. For example, when set to a first state (e.g., ⁇ ”), this indicates that the signaling is for R-TWT instead of a B-TWT. Accordingly, the TWT SP in the signaling would be scheduled for R-TWT SP. Otherwise, the value of the broadcast TWT recommendation field is from 0 to 3 which is for broadcast TWT signaling and the TWT SP in the signaling is scheduled for B-TWT SP.
- a first state e.g., ⁇
- each bit can be used to set the parameter set for R-TWT if the signaling is for R-TWT. It is possible that each option bit can be set by the scheduling AP only, and other STAs have to follow the set by the scheduling AP when they send the broadcast TWT parameter set for the same R-TWT.
- each option bit can be negotiated between the scheduling AP only and the STA requesting membership of the R-TWT. After negotiation, the scheduling AP broadcasts this option bit setting to other members or this option bit is reserved when the scheduling AP broadcast it.
- the Overlapped R-TWT on ML field in FIG. 9 is set when a STA requests membership of the R-TWT, but is otherwise reserved (not used) when the scheduling AP broadcasts the Broadcast TWT parameter set. If this option bit is reserved when the scheduling AP broadcasts it, then this bit option only takes effect between the scheduling AP and the R-TWT member STA (or scheduled STA) which negotiates this option. If this option bit is set when the scheduling AP broadcasts it, then this bit option also takes effect for all the member STAs of the corresponding R-TWT.
- each option below may represent a default operation of the R-TWT even if it is not a parameter set in broadcast TWT parameter set field.
- the extend R-TWT SP field may not be a parameter set in broadcast TWT parameter set field because R-TWT SP is always allowed to extend by default.
- each option below can be any bit(s) in the broadcast TWT parameter set field (including the extra bits added to the broadcast TWT parameter set field for R-TWT parameter setting).
- this one bit indicates whether a quiet interval will be scheduled to protect the R-TWT SP.
- This subfield is set to a first state (e.g., ⁇ ”) to indicate that the scheduling AP will use quiet element to schedule the quiet interval to protect R-TWT SP.
- the STAs or member STAs of the R-TWT SP only) which receive this bit can ignore the quiet interval that is scheduled during the R-TWT SP. Otherwise, this subfield is set to a second state (e.g., “0”) and there is no quiet interval scheduled to protect R-TWT SP.
- All SCS (or All Traffic Stream (TS): this one bit indicates whether it is allowed for the traffic belonging to all the SCSs (or TSs) to transmit during the R-TWT SP. This field is set to a first state (e.g., “1”) if it is allowed, or a second state (e.g., “0”) it is not allowed and only the traffic belonging to the specified SCS (or TS) can be transmitted during the R- TWT SP.
- the SCS (or TS) setup information (such as SCSID, TID, TSPEC element or QoS Characteristic element) can be included in the TWT signaling frames, such as TWT request/response frame.
- this subfield may constitute a one bit indication. If this bit is set to a first state (e.g., “1”), then the R-TWT SP can be extended by the members (or the scheduling AP only) of the R-TWT; for example, if its R-TWT SP does not start as scheduled, or if the members of the R-TWT could not access the channel at the scheduled start time of R- TWT SP.
- a first state e.g., “1”
- the scheduling AP or the member STA may reserve a TXOP during R-TWT SP that exceeds the original scheduled R- TWT SP end time.
- the extended R-TWT SP time is constrained so that it is not longer than the Transmit Opportunity (TXOP) limit.
- TXOP time obtained by a R-TWT member (including the scheduling AP) during the R-TWT SP is constrained so that it is not longer than the scheduled R-TWT SP time.
- the R-TWT can be trigger-based, wherein only the AP can extend the R-TWT SP.
- this bit is set to a second state (e.g., “0”) and the R-TWT SP cannot be extended.
- R-TWT SP has to end at the scheduled end time, and the TXOP reserved by the R-TWT member (including the scheduling AP) during the R-TWT SP cannot exceed the original scheduled end time of the R-TWT SP.
- the extent of the R-TWT SP subfield for the current R-TWT SP should be set to a second state (e.g.,
- the scheduling AP makes the decision of setting this subfield.
- the R-TWT SP can be extended only for DL transmissions of any member STAs of the R-TWT SP and/or UL/P2P transmissions of the member STAs of the R-TWT SP that do not contend the channel outside the R-TWT SPs.
- this subfield can be implemented with a one-bit indication. If this bit is set to a first state (e.g., “1”), then the member of the R-TWT will wake-up and sleep according to the broadcast TWT. For example, the member STA of the R-TWT wakes up during the R- TWT SP and falls asleep outside the R-TWT SP. Otherwise, this bit is set to second state (e.g., “0”) and the member STA of the R-TWT always remains awake. Then, the scheduling AP can transmit DL transmissions (and/or trigger UL/P2P transmissions) to the member STA outside the R- TWT SP. It should be noted that the R-TWT SP is scheduled and informed the same as B-TWT SP.
- a first state e.g., “1”
- the member of the R-TWT will wake-up and sleep according to the broadcast TWT. For example, the member STA of the R-TWT wakes up during
- this one bit indication can be set to indicate whether the scheduling AP MLD and the same R-TWT MLD members are allowed to start multiple overlapped R-TWT SPs on different links. If this bit is set to a first state (e.g., “1”), then the AP and the R-TWT members are allowed to start multiple R-TWT SPs on different links. In at least one embodiment quiet intervals may not be allowed to be used, thus protecting the R-TWT SP.
- this bit is set to a second state (e.g., “0”) and the AP and the R-TWT members could only start one R-TWT SP on a link even if there are multiple overlapped R-TWT SPs scheduled on the different links.
- this one bit indication can be used to indicate whether the
- PSRR PPDU has to send a PSRR PPDU to trigger a UL transmission. If this bit is set to a first state (e.g., “1”), then the AP is configured to send PSRR PPDU to trigger UL transmissions (PSRT PPDU) during the R-TWT SP. That is, the AP cannot set the spatial reuse field in the UpLink (UL) spatial reuse subfield in the common information field of the trigger frame (PSRR PPDU) to PSR_DISALLOW or PSR_AND_NON-SRG_OBSS_PD_PROHIBITED to disallow OBSS STAs from performing Parameterized Spatial Reuse (PSR)- based SR transmission.
- UL UpLink
- PSR_DISALLOW PSR_AND_NON-SRG_OBSS_PD_PROHIBITED
- the value of spatial reuse of the solicited TB PPSU should follows the PSRR PPDU.
- OBSS Overlapping Basic Service Set
- SRP Spatial Reuse Parameters
- this bit is set to a second state (e.g., “0”) and the AP does not send PSRR PPDU when triggering UL transmissions.
- the AP broadcasts this option, the OBSS STAs receiving this option can access the channel during a Parameterized Spatial Reuse (PSR) opportunity, and the intra-Basic Service Set (BSS) STA may not request membership of the R- TWT if it does not support PSR-based SR. It is also possible that the intra- BSS STA can request to change this option when it requests membership.
- PSR Parameterized Spatial Reuse
- BSS intra-Basic Service Set
- this one bit indication can be used to indicate whether spatial reuse is allowed during the R-TWT SP.
- this bit is set to a first state (e.g., “1”), then the AP and the members of the R-TWT may (or must) perform spatial reuse operation, such as OBSS Preamble Detect(PD)-based spatial reuse and PSR-based spatial reuse as defined in IEEE 802.11 ax, during the R-TWT SP.
- the spatial reuse operation during the R-TWT SP can be the same as outside the R-TWT SP.
- this bit is set to a second state (e.g., “0”), and the scheduling AP and the members of the R-TWT are not allowed to perform spatial reuse operation during the R-TWT SP.
- a second state e.g., “0”
- the OBSS STAs receiving this option can access the channel during a Spatial Reuse (SR) opportunity, and the intra-BSS STA may not request the membership of the R-TWT if it does not support SR.
- the intra-BSS STA can also request to change this option when it requests membership.
- SR Spatial Reuse
- TWT protection this bit is similar to the TWT protection request type field in the Individual TWT parameter set field.
- this one bit indication is set to indicate whether traffic belonging to all the TIDs is allowed to be transmitted during the R-TWT SP.
- This field is set to a first state (e.g., ⁇ ”) if the traffic (maybe low latency traffic only) belonging to all the TIDs is allowed to be transmitted during the R-TWT SP, and STAs which are members of the R-TWT can transmit the traffic (maybe low latency traffic only) belonging to all the TIDs to transmit during the R-TWT SP.
- this subfield is set to a second state (e.g., ”0”) and only the traffic (maybe low latency traffic only) belonging to the specified TID can be transmitted during the R-TWT SP.
- the traffic information can be included in the TWT signaling frames, such as TWT request/respond frame.
- this one bit indication can be used to indicate whether there is a Link ID Bitmap field in the Broadcast TWT parameter set field. If this bit is set to a first state (e.g., “1”), then the R- TWT signaling is for multi-link R-TWT and the Link ID Bitmap field is present in the Broadcast TWT parameter set field. The R-TWT SPs should be scheduled on the links that are indicated in the Link ID Bitmap field. Otherwise, this bit is set to a second state (e.g., “0”) and the Link ID Bitmap field is not present in the Broadcast TWT parameter set field. The R-TWT signaling is only for the link that the signaling is transmitted over.
- a first state e.g., “1”
- Transmission allowance outside R-TWT this field is set to a first state (e.g., ”1”) to indicate that the member STA of the R-TWT is allowed to contend for channel access (i.e. , transmit frames) outside of the R-TWT SP.
- this bit (set to ⁇ ”) could also represent that the individual STA which applies for R-TWT membership needs to (or will) transmit (and/or receive) frames outside the SPs of the R- TWT.
- this bit (set to “1”) could also indicate that the R-TWT scheduling AP may/will schedule UL (and/or DL and/or P2P) transmission for the member STA of the R-TWT. Otherwise, this bit is set to a second state (e.g., “0”) to indicate that the member STA of the R-TWT is not allowed to (or should not) contend for channel access (maybe also transmit and receive) outside the R-TWT SP. In a TWT request frame, this bit (set to “0”) could also represent that the individual STA which applies for the membership of the R-TWT will not transmit (and/or receive) frames outside the SPs of the R-TWT. In a TWT response frame, this bit (set to “0”) could also indicate that the R-TWT scheduling AP will not schedule UL (and/or DL and/or P2P) transmission for the member STA of the R-TWT.
- the R-TWT scheduling AP only schedules (or trigger) UL (and/or DL and/or P2P) transmission for the individual STA within the scheduled R-TWT SPs. For example, if the R-TWT SP is extended after the scheduled end time, the R-TWT scheduling AP will not schedule UL (and/or DL and/or P2P) transmission for the individual STA.
- the R-TWT SP will not be extended for the UL (and/or DL and/or P2P) transmission for the individual STA as a member of the R-TWT SP. It is possible that when the individual STA sets this bit in a TWT request frame to indicate that it will not transmit (and/or receive) frames outside the SPs of the R-TWT and the TWT request is accepted, the R-TWT scheduling AP may extend the R-TWT SP for the UL (and/or DL and/or P2P) transmission for the individual STA as a member of the R-TWT SP.
- the figure depicts an example of using B7 for the All SCS subfield, B8 for Quiet element protection subfield, and B15 for the overlapped R- TWT on ML subfield. It will be noted that each reserved bit can be used for any R-TWT parameter set option. For example, ALL SCS subfield in B7 could be replaced by all TID subfield. It will be noted that the request type field in a broadcast TWT parameter set field for R-TWT can be added with extra bits if it is for R-TWT signaling.
- PSRR field, SR enable field, TWT protection field, All TID field, LinkID Bitmap Present field, Transmission allowance outside R-TWT field are in extra bits for R-TWT parameter setting as shown in the figure. It should also be appreciated that those extra bits can be anyplace in the Broadcast TWT parameter set field for the R-TWT parameter setting.
- FIG. 10 illustrates an example embodiment 250 of using a reserved bit in the Broadcast TWT Info field.
- the reserved bits B0 through B2 in the Broadcast TWT Information field can be used for R-TWT information, as shown in the example. It should be noted that the reserved bits can be used for any fields as shown in FIG. 9.
- this one bit indication is set to indicate whether the traffic belonging to all the SCSs is allowed to transmit during R-TWT SP.
- This field is set to a first state (e.g., ⁇ ”) to allow the traffic belonging to all the SCSs to transmit during the R-TWT SP, and STAs which are members of the R-TWT can transmit the traffic belonging to all the SCSs to transmit during the R-TWT SP. Otherwise, this subfield is set to a second state (e.g., ”0”) and only the traffic belonging to the specified SCS can be transmitted during the R-TWT SP.
- the SCS setup information (e.g., SCS ID field, TSPEC element (or QoS Characteristic element), TCLAS element, Traffic Classification (TCLAS) Processing element, Intra-Access Category Priority Element) can be included in the TWT signaling frames, such as TWT request/respond frame.
- the SCS setup information can be used to set up an SCS whose traffic is to be transmitted during the R-TWT SP. In this example, if the All SCS field is set to a second state (e.g., “0”), then the traffic from the SCS indicated in the SCS ID field can be transmitted during the R-TWT SP.
- Broadcast TWT ID represents the R-TWT ID. It will be noted that a scheduling AP or STA should not set a same ID to a R-TWT and a broadcast TWT at the same time. In this way, an AP or STA can differentiate a broadcast TWT from a R-TWT by their IDs.
- An AC subfield can be carried by any other two reserved bits in the Broadcast TWT parameter set field.
- FIG. 11 illustrates an example embodiment 290 of setting All SCS for not allowed (e.g., "0").
- the upper portion of the figure depicts the Broadcast TWT information field, while the lower portion of the figure depicts the Broadcast TWT Parameter Set Field.
- the traffic information i.e. , per traffic stream
- TWT signaling frames such as TWT setup (request/response) frame.
- the All SCS fields can be replaced by any field which can indicate the presence of traffic information.
- the SCS ID, TID and TSPEC field (or QoS Characteristics element) can be present by default, for example when it is sent by a non-AP STA to request membership of an R-TWT.
- the traffic information can be included at any place within TWT signaling frames, such as in a TWT setup (request/response) frame.
- the traffic information When the traffic information is present in a broadcast TWT parameter set field of a broadcast TWT setup frame which is sent by a non- AP STA to request a membership of a R-TWT, the traffic information specifies the traffic belonging to the traffic streams (between the non-AP STA and the scheduling AP) indicated in the traffic information needs to be transmitted during the R-TWT SPs.
- the scheduling AP receives this information, it can decide whether to accept the membership request or not to accept it, as based on that information. Below are two examples in which the scheduling AP does not accept the membership request due what is found in the traffic information.
- the membership request is not accepted if the total time that will be required to transmit the traffic of all the traffic streams indicated in the broadcast TWT parameter set field exceeds the amount of time that can be scheduled for the R-TWT SP. For example, the sum of the medium time in the TSPEC elements of all the traffic streams indicated in the broadcast TWT parameter set field is longer than the scheduled R-TWT SPs allowed time per second.
- the membership request will not be accepted if the total time is required to transmit the traffic of all the traffic streams indicated in the broadcast TWT parameter set field exceeds the upper limit of the total time of all the R-TWT SPs that a scheduling AP could schedule (or a scheduling AP MLD could schedule on all links). It is possible that there exists an upper limit of the total time of all the R-TWT SPs that each scheduling AP could schedule (or a scheduling AP MLD could schedule on all links) in the network.
- the scheduling AP can reject the membership request.
- the traffic information can represent the traffic (transmitted between the non-AP STA and the scheduling AP) that is allowed to transmit during the scheduled R- TWT SPs while other traffic (transmitted between the non-AP STA and the scheduling AP) can be either not allowed to transmit or has lower priority (compared with the traffic indicated in the traffic information) to transmit during the R-TWT SPs.
- the traffic information When the traffic information is present in a broadcast TWT parameter set field of a broadcast TWT setup frame which is sent by a scheduling AP to respond to a membership request of a R-TWT and the TWT setup command field in a response frame is Alternate TWT or Dictate TWT, the traffic information could represent the traffic (transmitted between the non-AP STA and the scheduling AP) that is suggested to transmit during the R-TWT SPs. The non-AP STA can send another request frame with the suggested traffic information to request the membership of the R- TWT.
- this field is set to a first state (e.g., “1”) to indicate that there is more traffic information, such as SCSID, TSPEC and TID for another traffic stream. Otherwise, this bit is set to a second state (e.g., “0”).
- the traffic information can be used to identify traffic, such as in differentiating latency sensitive traffic, under SCS or TSPEC, from other traffic.
- a scheduling AP MLD is a MLD having multiple scheduling affiliated with different links. It is possible that one traffic stream, such as SCS, can be mapped to only one R-TWT of a scheduling AP MLD or could be mapped to only one R-TWT of a scheduling AP on one link. For example, one SCS can only be mapped to one R-TWT. That is, when the traffic of the SCS is allowed to transmit by a R-TWT during its R-TWT SP, other R-TWTs should not accept the request to transmit the traffic of that SCS during their R-TWT SPs.
- FIG. 12 illustrates an example embodiment 310 of indicating that the Link ID Bitmap is Present.
- the upper portion of the figure depicts request type field in a Broadcast TWT Parameter Set field for R-TWT, while the lower portion of the figure depicts the Broadcast TWT Parameter Set Field.
- Link ID Bitmap Present is set to a first state (e.g., "1") in the signaling, then the Link ID Bitmap is present in the Broadcast TWT parameter set field.
- B15 of Request type field in a broadcast TWT parameter set field for R-TWT is used to carry the Link ID Bitmap Present subfield.
- any reserved bit in the Broadcast TWT parameter set field can operate in the same manner as B15 of Request type field in a broadcast TWT parameter set field.
- Link ID Bitmap this field consists of a sequence of bits, with each bit presets or is mapped to a link. If a bit is set to a first state (e.g., “1”), then the R-TWT is set for the link with respect to that bit. Otherwise, the bit is set to a second state (e.g., “0”) and the R-TWT is not for the link with respect to that bit. It will be noted that this is one possible way to schedule overlapped R-TWT SPs on multiple links. It should also be noted that Link ID Bitmap Present subfield could also be used for the broadcast TWT setup on multiple links. It will be noted that more than one bit can be set to “1” in the Link ID Bitmap field.
- Recommendation field represents one R-TWT with default parameter set. [00131]
- each value between 4 and 7 can be set to represent one of the following R-TWT settings:
- TWT SP similar to value 0 to 3.
- the value 4 represents Basic R-TWT. It should be appreciated that the values may be mapped in any desired sequence without departing from the teachings of the present disclosure.
- FIG. 13 illustrates an example embodiment 330 of performing overlapped R-TWT SPs on multiple links.
- the overlapped R-TWT on different links are the R-TWT managed by a scheduling AP MLD and their R-TWT SPs on the different links are scheduled over the same periods of time. It will be noted that the overlapped R-TWT may only represent those serving the same TIDs or the same SCSs or the traffic streams or the same MLD members.
- the operation depicts multiple overlapped R-TWT SPs on different links being scheduled 332 over the same periods of time for the same R-TWT members.
- a check 334 determines if overlapped R-TWT on multiple links is allowed. By way of example, this can involve checking to see if the ML subfield is set to a first state (e.g., ⁇ ”) indicating that overlapped R-TWT on ML is allowed, while if overlapped R-TWT on ML subfield is set to a second state (e.g., “0”), then overlapped R-TWT on ML is not allowed.
- a first state e.g., ⁇
- a second state e.g., “0”
- FIG. 14 illustrates an example embodiment 350 of a first example of
- the figure depicts an MLD 352 with AP1 354 and AP2356.
- R-TWT SP1 358 and SP2360 There are multiple overlapped R-TWT SPs, such as for R-TWT SP1 358 and SP2360, scheduled on different links, e.g., Iink1 and Iink2.
- the Overlapped R-TWT on ML field is set to 0 for the overlapped R-TWT SPs.
- MLD members start 364 a R-TWT SP2366 on Iink2.
- AP2 or the R-TWT SP2 member can send a frame to indicate the start of R-TWT SP2.
- This frame for example may be a Clear-to-Send (CTS) frame with special Recipient Address (RA) field which indicates the start of R-TWT SP2.
- CTS Clear-to-Send
- RA Recipient Address
- the RA field of the frame (e.g., CTS) can be set to a special ID to a link that can be mapped to the R-TWT ID and/or the STA ID and/or BSS ID.
- the RA field of the frame can be set to the address of AP2.
- Other stations nodes
- the figure depicts communications between an MLD 352 with its AP1 354 and AP2 356, and another MLD 396, which is not a member of the R-TWT, having associated stations STA1 398 and STA2400.
- R- TWT SP1 There are multiple overlapped R-TWT SPs, exemplified here as R- TWT SP1 372 and SP2374, scheduled on different links, depicted as linkl and Iink2.
- the Overlapped R-TWT on ML field is set to 0 for the overlapped R-TWT SPs.
- MLD members start 378 a R-TWT SP2380 on Iink2.
- AP2 or the R-TWT SP2 member can send a frame to indicate the start of R-TWT SP2.
- This frame could be a CTS frame with special RA which indicates the start of R-TWT SP2.
- the RA field of the frame (e.g., CTS) could be set to a special ID to link that can be mapped to the R-TWT ID and/or the STA ID and/or BSS ID. It is also possible that the RA field of the frame is set to the address of AP2.
- Other nodes can recognize the start of R-TWT SP2 scheduled by AP2.
- the AP affiliated with the same MLD of the R-TWT SP2 members on linkl may access 382 the channel on linkl for communicating 384 until the R-TWT SP on Iink2 ends for the following purposes only.
- the scheduling AP may access the channel to send a frame, such as a QoS Data or QoS Null frame that had the EOSP subfield equal to 1 , to indicate the end of R-TWT SP1 since it is canceled.
- the AP may access the channel to serve the R-TWT members whose MLDs are not R-TWT members on Iink2.
- the AP may access the channel to send a frame (e.g., CF-End) to indicate the end of the R-TWT SP or the end of the quiet time on linkl which is as depicted 384 in the figure.
- a frame e.g., CF-End
- the TA field of the frame e.g., CF-End
- the AP may access the channel to send DL traffic (or DL traffic that is not allowed to be transmitted during the R-TWT SP only) or trigger UL traffic (or UL traffic that is not allowed to be transmitted during the R-TWT SP only) to its associated STAs.
- the AP may access the channel to send control frames or management frames.
- the figure shows a PPDU 386 sent from AP1 to STA1 over linkl , followed by a Block Acknowledgement (BA) 388 from STA.
- BA Block Acknowledgement
- a Trigger Frame (TF) 390 is shown being sent from AP1 to STA1 in response to which is a Trigger Based (TB) PPDU 392 from STA1 to AP1 , and followed by a BA 394 from AP1.
- TB Trigger Based
- the R-TWT members may classify an event by indicating the end/termination of a R-TWT SP in the same manner as for B-TWT in IEEE 802.11 ax.
- the figure depicts an MLD 352 with AP1 354 and AP2356.
- R-TWT SP1 358 and SP2360 There are multiple overlapped R-TWT SPs, depicted for example as R-TWT SP1 358 and SP2360, scheduled for the same MLD members on different links, depicted as linkl and Iink2.
- the Overlapped R-TWT on ML field is set to 0 for the overlapped R-TWT SPs.
- MLD members start 364 a R-TWT SP2366 on Iink2.
- R-TWT SP2368 on Iink2 may end 370 earlier than it is scheduled.
- AP2 or the other R-TWT SP2 members send a frame, for example a Contention Free (CF)-End as in the previous example, to indicate the end of R-TWT SP2.
- CF-End Contention Free
- the AP affiliated with the same MLD of the R-TWT SP2 members on linkl may access the channel on linkl until the R-TWT SP on linkl (or Iink2) ends for the following purposes only.
- the AP may access the channel to serve the R-TWT members whose MLDs are not R-TWT members on Iink2.
- the AP may access the channel to send a frame (e.g., CF-End) to indicate the end of the R-TWT SP or the end of the quiet time on linkl .
- a frame e.g., CF-End
- the TA field of the frame (e.g., CF-End) can be set to a special ID to a link that can be mapped to the R-TWT ID and/or the STA ID and/or BSS ID.
- the AP may access the channel to send DownLink (DL) traffic (or DL traffic that is not allowed to be transmitted during the R-TWT SP only) or trigger UL traffic (or UL traffic that are not allowed to be transmitted during the R-TWT SP only) to its associated STAs.
- DL DownLink
- the AP may access the channel to send control frames or management frames.
- FIG. 17 illustrates an example embodiment 450 of a fourth example of overlapped R-TWT on ML.
- This example there is allowed a maximum of two overlapped R-TWT SPs on different links over the same periods of time.
- the figure depicts an MLD 452 with AP1 454, AP2456 and AP3458.
- R-TWT SP1 , 460, SP2462 and SP3464 scheduled.
- only a limited number overlapped R-TWT SPs are allowed to be started on different links.
- only a maximum of two overlapped R-TWT SPs can be started (or launched) during the same period of R-TWT SP time on different links.
- FIG. 18 illustrates an example embodiment 490 of extending R-TWT SP.
- the figure depicts an example of extending R-TWT SP, such as when the subfield Extend R-TWT SP is set to a first state (e.g., “1”), indicating that R-TWT SP is extended.
- AP or STAs are seen with scheduled R-TWT SP 494, which can be extended 500, by a time period Time 1 502.
- the AP or other R-TWT members may start 496 an R-TWT SP (e.g., the time of gaining channel access and obtaining TXOP) for a time period Time 2498 until R-TWT SP ends 504.
- the present disclosure can provide numerous options for R-TWT SP extensions.
- Time 1 should not be longer than a given fraction (e.g.,
- Option3 Time 2 should not be longer than the TXOP limit.
- Option4 Time 2 should not be longer than a given fraction (e.g.,
- Option5 Time 2 should not be longer than the scheduled R-TWT SP time.
- Option6 Time 1 should not exceed the next target beacon transmission time.
- the AP or STA that is a member of the R-TWT SP can extend the R-TWT SP when it obtains a TXOP during the scheduled R- TWT SP and the TXOP lasts beyond the end time of the scheduled R-TWT SP.
- the R-TWT SP is extended to the end time of the TXOP.
- AP or STA that is a member of the R-TWT SP can extend the R-TWT SP when it starts a PPDU transmission during the scheduled R- TWT SP and the PPDU duration and the solicited transmissions are beyond the end time of the scheduled R-TWT SP.
- the R-TWT SP is extended to the end time of that PPDU transmission and its solicited transmissions.
- the TXOP limit could be the TXOP limit of the AC which obtains the
- the TXOP limit can also be the TXOP limit of the AC of the highest priority TID whose traffic is scheduled to transmit during R-TWT SP.
- the TXOP limit can also be the maximum TXOP limit of the TIDs whose traffic is scheduled to transmit during R-TWT.
- the TXOP limit could be a value set for the R-TWT SP only.
- FIG. 19 illustrates an example embodiment 510 of when R-TWT extension is not allowed. This example shows a situation in which extending R-TWT SP is not allowed, for example when the subfield Extend R-TWT SP is set to a second state (e.g.,“0”) indicative of not allowing extension.
- a second state e.g.,“0”
- AP or STAs 512 are seen with scheduled R-TWT SP 514.
- AP2 or other R-TWT members access the channel 516 up to the maximum TXOP length 518.
- FIG. 20 illustrates an example embodiment 530 of setting PSRR to allow PSR, such as setting PSRR to a first state (e.g., "1").
- AP1 should always set parameters in PSRR PPDU to allow PSR.
- AP1 532 and AP2534 are shown with R-TWT SP on linkl 536, with AP1 accessing the channel to start 538 R-TWT SPT with a PSRR PPDU 540.
- the figure also exemplifies a TB PPDU 542 being received, during which AP2 sends a PSRT PPDU 544 for which a block acknowledgement 546 is shown.
- AP1 could not set the spatial reuse field in the UL spatial reuse subfield of the common info field of the trigger frame (PSRR PPDU) to PSR_DISALLOW or PSR_AND_NON-
- SRG_OBSS_PD_PROHIBITED to disallow OBSS STAs from performing PSR-based SR transmission.
- the value of spatial reuse of the solicited TB PPSU should follow the PSRR PPDU.
- a quiet element is utilized to schedule quiet time within the R-TWT SP to protect the R-TWT SP.
- the quiet interval should not exceed the R-TWT SP time.
- the end of this quiet time and the end time of the R-TWT SP should be aligned (and/or the start time of quiet time and the start time of the R-TWT SP should be aligned).
- a R-TWT SP member accesses the channel during the R-TWT SP for R-TWT purposes, it can send a frame (e.g., CF-End) to cancel the quiet time scheduled during the quiet time.
- a R-TWT SP can send a frame (e.g., CF-End) to cancel the quiet time scheduled during the current R-TWT SP.
- a frame e.g., CF-End
- FIG. 21 illustrates an example embodiment 550 of a first example of using a quiet element, in which the end time of the quiet interval and the end time of the R-TWT SP are aligned.
- the figure shows AP1 552 on linkl , STA1 554 as a member of R- TWT on linkl , and STA2556, which is not a member of R-TWT on linkl .
- R-TWT SP on linkl 558 is shown during which AP1 560 accesses the channel to start R-TWT SP on linkl .
- a scheduled quiet interval 562 is commenced on linkl , with STA2 entering 564 the quiet mode.
- the quiet time interval ends coinciding with the end of R-TWT SP 566 on linkl , upon which STA2 ends 568 its quiet mode.
- FIG. 22 illustrates an example embodiment 570 of a second example of using a quiet element. The figure shows the same stations as in the prior example.
- AP1 accesses 578 the channel to start R-TWT SP on linkl .
- the quiet time interval ends coinciding with the end of an R-TWT SP 580 on linkl , upon which STA2 ends 582 its quiet mode.
- Embodiments of the present technology may be described herein with reference to flowchart illustrations of methods and systems according to embodiments of the technology, and/or procedures, algorithms, steps, operations, formulae, or other computational depictions, which may also be implemented as computer program products.
- each block or step of a flowchart, and combinations of blocks (and/or steps) in a flowchart, as well as any procedure, algorithm, step, operation, formula, or computational depiction can be implemented by various means, such as hardware, firmware, and/or software including one or more computer program instructions embodied in computer-readable program code.
- any such computer program instructions may be executed by one or more computer processors, including without limitation a general purpose computer or special purpose computer, or other programmable processing apparatus to produce a machine, such that the computer program instructions which execute on the computer processor(s) or other programmable processing apparatus create means for implementing the function(s) specified.
- blocks of the flowcharts, and procedures, algorithms, steps, operations, formulae, or computational depictions described herein support combinations of means for performing the specified function(s), combinations of steps for performing the specified function(s), and computer program instructions, such as embodied in computer-readable program code logic means, for performing the specified function(s).
- each block of the flowchart illustrations, as well as any procedures, algorithms, steps, operations, formulae, or computational depictions and combinations thereof described herein can be implemented by special purpose hardware-based computer systems which perform the specified function(s) or step(s), or combinations of special purpose hardware and computer-readable program code.
- these computer program instructions may also be stored in one or more computer-readable memory or memory devices that can direct a computer processor or other programmable processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory or memory devices produce an article of manufacture including instruction means which implement the function specified in the block(s) of the flowchart(s).
- the computer program instructions may also be executed by a computer processor or other programmable processing apparatus to cause a series of operational steps to be performed on the computer processor or other programmable processing apparatus to produce a computer-implemented process such that the instructions which execute on the computer processor or other programmable processing apparatus provide steps for implementing the functions specified in the block(s) of the flowchart(s), procedure (s) algorithm(s), step(s), operation(s), formula(e), or computational depiction(s). [00200] It will further be appreciated that the terms "programming" or
- program executable refer to one or more instructions that can be executed by one or more computer processors to perform one or more functions as described herein.
- the instructions can be embodied in software, in firmware, or in a combination of software and firmware.
- the instructions can be stored local to the device in non-transitory media, or can be stored remotely such as on a server, or all or a portion of the instructions can be stored locally and remotely. Instructions stored remotely can be downloaded (pushed) to the device by user initiation, or automatically based on one or more factors.
- processor hardware processor, computer processor, central processing unit (CPU), and computer are used synonymously to denote a device capable of executing the instructions and communicating with input/output interfaces and/or peripheral devices, and that the terms processor, hardware processor, computer processor, CPU, and computer are intended to encompass single or multiple devices, single core and multicore devices, and variations thereof.
- An apparatus for wireless communication in a network comprising: (a) a wireless communication circuit, as a wireless station (STA) operating as either a regular STA or an Access Point (AP) STA for wirelessly communicating with other wireless stations (STAs) using a carrier sense multiple access/collision avoidance (CSMA/CA) mechanism on a wireless local area network (WLAN); (b) a processor coupled to said wireless communication circuit for operating on the WLAN; (c) a non- transitory memory storing instructions executable by the processor for communicating with other STAs; and (d) wherein said instructions, when executed by the processor, perform one or more steps of a wireless communications protocol for said wireless communication circuit, comprising: (d)(i) reusing broadcast target wake time (B-TWT) signaling as defined in IEEE 802.11 ax for establishing a restricted TWT (R-TWT); (d)(ii) indicating within said B-TWT, using a bit of a broadcast TWT parameter
- An apparatus for wireless communication in a network comprising: (a) a wireless communication circuit, as a wireless station (STA) operating as either a regular STA or an Access Point (AP) STA for wirelessly communicating with other wireless stations (STAs) using a carrier sense multiple access/collision avoidance (CSMA/CA) mechanism on a wireless local area network (WLAN); (b) a processor coupled to said wireless communication circuit for operating on the WLAN; (c) a non- transitory memory storing instructions executable by the processor for communicating with other STAs; and (d) wherein said instructions, when executed by the processor, perform one or more steps of a wireless communications protocol for said wireless communication circuit, comprising: (d)(i) reusing broadcast target wake time (B-TWT) signaling as defined in IEEE 802.11 ax for establishing a restricted TWT (R-TWT); (d)(ii) indicating within said B-TWT, using a bit of a broadcast TWT parameter
- (d)(iii) indicating additional settings to specify traffic flow for R-TWT in response to utilizing other bits in the broadcast TWT recommendation field which are reserved in IEEE 802.11 ax; and (d)(iv) wherein one or more of said traffic flow settings are selected from the group of traffic flow settings consisting of: (A) indicating whether a quiet element is used to protect R- TWT, (B) indicating whether the restricted TWT can be extended to beyond its scheduled end time if corresponding traffic has not been transmitted at the end of R-TWT SP, (C) indicating whether the AP is forced to use PSR- based spatial reuse during restricted TWT SP, (D) indicating whether the AP and R-TWT members can access multiple overlapped R-TWT SPs on different links over the same periods of time, (E) indicating whether traffic from all the SCS is allowed to transmit during R-TWT SP, (F) indicating whether the member of R-TWT need to wake-up and sleep in response to the
- a method of wireless communication in a network comprising: (a) communicating between a wireless station (STA) executing a wireless communications protocol and operating as either a regular STA or an Access Point (AP) STA for wirelessly communicating with other wireless stations (STAs) using a carrier sense multiple access/collision avoidance (CSMA/CA) mechanism on a wireless local area network (WLAN); (b) reusing broadcast target wake time (B-TWT) signaling as defined in IEEE 802.11 ax for establishing a restricted TWT (R-TWT); (c) indicating within said B-TWT, using a bit of a broadcast TWT parameter set field which is reserved in IEEE 802.11 ax, for indicating use of R-TWT; and (d) indicating additional settings to specify traffic flow for R-TWT in response to utilizing other bits in the broadcast TWT recommendation field which are reserved in IEEE 802.11 ax.
- STA wireless station
- AP Access Point
- B-TWT broadcast
- An apparatus for wireless communication in a network comprising: (a) a wireless communication circuit, as a wireless station (STA) operating as either a regular STA or an Access Point (AP) STA for wirelessly communicating packets with other wireless stations (STAs) using a carrier sense multiple access/collision avoidance (CSMA/CA) mechanism for use with a multi-link device (MLD) on a wireless local area network (WLAN); (b) a processor coupled to said wireless communication circuit for operating on the WLAN; (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs; and (d) wherein said instructions, when executed by the processor, perform one or more steps of a wireless communications protocol for said wireless communication circuit, comprising: (d)(i) scheduling multiple overlapped R-TWT SPs by the MLD; (d)(ii) starting a R- TWT SP on a link if the number of overlapped R-TWT SPs that have been started on other
- An apparatus for wireless communication in a network comprising: (a) a wireless communication circuit, as a wireless station (STA) operating as either a regular STA or an Access Point (AP) STA for wirelessly communicating with other wireless stations (STAs) using a carrier sense multiple access/collision avoidance (CSMA/CA) mechanism on a wireless local area network (WLAN); (b) a processor coupled to said wireless communication circuit for operating on the WLAN; (c) a non- transitory memory storing instructions executable by the processor for communicating with other STAs; and (d) wherein said instructions, when executed by the processor, perform one or more steps of a wireless communications protocol for said wireless communication circuit, comprising: (d)(i) setting up a R-TWT and scheduling quiet intervals whereby the R-TWT SP end time aligns to end times of the quiet intervals; (d)(ii) entering a quiet mode during the quiet interval by STAs that are not members of the R-TWT; and (d
- An apparatus for wireless communication in a network comprising: (a) a wireless communication circuit, as a wireless station (STA) operating as either a regular STA or an Access Point (AP) STA for wirelessly communicating with other wireless stations (STAs) using a carrier sense multiple access/collision avoidance (CSMA/CA) mechanism on a wireless local area network (WLAN); (b) a processor coupled to said wireless communication circuit for operating on the WLAN; (c) a non- transitory memory storing instructions executable by the processor for communicating with other STAs; and (d) wherein said instructions, when executed by the processor, perform one or more steps of a wireless communications protocol for said wireless communication circuit, comprising: (d)(i) sending a R-TWT membership request to an associated AP with specific traffic information that will be transmitted during R-TWT SPs; (d)(ii) wherein acceptance of said R-TWT membership request is determined by the associated AP based on the specific traffic information; and (d)(
- An apparatus for wireless communication in a network comprising: (a) a wireless communication circuit, as a wireless station (STA) operating as an Access Point (AP) STA for wirelessly communicating with other wireless stations (STAs) using a carrier sense multiple access/collision avoidance (CSMA/CA) mechanism on a wireless local area network (WLAN); (b) a processor coupled to said wireless communication circuit for operating on the WLAN; (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs; and (d) wherein said instructions, when executed by the processor, perform one or more steps of a wireless communications protocol for said wireless communication circuit, comprising: (d)(i) scheduling a start time of a R-TWT SP by the AP; (d)(ii) starting the R-TWT SP, by the AP and R-TWT members, as scheduled; and (d)(iii) extending the R-TWT SP be an extended time, by the AP
- a wireless communication apparatus performing transmission of packets, where CSMA/CA is applied in the system/apparatus, comprising: (a) STA reuses the broadcast TWT signaling as defined in IEEE 802.11 ax to set up restricted TWT; (b) STA indicates that the signaling is for restricted TWT in broadcast TWT recommendation field in a reserved bit of broadcast TWT parameter set field; and (c) STA indicates the additional setting of restricted TWT in broadcast TWT recommendation field.
- a wireless communication apparatus for performing transmission of packets, where CSMA/CA is applied in the system/apparatus comprising: (a) MLD schedules multiple overlapped R-TWT SPs; (b) an R-TWT SP on a link can be started if the number of overlapped R-TWT SPs that has been started on other links does not reach the maximum number (the overlapped R-TWT may only represent those serving the same TIDs or the same SCSs or the traffic streams); (c) the R-TWT SPs on some links are canceled if the maximum number of R-TWT SPs has been started on other links.
- a Wireless communication apparatus performing transmission of packets, where CSMA/CA is applied in the system/apparatus, comprising: (a) a STA sets up a R-TWT and schedules quiet intervals whereby the R- TWT SP end time algins to quiet interval end time; (b) the STAs that are not the members of the R-TWT enter quiet mode during the quiet interval; (c) the STAs that are the members of the R-TWT may not enter quiet mode during the quiet interval.
- a wireless communication apparatus performing transmission of packets, where CSMA/CA is applied in the system/apparatus, comprising: (a) a STA sends a R-TWT membership request to the AP with specific traffic information that will be transmitted during R-TWT SPs; (b) the AP decides whether to accept the R-TWT membership request based on the specific traffic information; (c) the AP uses the specific traffic information to differentiate traffic matching the specific traffic information from others.
- a wireless communication apparatus performing transmission of packets, where CSMA/CA is applied in the system/apparatus, comprising: (a) AP schedules a start time of a R-TWT SP; (b) AP and the R-TWT members try to start the R-TWT SP as scheduled; (c) AP and the R-TWT members extend the R-TWT SP if they are unable to start the R-TWT SP as scheduled.
- the STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field to indicate whether a quiet element is used to protect R-TWT; and wherein said quiet element is utilized to schedule quiet intervals to prevent channel contention from the STAs, which are not members of the R-TWT SP, enter a quiet mode during the R-TWT SP after receiving a quiet element command from the scheduling AP.
- PSR-based spatial reuse comprises Parameterized Spatial Reuse Transmission (PSRT) or Parameterized Spatial Reuse Reception (PSRR) Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) as defined IEEE 802.11 ax for spatial reuse.
- PSRT Parameterized Spatial Reuse Transmission
- PSRR Parameterized Spatial Reuse Reception
- PLCP Physical Layer Convergence Procedure
- PPDU Protocol Data Unit
- an option for multiple overlapped R-TWT SPs is selected from the group of options consisting of (a) allowing only one scheduled overlapped R-TWT SP to be started and the others cancelled; and (b) allowing multiple scheduled overlapped R-TWT SPs to be started.
- traffic information is selected from the group of traffic information consisting of traffic specification (TSPEC), stream classification service identification (SCSID) and traffic identifier (TID).
- TSPEC traffic specification
- SCSID stream classification service identification
- TID traffic identifier
- the apparatus or method of any preceding implementation wherein the AP or a STA that is a member of the R-TWT SP can extend the R-TWT SP when it obtains a TXOP during the scheduled R-TWT SP when the TXOP extends beyond an end time of the scheduled R-TWT SP; and wherein the R-TWT SP is extended to an end time of the TXOP.
- the apparatus or method of any preceding implementation, wherein the AP or a STA that is a member of the R-TWT SP can extend the R-TWT SP when it starts a PPDU transmission during scheduled R-TWT SP and the PPDU duration and the solicited transmissions are beyond an end time of the scheduled R-TWT SP.
- the apparatus or method of any preceding implementation where the AP or STA who is the member of the R-TWT SP can extend the R-TWT SP when it obtains a TXOP during the scheduled R-TWT SP and the TXOP lasts beyond the end time of the scheduled R-TWT SP.
- the R-TWT SP is extended to the end time of the TXOP.
- the apparatus or method of any preceding implementation where the AP or STA who is the member of the R-TWT SP could extend the R- TWT SP when it starts a PPDU transmission during the scheduled R-TWT SP and the PPDU duration and the solicited transmissions are beyond the end time of the scheduled R-TWT SP.
- the R-TWT SP is extended to the end time of that PPDU transmission and its solicited transmissions.
- Phrasing constructs such as “A, B and/or C”, within the present disclosure describe where either A, B, or C can be present, or any combination of items A, B and C.
- references in this disclosure referring to “an embodiment”, “at least one embodiment” or similar embodiment wording indicates that a particular feature, structure, or characteristic described in connection with a described embodiment is included in at least one embodiment of the present disclosure. Thus, these various embodiment phrases are not necessarily all referring to the same embodiment, or to a specific embodiment which differs from all the other embodiments being described.
- the embodiment phrasing should be construed to mean that the particular features, structures, or characteristics of a given embodiment may be combined in any suitable manner in one or more embodiments of the disclosed apparatus, system or method.
- a set refers to a collection of one or more objects.
- a set of objects can include a single object or multiple objects.
- Relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
- the terms can refer to instances in which the event or circumstance occurs precisely as well as instances in which the event or circumstance occurs to a close approximation.
- the terms can refer to a range of variation of less than or equal to ⁇ 10% of that numerical value, such as less than or equal to ⁇ 5%, less than or equal to ⁇ 4%, less than or equal to ⁇ 3%, less than or equal to ⁇ 2%, less than or equal to ⁇ 1 %, less than or equal to ⁇ 0.5%, less than or equal to ⁇ 0.1 %, or less than or equal to ⁇ 0.05%.
- substantially aligned can refer to a range of angular variation of less than or equal to ⁇ 10°, such as less than or equal to ⁇ 5°, less than or equal to ⁇ 4°, less than or equal to ⁇ 3°, less than or equal to ⁇ 2°, less than or equal to ⁇ 1 °, less than or equal to ⁇ 0.5°, less than or equal to ⁇ 0.1 °, or less than or equal to ⁇ 0.05°.
- Coupled as used herein is defined as connected, although not necessarily directly and not necessarily mechanically.
- a device or structure that is “configured” in a certain way is configured in at least that way, but may also be configured in ways that are not listed.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP22731017.4A EP4316019A1 (en) | 2021-05-25 | 2022-05-23 | Restricted target wait time (r-twt) operations and parameters |
JP2023570281A JP2024518101A (en) | 2021-05-25 | 2022-05-23 | Limited Target Wake Time (R-TWT) Operation and Parameters |
KR1020237038828A KR20230169288A (en) | 2021-05-25 | 2022-05-23 | Constrained Target Latency (R-TWT) operations and parameters |
CN202280007212.5A CN116458262A (en) | 2021-05-25 | 2022-05-23 | Constrained target latency (R-TWT) operations and parameters |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202163192656P | 2021-05-25 | 2021-05-25 | |
US63/192,656 | 2021-05-25 | ||
US202163211683P | 2021-06-17 | 2021-06-17 | |
US63/211,683 | 2021-06-17 | ||
US17/679,798 | 2022-02-24 | ||
US17/679,798 US20220386372A1 (en) | 2021-05-25 | 2022-02-24 | Restricted target wait time (r-twt) operations and parameters |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022251117A1 true WO2022251117A1 (en) | 2022-12-01 |
Family
ID=82067451
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2022/030546 WO2022251117A1 (en) | 2021-05-25 | 2022-05-23 | Restricted target wait time (r-twt) operations and parameters |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2022251117A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230239788A1 (en) * | 2021-09-07 | 2023-07-27 | Ofinno, Llc | Quiet interval termination |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3629622A1 (en) * | 2017-06-20 | 2020-04-01 | Sony Corporation | Radio communication device, communication system, and communication method |
WO2022075821A1 (en) * | 2020-10-08 | 2022-04-14 | 주식회사 윌러스표준기술연구소 | Method and wireless communication terminal for transmitting/receiving frame in wireless communication system |
-
2022
- 2022-05-23 WO PCT/US2022/030546 patent/WO2022251117A1/en active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3629622A1 (en) * | 2017-06-20 | 2020-04-01 | Sony Corporation | Radio communication device, communication system, and communication method |
WO2022075821A1 (en) * | 2020-10-08 | 2022-04-14 | 주식회사 윌러스표준기술연구소 | Method and wireless communication terminal for transmitting/receiving frame in wireless communication system |
Non-Patent Citations (6)
Title |
---|
"IEEE Standard for Information Technology--Telecommunications and Information Exchange between Systems Local and Metropolitan Area Networks--Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 1: Enhancements for High-Efficiency WL", 19 May 2021 (2021-05-19), pages 1 - 767, XP068181575, ISBN: 978-1-5044-7389-7, Retrieved from the Internet <URL:https://ieeexplore.ieee.org/document/9442429> [retrieved on 20210526], DOI: 10.1109/IEEESTD.2021.9442429 * |
CHUNYU HU (FACEBOOK INC): "PDT-MAC-Restricted-TWT", vol. 802.11 EHT; 802.11be, no. 9, 4 March 2021 (2021-03-04), pages 1 - 4, XP068179460, Retrieved from the Internet <URL:https://mentor.ieee.org/802.11/dcn/21/11-21-0142-09-00be-pdt-mac-restricted-twt.docx> [retrieved on 20210304] * |
CHUNYU HU (FACEBOOK INC): "Prioritized EDCA channel access - slot management", vol. 802.11 EHT; 802.11be, no. 4, 8 September 2020 (2020-09-08), pages 1 - 17, XP068172529, Retrieved from the Internet <URL:https://mentor.ieee.org/802.11/dcn/20/11-20-1046-04-00be-prioritized-edca-channel-access-slot-management.pptx> [retrieved on 20200908] * |
DIBAKAR DAS (INTEL): "CR for CID 1977", vol. 802.11 EHT; 802.11be, no. 5, 10 May 2021 (2021-05-10), pages 1 - 8, XP068180120, Retrieved from the Internet <URL:https://mentor.ieee.org/802.11/dcn/21/11-21-0340-05-00be-cr-for-cid-1977.docx> [retrieved on 20210510] * |
LIANGXIAO XIN (SONY): "Interaction between R-TWT and SCS (CC36 resolution for CID 4121)", vol. 802.11 EHT; 802.11be, no. 2, 23 February 2022 (2022-02-23), pages 1 - 12, XP068189089, Retrieved from the Internet <URL:https://mentor.ieee.org/802.11/dcn/22/11-22-0212-02-00be-interaction-between-r-twt-and-scs-cc36-resolution-for-cid-4121.pptx> [retrieved on 20220223] * |
SUNHEE BAEK: "CR for Restricted TWT SP", vol. 802.11 EHT; 802.11be, 15 April 2021 (2021-04-15), pages 1 - 3, XP068179753, Retrieved from the Internet <URL:https://mentor.ieee.org/802.11/dcn/21/11-21-0672-00-00be-cr-for-restricted-twt-sp.docx> [retrieved on 20210415] * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230239788A1 (en) * | 2021-09-07 | 2023-07-27 | Ofinno, Llc | Quiet interval termination |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20220386372A1 (en) | Restricted target wait time (r-twt) operations and parameters | |
US20230058871A1 (en) | Stream classification service (scs) with restricted target wait time (r-twt) setup | |
US20230081745A1 (en) | Preemption / interruption of an ongoing low priority ppdu | |
WO2022251117A1 (en) | Restricted target wait time (r-twt) operations and parameters | |
WO2023122530A1 (en) | Fast restricted target wait time update | |
US20230139168A1 (en) | Multi-link restricted twt | |
US20230269788A1 (en) | Dynamic edca in r-twt initial access | |
US20230047705A1 (en) | Restricted target wake time service period termination | |
EP4364513A1 (en) | Restricted target wake time service period termination | |
US11889556B2 (en) | Prioritized channel access | |
US20240008086A1 (en) | Prioritization of r-twt tids in r-twt sps | |
US20230262770A1 (en) | Transmit opportunity sharing in a restricted target wait time | |
US20240008081A1 (en) | Triggered txop sharing with ac limitation | |
US20220400500A1 (en) | Enabling legacy (non-eht) stations to operate on the conditional link of a soft ap mld | |
WO2022130216A1 (en) | Prioritized channel access | |
US20230262769A1 (en) | Single channel p2p communication for mlds | |
WO2023114673A1 (en) | Multiple station access in a reserved target-wait-time service period | |
WO2023177990A1 (en) | Transmit identifier to user priority / ac mapping | |
WO2023091864A1 (en) | Non-r-twt member sta access grant for burst traffic transmission | |
CN116803184A (en) | Preemption/interruption of an ongoing low priority PPDU | |
CN116830650A (en) | Stream Classification Service (SCS) with limited target latency (R-TWT) setting | |
WO2022259080A1 (en) | Enabling legacy (non-eht) stations to operate on the conditional link of a soft ap mld | |
CN116889071A (en) | Limited target wake time service period expiration | |
WO2023044263A1 (en) | Preemption / interruption of an ongoing low priority ppdu | |
WO2023154584A2 (en) | Block acknowledgement agreement for latency sensitive traffic stream |
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: 22731017 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280007212.5 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022731017 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2022731017 Country of ref document: EP Effective date: 20231102 |
|
ENP | Entry into the national phase |
Ref document number: 20237038828 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020237038828 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023570281 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |