阅读说明：本技术 请求发送（rts）帧/允许发送（cts）帧和传输规则 (Request To Send (RTS) frame/Clear To Send (CTS) frame and transmission rules ) 是由 S·K·杨 江津菁 刘勇 J·L·克内科特 伍天宇 王�琦 L·维尔马 于 2021-04-26 设计创作，主要内容包括：本公开涉及请求发送(RTS)帧/允许发送(CTS)帧和传输规则。本公开的一些方面包括用于实现请求发送(RTS)帧和允许发送(CTS)帧以及用于RTS帧和CTS帧的传输规则的装置和方法。例如,一些方面涉及一种电子设备,该电子设备包括收发器和通信地耦接到该收发器的一个或多个处理器。一个或多个处理器使用收发器从第二电子设备接收请求发送(RTS)帧,并且使用所接收的RTS帧确定要响应于RTS帧使用的允许发送(CTS)帧的格式。一个或多个处理器还基于在其上接收到RTS帧的至少一个子信道上所确定的格式并且基于至少一个子信道是空闲的来使用收发器传输CTS帧。(The present disclosure relates to Request To Send (RTS) frames/Clear To Send (CTS) frames and transmission rules. Some aspects of the present disclosure include apparatus and methods for implementing Request To Send (RTS) and Clear To Send (CTS) frames and transmission rules for RTS and CTS frames. For example, some aspects relate to an electronic device that includes a transceiver and one or more processors communicatively coupled to the transceiver. The one or more processors receive, using the transceiver, a Request To Send (RTS) frame from the second electronic device and determine, using the received RTS frame, a format of a Clear To Send (CTS) frame to be used in response to the RTS frame. The one or more processors also transmit, using the transceiver, a CTS frame based on the determined format on the at least one subchannel on which the RTS frame was received and based on the at least one subchannel being idle.)

1. An electronic device, comprising:

a transceiver configured to communicate with a second electronic device; and

one or more processors communicatively coupled to the transceiver and configured to:

receiving, using the transceiver, a request-to-send (RTS) frame sent by the second electronic device;

determining, based at least on the received RTS frame, a Clear To Send (CTS) frame format to be transmitted in response to the RTS frame; and

transmitting, using the transceiver, a CTS frame based at least on the determined CTS frame format, wherein the CTS frame is transmitted on at least one subchannel on which the RTS frame is received when the at least one subchannel is idle.

2. The electronic device of claim 1, wherein to determine the CTS frame format, the one or more processors are further configured to:

determining whether the RTS frame is transmitted only to the electronic device.

3. The electronic device of claim 2, wherein in response to determining that the RTS frame is transmitted only to the electronic device, the CTS frame is configured to include a channel bitmap field indicating the at least one sub-channel on which the CTS frame is transmitted.

4. The electronic device of claim 1, wherein to determine the CTS frame format, the one or more processors are further configured to:

processing a subfield of the RTS frame, the subfield representing the CTS frame format indicated by the second electronic device.

5. The electronic device of claim 1, wherein to transmit the CTS frame, the one or more processors are further configured to:

transmitting, using the transceiver, the CTS frame on a plurality of subchannels on which the RTS frame is received based at least on determining that the plurality of subchannels are idle and that the plurality of subchannels generate a large Resource Unit (RU) aggregation mode.

6. The electronic device of claim 1, wherein the one or more processors are further configured to determine that the at least one sub-channel is clear using a high-efficiency HE Clear Channel Assessment (CCA) mechanism.

7. The electronic device of claim 6, wherein the HE CCA mechanism comprises at least one of a virtual Carrier Sense (CS) mechanism or an energy detection mechanism during a period of time after receiving the RTS frame.

8. The electronic device of claim 1, wherein the one or more processors are configured to transmit the CTS frame on a plurality of subchannels on which the RTS frame is received and idle, and wherein the CTS frame is not transmitted on a punctured subchannel.

9. The electronic device of claim 1, wherein the RTS frame comprises a high-efficiency HE multi-user MURTS frame.

10. A method, comprising:

receiving, at the first electronic device and on the at least one sub-channel, a request to send, RTS, frame sent by the second electronic device;

determining, based at least on the received RTS frame, a Clear To Send (CTS) frame format to be transmitted in response to the RTS frame;

determining that the at least one sub-channel is idle; and

transmitting a CTS frame to the second electronic device based at least on the determined CTS frame format, wherein the CTS frame is transmitted on the at least one sub-channel on which the RTS frame is received when the at least one sub-channel is idle.

11. The method of claim 10, wherein determining the CTS frame format further comprises determining whether the RTS frame is transmitted only to the first electronic device.

12. The method of claim 11, wherein in response to determining that the RTS frame is transmitted only to the first electronic device, the CTS frame is configured to include a channel bitmap field indicating the at least one sub-channel on which the CTS frame is transmitted.

13. The method of claim 10, wherein determining the CTS frame format further comprises processing a subfield of the RTS frame that represents the CTS frame format indicated by the second electronic device.

14. The method of claim 10, wherein determining that the at least one sub-channel is clear comprises using a high-efficiency HE Clear Channel Assessment (CCA) mechanism, wherein the HE CCA mechanism comprises at least one of a virtual Carrier Sense (CS) mechanism or an energy detection mechanism during a period of time after receiving the RTS frame.

15. An electronic device, comprising:

a transceiver configured to communicate with a second electronic device; and

one or more processors communicatively coupled to the transceiver and configured to:

generating a request to send RTS frame, wherein the RTS frame includes a first subfield and a second subfield to indicate a bandwidth BW associated with the RTS frame;

determining that at least one subchannel is idle; and

transmitting, using the transceiver, the RTS frame to the second electronic device on the at least one sub-channel.

16. The electronic device of claim 15, wherein the RTS frame further comprises a common information field, wherein the first subfield is in the common information field and the second subfield is in the special user information field.

17. The electronic device of claim 15, wherein to transmit the RTS frame, the one or more processors are further configured to:

transmitting the RTS frame on the at least one subchannel when the at least one channel is idle and the at least one subchannel results in a large RU aggregation mode in which 242 or more RUs are aggregated in the RTS frame.

18. The electronic device of claim 15, wherein the RTS frame comprises a high-efficiency HE multi-user MU RTS frame.

19. The electronic device of claim 15, wherein the BW associated with the RTS frame comprises one of 320MHz, 160+160MHz, 240MHz, or 160+80 MHz.

20. The electronic device of claim 19, wherein the RTS frame comprises a special user information field comprising an association identifier, AID, having a predefined value.

Technical Field

Aspects described herein generally relate to channel access in wireless communications. For example, aspects of the present disclosure relate to Request To Send (RTS) frames, Clear To Send (CTS) frames, and transmission rules for RTS and/or CTS frames.

RELATED ART

Request To Send (RTS) and Clear To Send (CTS) are mechanisms that may be used at a communication system (e.g., a wireless communication system) to reduce data collisions by, for example, reserving a channel. For example, a first Station (STA) (e.g., a transmitting STA) having data to transmit sends an RTS frame on a channel to a second STA (e.g., a receiving STA). After receiving the CTS frame, and for example after a period of time (e.g., SIFS), the transmitting STA sends its data on the channel to the receiving STA.

Background

Disclosure of Invention

Some aspects of the present disclosure include apparatus and methods for implementing Request To Send (RTS) and Clear To Send (CTS) frames and transmission rules for RTS and CTS frames. For example, some aspects of the present disclosure relate to puncturing RTS transmission rules. Some aspects relate to puncturing CTS transmission rules. Some aspects of the present disclosure relate to RTS and CTS frames. In addition, some aspects of the present disclosure relate to Clear Channel Assessment (CCA) rules for RTS and CTS. According to some aspects, RTS/CTS frames and transmission rules are discussed with respect to a large Resource Unit (RU) (e.g., greater than or equal to 242 subcarriers and/or greater than or equal to 20MHz bandwidth) aggregation mode in Orthogonal Frequency Division Multiple Access (OFDMA) and/or non-OFDMA transmissions.

Some aspects relate to an electronic device. The electronic device includes a transceiver configured to communicate with a second electronic device and one or more processors communicatively coupled to the transceiver. The one or more processors receive, using the transceiver, a Request To Send (RTS) frame from the second electronic device and determine, using the received RTS frame, a format of a Clear To Send (CTS) frame to be used in response to the RTS frame. The one or more processors also transmit, using the transceiver, a CTS frame based on the determined format on the at least one subchannel on which the RTS frame was received and in response to the at least one subchannel being idle.

Some aspects relate to a method that includes receiving, at a first electronic device and on at least one sub-channel, a Request To Send (RTS) frame from a second electronic device. The method also includes determining, using the received RTS frame, a format of a clear-to-send (CTS) frame to be used in response to the RTS frame. The method also includes determining that at least one sub-channel is idle, and transmitting a CTS frame to the second electronic device based on the determined format on the at least one sub-channel on which the RTS frame was received and in response to the at least one sub-channel being idle.

Some aspects relate to a non-transitory computer-readable medium storing instructions. When executed by a processor of an electronic device, the instructions cause the processor to perform operations including receiving, at the electronic device and on at least one sub-channel, a Request To Send (RTS) frame from a second electronic device. The operations also include determining, using the received RTS frame, a format of a clear-to-send (CTS) frame to be used in response to the RTS frame. The operations also include determining that at least one sub-channel is idle, and transmitting a CTS frame to the second electronic device based on the determined format on the at least one sub-channel on which the RTS frame was received and in response to the at least one sub-channel being idle.

