Internet-of-things communication method and apparatus, and device
By determining transmission resources through communication equipment, IoT devices can perform non-contention transmission on the determined resources, which solves the problem of low communication efficiency of IoT devices and achieves more efficient communication.
Patent Information
- Application Number
- PCT/CN2025/100200
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-06-17
- Filing Date
- 2025-06-10
- Publication Date
- 2025-12-26
AI Technical Summary
The low communication efficiency between IoT devices is mainly due to intense competition for transmission resources caused by competing for access.
Communication devices determine transmission resources by sending a first message, and IoT devices send a second message on the determined transmission resources based on the first message, thus achieving non-contention transmission.
It improves communication efficiency between IoT devices, reduces latency overhead, and simplifies network complexity.
Smart Images

Figure CN2025100200_26122025_PF_FP_ABST
Abstract
Description
Internet of Things (IoT) communication methods, devices and equipment
[0001] This application claims priority to Chinese patent application filed on June 17, 2024, with application number 202410777174.2 and entitled "Internet of Things Communication Method, Apparatus and Device", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application belongs to the field of communication technology, specifically relating to an Internet of Things (IoT) communication method, apparatus, and device. Background Technology
[0003] In some related technologies, IoT devices communicate with other devices using a contention-based access method. For example, all communication between an Ambient Internet of Things (AIoT) device and a reader is transmitted through a contention-based access process. This contention-based access involves competition for transmission resources, resulting in relatively low communication efficiency. Summary of the Invention
[0004] This application provides an Internet of Things (IoT) communication method, apparatus, and device that can solve the problem of low communication efficiency.
[0005] Firstly, an Internet of Things (IoT) communication method is provided, including:
[0006] The communication device sends a first message, which is used to determine transmission resources;
[0007] The communication device receives a second message sent by an IoT device through the transmission resources.
[0008] Secondly, an Internet of Things (IoT) communication method is provided, including:
[0009] The Internet of Things (IoT) device receives a first message sent by the communication device, the first message being used to determine transmission resources;
[0010] The IoT device sends a second message to the communication device through the transmission resources.
[0011] Thirdly, an Internet of Things (IoT) communication device is provided, comprising:
[0012] A sending module is used to send a first message, which is used to determine transmission resources;
[0013] The receiving module is used to receive a second message sent by an IoT device through the transmission resource.
[0014] Fourthly, an Internet of Things (IoT) communication device is provided, comprising:
[0015] The receiving module is used to receive a first message sent by the communication device, wherein the first message is used to determine transmission resources;
[0016] The sending module is used to send a second message to the communication device through the transmission resources.
[0017] Fifthly, an Internet of Things (IoT) communication device is provided, the device being configured to perform the steps of the IoT communication method on the communication device side as provided in the embodiments of this application.
[0018] In a sixth aspect, an Internet of Things (IoT) communication device is provided, the device being configured to perform the steps of the IoT device-side IoT communication method as provided in the embodiments of this application.
[0019] In a seventh aspect, an apparatus is provided, the apparatus including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the Internet of Things communication method on the communication device side as provided in the embodiments of this application.
[0020] Eighthly, a device is provided, including a processor and a communication interface, wherein the communication interface is used to send a first message, the first message being used to determine transmission resources; and to receive a second message sent by an Internet of Things (IoT) device through the transmission resources.
[0021] In a ninth aspect, an apparatus is provided, the apparatus including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the IoT device-side IoT communication method as provided in the embodiments of this application.
[0022] In a tenth aspect, a device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a first message sent by a communication device, the first message being configured to determine transmission resources; and to send a second message to the communication device through the transmission resources.
[0023] Eleventhly, 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 communication method on the communication device side as provided in the embodiments of this application, or implement the steps of the IoT communication method on the IoT device side as provided in the embodiments of this application.
[0024] In a twelfth aspect, a wireless communication system is provided, comprising: a communication device and an Internet of Things (IoT) device, wherein the communication device can be used to perform the steps of the IoT communication method on the communication device side as provided in the embodiments of this application, and the network-side device can be used to perform the steps of the IoT communication method on the IoT device side as provided in the embodiments of this application.
[0025] 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 communication method on the communication device side as provided in the embodiments of this application, or to implement the IoT communication method on the IoT device side as provided in the embodiments of this application.
[0026] 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 communication method on the communication 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 communication method on the IoT device side as provided in the embodiments of this application.
[0027] In this embodiment, a communication device sends a first message to determine transmission resources; the communication device then receives a second message sent by an IoT device using those transmission resources. Since the communication device receives the second message sent by the IoT device using the transmission resources determined by the first message, the transmission resources for transmitting the second message are determined based on the first message. This achieves non-competitive transmission between the communication device and the IoT device, thereby improving communication efficiency. Attached Figure Description
[0028] Figure 1 is a schematic diagram of a system provided in an embodiment of this application;
[0029] Figure 2 is an instruction diagram of a reader and a tag provided in an embodiment of this application;
[0030] Figure 3 is a flowchart of an IoT communication method provided in an embodiment of this application;
[0031] Figure 4 is a flowchart of another IoT communication method provided in an embodiment of this application;
[0032] Figure 5 is a schematic diagram of an Internet of Things (IoT) communication provided in an embodiment of this application;
[0033] Figure 6 is a schematic diagram of another IoT communication provided in an embodiment of this application;
[0034] Figure 7 is a schematic diagram of another IoT communication provided in an embodiment of this application;
[0035] Figure 8 is a schematic diagram of another IoT communication provided in an embodiment of this application;
[0036] Figure 9 is a structural diagram of an Internet of Things (IoT) communication device provided in an embodiment of this application;
[0037] Figure 10 is a structural diagram of an Internet of Things (IoT) communication device provided in an embodiment of this application;
[0038] Figure 11 is a structural diagram of a communication device provided in an embodiment of this application;
[0039] Figure 12 is a structural diagram of a terminal provided in an embodiment of this application;
[0040] Figure 13 is a structural diagram of a network-side device provided in an embodiment of this application. Detailed Implementation
[0041] 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] Figure 1 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. The 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), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, 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 (AIoT) 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 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, radio access network unit, or satellite. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (Wi-Fi) 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.
[0046] 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.
[0047] 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).
[0048] AIoT, also known as Ambient Power-Enabled Internet of Things (Ambient Power-Enabled IoT), is a type of IoT business 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.
[0049] 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 AIoT, passive IoT devices, or response devices.
[0050] 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.
[0051] In some embodiments, AIoT devices can be classified based on factors such as energy source, energy storage capacity, and whether they are passive or active transmitters, and can be categorized into the following device types:
[0052] Device Type A: This is a passive device, which has no energy storage and no independent signal generation / amplification, i.e., backscatter transmission;
[0053] 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.
[0054] Device type C: Active Device, which has energy storage and independent signal generation, i.e., an active radio frequency component used for transmission.
[0055] In some embodiments, the AIoT device may be a tag or other low-power IoT device.
[0056] In some embodiments, a non-tag terminal or network-side device can act as a tag reader, which can be an RFID tag.
[0057] In some embodiments, the information transmission between the reader and the tag can be as shown in Figure 2, and the reader operation instructions can be as shown in Table 1:
[0058] Table 1:
[0059] In some embodiments, the status of the label is as shown in Table 2:
[0060] Table 2:
[0061] It should be noted that Tables 1 and 2 above are only examples of information transmission between the reader and the tag. In this embodiment of the application, no specific limitations are made on the information transmission between the reader and the tag.
[0062] The IoT communication methods, apparatus, and devices provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.
[0063] Please refer to Figure 3, which is a flowchart of an IoT communication method provided in an embodiment of this application. As shown in Figure 3, it includes the following steps:
[0064] Step 301: The communication device sends a first message, which is used to determine the transmission resources.
[0065] The aforementioned communication equipment can be a network-side device or terminal, or a reader for AIoT devices.
[0066] Sending the first message can be done by sending the first message to one or more IoT devices, which can be AIoT devices or other IoT devices.
[0067] The first message used to determine the transmission resource may indicate the transmission resource, specifically, it may be an explicit or implicit indication of the transmission resource; or the first message may be associated with the transmission resource, thereby allowing the transmission resource to be determined through the first message.
[0068] Step 302: The communication device receives a second message sent by the IoT device through the transmission resources.
[0069] The above-mentioned communication device receiving the second message sent by the IoT device through the transmission resource can be understood as follows: after receiving the first message, the IoT device determines the transmission resource based on the first message and sends the second message to the communication device through the transmission resource.
[0070] When the first message is sent to multiple IoT devices, the transmission resources can include the transmission resources corresponding to each of these IoT devices, so that each IoT device can use its own corresponding transmission resources to send the second message to the communication device.
[0071] The second message can carry the communication content between the IoT device and the communication device, so as to realize the transmission of communication content between the IoT device and the communication device through the transmission resources; the second message can also carry information such as the identification information of the IoT device, so as to realize the inventory of the IoT device.
[0072] In some implementations, the aforementioned IoT device may be an IoT device specified by the aforementioned communication equipment, or an IoT device specified by the core network equipment, or an IoT device specified by the server; specifically, it may be a particular IoT device.
[0073] In this embodiment of the application, since the communication device receives the second message sent by the IoT device through the transmission resources determined by the first message, that is, the transmission resources for transmitting the second message are determined based on the first message, the communication device and the IoT device can perform non-competitive transmission, thereby improving communication efficiency.
[0074] In this embodiment, since the transmission resources are determined by the first message sent by the communication device, IoT devices can perform non-contention-based access and transmission under the control of the communication device, improving communication efficiency and reducing latency overhead. This reduces network complexity and overhead while ensuring transmission performance, and improves the efficiency of the communication system. For example, for AIoT devices, non-contention-based access and transmission can be achieved under the control of the reader, ensuring communication efficiency and low latency performance.
[0075] As an optional implementation, the first message includes at least one of the following:
[0076] Paging messages, downlink (DL) messages, and reader-to-device (R2D) messages.
[0077] The above paging message can be understood as a message during the paging process, such as message (Message, Msg)0.
[0078] The aforementioned DL message can also be called DL signaling, and the aforementioned R2D message can also be called R2D signaling.
[0079] This implementation can support multiple message determination transmission resources to meet the needs of different scenarios or services.
[0080] As an optional implementation, the first message includes at least one of the following:
[0081] First high-layer signaling, at least one device identifier, indication information of the transmission resource, transmission indication information, and a temporary identifier effective within the scope of the communication device;
[0082] The IoT device belongs to the IoT device corresponding to the at least one device identifier, the transmission indication information is used to indicate the transmission behavior between the IoT device and the communication device, and the temporary identifier includes the temporary identifier of the IoT device corresponding to the at least one device identifier.
[0083] The aforementioned first-level signaling can be inventory signaling or other specific commands, such as Read, Write, Kill, etc.
[0084] The aforementioned first-layer signaling can be used to control the IoT devices, thereby improving the control effect of the IoT devices.
[0085] In some implementations, the first message described above may not include the first higher-layer signaling.
[0086] The above-mentioned IoT devices belonging to the IoT devices corresponding to the at least one device identifier can be understood as the IoT devices in step 302 being the IoT devices corresponding to the at least one device identifier.
[0087] The aforementioned device identifier can be the identifier of a single IoT device or the identifier of a group of IoT devices. Furthermore, the device identifier can be temporary or permanent; specifically, it can be a temporary unique identifier within the network of a network-side device, a temporary unique identifier assigned to a server within a certain range, or a globally unique identifier for the device.
[0088] In some implementations, the device identifier in this application embodiment may include at least one of the following:
[0089] Device identifiers, device group identifiers, and device characteristic information are used to identify individual devices.
[0090] The device identifier used to identify a single device can be understood as one identifier being specific to only one IoT device.
[0091] The aforementioned device group identifier is used to identify groups of IoT devices. When the device group identifier is a temporary identifier assigned to a group of IoT devices by a network-side device or server, it can have the same or similar format as the temporary identifier assigned to an individual IoT device, such as the same number of bits. However, it is necessary to clearly distinguish that the value range of the device group identifier is different from the value range of the temporary identifier for an individual IoT device, or to carry a displayed group identifier indication / individual device identifier indication, etc., to facilitate communication devices in determining whether it is targeting a single specific device, rather than a group of devices.
[0092] The aforementioned device group identifiers can save message overhead.
[0093] The aforementioned device feature information is used to represent the characteristics of IoT devices. This allows device identification to be achieved through device feature information. If the total number of devices that match the device feature information is determined or known (e.g., informed to the reader by the network-side device or server) and / or the order of devices that match the device feature information is determined or known, then the communication device can be identified as the specified IoT device.
[0094] The aforementioned device characteristic information enables non-contention communication between IoT devices and those with specified device characteristics, thereby improving the flexibility of the communication system.
[0095] In some implementations, the device identifier includes:
[0096] The communication device receives the device identifier from the network-side device or the server.
[0097] The device identifier received by the aforementioned communication device from the network-side device or server may be a message containing at least one of the aforementioned device identifiers sent by the network-side device or server before the communication device sends the aforementioned first message, thereby enabling the IoT device communicating with the aforementioned communication device to be the IoT device specified by the network-side device or server.
[0098] This allows the IoT devices that can communicate with the communication equipment without contention to be designated by the aforementioned network-side devices or servers, thereby enabling non-contention communication for designated IoT devices and improving communication flexibility.
[0099] Furthermore, the aforementioned network-side devices can be core network devices or wireless access network devices. For core network devices, they can initiate Inventory or Command procedures for one or more specific IoT devices. Communication devices (such as Readers) send Paging messages or other R2D / DL messages to the specific IoT devices. These messages can carry the IoT device's device identifier, dedicated resources allocated to the IoT device, temporary identifiers, and instructions for subsequent steps. The designated IoT device then responds on its dedicated resources, sends messages to higher layers, and performs subsequent communication according to the instructions from the communication device.
[0100] In some implementations, the first message does not include at least one device identifier. For example, in some scenarios, the communication device may send the first message only to a designated IoT device.
[0101] The aforementioned transmission resource indication information is used to indicate the aforementioned transmission resources. In the case of multiple IoT devices, the aforementioned indication information can indicate the dedicated resources of each IoT device, or multiple IoT devices can select their respective dedicated resources from multiple transmission resources according to preset rules.
[0102] The aforementioned transmission resource indication information allows for a simple and direct determination of the dedicated resources for each IoT device, thereby improving the accuracy of communication.
[0103] In some implementations, when the first message does not include the indication information of the transmission resources, the transmission resources may be implicitly indicated by the first message. For example, the first message may implicitly indicate n time slots or n symbols between the first messages as the transmission resources, or implicitly indicate time-domain or frequency-domain resources adjacent to the first message as the transmission resources.
[0104] The temporary identifier that is effective within the scope of the aforementioned communication device can be understood as being effective only within the scope of the aforementioned communication device. For example, the aforementioned temporary identifier is assigned a value to the aforementioned communication device, such as the Reader Radio Network Temporary Identity (R-RNTI).
[0105] The aforementioned temporary identifier, including the temporary identifier of the IoT device corresponding to the at least one device identifier, can be understood as the aforementioned first message including the temporary identifier of the IoT device corresponding to the at least one device identifier. However, if the aforementioned first message does not include the at least one device identifier, it may still include the aforementioned temporary identifier. For example, if the IoT device corresponding to the at least one device identifier is a pre-specified or default IoT device, then the aforementioned first message includes the temporary identifier of the pre-specified or default IoT device.
[0106] Since the first message includes the temporary identifier, the communication device can schedule or identify the IoT device based on the temporary identifier during subsequent communication, thereby avoiding the easy leakage of the IoT device identifier due to the subsequent use of the device identifier for scheduling or identification, and thus improving communication security.
[0107] In some implementations, the first message may not include the temporary identifier. For example, in some scenarios, the device identifier may be used directly for scheduling or identification in subsequent scheduling or identification processes.
[0108] The transmission behavior between the IoT device and the communication device indicated by the above transmission indication information may include any transmission behavior between the communication device and the IoT device from the start to the end of communication, such as: indicating the transmission resources of the first message, or indicating the transmission resources of the second message, or indicating the content transmitted by the IoT device to the communication device, or indicating the content transmitted by the communication device to the IoT device, etc.
[0109] Since the first message includes the aforementioned transmission instruction information, it can clearly indicate the transmission behavior between the IoT device and the communication device to the IoT device, so that the communication device can control and select the communication process between the IoT device and the communication device, thereby improving the transmission reliability between the IoT device and the communication device.
[0110] In some implementations, the transmission indication information is used to indicate one of the following transmission behaviors between the IoT device and the communication device:
[0111] Send a random number to the communication device;
[0112] Do not send random numbers to the communication device;
[0113] The communication device sends the temporary identifier to the Internet of Things device;
[0114] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0115] The above random number is a random number generated by the IoT device. For example, the above random number can be a random number (RN)16, or other random numbers, such as random numbers with fewer or more than 16 bits.
[0116] Since the random number is used to schedule and identify the IoT device, the communication device can schedule or identify the IoT device based on the random number in subsequent communication processes. This avoids the easy leakage of the IoT device's device identifier due to the subsequent use of the device identifier for scheduling or identification, thereby improving communication security.
[0117] In the absence of sending random numbers to the communication device, the aforementioned temporary identifier can be used for subsequent scheduling or identification.
[0118] The aforementioned communication device may send the temporary identifier to the IoT device during the aforementioned first message.
[0119] In this embodiment, since the above-mentioned transmission behavior is indicated, the IoT device can communicate using the indicated transmission behavior, thereby improving the transmission reliability between the IoT device and the communication device.
[0120] In some implementations, when sending a random number to the communication device:
[0121] The second message includes the random number, as well as at least one of the identification information of the IoT device and first high-level data;
[0122] Alternatively, the second message may include a random number, and at least one of the IoT device's identification information and first high-level data may be sent to the communication device via a message other than the second message.
[0123] The identification information of the Internet of Things mentioned above can be a globally unique identifier or a high-level identifier, such as an Electronic Product Code (EPC), and can be an identifier configured by core network equipment or servers, such as the device identifier described in the above embodiments.
[0124] The aforementioned first high-level data can be high-level data that IoT devices need to send to communication devices, such as high-level data in response to the first high-level signaling of IoT devices.
[0125] In this embodiment, at least one of the following can be transmitted via the second message: a random number, the identification information of the IoT device, and the first high-level data, thereby saving transmission overhead.
[0126] The message other than the second message mentioned above can be the fourth message described in the following implementation.
[0127] In the above embodiments, since at least one of the above-mentioned random number, IoT device identification information and first high-level data is transmitted through different messages, it is possible to transmit the IoT device identification information and first high-level data after the random number is successfully transmitted, thereby improving the transmission reliability of the IoT device identification information and first high-level data.
[0128] It should be noted that in some implementations, the first message may not include the transmission indication information, such as the transmission behavior between the IoT device and the communication device as agreed upon or pre-configured by the protocol.
[0129] As an optional implementation, the transmission resources include at least one of the following:
[0130] The default transport resource associated with the first message, and the transport resource indicated by the first message.
[0131] The aforementioned associated default transmission resources can be determined based on preset rules or protocols, such as time-domain or frequency-domain resources adjacent to the first message, or fixed-size transmission resources spaced n time slots or symbols away from the first message. Using these default transmission resources associated with the first message can save on transmission overhead.
[0132] The transmission resource indicated by the first message can be a transmission resource explicitly or implicitly indicated by the first message.
[0133] The transmission resources indicated by the first message above allow for more flexible resource configuration for IoT devices.
[0134] As an optional implementation, the communication device sends a first message, including:
[0135] The communication device sends the first message to N Internet of Things devices;
[0136] The transmission resources include N transmission resources, each of which is a dedicated transmission resource for the N IoT devices, where N is a positive integer.
[0137] The aforementioned N IoT devices can be one or more IoT devices.
[0138] For multiple IoT devices, the dedicated transmission resources for each IoT device can be as indicated by the first message mentioned above, or the multiple IoT devices can determine their respective transmission resources based on preset rules or protocol agreements. For example, N transmission resources can be determined according to the order of the IoT devices to determine their respective dedicated transmission resources.
[0139] In this implementation, each IoT device is configured with its own dedicated transmission resources to avoid transmission conflicts between IoT devices and improve transmission reliability.
[0140] As an optional implementation, the second message includes at least one of the following:
[0141] The identification information, first high-level data, and random number of the IoT device;
[0142] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0143] The identification information, first high-level data, and random number mentioned above are described in the corresponding descriptions of the above implementation methods, and will not be repeated here.
[0144] In this embodiment, at least one of the identification information, first high-layer data, and random number of the IoT device can be transmitted using the aforementioned transmission resources, thereby improving the transmission efficiency and reliability of at least one of the identification information, first high-layer data, and random number of the IoT device.
[0145] In some embodiments, after the communication device receives the second message sent by the IoT device through the transmission resource, the method further includes:
[0146] The communication device sends a third message to the IoT device, the third message including at least one of the following:
[0147] The confirmation information of the random number and the second higher-level signaling.
[0148] The confirmation information for the above random number can be an acknowledgment (ACK) of the random number.
[0149] The aforementioned second layer signaling can be signaling other than the aforementioned first layer signaling, such as Write, Lock, etc.
[0150] Sending confirmation of the random number can notify the IoT device that the random number was successfully sent, thereby improving the transmission reliability between the IoT device and the communication device.
[0151] Sending the aforementioned second-layer signaling enables greater control over IoT devices, thereby improving the effectiveness of IoT device control.
[0152] It should be noted that in some implementations, the confirmation of the random number may not be sent, such as by implicitly indicating successful transmission of the random number through the second higher-layer signaling. Alternatively, in some implementations, the IoT device assumes successful transmission of the second message after sending the second message.
[0153] In some implementations, the third message includes confirmation information for the random number, and after the communication device sends the third message to the IoT device, the method further includes:
[0154] The communication device receives a fourth message sent by the IoT device, the fourth message including at least one of the following:
[0155] The identification information of the IoT device and the second high-level data.
[0156] The aforementioned second high-level data may be high-level data other than the aforementioned first high-level data, or high-level data that is the same as the aforementioned first high-level data.
[0157] In this implementation, the identification information and high-level data of the IoT device can be sent after receiving the third message, thereby improving the transmission reliability of the identification information and high-level data of the IoT device. For example, the identification information and high-level data of the IoT device can be sent after receiving the confirmation information of the random number.
[0158] As an optional implementation, before the communication device sends the first message, the method further includes:
[0159] The communication device receives a fifth message sent by a network-side device or a server, the fifth message including at least one of the following:
[0160] Third-layer signaling, at least one device identifier;
[0161] The IoT device belongs to the IoT device corresponding to the at least one device identifier.
[0162] The aforementioned network-side equipment can be core network equipment.
[0163] The aforementioned third-layer signaling can be inventory signaling or other commands, such as Read, Write, Kill, etc. Furthermore, the aforementioned third-layer signaling can include the aforementioned first-layer signaling or the aforementioned second-layer signaling.
[0164] The fifth message mentioned above can represent a communication request for an IoT device corresponding to at least one of the above device identifiers. When a communication device receives a communication request for one or more specified IoT devices from a network-side device or server, such as receiving an inventory or various command requests, the communication device identifies the corresponding IoT device based on the above device identifier and communicates with these IoT devices.
[0165] In this implementation, the aforementioned IoT devices can be designated by the network-side device or server, and communication between the IoT devices and the communication devices can be triggered by the network-side device or server, thereby improving the flexibility of controlling or managing IoT devices. Specifically, when the network-side device or server designates one or more IoT devices to initiate an inventory or command, high-level data transmission between the communication devices and the IoT devices can be completed through non-competitive resources. This ensures the success rate of communication, reduces signaling overhead and processing complexity on the network side, and improves the overall network efficiency, capacity, and coverage.
[0166] In this embodiment, a communication device sends a first message to determine transmission resources; the communication device then receives a second message sent by an IoT device using those transmission resources. Since the communication device receives the second message sent by the IoT device using the transmission resources determined by the first message, the transmission resources for transmitting the second message are determined based on the first message. This achieves non-competitive transmission between the communication device and the IoT device, thereby improving communication efficiency.
[0167] Please refer to Figure 4, which is a flowchart of another IoT communication method provided in an embodiment of this application. As shown in Figure 4, it includes the following steps:
[0168] Step 401: The IoT device receives a first message sent by the communication device, the first message being used to determine transmission resources;
[0169] Step 402: The IoT device sends a second message to the communication device through the transmission resources.
[0170] Optionally, the first message includes at least one of the following:
[0171] Paging messages, downlink messages, and reader-to-device R2D messages.
[0172] Optionally, the first message includes at least one of the following:
[0173] First high-layer signaling, at least one device identifier, indication information of the transmission resource, transmission indication information, and a temporary identifier effective within the scope of the communication device;
[0174] The IoT device belongs to the IoT device corresponding to the at least one device identifier, the transmission indication information is used to indicate the transmission behavior between the IoT device and the communication device, and the temporary identifier includes the temporary identifier of the IoT device corresponding to the at least one device identifier.
[0175] Optionally, the device identifier includes at least one of the following:
[0176] The communication device receives the device identifier from the network-side device or the server.
[0177] Optionally, the transmission indication information is used to indicate one of the following transmission behaviors between the IoT device and the communication device:
[0178] Send a random number to the communication device;
[0179] Do not send random numbers to the communication device;
[0180] The communication device sends the temporary identifier to the Internet of Things device;
[0181] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0182] Optionally, when sending a random number to the communication device:
[0183] The second message includes the random number, as well as at least one of the identification information of the IoT device and first high-level data;
[0184] Alternatively, the second message may include a random number, and at least one of the IoT device's identification information and first high-level data may be sent to the communication device via a message other than the second message.
[0185] Optionally, the transmission resources include at least one of the following:
[0186] The default transport resource associated with the first message, and the transport resource indicated by the first message.
[0187] Optionally, the transmission resources include: N transmission resources, each of which is a dedicated transmission resource for the N IoT devices, where N is a positive integer;
[0188] The IoT device sends a second message to the communication device through the transmission resources, including:
[0189] The IoT device sends a second message to the communication device through its dedicated transmission resources.
[0190] Optionally, the second message includes at least one of the following:
[0191] The identification information, first high-level data, and random number of the IoT device;
[0192] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0193] Optionally, after the IoT device sends a second message to the communication device through the transmission resources, the method further includes:
[0194] The IoT device receives a third message sent by the communication device, the third message including at least one of the following:
[0195] The confirmation information of the random number and the second higher-level signaling.
[0196] Optionally, the third message includes confirmation information for the random number. After the IoT device receives the third message sent by the communication device, the method further includes:
[0197] The fourth message sent by the IoT device to the communication device includes at least one of the following:
[0198] The identification information of the IoT device and the second high-level data.
[0199] It should be noted that this embodiment is an implementation method of the Internet of Things device corresponding to the embodiment shown in Figure 3. For the specific implementation method, please refer to the relevant description of the embodiment shown in Figure 3. In order to avoid repeated description, this embodiment will not be repeated.
[0200] The following examples, using a communication device as a reader and an IoT device as an AIoT device, illustrate the methods provided in this application through multiple embodiments:
[0201] Example 1:
[0202] This embodiment provides an overall description of the Reader's control mechanism, specifically outlining the overall framework of the solution and emphasizing the Reader's complete control over subsequent detailed processing.
[0203] Firstly, in this embodiment, the goal of communication is for the network-side device or server to complete Inventory or Command communication processes with one or more designated AIoT devices. Inventory generally refers to the inventory process. Upon receiving Inventory information, the AIoT device needs to report specified information, such as its device identifier and EPC ID, so that the network side can obtain information such as the number, attributes, and location of the devices. Commands typically include instructions such as Read, Write, and Kill, requiring the device to read or write specific content, or to perform removal operations on the device. These Commands generally require a response or confirmation from the device.
[0204] When a network-side device or server initiates an Inventory or Command procedure for one or more AIoT devices as needed, it sends the signaling details to the Reader via the core network interface or server interface. This includes, for example, Inventory or Command / Read / Write / Kill instructions, along with the device identifiers of one or more corresponding devices. The device identifier can be a temporary, unique identifier assigned to the device by the network-side device or server within a certain range, or it can be a globally unique identifier for the device. However, due to security and privacy concerns, the former is more suitable for plaintext transmission, while the latter requires secure transmission methods.
[0205] Next, the Reader receives signaling from the network-side device or server (i.e., the fifth message in the above embodiment), and determines from the device identification information that this is a communication request for one or more specified AIoT devices. The method of determining based on the device identification information can be at least one of the following:
[0206] A device identifier is one or more identifiers that are specific to a single device. It can be in any form, such as a temporary identifier or a permanent identifier, but each identifier is only for one specific device.
[0207] The device identifier needs to be identified as a group identifier. When the group identifier is a temporary identifier assigned to a group of devices by a network-side device or server, the group identifier may have the same or similar format as the temporary identifier assigned to a single device; for example, the same number of bits. However, it is necessary to clearly distinguish that the value range of the group identifier is different from the value range of the temporary identifier of a single device, or to carry a display of group identifier indication / single device identifier indication, etc., so that the Reader can determine that it is for a single specific device, rather than a group of devices.
[0208] If the device identifier is clearly a group identifier, and the group member information of the group identifier is relatively clear (e.g., the network-side device or server informs the Reader), such as the total number of devices in the group corresponding to the group identifier, and the order of each device in the group is predefined or preconfigured. For example, if the group has 10 devices, and the order of the devices in the group is 0-9, each corresponding to a specific 10 devices, then the Reader also clearly knows the number of devices and the specific correspondence of each device. This can also be used to determine one or more specified devices.
[0209] If the device identifier is a group identifier and the information of the group members is uncertain, such as not knowing the total number of devices in the group or the order of the devices in the group, then it cannot be identified as a specified AIoT device. In this case, the reader can use other methods to identify the specified AIoT device.
[0210] Device characteristic information: If the device identifier is given by device characteristic information, and the total number of devices that match the device characteristic information is uncertain, or the order of devices that match the device characteristic information is also uncertain, then it is generally judged as a non-designated AIoT device.
[0211] Device characteristic information: If the device identifier is given by device characteristic information, and the total number of devices that match the device characteristic information is determined or known (e.g., informed to the Reader by network-side devices or servers), and / or the order of devices that match the device characteristic information is determined, then it can be identified as the specified AIoT device.
[0212] The Reader can perform precise control over the signaling process of sending messages to one or more specified AIoT devices to ensure communication efficiency and latency performance. The information sent by the Reader to the AIoT devices can be carried using Paging messages or other R2D / DL signaling, and the content includes at least one of the following:
[0213] The signaling content of higher layers (i.e., the first higher layer command in the above embodiment), such as the Inventory command, the Command command, and the specific content of the Command command, such as Read, Write, Kill, etc.;
[0214] The targeted device identification information (i.e., at least one device identifier in the above embodiments), such as device identifier ID, or a list of device identifier IDs;
[0215] Dedicated resources are allocated to each specified AIoT device. When there is only one AIoT device, the dedicated resources are directly targeted at that UE. If there are multiple devices, the correspondence between the dedicated resource list and the multiple AIoT devices can be either default or specified. For example, N dedicated resources, N time slots, N frequency resources, or N resource blocks are assigned sequentially to the N devices according to the order in the device identifier list. The device at the first position in the device identifier list corresponds to the first dedicated resource, and so on, with the device at the nth position in the device identifier list corresponding to the nth dedicated resource. Alternatively, a specified method can be used, such as device identifier 1 carrying the corresponding dedicated resource or resource identifier, and so on. Each device identifier displays or indicates the corresponding resource.
[0216] Assign a valid temporary identifier from the Reader to the specified AIoT device for subsequent data scheduling and transmission. This can be done for one device, multiple devices, or all devices involved in this command. Each device has its own unique temporary identifier.
[0217] To indicate subsequent steps to a specified device (i.e., the transmission indication information in the above embodiments), such as the execution method of a command, there may be multiple steps to choose from, such as instructing the AIoT device to execute method 1 (i.e., the method provided in Embodiment 2 below), or other methods, or instructing how step 1 is sent, the content in Msg1, etc.
[0218] After receiving the Paging and R2D / DL signaling from the Reader, the designated AIoT device initiates subsequent communication processes according to the Reader's instructions to complete the entire signaling flow.
[0219] Example 2:
[0220] The communication method in this embodiment can be called Method 1. The request sent by the network-side device or server to the reader is detailed in Embodiment 1. The focus of this embodiment is the interaction steps between the reader and the AIoT device, as shown in Figure 5, including the following steps:
[0221] Step 1: The Reader sends a Msg0 message (i.e., the first message in the above embodiment) to the AIoT device. This message can be a Paging message or other R2D message type. The message carries high-level signaling content from the core network or server, such as Inventory, Command (e.g., Read, Write, Kill, etc.), and also carries the device identifier or a list of device identifiers targeted by this signaling. For example, it may contain one or more device identifiers for a single device. Optionally, dedicated transmission resources may be allocated to each AIoT device involved, either implicitly or explicitly.
[0222] For example, if there is only one device, then the default Msg1 resource after Msg0 is dedicated to that device. If there is more than one device, then Msg0 can carry multiple resource blocks, such as N time slots, N frequencies, and N time-frequency resource blocks, which correspond to each device in the AIoT device ID in sequence, specifically in a one-to-one correspondence.
[0223] Step 2: After receiving the Msg0 message, the designated AIoT device acquires its own dedicated transmission resources in sequence and sends the Msg1 message (i.e., the second message in the above embodiment) to the Reader on its own dedicated resources. The Msg1 message is a response to the higher-level message content in Msg0. For example, for Inventory, the AIoT device can return its own EPC ID; for Read information, the AIoT device can return the data content that was requested to be read; for Write message, the AIoT device can return confirmation information that the write is completed, etc. In short, the Msg1 message contains the EPC ID and / or higher-level data content and is sent to the Reader on the designated dedicated resources.
[0224] Next: Since Msg1 is a dedicated resource, there is no conflict or competition. On the dedicated resource of each device, the Reader reads the feedback Msg1 message of that device and sends the higher-level EPC ID or higher-level data content in the Msg1 message to the core network or server.
[0225] In particular, if the expected Msg1 message from the UE is not correctly received on the designated dedicated resource, the Reader can determine that the process has failed, and can continue to complete the communication process for the failed device by retransmitting a new Msg0 message and receiving a Msg1 message.
[0226] For AIoT devices, under the control of Msg0 information and parameters, the transmission of Msg1 does not require any failure detection or active recovery. The Reader is fully responsible for judging process failures and retransmission to ensure the reliability and completion of information transmission.
[0227] Example 3:
[0228] The communication method in this embodiment can be called Method 2. The request sent by the network-side device or server to the Reader is detailed in Embodiment 1. The focus of this example is the interaction steps between the Reader and the AIoT device. Specifically, based on Embodiment 1, another detailed interaction step between the Reader and the AIoT device is given to complete the entire signaling flow, as shown in Figure 6, including the following steps:
[0229] Step 1 (similar to Example 2): The Reader sends a Msg0 message (i.e., the first message in the above example) to the AIoT device. This message can be a Paging message or other R2D message type. The message carries the higher-level signaling content of the core network or server, such as Inventory, Command (Read, Write, Kill, etc.), and also carries the device identifier or list of device identifiers targeted by this signaling, such as one or more AIoT device IDs for a single device. Optionally, dedicated transmission resources are allocated to each AIoT device involved in an implicit or explicit manner.
[0230] For example, if there is only one device, then the default Msg1 resource after Msg0 is dedicated to that device. If there is more than one device, then multiple resource blocks can be carried in Msg0, such as N time slots, N frequencies, and N time-frequency resource blocks, which correspond to each device in the AIoT device ID in sequence, specifically in a one-to-one correspondence.
[0231] Specifically, Msg0 can also carry an indication requesting the AIoT device to send its own random number RN16 in Msg1 for subsequent scheduling. This is a significant difference between Embodiments 2 and 3 regarding Msg0: Msg0 carries whether Msg1 needs to send the device's RN16, or whether there is an indication for subsequent scheduling. Of course, explicitly distinguishing Msg0 in Embodiments 2 and 3 using signaling methods represents a coexistence of both approaches. Alternatively, the standard might adopt a default approach, where Msg0 does not carry any subsequent indication or RN16 indication, and the AIoT device simply follows the instructions in Embodiments 2 or 3 as specified in the standard.
[0232] Step 2: After receiving the Msg0 message, the designated AIoT device acquires its own dedicated resources in sequence and sends the Msg1 message (i.e., the second message in the above embodiment) to the Reader on its own dedicated resources. The Msg1 message is a response to the higher-level message content in Msg0. For example, for Inventory, the AIoT device can return its EPC ID; for Read information, the AIoT device can return the data content that was requested to be read; for Write message, the AIoT device can return confirmation information that the write is completed, etc. In short, the Msg1 message contains the EPC ID and / or higher-level data content and is sent to the Reader on the designated dedicated resources.
[0233] Since Msg0 carries an explicit subsequent scheduling instruction or RN16 instruction, or the method in the standard selection embodiment three is used as the default method, in Msg1, the AIoT device also carries a random number RN16. This random number is randomly generated, or generated after randomization operation based on its own device ID, such as a hash function. The AIoT device carries RN16 in Msg1 and sends it to the reader.
[0234] Next: Since Msg1 is a dedicated resource, there is no conflict or competition. On the dedicated resource of each device, the reader reads the feedback Msg1 message of that device and sends the higher-level EPC ID or higher-level data content in the Msg1 message to the core network or server.
[0235] The Reader reads RN16 from Msg1 and determines whether RN16 conflicts with the random numbers of other devices. If there is no conflict, it confirms that RN16 can be used as the unique identifier of the device under this Reader for subsequent scheduling and transmission of the AIoT device.
[0236] Step 3: The Reader sends a Msg2 message (i.e., the third message in the above embodiment) to the AIoT device. This message contains an acknowledgment of the RN16 sent by the device in Msg1, which means that the reader has correctly received the Msg1 message and that the device's RN16 is valid and can be used for subsequent identification and scheduling. Optionally, other higher-layer signaling information can also be carried in Msg2.
[0237] When an AIoT device receives the RN16 acknowledgment from Msg2, it considers its access process successful. It stores the RN16 for subsequent scheduling and identification. If other messages are present in Msg2, it processes and responds accordingly. Alternatively, it can use the RN16 as an identifier for its own message transmission and scheduling after Msg2.
[0238] If the AIoT device does not receive the RN16 acknowledgment from Msg2 within a specific time period, such as the next R2D time slot or after the timer / window expires, the AIoT device can consider the communication to have failed.
[0239] If the Reader fails to receive Msg1 on the dedicated resource, it can determine that the AIoT device has failed and resend Msg0 to ensure reliability and success rate. Alternatively, if the Reader fails to send Msg2, and the AIoT device has not correctly stored and acknowledged RN16 as its valid identifier, and the Reader, due to the lack of feedback after sending Msg2, defaults to using RN16 as the identifier for subsequent scheduling of the device, and there is no expected response in subsequent scheduling, it can recognize the failure and initiate the process of synchronizing RN16 again.
[0240] Example 4:
[0241] The communication method in this embodiment can be called Method 3. The request sent by the network-side device or server to the Reader is detailed in Embodiment 1. The focus of this example is the interaction steps between the Reader and the AIoT device. Specifically, based on Embodiment 1, another detailed interaction step between the Reader and the AIoT device is given to complete the entire signaling flow, as shown in Figure 7, including the following steps:
[0242] Step 1 (similar to Example 2): The Reader sends a Msg0 message (i.e., the first message in the above example) to the AIoT device. This message can be a Paging message or other R2D message type. The message carries the higher-level signaling content of the core network or server, such as Inventory, Command (Read, Write, Kill, etc.), and also carries the device identifier or list of device identifiers targeted by this signaling, such as one or more AIoT device IDs for a single device. Optionally, dedicated transmission resources are allocated to each AIoT device involved in an implicit or explicit manner.
[0243] For example, if there is only one device, then the default Msg1 resource after Msg0 is dedicated to that device. If there is more than one device, then multiple resource blocks can be carried in Msg0, such as N time slots, N frequencies, and N time-frequency resource blocks, which correspond to each device in the AIoT device ID in sequence, specifically in a one-to-one correspondence.
[0244] In particular, Msg0 can also carry a unique identifier assigned to the AIoT device (i.e., the temporary identifier in the above embodiment) for subsequent scheduling. When there are multiple devices, each device can be assigned a unique identifier, or some devices can be assigned one identifier and some do not need to be assigned one identifier, as long as all are clearly identified.
[0245] This is a significant difference regarding Msg0 in Embodiments 2, 3, and 4. Embodiment 2 is more suitable for single transmissions, while Embodiments 3 and 4 assign RN16 to the device for subsequent scheduling and device identification, facilitating subsequent data transmission. The difference between Embodiments 3 and 4 is that in Embodiment 3, the AIoT device selects RN16, and the Reader confirms its validity, while Embodiment 4 is more direct, with the Reader directly assigning a temporary identifier (such as RN16). Since the Reader can ensure uniqueness during assignment, it is more efficient.
[0246] Step 2: After receiving the Msg0 message, the designated AIoT device acquires its own dedicated resources in sequence and sends the Msg1 message (i.e., the second message in the above embodiment) to the reader on its own dedicated resources. The Msg1 message is a response to the higher-level message content in Msg0. For example, for Inventory, the AIoT device can return its EPC ID; for Read information, the AIoT device can return the data content that was requested to be read; for Write message, the AIoT device can return confirmation information that the write is completed, etc. In short, the Msg1 message contains the EPC ID and / or higher-level data content and is sent to the Reader on the designated dedicated resources.
[0247] The AIoT device receives the temporary identifier assigned by the Reader, stores it, and uses it as a device identifier and identification for subsequent signaling transmissions and scheduling.
[0248] Optionally, AIoT devices can also carry a temporary identifier again in the Msg1 message as an identifier for this Msg1. Alternatively, since Msg1 is a dedicated resource that can identify the user, the temporary identifier can be omitted.
[0249] Example 5:
[0250] The communication method in this embodiment can be called Method 4. The request sent by the network-side device or server to the Reader is detailed in Embodiment 1. The focus of this example is the interaction steps between the Reader and the AIoT device. Specifically, based on Embodiment 1, another detailed interaction step between the Reader and the AIoT device is given to complete the entire signaling flow, as shown in Figure 8, including the following steps:
[0251] Step 1 (similar to Example 2): The Reader sends a Msg0 message (i.e., the first message in the above example) to the AIoT device. This message can be a Paging message or other R2D message type. The message carries high-level signaling content from the core network or server, such as Inventory, Command (Read, Write, Kill, etc.), and also carries the device identifier or list of device identifiers targeted by this signaling, such as one or more AIoT device IDs for a single device. Optionally, dedicated transmission resources are allocated to each AIoT device involved in an implicit or explicit manner.
[0252] For example, if there is only one device, then the default Msg1 resource after Msg0 is dedicated to that device. If there is more than one device, then multiple resource blocks can be carried in Msg0, such as N time slots, N frequencies, and N time-frequency resource blocks, which correspond to each device in the AIoT device ID in sequence, specifically in a one-to-one correspondence.
[0253] Specifically, unlike embodiments two, three, and four, this embodiment expects to send only the RN16 of the AIoT device in Msg1, instead of directly carrying the EPC ID or higher-layer data. Therefore, if this embodiment needs to coexist with other embodiments, the Reader needs to explicitly indicate in Msg0 whether to send higher-layer information or RN16 directly in Msg1, or to indicate implicitly in Msg0. For example, when resources are large, it means that higher-layer information can be sent directly, and when resources are small, it means that RN16 should be sent first. Alternatively, for the method of this embodiment five, it can be directly selected from the standard specifications to enter the standard's normative behavior, and the UE can execute according to the specified behavior without any discrepancy.
[0254] Step 2: After receiving the Msg0 message, the designated AIoT device acquires its own dedicated resources in sequence and sends the Msg1 message (i.e., the second message in the above embodiment) to the Reader on its own dedicated resources. The Msg1 message carries the device's RN16. This random number is generated randomly or generated after randomization calculation based on its own device ID, such as a hash function. The AIoT device carries the RN16 in the Msg1 message and sends it to the Reader.
[0255] Next: Since Msg1 is a dedicated resource, there is no conflict or competition. On the dedicated resource of each device, the Reader reads the feedback Msg1 message of that device. The Reader reads RN16 in Msg1 and determines whether RN16 conflicts with the random numbers of other existing devices. If there is no conflict, it is confirmed that RN16 can be used as the unique identifier of the device under this Reader for subsequent scheduling and transmission of the AIoT device.
[0256] Step 3: The Reader sends a Msg2 message (i.e., the third message in the above embodiment) to the AIoT device. This message contains an acknowledgment of the RN16 sent by the device in Msg1, which means that the Reader has correctly received the Msg1 message and that the device's RN16 is valid and can be used for subsequent identification and scheduling.
[0257] When an AIoT device receives the RN16 acknowledgment from Msg2, it considers its access process successful. It stores the RN16 for subsequent scheduling and identification. If other messages are present in Msg2, it processes and responds accordingly. Alternatively, it can use the RN16 as an identifier for its own message transmission and scheduling after Msg2.
[0258] If the AIoT device does not receive the RN16 acknowledgment from Msg2 within a specific time period, such as the next R2D time slot or after the timer / window expires, the AIoT device can consider the communication to have failed.
[0259] If the Reader fails to receive Msg1 on the dedicated resource, it can determine that the AIoT device has failed and resend Msg0 to ensure reliability and success rate. Alternatively, if the Reader fails to send Msg2, and the AIoT device has not correctly stored and acknowledged RN16 as its valid identifier, and the Reader, due to the lack of feedback after sending Msg2, defaults to using RN16 as the identifier for subsequent scheduling of the device, and there is no expected response in subsequent scheduling, it can recognize the failure and initiate the process of synchronizing RN16 again.
[0260] Step 4: Upon successfully receiving its own RN16 confirmed device, the device initiates a new UL, D2R message transmission (i.e., the fourth message in the above embodiment). This message is a response to the higher-level message content in Msg0. For example, for Inventory, the AIoT device can return its EPC ID; for Read information, the AIoT device can return the data content that was requested to be read; for Write message, the AIoT device can return confirmation information that the write is completed, etc. In short, the Msg1 message contains the EPC ID and / or higher-level data content and is sent to the Reader on the specified dedicated resource.
[0261] Next: Since this message is also transmitted using dedicated resources, there are no conflicts or contentions. The Reader reads the feedback message from the device and sends the higher-level EPC ID or higher-level data content in the message to the core network or server.
[0262] If there are any subsequent signaling processes, the Reader and the AIoT device rely on RN16 for scheduling and transmission.
[0263] The above embodiments provide a communication method for a designated AIoT device, enabling the AIoT device to perform non-contention access and transmission under the control of the Reader, ensuring communication efficiency and latency performance, thereby reducing network complexity and overhead and improving system efficiency while ensuring transmission performance.
[0264] The IoT communication method provided in this application can be executed by an IoT communication device. This application uses an IoT communication device executing the IoT communication method as an example to illustrate the IoT communication device provided in this application.
[0265] This application provides an Internet of Things (IoT) communication device. As an example, the IoT communication 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.
[0266] An IoT communication device may include a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor may include a general-purpose processor, a dedicated processor, such as a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), an Artificial Intelligence (AI) processor, a Graphics Processing Unit (GPU), an Application Specific Integrated Circuit (ASIC), a Network Processor (NP), a Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules may be implemented by a communication interface, which may include one or more of the following: a transceiver, pins, circuits, a bus, and a radio frequency unit.
[0267] Specifically, referring to Figure 9, when the IoT communication device is a network-side device or terminal, or a component in a network-side device or terminal, the IoT communication device 900 includes:
[0268] Sending module 901 is used to send a first message, the first message being used to determine transmission resources;
[0269] The receiving module 902 is used to receive a second message sent by an IoT device through the transmission resource.
[0270] Optionally, the first message includes at least one of the following:
[0271] Paging messages, downlink messages, and reader-to-device R2D messages.
[0272] Optionally, the first message includes at least one of the following:
[0273] First high-layer signaling, at least one device identifier, indication information of the transmission resource, transmission indication information, and a temporary identifier effective within the scope of the communication device;
[0274] The IoT device belongs to the IoT device corresponding to the at least one device identifier, the transmission indication information is used to indicate the transmission behavior between the IoT device and the communication device, and the temporary identifier includes the temporary identifier of the IoT device corresponding to the at least one device identifier.
[0275] Optionally, the device identifier includes:
[0276] The communication device receives the device identifier from the network-side device or the server.
[0277] Optionally, the transmission indication information is used to indicate one of the following transmission behaviors between the IoT device and the communication device:
[0278] Send a random number to the communication device;
[0279] Do not send random numbers to the communication device;
[0280] The communication device sends the temporary identifier to the Internet of Things device;
[0281] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0282] Optionally, when sending a random number to the communication device:
[0283] The second message includes the random number, as well as at least one of the identification information of the IoT device and first high-level data;
[0284] Alternatively, the second message may include a random number, and at least one of the IoT device's identification information and first high-level data may be sent to the communication device via a message other than the second message.
[0285] Optionally, the transmission resources include at least one of the following:
[0286] The default transport resource associated with the first message, and the transport resource indicated by the first message.
[0287] Optionally, the communication device sends a first message, including:
[0288] The communication device sends the first message to N Internet of Things devices;
[0289] The transmission resources include N transmission resources, each of which is a dedicated transmission resource for the N IoT devices, where N is a positive integer.
[0290] Optionally, the second message includes at least one of the following:
[0291] The identification information, first high-level data, and random number of the IoT device;
[0292] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0293] Optionally, the sending module is further configured to send a third message to the IoT device, the third message including at least one of the following:
[0294] The confirmation information of the random number and the second higher-level signaling.
[0295] Optionally, the receiving module is further configured to receive a fourth message sent by the IoT device, the fourth message including at least one of the following:
[0296] The identification information of the IoT device and the second high-level data.
[0297] Optionally, the receiving module is further configured to receive a fifth message sent by a network-side device or a server, the fifth message including at least one of the following:
[0298] Third-layer signaling, at least one device identifier;
[0299] The IoT device belongs to the IoT device corresponding to the at least one device identifier.
[0300] Optionally, the device identifier includes at least one of the following:
[0301] Device identifiers, device group identifiers, and device characteristic information are used to identify individual devices.
[0302] The aforementioned IoT communication devices can improve communication efficiency.
[0303] The IoT communication device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG3 and achieve the same technical effect. To avoid repetition, it will not be described again here.
[0304] Referring to Figure 10, when the IoT communication device is a component in an IoT device, the IoT communication device 1000 includes:
[0305] The receiving module 1001 is used to receive a first message sent by the communication device, wherein the first message is used to determine transmission resources;
[0306] The sending module 1002 is used to send a second message to the communication device through the transmission resources.
[0307] Optionally, the first message includes at least one of the following:
[0308] Paging messages, downlink messages, and reader-to-device R2D messages.
[0309] Optionally, the first message includes at least one of the following:
[0310] First high-layer signaling, at least one device identifier, indication information of the transmission resource, transmission indication information, and a temporary identifier effective within the scope of the communication device;
[0311] The IoT device belongs to the IoT device corresponding to the at least one device identifier, the transmission indication information is used to indicate the transmission behavior between the IoT device and the communication device, and the temporary identifier includes the temporary identifier of the IoT device corresponding to the at least one device identifier.
[0312] Optionally, the device identifier includes at least one of the following:
[0313] The communication device receives the device identifier from the network-side device or the server.
[0314] Optionally, the transmission indication information is used to indicate one of the following transmission behaviors between the IoT device and the communication device:
[0315] Send a random number to the communication device;
[0316] Do not send random numbers to the communication device;
[0317] The communication device sends the temporary identifier to the Internet of Things device;
[0318] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0319] Optionally, when sending a random number to the communication device:
[0320] The second message includes the random number, as well as at least one of the identification information of the IoT device and first high-level data;
[0321] Alternatively, the second message may include a random number, and at least one of the IoT device's identification information and first high-level data may be sent to the communication device via a message other than the second message.
[0322] Optionally, the transmission resources include at least one of the following:
[0323] The default transport resource associated with the first message, and the transport resource indicated by the first message.
[0324] Optionally, the transmission resources include: N transmission resources, each of which is a dedicated transmission resource for the N IoT devices, where N is a positive integer;
[0325] The sending module is used to send a second message to the communication device through the dedicated transmission resources of the IoT device.
[0326] Optionally, the second message includes at least one of the following:
[0327] The identification information, first high-level data, and random number of the IoT device;
[0328] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0329] Optionally, the receiving module is further configured to receive a third message sent by the communication device, the third message including at least one of the following:
[0330] The confirmation information of the random number and the second higher-level signaling.
[0331] Optionally, the sending module is further configured to send a fourth message to the communication device, the fourth message including at least one of the following:
[0332] The identification information of the IoT device and the second high-level data.
[0333] The aforementioned IoT communication devices can help improve communication efficiency.
[0334] The IoT communication device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG4 and achieve the same technical effect. To avoid repetition, it will not be described again here.
[0335] As shown in Figure 11, this application embodiment also provides a communication device 1100, including a processor 1101 and a memory 1102. The memory 1102 stores a program or instructions that can run on the processor 1101. For example, when the communication device 1100 is the communication device in the embodiment shown in Figure 3, the program or instructions, when executed by the processor 1101, implement the various steps of the above-described IoT communication method embodiment and achieve the same technical effect. When the communication device 1100 is an IoT device, the program or instructions, when executed by the processor 1101, implement the various steps of the above-described IoT communication method embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.
[0336] 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 FIG3. 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.
[0337] Specifically, this application embodiment also provides a communication device, which can be the IoT communication device shown in FIG9. As shown in FIG12, the communication device 1200 includes: an antenna 1201, a radio frequency device 1202, a baseband device 1203, a processor 1204, and a memory 1205. The antenna 1201 is connected to the radio frequency device 1202. In the uplink direction, the radio frequency device 1202 receives information through the antenna 1201 and sends the received information to the baseband device 1203 for processing. In the downlink direction, the baseband device 1203 processes the information to be transmitted and sends it to the radio frequency device 1202, which processes the received information and then transmits it through the antenna 1201.
[0338] The method executed by the communication device in the above embodiments can be implemented in the baseband device 1203, which includes a baseband processor.
[0339] The baseband device 1203 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG12. One of the chips is, for example, a baseband processor, which is connected to the memory 1205 via a bus interface to call the program in the memory 1205 and execute the network device operation shown in the above method embodiment.
[0340] The communication device may also include a network interface 1206, such as a Common Public Radio Interface (CPRI).
[0341] Specifically, the communication device 1200 in this application embodiment further includes: instructions or programs stored in memory 1205 and executable on processor 1204. Processor 1204 calls the instructions or programs in memory 1205 to execute the methods executed by each module shown in FIG9 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.
[0342] The radio frequency device 1202 is used to send a first message, the first message being used to determine transmission resources; and to receive a second message sent by an IoT device through the transmission resources.
[0343] Optionally, the first message includes at least one of the following:
[0344] Paging messages, downlink messages, and reader-to-device R2D messages.
[0345] Optionally, the first message includes at least one of the following:
[0346] First high-layer signaling, at least one device identifier, indication information of the transmission resource, transmission indication information, and a temporary identifier effective within the scope of the communication device;
[0347] The IoT device belongs to the IoT device corresponding to the at least one device identifier, the transmission indication information is used to indicate the transmission behavior between the IoT device and the communication device, and the temporary identifier includes the temporary identifier of the IoT device corresponding to the at least one device identifier.
[0348] Optionally, the device identifier includes:
[0349] The communication device receives the device identifier from the network-side device or the server.
[0350] Optionally, the transmission indication information is used to indicate one of the following transmission behaviors between the IoT device and the communication device:
[0351] Send a random number to the communication device;
[0352] Do not send random numbers to the communication device;
[0353] The communication device sends the temporary identifier to the Internet of Things device;
[0354] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0355] Optionally, when sending a random number to the communication device:
[0356] The second message includes the random number, as well as at least one of the identification information of the IoT device and first high-level data;
[0357] Alternatively, the second message may include a random number, and at least one of the IoT device's identification information and first high-level data may be sent to the communication device via a message other than the second message.
[0358] Optionally, the transmission resources include at least one of the following:
[0359] The default transport resource associated with the first message, and the transport resource indicated by the first message.
[0360] Optionally, sending the first message includes:
[0361] Send the first message to N IoT devices;
[0362] The transmission resources include N transmission resources, each of which is a dedicated transmission resource for the N IoT devices, where N is a positive integer.
[0363] Optionally, the second message includes at least one of the following:
[0364] The identification information, first high-level data, and random number of the IoT device;
[0365] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0366] Optionally, after receiving the second message sent by the IoT device through the transmission resource, the radio frequency device 1202 is further configured to:
[0367] Send a third message to the IoT device, the third message including at least one of the following:
[0368] The confirmation information of the random number and the second higher-level signaling.
[0369] Optionally, the third message includes confirmation information for the random number, and after sending the third message to the IoT device, the radio frequency device 1202 is further configured to:
[0370] Receive a fourth message sent by the IoT device, the fourth message including at least one of the following:
[0371] The identification information of the IoT device and the second high-level data.
[0372] Optionally, before sending the first message, the radio frequency device 1202 is further configured to:
[0373] Receive a fifth message sent by a network-side device or server, the fifth message including at least one of the following:
[0374] Third-layer signaling, at least one device identifier;
[0375] The IoT device belongs to the IoT device corresponding to the at least one device identifier.
[0376] Optionally, the device identifier includes at least one of the following:
[0377] Device identifiers, device group identifiers, and device characteristic information are used to identify individual devices.
[0378] The aforementioned communication equipment helps improve communication efficiency.
[0379] 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 communication method and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.
[0380] 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 13. That is, the device shown in Figure 13 can also implement the technical solution provided in this embodiment.
[0381] This application also provides a communication device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG4. This communication device embodiment corresponds to the above-described communication device-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this communication device embodiment and achieve the same technical effect. This communication device can be the IoT communication device shown in FIG10. Specifically, FIG13 is a schematic diagram of the hardware structure of a communication device implementing an embodiment of this application.
[0382] The communication device 1300 includes, but is not limited to, at least some of the following components: radio frequency unit 1301, network module 1302, audio output unit 1303, input unit 1304, sensor 1305, display unit 1306, user input unit 1307, interface unit 1308, memory 1309, and processor 1310.
[0383] Those skilled in the art will understand that the communication device 1300 may also include a power supply (such as a battery) for powering various components. The power supply may be logically connected to the processor 1310 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. The communication device structure shown in Figure 13 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.
[0384] It should be understood that, in this embodiment, the input unit 1304 may include a graphics processor 13041 and a microphone 13042. The graphics processor 13041 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 1306 may include a display panel 13061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1307 includes a touch panel 13071 and at least one of other input devices 13072. The touch panel 13071 is also called a touch screen. The touch panel 13071 may include a touch detection device and a touch controller. Other input devices 13072 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.
[0385] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1301 can transmit it to the processor 1310 for processing; in addition, the radio frequency unit 1301 can send uplink data to the network-side device. Typically, the radio frequency unit 1301 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.
[0386] The memory 1309 can be used to store software programs or instructions, as well as various data. The memory 1309 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 1309 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 1309 in this embodiment includes, but is not limited to, these and any other suitable types of memory.
[0387] Processor 1310 may include one or more processing units; optionally, processor 1310 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 1310.
[0388] 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.
[0389] The radio frequency unit 1301 is used to receive a first message sent by a communication device, the first message being used to determine transmission resources; and to send a second message to the communication device through the transmission resources.
[0390] Optionally, the first message includes at least one of the following:
[0391] Paging messages, downlink messages, and reader-to-device R2D messages.
[0392] Optionally, the first message includes at least one of the following:
[0393] First high-layer signaling, at least one device identifier, indication information of the transmission resource, transmission indication information, and a temporary identifier effective within the scope of the communication device;
[0394] The IoT device belongs to the IoT device corresponding to the at least one device identifier, the transmission indication information is used to indicate the transmission behavior between the IoT device and the communication device, and the temporary identifier includes the temporary identifier of the IoT device corresponding to the at least one device identifier.
[0395] Optionally, the device identifier includes at least one of the following:
[0396] The communication device receives the device identifier from the network-side device or the server.
[0397] Optionally, the transmission indication information is used to indicate one of the following transmission behaviors between the IoT device and the communication device:
[0398] Send a random number to the communication device;
[0399] Do not send random numbers to the communication device;
[0400] The communication device sends the temporary identifier to the Internet of Things device;
[0401] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0402] Optionally, when sending a random number to the communication device:
[0403] The second message includes the random number, as well as at least one of the identification information of the IoT device and first high-level data;
[0404] Alternatively, the second message may include a random number, and at least one of the IoT device's identification information and first high-level data may be sent to the communication device via a message other than the second message.
[0405] Optionally, the transmission resources include at least one of the following:
[0406] The default transport resource associated with the first message, and the transport resource indicated by the first message.
[0407] Optionally, the transmission resources include: N transmission resources, each of which is a dedicated transmission resource for the N IoT devices, where N is a positive integer;
[0408] The second message sent to the communication device via the transmission resources includes:
[0409] The second message is sent to the communication device via the dedicated transmission resources of the IoT device.
[0410] Optionally, the second message includes at least one of the following:
[0411] The identification information, first high-level data, and random number of the IoT device;
[0412] The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
[0413] Optionally, after sending the second message to the communication device via the transmission resources, the radio frequency unit 1301 is further configured to:
[0414] Receive a third message sent by the communication device, the third message including at least one of the following:
[0415] The confirmation information of the random number and the second higher-level signaling.
[0416] Optionally, the third message includes confirmation information for the random number, and after receiving the third message sent by the communication device, the radio frequency unit 1301 is further configured to:
[0417] A fourth message sent to the communication device, the fourth message including at least one of the following:
[0418] The identification information of the IoT device and the second high-level data.
[0419] The aforementioned communication equipment can improve communication efficiency.
[0420] 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 communication method and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.
[0421] 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 communication method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.
[0422] 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.
[0423] 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 communication method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0424] 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.
[0425] 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 communication method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0426] This application also provides a wireless communication system, including: a communication device and an Internet of Things (IoT) device. The communication device can be used to execute the steps of the IoT communication method on the communication device side as provided in this application embodiment, and the network-side device can be used to execute the steps of the IoT communication method on the IoT device side as provided in this application embodiment.
[0427] 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.
[0428] 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.
[0429] 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 Internet of Things (IoT) communication, comprising: sending, by a communication device, a first message, the first message being used for determining a transmission resource; receiving, by the communication device, a second message sent by an IoT device through the transmission resource.
2. The method of claim 1, wherein, The first message comprises at least one of: a paging message, a downlink message, a Reader-to-Device (R2D) message.
3. The method of claim 1 or 2, wherein, The first message comprises at least one of: first high layer signaling, at least one device identifier, indication information of the transmission resource, transmission indication information, a temporary identifier valid within a range of the communication device; the IoT device belongs to an IoT device corresponding to the at least one device identifier, the transmission indication information is used for indicating a transmission behavior between the IoT device and the communication device, and the temporary identifier comprises a temporary identifier of the IoT device corresponding to the at least one device identifier.
4. The method of claim 3, wherein, The device identifier comprises: a device identifier received by the communication device from a network side device or a server.
5. The method of claim 3 or 4, wherein, The transmission indication information is used for indicating at least one of the following transmission behaviors between the IoT device and the communication device: sending a random number to the communication device; not sending a random number to the communication device; sending, by the communication device, the temporary identifier to the IoT device; The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
6. The method of claim 5, wherein, In the case of sending a random number to the communication device: the second message comprises the random number and at least one of the following: identification information of the IoT device and first high layer data; or, the second message comprises a random number, and the communication device is sent at least one of the following: identification information of the IoT device and first high layer data through a message other than the second message.
7. The method of any one of claims 1 to 6, wherein, The transmission resource comprises at least one of: a default transmission resource associated with the first message, a transmission resource indicated by the first message.
8. The method of any one of claims 1 to 7, wherein, The communication device sending the first message comprises: the communication device sending the first message to N IoT devices; wherein the transmission resource comprises N transmission resources, the N transmission resources being dedicated transmission resources for the N IoT devices respectively, N being a positive integer.
9. The method of any one of claims 1 to 8, wherein, The second message comprises at least one of: identification information of the IoT device, first high layer data, a random number; The random number is used for at least one of the following: scheduling the IoT device, identifying the IoT device.
10. The method of claim 9, wherein, After the communication device receives the second message sent by the IoT device through the transmission resource, the method further comprises: the communication device sending a third message to the IoT device, the third message comprising at least one of: confirmation information of the random number, second high layer signaling.
11. The method of claim 10, wherein, The third message comprises confirmation information of the random number, and after the communication device sends the third message to the IoT device, the method further comprises: the communication device receiving a fourth message sent by the IoT device, the fourth message comprising at least one of: identification information of the IoT device, second high layer data.
12. The method of any one of claims 1 to 11, wherein, Before the communication device sends the first message, the method further comprises: The communication device receives a fifth message sent by a network side device or a server, and the fifth message includes at least one of the following: Third high layer signaling, at least one device identifier; The Internet of Things device belongs to the Internet of Things device corresponding to the at least one device identifier.
13. The method of claim 3, 4, or 12, wherein, The device identifier includes at least one of the following: Device identifier for identifying a single device, device group identifier, and device feature information.
14. An Internet of Things communication method, comprising: An Internet of Things device receives a first message sent by a communication device, and the first message is used to determine a transmission resource; The Internet of Things device sends a second message to the communication device through the transmission resource.
15. The method of claim 14, wherein, The first message includes at least one of the following: Paging message, downlink message, and reader-to-device (R2D) message.
16. The method of claim 14 or 15, wherein, The first message includes at least one of the following: First high layer signaling, at least one device identifier, indication information of the transmission resource, transmission indication information, and temporary identifier valid within a range of the communication device; The Internet of Things device belongs to the Internet of Things device corresponding to the at least one device identifier, the transmission indication information is used to indicate a transmission behavior between the Internet of Things device and the communication device, and the temporary identifier includes a temporary identifier of the Internet of Things device corresponding to the at least one device identifier.
17. The method of claim 16, wherein, The device identifier includes at least one of the following: Device identifier received by the communication device from a network side device or a server.
18. The method of claim 16 or 17, wherein, The transmission indication information is used to indicate at least one of the following transmission behaviors between the Internet of Things device and the communication device: Sending a random number to the communication device; Not sending a random number to the communication device; The communication device sends the temporary identifier to the Internet of Things device; The random number is used for at least one of the following: scheduling the Internet of Things device and identifying the Internet of Things device.
19. The method of claim 18, wherein, In the case of sending a random number to the communication device: The second message includes the random number, and at least one of the following: identification information of the Internet of Things device and first high layer data; Or, the second message includes a random number, and at least one of the following: identification information of the Internet of Things device and first high layer data is sent to the communication device through a message other than the second message.
20. The method of any one of claims 14 to 19, wherein, The transmission resource includes at least one of the following: Default transmission resource associated with the first message, and transmission resource indicated by the first message.
21. The method of any one of claims 14 to 20, wherein, The transmission resource includes N transmission resources, and the N transmission resources are dedicated transmission resources of the N Internet of Things devices, where N is a positive integer. The Internet of Things device sends a second message to the communication device through the transmission resource, including: The Internet of Things device sends a second message to the communication device through the dedicated transmission resource of the Internet of Things device.
22. The method of any one of claims 14 to 21, wherein, The second message includes at least one of the following: Identification information of the Internet of Things device, first high layer data, and random number; The random number is used for at least one of the following: scheduling the Internet of Things device and identifying the Internet of Things device.
23. The method of claim 22, wherein, After the Internet of Things device sends a second message to the communication device through the transmission resource, the method further includes: The Internet of Things device receives a third message sent by the communication device, and the third message includes at least one of the following: confirmation information of the random number, second high-layer signaling.
24. The method of claim 23, wherein, The third message includes the confirmation information of the random number, and after the Internet of Things device receives the third message sent by the communication device, the method further includes: The fourth message sent by the Internet of Things device to the communication device, and the fourth message includes at least one of the following: identification information of the Internet of Things device, second high-layer data.
25. An Internet of Things communication device, comprising: a sending module configured to send a first message, the first message being used to determine a transmission resource; a receiving module configured to receive a second message sent by an Internet of Things device through the transmission resource.
26. The apparatus of claim 25, wherein, The first message includes at least one of the following: a paging message, a downlink message, and a reader-to-device (R2D) message.
27. The apparatus of claim 25 or 26, wherein, The second message includes at least one of the following: identification information of the Internet of Things device, first high-layer data, and a random number; The random number is used for at least one of the following: scheduling the Internet of Things device and identifying the Internet of Things device.
28. The apparatus of claim 27, wherein, The sending module is further configured to send a third message to the Internet of Things device, and the third message includes at least one of the following: confirmation information of the random number, second high-layer signaling.
29. The apparatus of claim 28, wherein, The receiving module is further configured to receive a fourth message sent by the Internet of Things device, and the fourth message includes at least one of the following: identification information of the Internet of Things device, second high-layer data.
30. The apparatus of any one of claims 25-29, wherein, The receiving module is further configured to receive a fifth message sent by a network-side device or a server, and the fifth message includes at least one of the following: third high-layer signaling and at least one device identifier; The Internet of Things device belongs to an Internet of Things device corresponding to the at least one device identifier.
31. An Internet of Things communication device, comprising: a receiving module configured to receive a first message sent by a communication device, the first message being used to determine a transmission resource; a sending module configured to send a second message to the communication device through the transmission resource.
32. The apparatus of claim 31, wherein, The first message includes at least one of the following: a paging message, a downlink message, and a reader-to-device (R2D) message.
33. The apparatus of claim 31 or 32, wherein, The second message includes at least one of the following: identification information of an Internet of Things device, first high-layer data, and a random number; The random number is used for at least one of the following: scheduling the Internet of Things device and identifying the Internet of Things device.
34. The apparatus of claim 33, wherein, The receiving module is further configured to receive a third message sent by the communication device, and the third message includes at least one of the following: confirmation information of the random number, second high-layer signaling.
35. The apparatus of claim 34, wherein, The sending module is further configured to send a fourth message to the communication device, and the fourth message includes at least one of the following: identification information of the Internet of Things device, second high-layer data.
36. An apparatus comprising a processor and a memory, said memory storing programs or instructions executable on said processor, said programs or instructions, when executed by said processor, implementing the steps of the method of Internet of Things communication according to any one of claims 1 to 13, or said programs or instructions, when executed by said processor, implementing the steps of the method of Internet of Things communication according to any one of claims 14 to 24.
37. A readable storage medium, said readable storage medium storing programs or instructions, said programs or instructions, when executed by a processor, implementing the steps of the method of Internet of Things communication according to any one of claims 1 to 13, or implementing the steps of the method of Internet of Things communication according to any one of claims 14 to 24.
38. A computer program product, said computer program product being stored in a storage medium, said computer program product being executed by at least one processor to implement the steps of the method of Internet of Things communication according to any one of claims 1 to 13, or to implement the steps of the method of Internet of Things communication according to any one of claims 14 to 24.
Citation Information
Patent Citations
Communication method and device
CN115769650A
Communication method and device
CN117460070A
Communication method, device and system
CN117676859A
Information transmission method and device and storage medium
CN117956552A
Random access method and related device
US20210153263A1