Internet-of-things information transmission method and apparatus, and network-side device

Abstract

The present application belongs to the technical field of communications. Disclosed are an Internet-of-Things information transmission method and apparatus, and a network-side device. The Internet-of-Things information transmission method in the embodiments of the present application comprises: an Internet-of-Things device receiving a first R2D transmission, wherein the first R2D transmission is used for indicating at least one of the following: quantity information of D2R transmission from a first device to a reader, and scheduling information of at least one first D2R transmission, the first D2R transmission being a D2R transmission indicated or scheduled by means of the first R2D transmission.

Description

Internet of Things (IoT) information transmission methods, devices and network-side equipment

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410967792.3, filed in China on July 18, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to an Internet of Things (IoT) information transmission method, apparatus, and network-side equipment. Background Technology

[0004] With the development of communication technology, the application of Ambient Internet of Things (A-IoT) is becoming increasingly widespread. However, some related technologies have not yet defined the specific content of Reader-to-Device (R2D) transmission, and still use New Radio (NR) format signaling to transmit information to IoT devices, specifically Medium Access Control (MAC) Protocol Data Units (PDUs). The content included in this signaling is the same as the signaling sent in the NR system, which leads to high demodulation time and complexity for IoT devices, resulting in high power consumption. Summary of the Invention

[0005] This application provides an IoT information transmission method, apparatus, and network-side device that can solve the problem of high power consumption in IoT devices.

[0006] Firstly, an Internet of Things (IoT) information transmission method is provided, including:

[0007] The IoT device receives a first R2D transmission, the first R2D transmission being used to indicate at least one of the following:

[0008] The quantity information transmitted from the first device to the reader (D2R);

[0009] At least one scheduling information for the first D2R transmission;

[0010] Wherein, the first D2R transmission is the D2R transmission indicated or scheduled by the first R2D transmission.

[0011] Secondly, an Internet of Things (IoT) information transmission method is provided, including:

[0012] The communication device sends a first R2D transmission to the Internet of Things (IoT) device, the first R2D transmission being used to indicate at least one of the following:

[0013] The quantity information transmitted from the first device to the reader (D2R);

[0014] At least one scheduling information for the first D2R transmission;

[0015] Wherein, the first D2R transmission is the D2R transmission indicated or scheduled by the first R2D transmission.

[0016] Thirdly, an Internet of Things (IoT) information transmission device is provided, comprising:

[0017] A receiving module is configured to receive a first R2D transmission, the first R2D transmission being configured to indicate at least one of the following:

[0018] The quantity information transmitted from the first device to the reader (D2R);

[0019] At least one scheduling information for the first D2R transmission;

[0020] Wherein, the first D2R transmission is the D2R transmission indicated or scheduled by the first R2D transmission.

[0021] Fourthly, an Internet of Things (IoT) information transmission device is provided, comprising:

[0022] The sending module is configured to send a first R2D transmission to an IoT device, the first R2D transmission indicating at least one of the following:

[0023] The quantity information transmitted from the first device to the reader (D2R);

[0024] At least one scheduling information for the first D2R transmission;

[0025] Wherein, the first D2R transmission is the D2R transmission indicated or scheduled by the first R2D transmission.

[0026] Fifthly, an Internet of Things (IoT) information transmission device is provided, the device being configured to perform the steps of the IoT device-side IoT information transmission method as provided in the embodiments of this application.

[0027] In a sixth aspect, an Internet of Things (IoT) information transmission device is provided, the device being configured to perform the steps of the IoT information transmission method on the communication device side as provided in the embodiments of this application.

[0028] In a seventh aspect, an apparatus is provided, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions being executed by the processor to implement the steps of the IoT device-side IoT information transmission method as provided in the embodiments of this application.

[0029] Eighthly, an apparatus is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a first R2D transmission, the first R2D transmission being configured to indicate at least one of the following: quantity information of the first D2R transmission; scheduling information of at least one first D2R transmission; wherein the first D2R transmission is a D2R transmission indicated or scheduled by the first R2D transmission.

[0030] In a ninth aspect, a communication device is provided, the device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions being executed by the processor to implement the steps of the Internet of Things information transmission method on the communication device side as provided in the embodiments of this application.

[0031] In a tenth aspect, a communication device is provided, including a processor and a communication interface, wherein the communication interface is used to send a first R2D transmission to an Internet of Things (IoT) device, the first R2D transmission being used to indicate at least one of the following: quantity information of the first D2R transmission; scheduling information of at least one first D2R transmission; wherein the first D2R transmission is a D2R transmission indicated or scheduled by the first R2D transmission.

[0032] In the eleventh aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the IoT information transmission method on the IoT device side as provided in the embodiments of this application, or implement the steps of the IoT information transmission method on the communication device side as provided in the embodiments of this application.

[0033] In a twelfth aspect, a wireless communication system is provided, comprising: an Internet of Things (IoT) device and a communication device, wherein the IoT device can be used to perform the steps of the IoT information transmission method on the IoT device side as provided in the embodiments of this application, and the communication device can be used to perform the steps of the IoT information transmission method on the communication device side as provided in the embodiments of this application.

[0034] In a thirteenth aspect, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the IoT information transmission method on the IoT device side as provided in the embodiments of this application, or to implement the IoT information transmission method on the communication device side as provided in the embodiments of this application.

[0035] In a fourteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the IoT information transmission method on the IoT device side as provided in the embodiments of this application, or the computer program / program product is executed by at least one processor to implement the steps of the IoT information transmission method on the communication device side as provided in the embodiments of this application.

[0036] In this embodiment, the IoT device receives a first R2D transmission, which indicates at least one of the following: quantity information of the first D2R transmission; and scheduling information of at least one first D2R transmission. The first D2R transmission is a D2R transmission indicated or scheduled by the first R2D transmission. Since the first R2D transmission indicates at least one of the quantity information of the first D2R transmission and the scheduling information of at least one first D2R transmission, it is possible to indicate or schedule D2R transmissions to the IoT device based on the R2D transmission. This avoids transmitting information to the IoT device using NR format signaling, reducing the time and complexity of demodulating signaling for the IoT device, thus saving power. Furthermore, by indicating at least one of the quantity information of the first D2R transmission and the scheduling information of at least one first D2R transmission, it is possible to support one R2D indication or scheduling of multiple D2Rs, thereby reducing transmission behavior between the communication device and the IoT device, resulting in even better power saving. Attached Figure Description

[0037] Figure 1a is a schematic diagram of a system provided in an embodiment of this application;

[0038] Figure 1b is a schematic diagram of an application scenario provided by an embodiment of this application;

[0039] Figure 1c is a schematic diagram of another application scenario provided by an embodiment of this application;

[0040] Figure 2 is a flowchart of an Internet of Things (IoT) information transmission method provided in an embodiment of this application;

[0041] Figures 3 to 8 are schematic diagrams of R2D transmission provided in the embodiments of this application;

[0042] Figure 9 is a flowchart of an Internet of Things (IoT) information transmission method provided in an embodiment of this application;

[0043] Figures 10 to 15 are schematic diagrams of R2D transmission provided in the embodiments of this application;

[0044] Figure 16 is a structural diagram of an Internet of Things (IoT) information transmission device provided in an embodiment of this application;

[0045] Figure 17 is a structural diagram of an Internet of Things (IoT) information transmission device provided in an embodiment of this application;

[0046] Figure 18 is a structural diagram of a communication device provided in an embodiment of this application;

[0047] Figure 19 is a structural diagram of a terminal provided in an embodiment of this application;

[0048] Figure 20 is a structural diagram of a network-side device provided in an embodiment of this application. Detailed Implementation

[0049] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0050] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0051] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0052] It is worth noting that the technologies described in this application are 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 this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0053] Figure 1a shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipborne equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication functions, such as refrigerators, televisions, washing machines or furniture), game console, personal computer (PC), ATM, self-service machine, Internet of Things (IoT) device or Ambient IoT (A-IoT) device, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 can include access network equipment or core network equipment, wherein access network equipment can also be referred to as Radio Access Network (RAN) equipment, radio access network function, radio access network unit, or satellite. Access network equipment can include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0054] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0055] 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).

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

[0057] In some implementations, the topology of A-IoT can include two types, as shown in Figure 1b and Figure 1c. In the topology shown in Figure 1b, the BS communicates with the A-IoT device, that is, the BS is the reader. In the topology shown in Figure 1c, 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.

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

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

[0060] 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:

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

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

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

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

[0065] In some embodiments, an A-IoT device may be a tag or other low-power IoT device or a terminal that acts as a tag.

[0066] In some embodiments, the terminal that serves as a tag can be a terminal with degraded capabilities, which may include, but are not limited to, processing capabilities or energy storage capabilities.

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

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

[0069] 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:

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

