A communication method, apparatus, and system

Abstract

This application provides a communication method, apparatus, and system, relating to the field of communication technology. The reader / writer can determine the number of IoT devices supporting DOA services in advance before allocating random access resources, thereby allocating resources to each IoT device on demand, saving resources, and improving communication efficiency and stability. The method includes: sending a first synchronization message indicating a first access resource; monitoring first D2R messages sent by at least one IoT device supporting DOA services on the first access resource to determine the number of at least one IoT device; for any IoT device, configuring a random access resource for the IoT device based on the number of at least one IoT device, and sending a paging message for the random access resource to the IoT device; and receiving a random access request sent by the IoT device on the random access resource.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, apparatus and system. Background Technology

[0002] In the context of the 3rd Generation Partnership Project (3GPP) for fifth-generation mobile communications, rd In the Generation Partnership Project 5G (3GPP 5G) standard, IoT devices that support Device Originated Automation (DOA) services in ambient IoT (AIoT) communication scenarios are defined.

[0003] Before an IoT device supporting DOA (Demand for Access) can initiate a DOA service, the network device needs to allocate network resources to the IoT device, such as allocating random access resources. However, there are no clear regulations on how to effectively allocate resources to IoT devices, which can lead to resource waste and affect communication efficiency and stability. Summary of the Invention

[0004] This application provides a communication method, apparatus, and system. Before allocating random access resources, the reader can determine the number of at least one IoT device based on the signal strength of a first device-to-reader (D2R) message sent by at least one IoT device supporting DOA services on the first access resource. This allows for on-demand resource allocation to each IoT device according to the number of DOA-supporting IoT devices, saving resources and improving communication efficiency and stability. The reader can also send multiple D2R synchronization signals to the IoT devices for carrier frequency offset (CFO) compensation, improving the accuracy, anti-interference capabilities, and efficiency of CFO compensation, thereby further saving resources.

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

[0006] The method includes: sending a first synchronization message indicating a first access resource; monitoring a first D2R message sent by at least one IoT device on the first access resource to monitor the signal strength on the first access resource; each IoT device supporting a DOA service; for any one of the at least one IoT device, sending a paging message to the IoT device to configure a random access resource for the IoT device; wherein the random access resource configured for the IoT device is determined based on the number of at least one IoT device; the number of at least one IoT device is determined based on the signal strength of the first D2R message sent by at least one IoT device on the first access resource; and receiving a random access request sent by the IoT device on the random access resource.

[0007] The aforementioned communication method is applied to IoT devices. Since each IoT device supporting DOA services sends a first D2R message to the reader on the first access resource, and each first D2R message corresponds to one IoT device and one signal strength, the reader can determine the number of IoT devices by monitoring the total signal strength on the first access resource. Based on this number, the reader can then determine the random access resources required by each IoT device. This allows for accurate on-demand configuration of random access resources for each IoT device, significantly reducing access conflicts and congestion, improving access success rate and reliability, and significantly reducing power consumption, thereby saving resources and improving communication efficiency and stability.

[0008] In one possible implementation of the first aspect, the method further includes: in response to detecting a first D2R message sent by at least one IoT device, sending a second synchronization message; the second synchronization message is used for time synchronization between at least one IoT device and the reader / writer, and for locating a paging message corresponding to at least one IoT device.

[0009] In this implementation, the second synchronization message can be described as a synchronization signal or a D2R synchronization signal. Optionally, the reader can also send multiple D2R synchronization signals to the IoT device. Since the synchronization signal has the functions of time synchronization and CFO compensation, the reader can perform CFO compensation on the IoT device multiple times, thereby improving the accuracy, anti-interference and efficiency of CFO compensation, and further saving resources.

[0010] In one possible implementation of the first aspect, sending the first synchronization message includes: periodically sending the first synchronization message.

[0011] In this implementation, by periodically sending the first synchronization message, the IoT device can avoid being unable to send the first D2R message on the first access resource due to not receiving the first synchronization message.

[0012] In one possible implementation of the first aspect, the first synchronization message corresponds to a first time length; the random access resources configured for the IoT devices are obtained by allocating the random access resources corresponding to the first time length based on the number of at least one IoT device.

[0013] In this implementation, the first time length can be the time interval between two adjacent synchronization messages when the first synchronization message is sent periodically. The first time length can be relatively long, meaning one first synchronization message can correspond to a long period. The reader can monitor the number of IoT devices supporting DOA services within this long period and then allocate random access resources to the IoT devices as needed within that long period. In this implementation, since IoT devices are mostly in an ultra-low power "deep sleep" state, the reader's periodic sending of the first synchronization message can periodically wake up the IoT devices for a short period, allowing them to receive and parse the first synchronization message and quickly synchronize with the reader's time. This achieves time calibration between the IoT devices and the reader while maintaining low power consumption, providing initial CFO compensation. Furthermore, the first synchronization message can also provide a unified time reference for all IoT devices.

[0014] In one possible implementation of the first aspect, the second synchronization message is sent by the reader within a first time period. For example, the first second synchronization message is sent after a preset time period following the end of the first synchronization message. This preset time period is relatively short and can be set as needed without limitation.

[0015] In this implementation, the second synchronization message can provide a more accurate timestamp. The IoT device can make multiple fine-tuning adjustments based on multiple second synchronization messages, improving the accuracy of time synchronization between the IoT device and the reader. This improves the accuracy, anti-interference, and efficiency of CFO compensation, enabling the reader to dynamically and efficiently configure random access resources for each IoT device. This avoids the IoT device missing the random access resources configured by the reader due to time asynchrony with the reader, thus preventing resource waste.

[0016] In one possible implementation of the first aspect, the number of second synchronization messages is greater than or equal to the first quantity threshold.

[0017] In this implementation, by sending the second synchronization message multiple times, the IoT device can avoid being unable to synchronize its time with the reader again due to not receiving the second synchronization message.

[0018] Secondly, a communication method is provided, which can be executed by an 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. The following description uses any IoT device among at least one IoT device supporting DOA services as an example.

[0019] The method includes: receiving a first synchronization message sent by a reader to indicate a first access resource; sending a first D2R message to the reader on the first access resource for the reader to monitor the signal strength on the first access resource; receiving a paging message sent by the reader to configure a random access resource for an IoT device; wherein the random access resource configured for the IoT device is determined by the reader based on the number of at least one IoT device; the number of at least one IoT device is determined by the reader based on the signal strength of the first D2R message sent by at least one IoT device on the first access resource; and sending a random access request to the reader on the random access resource.

[0020] The aforementioned communication method is applied to IoT devices. Since each IoT device supporting DOA services sends a first D2R message to the reader on the first access resource, and each first D2R message corresponds to one IoT device and one signal strength, the reader can determine the number of IoT devices by monitoring the total signal strength on the first access resource. Based on this number, the reader can then determine the random access resources required by each IoT device. This allows for accurate and on-demand configuration of random access resources for each IoT device, significantly reducing access conflicts and congestion, improving access success rate and reliability, and significantly reducing power consumption, thereby saving resources and improving communication efficiency and stability.

[0021] In one possible implementation of the second aspect, the method further includes: receiving a second synchronization message sent by the reader for time synchronization and location paging messages between the IoT device and the reader; the second synchronization message is sent by the reader in response to detecting a first D2R message sent by at least one IoT device.

[0022] In one possible implementation of the second aspect, receiving a first synchronization message sent by the reader includes: receiving a first synchronization message periodically sent by the reader.

[0023] In one possible implementation of the second aspect, the first synchronization message corresponds to a first time length; the random access resources configured for the IoT devices are obtained by allocating the random access resources corresponding to the first time length based on the number of at least one IoT device.

[0024] In one possible implementation of the second aspect, the second synchronization message is sent by the reader within the first time length.

[0025] In one possible implementation of the second aspect, the number of second synchronization messages is greater than or equal to the first quantity threshold.

[0026] The second aspect is the implementation on the IoT device side, which corresponds to the first aspect. The explanations, supplements, and descriptions of the beneficial effects of the first aspect also apply to the second aspect, and will not be repeated here.

[0027] Thirdly, a communication device is provided, the communication device including at least one processor coupled to a memory storing a program or instructions; the processor is configured to execute the program or instructions such that the communication device is configured to perform a communication method as described in the first aspect and any embodiment thereof, or to perform a communication method as described in the second aspect and any embodiment thereof.

[0028] The third aspect is the implementation on the device side, which corresponds to the first and second aspects. The explanations, supplements, and descriptions of the beneficial effects of the first and second aspects also apply to the third aspect, and will not be repeated here.

[0029] Fourthly, 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 a communication method as described in the first aspect and any embodiment thereof, or to perform a communication method as described in the second aspect and any embodiment thereof.

[0030] Fifthly, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform a communication method as described in the first aspect and any embodiment thereof, or to perform a communication method as described in the second aspect and any embodiment thereof.

[0031] Sixthly, a communication system is provided, including a reader / writer and an IoT device supporting DOA services. The reader / writer has the communication functions as described in the first aspect and any embodiment thereof, and the IoT device supporting DOA services has the communication functions as described in the second aspect and any embodiment thereof.

[0032] In a seventh aspect, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, such that a communication method as described in the first aspect and any embodiment thereof, or a communication method as described in the second aspect and any embodiment thereof, is executed. The chip system may be composed of chips or may include chips and other discrete devices.

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

[0034] The technical effects of the design methods in the third, fourth, fifth, sixth, and seventh aspects can be found in the technical effects of the different design methods in the first or second aspects, and will not be repeated here. Attached Figure Description

[0035] Figure 1 This application provides a schematic diagram of the structure of a communication system according to an embodiment of the present application.

[0036] Figure 2 A schematic diagram of the structure of a reader, an Internet of Things device, and a network device provided in the embodiments of this application;

[0037] Figure 3 A flowchart of a communication method provided for related technologies;

[0038] Figure 4 A schematic diagram of a communication method provided for related technologies;

[0039] Figure 5 A schematic diagram of a DOA service provided for related technologies;

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

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

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

[0043] Figure 9 A schematic diagram illustrating a communication method provided in an embodiment of this application;

[0044] Figure 10 A schematic diagram illustrating another communication method provided in an embodiment of this application;

[0045] Figure 11 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0046] Figure 12 A schematic diagram illustrating yet another communication method provided in an embodiment of this application;

[0047] Figure 13 A schematic diagram illustrating yet another communication method provided in an embodiment of this application;

