Communication method and communication apparatus

Abstract

The application discloses a communication method and a communication device, and relates to the field of communication. The communication method comprises the following steps: receiving system parameters, including at least one of the following: SFS anchor group configuration, mapping rules between device identifiers and SFS anchor groups, preamble configuration; the SFS anchor group configuration comprises the number N of SFS anchor groups and an SFS anchor frequency list; the preamble configuration comprises a first preamble set for random access when performing time-sensitive DO-A services, and a second preamble set for random access when performing non-time-sensitive DO-A services; locking on an SFS anchor frequency of an SFS anchor group n according to a device identifier, SFS anchor group configuration and mapping rules; selecting a preamble in the first preamble set or the second preamble set for random access according to the type of DO-A services and the preamble configuration; and receiving a first frequency adjustment parameter and adjusting an uplink frequency according to the first frequency adjustment parameter.

Description

Technical Field

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

[0002] In IoT communication systems, to improve the sustainability and performance of wireless communication and reduce its power consumption, low-power ambient internet of things (AIoT) technology has been introduced, including IoT devices (such as AIoT devices) and AIoT readers. IoT devices and AIoT readers communicate via frequency division multiple access (FDMA). IoT devices need to have frequency adjustment capabilities to match the uplink frequency allocated by the AIoT reader. Current frequency adjustment methods either only produce small adjustment offsets, easily leading to network congestion, or require long adjustment times, resulting in communication delays. Summary of the Invention

[0003] This application provides a communication method and a communication device for reducing communication latency and avoiding network congestion.

[0004] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0005] Firstly, a communication method is provided, which can be executed by, for example, an Internet of Things (IoT) device, or by a component (such as a circuit, chip, or chip system) configured in the IoT device, or by a logic module or software capable of implementing all or part of the functions of the IoT device. This application does not limit this approach. The following description uses a first IoT device as an example.

[0006] The method includes: a first Internet of Things (IoT) device receiving broadcast system parameters, where the system parameters include at least one of the following: SFS anchor group configuration, mapping rule between device identifier and SFS anchor group, and preamble configuration. The SFS anchor group configuration includes the number N of SFS anchor groups. The preamble configuration includes a first preamble set and a second preamble set. The first preamble set is used for random access when the IoT device performs time-sensitive data origination autonomous (DO-A) service, and the second preamble set is used for random access when the IoT device performs non-time-sensitive DO-A service. The first IoT device locks onto the SFS anchor frequency of SFS anchor group n according to the device identifier, SFS anchor group configuration, and mapping rule, where 0 ≤ n < N. The first IoT device selects a preamble from the first preamble set or the second preamble set for random access according to the type of DO-A service and the preamble configuration. The first IoT device receives a first frequency adjustment parameter and adjusts the uplink frequency according to the first frequency adjustment parameter, where the first frequency adjustment parameter is used to indicate that the first IoT device performs SFS adjustment. The first frequency adjustment parameter is determined by the preamble and network congestion situation.

[0007] In the communication method provided by the embodiment of this application, the AIoT reader divides all IoT devices into N SFS anchor groups according to the mapping rule between the device identifier and the SFS anchor group, divides the uplink spectrum into N independent frequency bands, allocates one frequency band to each SFS anchor group, and uses the center frequency of each frequency band as the SFS anchor frequency. When the IoT device performs initial random access, it can autonomously calculate and lock onto the SFS anchor frequency of its所属 SFS anchor group, and can always perform SFS adjustment within the frequency band of the SFS anchor group. The adjustment time is very short and the communication delay is very small. Moreover, the preamble sent by the IoT device can indicate whether the type of DO-A service is time-sensitive DO-A service or non-time-sensitive DO-A service. The AIoT reader configures the frequency adjustment parameter for the IoT device in combination with the type of DO-A service and the network congestion situation to avoid network congestion.

[0008] In a possible implementation manner, the SFS anchor group configuration includes an SFS anchor frequency list; locking onto the SFS anchor frequency of SFS anchor group n according to the device identifier, SFS anchor group configuration, and mapping rule includes: performing an operation on the device identifier according to the mapping rule to obtain the index n of the SFS anchor group; looking up the SFS anchor frequency of SFS anchor group n from the SFS anchor frequency list and locking onto the SFS anchor frequency.

[0009] By dividing all IoT devices into N SFS anchor group groups, the uplink spectrum is divided into N independent frequency bands. Each SFS anchor group is allocated a frequency band, and IoT devices are mapped to the frequency band of one of the SFS anchor groups according to their device identifiers. This is equivalent to distributing all IoT devices evenly across the uplink spectrum, avoiding concentration at a single SFS anchor point and preventing congestion.

[0010] In one possible implementation, random access is performed by selecting a preamble from a first preamble set or a second preamble set, depending on the type of DO-A service and the preamble configuration. This includes: if time-sensitive DO-A service data is being sent, random access is performed by selecting a preamble from the first preamble set; if non-time-sensitive DO-A service data is being sent, random access is performed by selecting a preamble from the second preamble set.

[0011] IoT devices randomly access the network using preambles from different preamble sets to indicate whether the DO-A service is a time-sensitive DO-A service or a non-time-sensitive DO-A service, helping AIoT readers determine frequency adjustment parameters based on network congestion conditions.

[0012] In one possible implementation, the first frequency adjustment parameter includes at least one of the following: local oscillator (LO) adjustment indication information, target frequency, carrier frequency offset (CFO) calibration signal, and dwell time; the LO adjustment indication information is used to indicate whether the IoT device initiates LO adjustment; the target frequency is used to indicate the frequency of the SFS resources allocated to the IoT device; the CFO calibration signal is a reference signal used to measure and correct the CFO; and the dwell time is used to indicate the length of time the IoT device maintains a monitoring state on the target frequency after completing LO adjustment and transmitting data.

[0013] The LO adjustment indication information in the first frequency adjustment parameter indicates that the IoT device should not initiate LO adjustment. The target frequency in the first frequency adjustment parameter is the frequency within the frequency band of the SFS anchor group where the IoT device is located (at which point the IoT device needs SFS adjustment). The first frequency adjustment parameter may not include the CFO calibration signal and dwell time.

[0014] Secondly, a communication method is provided, which can be executed by an AIoT reader, or by a component (such as a circuit, chip, or chip system) configured in the AIoT reader, or by a logic module or software capable of implementing all or part of the functions of the AIoT reader. This application does not limit this approach. The following description uses an AIoT reader as an example.

[0015] The method includes: an AIoT reader sending system parameters, which include at least one of the following: SFS anchor group configuration, mapping rules between device identifiers and SFS anchor groups, and preamble configuration. The SFS anchor group configuration includes the number N of SFS anchor groups; the preamble configuration includes a first preamble set and a second preamble set. The first preamble set is used for random access when the IoT device performs time-sensitive DO-A services, and the second preamble set is used for random access when the IoT device performs non-time-sensitive DO-A services. The AIoT reader receives a preamble from either the first or second preamble set. Based on the received preamble and network congestion conditions, the AIoT reader sends a first frequency adjustment parameter to a first IoT device, which instructs the first IoT device to perform SFS adjustment.

[0016] The communication method provided in this application involves an AIoT reader dividing all IoT devices into N SFS anchor groups according to the mapping rules between device identifiers and SFS anchor groups. The uplink spectrum is divided into N independent frequency bands, and each SFS anchor group is assigned a frequency band, with the center frequency of each band serving as the SFS anchor frequency. During initial random access, IoT devices can autonomously calculate and lock the SFS anchor frequency of their respective SFS anchor group. Within the frequency band of the SFS anchor group, SFS adjustments can be performed continuously with very short adjustment times and minimal communication latency. Furthermore, the preamble sent by the IoT device can indicate whether the DO-A service is time-sensitive or non-time-sensitive. The AIoT reader configures frequency adjustment parameters for the IoT device based on the DO-A service type and network congestion conditions to avoid network congestion.

[0017] In one possible implementation, a first frequency adjustment parameter is sent to the first IoT device based on the received preamble and network congestion status, including: determining the DO-A type of the first IoT device based on the received preamble; determining the SFS anchor group n to which the first IoT device belongs based on the device identifier or the frequency band to which the uplink frequency belongs; and checking whether the first resource area of ​​the SFS anchor group n is congested.

[0018] If the first resource area of ​​SFS anchor group n is not congested, then an idle SFS resource is allocated as the target frequency for the first IoT device in the first resource area of ​​SFS anchor group n, and the first frequency adjustment parameters are sent to the first IoT device. This method allows the first IoT device to complete transmission solely through baseband digital frequency shifting without triggering LO adjustment, thereby maximizing system energy efficiency and maintaining low-power operation of the first IoT device by default.