Some aspects relate to an electronic device. The electronic device includes a transceiver configured to communicate with a second electronic device and one or more processors communicatively coupled to the transceiver. One or more processors generate a Request To Send (RTS) frame, wherein the RTS frame includes a first subfield and a second subfield to indicate a Bandwidth (BW) associated with the RTS frame. The one or more processors also determine that the at least one subchannel is idle and transmit, using the transceiver, an RTS frame to the second electronic device on the at least one subchannel.

Some aspects relate to a method that includes generating a Request To Send (RTS) frame, wherein the RTS frame includes a first subfield and a second subfield to indicate a Bandwidth (BW) associated with the RTS frame. The method also includes determining that at least one sub-channel is idle, and transmitting an RTS frame to the second electronic device on the at least one sub-channel.

Some aspects relate to a non-transitory computer-readable medium storing instructions. When executed by a processor of an electronic device, the instructions cause the processor to perform operations comprising generating a Request To Send (RTS) frame, wherein the RTS frame comprises a first subfield and a second subfield to indicate a Bandwidth (BW) associated with the RTS frame. The operations also include determining that at least one sub-channel is idle, and transmitting an RTS frame to the second electronic device on the at least one sub-channel.

This summary is provided merely for purposes of illustrating some aspects in order to provide an understanding of the subject matter described herein. Accordingly, the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter in this disclosure. Other features, aspects, and advantages of the disclosure will become apparent from the following detailed description, the accompanying drawings, and the claims.

Drawings

The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the present disclosure and, together with the description, further serve to explain the principles of the disclosure and to enable a person skilled in the pertinent art to make and use the disclosure.

Fig. 1 illustrates an example system implementing RTS/CTS frames in accordance with some aspects of the present disclosure.

Fig. 2A and 2B illustrate example punctured RTS transmission rules, in accordance with some aspects of the present disclosure.

Fig. 3A and 3B illustrate example punctured CTS transmission rules in accordance with some aspects of the present disclosure.

Fig. 4 illustrates a block diagram of an example wireless system implementing an electronic device based on RTS/CTS frames and transmission rules in accordance with some aspects of the present disclosure.

Fig. 5 illustrates an example frame format for a multi-user (MU) RTS (MU-RTS) frame, in accordance with some aspects of the present disclosure.

Fig. 6A and 6B illustrate example frame formats of CTS frames in accordance with aspects of the present disclosure.

Fig. 7 illustrates an example MU-RTS and CTS frame exchange in accordance with some aspects of the present disclosure.

Fig. 8 illustrates an example method of a wireless system for generating and transmitting an RTS frame in accordance with some aspects of the disclosure.

Fig. 9 illustrates an example method of a wireless system for generating and transmitting CTS frames in accordance with some aspects of the present disclosure.

FIG. 10 is an exemplary computer system for implementing some aspects or portions thereof.

The present disclosure is described with reference to the accompanying drawings. In the drawings, generally, like reference numbers indicate identical or functionally similar elements. Additionally, in general, the left-most digit(s) of a reference number identifies the drawing in which the reference number first appears.

Detailed Description

Some aspects of the present disclosure include apparatus and methods for implementing Request To Send (RTS) and Clear To Send (CTS) frames and transmission rules for RTS and CTS frames. For example, some aspects of the present disclosure relate to puncturing RTS transmission rules. Some aspects relate to puncturing CTS transmission rules. Some aspects of the present disclosure relate to RTS and CTS frames. In addition, some aspects of the present disclosure relate to Clear Channel Assessment (CCA) rules for RTS and CTS.

According to some aspects, the RTS/CTS frames and transmission rules of the present disclosure can be implemented with communication techniques compatible with Institute of Electrical and Electronics Engineers (IEEE)802.11 standards, such as, but not limited to, IEEE802.11ac, IEEE802.11 ax, IEEE802.11 bc, IEEE802.11 bd, IEEE802.11be, and the like. For example, RTS/CTS frames and transmission rules may be used within a Wireless Local Area Network (WLAN).

According to some aspects, RTS/CTS frames and transmission rules may be used with IEEE802.11be and may also be compatible with IEEE802.11 ax. However, aspects of the present disclosure are not limited to these examples. According to some aspects, large Resource Unit (RU) aggregation rules and/or patterns for transmissions in a wireless network (e.g., WLAN) may have an impact on RTS/CTS frames and transmission rules. In addition, using a larger bandwidth to transmit data (e.g., frames such as, but not limited to, physical layer convergence protocol data units (PPDUs)) may also have an impact on RTS/CTS frames and transmission rules. According to some aspects of the present disclosure, RTS/CTS frames and transmission rules are provided for large aggregation rules/modes and/or for PPDU Bandwidths (BWs) including, but not limited to, 320MHz, 160+160MHz, 240MHz, and/or 160+80 MHz. However, aspects of the present disclosure are not limited to these examples and may be applied to other aggregation rules/patterns and/or other PPDU BWs.

As discussed in more detail below, according to some aspects, only High Efficiency (HE) multi-user (MU) RTS (HE MU-RTS) trigger frames may be used to elicit CTS responses from one or more Stations (STAs). According to some aspects, and as discussed in more detail below, using the HE MU-RTS trigger frame may preserve an attribute that the HE device may reset a Network Allocation Vector (NAV) set by the MU-RTS. According to some aspects, when the MU-RTS elicits a CTS response from more than one STA, then the CTS may use a legacy CTS format for the CTS response. However, according to some aspects, if the MU-RTS elicits a CTS response from one STA, the CTS may use the ehtts format (as discussed in more detail below) for the CTS response. Additionally, some aspects of the present disclosure relate to Clear Channel Assessment (CCA) rules for MU-RTS/CTS and MU-RTS/ehttcts.

According to some aspects, RTS/CTS frames and transmission rules are discussed with respect to a large RU (e.g., greater than or equal to 20MHz bandwidth and/or greater than or equal to 242 subcarriers) aggregation mode in Orthogonal Frequency Division Multiple Access (OFDMA) and/or non-OFDMA transmissions. Examples of puncturing RTS transmission rules are provided. In some examples, the RTS frame is transmitted only on one or more subchannels that have CCA idle and result in a valid large RU aggregation mode. According to some examples, the example method may avoid unnecessary medium reservations. Additionally or alternatively, an RTS frame may be transmitted on all subchannels with CCA idle.

The present disclosure also provides examples of punctured CTS transmission rules. In some examples, the CTS frame may be transmitted on all subchannels on which the RTS frame was received and which have CCA clear. According to some examples, the example method may simplify the CTS transmission logic. Additionally or alternatively, the CTS frame may be transmitted only on the subchannel on which the RTS frame was received, with CCA idle, and resulting in a large RU aggregation mode.

In addition to exemplary RTS/CTS transmission rules, the present disclosure provides exemplary RTS and CTS frames. According to some examples, the BW signaling Target Address (TA) method used in IEEE802.11 standards, such as but not limited to IEEE802.11ac, may be extended to exemplary RTS and CTS frames. However, in some examples, the extended BW signaling TA approach may have feasibility issues due to the lack of bits available for reuse. According to some aspects, new RTS and CTS frames may be defined. However, defining a new RTS frame may result in the HE device being unable to reset the NAV using the new RTS frame. In other words, the new RTS frame may not be backward compatible and cannot be used by STAs that operate based on, for example, IEEE802.11 ax.

According to some aspects, HE MU-RTS trigger frames may be adapted and used for example RTS frames. In these examples, the HE STA will be able to reset the NAV using the MU-RTS frame. For example, the STA may use a MU-RTS frame followed by no CTS frame and no data to allow NAV. In other words, the MU-RTS frame may be backward compatible and may be used by STAs that operate based on, for example, IEEE802.11 ax. In addition, the MU-RTS frame may also be used by very high throughput (EHT) STAs. For example, by STAs operating based on ieee802.11be.

As discussed in more detail below, the MU-RTS frame may carry a special user information field for indicating a value of a Bandwidth (BW) associated with the MU-RTS frame (and/or a BW associated with a PPDU carrying the MU-RTS frame, such as, but not limited to, 320MHz, 160+160MHz, 240MHz, 160+80 MHz). In some examples, a subfield in the special user information field may be used to indicate the value of BW in addition to a subfield in the common information field of the MU-RTS frame. Additionally or alternatively, the special user information field of the MU-RTS frame may include an erasure pattern. The puncturing pattern may comprise a bitmap mapped to each of the sub-channels in the PPDU BW. In addition, the special user information field of the MU-RTS frame may also include an Association Identifier (AID) value to identify that the user information field is a special user information field.

The MU-RTS frame may also include one or more user information fields. Each user information field may include its associated AID value. According to some aspects, the MU-RTS frame may be transmitted by an Access Point (AP) and/or a non-AP STA. In some examples, the AID value of the user information field may be set to the AID value of the non-AP STA triggered for the CTS response for MU-RTS frames transmitted by the AP. Additionally or alternatively, for MU-RTS frames transmitted by non-AP STAs, the AID value of the user information field may be set to the AID value of the non-AP STA that is transmitting the MU-RTS frame. Additionally or alternatively, the AID value may be set to a value of "0" (e.g., reserved) or some other predefined value.

