Monitoring method and apparatus, and internet-of-things device

Abstract

The present application belongs to the technical field of communications. Disclosed are a monitoring method and apparatus, and an Internet-of-Things device. The monitoring method in the embodiments of the present application comprises: a first Internet-of-Things device determining a time window, wherein the time window is a window used for monitoring R2D transmission; and the first Internet-of-Things device monitoring R2D transmission in the time window.

Description

Monitoring method, apparatus and internet of things device

[0001] Cross-reference to Related Applications

[0002] The present application claims priority to Chinese Patent Application No. 202410967713.9, filed on July 18, 2024, the contents of which are incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application belongs to the field of communication technology, and particularly relates to a monitoring method, an apparatus and an internet of things device. BACKGROUND

[0004] With the development of communication technology, the internet of things application is more and more widely used, and two kinds of transmissions are mainly defined in the internet of things communication, one is reader-to-device (R2D) transmission, and the other is device-to-reader (D2R) transmission. In some related technologies, the internet of things device often continuously monitors the R2D transmission, which results in high power consumption of the internet of things device. SUMMARY

[0005] Embodiments of the present application provide a monitoring method, an apparatus and an internet of things device, which can solve the problem of high power consumption of the internet of things device.

[0006] In a first aspect, a monitoring method is provided, comprising:

[0007] A first internet of things device determines a time window, the time window being a window for monitoring R2D transmission;

[0008] The first internet of things device monitors R2D transmission in the time window.

[0009] In a second aspect, a monitoring apparatus is provided, comprising:

[0010] A processing module is configured to determine a time window, the time window being a window for monitoring reader-to-device (R2D) transmission;

[0011] A receiving module is configured to monitor R2D transmission in the time window.

[0012] In a third aspect, a monitoring apparatus is provided, which is configured to perform the steps of the monitoring method provided by the embodiments of the present application.

[0013] In a fourth aspect, a device is provided, which comprises a processor and a memory, the memory storing programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement the steps of the monitoring method provided by the embodiments of the present application.

[0014] In a fifth aspect, a device is provided, including a processor and a communication interface, wherein the processor is configured to determine a time window, the time window being a window for monitoring a reader-to-thing device (R2D) transmission; and the communication interface is configured to monitor the R2D transmission in the time window.

[0015] In a sixth aspect, a readable storage medium is provided, the readable storage medium storing a program or instructions, the program or instructions being executed by a processor to implement the steps of the monitoring method provided in the embodiments of the present application.

[0016] In a seventh aspect, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, and the processor being configured to execute a program or instructions to implement the monitoring method provided in the embodiments of the present application.

[0017] In an eighth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, and the computer program / program product being executed by at least one processor to implement the steps of the monitoring method provided in the embodiments of the present application.

[0018] In the embodiments of the present application, a first thing device determines a time window, the time window being a window for monitoring a R2D transmission; and the first thing device monitors the R2D transmission in the time window. In this way, since the R2D transmission is monitored in the time window, the thing device can avoid continuous monitoring, thereby saving the power consumption of the thing device. BRIEF DESCRIPTION OF DRAWINGS

[0019] FIG. 1 is a schematic diagram of a system provided in the embodiments of the present application;

[0020] FIG. 2a and FIG. 2b are schematic diagrams of application scenarios provided in the embodiments of the present application;

[0021] FIG. 3 is a schematic diagram of a transmission provided in the embodiments of the present application;

[0022] FIG. 4 is a flowchart of a monitoring method provided in the embodiments of the present application;

[0023] FIG. 5 is a schematic diagram of signaling interaction provided in the embodiments of the present application;

[0024] FIG. 6 to FIG. 18 are schematic diagrams of transmission timing provided in the embodiments of the present application;

[0025] FIG. 19 is a structural diagram of a monitoring apparatus provided in the embodiments of the present application;

[0026] FIG. 20 is a structural diagram of a communication device provided in the embodiments of the present application;

[0027] FIG. 21 is a structural diagram of a terminal according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all the other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0029] The terms "first", "second", and the like in the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second" are generally a category and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in the present application means at least one of the connected objects. For example, the protection scope of "A or B" at least covers three schemes, namely, scheme one: including A and not including B; scheme two: including B and not including A; scheme three: including A and including B. In addition, the terms "A and / or B", "at least one of A and B", "at least one of A or B" also at least cover the above three schemes, respectively. The character " / " generally represents that the objects before and after are in an "or" relationship.

[0030] The term "indication" in the present application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). Among them, the direct indication can be understood as that the sender explicitly informs the receiver of the specific information, the operation to be performed or the request result, etc. in the indication sent by the sender; the indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or judges and determines the operation to be performed or the request result, etc. according to the judgment result.

[0031] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems. th

[0032] ​FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a terminal-side device such as a mobile phone, a Tablet Personal Computer, a Laptop Computer, a notebook computer, a Personal Digital Assistant (PDA), a palmtop computer, a netbook, an Ultra-mobile Personal Computer (UMPC), a Mobile Internet Device (MID), an Augmented Reality (AR) device, a Virtual Reality (VR) device, a robot, a wearable device, a flight vehicle, a Vehicle User Equipment (VUE), a shipboard device, a Pedestrian User Equipment (PUE), a smart home (a home device with a wireless communication function such as a refrigerator, a television, a washing machine, or furniture, etc.), a game console, a Personal Computer (PC), a kiosk, a self-service machine, an Internet of Things (IoT) device, an Ambient IoT (A-IoT) device, or the like. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, etc.), a smart wristband, smart clothing, or the like. The vehicle-mounted device can also be referred to as a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device or a core network device. The access network device can also be referred to as a Radio Access Network (RAN) device, a radio access network function, a radio access network unit, or a satellite. The access network device can include a base station, a Wireless Local Area Network (WLAN) Access Point (AP), or a Wireless Fidelity (WiFi) node, etc.The base station can be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a relay station (RBS), a serving base station (SBS), a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home Node B (HNB), a home evolved Node B, a transmit / receive point (TRP), or some other suitable terminology in the art, and is not limited to a particular technical terminology, provided that the same technical effect is achieved. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0033] The core network device can also be referred to as a core network node, a core network function, or a core network network element, etc., which includes but is not limited to at least one of the following: a mobility management entity (MME), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a policy and charging rules function (PCRF), an edge application server discovery function (EASDF), a unified data management (UDM), a unified data repository (UDR), a home subscriber server (HSS), a centralized network configuration (CNC), a network repository function (NRF), a network exposure function (NEF), a local NEF (L-NEF), a binding support function (BSF), an application function (AF), a location management function (LMF), a gateway mobile location center (GMLC), a network data analytics function (NWDAF), etc. It should be noted that only the core network device in the NR system is taken as an example for introduction in the embodiments of the present application, and the specific type of the core network device is not limited. If the name of the core network device mentioned in the embodiments of the present application changes in the subsequent protocol version (for example, 6G), it is also within the protection scope of the present application.

[0034] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0035] A-IoT, also known as Ambient Powered Internet of Things (A-IoT), is a type of IoT service where IoT devices are powered through energy harvesting. These devices either do not have batteries or have limited energy storage capacity (e.g., using a capacitor). Energy sources for harvesting include radio waves, light, motion, heat, or other suitable energy sources.

[0036] Low-power IoT devices are a type of IoT device characterized by low overall power consumption, including low-power signal reception and low-power signal transmission. Due to their low overall power consumption, the energy for communication can be derived from the environment, such as wind power, kinetic energy, heat energy, or radio frequency (RF) signals. They can also be referred to as A-IoT, passive IoT devices, or response devices.

[0037] IoT devices can transmit signals using backscattered radio frequency (RF) signals; these devices are also called electronic tags or radio frequency identification (RFID) tags. Some active tags have the ability to generate signals actively, but in order to achieve low power consumption, they are generally below 0dBm, for example, less than or equal to -10dBm.

[0038] In some embodiments, A-IoT devices can be classified based on factors such as energy source, energy storage capability, and whether they are passive or active transmitters, and can be categorized into the following device types:

[0039] Device Type A: This is a passive device, which has no energy storage and no independent signal generation / amplification, i.e., backscatter transmission;

[0040] Equipment Type B: Semi-passive Device, also belonging to the broader category of Passive Devices. It features energy storage but lacks independent signal generation, relying on backscatter transmission. The use of the stored energy can include amplifying the reflected signal.

[0041] Device type C: Active Device, which has energy storage and independent signal generation, i.e., an active radio frequency component used for transmission.

[0042] Devices with different energy storage capacities also affect their transmission quality. Generally, devices with higher energy storage capacity also mean higher receiving sensitivity or higher transmitting power, and the reliability of the receiving or transmitting link can be better guaranteed.

[0043] In some embodiments, an A-IoT device may be a tag or other low-power IoT device.

[0044] In some embodiments, a non-tag terminal or network-side device can act as a tag reader, which can be an RFID tag.

[0045] In some embodiments, the data (or services) types of A-IoT devices include: Device-originated (DO) data and Device-terminated (DT) data.

[0046] DO data and DT data indicate that the data stream originates from or is transmitted to an A-IoT device (similar to an RFID tag). DO data, which originates from an A-IoT device, can be further categorized as follows:

[0047] Devices autonomously initiate data transmission (DO-A), for example, by connecting a large number of various sensors that collect and proactively report information about the environment, equipment, and organisms when necessary.

[0048] Device-terminated data transmission (DO-DTT) is a data transfer service initiated by a device (DT) that terminates at the tag. This DT triggers the tag to initiate a DO service. Examples include asset identification, status reporting, and tracking, all of which involve downlink-triggered reporting. The reader collects data from the tag by triggering an inventory process. Since the data is generated / initiated within the A-IoT device, this service should be considered as a DO service initiated by the tag based on a command sent by the reader.

[0049] In some implementations, the topology of A-IoT can include two types, as shown in Figure 2a and Figure 2b. In the topology shown in Figure 2a, the base station (BS) communicates with the A-IoT device, that is, the BS is the reader. In the topology shown in Figure 2b, there is an intermediate node between the BS and the A-IoT device. The intermediate node can act as the reader of the A-IoT device, such as a terminal acting as the reader of the A-IoT device.

[0050] In some implementations, R2D transmission can be understood as transmission from a reader to an A-IoT device / tag; D2R transmission can be understood as transmission from an AIoT device / tag to a reader.

[0051] The time relationship between R2D and D2R transmissions can include:

[0052] T R2D_min , refers to the minimum time between an R2D transmission and the subsequent corresponding D2R transmission;

[0053] T D2R_min , refers to the minimum time interval between a D2R transmission and the subsequent corresponding R2D transmission;

[0054] T R2D_R2D_min It refers to the minimum time interval between two consecutive R2D transmissions with the same AIoT device;

[0055] T D2R_D2R_min It refers to the minimum time interval between two consecutive D2R transmissions from the same AIoT device.

[0056] In some implementations, different IoT devices transmit D2R using at least one of Time Division Multiplexing (TDM) and Frequency Division Multiplexing (FDM). As shown in Figure 3, a Reader can schedule multiple IoT devices to perform D2R transmissions through a single R2D transmission. After the Reader sends R2D signaling, multiple tags perform D2R transmissions at different times using different resources via TDM or FDM.

[0057] In some implementations, the aforementioned IoT devices can be referred to as response devices, which can be tags, such as electronic tags (i.e., RFID tags). The RFID technology used in IoT devices can be further divided into active, passive, and semi-active types. Passive tags can also be called passive IoT devices. The communication method of IoT devices can be backscattered radio frequency (RF) signals for signal transmission, or some active tags have the ability to actively generate signals. Because IoT devices can originate from the environment, such as environmental RF energy, heat energy, wind energy, kinetic energy, etc., they can also be called A-IoT. Therefore, IoT devices are also understood as a type of terminal and are called terminal devices.

[0058] In some implementations, the reader can be a handheld or fixed device for reading (and sometimes writing) tag information, or it can be understood as a device that communicates with the tag. For example, it can be a terminal, a network-side device, or a device with read and write functions, such as a reader / writer. The specific function is not limited here. The read / write device can send carrier excitation signals or control commands.

[0059] The monitoring method, apparatus, and IoT device provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0060] Please refer to Figure 4, which is a flowchart of a monitoring method provided in an embodiment of this application. As shown in Figure 4, it includes the following steps:

[0061] Step 401: The first IoT device determines a time window, which is a window used to monitor R2D transmission.

[0062] The aforementioned first IoT device can be an A-IoT device or other IoT devices, without limitation.

[0063] The reader (also called a read / write device) in this application embodiment can be a network-side device or a terminal.

[0064] The time window determined by the first IoT device can be a time window determined based on the resources of the D2R transmission sent by the first IoT device before the R2D transmission, or a time window determined based on the resources of the D2R transmission sent by other IoT devices before the R2D transmission, etc. See the following implementation method for details.

[0065] In this embodiment of the application, R2D transmission can also be referred to as R2D message or R2D signaling, and D2R transmission can also be referred to as D2R message or D2R signaling.

[0066] In some implementations, the R2D transmission described above may be a paging message, A-IoT message 2 (A-IoT Msg2), A-IoT message 4 (A-IoT Msg4) during a random access process, or a feedback R2D transmission to a D2R transmission sent by an IoT device.

[0067] The length of the aforementioned time window can be agreed upon in the protocol or determined by the aforementioned first IoT device.

[0068] Step 402: The first IoT device monitors R2D transmission within the time window.

[0069] The first IoT device monitoring R2D transmission within the time window can be understood as the first IoT device only needing to monitor R2D transmission within that time window.

[0070] In this embodiment, by monitoring R2D transmission within a time window, continuous monitoring by IoT devices can be avoided, thereby saving power consumption of IoT devices.

[0071] The scenarios applied in the embodiments of this application may include, but are not limited to, at least one of the following:

[0072] Scenario 1: The reader sends a paging message to the IoT device, and the IoT device sends A-IoT message 1 (A-IoT Msg1) to the reader, which is a D2R transmission. The R2D transmission mentioned above is A-IoT message 2 (A-IoT Msg2), which is the R2D transmission / response corresponding to A-IoT Msg1. The paging message can schedule or trigger multiple TDM (or TDMed) or FDM (or FDMed) or TDM+FDM (TDMed+FDMed) D2R transmissions. The monitored R2D transmission can be a response to these multiple D2R transmissions.

[0073] In this embodiment of the application, A-IoT Msg1 can also be abbreviated as Msg1, A-IoT Msg2 can also be abbreviated as Msg2, A-IoT Msg3 can also be abbreviated as Msg3, and A-IoT Msg4 can also be abbreviated as Msg4.

[0074] Scenario 2: During the inventory process, multiple IoT devices send Msg3 to the reader via TDM, FDM, or TDM+FDM. Different IoT devices determine a time window to monitor the Msg4 sent by the reader, i.e., monitor the R2D transmission mentioned above.

[0075] Scenario 3: The reader schedules multiple IoT devices through the select command. After each IoT device sends a D2R transmission to the reader, a time window is determined to monitor the R2D transmission fed back by the reader.

[0076] As an optional implementation, the first IoT device determines the time window by including at least one of the following:

[0077] The first IoT device determines the start time of the time window;

[0078] The first IoT device determines the duration of the time window;

[0079] The first IoT device determines the end time of the time window.

[0080] Either the time length or the end time can be chosen, because when the start time is determined, the time length determines the end time, or vice versa.

[0081] It should be noted that the above at least one can be understood as meaning that only the above at least one can be executed in step 401. For example: if only the start time of the time window is determined, the length of the time window can be agreed upon by the protocol or pre-configured; if only the duration of the time window is determined, the start time of the time window can be agreed upon by the protocol or pre-configured, or the start time can be determined based on the mapping relationship between the duration and the start time; if only the end time of the time window is determined, the start time or duration of the time window can be agreed upon by the protocol or pre-configured.

[0082] Optionally, the first IoT device determines the start time of the time window by including:

[0083] The first IoT device determines the start time of the time window based on first information, which includes at least one of the following:

[0084] Resource information from multiple D2R transmissions;

[0085] The resource information of the first D2R transmission of the first IoT device, wherein the first D2R transmission is the D2R transmission sent by the first IoT device before the time window;

[0086] The time interval between D2R transmission and R2D transmission, wherein the time interval between D2R transmission and R2D transmission represents the time interval between the first IoT device sending a D2R transmission and the reader responding by sending an R2D transmission;

[0087] A first time interval is used to ensure that the start time of the time window is after the time resources of multiple D2R transmissions;

[0088] The second time interval is a time interval related to the time deviation;

[0089] The duration of the time window for other IoT devices;

[0090] The end time of the time window for other IoT devices;

[0091] The multiple D2R transmissions are scheduled or triggered by the same R2D transmission.

[0092] The aforementioned multiple D2R transmissions are multiple D2R transmissions scheduled or triggered by the same R2D transmission, such as multiple Msg1s scheduled or triggered by the same paging message. These multiple D2R transmissions can be D2R transmissions sent by different IoT devices. Furthermore, the aforementioned multiple D2Rs are D2R transmissions sent by the same or different IoT devices before the reader sends the aforementioned R2D transmission, such as A-IoT Msg1s sent by multiple IoT devices.

[0093] The aforementioned multiple D2R transmissions can be D2R transmissions performed using TDM, FDM, or TDM+FDM methods.

[0094] The resource information of the aforementioned multiple D2R transmissions can be the resource information indicated in the R2D transmission that schedules or triggers these multiple D2R transmissions, such as the resource information of multiple D2R transmissions indicated by a paging message, or the resource information of multiple D2R transmissions derived based on preset rules.

[0095] The resource information of the aforementioned multiple D2R transmissions can be the last time represented by that resource information.

[0096] In some implementations, the resource information transmitted by the plurality of D2R transmissions includes at least one of the following:

[0097] The end time of the last time resource among multiple D2R transmissions, wherein the multiple D2R transmissions are TDM or FDM;

[0098] Resource configuration information for the multiple D2R transmissions.