[0019] If the first resource area of ​​SFS anchor group n is congested, and the DO-A type of the first IoT device is a time-sensitive DO-A service, then in the second resource area of ​​SFS anchor group n, an idle SFS resource is allocated as the target frequency for the first IoT device, and the first frequency adjustment parameter is sent to the first IoT device. This method ensures that even when the network is congested, the first IoT device does not need to adjust the LO to cause communication delays; the transmission of time-sensitive services can be guaranteed through SFS adjustment.

[0020] If the first resource area of ​​SFS anchor group n is congested, and the DO-A type of the first IoT device is a non-time-sensitive DO-A service, then at least one second IoT device that also belongs to SFS anchor group n is selected from the list of oldest aging states, and a second frequency adjustment parameter is sent to the second IoT device to instruct the second IoT device to temporarily move out of SFS anchor group n and perform LO adjustment; and the SFS resources released by the second IoT device are redistributed to the first IoT device as the target frequency, and a first frequency adjustment parameter is sent to the first IoT device.

[0021] This method searches for IoT devices belonging to the same SFS anchor group from the oldest aging state list, forces the IoT device to perform LO adjustment according to the CFO calibration signal, and frees up SFS resources for newly connected IoT devices. This design cleverly transforms the inherent signaling overhead of LO adjustment into the benefit of automatic aging state updates, effectively solving the problems of resource waste caused by CFO calibration signal broadcasting across the network and lack of basis for on-demand transmission in existing technologies.

[0022] In one possible implementation, the method further includes: when information from the first IoT device is received, removing the device identifier of the first IoT device from the current aging state list and adding it to the latest aging state list; after a preset time, removing the device identifier of the IoT device in the oldest aging state list and moving the device identifier of the IoT device in the updated aging state list to the older aging state list.

[0023] The hierarchical aging state list involved in this application is designed to address the significant memory overhead, processing latency, and complexity that arises when maintaining an independent timer for each IoT device on the network side in ultra-large-scale IoT scenarios. By using an aging state list, batch maintenance of the aging state of all IoT devices in the network is achieved, reducing memory overhead, processing latency, and complexity.

[0024] In a possible implementation manner, the first frequency adjustment parameter includes at least one of the following: LO adjustment indication information, target frequency, CFO calibration signal, and dwell duration. The LO adjustment indication information is used to indicate whether the Internet of Things device starts LO adjustment; the target frequency is used to indicate the frequency of the SFS resource allocated to the Internet of Things device; the CFO calibration signal is a reference signal used to measure and correct the CFO; the dwell duration is used to indicate the time length for which the Internet of Things device maintains a monitoring state at the target frequency after completing LO adjustment and sending data.

[0025] The LO adjustment indication information in the first frequency adjustment parameter indicates that the Internet of Things device does not start LO adjustment. The target frequency in the first frequency adjustment parameter is a frequency within the frequency band of the SFS anchor point group where the Internet of Things device is located (in this case, the Internet of Things device requires SFS adjustment). The first frequency adjustment parameter may not include the CFO calibration signal and the dwell duration.

[0026] In a third aspect, a communication device is provided. The communication device includes a communication module and a processing module. The communication module is used to receive system parameters, and the system parameters include at least one of the following: small frequency offset SFS anchor point group configuration, mapping rule between device identifier and SFS anchor point group, preamble configuration; the SFS anchor point group configuration includes the number N of SFS anchor point groups; the preamble configuration includes a first preamble set and a second preamble set. The first preamble set is used for random access when the Internet of Things device performs time-sensitive data autonomous reporting DO-A service, and the second preamble set is used for random access when the Internet of Things device performs non-time-sensitive DO-A service. The processing module is used to lock onto the SFS anchor point frequency of the SFS anchor point group n according to the device identifier, SFS anchor point group configuration, and mapping rule, where 0 ≤ n < N; and select a preamble from the first preamble set or the second preamble set for random access according to the type of DO-A service and the preamble configuration. The communication module is used to receive the first frequency adjustment parameter and adjust the uplink frequency according to the first frequency adjustment parameter. The first frequency adjustment parameter is used to indicate that the first Internet of Things device performs SFS adjustment, and the first frequency adjustment parameter is determined by the preamble and the network congestion situation.

[0027] In a possible implementation manner, the processing module is used to perform an operation on the device identifier according to the mapping rule to obtain the index n of the SFS anchor point group; look up the table from the SFS anchor point frequency list to find the SFS anchor point frequency of the SFS anchor point group n, and lock onto the SFS anchor point frequency.

[0028] In a possible implementation manner, the processing module is used to select a preamble from the first preamble set for random access if sending data for time-sensitive DO-A service; and select a preamble from the second preamble set for random access if sending data for non-time-sensitive DO-A service.

[0029] Fourthly, a communication device is provided, comprising a communication module. The communication module is used to transmit system parameters, which include at least one of the following: Small Frequency Offset (SFS) anchor group configuration, mapping rules between device identifiers and SFS anchor groups, and preamble configuration; the SFS anchor group configuration includes the number N of SFS anchor groups; the preamble configuration includes a first preamble set and a second preamble set, the first preamble set being used for random access when an IoT device performs Time-Sensitive Data Autonomous Reporting (DO-A) service, and the second preamble set being used for random access when an IoT device performs non-Time-Sensitive DO-A service; receiving a preamble from either the first or second preamble set; and, based on the received preamble and network congestion conditions, sending a first frequency adjustment parameter to a first IoT device, the first frequency adjustment parameter being used to instruct the first IoT device to perform SFS adjustment.

[0030] In one possible implementation, the communication module is configured to: determine the DO-A service type of the first IoT device based on the received preamble; determine the SFS anchor group n to which the first IoT device belongs based on the device identifier or the frequency band to which the uplink frequency belongs; check whether the first resource area of ​​the SFS anchor group n is congested; if the first resource area of ​​the SFS anchor group n is not congested, allocate an idle SFS resource as a target frequency for the first IoT device in the first resource area of ​​the SFS anchor group n, and send a first frequency adjustment parameter to the first IoT device; if the first resource area of ​​the SFS anchor group n is congested, and the DO-A service type of the first IoT device is a time-sensitive DO-A service, then in the SFS anchor group n... In the second resource area of ​​anchor group n, an idle SFS resource is allocated as the target frequency for the first IoT device, and a first frequency adjustment parameter is sent to the first IoT device. If the first resource area of ​​SFS anchor group n is congested, and the DO-A service type of the first IoT device is a non-time-sensitive DO-A service, then at least one second IoT device belonging to the same SFS anchor group n is selected from the oldest aging state list, and a second frequency adjustment parameter is sent to the second IoT device, instructing the second IoT device to temporarily move out of SFS anchor group n and perform LO adjustment; and the SFS resource released by the second IoT device is redistributed as the target frequency to the first IoT device, and the first frequency adjustment parameter is sent to the first IoT device.

[0031] In one possible implementation, a processing module is also included. When the information of the first IoT device is received, the processing module removes the device identifier of the first IoT device from the current aging state list and adds it to the latest aging state list. After a preset time, the processing module removes the device identifier of the IoT device in the oldest aging state list and moves the device identifier of the IoT device in the latest aging state list to the older aging state list.

[0032] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods of the first aspect and any implementation thereof. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0033] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0034] In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface can be an input / output interface.

[0035] Sixthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods of the second aspect and any implementation thereof. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0036] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0037] In another implementation, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface can be an input / output interface.

[0038] A seventh aspect provides a processor, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method of any possible implementation of the first to second aspects described above.

[0039] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0040] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the methods in any of the possible implementations of the first to second aspects described above.

[0041] Optionally, the processor may be one or more, and the memory may be one or more.

[0042] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform the method in any of the possible implementations of the first to second aspects described above.

[0043] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods in any of the possible implementations of the first to second aspects described above.

[0044] Eleventhly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the possible implementations of the first to second aspects to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0045] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0046] In a twelfth aspect, a communication system is provided, including the aforementioned communication devices, such as Internet of Things (IoT) devices or AIoT readers. Optionally, the communication system may further include other devices that communicate with IoT devices or AIoT readers.

[0047] The technical effects of the third to twelfth aspects refer to the technical effects of the first to second aspects and any of their embodiments, and will not be repeated here. Attached Figure Description

[0048] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0049] Figure 2 A schematic diagram of the structure of a UE provided in an embodiment of this application;

[0050] Figure 3 This is a schematic diagram of the structure of a RAN device provided in an embodiment of this application;

