PPDU receiving method and device, PPDU sending method and device, equipment and storage medium

Abstract

The invention discloses a PPDU receiving method and device, a PPDU sending method and device, equipment and a storage medium, and belongs to the field of wireless communication. The method is executed by an electronic device, and the method comprises: receiving all or part of information domains of a first PPDU, the all or part of information domains comprising a first information domain, and the first information domain being used for indicating the type of a target device receiving the first PPDU. Optionally, the target device type comprises a WUR device and an AMP device.

Description

PPDU receiving method, sending method, device, equipment and storage medium Technical Field

[0001] The present application relates to the field of wireless communications, and in particular to a method for receiving, a method for sending, an apparatus, a device, and a storage medium for a physical layer protocol data unit (PHY Protocol Data Unit, PPDU). Background Art

[0002] With the increasing demand for fifth-generation (5G) mobile communications technology, and especially with the increasing variety of connected objects and application scenarios driven by the Internet of Things (IoT), higher requirements are being placed on the price and power consumption of communication terminals. This has led to the development of ambient energy-based IoT (AMP IoT) devices, often referred to as AMP devices. AMP devices operate by harvesting ambient energy, which can come from wireless signals, solar energy, thermal energy, and other sources.

[0003] In the related art, an AMP device is supported to communicate with a wireless access point (AP) in a WiFi system.

[0004] Summary of the Invention

[0005] This application provides a PPDU receiving method, sending method, apparatus, device, and storage medium, which enable AMP devices and wake-up receivers (WURs) in WiFi systems to share the same PPDU format. This technical solution includes at least:

[0006] According to one aspect of an embodiment of the present application, a method for receiving a PPDU is provided. The method is performed by an AMP device or a WUR device. The electronic device includes a first receiver and a primary transceiver. The operating energy consumption of the first receiver is less than the operating energy consumption of the primary transceiver. The method includes:

[0007] Receive all or part of the information fields of a first PPDU, where the all or part of the information fields include a first information field, where the first information field is used to indicate a target device type for receiving the first PPDU.

[0008] In some embodiments, the target device type includes a first device type and a second device type. Optionally, the first device type is an AMP device and the second device type is a WUR device; or the first device type is a WUR device and the second device type is an AMP device.

[0009] According to another aspect of an embodiment of the present application, a method for sending a PPDU is provided. The method is performed by an access point, and the method includes:

[0010] A first PPDU is sent, where the first PPDU includes a first information field, where the first information field is used to indicate a target device type receiving the first PPDU.

[0011] In some embodiments, the target device type includes a first device type and a second device type. Optionally, the first device type is an AMP device and the second device type is a WUR device; or the first device type is a WUR device and the second device type is an AMP device.

[0012] According to another aspect of an embodiment of the present application, an electronic device is provided, the device comprising:

[0013] The receiving module is configured to receive all or part of the information fields of a first PPDU, where the all or part of the information fields include a first information field, and the first information field is configured to indicate a target device type for receiving the first PPDU.

[0014] In some embodiments, the target device type includes a first device type and a second device type. Optionally, the first device type is an AMP device and the second device type is a WUR device; or the first device type is a WUR device and the second device type is an AMP device.

[0015] According to another aspect of an embodiment of the present application, an access point device is provided, the device including:

[0016] The sending module is configured to send a first PPDU, where the first PPDU includes a first information field, where the first information field is used to indicate a target device type receiving the first PPDU.

[0017] In some embodiments, the target device type includes a first device type and a second device type. Optionally, the first device type is an AMP device and the second device type is a WUR device; or the first device type is a WUR device and the second device type is an AMP device.

[0018] According to another aspect of an embodiment of the present application, an electronic device is provided, the electronic device including:

[0019] processor;

[0020] a receiver coupled to the processor;

[0021] a memory for storing executable instructions for the processor;

[0022] The processor is configured to load and execute executable instructions to implement the PPDU receiving method as described in the above aspects.

[0023] According to another aspect of an embodiment of the present application, an access point is provided, the access point including:

[0024] processor;

[0025] a transceiver connected to the processor;

[0026] a memory for storing executable instructions for the processor;

[0027] The processor is configured to load and execute executable instructions to implement the PPDU sending method as described in the above aspects.

[0028] According to another aspect of an embodiment of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the PPDU receiving method and / or PPDU sending method as described in the above aspects.

[0029] According to another aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores at least one program, and the at least one program is loaded and executed by a processor to implement the PPDU receiving method and / or PPDU sending method as described in the above aspects.

[0030] According to another aspect of an embodiment of the present application, a computer program product or computer program is provided, which includes computer instructions, the computer instructions are stored in a computer-readable storage medium, a processor obtains the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to implement the PPDU receiving method and / or PPDU sending method as described in the above aspects.

[0031] The technical solutions provided by the embodiments of the present application may have the following beneficial effects:

[0032] By using the first information field to indicate the target device type for receiving the first PPDU, electronic devices of different types can share the same PPDU format. For example, if different device types include AMP devices and WUR devices, AMP devices and WUR devices can share the same PPDU format. When sending the first PPDU, the AP specifically indicates whether the first PPDU should be received by the AMP device or the WUR device, thereby improving the compatibility of the WiFi system. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0034] FIG1 shows a schematic diagram of a zero-power communication system provided by related art;

[0035] FIG2 shows a schematic diagram of radio frequency energy harvesting provided by related art;

[0036] FIG3 is a schematic diagram showing a backscatter communication process provided by the related art;

[0037] FIG4 shows a schematic diagram of resistive load modulation provided by the related art;

[0038] FIG5 is a schematic diagram showing an encoding method provided by related art;

[0039] FIG6 is a schematic diagram showing a communication process of a zero-power IoT device provided by a related art;

[0040] FIG7 shows a schematic diagram of a receiver system provided by the related art;

[0041] FIG8 shows a diagram of a PPDU message format provided in the related art;

[0042] FIG9 shows a diagram of a message format of a data field provided by related art;

[0043] FIG10 shows a message format diagram of a frame control field in a MAC frame header provided in the related art;

[0044] FIG11 shows a message format diagram of a wake-up signal provided in the related art;

[0045] FIG12 shows a schematic diagram of the principle of OOK modulation provided in the related art;

[0046] FIG13 is a schematic diagram showing the principle of OOK modulation provided in the related art;

[0047] FIG14 shows a schematic diagram showing the principle of MC-OOK modulation provided in the related art;

[0048] FIG15 shows a flowchart of a method for receiving a PPDU provided by an exemplary embodiment of the present application;

[0049] FIG16 shows a flowchart of a method for sending a PPDU provided by an exemplary embodiment of the present application;

[0050] FIG17 shows a schematic diagram of masking a first sequence into a second sequence provided by an exemplary embodiment of the present application;

[0051] FIG18 shows a message structure diagram of a data field provided by an exemplary embodiment of the present application;

[0052] FIG19 shows a message structure diagram of a MAC header field provided by an exemplary embodiment of the present application;

[0053] FIG20 shows a message structure diagram of a frame control field provided by an exemplary embodiment of the present application;

[0054] FIG21 shows a block diagram of a PPDU sending device provided by an exemplary embodiment of the present application;

