Environment power ppdu format design for wireless communication

Abstract

This disclosure describes techniques related to the design of the Ambient Power (AMP) Physical Layer Protocol Data Unit (PPDU) format for wireless communication. An apparatus (e.g., a station (STA)) performs wireless communication by (i) generating and transmitting a PPDU; or (ii) receiving and processing the PPDU. The PPDU includes a conventional preamble followed by an AMP packet. The conventional preamble includes a conventional short training field (L-STF), a conventional long training field (L-LTF), a conventional signaling field (L-SIG), a redundant conventional signaling field (RL-SIG), and at least two universal signaling fields (U-SIGs).

Description

[0001] Cross-references to related applications

[0002] This disclosure is part of a non-provisional patent application that claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 569,252, filed March 25, 2024, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to wireless communication, and more specifically, to the design of an ambient power (AMP) physical-layer protocol data unit (PPDU) format for wireless communication. Background Technology

[0004] Unless otherwise specified herein, the solutions described in this section are not prior art to the following claims and are not recognized as prior art by virtue of their inclusion in this section.

[0005] In wireless communications such as Wi-Fi (or WiFi) according to the Institute of Electrical and Electronics Engineers (IEEE) specifications, battery-free and maintenance-free wireless solutions are gaining increasing attention. Passive radio frequency identification (RFID) once dominated this market; however, its application is often limited by its transmission distance and lack of network-level backhaul. Therefore, additional human resources are required to achieve low-maintenance automated systems. On the other hand, deploying AMP devices that can directly connect to the network in a wireless local area network (WLAN) enables a wide range of applications and reduces labor costs. Ideally, AMP devices should be low-cost and low-power devices. Furthermore, coexistence with the IEEE 802.11 standard is crucial. Therefore, a solution for designing AMP PPDU format for wireless communication is needed. Summary of the Invention

[0006] The following description is illustrative only and is not intended to be limiting in any way. That is, the following description is intended to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Selected embodiments are further described below in the detailed description. Therefore, the following description is not intended to identify the essential features of the claimed subject matter, nor is it intended to define the scope of the claimed subject matter.

[0007] One object of this disclosure is to provide schemes, concepts, designs, techniques, methods, and apparatus related to the design of AMP PPDU formats for wireless communication. It is believed that by implementing one or more of the various proposed schemes described herein, the aforementioned problems can be avoided or otherwise mitigated. For example, implementing one or more novel AMP PPDU format designs under the proposed schemes can enhance coexistence with IEEE 802.11be+ sites (STAs).

[0008] In one aspect, a method may involve a processor of a device performing wireless communication by: (i) generating and transmitting a PPDU; or (ii) receiving and processing the PPDU. The PPDU may include a conventional preamble followed by an AMP packet.

[0009] In another aspect, an apparatus may include a transceiver configured to perform wireless communication and a processor coupled to the transceiver. The processor may perform wireless communication by (i) generating and transmitting a PPDU; or (ii) receiving and processing the PPDU. The PPDU may include a conventional preamble followed by an AMP packet.

[0010] It is worth noting that although the descriptions provided herein may be given in the context of certain wireless access technologies, networks, and network topologies such as Wi-Fi, the proposed concepts, schemes, and any variations / derivatives thereof can also be implemented, for, and by other types of wireless access technologies, networks, and network topologies, such as, but not limited to, Bluetooth, ZigBee, and 5G (5G). th Generation (5G) / New Radio (NR), Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Industrial IoT (IIoT), and Narrowband IoT (NB-IoT). Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0011] The accompanying drawings are included to provide a further understanding of this disclosure and are incorporated in and constitute a part of this disclosure. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to actual dimensions in order to clearly illustrate the concepts of the disclosure.

[0012] Figure 1 This is a schematic diagram of an example network environment in which various solutions and schemes based on this disclosure can be implemented.

[0013] Figure 2 This is a schematic diagram of an example scenario based on the proposed solution in this disclosure.

[0014] Figure 3 This is a schematic diagram of an example design based on the scheme proposed in this disclosure.

[0015] Figure 4 This is a schematic diagram of an example design based on the scheme proposed in this disclosure.

[0016] Figure 5 This is a block diagram of an example communication system based on the proposed scheme of this disclosure.

[0017] Figure 6 This is a flowchart of an example process based on the proposed scheme of this disclosure. Detailed Implementation