[0048] Figure 14 A schematic diagram of a communication device provided in an embodiment of this application;

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

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

[0051] 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.

[0052] 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.

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

[0054] The technical solutions provided in this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) systems, General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), 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, or new radio access technology (NR). 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.

[0055] Appendix Figure 1 A schematic diagram of a communication system provided in an embodiment of this application is attached. Figure 1 As shown in (a), the communication system may include an Internet of Things (IoT) device 130 and a reader / writer 120, and may also include a network device 110. The network device 110 and the reader / writer 120 can communicate via a wireless link. (See attached image.) Figure 1 Image (a) exemplarily illustrates a plurality of Internet of Things (IoT) devices 130, a network device 110, and a reader 120. Optionally, the communication system may also include a plurality of IoT devices 130, a plurality of network devices 110, or a plurality of readers 120.

[0056] The aforementioned IoT device 130 is a device for inventorying assets. Assets may include hardware assets, software assets, and data assets related to the IoT device 130, which are not limited in this embodiment. In some embodiments, hardware assets may be the brand, model, quantity, or usage status of sensors, etc., which are not limited in this embodiment. In some embodiments, software assets may be the name, version, developer, functional description, or scope of use of application software, etc., which are not limited in this embodiment. In some embodiments, data assets may be user data using the IoT device 130, such as user identity information, user usage habits, etc., which are not limited in this embodiment. For some or all characteristics of the IoT device 130, please refer to the descriptions in existing standards of the 3rd Generation Partnership Project (3GPP).

[0057] It should be understood that some or all of the characteristics of the IoT device 130 described herein may refer to the description in the existing 3GPP standard. This description is only a possible example description, and the embodiments of this application are not limited thereto. As the communication standard protocol version evolves or is updated, some or all of the characteristics of the IoT device 130 described herein may refer to the evolved or updated version; or some or all of the characteristics of the IoT device 130 may also refer to the description in the related technology.

[0058] The Internet of Things (IoT) device 130 includes, but is not limited to: passive devices based on the backscattering principle (e.g., passive tags), semi-passive devices based on the backscattering principle (e.g., semi-passive tags), and active communication devices with power consumption in the hundreds of microwatts range. Passive devices can also be referred to as ultra-low-power terminals. Passive tags are just one form of this passive IoT device; those skilled in the art will understand that passive IoT devices are not limited to the form of passive tags.

[0059] The IoT device 130 can be applied in various scenarios, such as smart buildings, asset tracking, agriculture, and smart homes. For example, the IoT device 130 can be a smart switch, smart lock, smart meter, sensor-based device for monitoring machine status, environmental conditions, etc., building automation and control equipment, asset tagging device, etc., and this application embodiment does not limit this. In these scenarios, the networking requirements of the IoT device 130 are generally simple, possibly involving simple asset information reporting or sending very little sensor data.

[0060] Furthermore, different application scenarios lead to different requirements for IoT devices. Currently, considering the energy storage capacity and signal transmission capability of different devices, the following three categories of IoT devices are defined:

[0061] Device type 1a: This refers to devices without energy storage capabilities or independent signal generation and amplification capabilities. This is the lowest-cost device type, relying on backscattering for communication. The power consumption of the device during signal reception or transmission is less than 1 microwatt or less than 10 microwatts.

[0062] Device type 1b: This refers to devices with energy storage capabilities but no independent signal generation capabilities. Because the device can store energy, after collecting enough electrical energy, it can amplify the backscattered signal, covering a longer distance. The power consumption of this type of device during signal reception or transmission is between that of device type 1a and device type 2.

[0063] Device Type 2: This refers to devices that possess both energy storage capabilities and independent signal generation and amplification capabilities. The communication capabilities of this type of device are similar to traditional IoT devices. The power consumption during signal reception or transmission is less than 1 milliwatt or less than 10 milliwatts.

[0064] It should be noted that the embodiments of this application only use the above three device types as examples to illustrate the types of IoT devices. In actual applications, there may be other different device types, which are not limited in this application embodiment.

[0065] In some embodiments, the IoT device 130 can communicate with the reader 120 (including interactive signaling and / or data, where data includes, but is not limited to, asset information, sensor data, etc.). For example, the reader 120 can read data from the IoT device 130 and send the data to the network device 110. The data can be the result of the IoT device 130 executing commands such as read commands, write commands, disable commands, or start commands sent by the reader 120. For example, when the IoT device 130 is a sensor, in a sensor data reading scenario, the network device 110 sends a read command to the sensor through the reader 120, and the reader 120 can acquire the data from the sensor.

[0066] The network device 110 described above can be a device that provides wireless interface transmission services for the Internet of Things device 130. This application embodiment does not specifically limit the form of the network device 110.

[0067] Network device 110 can be network-side equipment such as access network equipment. Access network equipment is sometimes also called access node. Access network equipment has wireless transceiver capabilities and is used to communicate with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the aforementioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units that can implement some of the functions of a base station. Access network equipment can be macro base stations, micro base stations, or indoor stations, relay nodes or donor nodes, or wireless controllers in cloud radio access network (CRAN) scenarios. Optionally, access network equipment can also be servers, wearable devices, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a 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. The embodiments of this application do not limit the specific technology or device form used in the access network equipment. In this application, the access network equipment is referred to as a network device.

[0068] In this application, the means for implementing the functions of a network device can be a network device itself, or a means capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This means can be installed in or connected to the network device. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.

[0069] The reader 120 in this application can also be described as an AIoT reader, AIoT reader, AIoT reading device, AIoT reading device, or simply a reader or other names, without limitation. The reader 120 serves as an intermediate node for communication between the IoT device 130 and the access network device or core network device. The reader 120 can be an entity of the radio access network (RAN) (such as a base station or other network device) or a terminal device. For example, the reader 120 can be a base station, and a base station can have multiple readers 120.

[0070] The reader / writer 120 for the terminal device can be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal device.

[0071] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solutions provided in this application, the example of a terminal device being used to implement the functions of a terminal device is used to describe the technical solutions provided in this application.

[0072] Access network equipment and / or terminal equipment can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network equipment and terminal equipment. They can be deployed in the same or different scenarios; for example, both can be deployed on land simultaneously; or the access network equipment can be deployed on land while the terminal equipment is deployed on water, etc., and so on.

[0073] Taking reader 120 as a base station or other network device as an example, in another possible topology, as shown in the attached diagram... Figure 1 As shown in Figure (b), the communication system provided in this application embodiment may include: an Internet of Things (IoT) device 130 and a reader / writer 120, and the IoT device 130 and the reader / writer 120 can directly transmit data information.

[0074] It should be understood that, attached Figure 1 The topology shown in (b) is merely an example description, and the embodiments of this application are not limited thereto. It should also be understood that the appendix... Figure 1 The number of IoT devices 130 or readers 120 shown in (b) is merely an exemplary description, and the embodiments of this application are not limited thereto. For example, the number of IoT devices 130 may be 5, 10, etc.

[0075] Appendix Figure 2 This is a schematic diagram of the structure of an Internet of Things (IoT) device 130, a reader / writer 120, and a network device 110 provided in an embodiment of this application. The reader / writer 120 includes a first processor 1201, a first memory 1202, and a first transceiver 1203.

[0076] The first processor 1201 may include one or more processing units, such as: 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 microcontroller unit (MCU), a programmable logic device (PLD), an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0077] The first memory 1202 can be volatile memory or non-volatile memory, or it can 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 (DRRAM).

[0078] The first memory 1202 can exist independently and be connected to the first processor 1201 via a bus. Alternatively, the first memory 1202 can be integrated with the first processor 1201. The first memory 1202 stores application code that executes the scheme of this application, and its execution is controlled by the first processor 1201. The first processor 1201 executes the computer program instructions stored in the first memory 1202, thereby performing various functional applications and data processing of the terminal device, such as implementing the communication method described in the embodiments of this application.

[0079] The first processor 1201 and the first transceiver 1203 are connected via a bus. The first transceiver 1203 can be any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. The first transceiver 1203 includes a transmitter Tx and a receiver Rx.

[0080] The network device 110 includes a second processor 1101 and a second memory 1102. The second processor 1101 is used to execute computer program instructions stored in the second memory 1102, thereby performing various functional applications and data processing of the network device 110, such as implementing the communication method described in the embodiments of this application. The function of the second processor 1101 is the same as that of the first processor 1201, and the function of the second memory 1102 is the same as that of the first memory 1202, and will not be repeated here.

[0081] The Internet of Things (IoT) device 130 includes a third processor 1301, a third memory 1302, and a third transceiver 1303. The third processor 1301 executes computer program instructions stored in the third memory 1302 to perform various functional applications and data processing of the IoT device 130, such as implementing the communication method described in the embodiments of this application. The functions of the third processor 1301, the third memory 1302, and the third transceiver 1303 are described in the same way as the first transceiver 1203, and will not be repeated here.

[0082] To facilitate understanding of the embodiments of this application, the terminology used in this application will be briefly explained first. Optionally, the explanation of some terms may also refer to the explanations in the 3rd Generation Partnership Project (3GPP) standard protocol.

[0083] 1. Environmental Internet of Things

[0084] Ambient IoT (AIoT) utilizes the tiny amounts of energy naturally present in the environment to power countless miniature, extremely low-cost sensors, enabling them to connect to networks without batteries, thereby achieving seamless and imperceptible digitization of the entire physical world.

[0085] 2. Triggering periodicity

[0086] The periodicity of triggering refers to the fact that after the device is triggered to start by external conditions (such as an activation signal sent by a reader), it reports data according to a preset, fixed, or regularly changing schedule.

[0087] 3. Non-triggering periodicity

[0088] Non-triggered periodicity refers to the device spontaneously reporting data according to a preset, fixed, or regularly changing schedule, without requiring external conditions (such as access failure or sudden changes in sensor readings) to trigger its start.

[0089] 4. Event-driven

[0090] Event-driven communication refers to a device's communication behavior being triggered entirely by specific internal or external events that occur asynchronously and unpredictably in time. The device is typically in a low-power mode, such as deep sleep, and is only "woke up" and attempts to communicate when an event occurs.

[0091] 5. DOA business

[0092] DOA (Domain-Oriented Automation) refers to a business model in which Internet of Things (IoT) devices (such as sensors, actuators, and smart meters) or readers (such as RFID and barcode scanners) act as "initiators" or "triggers" of automated processes. Based on their own status, read data, or events, they automatically initiate communication or requests to network devices or platforms, thereby driving the backend business system to automatically execute predetermined processes.