[0055] FIG22 shows a block diagram of a PPDU receiving apparatus provided by an exemplary embodiment of the present application;

[0056] FIG23 shows a schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application;

[0057] FIG24 shows a schematic structural diagram of an access point provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0058] To make the objectives, technical solutions, and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail herein, with examples shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are merely examples of devices and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0059] The terms used in this disclosure are for the purpose of describing specific embodiments only and are not intended to limit the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0060] It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining."

[0061] The technical solutions described in some embodiments of the present application can be applicable to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system, cellular Internet of Things system, cellular passive Internet of Things system, and can also be applied to subsequent evolution systems of 5G NR system, and can also be applied to 6G and subsequent evolution systems.

[0062] It should be understood that in some embodiments of the present application, "5G" may also be referred to as "5G NR" or "NR".

[0063] It should be understood that in the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0064] In the embodiments of the present application, "predefined" can be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (for example, a terminal device and a network device). The present application does not limit the specific implementation method. For example, predefined can refer to information defined in a protocol.

[0065] In the embodiments of the present application, "protocol" may refer to a standard protocol in the field of communications, for example, it may include an LTE protocol, a NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0066] The electronic devices involved in the embodiments of the present application may be active devices. Active devices refer to devices that have their own power supply and can actively generate and transmit signals, such as mobile phones, computers, smart watches, smart bracelets, etc.

[0067] It can also be a passive device. A passive device refers to a device that does not require a power supply or can work by receiving energy from other devices. It can be called a zero-power device, a zero-power terminal, a low-power device, a low-power terminal, etc.

[0068] It can also be a device that obtains energy from the environment, which can be called an ambient energy IoT device;

[0069] It can also be a device deployed at a fixed location, which can be called a zero-power site, a low-power site, etc.

[0070] It can also be a STA with WUR in the WiFi system.

[0071] FIG1 shows a schematic diagram of a zero-power communication system 100 provided by the related art. The zero-power communication system 100 includes a network device 120 and a zero-power device 140 .

[0072] The network device 120 is used to send wireless power supply signals, downlink communication signals and receive backscatter signals from the zero-power device 140 to the zero-power device 140. The zero-power device 140 is also called an ambient power enabled Internet of Things (Ambient IoT) device, which includes an energy collection module 141, a backscatter communication module 142 and a low-power computing module 143. The energy collection module 141 can collect energy carried by radio waves (wireless signals) in space, and is used to drive the low-power computing module 143 of the zero-power device 140 and realize backscatter communication. After obtaining energy, the zero-power device 140 can receive control signaling from the network device 120 and send data to the network device 120 based on the backscattering method according to the control signaling. The sent data can come from data stored in the zero-power device 140 itself (such as an identity or pre-written information, such as the production date, brand, manufacturer, etc. of the product).

[0073] Zero-power device 140 may also include a sensor module 144 and a memory 145. Sensor module 144 may include various sensors, and zero-power device 140 may report data collected by these sensors based on a zero-power mechanism. Memory 145 is used to store basic information (such as item identification) or obtain sensor data such as ambient temperature and humidity.

[0074] The zero-power device 140 itself does not require a battery, and at the same time, the low-power computing module 143 can perform simple signal demodulation, decoding or encoding, modulation and other simple calculation tasks. Therefore, the zero-power module only requires a very simple hardware design, making the zero-power device 140 very low in cost and small in size.

[0075] The network device 120 includes but is not limited to: cellular network devices, such as 5G / 6G network devices, base station devices; WiFi / WLAN network devices, such as access points (APs), routers, mobile access points, etc., and the mobile access point is, for example, a mobile phone.

[0076] The zero-power device 140 includes but is not limited to: handheld devices, wearable devices, vehicle-mounted devices and Internet of Things devices, etc. The zero-power device 140 can be at least one of a mobile phone, a tablet computer, an e-book reader, a laptop computer, a desktop computer, a television, a game console, an augmented reality (AR) terminal, a virtual reality (VR) terminal and a mixed reality (MR) terminal, a wearable device, a handle, an electronic tag and a controller, etc.

[0077] Next, the key technologies of zero-power communication are introduced:

[0078] Radio Frequency Power Harvesting

[0079] Figure 2 shows a schematic diagram of RF energy harvesting provided by related technologies. RF energy harvesting is based on the principle of electromagnetic induction, using a radio frequency (RF) module to conduct electromagnetic induction and maintain a parallel relationship with a capacitor C and a load resistor R. L By connecting to the power supply, the energy required to operate zero-power devices can be collected from electromagnetic waves in space, such as for driving low-power demodulation modules, modulation modules, sensors, and memory reading. Therefore, zero-power devices do not require traditional batteries.

[0080] Back scattering communication

[0081] Figure 3 shows a schematic diagram of the backscatter communication process provided by related art. A zero-power device 140 receives a wireless signal carrier 131 transmitted by a transmitter (TX) module 121 of a network device 120 using an amplifier (AMP) 122. It modulates the wireless signal carrier 131, loads the information to be transmitted using a logic processing module 147, and harvests radio frequency energy using an energy harvesting module 141. Zero-power device 140 radiates the modulated reflected signal 132 using an antenna 146. This information transmission process is called backscatter communication. A receiver (RX) module 123 of the network device 120 receives the modulated reflected signal 132 using a low-noise amplifier (LNA) 124. Backscatter and load modulation are closely related. Load modulation achieves this by adjusting and controlling the circuit parameters of the oscillator circuit of the zero-power device 140 according to the data stream's rhythm, causing parameters such as the electronic tag's impedance to change accordingly.

[0082] Load modulation technology mainly includes resistance load modulation and capacitance load modulation. Figure 4 shows a schematic diagram of resistance load modulation provided by related technology. In resistance load modulation, the load resistor R L The third resistor R3 is connected in parallel, and the switch S based on the binary code control is turned on or off. The on and off of the third resistor R3 will cause the voltage on the circuit to change. The load resistor R L Maintaining a parallel connection relationship with the first capacitor C1, the load resistor R LThe first inductor L1 is connected in series with the second resistor R2, and the second resistor R2 is connected in series with the first inductor L1. The first inductor L1 is coupled to the second inductor L2, and the second inductor L2 is connected in series with the second capacitor C2. Amplitude Shift Keying (ASK) can be implemented, that is, the modulation and transmission of the signal is achieved by adjusting the amplitude of the backscattered signal of the zero-power device. Similarly, in capacitive load modulation, the resonant frequency of the circuit can be changed by turning the capacitor on and off, and frequency shift keying (FSK) can be implemented, that is, the modulation and transmission of the signal is achieved by adjusting the operating frequency of the backscattered signal of the zero-power device.

[0083] Zero-power devices use load modulation to modulate incoming signals, enabling backscatter communication. These devices offer significant advantages: they don't actively transmit signals, eliminating the need for complex RF links like power amplifiers (PAs) and RF filters. They don't actively generate high-frequency signals, eliminating the need for high-frequency crystal oscillators. Furthermore, backscatter communication allows signal transmission without consuming the device's own energy.

[0084] Extremely low power active transmission technology;

