Fast trigger request indication

Abstract

The invention provides a quick trigger request indication. Methods, systems, and computer-readable media configured to perform operations including: determining that an electronic device has at least one item to be sent to an access point (AP) or another electronic device; encoding a trigger request message with information associated with the at least one item to be transmitted; and transmitting the trigger request message to the AP to request an uplink (UL) resource allocation or a peer-to-peer (P2P) resource allocation.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 525,349, filed on July 6, 2023, which is incorporated herein by reference in its entirety. Background Art

[0003] Many electronic devices communicate with each other using wireless local area networks (WLANs), such as those based on communication protocols for wireless local area networks (also known as "Wi-Fi") that conform to Institute of Electrical and Electronics Engineers (IEEE) standards (e.g., IEEE 802.11 standards). A WLAN typically includes an access point (AP) that provides one or more stations (STAs) with access to another network, such as the Internet. There are many generations of the IEEE 802.11 standard, including 802.11ax (Wi-Fi 6) and 802.11be (Wi-Fi 7).

[0004] IEEE 802.11 is a packet-based protocol. According to the protocol, a transmitter (e.g., AP) packages control information or user data into a protocol data unit (PDU) in a physical layer convergence protocol (PLCP). A PLCP PDU (PPDU) includes a preamble and a data field, among other fields. After generating the PPDU, the AP can send the PPDU to a STA connected to (e.g., associated with) the AP. Communication from the AP to the STA is called a downlink (DL), and communication from the STA to the AP is called an uplink (UL). Summary of the invention

[0005] The present disclosure describes techniques and electronic devices for providing a fast trigger request indication from a STA to an AP to transmit UL data or peer-to-peer (P2P) data. The fast trigger request indication may be transmitted using an A control subfield in a quality of service (QoS) blank frame, an UL data frame encoded in a PPDU, a dedicated fast trigger request indication message, or other types of UL messages. The A control subfield or the fast trigger request indication (FTRI) field may include one or more bits of information about the UL transmission, including a traffic identifier (TID) and / or a queue size and optionally one or more other bits, as further discussed herein.

[0006] According to one aspect of the present disclosure, a method includes: determining that an electronic device has traffic (e.g., at least one item) to be sent to an AP or another electronic device; encoding a trigger request message using information related to the traffic to be sent; and sending the trigger request message to the AP for UL resource allocation or P2P resource allocation.

[0007] According to another aspect of the present disclosure, a method includes: receiving a trigger request message requesting UL resource allocation or P2P resource allocation from an electronic device, the trigger request message containing information associated with UL traffic to be sent by the electronic device; encoding a trigger frame (TF) using the UL resource allocation or the P2P resource allocation; and transmitting the TF to the electronic device.

[0008] In some embodiments, the trigger request message includes information about the traffic encoded in the A control subfield.

[0009] In some embodiments, the A Control subfield is part of a QoS Blank subframe of a Control Response (CR) frame.

[0010] In some embodiments, the A Control subfield is part of the UL PPDU.

[0011] In some embodiments, the trigger request message includes information about the traffic encoded in a dedicated FTRI frame.

[0012] In some embodiments, the trigger request includes: a P2P bit indicating whether the trigger request is for delivering traffic in P2P or between a STA and an infra-AP; a TID field for access category (AC) triggering and TID to link mapping (T2LM); a delay bound (DB) field indicating a tolerable delay bound or latency requirement for the traffic; and a QS field indicating the QS of the traffic in bytes (e.g., how much traffic the STA has in the queue to deliver on the UL or P2P link).

[0013] Some embodiments include receiving the TF from an AP with resource allocations for sending traffic in the UL or P2P link.

[0014] In some embodiments, the electronic device operates using a single link.

[0015] In some embodiments, the electronic device operates using multiple links.

[0016] In some embodiments, the electronic device sends the trigger request message on a first link and receives the TF on a second link different from the first link.

[0017] Aspects of the embodiments are directed to an apparatus comprising at least one baseband processor and an antenna, the apparatus configured to perform any of the operations described herein.

[0018] Aspects of the embodiments are directed to a non-transitory computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform any of the operations described herein.

[0019] The details of one or more embodiments of these systems and methods are set forth in the following drawings and description. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 A block diagram illustrates an example electronic device that communicates wirelessly in accordance with some implementations.

[0021] Figure 2A is a diagram illustrating an example message flow between an AP and an electronic device in single link operation for requesting UL resources and resource allocation using an A control subfield encoded in a control frame or a data frame according to some implementations.

[0022] Figure 2B is a diagram illustrating an example message flow between an AP and an electronic device for requesting UL resources and resource allocation using a control subfield encoded in a control frame or a data frame in multi-link operation (MLO) according to some implementations.

