Communication method and communication device

By utilizing energy harvesting and backscatter communication techniques in low-power communication devices, the carrier frequency is determined to achieve frequency division multiplexing. This solves the problem of determining the communication frequency for low-power devices in extreme environments and extremely small-size scenarios, thereby increasing system capacity and reducing device complexity and cost.

WO2026065116A1PCT designated stage Publication Date: 2026-04-02GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 5 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-09-27
Publication Date
2026-04-02

AI Technical Summary

Technical Problem

For low-power communication devices, especially environmental IoT devices, existing technologies have failed to effectively solve the problem of how to determine the carrier frequency for other devices to send messages in order to achieve communication, particularly in extreme environments and scenarios with extremely small size and low cost.

Method used

A communication method is provided in which a first device receives or detects messages sent by a second device on one or more supported receiving frequencies, and uses energy harvesting and backscatter communication technology to determine the carrier frequency to achieve frequency division multiplexing, thereby reducing implementation complexity.

Benefits of technology

It enables frequency division multiplexing between different devices, improves system capacity, reduces device complexity and cost, and is suitable for low-power communication needs in extreme environments and with extremely small sizes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024121857_02042026_PF_FP_ABST
    Figure CN2024121857_02042026_PF_FP_ABST
Patent Text Reader

Abstract

Provided are a communication method and a communication device. The method comprises: a first device receives or detects, at a first frequency, a first message sent by a second device, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used for receiving the message sent by the second device.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and communication device TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and more particularly, to a communication method and a communication device. BACKGROUND

[0002] In some scenarios, low-power devices can be powered by batteries. In other scenarios, low-power communication devices can use various ambient energy based on an ambient energy harvesting module, such as an ambient IoT (A-IoT) device; for example, such a communication device can receive a wireless power signal and send a backscatter signal, or actively transmit a signal. How low-power communication devices, including A-IoT devices, can transmit messages with other communication devices is a problem to be solved.

[0003] SUMMARY

[0004] The present application provides a communication method and a communication device. Each aspect of the present application is described below.

[0005] In a first aspect, a communication method is provided, comprising: receiving or detecting, by a first device, a first message sent by a second device at a first frequency, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used to receive messages sent by the second device.

[0006] In a second aspect, a communication method is provided, comprising: sending, by a second device, a first message to a first device at a frequency corresponding to a first frequency, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used to receive messages sent by the second device. The frequency corresponding to the first frequency can be equal to the first frequency, or a frequency close to the first frequency.

[0007] In a third aspect, a communication device is provided, the communication device being a first device, the communication device comprising: a communication module configured to receive or detect a first message sent by a second device at a first frequency, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used to receive messages sent by the second device.

[0008] In a fourth aspect, a communication device is provided, the communication device being a second device, the communication device comprising: a communication module configured to send a first message to a first device at a frequency corresponding to a first frequency, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used to receive messages sent by the second device.

[0009] In a fifth aspect, a communication device is provided, comprising a transceiver, a memory, and a processor, the memory being configured to store a program, the processor being configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the communication device performs the method according to the first aspect or the second aspect.

[0010] In a sixth aspect, an apparatus is provided, comprising a processor configured to invoke a program from a memory, so that the apparatus performs the method according to the first aspect or the second aspect.

[0011] In a seventh aspect, a chip is provided, comprising a processor configured to invoke a program from a memory, so that a device installed with the chip performs the method according to the first aspect or the second aspect.

[0012] In an eighth aspect, a computer readable storage medium is provided, having a program stored thereon, the program causing a computer to perform the method according to the first aspect or the second aspect.

[0013] In a ninth aspect, a computer program product is provided, comprising a program, the program causing a computer to perform the method according to the first aspect or the second aspect.

[0014] In a tenth aspect, a computer program is provided, the computer program causing a computer to perform the method according to the first aspect or the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0015] FIG. 1 is an example diagram of an architecture of a wireless communication system to which embodiments of the present application can be applied.

[0016] FIG. 2 is an example diagram of an architecture of an environmental Internet of Things communication system.

[0017] FIG. 3 is an example diagram of an energy harvesting method of an environmental Internet of Things device.

[0018] FIG. 4 is an example diagram of a backscatter communication method of an environmental Internet of Things device.

[0019] FIG. 5 is an example diagram of a load modulation method of an environmental Internet of Things device.

[0020] FIG. 6 is a structural schematic diagram of an environmental Internet of Things device supporting an intermediate frequency receiver.

[0021] FIG. 7 is a structural schematic diagram of an environmental Internet of Things device supporting a zero intermediate frequency receiver.

[0022] FIG. 8 is an example diagram of bidirectional communication between an environmental Internet of Things device and a base station.

[0023] FIG. 9 is an example diagram of bidirectional communication between an environmental Internet of Things device and an intermediate node.

[0024] FIG. 10 is a flow diagram of a communication method according to an embodiment of the present application.

[0025] FIG. 11 is an example diagram of a possible implementation of multiple receiving frequencies.

[0026] FIG. 12 is a schematic diagram of a communication device according to an embodiment of the present application.

[0027] FIG. 13 is a schematic diagram of a communication device according to another embodiment of the present application.

[0028] FIG. 14 is a schematic diagram of an apparatus to which embodiments of the present application can be applied. DETAILED DESCRIPTION

[0029] The technical solutions in the present application will be described below with reference to the accompanying drawings. In order to facilitate understanding, first, the communication terms and communication processes that may be involved in the embodiments of the present application will be introduced with reference to FIGS. 1 to 9.

[0030] Communication system

[0031] The technical solutions of the embodiments of the present application can be applied to various communication systems. For example, the embodiments of the present application can be applied to a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS) system, a long term evolution (LTE) system, an advanced long term evolution (LTE-A) system, a new radio (NR) system, an evolved system of the NR system, a universal mobile telecommunication system (UMTS), a wireless local area networks (WLAN) system, a wireless fidelity (WiFi) system, a 5th-generation (5G) system. The embodiments of the present application can also be applied to other communication systems, such as a 6th-generation (6G) mobile communication system, or a satellite communication system, etc. future communication system.

[0032] The conventional communication system supports a limited number of connections, which is easy to implement. However, with the development of communication technology, the communication system can not only support the conventional cellular communication, but also support one or more types of other communications. For example, the communication system can support one or more of the following communications: device to device (D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), enhanced MTC (eMTC), vehicle to vehicle (V2V) communication, vehicle to everything (V2X) communication, and the like. The embodiments of the present application can also be applied to a communication system supporting the above communication modes.

[0033] The communication system in the embodiments of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) network deployment scenario.

[0034] The communication system in the embodiments of the present application can be applied to an unlicensed spectrum. The unlicensed spectrum can also be regarded as a shared spectrum. Alternatively, the communication system in the embodiments of the present application can also be applied to a licensed spectrum. The licensed spectrum can also be regarded as a dedicated spectrum.

[0035] The technical solutions of the embodiments of the present application can be applied to various internet of things (IoT) communication systems. For example, the technical solutions can be applied to a narrow band internet of things (NB-IoT) communication system. For another example, the technical solutions can be applied to an ambient IoT (A-IoT) communication system.

[0036] FIG. 1 shows an example of a system architecture diagram of a communication system 100 to which the embodiments of the present application are applicable. The communication system 100 can include a network device 110 and a terminal device 120. The network device 110 can be a device that communicates with the terminal device 120. The network device 110 can provide network coverage for a specific geographic area, and can communicate with the terminal device 120 located in the coverage area. The terminal device 120 can access a network (such as a wireless network) through the network device 110. Optionally, the wireless communication system 100 can also include a network controller, a mobile management entity, and other network entities, which are not limited in the embodiments of the present application.

[0037] The terminal device in the embodiments of the present application can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user apparatus. The terminal device in the embodiments of the present application can refer to a device that provides voice and / or data connectivity for a user, and can be used to connect people, things and machines, such as handheld devices with wireless connection function, vehicle-mounted devices, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity, which provides sidelink signals between terminal devices in vehicle to everything (V2X) or device to device (D2D), etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and the smart home device communicate with each other without relaying the communication signals through the base station.

[0038] In some embodiments, the terminal device can also be an A-IoT device to meet the needs in some scenarios.