[0099] The end time of the aforementioned last time resource can be the end time of the time resource of the last D2R transmission among the aforementioned multiple D2R transmissions, such as using the time adjacent to the end time as the aforementioned start time, or using the time at a specific interval from the end time interval as the aforementioned start time.

[0100] In this way, the end time of the last time resource among the multiple D2R transmission time resources mentioned above can avoid the time window determined by the first IoT device from conflicting with the D2R transmission time resources, thereby improving the reliability of R2D transmission.

[0101] The resource configuration information for the aforementioned multiple D2R transmissions may include at least one of the following:

[0102] The multiple D2Rs transmit TDM resource information;

[0103] The multiple D2Rs transmit FDM resource information.

[0104] For example, resource configuration information for Msg1 transmission corresponding to the same paging message includes TDM resource information and / or FDM resource information. The aforementioned start time can be determined based on the mapping relationship between resource configuration information and start time.

[0105] In this way, the start time of the time window can be determined based on the resource configuration information transmitted by multiple D2Rs, making the determination of the start time more flexible and improving the flexibility of R2D monitoring.

[0106] The first D2R transmission mentioned above can be one or more D2R transmissions sent by the first IoT device before the time window, and the multiple D2R transmissions described above include the first D2R transmission.

[0107] The resource information transmitted in the first D2R transmission of the aforementioned first IoT device may include at least one of the following:

[0108] The end time of the time resource for the first D2R transmission of the first IoT device;

[0109] The location information of the time resource of the first D2R transmission of the first IoT device in the time resources of the plurality of D2R transmissions.

[0110] For example, it could be the end time of the time resources used by the first IoT device to perform the first D2R transmission (Msg1), such as using the time adjacent to the end time as the start time, or using the time at a specific interval from the end time interval as the start time.

[0111] By controlling the end time of the first D2R transmission by the first IoT device, the first IoT device can quickly monitor the R2D transmission after the first D2R transmission ends, thereby improving monitoring efficiency.

[0112] Alternatively, based on the aforementioned location information, the interval between the aforementioned start time and the end time of the last time resource of the aforementioned multiple D2R transmission time resources can be determined to enable the time windows of multiple IoT devices to be sorted by location, thereby improving the reliability of multiple IoT devices monitoring R2D transmission.

[0113] The time interval between the aforementioned D2R and R2D transmissions can be understood as the minimum time interval required for the reader to respond to a D2R transmission from the first IoT device and send its own R2D transmission. This ensures that the time interval includes the processing time of both the first IoT device and the reader. For example, the time interval between the aforementioned D2R and R2D transmissions is the minimum time interval T between D2R and R2D transmissions. D2R_min This refers to the minimum time interval between a D2R transmission and the subsequent corresponding R2D transmission, or, the time interval between the aforementioned D2R transmission and R2D transmission is the minimum time interval T between the aforementioned D2R transmission and R2D transmission. D2R_max This refers to the maximum time interval between a D2R transmission and the subsequent corresponding R2D transmission.

[0114] The time interval between the D2R and R2D transmissions mentioned above can ensure that the determined start time is more reliable, such as avoiding monitoring R2D transmissions during the processing time of the first IoT device and the reader.

[0115] The first time interval mentioned above can be expressed as T. gap1 The first time interval T can be determined by reader indication or predefined. gap1 The size needs to meet the requirement that the start time of the time window for IoT device R2D transmission monitoring is after the TDM D2R transmission resource time.

[0116] In this way, the first time interval mentioned above can ensure that the determined start time is located after the time resources of multiple D2R transmissions, so as to avoid conflicts between monitoring R2D transmissions and D2R transmissions and improve the reliability of monitoring R2D transmissions.

[0117] The aforementioned second time interval can be expressed as T. gap2 The aforementioned time interval related to time deviation can be understood as the second time interval being used to eliminate or overcome the time deviation of the theoretically or nominally determined start time. In this way, the second time interval can eliminate or overcome the problem that the start time determined by IoT devices due to capability limitations is not accurate enough, thereby improving the accuracy of the time window.

[0118] In some implementations, the second time interval is determined based on at least one of the following:

[0119] Sampling Frequency Offset (SFO), time drift, frequency tolerance (FrT), and backscatter link frequency (BLF).

[0120] This allows for the determination of the second time interval based on at least one of the aforementioned dimensions, thereby overcoming or eliminating the problem of insufficient accuracy of the start time caused by at least one of the aforementioned dimensions, and improving the accuracy of the time window.

[0121] The aforementioned other IoT devices may be IoT devices other than the first IoT device mentioned above, such as those whose D2R transmissions with the first IoT device are scheduled or triggered by the same R2D transmission.

[0122] By using the aforementioned time window length or end time, conflicts in start times determined by different IoT devices can be avoided, thereby improving the reliability of R2D monitoring.

[0123] In some implementations, the first information may also include the length or end time of the time window determined by the first IoT device.

[0124] It should be noted that the above implementation can determine the start time based on any one or more of the above-mentioned methods. Furthermore, the first information can be sent by the first IoT device to the reader, or it can be obtained by the first IoT device based on received R2D transmissions, such as determining the resource information in the first information based on received paging messages, or the time length and end time of other IoT device time windows.

[0125] Optionally, the start time of the time window satisfies at least one of the following:

[0126] The start time of the time window is after the end time of the time resources of multiple D2R transmissions, which are scheduled or triggered by the same R2D transmission.

[0127] The start time of the time window is after the end time of the time resource for the first D2R transmission of the first IoT device;

[0128] The start time of the time window is the same as the start time of the time window of the second IoT device, and the first D2R of the first IoT device and the second IoT device is scheduled or triggered by the same R2D transmission.

[0129] The start time of the time window is the end time of the time window of the third IoT device, and the first D2R of the first IoT device and the third IoT device is scheduled or triggered by the same R2D transmission.

[0130] The start time of the time window is after the end time of the time window of the fourth IoT device, and the first D2R of the first IoT device and the fourth IoT device are scheduled or triggered by the same R2D transmission.

[0131] By setting the start time of the aforementioned time window after the end time of multiple D2R transmission time resources, conflicts between the time of the first IoT device monitoring R2D transmission and the time resources of D2R transmission can be avoided, thereby improving the reliability of monitoring R2D transmission.

[0132] By starting the aforementioned time window after the end time of the time resource for the first D2R transmission of the first IoT device, the first IoT device can promptly monitor the R2D transmission after the first D2R transmission ends, thereby improving monitoring efficiency.

[0133] The aforementioned second, third, and fourth IoT devices are IoT devices corresponding to multiple first D2R transmissions scheduled or triggered by the same R2D transmission. That is, the first D2R transmissions of these IoT devices are scheduled or triggered by the same R2D transmission, just as multiple IoT devices corresponding to multiple Msg1s triggered or scheduled by the same paging message.

[0134] By aligning the start time of the aforementioned time window with the start time of the second IoT device's time window, the start times of multiple IoT devices can be made identical, thereby improving the monitoring efficiency of multiple IoT devices.

[0135] By setting the start time of the aforementioned time window as the end time of the third IoT device's time window, the time windows of multiple IoT devices can be made continuous. This avoids time window conflicts among multiple IoT devices and improves the monitoring efficiency of multiple IoT devices.

[0136] By setting the start time of the aforementioned time window to the end time of the fourth IoT device's time window, the time windows of the two IoT devices can be spaced out, reducing interference.

[0137] The following example illustrates how to determine the start time of a time window, using the first D2R transmission as Msg1, the aforementioned R2D transmission as Msg2, and the first IoT device as Tag:

[0138] Tag determines the time window T D2R_window The monitoring of Msg2 begins at the starting time, and the corresponding signaling flow is shown in Figure 5, which includes the following steps:

[0139] Step 1. The reader sends a paging message to the tag;

[0140] Step 2. The tag sends Msg1 to the reader;

[0141] Step 3. Tag Determine Time T D2R_window The start time and duration, and the time window T. D2R_window Internal monitoring of Msg2;

[0142] Step 4. The reader sends Msg2 to the tag.

[0143] When accessing via Time Division Multiple Access (TDMA), the Reader first sends a Paging message. After at least one Tag receives the Paging message, it can send Msg1 to the Reader via TDMA. For example, as shown in Figure 6, Tag#1 / 2 / 3 use time-division multiplexed resources#1 / 2 / 3 respectively to send Msg1.

[0144] In addition, different tags can also send Msg1 to the Reader via TDMA + Frequency Division Multiple Access (FDMA), as shown in Figure 7.

[0145] For the above scenarios where different tags transmit Msg1 via TDMA or TDMA+FDMA, after the tag has sent Msg1, a time window needs to be determined for monitoring Msg2. The start time of the time window can be determined as follows:

[0146] Method 1: Use different tags from different Msg1 resources (including different TDMs or FDMs) to monitor Msg2 with the same start time. The start time of the time window is located after the end time of the last resource in the TDM Msg1 resource corresponding to the same paging message scheduling / triggering. D2R_min T D2R_min T is the minimum time interval between D2R and R2D transmissions. D2R_min This can be understood as the time interval between the end time of the last resource in the TDM Msg1 resource and the R2D transmission.