[0023] Figure 3 is a diagram illustrating an example message flow between an AP and an electronic device for requesting UL resources or P2P resources and resource allocation using an A control subfield encoded in a PPDU in single link operation according to some implementations.

[0024] Figure 4A is a diagram illustrating an example message flow between an AP and an electronic device for requesting UL resources or P2P resources using a fast triggered request indication in a simultaneous transmit and receive (STR) operation according to some implementations.

[0025] Figure 4B is a diagram illustrating an example message flow between an AP and an electronic device for requesting UL resources or P2P resources using a fast triggered request indication in enhanced multi-link single radio (EMLSR) operation according to some implementations.

[0026] Figure 5A is a schematic diagram of an example A control subfield with trigger request information according to an embodiment of the present disclosure.

[0027] Figure 5B is a diagram of an example dedicated fast trigger request indicator with trigger request information according to an embodiment of the present disclosure.

[0028] Figure 6 A flow chart illustrating an example method performed by an electronic device for requesting UL resources or P2P resources according to some implementations is illustrated.

[0029] Figure 7 A flow chart illustrating an example method performed by an AP for allocating UL resources or P2P resources according to some implementations is illustrated.

[0030] Figure 8 A block diagram of an example electronic device is illustrated according to some implementations. DETAILED DESCRIPTION

[0031] When a non-AP STA or non-AP multi-link device (MLD) has a high priority (HP) packet with latency sensitivity and needs to deliver latency sensitive traffic, the non-AP STA or non-AP MLD should be able to indicate polling to the AP or AP MLD in the UL. The present disclosure describes techniques for causing (or requesting) an AP or AP MLD to poll a non-AP STA or non-AP MLD.

[0032] There are already some procedures for indicating delay sensitive traffic to the AP, such as TSPEC (QoS characteristics of the flow) and the Flow Classification Service (SCS) mechanism. These are back and forth negotiations and do not take into account the immediacy of UL traffic flow. Moreover, these techniques do not take into account the dynamic nature of the UL. Currently, the specification lacks the ability for a STA to indicate an immediate request to be triggered to send its delay sensitive traffic. The present disclosure describes techniques by which traffic indications and / or resource requests can be sent by a non-AP STA or non-AP MLD and received by an AP or MLD.

[0033] SCS defines a pre-negotiated predetermined traffic pattern, while realistic traffic patterns are bursty in nature. The present disclosure describes techniques for requesting an AP to trigger resources and allocate resources to STAs to meet more spontaneous traffic demands (e.g., in addition to the traffic that the AP has been allocated), including high priority or latency sensitive traffic, or if there are a large number of conflicts and traffic demands retransmission. The AP as a resource manager can perform resource allocation and notify the resource allocation through a TF, which serves as a synchronization frame for STA transmissions in UL or P2P. Therefore, the AP can allocate resources for UL or P2P transmissions instead of independently contending for UL. The STA can also indicate additional information about the traffic within the request.

[0034] On the AP side, this disclosure describes a mechanism for determining whether a STA has traffic and sending a TF with resource allocation.

[0035] In addition, the present disclosure describes a P2P resource request indication from a STA to an AP for the AP to allocate resources for P2P using tools such as a transmission opportunity (TXOP) sharing trigger (TXS TF) mechanism. If the AP reserves resources for P2P, the AP needs to know the traffic and traffic type in order to correctly allocate resources for P2P.

[0036] In some embodiments, the STA may indicate a trigger request to the AP to be triggered on the same link (single link) or another link (multi-link).

[0037] The techniques described herein are applicable to single link and / or MLO, and can be used in the following scenarios: when all links are busy in the DL and the STA wants to indicate a trigger request to the AP; when the STA is transmitting HP traffic on a link in the UL and wants to indicate a trigger request for next polling; when the STA requests to be triggered on a link different from the one currently accessed (due to higher bandwidth, T2LM, etc.).

[0038] Figure 1 A block diagram 100 of an example of an electronic device for wireless communication according to some specific implementations is illustrated. It is noteworthy that one or more electronic devices 110 (such as a smart phone, a laptop, a notebook computer, a tablet computer, or another such electronic device) and an AP 112 can communicate wirelessly in a WLAN, for example, using an IEEE 802.11 communication protocol. Therefore, the electronic device 110 can be associated with the AP 112 or can have a connection with the AP. For example, the electronic device 110 and the AP 112 can communicate wirelessly in the following situations: detect each other by scanning a wireless channel, transmit and receive beacons or beacon frames on a wireless channel, establish a connection (e.g., by transmitting a connection request), and / or transmit and receive packets or frames (packets or frames may include requests and / or additional information such as data as payload). It is noted that the AP 112 can provide access to a network such as the Internet via an Ethernet protocol, and can be a physical AP or a virtual (or "software") AP implemented on a computer or electronic device. In this specification, the electronic device 110 is sometimes referred to as a "receiving electronic device" or "receiver STA".