[0071] Device-terminated data transmission (DO-DTT) is a data transfer service initiated by a device (DT) and terminated 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.

[0072] In some implementations, the inventory or inventory + control process for A-IoT devices can be as follows:

[0073] As a foundation, for programs that support "inventory only", the process is as follows:

[0074] Step A: A-IoT paging;

[0075] Step B: Device ID transmission (with or without random access).

[0076] As a foundation, for the "Inventory and Command" case where the program supports it, the process is as follows:

[0077] Step A: A-IoT paging;

[0078] Step B: Device ID transmission (with or without random access);

[0079] Step C: Data transfer from reader to device (e.g., R2D transfer), and

[0080] Step D: Data transmission from the corresponding device to the reader (e.g., feedback).

[0081] In some implementations, the four-step random access can be as follows:

[0082] 1. A-IoT Message 1 (A-IoT Msg1): The device sends its ID to the reader. The ID is a random ID generated by the device (e.g., randomly generated or generated based on the device ID);

[0083] 2. A-IoT Message 2 (A-IoT Msg2): The reader responds with the ID received in Msg1.

[0084] 3. A-IoT Message 3 (A-IoT Msg3): The device sends its device ID and / or any other upper-layer data (depending on the upper-layer request);

[0085] 4. If Msg2 containing the same random ID is received in Msg1, the device considers the contention to be resolved successfully.

[0086] 5. Message 4 ("Msg4") (i.e., the subsequent R2D transmission after the D2R transmission) does not always need to be sent in random access mode. "Msg4" can be considered as handling the failure of the Msg3 transmission (due to various reasons).

[0087] In some implementations, two-step contention-based random access (CBRA) can be as follows:

[0088] 1. A-IoT Msg1: The device sends its device ID and / or any other upper-layer data (depending on the upper-layer request);

[0089] 2. A-IoT Msg2: The reader may respond with some information in Msg1.

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

[0091] Please refer to Figure 2, which is a flowchart of an Internet of Things (IoT) information transmission method provided in an embodiment of this application. As shown in Figure 2, it includes the following steps:

[0092] Step 201: The IoT device receives a first R2D transmission, the first R2D transmission being used to indicate at least one of the following:

[0093] The quantity information of the first D2R transmission;

[0094] At least one scheduling information for the first D2R transmission;

[0095] Wherein, the first D2R transmission is the D2R transmission indicated or scheduled by the first R2D transmission.

[0096] The aforementioned IoT devices can be A-IoT devices or other IoT devices, without limitation.

[0097] The above-mentioned receiving of the first R2D transmission refers to the Internet of Things device receiving the first R2D transmission sent by the communication device, which is a reader, specifically a network-side device or a terminal.

[0098] In this embodiment of the application, the first R2D transmission may also be referred to as the first R2D message, the first R2D signaling, or the Physical Reader-to-Device Channel (PRDCH).

[0099] In this embodiment of the application, D2R transmission can also be referred to as D2R message, D2R signaling, or Physical Device-to-Reader Channel (PDRCH).

[0100] In some implementations, the first R2D transmission can be A-IoT Msg2, such as when the IoT device sends A-IoT Msg1 to the communication device before receiving the first R2D transmission. In this case, A-IoT Msg2 and A-IoT Msg1 are A-IoT Msg2 and A-IoT Msg1 in a four-step or two-step access process.

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

[0102] In some implementations, the first R2D transmission described above may be a paging message.

[0103] It should be noted that the type of the first R2D transmission is not limited in the embodiments of this application. Specifically, it can be an R2D transmission used to indicate or schedule D2R transmission.

[0104] In some implementations, the D2R transmission described above may be A-IoT Msg3, or it may be an identifier, data or information that the IoT device can feed back to the reader. In the embodiments of this application, the type of D2R transmission is not limited.

[0105] In this embodiment of the application, A-IoT Msg3 can also be abbreviated as Msg3.

[0106] The aforementioned first R2D transmission indication or scheduled D2R transmission can also be understood as a D2R transmission triggered by the first R2D transmission.

[0107] The aforementioned first R2D transmission indication can be explicit or implicit. For example, the aforementioned first R2D transmission may include scheduling information for at least one of the aforementioned first D2R transmissions, or the aforementioned first R2D transmission may include scheduling information for a portion of the first D2R transmissions, while the scheduling information for another portion of the D2R transmissions is implicitly indicated based on the included scheduling information for that portion of the first D2R transmissions. Another example is that the quantity information of the aforementioned first D2R transmissions may be implicitly indicated by the quantity including scheduling information, or the aforementioned first R2D transmissions may include the quantity information of the first D2R transmissions. Yet another example is that the scheduling information for at least one first D2R transmission is implicitly indicated by the quantity information of the first D2R transmissions, such as deriving the scheduling information for each D2R transmission based on a pre-configured mapping relationship using the quantity information of the first D2R transmissions.

[0108] In this embodiment of the application, without indicating the above-mentioned scheduling information, the IoT device can deduce the scheduling resources of the first D2R corresponding to the IoT device based on the quantity information of the first D2R transmission. For example, when indicating two first D2Rs, the pre-configured resources corresponding to the first R2D transmission can be divided into two scheduling resources to determine one of the scheduling resources as the scheduling resource of the first D2R corresponding to the IoT device.

[0109] In this embodiment of the application, without specifying the quantity information of the first D2R transmissions, the IoT device can determine the quantity information of the first D2R transmissions based on the scheduling information of at least one first D2R transmission, such as using the number of scheduled resources as the quantity of the first D2R transmissions. Alternatively, in some scenarios, the IoT device may not need to determine the quantity information of the first D2R transmissions.

[0110] In this embodiment, since the first R2D transmission indicates at least one of the quantity information of the first D2R transmission and the scheduling information of at least one first D2R transmission, it is possible to indicate or schedule D2R transmissions to IoT devices based on the first R2D transmission. This avoids transmitting information to IoT devices using NR format signaling, reducing the time and complexity of demodulating signaling for IoT devices, thus saving power for IoT devices. Furthermore, by indicating at least one of the quantity information of the first D2R transmission and the scheduling information of at least one first D2R transmission, it is possible to support one R2D indication or scheduling of multiple D2Rs, thereby reducing transmission behavior between communication devices and IoT devices, resulting in even better power saving.

[0111] As an optional implementation, the quantity information of the first D2R transmission includes one of the following:

[0112] The number of first D2R transmissions;

[0113] The number of resources transmitted in the first D2R transmission.

[0114] The number of the first D2R transmissions mentioned above can be understood as how many D2R transmissions a first R2D transmission indicates or schedules, such as indicating or scheduling N (N>=1) D2R transmissions.

[0115] When multiple first D2R transmissions are instructed or scheduled, the different first D2R transmissions can be first D2R transmissions of different IoT devices. In some implementations, there may also be at least two first D2R transmissions of the same IoT device among the multiple first D2R transmissions. The at least two first D2R transmissions of the same IoT device can be repeated transmissions of the same data or transmissions of different data.

[0116] The resource quantity of the first D2R transmission mentioned above can be understood as how many D2R transmission resources are scheduled or allocated in a first R2D, such as scheduling or allocating transmission resources for N (N>=1) D2R transmissions.

[0117] The number of first D2R transmissions or the amount of resources transmitted in the first D2R transmission can support one R2D instruction or scheduling of multiple D2Rs, thereby saving transmission resource overhead and device power consumption.

[0118] Optionally, the number of resources in the first D2R transmission includes at least one of the following:

[0119] The amount of time-domain resources in the first D2R transmission;

[0120] The number of frequency domain resources in the first D2R transmission;

[0121] The amount of airspace resources transmitted in the first D2R transmission;

[0122] The number of code domain resources in the first D2R transmission.

[0123] The number of time-domain resources for the first D2R transmission can be expressed as Nt (Nt>=1), which means how many time-division multiplexing (TDM) D2R transmissions are scheduled or triggered by a first R2D transmission, or how many D2R transmission resources are scheduled / allocated in the time domain by a first R2D transmission.

[0124] The aforementioned amount of time-domain resources can support time-division multiplexing of multiple D2R transmissions to improve IoT transmission performance.

[0125] The number of frequency domain resources for the above D2R transmission can be represented as Nf (Nf>=1), and each frequency domain resource can correspond to one D2R transmission.

[0126] The aforementioned number of frequency domain resources can support frequency division multiplexing of multiple D2R transmissions, thereby improving the transmission performance of the Internet of Things.

[0127] The number of spatial or code domain resources for the aforementioned D2R transmission can be represented as Nc (Nc>=0), and each frequency domain resource can correspond to one D2R transmission.

[0128] The aforementioned number of spatial or code domain resources can support code division multiplexing of multiple D2R transmissions, thereby improving IoT transmission performance.

[0129] As an optional implementation, the scheduling information of the at least one first D2R transmission includes at least one of the following:

