Communication method and communication device

Abstract

Provided are a communication method and a communication device. The method comprises: a first device receives a first trigger frame sent by a second device, the first trigger frame being used for indicating a first resource; and the first device sends a first random access code to the second device via the first resource.

Description

Communication methods and communication equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0002] Communication devices can schedule resources by sending trigger frames, enabling devices with data transmission needs to use those resources. However, communication devices may sometimes be unable to know in advance which devices have data transmission needs. This forces devices with data transmission needs to autonomously select resources from the resources scheduled by the trigger frame according to certain rules, which can easily lead to resource collisions. Summary of the Invention

[0003] This application provides a communication method and a communication device. The various aspects covered by this application are described below.

[0004] In a first aspect, a communication method is provided, comprising: a first device receiving a first trigger frame sent by a second device, the first trigger frame being used to indicate a first resource; and the first device sending a first random access code to the second device through the first resource.

[0005] In a second aspect, a communication method is provided, comprising: a second device sending a first trigger frame to a first device, the first trigger frame being used to indicate a first resource; and the second device receiving a first random access code sent by the first device through the first resource.

[0006] Thirdly, a communication device is provided, the communication device being a first device, the first device comprising: a communication module, configured to receive a first trigger frame sent by a second device, the first trigger frame being used to indicate a first resource; and to send a first random access code to the second device through the first resource.

[0007] Fourthly, a communication device is provided, the communication device being a second device, the second device comprising: a communication module, configured to send a first trigger frame to a first device, the first trigger frame being used to indicate a first resource; and to receive a first random access code sent by the first device through the first resource.

[0008] Fifthly, a communication device is provided, including a transceiver, a memory, and a processor, wherein the memory is used to store a program, the processor is used to invoke the program in the memory, and to control the transceiver to receive or transmit signals, so that the communication device performs the method as described in the first or second aspect.

[0009] A sixth aspect provides an apparatus including a processor for calling a program from a memory to cause the apparatus to perform the method as described in the first or second aspect.

[0010] A seventh aspect provides a chip including a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in the first or second aspect.

[0011] Eighthly, a computer-readable storage medium is provided having a program stored thereon that causes a computer to perform the method as described in the first or second aspect.

[0012] Ninth aspect, a computer program product is provided, characterized in that it includes a program that causes a computer to perform the method as described in the first or second aspect.

[0013] In a tenth aspect, a computer program is provided that causes a computer to perform the method as described in the first or second aspect.

[0014] As can be seen from the above, in this embodiment of the application, the first device is instructed to report its random access code by triggering a frame, so that the second device can know the device with data transmission needs. This helps the second device to make more targeted scheduling, thereby avoiding resource collisions between devices during data reporting to a certain extent. Attached Figure Description

[0015] Figure 1 is a system architecture example diagram of a wireless communication system applicable to embodiments of this application.

[0016] Figure 2 shows an example diagram of a zero-power network.

[0017] Figure 3 is an example diagram of energy harvesting methods for zero-power devices.

[0018] Figure 4 is an example diagram of the backscatter communication method of zero-power devices.

[0019] Figure 5 shows an example of load modulation methods for zero-power devices.

[0020] Figure 6 is an example diagram of the encoding method for zero-power devices.

[0021] Figure 7 is an example of resource collision phenomena in a communication system.

[0022] Figure 8 is a flowchart illustrating the communication method provided in an embodiment of this application.

[0023] Figure 9 is a schematic diagram of the random access phase provided in an embodiment of this application.

[0024] Figure 10 is a flowchart illustrating the authorized access phase provided in an embodiment of this application.

[0025] Figure 11 is an example diagram of the format of the synchronization frame provided in the embodiments of this application.

[0026] Figure 12 is a structural example of a traditional leader.

[0027] Figure 13 is another example diagram of the format of the synchronization frame provided in the embodiments of this application.

[0028] Figure 14 shows another structural example of a traditional leader.

[0029] Figure 15 is a schematic diagram of the signal domain format in Figure 14.

[0030] Figure 16 is another example diagram of the format of the synchronization frame provided in the embodiments of this application.

[0031] Figure 17 is a flowchart illustrating the entire access process provided in an embodiment of this application.

[0032] Figure 18 is a schematic diagram of the structure of a communication device provided in one embodiment of this application.

[0033] Figure 19 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0034] Figure 20 is a schematic diagram of an apparatus applicable to embodiments of this application. Detailed Implementation

[0035] The technical solutions in this application will now be described with reference to the accompanying drawings. For ease of understanding, the communication terms and processes that may be involved in the embodiments of this application will first be introduced with reference to Figures 1 to 6.

[0036] Communication system

[0037] The technical solutions of this application can be applied to various communication systems, such as wireless local area networks (WLAN), wireless fidelity (Wi-Fi), high-performance radio local area networks (HIPELAN), wide area networks (WAN), cellular networks, or other communication systems. For example, the technical solutions provided in this application can be applied to communication systems using the 802.11 standard. Exemplarily, the 802.11 standard includes, but is not limited to, the 802.11a standard, the 802.11g standard, the 802.11ba standard, the 802.11bp standard, and next-generation 802.11 standards.

[0038] Figure 1 shows a schematic diagram of a communication system applicable to an embodiment of this application. As shown in Figure 1, the communication devices in the communication system 100 may include a first device 110 and a second device 120.

[0039] In some scenarios, such as in a Wi-Fi system, the first device 110 can be a station (STA), and the second device 120 can be an access point (AP). The AP is used to create a wireless network and provide wireless network services to the STA. STAs can access the network through the AP.

[0040] In this context, the Access Point (AP) can be a device in a wireless network. An AP can be a communication entity such as a communication server, router, switch, or bridge; alternatively, it can include various forms of macro base stations, micro base stations, or relay stations. Of course, an AP can also be a chip, circuit, or processing system within these various types of devices to implement the methods and functions of the embodiments described in this application. APs can be applied in various scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes); smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines); nodes in the Internet of Things (IoT); entertainment terminals (e.g., AR / VR wearable devices); smart devices in smart offices (e.g., printers, projectors); vehicle-to-everything (V2X) devices; and infrastructure in everyday life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-checkout machines, self-service ordering machines).

[0041] A STA can be a device with wireless transceiver capabilities, such as supporting the 802.11 series of protocols, and communicating with an AP or other STAs. For example, an STA is any user communication device that allows a user to communicate with an AP and thus with a WLAN network. STAs include, for example, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device.

[0042] STA can also be a device that provides users with voice and / or data connectivity, such as a handheld device or in-vehicle device with wireless connectivity. Examples include mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future evolution of public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0043] STA can also refer to wearable devices. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Examples include smartwatches or smart glasses, as well as devices focused on a specific application function that require interaction with other devices like smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0044] STA can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network for human-machine interconnection and object-to-object interconnection.

[0045] STA can also refer to devices within a vehicle-to-everything (V2X) system. The communication methods within a V2X system are collectively referred to as V2X, where X can represent anything. For example, V2X communication includes vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0046] In addition, STA can also include sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data, receiving control information and downlink data from the AP, and sending electromagnetic waves to transmit data to the AP.

[0047] In this application embodiment, the AP can be a device used to communicate with the STA. The AP can be a network device or a terminal device in a wireless local area network. The AP can be used to communicate with the STA through a wireless local area network.

[0048] From the perspective of the communication standards supported by the AP, in some implementations, the AP is a device that supports the 802.11 standard. Furthermore, the AP can also be a device that supports various current and future 802.11 family WLAN standards, including 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11ba, and 802.11a.

[0049] From the perspective of the communication standards supported by the STA, in some implementations, the STA is a device that can support the 802.11 standard. The STA can also support various current and future 802.11 family WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11ba, and 802.11a.

[0050] It should be understood that the specific forms of STA and AP are not specifically limited in the embodiments of this application, and are merely illustrative examples.

[0051] Furthermore, the technical solution implemented in this application can also be extended to other scenarios beyond Wi-Fi systems. For example, in some other scenarios, the first device 110 can be a terminal device, and the second device 120 can be a network device. The network device can be a device that communicates with the terminal device. The network device can provide communication coverage for a specific geographical area and can communicate with terminal devices located within that coverage area.

[0052] In this context, terminal equipment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication equipment, user agent, or user device. Terminal equipment can be, for example, a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as home appliances, sensors, and electronic tags with wireless connectivity. Terminal equipment can also be a wireless terminal in a smart home, a wireless terminal in an IWSN (Internet Wireless Network), a wireless terminal in smart logistics and smart warehousing, a wireless terminal in self-driving vehicles, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, and a wireless terminal in a smart city, etc.

[0053] A network device can be a device used to communicate with a terminal device. A network device can also be an access network device or a radio access network device; for example, a network device can be a base station. In the embodiments of this application, the network device can refer to a radio access network (RAN) node or device that connects a terminal device to a wireless network. A base station can broadly encompass various names listed below, or can be replaced by names such as: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), secondary station (SeNB), multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, or a device that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device performing base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0054] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0055] In some deployments, the network device in this application embodiment may refer to a CU or a DU; or, the network device may include both a CU and a DU. The gNB may also include an AAU.

[0056] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0057] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform such as a cloud platform.

[0058] Figure 1 illustrates two first devices 110 and one second device 120. Optionally, the communication system 100 may include a plurality of second devices 120, and the communication system 100 may also include other numbers of first devices 110.

[0059] Zero-power communication technology

[0060] Zero-power communication networks can employ power harvesting and backscattering communication technologies. A zero-power communication network consists of a network device 110 and a zero-power device 120, as shown in Figure 2. The network device 110 sends wireless power signals and downlink communication signals to the zero-power device 120, and receives backscattered signals from the zero-power device. A basic zero-power device 120 may include a power harvesting module, a backscattering communication module, and a low-power computing module. Furthermore, the zero-power device 120 may also have a memory or sensor to store basic information (such as object identification) or acquire sensor data such as ambient temperature and humidity. The power harvesting and backscattering communication technologies in zero-power communication are described below.

[0061] As shown in Figure 3, the energy harvesting module harvests electromagnetic wave energy from space based on the principle of electromagnetic induction, thereby obtaining the energy required to drive the zero-power device. For example, the energy harvesting module can be used to drive low-power demodulation and modulation modules, sensors, and memory modules within the zero-power device. Therefore, the zero-power device does not require a traditional battery.