According to some examples, the MU-RTS frame may be carried in a non-HT (high throughput) PPDU or a non-HT DUP (duplicate) PPDU.

In addition to the example RTS/CTS transmission rules and RTS frames, the present disclosure also provides example CTS frames. According to some aspects, a receiving STA receiving an RTS frame (e.g., an MU-RTS frame) from a transmitting STA uses a legacy CTS frame format (e.g., as used in the IEEE802.11 standard, such as, but not limited to, IEEE802.11 ax) when the RTS frame indicates that the RTS is eliciting a response from more than one STA. In this example, the CTS frame does not indicate reserved BW, as the CTS frame transmitted by the STA will be the same.

According to some aspects, a receiving STA receiving an RTS frame (e.g., MU-RTS frame) from a transmitting STA uses a new ehtts frame format when the RTS frame indicates that the RTS is eliciting a response from one STA. In this example, the ehhtcts frame may indicate the reserved BW, allowing any STA to determine the reserved BW by, for example, receiving the ehhtcts frame on at least a primary channel (e.g., a 20MHz primary channel). According to some aspects, the CTS frame and/or the ehhtcts frame may be carried in a non-HT PPDU or a non-HT DUP PPDU. According to some examples, one bit in the common information field of an RTS frame (e.g., MU-RTS frame) may indicate to the receiving STA which CTS frame to use in response to the RTS frame.

In addition to example RTS/CTS transmission rules and RTS/CTS frames, the present disclosure provides example Clear Channel Assessment (CCA) rules for CTS frames and ehttcts frames. In accordance with some aspects, Clear Channel Assessment (CCA) is a mechanism by which STAs determine whether a channel is clear. According to some examples, the CCA may include one or more mechanisms. For example, the CCA may include Carrier Sense (CS). Additionally or alternatively, the CCA may include Energy Detection (ED). In the energy detection mechanism, a STA may measure the energy received by the STA. If the measured energy is greater than the threshold, the STA may determine that the channel is busy. If the measured energy is less than the threshold, the STA may determine that the channel is idle. According to some aspects, the threshold may be defined in the IEEE802.11 standard.

In some examples, the CS may include a physical CS that may be performed by a Physical (PHY) layer. Additionally or alternatively, the CCA may include a virtual CS, which may be provided by a Medium Access Control (MAC) layer. The virtual CS may also be referred to as a Network Allocation Vector (NAV). In accordance with some aspects, the NAV is (or includes) an indicator of the STA indicating when the channel will next become idle. The current NAV may be maintained using, for example, a session duration value in the frame. For example, when a STA receives a valid frame that is not addressed to the STA, the STA may use the duration value in the frame to update the NAV of the STA. In some examples, a STA updates its NAV when the duration value of a frame is greater than the current value of the STA's NAV. In some examples, by using NAVs, STAs may avoid transmitting on the channel even if the physical CS indicates that the channel is idle.

According to some aspects, HE CCA rules for CTS frames, e.g., in IEEE802.11 ax and/or IEEE802.11be, may be followed for MU-RTS frames. For example, a combination of virtual CS and ED based CCAs during SIFS following the MU-RTS frame may be used to determine a medium status (e.g., channel status) on a non-punctured subchannel (e.g., a non-punctured 20MHz subchannel). In some examples, only the non-primary channels are erasure channels.

According to some aspects, if a MU-RTS frame is eliciting responses from more than one STA, a STA may transmit a CTS response only if all subchannels (e.g., all 20MHz subchannels) contained in the allocated RU are CCA-idle. Additionally or alternatively, if the MU-RTS frame is eliciting a response from one STA, the STA may transmit an ehtts response on the primary sub-channel (e.g., the 20MHz primary sub-channel) and any other sub-channel (e.g., any other 20MHz sub-channel) for which the CCA contained in the allocated RU is clear.

Fig. 1 illustrates an example system 100 implementing RTS/CTS frames in accordance with some aspects of the present disclosure. The exemplary system 100 is provided for illustrative purposes only and is not limiting of the disclosed aspects. System 100 may include, but is not limited to, an Access Point (AP)110, a Station (STA)120, and a network 130. The stations 120a-120c may include, but are not limited to, Wireless Local Area Network (WLAN) stations, such as wireless communication devices, smart phones, laptops, desktop computers, tablets, personal assistants, monitors, televisions, wearable devices (e.g., smart watches), and so forth. The Access Point (AP)110 may include, but is not limited to, a WLAN electronic device, such as a wireless router, a wearable device (e.g., a smart watch), a wireless communication device (e.g., a smartphone), or a combination thereof. The network 130 may be the internet and/or a WLAN. The communication of station 120 is shown as wireless communication 140. Communication between AP110 and STA120 may be conducted using wireless communications 140a-140 c. Communications between STAs 120 may be conducted using wireless communications 140d-140 e. The wireless communications 140a-140e may be based on a variety of wireless communication technologies. These techniques may include, but are not limited to, techniques based on IEEE802.11 (such as, but not limited to, IEEE802.11ac, IEEE802.11 ax, IEEE802.11 bc, IEEE802.11 bd, IEEE802.11be, IEEE802.11 v, and so forth).

It is noted that although some aspects are discussed with respect to some examples of WLANs, aspects of the present disclosure are not limited to these examples of WLANs and may be used by other WLAN topologies such as, but not limited to, infrastructure networks, peer-to-peer networks, mesh networks, and the like. In addition, some aspects of the disclosure are discussed with respect to communications between non-AP STAs (e.g., STA 120) and/or communications between an AP (e.g., AP 110) and non-AP STAs (e.g., STA 120). However, aspects of the present disclosure may be applied to communication between any STAs (AP STAs and/or non-AP STAs).

In accordance with some aspects, the AP110 and/or the STA120 are configured to implement RTS/CTS frames and transmission rules. For example, the AP110 and the STA120a may use the RTS/CTS frames and transmission rules of the present disclosure to reduce data collisions by, for example, reserving a channel. For example, a first STA (e.g., a transmitting STA such as AP 110) having data to transmit sends an RTS frame on a channel to a second STA (e.g., a receiving STA such as STA120 a). After receiving the CTS frame, and for example after a period of time (e.g., SIFS), the AP110 transmits its data on the channel to the STA120, if the STA120a correctly receives and decodes the data, the STA120a may transmit an Acknowledgement (ACK), for example, after a period of time (e.g., SIFS) after receiving the data.

According to some aspects, AP110 is configured to transmit its frames (e.g., data, RTS frames, CTS frames, etc.) using a large Resource Unit (RU) aggregation mode. In some examples, the large RU aggregation mode may include a mode in which 242 or more subcarriers are aggregated in a frame. Additionally or alternatively, the large RU aggregation mode may include a mode in which a bandwidth of an RU is 20MHz or more. However, the large RU aggregation mode may include a mode in which other numbers of subcarriers and/or bandwidths are aggregated. According to some examples, the large RU aggregation mode is used as defined in, for example, IEEE802.11 ax and/or IEEE802.11 be. According to some examples, the large RU aggregation mode may be used for OFDMA transmissions and/or non-OFDMA transmissions.

According to some aspects, when using frames with large Bandwidth (BW) and/or in large RU aggregation mode, the BW may be divided into a plurality of subchannels. According to some examples, one or more of the subchannels in the BW may be used for transmission by incumbent devices. In other words, when the AP110 transmits frames with large BW and/or in large RU aggregation mode, the AP110 does not transmit any data, information, and/or requests in one or more subchannels of the BW (e.g., the AP110 uses bits with a value of "0" (subcarriers zeroed out) for subcarriers in the one or more subchannels). These one or more sub-channels may be used by other devices (e.g., existing devices for using those channels/bandwidths, such as satellites, radar, etc.) to transmit data/information using frequencies in those one or more sub-channels. In other words, these one or more subchannels are considered punctured subchannels. Some aspects of the present disclosure discuss a single puncturing subchannel. However, aspects of the present disclosure are not limited to these examples, and other numbers of punctured subchannels may be used.

In a non-limiting example, a frame with an 80MHz BW (a frame for OFDMA transmissions and/or non-OFDMA transmissions) may include (and/or be allowed to include) a single 20MHz punctured subchannel. In this non-limiting example, the 80MHz BW may include two 20MHz subchannels, one 20MHz puncture subchannel, and another 20MHz subchannel. Alternatively, the 80MHz BW may include one 20MHz channel, the 20MHz puncture subchannel, and two 20MHz subchannels. When using frames with large Bandwidth (BW) and/or in large RU aggregation mode, a transmitting STA (e.g., AP 110) may have different options for transmitting RTS frames. Two exemplary punctured RTS transmission rules are discussed in fig. 2A and 2B.

Fig. 2A illustrates an example truncated RTS transmission rule 200, according to some aspects of the disclosure. As one non-limiting example, the frame BW 201 (e.g., PPDU BW) is 320MHz and includes four sections 203a-203d (collectively referred to as sections 203). Each of the sections 203 may have a BW of 80 MHz. According to some examples, the segment 203a may be divided into four sub-channels 205a-205d, each having a BW of 20 MHz. In some examples, subchannel 205a may be a primary subchannel and subchannel 205c may be a puncturing subchannel. An exemplary punctured RTS transmission rule 200 is discussed with respect to channel 203 a. However, similar puncturing RTS transmission rules may be applied to the other channels 203b-203 d.