[0018] This document discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be embodied in various forms. This disclosure may be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided to make the description of this disclosure exhaustive and complete, and to fully communicate the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and technologies may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0019] Overview

[0020] Embodiments of this disclosure relate to various techniques, methods, schemes, and / or solutions related to the design of AMP PPDU formats for wireless communication. According to this disclosure, multiple possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described separately below, two or more of these possible solutions may be implemented in one or another combination.

[0021] Figure 1 An example network environment 100 is shown that various solutions and schemes based on this disclosure can be implemented. Figures 2-6 Examples of implementing various proposed schemes in a network environment 100 according to this disclosure are shown. The following references... Figures 1-6 Provide descriptions of the various proposed solutions.

[0022] refer to Figure 1 Network environment 100 may involve at least stations (STAs) 110 and STA 120 communicating wirelessly. Each of STAs 110 and 120 may be an access point (AP) STA, or otherwise used as an AP STA, or alternatively a non-AP STA. STAs 110 and 120 may be configured or otherwise capable of operating according to the same or different IEEE 802.11 standards (e.g., IEEE 802.11be and future standards). Each of STAs 110 and 120 may be configured to communicate with each other using techniques related to the design of the AMP PPDU format for wireless communication, according to the various proposed schemes described below. It is worth noting that although the various proposed schemes may be described individually or separately below, in practice, some or all of the proposed schemes may be used in combination or otherwise implemented together. Of course, each of the proposed schemes may also be used individually or separately or otherwise implemented.

[0023] To achieve better coexistence under the various proposed schemes according to this disclosure, the novel AMP PPDU format design can adopt a preamble design similar to that in IEEE 802.11be (e.g., legacy short training field (L-STF), legacy long training field (L-LTF), legacy signaling field (L-SIG), redundant legacy signaling field (RL-SIG), and universal signaling field (U-SIG)). In the first option (Option 1), for narrow bandwidth (BW) (e.g., BW < 20MHz), AMP packets can be added after the first universal signaling field (U-SIG1) and the second universal signaling field (U-SIG2). In the second option (Option 2), for narrow bandwidth (e.g., BW < 20MHz), AMP packets can be added after U-SIG1, U-SIG2, and repeating U-SIGs (e.g., the third U-SIG (U-SIG3) and the fourth U-SIG (U-SIG4)). The content of the U-SIG can include version-independent fields (e.g., physical-layer (PHY) version, bandwidth, basic service set (BSS) color, downlink (DL) / uplink (UL), and transmission opportunity (TXOP)). Furthermore, under the proposed scheme, an indicator can be added to the AMP PPDU in the traditional PHY preamble (20MHz) portion of the PPDU. For example, in the first option (Option 1), the indicator can be a 1-bit indicator that can reuse one or more reserved bits from the U-SIG (e.g., the Validate bit and the Disregard bit). In the second option (Option 2), the indicator can be used in the PHY version subfield using one or more reserved entries (e.g., PHY version = 7).

[0024] Under the various proposed schemes according to this disclosure, the AMP AP can support IEEE 802.11be and higher versions. For coexistence considerations, conventional preambles (e.g., conventional preambles in orthogonal frequency-division multiplexing (OFDM) format) can be applied in the AMP PPDU (e.g., at least in the pre-High-Throughput (pre-HT) portion of the DL), as this can help the Wi-Fi STA perform backoff. Additionally, incoherent waveforms (e.g., amplitude-shift keying (ASK) and / or on-off keying (OOK)) can be applied to the DL data portion (e.g., from the AP to a non-AP STA, or from the reader to the tag) to reduce power consumption. Therefore, IEEE 802.11ba-like PPDUs (e.g., PPDUs with 20MHz preambles and 4MHz multi-carrier on-off keying (MC-OOK) data) are strong candidates for AMP DL applications.

[0025] Figure 2 Example scenario 200 regarding AMP DL PPDU is shown. Currently, AMP DL designs tend to focus on waveform designs similar to IEEE 802.11ba, as illustrated in the example. Figure 2 More specifically, the AMP DL design includes a 20MHz OFDM spoofing preamble and a 4MHz MC-OOK AMP packet.