[0039] Despite providing Figure 1The environment shown is used as an example, but in alternative implementations, there may be different numbers and / or types of electronic devices. For example, some implementations may include more or fewer electronic devices. As another example, in some implementations, different electronic devices may transmit and / or receive packets or frames. In some implementations, multiple links may be used during communication between electronic devices 110.

[0040] As referenced below Figure 8 As further described, the electronic device 110 and the AP 112 may include subsystems, such as a networking subsystem, a memory subsystem, and a processor subsystem. In addition, the electronic device 110 and the AP 112 may include a radio component 114 in the networking subsystem. More generally, the electronic device 110 and the AP 112 may include any electronic device having a networking subsystem (or may be included therein) that enables the electronic device 110 and the AP 112 to respectively communicate wirelessly with another electronic device. This may include transmitting beacons on a wireless channel to enable the electronic devices to make initial contact or detect each other, and then exchanging subsequent data / management frames (such as connection requests) to establish a connection, configure security options, transmit and receive packets or frames via the connection, etc.

[0041] like Figure 1 As shown, wireless signals 116 are transmitted by one or more radio components 114-1 and 114-2 in electronic device 110-1 and AP 112, respectively. For example, as previously described, electronic device 110-1 and AP 112 may exchange packets or frames using the Wi-Fi communication protocol in a WLAN. In addition, one or more radio components 114-1 may receive wireless signals 116 transmitted by one or more radio components 114-2 via one or more links between electronic device 110-1 and AP 112. Alternatively, one or more radio components 114-1 may transmit wireless signals 116 received by one or more radio components 114-2.

[0042] In some implementations, the wireless signals 116 are transmitted by one or more radio components 114 in the electronic device 110 and the AP 112, respectively. For example, the one or more radio components 114-1 and 114-3 can receive the wireless signals 116 transmitted by the one or more radio components 114-2 via one or more links between the electronic devices 110-1 and 110-2 and the AP 112.

[0043] In some implementations, the AP 112 may group the electronic devices 110 into a target STA set. The target STA set concept comes from DL multi-user transmission, where the AP 112 may use orthogonal frequency division multiple access (OFDMA) or multi-user (MU) multiple input multiple output (MU-MIMO) to transmit to multiple STAs simultaneously in one PPDU. Here, the target STA set is a set of STAs that can be served by the AP 112 at the same time. The STAs in the set do not need to share the same PHY parameters, such as MCS, number of streams, etc.

[0044] In some implementations, the AP 112 may use multi-user (MU) technology, such as MU multiple-input multiple-output (MU-MIMO), to communicate with multiple electronic devices 110 simultaneously. In some examples, the AP 112 communicates with the electronic devices 110 using frequency reuse, such that the AP 112 allocates a portion of the total bandwidth to each of the electronic devices. For example, in order to communicate with four electronic devices simultaneously over an 80 megahertz (MHz) bandwidth, the AP 112 transmits a MU-PPDU over the 80 MHz bandwidth. The MU-PPDU includes a sub-PPDU for each of the four electronic devices, where each sub-PPDU (or sub-channel) is allocated 20 MHz, for example, a corresponding 20 MHz sub-channel. The AP 112 may use the MU-PPDU to communicate with devices in the same target set, devices in different target sets, or a combination of both.

[0045] In some specific implementations, AP 112 and one or more electronic devices may be compatible with an IEEE 802.11 standard (e.g., IEEE 802.11ax) that includes trigger-based channel access. In 802.11ax, orthogonal frequency division multiple access (OFDMA) is used to enable simultaneous communication between AP 112 and multiple electronic devices. OFDMA divides the available physical spectrum into multiple orthogonal subchannels or resource units (RUs) that can be allocated to different electronic devices (users). According to the standard, AP 112 coordinates multi-user OFDMA by broadcasting a TF, which also allocates RUs to each participating electronic device. Each electronic device responds to the TF by transmitting a PPDU to AP 112 using the allocated RU. The TF may also include power control information. AP 112 may indicate when all electronic devices 110 start and stop transmission. It should be noted that AP 112 and electronic device 110 may communicate with one or more traditional electronic devices that are not compatible with the same IEEE 802.11 standard (i.e., do not use multi-user triggered channel access).

[0046] In some specific implementations, processing a packet or frame in one of the electronic device 110 and / or the AP 112 may include: receiving a wireless signal 116 that encodes the packet or frame; decoding / extracting the packet or frame from the received wireless signal 116 to obtain the packet or frame; and processing the packet or frame to determine information contained in the packet or frame (such as data in a payload).