[0093] It should be understood that the technical terms used in this application are for illustrative purposes only and not as limiting. For example, as technology evolves, technical terms may also change, and other technical terms that have the same technical meaning should also apply to this application.

[0094] In related technologies, AIoT communication between the reader 120 and the IoT device 130 includes a paging-random access process. (Appendix) Figure 3 This is a schematic diagram of a communication method 300 including a paging-random access process, based on related technologies. The reader / writer 120 may be an accessory... Figure 1 - Appendix Figure 2 The term "reader 120" can refer to any device within the reader 120 (e.g., a processor, chip, or chip system). The IoT device 130 can be an append-on... Figure 1 - Appendix Figure 2 The term 130 can refer to any IoT device, or a device within the IoT device 130 (e.g., a processor, chip, or chip system). For example, see the attached diagram. Figure 3 As shown, the communication method 300 may include the following steps S301-S304:

[0095] S301, the reader 120 sends a paging message to the IoT device 130.

[0096] The paging message is used by reader / writer 120 to page IoT device 130. The paging message also indicates the random access occasion (RAO) index n. n is an integer, greater than or equal to 0 and less than the total number of RAOs N. N is also referred to as the total number of RAOs within a paging cycle. An example is shown in the attached... Figure 4As shown, the paging message is responsible for configuring the random access resources within a paging cycle, specifically index n from index 0 to 31 of the random access opportunity (RAO). There are 4 sets of random access opportunities within a paging cycle (meaning a paging cycle can send 3 trigger messages), and each set of random access opportunities contains 8 random access opportunities. Therefore, there are 32 RAOs within a paging cycle, i.e., N=32.

[0097] It is understood that a paging cycle refers to the time slot between two paging messages. A paging cycle includes multiple random access sets. In this application, random access opportunities can also be described as access opportunities (AOs).

[0098] Optionally, during the time slot between the reader 120 sending a paging message to the IoT device 130 and the IoT device 130 sending msg1 to the reader 120, the IoT device 130 may choose not to compete for access, i.e., the IoT device 130 may choose not to receive the trigger message sent by the reader 120, or it may compete for access, i.e., receive the trigger message sent by the reader 120. This application embodiment does not limit the form of random access of the IoT device 130.

[0099] Correspondingly, the communication method 300 may or may not include step S302. In the case where the communication method 300 includes step S302, an example is shown in the attached document. Figure 3 As shown, the communication method 300 further includes the following step S302:

[0100] S302, the reader 120 sends a trigger message to the IoT device 130.

[0101] Accordingly, IoT device 130 receives a trigger message sent by reader 120. This trigger message is used to locate the next random access opportunity set. One trigger cycle includes one random access set, and one random access set includes m random access opportunities. m is the total number of time-frequency resource units (RAOs) in a time slot. N is an integer multiple of m. m is the total number of RAOs available for all IoT devices 130 to randomly select within a random access cycle; that is, within a random access response window, the network device 110 provides the IoT device 130 with the total number of time-frequency resource units (RAOs) for initiating the initial connection, also referred to as the total number of RAOs in the random access opportunity set.

[0102] m and the number of time slots X and the number of frequencies N of the access opportunity set. SFS The relationship satisfies the following formula (1):

[0103] m=X×N SFS Formula (1);

[0104] Where X is the number of time slots in the access opportunity set, that is, the number of different time segments divided on the time axis. N SFS The access opportunity set is the number of frequencies, i.e., the number of different subcarriers or channels divided on the frequency axis. Combining the time and frequency domain resources forms a two-dimensional time-frequency grid, where m is the total number of grid points. m is also referred to as the RAO in a triggering loop.

[0105] It is understandable that a trigger cycle refers to the time slot between two trigger messages within a paging cycle, or the time slot between a paging message and a trigger message (including the current paging message and the first trigger message, as well as the last trigger message and the next paging message).

[0106] For example, see attached Figure 4 As shown, there are 4 triggering cycles in one paging cycle (i.e., between two paging messages), which means one paging cycle can send 3 triggering messages, i.e., 4 random access opportunity sets. There are 8 RAOs in one triggering cycle, i.e., one random access opportunity set has 8 random access opportunities, m=8.

[0107] S303, IoT device 130 sends msg1 to reader 120.

[0108] msg1 is used to confirm a successful paging. msg1 carries a 16-bit pseudo-random number RN16. RN16 consists of 16 0s or 1s in binary; therefore, the value of RN16 typically ranges from 0 to 2. 16 (65535) (decimal). RN16 can guarantee sufficient randomness (65536 possible combinations with low probability of repetition) without consuming too many communication resources.

[0109] RN16 is used to represent the identity information (ID) of IoT device 130. Since the RN16 generated by each IoT device 130, and the RN16 generated by each IoT device 130 each time, is likely to be different, the IoT device 130 sends msg1 to the reader 120 to verify the identity of the IoT device 130 through RN16, thus ensuring the communication security between the IoT device 130 and the reader 120 and avoiding communication conflicts.

[0110] In the communication method 300 described in steps S301-S303 above, whether the IoT device 130 receives the trigger message sent by the reader 120 during the time slot between the reader 120 sending a paging message to the IoT device 130 and the IoT device 130 sending msg1 to the reader 120 is determined by judging whether n is less than m.

[0111] When n is less than m, it indicates that n, as indicated by the paging message, is in the current triggering loop. The IoT device 130 can execute step S302 directly without waiting for the trigger message. For example, see attached... Figure 4 As shown, after receiving the paging message from the reader 120, the IoT device 130 randomly selects an access opportunity with index n=5 from the 32 access opportunities indicated by the scheduling information carried in the paging message. The initial value of the countdown counter is set to AO_COUNTER=5. Since 5<8, the IoT device 130 searches for an access opportunity on the first random access set. Because AO_COUNTER<8, the IoT device 130 generates a random number and fills it into msg1, starting the countdown from n until it reaches 0. That is, msg1 is sent on the access opportunity with index n+1, i.e., 6.

[0112] If n is greater than or equal to m, it indicates that n, as indicated by the paging message, is not in the current triggering loop. The IoT device 130 can wait to receive a trigger message from the reader 120, i.e., execute step S302, update n=nm, and then determine whether the updated n is less than m. Specifically, the IoT device 130 updates n=nm and determines whether the updated n is less than m each time it receives a trigger message from the reader 120, until n is less than m. For example, see attached... Figure 4 As shown, after receiving the paging message from the reader 120, the IoT device 130 randomly selects an access opportunity with index n=14 from the 32 access opportunities indicated by the scheduling information carried in the paging message. The initial value of the countdown counter is set to AO_COUNTER=14. Since 14>8, the IoT device 130 will not search for an access opportunity on the first random access set. When the IoT device 130 receives the first trigger message, it updates n=nm, i.e., AO_COUNTER=14–8=6. Since AO_COUNTER<8, the IoT device 130 generates a random number, fills it into msg1, and then sends msg1 on the access opportunity with index n+1, i.e., 7.

[0113] S304, Reader 120 sends msg2 to IoT device 130.

[0114] msg2 is used to verify RN16, that is, to confirm the identity information of IoT device 130. If IoT device 130 successfully receives msg2 sent by reader 120, it indicates that reader 120 has confirmed the legitimate identity of IoT device 130, and IoT device 130 and reader 120 have successfully established a connection.

[0115] If IoT device 130 successfully receives msg2 sent by reader 120, the identity of IoT device 130 has been successfully verified. IoT device 130 may or may not transmit data to reader 120. Afterwards, IoT device 130 may disconnect from reader 120 and enter a sleep state. IoT device 130 will only be activated when reader 120 sends a paging message to IoT device 130 again. Optionally, communication method 300 may include steps S305-S306, or may not include steps S305-S306. When communication method 300 includes steps S305-S306, an example is shown in the attached... Figure 3 As shown, the communication method 300 further includes the following steps S305-S306:

[0116] S305, IoT device 130 sends msg3 to reader 120.

[0117] Among them, msg3 carries the device ID and uplink data of IoT device 130.

[0118] After the IoT device 130 and the reader 120 successfully establish a connection, the IoT device 130 and the reader 120 can transmit data. Specifically, the IoT device 130 can send its device ID and uplink data to the reader 120.

[0119] If the reader 120 successfully receives msg3 sent by the IoT device 130, it indicates that the IoT device 130 and the reader 120 have successfully connected.

[0120] S306, the reader 120 sends a negative confirmation message to the IoT device 130.

[0121] The negative confirmation message is used to confirm that the device ID matching of IoT device 130 failed. Optionally, reader 120 can send a confirmation message to IoT device 130 to confirm that the device ID matching of IoT device 130 was successful.

[0122] After receiving the device ID of IoT device 130 from IoT device 130, reader 120 verifies whether the device ID matches. If they do not match, reader 120 sends a negative acknowledgment message to IoT device 130, informing IoT device 130 that random access failed. If they match, reader 120 sends an acknowledgment message to IoT device 130, informing IoT device 130 that random access was successful.

[0123] The communication method 300 described in steps S301-S306 above is a paging-random access process between the reader 120 and the IoT device 130. The IoT device 130 receives a paging message sent by the reader 120, randomly accesses the reader 120 after successful paging, and transmits data with the reader 120 after successful random access.

[0124] In AIoT communication scenarios, based on traffic type, AIoT services include device-originating-by-device-terminated-trigger (DO-DTT) services and device-terminated (DT) services, such as inventory counting and command services. DO-DTT services refer to device-originating-by-device services triggered by a device-terminated trigger, such as communication initiated by IoT device 130 triggered by reader 120. DT services refer to device-terminated-by-device (R2D) communication initiated by reader 120 and received by IoT device 130. Both DO-DTT and DT services are applicable to scenarios where reader 120 actively triggers a response from IoT device 130.

[0125] In the AIoT business, besides DO-DTT and DT services, there are many other traffic types of services, as follows:

[0126] 1) Triggered Periodic and Event-Driven Services: After being triggered by external conditions, the device periodically (at fixed time intervals) reports data. When the device detects a preset event or state change (such as alarm triggering, sensor readings exceeding thresholds, receiving remote commands, etc.), it will immediately (or as soon as possible) proactively communicate with the network without waiting for a trigger. In other words, the device only communicates data when a specific event occurs or a threshold condition is met. For example, reader 120 may periodically send an activation signal to IoT device 130 to keep IoT device 130 in a ready state, enabling IoT device 130 to continuously monitor environmental data and transmit data to reader 120. When the data exceeds a preset threshold, IoT device 130 will immediately and proactively communicate with reader 120 without waiting for a trigger, thus enabling near real-time alarms for specific events.

[0127] 2) Non-triggered periodic and event-driven services: Devices periodically report data without requiring any internal or external conditions to trigger activation. When a device detects a preset event or state change (such as alarm triggering, sensor readings exceeding thresholds, or receiving remote commands), it will immediately (or as quickly as possible) proactively communicate with the network, without waiting for a trigger. In other words, the device only communicates data when a specific event occurs or threshold conditions are met. For example, IoT device 130 deployed in a forest continuously monitors environmental data and spontaneously and periodically transmits data to reader 120 without any triggering from reader 120. When IoT device 130 detects wildfire indicators, it will immediately and proactively communicate with reader 120 to issue an "on-demand" alarm.

[0128] The aforementioned triggered periodic and event-driven services, as well as non-triggered periodic and event-driven services, differ from the traffic types of DO-DTT and DT services in that: 1) Non-triggered periodicity: The IoT device 130 can spontaneously and periodically transmit data to the reader 120 without triggering from the reader 120. For example, see attached... Figure 5 As shown in (a) of the diagram, in R2D communication, the IoT device 130 spontaneously transmits data to the reader 120 periodically at fixed time intervals P, without requiring triggering by the reader 120. 2) Event-driven: The IoT device 130 can communicate with the reader 120 when a specific event occurs or a threshold condition is met. For example, see attached... Figure 5 As shown in (b) of the diagram, in R2D communication, IoT device 130 can communicate with reader 120 in event-driven, i.e., specific event-driven, communication. These two types of services are also known as DOA services, characterized by IoT device 130 spontaneously transmitting data to reader 120 without needing to receive an explicit trigger signal from reader 120.

[0129] Currently, in the 3GPP 5G standard, there are two resource allocation methods for random access of DOA services:

[0130] 1) Periodically allocate resources for DOA services. For example, reader 120 can pre-allocate device-to-reader (D2R) resources, and IoT device 130 supporting DOA services can periodically perform D2R transmissions with reader 120 based on the pre-configured D2R resources. In this case, periodically allocating resources will result in resource waste.

[0131] 2) Allocating resources for DOA services on demand. For example, an IoT device 130 supporting DOA services can request D2R resources from a reader 120 according to actual needs. The reader 120 responds to the on-demand request and allocates D2R resources to the IoT device 130 as needed. After receiving the D2R resources sent by the reader 120, the IoT device 130 can perform D2R transmission using the allocated D2R resources. In this case, although resources can be allocated to the IoT device 130 on demand, how to effectively allocate these resources is not clearly defined, which can lead to resource waste and affect communication efficiency and stability.

[0132] Furthermore, due to inherent errors in the crystal oscillator of the IoT device 130 and the Doppler effect (device movement), the actual frequency of the radio waves emitted by the IoT device 130 will deviate slightly from the nominal frequency expected by the reader 120 in the two resource allocation methods mentioned above. This deviation is also known as CFO. Currently, to compensate for CFO, the reader 120 can periodically send a single synchronization signal to the IoT device 130 to synchronize their times. However, CFO compensation with a single synchronization signal is only a time calibration, achieving preliminary CFO compensation. Therefore, it has low accuracy, poor anti-interference capability, and low efficiency. This results in a large clock deviation (e.g., a clock deviation of ±90 seconds every 15 minutes) when the high-frequency oscillator of the IoT device 130 is turned off during its sleep period. This may cause it to miss the pre-configured initial D2R transmission (as a scheduling request) time-frequency resources, further wasting resources.

[0133] In view of this, this application provides a communication method, apparatus, and system applied to Internet of Things (IoT) devices and readers. The method includes: sending a first synchronization message indicating a first access resource; monitoring first D2R messages sent by at least one IoT device on the first access resource to monitor signal strength on the first access resource, each IoT device supporting DOA services; sending a paging message to any one of the at least one IoT device to configure random access resources for the IoT device, wherein the random access resources configured for the IoT device are determined based on the number of at least one IoT device; the number of at least one IoT device is determined based on the signal strength of the first D2R messages sent by at least one IoT device on the first access resource; and receiving random access requests sent by the IoT devices on the random access resources.

[0134] Since each IoT device supporting DOA services sends a first D2R message to the reader on the first access resource, and each first D2R message corresponds to one IoT device and one signal strength, the reader can determine the number of IoT devices by monitoring the total signal strength on the first access resource. Based on this number, the reader can then determine the random access resources required by each IoT device. This allows for accurate, on-demand configuration of random access resources for each IoT device, significantly reducing access conflicts and congestion, improving access success rate and reliability, and significantly reducing power consumption, thereby saving resources and improving communication efficiency and stability.

[0135] In addition, in response to detecting a first D2R message sent by at least one IoT device, the reader sends a second synchronization message to each IoT device for time synchronization between each IoT device and the reader. There can be multiple second synchronization messages. This allows for multiple CFO compensations to be performed on the IoT devices, improving the accuracy, interference resistance, and efficiency of CFO compensation, thereby further saving resources.

[0136] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of this interactive illustration to illustrate the method, but this application does not limit the execution subjects of the interactive illustrations. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software that can implement all or part of the functions of the device.

[0137] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0138] In the following embodiments of this application, taking the paging-random access process between reader 120 and IoT device 130 as an example, a communication method provided by the embodiments of this application will be described in detail.

[0139] In one possible implementation, the IoT device 130 may or may not support DOA services. This application embodiment does not limit the type of IoT device 130.

[0140] In the following embodiments of this application, taking the example that each IoT device 130 supports DOA services, a communication method provided by the embodiments of this application will be described in detail.

[0141] Appendix Figure 6 This is a schematic diagram of a communication method 600 according to an embodiment of this application. It can be understood that the attached diagram... Figure 6 The reader 120 in the middle can be an accessory Figure 1 - Appendix Figure 2 The term "reader 120" can refer to any device within the reader 120 (e.g., a processor, chip, or chip system). The IoT device 130 can be an append-on... Figure 1 - Appendix Figure 2 The term 130 can refer to any IoT device, or a device within the IoT device 130 (e.g., a processor, chip, or chip system). For example, see the attached diagram. Figure 6 As shown, the communication method 600 may include the following steps S601-S607:

[0142] S601, Reader 120 sends the first synchronization message.

[0143] The first synchronization message is used to indicate the first time synchronization between the first access resource and the device receiving the first synchronization message and the reader 120. The first synchronization message corresponds to a first time length.

[0144] Optionally, the first access resource can be a time-frequency resource, such as a time-frequency block. A time-frequency block is the smallest scheduling unit or basic component of time and frequency resources. The reader 120 can allocate time-frequency blocks of different locations and sizes to multiple IoT devices 130, enabling the multiple IoT devices 130 to simultaneously send the first message on the corresponding time-frequency blocks.

[0145] In one possible implementation, the reader 120 may send the first synchronization message periodically (i.e., for a fixed first time length) or non-periodically (i.e., for a variable first time length). This application embodiment does not limit the form in which the reader 120 sends the first synchronization message.

[0146] When the first synchronization message is a periodic message, the first time length corresponding to the first synchronization message can be the period of the first synchronization message or the sending period. In one possible implementation, the periodic first synchronization message can be a long period (longer first time length) or a medium period (first time length in the middle, shorter than a long period, longer than a short period). This application embodiment does not limit the form of the periodic first synchronization message. In this application embodiment, the first synchronization message is a long period message.

[0147] The period for the reader 120 to send the first synchronization message can be set according to actual needs or based on empirical values, such as 160ms.

[0148] In one possible implementation, the reader 120 may send the first synchronization message in a broadcast manner. This application embodiment does not limit the form in which the reader 120 sends the first synchronization message. It is understood that if the reader 120 sends the first synchronization message in a broadcast manner, multiple IoT devices 130 may be listening to the first synchronization message.

[0149] In one possible implementation, there may be one or more (two or more) IoT devices 130. This application embodiment does not limit the number of IoT devices 130.

[0150] In the following embodiments of this application, taking at least one Internet of Things (IoT) device 130 as an example, the device listening to the first synchronization message sent by the reader 120 is used to describe in detail a communication method 600 provided in the embodiments of this application.

[0151] In this application, the first synchronization message can be described as a long period synchronization signaling (LPSS). The first synchronization message can have the format of a synchronization signal; in other words, it can be an initial synchronization signal. It can be understood that the first synchronization message corresponding to IoT device 130 is used for the initial time synchronization between IoT device 130 and reader 120. Since IoT device 130 is mostly in an ultra-low power "deep sleep" state, the periodic sending of the first synchronization message by reader 120 can periodically wake up IoT device 130 for a short period, allowing IoT device 130 to receive and parse the first synchronization message sent by reader 120, quickly synchronizing its time with reader 120. This achieves time calibration between IoT device 130 and reader 120 with low power consumption, performing initial CFO compensation. Furthermore, the first synchronization message can also provide a unified time reference for all IoT devices 130.

[0152] In this application, the first synchronization message can be sent on a preset time-frequency resource. The preset time-frequency resource can be set according to actual needs.

[0153] In one embodiment, the preset time and frequency resources may include a preset time point and a preset frequency. The Internet of Things device 130 can wake up at the preset time point and listen to the first synchronization message on the preset frequency.

[0154] In another implementation, the preset time-frequency resources include a preset period T, and the IoT device 130 can search for and listen to the first synchronization message at the preset period T after being woken up.

[0155] In the following embodiments of this application, taking at least one Internet of Things (IoT) device 130 including a first IoT device and a second IoT device as an example, the communication method 600 provided in the embodiments of this application will be described in detail.

[0156] Understandably, when reader 120 sends a first synchronization message, the first IoT device can receive it. The second IoT device can also receive the first synchronization message sent by reader 120.

[0157] In this configuration, the first synchronization message received by the first IoT device is used by the reader 120 to indicate a first access resource to the first IoT device. The first IoT device is one of the devices listening to the first synchronization message sent by the reader 120. The first synchronization message received by the second IoT device is used by the reader 120 to indicate a first access resource to the second IoT device. The second IoT device is at least one of the IoT devices 130 listening to the first synchronization message sent by the reader 120, excluding the first IoT device.