[0085] Zero-power devices can also use ultra-low-power active transmission technology. Unlike backscattering, when using ultra-low-power active transmission technology for data transmission, the device uses a relatively simple and low-power oscillator to generate the RF carrier, and then modulates the information to be transmitted onto the RF carrier. Based on current research, the power consumption of ultra-low-power active transmitters can be as low as hundreds of microwatts, thus achieving ultra-low-power data transmission.

[0086] Next, the encoding method of zero-power communication is introduced:

[0087] FIG5 is a schematic diagram of an encoding method provided by related art. The data transmitted by the electronic tag can use different forms of codes to represent binary "1" and "0". Wireless radio frequency identification systems generally use one of the following encoding methods: Not Return to Zero (NRZ) encoding, Manchester encoding, Unipolar Return to Zero (URZ) encoding, Differential Binary Phase (DBP) encoding, Miller encoding, and differential encoding. That is, different pulse signals can be used to represent 0 and 1.

[0088] ·NRZ encoding; Inverse non-return-to-zero encoding uses a high level to represent a binary "1" and a low level to represent a binary "0". Figure 5 shows a level diagram of encoding binary data: 101100101001011 using the NRZ method.

[0089] Manchester encoding: Manchester encoding is also known as split-phase coding. In Manchester encoding, a binary value is represented by a voltage level change (rising or falling) during half a bit period within the bit length. A negative transition during half a bit period represents a binary "1," and a positive transition during half a bit period represents a binary "0." Data transmission errors occur when multiple tags simultaneously transmit data bits with different values, causing the received rising and falling edges to cancel each other, resulting in an uninterrupted carrier signal throughout the entire bit length. Manchester encoding makes it impossible to have an unchanging state within the bit length. The reader can use this error to determine the specific location of the collision. Manchester encoding facilitates data transmission error detection and is commonly used for data transmission from tags to readers when using carrier load modulation or backscatter modulation. Figure 5 shows a schematic diagram of the voltage levels for binary data 101100101001011 encoded using the Manchester method.

[0090] ·URZ encoding; unipolar return-to-zero encoding: a high level in the first half of the bit period represents a binary "1", while a low level signal that lasts throughout the entire bit period represents a binary "1". Figure 5 shows a level diagram of encoding binary data: 101100101001011 using the URZ method.

[0091] DBP encoding: Differential biphase encoding uses any edge within half a bit period to represent a binary "0," while the absence of an edge represents a binary "1." Furthermore, the voltage level is inverted at the beginning of each bit period. This makes the bit beat easier for the receiver to reconstruct. Figure 5 shows the voltage levels of the binary data 101100101001011 encoded using the DBP method.

[0092] Miller coding: In Miller coding, any edge within half a bit period represents a binary "1," while a constant level throughout the next bit period represents a binary "0." The level transition at the beginning of a bit period makes it easier for the receiver to reconstruct the bit beat. Figure 5 shows the level diagram of the binary data 101100101001011 encoded using the Miller method.

[0093] Differential encoding: In differential encoding, each transmitted binary "1" causes a change in the signal level, while for a binary "0" the signal level remains unchanged.

[0094] Next, we will introduce the classification of zero-power devices:

[0095] Based on the energy source and usage of zero-power devices, zero-power devices can be divided into the following types:

[0096] Passive zero-power devices;

[0097] Zero-power devices do not require internal batteries. When they approach a network device, they are within the near field generated by the network device's antenna radiation. For example, the network device is a reader / writer in a radio frequency identification (RFID) system. Therefore, the zero-power device's antenna generates an induced current through electromagnetic induction, which drives the device's low-power chip circuitry. This enables tasks such as demodulating forward link signals and modulating reverse link signals. For backscatter links, the zero-power device can use backscatter or extremely low-power active transmission to transmit signals. Passive zero-power devices do not require internal batteries for either the forward or reverse link, making them truly zero-power devices. Passive zero-power devices do not require batteries, and their RF and baseband circuits are very simple. For example, they do not require components such as LNAs, PAs, crystal oscillators, and analog-to-digital converters (ADCs). They offer numerous advantages, including small size, light weight, very low price, and a long service life.

[0098] Semi-passive zero-power device;

[0099] Semi-passive zero-power devices lack conventional batteries. Instead, they use a radio frequency energy harvesting module to harvest radio wave energy and store it in an energy storage unit, typically a capacitor. This energy is then used to power the device's low-power chip circuitry, enabling tasks such as demodulating forward link signals and modulating backward link signals. For backscatter links, the device can transmit signals using either backscatter or extremely low-power active transmission.

[0100] Semi-passive zero-power devices require no internal batteries for either the forward or reverse link. Instead, the energy stored in the capacitors is harvested by the radio energy harvesting module, making them truly zero-power devices. They inherit many of the advantages of passive zero-power devices, including small size, light weight, very low price, and long service life.

[0101] Active zero-power devices;

[0102] Zero-power devices used in some scenarios can also be active zero-power devices, which can have built-in batteries. The battery is used to drive the low-power chip circuit of the zero-power device. This enables tasks such as demodulating forward link signals and modulating reverse link signals. However, for backscatter links, zero-power devices can use backscatter or extremely low-power active transmission to transmit signals. Therefore, the zero-power of active zero-power devices is mainly reflected in the fact that reverse link signal transmission does not consume the zero-power device's own power, but instead uses backscatter. In active zero-power devices, the built-in battery powers the RFID chip, increasing the tag's read and write distance and improving communication reliability. Therefore, they are used in scenarios with relatively high requirements for communication distance and read latency.

[0103] Next, we will introduce the classification of zero-power devices based on transmitter type:

[0104] (1) Zero-power devices based on backscattering;

[0105] These zero-power devices use backscattering, as described above, for uplink data transmission. They lack active transmitters, only backscattering transmitters. Therefore, when these zero-power devices transmit uplink data, they require network equipment to provide a carrier. These zero-power devices use backscattering based on the carrier to achieve uplink data transmission.

[0106] (2) Zero-power devices based on active transmitters;

[0107] These zero-power devices use active transmitters with active transmission capabilities for uplink data transmission. Therefore, when sending uplink data, these zero-power devices can use their own active transmitters to send uplink data without the need for network equipment to provide a carrier. Examples of active transmitters suitable for zero-power devices include ultra-low-power ASK transmitters and ultra-low-power FSK transmitters. Based on current implementations, these transmitters can reduce overall power consumption to 400-600 microwatts when transmitting a 100-microwatt signal.

[0108] (3) Zero-power devices that have both backscatter and active transmitters;

[0109] These zero-power devices can support both backscatter and active transmitters. They can determine whether to use backscatter or active transmitters based on different situations (such as varying battery levels, available ambient energy), or based on network device scheduling.

[0110] Next, let’s introduce the cellular Internet of Things:

[0111] Cellular IoT is booming. The 3rd Generation Partnership Project (3GPP) has standardized IoT technologies such as NarrowBand-Internet of Things (NB-IoT), Machine-Type Communications (MTC), and RedCap. However, IoT communication needs in many scenarios remain unmet. For example:

[0112] Harsh communication environment;