[0047] As previously described, one or more electronic devices in the electronic device 110 and the AP 112 can communicate with each other. It is worth noting that the AP 112 can transmit a PPDU including a preamble and a data field. In some specific implementations, the AP 112 may be configured to use a cascaded PPDU (C-PPDU), for example, for low-latency communication with a receiver STA. The C-PPDU includes a plurality of component PPDUs, each of which includes a preamble and a data payload. As described in more detail below, the C-PPDU includes a plurality of component PPDUs. The first component PPDU is preceded by a first preamble called a "full preamble". Each of the remaining component PPDUs in the C-PPDU is preceded by a corresponding preamble having a length shorter than the first preamble. In some specific implementations, before transmitting a plurality of component PPDUs, the AP 112 may not perform contention or receive a block acknowledgement (BA).

[0048] According to aspects of the present disclosure, the STA may indicate a trigger request to the AP, requesting to be triggered on the same link or another link. The operations described below are applicable to single link operation and / or MLO.

[0049] Scenario 1 is the case where all links in DL are busy when the STA wants to indicate a trigger request to the AP. Figure 2A Scenario 1 of a single link is illustrated. Figure 2B Scenario 1 of MLO is illustrated. Scenario 2 is the case where the STA is transmitting HP traffic on the link in UL and the STA wants to indicate a trigger request to poll next. Figure 3 Scenario 2 is illustrated. Scenario 3 is the case where the STA request is triggered on a different link than the one currently being accessed (eg, due to higher bandwidth, T2LM, etc.). Figure 4A and Figure 4B Scenario 3 is illustrated.

[0050] Note that the AP may receive a trigger request and use that information to trigger the STA as soon as possible thereafter, taking into account the traffic information of the STA provided to the AP. The AP may use the trigger request as an indication of resource allocation to support UL transmissions, but it may respond with a TF with UL or P2P resource allocation information when resources become available.

[0051] The STA may request a TF 204 for UL traffic or P2P traffic by sending a fast trigger request to the AP in a data frame or using a CR frame during transmission of the UL traffic. For a single link, the AP upon receiving the trigger request may a) trigger the STA using the current TXOP duration or frame burst, b) contend for triggering the STA if there is not enough TXOP duration available, c) schedule the STA on UL MU transmission, or d) preempt the PPDU or TXOP / frame burst to poll the STA in the UL. Figure 2A is a diagram illustrating an example message flow between an AP 212 and a STA 210 for requesting UL resources or P2P resources and resource allocation using a control subfield encoded in a CR frame 202 or a data frame in a single link operation according to some implementations.

[0052] STA 210 is a TXOP responder and indicates a fast trigger request in CR frame 202 (eg, BA 206 + A control subfield in QoS blank 208).

[0053] In some instances, AP 212 can send TF 204 to STA 210 immediately after receiving the trigger request indication. In some other instances, AP 212 can trigger STA 210 after some delay (eg, based on delay bound information, resource availability, etc.).

[0054] Figure 2B is a diagram illustrating example message flows associated with request for UL resources or P2P resources and resource allocation using the A control subfield encoded in the CR frame 202 or data frame between the AP MLD 214 and the non-AP MLD 216 in MLO according to some implementations.

[0055] The non-AP MLD 216 may indicate a request for the TF 204 through the A control subfield in the UL PPDU or through one of the links when sending the CR frame 202 to the DL traffic.

[0056] AP MLD 214 may respond with TF 204 on any of the MLD links enabled with the requesting STA during the same TXOP / frame burst or in a new TXOP initiated by AP MLD 214.

[0057] When STA-1 has HP traffic, STA-1 indicates a fast trigger request sent over one link using the A control subfield in the CR frame 202 including a QoS blank frame 206 or a data frame in a UL PPDU (as described above).

[0058] Upon receiving the trigger request, in addition to the procedures mentioned for the single link case, the AP MLD 214 may a) contend for the same link (Link-1) or another link (Link-2) to trigger STA-1, or b) preempt the DL PPDU or TXOP / frame burst of any link covered by the T2LM of the requested TID to poll STA-1 in the UL if possible. Figure 2B In the example of FIG. 4 , AP-2 contends for and triggers STA-1 on link-2.

[0059] Figure 3 is a diagram illustrating an example message flow between the AP 312 and the STA1 310 in a single link operation for requesting UL resources or P2P resources and resource allocation using the A control subfield encoded in the PPDU according to some implementations.

[0060] STA1 310 is a TXOP initiator and does not terminate the current TXOP / frame burst. For example, STA1 310 indicates to AP 312 a request for P2P polling with another STA. P2P is an example, and STA1 310 may also request UL resources for communication with AP 312. AP 312 sends TXS TF 302 (mode-2) to reserve the medium for STA1 310 to deliver P2P traffic 304 to STA2 (not shown).