According to some aspects, in the pruned RTS transmission rule 200, an RTS frame is transmitted only on subchannels that have CCA idle and result in a large RU aggregation mode, as described above. In other words, in order for AP110 to transmit its RTS frame, AP110 may determine a clear subchannel using one or more CCA mechanisms, and AP110 may determine a subchannel that results in a large RU aggregation mode. For example, in accordance with some aspects, assuming that subchannels 205a, 205b, and 205d are CCA-idle, AP110 transmits only on subchannels 205a and 205b that result in a large RU aggregation mode. In this example, subchannels 205a and 205b are aggregated to produce a large RU aggregation mode. According to some examples, the punctured RTS transmission rule 200 of fig. 2A may avoid unnecessary medium reservations.

According to some aspects, if one or more segments (e.g., segment 203b) do not include any punctured subchannels and all subchannels of segment 203b are CAA-free, AP110 may transmit an RTS frame on each subchannel of segment 203 b.

Fig. 2B illustrates another example punctured RTS transmission rule 230, in accordance with some aspects of the present disclosure. As one non-limiting example, the frame BW 231 (e.g., PPDU BW) is 320MHz and includes four segments 233a-233d (collectively segments 233). Each of the segments 233 may have a BW of 80 MHz. According to some examples, segment 233a may be divided into four sub-channels 235a-235d, each having a BW of 20 MHz. In some examples, subchannel 235a may be a primary subchannel and subchannel 235c may be a puncturing subchannel. Exemplary punctured RTS transmission rules 230 are discussed with respect to channel 233 a. However, similar puncturing RTS transmission rules may be applied to the other channels 233b-233 d.

In accordance with some aspects, in the puncturing RTS transmission rule 230, RTS frames are transmitted on all subchannels with CCA clear. In other words, for AP110 to transmit its RTS frame, AP110 may use one or more CCA mechanisms to determine the clear subchannels. For example, in accordance with some aspects, assuming subchannels 235a, 235b, and 235d are CCA-clear, AP110 transmits on subchannels 235a, 235b, and 205 d. According to some examples, the puncturing RTS transmission rule 230 of fig. 2B may be easy to implement and may be applicable to cases where a CTS frame is returned, e.g., on an 80/160MHz BW, and where 20MHz puncturing is allowed.

According to some aspects, if one or more segments (e.g., segment 233b) do not include any punctured subchannels and all subchannels of segment 233b are CAA-free, AP110 may transmit an RTS frame on each subchannel of segment 233 b.

Although the puncturing RTS transmission rules 200 and 230 are discussed with respect to a frame BW of 320MHz, four channels of 80MHz, and a subchannel of 20MHz, aspects of the present disclosure are not limited to these examples, and other values for the frame BW, the large RU aggregation mode, the channels, and/or the subchannels may be used.

According to some aspects, after receiving the RTS frame from the AP110, the STA120a may send a CTS frame back to the AP110 if the AP110 is allowed to transmit its data on the channel. In some examples, the STA120 may send a CTS frame to the AP110 after a period of time (e.g., SIFS) after receiving the RTS frame to indicate that the channel is idle and that the AP110 may send its data. In accordance with some aspects, the STA120a is configured to transmit its frames (e.g., data, RTS frames, CTS frames, etc.) using the large RU aggregation mode. When using frames with large Bandwidth (BW) and/or in large RU aggregation mode, the receiving STA (e.g., STA120a) may have different options for transmitting CTS frames. Two exemplary punctured CTS transmission rules are discussed in fig. 3A and 3B.

Fig. 3A illustrates an example punctured CTS transmission rule 300 in accordance with some aspects of the present disclosure. As one non-limiting example, frame BW 301 (e.g., PPDU BW) is 320MHz and includes four segments 303a-303d (collectively referred to as segments 303). Each of the sections 303 may have a BW of 80 MHz. According to some examples, section 303a may be divided into four sub-channels 305a-305d, each having a BW of 20 MHz. In some examples, subchannel 305a may be a primary subchannel and subchannel 305c may be a puncturing subchannel. An exemplary punctured CTS transmission rule 300 is discussed with respect to channel 303 a. However, similar puncturing RTS transmission rules may be applied to the other channels 303b-303 d.

According to some aspects, in the punctured CTS transmission rule 300, CTS frames are transmitted on all subchannels on which RTS frames are received and which have CCA clear. In other words, for STA120a to transmit its CTS frame, STA120a may determine the sub-channel on which STA120 receives the RTS frame from AP 110. In addition, the STA120a may determine a clear subchannel using one or more CCA mechanisms. The STA120a may transmit a CTS frame on all subchannels on which the RTS frame was received and which have CCA clear. For example, in accordance with some aspects, assuming that the sub-channels 305a, 305b, and 305d are CCA idle and an RTS frame is received at the STA120a on the sub-channels 305a, 305b, and 305d, the STA120a transmits a CTS frame on the sub-channels 305a, 305b, and 305 d. As another example, in accordance with some aspects, assuming that the subchannels 305a, 305b, and 305d are CCA-idle and an RTS frame is received at the STA120a on the subchannels 305a and 305d, the STA120a transmits a CTS frame on the subchannels 305a and 305 d. According to some examples, the punctured CTS transmission rule 300 of fig. 3A may simplify the CTS transmission logic.

According to some aspects, if one or more segments (e.g., segment 303b) do not include any punctured subchannels, and all subchannels of segment 303b are CAA-free and were used to receive RTS frames, STA120a may transmit a CTS frame on each subchannel of segment 303 b.

Fig. 3B illustrates another exemplary punctured CTS transmission rule 330 in accordance with some aspects of the present disclosure. As one non-limiting example, the frame BW 331 (e.g., PPDU BW) is 320MHz and includes four segments 333a-333d (collectively referred to as segments 333). Each of the segments 333 may have a BW of 80 MHz. According to some examples, the segment 333a may be divided into four sub-channels 335a-335d, each having a BW of 20 MHz. In some examples, subchannel 335a may be a primary subchannel and subchannel 335c may be a puncturing subchannel. An exemplary punctured CTS transmission rule 330 is discussed with respect to channel 333 a. However, similar puncturing RTS transmission rules may be applied to the other channels 333b-333 d.

According to some aspects, in the pruned CTS transmission rule 300, CTS frames are transmitted only on subchannels on which RTS frames are received, have CCA idle, and result in a large RU aggregation mode, as described above. In other words, for STA120a to transmit its CTS frame, STA120a may determine the sub-channel on which STA120 receives the RTS frame from AP 110. In addition, the STA120a may determine a clear subchannel using one or more CCA mechanisms. In addition, the STA120a may determine the subchannels that result in the large RU aggregation mode. The STA120a may transmit a CTS frame only on the subchannel on which the RTS frame was received, which has CCA idle, and which results in the large RU aggregation mode. For example, in accordance with some aspects, assuming that the sub-channels 305a, 305b, and 305d are CCA idle and an RTS frame is received at the STA120a on the sub-channels 305a, 305b, and 305d, the STA120a transmits a CTS frame on the sub-channels 305a and 305 b. In this example, subchannels 305a and 305b are aggregated to produce a large RU aggregation mode.

According to some aspects, if one or more segments (e.g., segment 333b) do not include any punctured subchannels, and all subchannels of segment 333b are CAA-free and were used to receive RTS frames, STA120a may transmit a CTS frame on each subchannel of segment 333 b.

Although the punctured CTS transmission rules 300 and 330 are discussed with respect to a frame BW of 320MHz, four channels of 80MHz, and a subchannel of 20MHz, aspects of the present disclosure are not limited to these examples, and other values of the frame BW, large RU aggregation mode, channels, and/or subchannels may be used.

Fig. 4 illustrates a block diagram of an example wireless system 400 implementing an electronic device based on RTS/CTS frames and transmission rules in accordance with some aspects of the present disclosure. System 400 may be any of the electronic devices (e.g., AP110, STA 120) of system 100. System 400 includes processor 410, transceiver 420, communication infrastructure 440, memory 450, operating system 452, applications 454, and antenna 460. The illustrated system is provided as an exemplary portion of a wireless system 400, and the system 400 may include other circuits and subsystems. Additionally, although the systems of wireless system 400 are shown as separate components, aspects of the present disclosure may include any combination of these components, fewer components, or more components.

The memory 450 may include Random Access Memory (RAM) and/or cache memory, and may include control logic (e.g., computer software) and/or data. Memory 450 may include other storage devices or memory, such as, but not limited to, a hard disk drive and/or a removable storage device/unit. According to some examples, an operating system 452 may be stored in memory 450. The operating system 452 may manage the transfer of data from the memory 450 and/or one or more applications 454 to the processor 410 and/or transceiver 420. In some examples, the operating system 452 maintains one or more network protocol stacks (e.g., internet protocol stacks, cellular protocol stacks, etc.) that may include multiple logical layers. At a corresponding layer of the protocol stack, the operating system 452 includes control mechanisms and data structures to perform the functions associated with that layer.

According to some examples, application programs 454 may be stored in memory 450. The applications 454 may include applications (e.g., user applications) used by the wireless system 400 and/or a user of the wireless system 400. Applications in applications 454 may include applications such as, but not limited to: siri^TM、FaceTime^TMWireless streaming, video streaming, remote control, and/or other user applications.