[0039] The network device in the embodiments of the present application can also be an access network device or a radio access network device, for example, the network device can be a base station. The network device in the embodiments of the present application can refer to a radio access network (RAN) node or device that accesses a terminal device to a wireless network. The base station can broadly cover various names in the following or can be replaced by the following names, for example: node B (NodeB), evolved node B (eNB), next generation node B (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), auxiliary station (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, modem or chip used in the foregoing devices or apparatuses. The base station can also be a mobile switching center and a device that performs the function of a base station in device-to-device (D2D), V2X, M2M communication, a network side device in a 6G network, a device that performs the function of a base station in a future communication system, etc. The base station can support networks of the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form of the network device.

[0040] The base station can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, the helicopter or the drone can be configured to act as a device that communicates with another base station.

[0041] In some deployments, the network device in the embodiments of the present application can refer to a CU or a DU; or the network device includes a CU and a DU. The gNB can also include an AAU.

[0042] The network device and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water; and can also be deployed on airplanes, balloons and satellites in the air. The scene in which the network device and the terminal device are located is not limited in the embodiments of the present application.

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

[0044] FIG. 1 exemplarily shows one network device 110 and two terminal devices 120. Optionally, the communication system 100 can include multiple network devices 110, and the communication system 100 can also include other numbers of terminal devices 120.

[0045] It should be understood that the devices with communication functions in the network / system in the embodiments of the present application can be referred to as communication devices. Taking the communication system 100 shown in FIG. 1 as an example, the communication devices can include the network devices 110 and the terminal devices 120 with communication functions, which can be the specific devices described above, and details are not described herein again. The communication devices can also include other devices in the communication system 100, such as network controllers, mobile management entities and other network entities, and the embodiments of the present application do not limit the same.

[0046] The environment Internet of Things (IoT) communication system is taken as an example in the following description. It can be understood that the technical solutions of the embodiments of the present application can also be extended to other communication systems with the same functions.

[0047] Ambient Internet of Things (A-IoT)

[0048] The environment Internet of Things (IoT) communication can use power harvesting and back scattering communication technology for communication, or can use active emission for communication. The terminal device in the A-IoT system can be referred to as an A-IoT device. The A-IoT device refers to an IoT device that uses various environmental energies, such as wireless radio frequency energy, light energy, solar energy, thermal energy, mechanical energy and various environmental energies to drive itself. Such a device can have no energy storage capability, or can have very limited energy storage capability (such as using a capacitor with a capacity of several tens of uF). Compared with the traditional IoT device, the A-IoT device has many advantages such as no conventional battery, no maintenance, small size, low complexity, low cost and long service life.

[0049] The environmental IoT communication network can be composed of network devices 210 and A-IoT devices 220, as shown in FIG. 2. The network devices 210 are used to send wireless energizing signals, downlink communication signals to the A-IoT devices 220, and receive backscattering signals from the A-IoT devices. As shown in FIG. 2, a basic A-IoT device 220 can include an energy harvesting module, a backscattering communication module, and a low-power computing module. The A-IoT device 220 can also have a sensor for obtaining environmental temperature, humidity, and other sensing data. In addition, the A-IoT device can also have a memory for storing some basic information (such as item identification, etc.).

[0050] The energy harvesting technology and the backscattering communication technology in the environmental IoT communication will be introduced below in conjunction with FIGS. 3-5.

[0051] FIG. 3 takes radio frequency energy harvesting as an example for introduction. As shown in FIG. 3, the energy harvesting module is based on the principle of electromagnetic induction to harvest the energy of the space electromagnetic wave, and then obtain the energy required to drive the A-IoT device to work. For example, the energy harvesting module can be used to drive the low-power demodulation and modulation modules, sensors, memories, and other modules in the A-IoT device to work. Therefore, the A-IoT device does not need a traditional battery.

[0052] FIG. 4 is a schematic diagram of a backscattering communication. As shown in FIG. 4, the A-IoT device 420 receives the wireless signal sent by the network device 410. After receiving the wireless signal, the A-IoT device 420 modulates the wireless signal to load the information to be sent. Then, the A-IoT device 420 radiates the modulated signal from the antenna. The above information transmission process is called backscattering communication.

[0053] The backscattering and load modulation functions are closely related. Load modulation adjusts and controls the circuit parameters of the oscillation loop of the A-IoT device according to the beat of the data stream, so that the size of the impedance and other parameters change, thereby completing the modulation. The load modulation technology mainly includes resistance load modulation and capacitance load modulation.

[0054] In resistance load modulation, a resistor is connected in parallel with the load, which is turned on or off based on the control of the binary data stream, as shown in FIG. 5. The on-off of the resistor will cause the change of the circuit voltage, so as to realize amplitude shift keying (ASK), that is, the modulation and transmission of the signal by adjusting the amplitude of the backscattering signal of the A-IoT device. Similarly, in the capacitive load modulation, the on-off of the capacitor can realize the change of the circuit resonance frequency, so as to realize frequency shift keying (FSK), that is, the modulation and transmission of the signal by adjusting the working frequency of the backscattering signal of the A-IoT device.

[0055] It can be seen that the A-IoT device modulates the incoming signal by means of load modulation, so as to realize backscattering communication. Therefore, the A-IoT device has the following advantages:

[0056] Firstly, the A-IoT device does not actively emit signals, and therefore does not need a complex radio frequency link, such as a power amplifier (PA) and a radio frequency filter.

[0057] Secondly, the A-IoT device does not need to actively generate high-frequency signals, and therefore does not need a high-frequency crystal oscillator.

[0058] Thirdly, by means of backscattering communication, the signal transmission of the A-IoT device does not need to consume the energy of the A-IoT device itself.

[0059] Due to the advantages of low cost, zero power consumption, and small size, the A-IoT device can be widely applied in various industries. For example, the A-IoT device can be applied in the fields of logistics, intelligent warehousing, smart agriculture, energy and power, and industrial internet. Alternatively, the A-IoT device can also be applied in the fields of smart wearable and smart home.

[0060] Hereinafter, various classification methods of the A-IoT device are introduced.

[0061] In the A-IoT communication technology, the A-IoT device can be divided into three categories based on the energy source and the energy usage mode of the A-IoT device: passive A-IoT device, semi-passive A-IoT device, and active A-IoT device.

[0062] The passive A-IoT device usually does not need to be equipped with a battery. When the passive A-IoT device is close to the network device, the passive A-IoT device is in the near field range formed by the antenna radiation of the network device. At this time, the antenna of the passive A-IoT device can generate an induced current through electromagnetic induction, and the induced current can power the low-power chip circuit of the passive A-IoT device to drive the low-power chip circuit. Through this way, the demodulation of the forward link signal and the modulation of the backward link signal can be realized. For the backscatter link, the passive A-IoT device can use the backscatter implementation to transmit signals.

[0063] In some implementations, the forward link in the above can be a downlink, that is, a link from the network device to the A-IoT device; and the backward link can be an uplink, that is, a link from the A-IoT device to the network device.

[0064] As can be seen from the above introduction, the passive A-IoT device does not need to be equipped with a battery to drive, whether it is based on the transmission process of the forward link or the transmission process of the backward link, and is a truly A-IoT device. The passive A-IoT device does not need a battery, and the radio frequency circuit and the baseband circuit are very simple. For example, the passive A-IoT device does not need a low noise amplifier (LNA), a PA, a crystal oscillator, an analog-to-digital converter (ADC), and the like, and therefore has many advantages such as small size, light weight, very low price, and long service life.

[0065] In some implementations, the passive A-IoT device described above can be an electronic tag, and correspondingly, the network device can be a reader of a radio frequency identification (RFID) system, for reading the content in the electronic tag and / or for changing the content in the electronic tag.

[0066] The semi-passive A-IoT device itself does not install a conventional battery, but can use an energy harvesting module to harvest energy, and store the harvested energy in an energy storage unit (such as a capacitor). After the energy storage unit obtains energy, it can drive the low-power chip circuit of the A-IoT device to realize the demodulation of the forward link signal and the modulation of the backward link signal, and the like. For the backscatter link, the semi-passive A-IoT device can use the backscatter implementation to transmit signals.

[0067] In some implementations, the semi-passive A-IoT device can use a radio frequency (RF) energy harvesting module to harvest radio wave energy. In other implementations, the semi-passive A-IoT device can also use a solar energy / light energy / thermal energy / kinetic energy harvesting module to harvest corresponding energy.

[0068] As can be seen from the foregoing, the semi-passive A-IoT device does not need to be built-in with a battery to drive, whether based on a forward link transmission process or a reverse link transmission process. Although the energy is stored in a capacitor during operation, the energy is derived from the radio energy harvested by the energy harvesting module, and thus is a truly A-IoT device. As can be seen, the semi-passive A-IoT device inherits many advantages of the passive A-IoT device, and also has many advantages such as small size, light weight, very low price, long service life, and the like.

[0069] The active A-IoT device can be built-in with a battery. The battery can supply energy for the active A-IoT device to drive the low-power chip circuit of the active A-IoT device. The A-IoT device used in some scenarios can be an active A-IoT device. The battery in the active A-IoT device can implement the demodulation of the forward link signal by the device, and the modulation of the backward link signal, and the like. For the backscatter link, the active A-IoT device uses a backscatter implementation to transmit signals. Therefore, the low power consumption of this type of device is mainly embodied in that the signal transmission of the reverse link does not need to consume the power of the terminal itself, but uses the backscatter mode.

[0070] In some implementations, the battery built-in in the active A-IoT device can be a conventional battery, such as a dry battery, a rechargeable lithium battery, and the like.

[0071] As can be seen from the foregoing, although the active A-IoT device uses a battery, due to the use of ultra-low power consumption communication technology, the power consumption is very low, and thus the working life of the battery can be greatly improved compared to related technologies.

[0072] For the active A-IoT device, power can be supplied by the built-in battery, and thus the communication distance of the active A-IoT device can be increased, and the reliability of the communication can be improved. Therefore, the active A-IoT device can be applied in some scenarios with relatively high requirements on the communication distance, reading latency, and the like.

[0073] In some implementations, the active A-IoT device described above can be an electronic tag, and the network device can be a wireless RFID reader. In this case, the built-in battery can supply power to the RFID chip in the electronic tag to increase the read-write distance between the RFID reader and the electronic tag. On the other hand, the built-in battery can supply power to the RFID chip in the electronic tag to shorten the read-write latency of the RFID reader to the electronic tag, which is conducive to improving the reliability of communication.

[0074] In addition to classifying A-IoT devices based on energy sources and energy usage, A-IoT devices can also be classified based on transmitter types. Like other IoT services, the service type of A-IoT will also be mainly industry services. Therefore, A-IoT devices can be classified into three categories based on transmitter types: A-IoT devices based on backscatter, A-IoT devices based on active transmitters, and A-IoT devices with both backscatter and active transmitters.

[0075] A-IoT devices based on backscatter use the backscatter method described above to transmit uplink data. Such devices do not have an active transmitter for active transmission, but only have a backscatter transmitter. Therefore, when such terminal devices transmit data, the network device needs to provide a carrier, and the terminal devices perform backscatter based on the carrier to achieve data transmission.

[0076] A-IoT devices based on active transmitters use active transmitters with active transmission capabilities to transmit uplink data. Such A-IoT devices can transmit data using their own active transmitters when transmitting data, without the need for the network device to provide a carrier. Active transmitters suitable for A-IoT devices can be, for example, ultra-low-power ASK, ultra-low-power FSK transmitters, etc. Based on current implementations, the overall power consumption of such transmitters can be reduced to 400-600 uw when transmitting a 100 uw signal.

[0077] A-IoT devices with both backscatter and active transmitters can support both backscatter and active transmitters. Such A-IoT devices can determine which type of uplink signal transmission to use, i.e., backscatter or active transmitter for active transmission, based on different situations (such as the amount of power, available environmental energy), or based on the scheduling of the network device.

[0078] A-IoT device can also support intermediate frequency (IF) receiver or zero intermediate frequency (ZIF) receiver. An example of the structure of an intermediate frequency receiver is shown in FIG. 6, and an example of the structure of a zero intermediate frequency receiver is shown in FIG. 7. For an intermediate frequency receiver, the device combines the received radio frequency signal with a local oscillation signal through a mixer to generate a difference frequency, i.e., an intermediate frequency signal. This intermediate frequency signal usually has a lower frequency and is easier to process and amplify. A zero intermediate frequency receiver can directly convert the signal to the baseband, thereby avoiding the problem of image frequency suppression. As can be seen from a comparison of FIG. 6 and FIG. 7, the zero intermediate frequency receiver simplifies the circuit design, reduces the cost and size, but may require more complex baseband processing. As can be seen, both the intermediate frequency receiver and the zero intermediate frequency receiver require the receiving device to generate a local oscillation signal of a specific frequency, and moreover, the frequency of the local oscillation signal required by the zero intermediate frequency receiver is closer to the received radio frequency signal.

[0079] Low power internet of things based on cellular network

[0080] Cellular internet of things technology is booming, and the 3rd generation partnership project (3GPP) has standardized NB-IoT, machine type communication (MTC), reduced capability (RedCap), and other internet of things technologies. However, there are still many scenarios where internet of things communication needs cannot be met, for example:

[0081] First, harsh communication environment

[0082] Some internet of things scenarios may face extreme environments such as high temperature, extremely low temperature, high humidity, high pressure, high radiation, or high-speed motion. For example, ultra-high voltage substations, high-speed train track monitoring, high-cold environment monitoring, industrial production lines, etc. In these scenarios, due to the working environment limitations of conventional power supplies, existing internet of things terminals will not be able to work. In addition, extreme working environments are also not conducive to the maintenance of the internet of things, such as replacing the battery.

[0083] Second, extremely small terminal form factor requirement

[0084] Some internet of things communication scenarios, such as food traceability, commodity circulation, and smart wearables, require terminals to have extremely small sizes to facilitate use in these scenarios. For example, internet of things terminals for commodity management in the circulation link are usually in the form of electronic tags, which are embedded in commodity packaging in a very small form factor. For another example, lightweight wearable devices can meet user needs while improving user experience.

[0085] Third, the demand of very low cost IoT communication

[0086] Many IoT communication scenarios require the cost of IoT terminal to be low enough to enhance the competitiveness relative to other alternative technologies. For example, in logistics or warehouse scenarios, in order to facilitate the management of a large number of circulating goods, an IoT terminal can be attached to each item, so as to complete the accurate management of the whole process and whole cycle of logistics through the communication between the terminal and the logistics network. These scenarios require the price of the IoT terminal to be competitive enough.

[0087] Therefore, in order to cover these unmet IoT communication needs, there is a need to develop a very low cost, very small size, battery-free / maintenance-free IoT in the cellular network, and the environmental IoT can exactly meet this demand.

[0088] Based on the discussion of A-IoT application scenarios by 3GPP SA1, A-IoT can be used in at least the following four scenarios:

[0089] Scenario one: object identification, such as logistics, production line product management, supply chain management;

[0090] Scenario two: environmental monitoring, such as temperature, humidity, and harmful gas monitoring of working environment and natural environment;

[0091] Scenario three: positioning, such as indoor positioning, intelligent search for objects, and production line object positioning;

[0092] Scenario four: intelligent control, such as intelligent control of various appliances in smart home (turning on / off air conditioner, adjusting temperature), and intelligent control of various facilities in agricultural greenhouse (automatic irrigation, fertilization).

[0093] In the low-power IoT based on the cellular network, the A-IoT device can transceive A-IoT control / data / signal from the reader. The reader can be a base station or an intermediate node, as shown in FIGS. 8 and 9. If the A-IoT device sends A-IoT control / data / signal to the reader through backscattering, a carrier needs to be provided to the A-IoT device, and the node providing the carrier can be the reader or another node. In addition, the A-IoT device can also send A-IoT control / data / signal to the reader through active transmission.

[0094] Referring to FIG. 8, the A-IoT device 820 can communicate bi-directionally with the base station 810. The A-IoT device 820 can send A-IoT control / data / signal to the base station 810 according to the provided carrier.

[0095] Referring to FIG. 9, the A-IoT device 920 can communicate with an intermediate node 930 in both directions. The A-IoT device 920 can send A-IoT control / data / signal to the intermediate node 930 according to the provided carrier. The intermediate node 930 can forward data or signal between the base station 910 and the A-IoT device 920.

[0096] In the ambient IoT, for an A-IoT device supporting an intermediate frequency or zero intermediate frequency receiver, when receiving a message sent by another device, it is necessary to determine the carrier frequency of the message and receive the message. That is, the A-IoT device needs to determine the receiving frequency of the message. For example, the A-IoT device in FIG. 8 and FIG. 9 needs to determine the carrier frequency used by the reader to send the message when receiving the message sent by the reader.

[0097] However, how the A-IoT device determines the carrier frequency of the message sent by another device is a problem that has not yet been solved.

[0098] It should be noted that the above-mentioned problem of how the A-IoT device determines the receiving frequency of the message in the ambient IoT is only an example, and the embodiments of the present application can be applied to any type of communication device that needs to determine the receiving frequency of the message in the communication scenario.

[0099] Based on this, the embodiments of the present application provide a communication method. In the method, a first device supports one or more receiving frequencies. The first device can receive or detect a message sent by a second device at a first frequency of the one or more receiving frequencies. Specifically, the embodiments of the present application provide a method for a low-power device to determine the receiving frequency of the message, and to receive the related message in time. According to the method proposed in the present application, frequency division multiplexing between different devices can be achieved, the system capacity can be improved, and the implementation complexity can be reduced.

[0100] The embodiments of the present application will be described in detail below. FIG. 10 is a schematic flowchart of a communication method provided by the embodiments of the present application. FIG. 10 is introduced from the perspective of the interaction between the first device and the second device. The first device can be a low-power or zero-power communication device. The second device can be a communication device that sends a message to the first device.

[0101] In some embodiments, the first device can be a communication device that communicates using energy harvesting and / or backscatter communication technology. Optionally, the first device can use various environmental energy through energy harvesting. Optionally, the first device does not actively emit signals and does not need to actively generate high-frequency signals. Optionally, the first device can transmit signals by means of backscatter communication. Optionally, the first device can have no energy storage capability or have very limited energy storage capability.

[0102] In some embodiments, the first device can be a terminal device in a low power internet of things, e.g., a low power internet of things based on a cellular network. In some implementations, the first device can be a terminal device in an ambient internet of things. In other words, the first device is an A-IoT device. The first device can be any one of the passive A-IoT device, the semi-passive A-IoT device, or the active A-IoT device as described above.

[0103] As an example, as a low power communication device, the first device is only a device in the terminal devices that has a higher requirement on power consumption.

[0104] The first device can include different modules according to the device usage. For example, the first device can include an energy harvesting module and a backscatter communication module. As another example, the first device can include an energy harvesting module, a backscatter communication module, and one or more of the following modules: a low power computation module, a sensor module, and a memory.

[0105] The second device is any kind of communication device that sends a message to the first device. In some embodiments, the second device can be a network device, e.g., a base station. In some embodiments, the second device can be an intermediate node between the network device and the first device. The second device can convert data between the network device and the first device. In some embodiments, the second device can be a terminal device, e.g., a UE.

[0106] In some implementations, the second device is a reader. The reader can also be referred to as a reader-writer. The first device can be a target device that is read by the reader. In some implementations, the second device can be any one of a plurality of readers. The second device can read information from the first device. The first device can be a communication device that is read by the second device.

[0107] The first device needs a carrier provided by another communication device to send relevant control / data / signal. In some embodiments, the node that provides the carrier to the first device can be the second device. That is, the second device not only sends a message to the first device, but also provides a carrier for the first device to perform feedback or backscatter communication. In some embodiments, the node that provides the carrier to the first device can be another communication device other than the second device. For example, when the second device is a terminal device that performs bidirectional communication with the first device, the node that provides the carrier to the first device can be a network device or a terminal device other than the second device.

[0108] In some embodiments, the first device is one of a plurality of A-IoT devices. The second device can send a message to different A-IoT devices, or a plurality of communication devices including the second device can send a message to the plurality of A-IoT devices. In some embodiments, the first device is one of a plurality of A-IoT devices. The second device can send a message to different A-IoT devices, or a plurality of communication devices including the second device can send a message to the plurality of A-IoT devices.

[0109] When the second device is a reader, the first device can be one of a plurality of communication devices being read by the second device. For example, the plurality of communication devices being read by the second device are a plurality of given A-IoT devices. The first device is any given A-IoT device.

[0110] Referring to FIG. 10, at step S1010, the first device receives or detects a first message sent by the second device.

[0111] The first message can be any message sent by the second device to the first device. When the first device is an A-IoT device and the second device is a reader, the first message can be a message sent by the reader to the A-IoT device. In this scenario, the first message can be referred to as a reader-to-device (R2D) message, and can also be referred to as a R2D transmission or R2D transmission.

[0112] In some embodiments, the first message can be a message sent after the first device establishes communication with the second device, or can be a message used between the first device and the second device to establish communication. In some implementations, the first message can include multiple types of messages.

[0113] As an example, the first message can be an initial message sent by the second device. The initial message can be the first message that the first device needs to receive from the second device after the first device is started, or can be a paging message used to page the first device. The paging message used to page the first device can also be referred to as an A-IoT paging message. For example, the first message can be an initial R2D message.

[0114] As an example, the first message can be a second message sent by the second device to the first device. The second message can indicate that the first device and the second device will perform subsequent message transmission. For example, the second message can be a second R2D message after the initial message.

[0115] As an example, the first message can be one or more messages sent by the second device to the first device, in addition to the initial message and the second message. For example, the one or more messages can be R2D messages used by the first device and the second device to communicate.

[0116] The first device receives or detects a first message at a first frequency (the first message can be a message sent by a second device at a frequency corresponding to the first frequency, which can be equal to the first frequency or not equal to the first frequency but close to the first frequency). The first device can directly receive the first message at the first frequency or detect the first message at the first frequency. For example, the first device can detect the R2D transmission at the first frequency according to the indication.

[0117] The first frequency is one of one or more receiving frequencies supported by the first device. The receiving frequency supported by the first device can also be referred to as a carrier frequency. When the first device supports one receiving frequency, the first frequency is the receiving frequency, i.e., the first device only supports the first frequency. When the first device supports multiple receiving frequencies, the first frequency is one of the multiple receiving frequencies.

[0118] In some embodiments, the one or more receiving frequencies supported by the first device can be receiving frequencies in a first set of receiving frequencies. The first set of receiving frequencies is, for example, set G. The first set of receiving frequencies can be determined by protocol predefined information or preconfigured information.

[0119] As an example, the first set of receiving frequencies can be explicitly specified in a relevant standard. As an example, the first set of receiving frequencies can be preconfigured by a network device or preconfigured by higher layer signaling.

[0120] In some implementations, when the first device only supports the first frequency, the first frequency is one of the first set of receiving frequencies. For example, the first frequency supported by the first device is one receiving frequency in a specific set of multiple receiving frequencies G.

[0121] In some implementations, when the first device supports multiple receiving frequencies, the multiple receiving frequencies can belong to the first set of receiving frequencies, and the first frequency is one of the first set of receiving frequencies. For example, when the multiple receiving frequencies supported by the first device belong to set G, the total number of receiving frequencies supported by the first device can be less than or equal to the total number of frequencies in set G.

[0122] In some embodiments, when the first device only supports the first frequency, multiple A-IoT devices including the first device can support different receiving frequencies. When the first device is one of the multiple A-IoT devices, if each A-IoT device only supports one receiving frequency, different A-IoT devices can support different receiving frequencies. For example, when the multiple A-IoT devices each only support one receiving frequency, different A-IoT devices can support different receiving frequencies in set G.

[0123] In some implementations, the multiple devices including the first device can each support a different receive frequency.

[0124] In some implementations, at least two of the multiple A-IoT devices can support different receive frequencies.

[0125] In some embodiments, when the first device supports multiple frequencies, the multiple receive frequencies supported by the multiple low-power devices including the first device can also be different. When the first device is one of the multiple A-IoT devices, if each A-IoT device supports multiple receive frequencies, different A-IoT devices can each support a different set of receive frequencies.

[0126] In some implementations, at least two of the multiple A-IoT devices can each support a different set of receive frequencies.

[0127] In some implementations, the two sets of receive frequencies supported by at least two of the multiple A-IoT devices can partially overlap or can not overlap at all.

[0128] In some embodiments, when the multiple devices including the first device each support multiple receive frequencies, the multiple receive frequencies should satisfy a specific spacing to avoid the first device receiving signals transmitted by the second device to other devices. For example, when the multiple devices each support only one receive frequency, the multiple receive frequencies supported by the multiple devices should satisfy a specific spacing. For another example, when the multiple devices each support multiple receive frequencies, the multiple receive frequencies supported by different devices should satisfy a specific spacing.

[0129] In some implementations, the spacing between the multiple receive frequencies is greater than or equal to a first frequency spacing. As an example, the first frequency spacing should be greater than a filter cutoff bandwidth that the first device is capable of supporting. For example, when the first device supports an IF receiver, the first frequency spacing should be greater than a maximum intermediate frequency filter cutoff bandwidth that the first device is capable of supporting. For another example, when the first device supports a ZIF receiver, the first frequency spacing should be greater than a maximum baseband filter cutoff bandwidth that the first device is capable of supporting.

[0130] As an example, the spacing between at least two of the multiple receive frequencies is greater than or equal to the first frequency spacing.

[0131] In some implementations, the multiple receiving frequencies supported by the multiple devices can be located within the same channel bandwidth or within different channel bandwidths. For example, the multiple receiving frequencies supported by the multiple devices can be located within one carrier bandwidth. For another example, the multiple receiving frequency sets G described above can be located within one carrier bandwidth, as shown in FIG. 11. Referring to FIG. 11, the carrier bandwidth can include N receiving frequencies, i.e., receiving frequency 0 to receiving frequency N-1, i.e., f0to fN-1. N-1 .

[0132] In some embodiments, the one or more receiving frequencies supported by the first device can be located within the same channel bandwidth. For example, the one or more receiving frequencies supported by the first device can be located within one carrier bandwidth.

[0133] In some embodiments, the one or more receiving frequencies supported by the first device can be located within different channel bandwidths. For example, when the first device supports multiple receiving frequencies, the multiple receiving frequencies can be located within multiple carrier bandwidths.

[0134] The one or more receiving frequencies supported by the first device can be used to receive the message transmitted by the second device. That is, the first device can receive the message through the one or more receiving frequencies. The message received through the one or more receiving frequencies can be any one or more of the first message, the second message, and the fourth message. The second device can transmit the message at a frequency corresponding to the one or more receiving frequencies supported by the first device. Therefore, the one or more receiving frequencies supported by the first device can correspond to the message transmission frequency of the second device. The frequency corresponding to the one or more receiving frequencies supported by the first device can be equal to the one or more receiving frequencies, or can be a frequency close to the one or more receiving frequencies.

[0135] In some implementations, when the second device is any one of the multiple readers, the second device can transmit R2D at a frequency corresponding to the one or more receiving frequencies supported by the first device.

[0136] In some embodiments, the one or more receiving frequencies supported by the first device are associated with the local oscillator frequency of the first device. That is, the receiving frequencies supported by the first device can be determined according to the local oscillator frequency of the first device. It can be understood that there can be a relatively large error in the local oscillator of the first device. When the local oscillator frequency is the expected value of the carrier frequency of the signal transmitted by the second device, the actual oscillation frequency generated by the first device has a certain deviation from the expected value.

[0137] The first device can determine the first frequency based on a variety of manners. In some implementations, when the first device only supports the first frequency, the first frequency can be determined based on protocol predefined information or preconfigured information. In some implementations, when the first device supports multiple receiving frequencies, the first frequency can be randomly selected by the first device from the multiple receiving frequencies. In some implementations, when the first device supports multiple receiving frequencies, the first frequency can be determined by an indication of the second device.

[0138] In some embodiments, when the first device only supports the first frequency, the first frequency can be predefined. Illustratively, the first device or the second device can determine the first frequency according to predefined information, and perform the transceiving of the first message on the first frequency.

[0139] In some embodiments, when the first device only supports the first frequency, the first frequency can be preconfigured. Illustratively, the first frequency can be preconfigured by a network device or preconfigured by high layer signaling. The first device or the second device can determine the carrier frequency for the transceiving of the first message according to the preconfigured information.

[0140] In some embodiments, the one or more receiving frequencies supported by the first device can be a default receiving frequency or a specific receiving frequency. For example, when the multiple receiving frequencies supported by the first device belong to a first receiving frequency set, the first device can support all the receiving frequencies in the first receiving frequency set by default. For another example, when one receiving frequency supported by the first device belongs to a first receiving frequency set, the one receiving frequency can be a specific receiving frequency in the first receiving frequency set corresponding to the first device.

[0141] In some embodiments, when the first device supports multiple receiving frequencies, the first device can randomly select at least one receiving frequency from the multiple supported receiving frequencies as the first frequency to detect the first message. That is, the first frequency can be randomly selected by the first device from the multiple receiving frequencies. For example, the first device can randomly select one from the multiple receiving frequencies after starting to detect R2D transmission.

[0142] In some embodiments, the first frequency can be determined based on indication information transmitted by the second device. For example, the first frequency can be indicated based on a second message transmitted by the second device. That is, the first device can receive other messages transmitted by the second device before receiving the first message. These other messages can indicate the first frequency used by the first device to receive the first message.

[0143] In some implementations, the second message can be an initial message sent by the second device to the first device. The initial message can be a paging message for paging the first device, or can be a first message that the first device needs to receive after the multiple devices including the first device are started. For example, the second message can be an initial R2D message. The first device receives subsequent R2D transmissions according to the first frequency indicated by the initial R2D message.

[0144] In the above implementations, since the second device cannot determine the second frequency at which the first device receives the second message, the second device can send the same second message at all frequencies corresponding to all the receiving frequencies that the first device can select.

[0145] In some implementations, the second message can be a second message sent by the second device after the initial message. For example, the first device can detect the initial R2D message and a second R2D message, and then receives subsequent R2D transmissions according to the indication of the second R2D message.

[0146] In some implementations, the second message can carry identity (ID) information of the first device.

[0147] In some embodiments, the frequency at which the first device receives the second message can be the second frequency. For example, the first device can first receive the second message at the second frequency, and then receive or detect the first message according to the indication of the first frequency in the second message.

[0148] In some embodiments, the first device can determine the second frequency at which the second message is received in a variety of ways. For example, the second frequency can be one of the one or more receiving frequencies supported by the first device. For another example, the second frequency can be a default or specific receiving frequency.

[0149] In some implementations, the second frequency can be the same as or different from the first frequency.

[0150] In some implementations, when the second frequency is one of the one or more receiving frequencies supported by the first device, the determination of the second frequency can refer to the determination of the first frequency. For example, when the first device only supports the first frequency, the second frequency is the same as the first frequency. For another example, when the first device supports multiple receiving frequencies, the second frequency can be one of the multiple receiving frequencies.

[0151] As an example, the second frequency at which the first device receives the second message can be randomly selected by the first device from a plurality of supported receiving frequencies. For example, the first device can randomly select one receiving frequency from the plurality of receiving frequencies as the second frequency, and detect the second message. The second message can indicate the first frequency. When the first frequency is different from the second frequency, the first device can switch to the first frequency indicated by the second message to receive the first message according to the indication of the second message.

[0152] As an example, the first device can inform the second device of one or more receiving frequencies supported by the first device in advance, so that the second device indicates the first frequency through the second message. For example, before receiving the second message, the first device can send a third message to the second device to inform the second device of the receiving frequencies supported by the first device. Accordingly, before sending the second message, the second device receives the third message from the first device.

[0153] Optionally, the third message can include first information. The first information can be used to indicate the plurality of receiving frequencies supported by the first device. Alternatively, the first information can be used to indicate one receiving frequency supported by the first device.

[0154] In the above example, for the first device, before sending the third message, the first device can also receive a fourth message sent by the second device to establish communication with the second device. Accordingly, before receiving the third message, the second device sends the fourth message to the first device.

[0155] Optionally, the fourth message can be an initial message sent by the second device to the first device. That is, the fourth message can be a paging message used to page the first device, or can be the first message that the first device needs to receive after starting up. For example, the fourth message can be an initial R2D message. The first device can send the third message to the second device after receiving the initial R2D message.

[0156] In some implementations, the second frequency at which the first device receives the second message can be a default receiving frequency. For example, after starting up, the first device can detect the second message on the default receiving frequency.

[0157] As an example, when the second frequency is the default receiving frequency, the second message can be an initial message sent by the second device to the first device. At this time, the second message can be a paging message used to page the first device, or can be the first message that the first device needs to receive after starting up.

[0158] In the above examples, the first device can receive the initial message sent by the second device. After receiving the initial message, the first device can receive or detect the first message according to the first frequency indicated in the initial message, or can choose to terminate the current process, in order to avoid too many devices detecting messages on the same first frequency at the same time.

[0159] As an implementation manner, after receiving the initial message, the first device can generate a random number, and then determine whether to switch to the first frequency or terminate the current process according to the random number. When the first device chooses to terminate the current process, the first device can reselect a receiving frequency to receive a new initial message.

[0160] As can be seen from the foregoing, the second device can be a network device or a terminal device. When the second device is a network device, the network device can directly configure the communication resource for sending the message to the first device. When the second device is a terminal device, the communication resource between the terminal device and the first device can be determined based on the scheduling of the network device.

[0161] In some implementation manners, the network device can allocate the resource for the terminal device to send the R2D message through physical layer or high layer signaling. The physical layer or high layer signaling can indicate the resource on one or more sending frequencies. For example, when the network device indicates the resource for the terminal device type reader through downlink control information (DCI) or radio resource control (RRC) layer signaling, the DCI can contain the indication information of the number of sending carriers and frequencies.

[0162] In some implementation manners, before sending the first message to the first device, the terminal device can send a fifth message to the network device. The fifth message is used to request a first resource, and the first resource is used for the terminal device to send a message to the first device on the frequency corresponding to the one or more receiving frequencies of the first device. The frequency corresponding to the one or more receiving frequencies of the first device can be equal to the one or more receiving frequencies, or can not be equal to the one or more receiving frequencies, but can be a frequency close to the one or more receiving frequencies.

[0163] As an example, the one or more receiving frequencies of the terminal device for sending a message to the first device are the one or more receiving frequencies supported by the first device. The terminal device can directly indicate the one or more receiving frequencies supported by the first device to the network device through the fifth message. Alternatively, the terminal device can send the fifth message to the network device after receiving the third message.

[0164] As an example, the multiple receiving frequencies indicated by the fifth message can include one or more receiving frequencies supported by the first device.

[0165] As an example, the first resource can include a carrier corresponding to one or more receiving frequencies supported by the first device.

[0166] The method that the first device determines the first frequency and receives or detects the first message at the first frequency is described above in combination with FIG. 10. As known from the above, the first frequency can be one receiving frequency supported by the first device only, or one of multiple receiving frequencies supported by the first device. In the following, the first device is taken as an A-IoT device, and the second device is taken as a reader as an example, and multiple embodiments are combined to exemplarily describe multiple determination methods of the first frequency.

[0167] Embodiment One

[0168] In this embodiment, the first device supports only one receiving frequency (i.e., the first frequency), but different devices can support different receiving frequencies. The receiving frequency supported by the first device is one of a specific multiple receiving frequency set G (i.e., the first receiving frequency set).

[0169] The set G can be defined by a standard or preconfigured, and different devices can support different receiving frequencies therein. In order to avoid receiving signals sent by the second device to other devices, a specific multiple receiving frequency (multiple receiving frequencies in the set G) should satisfy a specific interval, i.e., the first frequency interval. For example, the first frequency interval should be greater than the maximum intermediate frequency (IF receiver) or the filter cutoff bandwidth of the baseband (ZIF receiver) that the first device can support.

[0170] Optionally, the multiple receiving frequencies supported by different devices are located within the same channel bandwidth, for example, within one carrier bandwidth.

[0171] For any second device as a reader, R2D can be sent at a frequency corresponding to one or more receiving frequencies in the set G. The one or more receiving frequencies correspond to the R2D sending frequency of the second device. The frequency corresponding to the one or more receiving frequencies mentioned here can be equal to the one or more receiving frequencies, or not equal to the one or more receiving frequencies, but a frequency close to the one or more receiving frequencies.

[0172] If the second device is a terminal device, the terminal device can report one or more sending frequencies to the base station. That is, the terminal device can report the required carrier to the network device, and send R2D on one or more carriers according to the scheduling of the network device. As described above, before the terminal device sends the first message to the first device, the terminal device can send a fifth message to the network device to request the first resource. The first resource can be used for the terminal device to send a message to the first device on the frequency corresponding to the one or more receiving frequencies of the first device, and thus the frequency corresponding to the one or more receiving frequencies of the first device can also be referred to as the one or more sending frequencies.

[0173] The terminal device can determine the frequency corresponding to the one or more receiving frequencies of the first device according to the receiver type supported by the device. For example, if the first device supports a ZIF receiver, the frequency corresponding to the one or more receiving frequencies of the first device can be equal to the one or more receiving frequencies, and if it is an IF receiver, the frequency corresponding to the one or more receiving frequencies of the first device can not be equal to the one or more receiving frequencies, but needs to be relatively close to the one or more receiving frequencies, so as to ensure that the device can perform intermediate frequency reception.

[0174] The base station can allocate resources for the second device to send R2D through physical layer or high layer signaling. The physical layer or high layer signaling can indicate the first resource, that is, the resource on the one or more sending frequencies. For example, when the base station indicates the resource for the terminal device type reader through DCI or RRC layer signaling, the DCI can contain indication information of the number of sending carriers and frequencies.

[0175] In embodiment one, regardless of whether the device supports IF or ZIF, the R2D sending mode between the reader and a specific device is the same. That is, there is no need to introduce a special interface design for supporting IF or ZIF reception, thereby simplifying the implementation of the reader and the first device.

[0176] Embodiment two

[0177] In this embodiment, the first device supports multiple receiving frequencies. After starting, the first device can randomly select one receiving frequency (i.e., the first frequency) from the multiple receiving frequencies to detect the R2D sending (i.e., the first message). The receiving frequency supported by the first device can belong to the set G. The total number of receiving frequencies supported by the first device can be less than or equal to the total number of frequencies in the set G.

[0178] The multiple receiving frequencies supported by different devices can be different. In order to avoid receiving signals sent by the second device to other devices, a specific interval should be met between the specific multiple receiving frequencies, for example, the first frequency interval in embodiment one.

[0179] For any first device being read, at least one detection R2D transmission can be randomly selected from the supported multiple receiving frequencies.

[0180] For any second device being a reader, the R2D can be transmitted on the frequency corresponding to the one or more receiving frequencies supported by the first device. In this scenario, the one or more receiving frequencies correspond to the R2D transmission frequency of the second device. The frequency corresponding to the one or more receiving frequencies of the first device can be equal to the one or more receiving frequencies, or not equal to the one or more receiving frequencies, but a frequency close to the one or more receiving frequencies.

[0181] The same as embodiment one, if the second device is a terminal device, the terminal device can report one or more expected transmission frequencies to the base station. As described above, before the terminal device transmits the first message to the first device, the terminal device can transmit a fifth message to the network device to request a first resource. The first resource can be used for the terminal device to transmit a message to the first device on the frequency corresponding to the one or more receiving frequencies of the first device, so the frequency corresponding to the one or more receiving frequencies can also be called one or more transmission frequencies.

[0182] The base station can allocate resources for the second device to transmit R2D through physical layer or high layer signaling. The physical layer or high layer signaling can indicate the first resource, that is, the resource on the one or more transmission frequencies. For example, when the base station indicates the resource to the reader of the terminal device type through DCI or RRC layer signaling. The DCI can contain the indication information of the number of transmission carriers and frequencies.

[0183] In this embodiment, since the second device cannot predict the possible receiving device on one transmission frequency, the initial message transmitted by the second device on the frequency corresponding to the receiving frequency that the first device can select should be the same. The initial message can be an A-IoT paging message, or the first message that needs to be received after the start of other devices.

[0184] In embodiment two, since the first device supports multiple receiving frequencies, through the random selection method, the balanced distribution of multiple devices on different frequencies can be realized, so as to realize the purpose of load balancing on multiple frequencies.

[0185] Embodiment three

[0186] In this embodiment, the first device supports multiple carrier receiving frequencies. After starting up, the first device can randomly select one receiving frequency (i.e. the second frequency) from the multiple receiving frequencies to detect the initial R2D message and the second R2D message. Then, the first device can receive the following R2D transmission according to the indication of the second R2D message. That is, the first device can switch to the frequency (i.e. the first frequency) indicated in the second R2D message to receive the following R2D transmission.

[0187] Different from embodiment two, for the first device, at least one receiving frequency can be randomly selected from the multiple supported receiving frequencies to detect the initial message and the following R2D message (i.e. the second R2D message) transmitted by the second device. That is, the first device can receive the initial R2D message and the second R2D message transmitted by the second device on the second frequency. The initial R2D message can be an A-IoT paging message, or the first message that the first device needs to receive after starting up. The second R2D message can indicate the first frequency.

[0188] Optionally, the first device can send a third message to the second device after receiving the initial R2D message. The receiving frequency information supported by the first device can be carried in the third message sent by the first device to the second device. That is, before sending the second R2D message, the second device can receive the third message sent by the first device to determine the receiving frequency information supported by the first device and indicate the first frequency.

[0189] Optionally, the first device can support all receiving frequencies in the set G by default, in which case the receiving frequency information can not be carried in the third message. Alternatively, the first device can send the third message.

[0190] The second R2D message is the second message described above. The second device can indicate a receiving frequency different from the second frequency through the second R2D message. The first device should switch to the receiving frequency indicated in the second R2D message to receive the following R2D transmission.

[0191] Optionally, the second R2D message should carry the ID information specific to the first device.

[0192] Optionally, the initial R2D message detected by the first device on the randomly selected second frequency can be the fourth message described above. The R2D transmission received by the first device on the frequency indicated in the second R2D message can be the first message described above.

[0193] Other aspects are the same as those of embodiment two and will not be described again.

[0194] The second device in embodiment three can flexibly control the R2D receiving frequency of the first device, so as to better realize load balancing on multiple frequencies.

[0195] Embodiment four

[0196] In this embodiment, the first device supports multiple receiving frequencies. After starting, the first device randomly selects one receiving frequency from the multiple receiving frequencies as the second frequency to detect the initial R2D message. Then, the first device can receive the next R2D transmission according to the indication of the initial R2D message. That is, the first device can switch to the frequency (i.e., the first frequency) indicated in the initial R2D message to receive the next R2D transmission.

[0197] Unlike embodiment three, the first device in embodiment four can randomly select at least one receiving frequency from the supported multiple receiving frequencies to detect the initial message (i.e., the initial R2D message) sent by the second device. The initial message can be an A-IoT paging message, or the first message that needs to be received after the device starts.

[0198] In this embodiment, the first device can support all receiving frequencies in set G by default.

[0199] In the initial message, the second device can indicate a receiving frequency different from the second frequency selected by the first device as the first frequency. The first device should switch to the first frequency indicated in the initial message to receive the next R2D transmission (i.e., the first message).

[0200] Since the second device cannot determine the frequency at which the first device receives the initial message, the second device should send the same initial message on the frequencies corresponding to all receiving frequencies that the first device can select, so that the first device can receive the initial message on the randomly selected receiving frequency. The frequency corresponding to a receiving frequency can be equal to the receiving frequency, or not equal to the receiving frequency, but close to the receiving frequency.

[0201] After receiving the initial message, the first device can generate a random number, and then determine whether to switch to the indicated frequency to receive the next R2D message or terminate the current process according to the generated random number. If the first device decides to terminate the current process, it can randomly select a carrier frequency to receive the initial R2D message again. In this way, it can avoid too many devices switching to the frequency indicated in the initial message at the same time.

[0202] Optionally, the initial message detected by the first device on the randomly selected second frequency can be the second message described above, and the R2D transmission received on the frequency indicated in the initial R2D message can be the first message described above.

[0203] The other parts are the same as Embodiment Three, and are not described here.

[0204] The second device in Embodiment Four can disperse the devices to different R2D receiving frequencies before sending the second message, so as to optimize the load on different frequencies as early as possible.

[0205] Embodiment Five

[0206] In this embodiment, the first device supports multiple carrier frequencies. After starting, the first device detects an initial R2D message on a default receiving frequency (i.e., the second frequency). Then, the first device can receive the next R2D transmission according to the indication of the initial message. That is, the first device can switch to the frequency (i.e., the first frequency) indicated in the initial R2D message to receive the next R2D transmission.

[0207] Different from Embodiment Four, the R2D transmission detected by the first device on the default receiving frequency in Embodiment Five is the initial message sent by the second device. The initial message can be an A-IoT paging message, or the first message that needs to be received after the first device starts. In addition, the default receiving frequency can be a specific frequency belonging to the set G, which can be defined by a standard or preconfigured.

[0208] Optionally, the initial R2D message detected by the first device on the default receiving frequency is the second message described above for paging the first device, and the R2D transmission received on the frequency indicated by the initial R2D message can be the first message described above.

[0209] The other parts are the same as Embodiment Four, and are not described here.

[0210] In addition to the advantages of Embodiment Four, the second device in Embodiment Five only needs to send the initial R2D message on the default frequency, which is beneficial to reduce the power consumption of the second device.

[0211] The method embodiments of the present application are described in detail above in combination with FIG. 1 to FIG. 11, and the device embodiments of the present application are described in detail below in combination with FIG. 12 to FIG. 14. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, and therefore, the parts not described in detail can be referred to the method embodiments described above.

[0212] FIG. 12 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 1200 shown in FIG. 12 is any one of the first devices described above. As shown in FIG. 12, the communication device 1200 includes a communication module 1210.

[0213] The communication module 1210 can be configured to receive or detect a first message sent by the second device at a first frequency, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used for receiving messages sent by the second device.

[0214] Optionally, the first device only supports the first frequency.

[0215] Optionally, the first frequency is determined based on protocol predefined information or preconfigured information.

[0216] Optionally, the first device supports a plurality of receiving frequencies.

[0217] Optionally, the first frequency is randomly selected by the first device from the plurality of receiving frequencies.

[0218] Optionally, the first frequency is indicated based on a second message sent by the second device, a receiving frequency of the second message being a second frequency, the second frequency being one of the plurality of receiving frequencies, and the second frequency being the same as or different from the first frequency.

[0219] Optionally, the second frequency is randomly selected by the first device from the plurality of receiving frequencies.

[0220] Optionally, the communication module 1210 is further configured to, before receiving the second message, send a third message to the second device, the third message comprising first information, the first information being used to indicate the plurality of receiving frequencies supported by the first device.

[0221] Optionally, the communication module 1210 is further configured to, before sending the third message, receive a fourth message sent by the second device, the fourth message being a paging message used for paging the first device.

[0222] Optionally, the second frequency is a default receiving frequency of the first device.

[0223] Optionally, the second message is a paging message used for paging the first device.

[0224] Optionally, the second device is a terminal device, and a communication resource between the terminal device and the first device is determined based on scheduling of a network device.

[0225] Optionally, the one or more receiving frequencies are receiving frequencies in a first set of receiving frequencies, the first set of receiving frequencies being determined based on protocol predefined information or preconfigured information.

[0226] Optionally, the second device is a reader.

[0227] Optionally, the first device is an A-IoT device.

[0228] FIG. 13 is a schematic diagram of another communication device according to an embodiment of the present application. The communication device 1300 shown in FIG. 13 is any of the second devices described above. As shown in FIG. 13, the communication device 1300 includes a communication module 1310.

[0229] The communication module 1310 can be configured to send a first message to the first device on a frequency corresponding to a first frequency, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used to receive messages sent by the second device.

[0230] Optionally, the first device only supports the first frequency.

[0231] Optionally, the first frequency is determined based on protocol predefined information or preconfigured information.

[0232] Optionally, the first device supports a plurality of receiving frequencies.

[0233] Optionally, the first frequency is randomly selected by the first device from the plurality of receiving frequencies.

[0234] Optionally, the first frequency is indicated based on a second message sent by the second device, a receiving frequency of the second message being a second frequency, the second frequency being one of the plurality of receiving frequencies, and the second frequency being the same as or different from the first frequency.

[0235] Optionally, the second frequency is randomly selected by the first device from the plurality of receiving frequencies.

[0236] Optionally, the communication module 1310 is further configured to receive, by the second device from the first device, a third message before sending the second message, the third message including first information, the first information being used to indicate the plurality of receiving frequencies supported by the first device.

[0237] Optionally, the communication module is further configured to send, to the first device, a fourth message before receiving the third message, the fourth message being a paging message used to page the first device.

[0238] Optionally, the second frequency is a default receiving frequency of the first device.

[0239] Optionally, the second message is a paging message used to page the first device.

[0240] Optionally, the second device is a terminal device, and the sending unit is further configured to send, to a network device, a fifth message before the terminal device sends the first message, the fifth message being used to request a first resource, the first resource being used to send a message to the first device on a frequency corresponding to one or more receiving frequencies of the first device.

[0241] Optionally, the fifth message is used to indicate the one or more receiving frequencies.

[0242] Optionally, the one or more receiving frequencies are receiving frequencies in a first set of receiving frequencies, and the first set of receiving frequencies is determined by the protocol predefined information or the pre-configuration information.

[0243] Optionally, the second device is a reader.

[0244] Optionally, the first device is an A-IoT device.

[0245] FIG. 14 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application. The dashed line in FIG. 14 indicates that the unit or module is optional. The apparatus 1400 can be used to implement the method described in the above method embodiments. The apparatus 1400 can be a chip, a terminal device, or a network device.

[0246] The apparatus 1400 can include one or more processors 1410. The processor 1410 can support the apparatus 1400 to implement the method described in the foregoing method embodiments. The processor 1410 can be a general purpose processor or a dedicated processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, etc. The general purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0247] The apparatus 1400 can further include one or more memories 1420. The memory 1420 stores a program, which can be executed by the processor 1410, so that the processor 1410 performs the method described in the foregoing method embodiments. The memory 1420 can be independent of the processor 1410 or integrated in the processor 1410.