[0051] Figure 4 A schematic diagram of the structure of a core network element provided in an embodiment of this application;

[0052] Figure 5 This is a schematic diagram of the structure of an Internet of Things (IoT) device provided in an embodiment of this application;

[0053] Figure 6 A flowchart illustrating a communication method provided in an embodiment of this application;

[0054] Figure 7 A flowchart illustrating another communication method provided in an embodiment of this application;

[0055] Figure 8 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0056] Figure 9 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0057] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0058] First, some concepts involved in this application will be described.

[0059] The terms "first" and "second" used in the embodiments of this application are only used to distinguish features of the same type and should not be construed as indicating relative importance, quantity, order, etc.

[0060] The terms "exemplary" or "for example" used in the embodiments of this application are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0061] The technical solutions provided in this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, new radio access technology (NR), future communication systems, and 5G Advanced communication systems. Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technologies can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies.

[0062] Figure 1 This is a schematic diagram of the architecture of a communication system used in an embodiment of this application. The communication system 100 can be used for Internet of Things (IoT) communication. The communication system 100 may include: user equipment (UE) 101, radio access network (RAN) equipment 102, IoT devices 103, and core network elements 104. The main functions of each device are described in detail below.

[0063] UE 101 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities; it may also include subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, wireless modems, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, machine-type communication (MTC) terminals, mobile stations (MS), terminal devices, or relay subscriber equipment, etc. Relay subscriber equipment may, for example, be a 5G residential gateway (RG).

[0064] RAN equipment 102 may include access network equipment including, but not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, next-generation base stations in 6th-generation (6G) mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, base stations in future mobile communication systems, or access nodes in Wi-Fi systems. Access network equipment may also be modules or units capable of implementing some of the functions of a base station. For example, access network equipment may be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), as described below. In the ORAN system, CU can also be called open (O)-CU, DU can also be called open (O)-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CUP-UP, and RU can also be called O-RU. The access network equipment can be a macro base station, micro base station, indoor station, relay node, donor node, or a radio controller in a cloud radioaccess network (CRAN) scenario. Optionally, the access network equipment can also be a server, wearable device, or vehicle-mounted equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network equipment in the communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations using different access technologies. RAN device 102 is used for functions such as radio resource management on the air interface side, uplink and downlink data classification, quality of service (QoS) management, data compression and encryption, signaling processing with control plane network elements, and data forwarding with user plane function network elements. This application embodiment does not limit the specific form and structure of RAN device 102. For example, in systems employing different radio access technologies, the name of the RAN device 102 with base station functionality may differ.For example, a base station can be an evolved universal terrestrial radio access network (E-UTRAN) device in LTE, such as an evolved NodeB (eNB or e-NodeB), or a next-generation radio access network (NG-RAN) device (such as a gNB) in a 5G system.

[0065] The Internet of Things (IoT) device 103 can be an AIoT device. AIoT devices operate by collecting and utilizing various energy sources in the environment (including but not limited to radio waves, light energy, kinetic energy, and heat energy), improving the sustainability and performance of wireless communication and reducing its power consumption. AIoT devices can be applied in various scenarios, such as smart buildings, asset tracking, agriculture, and smart homes. Specifically, AIoT devices can be smart switches, smart locks, smart meters, sensor-based devices for monitoring machine status and environmental conditions, building automation and control equipment, and tagging devices. In these scenarios, the communication needs of AIoT devices are generally simple, perhaps involving simple asset information reporting or sending minimal sensor data.

[0066] Core network element 104 is used to manage the AIoT communication system and provide AIoT-related services and capabilities.

[0067] like Figure 1 As shown in Figure A, RAN device 102 can act as an AIoT reader, responsible for communication between IoT device 103 and core network element 104. This network architecture is referred to as Topology 1. RAN device 102 integrates AIoT RAN node function and common reader function. The AIoT RAN node function is used for communication with core network element 104, and the common reader function is used for air interface communication with IoT device 103. Alternatively, as... Figure 1 As shown in Figure B, UE 101 can act as an AIoT reader, responsible for communication between IoT device 103, RAN device 102, and core network element 104. This network architecture is called Topology 2.

[0068] An AIoT reader can be called an AIoT reader-writer, AIoT reading-writing device, tag reading-writing device, etc. An AIoT reader can use wireless communication to read and write to IoT device 103, thereby achieving the purpose of target identification and data exchange. Taking IoT device 103 as a tag device as an example, the AIoT reader provides energy to the tag device by sending excitation signals and transmitting commands. The tag device sends a response to the AIoT reader through reflected signals. In this way, the AIoT reader can identify the tag device's identification information and perform reading and writing operations on the tag device.

[0069] Figure 2 This is a schematic diagram of the structure of a UE provided in an embodiment of this application. Taking UE 101 as a mobile phone as an example, UE 101 may include components such as: radio frequency (RF) circuit 210, memory 220, other input devices 230, display screen 240, sensor 250, audio circuit 260, I / O subsystem 270, processor 280, and power supply 290. Those skilled in the art will understand that the structure shown in the figure does not constitute a limitation on UE 101, and may include more or fewer components than shown, or combine some components, or split some components, or have different component arrangements. Those skilled in the art will understand that the display screen 240 belongs to the user interface (UI), and the display screen 240 may include a display panel 241 and a touch panel 242. Although not shown, UE 101 may also include functional modules or devices such as a camera and Bluetooth module, which will not be described in detail here.

[0070] Furthermore, the processor 280 is connected to the RF circuit 210, memory 220, audio circuit 260, I / O subsystem 270, and power supply 290. The I / O subsystem 270 is connected to other input devices 230, display screen 240, and sensor 250. The RF circuit 210 can be used to receive and transmit signals during information transmission or calls; specifically, after receiving downlink information from network devices, it sends it to the processor 280 for processing. The memory 220 can be used to store software programs and modules. The processor 280 executes various functional applications and data processing of the UE 101 by running the software programs and modules stored in the memory 220, such as executing the methods involved in the embodiments of this application.

[0071] Other input devices 230 can be used to receive input digital or character information, and generate keyboard signal input related to user settings and function control of UE 101. Display screen 240 can be used to display information input by the user or information provided to the user, as well as various menus of UE 101, and can also accept user input. Sensor 250 can be a light sensor, motion sensor, or other sensor. Audio circuit 260 provides an audio interface between the user and UE 101. I / O subsystem 270 is used to control external input / output devices, which may include other device input controllers, sensor controllers, and display controllers. Processor 280 is the control center, connecting various parts of UE 101 through various interfaces and lines. It executes various functions of UE 101 and processes data by running or executing software programs and / or modules stored in memory 220, and by calling data stored in memory 220. Power supply 290 (e.g., a battery) is used to power the above components. The power supply can be logically connected to processor 280 through a power management system, thereby managing charging, discharging, and power consumption.

[0072] Figure 3 This is a schematic diagram of a RAN device provided in an embodiment of this application. Taking RAN device 102 as a base station as an example, RAN device 102 may include an indoor baseband unit (BBU) 301 and a remote radio unit (RRU) 302. The RRU 302 is connected to the antenna system (i.e., antenna) 303. BBU 301 and RRU 302 can be disassembled and used as needed. BBU 301 may include a processor 3011, a memory 3012, and a bus system 3013. The processor 3011 and memory 3012 of BBU 301 are interconnected through the bus system 3013. The bus system may be a peripheral component interconnection standard bus or an extended industrial standard structure bus, etc. The bus may be divided into address bus, data bus, control bus, etc. For ease of illustration, only one line is used to represent it in the figure, but this does not mean that there is only one bus or one type of bus. RRU 302 may include RF circuitry 3021, which is interconnected with BBU 301 via optical fiber and with antenna 303 via coaxial cable. Processor 3011 executes various functional applications and data processing of RAN device 102 by running computer instructions stored in memory 3012, such as the methods described in the embodiments of this application.

[0073] Figure 4This is a schematic diagram of the structure of a core network element provided in an embodiment of this application. Taking core network element 104 as an example of a network device, core network element 104 may include at least one processor 401, a communication line 402, a memory 403, and at least one communication interface 404. The processor 401 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of this application. The communication line 402 may include a path for transmitting information between the above components. The communication interface 404, using any transceiver-like device, is used to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. The memory 403 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory may exist independently and be connected to the processor via communication line 402. The memory may also be integrated with the processor. The memory 403 is used to store computer execution instructions (which may be referred to as application code) for executing the scheme of this application, and its execution is controlled by the processor 401. The processor 401 is used to execute computer execution instructions stored in the memory 403, thereby performing the methods involved in the embodiments of this application.