Alternatively or in addition to an operating system, system 400 may include a communication infrastructure 440. Communication infrastructure 440 provides communication between, for example, processor 410, transceiver 420, and memory 450. In some implementations, the communication infrastructure 440 may be a bus. Processor 410, together with instructions stored in memory 450, performs operations that enable wireless system 400 of system 100 to implement RTS/CTS frames and transmission rules as described herein. Additionally or alternatively, transceiver 420 performs operations that enable wireless system 400 of system 100 to implement RTS/CTS frames and transmission rules as described herein.

According to some aspects, transceiver 420 transmits and receives communication signals supporting RTS/CTS frames and transmission rules and may be coupled to antenna 460. The antenna 460 may include one or more antennas, which may be of the same or different types. Transceiver 420 allows system 400 to communicate with other devices, which may be wired and/or wireless. The transceiver 420 may include a processor, controller, radio, socket, plug, buffer, and similar circuits/devices for connecting to and communicating over a network. According to some examples, transceiver 420 may include one or more circuits for connecting to and communicating over wired and/or wireless networks. Transceiver 420 may include a cellular subsystem, a WLAN subsystem, and/or Bluetooth^TMSubsystems, each of which includes its own radio transceiver and protocol, as will be understood by those skilled in the art based on the discussion provided herein. In some implementations, the transceiver 420 may include more or fewer systems for communicating with other devices.

The cellular subsystem (not shown) may include one or more circuits (including a cellular transceiver) for connecting to and communicating over a cellular network. Cellular networks may include, but are not limited to, 3G/4G/5G networks such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and the like. Bluetooth (R) protocol^TMThe subsystem (not shown) may include one or more circuits (including Bluetooth (r))^TMTransceivers) to enable Bluetooth based, for example, to be implemented^TMProtocol, Bluetooth^TMLow power consumption protocol, or Bluetooth^TMLow power long distance protocol connection and communication. The WLAN subsystem (not shown) may include one or more circuits (including a WLAN transceiver) to enable connection and communication over a WLAN network, such as, but not limited to, a network based on the standards described in IEEE802.11, such as, but not limited to, IEEE802.11ac, IEEE802.11 ax, IEEE802.11 bc, IEEE802.11 bd, IEEE802.11be, etc.

According to some aspects, processor 410 implements RTS/CTS frames and transmission rules, alone or in conjunction with memory 450 and/or transceiver 420. For example, processor 410, alone or with transceiver 420 and/or memory 405, may transmit an RTS frame and/or a CTS frame based on the transmission rules described with respect to fig. 2A, 2B, 3A, and/or 3B. Additionally or alternatively, processor 410, alone or with transceiver 420 and/or memory 405, may generate RTS and CTS frames as described with respect to fig. 5, 6A, and 6B. Additionally or alternatively, processor 410, alone or in conjunction with transceiver 420 and/or memory 405, may perform operations as described with respect to fig. 7-9.

According to some aspects of the disclosure, different frame formats may be used for RTS and CTS frames. According to some examples, the BW signaling Target Address (TA) method used in IEEE802.11 standards, such as but not limited to IEEE802.11ac, may be extended to exemplary RTS and CTS frames. However, in some examples, the extended BW signaling TA approach may have feasibility issues due to the lack of bits available for reuse. According to some aspects, new RTS and CTS frames may be defined. However, defining a new RTS frame may result in the HE device being unable to reset the NAV using the new RTS frame. In other words, using a new RTS frame may lose backward compatibility capability and may cause legacy devices to operate in, for example, IEEE802.11 ax, be unable to reset their NAVs and thus be unable to transmit their data.

According to some aspects, HE MU-RTS trigger frames may be adapted and used for example RTS frames. In these examples, the HE STA will be able to reset the NAV using the MU-RTS frame. For example, a STA may use a MU-RTS frame followed by a CTS frame and data for a predefined period of time to allow NAV. In other words, the MU-RTS frame may be backward compatible and may be used by STAs that operate based on, for example, IEEE802.11 ax. In addition, the MU-RTS frame may also be used by very high throughput (EHT) STAs. For example, by STAs operating based on ieee802.11be.

Fig. 5 illustrates an example frame format for an RTS frame 500, in accordance with some aspects of the present disclosure. RTS frame 500 illustrates the format of an RTS frame, which is also referred to herein as a multi-user (MU) RTS (MU-RTS) frame and/or a MU-RTS trigger frame. According to some aspects, the MU-RTS frame 500 may signal the Bandwidth (BW) of the MU-RTS frame 500 (and/or the BW of the PPDU carrying the MU-RTS frame 500) to the receiving STA. In some examples, the MU-RTS frame 500 may signal the bandwidth to STAs (e.g., EHT STAs) operating in, for example, IEEE802.11 be. Additionally, the MU-RTS frame 500 may signal bandwidth to STAs (e.g., HE STAs) operating in, for example, IEEE802.11 ax.

According to some aspects, the MU-RTS frame 500 may include a Medium Access Control (MAC) header 501. In some examples, the MAC header 501 may include fields such as, but not limited to, a frame control field 503, a duration field 505, and addresses 507 and 509 (e.g., one or more source addresses, one or more destination addresses, etc.). For example, the MAC header 501 may include a Receiver Address (RA) 507. In some examples, different RTS frames may have different RAs. Additionally or alternatively, the MU-RTS frame 500 may use a broadcast address as RA 507. The MAC header 501 may also include a Transmitter Address (TA) 509. In some examples, the MAC header 501 may include additional fields such as, but not limited to, a sequence control field, a quality of service (QoS) control field, and the like.

Additionally, the MU-RTS frame 500 may include fields such as, but not limited to, a common information field 511, a special user information field 515, user information fields 519a-519 n. In addition, the MU-RTS frame 500 may include a padding field 521 for additional padding to compensate for different lengths of different MU-RTS frames, and a Frame Check Sequence (FCS)523 for error detection. In some non-limiting examples, the common information field 511 may have a length of 8 or more octets, the special user information field 515 may have a length of 5 or more octets, the user information fields 519a-519n may have a length of 5 or more octets, the padding field 521 may have a variable length, and the FCS field 523 may have a length of 4 octets. However, aspects of the present disclosure are not limited to these lengths and fields, and other lengths and fields may also be used.

According to some aspects, the common information field 511 may include one or more subfields such as, but not limited to, a trigger type subfield, an Uplink (UP) length subfield, a more TF subfield, a Carrier Sensing (CS) required subfield, and an UL Bandwidth (BW) subfield. The common information field 511 may include fewer or additional subfields. According to some aspects, the special user information field 515 and the user information fields 519a-519n may include one or more subfields such as, but not limited to, an Association Identifier (AID) subfield, an RU assignment subfield, an UL Forward Error Correction (FEC) coding type subfield, an UL Modulation and Coding Scheme (MCS) subfield, an UL Dynamic Coding and Modulation (DCM) subfield. Special user information field 515 and user information fields 519a-519n may include fewer or additional sub-fields.

According to some aspects, the MU-RTS frame 500 may signal to the receiving STA the Bandwidth (BW) associated with the MU-RTS frame 500 and/or the BW associated with the PPDU carrying the MU-RTS frame 500 using a first subfield in the common information field 511 and a second subfield in the special user information field 515. For example, the MU-RTS frame 500 may use the UL BW subfield 513 of the common information field 511 and the BW subfield 517 in the special user information field 515 to signal the BW associated with the MU-RTS frame 500 and/or the BW associated with the PPDU carrying the MU-RTS frame 500. According to some examples, BW includes, but is not limited to, 320MHz, 160+160MHz, 240MHz, 160+80 MHz.

According to some aspects, upon receiving the MU-RTS 500, an Extremely High Throughput (EHT) STA (e.g., a STA operating in IEEE802.11 be) may read the UL BW subfield 513 of the common information field 511 and the BW subfield 517 in the special user information field 515 to determine the BW associated with the MU-RTS frame 500 and/or the BW associated with the PPDU carrying the MU-RTS frame 500. Additionally or alternatively, upon receiving the MU-RTS 500, a High Efficiency (HE) STA (e.g., a STA operating in IEEE802.11 ax) may read the UL BW subfield 513 of the common information field 511 to determine the BW associated with the MU-RTS frame 500 and/or the BW associated with the PPDU carrying the MU-RTS frame 500.

In some examples, the UL BW subfield 513 of the common information field 511 may be set to 20, 40, 80, 160/80+80 if the BW associated with the MU-RTS frame 500 and/or the BW associated with the PPDU carrying the MU-RTS frame 500 is equal to or less than 160 MHz. In some examples, the UL BW subfield 513 of the common information field 511 may be set to 160/80+80 if the BW associated with the MU-RTS frame 500 and/or the BW associated with the PPDU carrying the MU-RTS frame 500 is greater than 160 MHz. The BW subfield 517 in the special user information field 515 may be used in addition to the UL BW subfield 513 of the common information field 511 to signal BW when it is greater than 160 MHz.

According to some aspects, the special user information field 515 may include an AID subfield 516. The AID subfield 516 may have a predefined value to indicate that field 515 is a special user information field. In other words, in some RTS frames, field 515 may be similar to user information fields 519a-519 n. However, the MU-RTS frame 500 indicates that field 515 is a special user information field by using a predefined value (e.g., reserved AID value) of AID subfield 516.