[0158] S602, on the first access resource, each of at least one IoT device 130 sends a first D2R message to the reader 120.

[0159] The first D2R message is used by the reader 120 to monitor the signal strength on the first access resource. Optionally, the first D2R message can be message 1 (msg1), and the first D2R message can be used to initiate a random access request to the reader.

[0160] It is understood that, on the first access resource, each of at least one IoT device 130 sends a first D2R message to the reader 120, including: on the first access resource, a first IoT device sends a first D2R message to the reader 120, and a second IoT device sends a first D2R message to the reader 120.

[0161] Specifically, the first D2R message sent by the first IoT device and the first D2R message sent by the second IoT device are used by the reader 120 to monitor the signal strength on the first access resource. The first D2R message sent by the first IoT device is one of at least one first D2R message sent by at least one IoT device 130. The first D2R message sent by the second IoT device is at least one of the first D2R messages sent by at least one IoT device 130 other than the first D2R message sent by the first IoT device.

[0162] On the first access resource, the first D2R message sent by each of the at least one IoT device 130 to the reader 120 is, since it is sent before acquiring a random access opportunity, a form of uncoordinated contention. Essentially, multiple IoT devices 130 (i.e., transmitters) simultaneously transmit the first D2R message on the same shared wireless medium, which can cause signal superposition and interference. Some first D2R messages may collide on the first access resource, making it impossible for the reader 120 (i.e., receiver) to correctly parse some first D2R messages. Therefore, although each of the at least one IoT device 130 sends a first D2R message to the reader 120, the reader 120 may not be able to correctly parse the first D2R message sent by each of the at least one IoT device 130.

[0163] S603, Reader 120 monitors at least one Internet of Things device 130 sending a first D2R message on a first access resource.

[0164] After each of the at least one IoT device 130 sends a first D2R message to the reader 120 on the first access resource, since the reader 120 cannot receive the first D2R message sent by any of the at least one IoT device 130, the reader 120 can monitor the first D2R message sent by at least one IoT device 130 on the first access resource, so as to determine the number of at least one IoT device 130 based on the signal strength of the first D2R message sent by at least one IoT device 130.

[0165] Optionally, the reader 120 can monitor the total signal strength of the first D2R message based on the received signal strength indicator (RSSI) measurement circuit inside the reader 120, using the preamble and reference signal contained in the first D2R message.

[0166] S604, the reader 120 determines the random access resource of each IoT device 130 based on the signal strength of the first D2R message sent by at least one IoT device 130 on the first access resource.

[0167] Optionally, the reader 120 can determine the number of at least one IoT device 130 based on the signal strength of the first D2R message sent by at least one IoT device 130, and then determine the random access resources that at least one IoT device 130 needs to be configured based on the number of at least one IoT device 130, thereby configuring random access resources for each IoT device 130.

[0168] In one possible implementation, after monitoring the total signal strength of the first D2R message, the reader 120 can determine the number of at least one IoT device 130 using an air-channel reference comparison method. For example, before at least one IoT device 130 sends the first D2R message on the first access resource, the reader 120 can first measure the background noise power Pnoise on the first access resource, and after at least one IoT device 130 sends the first D2R message on the first access resource, measure the total received power Ptotal on the first access resource. The number of at least one IoT device 130 can be roughly estimated using Pnoise and Ptotal. Specifically, if Ptotal is slightly higher than Pnoise, one or a few (e.g., 2 or 3) IoT devices 130 are identified; if Ptotal is much higher than Pnoise, multiple (e.g., 4, 5, 6, etc.) IoT devices 130 are identified. Alternatively, the number of at least one IoT device 130 can be determined using advanced signal processing and multi-antenna techniques. For example, the dimension of the signal subspace can be analyzed using the signal covariance matrix received by multiple antennas. This dimension is strongly correlated with the number of signal sources (i.e., IoT devices 130), thereby accurately determining the number of at least one IoT device 130. This application does not limit the method used to determine the number of at least one IoT device 130.

[0169] In one possible implementation, the reader 120 can allocate random access resources to each IoT device 130 in a fixed allocation manner based on the total amount of random access resources and the number of at least one IoT device 130. For example, if the number of at least one IoT device 130 is determined to be 'a', and the number of AOs in the random access resources is 'm', then the random access resources allocated to each IoT device 130 are 'm / a'. Alternatively, random access resources can be allocated to each IoT device 130 using dynamic grouping, game theory-based distributed, or adaptive algorithms. For example, if the number of at least one IoT device 130 is determined to be 'a', and the number of AOs in the random access resources is 'm', the IoT devices 130 of quantity 'a' can be divided into three groups: the first group has a / 5 IoT devices, the second group has 2a / 5 IoT devices, and the third group has 2a / 5 IoT devices. The first group of IoT devices 130 is allocated m / 4 random access resources, the second group has m / 2 random access resources, and the third group has m / 4 random access resources. The random access resources allocated to each IoT device 130 in the first group are 5m / 4a, the random access resources allocated to each IoT device 130 in the second group are 5m / 4a, and the random access resources allocated to each IoT device 130 in the third group are 5m / 8a. This embodiment of the application does not limit the allocation method of random access resources allocated by the reader 120 to each IoT device 130.

[0170] After the reader 120 determines the random access resource of each IoT device 130 based on the signal strength of the first D2R message sent by at least one IoT device 130 on the first access resource, optionally, in order to compensate for CFO, further save resources, and locate the paging message corresponding to the IoT device 130, the reader 120 may send a second synchronization message to each IoT device 130 in response to detecting the first D2R message sent by at least one IoT device 130, or may not send a second synchronization message to each IoT device 130. The embodiments of this application do not limit the content of communication between the reader 120 and the IoT device 130.

[0171] Correspondingly, the communication method 600 may or may not include step S605. When the communication method 600 includes step S605, an example is shown in the appendix. Figure 6 As shown, the communication method 600 further includes the following step S605:

[0172] S605, in response to detecting a first D2R message sent by at least one IoT device 130, the reader 120 sends a second synchronization message.

[0173] Accordingly, each of at least one IoT device 130 can receive a second synchronization message sent by the reader 120.

[0174] In this application, the second synchronization message can be described as an on-demand synchronization signaling (OD-SS). The second synchronization message can have the format of a synchronization signal; in other words, the second synchronization message can be a synchronization signal.

[0175] In one possible implementation, the second synchronization message sent by the reader 120 can be sent periodically or non-periodically. This application embodiment does not limit the form of the second synchronization message sent by the reader 120.

[0176] In the case where the second synchronization message is a periodic message, in one possible implementation, the periodic second synchronization message can be of medium or short period. This application embodiment does not limit the form of the periodic second synchronization message. In this application embodiment, the second synchronization message is a short-period message.

[0177] The period for the reader 120 to send the second synchronization message can be set according to actual needs or based on empirical values, such as 20ms.

[0178] In one embodiment, for any one of at least one IoT device 130, the second synchronization message is sent by the reader 120 within a first time length. The number of second synchronization messages is greater than or equal to a first quantity threshold. The interval between the start time of the second synchronization message and the end time of the first synchronization message is less than or equal to a preset number of time units.

[0179] The first quantity threshold is the threshold for the number of second synchronization messages sent by the reader 120 within the first time length, and can be set according to actual needs. For example, it can be obtained by counting multiple quantities of second synchronization messages sent by the reader 120 within the first time length, such as the average, median, or minimum of multiple quantities of second synchronization messages sent by the reader 120 within the first time length; it can also be set according to empirical values, such as 2, 3, or 4.

[0180] The preset quantity is the default quantity, which can be set according to actual needs or based on experience, such as 2, 3 or 4.

[0181] Among them, the second synchronization message corresponding to the IoT device 130 is used for the second time synchronization between the IoT device 130 and the reader / writer 120, as well as the paging message corresponding to the location of the IoT device 130.

[0182] In this way, IoT device 130 and reader 120 can achieve a second time synchronization. Since the second synchronization message provides a more accurate timestamp, IoT device 130 can perform multiple fine-tuning adjustments based on multiple second synchronization messages, improving the accuracy of time synchronization between IoT device 130 and reader 120. This improves the accuracy, anti-interference capability, and efficiency of CFO compensation, enabling reader 120 to dynamically and efficiently configure random access resources for each IoT device 130. This avoids IoT device 130 missing the random access resources configured by reader 120 due to time asynchrony with reader 120, thus preventing resource waste. Furthermore, the second synchronization message locates the corresponding paging message for IoT device 130, ensuring that each IoT device 130 accurately receives the corresponding paging message sent by reader 120, thereby obtaining the corresponding random access resources configured by reader 120.

[0183] Understandably, when reader 120 sends a second synchronization message, the first IoT device can receive the second synchronization message sent by reader 120. The second IoT device can also receive the second synchronization message sent by reader 120.

[0184] The second synchronization message received by the first IoT device is used for the second time synchronization between the first IoT device and the reader 120, as well as for locating the paging message corresponding to the first IoT device. The second synchronization message received by the first IoT device is one of the second synchronization messages sent by the reader 120.

[0185] The second synchronization message received by the second IoT device is used for the second time synchronization between the second IoT device and the reader 120, as well as for locating the paging message corresponding to the second IoT device. The second synchronization message received by the second IoT device is at least one of the second synchronization messages sent by the reader 120 other than the second synchronization message received by the first IoT device.

[0186] S606, the reader 120 sends a paging message to each of at least one Internet of Things (IoT) device 130.

[0187] Accordingly, each of the at least one IoT device 130 receives a paging message sent by the reader 120. The paging message is used by the reader 120 to configure random access resources for each of the at least one IoT device 130.

[0188] Understandably, reader 120 can send paging messages to the first IoT device. Reader 120 can also send paging messages to the second IoT device. Accordingly, the first IoT device receives the paging message sent by reader 120. The second IoT device receives the paging message sent by reader 120.

[0189] The paging message received by the first IoT device is used by the reader 120 to configure random access resources for the first IoT device. The paging message received by the first IoT device is one of the paging messages sent by the reader 120 to each IoT device 130.

[0190] The paging message received by the second IoT device is used by the reader 120 to configure random access resources for the second IoT device. The paging message received by the second IoT device is at least one of the paging messages sent by the reader 120 to each IoT device 130, excluding the paging message received by the first IoT device.