[0074] Figure 5This is a schematic diagram of the structure of an Internet of Things (IoT) device provided in an embodiment of this application. Taking IoT device 103 as a tag device as an example, IoT device 103 may include a processing module 501, a communication module 502, and an energy harvesting module 503. The processing module 501 is used for data preprocessing and controlling the IoT device 103 to go into sleep mode or power on. The communication module 502 is used for communication via backscatter or a simplified radio frequency protocol. The energy harvesting module 503 is used to convert energy sources such as radio frequency, light energy, heat energy, and kinetic energy in the environment into electrical energy to power the processing module 501 and the communication module 502.

[0075] IoT devices communicate with AIoT readers via Frequency Division Multiple Access (FDMA). IoT devices need frequency adjustment capabilities to match the communication frequency allocated by the AIoT reader. Current frequency adjustment methods primarily include small frequency shift (SFS) adjustment and local oscillator (LO) adjustment.

[0076] SFS adjustment is a frequency adjustment technique with a limited range. IoT devices generate a small, controllable frequency offset through baseband digital signal processing while keeping the physical frequency of the local oscillator constant.

[0077] SFS tuning offers several advantages: It results in extremely low power consumption by avoiding the high-power RF frequency synthesizer and the relocking process of the PLL circuit. This is crucial for battery-powered IoT devices requiring years of battery life. There is no hardware settling time; frequency tuning is instantaneous. This is irreplaceable for event-triggered applications requiring millisecond-level response times. Furthermore, being based on digital signal processing, it is easier to implement on-chip, reducing the requirements for RF front-end hardware.

[0078] SFS adjustment has the following drawbacks: Limited resources, easily leading to resource congestion. Because the available frequency offset range provided by each SFS anchor point is very small, if too many IoT devices belong to that anchor point, spectrum resources become congested, preventing new devices from communicating. It cannot solve long-distance frequency hopping. When it is necessary to schedule an IoT device to a completely different frequency band (e.g., from 900MHz to 910MHz), SFS is ineffective, and LO adjustment is required.

[0079] LO adjustment is a technique that uses a physical change in the output frequency of a local oscillator in the radio frequency front-end circuit to achieve channel switching in a device's communication circuit. The local oscillator is a core component in wireless equipment used to generate carrier signals.

[0080] LO adjustment has the following advantages: When there are too many devices in a certain SFS anchor group, causing SFS resources to be exhausted, LO adjustment can schedule IoT devices to other idle frequency bands, thereby fundamentally solving congestion and improving the overall network capacity. It can achieve global frequency resource scheduling and global optimization of spectrum resources.

[0081] Loop (LO) adjustment has the following disadvantages: Starting the phase-locked loop (PLL) and oscillator for frequency relocking is an energy-intensive operation with high power consumption. The PLL's settling time is typically in the millisecond to tens of millisecond range, resulting in high latency and communication delays. This makes it unsuitable for event-triggered services requiring instantaneous transmission. After switching to a new frequency, due to the initial error of the equipment's crystal oscillator, there is still a deviation between its actual frequency and the network's expected target frequency, thus requiring carrier frequency offset (CFO) calibration.

[0082] To address this, this application provides a communication method. An AIoT reader, according to the mapping rules between device identifiers and SFS anchor groups, divides all IoT devices into N SFS anchor groups, divides the uplink spectrum into N independent frequency bands, and assigns one frequency band to each SFS anchor group. The center frequency of each frequency band serves as the SFS anchor frequency. During initial random access, IoT devices can autonomously calculate and lock the SFS anchor frequency of their respective SFS anchor group. Within the frequency band of the SFS anchor group, SFS adjustments can be performed continuously with very short adjustment times and minimal communication latency. Furthermore, the preamble sent by the IoT device can indicate whether the DO-A service is time-sensitive or non-time-sensitive. The AIoT reader configures frequency adjustment parameters for the IoT device based on the DO-A service type and network congestion conditions to avoid network congestion.

[0083] Figure 6 This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 6 The AIoT reader in the middle can be Figure 1 RAN device 102 shown in Figure A Figure 1 The UE 101 shown in B can also refer to the device (such as a processor, chip, or chip system) in the RAN equipment 102 or UE 101. Figure 6 IoT devices in the context can be Figure 1 The IoT device 103 mentioned can also refer to the components (such as processors, chips, or chip systems) within the IoT device 103. Figure 6 As shown, the communication method 600 includes S101-S105.

[0084] The S101 AIoT reader periodically broadcasts system parameters.

[0085] AIoT readers periodically broadcast system parameters in synchronization messages on the public resource downlink control channel (PRDCH). System parameters include at least one of the following: SFS anchor group configuration, mapping rules between device identifiers and SFS anchor groups, and preamble configuration.

[0086] The AIoT reader divides all IoT devices into N SFS anchor groups according to the mapping rules between device identifiers and SFS anchor groups. Based on spectrum availability and deployment density, the uplink spectrum is divided into N independent frequency bands, with each SFS anchor group corresponding to one of these frequency bands. This means that IoT devices belonging to the same SFS anchor group transmit uplink data within the same frequency band. N is an integer greater than or equal to 1. The center frequency of each frequency band is called the SFS anchor frequency.

[0087] By dividing all IoT devices into N SFS anchor group, the uplink spectrum is divided into N independent frequency bands. Each SFS anchor group is allocated a frequency band, and IoT devices are mapped to the frequency band of one of the SFS anchor groups according to their device identifiers. This is equivalent to distributing all IoT devices evenly across the uplink spectrum, avoiding concentration on a single SFS anchor frequency and preventing congestion.

[0088] The SFS anchor group configuration includes the number N of SFS anchor groups and a list of SFS anchor frequencies. The SFS anchor frequency list contains a list of the center frequencies (i.e., SFS anchor frequencies) of the N SFS anchor groups. The SFS anchor frequencies in the SFS anchor frequency list can be arranged in order from index 0 to N-1 of the SFS anchor groups. SFS anchor frequencies can be represented as absolute frequency values ​​(e.g., kHz), channel numbers, or offsets relative to a reference frequency.

[0089] The AIoT reader configures a target frequency for IoT devices. If the frequency is within the band of the SFS anchor group where the IoT device is located, the IoT device only needs SFS adjustment. If the frequency is outside the band of the SFS anchor group where the IoT device is located, the IoT device needs LO adjustment.

[0090] The purpose of the SFS anchor grouping mechanism is to solve the problem of effectively managing the spectrum resource allocation caused by a large number of devices in IoT communication scenarios of AIoT active devices, while prioritizing the maximization of the low-power and low-latency SFS mechanism, and limiting the high-cost LO adjustment to a secondary congestion management means.

[0091] The AIoT reader can divide the frequency band of each SFS anchor point group into two frequency bands with different priorities and access policies, namely the regular resource area (referred to as the first resource area) and the high-priority reservation area (referred to as the second resource area).

[0092] The regular resource area occupies most of the frequency band of this SFS anchor point group, such as the center frequency band. The regular resource area is the main common resource pool for all Internet of Things devices in this SFS anchor point group to perform random access and data transmission in the default and non-congested state. When an Internet of Things device initiates a regular service, especially the periodic data autonomous reporting (DO-A) service, it defaults to applying for and using SFS resources in the regular resource area through a contention mechanism (such as backoff-based random access).

[0093] The high-priority reservation area occupies a small part of the frequency band of this SFS anchor point group, such as the edge frequency band. The high-priority reservation area is a reserved frequency band that does not participate in the regular contention of Internet of Things devices in this SFS anchor point group in the default and non-congested state. It is only directly assigned to this Internet of Things device for use by the scheduler when the AIoT reader detects congestion in the regular resource area and receives a preamble from the first preamble set. It is a dedicated emergency channel to ensure that event-triggered (or time-sensitive) DO-A services can still access with low latency in extreme cases (i.e., when the regular resource area is congested).

[0094] All Internet of Things devices adopt the same mapping rule between the device identifier and the SFS anchor point group. Exemplarily, this mapping rule can be a modulo operation hash algorithm, that is, taking the modulo of the device identifier of the Internet of Things device with the number N of SFS anchor point groups to obtain the index n of the SFS anchor point group, 0 ≤ n < N. This mapping rule can also be specified by the protocol and does not have to be sent in the system parameters.

[0095] The preamble configuration includes a first preamble set and a second preamble set. The first preamble set is used for random access (or scheduling request) when an Internet of Things device performs an event-triggered (or time-sensitive) DO-A service. The second preamble set is used for random access when an Internet of Things device performs a periodic (or non-time-sensitive) DO-A service.