[0026] It is worth noting that initially only binary phase-shift keying (BPSK) mark 1 was added to the wake-up radio (WUR). BPSK mark 1 was designed to trick IEEE 802.11 STAs into mistaking WUR PPDUs for IEEE 802.11a PPDUs, thus causing IEEE 802.11ax+ STAs to waste power when receiving WUR PPDUs. Because WUR data is narrowband and depends on its implementation, the next 4µs symbol duration after BPSK mark 1 might be interpreted as orthogonal BPSK (Q-BPSK). In this case, Very-High-Throughput (VHT) STAs might identify WUR PPDUs as VHT PPDUs, which could lead to unpredictable behavior from VHT STAs. Therefore, BPSK mark 2 was added to trick VHT STAs.

[0027] Assuming AMP uses IEEE 802.11ba PPDUs (e.g., 20MHz preambles with narrow BW AMP packets), several issues may need to be considered. First, many IEEE 802.11be+ STAs may apply target wake time (TWT) / restricted TWT (rTWT) to conserve power. However, if they receive AMP PPDUs from overlapping basic service sets (OBSSs) (if directly reusing IEEE 802.11ba PPDUs), IEEE 802.11be+ STAs may waste their time processing the data portion (treating it as an IEEE 802.11a PPDU) and miss the expected Extremely High Throughput (EHT) and higher versions of PPDUs (e.g., network allocation vectors (NAVs) within the intra-basic service set, intra-BSS) expected in this BSS (myBSS). Secondly, the BPSK-mark does not provide sufficient information to allow IEEE 802.11be+ STAs to determine the format of incoming PPDUs (e.g., PHY version, BSS color, DL / UL, TXOP) early, often wasting the power of third-party IEEE 802.11be+ STAs. Thirdly, there is a power drop between the traditional preamble and the OOK portion. On the other hand, in fading channels, the received power during the on-duration period may fall below a certain threshold, which, combined with the off-duration period, may cause some STAs to detect an idle channel. In this case, the clear channel assessment (CCA) rules determined by the LENGTH field in L-SIG may not be followed because the third-party STA cannot decode the OOK data portion, thus lacking medium access control (MAC) information for its use. TXOP information (set by the third-party STA using NAV) is desirable to protect the reception of AMPPPDUs. Furthermore, some AMP applications tend to focus on short ranges (e.g., backscatter type tags). Therefore, the BSS color information in the spoofing preamble allows IEEE 802.11be+ STAs to utilize spatial reuse when the power of the detected AMP PPDU is below a certain threshold. Thus, it is desirable to allow the spoofing preamble to have multiple uses. It is also desirable to allow IEEE 802.11be+ STAs to identify AMP PPDUs.

[0028] Figure 3 An example design 300 based on the proposed scheme of this disclosure is shown. Under the proposed scheme, to achieve better coexistence, the AMP PPDU format design can adopt a preamble design from IEEE 11be (including fields such as L-STF, L-LTF, L-SIG, RL-SIG, and U-SIG), which can provide additional information for IEEE 802.11be+ devices. Regarding the content of U-SIG, under the proposed scheme, a version-independent field (and optionally one or more other fields, such as PHY version, bandwidth, BSS color, DL / UL, TXOP) can be retained in the AMP PPDU.

[0029] Under the proposed scheme, two options are possible. In the first option (Option 1), for narrow BW (e.g., BW < 20MHz), AMP packets can be added after U-SIG1 and U-SIG2. In the second option (Option 2), for narrow BW (e.g., BW < 20MHz), AMP packets can be added after U-SIG1, U-SIG2, and repeating U-SIGs (e.g., U-SIG3 and U-SIG4). The paired preambles and AMP waveforms under Option 2 can cover a longer distance than under Option 1. It is believed that Design 300 may add 4µs (or 12µs, depending on the option); however, this is only a small fraction compared to low-rate PPDUs (e.g., PPDUs with 2–3ms airtime). Nevertheless, Design 300 is believed to significantly improve network performance. Therefore, under the proposed scheme, the preamble of the AMP DL PPDU may include L-STF, L-LTF, L-SIG, RL-SIG, and U-SIG for use in 2.4 GHz non-AP STAs supporting AMP as well as actively transmitted non-AP AMP STAs.