[0130] Multiplexing of at least two first D2R transmissions;

[0131] Common transmission parameters for at least two first D2R transmissions;

[0132] At least one dedicated transmission parameter for the first D2R transmission.

[0133] The aforementioned at least two first D2R transmissions may be all or part of the D2R transmissions indicated or scheduled by the aforementioned first R2D transmission. For example, the first R2D transmission indicates or schedules N D2R transmissions, and the aforementioned at least two may be M, where M is an integer less than or equal to N.

[0134] The aforementioned reuse methods may include at least one of the following:

[0135] Time division multiplexing, frequency division multiplexing, code division multiplexing.

[0136] For example, M D2R transmissions include at least one or more combinations: time-division multiplexed D2R, frequency-division multiplexed D2R, and code-division multiplexed D2R.

[0137] The above multiplexing methods can support at least one of time division multiplexing, frequency division multiplexing, and code division multiplexing for multiple D2R transmissions, thereby improving the transmission performance of the Internet of Things.

[0138] The aforementioned common transmission parameters can be understood as at least two first D2R transmissions sharing all or part of the same transmission parameters, which can save signaling overhead.

[0139] The aforementioned common transmission parameters can also be called shared transmission parameters or shared scheduling information.

[0140] In some implementations, the aforementioned common transmission parameters include at least one of the following:

[0141] Information bit length, number of information bits, transfer block size (TBS), chip length, retransmission type, number of retransmissions, indication of whether to add cyclic redundancy check (CRC) information, number of CRC bits, indication of whether to use scrambling, indication of whether to use mask, scrambling sequence information, and mask information.

[0142] The aforementioned repeat transmission type can be block-level repeat, bit-level repeat type 1, or bit-level repeat type 2. Bit-level repeat type 1 means that each bit after CRC appending (if used) repeats R bits, and bit-level repeat type 2 means that each bit after CRC appending (if used) and forward error correction (FEC) (if used) repeats R bits.

[0143] In the above embodiments, the sharing of at least one of the above transmission parameters can be achieved, which can save signaling overhead.

[0144] The dedicated transmission parameters of at least one first D2R transmission can be understood as all or part of the transmission parameters of this at least one first D2R transmission being dedicated or not public. Furthermore, the aforementioned at least one first D2R transmission can be all or part of the aforementioned first R2D transmission indication or scheduling D2R transmission.

[0145] The aforementioned dedicated transmission parameters can also be referred to as dedicated scheduling information.

[0146] In some implementations, the aforementioned dedicated transmission parameters may include at least one of the following:

[0147] Start time, frequency domain resources, codeword information.

[0148] The aforementioned start time can be the start time of the time domain resources of the first D2R transmission. For example, for time-division multiplexed first D2R transmissions, the start time of each first D2R transmission, and multiple time-division multiplexed first D2R transmissions can adopt at least one of the following: a common frequency domain location or resource and a codeword.

[0149] The aforementioned frequency domain resources can be the frequency domain location or resources of each first D2R transmission for frequency division multiplexing.

[0150] The aforementioned frequency domain resources may be indicated or determined by at least one of the following:

[0151] Frequency shift parameter, number of line code repetitions in one information bit length, number of square wave repetitions in one information bit length, or frequency / period of square wave.

[0152] In addition, multiple first D2R transmissions of frequency division multiplexing can adopt at least one of the common transmission start time and codeword.

[0153] The codeword information mentioned above can be the codeword for each first D2R transmission of code division multiplexing, and multiple first D2R transmissions of code division multiplexing can adopt at least one of the common transmission start time and transmission frequency domain location / resource.

[0154] The aforementioned dedicated transmission parameters allow for the configuration of dedicated resources for each first D2R transmission, thereby improving transmission performance.

[0155] As an optional implementation, the first R2D transmission includes at least one of the following:

[0156] The first indication information is used to indicate whether the first R2D transmission is the last first R2D transmission in this communication process, or the first indication information is used to indicate whether there are any subsequent first R2D transmissions after the first R2D transmission.

[0157] The second indication information is used to indicate the amount of response information carried in the first R2D transmission;

[0158] The third indication information is used to indicate whether the response information corresponding to the third indication information is the last response information in the first R2D transmission;

[0159] The fourth indication information is used to indicate whether the response information corresponding to the fourth indication information should schedule the first D2R transmission;

[0160] The fifth indication information is used to indicate whether the response information corresponding to the fifth indication information contains the scheduling information of the first D2R transmission;

[0161] The sixth indication information is used to indicate whether there are dedicated transmission parameters in the first R2D transmission. The dedicated transmission parameters are the dedicated transmission parameters of the first D2R of the IoT device that match the response information corresponding to the sixth indication information.

[0162] At least one first D2R scheduling information;

[0163] The response information is the response information to the second D2R in the first R2D transmission.

[0164] The above communication process can be random access. For example, the first indication information indicates whether the current R2D transmission (such as A-IoT Msg2) is the last R2D transmission (such as A-IoT Msg2) in this random access, or indicates whether there will be any subsequent R2D transmissions (such as A-IoT Msg2) after the current R2D transmission (such as A-IoT Msg2).

[0165] For example, as shown in Figures 3 and 4, the first R2D transmission mentioned above includes an indication of whether it is the last Msg2 transmission.

[0166] The command code is used to determine the transmission type, purpose, function, and / or destination of the R2D transmission, such as whether the R2D transmission is an A-IoT paging, an A-IoT Msg2, or another function (read or write, etc.). This command code can also be called the command header.

[0167] The aforementioned first indication information can prevent IoT devices from continuing to monitor without subsequent R2D transmission, thereby achieving the effect of saving power for IoT devices.

[0168] It should be noted that in some implementations, the first instruction information mentioned above may not be included.

[0169] The aforementioned second D2R transmission is a D2R sent by the IoT device to the communication device before the aforementioned first R2D transmission, such as Msg1.

[0170] The aforementioned response information is a response to the second D2R transmission sent by the IoT device to the communication device prior to the first R2D transmission, and the response information corresponds one-to-one with the second D2R. For example, the response information to A-IoT Msg1 might be the ID received in Msg1 as responded by the reader. For example, the aforementioned second indication information is used to indicate the number of response messages to A-IoT Msg1 carried in the current R2D transmission (such as A-IoT Msg2). For example, as shown in Figures 5 and 6, the aforementioned first R2D transmission includes the number of response messages to A-IoT Msg1.

[0171] The response information corresponding to the aforementioned third indication information may include the third indication information within the response information. For example, the aforementioned first R2D transmission includes multiple response information, and each response information may include one third indication information. For instance, the aforementioned third indication information is used to indicate whether the response information of the current A-IoT Msg1 is the last response information to A-IoT Msg1 in the first R2D transmission (such as A-IoT Msg2).

[0172] The aforementioned second or third instruction information can prevent IoT devices from continuing to monitor if there is no subsequent response, thereby achieving the effect of saving power for IoT devices.

[0173] It should be noted that in some implementations, the second and third instruction information described above may not be included.

[0174] Furthermore, the number of response messages can also implicitly indicate the number of first D2R (e.g., A-IoT Msg3) transmissions, such as the number of first D2R transmissions being equal to the number of response messages. Whether the response message is the last response message in the first D2R transmission can also implicitly indicate the number of first D2R transmissions, such as the number of response messages detected by the IoT device.

[0175] The response information corresponding to the aforementioned fourth indication information may include the fourth indication information within the response information, such as each response information may include one fourth indication information. Whether the response information corresponding to the aforementioned fourth indication information schedules the first D2R transmission may indicate whether the corresponding response information includes the scheduling information of the first D2R transmission (such as A-IoT Msg3), or it may indicate whether the corresponding response information schedules the first D2R transmission. If it does schedule, the scheduling information may be included in the response information or in other information fields of the R2D transmission.

[0176] For example, as shown in Figure 7, the response information in the first R2D transmission includes an indication of whether to schedule a D2R transmission.

[0177] The fourth indication information mentioned above can be used to indicate whether to schedule the corresponding D2R transmission in the response information, thus eliminating the need for additional information indication and saving transmission overhead.

[0178] It should be noted that in some implementations, the fourth instruction information mentioned above may not be included, such as the default response information scheduling the first D2R transmission.

[0179] The response information corresponding to the aforementioned fifth indication information can be a response information that includes the fifth indication information, such as each response information may include one fifth indication information. The aforementioned fifth indication information indicates whether the response information is scheduling information. For example, as shown in Figure 8, the response information includes whether there is scheduling information for the first D2R transmission (such as A-IoT Msg3).

[0180] The aforementioned fifth instruction information enables IoT devices to parse response information based on the fifth instruction information, thereby reducing the complexity of parsing and saving power consumption of IoT devices.

[0181] It should be noted that in some implementations, the fifth indication information mentioned above may not be included. For example, the default response information may include scheduling information, or the length of the response information may be used to determine whether to include scheduling information.