[0248] The apparatus 1400 can further include a transceiver 1430. The processor 1410 can communicate with other devices or chips through the transceiver 1430. For example, the processor 1410 can perform data transceiving with other devices or chips through the transceiver 1430.

[0249] The embodiment of the present application further provides a computer readable storage medium for storing a program. The computer readable storage medium can be applied to the terminal or the network device provided by the embodiment of the present application, and the program causes the computer to execute the method performed by the environment Internet of Things device, the terminal device or the network device in the various embodiments of the present application.

[0250] The embodiment of the present application further provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal or the network device provided by the embodiment of the present application, and the program causes the computer to execute the method performed by the environment Internet of Things device, the terminal device or the network device in the various embodiments of the present application.

[0251] The embodiment of the present application further provides a computer program. The computer program can be applied to the environment Internet of Things device, the terminal device or the network device provided by the embodiment of the present application, and the computer program causes the computer to execute the method performed by the terminal or the network device in the various embodiments of the present application.

[0252] It should be understood that the terms used in the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second" and the like in the specification and claims of the present application and the drawings are used to distinguish different objects, and are not used to describe a particular order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0253] In the embodiments of the present application, the "indication" mentioned can be direct indication, or indirect indication, or can be an indication with an associated relationship. For example, A indicates B, which can mean that B can be obtained by A; or A indirectly indicates B, for example, A indicates C, and B can be obtained by C; or A and B have an associated relationship.