[0030] Figure 4An example design 400 based on the proposed scheme according to this disclosure is shown. In the proposed scheme, to achieve better power saving by allowing early termination (e.g., by allowing IEEE 802.11be+ STAs to recognize AMP PPDUs), an indicator can be added to the design of the AMP PPDU format, for example, added to the conventional PHY preamble (20MHz) section. In the proposed scheme, two options are possible. In the first option (Option 1), the indicator can be a bit indicator that can reuse U-SIG reserved bits (e.g., the Validate bit and the Disregard bit). In the second option (Option 2), the indicator can be indicated in the PHY version using a reserved entry (e.g., PHY version = 7). For example, when using the Validate bit to indicate that a given PPDU is an AMP PPDU, when an IEEE 11be STA receives the AMP PPDU, the STA can perform early termination and postpone the duration indicated in the PHY header.

[0031] Under the proposed scheme, other information can also be carried in the U-SIG for AMP reception. For example, one type of additional information that can be carried in the U-SIG is the AMP PPDU type. Alternatively, another type of additional information that can be carried in the U-SIG is an indication of the reference symbol and its length.

[0032] Illustrative Implementation

[0033] Figure 5 An example system 500 having at least example apparatus 510 and example apparatus 520 according to one embodiment of the present disclosure is shown. Each of apparatus 510 and apparatus 520 can perform various functions to implement the schemes, techniques, processes, and methods described herein in relation to the design of AMP PPDU formats for wireless communication, including the various schemes described above with respect to various proposed designs, concepts, schemes, systems, and methods, as well as the processes described below. For example, apparatus 510 may be implemented in STA 110, and apparatus 520 may be implemented in STA 120, or vice versa.

[0034] Each of devices 510 and 520 may be part of an electronic device, which may be a non-AP STA or AP STA, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. When implemented in an STA, each of devices 510 and 520 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet, laptop, or notebook computer. Each of devices 510 and 520 may also be part of a machine-type device, which may be an IoT device, such as a non-movable or fixed device, a home appliance, a wired communication device, or a computing device. For example, each of devices 510 and 520 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. When implemented in or as a network device, devices 510 and / or 520 may be implemented in a network node, such as an AP in a WLAN.

[0035] In some embodiments, each of devices 510 and 520 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set computing (RISC) processors, or one or more complex-instruction-set computing (CISC) processors. In the various embodiments described above, each of devices 510 and 520 may be implemented in a STA or AP, or implemented as a STA or AP. Each of devices 510 and 520 may include... Figure 5 At least some of the components shown are, for example, processors 512 and 522, respectively. Each of devices 510 and 520 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the proposed solutions of this disclosure; therefore, such components of devices 510 and 520 are not... Figure 5 It is shown in the text and not described below, in order to be concise.

[0036] In one aspect, each of processors 512 and 522 may be implemented as one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, although the singular term "a processor" is used herein to refer to processors 512 and 522, each of processors 512 and 522 may include multiple processors in some embodiments and a single processor in other embodiments, according to this disclosure. In another aspect, each of processors 512 and 522 may be implemented as hardware (and optional firmware) having electronic components, such as, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes, configured and arranged to perform a particular purpose according to this disclosure. In other words, in at least some embodiments, each of processors 512 and 522 is a dedicated machine specifically designed, arranged, and configured to perform a particular task, including tasks related to the design of AMP PPDU formats for wireless communication according to various embodiments of this disclosure.

[0037] In some embodiments, device 510 may further include a transceiver 516 coupled to processor 512. Transceiver 516 may include a transmitter capable of wireless transmission and a receiver capable of wirelessly receiving data. In some embodiments, device 520 may further include a transceiver 526 coupled to processor 522. Transceiver 526 may include a transmitter capable of wireless transmission and a receiver capable of wirelessly receiving data. It is worth noting that although transceivers 516 and 526 are shown as being external to and separate from processors 512 and 522, respectively, in some embodiments, transceiver 516 may be a component of processor 512 as a system-on-a-chip (SoC), and transceiver 526 may be a component of processor 522 as a SoC.

[0038] In some embodiments, device 510 may further include memory 514 coupled to processor 512, accessible by processor 512, and storing data therein. In some embodiments, device 520 may further include memory 524 coupled to processor 522, accessible by processor 522, and storing data therein. Each of memory 514 and memory 524 may include a type of random-access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively or additionally, each of memory 514 and memory 524 may include a type of read-only memory (ROM), such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively or additionally, each of memories 514 and 524 may include a type of non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0039] Each of devices 510 and 520 may be a communication entity capable of communicating with each other using various proposed schemes according to this disclosure. For illustrative purposes and not for limitation, the capabilities of device 510 as STA 110 and device 520 as STA 120 are described below in the context of example process 600. It is worth noting that although a detailed description of the capabilities, functions, and / or technical features of either device 510 or device 520 is provided below, the same description may also be applied to the other of devices 510 and device 520, although its detailed description is not provided for the sake of brevity. It is also worth noting that although the example implementations described below are provided in the context of WLAN, the same implementations may also be implemented in other types of networks.