[0147] For example, as shown in Figure 8, suppose the TDM Msg1 resource indicated in the Paging message includes {resource#1, resource#2}, where the end time of resource#2 is T. r2_end Assuming that Tag#1 and Tag#2 send Msg1 using resource#1 and resource#2 respectively, then the start time T of the time window for Tag1 and Tag2 to monitor Msg2 is... window_start =T r2_end +T D2R_min That is, all of them are after the end time of resource#2. D2R_min Then we started monitoring Msg2.

[0148] Method 2: Using tags from different TDM Msg1 resources, the start time for Msg2 monitoring is different, and the start time of the time window is located after the end time of the Msg1 resource used by the tag. D2R_min In the case of TDM+FDM, the start time for Msg2 monitoring is the same for tags using the same TDM resources but different FDM resources.

[0149] For example, as shown in Figure 9, assuming the TDM Msg1 resource indicated in the Paging message includes {resource#1, resource#2}, and Tag#1 and Tag#2 send Msg1 using resource#1 and resource#2 respectively, then the start time T of the time window for Tag1 to monitor Msg2 is... window_start =T r1_end +T D2R_min The start time T of the time window for Tag2 to monitor Msg2. window_start =T r2_end +T D2R_min .

[0150] As shown in Figure 10, in the case of TDM+FDM, Tag1 and Tag2 use resource#1 and resource#2 respectively to send Msg1 via FDM. Since resource#1 and resource#2 are different frequency domain resources corresponding to the same time, the start time of the time window for monitoring Msg2 for Tag1 and Tag2 is the same. Tag3 and Tag2 use different time resources to send Msg1, so the start time of the time window for monitoring Msg2 for Tag3 and Tag2 is different.

[0151] Method 3: Using different tags for Msg1 resources in TDM to start monitoring Msg2 at different times. The start time for Msg2 monitoring for the first resource in the TDM Msg1 resource is after the last resource. D2R_min The start time of monitoring Msg2 corresponding to the Nth (N>1)th Msg1 resource is located at the end position of the (N-1)th Msg2 monitoring window corresponding to the (N-1)th Msg1 resource. In the case of TDM+FDM, the start time of monitoring Msg2 using tags of different FDM Msg1 resources at the same time is the same.

[0152] For example, as shown in Figure 11, assuming the TDM Msg1 resource indicated in the Paging message includes {resource#1, resource#2}, and Tag#1 and Tag#2 send Msg1 using resource#1 and resource#2 respectively, then the start time of the time window for Tag#1 to monitor Msg2 is T. r2_end +T D2R_min Assume the time window length for monitoring Msg2 using Tag#1 is T. window1 Therefore, the start time of the time window for monitoring Msg2 using Tag#2 is T. r2_end +T D2R_min +T window1 .

[0153] Another scenario is that at least some different TDM Msg1 resources have different Msg2 monitoring start times, meaning that some different TDM Msg1 resources have the same Msg2 monitoring start time. For example, as shown in Figure 12, {resource#1, resource#2} corresponds to Window#1, and {resource#3, resource#4} corresponds to Window#2. Window#1 and Window#2 have different start times. The correspondence between different Msg1 resources and time window start times can be determined by Reader indication, such as in the Paging message, or by predefined / preconfigured settings.

[0154] The above-mentioned time windows are continuous in time. Another situation is that the time windows for Msg2 monitoring of Tag#1 and Tag#2 are not continuous, that is, the start time of Msg2 monitoring corresponding to the first resource in TDM Msg1 resource is after the end time of the last resource. D2R_min The Msg2 monitoring start time corresponding to the Nth (N>1) resource is located after the end of the Msg2 monitoring window corresponding to the (N-1)th resource, plus a time gap. This time gap value is configurable or determined according to a predefined method. For example, this time gap value is the second time interval T. gap2 Or that time gap is T D2R_min As shown in Figure 13, for Tag#2, the start time of its Msg2 monitoring time window is T. r2_end +T D2R_min +T window1 +T D2R_min .

[0155] In the case of TDM+FDM, the start time of the time window for Msg2 monitoring using tags with different frequencies at the same time is the same, and the determination method is the same as above, so it will not be repeated here.

[0156] Method 4: Different tags start monitoring Msg2 at different times. The start time of the time window is T after the end time of the time resources used by the tag for Msg1 transmission. D2R_min +T gap1 .

[0157] For example, as shown in Figure 14, assuming the time resources indicated in the Paging message for Time Division Multiplexing (TDM) transmission of Msg1 include {resource#1, resource#2}, and Tag#1 and Tag#2 use resource#1 and resource#2 respectively to send Msg1, the first time interval T... gap1 The timeframe can be determined by the Reader in the Paging message, or by a predefined / preconfigured setting, where T... gap1 The size needs to satisfy the condition that the start time of the time window for Tag#1 to monitor Msg2 is after the time resources used for Time Division Multiplexing (TDM) for Msg1 transmission. Therefore, the start time of the time window for Tag#1 to monitor Msg2 is T. r1_end +T D2R_min +T gap1 Therefore, the start time of the time window for Msg2 monitoring for Tag#2 is T. r2_end +T D2R_min +T gap1 For different TDMed Msg1 resources, they can correspond to a common T. gap1 The Reader only needs to indicate or predefine a T gap1 It's understandable that this method is relatively simple and can save potential signaling overhead, but for resources with later times in the TDMed Msg1 resource, the corresponding time window starts later; or for different TDMed Msg1 resources, they can correspond to different T... gap1 The Reader needs to indicate multiple or predefined Ts. gap1 It is understandable that this method may have a large potential signaling overhead, but it can ensure that the start time of the time window corresponding to different TDMed Msg1 resources is not too late.

[0158] The above embodiments represent the theoretical or nominal start time for Tag Msg2 monitoring. However, considering the capabilities of Tag, its timing is not sufficiently accurate. Therefore, the actual start time for Tag Msg2 monitoring can allow for a second time interval T beyond the theoretical / nominal start time. gap2 The time deviation, where T gap2 The size can be determined based on at least one of the following parameters: SFO, time drift, FrT, BLF.

[0159] As an optional implementation, the first IoT device determines the time window, including:

[0160] The first IoT device determines the duration or end time of the time window based on second information, wherein the second information includes at least one of the following:

[0161] Predefined information;

[0162] Reader instructions;

[0163] The time interval between D2R transmission and R2D transmission, wherein the time interval between D2R transmission and R2D transmission represents the time interval between the first IoT device sending a D2R transmission and the reader responding by sending an R2D transmission;

[0164] The resource configuration information of the multiple D2R transmissions, wherein the multiple D2R transmissions are scheduled or triggered by the same R2D transmission;

[0165] Resource information transmitted by the first D2R of the first IoT device;

[0166] The data rate of the first D2R transmission of the first IoT device;

[0167] The device type of the first IoT device;

[0168] Inventory type;

[0169] The second time interval is a time interval related to the time deviation;

[0170] The third time interval is a predefined time interval or a time interval indicated by the reader.

[0171] The aforementioned predefined information can be protocol predefined information or information predefined by IoT devices, such as predefining the length or end time of the aforementioned time window.

[0172] The reader's indication can be understood as the reader directly or indirectly indicating the duration or end time of the time.

[0173] The length or end time of a time window can be easily and directly determined using the predefined information or reader instructions, thereby reducing the complexity of IoT devices.

[0174] The time interval between D2R and R2D transmissions can include the minimum time interval T between D2R and R2D transmissions. D2R_min Or the maximum time interval T D2R_max For details, please refer to the corresponding descriptions of the above embodiments.

[0175] Determining the time length or end time by using the time interval between the aforementioned D2R and R2D transmissions can be based on the mapping relationship between this time interval and the time length or end time.

[0176] Determining the time length or end time based on this time interval allows the reader and the first IoT device sufficient time for other processing, thereby improving their performance.

[0177] The resource configuration information for the aforementioned multiple D2R transmissions can be found in the corresponding descriptions of the above implementation methods, and will not be repeated here.

[0178] Determining the time length or end time through resource configuration information of multiple D2R transmissions can be based on the mapping relationship between the resource configuration and the time length or end time. For example, the first IoT device determines the window length for monitoring R2D transmissions based on which resource in the TDM resource it uses for the first D2R transmission.

[0179] The resource information transmitted in the first D2R transmission of the aforementioned first IoT device may include at least one of the following:

[0180] The end time of the time resource for the first D2R transmission of the first IoT device;

[0181] The location information of the time resources of the first D2R transmission of the first IoT device within the time resources of the plurality of D2R transmissions.

[0182] The aforementioned first IoT device can determine the length or end time of the time window based on the mapping relationship between the end time of the time resource of the first D2R transmission and the length or end time of the time window, or based on the mapping relationship between the aforementioned location information and the length or end time of the time window.

[0183] The aforementioned first IoT device can determine the time length or end time based on the mapping relationship between the data rate and the time length or end time. This allows the time window length or end time to match the data rate, thereby improving the reliability of monitoring R2D transmission.

[0184] The first IoT device can determine the time length or end time based on the mapping relationship between the device type and the time length or end time. This allows the time window length or end time to match the device type, thereby improving the reliability of monitoring R2D transmission.

[0185] The above inventory type can be an access type.

[0186] The first IoT device can determine the time length or end time based on the mapping relationship between the inventory type and the time length or end time. This allows the time window length or end time to match the inventory type, thereby improving the reliability of monitoring R2D transmission.

[0187] The second time interval is described in the corresponding description of the above embodiments, and will not be repeated here.

[0188] The size of the third time interval mentioned above can satisfy the requirement that the end time of the time window for the first IoT device to perform R2D transmission monitoring is after the resource time of TDM D2R transmission.

[0189] The aforementioned first IoT device can determine the time length or end time based on the mapping relationship between the aforementioned second or third time interval and the time length or end time.

[0190] The following example, using Msg1 as the first D2R transmission, Msg2 as the aforementioned R2D transmission, and Tag as the first IoT device, illustrates how to determine the length or end time of the time window:

[0191] This embodiment mainly describes how to determine the length (or end time) of the time window used for Msg2 monitoring, so that the Tag can uniquely determine a time window for Msg2 monitoring. The corresponding signaling flowchart is shown in Figure 5 above. Determining the length (or end time) of the time window used for Msg2 monitoring includes the following methods:

[0192] Method 1: The time window length is determined by the Reader indicator, such as in the Paging message, or by a predefined convention.

[0193] For example, for the time window for receiving Msg2 corresponding to TDMed Msg1 resource, the Reader can uniformly indicate a time window length, that is, different TDMed Msg1 resources correspond to the same time window length, or indicate their respective time window lengths.

[0194] Method 2: The time window length is determined based on the time interval between D2R and R2D transmissions. For example, the minimum time interval between D2R and R2D transmissions is T. D2R_min The maximum time interval is T D2R_max Then the time window length time_length = T D2R_max -T D2R_min ;

[0195] For example, if different TDMed Msg1 resources have the same monitoring Msg2 time window length, this can be determined based on the aforementioned Reader indication, predefined, or the time interval between D2R and R2D transmissions, etc., without restriction. If different TDMed Msg1 resources also have the same start time for their time windows, and the start time is located after the end time of the last resource in the TDMed Msg1 resource corresponding to the same paging message scheduling / triggering, then... D2R_min Therefore, different TDMed Msg1 resources all correspond to the same time window, as shown in Figure 15.

[0196] Method 3: Determined based on the resource configuration used for Msg1 transmission and the resources used by the Tag for Msg1 transmission. For example, the Reader indicates or predefines multiple time window lengths, and the Tag determines which window length it uses to monitor Msg2 based on which resource in the TDMed Msg1 resource it is using.

[0197] One approach is to use tags that transmit Msg1 using different TDM resources, resulting in different time window lengths for monitoring Msg2. For example, as shown in Figure 16, the TDM Msg1 resource includes resource#1 and resource#2, corresponding to time windows Window#1 and Window#2, respectively. Both start times are after the corresponding Msg1 resource time. To ensure that the end of the time window Window#1 corresponding to Msg1 resource#1 is after all TDMed Msg1 resource times, Window#1 has a longer duration. Window#2, on the other hand, starts after all TDMed Msg1 resource times, thus having a relatively shorter duration. The tag determines whether its time window is Window#1 or Window#2 based on whether it uses resource#1 or resource#2.

[0198] Another approach is to ensure that at least some different TDM Msg1 resources correspond to different time window lengths, meaning that some Msg1 resources correspond to the same time window length. For example, as shown in Figure 17, {resource#1, resource#2} corresponds to Window#1, and {resource#3, resource#4} corresponds to Window#2. The time window lengths of Window#1 and Window#2 are different. The correspondence between different Msg1 resources and time window lengths can be determined by Reader indication, such as in the Paging message, or by predefinition / preconfiguration.

[0199] For the TDM+FDM scenario, the length of the time window can be determined based on the number of FDM resources. For example, when the number of FDM Msg1 resources is large, such as 4, the time window length is 20ms. When the number of FDM Msg1 resources is small, such as 2, the time window length is 10ms. The correspondence between the number of FDM resources and the time window length can be determined by the Reader instruction or by predefinition or preconfiguration.

[0200] Method 4: The length of the time window is equal to T D2R_max -T D2R_min+ +T gap3 The third time interval T gap3 It can be determined by Reader instructions or predefined rules, and it needs to meet the requirement that the end time of the time window for Tag to perform Msg2 monitoring is after the time resource of TDM Msg1 resource.

[0201] For example, as shown in Figure 18, the start time of the time window is located after the end time of Msg1 resource#1 used by the Tag. D2R_min The end time is after Msg1 resource#2 time.

[0202] Method 5: The length of the time window can also be determined based on the following method:

[0203] The data rate or backscatter frequency (BLF) used for transmitting Msg1 based on other tags can be considered. For example, a tag needs to ensure that the end time of its time window is after the time when other tags have finished sending Msg1. The transmission duration of Msg1 for other tags depends on the BLF or data rate used. Therefore, when determining its own time window length, a tag needs to consider the data rate or BLF used by other tags that send Msg1 via TDM.

[0204] The time window length is determined based on the data rate or BLF used by the tag itself; for example, different data rates or different BLFs correspond to different time window lengths.

[0205] In the case of TDMA+FDMA, for tags using different FDMed Msg1 resources at the same time, the data rate or BLF may be different. In order to ensure that the time window length corresponding to different FDMed Msg1 resources at the same time is the same, it is necessary to determine the time window length based on a common reference BLF or data rate. For example, the time window length can be determined based on the BLF / data rate used by one of the tags.

[0206] For example, the length of a time window can be determined based on the BLF / data rate used by one of the tags.

[0207] The device type of the tag corresponds to different time window lengths;

[0208] Inventory type (access type), such as contention-based access and non-contention-based access, with different access types corresponding to different time window lengths.

[0209] This embodiment represents the theoretical / nominal end time of the Msg2 monitoring time window. Considering the capabilities of Tags, their timing is not sufficiently accurate. Therefore, the actual end time of Msg2 monitoring by Tags is allowed to differ by a margin of T from the theoretical / nominal end time. gap2 The time deviation, where T gap2 The size can be determined based on at least one of the following parameters: SFO, time drift, FrT, BLF.

[0210] As an optional implementation, the time window has a duration of N time units, where N is a positive integer, and the time units are determined based on at least one of the following:

[0211] The time interval between D2R and R2D transmissions, the absolute time unit, the time unit of R2D transmission, the time unit of D2R transmission, and the symbol time length of Orthogonal Frequency Division Multiplexing (OFDM);

[0212] The time interval between the D2R transmission and the R2D transmission represents the time interval between the first IoT device sending a D2R transmission and the reader responding to the D2R by sending an R2D transmission.

[0213] The time interval between the D2R and R2D transmissions mentioned above can be the minimum time interval between D2R and R2D transmissions.

[0214] The above absolute time unit can be understood as absolute time, such as a time unit length of 10ms or 20ms, etc.

[0215] The aforementioned time unit for R2D transmission can be understood as the time granularity of R2D transmission. For example, the aforementioned time unit for R2D transmission may include at least one of the following:

[0216] The chip length corresponding to the R2D preamble, the chip length corresponding to the Physical Reader to Device Channel (PRDCH), and the time length corresponding to the information bits.

[0217] The time length of any of the above-mentioned chips corresponds to one On-Off Keying (OOK) modulation symbol, and the above-mentioned chips are time units before or after encoding. For example, the time length of a chip after line code encoding, such as 1 bit of information, is 1 bit corresponding to 2 chips after Manchester encoding, and each chip is an encoded chip.

[0218] For example: the time window is N chip time lengths, where N is an integer greater than or equal to 1.

[0219] For example, Paging messages are sent via PRDCH, and the time window length is the chip time length corresponding to X2 (X2≥1) Paging messages.

[0220] The time length corresponding to the aforementioned information bits can refer to the time length corresponding to the encoded information bit. This encoding can include line code, forward error correction (FEC) encoding, square wave, repetition, and other encodings.

[0221] For example, in Manchester encoding at a 1 / 4 code rate, the time length of one information bit is 4 chip lengths. Similarly, in Manchester encoding at a 1 / 2 code rate, the time length of one information bit is 2 chip lengths. In Manchester encoding with two repetitions at a 1 / 2 code rate, the time length of one information bit is 4 chip lengths. For biphase-interval coding (FM0), the length of one codeword is 2 chip lengths. For Miller coding, the length of one codeword is 2 chip lengths. For Miller-2 coding, the time length of one codeword is 4 chip lengths. For Pulse-interval encoding (PIE), bit 0 is encoded as chip {10}, which is 2 chip lengths, and bit 1 is encoded as chip {1110}, which is 4 chip lengths. PIE encoding can be measured in units of the time length of one information bit '0', the time length of one information bit '1', or the sum or average of the time lengths of one information bit '0' and '1'.

[0222] The time unit of the aforementioned D2R transmission can be understood as the time granularity of the D2R transmission. For example, the time unit of the aforementioned D2R transmission may include at least one of the following:

[0223] The chip time length corresponding to the D2R preamble, the chip time length corresponding to the Physical Device to Reader Channel (PDRCH), and the time length corresponding to the information bits.

[0224] The chip length mentioned above can be the line code chip length after encoding. The chip length can be determined based on at least one of the backscatter frequency (BLF), transmission bandwidth, and transmission rate. The chip length is related to the parameters of the line code. Alternatively, the chip length can be the chip length of a square wave of a modulated subcarrier. Or, the chip length can also be the chip length of a square wave.

[0225] In the above embodiments, the length of the time window can be determined based on multiple time units to improve the flexibility of monitoring R2D transmission and make it applicable to more scenarios or services.

[0226] In some implementations, the duration of the time window can be a combination of the above-mentioned multiple factors, such as the maximum value, minimum value, summation, or average of the above-mentioned multiple factors.

[0227] In some implementations, in addition to determining the time window length based on the time granularity of D2R transmission, for different FDMed D2R transmission resources at the same time, it is necessary to ensure that their corresponding time lengths are the same. Therefore, it is necessary to determine the time window length based on a common D2R transmission time granularity, such as based on the chip time length used by one of the IoT devices.

[0228] As an optional implementation, the method further includes:

[0229] Under target conditions, monitoring of R2D transmission is stopped, and the target conditions include at least one of the following:

[0230] R2D transmission is detected, or R2D transmission matching the first IoT device is detected;

[0231] The time window ends;

[0232] R2D transmissions including indication information are detected, the indication information being used to indicate that the R2D transmission is the last R2D transmission in the time window, or the indication information being used to indicate that there are no subsequent R2D transmissions in the time window;

[0233] The battery level of the first IoT device is below a preset threshold.

[0234] The aforementioned monitoring of R2D transmissions can end as soon as a D2R transmission is detected. If the monitored R2D transmission does not contain a device identifier matching the first IoT device (e.g., the device ID of the first IoT device), the first IoT device considers the first D2R transmission (e.g., Msg1) to have failed. For example, after the first IoT device detects Msg2 for the first time within a defined time window, regardless of whether Msg2 contains an identifier matching the Tag's own ID, the Tag will not monitor Msg2 again within that time window. If the reader needs to provide feedback on all received Msg1s in a single Msg2 message, when the Msg2 detected by the Tag does not contain an identifier matching the IoT device's own ID, the IoT device can consider the Msg1 transmission to have failed and can enter a sleep state or resend Msg1 if access is triggered again.

[0235] The aforementioned detected R2D transmission matching the first IoT device can be an R2D transmission that includes a device identifier matching the first IoT device. For example, the IoT device continuously monitors Msg2 within a defined time window until it detects Msg2 and Msg2 contains an identifier matching the IoT device's own ID, and then stops monitoring, or stops monitoring after the time window ends.

[0236] Since the aforementioned indication information indicates that the R2D transmission is the last R2D transmission within the time window or indicates that there are no subsequent R2D transmissions within the time window, the first IoT device can promptly end monitoring to save power consumption. For example, if an IoT device monitors Msg2 within a defined time window and receives Msg2, and Msg2 indicates that it is the last Msg2 within that time window, then the IoT device stops monitoring Msg2 within that time window.

[0237] The aforementioned preset threshold can be determined by reader indication, predefined, or preconfigured. For example, different preset thresholds can be implicitly determined based on the device type of the first IoT device. Furthermore, the preset threshold can be general, i.e., not limited to receiving Msg2, or it can be a power threshold value specifically defined for receiving Msg2, such as 30%, 25%, etc.

[0238] The process ends when the battery level of the first IoT device falls below a preset threshold, allowing the first IoT device to retain sufficient battery power for other tasks.

[0239] For example, if an IoT device monitors Msg2 within a defined time window, and the device's battery level falls below the preset threshold during the monitoring process, then monitoring of Msg2 will cease within that time window.

[0240] In some implementations, the time window includes the start time of the reader sending the R2D transmission, wherein the end time of the reader sending the R2D transmission may or may not be within the time window.

[0241] In this embodiment, a first IoT device determines a time window, which is a window for monitoring R2D transmission; the first IoT device monitors R2D transmission within the time window. By monitoring R2D transmission within the time window, continuous monitoring by the IoT device can be avoided, thus saving power consumption. For example, using the method provided in this embodiment, when the IoT device transmits Msg1 via TDM or TDM+FDM, the time window for monitoring Msg2 can be uniquely determined, which is beneficial to the transmission performance of Msg2.

[0242] This application provides a monitoring device. As an example, the monitoring device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, etc. Exemplarily, the terminal may include, but is not limited to, the types of terminals 11 listed above; this application does not impose specific limitations.

[0243] The monitoring device may include a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor may include a general-purpose processor, a special-purpose processor, such as a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), an Artificial Intelligence (AI) processor, a Graphics Processing Unit (GPU), an Application Specific Integrated Circuit (ASIC), a Network Processor (NP), a Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules may be implemented by a communication interface, which may include one or more of the following: a transceiver, pins, circuits, a bus, and a radio frequency unit.

[0244] Specifically, referring to Figure 19, when the monitoring device is a terminal or a component within a terminal, the monitoring device 1900 includes:

[0245] Processing module 1901 is used to determine a time window, which is a window for monitoring the R2D transmission from the reader to the Internet of Things device;

[0246] The receiving module 1902 is used to monitor R2D transmission within the time window.

[0247] Optionally, the processing module 1901 is used for at least one of the following:

[0248] Determine the start time of the time window;

[0249] Determine the duration of the time window;

[0250] Determine the end time of the time window.

[0251] Optionally, determining the start time of the time window includes:

[0252] The start time of the time window is determined based on first information, wherein the first information includes at least one of the following:

[0253] Resource information transmitted from multiple IoT devices to a reader via D2R;

[0254] Resource information of the first D2R transmission of the first IoT device, wherein the first D2R transmission is the D2R transmission sent by the first IoT device before the time window;

[0255] The time interval between D2R transmission and R2D transmission, wherein the time interval between D2R transmission and R2D transmission represents the time interval between the first IoT device sending a D2R transmission and the reader responding by sending an R2D transmission;

[0256] A first time interval is used to ensure that the start time of the time window is after the time resources of multiple D2R transmissions;

[0257] The second time interval is a time interval related to the time deviation;

[0258] The duration of the time window for other IoT devices;

[0259] The end time of the time window for other IoT devices;

[0260] The multiple D2R transmissions are scheduled or triggered by the same R2D transmission.

[0261] Optionally, the resource information of the plurality of D2R transmissions includes at least one of the following:

[0262] The end time of the last time resource among multiple D2R transmission time resources, wherein the multiple D2R transmissions are time-division multiplexing (TDM) or frequency-division multiplexing (FDM);

[0263] Resource configuration information for the multiple D2R transmissions.

[0264] Optionally, the resource information transmitted by the first D2R of the first IoT device includes at least one of the following:

[0265] The end time of the time resource for the first D2R transmission of the first IoT device;

[0266] The location information of the time resource of the first D2R transmission of the first IoT device in the time resources of the plurality of D2R transmissions.

[0267] Optionally, the start time of the time window satisfies at least one of the following:

[0268] The start time of the time window is after the end time of the time resources of multiple D2R transmissions, which are scheduled or triggered by the same R2D transmission.

[0269] The start time of the time window is after the end time of the time resource for the first D2R transmission of the first IoT device;

[0270] The start time of the time window is the same as the start time of the time window of the second IoT device, and the first D2R of the first IoT device and the second IoT device is scheduled or triggered by the same R2D transmission.

[0271] The start time of the time window is the end time of the time window of the third IoT device, and the first D2R of the first IoT device and the third IoT device is scheduled or triggered by the same R2D transmission.

[0272] The start time of the time window is after the end time of the time window of the fourth IoT device, and the first D2R of the first IoT device and the fourth IoT device are scheduled or triggered by the same R2D transmission.

[0273] Optionally, the processing module 1901 is used to determine the duration or end time of the time window based on second information, wherein the second information includes at least one of the following:

[0274] Predefined information;

[0275] Reader instructions;

[0276] The time interval between D2R transmission and R2D transmission, wherein the time interval between D2R transmission and R2D transmission represents the time interval between the first IoT device sending a D2R transmission and the reader responding by sending an R2D transmission;

[0277] The resource configuration information of the multiple D2R transmissions, wherein the multiple D2R transmissions are scheduled or triggered by the same R2D transmission;

[0278] Resource information transmitted by the first D2R of the first IoT device;

[0279] The data rate of the first D2R transmission of the first IoT device;

[0280] The device type of the first IoT device;

[0281] Inventory type;

[0282] The second time interval is a time interval related to the time deviation;

[0283] The third time interval is a predefined time interval or a time interval indicated by the reader.

[0284] Optionally, the resource configuration information of the plurality of D2R transmissions includes at least one of the following:

[0285] The multiple D2Rs transmit TDM resource information;

[0286] The multiple D2Rs transmit FDM resource information.

[0287] Optionally, the second time interval is determined based on at least one of the following:

[0288] Sampling frequency drift (SFO), time drift, frequency tolerance (FrT), and backscatter frequency (BLF).

[0289] Optionally, the time window has a duration of N time units, where N is a positive integer, and the time units are determined based on at least one of the following:

[0290] The time interval between D2R and R2D transmissions, the absolute time unit, the time unit of R2D transmission, the time unit of D2R transmission, and the symbol time length of Orthogonal Frequency Division Multiplexing (OFDM);

[0291] The time interval between the D2R transmission and the R2D transmission represents the time interval between the first IoT device sending a D2R transmission and the reader responding to the D2R by sending an R2D transmission.

[0292] Optionally, the time unit of the R2D transmission includes at least one of the following:

[0293] The chip time length corresponding to the R2D preamble, the chip time length corresponding to the physical reader to the device channel PRDCH, and the time length corresponding to the information bits.

[0294] Optionally, the time unit of the D2R transmission includes at least one of the following:

[0295] The chip time length corresponding to the D2R preamble, the chip time length corresponding to the PDRCH channel from the IoT device to the reader, and the time length corresponding to the information bits.

[0296] Optionally, the processing module 1901 is further configured to stop monitoring R2D transmission under target conditions, the target conditions including at least one of the following:

[0297] R2D transmission is detected, or R2D transmission matching the first IoT device is detected;

[0298] The time window ends;

[0299] R2D transmissions including indication information are detected, the indication information being used to indicate that the R2D transmission is the last R2D transmission in the time window, or the indication information being used to indicate that there are no subsequent R2D transmissions in the time window;

[0300] The battery level of the first IoT device is below a preset threshold.

[0301] The aforementioned monitoring device can save power consumption of IoT devices.

[0302] The monitoring device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG4 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0303] As shown in Figure 20, this application embodiment also provides a communication device 2000, including a processor 2001 and a memory 2002. The memory 2002 stores a program or instructions that can run on the processor 2001. For example, when the communication device 2000 is the communication device in the embodiment shown in Figure 4, the program or instructions, when executed by the processor 2001, implement the various steps of the above-described monitoring method embodiment and achieve the same technical effect. When the communication device 2000 is an Internet of Things (IoT) device, the program or instructions, when executed by the processor 2001, implement the various steps of the above-described monitoring method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0304] It should be noted that Figure 20 is an example illustrating an IoT device that includes a processor and memory. In this embodiment, the IoT device may be an A-IoT device, such as a tag, which does not include a processor and memory. In this embodiment, the structure of the IoT device is not limited; it can specifically be any of the various device types described above.

[0305] This application also provides a communication device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG4. This communication device embodiment corresponds to the above-described communication device-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this communication device embodiment and achieve the same technical effect. This communication device can be the monitoring device shown in FIG16. Specifically, FIG21 is a schematic diagram of the hardware structure of a communication device implementing an embodiment of this application.

[0306] The communication device 2100 includes, but is not limited to, at least some of the following components: radio frequency unit 2101, network module 2102, audio output unit 2103, input unit 2104, sensor 2105, display unit 2106, user input unit 2107, interface unit 2108, memory 2109, and processor 2110.

[0307] Those skilled in the art will understand that the communication device 2100 may also include a power supply (such as a battery) for powering various components. The power supply may be logically connected to the processor 2110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. The communication device structure shown in Figure 21 does not constitute a limitation on the communication device. The communication device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0308] It should be understood that, in this embodiment, the input unit 2104 may include a graphics processor 21041 and a microphone 21042. The graphics processor 21041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 2106 may include a display panel 21061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 2107 includes at least one of a touch panel 21071 and other input devices 21072. The touch panel 21071 is also called a touch screen. The touch panel 21071 may include a touch detection device and a touch controller. Other input devices 21072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0309] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 2101 can transmit it to the processor 2110 for processing; in addition, the radio frequency unit 2101 can send uplink data to the network-side device. Typically, the radio frequency unit 2101 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0310] The memory 2109 can be used to store software programs or instructions, as well as various data. The memory 2109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 2109 may include volatile memory or non-volatile memory. The non-volatile memory may 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. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 2109 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0311] Processor 2110 may include one or more processing units; optionally, processor 2110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 2110.