[0096] S102. The first Internet of Things device locks onto the SFS anchor point frequency of the SFS anchor point group n according to the device identifier, the SFS anchor point group configuration, and the mapping rule between the device identifier and the SFS anchor point group.

[0097] When the first IoT device powers on or connects to the network for the first time, it enters the initial configuration mode. The first IoT device first searches for and monitors the PRDCH until it successfully receives the system parameters broadcast by the AIoT reader. The first IoT device loads a globally unique device identifier (Device_ID) from non-volatile memory and performs a calculation on its own device identifier according to the mapping rules between the device identifier and the SFS anchor group (e.g., taking the device identifier modulo N) to obtain the index n of the SFS anchor group. Based on index n, the first IoT device looks up the SFS anchor frequency in the SFS anchor frequency list to find the SFS anchor frequency for SFS anchor group n. Then, the first IoT device physically locks the local oscillator of its RF front-end to that SFS anchor frequency.

[0098] After frequency locking is completed, the first IoT device turns off the high-power broadband tuning circuit and turns on only the baseband digital filter covering the frequency band of the SFS anchor group to perform the subsequent device-to-reader (D2R) communication transmission process with the lowest power consumption.

[0099] S103. The first IoT device selects a preamble from the first preamble set or the second preamble set for random access (or scheduling request) based on the type of DO-A service and the preamble configuration.

[0100] When the first IoT device needs to send data, if it's sending event-triggered (or time-sensitive) DO-A service data, the first IoT device selects a preamble from the first preamble set for random access. If it's sending periodic (or non-time-sensitive) DO-A service data, the first IoT device selects a preamble from the second preamble set for random access. That is, it sends the preamble on the corresponding uplink resources, thereby initiating a scheduling request.

[0101] IoT devices randomly access the network using preambles from different preamble sets to indicate whether the DO-A service is a time-sensitive DO-A service or a non-time-sensitive DO-A service, helping AIoT readers determine frequency adjustment parameters based on network congestion conditions.

[0102] S104. The AIoT reader sends the first frequency adjustment parameters to the first IoT device based on the received preamble and network congestion status.

[0103] Frequency adjustment parameters (first frequency adjustment parameters and second frequency adjustment parameters) can be carried in reader-to-device (R2D) messages. Frequency adjustment parameters include at least one of the following: LO adjustment indication information, target frequency, CFO calibration signal, and dwell time.

[0104] The LO adjustment indication information is used to indicate whether the IoT device should initiate LO adjustment. For example, the LO adjustment indication information occupies 1 bit. A first value (e.g., 0) indicates that the IoT device should not initiate LO adjustment, and a second value (e.g., 1) indicates that the IoT device should initiate LO adjustment.

[0105] The target frequency indicates the frequency of the SFS resources allocated to the IoT device. The target frequency can be a frequency within the frequency band of the SFS anchor group where the IoT device is located (in which case the IoT device needs SFS adjustment), or a frequency outside the frequency band of the SFS anchor group where the IoT device is located (in which case the IoT device needs LO adjustment).

[0106] The CFO calibration signal is a reference signal used to measure and calibrate the CFO. The CFO calibration signal can be located at the end of an R2D message.

[0107] Dwell time indicates the length of time an IoT device maintains a monitoring state on a target frequency after completing LO adjustment and sending data. For example, dwell time can be 1000ms.

[0108] Specifically, such as Figure 7 As shown, S104 includes S1041-S1046:

[0109] S1041, The AIoT reader determines the DO-A service type of the first IoT device based on the received preamble.

[0110] If the received preamble belongs to the first preamble set, it indicates that the DO-A service type of the first IoT device is an event-triggered (or time-sensitive) DO-A service. If the received preamble belongs to the second preamble set, it indicates that the DO-A service type of the first IoT device is a periodic (or non-time-sensitive) DO-A service.

[0111] S1042. The AIoT reader determines the SFS anchor group n to which the first IoT device belongs based on the device identifier of the first IoT device or the frequency band to which the uplink frequency belongs.

[0112] The AIoT reader determines the SFS anchor group to which the first IoT device belongs based on the device identifier of the first IoT device. For example, the AIoT reader can perform a calculation on the device identifier of the first IoT device (e.g., modulo N) according to the mapping rules between the device identifier and the SFS anchor group to obtain the index n of the SFS anchor group to which the first IoT device belongs.

[0113] Alternatively, the AIoT reader can determine the SFS anchor group to which the first IoT device belongs based on the frequency band of its uplink frequency. For example, if the uplink frequency of the first IoT device belongs to the frequency band of SFS anchor group n, then the first IoT device belongs to SFS anchor group n.

[0114] S1043, AIoT reader counts whether the regular resource area of ​​SFS anchor group n is congested.

[0115] The AIoT reader can determine whether the regular resource area of ​​SFS anchor group n is congested based on the number of IoT devices accessing it. For example, if the number of IoT devices accessing the regular resource area of ​​SFS anchor group n exceeds a certain threshold, then the regular resource area of ​​SFS anchor group n is congested; otherwise, the regular resource area of ​​SFS anchor group n is not congested.

[0116] S1044. If the regular resource area of ​​SFS anchor group n is not congested, the AIoT reader allocates an idle SFS resource as the target frequency for the first IoT device in the regular resource area of ​​SFS anchor group n, and sends the first frequency adjustment parameter to the first IoT device.

[0117] The first frequency adjustment parameter is used to instruct the first IoT device to perform SFS adjustment. The LO adjustment indication information in the first frequency adjustment parameter indicates that the IoT device does not initiate LO adjustment. The target frequency in the first frequency adjustment parameter is the frequency within the frequency band of the SFS anchor group where the IoT device is located (at which point the IoT device needs SFS adjustment). The first frequency adjustment parameter may not include the CFO calibration signal and dwell time.

[0118] This approach allows the first IoT device to transmit solely through baseband digital frequency shifting without triggering LO adjustment, thereby maximizing system energy efficiency by default and maintaining low-power operation of the first IoT device.

[0119] S1045. If the regular resource area of ​​SFS anchor group n is congested, and the DO-A service type of the first IoT device is event-triggered (or time-sensitive) DO-A service, then the AIoT reader allocates an idle SFS resource as the target frequency for the first IoT device in the high-priority reserved area of ​​SFS anchor group n, and sends the first frequency adjustment parameter to the first IoT device.

[0120] This approach ensures that even during network congestion, the first IoT device does not require LO adjustment to cause communication delays; the transmission of time-sensitive services can be guaranteed through SFS adjustment.

[0121] S1046. If the regular resource area of ​​SFS anchor group n is congested, and the DO-A service type of the first IoT device is a periodic (or non-time-sensitive) DO-A service, then the AIoT reader selects at least one second IoT device that also belongs to SFS anchor group n from the list of oldest aging states, sends a second frequency adjustment parameter to the second IoT device, instructing the second IoT device to temporarily move out of SFS anchor group n and perform LO adjustment. The SFS resources released by the second IoT device are then redistributed to the first IoT device as the target frequency, and a first frequency adjustment parameter is sent to the first IoT device.

[0122] The second frequency adjustment parameter is used to instruct the second IoT device to perform LO adjustment. The LO adjustment indication information in the second frequency adjustment parameter instructs the IoT device to initiate LO adjustment. The target frequency in the second frequency adjustment parameter is a frequency outside the frequency band of the SFS anchor group where the IoT device is located (at which point the IoT device needs LO adjustment). The second frequency adjustment parameter may include the CFO calibration signal and dwell time.

[0123] This method searches for IoT devices belonging to the same SFS anchor group from the oldest aging state list, forces the IoT device to perform LO adjustment according to the CFO calibration signal, and frees up SFS resources for newly connected IoT devices. This design cleverly transforms the inherent signaling overhead of LO adjustment into the benefit of automatic aging state updates, effectively solving the problems of resource waste caused by CFO calibration signal broadcasting across the network and lack of basis for on-demand transmission in existing technologies.

[0124] The hierarchical management aging state list involved in the embodiments of this application is designed to solve the problem that if the network side maintains an independent timer for each IoT device in a large-scale IoT scenario, it will bring huge memory overhead, processing latency and complexity.

[0125] The AIoT reader maintains multiple aging state lists, each containing device identifiers for multiple IoT devices in the same aging state. The aging state of an IoT device indicates how long ago the AIoT reader last received information from that device. For example, an older or more recent aging state indicates that the AIoT reader last received information from that IoT device, while a newer aging state indicates that the AIoT reader last received information from that IoT device more recently. This enables unified aging state maintenance for all IoT devices across the network.