[0254] In the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.

[0255] In the embodiments of the present application, the term "corresponding" can mean that there is a direct or indirect corresponding relationship between the two, or can mean that there is an associated relationship between the two, or can mean an indication and being indicated, configuration and being configured, etc.

[0256] In the embodiments of the present application, the "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables or other manners that can be used to indicate relevant information in devices (for example, including terminal devices and network devices), and the specific implementation manners are not limited in the present application. For example, the predefinition can refer to the definition in a protocol.

[0257] In the embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, for example, can include the LTE protocol, the NR protocol and the related protocol applied to the future communication system, and the present application is not limited to this.

[0258] In the embodiments of the present application, the term "and / or" is only used to describe the association relationship of the associated objects, and can represent three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in the present application generally represents an "or" relationship between the front and rear associated objects.

[0259] In various embodiments of the present application, the size of the serial number of the above processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0260] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic. The division of the units is only a logical function division. There can be another division manner in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed coupling or direct coupling or communication connection between each other can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or in other forms.

[0261] The units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiments of the present application.

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

[0263] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. 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 one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server, data center and the like integrated with one or more available media sets. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, digital video disc (DVD)) or semiconductor media (for example, solid state disk (SSD)) and the like.

[0264] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method characterized by comprising: The method comprises: receiving, by a first device, a first message sent by a second device at a first frequency, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used for receiving messages sent by the second device.