According to some aspects, special user information field 515 may include puncturing pattern 518. In some examples, puncturing pattern 518 may comprise a bitmap. As a non-limiting example, puncturing pattern 518 may be a 16-bit bitmap. Each bit in the bitmap is mapped to a subchannel. For example, each bit in the bitmap may map to a subchannel 205a-205d of section 203a of FIG. 2A (and/or a subchannel 235a-235d of section 233a of FIG. 2B). In addition, each bit in the bitmap may map to a subchannel of zones 203B-203d of FIG. 2A (and/or a subchannel of zones 233B-233d of FIG. 2B). For example, a value of "1" for a bit in the bitmap 518 may indicate that the MU-RTS frame 500 is transmitted on the subchannel associated with the bit. A value of "0" for a bit in the bitmap 518 may indicate that the MU-RTS frame 500 is not transmitted on the subchannel associated with the bit.

According to some aspects, the MU-RTS frame 500 may be transmitted on the uplink and the downlink. In other words, the MU-RTS frame 500 may be transmitted by the AP110 to one or more STAs 120. Additionally, the MU-RTS frame 500 may be transmitted by a non-AP STA (e.g., STA 120) to the AP 110. According to some aspects, the user information field 519a also includes an AID subfield 520. According to some examples, the MU-RTS frame 500 may be transmitted by an AP (e.g., AP 110) to a non-AP STA (e.g., STA120 a). In some examples, the AID subfield 520 may be set to trigger the AID of the non-AP STA (e.g., STA120a) for the CTS response by the MU-RTS frame 500 when the MU-RTS frame 500 is transmitted by the AP. Additionally or alternatively, the MU-RTS frame 500 may be transmitted by a non-AP STA (e.g., STA120 a). The MU-RTS frame 500 may be transmitted to another non-AP STA (e.g., STA120 b) and/or an AP (e.g., AP 110). When the MU-RTS frame 500 is transmitted by a non-AP STA (e.g., STA120a), the AID subfield 520 may be set to the AID of the non-AP STA (e.g., STA120a) that is transmitting the MU-RTS frame 500. Alternatively, the AID subfield 520 may be set to a value of "0" (e.g., reserved) or some other predefined value when the MU-RTS frame 500 is transmitted by a non-AP STA (e.g., STA120 a).

According to some examples, the MU-RTS frame 500 may be carried in a non-HT (high throughput) PPDU or a non-HT DUP (duplicate) PPDU.

According to some aspects, after receiving the MU-RTS frame 500 from a transmitting STA (e.g., AP 110), if the transmitting STA is allowed to transmit its data on the channel, the receiving STA (e.g., STA120a) may send a CTS frame back to the transmitting STA. In some examples, the receiving STA may send a CTS frame to the transmitting STA after a period of time (e.g., SIFS) to indicate that the channel is idle and that the AP110 may send its data. According to some aspects, the MU-RTS 500 is transmitted to a plurality of receiving STAs. Each receiving STA may send its CTS frame back to the transmitting STA. Alternatively, the MU-RTS 500 may be transmitted to only one receiving STA. The receiving STA may send its CTS frame back to the transmitting STA.

Fig. 6A illustrates an example frame format for a CTS frame 600, in accordance with some aspects of the present disclosure. According to some aspects, a receiving STA receiving the MU-RTS frame 500 from a transmitting STA uses the CTS frame 600 when the MU-RTS frame 500 indicates that the MU-RTS is eliciting responses from more than one STA. In some examples, the CTS frame 600 has the same or similar format as a CTS frame format used in IEEE802.11 standards (such as, but not limited to, IEEE802.11 ax). According to some examples, the receiving STA determines, based on the user information fields 519a-519n, that the received MU-RTS 500 elicits a response from more than one STA. In other words, the MU-RTS 500 includes more than one user information field. Additionally or alternatively, the receiving STA determines, based on RA field 507, that the received MU-RTS 500 elicits a response from more than one STA. For example, RA field 507 may include more than one receive address and/or multicast or broadcast address. Although some examples are provided in the present disclosure, aspects of the present disclosure are not limited to these examples, and the receiving STA may use other information in the MU-RTS 500 to determine that the received MU-RTS 500 elicits a response from more than one STA.

According to some examples, the CTS frame 600 may include one or more fields including, but not limited to, a frame control field 601, a duration field 603, an RA field 605, and an FCS field 607. The frame control field 601 may include a value to indicate that the frame 600 is a CTS frame. The duration field 603 may include the value used in the duration 505 from the MU-RTS frame 500. The RA field 605 includes the receiver address of the CTS frame 600 (e.g., the transmitter address of the RTS frame 500). The FCS field 607 is a frame check sequence for error detection. In some examples, the frame control field 601 may have a length of 2 bytes, the duration field 603 may have a length of 2 bytes, the RA field 605 may have a length of 6 bytes, and the FCS field 607 may have a length of 4 bytes. In some examples, the frame control field 601, duration field 603, and RA field 605 may constitute a MAC header of the CTS frame 600. Note that the CTS frame 600 may include other, fewer, or more fields having other exemplary lengths. In some examples, the CTS frame 600 does not indicate reserved BW because the CTS frames transmitted by different STAs are the same. In some examples, the CTS frame 600 may be carried in a non-HT PPDU or a non-HT DUP PPDU.

Fig. 6B illustrates an example frame format for a CTS frame 620 in accordance with some aspects of the present disclosure. According to some aspects, a CTS frame 620 is used by a receiving STA that receives a MU-RTS frame 500 from a transmitting STA when the MU-RTS frame 500 indicates that the MU-RTS is eliciting a response from more than one STA. According to some examples, the receiving STA determines, based on the user information fields 519a-519n, that the received MU-RTS 500 elicits a response from one STA. In other words, the MU-RTS 500 includes one user information field. Additionally or alternatively, the receiving STA determines, based on RA field 507, that the received MU-RTS 500 elicits a response from one STA. For example, RA field 507 may include a receive address. Although some examples are provided in the present disclosure, aspects of the present disclosure are not limited to these examples, and the receiving STA may use other information in the MU-RTS 500 to determine that the received MU-RTS 500 elicits a response from one STA.

According to some examples, a CTS frame 620 (also referred to herein as an extremely high throughput CTS (ehtts)) may include one or more fields, including, but not limited to, a frame control field 621, a duration field 623, an RA field 625, a channel bitmap field 626, and an FCS field 627, the frame control field 621 may include a value to indicate that the frame 620 is a CTS frame, in some examples, the frame control field 621 may include a value to indicate that the frame 620 is an ehtts frame, the duration field 623 may include a value used in the duration 505 from the MU-RTS frame 500, the RA field 625 includes a receiver address of the CTS frame 620 (e.g., a transmitter address of the RTS frame 500), the FCS field 627 is a frame check sequence for error detection, in some examples, the frame control field 621 may have a length of 2 bytes, the duration field 623 may have a length of 2 bytes, the RA field 625 may have a length of 6 bytes, and the FCS field 627 may have a length of 4 bytes. In some examples, the frame control field 621, duration field 623, and RA field 625 may constitute a MAC header of the CTS frame 620.

In accordance with some aspects, the channel bitmap field 626 of the CTS frame 620 may indicate the sub-channel on which the CTS frame 620 is transmitted. For example, each bit in channel bitmap field 626 may map to a subchannel 305a-305d of section 303A of FIG. 3A (and/or a subchannel 335a-235d of section 333A of FIG. 3B). In addition, each bit in channel bitmap field 626 may map to a subchannel of segments 303B-303d of FIG. 3A (and/or a subchannel of segments 333B-333d of FIG. 3B). For example, a value of "1" for a bit in the channel bitmap field 626 may indicate that the CTS frame 620 is transmitted on the subchannel associated with the bit. A value of "0" for a bit in the channel bitmap field 626 may indicate that the CTS frame 620 is not transmitted on the subchannel associated with the bit.

Additionally or alternatively, the channel bitmap field 626 of the CTS frame 620 may be used to indicate the reserved BW, allowing any STA to determine the reserved BW by receiving the CTS frame 620 on, for example, at least a primary channel (e.g., a 20MHz primary channel). For example, any receiving STA may determine the reserved BW by using the channel bitmap field 626 (which may indicate the sub-channel on which the CTS frame 620 is transmitted and the sub-channel on which the CTS frame 620 is not transmitted).

In some examples, the CTS frame 620 may be carried in a non-HT PPDU or a non-HT DUP PPDU.

Note that the frame format of the CTS frame 620 in fig. 6B is provided as an example. The CTS frame 620 may have other formats so long as the format includes and/or indicates a channel bitmap that indicates the sub-channel on which the CTS frame 620 is transmitted. Additionally or alternatively, other frame formats of the CTS frame 620 may include an indication of the reserved BW for the CTS frame, allowing any STA to determine the reserved BW by receiving the CTS frame 620.

According to some examples, a subfield (including one or more bits) in the common information field 511 of the MU-RTS frame 500 may indicate to the receiving STA which CTS frame (CTS frame 600 or CTS frame 620) to use to respond to the MU-RTS frame 500. For example, the MU-RTS frame 500 may include a subfield 514 to indicate to the receiving STA whether to use the CTS frame 600 or the CTS frame 620. For example, the subfield 514 may be set to a first value (e.g., a value of "1") to use the CTS frame 620 and may be set to a second value (e.g., a value of "0") to use the CTS frame 600. In some examples, bits from the UL HE-SIG-a2 Reserved field in the MU-RTS frame 500 may be used as the sub-field 514.