[0182] The response information corresponding to the aforementioned sixth instruction information may include the sixth instruction information in the response information, such as each response information may include a sixth instruction information.

[0183] Whether a dedicated transmission parameter exists in the first R2D transmission can be understood as whether a dedicated information field carrying scheduling information in the first R2D transmission includes the dedicated transmission parameter, or whether the response information corresponding to the sixth indication information in the first R2D transmission includes the dedicated transmission parameter. That is, the dedicated transmission parameter can be included in the response information, or it can be included in other information fields of the first R2D transmission. Specifically, as shown in Figure 7, the dedicated scheduling information can be included in the information field corresponding to the separate scheduling information.

[0184] The aforementioned dedicated transmission parameters for the first D2R of the IoT device matching the response information corresponding to the sixth indication information can be understood as follows: one response information is used to respond to a second D2R (such as A-IoT Msg1), and one second D2R corresponds to one IoT device, that is, one response information corresponds to one IoT device. If a response information includes an IoT device identifier, the dedicated scheduling parameters indicated by the sixth indication information corresponding to the response information (such as the sixth indication information in the response information) are the dedicated transmission parameters for the first D2R transmission of that IoT device (such as A-IoT Msg3). Specifically, as shown in Figure 7, the response information includes dedicated scheduling information used to indicate whether a D2R transmission exists, i.e., dedicated transmission parameters.

[0185] The aforementioned sixth indication information enables the indication of dedicated transmission parameters, thereby improving the flexibility of the first D2R transmission.

[0186] In some implementations, the sixth indication information may not be carried. For example, it may be pre-agreed that the first D2R transmission of the IoT device corresponding to the first response information has dedicated transmission parameters.

[0187] The scheduling information of at least one first D2R mentioned above may be included in the response information or in a dedicated information field.

[0188] The scheduling information of at least one first D2R can be used to schedule at least one first D2R, so as to support one R2D transmission to schedule multiple D2R transmissions, thereby saving transmission resources and device power consumption.

[0189] It should be noted that the scheduling information of at least one first D2R can implicitly indicate the number of first D2R transmissions.

[0190] In some implementations, at least one of the aforementioned third indication information, fourth indication information, fifth indication information, sixth indication information, and scheduling information is located in the corresponding response information.

[0191] In this embodiment, at least one of the aforementioned third indication information, fourth indication information, fifth indication information, sixth indication information, and scheduling information can be carried in the response information, as shown in Figures 3 to 8, which makes the R2D transmission format more concise.

[0192] As an optional implementation, the first R2D transmission described above includes a first information field, which includes scheduling information for the at least one first D2R.

[0193] The first information field mentioned above can be understood as an information field used to carry scheduling information.

[0194] The scheduling information of at least one first D2R may include at least one of common scheduling information and dedicated scheduling information. For example, as shown in Figure 7, both common scheduling information and dedicated scheduling information are in the first information field.

[0195] Since the first information field includes the scheduling information of at least one first D2R transmission, it is possible to avoid repeatedly carrying common scheduling information, thereby saving the overhead of R2D transmission.

[0196] In some implementations, the first R2D transmission described above may further include at least one of the following:

[0197] Reserved fields, CRC fields.

[0198] As an optional implementation, if the first R2D transmission does not indicate scheduling information for the target first D2R transmission, the IoT device may use at least one of the following scheduling information when sending the target first D2R transmission:

[0199] Refer to the scheduling information for D2R transmission;

[0200] The scheduling information defined by the protocol.

[0201] The aforementioned reference D2R transmission can be pre-configured or agreed upon by the protocol.

[0202] For example, the above-mentioned reference D2R transmission may include at least one of the following:

[0203] The most recent D2R transmission;

[0204] The most recent D2R transmission triggered or scheduled by the IoT device;

[0205] Msg1 (e.g., A-IoT Msg1);

[0206] The D2R transmission was triggered or scheduled by the most recent command received by the IoT device, and the command carried unique identification information that identifies the IoT device.

[0207] The most recent D2R transmission mentioned above can also be understood as the previous D2R transmission.

[0208] The D2R transmission triggered or scheduled by the most recent command received by the aforementioned IoT device can be a D2R transmission triggered or scheduled by the most recent A-IoT command received by the IoT device that uniquely identifies the device.

[0209] The scheduling information defined in the above protocol can be the default value specified by the protocol. For example, the scheduling information defined in the above protocol includes: the transmission time window defined by the protocol. For example, when one or more D2R transmissions do not use time division multiplexing, the start time of the D2R transmission may not be indicated, but is specified by the protocol within the time window [T]. R2Dmin ,T R2Dmax Send in ]

[0210] In some implementations, the scheduling information defined by the above protocol may also represent the addition of a CRC, or it may be the length of the CRC. For example, the length of the CRC is fixed at X bits, regardless of the transmission length of D2R / TBS. Alternatively, the length of the CRC may be determined based on the transmission length of D2R / TBS. For example, a larger TBS may use an X2-bit CRC, and a smaller TBS may use an X1-bit CRC, where X2 > X1.

[0211] In the above embodiments, scheduling indication information can be omitted in the first R2D transmission, thereby saving the overhead of R2D transmission.

[0212] In this embodiment, the IoT device receives a first R2D transmission, which indicates at least one of the following: quantity information of the first D2R transmission; and scheduling information of at least one first D2R transmission. The first D2R transmission is a D2R transmission indicated or scheduled by the first R2D transmission. Since the first R2D transmission indicates at least one of the quantity information of the first D2R transmission and the scheduling information of at least one first D2R transmission, it is possible to indicate or schedule D2R transmissions to the IoT device based on the R2D transmission. This avoids transmitting information to the IoT device using NR format signaling, reducing the time and complexity of demodulating signaling for the IoT device, thus saving power. Furthermore, by indicating at least one of the quantity information of the first D2R transmission and the scheduling information of at least one first D2R transmission, it is possible to support one R2D indication or scheduling of multiple D2Rs, thereby reducing transmission behavior between the communication device and the IoT device, resulting in even better power saving.

[0213] Please refer to Figure 9, which is a flowchart of another IoT information transmission method provided in an embodiment of this application. As shown in Figure 9, it includes the following steps:

[0214] Step 901: The communication device sends a first R2D transmission to the IoT device, the first R2D transmission being used to indicate at least one of the following:

[0215] The quantity information transmitted from the first device to the reader (D2R);

[0216] At least one scheduling information for the first D2R transmission;

[0217] Wherein, the first D2R transmission is the D2R transmission indicated or scheduled by the first R2D transmission.

[0218] Optionally, the quantity information of the first D2R transmission includes one of the following:

[0219] The number of first D2R transmissions;

[0220] The number of resources transmitted in the first D2R transmission.

[0221] Optionally, the number of resources in the first D2R transmission includes at least one of the following:

[0222] The amount of time-domain resources in the first D2R transmission;

[0223] The number of frequency domain resources in the first D2R transmission;

[0224] The amount of airspace resources transmitted in the first D2R transmission;

[0225] The number of code domain resources in the first D2R transmission.

[0226] Optionally, the scheduling information for the at least one first D2R transmission includes at least one of the following:

[0227] Multiplexing of at least two first D2R transmissions;

[0228] Common transmission parameters for at least two first D2R transmissions;

[0229] At least one dedicated transmission parameter for the first D2R transmission.

[0230] Optionally, the reuse method includes at least one of the following:

[0231] Time division multiplexing, frequency division multiplexing, code division multiplexing.

[0232] Optionally, the common transmission parameters include at least one of the following:

[0233] Information bit length, number of information bits, transport block size (TBS), chip length, retransmission type, number of retransmissions, indication information for adding cyclic redundancy check (CRC) information, number of CRC bits, indication information for using scrambling, indication information for using a mask, scrambling sequence information, and mask information.

[0234] Optionally, the dedicated transmission parameters include at least one of the following:

[0235] Start time, frequency domain resources, codeword information.

[0236] Optionally, the first R2D transmission includes at least one of the following:

[0237] The first indication information is used to indicate whether the first R2D transmission is the last first R2D transmission in this communication process, or the first indication information is used to indicate whether there are any subsequent first R2D transmissions after the first R2D transmission.

[0238] The second indication information is used to indicate the amount of response information carried in the first R2D transmission;

[0239] The third indication information is used to indicate whether the response information corresponding to the third indication information is the last response information in the first R2D transmission;

[0240] The fourth indication information is used to indicate whether the response information corresponding to the fourth indication information should schedule the first D2R transmission;

[0241] The fifth indication information is used to indicate whether the response information corresponding to the fifth indication information contains the scheduling information of the first D2R transmission;