[0061] The AP 312 may send the TXS TF 302 to the STA1 310 for P2P purposes after receiving the trigger request indication, or alternatively may trigger the STA1 310 after a certain delay, for example, based on delay bound information, resource availability, etc.

[0062] In some embodiments (such as Figure 4A and Figure 4B ), the STA may send an FTRI frame 402 to the AP to request a TF 404 for UL traffic or for P2P communication. In response to the request, the AP acknowledges the FTRI frame 402 and schedules the TF 404 on one of the MLD-enabled links.

[0063] Figure 4A is a diagram illustrating an example message flow between the AP MLD 414 and the non-AP MLD 416 for requesting UL resources or P2P resources using a fast triggered request indication in STR operation according to some implementations.

[0064] exist Figure 4AIn the example of FIG. 4 , link-1 has a 20 MHz bandwidth and link-2 has an 80 MHz bandwidth. STA-1 prefers to use link-2 due to the higher bandwidth or T2LM, so STA-1 sends an FTRI frame 402 to indicate a request for TF 404. AP-2 decides to trigger STA-2 over link-2 upon receiving this information. AP-2 may trigger STA-2 immediately after receiving this indication or after a certain delay. Note that instead of the FTRI frame 402, a QoS blank frame 208 including an A control subfield may be used.

[0065] Figure 4B is a diagram illustrating an example message flow between the AP MLD 414 and the non-AP MLD 416 for requesting UL resources or P2P resources using a fast triggered request indication in EMLSR operation according to some implementations.

[0066] exist Figure 4B 4, link-2 is busy due to transmission from AP-2 to another non-AP MLD (not shown). STA-1 prefers to use link-2 due to higher bandwidth or T2LM, so STA-1 sends FTRI frame 402 to indicate a request for TF 404. AP MLD 414 triggers STA-2 over link-2 upon receiving this information. AP MLD 414 can trigger the STA immediately after receiving this indication or after some delay.

[0067] Figure 5A is a schematic diagram of an A control subfield with trigger request information according to an embodiment of the present disclosure. Figure 5B is a schematic diagram of a dedicated fast trigger request indicator with trigger request information according to an embodiment of the present disclosure.

[0068] The indication of a fast trigger request may be signaled in one of the following formats: an A control subfield sent in a CR frame or a Data frame, which is applicable to scenarios 1, 2, and 3; a new data / management / control frame (e.g., FTRI) that may be aggregated in an A-MPDU, which is applicable to scenarios 2 and 3; or a new data / management / control frame that may be aggregated in an A-MPDU, which is applicable to both of the aforementioned formats (e.g., A control subfield or FTRI).

[0069] The information required for the fast trigger request indication of the A control subfield may include one or more of the following: a P2P bit 502 indicating whether the trigger request is for delivering traffic in P2P or between a STA and an Infra AP; a TID field 504 indicating the TID of the traffic, used for per-AC triggering and facilitating TID to link mapping scenarios; a DB field 506 indicating a tolerable delay bound associated with the traffic; and a QS field indicating a queue size associated with the traffic (e.g., a single bit in bytes).

[0070] Similar information as described above may be used in the FTRI Info field 510 of the FTRI control frame 512. Information in the fast trigger request indication for the A control subfield or the FTRI control frame 512 may include one or more of the following: a P2P field 502 (e.g., 1 bit) indicating whether the trigger request is for delivering traffic in P2P or between a STA and an Infra AP; a TID field 504 (e.g., 4 bits) used for AC-by-AC triggering and also to help trigger the STA on the link based on the negotiated T2LM; and a DB field (e.g., 8 bits) including, for example, 1 bit for resolution (0:256μs, 1:1TU) and, for example, 7 bits for value. For resolution, when the value is 0, a delay limit of up to 32.8ms may be indicated, and when the value is 1, a delay limit of up to 128ms may be indicated.

[0071] The information in the fast trigger request indication may also include a QS field 508 (e.g., 12 bits), where the maximum PHY data rate at BW320 / MCS13 / NSS2 / GI0.8 is 5.76 Gbps. Considering VI / VO as HP traffic, the maximum TXOP duration may be considered to be 3 ms. The maximum amount of information that may be included in a PPDU with a duration of 3 ms is 17.292 Mbits or 2.16 Mbytes. The QS field 508 includes, for example, 1 bit for resolution (0: 256 bytes, 1: 1 kilobyte) and, for example, 11 bits for value. For resolution, when the value is 0, up to 0.52 Mbytes may be indicated; when the value is 1, up to 2.05 Mbytes may be indicated.