According to some aspects, a receiving STA (e.g., STA120a) receiving a MU-RTS frame (e.g., MU-RTS frame 500) may use one or more CCA mechanisms prior to generating and transmitting a CTS frame (e.g., CTS frames 600 and/or 620). According to some examples, the receiving STA may check the medium using HE CCA rules (e.g., as used in IEEE802.11 ax) as a CCA mechanism. For example, the receiving STA may determine the state of the medium on the non-punctured subchannel using one or more of a virtual Carrier Sensing (CS) mechanism and/or an Energy Detection (ED) based mechanism during a predefined time period (e.g., SIFS) after receiving the MU-RTS frame (e.g., MU-RTS frame 500). For example, the receiving STA may use a combination of a virtual CS mechanism and an ED-based mechanism as a CCA mechanism. In some examples, only the non-primary channels are erasure channels.

According to some aspects, if a MU-RTS frame (e.g., MU-RTS frame 500) is eliciting responses from more than one STA, the receiving STA transmits a CTS frame (e.g., CTS frame 600) only if all of the subchannels (e.g., 20MHz subchannels) contained in the allocated RU are CCA-free.

Additionally or alternatively, if an MU-RTS frame (e.g., MU-RTS frame 500) elicits a response from only one STA, the receiving STA transmits a CTS frame (e.g., CTS frame 620-ehtts frame) on the primary subchannel (e.g., 20MHz primary subchannel) and on any other subchannels (e.g., 20MHz subchannels) for which the CCA contained in the allocated RU is clear.

An example of this process is further discussed with respect to fig. 7. Fig. 7 illustrates an example MU-RTS and CTS frame exchange as a function of time and frequency in accordance with some aspects of the present disclosure. For convenience, and not limitation, the operations 700 of fig. 7 may be described with respect to elements of fig. 1-6. Operation 700 represents communication between multiple electronic devices-an AP 701 and non-AP STAs 703 and 704. According to some examples, AP 701 may include AP110 of fig. 1, and non-AP STAs 703 and 704 may include STA120 of fig. 1.

According to some aspects, the AP 701 may transmit a MU-RTS frame 705 to the STA 703 and the STA 704. In some examples, the MU-RTS frame 705 (or PPDU carrying the MU-RTS frame 705) has a Bandwidth (BW) 707. In a non-limiting example, BW 707 may be 160 MHz. The BW 707 may include two sections: a primary section 709a and a secondary section 709b, each of which is, for example, 80 MHz. Section 709b may also include punctured subchannels 711 of 20MHz bandwidth. However, sections 707 and 709 may include other bandwidths as described above. According to some examples, the AP 701 transmits the MU-RTS frame 705 in a non-HT DUP PPDU.

According to some aspects, the MU-RTS frame 705 may request the STA 703 to transmit a CTS response in a non-HT PPDU having a BW 715, and may request the STA 704 to transmit a CTS response in a non-HT DUP PPDU having a 719. STAs 703 and 704 may use the virtual CS and/or ED based CCA to determine the channel status (e.g., whether the medium/channel is clear or busy) during SIFS after receiving the MU-RTS 705. In response to the CCA being idle, the STAs 703 and 704 may transmit their respective CTS frames 713 and 717.

According to some aspects, the STA 703 transmits the CTS frame 713 in a non-HT PPDU requested by the MU-RTS frame 705. In some examples, the CTS frame 713 may be based on the CTS frame 600 of fig. 6A. STA 703 transmits CTS frame 713 with BW 715. In some examples, BW 715 is the same as BW 709 a. In this example, all BW 715(BW 709) was CCA idle.

According to some aspects, the STA 704 transmits the CTS frame 717 in the non-HT PPDU requested by the MU-RTS frame 705. In some examples, the CTS frame 717 may be based on the CTS frame 600 of fig. 6A. STA 704 transmits a CTS frame 717 with BW 719. In some examples, the STA 704 does not transmit the CTS frame 717 on the puncturing subchannel 721. In some examples, BW 719 is the same as BW 707, and puncturing sub-channels 721 are the same as puncturing sub-channels 711. In this example, the STA 704 transmits the CTS frame 717 only when all sub-channels on the BW 719(BW 707) are CCA idle, excluding the puncturing sub-channel 721 (puncturing sub-channel 711).

Fig. 8 illustrates an example method 800 for a wireless system to generate and transmit an RTS frame in accordance with some aspects of the disclosure. For convenience, but not limitation, fig. 8 may be described with respect to elements of fig. 1-7. Method 800 may represent operations of a station (e.g., AP110 and/or STA120a of fig. 1) generating and transmitting an RTS frame. The method 800 may also be performed by the system 400 of FIG. 4 or the computer system 1000 of FIG. 10. Method 800 is not limited to the specific aspects depicted in those figures and other systems may be used to perform the method, as will be understood by those skilled in the art. It should be understood that not all operations may be required, and that the operations may not be performed in the same order as shown in fig. 8.

At 802, a Request To Send (RTS) frame is generated. For example, a transmitting STA (e.g., AP110 of fig. 1) having data to be sent to a receiving STA (e.g., STA120a of fig. 1) generates an RTS frame. A transmitting STA generates an RTS frame to send to a receiving STA to reserve a medium for transmitting its data. According to some aspects, the RTS frame is generated based on the MU-RTS frame 500 of fig. 5. According to some aspects, the RTS frame may be detected and decoded by EHT STAs (e.g., STAs operating in IEEE802.11 be) and HE STAs (e.g., STAs operating in IEEE802.11 ax).

For example, the RTS frame may include a MAC header (e.g., MAC header 501 of fig. 5), a common information field (e.g., common information field 511 of fig. 5), a special user information field (e.g., special user information field 515 of fig. 5), user information fields (e.g., user information fields 519a-519n of fig. 5), and other fields. According to some aspects, two subfields in the RTS frame may be used to signal the Bandwidth (BW) associated with the RTS frame to other STAs (e.g., receiving STAs). In some examples, the first subfield (e.g., UL BW subfield 513) and the second subfield (e.g., BW subfield 517) are used to indicate the BW associated with the RTS frame.

In some examples, an EHT STA receiving an RTS frame (e.g., a STA operating in IEEE802.11 be) may detect and decode two subfields to determine BW. On the other hand, HE STAs (e.g., STAs operating in IEEE802.11 ax) may detect and decode the first subfield (e.g., UL BW subfield 513).

According to some aspects, the RTS frame may also include another subfield (e.g., subfield 514) to indicate to the receiving STA which CTS frame (e.g., CTS frame 600 or CTS frame 620) to use.

Additionally or alternatively, the RTS frame can include an erasure pattern (e.g., erasure pattern 518). In some examples, the puncturing pattern may include a bitmap, wherein each bit in the bitmap maps to a subchannel. For example, a value of "1" for a bit in the bitmap may indicate that an RTS frame is transmitted on the subchannel associated with the bit. A value of "0" for a bit in the bitmap may indicate that an RTS frame is not transmitted on the subchannel associated with the bit.

At 804, one or more sub-channels are examined to determine whether a sub-channel is free. After generating the RTS frame and before transmitting the RTS frame, the transmitting STA determines whether at least one sub-channel is idle. As described above, the transmitting STA may determine the status of the medium using one or more CCA mechanisms.

Depending on the puncturing RTS transmission rule (e.g., as described in fig. 2A and 2B), the transmitting STA may transmit an RTS frame to the receiving STA. For example, at 806, an RTS frame is transmitted on a CCA-cleared subchannel. In accordance with some aspects, the RTS frame is transmitted on all subchannels (e.g., 20MHz subchannels) for which the CCA is clear. Alternatively, an RTS frame is transmitted on one or more subchannels in response to the one or more subchannels being idle and the one or more subchannels creating a large Resource Unit (RU) aggregation mode.

According to some aspects, the transmitting STA may receive a CTS frame from the receiving STA. In response to receiving the CTS frame, the transmitting STA may transmit its data to the receiving STA. In addition, the transmitting STA may receive an ACK from the receiving STA, which indicates that the receiving STA correctly received the data.

Fig. 9 illustrates an example method 900 for a wireless system that generates and transmits CTS frames in accordance with some aspects of the present disclosure. For convenience, but not limitation, fig. 9 may be described with respect to elements of fig. 1-7. Method 900 may represent the operation of a station (e.g., AP110 and/or STA120a of fig. 1) generating and transmitting an RTS frame. The method 900 may also be performed by the system 400 of FIG. 4 or the computer system 1000 of FIG. 10. Method 900 is not limited to the specific aspects depicted in those figures and other systems may be used to perform the method, as will be understood by those skilled in the art. It should be understood that not all operations may be required, and that the operations may not be performed in the same order as shown in fig. 9.

At 902, a Request To Send (RTS) frame is received. For example, the receiving STA receives an RTS frame from the transmitting STA. According to some aspects, the RTS frame may be a MU-RTS frame. In some examples, after receiving the RTS frame, the receiving STA may determine a Bandwidth (BW) associated with the RTS frame and/or a PPDU carrying the RTS frame. For example, as discussed with respect to fig. 5 and 8, the receiving STA may check one or both subfields in the RTS frame to determine BW. Additionally or alternatively, the receiving STA may check a subfield in the RTS frame to determine one or more subchannels on which the RTS frame was transmitted.