[0113] Certain IoT scenarios may encounter extreme environments such as high temperature, extremely low temperature, high humidity, high voltage, high radiation, or high-speed movement. Examples include ultra-high voltage substations, high-speed train track monitoring, environmental monitoring in high-altitude cold regions, and industrial production lines. In these scenarios, IoT devices will not function due to the operating environment limitations of conventional power supplies. Furthermore, extreme operating environments are not conducive to IoT device maintenance, such as battery replacement.

[0114] ·Requirement for extremely small terminal form factor;

[0115] Certain IoT communication scenarios, such as food traceability, commodity distribution, and smart wearables, require terminals to be extremely small for ease of use. For example, IoT terminals used for commodity management in the distribution process often use electronic tags, which are embedded in the product packaging in a very compact form factor. Another example is lightweight wearable IoT terminals that can meet user needs while improving the user experience.

[0116] Extremely low-cost IoT communication requirements;

[0117] Many IoT communication scenarios require IoT terminal devices to be sufficiently low-cost to enhance their competitiveness compared to alternative technologies. For example, in logistics or warehousing scenarios, IoT terminal devices can be attached to each item to facilitate the management of large quantities of circulating items. Communication between the IoT terminal device and the logistics network enables precise management of the entire logistics process and lifecycle. These scenarios require IoT terminal devices to be sufficiently competitively priced.

[0118] Therefore, in order to cover these unmet IoT communication needs, cellular IoT also needs to develop ultra-low-cost, extremely small-size, battery-free / maintenance-free IoT, and zero-power IoT can just meet these needs.

[0119] Zero-power IoT, also known as Ambient IoT or passive IoT, refers to IoT devices that use various environmental energies, such as radio frequency energy, light energy, solar energy, thermal energy, and mechanical energy, to power themselves. These devices can have no energy storage capacity or very limited energy storage capacity (such as using capacitors with a capacity of tens of microfarads). Compared to existing IoT devices, Ambient IoT devices offer many advantages, including no conventional batteries, no maintenance, small size, low complexity, low cost, and a long lifespan.

[0120] Zero-power IoT can be used in at least four scenarios:

[0121] (1) Object recognition, such as logistics, production line product management, and supply chain management;

[0122] (2) Environmental monitoring, such as temperature, humidity, and harmful gas monitoring of the working environment and natural environment;

[0123] (3) Positioning, such as indoor positioning, intelligent object search, and production line item positioning;

[0124] (4) Intelligent control, such as intelligent control of various electrical appliances in smart homes (turning on and off air conditioners, adjusting temperature), and intelligent control of various facilities in agricultural greenhouses (automatic irrigation and fertilization).

[0125] Next, we will introduce the communication process of Ambient IoT devices:

[0126] In the future, cellular passive IoT or WLAN passive IoT, or Ambient IoT devices, new Ambient IoT devices (electronic devices) can be supported, thereby meeting the corresponding types of IoT communication needs in different application scenarios.

[0127] In actual deployment scenarios, supporting these electronic devices requires APs capable of communicating with them. However, in some application scenarios, a large number of APs supporting traditional technologies have already been deployed. If these APs can support electronic devices that can function in the environment, traditional communication functions can be maintained while reducing power consumption during communication, fully utilizing these deployed APs and reducing physical and financial resource consumption.

[0128] Figure 6 shows a schematic diagram of a WiFi system according to an exemplary embodiment of the present application. An electronic device 610 is capable of data communication with an access point 620 in the WiFi system. Electronic device 610 can be a new Ambient IoT device or an existing WUR device in the WiFi system. Deploying Ambient IoT devices within the WiFi system fully utilizes existing network infrastructure and reduces network deployment costs.

[0129] However, since the access point 620 in the WiFi system usually does not have functions such as wireless power supply, new network nodes can be deployed, such as the power supply node 630 in Figure 6, which can also be called an auxiliary node, for providing wireless power supply to the Ambient IoT device.

[0130] Next, the wake-up receiver is introduced:

[0131] 7 shows a schematic diagram of an electronic device 700 with a wake-up receiver (WUR) according to the related art. The electronic device 700 includes a wake-up receiver 710 and a main transceiver 720 .

[0132] In some embodiments, the main radio 720 can be equivalently understood as a main transceiver, or a main air interface communication unit.

[0133] In some embodiments, the primary transceiver 720 includes a receiver.

[0134] In some embodiments, the primary transceiver 720 includes a receiver and a transmitter.

[0135] In order to further save power, WUR is introduced to receive energy-saving signals. The wake-up receiver has the characteristics of extremely low cost, extremely low complexity and extremely low power consumption. It mainly receives energy-saving signals through envelope detection. Therefore, the energy-saving signal received by the wake-up receiver is different from the modulation method, waveform, etc. of the signal carried by the physical downlink control channel (PDCCH) defined in the relevant standards. The energy-saving signal is mainly an envelope signal that performs ASK modulation on the carrier signal. The demodulation of the envelope signal can also be completed by driving the low-power circuit with the energy provided by the wireless radio frequency signal, so it can be passive. The wake-up receiver can also be actively powered by an electronic device (terminal device). Regardless of the power supply method, the receiver greatly reduces power consumption compared to traditional receivers. For example, WUR can achieve power consumption of less than 1 milliwatt, which is much lower than the power consumption of tens to hundreds of milliwatts of the main receiver. The wake-up receiver can be combined with an electronic device as an additional module of the receiver of the electronic device, or it can be used alone as a wake-up function module of an electronic device.

[0136] Figure 8 shows a message format diagram of a PPDU provided in the related art. The PPDU includes at least one of a physical layer header and a data portion.

[0137] The physical layer header includes at least one of a short training field (STF), a long training field (LTF), and a signal (SIGNAL).

[0138] The short training field consists of 10 short symbols, denoted as t1-t10, with each symbol lasting 0.8µs. The short training field is used to achieve frame synchronization and coarse frequency synchronization. Among them, t1-t7 mainly include signal detection (Signal Detect), automatic gain control (AGC), and receive antenna selection (Diversity Selection) functions, while t8-t10 mainly include coarse frequency (Coarse Freq), offset estimation (Offset Estimation), and symbol timing synchronization (Timing Synchronize) functions.

[0139] The long training field is used to achieve fine frequency synchronization and channel estimation.

[0140] The signal portion is used to carry information related to the data portion, including data transmission rate, data packet length information (Length), and at least one of reserved bits and tail bits.

[0141] The data portion is used to carry a MAC frame. The frame format of the MAC frame includes at least one of a MAC header, a frame body, and a frame check sequence (FCS). The frame format of the data portion can be shown in FIG9 .

[0142] The frame body is used to store the information being sent or received.

[0143] The frame check sequence (FCS) is used to check data packets and includes a 32-bit cyclic redundancy check (CRC).

[0144] The MAC header includes at least one of frame control (Frame Control), duration / identification (Duration / ID), address 1 (address 1), address 2 (address 2), address 3 (address 3), sequence control (Sequence Control), address 4 (address 4), quality of service control (QoS Control), and HT control (HT Control).

[0145] The duration / flag is used to indicate how long the frame and its confirmation frame will occupy the channel. The Duration value is used for Network Allocation Vector (NAV) calculation.