[0242] The sixth indication information is used to indicate whether there are dedicated transmission parameters in the first R2D transmission. The dedicated transmission parameters are the dedicated transmission parameters of the first D2R of the IoT device that match the response information corresponding to the sixth indication information.

[0243] At least one first D2R scheduling information;

[0244] The response information is the response information to the second D2R in the first R2D transmission.

[0245] Optionally, at least one of the third indication information, the fourth indication information, the fifth indication information, the sixth indication information, and the scheduling information is located in the corresponding response information.

[0246] Optionally, the first R2D transmission includes a first information field, which includes scheduling information for the at least one first D2R.

[0247] It should be noted that this embodiment is an implementation method of the Internet of Things device corresponding to the embodiment shown in Figure 2. For the specific implementation method, please refer to the relevant description of the embodiment shown in Figure 2. In order to avoid repeated description, this embodiment will not be repeated.

[0248] The following examples, using a communication device as the reader, the first R2D transmission as Msg2, the first D2R transmission as Msg3, the second D2R transmission as Msg1, and the transmission parameter as scheduling information, illustrate the method provided in this application through multiple embodiments:

[0249] Example 1:

[0250] A Msg2 carries N (N>=1) response messages to Msg1 and scheduling information for Msg3, which can be implemented in the following two ways:

[0251] Method 1: Restrict the reader to carry responses to all Msg1 messages received by the reader in a single Msg2 message. This way, if the device does not find a response to the Msg1 message it sent after receiving a Msg2 message, the device does not need to check the Msg2 message again, which can help save power for the device.

[0252] An IoT device determines its response to sending Msg1 by at least one of the following:

[0253] If the device ID carried in Msg2 is the same as the ID sent by the device in Msg1, the device can determine that Msg2 contains a response to Msg1 sent to the device, or the device can determine that the response information field in Msg2 is a response to itself.

[0254] By defining the sorting rules for different Msg1 response messages in Msg2, the sorting rules include at least one of the following:

[0255] The order in which Msg2 responds to multiple Msg1 responses is first based on the time sequence of Msg1, and then based on the frequency sequence of Msg1 from low to high, as shown in Figure 10.

[0256] The order in which Msg2 responds to multiple Msg1 responses is first based on the frequency domain resource order of Msg1 from low to high, and then based on the time domain resource order of Msg1, as shown in Figure 11.

[0257] The device determines its own response information by specifying the sorting rules for different Msg1 response information in Msg2. If multiple devices select conflicting Msg1 resources and the reader does not demodulate Msg1#i correctly, the response information for Msg1#i in Msg2 also includes indicating that the response information is invalid or indicating that the response information is for a conflicting Msg1#i.

[0258] Method 2: The reader is not restricted to carrying responses to all Msg1 messages received by the reader within a single Msg2 message. This means the reader can send multiple Msg2 messages in response to Msg1 messages sent by different devices. To help save device power, a "Is this the last Msg2 transmission?" field can be set in the Msg2 message. If this field indicates "No," and the device has not found a response to its own Msg1 message, the device needs to continue checking Msg2 messages to avoid missing any. If this field indicates "Yes," and the device has not found a response to its own Msg1 message, the device does not need to continue checking Msg2 messages. Figures 3 and 4 provide two example diagrams.

[0259] It should be noted that in the embodiments of this application, the "whether it is the last Msg2 transmission" field and the CRC field may or may not be carried. In some figures, these two fields are omitted, but they may exist.

[0260] As shown in Figure 5, each response message carries a fixed-length device ID and a scheduling information field for Msg3. The length of the scheduling field for Msg3 is fixed or variable. The dashed boxes represent the possible fields.

[0261] As shown in Figure 6, each response message carries a fixed-length device ID, a field indicating whether there is scheduling information for subsequent D2R operations, and a field for scheduling information for D2R operations. If the field indicating whether there is scheduling information for subsequent D2R operations is yes / yes, then the field for scheduling information for D2R operations exists; otherwise, the field for scheduling information for D2R operations does not exist.

[0262] As shown in Figure 12, the number of response messages carried in Msg2 can be obtained through the "whether it is the last response message" field in each response message. Each response message carries a fixed-length "whether it is the last response message", a fixed-length device ID, and a D2R scheduling information field.

[0263] Example 2:

[0264] In Example 1, the response information includes scheduling information for subsequent D2R transmissions. In Example 2, the D2R scheduling information is not included in the response information. This facilitates indicating shared scheduling information for multiple D2R transmissions, reducing signaling overhead. As shown in Figure 13, the "Shared Scheduling Information" field indicates shared scheduling parameters for all response information, with the same parameter values.

[0265] Figures 14 and 15 show that some response messages have corresponding D2R transmissions, while others do not. Response messages requiring D2R transmission need to carry dedicated D2R scheduling information. The Device finds its Device ID reported in Msg1 in the response message field and determines whether to read the shared and dedicated scheduling information in the D2R scheduling information based on whether the D2R scheduling information "exists" or "does not exist" as indicated in the response field. The Xth response message indicating "exists" corresponds to the Xth dedicated D2R scheduling information in the D2R scheduling information.

[0266] As shown in Figure 7 above, it is also possible to support some response information having corresponding D2R transmissions and others not having corresponding D2R transmissions. However, unlike Figures 14 and 15, in Figure 7, even if some response information schedules a D2R transmission, it may not carry the scheduling information specific to that D2R. If it is not carried, the parameters used for the D2R transmission are determined by the rules defined in the embodiment shown in Figure 2.

[0267] In this embodiment of the application, by indicating whether the current A-IoT Msg2 is the last A-IoT Msg2 transmission in this random access, or indicating whether there will be any subsequent A-IoT Msg2 transmissions after the current A-IoT Msg2 transmission; indicating the number of response messages to A-IoT Msg1 carried by the current A-IoT Msg2; or whether the response message of the current A-IoT Msg1 is the last response message to A-IoT Msg1 in A-IoT Msg2, it can help save power on the device;

[0268] By designing shared and dedicated scheduling fields, signaling and device reception time can be saved.

[0269] The IoT information transmission method provided in this application can be executed by an IoT information transmission device. This application uses an IoT information transmission device executing the IoT information transmission method as an example to illustrate the IoT information transmission device provided in this application.

[0270] This application provides an Internet of Things (IoT) information transmission device. As an example, the IoT information transmission device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations on these aspects.

[0271] An IoT information transmission 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 general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), 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: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0272] Specifically, referring to Figure 16, when the IoT information transmission device is a terminal or a component within a terminal, the IoT information transmission device 1600 includes:

[0273] Receiver module 1601 is configured to receive a first R2D transmission, the first R2D transmission being used to indicate at least one of the following:

[0274] The quantity information transmitted from the first device to the reader (D2R);

[0275] At least one scheduling information for the first D2R transmission;

[0276] Wherein, the first D2R transmission is the D2R transmission indicated or scheduled by the first R2D transmission.

[0277] Optionally, the quantity information of the first D2R transmission includes one of the following:

[0278] The number of first D2R transmissions;

[0279] The number of resources transmitted in the first D2R transmission.

[0280] Optionally, the number of resources in the first D2R transmission includes at least one of the following:

[0281] The amount of time-domain resources in the first D2R transmission;

[0282] The number of frequency domain resources in the first D2R transmission;

[0283] The amount of airspace resources transmitted in the first D2R transmission;

[0284] The number of code domain resources in the first D2R transmission.

[0285] Optionally, the scheduling information for the at least one first D2R transmission includes at least one of the following:

[0286] Multiplexing of at least two first D2R transmissions;

[0287] Common transmission parameters for at least two first D2R transmissions;

[0288] At least one dedicated transmission parameter for the first D2R transmission.

[0289] Optionally, the reuse method includes at least one of the following:

[0290] Time division multiplexing, frequency division multiplexing, code division multiplexing.

[0291] Optionally, the common transmission parameters include at least one of the following:

[0292] Information bit length, number of information bits, transport block size (TBS), chip length, retransmission type, number of retransmissions, indication information for adding cyclic redundancy check (CRC) information, number of CRC bits, indication information for using scrambling, indication information for using a mask, scrambling sequence information, and mask information.

[0293] Optionally, the dedicated transmission parameters include at least one of the following:

[0294] Start time, frequency domain resources, codeword information.

[0295] Optionally, the first R2D transmission includes at least one of the following:

[0296] The first indication information is used to indicate whether the first R2D transmission is the last first R2D transmission in this communication process, or the first indication information is used to indicate whether there are any subsequent first R2D transmissions after the first R2D transmission.

[0297] The second indication information is used to indicate the amount of response information carried in the first R2D transmission;

[0298] The third indication information is used to indicate whether the response information corresponding to the third indication information is the last response information in the first R2D transmission;

[0299] The fourth indication information is used to indicate whether the response information corresponding to the fourth indication information should schedule the first D2R transmission;