At 904, a format of a Clear To Send (CTS) frame to be used in response to the RTS frame is determined using the received RTS frame. For example, the receiving STA determines whether an RTS frame is transmitted only to the receiving STA or whether an RTS frame is transmitted to more than one STA. In response to the RTS frame being transmitted only to the receiving STA, the receiving STA selects the frame format 620 of fig. 6B for the CTS frame. In this example, the CTS frame may include a channel bitmap field (e.g., channel bitmap field 626 of fig. 6B) that indicates at least one subchannel over which the CTS frame is transmitted. For example, a value of "1" for a bit in the channel bitmap field may indicate that a CTS frame is transmitted on the subchannel associated with the bit. A value of "0" for a bit in the channel bitmap field may indicate that the CTS frame is not transmitted on the subchannel associated with the bit.

Alternatively, if an RTS frame is transmitted to more than one STA, the receiving STA selects the frame format 600 of fig. 6A for a CTS frame.

According to some aspects, determining the format of the CTS frame may include checking a subfield in the RTS frame that indicates the format indicated by the transmitting STA. For example, the RTS frame may include a subfield (e.g., subfield 514 of fig. 5) to indicate to the receiving STA whether to use the CTS frame 600 or the CTS frame 620.

After determining the format of the CTS frame, the receiving STA may generate a CTS frame. At 906, one or more subchannels are examined to determine whether a subchannel is free. After generating the CTS frame and before transmitting the CTS frame, the receiving STA determines whether at least one sub-channel is idle. As described above, the receiving STA may determine the status of the medium using one or more CCA mechanisms.

At 908, the receiving STA may transmit a CTS frame to the transmitting STA in accordance with a punctured CTS transmission rule (e.g., as described in fig. 3A, 3B, and/or 7). According to some aspects, the receiving STA transmits a CTS frame on one or more subchannels on which the RTS frame was received in response to the one or more subchannels being idle based on the determined format.

Alternatively, the receiving STA transmits the CTS frame on the one or more subchannels on which the RTS frame was received in response to the one or more subchannels being idle and the one or more subchannels yielding a large Resource Unit (RU) aggregation mode based on the determined format.

In some examples, the one or more subchannels include a puncturing subchannel, and the receiving STA does not transmit the CTS frame on the puncturing subchannel.

According to some aspects, the receiving STA may receive data from the transmitting STA. In response to receiving the data, the receiving STA may transmit an ACK to the transmitting STA to indicate that the receiving STA correctly received the data.

For example, various aspects may be implemented using one or more computer systems, such as computer system 1000 shown in FIG. 10. Computer system 1000 may be any known computer capable of performing the functions described herein, such as devices 110, 120 of FIG. 1 or 400 of FIG. 4. Computer system 1000 includes one or more processors (also referred to as central processing units, or CPUs), such as processor 1004. The processor 1004 is connected to a communication infrastructure 1006 (e.g., a bus). Computer system 1000 also includes user input/output devices 1003 such as a monitor, keyboard, pointing device, etc. that communicate with the communication infrastructure 1006 via user input/output interfaces 1002. Computer system 1000 also includes a main or primary memory 1008, such as Random Access Memory (RAM). Main memory 1008 may include one or more levels of cache. The main memory 1008 has stored therein control logic (e.g., computer software) and/or data.

The computer system 1000 may also include one or more secondary storage devices or memories 1010. The secondary memory 1010 may include, for example, a hard disk drive 1012 and/or a removable storage device or drive 1014. Removable storage drive 1014 may be a floppy disk drive, a magnetic tape drive, an optical disk drive, an optical storage device, a tape backup device, and/or any other storage device/drive.

Removable storage drive 1014 may interact with a removable storage unit 1018. Removable storage unit 1018 includes a computer usable or readable storage device having stored therein computer software (control logic) and/or data. Removable storage unit 1018 may be a floppy disk, magnetic tape, optical disk, DVD, optical storage disk, and/or any other computer data storage device. Removable storage drive 1014 reads from and/or writes to removable storage unit 1018 in a well known manner.

According to some aspects, secondary memory 1010 may include other means, tools, or other methods for allowing computer programs and/or other instructions and/or data to be accessed by computer system 1000. Such means, tools, or other methods may include, for example, a removable storage unit 1022 and an interface 1020. Examples of a removable storage unit 1022 and interface 1020 may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM, or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and/or any other removable storage unit and associated interface.

Computer system 1000 may also include a communications or network interface 1024. Communication interface 1024 enables computer system 1000 to communicate and interact with any combination of remote devices, remote networks, remote entities, and the like, individually and collectively referenced by reference numeral 1028. For example, communication interface 1024 may allow computer system 1000 to communicate with remote device 1028 via a communication path 1026, which may be wired and/or wireless and may include any combination of a LAN, a WAN, the Internet, or the like. Control logic and/or data can be transferred to and from computer system 1000 via communications path 1026.

The operations in the foregoing aspects may be implemented in various configurations and architectures. Thus, some or all of the operations in the foregoing aspects may be performed in hardware, software, or both. In some aspects, a tangible, non-transitory apparatus or article of manufacture includes a tangible, non-transitory computer usable or readable medium having control logic components (software) stored thereon, also referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 1000, main memory 1008, secondary memory 1010, and removable storage units 1018 and 1022, as well as tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (such as computer system 1000), causes such data processing devices to operate as described herein.

Based on the teachings contained in this disclosure, it will be apparent to a person skilled in the relevant art how to make and use aspects of this disclosure using data processing devices, computer systems, and/or computer architectures other than that shown in FIG. 10. In particular, aspects may operate with software, hardware, and/or operating system implementations other than those described herein.

It should be understood that the detailed description section, and not the summary and abstract sections, is intended to be used to interpret the claims. The summary and abstract sections may set forth one or more, but not all exemplary aspects of the disclosure as contemplated by the inventors, and are therefore not intended to limit the disclosure or the appended claims in any way.

Although the present disclosure has been described herein with reference to exemplary fields and exemplary aspects of application, it should be understood that the present disclosure is not limited thereto. Other aspects and modifications are possible and are within the scope and spirit of the present disclosure. For example, and without limiting the generality of this paragraph, aspects are not limited to the software, hardware, firmware, and/or entities illustrated in the figures and/or described herein. Moreover, the aspects (whether explicitly described herein or not) have significant utility for fields and applications outside of the examples described herein.

Aspects have been described herein in terms of functional building blocks illustrating specific implementations of functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries may be defined so long as the specified functions and relationships (or equivalents thereof) are appropriately performed. In addition, alternative aspects may perform the functional blocks, steps, operations, methods, etc. in a different order than described herein.

References herein to "an aspect," "one embodiment," "an example embodiment," or similar phrases indicate that the embodiment described may include a particular feature, structure, or characteristic, but every aspect may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same aspect. Further, when a particular feature, structure, or characteristic is described in connection with an aspect, it is within the knowledge of one skilled in the relevant art to combine such feature, structure, or characteristic with other aspects whether or not explicitly mentioned or described herein.

The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary aspects, but should be defined only in accordance with the following claims and their equivalents.

As described above, various aspects of the present technology may include collecting and using data available from various sources, for example, to improve or enhance functionality. The present disclosure contemplates that, in some instances, such collected data may include personal information data that uniquely identifies or may be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information. The present disclosure recognizes that the use of such personal information data in the present technology may be useful to benefit the user.

The present disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and/or privacy practices. In particular, such entities should enforce and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data is collected and/or used. Personal information from the user should be collected for legitimate and legitimate uses by the entity and not shared or sold outside of these legitimate uses. Furthermore, such acquisition/sharing should only be done after receiving users informed consent. Furthermore, such entities should consider taking any necessary steps to defend and secure access to such personal information data, and to ensure that others who have access to the personal information data comply with their privacy policies and procedures. In addition, such entities may subject themselves to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to the particular type of personal information data collected and/or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the united states, the collection or acquisition of certain health data may be governed by federal and/or state laws, such as the health insurance transfer and accountability act (HIPAA); while other countries may have health data subject to other regulations and policies and should be treated accordingly. Therefore, different privacy practices should be maintained for different personal data types in each country.

Regardless of the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use or access to personal information data. That is, the present disclosure contemplates that hardware elements and/or software elements may be provided to prevent or block access to such personal information data. For example, the present technology may be configured to allow a user to selectively engage in "opt-in" or "opt-out" of collecting personal information data at any time, e.g., during or after a registration service. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to accessing or using personal information. For example, the user may be notified that their personal information data is to be accessed when the application is downloaded, and then be reminded again just before the personal information data is accessed by the application.

Further, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting data collection and deleting data. In addition, and when applicable, including in certain health-related applications, data de-identification may be used to protect the privacy of the user. De-identification may be facilitated by removing particular identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at a city level rather than at an address level), controlling how data is stored (e.g., aggregating data among users), and/or other methods, as appropriate.

Thus, while the present disclosure may broadly cover the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without the need to access such personal information data. That is, various embodiments of the present technology do not fail to function properly due to the lack of all or a portion of such personal information data.