[0191] S607. On the corresponding random access resource, at least one of the IoT devices 130 sends a random access request to the reader 120.

[0192] Accordingly, reader 120 receives random access requests from each of at least one IoT device 130. After each IoT device 130 receives a paging message, based on the random access resource indicated by the paging message, each IoT device 130 sends a random access request to reader 120 on the corresponding random access resource.

[0193] Understandably, on the random access resources of the first IoT device, the first IoT device can send a random access request to the reader 120. The second IoT device can also send a random access request to the reader 120. Correspondingly, the reader 120 receives the random access request sent by the first IoT device. The reader 120 also receives the random access request sent by the second IoT device.

[0194] The random access request sent by the first IoT device is one of the random access requests sent by each of the at least one IoT device 130.

[0195] The random access request sent by the second IoT device is at least one of the random access requests sent by each of the at least one IoT device 130, other than the random access request sent by the first IoT device.

[0196] In the communication method 600 described in steps S601-S607 above, each IoT device 130 supporting DOA service sends a first D2R message to the reader 120 on the first access resource indicated by the reader 120. Each first D2R message corresponds to one IoT device 130 and a signal strength. Therefore, by monitoring the total signal strength on the first access resource, the reader 120 can determine the number of IoT devices 130, and thus determine the random access resources required by each IoT device 130 based on the number of IoT devices 130. This accurately determines the random access resources that need to be configured for each IoT device 130, significantly reducing access conflicts and congestion, improving the access success rate and reliability of IoT devices 130, and significantly reducing the power consumption of IoT devices, thereby saving resources and improving communication efficiency and stability. Alternatively, in response to detecting a first D2R message sent by at least one IoT device 130, the reader 120 sends a second synchronization message to each IoT device 130 for time synchronization between each IoT device 130 and the reader 120. This allows for multiple CFO compensations to be performed on the IoT devices 130, improving the accuracy, interference resistance, and efficiency of CFO compensation, and further saving resources.

[0197] The communication between at least one IoT device 130 and the reader 120 can be described in detail through the communication between any one of the IoT devices 130 and the reader 120.

[0198] In the following embodiments of this application, taking the communication between any one of the at least one Internet of Things (IoT) devices 130 and the reader 120 as an example, a communication method provided by the embodiments of this application will be described in detail.

[0199] Appendix Figure 7 - Appendix Figure 8 This is a schematic diagram of a communication method 700 according to an embodiment of this application. It can be understood that the attached diagram... Figure 7 - Appendix Figure 8 The reader 120 in the middle can be an accessory Figure 1 - Appendix Figure 2 The term "reader 120" can refer to any device within the reader 120 (e.g., a processor, chip, or chip system). The IoT device 130 can be an append-on... Figure 1 - Appendix Figure 2 The term 130 can refer to any IoT device, or a device within the IoT device 130 (e.g., a processor, chip, or chip system). For example, see the attached diagram. Figure 7 - Appendix Figure 8 As shown, the communication method 700 may include the following steps S701-S719:

[0200] S701, Reader 120 sends the first synchronization message.

[0201] Accordingly, IoT device 130 receives the first synchronization message sent by reader 120. Step S701 is the same as the first IoT device in step S601 described above, and has been described in detail in step S601, so it will not be repeated here. For example, see the attached... Figure 9 As shown, reader 120 sends multiple (e.g., two) first synchronization messages. Optionally, reader 120 sends the first synchronization messages to IoT device 130.

[0202] S702, On the first access resource, the IoT device 130 sends a first D2R message to the reader 120.

[0203] Accordingly, the reader 120 receives the first D2R message sent by the IoT device 130. Step S702 is the same as the content of the first IoT device in step S602 above, and has been described in detail in step S602 above, so it will not be repeated here.

[0204] S703, Reader 120 monitors at least one Internet of Things device 130 sending a first D2R message on a first access resource.

[0205] Step S703 is the same as step S603 above, and has been described in detail in step S603 above, so it will not be repeated here.

[0206] S704, Reader 120 determines whether the signal strength of the first D2R message on the first access resource is greater than the first threshold.

[0207] After the reader 120 detects the first D2R message sent on the first access resource, it can determine whether the signal strength of the first D2R message on the first access resource is greater than the first threshold.

[0208] The first threshold is the signal strength threshold of the first D2R message on the first access resource, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple signal strengths of the first D2R message on the first access resource, such as the mean, median, or minimum of multiple signal strengths of the first D2R message on the first access resource; it can also be set based on empirical values, such as -70dBm.

[0209] The reader 120 determines whether the signal strength of the first D2R message on the first access resource is greater than a first threshold in order to avoid misjudgment. This is because the reader 120 allocates its limited computing resources to calculating the signal strength of the first D2R message on the first access resource, thereby saving power and computing resources. For example, if the signal is interfered with by noise, computing resources would be wasted calculating the signal strength of the interference or noise signal.

[0210] If the signal strength of the first D2R message on the first access resource is greater than the first threshold, step S705 is executed. If the signal strength of the first D2R message on the first access resource is less than or equal to the first threshold, it indicates that there is a high probability of interference or noise signals on the first access resource, and the reader 120 can return to step S703 to monitor the first D2R message sent by at least one IoT device 130 on the first access resource again.

[0211] S705, the reader 120 determines the number of at least one Internet of Things (IoT) device 130 based on the signal strength of the first D2R message on the first access resource.

[0212] If the signal strength of the first D2R message on the first access resource is greater than the first threshold, it indicates that the first D2R message on the first access resource is more likely. The reader 120 can allocate computing resources to calculate the signal strength of the first D2R message on the first access resource, and thus determine the number of at least one IoT device 130 based on the signal strength of the first D2R message on the first access resource.

[0213] Step S705 is the same as step S604 above, and has been described in detail in step S604 above, so it will not be repeated here.

[0214] S706, the reader 120 determines the random access resources required by each IoT device 130 based on the number of at least one IoT device 130.

[0215] After determining the number of at least one IoT device 130, the reader 120 can determine the random access resources required by each IoT device 130 based on the number of at least one IoT device 130.

[0216] Step S706 is the same as step S604 above, and has been described in detail in step S604 above, so it will not be repeated here.

[0217] Similarly, optionally, the communication method 700 may include steps S707-S709, or may not include steps S707-S709, and the embodiments of this application do not limit this.

[0218] In the following embodiments of this application, taking the communication method 700 including steps S707-S709 as an example, a detailed description of a communication method 700 provided in the embodiments of this application will be given.

[0219] S707, In response to detecting the first D2R message sent by the IoT device 130, the reader 120 sends a second synchronization message.

[0220] Accordingly, IoT device 130 can receive the second synchronization message sent by reader 120. Step S708 is the same as the content of the first IoT device in step S605 above, and has been described in detail in step S605 above, so it will not be repeated here. For example, see attached Figure 9 As shown, reader 120 sends multiple (e.g., four) second synchronization messages within a first time length of the second first synchronization message. Optionally, reader 120 sends the second synchronization messages to IoT device 130.

[0221] S708, IoT device 130 determines whether it has received the second synchronization message.

[0222] After the reader 120 sends the second synchronization message, the IoT device 130 can determine whether it has received the second synchronization message. Specifically, the IoT device 130 can determine whether it has received the second synchronization message by detecting the received signal.

[0223] In one possible implementation, the IoT device 130 can determine whether a second synchronization message has been received by detecting the energy of the received signal or by detecting a valid second synchronization signal sequence (SSS) of the received signal. This application embodiment does not limit the method of determining whether a second synchronization message has been received by detecting the received signal.

[0224] In one embodiment, when the IoT device 130 determines whether it has received a second synchronization message by detecting the energy of the received signal, if the peak power of the received signal is greater than a second threshold, the IoT device 130 receives the second synchronization message; if the peak power of the received signal is less than or equal to the second threshold, the IoT device 130 does not receive the second synchronization message.

[0225] The second threshold is the peak power threshold of the received signal of the IoT device 130, which can be set according to actual needs. For example, it can be obtained by statistically analyzing the peak power of multiple received signals of the IoT device 130, such as the average, median, minimum, or maximum peak power of multiple received signals of the IoT device 130; it can also be set based on empirical values, such as -20dBm.

[0226] In another implementation, when the IoT device 130 determines whether it has received the second synchronization message by detecting a valid SSS sequence of the received signal, the IoT device 130 receives the second synchronization message if a valid SSS sequence is decoded from the received signal, and does not receive the second synchronization message if a valid SSS sequence is not decoded from the received signal.

[0227] If the IoT device 130 receives the second synchronization message, step S709 is executed. If the IoT device 130 does not receive the second synchronization message, indicating that the IoT device 130 has not received any message instruction sent by the reader 120, step S708 is executed to determine again whether the second synchronization message has been received.

[0228] S709 and IoT device 130 synchronize time with reader 120 based on the second synchronization message and locate the paging message.

[0229] When IoT device 130 receives the second synchronization message, it indicates that IoT device 130 has received the instruction from reader 120 regarding the second synchronization message. Based on the instruction of the second synchronization message, IoT device 130 synchronizes its time with reader 120 and locates the paging message sent to it by reader 120. In this way, IoT device 130 can not only synchronize its time with reader 120 through the second synchronization message, further saving resources, but also identify the paging message sent to it by reader 120 through the second synchronization message, that is, the random access resources allocated to it by reader 120.

[0230] S710 and reader 120 send paging messages to IoT device 130.

[0231] Accordingly, IoT device 130 receives a paging message sent by reader 120. Step S710 is the same as the first IoT device in step S606 above, and has been described in detail in step S606 above, so it will not be repeated here. For example, see attached... Figure 9 As shown, after sending the fourth second synchronization message, reader 120 sends a paging message.

[0232] It is understandable that after the IoT device 130 locates the paging message, it receives the paging message sent to it by the reader 120, thereby identifying the random access resources allocated to it by the reader 120.

[0233] S711, IoT device 130 reads the random access resources configured in the paging message.

[0234] After receiving a paging message from the reader 120, the IoT device 130 can read the random access resources configured in the paging message. These random access resources include a random access opportunity index n.

[0235] S712, IoT device 130 generates random numbers.

[0236] The IoT device 130 can generate random numbers. The random number generated by the IoT device 130 is RN16, which is used to verify the identity of the IoT device 130, ensure the communication security between the IoT device 130 and the reader 120, and avoid communication conflicts.

