Data transmission method, first device and second device
Patent Information
- Application Number
- CN202280093463.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-17
- Publication Date
- 2024-11-12
AI Technical Summary
Existing IoT communication technology is difficult to meet the needs of extreme environments, extremely small size and extremely low cost, especially in harsh environments such as high temperature, extremely low temperature, high humidity, high radiation or high-speed movement. Traditional terminal equipment requires battery power. This results in high power consumption, and it is difficult to achieve zero power consumption and distinguish the needs of different devices.
Using passive electronic tags and backscatter communication technology, the data transmission of zero-power devices is realized through the energy collection module and low-power computing module, and different devices are distinguished through terminal identification, and the carrier signal and energy supply signal are combined for data transmission. .
It achieves zero-power communication without batteries in extreme environments, reduces the cost and complexity of IoT terminals, and can effectively distinguish between different devices to meet the extremely small size and low-cost requirements of IoT communications.
Smart Images

Figure CN118947073A_ABST
Abstract
Description
Data transmission method, first device and second device Technical Field
[0001] The present application relates to the field of communications, and more specifically, to a data transmission method, a first device, and a second device. Background Art
[0002] Radio Frequency Identification (RFID) technology, commonly known as electronic tags, can automatically identify a target object through radio frequency signals to facilitate data transmission. Considering that data transmission based on RFID technology is mostly between multiple devices, and there are multiple devices, it is necessary to distinguish between different devices to ensure correct data transmission and meet the requirements of zero-power data transmission between multiple devices.
[0003] Summary of the Invention
[0004] The embodiments of the present application provide a data transmission method, a first device, and a second device, which can realize data transmission, not only distinguish different devices, but also meet the data transmission requirements of zero power consumption.
[0005] An embodiment of the present application provides a data transmission method, applied to a first device, the method comprising:
[0006] The first device receives a downlink signal sent by the second device, where the downlink signal carries a terminal identifier;
[0007] The first device recognizes that the terminal identifier is its own identifier, and sends an uplink signal to the second device according to the downlink signal;
[0008] Wherein, the first device is a zero-power consumption device.
[0009] An embodiment of the present application provides a data transmission method, applied to a second device, the method comprising:
[0010] The second device sends a downlink signal to the first device, where the downlink signal carries a terminal identifier;
[0011] The second device receives the uplink signal;
[0012] The uplink signal is a signal obtained by the first device according to the downlink signal when the first device performs identification based on the terminal identifier, and the first device is a zero-power consumption device.
[0013] An embodiment of the present application provides a first device, including:
[0014] A first receiving unit, configured to receive a downlink signal sent by a second device, where the downlink signal carries a terminal identifier;
[0015] a first identification unit, configured to identify that the terminal identifier is the identifier of the first device itself, and send an uplink signal to the second device according to the downlink signal;
[0016] Wherein, the first device is a zero-power consumption device.
[0017] An embodiment of the present application provides a second device, including:
[0018] A first sending unit, configured to send a downlink signal to a first device, where the downlink signal carries a terminal identifier;
[0019] A second receiving unit, configured to receive an uplink signal;
[0020] The uplink signal is a signal obtained by the first device according to the downlink signal when the first device performs identification based on the terminal identifier, and the first device is a zero-power consumption device.
[0021] The embodiment of the present application provides a first device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the method described in the embodiment of the present application.
[0022] The embodiment of the present application provides a second device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the method described in the embodiment of the present application.
[0023] An embodiment of the present application provides a chip for implementing the method described in the above embodiment of the present application.
[0024] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method described in the above-mentioned embodiment of the present application.
[0025] An embodiment of the present application provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a device, the device executes the method described in the above embodiment of the present application.
[0026] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the method described in the above-mentioned embodiment of the present application.
[0027] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the above-mentioned embodiment of the present application.
[0028] In an embodiment of the present application, a first device (such as a zero-power device) can receive a downlink signal sent by a second device, and the downlink signal carries a terminal identifier. The first device recognizes that the terminal identifier is the first device's own identifier, and sends an uplink signal to the second device according to the downlink signal. The first device is a zero-power device that does not require battery power and can realize data transmission between the first device and the second device through backscatter communication. Moreover, when the first device recognizes that the terminal identifier is the first device's own identifier, different terminal devices can be distinguished. Thus, by adopting the embodiment of the present application, not only different devices can be distinguished, but also the data transmission requirements of zero power consumption can be met. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.
[0030] FIG2 is a schematic diagram of a cellular-based zero-power consumption system according to an embodiment of the present application.
[0031] FIG3 is a schematic diagram of a zero-power consumption system using auxiliary power supply cellular direct connection according to an embodiment of the present application.
[0032] FIG4 is a schematic diagram of backscattering based on a passive electronic tag according to an embodiment of the present application.
[0033] FIG5 is a schematic diagram of another method for implementing backscattering based on a passive electronic tag according to an embodiment of the present application.
[0034] FIG6 is a schematic diagram of energy harvesting based on a passive electronic tag according to an embodiment of the present application.
[0035] FIG7 is a schematic diagram of a resistance load modulation circuit of a passive electronic tag according to an embodiment of the present application.
[0036] FIG8 is a schematic diagram of an application scenario of implementing zero-power communication between a base station and a zero-power device according to a data transmission method of an embodiment of the present application.
[0037] FIG9 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0038] FIG10 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0039] FIG11 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0040] FIG12 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0041] FIG13 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0042] FIG14 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0043] FIG15 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0044] FIG16 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0045] Figure 17 is a schematic diagram of data transmission between a power supply node, a network device and a zero-power device according to a data transmission method in an embodiment of the present application.
[0046] FIG18 is a schematic diagram of data transmission between a network device and a zero-power device according to an example of a data transmission method according to an embodiment of the present application.
[0047] FIG19 is a schematic diagram of downlink data transmission between a network device and a zero-power device according to an example of a data transmission method according to an embodiment of the present application.
[0048] FIG20 is a schematic diagram of the encapsulation format of a downlink signal in downlink data transmission between a network device and a zero-power device according to an example of a data transmission method according to an embodiment of the present application.
[0049] Figure 21 is a schematic diagram of uplink data transmission between a network device and a zero-power device according to an example of a data transmission method according to an embodiment of the present application.
[0050] FIG22 is a schematic block diagram of a first device according to an embodiment of the present application.
[0051] FIG23 is a schematic block diagram of a second device according to an embodiment of the present application.
[0052] Figure 24 is a schematic block diagram of a communication device according to an embodiment of the present application.
[0053] Figure 25 is a schematic block diagram of a chip according to an embodiment of the present application.
[0054] Figure 26 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION
[0055] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.
[0056] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
[0057] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.
[0058] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.
[0059] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.
[0060] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
[0061] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.
[0062] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).
[0063] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.
[0064] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
[0065] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.
[0066] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.
[0067] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
[0068] FIG1 exemplarily illustrates a communication system 100. The communication system 100 includes a network device 110 and two terminal devices 120. Optionally, the communication system 100 may include multiple network devices 110, and each network device 110 may include another number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.
[0069] Optionally, the communication system 100 may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), which is not limited in the embodiments of the present application.
[0070] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.
[0071] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.
[0072] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.
[0073] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.
[0074] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.
[0075] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.
[0076] With the rapid development of communication technologies, a variety of industry applications that are compatible with IoT communication technologies have emerged. However, there are still many application scenarios whose needs are not well met, including but not limited to the following scenarios:
[0077] (1) Some IoT scenarios in harsh communication environments may face extreme environments such as high temperature, extremely low temperature, high humidity, high voltage, high radiation, or high-speed movement, such as ultra-high voltage power stations, high-speed train track monitoring, high-altitude cold zone environmental monitoring, and industrial production lines. In these scenarios, existing IoT terminals will not work due to the working environment limitations of conventional power supplies. In addition, extreme working environments are not conducive to IoT maintenance, such as battery replacement.
[0078] (2) IoT scenarios that require extremely small terminal form factors, such as food traceability, commodity circulation, and smart wearables, require terminals to be extremely small in size to facilitate use in these scenarios. For example, IoT terminals used for commodity management in the circulation process usually use electronic tags and need to be embedded in commodity packaging in a very compact form factor. For example, lightweight wearable devices can meet user needs while improving user experience, so the size of wearable devices needs to be designed to be smaller and lighter.
[0079] (3) In IoT scenarios that meet the requirements of extremely low-cost IoT communication, such as logistics or warehousing scenarios, IoT terminals can be attached to each item to facilitate the management of a large number of circulating items. Thus, the entire logistics process and the entire cycle can be accurately managed through communication between the terminal and the logistics network. This requires the cost of IoT terminals to be sufficiently low to enhance competitiveness relative to other alternative technologies.
[0080] IoT communication scenarios, such as those described above, require IoT communication terminals that are battery-free, ultra-low power, extremely small, and low-cost. Existing IoT communication technologies struggle to meet these requirements. However, zero-power communication technologies using energy harvesting and backscattering, due to their exceptional performance in terms of extremely low power consumption, extremely small size, and extremely low cost, are expected to become the next generation of IoT communication technologies, thereby addressing the communication needs of IoT-related application scenarios.
[0081] FIG2 exemplarily shows a cellular-based zero-power communication system 200. The zero-power communication system 200 includes: a network device and cellular users located in different cells. For example, in cell 1, there are two cellular users (such as terminal device 220-terminal device 230) evenly distributed around the network device 210 (such as a base station), and in cell 2, there are two cellular users (such as terminal device 240-terminal device 250) evenly distributed around the network device 210 (such as a base station). Optionally, the zero-power communication system 200 may also include multiple network devices, and the coverage range of each network device may include multiple terminal devices of other numbers, which is not limited in the embodiment of the present application.
[0082] Terminal devices 220, 230, 240, and 250 can be zero-power devices, which do not require batteries. Terminal devices 220 and 230 can directly use tags based on radio frequency identification (RFID) technology. RFID tags are also called "radio frequency tags" or "electronic tags." Specifically, passive electronic tags (or passive electronic tags) are used. Since they support backscattering, they can also be called backscattering tags. Terminal devices 240 and 250 can be zero-power devices that include passive electronic tags. For example, the passive electronic tags can be set inside terminal devices 240 and 250, or the passive electronic tags can be attached to the outside of terminal devices 240 and 250, etc. Terminal devices 240 and 250 can be mobile phones, and at least one of terminal devices 240 and 250 can also be a signal receiver. The present invention is not limited to these types of terminal devices. Any terminal device that can implement backscattering is within the scope of protection of this application.
[0083] As shown in Figure 2, the zero-power communication system 200 adopts a cellular direct connection communication method, that is, the network device and the zero-power device communicate directly. Before communication, the zero-power device needs to receive a wireless power supply signal to collect energy to obtain the energy required for work. Correspondingly, the network device sends a wireless power supply signal and a trigger signal to the zero-power device. The wireless power supply signal is used to provide energy to the zero-power device and can be a carrier signal sent by the network device; the trigger signal can use the same carrier signal as the wireless power supply signal, and the carrier signal can carry control information or data information sent to the zero-power device. The zero-power device modulates the carrier signal to obtain a backscattered signal, and transmits the reflected scattered signal to the network device by backscattering.
[0084] FIG3 exemplarily shows another cellular-based zero-power communication system 300. The zero-power communication system 300 includes: a network device, cellular users located in different cells, and a third-party device for power supply. For example, in cell 1, there is a cellular user (such as terminal device 320) distributed around the network device 310 (such as a base station), and in cell 2, there are two cellular users (such as terminal device 330-terminal device 340) evenly distributed around the network device 210 (such as a base station). Optionally, the zero-power communication system 300 may also include multiple network devices, and each network device may include multiple terminal devices of another number within its coverage range. The third-party device may be one or more, such as a power supply node 350 that supplies power to the terminal device 320 and the terminal device 330, and a power supply node 360 that supplies power to the terminal device 340. This embodiment of the present application does not limit this.
[0085] Terminal device 320, terminal device 330, and terminal device 340 can be zero-power devices, which do not need to carry batteries themselves. Among them, terminal device 320 can directly use RFID tags, which are also called "radio frequency tags" or "electronic tags". Specifically, passive electronic tags (or passive electronic tags) are used. Since they support backscattering, they can also be called backscattering tags. Terminal device 330 and terminal device 340 can be zero-power devices including passive electronic tags. For example, the passive electronic tags are set inside terminal device 330 and terminal device 340, or the passive electronic tags can be attached to the outside of terminal device 330 and terminal device 340, etc. Among them, terminal device 330 can be a mobile phone, and terminal device 340 can be a signal receiver. The terminal device is not limited to these types of terminal devices. As long as the terminal device can achieve backscattering, it is within the scope of protection of this application.
[0086] When third-party devices serve as energy supply nodes, they can be base stations, mobile phones, relay nodes, customer premises equipment (CPE), etc. in the network. Dedicated energy supply nodes can also be deployed when necessary. The wireless communication signals (such as synchronization signals, broadcast signals, data channels, etc.) sent by these energy supply nodes can be used to provide wireless energy for zero-power devices. Alternatively, based on a reasonable scheduling method, these energy supply nodes can also send dedicated wireless energy supply signals.
[0087] As shown in Figure 3, the zero-power communication system 300 adopts a cellular direct connection communication method with auxiliary power supply, that is, the zero-power device can obtain wireless power supply not only from the network device with which it communicates, but also from third-party devices. Before communication, the zero-power device needs to receive the wireless power supply signal sent by the third-party device and obtain energy through wireless power supply to perform energy harvesting, thereby obtaining the energy required for operation. Considering that the intensity of the power supply signal reaching the terminal device needs to meet a certain threshold, such as -20dBm or -30dBm, this results in the power supply signal transmitted by the network device covering a small range, generally ranging from tens of meters to 100 meters, when the power supply signal transmission power is limited. From the perspective of cellular cell coverage, the coverage range of wireless power supply is much smaller than the coverage range of data transmission signals. It is necessary to implement wireless power supply through more power supply nodes to significantly increase the coverage range of wireless power supply, thereby maximizing the cell coverage of zero-power communication. To this end, other nodes in the network besides network devices (such as base stations) can be used for wireless power supply. For example, the power supply nodes that can be used include mobile phones, relay nodes, CPEs, etc. in the network. If necessary, dedicated energy supply nodes can also be deployed. These energy supply nodes transmit wireless energy supply signals to the zero-power devices, and the network equipment transmits trigger signals to the zero-power devices. The wireless energy supply signal is used to provide energy to the zero-power devices and can be a carrier signal. The trigger signal and the wireless energy supply signal can use different carrier signals. The carrier signal can carry control information or data information for the zero-power device. The zero-power device modulates the carrier signal to generate a backscattered signal, which is then transmitted to the network equipment via backscattering.
[0088] As shown in Figure 4, the zero-power device is the above-mentioned passive electronic tag, or the zero-power device may include the above-mentioned passive electronic tag. The passive electronic tag includes an energy collection module (for energy collection), a backscatter communication module (for backscatter communication), a low-power computing module (for low-power computing) and a sensor module (for data collection and reporting), wherein the low-power computing module and the sensor module are optional modules. The network device (including but not limited to setting a reader / writer in the network device, or the network device supporting the read-write processing performed by the reader / writer) sends a power supply signal (such as radio waves) to the zero-power device, which can provide the energy required for the zero-power device to work. Specifically, the zero-power device can collect the energy carried by the radio waves in the space through the energy collection module, so as to drive the backscatter communication module, the low-power computing module and the sensor module to work through the energy collection module, and finally realize backscatter communication. The zero-power device obtains the energy required for work and can also receive trigger signals sent by network devices (such as control commands sent by the set reader / writer). The zero-power device responds to the trigger signal and establishes backscatter communication with the network device in a backscatter manner. For example, it can receive downlink data sent by the network device, and can also send uplink data requested by the network device. The uplink data sent can come from the data stored in the zero-power device itself (such as identity identification or pre-written information, such as the production date, brand, manufacturer, etc. of the product).
[0089] As shown in FIG5 , the zero-power device is the aforementioned passive electronic tag, or the zero-power device may include the aforementioned passive electronic tag. The passive electronic tag receives a carrier signal, collects energy through an energy harvesting module, and supplies energy to a low-power computing module through the energy harvesting module, which then modulates the carrier signal and performs backscatter communication.
[0090] As shown in Figure 6, the zero-power device is the aforementioned passive electronic tag, or the zero-power device may include the aforementioned passive electronic tag. The passive electronic tag utilizes an energy harvesting module (denoted as an RF module) to harvest electromagnetic wave energy from space through electromagnetic induction, thereby driving a load circuit (composed of a capacitor and a resistor). The energy harvesting module then drives the backscatter communication module, the low-power computing module, and the sensor module to operate, ultimately achieving backscatter communication.
[0091] As shown in Figure 7, load modulation is a method used by passive electronic tags to adjust data transmission to a reader / writer. Specifically, load modulation primarily adjusts the electrical parameters of the passive electronic tag's oscillating circuit according to the data stream's rhythm, causing the magnitude and phase of the passive electronic tag's impedance to change accordingly, thereby completing the modulation process. There are two main types of load modulation: resistive load modulation and capacitive load modulation. In resistive load modulation, a resistor is connected in parallel with the load, called the load modulation resistor. This resistor is switched on and off according to the data stream's clock, and the on and off of switch S is controlled by binary data encoding. In capacitive load modulation, compared to resistive load modulation, a capacitor is connected in parallel with the load, replacing the load modulation resistor controlled by binary data encoding in Figure 7.
[0092] To sum up, considering the increasing number of types of connected objects and application scenarios in the Internet of Things, in order to realize the interconnection of all things and avoid the problem of high power consumption caused by the need for battery power supply of traditional terminal devices in cellular networks, zero-power devices are introduced into cellular networks. Since the zero-power device is the above-mentioned passive electronic tag, or the zero-power device can include the above-mentioned passive electronic tag, it does not rely on the traditional active power amplifier transmitter, and can perform energy collection through the energy collection module in the passive electronic tag. At the same time, the low-power computing module in the passive electronic tag is used to greatly reduce the complexity of the hardware. Moreover, the zero-power device does not actively transmit signals, but realizes backscatter communication by adjusting the received carrier signal. Therefore, the use of the battery-free zero-power device can realize battery-free, zero-power backscatter communication, which not only meets the communication needs of IoT-related application scenarios, but also reduces the investment cost of IoT-related communication systems.
[0093] Taking uplink / downlink data transmission as an example, a network device can perform backscatter-based data transmission with multiple zero-power devices. Considering the number of terminal devices, different terminal devices need to be distinguished to ensure correct data transmission and meet the requirements of zero-power data transmission between multiple devices.
[0094] FIG8 is a schematic diagram of another application scenario according to an embodiment of the present application, exemplarily illustrating a data transmission method 800 according to an embodiment of the present application. Taking the network device as a base station and the terminal device as a mobile phone as an example, communication is performed between the base station 811 and the mobile phone 821, the mobile phone 831, and the mobile phone 841. At least one of the mobile phones 821, 831, and 841 is a mobile phone carrying a passive electronic tag. Taking the data transmission between the base station 811 and the mobile phone 841 (i.e., the mobile phone including the passive electronic tag) as an example, the data transmission process includes some or all of the following steps:
[0095] S810: The base station 811 sends a carrier signal, where the carrier signal includes a trigger signal for triggering backscatter communication (the trigger signal carries a terminal identifier) and a power supply signal.
[0096] S820, mobile phone 841 receives the power supply signal to obtain the energy required for work, and mobile phone 841 receives the trigger signal and obtains the terminal identifier carried in the trigger signal. Mobile phone 841 recognizes that the terminal identifier is the terminal device's own identifier and triggers backscatter communication.
[0097] S830 , the mobile phone 841 sends a reflected signal to the base station 811 , and establishes backscatter communication with the base station 811 , wherein the reflected signal is obtained based on the carrier signal.
[0098] There is no necessary order relationship between steps S810-S830. Some steps can be selected and executed as needed, and the above steps do not need to be executed in sequence.
[0099] The data transmission based on backscattering between the above-mentioned base station and the mobile phone is only an example. The embodiments of the present application are not limited to this example. It can be data transmission between multiple devices in other IoT scenarios, such as data transmission between an intelligent control center and multiple terminal devices in an IoT warehousing scenario, etc.
[0100] FIG9 is a schematic flow chart of a data transmission method 900 according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents:
[0101] S910. A first device receives a downlink signal sent by a second device, where the downlink signal carries a terminal identifier, wherein the first device is a zero-power consumption device.
[0102] In some examples, the first device may be a terminal device and the second device may be a network device, wherein the first device is a zero-power device including a passive electronic tag. Through the passive electronic tag, the zero-power device can not only realize data transmission with the network device based on backscatter communication, but also meet the zero-power data transmission requirements.
[0103] S920: The first device recognizes that the terminal identifier is its own identifier, and sends an uplink signal to the second device according to the downlink signal.
[0104] In some examples, the first device may be a terminal device and the second device may be a network device, wherein the first device is a zero-power device. Since there may be multiple zero-power devices communicating with the network device, it is necessary to distinguish which zero-power device the downlink signal sent by the network device is for. The zero-power device compares the terminal identifier carried by the downlink signal with the zero-power device's own identifier. When it is identified that the terminal identifier carried by the downlink signal is the zero-power device's own identifier, it is clear that the downlink signal sent by the network device is for itself, and thus an uplink signal is sent to the second device based on the downlink signal.
[0105] Using an embodiment of the present application, a first device (such as a zero-power device) can receive a downlink signal sent by a second device, and the downlink signal carries a terminal identifier. The first device recognizes that the terminal identifier is the first device's own identifier, and sends an uplink signal to the second device based on the downlink signal. The first device is a zero-power device that does not require battery power and can realize data transmission between the first device and the second device through backscatter communication. Moreover, when the first device recognizes that the terminal identifier is the first device's own identifier, different terminal devices can be distinguished. Thus, not only can different devices be distinguished, but also the data transmission requirements of zero power consumption can be met.
[0106] In a possible implementation, at least one of the following solutions (1) to (2) is included:
[0107] (1) The downlink signal is used to power the first device. For example, the first device is a zero-power device, and the second device is a network device, such as a base station. The carrier signal sent by the base station is used as the downlink signal. The downlink signal itself can power the zero-power device. The downlink signal and the power supply signal are the same.
[0108] (2) The first device receives a power supply signal, which is used to supply power to the first device. For example, the first device is a zero-power device and requires a signal other than a downlink signal as a power supply signal. The power supply signal can be a carrier signal sent by other power supply nodes other than the base station in the network (mobile phones, relay nodes, CPEs in the network, deployed dedicated power supply nodes, etc.). The downlink signal and the power supply signal are different.
[0109] In one possible implementation, the downlink signal may include two signals. When the downlink signal includes a first signal and a second signal, the first signal is used to carry a terminal identifier, and the second signal is used to carry an indication of downlink data or uplink data. For example, the first signal may be a trigger signal carrying a terminal identifier, and the second signal may be a data signal carrying downlink data or an indication of uplink data, wherein the downlink data is data sent by the second device (network device) to the first device (zero-power device), and the uplink data indication is used by the second device (network device) to request the first device (zero-power device) to receive uplink data.
[0110] In one possible implementation, the downlink signal may include one signal. When the downlink signal includes a first field and a second field, the first field is used to carry a terminal identifier, and the second field is used to carry an indication of downlink data or uplink data. The downlink data is data sent by the second device (network device) to the first device (zero-power device), and the uplink data indication is used by the second device (network device) to request the first device (zero-power device) to receive uplink data.
[0111] In a possible implementation, the identification of the terminal identifier includes at least one of the following solutions 1 to 3:
[0112] 1. Time Division: For downlink data transmission scenarios, the downlink signal includes two signals. The first signal is used to carry the terminal identifier, and the second signal is used to carry the downlink data. As shown in Figure 10, the first device recognizes that the terminal identifier is its own identifier and sends an uplink signal to the second device based on the downlink signal. The uplink signal includes at least part of the following content:
[0113] S1010. The first device obtains a terminal identifier from a received first signal.
[0114] In some examples, the first device is a zero-power device, and the zero-power device obtains a terminal identifier from the first signal, wherein the terminal identifier is an identifier registered when the zero-power device initially accesses the network.
[0115] S1020: The first device recognizes that the terminal identifier is the first device's own identifier and receives a second signal.
[0116] In some examples, the first device is a zero-power device and the second device is a network device. The zero-power device compares the terminal identifier obtained from the first signal with the zero-power device's own identifier. When it is identified that the terminal identifier obtained from the first signal is the zero-power device's own identifier, it is clear that the second signal sent by the network device is for itself, and thus the second signal is received to obtain downlink data from the second signal.
[0117] In some examples, there is a time interval between the first signal and the second signal.
[0118] S1030. The first device determines an uplink signal according to whether the downlink data in the second signal is successfully received.
[0119] In some examples, when the downlink data is successfully received, the uplink signal is determined to be an acknowledgment character (ACK). In other words, when the downlink data is successfully received, the uplink signal is ACK.
[0120] In some examples, when the downlink data is not successfully received, the uplink signal is determined to be a negative acknowledgement (NACK). In other words, the downlink data is not successfully received, and the uplink signal is NACK.
[0121] In some examples, ACK and NACK are separated by different sequences.
[0122] S1040. The first device sends an uplink signal to the second device.
[0123] In some examples, the first device is a zero-power device, and the second device is a network device. The zero-power device determines whether the uplink signal is ACK or NACK based on whether the downlink data in the second signal is successfully received, and then sends ACK or NACK to the network device.
[0124] 2. Modulation: For downlink data transmission scenarios, the downlink signal includes one signal, which includes a first field and a second field. The first field is used to carry the terminal identifier, and the second field is used to carry the downlink data. As shown in Figure 11, the first device recognizes that the terminal identifier is the first device's own identifier and sends an uplink signal to the second device based on the downlink signal, including at least part of the following content:
[0125] S1110. The first device demodulates the downlink signal to obtain a terminal identifier.
[0126] In some examples, the first device is a zero-power device, and the zero-power device obtains a terminal identifier from the first field through demodulation, wherein the terminal identifier is an identifier registered when the zero-power device initially accesses the network.
[0127] S1120: The first device recognizes that the terminal identifier is its own identifier and receives downlink data.
[0128] In some examples, the first device is a zero-power device and the second device is a network device. The zero-power device will obtain the terminal identifier from the first field and compare it with the zero-power device's own identifier. When it is identified that the terminal identifier obtained from the first field is the zero-power device's own identifier, it is clear that the downlink signal sent by the network device is for itself, and thus the downlink signal is received to obtain downlink data from the second field of the downlink signal.
[0129] S1130. The first device determines an uplink signal according to whether the downlink data is successfully received.
[0130] In some examples, when the downlink data is successfully received, the uplink signal is determined to be ACK. In other words, when the downlink data is successfully received, the uplink signal is ACK.
[0131] In some examples, when the downlink data is not successfully received, the uplink signal is determined to be NACK. In other words, the downlink data is not successfully received, and the uplink signal is NACK.
[0132] In some examples, ACK and NACK are separated by different sequences.
[0133] S1140. The first device sends an uplink signal to the second device.
[0134] In some examples, the first device is a zero-power device, and the second device is a network device. The zero-power device determines whether the uplink signal is ACK or NACK based on whether the downlink data in the downlink signal is successfully received, and then sends ACK or NACK to the network device.
[0135] 3. Descrambling of Cyclic Redundancy Check (CRC): For downlink data transmission scenarios, the downlink signal includes one signal, the downlink signal includes a first field and a second field, the first field is used to carry the terminal identifier, and the second field is used to carry the downlink data. As shown in Figure 12, the first device recognizes that the terminal identifier is the first device's own identifier, and sends an uplink signal to the second device based on the downlink signal, including at least part of the following content:
[0136] S1210. The first device obtains a terminal identifier from a downlink signal.
[0137] In some examples, the first device is a zero-power device, and the zero-power device obtains a terminal identifier from the first field by descrambling, where the terminal identifier is an identifier registered when the zero-power device initially accesses the network.
[0138] S1220: The first device performs CRC check descrambling according to the terminal identifier. If the descrambling is successful, the terminal identifier is identified as the first device's own identifier, and downlink data is received.
[0139] In some examples, the first device is a zero-power device, and the second device is a network device. The zero-power device's own identification is used for CRC check descrambling. If the descrambling is successful, the terminal identification obtained from the first field is identified as the zero-power device's own identification, and it is clear that the downlink signal sent by the network device is for itself, so the downlink signal is received to obtain downlink data from the second field of the downlink signal.
[0140] S1230. The first device determines an uplink signal according to whether the downlink data is successfully received.
[0141] In some examples, when the downlink data is successfully received, the uplink signal is determined to be ACK. In other words, when the downlink data is successfully received, the uplink signal is ACK.
[0142] In some examples, when the downlink data is not successfully received, the uplink signal is determined to be NACK. In other words, the downlink data is not successfully received, and the uplink signal is NACK.
[0143] In some examples, ACK and NACK are separated by different sequences.
[0144] S1240. The first device sends an uplink signal to the second device.
[0145] In some examples, the first device is a zero-power device, and the second device is a network device. The zero-power device determines whether the uplink signal is ACK or NACK based on whether the downlink data in the downlink signal is successfully received, and then sends ACK or NACK to the network device.
[0146] In a possible implementation, the identification of the terminal identifier includes at least one of the following solutions (1) to (3):
[0147] 1. Time Division: For uplink data transmission scenarios, the downlink signal includes two signals. The first signal is used to carry the terminal identifier, and the second signal is used to carry the uplink data indication. As shown in Figure 13, the first device recognizes that the terminal identifier is its own identifier and sends an uplink signal to the second device based on the downlink signal. The uplink signal includes at least part of the following content:
[0148] S1310. The first device obtains a terminal identifier from a received first signal.
[0149] In some examples, the first device is a zero-power device, and the zero-power device obtains a terminal identifier from the first signal, wherein the terminal identifier is an identifier registered when the zero-power device initially accesses the network.
[0150] S1320: The first device recognizes that the terminal identifier is the first device's own identifier and receives a second signal.
[0151] In some examples, the first device is a zero-power device and the second device is a network device. The zero-power device compares the terminal identifier obtained from the first signal with the zero-power device's own identifier. When it is identified that the terminal identifier obtained from the first signal is the zero-power device's own identifier, it is clear that the second signal sent by the network device is for itself, and thus the second signal is received to obtain an indication of uplink data from the second signal.
[0152] In some examples, there is a time interval between the first signal and the second signal.
[0153] S1330. The first device sends an uplink signal to the second device according to an indication of the uplink data in the second signal; wherein the uplink signal includes the uplink data.
[0154] In some examples, the first device is a zero-power device, and the second device is a network device. The zero-power device obtains an indication of uplink data from the second signal. The uplink data indication is used by the network device to request the zero-power device for uplink data to be received. The zero-power device responds to the uplink data indication and sends an uplink signal including uplink data to the network device.
[0155] 2. Modulation: For uplink data transmission scenarios, the downlink signal includes one signal, which includes a first field and a second field. The first field is used to carry the terminal identifier, and the second field is used to carry the indication of uplink data. As shown in Figure 14, the first device recognizes that the terminal identifier is the first device's own identifier and sends an uplink signal to the second device based on the downlink signal, including at least part of the following content:
[0156] S1410. The first device demodulates the downlink signal to obtain a terminal identifier.
[0157] In some examples, the first device is a zero-power device, and the zero-power device obtains a terminal identifier from the first field through demodulation, wherein the terminal identifier is an identifier registered when the zero-power device initially accesses the network.
[0158] S1420: The first device recognizes that the terminal identifier is its own identifier and receives an indication of uplink data.
[0159] In some examples, the first device is a zero-power device and the second device is a network device. The zero-power device will obtain a terminal identifier from the first field and compare it with the zero-power device's own identifier. When it is identified that the terminal identifier obtained from the first field is the zero-power device's own identifier, it will clearly determine that the downlink signal sent by the network device is for itself, and thus receive the downlink signal to obtain an indication of uplink data from the second signal of the downlink signal.
[0160] S1430. The first device sends an uplink signal to the second device according to an indication of the uplink data; wherein the uplink signal includes the uplink data.
[0161] In some examples, the first device is a zero-power device, and the second device is a network device. The zero-power device obtains an indication of uplink data from the second signal. The uplink data indication is used by the network device to request the zero-power device for uplink data to be received. The zero-power device responds to the uplink data indication and sends an uplink signal including uplink data to the network device.
[0162] 3. CRC check descrambling: For the transmission scenario of uplink data, the downlink signal includes one signal, which includes a first field and a second field. The first field is used to carry the terminal identifier, and the second field is used to carry the indication of uplink data. As shown in Figure 15, the first device recognizes that the terminal identifier is the first device's own identifier and sends an uplink signal to the second device based on the downlink signal, including at least part of the following content:
[0163] S1510. The first device obtains a terminal identifier from a downlink signal.
[0164] In some examples, the first device is a zero-power device, and the zero-power device obtains a terminal identifier from the first field by descrambling, where the terminal identifier is an identifier registered when the zero-power device initially accesses the network.
[0165] S1520: The first device performs CRC check descrambling according to the terminal identifier. If the descrambling is successful, the first device identifies the terminal identifier as the first device's own identifier and receives an indication of uplink data.
[0166] In some examples, the first device is a zero-power device, and the second device is a network device. The zero-power device's own identification is used for CRC check descrambling. If the descrambling is successful, the terminal identification obtained from the first field is identified as the zero-power device's own identification, and it is clear that the downlink signal sent by the network device is for itself, so the downlink signal is received to obtain an indication of the uplink data from the second field of the downlink signal.
[0167] S1530. The first device sends an uplink signal to the second device according to an instruction of the uplink data; wherein the uplink signal includes the uplink data.
[0168] In some examples, the first device is a zero-power device, and the second device is a network device. The zero-power device obtains an indication of uplink data from the second signal. The uplink data indication is used by the network device to request the zero-power device for uplink data to be received. The zero-power device responds to the uplink data indication and sends an uplink signal including uplink data to the network device.
[0169] In some examples, the uplink signal is scrambled using a CRC check.
[0170] FIG16 is a schematic flow chart of a data transmission method 1600 according to an embodiment of the present application. The method may optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents:
[0171] S1610. The second device sends a downlink signal to the first device, where the downlink signal carries a terminal identifier.
[0172] In some examples, the second device is a network device, the first device is a zero-power device, the network device sends a downlink signal to the zero-power device, and the zero-power device can obtain a terminal identifier from the downlink signal, where the terminal identifier is the identifier registered when the zero-power device initially accesses the network.
[0173] S1620. The second device receives an uplink signal, where the uplink signal is a signal obtained by the first device according to the downlink signal when the first device performs identification based on the terminal identifier, and the first device is a zero-power consumption device.
[0174] In some examples, the second device is a network device, the first device is a zero-power device, and the network device sends a downlink signal to the zero-power device. Since there can be multiple zero-power devices communicating with the network device, it is necessary to distinguish which zero-power device the downlink signal sent by the network device is for. The zero-power device compares the terminal identifier carried by the downlink signal with the zero-power device's own identifier. When it is identified that the terminal identifier carried by the downlink signal is the zero-power device's own identifier, it is clear that the downlink signal sent by the network device is for itself, and thus an uplink signal is sent to the second device based on the downlink signal.
[0175] Using an embodiment of the present application, a second device (such as a network device) can send a downlink signal to a second device (such as a zero-power device), and the downlink signal carries a terminal identifier. The first device recognizes that the terminal identifier is the first device's own identifier, and sends an uplink signal to the second device according to the downlink signal. The first device is a zero-power device that does not require battery power and can realize data transmission between the first device and the second device through backscatter communication. Moreover, when the first device recognizes that the terminal identifier is the first device's own identifier, different terminal devices can be distinguished. Thus, not only can different devices be distinguished, but also the data transmission requirements of zero power consumption can be met.
[0176] In a possible implementation, at least one of the following solutions (1) to (2) is included:
[0177] (1) The second device uses a downlink signal to power the first device. For example, the first device is a zero-power device, and the second device is a network device, such as a base station. The carrier signal sent by the base station is used as a downlink signal. The downlink signal itself can power the zero-power device. The downlink signal and the power supply signal are the same.
[0178] (2) The second device sends a power supply signal and uses the power supply signal to supply power to the first device. For example, the first device is a zero-power device, and the second device is a network device, such as a base station. It requires other signals besides the downlink signal as the power supply signal. It can be a carrier signal sent by other power supply nodes in the network other than the base station (mobile phones, relay nodes, CPE in the network, deployed dedicated power supply nodes, etc.) as the power supply signal. The downlink signal and the power supply signal are different.
[0179] In one possible implementation, the downlink signal may include two signals. When the downlink signal includes a first signal and a second signal, the first signal is used to carry a terminal identifier, and the second signal is used to carry an indication of downlink data or uplink data. For example, the first signal may be a trigger signal carrying a terminal identifier, and the second signal may be a data signal carrying downlink data or an indication of uplink data, wherein the downlink data is data sent by the second device (network device) to the first device (zero-power device), and the uplink data indication is used by the second device (network device) to request the first device (zero-power device) to receive uplink data.
[0180] In one possible implementation, the downlink signal may include one signal. When the downlink signal includes a first field and a second field, the first field is used to carry a terminal identifier, and the second field is used to carry an indication of downlink data or uplink data. The downlink data is data sent by the second device (network device) to the first device (zero-power device), and the uplink data indication is used by the second device (network device) to request the first device (zero-power device) to receive uplink data.
[0181] In a possible implementation, the uplink signal includes: ACK or NACK, wherein ACK is used to describe that the first device successfully receives the downlink data, and NACK is used to describe that the first device fails to successfully receive the downlink data.
[0182] In a possible implementation, the uplink signal includes uplink data, where the uplink data is used to describe data obtained by the first device according to an indication of the uplink data.
[0183] Figure 17 is a schematic data interaction diagram of a data transmission method 1700 according to an embodiment of the present application. The method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The above-mentioned first device is a zero-power device, the above-mentioned second device is a network device, and the above-mentioned downlink signal includes a first signal and a second signal, wherein the first signal is a trigger signal carrying a terminal identifier, and the second signal is a data signal carrying downlink data or uplink data indication, and also includes an energy supply signal sent by a deployed dedicated energy supply node, that is, the energy supply signal and the trigger signal are different signals. The method includes at least part of the following content:
[0184] S1710. The energy supply node sends an energy supply signal.
[0185] S1720. The network device sends a trigger signal, where the trigger signal carries a terminal identifier.
[0186] S1730. The network device sends a data signal, where the data signal carries downlink data or uplink data indication.
[0187] In some examples, the data signal is used by the network device to send downlink data to the terminal device, or the network device requests uplink data by sending an uplink data indication to the terminal device.
[0188] S1740: The zero-power device receives the energy supply signal and extracts energy required for operation from the energy supply signal.
[0189] S1750: When the zero-power consumption device recognizes that the terminal identifier carried in the trigger signal is the zero-power consumption device's own identifier, it receives the data signal.
[0190] In some examples, when the zero-power device recognizes that the terminal identifier carried in the trigger signal is the zero-power device's own identifier, it obtains the downlink data sent by the network device from the data signal;
[0191] In some examples, when the zero-power device recognizes that the terminal identifier carried in the trigger signal is the zero-power device's own identifier, it obtains an uplink data indication from the data signal, responds to the uplink data indication, and prepares the requested uplink data for the network device.
[0192] S1760: The network device establishes backscatter communication with the zero-power device, and the network device receives an uplink signal sent by the zero-power device.
[0193] In some examples, the uplink signal is a reflected signal obtained based on the downlink signal, specifically, obtained based on the data signal. For example, when the downlink data sent by the network device is obtained from the data signal, the uplink signal is determined based on whether the downlink data is successfully received, and the uplink signal includes: ACK or NACK; for example, when an uplink data indication is obtained from the data signal, an uplink signal is obtained in response to the uplink data indication, and the uplink signal includes uplink data (the uplink data is used to describe the data obtained by the zero-power consumption device based on the indication of the uplink data).
[0194] The data transmission method provided in the above-mentioned embodiment of the present application is described in detail below.
[0195] The zero-power device of the embodiment of the present application may include a passive electronic tag, which can use the radio coupling method of the transceiver (including close-range inductive coupling and long-range electromagnetic coupling, etc.) to realize contactless automatic recognition and transmission of identification information in the tag. Specifically, the passive electronic tag uses the energy obtained from the electromagnetic field generated in space to realize zero-power backscatter communication. When the passive electronic tag is close to the reader, the electronic tag antenna within the near field formed by the radiation of the reader antenna generates an induced current through electromagnetic induction, and the induced current drives the electronic tag chip circuit. During the communication process, the chip circuit sends the identification information stored in the tag to the reader through the electronic tag antenna. The reader reads the identification information and decodes it, thereby identifying the information carried by the passive electronic tag. The reader can be set in any device that communicates with the zero-power device, such as setting the reader in a network device, or the network device supports the read and write processing performed by the reader, which is within the scope of protection of this application.
[0196] Considering that if the downlink signal of a network device reaches multiple zero-power devices, it may trigger multiple zero-power devices to respond and send uplink signals (the uplink signal in backscatter communication is the reflected signal). In the downlink data transmission scenario, how to distinguish different zero-power devices to correctly receive the downlink data carried in the downlink signal sent by the network device, and in the uplink data transmission scenario, how to make the network device distinguish which of the uplink signals sent by different zero-power devices is the one it requested through the uplink data indication carried in the downlink signal, so as to correctly receive the uplink signal sent by the zero-power device, are technical problems that need to be solved.
[0197] The following examples of the embodiments of the present application are used to distinguish terminals by the terminal identifier carried in the downlink signal. At the same time, in the backscatter scenario, zero-power data transmission is achieved based on the zero-power device. In the following backscatter scenario, the uplink signal is a reflected signal and is not described in detail. In addition to being applicable to data transmission corresponding to the zero-power device, the embodiments of the present application are also applicable to scenarios such as initial access and paging.
[0198] Example 1:
[0199] Figure 18 is a schematic diagram of zero-power communication between a network device and a terminal device according to an example of a data transmission method according to an embodiment of the present application. As shown in Figure 18, the terminal device is a zero-power device. Since the zero-power device is not equipped with a battery, it needs to obtain a power supply signal through a network device (such as a base station) or other sources (such as a specially deployed power supply node). In this example, the power supply signal is sent by a specially deployed power supply node to provide the energy required for the zero-power device to work. The zero-power device receives a downlink signal and a power supply signal. Wherein, when the downlink signal is two signals, it includes a first signal (such as a trigger signal carrying a terminal identifier) and a second signal (such as a data signal carrying downlink data or uplink data indication). When the downlink signal is one signal, it includes a first field (such as trigger information carrying a terminal identifier) and a second field (such as data information carrying downlink data or uplink data indication). After the zero-power device obtains the reflected signal based on the downlink signal, it sends the reflected signal to the network device through backscattering.
[0200] It should be pointed out that if the above-mentioned power supply signal is sent by a specially deployed power supply node, the power supply signal and the downlink signal are different signals, and the two signals may not be sent in the same frequency band; if the above-mentioned power supply signal is sent through network equipment (such as a base station), the power supply signal and the downlink signal are the same signal, and the two signals may be sent in the same frequency band.
[0201] Regarding power supply signals, network devices can transmit power supply signals continuously or intermittently within a certain frequency band. These signals are continuous waves (CW), such as sine waves. If the power supply signal is transmitted continuously, the continuously transmitted power supply signal comprises a constant amplitude continuous wave signal. Zero-power devices receive the power supply signal and harvest energy. Once the energy required for operation is obtained, they can then perform functions such as signal reception, signal reflection, and measurement.
[0202] Example 2:
[0203] FIG19 is a schematic diagram of downlink data transmission between a network device and a terminal device according to an example of a data transmission method according to an embodiment of the present application. As shown in FIG19 , the terminal device is a zero-power device, and the network device sends a downlink signal to the zero-power device. When the downlink signal is 1 signal, as shown in FIG20 , the downlink signal includes a first field (such as trigger information carrying a terminal identifier) and a second field (such as data information carrying downlink data). In the downlink signal, the terminal identifier is recorded as "0" and the downlink data is recorded as "1". The feedback uplink data (such as ACK / NACK) can be recorded as "0" in the reflected signal.
[0204] It should be pointed out that when the zero-power device transmits data, different forms of codes can be used to represent binary "1" and "0" (or, different pulse signals can be used to represent 0 and 1). The wireless radio frequency identification system can use one of the following encoding methods: reverse non-return to zero (NRZ) encoding, Manchester encoding, unipolar return to zero (Unipolar RZ) encoding, differential bi-phase (DBP) encoding, Miller encoding and differential encoding.
[0205] The zero-power device is powered by the downlink signal, and the energy required for the zero-power device to operate is extracted from the power supply signal. The zero-power device receives the downlink signal, identifies that the terminal identifier carried in the first field of the downlink signal is the zero-power device's own identifier, and then receives the downlink data carried in the second field of the downlink signal. The reflected signal is determined based on whether the downlink data is successfully received. If the downlink data is successfully received, the reflected signal includes an ACK, and the zero-power device establishes backscatter communication with the network device and sends a reflected signal including the ACK. If the downlink data is not successfully received, the reflected signal includes a NACK, and the zero-power device establishes backscatter communication with the network device and sends a reflected signal including the NACK.
[0206] Figure 21 is a schematic diagram of uplink data transmission between a network device and a terminal device according to an example of a data transmission method according to an embodiment of the present application. As shown in Figure 21, the terminal device is a zero-power device, and the network device sends a downlink signal to the zero-power device. When the downlink signal is 1 signal, the downlink signal includes a first field (such as trigger information carrying a terminal identifier) and a second field (such as data information carrying an uplink data indication). The terminal identifier and the uplink data indication can be distinguished in the downlink signal using different identification information. For example, the terminal identifier is recorded as "0" and the uplink data indication is recorded as "1".
[0207] The zero-power device is powered by the downlink signal, and the energy required for the zero-power device to operate is extracted from the power supply signal. The zero-power device receives the downlink signal, identifies that the terminal identifier carried in the first field of the downlink signal is the zero-power device's own identifier, and then receives the uplink data indication carried in the second field of the downlink signal. In response to the uplink data indication, the zero-power device obtains a reflected signal based on the downlink signal. The reflected signal includes the uplink data requested by the network device to the zero-power device (the uplink data is used to describe the data obtained by the zero-power device based on the indication of the uplink data).
[0208] In the above example, the downlink signal may also include: a cell identifier. For example, when the downlink signal is two signals, the first signal (such as a trigger signal) carries the cell identifier, thereby distinguishing different cells and knowing which cell the zero-power device belongs to. If data duplication occurs during data transmission, it can be clearly determined to which cell the data is sent.
[0209] The above example may also include: carrying the terminal identifier in the reflected signal, which may also serve as a preamble for the downlink signal. Optionally, the reflected signal may not carry the terminal identifier. In other words, carrying the terminal identifier in the reflected signal is optional and can be configured based on data transmission requirements.
[0210] In the above examples, the downlink signal and the reflected signal can both use a time division structure to define different components of the corresponding signal, or they can combine frequency division, code division, and other methods to define the structure.
[0211] In the above example, a reflected signal can be obtained by modulating the downlink signal. Optionally, the modulation method may include at least one of amplitude modulation, phase modulation, and frequency modulation. In terms of amplitude modulation, the amplitude of the carrier can vary with the modulation signal, thereby obtaining various amplitude modulated signals. Specifically, the zero-power device can obtain the reflected signal through subcarrier modulation and then transmit the reflected signal to the network device. For example, the subcarrier modulation can modulate the signal onto carrier 1, or it can perform another modulation on the modulation result of carrier 1 so that the modulation result can be used to modulate the signal onto another carrier 2 with a higher frequency.
[0212] It should be noted that the above examples can be combined with various possibilities in the above-mentioned embodiments of the present application, which will not be described in detail here.
[0213] Figure 22 is a schematic block diagram of a first device 2200 according to an embodiment of the present application. The first device 2200 may include: a first receiving unit 2210, configured to receive a downlink signal sent by a second device, the downlink signal carrying a terminal identifier; a first identification unit 2220, configured to identify the terminal identifier as the first device's own identifier and transmit an uplink signal to the second device based on the downlink signal. The first device is a zero-power device.
[0214] In a possible implementation, the downlink signal is used to power the first device; or, the method further includes: a second receiving unit, used to receive a power supply signal, where the power supply signal is used to power the first device.
[0215] In a possible implementation, when the downlink signal includes a first signal and a second signal, the first signal is used to carry the terminal identifier, and the second signal is used to carry an indication of downlink data or uplink data.
[0216] In a possible implementation, when the downlink signal includes a first field and a second field, the first field is used to carry the terminal identifier, and the second field is used to carry an indication of downlink data or uplink data.
[0217] In one possible implementation, the first identification unit is used to obtain the terminal identifier from the received first signal; identify the terminal identifier as the first device's own identifier, and receive the second signal; determine the uplink signal based on whether the downlink data in the second signal is successfully received; and send the uplink signal to the second device.
[0218] In a possible implementation, the first identification unit is configured to determine that the uplink signal is ACK if the downlink data is successfully received, and to determine that the uplink signal is NACK if the downlink data is not successfully received.
[0219] In a possible implementation manner, there is a time interval between the first signal and the second signal.
[0220] In one possible implementation, the first identification unit is used to demodulate the downlink signal to obtain the terminal identifier; identify the terminal identifier as the first device's own identifier, and receive the downlink data; determine the uplink signal based on whether the downlink data is successfully received; and send the uplink signal to the second device.
[0221] In a possible implementation, the first identification unit is configured to determine that the uplink signal is ACK if the downlink data is successfully received, and to determine that the uplink signal is NACK if the downlink data is not successfully received.
[0222] In one possible implementation, the first identification unit is used to obtain the terminal identifier from the downlink signal; perform CRC check descrambling based on the terminal identifier, and if the descrambling is successful, identify the terminal identifier as the first device's own identifier and receive the downlink data; determine the uplink signal based on whether the downlink data is successfully received; and send the uplink signal to the second device.
[0223] In a possible implementation, the first identification unit is configured to determine that the uplink signal is ACK if the downlink data is successfully received, and to determine that the uplink signal is NACK if the downlink data is not successfully received.
[0224] In a possible implementation, the method further includes an identification unit configured to identify the ACK and the NACK respectively by using different sequences.
[0225] In one possible implementation, the first identification unit is used to obtain the terminal identifier from the received first signal; identify the terminal identifier as the first device's own identifier, and receive the second signal; and send the uplink signal to the second device according to the indication of the uplink data in the second signal; wherein the uplink signal includes the uplink data.
[0226] In a possible implementation manner, there is a time interval between the first signal and the second signal.
[0227] In one possible implementation, the first identification unit is used to demodulate the downlink signal to obtain the terminal identifier; identify the terminal identifier as the first device's own identifier, and receive an indication of the uplink data; and send the uplink signal to the second device according to the indication of the uplink data; wherein the uplink signal includes the uplink data.
[0228] In one possible implementation, the first identification unit is used to obtain the terminal identifier from the downlink signal; perform CRC check descrambling based on the terminal identifier, and if the descrambling is successful, identify the terminal identifier as the first device's own identifier and receive an indication of the uplink data; and send the uplink signal to the second device based on the indication of the uplink data; wherein the uplink signal includes the uplink data.
[0229] In a possible implementation, the method further includes a scrambling unit configured to scramble the uplink signal using a CRC check method.
[0230] In a possible implementation manner, the terminal identifier is an identifier registered when the first device initially accesses the network.
[0231] The first device 2200 of the embodiment of the present application can be a zero-power device, which can realize the corresponding functions of the first device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the first device 2200 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the first device 2200 of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.), or by the same module (sub-module, unit or component, etc.).
[0232] Figure 23 is a schematic block diagram of a second device 2300 according to an embodiment of the present application. The second device 2300 may include: a first transmitting unit 2310, configured to transmit a downlink signal to a first device, the downlink signal carrying a terminal identifier; a second receiving unit 2320, configured to receive an uplink signal; wherein the uplink signal is a signal obtained by the first device based on the downlink signal when the first device performs identification based on the terminal identifier, and the first device is a zero-power device.
[0233] In a possible implementation, the first sending unit is configured to use the downlink signal to power the first device; or, to send a power supply signal and use the power supply signal to power the first device.
[0234] In a possible implementation, when the downlink signal includes a first signal and a second signal, the first signal is used to carry the terminal identifier, and the second signal is used to carry an indication of downlink data or uplink data.
[0235] In a possible implementation, when the downlink signal includes a first field and a second field, the first field is used to carry the terminal identifier, and the second field is used to carry an indication of downlink data or uplink data.
[0236] In a possible implementation, the uplink signal includes: ACK or NACK, wherein the ACK is used to describe that the first device successfully receives the downlink data, and the NACK is used to describe that the first device fails to successfully receive the downlink data.
[0237] In a possible implementation, the uplink signal includes uplink data, wherein the uplink data is used to describe data obtained by the first device according to an indication of the uplink data.
[0238] In a possible implementation manner, the terminal identifier is an identifier registered when the first device initially accesses the network.
[0239] The second device 2300 of the embodiment of the present application can be a network device, which can implement the corresponding functions of the second device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the second device 2300 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the second device 2300 of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.), or by the same module (sub-modules, units or components, etc.).
[0240] Figure 24 is a schematic structural diagram of a communication device 2400 according to an embodiment of the present application. The communication device 2400 includes a processor 2410, which can call and execute a computer program from a memory to enable the communication device 2400 to implement the method in the embodiment of the present application.
[0241] Optionally, the communication device 2400 may further include a memory 2420. The processor 2410 may call and execute a computer program from the memory 2420 to enable the communication device 2400 to implement the method in the embodiment of the present application.
[0242] The memory 2420 may be a separate device independent of the processor 2410 , or may be integrated into the processor 2410 .
[0243] Optionally, the communication device 2400 may further include a transceiver 2430 , and the processor 2410 may control the transceiver 2430 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.
[0244] The transceiver 2430 may include a transmitter and a receiver. The transceiver 2430 may further include an antenna, and the number of antennas may be one or more.
[0245] Optionally, the communication device 2400 may be the first device of an embodiment of the present application, and the communication device 2400 may implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.
[0246] Optionally, the communication device 2400 may be the second device of the embodiment of the present application, and the communication device 2400 may implement the corresponding processes implemented by the second device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.
[0247] 25 is a schematic structural diagram of a chip 2500 according to an embodiment of the present application. The chip 2500 includes a processor 2510, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.
[0248] Optionally, the chip 2500 may further include a memory 2520. The processor 2510 may call and execute a computer program from the memory 2520 to implement the method performed by the first device or the second device in the embodiment of the present application.
[0249] The memory 2520 may be a separate device independent of the processor 2510 or may be integrated into the processor 2510 .
[0250] Optionally, the chip 2500 may further include an input interface 2530. The processor 2510 may control the input interface 2530 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
[0251] Optionally, the chip 2500 may further include an output interface 2540. The processor 2510 may control the output interface 2540 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
[0252] Optionally, the chip can be applied to the first device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.
[0253] Optionally, the chip can be applied to the second device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the second device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0254] The chips used in the first device and the second device may be the same chip or different chips.
[0255] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0256] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.
[0257] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).
[0258] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.
[0259] Figure 26 is a schematic block diagram of a communication system 2600 according to an embodiment of the present application. The communication system 2600 includes a first device 2610 and a second device 2620. The first device 2610 may be a zero-power device, including: a first receiving unit for receiving a downlink signal sent by the second device, the downlink signal carrying a terminal identifier; a first identification unit for identifying that the terminal identifier is the first device's own identifier, and sending an uplink signal to the second device according to the downlink signal; wherein the first device is a zero-power device. The second device 2620 may be a network device, including: a first sending unit for sending a downlink signal to the first device, the downlink signal carrying a terminal identifier; a second receiving unit for receiving an uplink signal; wherein the uplink signal is a signal obtained by the first device based on the downlink signal when the first device performs identification based on the terminal identifier, and the first device is a zero-power device. For the sake of brevity, it will not be described here.
[0260] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part 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, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).
[0261] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean 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 the present application.
[0262] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0263] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.
Claims
1. A data transmission method, applied to a first device, comprising: The first device receives a downlink signal sent by the second device, where the downlink signal carries a terminal identifier; The first device recognizes that the terminal identifier is its own identifier, and sends an uplink signal to the second device according to the downlink signal; Wherein, the first device is a zero-power consumption device.
2. The method according to claim 1, wherein The downlink signal is used to supply energy to the first device; or, The first device receives a power supply signal, where the power supply signal is used to supply power to the first device.
3. The method according to claim 1, wherein When the downlink signal includes a first signal and a second signal, the first signal is used to carry the terminal identifier, and the second signal is used to carry an indication of downlink data or uplink data.
4. The method according to claim 1, wherein When the downlink signal includes a first field and a second field, the first field is used to carry the terminal identifier, and the second field is used to carry an indication of downlink data or uplink data.
5. The method according to claim 3, wherein The first device recognizes that the terminal identifier is its own identifier, and sends an uplink signal to the second device according to the downlink signal, including: The first device obtains the terminal identifier from the received first signal; The first device recognizes that the terminal identifier is the first device's own identifier, and receives the second signal; The first device determines the uplink signal according to whether the downlink data in the second signal is successfully received; The first device sends the uplink signal to the second device.
6. The method according to claim 5, wherein: The first device determining the uplink signal according to whether the downlink data in the second signal is successfully received includes: When the downlink data is successfully received, determining that the uplink signal is an acknowledgment character ACK; When the downlink data is not received successfully, it is determined that the uplink signal is a non-acknowledgement character NACK.
7. The method according to claim 3, wherein: There is a time interval between the first signal and the second signal.
8. The method according to claim 4, wherein The first device recognizes that the terminal identifier is its own identifier, and sends an uplink signal to the second device according to the downlink signal, including: The first device demodulates the downlink signal to obtain the terminal identifier; The first device recognizes that the terminal identifier is the first device identifier, and receives the downlink data; The first device determines the uplink signal according to whether the downlink data is successfully received; The first device sends the uplink signal to the second device.
9. The method according to claim 8, wherein The first device determining the uplink signal according to whether the downlink data is successfully received includes: When the downlink data is successfully received, determining that the uplink signal is an acknowledgment character ACK; When the downlink data is not received successfully, it is determined that the uplink signal is a non-acknowledgement character NACK.
10. The method according to claim 4, wherein: The first device recognizes that the terminal identifier is its own identifier, and sends an uplink signal to the second device according to the downlink signal, including: The first device obtains the terminal identifier from the downlink signal; The first device performs CRC check descrambling according to the terminal identifier, and if the descrambling is successful, identifies the terminal identifier as the first device's own identifier, and receives the downlink data; The first device determines the uplink signal according to whether the downlink data is successfully received; The first device sends the uplink signal to the second device.
11. The method according to claim 10, wherein: The first device determining the uplink signal according to whether the downlink data is successfully received includes: When the downlink data is successfully received, determining that the uplink signal is an acknowledgment character ACK; When the downlink data is not received successfully, it is determined that the uplink signal is a non-acknowledgement character NACK.
12. The method according to any one of claims 6, 9, and 11, further comprising: The ACK and the NACK are respectively identified by different sequences.
13. The method according to claim 3, wherein: The first device recognizes that the terminal identifier is its own identifier, and sends an uplink signal to the second device according to the downlink signal, including: The first device obtains the terminal identifier from the received first signal; The first device recognizes that the terminal identifier is the first device's own identifier, and receives the second signal; The first device sends the uplink signal to the second device according to an indication of the uplink data in the second signal; wherein the uplink signal includes the uplink data.
14. The method according to claim 3, wherein: There is a time interval between the first signal and the second signal.
15. The method according to claim 4, wherein The first device recognizes that the terminal identifier is its own identifier, and sends an uplink signal to the second device according to the downlink signal, including: The first device demodulates the downlink signal to obtain the terminal identifier; The first device recognizes that the terminal identifier is the first device identifier itself, and receives an indication of the uplink data; The first device sends the uplink signal to the second device according to an instruction of the uplink data; wherein the uplink signal includes the uplink data.
16. The method according to claim 4, wherein The first device recognizes that the terminal identifier is its own identifier, and sends an uplink signal to the second device according to the downlink signal, including: The first device obtains the terminal identifier from the downlink signal; The first device performs CRC check descrambling according to the terminal identifier, and if the descrambling is successful, identifies the terminal identifier as the first device's own identifier, and receives an indication of the uplink data; The first device sends the uplink signal to the second device according to an instruction of the uplink data; wherein the uplink signal includes the uplink data.
17. The method according to any one of claims 1 to 16, further comprising: The uplink signal is scrambled by CRC check.
18. The method according to any one of claims 1 to 16, wherein The terminal identifier is an identifier registered when the first device initially accesses the network.
19. A data transmission method, applied to a second device, the method comprising: The second device sends a downlink signal to the first device, where the downlink signal carries a terminal identifier; The second device receives the uplink signal; The uplink signal is a signal obtained by the first device according to the downlink signal when the first device performs identification based on the terminal identifier, and the first device is a zero-power consumption device.
20. The method according to claim 19, further comprising: The second device uses the downlink signal to supply energy to the first device; or, The second device sends a power supply signal, and uses the power supply signal to supply power to the first device.
21. The method according to claim 19, wherein When the downlink signal includes a first signal and a second signal, the first signal is used to carry the terminal identifier, and the second signal is used to carry an indication of downlink data or uplink data.
22. The method according to claim 19, wherein When the downlink signal includes a first field and a second field, the first field is used to carry the terminal identifier, and the second field is used to carry an indication of downlink data or uplink data.
23. The method according to claim 21 or 22, wherein: The uplink signal includes: an acknowledgment character ACK, or a non-acknowledgment character NACK, wherein the ACK is used to describe that the first device successfully receives the downlink data, and the NACK is used to describe that the first device fails to successfully receive the downlink data.
24. The method according to claim 21 or 22, wherein The uplink signal includes uplink data, wherein the uplink data is used to describe data obtained by the first device according to an indication of the uplink data.
25. The method according to any one of claims 19 to 24, wherein: The terminal identifier is an identifier registered when the first device initially accesses the network.
26. A first device comprising: A first receiving unit, configured to receive a downlink signal sent by a second device, where the downlink signal carries a terminal identifier; a first identification unit, configured to identify that the terminal identifier is the identifier of the first device itself, and send an uplink signal to the second device according to the downlink signal; Wherein, the first device is a zero-power consumption device.
27. The apparatus of claim 26, wherein: The downlink signal is used to supply energy to the first device; or, further includes: a second receiving unit, used to receive a power supply signal, wherein the power supply signal is used to supply energy to the first device.
28. The apparatus of claim 26, wherein When the downlink signal includes a first signal and a second signal, the first signal is used to carry the terminal identifier, and the second signal is used to carry an indication of downlink data or uplink data.
29. The apparatus of claim 26, wherein: When the downlink signal includes a first field and a second field, the first field is used to carry the terminal identifier, and the second field is used to carry an indication of downlink data or uplink data.
30. The apparatus of claim 28, wherein The first identification unit is configured to: Obtaining the terminal identifier from the received first signal; identifying that the terminal identifier is the identifier of the first device itself, and receiving the second signal; determining the uplink signal according to whether the downlink data in the second signal is successfully received; Send the uplink signal to the second device.
31. The apparatus of claim 30, wherein: The first identification unit is configured to: When the downlink data is successfully received, determining that the uplink signal is an acknowledgment character ACK; When the downlink data is not received successfully, it is determined that the uplink signal is a non-acknowledgement character NACK.
32. The apparatus of claim 28, wherein There is a time interval between the first signal and the second signal.
33. The apparatus of claim 29, wherein: The first identification unit is configured to: Demodulating the downlink signal to obtain the terminal identifier; Identifying that the terminal identifier is the identifier of the first device itself, and receiving the downlink data; determining the uplink signal according to whether the downlink data is successfully received; Send the uplink signal to the second device.
34. The apparatus of claim 33, wherein: The first identification unit is configured to: When the downlink data is successfully received, determining that the uplink signal is an acknowledgment character ACK; When the downlink data is not received successfully, it is determined that the uplink signal is a non-acknowledgement character NACK.
35. The apparatus of claim 29, wherein The first identification unit is configured to: Obtaining the terminal identifier from the downlink signal; Performing descrambling of the CRC check according to the terminal identifier, and if the descrambling is successful, identifying the terminal identifier as the first device's own identifier, and receiving the downlink data; determining the uplink signal according to whether the downlink data is successfully received; Send the uplink signal to the second device.
36. The apparatus of claim 35, wherein The first identification unit is configured to: When the downlink data is successfully received, determining that the uplink signal is an acknowledgment character ACK; When the downlink data is not received successfully, it is determined that the uplink signal is a non-acknowledgement character NACK.
37. The device according to any one of claims 31, 34, and 36, further comprising an identification unit for: The ACK and the NACK are respectively identified by different sequences.
38. The apparatus of claim 28, wherein The first identification unit is configured to: Obtaining the terminal identifier from the received first signal; identifying that the terminal identifier is the identifier of the first device itself, and receiving the second signal; According to an indication of the uplink data in the second signal, the uplink signal is sent to the second device; wherein the uplink signal includes the uplink data.
39. The apparatus of claim 28, wherein There is a time interval between the first signal and the second signal.
40. The apparatus of claim 29, wherein The first identification unit is configured to: Demodulating the downlink signal to obtain the terminal identifier; Identifying that the terminal identifier is the first device identifier, and receiving an indication of the uplink data; According to an indication of the uplink data, the uplink signal is sent to the second device; wherein the uplink signal includes the uplink data.
41. The apparatus of claim 29, wherein The first identification unit is configured to: Obtaining the terminal identifier from the downlink signal; Performing descrambling of the CRC check according to the terminal identifier, and if the descrambling is successful, identifying the terminal identifier as the first device's own identifier, and receiving an indication of the uplink data; According to an indication of the uplink data, the uplink signal is sent to the second device; wherein the uplink signal includes the uplink data.
42. The apparatus according to any one of claims 26 to 41, further comprising a scrambling unit configured to: The uplink signal is scrambled by CRC check.
43. The apparatus according to any one of claims 26 to 41, wherein The terminal identifier is an identifier registered when the first device initially accesses the network.
44. A second device comprising: A first sending unit, configured to send a downlink signal to a first device, where the downlink signal carries a terminal identifier; A second receiving unit, configured to receive an uplink signal; The uplink signal is a signal obtained by the first device according to the downlink signal when the first device performs identification based on the terminal identifier, and the first device is a zero-power consumption device.
45. The device according to claim 44, wherein the first sending unit is configured to: using the downlink signal to supply energy to the first device; or, A power supply signal is sent, and the power supply signal is used to supply power to the first device.
46. The apparatus of claim 44, wherein When the downlink signal includes a first signal and a second signal, the first signal is used to carry the terminal identifier, and the second signal is used to carry an indication of downlink data or uplink data.
47. The apparatus of claim 44, wherein: When the downlink signal includes a first field and a second field, the first field is used to carry the terminal identifier, and the second field is used to carry an indication of downlink data or uplink data.
48. Apparatus according to claim 46 or 47, wherein The uplink signal includes: an acknowledgment character ACK, or a non-acknowledgment character NACK, wherein the ACK is used to describe that the first device successfully receives the downlink data, and the NACK is used to describe that the first device fails to successfully receive the downlink data.
49. Apparatus according to claim 46 or 47, wherein The uplink signal includes uplink data, wherein the uplink data is used to describe data obtained by the first device according to an indication of the uplink data.
50. The apparatus according to any one of claims 44 to 49, wherein The terminal identifier is an identifier registered when the first device initially accesses the network.
51. A first device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the first device executes the method according to any one of claims 1 to 18.
52. A second device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the second device executes the method according to any one of claims 19 to 25.
53. A chip comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 18.
54. A chip comprising: A processor, configured to call and execute a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 19 to 25.
55. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 1 to 18.
56. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 19 to 25.
57. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 18.
58. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 19 to 25.
59. A computer program causing a computer to perform the method of any one of claims 1 to 18.
60. A computer program causing a computer to perform the method of any one of claims 19 to 25.
61. A communication system comprising: A first device, configured to perform the method according to any one of claims 1 to 18; A second device is configured to perform the method according to any one of claims 19 to 25.