[0062] As shown in Figure 4, the zero-power device 120 receives a wireless signal sent by the network device 110. After receiving the wireless signal, the zero-power device 120 modulates the wireless signal to load the information to be transmitted. Then, the zero-power device 120 radiates the modulated signal from the antenna. The above information transmission process is called backscatter communication. Backscatter and load modulation are inseparable. Load modulation adjusts and controls the circuit parameters of the zero-power device's oscillation circuit according to the data stream's rhythm, causing parameters such as impedance to change accordingly, thereby completing the modulation. Load modulation technology mainly includes two methods: resistive load modulation and capacitive load modulation. In resistive load modulation, a resistor is connected in parallel with the load, and this resistor is turned on or off based on the control of the binary data stream, as shown in Figure 5. The switching on and off of the resistor causes a change in the circuit voltage, thereby realizing amplitude shift keying (ASK), that is, signal modulation and transmission are achieved by adjusting the amplitude of the backscatter signal of the zero-power device. Similarly, in capacitive load modulation, the resonant frequency of the circuit can be changed by switching the capacitor on and off, realizing frequency shift keying (FSK), 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.

[0063] As can be seen, zero-power devices achieve backscatter communication by modulating the incoming signal using load modulation. Therefore, zero-power devices have the following significant advantages:

[0064] First: Zero-power devices do not actively transmit signals, therefore they do not require complex RF links, such as power amplifiers (PA) and RF filters;

[0065] Second: Zero-power devices do not need to actively generate high-frequency signals, therefore they do not need high-frequency crystal oscillators;

[0066] Third: With the help of backscatter communication, the signal transmission of zero-power devices does not require the zero-power devices to consume their own energy.

[0067] Zero-power devices, due to their significant advantages such as low cost, zero power consumption, and small size, can be widely used in various industries. For example, they can be applied to logistics, smart warehousing, smart agriculture, energy and power, and the industrial internet. Alternatively, they can be used in smart wearables and smart homes.

[0068] The following provides examples of encoding methods that may be used in zero-power communication.

[0069] Zero-power communication systems can encode signals using one of the following coding schemes: non-return-to-zero (NRZ) coding, Manchester coding, unipolar RZ coding, differential binary phase (DBP) coding, Miller coding, and differential coding.

[0070] (1) Reverse Non-Return-to-Zero Encoding

[0071] Inverted non-return-to-zero encoding uses a high level to represent binary "1" and a low level to represent binary "0", as shown in Figure 6(a).

[0072] (2) Manchester encoding

[0073] Manchester coding is also known as split phase coding. In Manchester coding, the value of a bit is represented by the change in level (rising / falling) over half a bit period within that bit length. A negative transition over half a bit period represents a binary "1", and a positive transition over half a bit period represents a binary "0", as shown in Figure 6(b).

[0074] (3) Unipolar Return-to-Zero (RZ) Encoding

[0075] In unipolar return-to-zero (UNZ) encoding, a high level during the first half-bit cycle represents a binary "1", while a low level signal throughout the entire bit cycle represents a binary "0", as shown in Figure 6(c). UNZ encoding can be used to extract bit synchronization signals.

[0076] (4) Differential biphase encoding

[0077] In differential biphase coding, any edge within half a bit cycle represents a binary "0", and the absence of an edge represents a binary "1", as shown in Figure 6(d). Furthermore, the voltage levels are inverted at the beginning of each bit cycle. Therefore, the bit clock is relatively easy to reconstruct for the receiver.

[0078] (5) Miller coding

[0079] Miller encoding uses any edge within half a bit cycle to represent a binary "1", while a constant level in the next bit cycle represents a binary "0". A level alternation occurs at the beginning of a bit cycle, as shown in Figure 6(e). Therefore, the bit clock is relatively easy for the receiver to reconstruct.

[0080] (6) Differential coding

[0081] In differential coding, each binary "1" to be transmitted will cause a change in the signal level, while for a binary "0", the signal level remains unchanged.

[0082] The following section describes the classification of zero-power devices.

[0083] In zero-power communication technology, based on the energy source and energy usage of zero-power devices, they can be divided into three categories: passive zero-power devices, semi-passive zero-power devices, and active zero-power devices.

[0084] Passive zero-power devices (ZEPDs) typically do not require an internal battery. When a ZEPD approaches a network device, it falls within the near-field range of the network device's antenna radiation. At this point, the ZEPD's antenna can generate an induced current through electromagnetic induction. This induced current powers the ZEPD, driving its low-power chip circuitry to demodulate forward link signals and modulate backward link signals. For backscatter links, ZEPDs can use backscattering to transmit signals.

[0085] As can be seen from the above introduction, passive zero-power devices do not require an internal battery to drive them, whether the transmission process is based on the forward link or the reverse link, making them truly zero-power devices.

[0086] In some implementations, the aforementioned passive zero-power device can be an electronic tag, and correspondingly, the network device can be a reader / writer of a radio frequency identification (RFID) system, used to read the contents of the electronic tag and / or to change the contents of the electronic tag.

[0087] Semi-passive zero-power devices do not have conventional batteries installed, but they can use energy harvesting modules, such as RF energy harvesting modules, to harvest radio wave energy and store the harvested energy in an energy storage unit, such as a capacitor. Once the energy storage unit has acquired energy, it can power the zero-power device to drive low-power chip circuits. This enables the demodulation of forward link signals and the modulation of backward link signals. For backscatter links, zero-power devices use backscattering to transmit signals.

[0088] As can be seen from the above introduction, semi-passive zero-power devices do not require a built-in battery to drive either the forward link transmission process or the reverse link transmission process. Although they use energy stored in capacitors during operation, the energy comes from the radio energy collected by the energy harvesting module, so they are also a true zero-power device.

[0089] Active zero-power devices can have a built-in battery. The battery powers the device, driving its low-power chip circuitry to demodulate the forward link signal and modulate the backward link signal. For the backscatter link, the active zero-power device uses backscattering for signal transmission. Therefore, the zero power consumption of this type of terminal is mainly reflected in the fact that the signal transmission in the backward link does not consume the terminal's own power, but instead uses backscattering.

[0090] Active zero-power devices can be powered by an internal battery, thus increasing their communication range and improving communication reliability. Therefore, they are used in scenarios with relatively high requirements for communication distance and read latency.

[0091] In some implementations, the aforementioned active zero-power device can be an electronic tag, and the network device can be a radio frequency identification (RFID) reader. In this case, the built-in battery can power the RFID chip inside the electronic tag, thereby increasing the read / write distance between the RFID reader and the electronic tag. On the other hand, the built-in battery can also power the RFID chip inside the electronic tag, thereby reducing the read / write latency of the RFID reader and improving communication reliability.

[0092] In addition to classifying zero-power devices based on their energy source and how they are used, they can also be classified based on the type of transmitter.

[0093] First, zero-power devices based on backscattering.

[0094] These zero-power devices transmit uplink data using the backscattering method described above. These devices do not have an active transmitter for active transmission, but only a backscattering transmitter. Therefore, when this type of terminal transmits data, a network device needs to provide a carrier wave, and the terminal device uses this carrier wave for backscattering to achieve data transmission.

[0095] Second, zero-power devices based on active transmitters.

[0096] These zero-power devices use active transmitters with active transmission capabilities for uplink data transmission. Therefore, when sending data, these devices can transmit data using their own active transmitters without requiring a carrier wave from network equipment. Suitable active transmitters for zero-power devices include, for example, ultra-low-power ASK or ultra-low-power FSK transmitters. Based on current implementations, these transmitters can reduce overall power consumption to 400–600 µW when transmitting a 100 µW signal.

[0097] Third, a zero-power device that simultaneously possesses backscattering and an active transmitter.

[0098] These zero-power devices can support both backscatter and active transmitters. The device can determine which uplink transmission method to use based on different conditions (such as battery level and available ambient energy) or network device scheduling: whether to use backscatter or an active transmitter for active transmission.

[0099] Cellular Passive Internet of Things

[0100] With the application of 5G technology, the types of connected devices and application scenarios in the Internet of Things (IoT) are increasing, placing higher demands on the price and power consumption of communication equipment. Therefore, the application of battery-free, low-cost passive IoT devices has become a key technology for cellular IoT. Passive IoT devices can be based on zero-power devices and extended to suit cellular IoT.

[0101] Devices based on ambient energy

[0102] In communication systems (such as NR or WiFi systems), the battery-free and low-cost nature of communication devices is highly advantageous for deployment and maintenance. Current standards are investigating how to support ambient-powered IoT devices in NR and WiFi systems, referred to as ambient IoT devices, ambient-powered devices (AMP devices), or AMP IoT devices. For ease of description, these devices will be collectively referred to as AMP devices below. The energy required for AMP devices to operate is ambient energy, such as wireless signals, solar energy, and thermal energy. AMP devices are similar to passive or semi-passive devices in zero-power communication.

[0103] The 3rd Generation Partnership Project (3GPP) RAN conducted research on AMP devices, broadly categorizing them into three types: Device A, Device B, and Device C. These three types of AMP devices differ in complexity and communication capabilities.

[0104] Device A does not have energy storage capabilities, and it cannot transmit signals independently. In other words, Device A uses backscattering for signal transmission.

[0105] Device B has energy storage capabilities, but it cannot transmit signals independently. In other words, Device B uses backscattering for signal transmission, and it can amplify the backscattered signal using the stored energy.

[0106] Device C has energy storage capabilities and can independently transmit signals. In other words, Device C has active signal transmission capabilities.

[0107] As can be seen from the above capability definitions, Device A has the lowest complexity and power consumption compared to Device B and Device C. For example, Device A's power consumption can be as low as 1μW, but its communication distance is limited, typically only a few meters. Device A generally requires a network device to provide a carrier signal for backscatter transmission. Device C generally has a large-capacity capacitor to store energy from the environment. Device C's power consumption can reach several hundred μW. Furthermore, Device C can actively transmit signals and has a longer communication distance. Device C can actively transmit, therefore it does not require a network device to provide a carrier signal. Device B's complexity and power consumption fall between those of Device A and Device C.

[0108] Based on the discussion of AMP equipment application scenarios in 3GPP SA1, AMP equipment can be applied to at least the following four scenarios:

[0109] Scenario 1: Object recognition, such as logistics, production line product management, and supply chain management;

[0110] Scenario 2: Environmental monitoring, such as monitoring of temperature, humidity, and harmful gases in the work environment and natural environment;

[0111] Scenario 3: Location services, such as indoor positioning, smart item finding, and production line item location.

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

[0113] Electronic product code query (EPC query) process