[0237] S713, IoT device 130 determines whether n is less than m.

[0238] After reading the random access resources configured in the paging message, the IoT device 130 can determine whether n is less than m.

[0239] If n is less than m, it indicates that n, as indicated by the paging message, is in the current triggering loop. The IoT device 130 can proceed directly to step S718 without waiting for the trigger message, filling the random number into msg1. If n is greater than or equal to m, it indicates that n, as indicated by the paging message, is not in the current triggering loop. The IoT device 130 waits to receive the trigger message sent by the reader 120 before proceeding to step S715.

[0240] S714, reader 120 sends a trigger message to IoT device 130.

[0241] Accordingly, the IoT device 130 receives a trigger message sent by the reader 120. The trigger message indicates the next set of random access opportunities. For example, see the attached... Figure 9 As shown, after sending a paging message, reader 120 sends a trigger message indicating the next random access opportunity set. A paging cycle includes four trigger messages.

[0242] If n is greater than or equal to m, it indicates that n indicated by the paging message is not in the current triggering loop. After the reader 120 sends a trigger message to the IoT device 130, the IoT device 130 can wait to receive the trigger message sent by the reader 120.

[0243] S715, IoT device 130 determines whether a trigger message has been received.

[0244] While the reader 120 sends a trigger message to the IoT device 130, and the IoT device 130 waits to receive the trigger message sent by the reader 120, the IoT device 130 can determine whether it has received the trigger message.

[0245] If IoT device 130 does not receive a trigger message, it indicates that IoT device 130 has not received the indication of the trigger message sent by reader 120, and step S716 is executed to continue waiting. If IoT device 130 receives a trigger message, it indicates that IoT device 130 has received the indication of the trigger message sent by reader 120, and step S717 is executed.

[0246] S716, IoT device 130 is not working.

[0247] If the IoT device 130 does not receive a trigger message, it indicates that the IoT device 130 has not received the instruction of the trigger message sent by the reader 120. The IoT device 130 can remain inactive and continue to wait.

[0248] S717, IoT device 130 update n=nm.

[0249] When IoT device 130 receives a trigger message, it indicates that IoT device 130 has received the trigger message sent by reader 120, updates n=nm, and returns to step S713 to perform the next round of judgment.

[0250] S718, IoT device 130 fills msg1 with a random number.

[0251] When n is less than m, indicating that n, as indicated by the paging message, is in the current triggering loop, the IoT device 130 can fill the random number into msg1 without waiting for the trigger message. Optionally, the IoT device 130 can fill the random number into the random field of msg1.

[0252] S719, IoT device 130 selects the (n+1)th random access opportunity and sends msg1 to reader 120.

[0253] Accordingly, the reader 120 receives msg1 sent by the IoT device 130. msg1 carries a random number generated by the IoT device 130, used to request access to the reader 120. After filling msg1 with the random number, the IoT device 130 sends msg1 carrying the random number generated by the IoT device 130 to the reader 120, requesting access to the reader 120, and verifying the IoT device 130 using the random number generated by the IoT device 130.

[0254] The subsequent random access procedure is the same as that in related technologies, and has been described in detail in steps S304-S306 above, so it will not be repeated here. For example, see the attached... Figure 10 As shown, after the reader / writer 120 sends a paging message to the IoT device 130, the IoT device 130 can send msg1 to the reader / writer 120. After receiving msg1 from the IoT device 130, the reader / writer 120 can send msg2 to the IoT device 130. After receiving msg2 from the reader / writer 120, the IoT device 130 can send msg3 to the reader / writer 120. Alternatively, after sending a paging message to the IoT device 130, the reader / writer 120 can send a trigger message to the IoT device 130. After receiving the trigger message from the reader / writer 120, the IoT device 130 can send msg1 to the reader / writer 120. After receiving msg1 from the IoT device 130, the reader / writer 120 can send msg2 to the IoT device 130. After receiving msg2 from the reader / writer 120, the IoT device 130 can send msg3 to the reader / writer 120. Similarly, a paging loop includes two trigger messages, or three trigger loops, and each trigger loop includes msg1, msg2, and msg3.

[0255] The communication method 700 described in steps S701-S719 above, since each msg1 on the first access resource corresponds to one IoT device 130 and one signal strength, the reader 120 can determine the number of IoT devices 130 by monitoring the total signal strength on the first access resource. Therefore, based on the number of IoT devices 130, the random access resources required by each IoT device 130 can be determined. This allows for the configuration of random access resources for each IoT device 130 on demand, significantly reducing access conflicts and congestion, improving the access success rate and reliability of IoT devices 130, and significantly reducing the power consumption of IoT devices, thereby saving resources and improving communication efficiency and stability. Optionally, in response to detecting a msg1 sent by an IoT device 130, the reader 120 sends a second synchronization message. The IoT device 130 determines whether it has received the second synchronization message. If the IoT device 130 has not received the second synchronization message, it does not take any action. Upon receiving the second synchronization message, the IoT device 130 synchronizes its time with the reader 120 based on the second synchronization message and locates the paging message. This allows for multiple CFO compensations to be performed on the IoT device 130, improving the accuracy, interference resistance, and efficiency of CFO compensation, further saving resources. Therefore, in this communication method 700, the reader 120 can also send multiple D2R synchronization signals to the IoT device 130 for CFO compensation, thereby further saving resources.

[0256] If IoT device 130 and reader 120 successfully compete for random access for the first time, IoT device 130 will access reader 120 on the (n+1)th random access opportunity based on the n indicated by the paging message.

[0257] Optionally, if the IoT device 130 and the reader 120 fail to compete for random access in the first instance, the IoT device 130 may also randomly select a random access opportunity to access the reader 120 based on the set of random access opportunities indicated by the trigger message received subsequently.

[0258] Appendix Figure 11 This is a schematic diagram of a communication method 1100 according to an embodiment of this application. It can be understood that the attached diagram... Figure 11 The reader 120 in the middle can be an accessory Figure 1 - Appendix Figure 2 The term "reader 120" can refer to any device within the reader 120 (e.g., a processor, chip, or chip system). The IoT device 130 can be an append-on... Figure 1 - Appendix Figure 2 The term 130 can refer to any IoT device, or a device within the IoT device 130 (e.g., a processor, chip, or chip system). For example, see the attached diagram. Figure 11 As shown, the communication method 1100 may include the following steps S1101-S1106:

[0259] S1101, IoT device 130 failed its first attempt to compete for random access to reader 120.

[0260] If the IoT device 130 fails to gain random access to the reader 120 on its first attempt based on the paging message indication n, a backoff algorithm can be initiated to avoid collisions. This means that instead of immediately retrying, the device waits for a random period of time. For example, it waits for the arrival of the next trigger message and then initiates a random access request again based on that trigger message. Specifically, the process of waiting for and initiating a random access request again based on the next trigger message can be referred to in S1102-S1106 below:

[0261] S1102, the reader 120 sends a trigger message to the IoT device 130.

[0262] Accordingly, IoT device 130 receives a trigger message sent by reader 120.

[0263] The trigger message is used to indicate the next set of random access opportunities.

[0264] S1103, IoT device 130 randomly selects an AO from the set of random access opportunities that trigger the message indication.

[0265] After receiving the trigger message sent by the reader 120, the IoT device 130 can randomly select an AO from the set of random access opportunities indicated by the trigger message.

[0266] S1104, IoT device 130 generates random numbers.

[0267] Step S1104 is the same as step S712 above, and has been described in detail in step S712 above, so it will not be repeated here.

[0268] S1105, IoT device 130 fills the random number into msg1.

[0269] Step S1105 is the same as step S718 above, and has been described in detail in step S718 above, so it will not be repeated here.

[0270] S1106, IoT device 130 sends msg1 again to reader 120 on the AO selected in S1103.

[0271] The difference between step S1106 and step S719 above is that step S1106 does not use a countdown method to select the AO. Instead, it directly sends msg1 to the reader 120 from the randomly selected AO. For example, if the AO with index 25 is selected, msg1 is sent directly to the reader 120 from the AO with index 25. All other aspects of step S1106 are the same as those in step S719 above, and have been described in detail in step S719 above, so they will not be repeated here.

[0272] The communication method 1100 described in steps S1101-S1106 above can ensure that when a collision occurs (multiple IoT devices 130 attempt to access the reader 120 at the same time), the multiple IoT devices 130 are dispersed to different time points / access opportunities to retry, thereby greatly reducing the probability of multiple IoT devices 130 colliding again.

[0273] Regarding the communication method provided in the embodiments of this application, see Appendix Figure 12 - Appendix Figure 13 This is a schematic diagram of a communication method according to an embodiment of this application. Examples are shown in the attached diagram. Figure 12 - Appendix Figure 13 As shown, the reader 120 periodically sends a first synchronization message (e.g., period greater than 160ms) to indicate a first access resource. At least one IoT device 130 supporting DOA detects the first synchronization message and then sends a first D2R message to the reader 120 on the first access resource indicated by the first synchronization message. The reader 120 monitors the first D2R messages sent by at least one IoT device 130 on the first access resource and determines whether the signal strength of the first D2R message is greater than a first threshold. If the signal strength of the first D2R message on the first access resource is greater than the first threshold, the reader 120 determines the number of at least one IoT device 130 based on the signal strength of the first D2R message on the first access resource. Then, in response to detecting the first D2R message sent by at least one IoT device 130, the reader 120 sends four second synchronization messages (e.g., period of 20ms) within a first time length of the first synchronization message. The interval between the start time of the second synchronization message and the end time of the first synchronization message is less than or equal to a preset number of time units. When at least one IoT device 130 receives the second synchronization message, the IoT device 130 synchronizes its time with the reader 120 and locates its own paging message indicating random access resources. A paging cycle includes 9 trigger cycles (i.e., one paging message corresponds to 9 trigger cycles), and a trigger cycle (i.e., a set of random access opportunities) includes m (i.e., 4) random access opportunities (which can be simply referred to as access opportunities / AO).

[0274] For example, see attached Figure 12 As shown, for any one of the at least one IoT devices 130, such as the first IoT device, the first IoT device randomly selects an access opportunity 10 according to the random access resource indicated by the paging message, and sets the access opportunity counter AO_COUNTER=10. Since AO_COUNTER>m (4), the first IoT device monitors subsequent trigger messages. When the first IoT device receives the first trigger message sent by the reader 120, AO_COUNTER=10–4=6>4. Therefore, the first IoT device continues to monitor the next trigger message. When the first IoT device receives the second trigger message sent by the reader 120, AO_COUNTER=6–4=2<4. The first IoT device generates a first random number RD1 and fills the first random number RD1 into the random field of msg1. Then, on the access opportunity 10, it sends msg1 carrying the first random number RD1 to the reader 120.