[0072] Figure 6 A flowchart of an example method for requesting UL resources or P2P resources performed by an electronic device according to some specific implementations is illustrated. For clarity of presentation, the following description generally describes method 600 in the context of other figures in this specification. For example, method 600 may be performed by Figure 1It should be understood that the method 600 may be performed by any suitable system, environment, software, hardware or a combination of systems, environments, software and hardware as appropriate. In some specific implementations, the various operations of the method 600 may be performed in parallel, in combination, cyclically or in different orders.

[0073] First, an electronic device such as a non-AP STA or a non-AP MLD can detect or determine (602) that there is traffic to be sent on UL or P2P. The traffic can be high priority traffic or delay sensitive traffic, where the electronic device needs to quickly make UL resource allocation or P2P resource allocation without having to conduct lengthy resource allocation negotiations with the AP. If resource allocation has been made for the electronic device, the resource allocation can be in addition to any resources already allocated to the electronic device.

[0074] The electronic device may encode (604) the traffic indication information into a trigger request message. The electronic device may encode the A control subfield into a QoS blank frame and include it in a CR frame. The electronic device may also encode the A control subfield in the UL PPDU, for example, by encoding the traffic indication information in the MPDU. The electronic device may also encode the A control subfield in a dedicated FTRI frame instead of a QoS blank frame.

[0075] Then, the electronic device may send (606) a trigger request to the AP. Depending on the scenario, the trigger request may be sent together with a CR frame, a ULPPDU, or a FTRI frame.

[0076] The electronic device may then receive (608) a TF from an AP with resource allocation for UL transmission. The electronic device may then transmit (610) traffic using UL resources or P2P resources according to the resource allocation.

[0077] Figure 6 The example method 600 shown may be modified or reconfigured to include additional, fewer, or different steps ( Figure 6 ), these steps may be performed in the order shown or in a different order.

[0078] Figure 7A flow chart of an example method for allocating UL resources or P2P resources performed by an AP according to some specific implementations is illustrated. The AP may receive (702) a trigger request from an electronic device. The AP may decode (704) the trigger request to identify an appropriate UL or P2P resource for the electronic device to send traffic. The AP may encode (706) a TF with the UL or P2P resource allocation for the electronic device. The AP may send (708) the TF to the electronic device. In some cases, the AP may then receive (710) traffic on the UL resources. If the resource allocation is for P2P, another electronic device may receive traffic on the P2P resources.

[0079] Figure 7 The example method 700 shown may be modified or reconfigured to include additional, fewer, or different steps ( Figure 7 ), these steps may be performed in the order shown or in a different order.

[0080] Figure 8 A block diagram of an electronic device 800 according to some specific implementations is illustrated. The electronic device 800 may be a mobile phone, a smart watch, an AP, a router, a wireless speaker, an Internet of Things (IoT) device, a portable computing device, and other examples. The electronic device 800 includes hardware resources 802, which include one or more processors (or processor cores) 810, one or more memory / storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840.