[0126] When the AIoT reader receives information from an IoT device, it removes the device's identifier from its current aging state list and adds it to the latest aging state list. Additionally, every preset time interval (e.g., 5 seconds), the AIoT reader removes the device identifiers of IoT devices from the oldest aging state list and moves the device identifiers of IoT devices from the most recent aging state list to an even older aging state list. This enables batch maintenance of the aging state of all IoT devices in the network, reducing memory overhead, processing latency, and complexity.

[0127] For example, suppose there are four aging state lists: List 1, List 2, List 3, and List 4. The aging states of List 1, List 2, List 3, and List 4 become older sequentially (i.e., the time taken to receive information from IoT devices in the lists increases sequentially). As shown in Table 1, when information from IoT device A is received, the AIoT reader adds the device identifier of IoT device A to List 1, which has the latest aging state. Additionally, as shown in Table 2, every preset time (e.g., 5 seconds), the AIoT reader removes the device identifiers of IoT devices from the oldest List 4, moves the device identifiers of IoT devices from the updated List 3 to the older List 4, moves the device identifiers of IoT devices from the updated List 2 to the older List 3, and moves the device identifiers of IoT devices from the updated List 1 to the older List 2. List 1 is then empty.

[0128] Table 1

[0129]

[0130] Table 2

[0131]

[0132] When an IoT device performs normal business interactions (such as sending D2R data or responding to R2D commands), it implicitly triggers a refresh of the aging state list. The IoT device does not need to send additional keep-alive commands; the successful D2R communication itself acts as a heartbeat, ensuring that the IoT device is in the latest aging state list.

[0133] If an IoT device remains in a silent state for an extended period (e.g., in a long-term sleep mode), due to the lack of D2R communication, its device identifier will gradually degrade in the aging state list over time, eventually falling into the oldest aging state list. At this point, the IoT device is considered to have a high CFO drift risk. When network SFS resource congestion occurs, the AIoT reader will prioritize selecting IoT devices from the oldest aging state list for LO adjustment. The device identifier of this IoT device will be added back to the latest aging state list. This completes the closed-loop repair of the aging state, and the IoT device switches back to low-power SFS monitoring mode.

[0134] The AIoT reader sends a local oscillator calibration command to the IoT device. Based on the instantaneous CFO signal in the local oscillator calibration command, the IoT device forces the local oscillator to calibrate and sends the information to the AIoT reader.

[0135] S105. After receiving the first frequency adjustment parameters, the first IoT device adjusts the uplink frequency according to the first frequency adjustment parameters.

[0136] Although the target frequency in the first frequency adjustment parameters may deviate from the center frequency (i.e., the SFS anchor frequency) of the SFS anchor group (SFS anchor group n) where the first IoT device is located, it is still within the frequency band of the current SFS anchor group where the first IoT device is located. The first IoT device can reach the target frequency through SFS adjustment and can send data at any time without LO adjustment, that is, keep the local oscillator frequency unchanged and do not perform any hardware retuning operation. This avoids the settling time of LO adjustment and achieves extremely low latency transmission.

[0137] Optionally, after receiving the second frequency adjustment parameters, the second IoT device adjusts the uplink frequency according to the second frequency adjustment parameters.

[0138] The target frequency in the second frequency adjustment parameter is outside the frequency band of the SFS anchor group (SFS anchor group n) where the second IoT device is located. The second IoT device needs to perform strict timing operations to complete the LO adjustment. Although the LO adjustment introduces additional power consumption and latency, it effectively eliminates the frequency drift that has accumulated in the IoT device over a long period of time, ensuring the reliability of the connection during inter-frequency transmission.

[0139] The second IoT device does not immediately switch to the target frequency. Instead, it locks onto the CFO calibration signal and measures the frequency offset error of its local oscillator relative to the network based on the CFO calibration signal. The second IoT device calculates compensation parameters based on the frequency offset error, activates the high-power LO circuit, and tunes to the target frequency. After the hardware adjustment stabilizes, the second IoT device transmits data at the target frequency.

[0140] After transmitting data on the target frequency, the second IoT device does not immediately return to the original frequency. Instead, it remains on the target frequency for standby monitoring based on the dwell time, in order to cope with subsequent sudden data transmissions or retransmissions, avoiding frequent frequency switching and increased transmission latency. Once the dwell time is reached, the second IoT device reverts its local oscillator frequency from the target frequency back to the frequency before the switch. No additional communication is required between the second IoT device and the AIoT reader; the AIoT reader can immediately detect that the second IoT device has reverted to the previous frequency.

[0141] Furthermore, since the local oscillator may drift again during the inter-frequency dwell period, the second IoT device, after falling back to the frequency before the switchover, does not immediately initiate data transmission. Instead, it monitors the synchronization messages of the periodically broadcast PRDCH on the previous frequency. The second IoT device performs passive CFO calibration of the local oscillator based on the clock acquisition part (CAP) or preamble in the PRDCH synchronization message. After completing the CFO calibration, the second IoT device returns to the SFS ready state, awaiting the next scheduling.

[0142] The communication method provided in this application involves an AIoT reader dividing all IoT devices into N SFS anchor groups according to the mapping rules between device identifiers and SFS anchor groups. The uplink spectrum is divided into N independent frequency bands, and each SFS anchor group is assigned a frequency band, with the center frequency of each band serving as the SFS anchor frequency. During initial random access, IoT devices can autonomously calculate and lock the SFS anchor frequency of their respective SFS anchor group. Within the frequency band of the SFS anchor group, SFS adjustments can be performed continuously with very short adjustment times and minimal communication latency. Furthermore, the preamble sent by the IoT device can indicate whether the DO-A service is time-sensitive or non-time-sensitive. The AIoT reader configures frequency adjustment parameters for the IoT device based on the DO-A service type and network congestion conditions to avoid network congestion.

[0143] The communication method provided in this application has the following innovations and significant advancements compared to the prior art:

[0144] 1. This application innovatively proposes a resource management architecture based on frequency domain grouping. Specifically, the AIoT reader divides all IoT devices into N SFS anchor groups according to the mapping rules between device identifiers and SFS anchor groups, divides the uplink spectrum into N independent frequency bands, allocates one frequency band to each SFS anchor group, and uses the center frequency of each frequency band as the SFS anchor frequency. Furthermore, when an IoT device initially connects randomly, it can autonomously calculate and lock the SFS anchor frequency of its respective SFS anchor group, and perform SFS adjustment within the frequency band of the SFS anchor group. This makes SFS adjustment the default low-power operating mode, thereby maximizing overall system-level energy efficiency.

[0145] 2. This application innovatively proposes an SFS redirection mechanism based on DO-A service type. The AIoT reader further divides the frequency band of each SFS anchor group into a regular resource area and a high-priority reserved area. To address this, this solution constructs a low-latency guarantee channel at the physical layer. When an IoT device performing an event-triggered (or time-sensitive) DO-A service randomly accesses the network, if the regular resource area of ​​the SFS anchor group to which the IoT device belongs becomes congested, the IoT device is prevented from being assigned to the frequency band of other SFS anchor groups, thus avoiding the need for time to achieve hardware-stable LO adjustments. The IoT device only needs to be assigned to the high-priority reserved area of ​​the same SFS anchor group, and the IoT device can then perform uplink transmission simply by performing SFS adjustments. This avoids the latency introduced by hardware switching and ensures the real-time nature of emergency information.

[0146] 3. This application innovatively integrates congestion management with aging state maintenance. It abandons the high-overhead approach of maintaining an independent synchronization timer for each IoT device, instead employing a low-complexity aging state list to maintain the aging state of IoT devices, reducing the risk of carrier or sampling frequency offset. When an IoT device performing periodic (or non-time-sensitive) DO-A service randomly accesses the network, if the regular resource area of ​​the SFS anchor group to which the IoT device belongs becomes congested, the system searches the oldest aging state list for IoT devices belonging to the same SFS anchor group. The IoT device is then forced to perform LO adjustment based on the CFO calibration signal, freeing up SFS resources for the newly accessed IoT device. This design cleverly transforms the inherent signaling overhead of LO adjustment into the benefit of automatic aging state updates, effectively solving the problems of resource waste caused by network-wide broadcasting of CFO calibration signals and the lack of basis for on-demand transmission in existing technologies.

[0147] 4. Addressing the challenge of maintaining the state of IoT devices after LO adjustment, this application innovatively proposes a dwell time and an automatic fallback mechanism. After completing LO adjustment and inter-frequency transmission, the IoT device dwells on the target frequency for a specific duration to cope with possible sudden retransmissions, and then autonomously falls back to the pre-adjustment frequency of its local oscillator. The innovation lies in the passive resynchronization strategy adopted after fallback: the IoT device uses the periodically broadcast common synchronization signal on the SFS anchor frequency for local calibration, restoring to a precise SFS synchronization state without additional interaction with the AIoT reader. While effectively ensuring the long-term frequency accuracy of IoT devices, this significantly reduces the signaling overhead and management complexity on the network side for maintaining a massive number of IoT devices.