[0114] In the radio frequency identification (RFID) standard, inventory operations can be completed through the EPC query process.

[0115] The EPC query process includes the following steps: initiating the identification process, tag selection, random number generation and response, collision handling and Q-value adjustment, tag state transition, entering a safe state, and ending the identification process.

[0116] Initiating the recognition process: The interrogator initiates a new tag recognition process by sending a query command. This command marks the start of a recognition process, which may consist of multiple frames.

[0117] Tag selection slot: Upon receiving a query command, all tags will determine whether to participate in the identification of this frame based on whether their own flag meets the requirements in the query command. Tags that meet the requirements will select a slot number as the slot for transmitting packets based on the frame length (determined by the Q value) in the query command and enter the arbitration state.

[0118] Random number generation and response: All tags selected with slot number 0 enter the response state and send a 16-bit random number (RN16) to the reader. Upon receiving the RN16, if no collision occurs, the reader considers the identification successful and subsequently sends an acknowledgment (ACK) command to the tag. This ACK command contains the same RN16 as confirmation information.

[0119] Collision handling and Q-value adjustment: If a collision occurs or a time slot is empty, the reader sends a query adjustment command to adjust the Q-value, which also signifies the start of the next time slot. All tags that participated in this round of queries but have not yet been queried decrement their time slot counters by 1 and return to the responding state.

[0120] Tag state transition: If the tag successfully receives an ACK with the correct RN16, it will send its protocol control (PC), EPC, and cyclic redundancy check (CRC) to the reader, and then enter the acknowledged state, waiting for the reader to send a Req_RN command with the correct RN16. If the tag does not receive the correct ACK, or receives the correct ACK but does not receive the correct Req_RN, it will return to the arbitration state.

[0121] Entering the secure state: If all goes well, after the tag receives the Req_RN with the correct RN16, it will enter the open state and wait for the password. If there is no password or the received password is correct, the tag will enter the secure state, at which point the reader can perform read and write operations on the tag.

[0122] End of recognition process: After completing the operation on the tag, the reader sends a query repeat command to indicate that it is entering the next time slot. All tags that participated in this round of query but have not yet been queried decrement their time slot counter by 1 and return to the response state. Tags that have already been queried can go into sleep mode.

[0123] The EPC query process employs a random-slotted collision arbitration algorithm to prevent collisions. This algorithm ensures that each label can be uniquely identified even in a multi-label environment.

[0124] In the random slot collision arbitration algorithm, each tag, upon receiving a query command or query adjustment command, loads a random number (or pseudo-random number) into its slot counter based on the Q value indicated by the hit indicator. These random numbers are generated by the tag's random number generator (RNG). The tag decrements its slot counter according to the reader's command (such as a query repeat command). When the slot counter reaches zero, the tag replies to the reader, typically replying with an RN16. Because each tag has a unique random slot counter value, the possibility of different tags replying simultaneously is reduced, effectively avoiding collisions. When a tag's slot counter reaches zero and it replies to the reader, if the reply is not acknowledged, the tag returns to the arbitration panel.

[0125] In certain communication scenarios, network devices need to communicate with a large number of terminal devices, but the network devices cannot know the number of terminal devices that need to communicate in advance. One possible solution for this scenario is to configure the network device with a large resource pool, allowing terminal devices to select resources from the pool according to certain rules. However, this solution may lead to resource collision issues.

[0126] Let's take AMP devices as an example. AMP devices can be applied to logistics and warehousing scenarios. In such scenarios, a large number of goods need to be transferred, stored, loaded, unloaded, and inventoried at logistics stations or warehouses. With warehouse ordering, goods receiving, goods management, and goods issuing occurring, AMP devices need to communicate centrally with network devices, such as reporting goods information and location information stored on the AMP device. Furthermore, the network device cannot know in advance the number of AMP devices that need to report data. Assuming the network device configures a large resource pool for the AMP devices, the AMP devices can select resources from the pool for transmission according to certain rules. However, multiple AMP devices may select the same resource, leading to resource collisions.

[0127] The following example uses a WiFi system to demonstrate in more detail the resource collision phenomenon that may occur when the AP schedules AMP STAs.

[0128] In WiFi systems, due to the low complexity of AMP STAs, their receivers typically only support simple modulation and demodulation methods, such as amplitude shift keying (ASK), frequency shift keying (FSK), and phase shift keying (PSK), but not orthogonal frequency division multiplexing (OFDM). Therefore, AMP STAs do not support traditional channel access mechanisms and cannot coexist with traditional devices. To transmit data in a WiFi system, the AP needs to indicate available channel resources to the AMP STA by sending trigger frames. These channel resources can be obtained by the AP, for example, through clear channel assessment (CCA). During the process of AP triggering AMP STA to transmit data, since there may be a large number of AMP STAs, a more efficient approach is for the AP to allocate a certain amount of resources through a trigger frame. Multiple AMP STAs can then use the resources allocated by the AP to transmit data in a multi-user multiplexing manner (such as time division multiplexing (TDM), frequency division multiplexing (FDM), or code division multiplexing (CDM)).

[0129] Taking TDM as an example, the AP can allocate a certain number of time-domain resources, such as time slots, through a trigger frame. The AMP STAs receiving this trigger frame can determine the target time-domain resource within the time-domain resources allocated by the AP for transmission according to certain rules. Figure 7 shows a typical triggering process. The AP sends resource scheduling information through the trigger frame, which can include four time slots. When AMP STAs 1-4 select time slots, different AMP STAs may select the same time slot, resulting in resource collisions (as shown in the collision time slots in Figure 7). Alternatively, a time slot may not be selected by any AMP STA (as shown in the empty time slots in Figure 7), thus wasting resources.

[0130] To address the aforementioned issues, the embodiments of this application will be described in detail below with reference to Figure 8.

[0131] Figure 8 is a schematic flowchart of the communication method provided in an embodiment of this application. The method in Figure 8 is described from the perspective of communication between a first device and a second device. The first device may be, for example, a terminal device (such as an AMP device), and the second device may be a network device (such as an AP, base station, or reader). Taking a Wi-Fi system as an example, the first device may be a STA (such as an AMP STA), and the second device may be an AP. As an example, this embodiment of the application is applied to scenarios such as logistics or inventory management. The first device may be an AMP device, and the second device may be a network device acting as a reader. The network device can collect information from the AMP device by sending trigger frames. It should be noted that when the first device is an AMP device, the AMP device may be an AMP device that supports backscatter communication and / or an AMP device that supports active transmission.

[0132] Referring to Figure 8, in step S810, the first device receives a first trigger frame sent by the second device. This first trigger frame indicates one or more resources. Different resources among these resources may correspond to different time-domain, frequency-domain, or code-domain locations. As an example, the first trigger frame indicates one or more time-domain resources (or one or more TDM resources), which may be, for example, one or more time units (such as one or more time slots).

[0133] The one or more resources may include a first resource. Referring to step S820 in Figure 8, the first device can send a first random access code to the second device through the first resource. Before executing step S820, the first device can determine the first resource from the one or more resources indicated by the first trigger frame according to certain rules. For example, the first device can randomly select the first resource from the one or more resources indicated by the first trigger frame. Alternatively, the first device can select the first resource from the one or more resources indicated by the first trigger frame according to its own identifier and a certain algorithm.

[0134] The first random access code can be used to identify the first device. This application embodiment does not specifically limit the type of the first random access code. For example, the first random access code can be a random number. This random number can, for example, be generated by the RNG of the first device. This application embodiment does not specifically limit the length of the random number; the random number can, for example, be a 16-bit random number, and correspondingly, the random number can also be called RN16.

[0135] Besides a random number, the first random access code can also be a first identifier of the first device. This first identifier can be, for example, a temporary identifier of the first device (the first identifier can also be a non-temporary identifier, for example, a second identifier mentioned below). This first identifier (such as a temporary identifier) ​​can be determined based on a second identifier of the first device. This second identifier can be, for example, one or more of the following: the device identifier of the first STA, the media access control (MAC) identifier of the first STA, the electronic product code (EPC) of the first STA, or an identifier determined based on standard predefined information. Determining the first identifier based on the second identifier can include: the first identifier being a portion of the second identifier. For example, the first identifier can be determined by truncating or extracting partial information from the second identifier. Alternatively, the first identifier (such as a temporary identifier) ​​can be an identifier selected from a set of temporary identifiers (e.g., randomly selected or selected according to certain rules).

[0136] The first random access code can be carried in the first message. The first message refers to the message used to carry or indicate the random access code. From this perspective, the first trigger frame can also be understood as a resource used to schedule one or more resources for one or more devices (such as AMP devices) to send the first message, which in turn sends their respective random access codes to the second device. Taking an inventory or logistics scenario as an example, assuming the first device is an AMP device and the second device is a network device (such as a reader), the network device may not know in advance the number of AMP devices that need to report data. Therefore, the second device can initiate a random access phase. In this phase, the first device can schedule one or more resources through the first trigger frame. These resources are used for the AMP devices to send the first message, which carries or indicates the corresponding random access code (or temporary identifier) ​​for each AMP device, enabling the network device to identify the AMP device that needs to report data.

[0137] After the first device sends a first random code to the second device, the second device can detect the first random access code. When the second device detects the first random access code, it can schedule the first device based on the first random access code. It should be understood that multiple devices may send their respective random access codes to the second device through the resources indicated by the first trigger frame. If multiple devices choose the same resource to send random access codes, a collision may occur. In this case, the second device may not be able to identify the random access codes of the multiple devices, or the second device may be able to successfully demodulate the random access code of one of the multiple devices. In this case, the second device can choose to schedule only the device corresponding to the random access code that it can identify in subsequent processes.

[0138] As can be seen from the above, in this embodiment of the application, the first device (such as an AMP device) is instructed to report its random access code by triggering a frame, so that the second device (such as a network device) knows the device that needs to report data. This helps the second device to make more targeted scheduling in the future, thereby avoiding resource collisions between devices during the data reporting process to a certain extent.

[0139] The process of sending the first trigger frame and receiving the random access code can be referred to as the random access phase in the entire access process. The following example, with reference to Figure 9, illustrates this random access phase in more detail. In the example shown in Figure 9, the first device is an AMP STA in the Wi-Fi system, the second device is an AP in the Wi-Fi system, the AP schedules time slots, and the random access code is the temporary ID of the AMP STA. Referring to Figure 9, the AP sends the first trigger frame (which can be called the AMP trigger frame). This first trigger frame can be used to schedule several time slots for the AMP STA to send the temporary ID, such as RN16. The AP schedules 4 time slots through the first trigger frame, and 3 AMP STAs send RN16 on time slots 0, 1, and 2 respectively. Through this random access phase, the AP can learn that AMP STAs 1-3 have data transmission needs. Next, the AP can selectively schedule AMP STAs 1-3 for data transmission based on their temporary IDs.