[0300] The fifth indication information is used to indicate whether the response information corresponding to the fifth indication information contains the scheduling information of the first D2R transmission;

[0301] The sixth indication information is used to indicate whether there are dedicated transmission parameters in the first R2D transmission. The dedicated transmission parameters are the dedicated transmission parameters of the first D2R of the IoT device that match the response information corresponding to the sixth indication information.

[0302] At least one first D2R scheduling information;

[0303] The response information is the response information to the second D2R in the first R2D transmission.

[0304] Optionally, at least one of the third indication information, the fourth indication information, the fifth indication information, the sixth indication information, and the scheduling information is located in the corresponding response information.

[0305] Optionally, the first R2D transmission includes a first information field, which includes scheduling information for the at least one first D2R.

[0306] Optionally, if the first R2D transmission does not indicate scheduling information for the target first D2R transmission, the IoT device uses at least one of the following scheduling information when sending the target first D2R transmission:

[0307] Refer to the scheduling information for D2R transmission;

[0308] The scheduling information defined by the protocol.

[0309] Optionally, the reference D2R transmission includes at least one of the following:

[0310] The most recent D2R transmission;

[0311] The most recent D2R transmission triggered or scheduled by the IoT device;

[0312] Msg1;

[0313] The D2R transmission was triggered or scheduled by the most recent command received by the IoT device, and the command carried unique identification information that identifies the IoT device.

[0314] Optionally, the scheduling information defined by the protocol includes:

[0315] The transmission time window defined by the protocol.

[0316] The aforementioned IoT information transmission device can enable IoT devices to save power.

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

[0318] Referring to Figure 17, when the IoT information transmission device is a component in an IoT device, the IoT information transmission device 1700 includes:

[0319] The sending module 1701 is configured to send a first R2D transmission to an IoT device, the first R2D transmission indicating at least one of the following:

[0320] The quantity information transmitted from the first device to the reader (D2R);

[0321] At least one scheduling information for the first D2R transmission;

[0322] Wherein, the first D2R transmission is the D2R transmission indicated or scheduled by the first R2D transmission.

[0323] Optionally, the quantity information of the first D2R transmission includes one of the following:

[0324] The number of first D2R transmissions;

[0325] The number of resources transmitted in the first D2R transmission.

[0326] Optionally, the number of resources in the first D2R transmission includes at least one of the following:

[0327] The amount of time-domain resources in the first D2R transmission;

[0328] The number of frequency domain resources in the first D2R transmission;

[0329] The amount of airspace resources transmitted in the first D2R transmission;

[0330] The number of code domain resources in the first D2R transmission.

[0331] Optionally, the scheduling information for the at least one first D2R transmission includes at least one of the following:

[0332] Multiplexing of at least two first D2R transmissions;

[0333] Common transmission parameters for at least two first D2R transmissions;

[0334] At least one dedicated transmission parameter for the first D2R transmission.

[0335] Optionally, the reuse method includes at least one of the following:

[0336] Time division multiplexing, frequency division multiplexing, code division multiplexing.

[0337] Optionally, the common transmission parameters include at least one of the following:

[0338] Information bit length, number of information bits, transport block size (TBS), chip length, retransmission type, number of retransmissions, indication information for adding cyclic redundancy check (CRC) information, number of CRC bits, indication information for using scrambling, indication information for using a mask, scrambling sequence information, and mask information.

[0339] Optionally, the dedicated transmission parameters include at least one of the following:

[0340] Start time, frequency domain resources, codeword information.

[0341] Optionally, the first R2D transmission includes at least one of the following:

[0342] The first indication information is used to indicate whether the first R2D transmission is the last first R2D transmission in this communication process, or the first indication information is used to indicate whether there are any subsequent first R2D transmissions after the first R2D transmission.

[0343] The second indication information is used to indicate the amount of response information carried in the first R2D transmission;

[0344] The third indication information is used to indicate whether the response information corresponding to the third indication information is the last response information in the first R2D transmission;

[0345] The fourth indication information is used to indicate whether the response information corresponding to the fourth indication information should schedule the first D2R transmission;

[0346] The fifth indication information is used to indicate whether the response information corresponding to the fifth indication information contains the scheduling information of the first D2R transmission;

[0347] The sixth indication information is used to indicate whether there are dedicated transmission parameters in the first R2D transmission. The dedicated transmission parameters are the dedicated transmission parameters of the first D2R of the IoT device that match the response information corresponding to the sixth indication information.

[0348] At least one first D2R scheduling information;

[0349] The response information is the response information to the second D2R in the first R2D transmission.

[0350] Optionally, at least one of the third indication information, the fourth indication information, the fifth indication information, the sixth indication information, and the scheduling information is located in the corresponding response information.

[0351] Optionally, the first R2D transmission includes a first information field, which includes scheduling information for the at least one first D2R.

[0352] The aforementioned IoT information transmission device can enable IoT devices to save power.

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

[0354] As shown in Figure 18, this application embodiment also provides a communication device 1800, including a processor 1801 and a memory 1802. The memory 1802 stores a program or instructions that can run on the processor 1801. For example, when the communication device 1800 is the communication device in the embodiment shown in Figure 3, the program or instructions, when executed by the processor 1801, implement the various steps of the above-described IoT information transmission method embodiment and achieve the same technical effect. When the communication device 1800 is an IoT device, the program or instructions, when executed by the processor 1801, implement the various steps of the above-described IoT information transmission method embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0355] It should be noted that Figure 18 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.

[0356] 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 FIG2. 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 IoT information transmission device shown in FIG16. Specifically, FIG19 is a schematic diagram of the hardware structure of a communication device implementing an embodiment of this application.

[0357] The communication device 1900 includes, but is not limited to, at least some of the following components: radio frequency unit 1901, network module 1902, audio output unit 1903, input unit 1904, sensor 1905, display unit 1906, user input unit 1907, interface unit 1908, memory 1909, and processor 1910.

[0358] Those skilled in the art will understand that the communication device 1900 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 1910 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The communication device structure shown in Figure 19 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.

[0359] It should be understood that, in this embodiment, the input unit 1904 may include a graphics processor 19041 and a microphone 19042. The graphics processor 19041 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 1906 may include a display panel 19061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1907 includes at least one of a touch panel 19071 and other input devices 19072. The touch panel 19071 is also called a touch screen. The touch panel 19071 may include a touch detection device and a touch controller. Other input devices 19072 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.

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

[0361] The memory 1909 can be used to store software programs or instructions, as well as various data. The memory 1909 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 1909 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 1909 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0362] Processor 1910 may include one or more processing units; optionally, processor 1910 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 1910.

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

[0364] The radio frequency unit 1901 is configured to receive a first R2D transmission, wherein the first R2D transmission is configured to indicate at least one of the following:

[0365] The quantity information transmitted from the first device to the reader (D2R);

[0366] At least one scheduling information for the first D2R transmission;

[0367] Wherein, the first D2R transmission is the D2R transmission indicated or scheduled by the first R2D transmission.

[0368] Optionally, the quantity information of the first D2R transmission includes one of the following:

[0369] The number of first D2R transmissions;

[0370] The number of resources transmitted in the first D2R transmission.

[0371] Optionally, the number of resources in the first D2R transmission includes at least one of the following:

[0372] The amount of time-domain resources in the first D2R transmission;

[0373] The number of frequency domain resources in the first D2R transmission;

[0374] The amount of airspace resources transmitted in the first D2R transmission;

[0375] The number of code domain resources in the first D2R transmission.

[0376] Optionally, the scheduling information for the at least one first D2R transmission includes at least one of the following:

[0377] Multiplexing of at least two first D2R transmissions;

[0378] Common transmission parameters for at least two first D2R transmissions;

[0379] At least one dedicated transmission parameter for the first D2R transmission.

[0380] Optionally, the reuse method includes at least one of the following:

[0381] Time division multiplexing, frequency division multiplexing, code division multiplexing.

[0382] Optionally, the common transmission parameters include at least one of the following:

[0383] Information bit length, number of information bits, transport block size (TBS), chip length, retransmission type, number of retransmissions, indication information for adding cyclic redundancy check (CRC) information, number of CRC bits, indication information for using scrambling, indication information for using a mask, scrambling sequence information, and mask information.

[0384] Optionally, the dedicated transmission parameters include at least one of the following:

[0385] Start time, frequency domain resources, codeword information.

[0386] Optionally, the first R2D transmission includes at least one of the following:

[0387] The first indication information is used to indicate whether the first R2D transmission is the last first R2D transmission in this communication process, or the first indication information is used to indicate whether there are any subsequent first R2D transmissions after the first R2D transmission.

[0388] The second indication information is used to indicate the amount of response information carried in the first R2D transmission;

[0389] The third indication information is used to indicate whether the response information corresponding to the third indication information is the last response information in the first R2D transmission;