[0312] In this embodiment, the structure of the terminal is used as an example to illustrate the Internet of Things (IoT) device. In this embodiment, the specific structure of the IoT device is not limited.

[0313] The processor 2110 is used to determine a time window, which is a window for monitoring the R2D transmission from the reader to the IoT device;

[0314] Radio frequency unit 2101 is used to monitor R2D transmission within the time window.

[0315] Optionally, the determination of the time window includes at least one of the following:

[0316] Determine the start time of the time window;

[0317] Determine the duration of the time window;

[0318] Determine the end time of the time window.

[0319] Optionally, determining the start time of the time window includes:

[0320] The start time of the time window is determined based on first information, wherein the first information includes at least one of the following:

[0321] Resource information transmitted from multiple IoT devices to a reader via D2R;

[0322] The resource information of the first D2R transmission of the first IoT device, wherein the first D2R transmission is the D2R transmission sent by the first IoT device before the time window;

[0323] The time interval between D2R transmission and R2D transmission, wherein the time interval between D2R transmission and R2D transmission represents the time interval between the first IoT device sending a D2R transmission and the reader responding by sending an R2D transmission;

[0324] A first time interval is used to ensure that the start time of the time window is after the time resources of multiple D2R transmissions;

[0325] The second time interval is a time interval related to the time deviation;