[0146] Among them, Address 1, Address 2, Address 3, and Address 4 can be referred to as Address Fields. The Address Field includes at least one of the following: Destination Address (DA), Source Address (SA), Transmitting Address (TA), Receiving Address (RA), and Basic Service Set ID (BSS ID).

[0147] The sequence control field is used to filter duplicate frames. It includes at least one of a MAC Service Data Unit (MSDU) and a MAC Management Service Data Unit (MMSDU). An MSDU consists of a 12-bit sequence number, while an MMSDU consists of a 4-bit fragment number.

[0148] Quality of Service (QoS) is used for priority control. This field is effective or required to be included when the data frame is of the QoS data subtype.

[0149] HT Control is used for throughput control. When the data frame is of high throughput type, this field takes effect or needs to be included.

[0150] Figure 10 shows the message format of the Frame Control field in the MAC frame header provided in the related art. Frame Control includes at least one of Protocol Version, Frame Type, Subtype, To DS, From DS, More Fragments, Retry, Power Management, More Data, Protected Frame, and +HTC.

[0151] The protocol version value is 0 or 1.

[0152] The frame type indicates the type of data frame. Frame types include at least one of control frames, management frames, and data frames. Control frames are used for handshakes and positive acknowledgements during contention periods, and for terminating non-contention periods. Management frames are used for negotiation and relationship control between stations (STAs) and access points (APs), such as association, authentication, and synchronization. Data frames are used to transmit data during both contention and non-contention periods.

[0153] Subtype is used to indicate the subtype of the data frame.

[0154] To DS is used to indicate that the frame is sent from the BSS to the DS.

[0155] From DS is used to indicate that the frame is sent from DS to BSS.

[0156] The More Segmented Frames field is used to indicate the segmentation status of the frame. If the frame is a segmented frame of a certain frame and is not the last segmented frame of a certain frame, the More Segmented Frames field of the frame is set to 1.

[0157] Retransmission is used to indicate the retransmission status of the segmented frame, that is, whether the frame is a segmented frame that has been transmitted before.

[0158] More data is used to indicate the cache status of the data frame in the station. If there is at least one data frame to be sent to the station, the more data of the frame is set to 1.

[0159] The protected frame is used to indicate the encryption status of the frame body. If the frame body contains encrypted data, the frame is set to 1; if it does not contain encrypted data, it is set to 0.

[0160] +HTC is an indicator bit associated with HT control.

[0161] Figure 11 shows a message format diagram of a wake-up signal provided in the related art. This wake-up signal may be referred to as a WUR wake-up frame. Related art uses WUR signals to achieve energy saving in electronic devices. The AP notifies the WUR non-AP STA via the WUR wake-up frame to perform energy-saving operations. The WUR wake-up frame is carried in the WUR PPDU.

[0162] In some embodiments, the WUR PPDU includes at least one of a legacy preamble, WUR synchronization (WUR-Sync), and WUR data (WUR-Data).

[0163] The traditional preamble is used to protect WUR synchronization and WUR data. The traditional preamble improves compatibility and is the non-WUR portion, using Orthogonal Frequency-Division Multiplexing (OFDM) modulation and a 20MHz bandwidth. WUR synchronization is used to identify and decouple the WUR data portion. The WUR data portion is used to carry the WUR physical layer service data unit (PSDU).

[0164] WUR synchronization and WUR data use On-Off Keying (OOK) modulation and 4MHz bandwidth.

[0165] OOK modulation works by modulating the carrier signal's amplitude between non-zero and zero values. Non-zero values ​​correspond to "on," while zero values ​​correspond to "off," representing information bits. OOK is also known as binary amplitude shift keying (2ASK). Figure 12 shows the OOK modulation principle.

[0166] The WUR synchronization sequence uses a predefined sequence W, which contains 32 bits. Different WUR synchronization sequences indicate different data rates used by WUR data.

[0167] The WUR synchronization sequence corresponding to the WUR low data rate (LDR) is as follows:

[0168] W=[10100100101110110001011100111000]

[0169] The WUR synchronization sequence corresponding to the WUR High Data Rate (HDR) is as follows:

[0170] W=[01011011010001001110100011000111]

[0171] After OOK modulation, each bit in the WUR synchronization will be mapped into an OOK symbol with a length of 2μs.

[0172] WUR data is used to carry user information. After the user information is encoded by the WUR encoder, it can be OOK modulated to form OOK symbols of corresponding length, as shown in Figure 13.

[0173] Among them, the OOK symbol lengths corresponding to WUR LDR and WUR HDR are 4μs and 2μs respectively.

[0174] The above-mentioned OOK signal is generated by multi-carrier (MC), and therefore can be called an MC-OOK signal. The MC-OOK signal generated by multi-carrier is shown in Figure 14. In some embodiments, the MC-OOK signal generates an OOK signal by multi-carrier modulation, for example, by OFDM modulation. By mapping the corresponding amplitude values ​​to multiple subcarriers in the frequency domain, the waveform of the time domain signal converted by inverse discrete Fourier transform (IDFT) is similar to the waveform formed by amplitude shift keying (ASK) modulation, where bit 1 is represented by a high level of the signal and bit 0 is represented by a low level of the signal.

[0175] In the embodiment of the present application, it is assumed that the downlink signals received by the AMP device and the WUR device have the same waveform, such as an OOK waveform. On this basis, it is also designed that the downlink signals received by the AMP device and the WUR device have a unified format, such as a PPDU format.

[0176] In order to achieve a unified PPDU format, the AMP PPDU received by the AMP device also adopts the format of the WUR PPDU. The AMP device and the WUR device can determine whether to receive the current PPDU based on the indication information carried by the first information field in the WUR PPDU.

[0177] FIG15 shows a flow chart of a method for receiving a PPDU provided by an exemplary embodiment of the present application. This embodiment is illustrated by an example in which the method is performed by an electronic device. The method includes:

[0178] Step 120: Receive all or part of the information fields of the first PPDU, where the all or part of the information fields include a first information field, and the first information field is used to indicate a target device type receiving the first PPDU.

[0179] In some embodiments, the first PPDU is a PPDU shared by the AMP device and the WUR device.

[0180] In some embodiments, the PPDU format of the first PPDU is derived based on the PPDU format of the WUR PPDU.

[0181] In some embodiments, the first PPDU uses an OOK waveform.

[0182] The target device type includes at least two types. This embodiment uses the example that the target device type includes a first device type and a second device type. Optionally, the first device type is an AMP device and the second device type is a WUR device; or the first device type is a WUR device and the second device type is an AMP device.

[0183] The first PPDU includes at least one information field. In some embodiments, similar to the WUR PPDU, the first PPDU includes at least one of a legacy preamble, a synchronization field, and a data field. The synchronization field is the same as or similar to the WUR synchronization field, and the data field is the same as or similar to the WUR data field.

[0184] In summary, the method provided in this embodiment uses the first information field to indicate the target device type receiving the first PPDU, allowing electronic devices of different device types to share the same PPDU format. For example, if different device types include AMP devices and WUR devices, AMP devices and WUR devices can share the same PPDU format. When sending the first PPDU, the AP specifically indicates whether the first PPDU should be received by the AMP device or the WUR device, thereby improving the compatibility of the WiFi system.