[0040] Explanatory process

[0041] Figure 6An example process 600 according to one embodiment of the present disclosure is shown. Process 600 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, process 600 may represent one aspect of proposed concepts and schemes related to the design of AMP PPDU format for wireless communication according to the present disclosure. Process 600 may include one or more operations, actions, or functions shown by block 610 and one or more sub-blocks 612 and 614. Although shown as discrete blocks, the individual blocks of process 600 may be divided into additional blocks, merged into fewer blocks, or removed depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 600 may be arranged in... Figure 6 The execution may be performed in the order shown, or alternatively in a different order. Additionally, one or more blocks / subblocks of process 600 may be executed repeatedly or iteratively. Process 600 may be implemented by or in devices 510 and 520, and any variations thereof. For illustrative purposes only and without limitation, process 600 is described below in the context of device 510 being implemented in STA 110 or as STA 110 and used as a non-AP STA, and device 520 being implemented in STA 120 or as STA 120 and used as an AP STA in a network environment 100 compliant with one or more IEEE 802.11 standards, in the context of a wireless network such as WLAN. Process 600 may begin with block 610.

[0042] At 610, process 600 may involve the processor 512 of device 510 performing wireless communication involving a PPDU (e.g., wireless communication with device 520) via transceiver 516, the PPDU including a conventional preamble followed by an AMP packet. The execution of the wireless communication may be represented by 612 and 614.

[0043] At 612, process 600 may involve processor 512 generating and sending the PPDU.

[0044] At 614, process 600 may involve processor 512 receiving and processing the PPDU.

[0045] In some implementations, the conventional preamble may include L-STF, L-LTF, L-SIG, RL-SIG, and at least two U-SIGs. In some implementations, the content of each of the at least two U-SIGs may include one or more version-independent fields. In some implementations, the one or more version-independent fields may include at least one of a PHY version field, a bandwidth field, a BSS color field, a DL / UL field, and a TXOP field. In some implementations, at least one of the at least two U-SIGs may carry information for AMP reception, wherein the information includes either or both of the following: (a) the AMP PPDU type; and (b) an indication of a reference symbol and its length.

[0046] In some embodiments, the AMP packet may include a narrowband AMP packet. In some embodiments, the narrowband AMP packet may include a 4MHz AMP packet, and the conventional preamble may include a 20MHz preamble.

[0047] In some implementations, the PPDU may include an indication in the conventional preamble that indicates the PPDU is an AMP PPDU. In some implementations, the indication may include a bit indicator that reuses one or more U-SIG reserved bits. Alternatively or additionally, the indication may be provided using one or more reserved entries in the PHY version.

[0048] Additional notes

[0049] The topics described herein sometimes illustrate different components contained within or connected to different other components. It should be understood that such architectures depicted are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components that achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined herein to achieve a particular function can be considered “associated” with each other to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” to each other to achieve the desired function, and any two components that can be suchly associated can also be considered “operably coupled” to each other to achieve the desired function. Specific examples of being operablely coupled include, but are not limited to, physically matable and / or physically interactive components, and / or wirelessly interactive and / or logically interactive components.

[0050] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can appropriately convert from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly described herein.