[0390] The fourth indication information is used to indicate whether the response information corresponding to the fourth indication information should schedule the first D2R transmission;

[0391] The fifth indication information is used to indicate whether the response information corresponding to the fifth indication information contains the scheduling information of the first D2R transmission;

[0392] The sixth indication information is used to indicate whether there are dedicated transmission parameters in the first R2D transmission. The dedicated transmission parameters are the dedicated transmission parameters of the first D2R of the IoT device that match the response information corresponding to the sixth indication information.

[0393] At least one first D2R scheduling information;

[0394] The response information is the response information to the second D2R in the first R2D transmission.

[0395] Optionally, at least one of the third indication information, the fourth indication information, the fifth indication information, the sixth indication information, and the scheduling information is located in the corresponding response information.

[0396] Optionally, the first R2D transmission includes a first information field, which includes scheduling information for the at least one first D2R.

[0397] Optionally, if the first R2D transmission does not indicate scheduling information for the target first D2R transmission, the IoT device uses at least one of the following scheduling information when sending the target first D2R transmission:

[0398] Refer to the scheduling information for D2R transmission;

[0399] The scheduling information defined by the protocol.

[0400] Optionally, the reference D2R transmission includes at least one of the following:

[0401] The most recent D2R transmission;

[0402] The most recent D2R transmission triggered or scheduled by the IoT device;

[0403] Msg1;

[0404] The D2R transmission was triggered or scheduled by the most recent command received by the IoT device, and the command carried unique identification information that identifies the IoT device.

[0405] Optionally, the scheduling information defined by the protocol includes:

[0406] The transmission time window defined by the protocol.

[0407] The aforementioned communication equipment can enable IoT devices to save power.

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

[0409] It should be noted that the device shown in Figure 19 can also perform the method shown in Figure 9, i.e., the terminal acts as a reader.

[0410] 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 of the method embodiment shown in FIG9. This communication device embodiment corresponds to the above-described communication device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this communication device embodiment and can achieve the same technical effect.

[0411] Specifically, this application embodiment also provides a communication device, which can be the IoT information transmission device shown in FIG17. As shown in FIG20, the communication device 2000 includes: an antenna 2001, a radio frequency device 2002, a baseband device 2003, a processor 2004, and a memory 2005. The antenna 2001 is connected to the radio frequency device 2002. In the uplink direction, the radio frequency device 2002 receives information through the antenna 2001 and sends the received information to the baseband device 2003 for processing. In the downlink direction, the baseband device 2003 processes the information to be transmitted and sends it to the radio frequency device 2002, which processes the received information and then transmits it through the antenna 2001.

[0412] The method executed by the communication device in the above embodiments can be implemented in the baseband device 2003, which includes a baseband processor.

[0413] The baseband device 2003 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG20. One of the chips is, for example, a baseband processor, which is connected to the memory 2005 via a bus interface to call the program in the memory 2005 and execute the network device operation shown in the above method embodiment.

[0414] The communication device may also include a network interface 2006, such as a Common Public Radio Interface (CPRI).

[0415] Specifically, the communication device 2000 in this application embodiment further includes: instructions or programs stored in memory 2005 and executable on processor 2004. Processor 2004 calls the instructions or programs in memory 2005 to execute the methods executed by each module shown in FIG17 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0416] Radio frequency device 2002 is configured to transmit a first R2D transmission to an Internet of Things (IoT) device, the first R2D transmission being configured to indicate at least one of the following:

[0417] The quantity information transmitted from the first device to the reader (D2R);

[0418] At least one scheduling information for the first D2R transmission;

[0419] Wherein, the first D2R transmission is the D2R transmission indicated or scheduled by the first R2D transmission.

[0420] Optionally, the quantity information of the first D2R transmission includes one of the following:

[0421] The number of first D2R transmissions;

[0422] The number of resources transmitted in the first D2R transmission.

[0423] Optionally, the number of resources in the first D2R transmission includes at least one of the following:

[0424] The amount of time-domain resources in the first D2R transmission;

[0425] The number of frequency domain resources in the first D2R transmission;

[0426] The amount of airspace resources transmitted in the first D2R transmission;

[0427] The number of code domain resources in the first D2R transmission.

[0428] Optionally, the scheduling information for the at least one first D2R transmission includes at least one of the following:

[0429] Multiplexing of at least two first D2R transmissions;

[0430] Common transmission parameters for at least two first D2R transmissions;

[0431] At least one dedicated transmission parameter for the first D2R transmission.

[0432] Optionally, the reuse method includes at least one of the following:

[0433] Time division multiplexing, frequency division multiplexing, code division multiplexing.

[0434] Optionally, the common transmission parameters include at least one of the following:

[0435] Information bit length, number of information bits, transport block size (TBS), chip length, retransmission type, number of retransmissions, indication information for adding cyclic redundancy check (CRC) information, number of CRC bits, indication information for using scrambling, indication information for using a mask, scrambling sequence information, and mask information.

[0436] Optionally, the dedicated transmission parameters include at least one of the following:

[0437] Start time, frequency domain resources, codeword information.

[0438] Optionally, the first R2D transmission includes at least one of the following:

[0439] The first indication information is used to indicate whether the first R2D transmission is the last first R2D transmission in this communication process, or the first indication information is used to indicate whether there are any subsequent first R2D transmissions after the first R2D transmission.

[0440] The second indication information is used to indicate the amount of response information carried in the first R2D transmission;

[0441] The third indication information is used to indicate whether the response information corresponding to the third indication information is the last response information in the first R2D transmission;

[0442] The fourth indication information is used to indicate whether the response information corresponding to the fourth indication information should schedule the first D2R transmission;

[0443] The fifth indication information is used to indicate whether the response information corresponding to the fifth indication information contains the scheduling information of the first D2R transmission;

[0444] The sixth indication information is used to indicate whether there are dedicated transmission parameters in the first R2D transmission. The dedicated transmission parameters are the dedicated transmission parameters of the first D2R of the IoT device that match the response information corresponding to the sixth indication information.

[0445] At least one first D2R scheduling information;

[0446] The response information is the response information to the second D2R in the first R2D transmission.

[0447] Optionally, at least one of the third indication information, the fourth indication information, the fifth indication information, the sixth indication information, and the scheduling information is located in the corresponding response information.

[0448] Optionally, the first R2D transmission includes a first information field, which includes scheduling information for the at least one first D2R.

[0449] The aforementioned communication equipment can enable IoT devices to save power.

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

[0451] It should be noted that this embodiment uses a communication device as an example of a network-side device. In some embodiments, the above-mentioned communication device can also be a terminal, as shown in Figure 19. That is, the device shown in Figure 19 can also implement the technical solution provided in this embodiment.

[0452] 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 IoT information transmission method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

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

[0454] 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-described IoT information transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0456] 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 IoT information transmission method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0457] This application also provides a wireless communication system, including: an Internet of Things (IoT) device and a communication device. The IoT device can be used to execute the steps of the IoT information transmission method on the IoT device side as provided in this application, and the communication device can be used to execute the steps of the IoT information transmission method on the communication device side as provided in this application.

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

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

[0460] 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 method for information transmission of Internet of Things, comprising: receiving, by an Internet of Things device, a first Reader-to-Device (R2D) transmission, the first R2D transmission being used to indicate at least one of: number information of first Device-to-Reader (D2R) transmissions; scheduling information of at least one first D2R transmission; wherein the first D2R transmission is a D2R transmission indicated or scheduled by the first R2D transmission.

2. The method of claim 1, wherein, The number information of the first D2R transmission comprises one of: a number of the first D2R transmissions; a number of resources of the first D2R transmissions.

3. The method of claim 2, wherein, The number of resources of the first D2R transmissions comprises at least one of: a number of time domain resources of the first D2R transmissions; a number of frequency domain resources of the first D2R transmissions; a number of space domain resources of the first D2R transmissions; a number of code domain resources of the first D2R transmissions.

4. The method of any one of claims 1 to 3, wherein, The scheduling information of the at least one first D2R transmission comprises at least one of: a multiplexing manner of the at least two first D2R transmissions; common transmission parameters of the at least two first D2R transmissions; dedicated transmission parameters of the at least one first D2R transmission.

5. The method of claim 4, wherein, The multiplexing manner comprises at least one of: time division multiplexing, frequency division multiplexing, code division multiplexing.

6. The method of claim 4 or 5, wherein, The common transmission parameters comprise at least one of: information bit length, information bit number, Transport Block Size (TBS), chip length, repetition transmission type, repetition transmission number, indication information of whether to add Cyclic Redundancy Check (CRC) information, CRC bit number, indication information of whether to use scrambling, indication information of whether to use masking, scrambling sequence information, masking information.

7. The method of any one of claims 4 to 6, wherein, The dedicated transmission parameters comprise at least one of: start time, frequency domain resource, code word information.