[0275] For example, see attached Figure 13 As shown, for any IoT device 130 other than the first IoT device, such as the second IoT device, the second IoT device randomly selects access opportunity 21 based on the access resource information provided by the paging message, and sets AO_COUNTER=21. Since AO_COUNTER>m (4), the second IoT device monitors subsequent trigger messages. When the second IoT device receives one trigger message sent by the reader 120, AO_COUNTER=AO_COUNTER–4. Similarly, when the second IoT device receives the fifth trigger message sent by the reader 120, AO_COUNTER=21–4×5=1<4. The second IoT device generates a second random number RD2 and fills the random field of msg1 with the second random number RD2. Then, on access opportunity 21, it sends msg1 carrying the second random number RD2 to the reader 120. However, msg1 carrying the second random number RD2 conflicts with msg1 sent by other IoT devices 130, and the second IoT device fails to compete for access to reader 120.

[0276] After the second IoT device fails to compete for access to reader 120 for the first time, when the second IoT device receives the trigger message (i.e. the 6th one) sent by reader 120 again, it randomly selects AO(26) from the set of random access opportunities (i.e. access opportunities 24, 25, 26 and 27) indicated by the trigger message. The second IoT device generates a random number RD3 and puts it into the random field of msg1. Then, on access opportunity 26, it sends msg1 carrying the third random number RD3 to reader 120.

[0277] It should be understood that, attached Figure 1 To be continued Figure 13 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on the accompanying drawings. Figure 1 To be continued Figure 13 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0278] The above text, combined with the appendix Figure 1 To be continued Figure 13 The present application describes in detail the communication method provided in its embodiments. The following will refer to the appendix... Figure 14 To be continued Figure 15 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0279] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step 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.

[0280] Appendix Figure 14 This is a schematic block diagram of a communication device provided in an embodiment of this application. (See attached diagram) Figure 14 As shown, the communication device 1400 may include a communication module 1410. The communication module 1410 can implement corresponding communication functions, which can be internal communication functions of the communication device 1400 or communication functions between the communication device 1400 and other devices. Optionally, the communication module 1410 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 1400 further includes a processing module 1420. The processing module 1420 can implement corresponding processing functions.

[0281] Optionally, the communication device 1400 further includes a storage module 1430, which can be used to store instructions and / or data; the processing module 1420 can read the instructions and / or data in the storage module 1430 so that the communication device 1400 can implement the aforementioned method embodiment.

[0282] In one possible design 140, the communication device 1400 may correspond to the reader 120 in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the reader 120. The communication device 1400 may be used to perform the steps or processes performed by the reader 120 in any of the above method embodiments.

[0283] For example, the processing module 1420 is used to execute a first D2R message sent by the reader 120 to at least one IoT device 130 on the first access resource for monitoring the signal strength on the first access resource; each IoT device 130 supports the communication method of DOA service.

[0284] The communication module 1410 is configured to execute the following: the reader 120 sends a first synchronization message indicating a first access resource; for any one of at least one IoT device 130, the module sends a paging message to the IoT device 130 to configure a random access resource for the IoT device 130; wherein the random access resource configured for the IoT device 130 is determined based on the number of at least one IoT device 130; the number of at least one IoT device 130 is determined based on the signal strength of the first D2R message sent by at least one IoT device 130 on the first access resource; and a communication method for receiving a random access request sent by the IoT device 130 on the random access resource.

[0285] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0286] In one possible design 140, the communication device 1400 may correspond to the IoT device 130 in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the IoT device 130. The communication device 1400 may be used to perform the steps or processes performed by the IoT device 130 in any of the above method embodiments.

[0287] For example, the communication module 1410 is configured to perform the following communication methods: receiving a first synchronization message from the reader 120 indicating a first access resource for any one of at least one IoT device 130 supporting DOA services; sending a first D2R message to the reader 120 on the first access resource for the reader 120 to monitor the signal strength on the first access resource; receiving a paging message from the reader 120 for configuring a random access resource for the IoT device 130; wherein the random access resource configured for the IoT device 130 is determined by the reader 120 based on the number of at least one IoT device 130; the number of at least one IoT device 130 is determined by the reader 120 based on the signal strength of the first D2R message sent by at least one IoT device 130 on the first access resource; and sending a random access request to the reader 120 on the random access resource.

[0288] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0289] Appendix Figure 15 This is another schematic block diagram of the communication device 1500 provided in the embodiments of this application. The communication device 1500 may be a chip, chip system, or processor, etc., used by the Internet of Things device 130 or the reader / writer 120 to implement the above methods. The communication device 1500 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.

[0290] As attached Figure 15 As shown, the communication device 1500 may include one or more processors 1510, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 1510 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 1500 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

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

[0292] In another alternative design, the communication device 1500 may include a communication interface 1530 for implementing receiving and transmitting functions. For example, the communication interface 1530 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.

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

[0294] 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.

[0295] In one implementation, the communication device 1500 may correspond to the reader 120 in the above method embodiments, and may be used to execute the various steps and / or processes executed by the reader 120 in the above method embodiments. The processor 1510 may be used to execute instructions stored in the memory 1520, and when the processor 1510 executes the instructions stored in the memory, the processor 1510 is used to execute the various steps and / or processes of the above method embodiments corresponding to the reader 120.

[0296] In another implementation, the communication device 1500 may correspond to the IoT device 130 in the above method embodiments, and may be used to execute the various steps and / or processes performed by the IoT device 130 in the above method embodiments. The processor 1510 may be used to execute instructions stored in the memory 1520, and when the processor 1510 executes the instructions stored in the memory, the processor 1510 is used to execute the various steps and / or processes of the above method embodiments corresponding to the IoT device 130.

[0297] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device 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.

[0298] 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.

[0299] 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.

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

[0301] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal device.

[0302] 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 executed by the network device or terminal device in any of the foregoing method embodiments.

[0303] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0304] 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.

[0305] 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.

[0306] 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. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0307] 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.

[0308] 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.

[0309] 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 reader / writer; the method includes: Send a first synchronization message; the first synchronization message is used to indicate the first access resource; Monitor at least one IoT device sending a first D2R message on the first access resource; each IoT device supports Device Initiated Automation (DOA) services. In response to detecting a first D2R message sent by the at least one IoT device, a second synchronization message is sent; the second synchronization message is used for time synchronization between the at least one IoT device and the reader / writer, and for locating the paging message corresponding to the at least one IoT device; For any one of the at least one IoT devices, a paging message is sent to the at least one IoT device; the paging message is used to configure random access resources for the IoT device; wherein, the random access resources configured for the IoT device are determined based on the number of the at least one IoT devices; the number of the at least one IoT devices is determined based on the signal strength of the first D2R message sent by the at least one IoT device on the first access resource; Receive the random access request sent by the IoT device on the random access resource.

2. The communication method according to claim 1, characterized in that, Sending the first synchronization message includes: The first synchronization message is sent periodically.

3. The communication method according to claim 2, characterized in that, The first synchronization message corresponds to a first time length; the random access resources configured for the IoT device are obtained by allocating the random access resources corresponding to the first time length based on the number of the at least one IoT device.

4. The communication method according to claim 3, characterized in that, The second synchronization message is sent by the reader within the first time period.

5. The communication method according to claim 4, characterized in that, The number of the second synchronization messages is greater than or equal to the first quantity threshold.

6. The communication method according to any one of claims 1-5, characterized in that, The interval between the start time of the second synchronization message and the end time of the first synchronization message is less than or equal to a preset number of time units.

7. A communication method, characterized in that, The method is applied to an Internet of Things (IoT) device that supports Device-Initiated Automation (DOA) services, wherein the IoT device is any one of at least one IoT device; the method includes: Receive a first synchronization message sent by the reader / writer; the first synchronization message is used to indicate a first access resource; On the first access resource, a first D2R message is sent to the reader / writer; The reader receives a second synchronization message sent by the reader; the second synchronization message is sent by the reader in response to detecting the first D2R message sent by the at least one IoT device; the second synchronization message is used for time synchronization between the IoT device and the reader, as well as for location paging messages; The reader receives the paging message sent by the reader; the paging message is used to configure random access resources for the IoT device; wherein, the random access resources configured for the IoT device are determined by the reader based on the number of the at least one IoT device; the number of the at least one IoT device is determined by the reader based on the signal strength of the first D2R message sent by the at least one IoT device on the first access resource; On the random access resource, a random access request is sent to the reader / writer.

8. The communication method according to claim 7, characterized in that, The receiving of the first synchronization message sent by the reader includes: Receive the first synchronization message periodically sent by the reader / writer.

9. The communication method according to claim 8, characterized in that, The first synchronization message corresponds to a first time length; the random access resources configured for the IoT device are obtained by the reader / writer allocating the random access resources corresponding to the first time length based on the number of the at least one IoT device.

10. The communication method according to claim 9, characterized in that, The second synchronization message is sent by the reader within the first time period.

11. The communication method according to claim 10, characterized in that, The number of the second synchronization messages is greater than or equal to the first quantity threshold.

12. The communication method according to any one of claims 7-11, characterized in that, The interval between the start time of the second synchronization message and the end time of the first synchronization message is less than or equal to a preset number of time units.

13. A communication device, characterized in that, The device includes at least one processor coupled to a memory storing a program or instructions, wherein the processor executes the program or instructions to cause the device to perform the communication method as described in any one of claims 1-6, or to perform the communication method as described in any one of claims 7-12.

14. A computer program product, characterized in that, include: A computer program, when the computer program is run, causes the computer to perform the communication method as described in any one of claims 1-6, or to perform the communication method as described in any one of claims 7-12.

15. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, the computer performs the communication method as described in any one of claims 1-6, or performs the communication method as described in any one of claims 7-12.

16. A communication system, characterized in that, Includes the communication device as described in claim 13.

17. A chip system, characterized in that, The chip system includes one or more processors, which are configured to retrieve and execute instructions stored in memory, enabling the communication method as described in any one of claims 1-6, or the communication method as described in any one of claims 7-12.

Images