[0081] The one or more processors 810 include one or more devices configured to perform computing operations. For example, the one or more processors 810 may include one or more microprocessors, application specific integrated circuits (ASICs), microcontrollers, graphics processing units (GPUs), programmable logic devices, and / or one or more digital signal processors (DSPs). The processor 810 may include, for example, a processor 812 and a processor 814. The processor 810 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0082] The memory / storage device 820 may include a main memory, a disk storage device, or any suitable combination thereof. The memory / storage device 820 may include, but is not limited to, any type of volatile or non-volatile memory, such as a dynamic random access memory (DRAM), a static random access memory (SRAM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a solid-state storage device, and the like. In some specific implementations, the memory / storage device 820 is coupled to one or more high-capacity mass storage devices (not shown). In some examples, the memory / storage device 820 may be coupled to a disk drive or an optical drive, a solid-state drive, or another type of mass storage device. In these examples, the memory / storage device 820 may be used by the electronic device 800 as a fast access storage device for frequently used data, while the mass storage device is used to store less frequently used data.

[0083] The communication resources 830 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 804 or one or more databases 806 via the network 808. For example, the communication resources 830 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

[0084] The communication resources 830 include one or more devices configured to couple to and communicate on a wired and / or wireless network (i.e., perform network operations), such as: a control logic component, one or more interface circuits, and a set of antennas (or antenna elements) in an adaptive array that can be selectively turned on and / or off by the control logic component to produce a variety of optional antenna patterns or "beam patterns." Alternatively, instead of the set of antennas, in some examples, the electronic device 800 includes one or more nodes, such as pads or connectors, which can be coupled to the set of antennas. Thus, the electronic device 800 may or may not include the set of antennas. For example, the communication resources 830 may include a Bluetooth TM Networking systems, cellular networking systems (such as 3G / 4G / 5G / 6G networks, such as UMTS, LTE, etc.), universal serial bus (USB) networking systems, based on IEEE 802.11 (such as networking system), an Ethernet networking system, and / or another network system.

[0085] In some implementations, the communication resources 830 include one or more radio components, such as a wake-up radio component for receiving wake-up frames and wake-up beacons, and a main radio component for transmitting and / or receiving frames or packets during normal operating mode. The wake-up radio component and the main radio component can be implemented separately (such as using discrete components or separate integrated circuits) or in a common integrated circuit.

[0086] The communication resources 830 may include processors, controllers, radios / antennas, sockets / plugs, and / or other devices for coupling to, communicating on, and processing data and events for each supported networked system. Note that the mechanisms for coupling to, communicating on, and processing data and events on the networks of network systems are sometimes collectively referred to as the "network interfaces" of the network systems.

[0087] The instructions 850 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 810 to perform any one or more of the methods discussed herein. The instructions 850 may reside completely or partially in at least one of the processors 810 (e.g., in a cache memory of the processor), the memory / storage device 820, or any suitable combination thereof. In some implementations, any portion of the instructions 850 may be transmitted to the hardware resources 802 from any combination of the peripheral device 804 or the database 806. Thus, the memory of the processor 810, the memory / storage device 820, the peripheral device 804, and the database 806 are examples of computer-readable media and machine-readable media.

[0088] Although the foregoing discussion uses the Wi-Fi communication protocol as an illustrative example, in other specific implementations, a variety of communication protocols may be used, and more generally, wireless communication technologies may be used. Therefore, the communication technology may be used in a variety of network interfaces. In addition, although some of the operations in the foregoing specific implementations are implemented in hardware or software, in general, the operations in the foregoing specific implementations may be implemented in a variety of configurations and architectures. Thus, some or all of the operations in the foregoing specific implementations may be performed in hardware, in software, or in a combination of both hardware and software. For example, at least some of the operations in the communication technology may be implemented using instructions 850, an operating system (such as a driver for an interface circuit in the communication resource 830), or in firmware in an interface circuit in the communication resource 830. Additionally or alternatively, at least some of the operations in the communication technology may be implemented in a physical layer (such as hardware in an interface circuit in the communication resource 830). In some specific implementations, the communication technology is implemented at least partially in a MAC layer and / or a physical layer in an interface circuit in the communication resource 830.

[0089] Although the foregoing embodiments illustrate the use of wireless signals in one or more frequency bands, in some implementations, electromagnetic signals in one or more different frequency bands are used to determine distance. For example, these signals may be communicated in one or more frequency bands, including: microwave bands, radar bands, 900 MHz, 2.4 GHz, 5 GHz, 6 GHz, 60 GHz, and / or frequency bands used by Citizens Broadband Radio Service, LTE, 5G, or any other communication system.

[0090] Although specific components are used to describe the electronic device 800, in some implementations, different components and / or subsystems may be present in the electronic device 800. For example, the electronic device 800 may include one or more additional processing subsystems, memory subsystems, networking subsystems, and / or display subsystems. Additionally, one or more of the subsystems may not be present in the electronic device 800. In some implementations, the electronic device 800 may include Figure 8 In some implementations, the electronic device may include an analysis subsystem that performs at least some of the operations in the communication technology. Figure 8 800 , some or all of a given subsystem or component may be integrated into one or more of the other subsystems or components in electronic device 800 .

[0091] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0092] As described above, one aspect of the present technology may involve collecting and using data that can be obtained from specific and legitimate sources to allow interaction with a second device for data transfer. The present disclosure contemplates that, in some instances, the collected data may include personal information data that uniquely identifies or can be used to identify a specific person. Such personal information data may include demographic data, location-based data, online identifiers, phone numbers, email addresses, home addresses, data or records related to the user's health or fitness level (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other personal information.

[0093] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit the user. For example, the personal information data can be used to provide a secure data transfer between a first device and a second device. The personal information data can also be used to identify an account associated with the user from a service provider to complete the data transfer.

[0094] The disclosure envisions 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. Specifically, it is expected that such entities will implement and consistently apply privacy practices that are generally recognized as meeting or exceeding the industry or government requirements for maintaining user privacy. Such information about the use of personal data should be highlighted and easily accessible to users, and should be updated as the collection and / or use of data changes. The user's personal information should be collected only for legal use. In addition, such collection / sharing should only occur after receiving user consent or other legal basis specified in applicable law. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data, and ensure that other entities with access to personal information data comply with their privacy policies and procedures. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted for specific types of personal information data collected and / or accessed, and applied to applicable laws and standards, including considerations that are exclusive to jurisdictions that can be used to impose higher standards. For example, in the United States, collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly.