[0140] Referring again to Figure 8, in some implementations, the first device can receive a second trigger frame sent by the second device (see step S830 in Figure 8). This second trigger frame can be used to schedule the first device to perform data transmission on the second resource. Alternatively, the second trigger frame can be used to authorize the first device to perform data transmission on the second resource. Accordingly, the first device can send first data through the second resource (see step S840 in Figure 8).

[0141] Therefore, this embodiment first uses a first trigger frame to understand the status of devices requiring data reporting, and then uses a second trigger frame to perform targeted data scheduling. If the entire process is understood as the access process of the first device (such as an AMP device), then the reporting process of the random access code corresponding to the first trigger frame can be understood as the random access phase of this access process, and the data reporting process corresponding to the second trigger frame can be understood as the authorized access phase of this access process. By dividing the access process into the above two phases, the second device (such as a network device) can first learn about the status of devices that need to report data, and then perform targeted data scheduling, thereby alleviating the resource collision problem in the data reporting process.

[0142] The embodiments of this application do not specifically limit the content of the scheduling information in the second trigger frame, as long as it enables the first device to determine the second resource based on the second trigger frame.

[0143] In some implementations, the second trigger frame may include a first random access code (such as a temporary identifier for the first device). The second trigger frame uses this first random access code to indicate that the first device belongs to the device scheduled by the second trigger frame. Of course, the second trigger frame may also indicate that the first device belongs to the device scheduled by the second trigger frame in other ways. For example, the second trigger frame may also include other access codes or identifiers determined based on the first random access code. The first device may also determine these other access codes or identifiers according to the same rules. Once the first device discovers that the second trigger frame contains these other access codes or identifiers, it can determine that it is a device scheduled by the second trigger frame.

[0144] In some implementations, the second trigger frame includes resource indication information, which indicates a second resource corresponding to the first random access code. In other words, the resource indication information indicates the correspondence between the first random access code and the second resource. Thus, after receiving the second trigger frame, the first device can determine, through this correspondence, which identifies it as the device scheduled by the second trigger frame and the resource allocated to it by the second trigger frame. Taking an AMP device as the first device and the first random access code as the temporary identifier of the first device as an example, the second trigger frame can indicate the second resource corresponding to the temporary identifiers of one or more AMP devices, enabling the one or more AMP devices to transmit data through their respective corresponding second resources.

[0145] When the second trigger frame indicates the correspondence between the first random access code and the second resource, the first device can directly determine the second resource based on this correspondence. Of course, in other implementations, the second trigger frame may not indicate the aforementioned correspondence; in this case, the first device can determine its corresponding second resource using preset rules. These preset rules may be associated with one or more of the following: the number of resources scheduled by the second trigger frame, the first random access code, the number of devices scheduled by the second trigger frame, and the order of the first random access code among the random access codes of one or more devices scheduled by the second trigger frame. For example, the association between the first random access code and the resources in the resource pool scheduled by the second trigger frame may be preset or pre-configured. The first device can determine the second resource based on this preset or pre-configured association. For example, the second trigger frame may indicate the number of resources scheduled and the set of scheduled random access codes. The first device can determine the index of the second resource based on the order (or index) of the first random access code in the set of random access codes. As a more concrete example, assuming the first device is an AMP device and the first random access code is a temporary identifier, the second trigger frame can indicate the number of time-domain resources and the set of scheduled temporary identifiers. The AMP device can determine the number of the time-domain resources, such as the time slot number, based on the order (or index) of the temporary identifiers in the set of temporary identifiers.

[0146] The process of sending the second trigger frame and receiving the first data can be referred to as the authorized access phase in the entire access process. The authorized access phase will be illustrated in more detail below with reference to Figure 10. In the example shown in Figure 10, the first device is an AMP STA in the Wi-Fi system, the second device is an AP in the Wi-Fi system, and the resource scheduled by the AP is a time slot. Before executing the process described in Figure 10, the random access phase shown in Figure 9 can be executed first. After this random access phase, the AP can detect three temporary IDs, namely the temporary IDs of AMP STAs 1-3. Then, the AP can schedule the corresponding resources for the AMP STAs corresponding to these three temporary IDs. For example, the AP can send a second trigger frame (such as an AMP trigger frame). This second trigger frame can carry resource scheduling information and the temporary IDs of AMP STAs 1-3. This second trigger frame can be used to authorize the AMP devices corresponding to the temporary IDs to send data on the corresponding resources. As shown in Figure 10, the AP triggers AMP STAs 1-3 to transmit data on time slots 0-2 respectively through the second trigger frame.

[0147] During communication between the first and second devices, the timing or local clock of the first device needs to be synchronized with that of the second device as much as possible to enable the transmission of random access codes or data on the resources indicated by the second device (i.e., the first device needs to be aligned with the time domain position of the resources indicated by the second device to ensure smooth communication). However, since the first device (such as an AMP device) may have lower complexity and power consumption, it does not have a high-precision local clock. Let's take an AMP device supporting backscatter communication as an example. During backscatter communication, the AMP device determines the start time of backscatter transmission based on its local clock. The AMP device's local clock needs to be synchronized with the network device (corresponding to the second device mentioned above) to ensure time alignment between backscatter and carrier transmission. Currently, the accuracy of the AMP device's local clock can only reach 1000-10000ppm. This causes a large deviation between the timing of the AMP device and the network device, resulting in misalignment between the AMP device's backscatter and the corresponding time slots, affecting the transmission and reception of the backscatter signal.

[0148] To address the aforementioned issues, in some implementations, the second device sends a synchronization frame. The synchronization frame mentioned in the various embodiments of this application can also be referred to as a synchronization signal. This synchronization frame can be, for example, a physical layer frame; therefore, it can be understood as a physical layer protocol data unit (PPDU) or PPDU frame. In the absence of conflict, the synchronization frame and the PPDU used for synchronization can be used interchangeably. This synchronization frame can be used for time synchronization between the first and second devices. Alternatively, the synchronization frame can be used by the first device to determine or identify the temporal location of resources indicated or scheduled by the second device, thereby sending random access codes (such as temporary identifiers) or data through the corresponding resources. The resources indicated or scheduled by the second device may belong to a resource set (or resource pool). In this case, the synchronization frame can be used by the first device to determine or identify the temporal location of resources in the resource set (or resource pool). Taking the first device as an AMP device and the resources indicated or scheduled by the second device as time slots as an example, the AMP device can identify the timing of the time slots based on the synchronization signal, thereby sending the aforementioned first random access code or first data in the corresponding time slot via active transmission or backscattering.

[0149] Assuming the synchronization frame is transmitted based on a third resource, in some implementations, the temporal location of this third resource can be associated with the temporal location of resources in a resource pool (or resource set, which may refer to the resource set formed by resources scheduled by the second device). This association can be determined based on predefined information and / or preconfiguration information. For example, the synchronization frame can be transmitted at the temporal start or end position of a resource in the resource pool. For example, the resource pool may include one or more time slots, and the synchronization frame can be transmitted at the boundary (start or end position) of each time slot, thereby enabling the first device to identify the location of each time slot.

[0150] It should be noted that in some implementations, the scheme for the second device to send synchronization frames can be combined with the transmission schemes of the first and / or second trigger frames. For example, as shown in Figure 9, the AP can send a synchronization frame (synchronization PPDU) at the beginning or end of each time slot. This synchronization PPDU is used by the AMP STA to determine the location of the time slot, thereby using that time slot to send RN16. Similarly, referring to Figure 10, the AP can send a synchronization frame (synchronization PPDU) at the beginning or end of each time slot. This synchronization frame facilitates the AMP device in identifying the timing of the time slot, thereby sending data in the corresponding time slot via active transmission or backscattering. However, in other implementations, the scheme for the second device to send synchronization frames can also be implemented independently of the transmission schemes of the first and / or second trigger frames. For example, the second device can directly schedule the first device to transmit data using a trigger frame. Based on this scheme, the second device can further transmit synchronization frames, enabling the first device to synchronize with the second device, thereby transmitting data at the resource location scheduled by the trigger frame.

[0151] This application does not specifically limit the format of the synchronization frame. As mentioned above, the synchronization frame can be a PPDU. The PPDU may include one or more of the following: preamble, synchronization field, signal field, and data field. Several possible implementations of the synchronization frame are given below with specific examples.

[0152] PPDU format 1

[0153] In PPDU format 1, the PPDU may include a preamble, a synchronization domain, a signal domain, and a data domain.

[0154] The preamble in this PPDU can also be called a physical preamble. The preamble can be used to coexist with legacy devices (devices that support traditional channel access protocols). Therefore, this preamble can also be called a legacy preamble. As shown in Figure 12, this preamble can include a short training field (STF) and a long training field (LTF). The presence of these fields allows legacy devices to detect the existence of this synchronization PPDU through carrier detection during clear channel assessment (CCA), thereby determining that the channel is not idle and taking avoidance measures. Furthermore, in some implementations, as shown in Figure 12, this preamble can also include a compatible physical header. This compatible physical header can be used to carry information such as the modulation and coding scheme used for the data portion of the PPDU, and the number of bytes in the data portion.

[0155] The synchronization domain can be used for synchronization between the first device and the second device. For example, the first device can determine the timing of the PPDU based on the synchronization domain, and then determine the time-domain position of the resources in the resource pool (also called a resource set, where the resources scheduled or indicated by the second device can be resources in the resource pool) according to the timing relationship between the timing of the PPDU and the time-domain position of the resources in the resource pool, thereby enabling the transmission of random access codes and / or data on the corresponding resources. Taking the first device as an AMP device and the resources in the resource pool as time slots as an example, the timing of the PPDU can be determined through the synchronization domain, and the timing of the time slot can be determined according to the relationship between the timing of the PPDU and the timing of the time slot, thus enabling the transmission of random access codes and / or data in the corresponding time slot.

[0156] The synchronization domain can carry synchronization sequences. The modulation scheme used for the sequence or signal in the synchronization domain can be a modulation scheme supported by the first device. Taking the first device as an AMP device as an example, this synchronization domain can be called the AMP synchronization domain (AMP Sync domain). The modulation scheme used for the sequence or signal in this synchronization domain can be a simple modulation scheme such as ASK, OOK, FSK or PSK modulation, which facilitates low-complexity and low-power demodulation by the AMP device.