2. The method of claim 1, wherein, The first device only supports the first frequency.

3. The method of claim 2, wherein, The first frequency is determined based on protocol predefined information or preconfigured information.

4. The method of claim 1, wherein, The first device supports the plurality of receiving frequencies.

5. The method of claim 4, wherein, The first frequency is randomly selected by the first device from the plurality of receiving frequencies.

6. The method according to claim 4 or 5, characterized in that, The first frequency is indicated based on a second message sent by the second device, a receiving frequency of the second message being a second frequency, the second frequency being one of the plurality of receiving frequencies, and the second frequency being the same as or different from the first frequency.

7. The method of claim 6, wherein, The second frequency is randomly selected by the first device from the plurality of receiving frequencies.

8. The method of claim 7, wherein, The method further comprises: Before receiving the second message, the first device sends a third message to the second device, the third message comprising first information, the first information being used for indicating the plurality of receiving frequencies supported by the first device.

9. The method of claim 8, wherein, The method further comprises: Before sending the third message, the first device receives a fourth message sent by the second device, the fourth message being a paging message used for paging the first device.

10. The method of claim 6, wherein, The second frequency is a default receiving frequency of the first device.

11. The method of claim 6, 7 or 10, wherein, The second message is a paging message used for paging the first device.

12. The method according to any one of claims 1 to 11, characterized in that, The second device is a terminal device, and a communication resource between the terminal device and the first device is determined based on a scheduling of a network device.