[0095] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of 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 technology of the present invention may be configured to allow users to choose to "opt in" or "opt out" to participate in the collection of personal information data anytime, anywhere during or after registration for a service. For example, a user may "opt in" or "opt out" of information associated with a user account stored on a user device and / or shared by a user device. In addition to providing "opt in" and "opt out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may be notified when downloading an application that their personal information data will be accessed, and then the user may be reminded again before the personal information data is accessed by the application. In some instances, a user may be notified when a data transfer is initiated in which a device accesses information associated with a user's account and / or shares information associated with the user's account with another device.

[0096] In addition, it is the intention of the present disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting the collection of data and deleting the data. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be promoted when appropriate by removing identifiers, controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods such as differential privacy.

[0097] Thus, while the present disclosure broadly covers 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 access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, content may be selected and delivered to a user based on aggregated non-personal information data or an absolute minimum amount of personal information, such as content processed only on the user's device or other non-personal information that may be used for content delivery services.

Claims

1. A method, comprising: determining that the electronic device has at least one item to send to an access point (AP) or another electronic device; encoding a trigger request message with information related to the at least one item; as well as The trigger request message is sent to the AP to request uplink (UL) resource allocation or peer-to-peer (P2P) resource allocation.

2. The method of claim 1, wherein the trigger request message encodes the information related to the at least one item in an A control subfield.

3. The method of claim 2, wherein the A control subfield is part of a Quality of Service (QoS) blank subframe of a Control Response (CR) frame.

4. The method of claim 2, wherein the A-control subfield is part of a UL physical layer protocol data unit (PPDU).

5. The method of claim 1, wherein the trigger request message encodes the information related to the at least one item in a dedicated Fast Trigger Request Indicator (FTRI) frame.

6. The method according to claim 1, wherein the trigger request message comprises: a P2P bit indicating whether the trigger request message is associated with transmitting the at least one item over a P2P connection or between a STA and an infrastructure AP; Traffic Identifier (TID) field, which triggers per Access Category (AC) and assists in TID to Link Mapping (T2LM); a delay bound (DB) field indicating a tolerable delay bound for the at least one item; and A queue size (QS) field indicating a size of the at least one item that the STA has queued for delivery on the UL.

7. The method of claim 1, further comprising receiving, from the AP, a trigger frame (TF) having a resource allocation for sending the at least one item on a UL to the AP or a P2P device. 8 . The method of claim 7 , wherein the electronic device sends the trigger request message on a first link, and receives the TF on a second link different from the first link.

9. The method of claim 1, wherein the electronic device operates using a plurality of links.

10. A method comprising: receiving, from an electronic device, a trigger request message requesting uplink (UL) resource allocation or peer-to-peer (P2P) resource allocation, the trigger request message including information associated with at least one item to be sent by the electronic device; encoding a trigger frame (TF) using the UL resource allocation or the P2P resource allocation; and The TF is sent to the electronic device.

11. The method of claim 10, wherein the trigger request message encodes the information related to the at least one item in an A control subfield.

12. The method of claim 11, wherein the A control subfield is part of a Quality of Service (QoS) blank subframe of a Control Response (CR) frame.

13. The method of claim 11, wherein the A-control subfield is part of a UL physical layer protocol data unit (PPDU).

14. The method of claim 10, wherein the trigger request message encodes the information related to the at least one item in a dedicated Fast Trigger Request Indicator (FTRI) frame.

15. The method according to claim 10, wherein the trigger request message comprises: a P2P bit indicating whether the trigger request message is associated with transmitting the at least one item over a P2P connection or between a STA and an infrastructure AP; Traffic Identifier (TID) field, which triggers per Access Category (AC) and assists in TID to Link Mapping (T2LM); a delay bound (DB) field indicating a tolerable delay bound for the at least one item; and A queue size (QS) field indicating a size of the at least one item that the STA has queued for delivery on the UL. The method of claim 10 , wherein the electronic device operates using a plurality of links. 17 . The method of claim 10 , wherein the electronic device sends the trigger request message on a first link, and receives the TF on a second link different from the first link.

18. An apparatus of a baseband processor circuit, the apparatus being configured to perform operations comprising: determining that at least one data item is to be sent to an access point (AP) or a second electronic device; encoding a trigger request message using information associated with the at least one data item; as well as A signal corresponding to the trigger request message is output to an interface, wherein the trigger request message requests uplink (UL) resource allocation or peer-to-peer (P2P) resource allocation from the AP.

19. The apparatus of claim 18, wherein the trigger request message encodes the information related to the at least one item in an A control subfield.

20. The apparatus of claim 19, wherein the A control subfield is part of a Quality of Service (QoS) blank subframe of a control response (CR) frame.

Images