[0051] Furthermore, those skilled in the art will understand that, in general, the terms used herein, and especially in the appended claims (e.g., in the body of the appended claims), are often intended as “open-ended” terms; for example, the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including but not limited to,” and so on. Those skilled in the art will also understand that if there is an intent to indicate a specific quantity recited in the introduced claim, that intent will be explicitly stated in the claim, and such an intent will not exist in the absence of such a statement. For example, for ease of understanding, the appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce the recitation of a claim. However, the use of such phrases should not be construed as implying that a claim recitation introduced by the indefinite article "a" or "an" limits any particular claim containing such a recitation to an embodiment containing only one such recitation, even if the same claim includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"; the same applies to the use of definite articles used to introduce a claim recitation. Furthermore, even if a specific number of recitations in the introduced claims is explicitly stated, those skilled in the art will recognize that such recitations should be interpreted as meaning at least the number recitations; for example, simply stating "two recitations" without other modifiers means at least two recitations or two or more recitations. Furthermore, in cases where conventions such as "at least one of A, B, and C" are used, generally, such structures are intended to mean as understood by those skilled in the art; for example, "a system having at least one of A, B, and C" will include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together. In cases where conventions such as "at least one of A, B, or C" are used, generally, such structures are intended to mean as understood by those skilled in the art; for example, "a system having at least one of A, B, or C" will include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together. Those skilled in the art will also understand that any transition words and / or phrases presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to cover the possibility of including one of the terms, any one of the terms, or both of the terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B".

[0052] As can be understood from the foregoing, various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the following claims.

Claims

1. A method comprising: Wireless communication is performed by the device's processor in the following manner: Generate and send Physical Layer Protocol Data Units (PPDUs); or Receive and process the PPDU. The PPDU includes a conventional preamble, followed by an ambient power (AMP) packet. The traditional preamble includes a traditional short training field (L-STF), a traditional long training field (L-LTF), a traditional signaling field (L-SIG), a redundant traditional signaling field (RL-SIG), and at least two universal signaling fields (U-SIG).

2. The method according to claim 1, wherein, The content of each of the at least two U-SIGs includes one or more version-independent fields.

3. The method according to claim 2, wherein, The one or more version-independent fields include at least one of the following: Physical Layer (PHY) version field, bandwidth field, Basic Service Set (BSS) color field, Downlink (DL) / Uplink (UL) field, and Transmission Opportunity (TXOP) field.

4. The method according to claim 1, wherein, At least one of the at least two U-SIGs carries information for AMP reception, and wherein the information includes either or both of the following: AMP PPDU type; and Reference symbols and their length indications.

5. The method according to claim 1, wherein, The AMP package includes a narrowband AMP package.

6. The method according to claim 5, wherein, The narrowband AMP packet includes a 4MHz AMP packet, and the conventional preamble includes a 20MHz preamble.

7. The method according to claim 1, wherein, The PPDU includes an indication in the conventional preamble that indicates the PPDU is an AMP PPDU.

8. The method according to claim 7, wherein, The indication includes a bit indicator that reuses one or more reserved bits of the Common Signaling Field (U-SIG).

9. The method according to claim 7, wherein, The indication is given using one or more reserved entries in the physical layer (PHY) version.

10. An apparatus comprising: A transceiver, configured to perform wireless communication; as well as A processor, coupled to the transceiver and configured to perform operations including: Wireless communication is performed via the transceiver in the following manner: Generate and send Physical Layer Protocol Data Units (PPDUs); or Receive and process the PPDU. The PPDU includes a conventional preamble, followed by an ambient power (AMP) packet. The traditional preamble includes a traditional short training field (L-STF), a traditional long training field (L-LTF), a traditional signaling field (L-SIG), a redundant traditional signaling field (RL-SIG), and at least two universal signaling fields (U-SIG).

11. The apparatus according to claim 10, wherein, The content of each of the at least two U-SIGs includes one or more version-independent fields.

12. The apparatus according to claim 11, wherein, The one or more version-independent fields include at least one of the following: Physical Layer (PHY) version field, bandwidth field, Basic Service Set (BSS) color field, Downlink (DL) / Uplink (UL) field, and Transmission Opportunity (TXOP) field.

13. The apparatus according to claim 10, wherein, At least one of the at least two U-SIGs carries information for AMP reception, and wherein the information includes either or both of the following: AMP PPDU type; and Reference symbols and their length indications.

14. The apparatus according to claim 10, wherein, The AMP package includes a narrowband AMP package.

15. The apparatus according to claim 14, wherein, The narrowband AMP packet includes a 4MHz AMP packet, and the conventional preamble includes a 20MHz preamble.

16. The apparatus according to claim 10, wherein, The PPDU includes an indication in the conventional preamble that indicates the PPDU is an AMP PPDU.

17. The apparatus according to claim 16, wherein, The indication includes a bit indicator that reuses one or more reserved bits of the Common Signaling Field (U-SIG).

18. The apparatus according to claim 16, wherein, The indication is given using one or more reserved entries in the physical layer (PHY) version.

Images