[0157] The signal field (SIG field) can be used to carry physical layer control information (or transmission parameters). For example, the signal field can indicate one or more of the following: the modulation and coding scheme, length, number of bytes, etc., used for signals in the data field. Based on the signal field, the first device can correctly receive signals or information in the data field. Taking the first device as an AMP device as an example, this signal field can be called the AMP SIG field.

[0158] The data field can be used to carry MAC layer information. Taking the resources scheduled by the second device as time slots as an example, the information carried in the data field can be used to carry time slot-related information. For example, this time slot-related information can be used to indicate or determine the time slot number. Taking the first device as an AMP device as an example, the AMP device can determine the timing of the time slot through the synchronization field. Furthermore, it can obtain the time slot number information through the data field, thereby determining which time slot in the resource pool scheduled by the second device the current time slot belongs to, and thus determining whether the time slot is the target time slot of the AMP device (the time slot used to transmit random access codes and / or data).

[0159] Taking the first device as an AMP device as an example, Figure 11 shows one possible definition of PPDU format 1. As can be seen from Figure 11, PPDU format 1 includes a traditional preamble, an AMP synchronization domain, an AMP signal domain, and an AMP data domain. Descriptions of these domains can be found above and will not be repeated here.

[0160] It should be noted that the data field in PPDU format 1 is optional. If PPDU format 1 does not include a data field, a first indication information can be carried in the signal field to indicate that the length of the data field is 0 (thus indicating that the PPDU does not contain a data field).

[0161] PPDU format 2

[0162] In PPDU format 2, the PPDU used for synchronization may include a preamble, a synchronization domain, and a signal domain.

[0163] The preamble in this PPDU can also be called a physical preamble. The preamble can be used to coexist with legacy equipment (equipment that supports traditional channel access protocols). Therefore, this preamble can also be called a legacy preamble. As shown in Figure 12, this preamble may include STF and LTF. The presence of these fields allows legacy equipment to detect the existence of this synchronization PPDU through carrier detection during CCA, thereby determining that the channel is not idle and thus avoiding it. Furthermore, in some implementations, as shown in Figure 12, this preamble may also include a compatible physical header. This compatible physical header can be used to carry information such as the modulation and coding scheme used for the data portion of the PPDU, the number of bytes in the data portion, etc.

[0164] The synchronization domain can be used for synchronization between the first device and the second device. For example, the first device can determine the timing of the PPDU based on the synchronization domain, and then determine the time-domain position of the resources in the resource pool (also called a resource set, where the resources scheduled or indicated by the second device can be resources in the resource pool) according to the timing relationship between the timing of the PPDU and the time-domain position of the resources in the resource pool, thereby enabling the transmission of random access codes and / or data on the corresponding resources. Taking the first device as an AMP device and the resources in the resource pool as time slots as an example, the timing of the PPDU can be determined through the synchronization domain, and the timing of the time slot can be determined according to the relationship between the timing of the PPDU and the timing of the time slot, thus enabling the transmission of random access codes and / or data in the corresponding time slot.

[0165] The synchronization domain can carry synchronization sequences. The modulation scheme used for the sequence or signal in the synchronization domain can be a modulation scheme supported by the first device. Taking the first device as an AMP device as an example, this synchronization domain can be called the AMP synchronization domain (AMP Sync domain). The modulation scheme used for the sequence or signal in this synchronization domain can be a simple modulation scheme such as ASK, OOK, FSK or PSK modulation, which facilitates low-complexity and low-power demodulation by the AMP device.

[0166] The signaling domain can contain control information for synchronization. Taking the resources scheduled by the second device as time slots as an example, the information carried in the signaling domain can be used to carry time slot-related information. For example, this time slot-related information can be used to indicate or determine the time slot number. Taking the first device as an AMP device as an example, the AMP device can determine the timing of the time slot through the synchronization domain. Furthermore, it can obtain the time slot number information through the signaling domain, thereby determining which time slot in the resource pool scheduled by the second device the current time slot belongs to, and thus determining whether the time slot is the target time slot of the AMP device (the time slot used to transmit random access codes and / or data).

[0167] Taking the first device as an AMP device as an example, Figure 13 shows one possible definition of PPDU format 2. As can be seen from Figure 13, PPDU format 2 includes a traditional preamble, an AMP synchronization domain, and an AMP signal domain. Descriptions of these domains can be found above and will not be repeated here.

[0168] 802.11ah proposes a null data packet carrying medium access control information (NPD CMAC PPDU). This NDP CMAC PPDU only includes the STF, LTF, and SIG fields, without a data field, as shown in Figure 14. The SIG field in this PPDU includes control information as shown in Figure 15. The NDP CMAC PPDU body includes NDP CMAC PPDU type information and related control information. For example, if the NDP CMAC PPDU type information indicates that the NDP is clear to send (CTS), then the control information carried by the NDP is CTS information, and the NDP frame is an NDP CTS frame. Since the PPDU format 2 provided in this embodiment also does not contain a data field, this PPDU frame can be understood as an NDP frame.

[0169] PPDU format 3

[0170] In PPDU format 3, the PPDU includes a preamble and a synchronization field.

[0171] The preamble in this PPDU can also be called a physical preamble. The preamble can be used to coexist with legacy devices (devices that support traditional channel access protocols). Therefore, this preamble can also be called a legacy preamble. As shown in Figure 12, this preamble can include a short training field (STF) and a long training field (LTF). The presence of these fields allows legacy devices to detect the existence of this synchronization PPDU through carrier detection during clear channel assessment (CCA), thereby determining that the channel is not idle and taking avoidance measures. Furthermore, in some implementations, as shown in Figure 12, this preamble can also include a compatible physical header. This compatible physical header can be used to carry information such as the modulation and coding scheme used for the data portion of the PPDU, and the number of bytes in the data portion.

[0172] The synchronization domain can be used for synchronization between the first device and the second device. For example, the first device can determine the timing of the PPDU based on the synchronization domain, and then determine the time-domain position of the resources in the resource pool (also called a resource set, where the resources scheduled or indicated by the second device can be resources in the resource pool) according to the timing relationship between the timing of the PPDU and the time-domain position of the resources in the resource pool, thereby enabling the transmission of random access codes and / or data on the corresponding resources. Taking the first device as an AMP device and the resources in the resource pool as time slots as an example, the timing of the PPDU can be determined through the synchronization domain, and the timing of the time slot can be determined according to the relationship between the timing of the PPDU and the timing of the time slot, thus enabling the transmission of random access codes and / or data in the corresponding time slot.

[0173] The synchronization domain can carry synchronization sequences. The modulation scheme used for the sequence or signal in the synchronization domain can be a modulation scheme supported by the first device. Taking the first device as an AMP device as an example, this synchronization domain can be called the AMP synchronization domain (AMP Sync domain). The modulation scheme used for the sequence or signal in this synchronization domain can be a simple modulation scheme such as ASK, OOK, FSK or PSK modulation, which facilitates low-complexity and low-power demodulation by the AMP device.

[0174] Taking the first device as an AMP device as an example, Figure 16 shows one possible definition of PPDU format 3. As can be seen from Figure 16, PPDU format 3 includes a traditional preamble and an AMP synchronization field. Descriptions of these fields can be found above and will not be repeated here.

[0175] The first and second trigger frames mentioned above can be transmitted within the same transmission opportunity (TXOP). For example, the transmission of the first trigger frame and the first random access code can belong to the random access phase of the entire access procedure, and the transmission of the second trigger frame and the first data can belong to the authorized access phase of the entire access procedure. Since the random access phase and the authorized access phase can be completed within the same TXOP, the first and second trigger frames will also be transmitted within the same TXOP, as shown in Figure 17.

[0176] Alternatively, the first and second trigger frames mentioned above can be transmitted in different TXOPs. For example, the transmission process of the first trigger frame and the first random access code can correspond to the random access phase of the entire access procedure, and the transmission process of the second trigger frame and the first data can correspond to the authorized access phase of the entire access procedure. The random access phase and the authorized access phase can be completed in different TXOPs, and correspondingly, the first and second trigger frames will also be transmitted in different TXOPs.

[0177] In some implementations, since the first trigger frame is used to trigger the random access phase of the entire access process, and the second trigger frame is used to trigger the authorized access phase of the entire access process, the first and second trigger frames can have a certain correlation. For example, the time-domain positions of the first and second trigger frames are correlated. Exemplarily, the first and second trigger frames are two trigger frames received within a first time range. Furthermore, the first and / or second trigger frames carry information that indicates their correlation. For example, the identification information carried in the first and second trigger frames is correlated. As an example, the first and second trigger frames carry the same identification information. As another example, the first and second trigger frames carry related identification information. The identification information mentioned here can be used to identify the access process. For example, the identification information may include one or more of a session ID, access ID, and round ID.

[0178] The resource pool mentioned in the preceding embodiments can refer to the set of resources scheduled by the second device. Taking the resources in the resource pool as time slots as an example, the resource pool mentioned in the preceding embodiments can refer to one or more time slots scheduled by the second device.

[0179] As mentioned earlier, the first device can be an AMP device. This AMP device can be a device that operates based on ambient energy. The ambient energy mentioned here can include one or more of the following: radio frequency energy, solar energy, thermal energy, mechanical energy, etc.

[0180] As mentioned earlier, the second device can be a network device. This network device can be a device that communicates with the AMP device, or it can be a device that provides wireless signal functionality to the AMP device.

[0181] The embodiments of this application are described in more detail below using communication between an AMP device (such as an AMP STA) and a network device (AP) as an example. It should be noted that the examples below are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments of this application to the specific numerical values ​​or specific scenarios illustrated. Those skilled in the art will obviously be able to make various equivalent modifications or variations based on the examples given below, and such modifications or variations also fall within the scope of the embodiments of this application.

[0182] Depending on the application scenarios of AIoT, such as logistics and warehousing, a large number of goods need to be transferred, stored, loaded, unloaded, and inventoried at logistics stations or warehouses. With the occurrence of warehouse ordering, goods receiving, goods management, and goods issuing, AMP STAs need to communicate centrally with APs, such as reporting the goods information and location information stored by the AMP STAs. Furthermore, the AP cannot know in advance the number of AMP STAs that need to report information.