[0148] The communication method provided in this application can be widely applied to complex IoT scenarios involving massive concurrent reporting by devices, hybrid Quality of Service (QoS) assurance, and long-term maintenance-free deployment. For example, this method is suitable for monitoring critical infrastructure such as urban gas pipelines and water supply networks, monitoring precision manufacturing in large industrial parks, and wide-area forest fire early warning. With the large-scale deployment of A-IoT devices (such as Device 2b / C) in these dense outdoor scenarios, the network side not only needs to handle massive amounts of regular status data, but also needs to dynamically balance the low-latency requirements of sudden emergency services with the synchronous maintenance requirements of long-term silent devices under limited spectrum resources (especially SFS bandwidth limitations).

[0149] However, traditional FDMA scheduling mechanisms face a typical dilemma when dealing with such mixed traffic concurrency scenarios: if relying solely on SFS scheduling, massive amounts of regular traffic can easily crowd out limited bandwidth, causing transmission delays for urgent services due to resource queuing. If load balancing is simply achieved through LO adjustment, the hardware settling time will significantly increase the transmission delay of critical alarm signals. Furthermore, for equipment that has been in a maintenance-free state for a long time, the lack of a targeted synchronization drift management mechanism will cause its carrier frequency to gradually drift, resulting in a gradual increase in the overall network interference level and affecting system capacity and reliability.

[0150] In specific implementations of urban gas pipeline networks or underground integrated pipe corridor monitoring, tens of thousands of pressure, flow, and combustible gas sensors are typically deployed. Under normal conditions, these devices only need to send low-frequency routine status reports periodically, which is a periodic DO-A (Do-A) service. However, in the event of emergencies such as pipeline leaks or pressure anomalies, they must immediately trigger and report emergency events, which is an event-triggered DO-A service. When a regional pressure anomaly occurs, a large number of sensors may trigger event reporting almost simultaneously, easily causing instantaneous congestion in the regular resource areas of the corresponding SFS (Self-Focused Flow) anchor point group. This communication method allows the network side to accurately identify such sudden abnormal flow. In terms of scheduling strategy, the system proactively avoids generating any commands that require triggering LO (Local Flow) adjustments, instead directly activating the preset high-priority reserved area within the same SFS anchor point group. This ensures that alarm signals can be transmitted through a pure SFS path without hardware switching, achieving near-zero-wait emergency information delivery at the physical layer and greatly guaranteeing the real-time nature of disaster warnings.

[0151] For routine, non-time-sensitive periodic status reporting services, if network congestion occurs during transmission, the aging status list used in this communication method can accurately identify devices that have not communicated for a long time and therefore have the highest risk of carrier frequency drift. The system will prioritize selecting such devices from the oldest aging status list, perform LO activation and migration operations across SFS anchor group, and use the CFO calibration signal in the command to complete the frequency calibration of the local oscillator of the IoT device. This strategy resolves the current SFS resource congestion by migrating out some devices, and also takes advantage of this transmission opportunity to complete the synchronous status refresh of the IoT devices with the oldest aging status in the network, realizing low-cost self-healing and synchronous maintenance of large-scale IoT without additional signaling overhead.

[0152] Figure 8 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 800 may include a communication module 810. The communication module 810 can implement corresponding communication functions, which can be internal communication functions of the communication device 800 or communication functions between the communication device 800 and other devices. Optionally, the communication module 810 may also be referred to as a communication interface or a transceiver module. Optionally, the communication device 800 also includes a processing module 820. The processing module 820 can implement corresponding processing functions.

[0153] Optionally, the communication device 800 further includes a storage module 830, which can be used to store instructions and / or data; the processing module 820 can read the instructions and / or data in the storage module 830 so that the communication device 800 can implement the aforementioned method embodiments.

[0154] In a possible design, the communication device 800 may correspond to the Internet of Things device in the above method embodiments, or be a component (such as a circuit, chip, or chip system, etc.) configured in the Internet of Things device. The communication device 800 can be used to execute the steps or processes performed by the Internet of Things device in any of the above method embodiments.

[0155] Exemplarily, the communication module 810 is used to receive system parameters, and the system parameters include at least one of the following: small frequency shift SFS anchor group configuration, mapping rule between device identifier and SFS anchor group, preamble configuration; the SFS anchor group configuration includes the number N of SFS anchor groups; the preamble configuration includes a first preamble set and a second preamble set. The first preamble set is used for random access when the Internet of Things device performs time-sensitive data autonomous reporting DO-A service, and the second preamble set is used for random access when the Internet of Things device performs non-time-sensitive DO-A service. The processing module 820 is used to lock onto the SFS anchor frequency of the SFS anchor group n according to the device identifier, SFS anchor group configuration, and mapping rule, where 0 ≤ n < N; and select a preamble from the first preamble set or the second preamble set for random access according to the type of DO-A service and the preamble configuration. The communication module 810 is used to receive a first frequency adjustment parameter, and adjust the uplink frequency according to the first frequency adjustment parameter. The first frequency adjustment parameter is used to indicate the first Internet of Things device to perform SFS adjustment, and the first frequency adjustment parameter is determined by the preamble and network congestion situation.

[0156] In a possible implementation manner, the processing module 820 is used to perform an operation on the device identifier according to the mapping rule to obtain the index n of the SFS anchor group; look up the table from the SFS anchor frequency list to find the SFS anchor frequency of the SFS anchor group n, and lock onto the SFS anchor frequency.

[0157] In a possible implementation manner, the processing module 820 is used to select a preamble from the first preamble set for random access if sending data of time-sensitive DO-A service; and select a preamble from the second preamble set for random access if sending data of non-time-sensitive DO-A service.

[0158] In a possible design, the communication device 800 may correspond to the AIoT reader in the above method embodiments, or be a component (such as a circuit, chip, or chip system, etc.) configured in the AIoT reader. The communication device 800 can be used to execute the steps or processes performed by the AIoT reader in any of the above method embodiments.

[0159] For example, the communication module 810 is used to send system parameters, which include at least one of the following: Small Frequency Offset (SFS) anchor group configuration, mapping rules between device identifiers and SFS anchor groups, and preamble configuration; the SFS anchor group configuration includes the number N of SFS anchor groups; the preamble configuration includes a first preamble set and a second preamble set, the first preamble set being used for random access when IoT devices perform time-sensitive data autonomous reporting (DO-A) services, and the second preamble set being used for random access when IoT devices perform non-time-sensitive DO-A services; receiving a preamble from the first preamble set or the second preamble set; and sending a first frequency adjustment parameter to the first IoT device based on the received preamble and network congestion conditions, the first frequency adjustment parameter being used to instruct the first IoT device to perform SFS adjustment.

[0160] In one possible implementation, the communication module 810 is configured to determine the DO-A service type of the first IoT device based on the received preamble; determine the SFS anchor group n to which the first IoT device belongs based on the device identifier or the frequency band to which the uplink frequency belongs; check whether the first resource area of ​​the SFS anchor group n is congested; if the first resource area of ​​the SFS anchor group n is not congested, then allocate an idle SFS resource as the target frequency for the first IoT device in the first resource area of ​​the SFS anchor group n, and send the first frequency adjustment parameter to the first IoT device; if the first resource area of ​​the SFS anchor group n is congested, and the DO-A service type of the first IoT device is a time-sensitive DO-A service, then in the SFS anchor group n, allocate an idle SFS resource as the target frequency, and send the first frequency adjustment parameter to the first IoT device; if the first resource area of ​​the SFS anchor group n is congested, and the DO-A service type of the first IoT device is a time-sensitive DO-A service, then in the SFS anchor group n, allocate an idle SFS resource as the target frequency, and send the first frequency adjustment parameter to the first IoT device. In the second resource area of ​​S anchor group n, an idle SFS resource is allocated as the target frequency for the first IoT device, and a first frequency adjustment parameter is sent to the first IoT device. If the first resource area of ​​SFS anchor group n is congested, and the DO-A service type of the first IoT device is a non-time-sensitive DO-A service, then at least one second IoT device belonging to SFS anchor group n is selected from the oldest aging state list, and a second frequency adjustment parameter is sent to the second IoT device, instructing the second IoT device to temporarily move out of SFS anchor group n and perform LO adjustment; and the SFS resource released by the second IoT device is reallocated as the target frequency to the first IoT device, and the first frequency adjustment parameter is sent to the first IoT device.