[0185] FIG16 shows a flow chart of a method for transmitting a PPDU provided by an exemplary embodiment of the present application. This embodiment is illustrated by an example in which the method is performed by an AP. The method includes:

[0186] Step 220: Send a first PPDU, where the first PPDU includes a first information field, and the first information field is used to indicate a target device type receiving the first PPDU.

[0187] In some embodiments, the first PPDU is a PPDU shared by the AMP device and the WUR device.

[0188] In some embodiments, the PPDU format of the first PPDU is derived based on the PPDU format of the WUR PPDU.

[0189] In some embodiments, the first PPDU uses an OOK waveform.

[0190] The target device type includes at least two types. This embodiment uses the example that the target device type includes a first device type and a second device type. Optionally, the first device type is an AMP device and the second device type is a WUR device; or the first device type is a WUR device and the second device type is an AMP device.

[0191] The first PPDU includes at least one information field. In some embodiments, similar to the WUR PPDU, the first PPDU includes at least one of a legacy preamble, a synchronization field, and a data field. The synchronization field is the same as or similar to the WUR synchronization field, and the data field is the same as or similar to the WUR data field.

[0192] In summary, the method provided in this embodiment uses the first information field to indicate the target device type receiving the first PPDU, allowing electronic devices of different device types to share the same PPDU format. For example, if different device types include AMP devices and WUR devices, AMP devices and WUR devices can share the same PPDU format. When sending the first PPDU, the AP specifically indicates whether the first PPDU should be received by the AMP device or the WUR device, thereby improving the compatibility of the WiFi system.

[0193] Based on the embodiment of FIG. 15 and / or FIG. 16 , possible design methods of the first information field include at least one of the following:

[0194] Method 1. The first information field is the synchronization field;

[0195] The sequence carried by the synchronization field indicates the target device type (which may be simply referred to as device type) for receiving the first PPDU.

[0196] Method 2. The first information field is the MAC header field;

[0197] The information carried by the MAC header field indicates the target device type for receiving the first PPDU.

[0198] For method 1: the first information field is the synchronization field;

[0199] In some embodiments, the synchronization field may use sequences of different lengths and / or values.

[0200] The synchronization field uses a first sequence to indicate that the target device type receiving the first PPDU is a first device type;

[0201] The synchronization field uses a second sequence to indicate that the target device type receiving the first PPDU is a second device type.

[0202] The first sequence and the second sequence are different sequences.

[0203] In some embodiments, the difference between the first sequence and the second sequence includes at least one of a different length and a different value.

[0204] In some embodiments, the second sequence is obtained based on the first sequence. That is, the second sequence is obtained by processing the first sequence. The processing method includes but is not limited to: at least one of cyclic shift, masking, and bit flipping:

[0205] In some embodiments, the second sequence is obtained by cyclically shifting the first sequence.

[0206] For example, the first sequence W=[10100100101110110001011100111000], and the first sequence is cyclically shifted right by 6 bits to obtain the second sequence; the second sequence W=[11100010100100101110110001011100].

[0207] The number of cyclic shift bits may be predefined by the communication protocol or configured by the AP.

[0208] In some embodiments, the second sequence is obtained by processing all or part of the bits in the first sequence. The processing includes at least one of cyclic shift, masking, and bit flipping.

[0209] The partial bits are the first n bits in the first sequence; or

[0210] The partial bits are the last n bits in the first sequence; or,

[0211] The portion of bits is a first subsequence in a first sequence, the first sequence includes the first subsequence and a second subsequence, and the second subsequence is obtained by flipping the first subsequence; or

[0212] Some bits are a second subsequence in a first sequence. The first sequence includes a first subsequence and a second subsequence. The second subsequence is obtained by flipping the first subsequence.

[0213] For example, referring to FIG17 , the first sequence W=[10100100101110110001011100111000];

[0214] After masking the last 16 bits of the first sequence with the mask = [1011001101001011], we get:

[0215] The second sequence W = [10100100101110111010010001110011].

[0216] For another example, a first sequence includes a first subsequence and a second subsequence. The first subsequence is the sequence used by the synchronization field corresponding to LDR, and the second subsequence is the sequence used by the synchronization field corresponding to HDR. The first subsequence is a 64-bit sequence that is a sequence W1 repeated twice, and the second subsequence is a sequence W that is a bit-flipped sequence W1.

[0217] The second sequence includes a third subsequence and a fourth subsequence. The third subsequence is a sequence used by the synchronization field corresponding to LDR, and the fourth subsequence is a sequence used by the synchronization field corresponding to HDR. The third subsequence is obtained by performing at least one of cyclic shifting, masking, and bit flipping on the first subsequence, and / or the fourth subsequence is obtained by performing at least one of cyclic shifting, masking, and bit flipping on the second subsequence.

[0218] For method 2: the first information field is the MAC header field.

[0219] 18, the data field includes at least one of a MAC header field, a frame body field, and an FCS field. As shown in FIG19, the MAC header field includes a frame control field, an ID field, and a type-dependent control field.

[0220] 20 , the frame control field includes at least one of a type field, a protected field, a frame body present field, and a length / miscellaneous field. The type field is also called a frame type field.

[0221] In the second approach, an information field in the MAC header field may be used to indicate the type of the target device receiving the first PPDU.

[0222] In some embodiments, the Usage Type field indicates the target device type for receiving the first PPDU; in some embodiments, the Usage ID field indicates the target device type for receiving the first PPDU.

[0223] In some embodiments, the usage type field indicates:

[0224] The type field has a first value, which is used to indicate that the target device type receiving the first PPDU is the first device type;

[0225] The type field is a second value, which is used to indicate that the target device type receiving the first PPDU is a second device type.

[0226] Exemplarily, the type field includes 3 bits to indicate the type of the frame. Table 1 shows a possible design of the type field:

[0227] Table 1

[0228] The value used to indicate an AMP device is 101, and the value used to indicate a WUR device is any one of 000, 001, 010, 011, and 100. In other embodiments, the value used to indicate an AMP device may also be 110 or 111.

[0229] In another possible design, the type field may further indicate a more specific AMP frame type, such as at least one of an AMP broadcast frame, an AMP data frame, and an AMP control frame, as shown in Table 2 below:

[0230] Table 2

[0231] It should be noted that the above Table 1 and Table 2 are both schematic illustrations. Some rows in the above Table 1 and Table 2 can be implemented individually as an embodiment, and some rows in the above Table 1 and some rows in Table 2 can be combined to form a new embodiment. This application does not limit this.

[0232] In some embodiments, the ID field is used for indication;

[0233] The ID field is a first ID, which is used to indicate that the target device type receiving the first PPDU is a first device type, and the first ID is an ID maintained by a device of the first device type;

[0234] The ID field is a second ID, which is used to indicate that the target device type receiving the first PPDU is a second device type, and the second ID is an ID maintained by a device of the second device type.

[0235] In some embodiments, the ID field comprises 12 bits. Table 3 shows the IDs that a WUR device may maintain.

[0236] Table 3

[0237] OUI is the abbreviation of Organizationally Unique Identifier (OUI).