8. The method of any one of claims 1 to 7, wherein, The first R2D transmission comprises at least one of: first indication information, the first indication information being used to indicate whether the first R2D transmission is the last first R2D transmission in a current communication process, or the first indication information being used to indicate whether there is a subsequent first R2D transmission after the first R2D transmission; second indication information, the second indication information being used to indicate a number of response information carried by the first R2D transmission; third indication information, the third indication information being used to indicate whether the response information corresponding to the third indication information is the last response information in the first R2D transmission; fourth indication information, the fourth indication information being used to indicate whether the response information corresponding to the fourth indication information schedules a first D2R transmission; fifth indication information, the fifth indication information being used to indicate whether the response information corresponding to the fifth indication information contains scheduling information of a first D2R transmission; sixth indication information, the sixth indication information being used to indicate whether there is a dedicated transmission parameter in the first R2D transmission, the dedicated transmission parameter being a dedicated transmission parameter of a first D2R of an Internet of Things device matched with the response information corresponding to the sixth indication information; scheduling information of at least one first D2R; wherein the response information is response information of a second D2R in the first R2D transmission.

9. The method of claim 8, wherein, At least one of the third indication information, the fourth indication information, the fifth indication information, the sixth indication information, and the scheduling information is located in the corresponding response information.

10. The method of any one of claims 1 to 8, wherein, The first R2D transmission comprises a first information field, and the first information field comprises scheduling information of the at least one first D2R.

11. The method of any one of claims 1 to 10, wherein, In a case where the first R2D transmission does not indicate the scheduling information of the target first D2R transmission, the at least one scheduling information used by the Internet of Things device when sending the target first D2R transmission comprises: Scheduling information of a reference D2R transmission; Protocol-defined scheduling information.

12. The method of claim 11, wherein, The reference D2R transmission comprises at least one of: A D2R transmission that is most recently sent; A D2R transmission that is most recently received by the Internet of Things device and triggered or scheduled by paging; A message Msg1; A D2R transmission that is most recently received by the Internet of Things device and triggered or scheduled by a command, and the command carries identification information uniquely identifying the Internet of Things device.

13. The method of claim 11 or 12, wherein, The protocol-defined scheduling information comprises: A protocol-defined transmission time window.

14. An Internet of Things information transmission method, comprising: A communication device sends a reader-to-device first R2D transmission to an Internet of Things device, and the first R2D transmission is used to indicate at least one of: Number information of first device-to-reader D2R transmissions; Scheduling information of at least one first D2R transmission; The first D2R transmission is a D2R transmission indicated or scheduled by the first R2D transmission.

15. The method of claim 14, wherein, The number information of the first D2R transmission comprises one of: A number of the first D2R transmissions; A resource number of the first D2R transmissions.

16. The method of claim 15, wherein, The resource number of the first D2R transmissions comprises at least one of: A time domain resource number of the first D2R transmissions; A frequency domain resource number of the first D2R transmissions; A space domain resource number of the first D2R transmissions; A code domain resource number of the first D2R transmissions.

17. The method of any one of claims 14 to 16, wherein, The scheduling information of the at least one first D2R transmission comprises at least one of: A multiplexing manner of at least two first D2R transmissions; Common transmission parameters of at least two first D2R transmissions; Dedicated transmission parameters of at least one first D2R transmission.

18. The method of claim 17, wherein, The multiplexing manner comprises at least one of: Time division multiplexing, frequency division multiplexing, and code division multiplexing.

19. The method of claim 17 or 18, wherein, The common transmission parameters comprise at least one of: Information bit length, information bit number, transport block size TBS, chip length, repetition transmission type, repetition transmission number, indication information of whether to add cyclic redundancy check CRC information, CRC bit number, indication information of whether to use scrambling, indication information of whether to use masking, scrambling sequence information, and masking information.

20. The method of any one of claims 17-19, wherein, The dedicated transmission parameters comprise at least one of: Starting time, frequency domain resource, and code word information.

21. The method of any one of claims 14 to 20, wherein, The first R2D transmission comprises at least one of: First indication information, the first indication information is used to indicate whether the first R2D transmission is the last first R2D transmission in the current communication process, or the first indication information is used to indicate whether there is a subsequent first R2D transmission after the first R2D transmission; second indication information, used for indicating a number of response information carried by the first R2D transmission; third indication information, used for indicating whether the response information corresponding to the third indication information is the last response information in the first R2D transmission; fourth indication information, used for indicating whether the response information corresponding to the fourth indication information schedules a first D2R transmission; fifth indication information, used for indicating whether the response information corresponding to the fifth indication information contains scheduling information of the first D2R transmission; sixth indication information, used for indicating whether there is a dedicated transmission parameter in the first R2D transmission, the dedicated transmission parameter being a dedicated transmission parameter of a first D2R of an Internet of Things device matched with the response information corresponding to the sixth indication information; scheduling information of at least one first D2R; wherein the response information is response information to a second D2R in the first R2D transmission.

22. The method of claim 21, wherein, At least one of the third indication information, the fourth indication information, the fifth indication information, the sixth indication information and the scheduling information is located in the corresponding response information.

23. The method of claim 21, wherein, The first R2D transmission includes a first information field, and the first information field includes the scheduling information of the at least one first D2R.

24. An Internet of Things information transmission device, comprising: a receiving module, configured to receive a first reader-to-device (R2D) transmission, wherein the first R2D transmission is used to indicate at least one of the following: number information of a first device-to-reader (D2R) transmission; scheduling information of at least one first D2R transmission; wherein the first D2R transmission is a D2R transmission indicated or scheduled by the first R2D transmission.

25. The apparatus of claim 24, wherein, The first R2D transmission includes at least one of the following: first indication information, used for indicating whether the first R2D transmission is the last first R2D transmission in the current communication process, or used for indicating whether there is a subsequent first R2D transmission after the first R2D transmission; second indication information, used for indicating a number of response information carried by the first R2D transmission; third indication information, used for indicating whether the response information corresponding to the third indication information is the last response information in the first R2D transmission; fourth indication information, used for indicating whether the response information corresponding to the fourth indication information schedules a first D2R transmission; fifth indication information, used for indicating whether the response information corresponding to the fifth indication information contains scheduling information of the first D2R transmission; sixth indication information, used for indicating whether there is a dedicated transmission parameter in the first R2D transmission, the dedicated transmission parameter being a dedicated transmission parameter of a first D2R of an Internet of Things device matched with the response information corresponding to the sixth indication information; scheduling information of at least one first D2R; wherein the response information is response information to a second D2R in the first R2D transmission.

26. The apparatus of claim 24 or 25, wherein, In a case that the first R2D transmission does not indicate the scheduling information of the target first D2R transmission, the IoT device adopts at least one of the following scheduling information when sending the target first D2R transmission: scheduling information of a reference D2R transmission; protocol-defined scheduling information. 27.An IoT information transmission apparatus, comprising: a sending module configured to send a first reader-to-device (R2D) transmission to an IoT device, wherein the first R2D transmission is used to indicate at least one of the following: number information of first device-to-reader (D2R) transmissions; scheduling information of at least one first D2R transmission; wherein the first D2R transmission is a D2R transmission indicated or scheduled by the first R2D transmission.

28. The apparatus of claim 27, wherein, The first R2D transmission comprises at least one of the following: first indication information, used to indicate whether the first R2D transmission is the last first R2D transmission in the current communication process, or whether there is a subsequent first R2D transmission after the first R2D transmission; second indication information, used to indicate the number of response information carried by the first R2D transmission; third indication information, used to indicate whether the response information corresponding to the third indication information is the last response information in the first R2D transmission; fourth indication information, used to indicate whether the response information corresponding to the fourth indication information schedules a first D2R transmission; fifth indication information, used to indicate whether the response information corresponding to the fifth indication information contains scheduling information of a first D2R transmission; sixth indication information, used to indicate whether there is a dedicated transmission parameter in the first R2D transmission, wherein the dedicated transmission parameter is a dedicated transmission parameter of a first D2R of an IoT device matched with the response information corresponding to the sixth indication information; scheduling information of at least one first D2R; wherein the response information is response information of a second D2R in the first R2D transmission. 29.A communication device, comprising a processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions, when executed by the processor, implement the steps of the IoT information transmission method according to any one of claims 1 to 13, or the programs or instructions, when executed by the processor, implement the steps of the IoT information transmission method according to any one of claims 14 to 23. 30.A readable storage medium, wherein the readable storage medium stores programs or instructions, and the programs or instructions, when executed by a processor, implement the steps of the IoT information transmission method according to any one of claims 1 to 13, or implement the steps of the IoT information transmission method according to any one of claims 14 to 23.

31. 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 method for information transmission of Internet of Things according to any one of claims 1 to 13, or to implement the steps of the method for information transmission of Internet of Things according to any one of claims 14 to 23.

Images