[0161] In one possible implementation, the processing module 820 is configured to, when receiving information from the first IoT device, remove the device identifier of the first IoT device from the current aging state list and add it to the latest aging state list; after a preset time, remove the device identifier of the IoT device in the oldest aging state list and move the device identifier of the IoT device in the latest aging state list to the older aging state list.

[0162] Figure 9 This is a schematic diagram of another communication device provided in an embodiment of this application. The communication device 900 can be an IoT device, an AIoT reader, a chip, a chip system, or a processor implementing the above methods, etc. The communication device 900 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0163] like Figure 9 As shown, the communication device 900 may include one or more processors 910, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 910 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 900 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0164] In an alternative design, the processor 910 may also store instructions and / or data, which can be executed by the processor 910 to cause the communication device 900 to perform the methods described in the above method embodiments.

[0165] In another alternative design, the communication device 900 may include a communication interface 920 for implementing receiving and transmitting functions. For example, the communication interface 920 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0166] Optionally, the communication device 900 may include one or more memories 930, which may store instructions that can be executed on the processor 910, causing the communication device 900 to perform the methods described in the above method embodiments. Optionally, the memories 930 may also store data. Optionally, the processor 910 may also store instructions and / or data. The processor 910 and the memories 930 may be provided separately or integrated together.

[0167] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0168] In one implementation, the communication device 900 may correspond to the IoT device in the above method embodiments and may be used to execute the various steps and / or processes executed by the IoT device in the above method embodiments. The processor 910 may be used to execute instructions stored in the memory 930, and when the processor 910 executes the instructions stored in the memory, the processor 910 is used to execute the various steps and / or processes of the above method embodiments corresponding to the IoT device.

[0169] In another implementation, the communication device 900 can correspond to the AIoT reader in the above method embodiments, and can be used to execute the various steps and / or processes executed by the AIoT reader in the above method embodiments. The processor 910 can be used to execute the instructions stored in the memory 930, and when the processor 910 executes the instructions stored in the memory, the processor 910 is used to execute the various steps and / or processes of the above method embodiments corresponding to the AIoT reader.

[0170] It should be understood that the aforementioned processor can be one or more chips. For example, the processor can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0171] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0172] According to the method provided in the embodiments of this application, this application also provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method described in the embodiments of this application.

[0173] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0174] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0175] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0176] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned Internet of Things (IoT) device and AIoT reader.

[0177] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes performed by the Internet of Things device or AIoT reader in any of the foregoing method embodiments.

[0178] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code. When the program code is run on a computer, it causes the computer to execute the various steps or processes performed by the Internet of Things device or AIoT reader in any of the foregoing method embodiments.

[0179] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0180] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0181] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated.

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

[0183] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0184] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applied to a first Internet of Things (IoT) device, the method includes: The system receives system parameters, which include at least one of the following: Small Frequency Offset (SFS) anchor group configuration, mapping rules between device identifiers and SFS anchor groups, and preamble configuration; the SFS anchor group configuration includes the number N of SFS anchor groups; the preamble configuration includes a first preamble set and a second preamble set, wherein the first preamble set is used for random access when IoT devices perform time-sensitive data autonomous reporting (DO-A) services, and the second preamble set is used for random access when IoT devices perform non-time-sensitive DO-A services. Based on the device identifier, the SFS anchor group configuration, and the mapping rules, the SFS anchor frequency of SFS anchor group n is locked, where 0 ≤ n. <N; Based on the type of DO-A service and the preamble configuration, a preamble from either the first preamble set or the second preamble set is selected for random access. The first frequency adjustment parameter is received, and the uplink frequency is adjusted according to the first frequency adjustment parameter. The first frequency adjustment parameter is used to instruct the first IoT device to perform SFS adjustment. The first frequency adjustment parameter is determined by the preamble and the network congestion situation.

2. The method according to claim 1, characterized in that, The SFS anchor group configuration includes an SFS anchor frequency list; locking onto the SFS anchor frequency of SFS anchor group n based on the device identifier, the SFS anchor group configuration, and the mapping rules includes: The device identifier is calculated according to the mapping rules to obtain the index n of the SFS anchor group; Look up the SFS anchor frequency in the SFS anchor frequency list, find the SFS anchor frequency of SFS anchor group n, and lock onto the SFS anchor frequency.

3. The method according to claim 1, characterized in that, The step of selecting a preamble from the first preamble set or the second preamble set for random access based on the type of DO-A service and the preamble configuration includes: If sending time-sensitive DO-A service data, select a preamble from the first preamble set for random access; If sending data for non-time-sensitive DO-A services, select a preamble from the second preamble set for random access.

4. The method according to any one of claims 1-3, characterized in that, The first frequency adjustment parameter includes at least one of the following: local oscillator (LO) adjustment indication information, target frequency, carrier frequency offset (CFO) calibration signal, and dwell time; The LO adjustment indication information is used to indicate whether the IoT device initiates LO adjustment; the target frequency is used to indicate the frequency of the SFS resources allocated to the IoT device; the CFO calibration signal is a reference signal used to measure and correct the CFO; the dwell time is used to indicate the length of time the IoT device maintains a monitoring state on the target frequency after completing LO adjustment and sending data.

5. A communication method, characterized in that, The method, applied to an environmental IoT (AIoT) reader, includes: Send system parameters, which include at least one of the following: Small Frequency Offset (SFS) anchor group configuration, mapping rules between device identifier and SFS anchor group, and preamble configuration; the SFS anchor group configuration includes the number N of SFS anchor groups; the preamble configuration includes a first preamble set and a second preamble set, wherein the first preamble set is used for random access when IoT devices perform time-sensitive data autonomous reporting (DO-A) services, and the second preamble set is used for random access when IoT devices perform non-time-sensitive DO-A services; Receive a preamble from the first preamble set or the second preamble set; Based on the received preamble and network congestion status, a first frequency adjustment parameter is sent to the first IoT device, which is used to instruct the first IoT device to perform SFS adjustment.

6. The method according to claim 5, characterized in that, The step of sending a first frequency adjustment parameter to the first IoT device based on the received preamble and network congestion status includes: The DO-A service type of the first IoT device is determined based on the received preamble. Based on the device identifier or the frequency band to which the uplink frequency belongs, determine the SFS anchor group n to which the first IoT device belongs; Check if the first resource zone of SFS anchor group n is congested; If the first resource area of ​​SFS anchor group n is not congested, then in the first resource area of ​​SFS anchor group n, an idle SFS resource is allocated as the target frequency for the first IoT device, and the first frequency adjustment parameter is sent to the first IoT device. If the first resource area of ​​SFS anchor group n is congested, and the DO-A service type of the first IoT device is a time-sensitive DO-A service, then in the second resource area of ​​SFS anchor group n, an idle SFS resource is allocated to the first IoT device as the target frequency, and the first frequency adjustment parameter is sent to the first IoT device. If the first resource area of ​​SFS anchor group n is congested, and the DO-A service type of the first IoT device is a non-time-sensitive DO-A service, then at least one second IoT device belonging to the same SFS anchor group n is selected from the list of oldest aging states, and a second frequency adjustment parameter is sent to the second IoT device, instructing the second IoT device to temporarily move out of SFS anchor group n and perform LO adjustment; and the SFS resources released by the second IoT device are redistributed to the first IoT device as the target frequency, and a first frequency adjustment parameter is sent to the first IoT device.

7. The method according to claim 6, characterized in that, Also includes: When the information of the first IoT device is received, the device identifier of the first IoT device is removed from the current aging status list and added to the latest aging status list. Every preset time interval, the device identifier of the IoT device in the oldest aging state list is removed, and the device identifier of the IoT device in the aging state list with the newest aging state is moved to the aging state list with an even older aging state.

8. The method according to any one of claims 5-7, characterized in that, The first frequency adjustment parameter includes at least one of the following: local oscillator (LO) adjustment indication information, target frequency, carrier frequency offset (CFO) calibration signal, and dwell time; The LO adjustment indication information is used to indicate whether the IoT device initiates LO adjustment; the target frequency is used to indicate the frequency of the SFS resources allocated to the IoT device; the CFO calibration signal is a reference signal used to measure and correct the CFO; the dwell time is used to indicate the length of time the IoT device maintains a monitoring state on the target frequency after completing LO adjustment and sending data.

9. A communication device, characterized in that, The communication device includes a processor and a memory, wherein the memory stores instructions, and when the processor executes the instructions, the communication device performs the method as described in any one of claims 1-8.

10. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1-8.

Images