[0238] In one example, the IDs in Table 3 above are all ID types maintained by a WUR non-AP STA (i.e., a WUR device). If the ID received in the ID field by the WUR non-AP STA is not one it maintains, the STA discards the first PPDU. In this example, the AP can allocate IDs for AMP devices. If the ID received in the ID field by the AMP device matches the ID for the AMP device, the AMP device considers the first PPDU to be received; otherwise, the AMP device discards the first PPDU.

[0239] In the above embodiment, the first device type is a WUR device, and the second device type is an AMP device. In the above embodiment, the first device type is an AMP device, and the second device type is a WUR device. A WUR device is a STA with a WUR, such as a WUR non-AP STA.

[0240] In summary, the PPDUs sent by the AP to the AMP and WUR use a unified format, reducing system design complexity. In the first PPDU, the AMP device can determine whether to receive the first PPDU by using the sequence of synchronization fields or by using fields in the MAC header to indicate the target receiving device type. If this is not necessary, the AMP device can stop receiving the remaining parts of the first PPDU, thus saving power.

[0241] FIG21 shows a block diagram of a PPDU receiving device provided by an exemplary embodiment of the present application. The information receiving device can be implemented as part of an AMP device or a WUR device. The information receiving device includes:

[0242] The receiving module 320 is configured to receive all or part of the information fields of the first PPDU, where the all or part of the information fields include a first information field, and the first information field is used to indicate a target device type for receiving the first PPDU.

[0243] In some embodiments, the first PPDU is a PPDU shared by the AMP device and the WUR device.

[0244] In some embodiments, the PPDU format of the first PPDU is derived based on the PPDU format of the WUR PPDU.

[0245] In some embodiments, the first PPDU uses an OOK waveform.

[0246] The target device type includes at least two types. This embodiment uses the example that the target device type includes a first device type and a second device type. Optionally, the first device type is an AMP device and the second device type is a WUR device; or the first device type is a WUR device and the second device type is an AMP device.

[0247] The first PPDU includes at least one information field. In some embodiments, similar to the WUR PPDU, the first PPDU includes at least one of a legacy preamble, a synchronization field, and a data field. The synchronization field is the same as or similar to the WUR synchronization field, and the data field is the same as or similar to the WUR data field.

[0248] In summary, the apparatus provided in this embodiment uses the first information field to indicate the target device type for receiving the first PPDU, enabling electronic devices of different device types to share the same PPDU format. For example, if different device types include AMP devices and WUR devices, AMP devices and WUR devices can share the same PPDU format. When the AP sends the first PPDU, it specifically indicates whether the first PPDU should be received by the AMP device or the WUR device, thereby improving the compatibility of the WiFi system.

[0249] FIG22 shows a flow chart of a method for transmitting a PPDU provided by an exemplary embodiment of the present application. This embodiment is illustrated by an example in which the method is performed by an AP. The method includes:

[0250] The sending module 420 is configured to send a first PPDU, where the first PPDU includes a first information field, and the first information field is used to indicate a type of a target device receiving the first PPDU.

[0251] In some embodiments, the first PPDU is a PPDU shared by the AMP device and the WUR device.

[0252] In some embodiments, the PPDU format of the first PPDU is derived based on the PPDU format of the WUR PPDU.

[0253] In some embodiments, the first PPDU uses an OOK waveform.

[0254] The target device type includes at least two types. This embodiment uses the example that the target device type includes a first device type and a second device type. Optionally, the first device type is an AMP device and the second device type is a WUR device; or the first device type is a WUR device and the second device type is an AMP device.

[0255] The first PPDU includes at least one information field. In some embodiments, similar to the WUR PPDU, the first PPDU includes at least one of a legacy preamble, a synchronization field, and a data field. The synchronization field is the same as or similar to the WUR synchronization field, and the data field is the same as or similar to the WUR data field.

[0256] In summary, the apparatus provided in this embodiment uses the first information field to indicate the target device type for receiving the first PPDU, enabling electronic devices of different device types to share the same PPDU format. For example, if different device types include AMP devices and WUR devices, AMP devices and WUR devices can share the same PPDU format. When the AP sends the first PPDU, it specifically indicates whether the first PPDU should be received by the AMP device or the WUR device, thereby improving the compatibility of the WiFi system.

[0257] Based on the embodiment of FIG. 21 and / or FIG. 22 , possible design methods of the first information field include at least one of the following:

[0258] Method 1. The first information field is the synchronization field;

[0259] The sequence carried by the synchronization field indicates the target device type (which may be referred to as the device type) for receiving the first PPDU. Detailed descriptions may be made with reference to the above descriptions, which will not be repeated here.

[0260] Method 2. The first information field is the MAC header field;

[0261] The information carried by the MAC header field indicates the target device type for receiving the first PPDU. For details, please refer to the above description and will not be repeated here.

[0262] FIG23 shows a schematic structural diagram of an electronic device 500 provided by an exemplary embodiment of the present application, including: a processor 501 , a wake-up receiver 502 , a main transceiver 503 , a memory 504 , and a bus 505 .

[0263] The processor 501 includes one or more processing cores. The processor 501 executes various functional applications and information processing by running software programs and modules.

[0264] The wake-up receiver 502 and the main transceiver 503 can be implemented as a communication component, which can be a communication chip, and the communication component can be called a transceiver. In some embodiments, the wake-up receiver 502 can be used to implement the functions and steps of the above-mentioned receiving module 320, or the main transceiver 503 can be used to implement the functions and steps of the above-mentioned receiving module 320.

[0265] In some embodiments, the electronic device 500 further includes a wireless energy harvesting circuit, or a peripheral circuit for waking up the receiver 502 .

[0266] The wireless energy harvesting circuit is used for performing wireless energy harvesting. When the wake-up receiver 502 and the main transceiver 503 are both turned off, the wireless energy harvesting circuit remains in the working state and continues to perform wireless energy harvesting.

[0267] The memory 504 is connected to the processor 501 via a bus 505 .

[0268] The memory 504 may be used to store at least one instruction, and the processor 501 may be used to execute the at least one instruction to implement each step in the above method embodiment.

[0269] In addition, the memory 504 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. Volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, and programmable read-only memory (PROM).

[0270] In some embodiments, the wake-up receiver 502 receives signals / data independently, or the processor 501 controls the wake-up receiver 502 to receive signals / data, or the processor 501 requests the wake-up receiver 502 to receive signals / data, or the processor 501 cooperates with the wake-up receiver 502 to receive signals / data.

[0271] In some embodiments, the main transceiver 503 independently sends signals / data, or the processor 501 controls the main transceiver 503 to send signals / data, or the processor 501 requests the main transceiver 503 to send signals / data, or the processor 501 cooperates with the main transceiver 503 to send signals / data.

[0272] FIG24 shows a schematic structural diagram of an access point 600 provided by an exemplary embodiment of the present application, including a processor 601 , a receiver 602 , a transmitter 603 , a memory 604 , and a bus 605 .

[0273] The processor 601 includes one or more processing cores. The processor 601 executes various functional applications and information processing by running software programs and modules.