[0183] To achieve efficient AMP STA information reporting, the AP can schedule multiple resources at once for uplink data transmission by multiple AMP STAs using a multi-user multiplexing approach. For example, the AP can schedule a set of TDM resources, and multiple AMP STAs can use these resources to send uplink data in a TDM manner. In this transmission method, it is necessary to address how to prevent resource collisions caused by multiple AMP STAs selecting the same resources.

[0184] This example proposes a random access method. This random access method is applicable to AP triggering multiple AMP STAs to transmit data. Through this random access method, AMP STAs can select appropriate resources to report temporary IDs based on AP triggering, and then transmit data according to AP scheduling. The access process includes the following random access phase and authorized access phase, which are described in detail below.

[0185] Random Access Phase

[0186] The random access phase can be used to schedule certain resources, allowing AMP STAs to send their first message based on those resources. This first message can carry or indicate the AMP STA's temporary ID. Reporting the temporary ID serves two purposes: first, it allows the AP to identify AMP STAs that need to report information; second, it resolves resource collision issues during data transmission.

[0187] Taking the AP scheduling TDM resources for AMP STAs to send temporary IDs as an example, the AP allocates a certain number of time units, such as time slots, through a trigger frame (corresponding to the first trigger frame mentioned above). AMP STAs can then select the appropriate time units to send temporary IDs according to certain rules.

[0188] A temporary ID can be a random number generated by the AMP STA to identify it. This random number can be generated by the AMP STA's RNG, such as RN16 in the RFID standard. Alternatively, a temporary ID can be a replacement ID obtained by the AMP STA through certain operations based on its own ID. For example, the AMP STA can truncate or extract its own ID to form a temporary ID. Or, a temporary ID can be a randomly selected ID from a set of temporary IDs.

[0189] After the AMP STA sends a temporary ID, the AP can detect the random number sent by the AMP STA in the corresponding time slot. When a random number is detected, the AP can record it for scheduling the AMP STA during the authorized access phase. During the random access phase, inevitably, AMP STAs will choose the same time slot to send random numbers, resulting in resource collisions. In this case, the AP may fail to identify any of the random numbers, or it may successfully demodulate one of them.

[0190] The AMP STA mentioned in this example can be an AMP STA that supports backscatter communication. During backscatter communication, the AMP STA can determine the start time of backscatter signal transmission based on its local clock. The AMP STA's local clock needs to be synchronized with the AP's timing to ensure time alignment between backscatter and carrier transmission. AMP STAs have extremely low complexity and power consumption, which often results in them not having high-precision local clocks. Generally, the accuracy of an AMP STA's local clock is only 1000-10000ppm. This can cause a significant deviation between the AMP STA's timing and the AP's timing, resulting in misalignment between the AMP STA's backscatter and the corresponding time slots, affecting the transmission and reception of backscatter signals. Therefore, at the boundaries of time slots, the AP can send a synchronization signal. The AMP STA can use this synchronization signal to identify the timing of the time slot and then send a temporary ID via backscatter in the corresponding time slot.

[0191] The synchronization signal can be a PPDU, called a synchronization PPDU. The synchronization PPDU can use the following PPDU formats.

[0192] Format 1: Traditional preamble + AMP synchronization domain + AMP signal domain + AMP data domain

[0193] Referring to Figure 11, Format 1 includes a traditional preamble, an AMP synchronization field, an AMP signal field, and an AMP data field. Specifically, to achieve coexistence with legacy devices, the PPDU needs to include a physical preamble compatible with legacy channel access protocols, called a traditional preamble. The traditional preamble can include STF and LTF. The presence of these fields allows legacy devices to detect the existence of the PPDU through carrier detection during CCA, thereby determining that the channel is not idle and circumventing it. Furthermore, the traditional preamble can also include a compatible physical header, such as a signal field. This signal field can be used to carry information such as the modulation and coding scheme used for the data portion of the PPDU, and the number of bytes in the data portion. A format of a traditional preamble is shown in Figure 12.

[0194] The AMP synchronization domain is used for AMP devices to detect PPDUs and synchronize. The AMP synchronization domain uses modulation methods supported by AMP devices, such as ASK, OOK, FSK, PSK and other simple modulation methods, which facilitates low-complexity and low-power demodulation by AMP devices.

[0195] The AMP signal field carries physical layer control information, including the modulation and coding scheme, length, and number of bytes used in the AMP data field. Through the AMP signal field, the AMP STA can correctly receive information from the AMP data field.

[0196] The AMP data field can be used to carry information from the MAC layer.

[0197] When the AMP STA uses a PPDU of this format for synchronization, the start position of the time slot can be obtained by demodulating the AMP portion of the PPDU. First, the AMP STA can achieve synchronization through the AMP synchronization field. For example, the AMP STA can determine the timing of the PPDU and, based on the relationship between the PPDU timing and the time slot timing, determine the timing of the time slot. Furthermore, it should be noted that the AMP data field in PPDU format 1 can be an optional field. For example, if the PPDU does not contain an AMP data field, the information carried in the AMP signal field can indicate that the length of the AMP data field is 0, thus indicating that the PPDU does not contain an AMP data field. Of course, if an AMP data field exists, it can carry time slot related information. Therefore, based on determining the time slot timing through the AMP synchronization field, the time slot number information can be further obtained through the AMP data field, thereby determining which time slot in the AP-scheduled time slot set the current time slot belongs to, and thus determining whether this time slot is the target time slot of the AMP device.

[0198] Format 2: Traditional preamble + AMP synchronization domain + AMP signal domain

[0199] As shown in Figure 13, the synchronous PPDU includes a traditional preamble, an AMP synchronization domain, and an AMP signal domain.

[0200] The NDP CMAC PPDU in 802.11ah only includes the STF, LTF, and SIG fields, without a data field, as shown in Figure 14. The SIG field includes the control information shown in Figure 15. Referring to Figure 15, the body of the NDP CMAC PPDU includes NDP CMAC PPDU type information and related control information. For example, if the NDP CMAC PPDU type information indicates that the NDP is a CTS, then the control information carried by the NDP is CTS information, and the NDP frame is an NDP CTS frame.

[0201] The synchronization PPDU format provided in this example also lacks a data field. Therefore, the PPDU shown in format 2 can be considered a type of AMP NDP. The AMP signal field can carry synchronization-related control information, such as slot number information. Based on this slot number information, it can be determined which slot in the network device's time slot set the current time slot belongs to, thus determining whether this time slot is the target time slot for the AMP device.

[0202] Format 3: Traditional Preamble + AMP Synchronization Domain

[0203] As mentioned earlier, AMP STA can achieve synchronization through the AMP synchronization domain. For example, AMP STA can determine the timing of PPDU and, based on the relationship between the timing of PPDU and the timing of time slots, determine the timing of time slots. Therefore, the synchronizing PPDU can contain only a traditional preamble and the AMP synchronization domain, as shown in Figure 16.

[0204] The random access phase is shown in Figure 9. The AP sends a first trigger frame to schedule several time slots for AMP STAs to send temporary IDs, such as RN16. In the example in Figure 9, the AP schedules 4 time slots, and 3 AMP STAs send RN16 on time slots 0, 1, and 2 respectively. At the beginning or end of each time slot, the AP sends a synchronization PPDU to help the AMP STAs determine the location of the time slot and use that time slot to send RN16.

[0205] Authorized access phase

[0206] During the random access phase, the AP detects several temporary IDs. Based on these temporary IDs, the AP can identify the AMP STAs that require data reporting. The AP can then allocate resources to enable these AMP STAs to use those resources for data reporting.

[0207] For example, the AP can send a second trigger frame carrying resource scheduling information and the temporary ID of the AMP STA. The second trigger frame can be used to authorize the AMP device corresponding to the temporary ID to transmit data on the appropriate resource. As shown in Figure 10, the AP triggers AMP STAs 1-3 to transmit data on time slots 0-2 respectively via the second trigger frame. Similarly, network devices can use synchronization PPDUs to indicate synchronization information, making it easier for AMP STAs to identify the timing of time slots and thus transmit data via backscatter in the corresponding time slots.

[0208] The AMP STA can determine the target resource based on the resource scheduling information carried in the second trigger frame. At this time, the second trigger frame can indicate the resource corresponding to each temporary ID.

[0209] Alternatively, AMP STA can determine the target resource using preset rules. For example, the association between a temporary ID and a resource in the resource pool scheduled by the second trigger frame may be preset or pre-configured. For instance, the second trigger frame indicates the number of time-domain resources and the set of scheduled temporary IDs; AMP STA determines the time-domain resource number, such as the time slot number, based on the order of the temporary IDs in the set (e.g., index).

[0210] The random access phase and authorized access phase mentioned above can be completed by the AP within one TXOP, or they can be completed separately in different TXOPs. Figure 17 shows how the AP completes the random access phase and authorized access phase within one TXOP.

[0211] The random access phase and the authorized access phase are related; that is, they belong to two phases of the same access procedure. This relationship can be determined implicitly, for example, through the temporal relationship between the first and second trigger frames. For instance, first and second trigger frames received within a certain time range are related. Alternatively, this relationship can be determined explicitly, for example, by having the first and second trigger frames carry the same or related IDs, such as session IDs, access IDs, round IDs, etc. This ID can be used to identify an access procedure.

[0212] This example provides a random access method that, through a two-stage access process, avoids resource collisions when AMP STAs transmit data and prevents resource waste caused by mismatches between resource scheduling and the data transmission needs of AMP STAs. A synchronization signal enables AMP STAs based on backscatter communication to identify the location of time-domain resources, thereby allowing them to transmit random access signals or data through those resources.

[0213] The method embodiments of this application have been described in detail above with reference to Figures 1 to 17. The apparatus embodiments of this application will be described in detail below with reference to Figures 18 to 20. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0214] Figure 18 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 1800 shown in Figure 18 can be the first device mentioned above. The communication device 1800 includes a communication module 1810. The communication module 1810 is used to receive a first trigger frame sent by a second device, the first trigger frame being used to indicate a first resource; and to send a first random access code to the second device through the first resource.

[0215] In some implementations, the communication module 1810 is further configured to: receive a second trigger frame sent by the second device, the second trigger frame being used to schedule the first device to perform data transmission on the second resource; and send first data through the second resource.

[0216] In some implementations, the second trigger frame includes the first random access code.

[0217] In some implementations, the second trigger frame further includes resource indication information, which is used to indicate the second resource that corresponds to the first random access code.

[0218] In some implementations, the second resource is determined based on preset rules.