13. The method according to any one of claims 1 to 12, characterized in that, The one or more receiving frequencies are receiving frequencies in a first set of receiving frequencies, the first set of receiving frequencies being determined based on protocol predefined information or preconfigured information.

14. The method according to any one of claims 1 to 13, characterized in that, The second device is a reader.

15. The method according to any one of claims 1 to 14, characterized in that, The first device is an A-IoT device.

16. A method of communication, comprising: The method comprises: sending, by a second device, a first message to a first device at a frequency corresponding to a first frequency, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used for receiving messages sent by the second device.

17. The method of claim 16, wherein, The first device only supports the first frequency.

18. The method of claim 17, wherein, The first frequency is determined based on protocol predefined information or preconfigured information.

19. The method of claim 16, wherein, The first device supports the plurality of receiving frequencies.

20. The method of claim 19, wherein, The first frequency is randomly selected by the first device from the plurality of receiving frequencies.

21. The method according to claim 19 or 20, characterized in that, The first frequency is indicated based on a second message sent by the second device, a receiving frequency of the second message being a second frequency, the second frequency being one of the plurality of receiving frequencies, and the second frequency being the same as or different from the first frequency.

22. The method of claim 21, wherein, The second frequency is randomly selected by the first device from the plurality of receiving frequencies.