[0326] The duration of the time window for other IoT devices;

[0327] The end time of the time window for other IoT devices;

[0328] The multiple D2R transmissions are scheduled or triggered by the same R2D transmission.

[0329] Optionally, the resource information of the plurality of D2R transmissions includes at least one of the following:

[0330] The end time of the last time resource among multiple D2R transmission time resources, wherein the multiple D2R transmissions are time-division multiplexing (TDM) or frequency-division multiplexing (FDM);

[0331] Resource configuration information for the multiple D2R transmissions.

[0332] Optionally, the resource information transmitted by the first D2R of the first IoT device includes at least one of the following:

[0333] The end time of the time resource for the first D2R transmission of the first IoT device;

[0334] The location information of the time resource of the first D2R transmission of the first IoT device in the time resources of the plurality of D2R transmissions.

[0335] Optionally, the start time of the time window satisfies at least one of the following:

[0336] The start time of the time window is after the end time of the time resources of multiple D2R transmissions, which are scheduled or triggered by the same R2D transmission.

[0337] The start time of the time window is after the end time of the time resource for the first D2R transmission of the first IoT device;

[0338] The start time of the time window is the same as the start time of the time window of the second IoT device, and the first D2R of the first IoT device and the second IoT device is scheduled or triggered by the same R2D transmission.

