EP4378265A1 - Détection de collision et résolution de collision pour une communication en duplex intégral priorisée - Google Patents

Détection de collision et résolution de collision pour une communication en duplex intégral priorisée

Info

Publication number
EP4378265A1
EP4378265A1 EP22778064.0A EP22778064A EP4378265A1 EP 4378265 A1 EP4378265 A1 EP 4378265A1 EP 22778064 A EP22778064 A EP 22778064A EP 4378265 A1 EP4378265 A1 EP 4378265A1
Authority
EP
European Patent Office
Prior art keywords
priority
sta
preamble
collision
traffic
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP22778064.0A
Other languages
German (de)
English (en)
Inventor
Qing Xia
Li-Hsiang Sun
Mohamed Abouelseoud
Liangxiao Xin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sony Group Corp
Sony Corp of America
Original Assignee
Sony Group Corp
Sony Corp of America
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
Priority claimed from US17/819,285 external-priority patent/US12273920B2/en
Application filed by Sony Group Corp, Sony Corp of America filed Critical Sony Group Corp
Publication of EP4378265A1 publication Critical patent/EP4378265A1/fr
Pending legal-status Critical Current

Links

Classifications

    • 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/0825—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision detection
    • 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
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0866—Non-scheduled access, e.g. ALOHA using a dedicated channel for access
    • H04W74/0875—Non-scheduled access, e.g. ALOHA using a dedicated channel for access with assigned priorities based access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • 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 wireless local area networks (WLANS), and more particularly to full-duplex WLANS which address self-interference issues.
  • WLANS wireless local area networks
  • WLANS full-duplex WLANS which address self-interference issues.
  • FD Full Duplex
  • WLANs wireless local area networks
  • a new preamble-based collision detection apparatus and method which can be performed without Self Interference (SI) estimation. Also disclosed is a new collision resolution estimation and scheduling mechanism for communication with prioritized traffic.
  • SI Self Interference
  • the collision detection (CD) mechanism is able to detect collisions more rapidly using orthogonal (e.g., time/frequency domain) preambles in time domain or in frequency domain.
  • the priority information is embedded in a preamble.
  • the priority levels can be predetermined and agreed by all FD STAs. This priority information can be embedded in a FD preamble field following the legacy preamble field defined in 802.11.
  • the FD STA can handle detection of colliding preambles in different ways, which can depend on relative priority.
  • the mechanism can guarantee prioritized transmission after the process of intra-BSS collision estimation, such as FD STAs indicating priority in control frames used for collision avoidance, and/or an FD scheduler STA allowing higher priority traffic to be processed no later than the lower priority traffic when intra-BSS collision is estimated.
  • an FD STA can initiate a Transmit Opportunity (TXOP) with a Ready-To-Send I Clear-to-Send (RTS/CTS) exchange.
  • TXOP Transmit Opportunity
  • RTS/CTS Clear-to-Send
  • FIG. 1 and FIG. 2 are plots comparing what is thought to be transmitted versus what is actually received to demonstrate various noise sources including SI.
  • FIG. 3 is a chart of SIC requirements of analog and digital cancellation based of a transmitted signal with its sub-component.
  • FIG. 4 and FIG. 5 depict an FD preamble that may be specified as a FD standalone training frame as in FIG. 4, or appended to the existing frames as is seen in FIG. 5.
  • FIG. 6 is a block diagram of full duplex transceiver with analog and digital SIC, showing that between each pair of Tx chain and Rx chain, there are RF I analog Self-Interference-Cancellation (SIC) and baseband I digital SIC elements, according to at least one embodiment of the present disclosure.
  • SIC Self-Interference-Cancellation
  • FIG. 7 is a hardware block diagram of wireless station (STA) hardware, according to at least one embodiment of the present disclosure.
  • FIG. 8 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. 9 is an example network topology for asymmetric FD as used for demonstration purposes according to at least one embodiment of the present disclosure.
  • FIG. 10 is an example network topology for symmetric FD as used for demonstration purposes according to at least one embodiment of the present disclosure.
  • FIG. 11 is an example network topology having an AP and multiple FD stations for demonstration purposes according to at least one embodiment of the present disclosure.
  • FIG. 12 and FIG. 13 are block diagrams of self-interferences paths for a dual and single antenna element which demonstrate various forms of interference.
  • FIG. 14 is a signal diagram on making time domain signals orthogonal in a FD preamble for collision detection according to at least one embodiment of the present disclosure.
  • FIG. 15 is a signal diagram of a preamble field and a FD preamble in the time domain and in the frequency domain, according to at least one embodiment of the present disclosure.
  • FIG. 16 is a signal diagram of frequency domain collisions between different prioritized preambles, according to at least one embodiment of the present disclosure.
  • FIG. 17 is a signal diagram of collisions between frequency-domain preambles which indicate the same priority, according to at least one embodiment of the present disclosure.
  • FIG. 18 is a signal diagram of collision detection between a prioritized preamble and a legacy preamble, according to at least one embodiment of the present disclosure.
  • FIG. 19 is an example network topology used for FIG. 18, according to at least one embodiment of the present disclosure.
  • FIG. 20 is a flow diagram of a transmitting station reacting to detection of a collision, according to at least one embodiment of the present disclosure.
  • FIG. 21 is an example network topology for describing Problem 6.2, according to at least one embodiment of the present disclosure.
  • FIG. 22 is a communication diagram of Example 2-1 for performing an HP traffic grant with a PR plus CDP frame, according to at least one embodiment of the present disclosure.
  • FIG. 23 is a communication diagram of Example 2-1-0: FD AP Trigger LP Traffic w/o Receiving any Response from the Granted HP Traffic Destination , according to at least one embodiment of the present disclosure.
  • FIG. 24 is a communication diagram of Example 2-1-1 : FD STA1 Re- Access Channel w/o Receiving Trigger from FD, according to at least one embodiment of the present disclosure.
  • FIG. 25 is a communication diagram of Example 2-1-2: HP Traffic Grant w/o PR+CDP Frame, according to at least one embodiment of the present disclosure.
  • FIG. 26 is a communication diagram of Example 2-2: HP Traffic Grant when AP has LP, according to at least one embodiment of the present disclosure.
  • FIG. 27 is an example network topology for use in describing Example 2-2: HP Traffic Grant when AP has LP, according to at least one embodiment of the present disclosure.
  • FIG. 28 is an example network topology for describing Extended Example 2-3: Effects of OBSS Collision for OBSS interference, according to at least one embodiment of the present disclosure.
  • FIG. 29 is an example network topology for describing Extended Example 2-3: Effects of OBSS Collision for intra-BSS interference, according to at least one embodiment of the present disclosure.
  • FIG. 30 is an example network of topologies in which cases the AP may overestimate the collision as described according to at least one embodiment of the present disclosure.
  • FIG. 31 is a communication diagram of resolving example Case 2 of an overestimated collision of FIG. 30, according to at least one embodiment of the present disclosure.
  • FIG. 32 through FIG. 35 is a flow diagram of FD AP operation if the TXOP is started with a P-RTS, P-CTS combination, according to at least one embodiment of the present disclosure.
  • FIG. 36 through FIG. 38 is a flow diagram of FD STA operation if the TXOP starts with a P-RTS, P-CTS combination, according to at least one embodiment of the present disclosure.
  • FIG. 39 is a communication diagram of Example 3-1 : HP Traffic Grant for PPDll Initiated TXOP, according to at least one embodiment of the present disclosure.
  • FIG. 40 is a communication diagram of Example 3-2: HP Traffic Grant with an Overestimated Intra-BSS Collision, according to at least one embodiment of the present disclosure.
  • FIG. 41 is a communication diagram of Example 3-3: HP Traffic Grant for PPDII initiated TXOP when AP has LP, according to at least one embodiment of the present disclosure.
  • FIG. 42 is a communication diagram of Example 3-4: HP Traffic Grant for PPDII Initiated TXOP when AP has LP, according to at least one embodiment of the present disclosure.
  • FIG. 43 through FIG. 45 is a flow diagram of a FD AP starting a TXOP with the DATA PPDII, according to at least one embodiment of the present disclosure.
  • FIG. 46 through FIG. 47 is a flow diagram of a non-AP STA starting the
  • TXOP with a DATA PPDII according to at least one embodiment of the present disclosure.
  • FIG. 48 is a data field diagram of a P-RTS frame according to at least one embodiment of the present disclosure.
  • FIG. 49 is a data field diagram of a PR request field from FIG. 48, according to at least one embodiment of the present disclosure.
  • FIG. 50 is a data field diagram of a P-CTS frame, according to at least one embodiment of the present disclosure.
  • FIG. 51 is a data field diagram of a PR control field shown in FIG. 50, according to at least one embodiment of the present disclosure.
  • FIG. 52 is a data field diagram of a PR+CDP frame, according to at least one embodiment of the present disclosure.
  • FIG. 53 is a data field diagram of the PR+CDP control field as seen in FIG. 52.
  • Benefits of FD include the ability to simultaneously transmit and receive wireless signals sharing the same frequency resource; thus, providing the potential to double the spectral efficiency of bidirectional links compare to half- duplex links.
  • the challenge is to efficiently and sufficiently cancel the selfinterference (SI) which is transmitted by an FD device and received by the same device through transceiver coupling and multipath reflections.
  • SI selfinterference
  • FIG. 1 and FIG. 2 depicts the spectrum (power and frequency) of an expected transmission (FIG. 1 ), and what was actually transmitted (FIG. 2).
  • the result is that a signal originally transmitted by a STA is as seen in FIG. 1 , however, the actual transmitted signal is as depicted in FIG. 2.
  • the numerous analog components in the transceiver distort the original signal as seen in FIG. 1 , by adding transmitter noise and harmonics to the transmitted signal, resulting in the signal received as per FIG. 2.
  • FIG. 3 depicts Self-Interference Cancelation (SIC) requirements for FD to sufficiently cancel any self-interference so that the interference power is reduced down to the level of the receiver noise floor (-90dBm).
  • SIC Self-Interference Cancelation
  • the transmitted signal comprising 110 dB main signal, 80 dB of harmonics, and 50 dB of transmitter noise.
  • noise cancelation which includes 60 dB of analog SIC cancellation, with which the receiver chain satisfies the 10 dB of Peak-to-Average-Power-Ratio (PAPR) at receiver saturation, and 50 dB of digital SIC cancellation, the use of SIC results in the -90 dBm receiver noise floor.
  • PAPR Peak-to-Average-Power-Ratio
  • an SIC should provide the following capabilities.
  • Any FD system should provide 110dB of linear self-interference cancellation to reduce SI to the receiver noise floor. This can eliminate the strongest main signal component (110dB) above the noise floor.
  • a FD system shall reduce non-linear harmonic components that are 80dB above the noise floor.
  • Any FD system shall have an analog cancellation component that provides at least 50dB of analog noise cancellation to cancel the transmitter noise.
  • receiver (RX) chain in radios can get saturated if the input signal is beyond a particular level which is determined by their Analog-to- Digital-Converter (ADC) resolution. As seen in FIG.
  • ADC Analog-to- Digital-Converter
  • Intra-access category (AC) communication prioritization provides six transmit queues that map to four enhanced distributed channel access functions (EDCAFs) to differentiate between traffic streams in the same AC to finer prioritize between AC_VI streams or AC_VO streams.
  • EDCAFs enhanced distributed channel access functions
  • Collision detection has been proposed for stopping concurrent transmissions from FD devices based on FD assisted collision detection to avoid wasted time caused by collisions. Further FD assisted EDCA access with contention resolution is also proposed to accelerate the recovery from collision. FD assisted Carrier-Sense-Multiple-Access I Collision Avoidance (CSMA/CA) has been proposed to improve the efficiency of existing MAC protocol. An FD preamble has been proposed which needs to be flexible enough to facilitate self-interference cancellation (SIC).
  • CSMA/CA Carrier-Sense-Multiple-Access I Collision Avoidance
  • FIG. 4 and FIG. 5 depict an FD preamble that may be specified as a FD standalone training frame as in FIG. 4, or appended to the existing frames as is seen in FIG. 5.
  • SIC Self-interference cancellation
  • the existing solutions request the complete SIC.
  • the current collision detection solutions cannot distinguish the different priorities of the colliding signals, and thus usually halts transmissions from both sides to avoid further collision.
  • FD collision detection methodologies utilize prioritized preambles defined in a new FD preamble field.
  • the collision detection of the prioritized preambles does not require complete Self- Interference Cancellation (SIC).
  • SIC Self- Interference Cancellation
  • the use of collision detection based on the FD preamble, without SIC, improves transmission efficiency of the detecting STAs, so it can halt transmitting the remainder of the Physical Layer Protocol Data Unit (PPDU) to avoid further collisions.
  • PPDU Physical Layer Protocol Data Unit
  • the present disclosure describes another collision resolution method for the prioritized streams, which grants the higher prioritized streams with earlier access than the lower streams when an intra- BSS collision occurs.
  • FIG. 6 illustrates an example embodiment 10 of Self-Interference Cancelation (SIC) hardware as utilized in a station having a Radio Frequency Front End (RFFE) 30.
  • This SIC hardware is utilized in wireless local area networks (WLANs), such as the STA seen below in FIG. 7 and the MLD seen in FIG. 8.
  • WLANs wireless local area networks
  • the Tx Digital BB 12 is the baseband Transmit (TX) signal.
  • the baseband digital signal accumulates harmonics and transmitter noises through modulation of the Digital-to-Analog converter (DAC) and upconverter (UC) 14 to a passband signal.
  • DAC Digital-to-Analog converter
  • UC upconverter
  • the SIC circuit consists of parallel fixed lines of varying delays 26a through 26n and tunable attenuators 28a through 28n. These lines are then collected and added up, and this combined signal is then subtracted 23 from the signal on the receive path.
  • the passband signal received from antenna 22, has SIC correction applied 23, and passes through analog to digital converter (ADC) and down converter (DC) 20.
  • a digital SIC 24 is applied 19 to the baseband digital signal from the ADC and DC, to estimate the remaining residual selfinterference, which includes the main TX SI after analog cancellation and any delayed reflections of this signal from the environment, to produce receiver digital baseband signal 18.
  • FIG. 7 illustrates an example embodiment 50 of STA hardware configured for executing the protocol of the present disclosure.
  • An external I/O connection 54 preferably couples to an internal bus 56 of circuitry 52 upon which are connected a CPU 58 and memory (e.g., RAM) 60 for executing a program(s) which implement the communication protocol.
  • the host machine accommodates at least one modem 62 to support communications coupled to at least one RF module 64, 68 each connected to one or multiple antennas 69, 66a, 66b, 66c through 66n.
  • 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 54 allows connecting various devices to the CPU, such as to sensors, actuators and so forth.
  • Instructions from memory 60 are executed on processor 58 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 62, 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. 8 illustrates an example embodiment 90 of a multi-link device (MLD) hardware configuration.
  • the MLDs may comprise a soft AP MLD, which is a MLD that consists of one or more affiliated STAs, which are operated as APs.
  • a soft AP MLD should support multiple radio operations on 2.4GHz, 5GHz and 6GHz.
  • basic link sets are the link pairs that satisfy simultaneous transmission and reception (STR) mode, e.g., basic link set (2.4 GHz and 5 GHz), basic link set (2.4 GHz and 6GHz).
  • STR simultaneous transmission and reception
  • the conditional link is a link that forms a non-simultaneous transmission and reception (NSTR) link pair with some basic link(s).
  • these link pairs may comprise a 6 GHz link as the conditional link corresponding to 5 GHz link when 5 GHz is a basic link; 5 GHz link is the conditional link corresponding to 6 GHz link when 6 GHz is a basic link.
  • the soft AP is used in different scenarios including Wi-Fi hotspots and tethering.
  • 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 98 having a CPU 112 and memory (e.g., RAM) 114 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 STA1 92, STA2 94 through to STA_N 96 and the sharing of information between affiliated STAs.
  • each STA of the MLD has its own CPU 100 and memory (RAM) 102, which are coupled through a bus 108 to at least one modem 104 which is connected to at least one RF circuit 106 which has one or more antennas.
  • the RF circuit has multiple antennas 110a, 110b, 11 Oc through 110n, 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. 9 illustrates an example embodiment 150 of an asymmetric FD architecture, in which FD AP 152 is transmitting to FD STA1 154 and receiving from FD STA2 156 simultaneously.
  • the transmitted signal from the TX antenna of FD AP creates self-interference and is received by the RX antenna of the FD AP.
  • FIG. 10 illustrates an example embodiment 160 of a symmetric FD architecture, in which FD AP 162 is transmitting to, and receiving from, another FD STA 164.
  • FD AP and FD STA receive self-interferences generated by themselves.
  • FIG. 11 illustrates an example embodiment 170 of a network topology used in the examples by way of illustration and not by way of limitation, which is also true of the other topologies exemplified herein.
  • the example depicts three FD transceivers as FD AP 172, FD STA1 174 and FD STA2 176.
  • FD AP, FD STA1 and FD STA2 are within the communication range of each other (e.g., they can ‘hear’ each other).
  • FD STA1 and FD AP start a transmission simultaneously.
  • FD STA1 is sending a PPDU to FD AP, at the same time FD AP is sending a PPDU to FD STA2.
  • FD STA1 and FD AP would be subject to SI before SIC processing is performed.
  • FIG. 12 and FIG. 13 illustrate examples 180, 200, of self-interferences paths for dual and single antennas.
  • a STA 182 is shown with a transmit chain 184 to antenna 186, and a receiver chain 188 from antenna 190. The figure depicts leakage between the antennas, reflections due to transceiver structure, and external reflections 192.
  • a STA 182 is shown with transmit chain 184 coupled 202 to a single antenna 210, and receive chain 188 coupled 204 to the same antenna 210. The figure depicts leakage between the transmit chain and the receiver chain, reflections due to antenna mismatch, reflection due to the environment, and external reflections 212.
  • SIC Self-Interference Cancellation
  • 802.11 FD technology attempts preamble-based collision detection, which is performed after completing self-interference cancellation (SIC).
  • SIC self-interference cancellation
  • the FD transceiver If the FD transceiver has not performed self-interference (SI) estimation of the external reflections (as shown in FIG. 12 and FIG. 13) of the SI, the FD transceiver will not recognize the presence of another signal.
  • SI self-interference
  • the FD transceiver may not be able to determine that a collision has occurred based on Cyclic Redundancy Check (CRC) error by hearing (receiving) its own preamble.
  • CRC Cyclic Redundancy Check
  • the colliding signal is too weak compared to self-interference of its own preamble (e.g., which is coded with MCS0).
  • (1 ) Include priority information in the FD preamble for collision detection resolution. In this case, the collision detection does not request the complete SIC.
  • Each STA Transmits FD preamble of the PPDU that carries the priority signals that is orthogonal to other priority signals carried by the FD preamble of the other STAs. For example, the orthogonal priority signals can be preconfigured.
  • (3) When collision is detected, the STA with higher priority should retransmit the PPDU.
  • the STA with lower priority, or the same priority should stop (halt) its transmission and start a backoff procedure after once again sensing that the medium is idle.
  • the STA detects a collision without detecting the priority of the colliding FD preamble, so the STA shall stop transmission and start a backoff after sensing the medium is idle (available).
  • FD STA1 is sending a PPDU to FD AP, and at the same time FD AP is sending a PPDU to FD STA2.
  • FD AP and FD STA1 receive signals during their transmission.
  • the received signals contains the self-interference signals and the interference signals from other STAs.
  • the following describes use of time domain signals in an FD preamble.
  • FIG. 14 illustrates an example embodiment 220 to make time domain signals orthogonal (orthogonalize) in a FD preamble for use in collision detection.
  • Blocks 222 and 224 represents Orthogonal Frequency Division Multiplexing (OFDM) symbols (defined as data samples with the Cyclic Prefix (CP), which in this case is around 3 is in time domain.
  • OFDM Orthogonal Frequency Division Multiplexing
  • the window size depicted as the vertical dashed line boxes, represent the duration of an OFDM symbol duration without the use of CP. Assuming the detecting STA is FD STA1 , and the colliding STA is FD AP. The upper symbols 222 are colliding with the STA’s FD preamble signal with priority 2. The lower symbols 224 are detecting the STA’s own FD preamble with priority 1.
  • This example is based on the content in section 5.2.1 , and describes the collision detection procedure.
  • the STA Before transmitting the FD preamble, the STA, which is a FD transceiver, has not performed channel estimation of self-interference (SI) from external surroundings.
  • SI self-interference
  • P-matrix which is an orthogonal matrix, (in this case 1 j is used for collision detection before performing the self-interference cancellation.
  • the P-matrix can be configured based on existing 802.11 standards or any other desired orthogonal matrix may be utilized.
  • [x0,x0] are two symbols as part of the FD preamble and the two xO symbols are identical.
  • STA1 (with priority 1 ) multiplies [x0,x0] by first column of P-matrix, it sends out [x0,x0];
  • STA2 is the colliding STA (with priority 2) multiplies [x0,x0] by the second column of the P-matrix, it then sends out [xO, -x0],
  • the STA shall determine if it should retransmit the frame, or stop (halt) transmission and perform a backoff after sensing that the channel medium is idle. In at least one embodiment, the decision is made based on comparing its own priority with the priority indicated in the received FD preamble from colliding STA.
  • the prioritized FD preambles are coded using the same P-matrix, the FD STA which detected a colliding FD preamble based on step (c) can deduce the vector of the P-matrix/priority that the colliding STA is using.
  • the STA1 detects the collision by subtracting yl from yO, which equals 2 * xO * h2 as explained in (c), and recognizes that this result represents a collision.
  • STA1 is using [1, 1] vector of the P-matrix to represent the priority 1. With this information, STA1 can deduce that the colliding FD preamble is coded with [1, -1] vector of P-matrix, which represents priority 2.
  • the STA should retransmit PPDll if it has higher priority. Otherwise, it shall stop transmitting PPDll immediately and backoff after sensing the medium idle.
  • CP cyclic prefix
  • time domain orthogonal signals may completely lose orthogonality.
  • FD preamble includes priority information which is embedded in the frequency domain. Different priorities can be carried by different subcarriers or tones of the FD preamble with them being separated by at least 40 ppm.
  • the STA In the received baseband signal after analog cancellation and before digital cancellation (it should be noted that the digital cancellation requires SI channel estimation), the STA zeros out the tones of its own FD preamble to discover other STAs with a different priority.
  • an FD STA If an FD STA detects the colliding FD preamble as having a lower priority than its own priority, it should retransmit the FD preamble and the remainder of the PPDU. Otherwise, it shall stop (halt) transmission and start a backoff process after sensing that the channel medium is again idle. In response to receiving the retransmitted FD preamble from a higher priority STA, the receiver can resynchronize and estimate the channel.
  • the transmitted center frequency tolerance shall be ⁇ 20 ppm for 20MHz. It should be appreciated that where parts per million (ppm) is used to describe frequency accuracy, e.g., an accuracy of 20 ppm indicates that the mean frequency of the clock may be off by 20 Hz for every 1 MHz of its specified value.
  • Different priorities can be carried by different subcarriers and/or tones of the transmitted FD preamble.
  • Each STA only transmits one or several consequent tones to carry the priority.
  • the tones used for indicating a priority carry symbol “1”s, and other tones carry symbol “0”s.
  • a FD device When a FD device is transmitting, it cannot distinguish a simultaneously received prioritized FD preamble from itself or from a colliding STA if the received prioritized FD preamble indicates the priority on the subcarriers and/or tones is within 40 ppm of the subcarriers and/or tones carrying its own priority. Thus, different priorities shall be carried on different subcarriers and/or tones of the FD preamble with at least a spacing of 40 ppm apart. The large space of greater than 40ppm between subcarriers carrying priority information enables the detection of a different priority even with CFO.
  • the subcamer(s) and/or tone(s) are predetermined to represent a specific priority.
  • a STA transmitting its prioritized FD preambles can detect a collision from the received FD preamble, by zeroing out the self-interference of its own priority signals using analog SIC. A collision is detected if the STA detects another priority signal after the zeroing out is performed.
  • the priority tones interleaved in the prioritized preamble may not be understood by legacy devices.
  • FIG. 15 illustrates an example embodiment 230 of a preamble field 232 and a FD preamble 234 in the time domain and in the frequency domain.
  • the preamble field can be the same as the preamble defined in the 802.11 baseline protocol.
  • the FD preamble field follows immediately after the preamble field and is used to carry a specific priority.
  • Different priorities exemplified as 236a, 236b, 236c and 236d, can be indicated in different subcarrier(s) of the FD preamble, with a given spacing (i.e., at least 40 ppm) in between.
  • FIG. 16 illustrates an example embodiment 240 of frequency domain collisions between different prioritized preambles.
  • the figure shows the preamble 242 and FD preambles 243 as were seen in FIG. 15.
  • This example is based on the same topology as introduced in FIG. 11. It is assumed that FD STA1 sends PPDII with preambles indicating priority ⁇ 244a and 246a; while at the same time the FD AP, as an interferer, sends a PPDII with a preamble indicating priorityl 244b and 246b.
  • the two preambles from FD STA1 and FD AP are sent almost at the same time. As a result, collisions may arise on FD STA2.
  • FD STA1 which indicates a priority equal to zero, will zero out the pulses associated with priorityO transmissions 244a and 246a, which are carried by priorityO tones, as well as a portion of the spurious signals, which are also on the priority 0 tones, but are from the interfering preamble indicating priority 1 (after analog SIC). Then, FD STA1 can detect the peaks in the priority 1 signal which indicates existence of a colliding preamble with different priority (priority 1 ) corresponding to the tones 244b and 246b.
  • the FD AP performs the same action as does FD STA1 , and can also detect a colliding preamble with different priority (priority 0).
  • the lower priority (e.g., priority 0) FD STA1 should then stop transmission and start a backoff. It is assumed in this discussion, that priority 0 refers to a lower priority than priority 1 .
  • the higher priority (e.g., priority 1 ) FD AP may retransmit and allow the intended receiver to re-synchronize and estimate the channel.
  • FIG. 17 illustrates an example embodiment 250 of collisions between frequency-domain preambles which indicate the same priority. This example is also based on the same topology as introduced in FIG. 11. It is assumed that FD STA1 sends a PPDll with a preamble indicating priority 0 252a and 254a. At this same time, an interfering FD AP, sends PPDll with preamble 252b and 254b, also indicating priority 0 and collision may occur on FD STA2.
  • FD STA1 may also zero out the interfering priority 0 pulses from
  • FD STA1 may detect the interfering peaks from FD AP, if CFO is significant (e.g., greater than 40 ppm), whereby the STA recognizes the interfering peaks indicate existence of a colliding preamble with the same priority (priority 0). In this case, FD STA1 halts transmission and performs a backoff when the channel is again idle. The FD AP performs in the same manner as described for FD STA1 .
  • the received peak pulse has the same priority tone or tones as the transmitted tone or tones, because the speed of the STA or the obstacles that reflect the signal are usually quite small compared to the speed of the wave.
  • the changing in frequency between received frequency and the emitted frequency Af Av * fO/c, where fO is the emitted frequency and c is the wave’s propagation speed in air (around 3 * 10 A 8 m/sec).
  • FIG. 18 and FIG. 19 illustrates an example embodiment 260 with a different topology 270.
  • FIG. 19 In FIG. 19 is seen a FD AP 272 which is receiving from both an FD STA1 274 and a half-duplex STA2 276.
  • FD STA1 sends a PPDll to FD AP with prioritized preamble 256a, 256b indicating priority on priority 0 tone/tones.
  • the non-FD STA2 an interferer, sends PPDll to the FD AP with a legacy preamble; whereby a collision may arise on the FD AP.
  • the legacy preamble is using the preamble frame format as defined in 802.11 standard, which does not contain subcarriers I tones to contain priority information.
  • FIG. 20 illustrates an example embodiment 280 of a transmitting station, which could be a FD non-AP STA or a FD AP, reacting to detection of a collision.
  • a check 282 determines the priority level of a colliding FD preamble. If the condition is met, then at block 284 a check determines if the detected priority is lower than that of the detecting station. If the condition is met, then a retransmission 286 is performed.
  • a problem can arise when a FD AP needs to prioritize high priority traffic over lower priority traffic, and both sets of traffic are using the channel at the same time and the destination non-AP STA of the DL traffic and source non-AP STA of the UL traffic are different, whereby collision occurs at the destination non-AP STA of the DL traffic.
  • FIG. 21 illustrates an example embodiment 300 of a topology showing a FD AP 302 receiving a low priority traffic from a FD STA1 304, and transmitting high priority traffic to a FD STA2 306.
  • FD STA1 , FD STA2 and FD AP are in communication range of one another, with the object being for the AP to send High priority traffic to STA2 and STA1 to send Low priority traffic to AP.
  • FD STA 1 transmits a Ready-To-Send (RTS) to FD AP and FD AP sends an RTS to FD STA2 simultaneously. Collision arises on FD STA2, resulting in FD AP not receiving CTS from FD STA2, although FD AP can receive RTS from FD STA1 .
  • RTS Ready-To-Send
  • FD devices may indicate priority in the control frames used for collision avoidance.
  • the FD device recognizes there is an intra-BSS interference and should first deal with the higher prioritized traffic.
  • the FD device which estimates intra-BSS interference as described in item 2, may broadcast a frame indicating the preferred priority that the FD device should handle first, (a) After receiving the frame indicating request traffic priority; the FD device transmitting lower priority traffic halts (stops) any transmissions I retransmissions, (b) The FD device that transmits the higher, or same, priority traffic should continue the (re)transmission process.
  • the FD AP may trigger a non-AP FD device to initiate the transmission of lower prioritized traffic.
  • the non-AP FD device with lower prioritized traffic may re-access the channel, without being triggered, if the channel is idle for at least a PIFS duration after the non-AP FD device receives the broadcast frame which indicates a higher prioritized traffic is preferred.
  • a FD device If a FD device directly transmits Data PPDll instead of RTS, it can use the simultaneously transmitted FD preamble and received FD preamble to estimate the intra-BSS collision and decide on the following process based on the priority resolution, (a) A FD device which estimates the existence of an intra-BSS collision with a lower priority than itself, should retransmit the PPDll.
  • a portion of the Resource Units (RUs) may be reserved for purposes other than for serving DATA PPDUs; and more particularly for exchanging control messages between the AP and other STAs.
  • a FD device which estimates the existence of an intra-BSS collision with higher priority than itself, is configured to stop transmitting the remainder of the PPDU; unless it receives a control frame from the reserved RU or the non-reserved RUs, such as a trigger from its destination. If this STA fails to receive any other frame exchanges between other STAs, it may access the channel again after EDCA backoff when CCA is idle, (c) A FD device which only receives a preamble without the remainder of the DATA PPDU may send a control frame using the reserved RUs (e.g., can be predetermined RUs) to indicate the existence of an overestimated intra-BSS collision.
  • the reserved RUs e.g., can be predetermined RUs
  • the preamble source STA may retransmit or trigger (through reserved Rlls) to retransmit the previously suspended PPDUs which has been overestimated as the intra-BSS colliding signal.
  • FIG. 22 Illustrates an example embodiment 310 of FD AP with High Priority (HP) 312, FD STA1 with Low Priority (LP) 314, and a FD STA2 316. It is assumed STA1 and STA2 can hear (communicate with) each other, and the process commences with RTS/CTS.
  • HP High Priority
  • LP Low Priority
  • the topology is the same as seen in FIG. 21 .
  • the FD AP has High Priority (HP) traffic to send to FD STA2, and FD STA1 has Low Priority (LP) traffic to send to FD AP.
  • the FD AP, FD STA1 and FD STA2 are in communication range of (e.g., they can hear) each other.
  • FD AP and FD STAs initiate a Transmit Opportunity (TXOP) each with a prioritized control frame, e.g., prioritized RTS (P-RTS) 318 and 319.
  • TXOP Transmit Opportunity
  • P-RTS prioritized RTS
  • the AP receives P-RTS 319 from STA1 (lower priority traffic) and at the same time sends P-RTS 318 to STA2 (higher priority traffic).
  • PR+CDP Detection Probability 320 to declare AP requests for higher priority DATA transmission.
  • the AP may thus indicate collision detection possibility in the new (PR+CDP) frame.
  • the AP shall retransmit another P-RTS 322 to STA2. It should be noted that the transmission time of the PR+CDP frame should be no longer than a P-CTS timeout. If the transmission time of the PR+CDP frame is longer than a P-CTS timeout, the AP shall retransmit the P-RTS a SIFS period after the AP sending out the PR+CDP frame.
  • STA2 receives the retransmitted P-RTS from the AP and responds to the AP with P-CTS 324.
  • the AP transmits PPDll 326 to STA2, with
  • the AP triggers 334 STA, which access the channel and send PPDll 338, which are Acked 340 and 342.
  • FIG. 23 illustrates an example embodiment 410 which is a variation of that seen in FIG. 22.
  • the description is the same as that in example 2-1 .
  • the first four bullet points for this example are the same as that described in Example 2-1 ; the differences commence here at the 5 th element.
  • STA2 fails to receive the retransmitted P-RTS 322 from the AP, and thus does not respond to the AP with P-CTS.
  • STA1 receives the trigger frame from AP and sends UL PPDll 418 to AP and receives Ack/BA 420 from the AP during the transmission of UL PPDU.
  • the AP sends a DL PPDU 430 to STA2 after receiving the P-CTS from STA2.
  • AP may receive Ack/BA 432 from STA2 during the transmission of DL PPDU.
  • STA2 shall acknowledge 434 AP for all received DL PPDUs.
  • FIG. 24 illustrates an example embodiment 510 which has the same topology and description as in Example 2-1 .
  • the first four bullet points are same as that described in Example 2-1 ; with the steps below starting at that point.
  • STA2 fails to receive the retransmitted P-RTS 322 from the AP, and thus it does not respond to the AP with a P-CTS.
  • AP does not receive the P-CTS from STA2 after the retransmission of P-RTS, and thus it doesn’t send a trigger frame to STA1 to enable STA1 to access the channel.
  • STA1 is CCA busy 512 during P-RTS. Then as STA1 senses CCA idle, it accesses the channel again by sending, for example a CTS-to-self, retransmitted P-RTS to AP or send UL DATA after receiving trigger frame from AP. In this example STA1 sends retransmitted P-RTS 514 to the AP, and STA2 is seen CCA busy 516.
  • AP receives the P-RTS from STA1 and responds with a P-CTS 518 to STA1 to enable STA1 transmission of the LP UL PPDUs.
  • STA1 receives the P-CTS frame from AP and sends UL PPDU 520 to the AP and then receive Ack/BA 522 from AP during the transmission of UL PPDU.
  • AP can receive Ack/BA 534 from STA2 during the transmission of DL PPDU.
  • FIG. 25 illustrates an example embodiment 610 in example 2-1 -2: HP Traffic Grant w/o PR+CDP Frame.
  • the topology and general description is the same as in FIG. 21.
  • both AP and STA1 estimate the intra-BSS collision and are preconfigured to grant the higher prioritized traffic, then after priority resolution from a colliding preamble, they can perform the following.
  • FD AP transmits P-RTS 318 from AP (High Priority) to STA2 and receive P-RTS 319 from STA1 (Low Priority) at the same time, (b) After priority resolution of the received preamble, the AP decides to continue transmission of higher prioritized traffic.
  • AP High P
  • AP retransmits P-RTS 612 to STA2 instead of sending P-CTS as response of the received P-RTS from FD STA1 (LP).
  • STA1 is CCA busy 614.
  • AP Upon receipt of P-CTS 616 from STA2, AP transmits PPDU 618, to which STA2 Acks 620, 622. After this the AP sends a trigger 624 to STA1 which responds with PPDU 626 which the AP Acks 628, 630, while STA2 is CCA busy 625.
  • STA1 (a) Transmit P-RTS 319 from STA1 (Low Priority) to the AP and receive a P-RTS 318 from the AP(High Priority) at the same time, (b) After priority resolution based on the received preamble, STA1 stops transmission to avoid colliding with a higher prioritize traffic and goes CCA busy 614. (c) STA1 receives trigger 624 from AP (High Priority) to transmit PPDU 626, receipt of which is acknowledged 628, 630, all while STA2 is CCA busy 625.
  • FIG. 26 and FIG. 27 illustrate an example embodiment 710, and example topology 750 of a high priority traffic grant when the AP has low priority traffic.
  • FIG. 27 the topology is almost identical to FIG. 21 , the difference being that the priority of the traffic is swapped with the FD AP having LP traffic to FD STA2 and FD STA1 having HP traffic to the AP.
  • the stations are in range of one another, and the FD AP and FD STAs initiate a TXOP with a prioritized control frame, exemplified with a Prioritized-RTS (P-RTS).
  • P-RTS Prioritized-RTS
  • FD STA1 sends P-RTS 319 (HP) to FD AP and FD AP sends P-
  • P-RTS frames may collide at FD STA2 if FD STA1 and FD STA2 are within the communication range of each other.
  • (2) FD AP responds with a P-CTS 712 to STA1 (HP) at first and temporally pauses retransmission of P-RTS to STA2. At that time STA2 is CCA busy 714.
  • STA1 transmits UL PPDU 716 after receiving P-CTS from AP; and receives Acks 718 and 720, accordingly.
  • AP1 sends a DL PPDll 728 to STA2 after receiving P-CTS from
  • FIG. 28 and FIG. 29 illustrates example topographies 790 and 810, used for illustrating the effects of Other Basic Service Set (OBSS) collision.
  • OBSS Basic Service Set
  • the AP should grant the transmission of higher prioritized traffic after performing collision resolution.
  • collisions may be caused by an OBSS interference, and the AP does not receive the colliding frame.
  • the FD AP1 802 estimates the existence of OBSS interference.
  • FD STA1 800 and FD STA2 798 are associated with FD AP1 802, with FD AP2 792 being an OBSS AP, which can create OBSS interference, exemplified by signals 794 and 796.
  • FD AP1 802 is sending out high priority traffic (HP) 804 to STA2 798.
  • HP high priority traffic
  • FD AP1 is sending high prioritized traffic 804 to FD STA2
  • the OBSS AP2 is sending some frames in the OBSS.
  • the high prioritized traffic frame from FD AP1 and the interference 794 frame from FD AP2 collide at FD STA2.
  • AP1 doesn’t receive the interference frame from the OBSS AP2 and cannot estimate the existence of the collision during sending out the high prioritized traffic frame. In this case, FD AP1 should retransmit the frame based on the legacy retransmission policies.
  • the AP estimates the existence of intra-BSS interference.
  • the topology and the OBSS interference is the same as that in FIG. 28, however, in this example FD AP1 812 is sending out the same HP traffic 814 to FD STA2 798; but in this example FD STA1 800 is also transmitting a lower priority traffic frame 816 to FD AP1 812.
  • FD STA2 798 which is caused by intra-BSS interference and OBSS interference.
  • FD AP1 can only estimate the existence of an intra-BSS collision, by receiving a colliding preamble indicating lower priority during transmission.
  • FIG. 30 illustrates example cases 850a, 850b, 850c and 850d in which the AP may overestimate the collision.
  • These cases depict different scenarios combining an FD AP 854 with one or more of the stations such as FD STA1 852, FD STA2 856, and FD STA3 858.
  • the AP sometimes may overestimate an intra-BSS collision as shown in Case 2 850b and Case 4 850d; in these cases, FD STA1 and FD STA2 are out of communication range of each other.
  • AP doesn’t know (e.g., does not have information indicating) that FD STA1 and FD STA2 cannot hear each other (are not able to communicate with each other).
  • the AP may estimate there is a collision inside the BSS in these two cases, however, there is no collision, due to the two stations being out of range of one another.
  • the AP is said to have overestimated the collision.
  • Case 1 850a the AP may detect a fake collision when it is transmitting to FD STA1 , and FD STA1 is also transmitting to the AP.
  • the FD AP cannot recognize the receiving PPDll is addressed to itself without decoding the receiver address indicated in the header of the receiving PPDll.
  • AP would stop transmitting once it detects the existence of the interfering preamble. But actually, there is no collision inside the BSS.
  • Case 3 850c the AP can detect a collision when it is transmitting to FD STA1 while FD STA1 is transmitting to FD STA2.
  • the AP hears (detects) the interfering preamble and may stop transmission, thus avoiding the collision on FD STA2.
  • FIG. 31 illustrates an example embodiment 910 of resolving example Case 2 of an overestimated collision of FIG. 30 in which the FD AP has High Priority (HP) traffic to FD STA2, FD STA1 has Low Priority (LP) traffic to FD AP.
  • FD STA1 and FD STA2 are not in communication range with each other, yet both can communicate with the FD AP.
  • FD AP and FD STAs initiate a TXOP with a prioritized control frame, e.g., prioritized RTS (P-RTS).
  • P-RTS prioritized RTS
  • AP broadcasts a new frame (PR+CDP) 912 to declare AP requests for higher priority (with indicating priority level) DATA transmission, (i) AP may indicate collision possibilities in the new (RP+CDP) frame.
  • PR+CDP new frame
  • AP may indicate collision possibilities in the new (RP+CDP) frame.
  • STA1 and STA2 are out of the communication range of each other, which means there is no collision of P-RTSs as mentioned in previous steps.
  • STA2 responds with a P-CTS 914 to the P-RTS sent by AP, which overlaps with the received PR+CDP frame from AP in time.
  • Both STA1 and the AP received the P-CTS from their destinations and start transmitting one or multiple PPDlls 924, 925, 932, 933 to the destination simultaneously with each PPDll start point and end point being aligned.
  • the alignment 922 and 930 of start time of PPDll can be achieved in the following ways: (a) based on predetermined time after AP (as the collision estimator) sends the first P-RTS until it sends P-CTS to STA1 (as the overestimated collider) plus a SIFS. (b) Alignment information can be sent such as PPDll start time can be defined in the PR+CDP frame. [0235] (9) Alignment 922 and 930 of the PPDII length can be achieved in the following ways: (a) Indicated in the first P-RTS; (b) Indicated in PR+CDP frame; (c) Indicated in management frames that exchanges between AP and STAs.
  • AP and STA2 receives the PPDUs 924, 925, 932, 933 and responds with Ack/BA 928, 929, 936 and 937 simultaneously with Ack/BA start point and end point alignment 926 and 934.
  • Ack/BA should not be scheduled when the STA is transmitting PPDII.
  • FIG. 32 through FIG. 35 illustrate an example embodiment 950 FD AP operation if the TXOP is started with a P-RTS, P-CTS combination.
  • a set of checks is performed to determine if a P-RTS was transmitted with priority 952; if a P-RTS was received at the same time 954; does the P-RTS for intra-BSS collision estimation have lower priority 956, if a PR+CDP has been broadcast 958 and if the intra-BSS collision has been overestimated 960. If all of these conditions are met, then at block 962 the AP responds with a P-CTS to the lower priority traffic source.
  • check 960 indicates that the collision was not overestimated, then at block 964 in FIG. 33 the AP retransmits 964 P-RTS with priority indicated, and completes 966 the higher priority traffic TX/RX sequences.
  • a check 968 then decides if it should send a frame to the lower priority traffic source. If the frame should not be sent, then the process ends. Otherwise, if it is decided to send the frame, then in block 970 the lower priority traffic sequences are completed before the process ends.
  • execution moves to block 976 in FIG. 34 with a check to determine if a P-CTS was received before the P-CTS timeout. If the condition was not met, then a P-CTS timeout 984 is registered and the P-RTS is retransmitted 986 before execution returns to start at block 952 of FIG. 32.
  • block 976 the AP sends a PPDll and receives Ack/BA 980, then a check 982 is made to determine whether the TXOP has not yet expired and more PPDll should be sent 982. If more PPDll are to be sent, then execution moves back to block 978; otherwise, execution moves to block 966 of FIG. 33 for completing the higher priority TX/RX sequences.
  • FIG. 36 through FIG. 38 illustrate operation of the FD STA if the TXOP starts with a P-RTS, P-CTS combination.
  • a sequence of checks determines 1012 if a P-RTS has been transmitted; if a P-RTS has been received at the same time and it estimates an intra-BSS collision 1014; and if a PR+CDP frame has been received 1016.
  • the STA sends a frame to the same destination as previously sent P-RTS using CCA to request processing of the following transmission.
  • execution moves to block 1020 which determines if the STA has received a P- RTS frame indicating a higher or equal priority. If the condition is not met, then execution moves to check 1026 of FIG. 37.
  • FD AP 312 has High Priority (HP) traffic for FD STA2 316
  • FD STA1 314 has Low Priority (LP) traffic to FD AP.
  • FD AP, FD STA1 and FD STA2 are in communication range of one another.
  • FD AP and FD STAs initiate a TXOP with a PPDU.
  • STA 1 stops transmitting the remainder of the PPDU to AP after estimating an intra-BSS collision and is seen CCA busy 1120. STA1 waits to sense the channel, or wait for AP’s response, or a trigger frame to perform the next transmission.
  • AP may reserve some RUs (represented by lower shaded region of the PPDU blocks) to transmit select control messages to other STAs which are not the destination of the current PPDU frames. If the colliding preamble indicates a higher priority than the traffic of the AP, then the process is performed as introduced in example 3-3 and 3-4 which will be described in latter sections.
  • STA2 receives DL PPDU 1122 from the AP and can respond with an Ack/BA 1124, 1126, to the AP during its reception.
  • the time to respond to the Ack/BA should follow the schedule (if any) which could be set in the BAR or other control/management frames.
  • AP does not receive an Ack/BA from STA2 after/during the retransmission of PPDII and may send a trigger frame 1128 to STA1 to enable STA1 to access the channel.
  • STA1 doesn’t receive a PPDII from the AP, nor from STA2 with a destination to the AP which can access the channel again after EDCA backoff by sending for example a control frame or retransmitted PPDII to the AP or wait for a trigger frame from the AP to start transmitting TB-PPDU.
  • STA1 senses CCA busy 1120, and thus waits to access the channel for (re)transmit PPDII unless it receives a trigger from the AP to enable STA1 to access channel.
  • STA2 sends ACKs 1124 and 1126.
  • AP sends a trigger to STA1 1128.
  • STA1 sends preamble (LP) 1132 PPDII 1134.
  • AP responds to STA1 with Acks 1136 and 1138; during which STA2 is CCA busy 1130.
  • FIG. 40 illustrates an example embodiment 1210 of the AP with HP, STA1 with LP. STA1 and STA2 are not in communication range. The process starts with a DATA PPDII.
  • STA1 stops transmitting the remainder of the PPDII to the AP after estimating the intra-BSS collision, it recognizes that a colliding preamble exists which indicates a higher priority traffic than its priority. STA1 should wait to sense the channel or wait for AP’s response or trigger frame 1222 to perform the next transmission.
  • the AP After the AP estimates the intra-BSS collision, if the colliding preamble indicates a lower priority than the traffic of the AP, then the AP retransmits 1220 the PPDII to STA2 immediately, or maybe a PIFS after receiving the colliding preamble.
  • the AP may reserve some Rlls (shown in the shaded portion of the PPDII) to transmit control messages to some other STAs, which are different from the destination of the ongoing transmitting PPDUs.
  • AP receives the control frame 1218 from STA2 in the reserved Rlls during which the AP may be transmitting a DL PPDU to STA2.
  • the AP may then send a trigger frame (e.g., PR+CDP) to STA1 using the reserved RU to trigger preamble 1224 with UL PPDU 1226 from STAI .
  • the trigger frame should contain the PPDU end point alignment information to align the end point of the TB PPDU from STA1 to AP and the UL PPDU from AP to STA2.
  • STA1 receives the control frame from the AP in the reserved RU to trigger UL PPDU 1220, it should transmit UL PPDU 1224, 1226 following the PPDU end point alignment 1225 rule from the received control frame.
  • AP and STA2 receives the PPDUs 1220, 1226 and should respond with an Ack/BA 1230 and 1231 , simultaneously with Ack/BA start point and end point alignment 1228.
  • the Ack/BA should not be scheduled when the STA is transmitting PPDU.
  • FIG. 41 illustrates an example embodiment 1310 of this Example 3-3, in exemplifying an HP traffic grant for a PPDU initiated TXOP when the AP has low priority.
  • the topology is shown as Case 2 of FIG. 30.
  • the FD AP 312 has Low Priority (LP) traffic to send to FD STA2 316, while FD STA1 314 has High Priority (HP) traffic to send to FD AP.
  • FD STA1 and FD STA2 are not in range of each other, but both are in communication range of the FD AP.
  • the FD AP and FD STAs initiate TXOP with PPDU.
  • STA1 (higher priority) sends a preamble 1314 to the associated AP, indicating the priority of the traffic.
  • AP (lower priority) also sends preamble 1312 to STA2 indicating the priority of the traffic.
  • STA1 stops transmitting the PPDU (to avoid any possible further collision) after estimating the intra-BSS collision based on the transmitted and received preambles at the same time. If STA1 has higher priority, it may immediately retransmit a new preamble 1318 and PPDU 1322 to the AP or retransmit the PPDU a PIFS after received the colliding preamble. STA1 may reserve some RUs (as shown in shaded area of the PPDU) for AP to exchange control massages with other STAs.
  • AP receives UL PPDU 1322 from STA1 and can respond with
  • Ack/BA 1324 to STA1 during its reception.
  • the time to respond with an Ack/BA should follow a schedule (if any), which can be set in the BAR or other control/management frames.
  • the AP can access the channel again after EDCA backoff to send a retransmitted preamble 1326, and PPDU 1330 to STA2, to be responded to by Ack/BA 1332 and 1334. During this time STA1 sees CCA busy.
  • FIG. 42 illustrates an example embodiment 1410 with the FD AP 312 having LP, the FD STA1 314 with HP, and FD STA2 316.
  • STA1 and STA2 are not in range of one another, but are in range of the AP.
  • the example commences with a DATA PPDU.
  • the topology is like that shown in FIG. 30 Case 2 850b, the only difference being that the AP has LP to STA2 and STA1 has HP to the AP.
  • the FD AP has Low Priority (LP) traffic to FD STA2, FD STA1 has High Priority (HP) traffic to FD AP.
  • FD STA1 and FD STA2 cannot communicate with each other, but both can communicate with FD AP.
  • FD AP and FD STAs initiate TXOP with PPDU.
  • STA1 (higher priority) sends a preamble 1414 to the associated AP, indicating the priority of the traffic.
  • the AP (lower priority) also sends preamble 1412 to STA2 with indicating the priority of the traffic.
  • STA1 stops transmitting the remainder of the PPDU 1414 (to avoid any possible further collision) after estimating the intra-BSS collision based on the transmitted and received preambles. If STA1 has higher priority, then STA1 may immediately retransmit the preamble 1418 and PPDU 1426 or retransmit the PPDU a PIFS after receiving the colliding preamble. STA1 may reserve some RUs (as shown in the shaded portion of the PPDU) for the AP to exchange control messages with the other STAs.
  • STA2 receives the preamble from the AP without the remainder of the DATA PPDII. If STA2 doesn’t receive anything and the channel is idle for another preamble duration and perhaps plus a PIFS interval, STA2 may send the AP a control frame immediately or with another SIFS delay using the reserved Rlls, to indicate it receives the preamble.
  • AP receives the control frame 1422 from STA2 on reserved Rlls, which indicates it overestimated the intra-BSS collision.
  • the AP may retransmit the preamble 1424 and PPDII 1428 to STA2, which is the destination of the over-estimated intra-BSS collision.
  • AP shall transmit DL PPDII to STA2 with PPDII having end point alignment with the received UL PPDII from STAI .
  • AP and STA2 receives the PPDlls and should respond with
  • Ack/BAs 1430 and 1431 simultaneously with Ack/BA start point and end point alignment. Ack/BA should not be scheduled when the STA is transmitting PPDlls. There are several ways to achieve this: (a) Transmit a BA request in the end of each PPDII transmission. Utilize BA only responses after a received BA request (BAR), (b) Configure this in the control frames, such as PR+CDP frame or other management frames that exchanges between AP and STAs for reconfiguration.
  • the figure shows additional PPDUs with preamble 1432 and PPDU 1436 to STA2, and preamble 1434 and PPDU to AP 1436, followed by Acks 1438 and 1439.
  • FIG. 43 through FIG. 45 illustrate an example embodiment 1470 of a FD AP starting a TXOP with the DATA PPDU.
  • the AP estimates an intra-BSS collision has lower priority than itself.
  • the AP retransmits the PPDU with a reserve of some RUs for other STAs. Then in check 1476 a check determines if the AP received a control frame from the destination through reserved RUs, indicating overestimation of the intra-BSS collision.
  • the AP sends a control (trigger) frame in reserved RUs to trigger estimated colliding STA to send a Trigger-Based PPDU (TB-PPDU). Then at block 1484 the AP maintains a PPDU end point and/or start point alignment and Ack/BA alignment under a schedule, if there is one, and the process ends.
  • a control (trigger) frame in reserved RUs to trigger estimated colliding STA to send a Trigger-Based PPDU (TB-PPDU).
  • TB-PPDU Trigger-Based PPDU
  • execution reaches block 1478 in FIG. 44 to finish the current PPDII transmission sequences, and sends a trigger to another STA which was estimated to be the colliding STA with lower priority. Then in block 1480, the AP sends an Ack/BA in response to the received PPDII, and the process ends.
  • execution reaches block 1486 in FIG. 45, where the AP stops transmitting the remainder of the PPDII. Then at check 1488 the AP determines if it has received a control frame from the destination STA through the reserved Rlls, indicating over estimation of the Intra-BSS collision.
  • the AP retransmits the DL PPDII during which it may be receiving a LIL PPDII, with execution moving to block 1484 in FIG. 44.
  • the AP sends an Ack/BA in response of the received PPDII, after which in block 1494 the AP finishes the current PPDII transmission sequences, that may send a trigger to the other STA, which was estimated as colliding STA with lower priority, and the process ends.
  • FIG. 46 and FIG. 47 illustrates an example embodiment 1510 of a non- AP STA starting the TXOP with a DATA PPDII.
  • a check 1512 determines if the non-AP STA has received a preamble without the remainder of the DATA PPDII. If this condition is met, then at block 1520 the STA sends a control frame using reserved Rlls to indicate an overestimated intra-BSS collision, then in block 1522 the non-AP STA sends an Ack/BA in response to the PPDU, and the process ends.
  • the STA retransmits PPDU with reserving some RUs for other STAs, and in block 1518 the STA maintains the PPDU end point and/or start point alignment and Ack/BA alignment under a schedule (if there is a schedule), and the process ends.
  • execution reaches block 1524 in FIG. 47 and the STA stops transmitting the remainder of the PPDU.
  • a check 1526 determines if a control frame has been received from the destination STA (AP) through reserved Rlls, or non-reserved Rlls, that triggered the UL PPDU.
  • the STA retransmits PPDU after EDCA backoff when channel is CCA Idle, if it is not able to receive frame exchanges between other STAs, and the process ends.
  • execution moves from check 1526 to block 1528 with the STA retransmitting the UL PPDU, before moving to block 1518 in FIG. 46.
  • bits 14 (B14) of the HE-SIG-A field of an HE SU PPDU and HE ER SU PPDU is reserved.
  • Bit 7 (B7) of HE-SIG-A field of an HE MU PPDU is reserved. In both cases, these reserved bits can be utilized to indicate priority High (stage 1 ) and priority Low (stage 0).
  • priority information in the FD Preamble following the legacy preamble was shown in FIG. 5.
  • a priority subfield can be contained in the FD Preamble field.
  • different priorities can be embedded in different subcarrier/subcarriers with certain space (i.e. , at least 40ppm) in between on top of the tones corresponding to the bits range of FD Preamble field.
  • FIG. 48 illustrates an example of a P-RTS frame 1590.
  • FD STAs may initiate a TXOP with sending a P-RTS frame, which indicates the priority of the traffic that the transmitting STA requests to send and some scheduling information such as PPDU alignment.
  • a STA receiving a P-RTS frame should recognize the traffic priority required, and should follow the PPDU or/and the Ack alignment rules as request in this frame.
  • Frame Control indicates frame control information corresponding to different frame types. Duration/ID field sets a NAV value at receiving STAs that protects up to the end of any following Data, Management, or response frame plus any additional overhead frames in single protection; otherwise, it sets a NAV that protects up to the estimated end of a sequence of multiple frames in multiple protection.
  • RA field of this frame is the address of the STA that is the intended immediate recipient TA field is the address of the STA transmitting this frame.
  • Priority field indicates the priority specified in the RTS frame.
  • FCS field for error-detection that contains a 32-bit CRC.
  • PR control field indicates the Priority Request information and the corresponding control information for the following process after sending/receiving this frame.
  • FIG. 49 illustrates an example embodiment 1610 of a PR Control field from FIG. 48.
  • a Priority Request subfield indicates the priority of the traffic that the STA who sent this frame requests to transmit.
  • PPDll and ACK SYN request subfield if set 1 , the STAs that sends or receives this frame should align the start point of PPDll and aligns the start point of Ack/BA as the response of per received PPDll.
  • a PPDU Start Time subfield indicates the options of starting PPDU TX/RX after TX/RX this frame. If set as 0: means no specific start time indicated, STA starts sending PPDU a SIFS after completing all control frame exchanges with its destination, (e.g., from sending P-RTS to receiving P-CTS as the response of P-RTS). If set as 1 : indicates a specific start time. For example, after 1 PR+CDP frame duration + SIFS+ 1 CTS frame duration + SIFS for FD STAs after receiving this frame. For FD STAs that sends this frame, it needs to add one more SIFS to the previous calculation since it starts counting after it transmits this frame.
  • PPDU Duration Alignment subfield set as 1 to indicate the PPDU shall be padded to end at the same time, as indicated by the L-SIG field of the preamble.
  • FIG. 50 illustrates an example embodiment 1630 of a P-CTS frame.
  • FIG. 51 illustrates an example embodiment 1650 of the PR control field shown in FIG. 50.
  • the PR control field indicates the Priority Request information for the following process after sending/receiving this frame.
  • the priority request subfield indicates which priority this P-CTS is a response for, which should be the same as the priority specified in the responded P-RTS frame.
  • FIG. 52 illustrates an example embodiment 1670 of a PR+CDP frame.
  • a FD AP may broadcast a new frame (PR+CDP) to declare AP requests for higher priority (with indicating priority level) DATA transmission, it may also indicate scheduling rules such as PPDll alignment and/or ACK alignment in this frame.
  • PR+CDP new frame
  • FIG. 53 illustrates an example embodiment 1690 of a PR+CDP control field.
  • PR+CDP control field indicates the Priority Request and Collision Detection Probability information and the corresponding control information for the following process after sending/receiving this frame.
  • a Priority Request subfield indicates the priority the STA that sent this frame requests to process at first.
  • a Collision Detection Probability subfield indicates the estimated probability of an intra-BSS collision, possible values are 0 or 1 .
  • a PPDll and ACK SYN request subfield can be set to 1 to indicate that the STAs sending or receiving this frame should align the start point of PPDll and align the start point of ACK as the response of per received PPDU.
  • PPDU Start Time subfield indicates the options of starting TX/RX PPDU after TX I RX this frame. If set as 0: means no specific start time indicated, STA starts sending PPDU a SIFS after completing all previous control frame exchange with its destination, (from sending RTS to receiving CTS and may include additional frame exchanges that used to cancel overestimation of collision detection).
  • PPDU Duration Alignment subfield set to 1 for indicating that the PPDll shall be padded to end at the same time as indicated by the L-SIG field of the preamble. Other fields are same as that defined in P-RTS frame.
  • 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).
  • programming or “program executable” as used herein 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 station (STA), wirelessly communicating with other STAs on a wireless local area network (WLAN) in an IEEE 802.11 protocol configured for supporting carrier sense multiple access I collision avoidance (CSMA/CA); (b) a processor of said STA;
  • a non-transitory memory storing instructions executable by the processor for communicating with other STAs and fulfilling different roles of a communications protocol; and (d) wherein said instructions, when executed by the processor, perform one or more steps of a preamble-based collision detection comprising: (d)(i) generating an orthogonal preamble by the STA, which is a full-duplex (FD) STA, said orthogonal preamble containing embedded traffic priority information, and processing preambles comprising:
  • An apparatus for wireless communication in a network comprising: (a) a wireless communication circuit, as a station (STA), wirelessly communicating with other STAs on a wireless local area network (WLAN) in an IEEE 802.11 protocol configured for supporting carrier sense multiple access I collision avoidance (CSMA/CA); (b) a processor of said STA; (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs and fulfilling different roles of a communications protocol; and (d) wherein said instructions, when executed by the processor, perform one or more steps of a preamble-based collision detection comprising: (d)(i) generating orthogonal preambles, which are orthogonal in a time domain and/or a frequency domain, by the STA which is an FD STA, which contain embedded traffic priority information, and processing preambles comprising: (d)(i)(A) upon detecting a colliding preamble with lower priority than its own priority, the STA retransmit
  • a method of wireless communication in a network comprising: (a) a wireless communication circuit, as a station (STA), wirelessly communicating with other STAs on a wireless local area network (WLAN) in an IEEE 802.11 protocol configured for supporting carrier sense multiple access I collision avoidance (CSMA/CA) configured for performing roles in preamble-based collision detection; (b) generating orthogonal preambles by the STA, which is an FD STA, which contain embedded traffic priority information, and processing preambles comprising: (b)(i) upon detecting a colliding preamble with lower priority than its own priority, the STA retransmits the preamble and its associated physical layer protocol data unit (PPDII); (b)(ii) upon detecting a colliding preamble with equal or higher priority than its own priority, or with no priority, the STA stops its transmissions and starts a backoff after sensing the medium is idle; and (b)(iii) continuing transmitting the remainder of a PPDII
  • a WLAN apparatus comprising: (a) full-duplex (FD) stations (STA) enabled with new preamble-based collision detection without performing selfinterference (SI) estimation, and provides new collision resolution estimation and scheduling for prioritized communication; (b) detecting collisions faster using orthogonal preambles without performing self-interference channel estimation; (c) embedding priority information in preambles; (d) priority levels can be predetermined and agreed upon by all FD STAs, and may be embedded in a FD preamble field, such as following the legacy preamble field defined in 802.11 ; (e) detecting the colliding preamble with lower priority than its own priority, and retransmit the preamble and its PPDU; otherwise stopping transmission and starting a backoff after sensing that the channel is idle; (f) detecting, by an FD STA, a collision without detecting the priority of the colliding preamble, wherein the STA should stop transmission and start a backoff after sensing that the channel is idle; and (g) FD
  • orthogonal preambles are orthogonal in a time domain, or in a frequency domain, or in both the time domain and the frequency domain.
  • orthogonal preambles in the time domain carry orthogonal priority signals which are orthogonal to other priority signals carried by preambles of other STAs.
  • the FD STA may initiate a transmit opportunity (TXOP) with a ready-to-send (RTS), clear-to-send (CTS), message exchange.
  • TXOP transmit opportunity
  • RTS ready-to-send
  • CTS clear-to-send
  • intra-BSS intra-basic service set
  • each FD STA on the network performs actions depending on which traffic priority is being processed: (i) when processing lower priority traffic than the requested priority, they stop any transmissions and retransmissions; and (ii) when processing higher, or equal, priority traffic than the requested priority, each FD STA continues their respective transmitter and receiver processing.
  • said STA is an FD access point (AP) which triggers non-AP FD STAs on the network to initiate transmissions of lower prioritized traffic, allowing these non- AP FD STAs with lower prioritized traffic to re-access the channel without the need of being triggered, if the channel is idle for at least a PIFS duration after the non-AP FD STA receives a broadcast frame, which indicates a higher prioritized traffic is preferred.
  • AP FD access point
  • the FD STA that broadcasted a frame with requested priority information then transmits another frame to estimated colliding FD STAs on the network, which have lower priority traffic, indicating they may commence lower priority traffic transmission and reception.
  • intra-basic-service-set (intra-BSS) collisions and make process decisions based on priority resolution as follows: (a) when existence of an intra-BSS collision with lower priority than itself is estimated, then the PPDU is retransmitted; (b) when existence of an intra-BSS collision with higher priority than itself is estimated, then transmission of the PPDU is stopped, unless a control frame was received from the reserved RU or the non-reserved RUs; and (c) when a preamble is received without a DATA PPDU portion, then a control frame is transmitted over reserved RUs to indicate there is an overestimated intra-BSS collision.
  • intra-BSS intra-basic-service-set
  • each FD STA on the network performs actions depending on which traffic priority being processed: (i) when processing lower priority traffic than the requested priority, they stop any transmissions and retransmissions; and (ii) when processing higher, or equal, priority traffic than the requested priority, each FD STA continues their respective transmitter and receiver processing.
  • each STA Transmits FD preamble of the PPDU that carries the priority signals that is orthogonal to other priority signals carried by the other STA’s FD preamble; and the orthogonal priority signals are preconfigured; and (ii) the application requests central frequency synchronization between transmitters.
  • priority information can be embedded in different subcarriers at least 40 ppm apart on frequency domain of the FD preamble; (ii) in baseband after analog cancellation and before digital cancellation (note that the digital cancellation requires SI channel estimation), STA zeros out the tones of its own FD preamble to discover other STAs with a different priority; (iii) as this application is CFO tolerance, a request may not be made for central frequency synchronization between transmitters.
  • an FD STA may initiate the TXOP with RTS/CTS exchange: (a) FD STA that estimates an existing of intra-BSS interference may broadcast a frame to indicate the preferred priority it requests to process at the first place; (b) After receiving the frame indicating the request traffic priority, FD STAs perform differently depend on the traffic priorities they are processing: (i) For FD STAs dealing with lower priority traffic than the requested priority, they shall stop any transmission I retransmission; (ii) For FD STAs dealing with higher/same priority traffic than the requested priority, they should continue their TX/RX process; (c) an FD AP may trigger non-AP FD device to initiate the transmission of lower prioritized traffic; wherein the non-AP FD device with lower prioritized traffic may re-access channel, without being triggered, if the channel is idle for at least a PIFS duration after the non-AP FD device receives the broadcast frame, which indicating a higher prioritized
  • the apparatus or method of any preceding implementation wherein in the FD STA that stops (re)transmission after receiving a broadcasted frame w/ higher request priority than its own priority, may access the medium if it doesn’t receive or detect any frames from STAs that dealing with the requested priority traffic after a certain time, e.g., 1 PIFS after stops (re)transmission.
  • the alignment of start time of PPDII can be achieved in: (a) based on the predetermined time after the collision detecting STA sends the 1 st frame e.g., P-RTS till it receives a response frame e.g., P-CTS with an additional SIFS; (b) an alignment information, e.g., PPDII start time can be defined in the broadcasted frame that indicating the request priority.
  • Ack/BA alignment could be achieved by: (a) sending a BA request with each PPDU, FD STA only response BA when receives BA request; (b) configuring as claimed in a previous claim in the first frame to start new TXOP, e.g., P-RTS; or in the broadcasted frame that indicating the request priority or in a management frame that exchangeable between AP and STAs.
  • TXOP e.g., P-RTS
  • a FD device estimates the existing of an intra-BSS collision with lower priority than itself should retransmit the PPDU; and wherein a portion of the RUs may be reserved not for serving DATA PPDUs for this device but for exchange control massages between AP and other STAs;
  • a FD device estimates the existing of an intra-BSS collision with higher priority than itself should stop transmitting the rest of the PPDII, unless it receives a control frame from the reserved Rll or the non-reserved Rlls, e.g., trigger from its destination.
  • this STA may access the channel again after EDCA backoff when CCA idle; and wherein (c) a FD device only receives a preamble without the rest of the DATA PPDII may send a control frame using the reserved Rlls (could be predetermined Rlls) to indicated there is an overestimated intra-BSS collision; wherein if the preamble source STA receives this control frame through the reserved Rlls, it may retransmit or trigger (through reserved Rlls) the retransition of the previously terminated PPDlls with lower priority which has been overestimated as the intra-BSS colliding signal.
  • Rlls could be predetermined Rlls
  • Ack/BA alignment could be achieved by: (a) Send BA request with each PPDII, FD STA only response BA when receives BA request; (b) configure that as in a previous claim, in the first frame to start new TXOP; or in the control frame that indicating the request priority or in a management frame that exchangeable between AP and STAs.
  • phrases “a,” “an,” and “the” may include plural referents unless the context clearly dictates otherwise. Reference to an object in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more.”
  • 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 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)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un mécanisme de détection de collision basé sur un préambule est destiné à être utilisé dans des réseaux locaux sans fil (WLAN), présentant une ou plusieurs stations en duplex intégral (FD). De plus, un nouveau mécanisme d'estimation et de planification de résolution de collision est décrit pour une communication priorisée. Ces techniques peuvent permettre une détection et une résolution de collision plus rapides, sans avoir besoin d'effectuer une estimation d'auto-brouillage (SI). Les techniques comprennent l'utilisation de préambules orthogonaux, dans le domaine temporel et/ou le domaine fréquentiel, dans lesquels des stations FD incorporent des informations de priorité.
EP22778064.0A 2021-09-09 2022-09-06 Détection de collision et résolution de collision pour une communication en duplex intégral priorisée Pending EP4378265A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US202163261062P 2021-09-09 2021-09-09
US17/819,285 US12273920B2 (en) 2021-09-09 2022-08-11 Collision detection and collision resolution for prioritized full duplex communication
PCT/IB2022/058377 WO2023037245A1 (fr) 2021-09-09 2022-09-06 Détection de collision et résolution de collision pour une communication en duplex intégral priorisée

Publications (1)

Publication Number Publication Date
EP4378265A1 true EP4378265A1 (fr) 2024-06-05

Family

ID=83853068

Family Applications (1)

Application Number Title Priority Date Filing Date
EP22778064.0A Pending EP4378265A1 (fr) 2021-09-09 2022-09-06 Détection de collision et résolution de collision pour une communication en duplex intégral priorisée

Country Status (4)

Country Link
EP (1) EP4378265A1 (fr)
JP (1) JP7733137B2 (fr)
KR (1) KR20230134602A (fr)
WO (1) WO2023037245A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025079944A1 (fr) * 2023-10-10 2025-04-17 삼성전자 주식회사 Dispositif électronique pour déterminer une politique de transmission de message de réponse d'une liaison, et procédé de fonctionnement de dispositif électronique

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3938916B2 (ja) * 2003-10-16 2007-06-27 株式会社国際電気通信基礎技術研究所 無線ネットワークのための制御方法及び制御装置
US9723621B2 (en) * 2012-10-19 2017-08-01 Qualcomm Incorporated Priority assignment in FlashLinQ distributed scheduling algorithm to fine-tune performance
TWI618437B (zh) * 2016-11-01 2018-03-11 財團法人資訊工業策進會 無線裝置、基地台、用於無線裝置之隨機存取方法及用於基地台之前置碼配置方法
JP2018152723A (ja) * 2017-03-13 2018-09-27 株式会社東芝 無線通信装置および無線通信方法
TWI638533B (zh) * 2017-07-10 2018-10-11 瑞昱半導體股份有限公司 無線通訊裝置
US11356900B2 (en) * 2019-07-03 2022-06-07 Sony Group Corporation Reserving future channel time for handling of real time application (RTA) packets on wireless local area network

Also Published As

Publication number Publication date
KR20230134602A (ko) 2023-09-21
JP2024522804A (ja) 2024-06-21
WO2023037245A1 (fr) 2023-03-16
JP7733137B2 (ja) 2025-09-02

Similar Documents

Publication Publication Date Title
US12432778B2 (en) Preemption / interruption of an ongoing low priority PPDU
US10484162B2 (en) Full duplex transmission setup and release mechanism
CN104301086B (zh) 无线网络中的全双工操作
US10492223B2 (en) Channel access for multi-user communication
US10411850B2 (en) Apparatus and method for network allocation vector operations
US10285203B2 (en) Network allocation vector types and transmission opportunity types for spatial reuse
CN115152305A (zh) 由non-ap sta发起的请求触发帧和txop共享
CN116368914A (zh) 对移动软接入点多链路设备的二级链路接入
AU2015244516B2 (en) Retransmission method at time of sharing transmission opportunity in wireless lan system, and device therefor
CN104780618A (zh) 利用码分复用的争用仲裁
JP2019500801A (ja) アクセス方法及び装置
JP7739604B2 (ja) 進行中の低優先度ｐｐｄｕのプリエンプション／中断
CN104717760A (zh) 全双工传输建立和释放机制
CN113475152B (zh) 通信装置和方法
US12273920B2 (en) Collision detection and collision resolution for prioritized full duplex communication
US11464050B2 (en) Timer for non-simultaneous T/R multi-link device accessing of the channel
CN116803184A (zh) 正在进行的低优先级ppdu的抢占/中断
CN114258644B (zh) 用于网络中的无线通信的装置和方法
Ma et al. MAC protocol for ad hoc networks using smart antennas for mitigating hidden and deafness problems
WO2023037245A1 (fr) Détection de collision et résolution de collision pour une communication en duplex intégral priorisée
Ahn et al. Hidden chain: A full-duplex mac protocol using hidden terminal relationships in wlans
CN117121616A (zh) 用于优先化的全双工通信的冲突检测和冲突解决
WO2023122463A1 (fr) Résolution d'un problème de collision factice dans une communication en duplex intégral
US12382498B2 (en) Resolving fake collision issue in full duplex communication
KR20260057191A (ko) 다중 ap txop 공유를 위한 기법들

Legal Events

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

Free format text: STATUS: UNKNOWN

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

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

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20240229

AK Designated contracting states

Kind code of ref document: A1

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

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SONY GROUP CORPORATION

Owner name: SONY CORPORATION OF AMERICA