[0219] In some implementations, the preset rule is associated with one or more of the following: the number of resources scheduled by the second trigger frame; the first random access code; the number of devices scheduled by the second trigger frame; and the order of the first random access code among the random access codes of one or more devices scheduled by the second trigger frame.

[0220] In some implementations, the first trigger frame and the second trigger frame are transmitted in the same TXOP; or, the first trigger frame and the second trigger frame are transmitted in different TXOPs.

[0221] In some implementations, the temporal positions of the first trigger frame and the second trigger frame are associated; and / or, the identification information carried in the first trigger frame and the second trigger frame is associated.

[0222] In some implementations, the communication module 1810 is further configured to: receive a synchronization frame sent by the second device, the synchronization frame being used for time synchronization between the first device and the second device.

[0223] In some implementations, the synchronization frame is used to determine the temporal location of resources in the resource pool.

[0224] In some implementations, the synchronization frame is transmitted based on a third resource, the temporal location of which is associated with the temporal location of resources in the resource pool, and the association is determined based on predefined information and / or preconfiguration information.

[0225] In some implementations, the temporal location of the third resource is located at the temporal start or end position of the resources in the resource pool.

[0226] In some implementations, the synchronization frame includes one or more of the following: a preamble, a synchronization domain, a signal domain, and a data domain.

[0227] In some implementations, the synchronization frame includes a preamble, a synchronization domain, a signal domain, and a data domain.

[0228] In some implementations, the data field contains time slot-related information.

[0229] In some implementations, the signal field includes first indication information, which indicates that the length of the data field is 0.

[0230] In some implementations, the synchronization frame includes a preamble, a synchronization domain, and a signal domain.

[0231] In some implementations, the signal domain contains control information for synchronization.

[0232] In some implementations, the signal domain includes time-slot related information.

[0233] In some implementations, the synchronization frame is characterized as an NDP frame.

[0234] In some implementations, the synchronization frame includes a preamble and a synchronization field.

[0235] In some implementations, the first random access code includes a random number and / or a first identifier of the first device.

[0236] In some implementations, the first identifier is a temporary identifier for the first device.

[0237] In some implementations, the first identifier is an identifier determined based on a second identifier of the first device, or an identifier from the temporary identifier set of the first device.

[0238] In some implementations, the first device is an AMP device; and / or, the second device is a network device.

[0239] Figure 19 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 1900 shown in Figure 19 can be the second device mentioned above. The communication device 1900 includes a communication module 1910. The communication module 1910 is used to send a first trigger frame to a first device, the first trigger frame being used to indicate a first resource; and to receive a first random access code sent by the first device through the first resource.

[0240] In some implementations, the communication module 1910 is further configured to: send a second trigger frame to the first device, the second trigger frame being used to schedule the first device to perform data transmission on a second resource; and receive first data sent by the first device through the second resource.

[0241] In some implementations, the second trigger frame includes the first random access code.

[0242] In some implementations, the second trigger frame further includes resource indication information, which is used to indicate the second resource that corresponds to the first random access code.

[0243] In some implementations, the second resource is determined based on preset rules.

[0244] In some implementations, the preset rule is associated with one or more of the following: the number of resources scheduled by the second trigger frame; the first random access code; the number of devices scheduled by the second trigger frame; and the order of the first random access code among the random access codes of one or more devices scheduled by the second trigger frame.

[0245] In some implementations, the first trigger frame and the second trigger frame are transmitted in the same TXOP; or, the first trigger frame and the second trigger frame are transmitted in different TXOPs.

[0246] In some implementations, the temporal positions of the first trigger frame and the second trigger frame are associated; and / or, the identification information carried in the first trigger frame and the second trigger frame is associated.

[0247] In some implementations, the communication module 1910 is further configured to: send a synchronization frame to the first device, the synchronization frame being used for time synchronization between the first device and the second device.

[0248] In some implementations, the synchronization frame is used to determine the temporal location of resources in the resource pool.

[0249] In some implementations, the synchronization frame is transmitted based on a third resource, the temporal location of which is associated with the temporal location of resources in the resource pool, and the association is determined based on predefined information and / or preconfiguration information.

[0250] In some implementations, the temporal location of the third resource is located at the temporal start or end position of the resources in the resource pool.

[0251] In some implementations, the synchronization frame includes one or more of the following: a preamble, a synchronization domain, a signal domain, and a data domain.

[0252] In some implementations, the synchronization frame includes a preamble, a synchronization domain, a signal domain, and a data domain.

[0253] In some implementations, the data field contains time slot-related information.

[0254] In some implementations, the signal field includes first indication information, which indicates that the length of the data field is 0.

[0255] In some implementations, the synchronization frame includes a preamble, a synchronization domain, and a signal domain.

[0256] In some implementations, the signal domain contains control information for synchronization.

[0257] In some implementations, the signal domain includes time-slot related information.

[0258] In some implementations, the synchronization frame is an NDP frame.

[0259] In some implementations, the synchronization frame includes a preamble and a synchronization field.

[0260] In some implementations, the first random access code includes a random number and / or a first identifier of the first device.

[0261] In some implementations, the first identifier is a temporary identifier for the first device.

[0262] In some implementations, the first identifier is an identifier determined based on a second identifier of the first device, or an identifier from the temporary identifier set of the first device.

[0263] In some implementations, the first device is an AMP device; and / or, the second device is a network device.

[0264] Figure 20 is a schematic structural diagram of a communication device applicable to embodiments of this application. The dashed lines in Figure 20 indicate that the unit or module is optional. The device 2000 can be used to implement the methods described in the above method embodiments. The device 2000 can be a chip, a station, or an access point.

[0265] Apparatus 2000 may include one or more processors 2010. The processor 2010 may support apparatus 2000 in implementing the methods described in the preceding method embodiments. The processor 2010 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0266] The apparatus 2000 may also include one or more memories 2020. The memories 2020 store a program that can be executed by the processor 2010, causing the processor 2010 to perform the methods described in the preceding method embodiments. The memories 2020 may be independent of the processor 2010 or integrated into the processor 2010.

[0267] The device 2000 may also include a transceiver 2030. The processor 2010 can communicate with other devices or chips through the transceiver 2030. For example, the processor 2010 can send and receive data with other devices or chips through the transceiver 2030.

[0268] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0269] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0270] This application also provides a computer program. This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.

[0271] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0272] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0273] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0274] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0275] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0276] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0277] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0278] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0279] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0280] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0281] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0282] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0283] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: The first device receives a first trigger frame sent by the second device, the first trigger frame being used to indicate a first resource; The first device sends a first random access code to the second device through the first resource.

2. The method according to claim 1, characterized in that, The method further includes: The first device receives a second trigger frame sent by the second device, the second trigger frame being used to schedule the first device to perform data transmission on the second resource; The first device sends the first data through the second resource.

3. The method according to claim 2, characterized in that, The second trigger frame contains the first random access code.

4. The method according to claim 2 or 3, characterized in that, The second trigger frame also includes resource indication information, which is used to indicate the second resource that corresponds to the first random access code.

5. The method according to claim 2 or 3, characterized in that, The second resource is determined based on preset rules.

6. The method according to claim 5, characterized in that, The preset rule is associated with one or more of the following: The number of resources scheduled by the second trigger frame; The first random access code; The number of devices scheduled by the second trigger frame; The order of the first random access code in the random access codes of one or more devices scheduled by the second trigger frame.

7. The method according to any one of claims 2 to 6, characterized in that: The first trigger frame and the second trigger frame are transmitted in the same transmission opportunity (TXOP); or, The first trigger frame and the second trigger frame are transmitted in different TXOPs.

8. The method according to any one of claims 2 to 7, characterized in that, The temporal positions of the first trigger frame and the second trigger frame are related; and / or, the identification information carried in the first trigger frame and the second trigger frame is related.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: The first device receives a synchronization frame sent by the second device, the synchronization frame being used for time synchronization between the first device and the second device.

10. The method according to claim 9, characterized in that, The synchronization frame is used to determine the temporal location of resources in the resource pool.

11. The method according to claim 9 or 10, characterized in that, The synchronization frame is transmitted based on a third resource, the temporal location of which is associated with the temporal location of resources in the resource pool, and the association is determined based on predefined information and / or preconfiguration information.

12. The method according to claim 11, characterized in that, The temporal location of the third resource is located at the temporal start or end position of the resources in the resource pool.

13. The method according to any one of claims 9 to 12, characterized in that, The synchronization frame includes one or more of the following: preamble, synchronization domain, signal domain, and data domain.

14. The method according to claim 13, characterized in that, The synchronization frame includes a preamble, a synchronization domain, a signal domain, and a data domain.

15. The method according to claim 14, characterized in that, The data field contains time slot related information.

16. The method according to claim 14 or 15, characterized in that, The signal field includes first indication information, which indicates that the length of the data field is 0.

17. The method according to claim 13, characterized in that, The synchronization frame includes a preamble, a synchronization domain, and a signal domain.

18. The method according to claim 17, characterized in that, The signal domain contains control information for synchronization.

19. The method according to claim 17 or 18, characterized in that, The signal domain contains time slot related information.

20. The method according to any one of claims 17 to 19, characterized in that, The synchronization frame is an empty data packet NDP frame.

21. The method according to claim 13, characterized in that, The synchronization frame includes a preamble and a synchronization field.

22. The method according to any one of claims 1 to 21, characterized in that, The first random access code includes a random number and / or the first identifier of the first device.

23. The method according to claim 22, characterized in that, The first identifier is a temporary identifier for the first device.

24. The method according to claim 22 or 23, characterized in that, The first identifier is an identifier determined based on the second identifier of the first device, or an identifier in the temporary identifier set of the first device.

25. The method according to any one of claims 1 to 24, characterized in that, The first device is an ambient power supply (AMP) device; and / or, the second device is a network device.

26. A communication method, characterized in that, include: The second device sends a first trigger frame to the first device, the first trigger frame being used to indicate a first resource; The second device receives the first random access code sent by the first device through the first resource.

27. The method according to claim 26, characterized in that, The method further includes: The second device sends a second trigger frame to the first device, the second trigger frame being used to schedule the first device to perform data transmission on the second resource; The second device receives the first data sent by the first device through the second resource.

28. The method according to claim 27, characterized in that, The second trigger frame contains the first random access code.

29. The method according to claim 27 or 28, characterized in that, The second trigger frame also includes resource indication information, which is used to indicate the second resource that corresponds to the first random access code.

30. The method according to claim 27 or 28, characterized in that, The second resource is determined based on preset rules.