23. The method of claim 22, wherein, The method further comprises: Before sending the second message, the second device receives a third message from the first device, the third message comprising first information, the first information being used for indicating the plurality of receiving frequencies supported by the first device.

24. The method of claim 23, wherein, The method further comprises: Before receiving the third message, the second device sends a fourth message to the first device, the fourth message being a paging message for paging the first device.

25. The method of claim 21, wherein, The second frequency is a default receiving frequency of the first device.

26. The method of claim 21, 22, or 25, wherein, The second message is a paging message for paging the first device.

27. The method of any one of claims 16-26, wherein, The second device is a terminal device, and the method further comprises: Before the terminal device sends the first message, the terminal device sends a fifth message to a network device, the fifth message being used for requesting a first resource, the first resource being used for sending a message to the first device on a frequency corresponding to one or more receiving frequencies of the first device.

28. The method of claim 27, wherein, The fifth message is used for indicating the one or more receiving frequencies.

29. The method of any one of claims 16 to 28, wherein, The one or more receiving frequencies are receiving frequencies in a first receiving frequency set, the first receiving frequency set being determined by protocol predefined information or preconfigured information.

30. The method of any one of claims 16-29, wherein, The second device is a reader.

31. The method of any one of claims 16-30, wherein, The first device is an A-IoT device.