[0274] The receiver 602 and the transmitter 603 may be implemented as a communication component, which may be a communication chip, and may be referred to as a transceiver. In some embodiments, the transmitter 603 may be used to implement the functions and steps of the sending module 420 described above.

[0275] The memory 604 is connected to the processor 601 via a bus 605 .

[0276] The memory 604 may be used to store at least one instruction, and the processor 601 may be used to execute the at least one instruction to implement each step in the above method embodiment.

[0277] In addition, the memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic or optical disks, EEPROM, EPROM, SRAM, ROM, magnetic storage, flash memory, PROM.

[0278] In some embodiments, the receiver 602 receives signals / data independently, or the processor 601 controls the receiver 602 to receive signals / data, or the processor 601 requests the receiver 602 to receive signals / data, or the processor 601 cooperates with the receiver 602 to receive signals / data.

[0279] In some embodiments, the transmitter 603 independently sends signals / data, or the processor 601 controls the transmitter 603 to send signals / data, or the processor 601 requests the transmitter 603 to send signals / data, or the processor 601 cooperates with the transmitter 603 to send signals / data.

[0280] In an exemplary embodiment, a computer-readable storage medium is further provided, in which at least one program is stored. The at least one program is loaded and executed by a processor to implement the PPDU receiving method and / or PPDU sending method provided in the above-mentioned various method embodiments.

[0281] In an exemplary embodiment, a computer program product or computer program is also provided. When the computer program product or computer program runs on a processor, it enables the communication device (electronic device 500 or access point 600) to perform the PPDU receiving method and / or PPDU sending method provided in the above-mentioned various method embodiments.

[0282] Those skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or may be accomplished by a program instructing the relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk, or an optical disk, etc.

[0283] The above are only optional embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application.

Claims

1. A method for receiving a physical layer protocol data unit PPDU, characterized in that: The method comprises: All or part of the information fields of a first PPDU are received, where the all or part of the information fields include a first information field, where the first information field is used to indicate a target device type for receiving the first PPDU.

2. The method according to claim 1, characterized in that The first information field is a synchronization field.

3. The method according to claim 2, characterized in that The synchronization domain is a first sequence, used to indicate that the target device type receiving the first PPDU is a first device type; The synchronization field is a second sequence, which is used to indicate that the target device type receiving the first PPDU is a second device type.

4. The method according to claim 3, characterized in that The second sequence is obtained based on the first sequence.

5. The method according to claim 4, characterized in that The second sequence is obtained by cyclically shifting the first sequence.

6. The method according to claim 4, characterized in that The second sequence is obtained by masking all or part of the bits in the first sequence.

7. The method according to claim 6, characterized in that n is a positive integer, The partial bits are the first n bits in the first sequence; or, The partial bits are the last n bits in the first sequence; or, The part of bits is a first subsequence in the first sequence, the first sequence includes the first subsequence and a second subsequence, and the second subsequence is obtained by flipping the first subsequence; or, The part of bits is a second subsequence in the first sequence, the first sequence includes a first subsequence and the second subsequence, and the second subsequence is obtained by flipping the first subsequence.

8. The method according to claim 2, characterized in that: The first information field is a media medium access MAC header field.

9. The method according to claim 8, characterized in that The MAC header field includes a type field; The type field is a first value, used to indicate that the target device type receiving the first PPDU is a first device type; The type field is a second value, used to indicate that the target device type receiving the first PPDU is a second device type.

10. The method according to claim 8, characterized in that The MAC header field includes an identification ID field; The ID field is a first ID, used to indicate that the target device type receiving the first PPDU is a first device type, and the first ID is an ID maintained by a device of the first device type; The ID field is a second ID, which is used to indicate that the target device type receiving the first PPDU is a second device type, and the second ID is an ID maintained by a device of the second device type.

11. The method according to any one of claims 2 to 10, characterized in that: The first device type is a wake-up receiver WUR device; The second device type is an ambient energy AMP device.

12. A method for sending a PPDU, characterized in that: The method is performed by an access point, and the method includes: All or part of the information fields of a first PPDU are received, where the all or part of the information fields include a first information field, where the first information field is used to indicate a target device type for receiving the first PPDU.

13. The method according to claim 12, characterized in that The first information field is a synchronization field.

14. The method according to claim 13, characterized in that The synchronization domain is a first sequence, used to indicate that the target device type receiving the first PPDU is a first device type; The synchronization field is a second sequence, which is used to indicate that the target device type receiving the first PPDU is a second device type.

15. The method according to claim 14, characterized in that The second sequence is obtained based on the first sequence.

16. The method according to claim 15, characterized in that The second sequence is obtained by cyclically shifting the first sequence.

17. The method according to claim 15, characterized in that The second sequence is obtained by masking all or part of the bits in the first sequence.

18. The method according to claim 17, characterized in that The partial bits are the first n bits in the first sequence; or, The partial bits are the last n bits in the first sequence; or, The part of bits is a first subsequence in the first sequence, the first sequence includes the first subsequence and a second subsequence, and the second subsequence is obtained by flipping the first subsequence; or, The part of bits is a second subsequence in the first sequence, the first sequence includes a first subsequence and the second subsequence, and the second subsequence is obtained by flipping the first subsequence.

19. The method according to claim 13, characterized in that The first information field is a MAC header field.

20. The method according to claim 19, characterized in that The MAC header field includes a type field; The type field is a first value, used to indicate that the target device type receiving the first PPDU is a first device type; The type field is a second value, used to indicate that the target device type receiving the first PPDU is a second device type.

21. The method according to claim 19, characterized in that The MAC header field includes an ID field; The ID field is a first ID, used to indicate that the target device type receiving the first PPDU is a first device type, and the first ID is an ID maintained by a device of the first device type; The ID field is a second ID, which is used to indicate that the target device type receiving the first PPDU is a second device type, and the second ID is an ID maintained by a device of the second device type.

22. The method according to any one of claims 13 to 21, characterized in that: The first device type is a WUR device; The second device type is an AMP device.

23. A PPDU receiving device, characterized in that: The device comprises: The receiving module is used to receive all or part of the information fields of the first PPDU, where the all or part of the information fields include a first information field, and the first information field is used to indicate a target device type for receiving the first PPDU.

24. A PPDU sending device, characterized in that: The device comprises: The sending module is used to send a first PPDU, where the first PPDU includes a first information field, where the first information field is used to indicate a target device type that receives the first PPDU.

25. An electronic device, characterized in that: The electronic device comprises: processor; a transceiver connected to the processor; a memory for storing executable instructions for the processor; The processor is configured to load and execute the executable instructions to implement the PPDU receiving method as described in any one of claims 1 to 11.

26. An access point, characterized in that: The access point comprises: processor; a transceiver connected to the processor; a memory for storing executable instructions for the processor; The processor is configured to load and execute the executable instructions to implement the PPDU according to any one of claims 12 to 22. The sending method.

27. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one program, and the at least one program is loaded and executed by the processor to implement the PPDU receiving method as described in any one of claims 1 to 11, or the PPDU sending method as described in any one of claims 12 to 22.

28. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. The processor obtains the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to implement the PPDU receiving method described in any one of claims 1 to 11, or the PPDU sending method described in any one of claims 12 to 22.

Images