31. The method according to claim 30, characterized in that, The preset rule is associated with one or more of the following: The number of resources scheduled by the second trigger frame; The first random access code; The number of devices scheduled by the second trigger frame; The order of the first random access code in the random access codes of one or more devices scheduled by the second trigger frame.

32. The method according to any one of claims 27 to 31, characterized in that: The first trigger frame and the second trigger frame are transmitted in the same transmission opportunity (TXOP); or, The first trigger frame and the second trigger frame are transmitted in different TXOPs.

33. The method according to any one of claims 27 to 32, characterized in that, The temporal positions of the first trigger frame and the second trigger frame are related; and / or, the identification information carried in the first trigger frame and the second trigger frame is related.

34. The method according to any one of claims 26 to 33, characterized in that, The method further includes: The second device sends a synchronization frame to the first device, the synchronization frame being used for time synchronization between the first device and the second device.

35. The method according to claim 34, characterized in that, The synchronization frame is used to determine the temporal location of resources in the resource pool.

36. The method according to claim 34 or 35, characterized in that, The synchronization frame is transmitted based on a third resource, the temporal location of which is associated with the temporal location of resources in the resource pool, and the association is determined based on predefined information and / or preconfiguration information.

37. The method according to claim 36, characterized in that, The temporal location of the third resource is located at the temporal start or end position of the resources in the resource pool.

38. The method according to any one of claims 34 to 37, characterized in that, The synchronization frame includes one or more of the following: preamble, synchronization domain, signal domain, and data domain.

39. The method according to claim 38, characterized in that, The synchronization frame includes a preamble, a synchronization domain, a signal domain, and a data domain.

40. The method according to claim 39, characterized in that, The data field contains time slot related information.

41. The method according to claim 39 or 40, characterized in that, The signal field includes first indication information, which indicates that the length of the data field is 0.

42. The method according to claim 38, characterized in that, The synchronization frame includes a preamble, a synchronization domain, and a signal domain.

43. The method according to claim 42, characterized in that, The signal domain contains control information for synchronization.

44. The method according to claim 42 or 43, characterized in that, The signal domain contains time slot related information.

45. The method according to any one of claims 42 to 44, characterized in that, The synchronization frame is an empty data packet NDP frame.

46. ​​The method according to claim 38, characterized in that, The synchronization frame includes a preamble and a synchronization field.

47. The method according to any one of claims 26 to 46, characterized in that, The first random access code includes a random number and / or the first identifier of the first device.

48. The method according to claim 47, characterized in that, The first identifier is a temporary identifier for the first device.

49. The method according to claim 47 or 48, characterized in that, The first identifier is an identifier determined based on the second identifier of the first device, or an identifier in the temporary identifier set of the first device.

50. The method according to any one of claims 26 to 49, characterized in that, The first device is an ambient power supply (AMP) device; and / or, the second device is a network device.

51. A communication device, characterized in that, The communication device is a first device, and the first device includes: The communication module is configured to receive a first trigger frame sent by the second device, the first trigger frame being used to indicate a first resource; and to send a first random access code to the second device through the first resource.

52. The communication device according to claim 51, characterized in that, The communication module is also used for: The first device receives a second trigger frame sent by the second device, the second trigger frame being used to schedule the first device to perform data transmission on the second resource; and sends first data through the second resource.

53. The communication device according to claim 52, characterized in that, The second trigger frame contains the first random access code.

54. The communication device according to claim 52 or 53, characterized in that, The second trigger frame also includes resource indication information, which is used to indicate the second resource that corresponds to the first random access code.

55. The communication device according to claim 52 or 53, characterized in that, The second resource is determined based on preset rules.

56. The communication device according to claim 55, characterized in that, The preset rule is associated with one or more of the following: The number of resources scheduled by the second trigger frame; The first random access code; The number of devices scheduled by the second trigger frame; The order of the first random access code in the random access codes of one or more devices scheduled by the second trigger frame.

57. The communication device according to any one of claims 52 to 56, characterized in that: The first trigger frame and the second trigger frame are transmitted in the same transmission opportunity (TXOP); or, The first trigger frame and the second trigger frame are transmitted in different TXOPs.

58. The communication device according to any one of claims 52 to 57, characterized in that, The temporal positions of the first trigger frame and the second trigger frame are related; and / or, the identification information carried in the first trigger frame and the second trigger frame is related.

59. The communication device according to any one of claims 51 to 58, characterized in that, The communication module is further configured to: receive a synchronization frame sent by the second device, the synchronization frame being used for time synchronization between the first device and the second device.

60. The communication device according to claim 59, characterized in that, The synchronization frame is used to determine the temporal location of resources in the resource pool.

61. The communication device according to claim 59 or 60, characterized in that, The synchronization frame is transmitted based on a third resource, the temporal location of which is associated with the temporal location of resources in the resource pool, and the association is determined based on predefined information and / or preconfiguration information.

62. The communication device according to claim 61, characterized in that, The temporal location of the third resource is located at the temporal start or end position of the resources in the resource pool.

63. The communication device according to any one of claims 59 to 62, characterized in that, The synchronization frame includes one or more of the following: preamble, synchronization domain, signal domain, and data domain.

64. The communication device according to claim 63, characterized in that, The synchronization frame includes a preamble, a synchronization domain, a signal domain, and a data domain.

65. The communication device according to claim 64, characterized in that, The data field contains time slot related information.

66. The communication device according to claim 64 or 65, characterized in that, The signal field includes first indication information, which indicates that the length of the data field is 0.

67. The communication device according to claim 63, characterized in that, The synchronization frame includes a preamble, a synchronization domain, and a signal domain.

68. The communication device according to claim 67, characterized in that, The signal domain contains control information for synchronization.

69. The communication device according to claim 67 or 68, characterized in that, The signal domain contains time slot related information.

70. The communication device according to any one of claims 67 to 69, characterized in that, The synchronization frame is an empty data packet NDP frame.

71. The communication device according to claim 13, characterized in that, The synchronization frame includes a preamble and a synchronization field.

72. The communication device according to any one of claims 51 to 71, characterized in that, The first random access code includes a random number and / or the first identifier of the first device.

73. The communication device according to claim 72, characterized in that, The first identifier is a temporary identifier for the first device.

74. The communication device according to claim 72 or 73, characterized in that, The first identifier is an identifier determined based on the second identifier of the first device, or an identifier in the temporary identifier set of the first device.

75. The communication device according to any one of claims 51 to 74, characterized in that, The first device is an ambient power supply (AMP) device; and / or, the second device is a network device.

76. A communication device, characterized in that, The communication device is a second device, and the second device includes: The communication module is configured to send a first trigger frame to a first device, the first trigger frame being used to indicate a first resource; and to receive a first random access code sent by the first device through the first resource.

77. The communication device according to claim 76, characterized in that, The communication module is further configured to: send a second trigger frame to the first device, the second trigger frame being used to schedule the first device to perform data transmission on a second resource; and receive first data sent by the first device through the second resource.

78. The communication device according to claim 77, characterized in that, The second trigger frame contains the first random access code.

79. The communication device according to claim 77 or 78, characterized in that, The second trigger frame also includes resource indication information, which is used to indicate the second resource that corresponds to the first random access code.

80. The communication device according to claim 77 or 78, characterized in that, The second resource is determined based on preset rules.

81. The communication device according to claim 80, characterized in that, The preset rule is associated with one or more of the following: The number of resources scheduled by the second trigger frame; The first random access code; The number of devices scheduled by the second trigger frame; The order of the first random access code in the random access codes of one or more devices scheduled by the second trigger frame.

82. The communication device according to any one of claims 77 to 81, characterized in that: The first trigger frame and the second trigger frame are transmitted in the same transmission opportunity (TXOP); or, The first trigger frame and the second trigger frame are transmitted in different TXOPs.

83. The communication device according to any one of claims 77 to 82, characterized in that, The temporal positions of the first trigger frame and the second trigger frame are related; and / or, the identification information carried in the first trigger frame and the second trigger frame is related.

84. The communication device according to any one of claims 76 to 83, characterized in that, The communication module is further configured to: send a synchronization frame to the first device, the synchronization frame being used for time synchronization between the first device and the second device.

85. The communication device according to claim 84, characterized in that, The synchronization frame is used to determine the temporal location of resources in the resource pool.

86. The communication device according to claim 84 or 85, characterized in that, The synchronization frame is transmitted based on a third resource, the temporal location of which is associated with the temporal location of resources in the resource pool, and the association is determined based on predefined information and / or preconfiguration information.

87. The communication device according to claim 86, characterized in that, The temporal location of the third resource is located at the temporal start or end position of the resources in the resource pool.

88. The communication device according to any one of claims 84 to 87, characterized in that, The synchronization frame includes one or more of the following: preamble, synchronization domain, signal domain, and data domain.

89. The communication device according to claim 88, characterized in that, The synchronization frame includes a preamble, a synchronization domain, a signal domain, and a data domain.

90. The communication device according to claim 89, characterized in that, The data field contains time slot related information.

91. The communication device according to claim 89 or 90, characterized in that, The signal field includes first indication information, which indicates that the length of the data field is 0.

92. The communication device according to claim 88, characterized in that, The synchronization frame includes a preamble, a synchronization domain, and a signal domain.

93. The communication device according to claim 92, characterized in that, The signal domain contains control information for synchronization.

94. The communication device according to claim 92 or 93, characterized in that, The signal domain contains time slot related information.

95. The communication device according to any one of claims 92 to 94, characterized in that, The synchronization frame is an empty data packet NDP frame.

96. The communication device according to claim 88, characterized in that, The synchronization frame includes a preamble and a synchronization field.

97. The communication device according to any one of claims 76 to 96, characterized in that, The first random access code includes a random number and / or the first identifier of the first device.

98. The communication device according to claim 97, characterized in that, The first identifier is a temporary identifier for the first device.

99. The communication device according to claim 97 or 98, characterized in that, The first identifier is an identifier determined based on the second identifier of the first device, or an identifier in the temporary identifier set of the first device.

100. The communication device according to any one of claims 76 to 99, characterized in that, The first device is an ambient power supply (AMP) device; and / or, the second device is a network device.

101. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs the method as described in any one of claims 1 to 25 or 26 to 50.

102. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method as described in any one of claims 1 to 25 or 26 to 50.

103. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 25 or 26 to 50.

104. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1 to 25 or 26 to 50.

105. A computer program product, characterized in that, The method includes a program that causes a computer to perform the method as described in any one of claims 1 to 25 or 26 to 50.

106. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1 to 25 or 26 to 50.

Images