[0339] The start time of the time window is the end time of the time window of the third IoT device, and the first D2R of the first IoT device and the third IoT device is scheduled or triggered by the same R2D transmission.

[0340] The start time of the time window is after the end time of the time window of the fourth IoT device, and the first D2R of the first IoT device and the fourth IoT device are scheduled or triggered by the same R2D transmission.

[0341] Optionally, the determination of the time window includes:

[0342] The duration or end time of the time window is determined based on the second information, wherein the second information includes at least one of the following:

[0343] Predefined information;

[0344] Reader instructions;

[0345] The time interval between D2R transmission and R2D transmission, wherein the time interval between D2R transmission and R2D transmission represents the time interval between the first IoT device sending a D2R transmission and the reader responding by sending an R2D transmission;

[0346] The resource configuration information of the multiple D2R transmissions, wherein the multiple D2R transmissions are scheduled or triggered by the same R2D transmission;

[0347] Resource information transmitted by the first D2R of the first IoT device;

[0348] The data rate of the first D2R transmission of the first IoT device;

[0349] The device type of the first IoT device;

[0350] Inventory type;

[0351] The second time interval is a time interval related to the time deviation;

[0352] The third time interval is a predefined time interval or a time interval indicated by the reader.

[0353] Optionally, the resource configuration information of the plurality of D2R transmissions includes at least one of the following:

[0354] The multiple D2Rs transmit TDM resource information;

[0355] The multiple D2Rs transmit FDM resource information.

[0356] Optionally, the second time interval is determined based on at least one of the following:

[0357] Sampling frequency drift (SFO), time drift, frequency tolerance (FrT), and backscatter frequency (BLF).

[0358] Optionally, the time window has a duration of N time units, where N is a positive integer, and the time units are determined based on at least one of the following:

[0359] The time interval between D2R and R2D transmissions, the absolute time unit, the time unit of R2D transmission, the time unit of D2R transmission, and the symbol time length of Orthogonal Frequency Division Multiplexing (OFDM);

[0360] The time interval between the D2R transmission and the R2D transmission represents the time interval between the first IoT device sending a D2R transmission and the reader responding to the D2R by sending an R2D transmission.

[0361] Optionally, the time unit of the R2D transmission includes at least one of the following:

[0362] The chip time length corresponding to the R2D preamble, the chip time length corresponding to the physical reader to the device channel PRDCH, and the time length corresponding to the information bits.

[0363] Optionally, the time unit of the D2R transmission includes at least one of the following:

[0364] The chip time length corresponding to the D2R preamble, the chip time length corresponding to the PDRCH channel from the IoT device to the reader, and the time length corresponding to the information bits.

[0365] Optionally, the processor 2110 is also used for:

[0366] Under target conditions, monitoring of R2D transmission is stopped, and the target conditions include at least one of the following:

[0367] R2D transmission is detected, or R2D transmission matching the first IoT device is detected;

[0368] The time window ends;

[0369] R2D transmissions including indication information are detected, the indication information being used to indicate that the R2D transmission is the last R2D transmission in the time window, or the indication information being used to indicate that there are no subsequent R2D transmissions in the time window;

[0370] The battery level of the first IoT device is below a preset threshold.

[0371] The aforementioned communication equipment can save power consumption for IoT devices.

[0372] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the monitoring method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0373] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described monitoring method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0374] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0375] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above monitoring method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0376] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0377] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described monitoring method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0378] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0379] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0380] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A monitoring method, comprising: a first IoT device determining a time window, the time window being a window for monitoring a reader-to-IoT device (R2D) transmission; the first IoT device monitoring the R2D transmission in the time window.

2. The method of claim 1, wherein, The first IoT device determining the time window comprises at least one of: the first IoT device determining a start time of the time window; the first IoT device determining a time length of the time window; the first IoT device determining an end time of the time window.

3. The method of claim 2, wherein, The first IoT device determining the start time of the time window comprises: the first IoT device determining the start time of the time window based on first information, the first information comprising at least one of: resource information of a plurality of IoT device-to-reader (D2R) transmissions; resource information of a first D2R transmission of the first IoT device, the first D2R transmission being a D2R transmission sent by the first IoT device before the time window; a time interval between a D2R transmission and a R2D transmission, the time interval between the D2R transmission and the R2D transmission representing a time interval from when the first IoT device sends the D2R transmission to when a reader sends a R2D transmission in response to the D2R transmission; a first time interval, the first time interval being used to make the start time of the time window after time resources of a plurality of D2R transmissions; a second time interval, the second time interval being a time interval related to a time offset; a time length of a time window of another IoT device; an end time of a time window of another IoT device; wherein the plurality of D2R transmissions are scheduled or triggered by a same R2D transmission.

4. The method of claim 3, wherein, The resource information of the plurality of D2R transmissions comprises at least one of: an end time of a last time resource of time resources of the plurality of D2R transmissions, the plurality of D2R transmissions being time division multiplexing (TDM) or frequency division multiplexing (FDM); resource configuration information of the plurality of D2R transmissions.

5. The method of claim 3 or 4, wherein, The resource information of the first D2R transmission of the first IoT device comprises at least one of: an end time of a time resource of the first D2R transmission of the first IoT device; location information of the time resource of the first D2R transmission of the first IoT device in time resources of the plurality of D2R transmissions.

6. The method of any one of claims 2 to 5, wherein, The start time of the time window satisfies at least one of: the start time of the time window is after an end time of time resources of the plurality of D2R transmissions, the plurality of D2R transmissions being scheduled or triggered by a same R2D transmission; the start time of the time window is after an end time of a time resource of the first D2R transmission of the first IoT device; the start time of the time window is the same as a start time of a time window of a second IoT device, first D2R transmissions of the first IoT device and the second IoT device being scheduled or triggered by a same R2D transmission; the start time of the time window is an end time of a time window of a third IoT device, first D2R transmissions of the first IoT device and the third IoT device being scheduled or triggered by a same R2D transmission; A start time of the time window is after an end time of a time window of a fourth IoT device, and a first D2R transmission of the first IoT device and the fourth IoT device is scheduled or triggered by a same R2D transmission.

7. The method of any one of claims 2 to 6, wherein, The first IoT device determines a time window, including: The first IoT device determines a time length or an end time of the time window based on second information, the second information including at least one of: Predefined information; An indication of a reader; A time interval between a D2R transmission and a R2D transmission, the time interval between the D2R transmission and the R2D transmission representing a time interval from when the first IoT device transmits the D2R transmission to when the reader transmits the R2D transmission in response to the D2R transmission; Resource configuration information of a plurality of D2R transmissions, the plurality of D2R transmissions being scheduled or triggered by a same R2D transmission; Resource information of a first D2R transmission of the first IoT device; A data rate of the first D2R transmission of the first IoT device; A device type of the first IoT device; An inventory type; A second time interval, the second time interval being a time interval related to a time offset; A third time interval, the third time interval being a time interval predefined or indicated by a reader.

8. The method of claim 4 or 7, wherein, The resource configuration information of the plurality of D2R transmissions includes at least one of: Resource information of the plurality of D2R transmissions TDMed; Resource information of the plurality of D2R transmissions FDMed.

9. The method of any one of claims 3 to 8, wherein, The second time interval is determined based on at least one of: A sampling frequency offset SFO, a time drift, a frequency tolerance FrT, a backscattering frequency BLF.

10. The method of any one of claims 1 to 9, wherein, A time length of the time window is N time units, N being a positive integer, the time unit being determined based on at least one of: The time interval between the D2R transmission and the R2D transmission, an absolute time unit, a time unit of the R2D transmission, a time unit of the D2R transmission, an orthogonal frequency division multiplexing OFDM symbol time length; The time interval between the D2R transmission and the R2D transmission represents a time interval from when the first IoT device transmits the D2R transmission to when the reader transmits the R2D transmission in response to the D2R transmission.

11. The method of claim 10, wherein, The time unit of the R2D transmission includes at least one of: A chip time length corresponding to a R2D preamble, a chip time length corresponding to a physical reader to device channel PRDCH, a time length corresponding to an information bit.

12. The method of claim 10, wherein, The time unit of the D2R transmission includes at least one of: A chip time length corresponding to a D2R preamble, a chip time length corresponding to a physical device to reader channel PDRCH, a time length corresponding to an information bit.

13. The method of any one of claims 1 to 12, further comprising: Stopping monitoring for the R2D transmission under a target condition, the target condition including at least one of: Monitoring for the R2D transmission, or monitoring for the R2D transmission matching the first IoT device; The time window ending; monitoring a R2D transmission including indication information, the indication information indicating that the R2D transmission is the last R2D transmission in the time window, or the indication information indicating that there is no R2D transmission following the time window; a power of the first IoT device is lower than a preset threshold.

14. A monitoring apparatus, comprising: a processing module configured to determine a time window, the time window being a window for monitoring a reader-to-IoT device (R2D) transmission; a receiving module configured to monitor a R2D transmission in the time window.

15. The apparatus of claim 14, wherein, The processing module is configured to determine at least one of: a start time of the time window; a time length of the time window; an end time of the time window.

16. The apparatus of claim 15, wherein, The determination of the start time of the time window comprises: determining the start time of the time window based on first information, the first information comprising at least one of: resource information of a plurality of IoT device-to-reader (D2R) transmissions; resource information of a first D2R transmission of a first IoT device, the first D2R transmission being a D2R transmission sent by the first IoT device before the time window; a time interval between a D2R transmission and a R2D transmission, the time interval between the D2R transmission and the R2D transmission representing a time interval from when the first IoT device sends the D2R transmission to when a reader sends a R2D transmission in response to the D2R transmission; a first time interval, the first time interval being used to make the start time of the time window after a time resource of a plurality of D2R transmissions; a second time interval, the second time interval being a time interval related to a time offset; a time length of a time window of another IoT device; an end time of a time window of another IoT device; wherein the plurality of D2R transmissions are scheduled or triggered by a same R2D transmission.

17. The apparatus of claim 15 or 16, wherein, The processing module is configured to determine the time length or the end time of the time window based on second information, the second information comprising at least one of: predefined information; an indication of a reader; a time interval between a D2R transmission and a R2D transmission, the time interval between the D2R transmission and the R2D transmission representing a time interval from when the first IoT device sends the D2R transmission to when a reader sends a R2D transmission in response to the D2R transmission; resource configuration information of a plurality of D2R transmissions, the plurality of D2R transmissions being scheduled or triggered by a same R2D transmission; resource information of a first D2R transmission of the first IoT device; a data rate of a first D2R transmission of the first IoT device; a device type of the first IoT device; an inventory type; the second time interval being a time interval related to a time offset; a third time interval, the third time interval being a time interval predefined or indicated by a reader.

18. The apparatus of any one of claims 14-17, wherein, The processing module is further configured to stop monitoring the R2D transmission under a target condition, the target condition comprising at least one of: monitoring a R2D transmission, or monitoring a R2D transmission matching the first IoT device; the time window ending; monitoring a R2D transmission including indication information, the indication information indicating that the R2D transmission is the last R2D transmission in the time window, or the indication information indicating that there is no subsequent R2D transmission in the time window; the first IoT device has a power level lower than a preset threshold.

19. An IoT device comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implement the steps of the monitoring method according to any one of claims 1 to 13.

20. A readable storage medium, the readable storage medium storing programs or instructions, the programs or instructions, when executed by a processor, implement the steps of the monitoring method according to any one of claims 1 to 13.

21. A computer program product stored in a storage medium, the computer program product being executed by at least one processor to implement the steps of the monitoring method according to any one of claims 1 to 13.

Images