32. A communications device, characterized by The communication device is a first device, and the communication device comprises: a communication module, configured to receive or detect a first message sent by a second device at a first frequency, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used for receiving a message sent by the second device.

33. The communication device of claim 32, wherein, The first device only supports the first frequency.

34. The communication device of claim 33, wherein, The first frequency is determined based on protocol predefined information or preconfigured information.

35. The communication device of claim 32, wherein, The first device supports the plurality of receiving frequencies.

36. The communication device of claim 35, wherein, The first frequency is randomly selected by the first device from the plurality of receiving frequencies.

37. The communication device of claim 35 or 36, wherein, The first frequency is indicated based on a second message sent by the second device, a receiving frequency of the second message being a second frequency, the second frequency being one of the plurality of receiving frequencies, and the second frequency being the same as or different from the first frequency.

38. The communication device of claim 37, wherein, The second frequency is randomly selected by the first device from the plurality of receiving frequencies.

39. The communication device of claim 38, wherein, The communication module is further configured to, before receiving the second message, send a third message to the second device, the third message comprising first information, the first information being used for indicating the plurality of receiving frequencies supported by the first device.

40. The communication device of claim 39, wherein, The communication module is further configured to, before sending the third message, receive a fourth message sent by the second device, the fourth message being a paging message for paging the first device.

41. The communications device of claim 37, wherein, The second frequency is a default receiving frequency of the first device.

42. The communications device of claims 37, 38, or 41, wherein, The second message is a paging message for paging the first device.

43. The communication device according to any one of claims 32 to 42, wherein, The second device is a terminal device, and a communication resource between the terminal device and the first device is determined based on scheduling of a network device.

44. The communication device according to any one of claims 32 to 43, wherein, The one or more receiving frequencies are receiving frequencies in a first receiving frequency set, the first receiving frequency set being determined by protocol predefined information or preconfigured information.

45. The communication device according to any one of claims 32 to 44, wherein, The second device is a reader.

46. The communication device of any one of claims 32 to 45, wherein, The first device is an A-IoT device.

47. A communications device, characterized by The communication device is a second device, and the communication device comprises: The communication module is configured to send a first message to the first device at a frequency corresponding to a first frequency, the first frequency being one of one or more receiving frequencies supported by the first device, and the one or more receiving frequencies being used to receive a message sent by the second device.

48. The communication device of claim 47, wherein, The first device only supports the first frequency.

49. The communication device of claim 48, wherein, The first frequency is determined based on protocol predefined information or pre-configuration information.

50. The communication device of claim 47, wherein, The first device supports the plurality of receiving frequencies.

51. The communication device of claim 50, wherein, The first frequency is randomly selected by the first device from the plurality of receiving frequencies.

52. The communication device of claim 50 or 51, wherein, The first frequency is indicated based on a second message sent by the second device, a receiving frequency of the second message being a second frequency, the second frequency being one of the plurality of receiving frequencies, and the second frequency being the same as or different from the first frequency.

53. The communication device of claim 52, wherein, The second frequency is randomly selected by the first device from the plurality of receiving frequencies.

54. The communication device of claim 53, wherein, The communication module is further configured to receive, from the first device, a third message before sending the second message, the third message comprising first information indicating the plurality of receiving frequencies supported by the first device.

55. The communication device of claim 54, wherein, The communication module is further configured to send, to the first device, a fourth message before receiving the third message, the fourth message being a paging message used to page the first device.

56. The communications device of claim 52, wherein The second frequency is a default receiving frequency of the first device.

57. The communications device of claims 52, 53, or 56, characterized by The second message is a paging message used to page the first device.

58. The communication device of any one of claims 47-57, wherein, The second device is a terminal device, and the sending unit is further configured to send, to a network device, a fifth message before the terminal device sends the first message, the fifth message being used to request a first resource, the first resource being used to send a message to the first device at a frequency corresponding to one or more receiving frequencies of the first device.

59. The communication device of claim 58, wherein, The fifth message is used to indicate the one or more receiving frequencies.

60. The communication device of any one of claims 47-59, wherein, The one or more receiving frequencies are receiving frequencies in a first set of receiving frequencies, the first set of receiving frequencies being determined based on protocol predefined information or pre-configuration information.

61. The communication device of any one of claims 47-60, wherein, The second device is a reader.

62. The communication device of any one of claims 47-61, wherein, The first device is an A-IoT device.

63. A communications device, characterized by A communication device comprising a transceiver, a memory, and a processor, the memory being configured to store a program, the processor being configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the communication device performs the method according to any one of claims 1-31.

64. An apparatus comprising: A device comprising a processor configured to invoke a program from a memory, so that the device performs the method according to any one of claims 1-31.

65. A chip, comprising: A chip comprising a processor configured to invoke a program from a memory, so that a device installed with the chip performs the method according to any one of claims 1-31.

66. A computer-readable storage medium, characterized in that, A computer program product having a program stored thereon, the program causing a computer to perform the method according to any one of claims 1-31.

67. A computer program product, characterised in that, A computer program product having a program stored thereon, the program causing a computer to perform the method according to any one of claims 1-31.

68. A computer program, characterized in that, The computer program product causes a computer to perform the method according to any one of claims 1-31.

Citation Information

Patent Citations

  • Radio frequency identification method and device

    CN114611535A

  • Device, method and equipment for determining working frequency of RFID tag of electric power facility

    CN116579355A

  • Adaptive configuration of multi-station tag backscatter

    CN117648938A

  • Communication method and device

    CN117676846A

  • Techniques for performing passive internet of things communications

    WO2023216213A1