Internet of Things equipment management method and system

Abstract

The invention relates to an Internet of Things equipment management method and system. The method comprises the following steps: receiving an initial trigger message sent by a network node, the initial trigger message comprising an electric quantity state report indication, an indication for access opportunity of the Internet of Things equipment, a paging period and / or a quantity indication for the quantity of the access opportunity, and a quantity indication for the quantity of the paging period and / or the access opportunity; the length information of the to-be-triggered Internet of Things equipment identifier, the to-be-triggered Internet of Things equipment identifier, the access type indicator, the network node identifier and the service identifier; and sending a first message to the network node, wherein the first message carries at least one item of the electric quantity state and the Internet of Things equipment identifier. By adopting the method, the problem of data packet transmission failure caused by limited electric quantity of the Internet of Things equipment can be avoided, and the flexibility of network deployment and the network stability are improved.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a method and system for managing Internet of Things (IoT) devices. Background Technology

[0002] With the development of wireless communication technology, more and more IoT devices are interconnected, enabling dense deployments and making wireless communication technology more practical in the IoT field. Therefore, reducing the size, complexity, and power consumption of IoT devices has become a current trend. To achieve the deployment of billions or even hundreds of billions of dense IoT devices, future IoT applications may rely on passive communication devices that do not depend on battery power and do not require manual battery replacement.

[0003] In traditional technologies, if rechargeable IoT devices are used for paging in the network, passive communication IoT devices will miss paging if they lose power during charging, leading to inaccurate statistics and failing to meet the resource inventory requirements of industrial applications. Furthermore, because IoT devices have limited power, and responding to reader commands requires reporting large data packets, insufficient power can easily cause transmission failures. Therefore, a new management method for IoT devices is urgently needed. Summary of the Invention

[0004] This application provides an Internet of Things (IoT) device management method and system.

[0005] Firstly, an Internet of Things (IoT) device management method is provided, the method being applied to IoT devices, the method comprising:

[0006] Receive an initial trigger message sent by a network node. The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, paging cycle and / or access timing quantity indication, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, network node identifier, and service identifier.

[0007] Send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier.

[0008] In one embodiment, the IoT device identifier includes a temporary identifier locally generated by the IoT device and / or the device identifier of the IoT device.

[0009] In one embodiment, the network node includes either a reader or an intermediate node device.

[0010] In one embodiment, the reader includes at least one of the following:

[0011] Base stations, repeaters, IAB integrated access and backhaul nodes, network control relays (NCRs), and user equipment of different standards.

[0012] In one embodiment, the power status reporting indication is used to request the Internet of Things device to report its current power status information.

[0013] In one embodiment, the power status is the predicted power status of the IoT device at the present or a first future point in time;

[0014] The power status includes communication status duration information and / or power status indication;

[0015] The communication status duration information refers to the monitoring of communication transmission from the network node to the IoT device after the IoT device completes the current communication transmission sent to the network node.

[0016] In one embodiment, the power status is used to indicate whether the IoT device has the energy to perform a second round of communication transmission between the IoT device and the network node.

[0017] In one embodiment, the indication of when the IoT device accesses the network is to instruct the IoT device to reply to the network node with the time-domain and / or frequency-domain resource location of the initial trigger message or command response message.

[0018] In one embodiment, the length information of the IoT device identifier to be triggered is used to indicate the length of the IoT device identifier to be triggered;

[0019] The length information includes at least one of the following: the overall length of the IoT device identifier to be triggered, the SDU length, and the paging padding length.

[0020] In one embodiment, the IoT device identifier to be triggered is used by the network node to trigger or select a single IoT device, a single group of IoT devices, or multiple non-grouped IoT devices;

[0021] If the initial trigger message does not contain the identifier of the IoT device to be triggered, the initial trigger message is used to instruct / select all IoT devices that have received the initial trigger message.

[0022] In one embodiment, the access type indicator is used to indicate the access type of the IoT device;

[0023] The access type indicator includes contention-based random access and non-contention-based random access;

[0024] The access types include contention-based access and contention-free access.

[0025] In one embodiment, if the initial trigger message does not carry the access type indicator, the method further includes:

[0026] The access type is determined based on the IoT device identifier to be triggered in the initial trigger message; or,

[0027] The access type is determined based on the access timing and / or the number of access timings in the initial trigger message.

[0028] In one embodiment, the method further includes:

[0029] Receive at least one first trigger message sent by the network node, wherein the first trigger message is used to indicate the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message.

[0030] In one embodiment, the first trigger message also carries a service identifier.

[0031] In one embodiment, the power status reporting indication is used to request the IoT device to report its current power status, and sending the first message to the network node includes:

[0032] If the initial trigger message contains a power status reporting indication and the IoT device supports power reporting, a first message carrying the power status is sent to the network node.

[0033] In one embodiment, the method further includes:

[0034] The service identifier contained in the initial trigger message is stored, and the service identifier is associated with the responded information; wherein, the service identifier is used to identify the service request corresponding to the initial trigger message;

[0035] If the service identifier contained in the initial trigger message is the same as the service identifier stored in the IoT device, and the previous paging process record associated with the service identifier contained in the initial trigger message is an access failure, then the IoT device is determined to be the responding device selected by the initial trigger message.

[0036] In one embodiment, the method further includes:

[0037] Based on the business identifier, determine whether it is necessary to reply to the initial trigger message;

[0038] If the IoT device stores the service identifier and the service identifier has no associated information, a first response result is determined. The first response result is that the initial trigger message has been responded to and there is no need to respond to this initial trigger message.

[0039] If the IoT device does not store the service identifier, a second response result is determined, which indicates that a response is required to the initial trigger message.

[0040] In one embodiment, the method further includes:

[0041] Based on the business identifier, determine whether it is necessary to reply to the initial trigger message;

[0042] If the IoT device stores a service identifier and the associated information of the service identifier has been responded to, a third response result is determined. The third response result indicates that the initial trigger message has been responded to and there is no need to respond to this initial trigger message.

[0043] If the IoT device stores the service identifier and the associated information of the service identifier is unanswered, a fourth response result is determined, which means that a response is required to the initial trigger message.

[0044] In one embodiment, the method further includes:

[0045] Based on the identifier of the IoT device to be triggered, determine whether it is necessary to reply to the initial trigger message.

[0046] In one embodiment, the method further includes:

[0047] The network node sends a second message, which includes at least one of a segmentation request identifier, an IoT device identifier, an access layer identifier, a command instruction, and associated information, as well as at least one of information on time-domain resources and / or frequency-domain resources required by the third message and the transport block size.

[0048] In one embodiment, the association information includes at least one of the following:

[0049] The association information between the IoT device identifier and the access layer identifier;

[0050] The command indicates the association information between the access layer identifier and the access layer identifier;

[0051] The association information between the IoT device identifier and the command indication.

[0052] In one embodiment, the segmentation request identifier is used to indicate whether the network node allows the transmission of third message segments.

[0053] In one embodiment, the command instruction includes at least one of the following:

[0054] Commands for reading data, writing data, locking data, deleting data, and setting access passwords.

[0055] In one embodiment, the method further includes:

[0056] Execute the command indicated by the command described in the second message;

[0057] Send a third message to the network node, the third message containing at least one of the IoT device identifier, segmented transmission identifier, inventory information, or command response;

[0058] The segmented transmission identifier is used to indicate whether more data needs to be reported during subsequent transmissions.

[0059] In one embodiment, the method further includes:

[0060] If the transmission of the third message fails, the network node receives a first command or a retransmitted second message. The first command indicates that the network node has not received the third message, and the retransmitted second message is consistent with the command information in the initially transmitted second message.

[0061] The first command contains a resource indication required for the retransmission of the third message;

[0062] The scheduling resources include at least one of time-domain indication, frequency-domain indication, and spatial-domain indication.

[0063] In one embodiment, the method further includes:

[0064] Based on the first command, the third message is retransmitted to the network node.

[0065] In one embodiment, the method further includes:

[0066] Receive a second command sent by the network node; the second command contains scheduling information.

[0067] In one embodiment, the scheduling information included in the second command includes at least one of command information, time-frequency resources required for the second command response message, and offset value.

[0068] In one embodiment, the method further includes:

[0069] Based on the scheduling information, a data transmission message is generated for the Data Service Data Unit (SDU) field in the second command to the upper layer of the Resource Description Framework (D2R).

[0070] The SDU field is a field starting from the offset+1th byte, indicated by the received data size field of the original upper-layer data SDU field, and includes all data starting from the received offset value.

[0071] In one embodiment, the method further includes:

[0072] Send a second command response message to the network node or send the second command response message in segments.

[0073] In one embodiment, if the second command response message or the first segment of the second command response message contains an offset value, then offset = 0.

[0074] Secondly, a method for managing Internet of Things (IoT) devices is provided, the method being applied to network nodes, the method comprising:

[0075] Send an initial trigger message to the Internet of Things (IoT) device. The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, number of paging cycles or access timings, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, network node identifier, and service identifier.

[0076] Receive a first message sent by the IoT device, the first message carrying at least one of the power status and the IoT device identifier.

[0077] In one embodiment, the network node includes either a reader or an intermediate node device.

[0078] In one embodiment, the intermediate node device includes a repeater, an IAB integrated access and backhaul node, a network control trunk (NCR), and a user equipment.

[0079] In one embodiment, the method further includes:

[0080] Based on the battery status, determine the device status indication of the IoT device;

[0081] The device status indicator is used to indicate whether the IoT device remains in a communication state or transitions to a shutdown / sleep state. The shutdown state and the sleep state are executed after the current uplink transmission ends or the current paging round ends, and the shutdown state and the sleep state are non-communication states.

[0082] In one embodiment, the method further includes:

[0083] Send at least one first trigger message to the IoT device, wherein the first trigger message is used to indicate the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message.

[0084] In one embodiment, after receiving the first message sent by the IoT device, the method further includes:

[0085] Based on the battery status carried in the first message, a second message is sent to the IoT device. The second message is a message sent when the network node configures the time-frequency resources of the third message.

[0086] In one embodiment, the second message includes at least one of a segmentation request identifier, an IoT device identifier, an access layer identifier, a command instruction, and associated information, as well as at least one of information on time-domain resources and / or frequency-domain resources required by the third message and the transport block size.

[0087] In one embodiment, the method further includes:

[0088] If the first message sent by the IoT device is not received, the step of sending the initial trigger message to the IoT device is re-executed.

[0089] In one embodiment, the method further includes:

[0090] The system receives a third message sent by the IoT device, the third message containing at least one of the IoT device identifier, segmented transmission identifier, inventory information, or command response; the segmented transmission identifier is used to indicate whether more data needs to be reported during subsequent transmission.

[0091] The command response messages are scheduled and configured based on the power status of the IoT devices.

[0092] In one embodiment, the method further includes:

[0093] If the third message sent by the IoT device is not received, a first command or a retransmitted second message is sent to the IoT device. The first command is used to indicate that the network node has not received the third message. The retransmitted second message is consistent with the command information in the initially transmitted second message.

[0094] The first command includes an indication of the scheduling resources required for the retransmission of the third message;

[0095] The scheduling resources include at least one of time-domain indication, frequency-domain indication, and spatial-domain indication.

[0096] In one embodiment, the step of scheduling and configuring the command response message based on the power status of the IoT device includes:

[0097] Send a second command to the IoT device. The second command includes at least one of the following: command information, time-frequency resources required for the second command response message, resource block size, and offset value.

[0098] In one embodiment, the method further includes:

[0099] Receive a second command response message or a segmented second command response message sent by the IoT device.

[0100] In one embodiment, the method further includes:

[0101] The first segment of information received from the second command response message sent by the IoT device includes the segmented transmission identifier.

[0102] In one embodiment, the method further includes:

[0103] If the second command response message or the first segment of the second command response message is not received from the IoT device, the first command is sent to the IoT device or the second command is resent.

[0104] In one embodiment, the method further includes:

[0105] The second segment of the second command response message is received until the transmission of the second command response message is complete;

[0106] Otherwise, perform the step of sending the first command to the IoT device or resending the second command.

[0107] Thirdly, an Internet of Things (IoT) device management apparatus is provided, the apparatus being applied to IoT devices, the apparatus comprising:

[0108] The first receiving module is used to receive an initial trigger message sent by a network node. The initial trigger message includes at least one of the following: a power status reporting indication, an indication of the access timing of IoT devices, an indication of the number of paging cycles and / or access timings, length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, an access type indicator, a network node identifier, and a service identifier.

[0109] A first sending module is configured to send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier.

[0110] Fourthly, an Internet of Things (IoT) device management apparatus is provided, the apparatus being applied to a network node, the apparatus comprising:

[0111] The first sending module is used to send an initial trigger message to an IoT device. The initial trigger message includes at least one of the following: a power status reporting indication, an indication of the IoT device access timing, an indication of the number of paging cycles or access timings, length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, an access type indicator, a network node identifier, and a service identifier.

[0112] A first receiving module is configured to receive a first message sent by the IoT device, the first message carrying at least one of the power status and the IoT device identifier.

[0113] Fifthly, an Internet of Things (IoT) management system is provided, the system comprising IoT devices and network nodes, wherein:

[0114] The IoT device is configured to receive an initial trigger message sent by a network node, the initial trigger message including at least one of the following: a power status reporting indication, an indication of the IoT device access timing, a paging cycle and / or the number of access timings, length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, an access type indicator, a network node identifier, and a service identifier; and to send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier.

[0115] The network node is used to send an initial trigger message to the IoT device and receive the first message sent by the IoT device.

[0116] In a sixth aspect, a communication device is provided, comprising: a transmitter, a receiver, a processor, and a memory, wherein the memory stores a computer program;

[0117] The receiver is configured to receive an initial trigger message sent by a network node. The initial trigger message includes at least one of the following: a power status reporting indication, an indication of the access timing for IoT devices, an indication of the number of paging cycles and / or access timings, length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, an access type indicator, a network node identifier, and a service identifier.

[0118] The transmitter is configured to send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier.

[0119] In a seventh aspect, a communication device is provided, comprising: a transmitter, a receiver, a processor, and a memory, wherein the memory stores a computer program;

[0120] The transmitter is used to send an initial trigger message to an IoT device. The initial trigger message includes at least one of the following: a power status reporting indication, an indication of the IoT device access timing, an indication of the number of paging cycles or access timings, length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, an access type indicator, a network node identifier, and a service identifier.

[0121] The receiver is configured to receive a first message sent by the IoT device, the first message carrying at least one of the power status and the IoT device identifier.

[0122] Eighthly, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0123] Receive an initial trigger message sent by a network node. The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, paging cycle and / or access timing quantity indication, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, network node identifier, and service identifier.

[0124] Send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier.

[0125] Ninthly, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0126] Send an initial trigger message to the Internet of Things (IoT) device. The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, number of paging cycles or access timings, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, network node identifier, and service identifier.

[0127] Receive a first message sent by the IoT device, the first message carrying at least one of the power status and the IoT device identifier.

[0128] Tenthly, a computer program product is provided, including a computer program that, when executed by a processor, implements the Internet of Things (IoT) device management method provided in the embodiments of this application. This method may include:

[0129] Receive an initial trigger message sent by a network node. The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, paging cycle and / or access timing quantity indication, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, network node identifier, and service identifier.

[0130] Send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier.

[0131] Eleventhly, a computer program product is provided, including a computer program that, when executed by a processor, implements the Internet of Things (IoT) device management method provided in the embodiments of this application. This method may include:

[0132] Send an initial trigger message to the Internet of Things (IoT) device. The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, number of paging cycles or access timings, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, network node identifier, and service identifier.

[0133] Receive a first message sent by the IoT device, the first message carrying at least one of the power status and the IoT device identifier.

[0134] The aforementioned IoT device management methods, devices, systems, communication equipment, storage media, and computer program products activate and schedule IoT devices through initial trigger messages sent by network nodes. Based on the network node's instructions, IoT devices can promptly report their power status, enabling network nodes to manage the power status of IoT devices within their coverage area. This allows for flexible time-frequency resource allocation for IoT devices, preventing data packet transmission failures due to power limitations and improving network deployment flexibility and stability. Attached Figure Description

[0135] Figure 1 This is an application environment diagram of an IoT device management method in one embodiment;

[0136] Figure 2 This is a flowchart illustrating an IoT device management method in one embodiment;

[0137] Figure 3 This is a schematic diagram of the first topology in one embodiment;

[0138] Figure 4 This is a schematic diagram of the second topology in one embodiment;

[0139] Figure 5 This is a flowchart illustrating the steps for determining the access type in one embodiment;

[0140] Figure 6 This is a flowchart illustrating the step of receiving the first trigger message in one embodiment;

[0141] Figure 7 This is a schematic diagram of the temporal domain resources corresponding to the initial trigger message frame after sending the initial trigger message in one embodiment;

[0142] Figure 8 This is a flowchart illustrating the step of sending the first message in one embodiment;

[0143] Figure 9 This is a flowchart illustrating the step of storing the service identifier in one embodiment;

[0144] Figure 10 This is a flowchart illustrating the steps for determining the response result based on the business identifier in one embodiment;

[0145] Figure 11 This is a flowchart illustrating the steps for determining the response result based on the business identifier in another embodiment;

[0146] Figure 12 This is a flowchart illustrating the step of sending the second message in one embodiment;

[0147] Figure 13 This is a flowchart illustrating the step of sending a third message in one embodiment;

[0148] Figure 14 This is a flowchart illustrating the step of receiving the first command in one embodiment;

[0149] Figure 15 This is a flowchart illustrating the step of retransmitting the third message in one embodiment;

[0150] Figure 16 This is a flowchart illustrating the step of receiving a second command in one embodiment;

[0151] Figure 17 This is a flowchart illustrating the step of sending a second command response message in one embodiment;

[0152] Figure 18 This is a flowchart illustrating the step of receiving the first message in one embodiment;

[0153] Figure 19 This is a flowchart illustrating the step of sending the first trigger message in one embodiment;

[0154] Figure 20 This is a flowchart illustrating the step of sending the second message in one embodiment;

[0155] Figure 21 This is a flowchart illustrating the step of resending the initial trigger message in one embodiment;

[0156] Figure 22 This is a flowchart illustrating the steps of receiving a third message and scheduling and configuring the command response message in one embodiment.

[0157] Figure 23 This is a flowchart illustrating the step of sending the first command in one embodiment;

[0158] Figure 24 This is a flowchart illustrating the step of sending the second command in one embodiment;

[0159] Figure 25 This is a flowchart illustrating the steps of receiving a second command response message in one embodiment;

[0160] Figure 26 This is a flowchart illustrating the steps of receiving the second command response message in segments in one embodiment;

[0161] Figure 27 This is a flowchart illustrating the steps of triggering a message retransmission mechanism when a second command response message or the first segment of the second command response message is not received in one embodiment.

[0162] Figure 28 This is a flowchart illustrating the steps of receiving a second command response message or triggering the retransmission of the second command response message in one embodiment.

[0163] Figure 29 This is a schematic diagram of an example flow of an IoT device management method in one embodiment;

[0164] Figure 30 This is a structural block diagram of an IoT device management device in one embodiment;

[0165] Figure 31 This is a structural block diagram of an IoT device management device in another embodiment;

[0166] Figure 32 This is an internal structural diagram of a communication device in one embodiment. Detailed Implementation

[0167] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0168] Figure 1 This is a schematic diagram illustrating an application scenario of an IoT device management method provided in an embodiment of this application. For example... Figure 1 As shown, this scenario includes an IoT device 100 and a network node 200. The IoT device 100 and the network node 200 transmit data via a network.

[0169] Among them, the IoT devices 100 can be smart home devices such as smart door locks, door and window sensors, cameras, smoke detectors, leak detectors, smart thermostats, air purifiers, humidifiers, smart curtains, smart refrigerators, robot vacuum cleaners, smart lights, voice assistants, etc.; smart city devices such as smart streetlights, garbage sorting monitors, smart traffic lights, vehicle GPS (Global Positioning System) terminals, electronic license plates, shared bicycle locks, air quality sensors, noise monitoring equipment, water quality testing buoys, etc.; and industrial IoT devices such as industrial sensors, PLCs (Programmable Logic Controllers), predictive maintenance equipment, AGVs (Automated Guided Vehicles). Vehicles (automated guided vehicles), robotic arms, intelligent warehousing robots, smart meters, photovoltaic power generation monitoring equipment, power transmission line fault detectors, etc., can also be used in the medical and health field for portable electrocardiogram monitors, blood glucose meters, smart bracelets (monitoring heart rate and blood oxygen), fall alarms, hearing aids, intelligent infusion pumps, and medical cold chain temperature control tags. In addition, they can be used in the field of smart agriculture for soil temperature and humidity sensors, light intensity detectors, livestock GPS collars, aquatic dissolved oxygen monitors, intelligent irrigation systems, drones, greenhouse climate control equipment, etc.; and they can also be used in the field of vehicle-to-everything (V2X) for on-board diagnostic systems (OBD), tire pressure monitors, charging piles, smart parking locks, and V2X (Vehicle to Everything) roadside units, etc., without limitation.

[0170] Examples of IoT devices include:

[0171] 1. ~1µW peak power consumption with energy storage, initial sampling frequency offset (SFO) up to 10X ppm, no R2D amplification or D2R amplification in the device. The device's D2R transmission is backscattered on an externally provided carrier.

[0172] 2. Peak power consumption ≤ several hundred µW, with energy storage function, initial sampling frequency offset (SFO) up to 10X ppm, and R2D and / or D2R amplification. The device's D2R transmission can be generated internally or backscattered on an externally provided carrier.

[0173] Network node 200 includes any one of a reader and an intermediate node device. The reader includes at least one of a base station of different types, a repeater (e.g., a repeater with IoT device functionality), an IAB integrated access and backhaul node, and a user equipment. The intermediate node device can be a repeater capable of realizing environmental IoT, an IAB node, a user equipment (UE), a regular repeater, etc.

[0174] In traditional technologies, with the development of wireless communication technology, more IoT devices will interconnect to improve productivity, leading to dense deployments and making wireless communication technology in the IoT field more practical. Therefore, reducing the size, complexity, and power consumption of IoT devices has become a current trend. To achieve the deployment of billions or even hundreds of billions of dense IoT devices, future IoT devices may be passive communication devices that do not rely on battery power and do not require manual battery replacement. If the paging process of the network uses rechargeable IoT devices, passive communication IoT devices will miss paging if power is lost during charging, leading to inaccurate statistics and failing to meet the resource inventory requirements of industrial applications. Furthermore, because IoT devices have limited power, and the command response to the reader requires reporting large data packets, insufficient power can easily cause transmission failures.

[0175] Based on the aforementioned traditional technologies, this application provides an IoT device management method. The method activates and schedules IoT devices by sending an initial trigger message from a network node. Based on the network node's instructions, IoT devices can promptly report their power status, allowing the network node to manage the power status of IoT devices within its coverage area. This enables flexible time-frequency resource allocation for IoT devices, avoiding data packet transmission failures due to power limitations and improving network deployment flexibility.

[0176] It should be noted that the beneficial effects or technical problems solved by the embodiments of this application are not limited to this one, but may also be other implicit or related problems. For details, please refer to the description of the embodiments below.

[0177] Before introducing specific embodiments of the present invention, the technical terms involved in the present invention will be explained:

[0178] AIoT: Ambient Internet of Things;

[0179] PDRCH: Physical device-to-reader channel;

[0180] PRDCH: Physical reader-to-device channel;

[0181] R2D: Reader to device;

[0182] RF: Radio frequency;

[0183] RFID: Radio frequency identification.

[0184] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0185] In one embodiment, such as Figure 2 As shown, an IoT device management method is provided, which is applied to... Figure 1 Taking IoT device 100 as an example, the explanation includes the following steps:

[0186] Step 202: Receive the initial trigger message sent by the network node.

[0187] The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, paging cycle and / or access timing quantity indication, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, network node identifier, and service identifier.

[0188] Specifically, the indication of the IoT device access timing is the time-domain and / or frequency-domain resource location that instructs the IoT device to reply to the network node with an initial trigger message or command response message. This access timing is used to inform the IoT device when to access the network. The access timing indicates the specific location where the IoT device accesses the network, and it can replace the function of the first trigger message (R2D trigger message). That is, the notification of IoT device access matters by the R2D trigger message can be accomplished through the IoT device access timing indication information carried in the initial trigger message padding.

[0189] The power status reporting indicator is used to request IoT devices to report their current power status.

[0190] The paging round is used to indicate the time interval at which a network node sends paging messages to an IoT device.

[0191] The Access Count indicator (represented by Q) indicates the number of IoT devices attempting to access the network within a specific time frame.

[0192] The paging ID length info indicates the length of the IoT device identifier to be triggered (or paging ID). This length includes at least one of the following: the overall length of the IoT device identifier to be triggered, the SDU length, and the paging padding length. For group paging (group ID), the length of the corresponding IoT device identifier to be triggered (paging ID) is obtained by masking or truncating the IoT device identifier, retaining only the first or second half of the identifier. Because the size of the IoT device identifier to be triggered in the paging ID is not fixed, it needs to carry the length info.

[0193] The identifier of the IoT device to be triggered is used by network nodes to trigger or select a single IoT device, a single group of IoT devices, or multiple IoT devices not in the same group. If the initial trigger message does not contain the identifier of the IoT device to be triggered, the IoT device instructs all IoT devices that received the initial trigger message to trigger / select the message based on the initial trigger message.

[0194] The access type indicator (1-bit CBRA / CFRA) indicates the access type of IoT devices. The access type indicator includes Contention-Based Random Access (CBRA) and Contention-Free Random Access (CFRA). The access type indicator is a 1-bit indication, where 0 represents CFRA and 1 represents CFRA; or 0 represents CFRA and 1 represents CBRA. Specifically, the access type includes contention-based access and contention-free access.

[0195] The business identifier includes a first business identifier and / or a second business identifier (transaction ID), wherein the first business identifier and the second business identifier respectively identify the business request corresponding to the initial trigger message.

[0196] The network node identifier corresponds to the situation where multiple network nodes send the initial trigger message paging to the same IoT device. The network node identifier is used to identify the network node that sends the paging message to the IoT device.

[0197] In implementation, when an IoT device is in an idle (IDLE) or deep sleep (PSM) state, the network node generates an initial trigger message to page the IoT device. Specifically, after the IoT device completes network registration and enters a managed state (i.e., when the IoT device is in an idle (IDLE) or deep sleep (PSM) state), the network node transmits the initial trigger message via a wireless or wired communication link to page the IoT device. This initial trigger message is typically encapsulated using a lightweight protocol (such as CoAP or LWM2M). The message header of the initial trigger message contains the IoT device identifier of the IoT device to be triggered, ensuring accurate addressing. Furthermore, the payload of the initial trigger message also carries one or more parameters for scheduling and managing the IoT device. These parameters may include: a power status reporting indication, an indication of the IoT device access timing, an indication of the paging cycle and / or the number of access timings, the length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, an access type indication, and a service identifier, etc. Thus, the IoT device can wake up the corresponding processing thread based on the received initial trigger message.

[0198] Step 204: Send the first message to the network node.

[0199] The first message carries at least one of the following: battery status and IoT device identifier.

[0200] In implementation, when an IoT device receives an initial trigger message from a network node, followed by at least one subsequent first trigger message, the IoT device determines whether a response is needed. If a response is required, the IoT device generates a first message based on the instructions in the initial trigger message and sends this first message to the network node. This first message carries the information indicated in the initial trigger message to respond to the network node's paging. Simultaneously, the IoT device stores a service identifier locally, which can be associated with "responded" information to record the response to this paging process. The first message carries at least one of the following: battery status and the IoT device identifier. Thus, upon receiving this first message, the network node can perform appropriate resource scheduling based on the IoT device's battery status.

[0201] The IoT device identifier carried in the first message includes a temporary identifier generated locally by the IoT device (e.g., RN16 or AS ID) and / or the device ID of the IoT device.

[0202] In an optional embodiment, if the access type indicated by the network node is CFRA, the IoT device identifier carried in the first message fed back by the IoT device is the device identifier of the IoT device; if the access type indicated by the network node is CBRA, the IoT device identifier carried in the first message fed back by the IoT device is a temporary identifier locally generated by the IoT device.

[0203] In one embodiment, the network node includes either a reader or an intermediate node device. The intermediate node device includes at least one of a repeater, an IAB integrated access and backhaul node, and a user equipment.

[0204] In the aforementioned IoT device management method, an initial trigger message sent by a network node activates and schedules the IoT device. Based on the network node's instructions, the IoT device can promptly report its power status, enabling the network node to manage the power status of IoT devices within its coverage area. This allows for flexible time-frequency resource allocation for IoT devices, preventing data packet transmission failures due to power limitations and improving network deployment flexibility.

[0205] In an optional embodiment, the topology corresponding to the currently densely deployed IoT network includes a first topology and a second topology, etc. Wherein, for example... Figure 3 As shown, the first topology involves direct bidirectional communication between IoT devices and the base station. In this case, the base station acts as the reader (i.e., network node) in this solution. Communication between the base station and the IoT devices includes environmental IoT data and / or signaling. This first topology includes the possibility that the signals sent by the base station to the IoT devices differ from the signals received by the base station from the IoT devices.

[0206] like Figure 4 As shown, the second topology involves an intermediate node device between the IoT device and the base station. The IoT device communicates bidirectionally with the base station through this intermediate node device (network node). In this case, the intermediate node device is the network node in this solution. This intermediate node device can be a repeater capable of IoT communication, a regular repeater, an IAB node, a user equipment (UE), or a user equipment supporting IoT environmental functions, etc. The intermediate node device transmits IoT data and / or signaling between the base station and the IoT device.

[0207] Thus, for different IoT topologies, if the current network is the first topology, the network node that communicates directly with the IoT device is the reader; if the current network is the second topology, the network node that communicates with the IoT device is the intermediate node device. The IoT device is unaware of whether it communicates directly with the reader or through the intermediate node device.

[0208] In an optional embodiment, if the network node is an intermediate node device, the intermediate node device may include at least one of the following:

[0209] Repeaters, IAB integrated access and backhaul nodes, network controlled relays (NCRs), and user equipment.

[0210] The Network Control Relay (NCR) is a relay node uniformly controlled by the network side (e.g., gNB or core network). It is mainly used to enhance network coverage, improve edge user experience, and increase network deployment flexibility. The most significant characteristic of the NCR is that it is not self-managed but is entirely controlled by the network, emphasizing centralized scheduling and resource management.

[0211] In one embodiment, the device status of an IoT device includes a communication status and a non-communication status; the non-communication status includes a shutdown status and a sleep status; in the communication status, a power status reporting instruction requests power status information of the IoT device based on the power status.

[0212] Specifically, in the operational architecture of an IoT system, the states of IoT devices are divided into two main categories: communication state (also known as available state) and non-communication state (unavailable state). The non-communication state is further subdivided into OFF state and SLEEP state. OFF state means the device is completely offline and does not transmit data or perform any functions. SLEEP state means the device is in a low-power hibernation mode, temporarily ceasing interaction with the network, but retaining a certain wake-up mechanism to quickly resume operation upon receiving specific instructions or meeting preset conditions.

[0213] When an IoT device is in a communication state, that is, an active state in which the IoT device establishes a connection with the network and performs (D2R) data transmission, command interaction, etc., the IoT device will report its power status based on the power status reporting indication so that the network node can read the power status of the IoT device.

[0214] In one embodiment, the power status is the predicted energy status of the IoT device at a future point in time; the power status includes information on the remaining power duration and / or a power status indication.

[0215] Among them, the remaining power duration information is the earliest time when the IoT device monitors the communication transmission between the network node and the IoT device and matches the corresponding R2D trigger after completing the communication transmission between the current IoT device and the network node D2R.

[0216] In one embodiment, the power status is used to indicate whether the IoT device has the energy to perform another communication transmission between the IoT device and the network node.

[0217] In one embodiment, IoT devices can report their battery status to network nodes by including it in uplink messages (msg3 and data transmission). Specifically, during IoT communication interactions, to enable the network to monitor the device's energy status in real time for rational resource allocation and scheduling strategies, IoT devices have the ability to transmit battery status information through specific uplink messages. These uplink messages mainly involve key communication links such as msg3 and data transmission. As an important message in the random access process, msg3 can carry a battery status indication in the initial stage of establishing a connection between the device and the network, allowing the network to understand the device's battery status upon access, thus providing a reference for subsequent resource allocation. In the data transmission stage, IoT devices can also embed the battery status indication, continuously feeding back battery information to network nodes. In this way, network nodes can determine the device's remaining battery level based on the battery status sent by the device. If the device has sufficient battery, more tasks or higher-priority services can be allocated; if the battery is low, strategies can be adjusted promptly to prevent service interruption due to battery depletion, achieving efficient and intelligent management of IoT devices and ensuring the stable operation of the entire IoT system.

[0218] In one embodiment, such as Figure 5 As shown, if the initial trigger message does not carry an access type indicator (CBRA / CFRA), the method may further include:

[0219] Step 502: Determine the access type based on the IoT device identifier to be triggered in the initial trigger message.

[0220] In practice, if the initial trigger message sent by the network node does not carry an access type indicator, but carries an identifier of the IoT device to be triggered, the IoT device will determine the access type based on the identifier of the IoT device to be triggered.

[0221] Optionally, if the initial trigger message does not carry the identifier of the IoT device to be triggered, it indicates that the network node indicates that the IoT device has contention for access; if the IoT identifier to be triggered carried in the initial trigger message is a group device identifier (group ID), it indicates that the network node indicates that the IoT device has contention for access; if the IoT identifier to be triggered carried in the initial trigger message is a single IoT device identifier (device ID), it indicates that the network node indicates that the IoT device has no contention for access. If the IoT device identifier to be triggered carried in the initial trigger message is the IoT device identifier of multiple IoT devices, it indicates that the network node indicates that the IoT device has no contention for access.

[0222] Step 504: Determine the access type based on the access timing and / or the number of access timings in the initial trigger message.

[0223] In practice, if the initial trigger message sent by the network node does not carry an access type indicator, but carries an indication of the access timing and / or the number of access timings for IoT devices, then if the initial trigger message carries the access timing for IoT devices, the IoT device will determine its access type based on the access timing in the initial trigger message. That is, if the initial trigger message carries a one-to-one mapping between IoT devices and access timings, then the IoT device is determined to have contention-free access.

[0224] Alternatively, if the initial trigger message does not carry an indication of the access timing of the IoT device, but instead carries at least one of the following: the period of the trigger message, the number of access timings, and the starting position of the access timing (including frequency point or time slot position), then the IoT device is determined to be in contention for access.

[0225] In this embodiment, the access type is determined by the IoT device identifier, access timing, and / or the number of access timings, thereby achieving differentiated access management and ensuring that heterogeneous devices can efficiently adapt to network resources. Based on the determination of access timing, network load changes can be flexibly responded to, resources can be reasonably allocated and access processes optimized during peak periods to avoid congestion, and device access requests can be quickly responded to during idle periods to improve network utilization.

[0226] In one exemplary embodiment, such as Figure 6 As shown, the method also includes:

[0227] Step 601: Receive at least one first trigger message sent by the network node.

[0228] The first trigger message is used to indicate the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message.

[0229] In implementation, after sending the initial paging message, the network node sends at least one first trigger message (R2D trigger msg) to the IoT device. This first trigger message is related to the resources that subsequently instruct the IoT device to send the first message. The network node sends N (N ≤ access timing) first trigger messages. Specifically, the first trigger message itself can carry frequency domain resource information and / or time domain resource information. In the time domain, such as... Figure 7 As shown, after a network node sends Paging(Q), it sends at least one R2D trigger msg (first trigger message). This first trigger message is immediately followed by the time slot (msg1 slot) where the first message was sent, meaning that the Nth time-domain resource is immediately following the first trigger message. Thus, the starting point of the frequency-domain resource indicated by the first trigger message determines the frequency band occupied by the IoT device's data transmission, helping to avoid signal interference and achieve a reasonable allocation of spectrum resources. The starting point of the time-domain resource clarifies the specific time when the IoT device begins sending data, ensuring that the IoT device's data transmission is synchronized with the network scheduling rhythm, effectively guaranteeing the timeliness and orderliness of data transmission.

[0230] In an optional embodiment, the first trigger message also carries a service identifier, so that in addition to the initial trigger message carrying the service identifier, at least one first trigger message sent by the network node can also carry the service identifier, so that the IoT device can store the service identifier.

[0231] In this embodiment, the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message is indicated by the first trigger message, thereby realizing resource scheduling of the IoT device, determining the frequency band position occupied by the IoT device for data transmission, which helps to avoid signal interference, and also clarifies the access timing of the IoT device, ensuring stable data interaction between the IoT device and the network node.

[0232] In one exemplary embodiment, such as Figure 8 As shown, the power status reporting indicator is used to request IoT devices to report their current power status. The specific processing steps for sending the first message to the network node in step 204 include:

[0233] Step 801: If the initial trigger message contains a power status reporting indication and the IoT device supports power reporting, send a first message carrying the power status to the network node.

[0234] In implementation, if the initial trigger message sent by the network node to the IoT device contains a power status reporting instruction and the IoT device supports power reporting (i.e., the IoT device stores power status), then the IoT device generates a first message containing current power status information based on the power status reporting instruction, and sends the first message to the network node so that the network node can clearly understand the current power status of the IoT device, thereby enabling the network node to flexibly schedule the IoT device.

[0235] Specifically, when an IoT device receives an initial trigger message from a network node, it parses the content contained in that message. If, during the parsing process, the initial trigger message contains a power status reporting instruction, it means that the network node needs to obtain the current power information of the device. At this time, the IoT device activates its power detection module, obtains the current power status of the device, and sends a first message carrying the power status to the network node according to the frequency domain resources and / or time domain resources starting point specified in the initial trigger message.

[0236] In this embodiment, IoT devices report their power status, enabling network nodes to monitor the power status of IoT devices in real time. This allows for reasonable resource scheduling and management, advance planning of IoT device hibernation strategies to reduce energy consumption, or prioritizing data transmission tasks for devices with insufficient power, ensuring the stable operation of the entire IoT system.

[0237] In one exemplary embodiment, such as Figure 9 As shown, the method also includes:

[0238] Step 901: Store the business identifier contained in the initial trigger message and associate the business identifier with the replied information.

[0239] The business identifier is used to identify the business request corresponding to the initial trigger message.

[0240] In practice, the IoT device stores the business identifier carried in the initial trigger message and determines the associated information corresponding to the business identifier as having been replied to.

[0241] Specifically, after an IoT device receives an initial trigger message from a network node, it stores the service identifier contained in the initial trigger message in a specific local storage area. This storage area is dedicated to recording relevant information during the interaction between the IoT device and the network node. Furthermore, the IoT device also establishes a one-to-one mapping between the information it has already replied to the network node and this service identifier, enabling the IoT device to determine whether it has responded to the initial trigger message.

[0242] Optionally, the business identifier serves as a unique identifier for the business request, carrying important information such as the type and priority of the business request corresponding to the initial trigger message.

[0243] Step 902: If the service identifier contained in the initial trigger message is the same as the service identifier stored in the IoT device, and the previous paging process record associated with the service identifier contained in the initial trigger message is an access failure, then the IoT device is determined to be the responding device selected by the initial trigger message.

[0244] In practice, when a new initial trigger message arrives, the IoT device compares and verifies the service identifier carried in it with the service identifier stored locally on the IoT device. If the two match perfectly, the IoT device will further check the historical paging records associated with that service identifier. If it finds that the previous paging process was recorded as an access failure, the IoT device is determined to be the target responding device for this initial trigger message, triggering the subsequent service processing flow. Otherwise, the IoT device does not need to paging for this initial trigger message.

[0245] In this embodiment, by establishing the association information of business identifiers, IoT devices can quickly and accurately retrieve all interaction information related to a specific business request in subsequent processing. This facilitates the traceability, management, and optimization of business processes, ensuring that the entire process of a business request from triggering to completion is traceable and controllable. It also improves the efficiency and reliability of device-network interaction and provides strong support for the orderly operation of the entire IoT system.

[0246] In one exemplary embodiment, such as Figure 10 As shown, the method also includes:

[0247] Step 1001: Determine whether an initial trigger message needs to be replied to based on the business identifier.

[0248] In implementation, since IoT devices receive more than one initial trigger message, a service identifier can be used to record responses to avoid duplicate or missed responses. Specifically, if an IoT device experiences a power outage or malfunction, it cannot respond to the network-side device in a timely manner. Furthermore, power outages or malfunctions will also prevent the IoT device from successfully storing the service identifier. Therefore, the IoT device can use this service identifier to determine whether it needs to reply to the initial trigger message.

[0249] Step 1002: If the IoT device stores a business identifier and the business identifier has no associated information, determine the first response result.

[0250] In practice, for at least one initial trigger message sent by a network node, if the IoT device stores the service identifier carried in the initial trigger message, it indicates that the IoT device has responded to the initial trigger message. The IoT device determines the first response result, which is that it has responded to the initial trigger message and does not need to respond to this initial trigger message.

[0251] Step 1003: If the IoT device does not store a business identifier, determine the second response result.

[0252] In implementation, if an IoT device does not store a service identifier in response to at least one initial trigger message sent by a network node, it indicates that the IoT device has not responded to the initial trigger message and therefore has not stored it. Consequently, the IoT device determines a second response result. This second response result indicates that a response to the current initial trigger message is required.

[0253] In this embodiment, the IoT device determines the response result based on the service identifier. If the service identifier has been stored, it is determined that no response is needed, which can effectively avoid the waste of resources caused by repeatedly processing the same service request and reduce the computing burden of the device and network redundant traffic. On the other hand, timely response to requests that have not stored service identifiers can ensure that new service requests are processed in a timely manner and ensure the integrity of the business process.

[0254] In another exemplary embodiment, such as Figure 11 As shown, IoT devices can also set association information for service identifiers. This association information indicates whether a response has been made to the initial trigger message sent by the network node. Therefore, the method may further include:

[0255] Step 1101: Determine whether an initial trigger message needs to be replied to based on the business identifier.

[0256] In implementation, IoT devices determine whether to respond to the initial trigger message based on the service identifier. Specifically, when an IoT device receives an initial trigger message from a network node, since the service identifier corresponds to the service request, to avoid duplicate or missed responses, the response can be recorded using the service identifier and its associated information. That is, when the IoT device stores the service identifier, it also stores the corresponding associated information. Through this associated information, it determines whether to respond to the initial trigger message carrying the service identifier.

[0257] Step 1102: If the IoT device stores a business identifier and the associated information of the business identifier has been replied to, determine the third response result.

[0258] In implementation, if the IoT device has stored a service identifier and the associated information of the service identifier has been replied to, it indicates that the IoT device has responded to the initial trigger message. The IoT device determines the third response result, which indicates that it has responded to the initial trigger message and does not need to respond to this initial trigger message, thereby avoiding duplicate responses.

[0259] Step 1103: If the IoT device stores a business identifier and the associated information of the business identifier is not responded to, determine the fourth response result.

[0260] In practice, if the IoT device has stored a business identifier and the associated information of the business identifier is unreplyable, then the IoT device does not respond to the initial trigger message. In this case, the IoT device determines the fourth response result, which is that a response to the initial trigger message is required.

[0261] In this embodiment, the IoT device determines the response result based on the service identifier and its associated information. If the associated information of the stored service identifier indicates that a response has been received, it is determined that no response is required. This effectively avoids resource waste caused by repeatedly processing the same service request and reduces the device's computational burden and network redundancy. However, if the associated information of the stored service identifier indicates that a response has not been received, the initial trigger message needs to be responded to in a timely manner. This ensures that new service requests are processed in a timely manner and guarantees the integrity of the business process.

[0262] In one exemplary embodiment, the method further includes:

[0263] Based on the identifier of the IoT device to be triggered, determine whether an initial trigger message needs to be replied to.

[0264] In implementation, based on the IoT device identifier contained in the initial trigger message, it is determined whether the IoT device indicated by the network node includes the current IoT device. Specifically, in the IoT data interaction and device management process, after receiving the initial trigger message, the IoT device extracts the IoT device identifier to be triggered contained in the message. This identifier serves as the device's unique identity and carries the target information of the trigger command. The IoT device initiates a determination mechanism, comparing the IoT device identifier to be triggered with its own IoT device identifier. If the IoT device identifier to be triggered contains its own IoT device identifier, the IoT device determines that it needs to respond to the initial trigger message to promote the subsequent business process; conversely, if the IoT device identifier to be triggered does not contain its own IoT device identifier, the IoT device determines that it does not need to respond to the initial trigger message, thereby avoiding invalid data interaction, optimizing resource utilization efficiency, and ensuring the stability and efficiency of IoT device operation.

[0265] In one exemplary embodiment, such as Figure 12 As shown, the method also includes:

[0266] Step 1201: Receive the second message sent by the network node.

[0267] The second message includes at least one of a segmentation request identifier, an IoT device identifier, an access layer identifier, a command instruction, and associated information, and at least one of the information on time-domain resources and / or frequency-domain resources required by the third message and the transport block size.

[0268] In implementation, after the network node and the IoT device complete paging (i.e., the interaction between the initial trigger message and the first message), the IoT device can receive a second message sent by the network node. This second message is a resource scheduling mechanism performed by the network node on the IoT device based on its battery status. Specifically, to prevent the IoT device from missing paging or data transmission during charging interruptions, and to address transmission failures caused by insufficient battery power but large data packets, the IoT device promptly reports its battery level based on the network node's battery reporting instruction. The network node can then send a second message based on the IoT device's battery status. This second message enables the IoT device to perform corresponding multi-round paging settings, time-frequency resource configuration optimization, and other reasonable resource scheduling and management. IoT devices with insufficient battery power are given priority for data transmission tasks, ensuring the stable operation of the entire IoT system. Therefore, the second message sent by the network-side device includes at least one of the following: segmentation request identifier, IoT device identifier, access layer identifier, command indication, and associated information, as well as information indicating the time-domain and / or frequency-domain resources and / or transport block size required for the IoT device to report a third message.

[0269] The segmentation request identifier included in the second message is used to clarify whether the network node allows the segmented transmission of the third message. If the second message carries this segmentation request identifier, it indicates that the network node allows the segmented transmission of the third message. Thus, when the third message sent by the IoT device carries this segmentation request identifier, the network node can accurately identify data segments, ensuring the integrity and orderliness of data transmission and avoiding information loss and out-of-order delivery. The IoT device identifier carried in the second message is used for conflict resolution. For example, when the access type is CFRA, the second message will carry command indication information to instruct the target IoT device to execute commands. Therefore, the IoT device identifier and the access layer identifier help the network node accurately locate the target (IoT) device, enabling differentiated management and targeted resource allocation, and improving the targeting and efficiency of communication. The command indication clarifies the direction of device operation, ensuring a high degree of consistency between device behavior and network requirements; the associated information facilitates the device to trace the business context and optimize processing logic. The time domain resource, frequency domain resource information, and transport block size required by the third message can guide the device to rationally plan the timing and scale of data transmission.

[0270] In one exemplary embodiment, the associated information included in the second message includes at least one of the following:

[0271] The association information between IoT device identifiers and access layer identifiers.

[0272] Information relating command instructions and access layer identifiers.

[0273] The association information between IoT device identifiers and command instructions.

[0274] The above-mentioned different types of related information are used to clarify different types of business contexts.

[0275] In one exemplary embodiment, a segmentation request identifier is used to indicate whether a network node allows the transmission of a third message segment.

[0276] In one exemplary embodiment, the command instruction included in the second message includes at least one of the following:

[0277] Commands include reading data, writing data, locking data, deleting data, and setting access passwords. Different commands instruct IoT devices to perform different tasks.

[0278] In this embodiment, effective scheduling of IoT devices is achieved by using at least one of the following included in the second message: segmentation request identifier, IoT device identifier, access layer identifier, command indication, and associated information.

[0279] Avoiding network congestion, improving spectrum resource utilization, and ensuring the real-time and stable transmission of data provide strong support for the efficient and reliable operation of IoT systems.

[0280] In one exemplary embodiment, such as Figure 13 As shown, the method also includes:

[0281] Step 1301: Execute the command indicated in the second message.

[0282] In practice, if the second message sent by the network node contains a command instruction, the IoT device will parse and execute the command instruction contained in the second message after receiving the second message. For example, if the command instruction is a read data command, the IoT device will respond to the read data command and read the relevant data.

[0283] Step 1302: Send a third message to the network node.

[0284] The third message contains at least one of the following: an IoT device identifier, a segmented transmission identifier, inventory information, or a command response. The segmented transmission identifier indicates whether more data needs to be reported during subsequent transmissions.

[0285] In implementation, after an IoT device executes a command, it sends a third message to the network node. This third message serves as feedback on the second message, which contains command instructions, sent to the network node. The IoT device identifier enables the network node to quickly and accurately locate the sender, achieving efficient communication between the IoT device and the network node, improving management efficiency and data transmission accuracy. The segmentation transmission identifier indicates whether a bit is the final data bit, preventing data loss and misalignment, and ensuring data integrity and continuity. Specifically, the segmentation transmission identifier is located at the end of the third message, occupying 1 bit, and is used to indicate whether the third message contains complete response information and whether more data needs to be reported subsequently. For example, if the segmentation transmission identifier is 1, it means that the bit containing the segmentation transmission identifier in the currently transmitted third message is not the final data bit, i.e., the current third message is not complete response information, but rather process information of segmented transmission; if the segmentation transmission identifier is 0, it indicates that the bit containing the segmentation transmission identifier in the currently transmitted third message is the final data bit, and the third message transmission is complete. The transmission of inventory information enables network nodes to monitor the status of device resources in real time, facilitating the rational allocation of resources and optimization of system operation. The command response in the third message sent by IoT devices realizes a two-way feedback loop between the device and the network side, ensuring that device operation meets network expectations and enhancing the reliability and stability of system interaction.

[0286] In an optional embodiment, when a network node instructs a third message to be transmitted in segments, the second message sent by the network node to the IoT device must carry a segmentation request identifier, and the third message sent by the IoT device to the network node must also carry a segmentation transmission identifier.

[0287] In an optional embodiment, when the access type indicated by the network node is CFRA (non-contentionable random access), the third message sent by the IoT device to the network node carries a command response.

[0288] In this embodiment, IoT devices execute commands and provide feedback on results based on instructions from network nodes, effectively improving the standardization, efficiency, and anti-interference capabilities of IoT data transmission.

[0289] In one exemplary embodiment, such as Figure 14 As shown, the method also includes:

[0290] Step 1401: If the third message transmission fails, receive the first command sent by the network node or the resent second message.

[0291] The first command indicates that the network node has not received the third message. The retransmitted second message is consistent with the command information in the initially transmitted second message; the first command includes an indication of the scheduling resources required for the retransmission of the third message. Specifically, the scheduling resources required for the retransmission of the third message in the first command include at least one of a time-domain indication, a frequency-domain indication, and a spatial-domain indication.

[0292] In implementation, during the process of an IoT device sending a third message to a network node, the complexity of the wireless communication environment, such as signal interference, network congestion, and channel fading, may cause the third message transmission to fail. If the third message transmission fails, meaning the network node has not successfully received the third message, the network node will send a first command to the IoT device. This first command (NACK, Negative Acknowledgment Message) triggers the IoT device to retransmit, indicating that the network node has not received the third message. Specifically, the network node explicitly informs the IoT device that it has not successfully received the third message through the first command. The first command not only conveys the status of the third message reception failure but also includes resource indication information required for the third message retransmission. This information covers the specific location and range of frequency domain resources and time domain resources required for retransmission, as well as key parameters such as the transport block size. In this way, by receiving the first command sent by the network node and obtaining these resource indications, the IoT device can accurately know when and which network resources to use to retransmit the third message, thereby effectively avoiding further transmission failures, ensuring that data can be successfully delivered to the network node, maintaining the stability of the communication link, and ensuring the integrity of data interaction.

[0293] In another exemplary embodiment, such as Figure 15 As shown, the method also includes:

[0294] Step 1501: Based on the first command, retransmit the third message to the network node.

[0295] In practice, when an IoT device receives the first command sent by a network node, it determines that the network node has not successfully received the third message based on the first command. Then, the IoT device retransmits the third message to the network node based on the resource indications for retransmission of the third message contained in the first command.

[0296] In this embodiment, when the transmission of the third message fails, the network node explicitly notifies the transmission anomaly via a first command. This effectively prevents IoT devices from blindly waiting or repeating invalid operations due to uncertain transmission results, saving device processing resources and energy consumption. Furthermore, the first command includes resource indications for retransmitting the third message, providing precise retransmission instructions to IoT devices. This ensures they accurately use the specified frequency domain, time domain resources, and transmission block size for data retransmission, reducing the probability of conflicts with other data transmissions during retransmission, enhancing the reliability and stability of the communication link, and ensuring the continuity and integrity of the IoT system's business processes.

[0297] In one exemplary embodiment, such as Figure 16 As shown, the method also includes:

[0298] Step 1601: Receive the second command sent by the network node.

[0299] The second command contains scheduling information.

[0300] In practice, if the IoT device successfully sends the third message, the network node can then send a second command to the IoT device to instruct it to perform subsequent operations. Specifically, the second command contains scheduling information.

[0301] In one optional embodiment, the scheduling information includes one or more of the following: command information, the time-frequency resources required for the second command response message, the resource block size, and the offset value. Thus, the IoT device will return a corresponding second command response message based on the resource scheduling of the second command, completing a basic interaction. If the amount of data transmitted is large or the protocol supports segmentation, the IoT device can also send the second command response message back to the network node via segmented transmission; this embodiment does not limit this approach.

[0302] In one exemplary embodiment, the method further includes:

[0303] Step 1602: Based on the scheduling information, generate a data transmission message from the Data Service Data Unit (SDU) field in the second command to the upper layer of the Resource Description Framework (D2R).

[0304] The SDU field is a field that starts from the offset+1th byte. It is indicated by the received data size field of the original upper-layer data SDU field. The SDU field includes all data starting from the received offset value.

[0305] In implementation, IoT devices generate D2R upper-layer data transmission messages based on scheduling information. Specifically, the IoT device determines the Data Service Unit (SDU) field in the second command according to preset protocol rules. This SDU field starts at the offset + 1 byte in the original upper-layer data, and its specific length can be precisely indicated by the received data size field. The SDU field completely contains all data content starting from the offset value (offset) bytes. Then, based on the data in the SDU field, the IoT device encapsulates and converts the data according to the Data to Resource Description Framework (D2R) protocol specifications and data format requirements, ultimately generating an upper-layer data transmission message that conforms to the D2R standard, so as to facilitate accurate and efficient data transmission and interaction between relevant IoT devices.

[0306] In one exemplary embodiment, such as Figure 17 As shown, the method also includes:

[0307] Step 1701: Send a second command response message to the network node or send the second command response message in segments.

[0308] In implementation, when a network node sends a second command to an IoT device, this second command not only contains specific command information but also carries scheduling information for the IoT device to send a second command response message. This includes key configurations such as time-frequency resource allocation, modulation and coding scheme (MCS), and power control parameters. Based on the resource scheduling and instructions of the second command, the IoT device can send a second command response message to the network node, or, in the case of segmented transmission, send the second command response message to the network node in segments, i.e., sending the first segment, the second segment, and so on of the second command response message sequentially.

[0309] Specifically, the IoT device determines the transmission timing based on the time slot offset value (e.g., K2) provided in the second command, maps uplink data according to resource block (RB) allocation information, and sends the second command response message through the PUSCH channel at the specified power level. If the network node has enabled the HARQ mechanism, the IoT device also needs to manage the corresponding retransmission process to ensure reliable data transmission. For large second command response messages that need to be transmitted in segments, the IoT device will interact multiple times according to the segmentation instructions in the command (e.g., segment sequence number, total data length, etc.), sending the first segment of the second command response message, the second segment, and so on, to complete the data transmission segment by segment until all data has been sent and the final confirmation from the network node is received.

[0310] In this embodiment, IoT devices achieve efficient and low-latency command responses based on network node scheduling instructions, which is applicable to various IoT application scenarios and ensures the continuity and integrity of IoT system business processes.

[0311] In one embodiment, if the second command response message or the first segment of the second command response message contains an offset value, then offset = 0.

[0312] Specifically, in the data interaction process, typically when a network node receives a second command response message, it immediately parses and processes the second command response message and its first segment. If an offset value (offset) is detected in the entire content of the second command response message or its first segment, the offset value is set to 0. Setting the offset value to 0 ensures that data is read from a unified and standardized starting position, avoiding confusion in data extraction and parsing due to differences in offset values ​​across different messages, and guaranteeing the consistency and accuracy of the data processing logic.

[0313] In one embodiment, such as Figure 18 As shown, an IoT device management method is provided, which is applied to a network node. The method includes:

[0314] Step 1801: Send an initial trigger message to the IoT device.

[0315] The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, number of paging cycles or access timings, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, network node identifier, and service identifier.

[0316] In implementation, when a network node needs to page an IoT device, it can send an initial trigger message to the IoT device. This initial trigger message not only activates the IoT device but also carries various scheduling indications to clarify information such as the IoT device's power status. This allows the network node to flexibly perform time-frequency resource scheduling, avoiding the problem of IoT devices missing responses due to insufficient power, reducing duplicate responses from IoT devices for the same service, ensuring the flexibility and effectiveness of network optimization strategies, and achieving the management of IoT devices. Specifically, the information indications carried in the initial trigger message, and the function of each information indication, have been described in detail in step 202 of the above embodiments and will not be repeated here.

[0317] Optionally, in one example scenario, most industries require asset identification. Traditional asset identification primarily relies on barcodes and RFID (Radio Frequency Identification). However, both technologies are limited to a few meters of reading range and typically require handheld scanning, leading to labor-intensive and time-consuming operations. The IoT device management method provided in this disclosure allows for management of IoT devices by having network nodes initiate paging. Therefore, when a network node needs to control and manage all or some of the IoT devices, it initiates paging by sending one or more initial trigger messages.

[0318] Step 1802: Receive the first message sent by the IoT device.

[0319] The first message carries at least one of the following: battery status and IoT device identifier.

[0320] In implementation, based on paging of IoT devices, the IoT devices will send an initial message back to the network node. If the initial trigger message carries a power status reporting indication, then the first message received by the network node from the IoT device will contain the current power status of the IoT device. Consequently, the network node can perform time-frequency resource scheduling, etc., based on the power status of the IoT devices.

[0321] In one optional embodiment, the network node can be either a reader or an intermediate node device, depending on the topology. The intermediate node device may include a repeater, an IAB integrated access and backhaul node, a network control trunk (NCR), and a user equipment.

[0322] In implementation, for different topologies, in the first topology, the reader (e.g., a base station) communicates directly with the IoT device. Therefore, the network nodes described in the embodiments of this disclosure are readers, which include various types such as base stations and repeaters. Each type of reader can be applied to the IoT device management method of this disclosure, and the execution process of each type of reader will not be described separately in this embodiment. In the second topology, the reader communicates with the IoT device through an intermediate node device. Therefore, the network nodes described in the embodiments of this disclosure can also be intermediate node devices. That is, the intermediate node device interacts with the IoT device. For different topologies, only the network side needs to interact with messages / signaling, etc., and the IoT device is unaware of this. The characteristics of different topologies have been described in the above embodiments and will not be repeated here.

[0323] In one embodiment, the method further includes:

[0324] Based on the battery status, determine the device status indication of IoT devices.

[0325] The device status indicator is used to indicate whether the IoT device remains in a communication state or transitions to a shutdown / sleep state. The shutdown and sleep states are executed after the current uplink transmission ends or the current paging round ends, and the shutdown and sleep states are non-communication states.

[0326] In implementation, during the operation and management of IoT devices, to achieve efficient resource utilization and energy consumption control, network nodes generate corresponding device status indicators based on the battery status of the IoT devices. The battery status of IoT devices is a key indicator for measuring device operational capability and sustainability. When the IoT device has sufficient battery power, the network node may generate an indicator to keep the IoT device in a communicating state (also known as an available state), enabling it to continuously perform data transmission, command response, and other communication tasks, ensuring smooth operation of business processes. When the IoT device's battery level is low, the network node will determine the device status indicator to transition to either an OFF or SLEEP state according to preset rules. Both OFF and SLEEP states are non-communication states (also known as unavailable states). OFF means the device will stop all operational functions and enter complete hibernation; SLEEP allows the device to operate in a low-power mode, reducing power consumption. These two states are typically executed after the current uplink transmission ends or the current paging round ends. This design avoids data transmission interruption or loss due to sudden power outages or sleep mode, ensuring the integrity and reliability of data interaction. It also effectively extends the device's battery life and improves the overall operating efficiency and stability of IoT network nodes.

[0327] In one implementation, during communication transmission between network nodes and Internet of Things (R2D) devices, the downlink time acquisition signal, the start point indicator section, and the fixed duration of the start point of transmission based on energy or edge detection to consider on-off transmission and the start indicator section include single-cycle single-ON-OFF transmission, single-cycle multiple ON-OFF transmission, and ON-OFF sequence transmission. A single ON-OFF transmission is a high-voltage transmission followed by a low-voltage transmission, where the durations of ON and OFF can be the same or different; multiple ON-OFF transmissions, where different ON and different OFF may have the same or different durations, and different parts may have the same or different durations; the design of the ON-OFF sequence consists of a predefined sequence detected by the start indicator section based on digital correlation.

[0328] In one exemplary embodiment, such as Figure 19 As shown, after paging an IoT device, the network node can allocate resources to the IoT device. Specifically, the method also includes:

[0329] Step 1901: Send at least one first trigger message to the IoT device.

[0330] The first trigger message is used to indicate the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message.

[0331] In implementation, after paging is completed, the network node sends at least one first trigger message (R2D trigger message) to the IoT device to allocate response resources. Specifically, this first trigger message is related to the resources that subsequently instruct the IoT device to send a first message. The network node sends N (N ≤ access time) first trigger messages. The first trigger message itself may carry frequency domain resource information and / or time domain resource information. The first trigger message is immediately followed by the time slot where the first message is located. Therefore, the first trigger message is also used to indicate the frequency domain resources and / or the starting point of the frequency domain resources. Based on the indication of the first trigger message, the allocation and scheduling of response resources for the IoT device are realized, determining the frequency band position occupied by the IoT device for data transmission, which helps to avoid signal interference. Specifically, the relationship of time domain resources for the first trigger message in the time domain has been described in step 601 of the above embodiment and will not be repeated here.

[0332] In one exemplary embodiment, such as Figure 20 As shown, the method also includes:

[0333] Step 2001: Based on the battery status carried in the first message, send a second message to the IoT device.

[0334] The second message is sent when the network node configures the time-frequency resources for the third message.

[0335] In implementation, IoT devices send a first message to the network node. Based on prior instructions from the network node, this first message carries the IoT device's battery status. Thus, the network node, based on the received first message, clearly understands the IoT device's battery status. Furthermore, to prevent IoT devices from missing paging or data transmission during charging interruptions, and to address data transmission failures caused by insufficient battery power, the network node, considering the IoT device's battery status, sends a second message to the IoT device. This second message then enables appropriate multi-round paging settings and time-frequency resource configuration optimization for the IoT device, allowing for reasonable resource scheduling and management. This prioritizes data transmission tasks for IoT devices with insufficient battery power, ensuring the stable operation of the entire IoT system.

[0336] In an optional embodiment, the second message includes at least one of a segmentation request identifier, an IoT device identifier, an access layer identifier, a command indication, and associated information, as well as at least one of information on time-domain and / or frequency-domain resources required by the third message and the transport block size. The role of the specific content information carried in the second message has been described in step 1201 of the above embodiment and will not be repeated here.

[0337] In this embodiment, based on the power status of the IoT device, the time and frequency resources for the IoT device to send the third message are allocated by sending the second message, thereby ensuring the stable operation of the entire IoT system.

[0338] In one exemplary embodiment, such as Figure 21 As shown, during the paging process, the network node monitors whether the paging of the IoT device has been successful. If the network node does not successfully receive the first response message from the IoT device, it will resend the paging message (initial trigger message). Specifically, this method also includes:

[0339] Step 2101: If the first message sent by the IoT device is not received, re-execute the step of sending the initial trigger message to the IoT device.

[0340] During implementation, the network node's management module continuously monitors the receiving channel. If the first message from the IoT device is not detected within the preset timeout period, the network node immediately initiates a retransmission mechanism. First, the network node's device management module re-verifies the integrity and accuracy of the initial trigger message, ensuring that the message carries the correct IoT device identifier, command parameters (power reporting indication, access timing indication, etc.), and relevant verification information. Next, the network node retransmits the initial trigger message to the target IoT device to be triggered via a specified communication protocol. Simultaneously, the network node updates the message transmission log, recording the timestamp and status identifier of this retransmission operation for subsequent tracking and analysis, thereby ensuring a stable communication link between the IoT device and the system.

[0341] In this embodiment, if the first message is not received from the IoT device, the network node will resend the initial trigger message to the target IoT device to be triggered, so as to ensure that the communication link between the target IoT device to be triggered and the network node is successfully established.

[0342] In one exemplary embodiment, such as Figure 22 As shown, after the network node sends the second message to the IoT device, the method further includes:

[0343] Step 2201: Receive the third message sent by the IoT device.

[0344] The third message contains at least one of the following: an IoT device identifier, a segmented transmission identifier, inventory information, or a command response. The segmented transmission identifier is used to indicate whether more data needs to be reported during subsequent transmissions.

[0345] In implementation, after the network node sends the second message to the IoT device, the IoT device executes the command instructions and other indications in the second message. After the command instruction is executed, the IoT device sends a third message to the network node. This third message is a command response to the network node's second message based on the IoT device's battery status. Upon receiving this third message, the network node can continue to allocate resources to the IoT device or continue a new round of command interaction with the IoT device. Specifically, the functions of the IoT device identifier, segmented transmission identifier, inventory information, or command response information in the third message received by the network node have been described in step 1102 of the above embodiments and will not be repeated here.

[0346] Step 2202: Configure and schedule command response messages according to the power status of IoT devices.

[0347] In implementation, network nodes schedule and configure command response messages based on the battery status of IoT devices. Specifically, network nodes determine the battery status information of IoT devices through the battery status reported by the devices. When a device's battery level is high, the network node configures a high-speed processing channel for command response messages, prioritizing and accelerating processing to fully utilize the device's abundant power resources. If the device's battery level is low to medium, the network node automatically adjusts its strategy, employing a low-power scheduling algorithm to merge similar command response messages, reducing transmission frequency and data volume, while lowering message priority to ensure the device prioritizes critical tasks. When an IoT device's battery is nearing depletion, the network node immediately activates an emergency scheduling scheme, retaining only the response configuration for core commands and minimizing device power consumption by optimizing transmission paths and compressing data, ensuring stable operation and critical data transmission under limited power conditions. The scheduling and configuration of IoT devices by the network node will be described in detail in the following embodiments, and will not be elaborated upon here.

[0348] In this embodiment, by receiving third messages, network nodes can accurately identify the identity of IoT devices, clarify the segmented transmission progress, obtain inventory status and command response content, etc. At the same time, network nodes dynamically schedule and configure command response messages in combination with the power status of IoT devices, which not only ensures the integrity and timeliness of data transmission, but also achieves a balance between device power consumption and performance, significantly improving the operating efficiency and stability of the IoT system.

[0349] In one exemplary embodiment, such as Figure 23 As shown, the network node monitors the third message sent by the IoT device. If the network node fails to receive the third message, it will promptly synchronize the information about the unsuccessful reception of the third message to the IoT device to trigger the message retransmission mechanism. Specifically, the method also includes:

[0350] Step 2301: If the third message sent by the IoT device is not received, send the first command or resend the second message to the IoT device.

[0351] The first command indicates that the network node has not received the third message. The retransmitted second message contains the same command information as the initially transmitted second message; the first command includes an indication of the scheduling resources required for the retransmission of the third message.

[0352] In implementation, the complexity of the wireless communication environment, such as signal interference, network congestion, and channel fading, may lead to the failure of third message transmission. Therefore, if the third message sent by the IoT device is not received, the network node sends a first command to the IoT device. This first command indicates that the network node has not received the third message. Based on this first command, the IoT device understands the failure to send the third message and retransmits it to the network node. Alternatively, a second message retransmitted by the network device to the IoT device triggers the IoT device to retransmit the third message to the network device.

[0353] The retransmitted second message contains the same command information as the initially transmitted second message, but the resources it carries are slightly different from those in the initially transmitted second message.

[0354] In an optional embodiment, the first command not only conveys the status of the failure to receive the third message, but also includes scheduling resource indication information required for the retransmission of the third message, wherein the scheduling resources include at least one of time domain indication, frequency domain indication and spatial domain indication.

[0355] This information includes key parameters such as the specific location and range of frequency and time domain resources required for retransmission, and the transport block size. In this way, when an IoT device receives the first command from a network node, it can accurately determine when and which network resources to use to retransmit the third message by acquiring these resource indications. This effectively prevents further transmission failures by the IoT device, ensuring that data is successfully delivered to the network node and maintaining the stability of the communication link and the integrity of data interaction.

[0356] Specifically, the resource indications required for the retransmission of the third message included in the first command include at least one of the following: a segmentation request identifier, an IoT device identifier, an access layer identifier, a command indication, and associated information, as well as information on the time-domain resources and / or frequency-domain resources required by the third message and the transport block size. This disclosure does not limit which specific resource indications are included in the first command.

[0357] In this embodiment, the reliability and efficiency of IoT communication are effectively guaranteed through a clear feedback and resource indication mechanism from network nodes. When a network node fails to receive a third message, it promptly sends a first command. This not only allows IoT devices to quickly become aware of transmission anomalies and avoid task stagnation due to information loss, but also provides clear guidance for IoT devices to retransmit the third message through the carried resource indication, reducing data transmission packet loss rate and ensuring accurate delivery of critical information.

[0358] In one exemplary embodiment, such as Figure 24 As shown, if the network node successfully receives the third message sent by the IoT device, the method further includes:

[0359] Step 2401: Send a second command to the IoT device.

[0360] The second command includes at least one of the following: command information, time-frequency resources required for the second command response message, resource block size, and offset value.

[0361] In implementation, if a network node successfully receives the third message, it can initiate new command interactions with the IoT device. Specifically, the network node sends a second command to the IoT device. This second command includes one or more of the following: command information, the time-frequency resources required for the second command response message, and an offset value. The IoT device will then return a corresponding second command response message based on the resource scheduling of the second command, completing a basic interaction. If the amount of data transmitted is large or the protocol supports segmentation, the IoT device can also send the second command response message back to the network node in segments. The following describes two scenarios: the IoT device transmitting the second command response message to the network node in one go based on its battery status, or transmitting the second command response message in segments.

[0362] Scenario 1, in an exemplary embodiment, such as Figure 25 As shown, the method also includes:

[0363] Step 2501: Receive the second command response message sent by the IoT device.

[0364] In practice, if the IoT device has sufficient power and the current IoT network condition is good, the network node can instruct the IoT device to transmit a second command response message all at once via a second command. In this way, the IoT device, based on the instructions in the second command and its own power status, transmits the second command response message all at once. Upon receiving the second command response message from the IoT device, the network node can perform data recording and subsequent processing operations.

[0365] Scenario 2, in an exemplary embodiment, such as Figure 26 As shown, the method also includes:

[0366] Step 2601: Receive the first segment of the second command response message sent by the IoT device.

[0367] The first segment of information contains a segmentation transmission identifier.

[0368] In implementation, if the IoT device has insufficient power or the current IoT network condition is poor, the network node can instruct the IoT device to transmit the second command response message in segments via a second command to reduce energy consumption and ensure data transmission stability. Thus, the IoT device transmits the second command response message in segments and adds a segmentation identifier to it. When the network node receives the first segment of the second command response message, it recognizes that the bits corresponding to the segmentation identifier are not the final data bits of the data transmission. Therefore, the network node stores the first segment of the second command response message until the entire second command response message has been transmitted.

[0369] In one exemplary embodiment, such as Figure 27 As shown, even if the network node fails to receive the second command response message or the first segment of the second command response message sent by the IoT device, it can still initiate a message retransmission mechanism to trigger the retransmission of the second command response message. This method further includes:

[0370] Step 2701: If the second command response message or the first segment of the second command response message is not received from the IoT device, send the first command to the IoT device or resend the second command.

[0371] In implementation, if a network node does not receive the second command response message or the first segment of the second command response message (i.e., a segmented second command response message) sent by the IoT device, the network node initiates a message retransmission mechanism to send the first command to the IoT device or retransmit the second command. Specifically, the network node can execute the step of sending the first command to the IoT device (offset value offset=0), which clarifies that the network node has not received the segmented information, and allocates resources to the IoT device for sending the second command response message, so that the IoT device can retransmit the segmented information and complete the segmented transmission of the remaining content of the second command response message. Alternatively, if the transmission of the completed second command response message fails, the network node can execute the step of retransmitting the second command to the IoT device, so that the IoT device, based on the trigger of the second command, regenerates the second command response message and transmits it to the network node through segmented transmission or complete transmission.

[0372] In one exemplary embodiment, such as Figure 28 As shown, the method also includes:

[0373] Step 2801: Receive the second segment of the second command response message until the transmission of the second command response message is complete.

[0374] In practice, during the segmented transmission of the second command response message, if a network node successfully receives the first segment of the second command response message, it can continue to receive other segments of the second command response message, that is, it can also receive the second segment, the third segment, and so on, until the transmission of the second command response message is completed.

[0375] Step 2802, otherwise, perform the step of sending the first command to the IoT device or resending the second command.

[0376] In implementation, if the second command response message of an IoT device fails to be transmitted successfully—for example, if a segment of the second command response message (such as the third segment) fails to be transmitted—the network node can also initiate a message retransmission mechanism. This mechanism instructs the IoT device to retransmit the failed segment. Specifically, the network node can send a first command (offset=0) to the IoT device. This first command clarifies that the network node has not received the segment and allocates resources to the IoT device for sending the second command response message. This allows the IoT device to retransmit the segment and complete the segmented transmission of the remaining content of the second command response message. Alternatively, if the transmission of a completed second command response message fails, the network node can resend the second command to the IoT device. This allows the IoT device to regenerate the second command response message based on the triggering of the second command and transmit it to the network node via segmented or complete transmission.

[0377] In this embodiment, the continuous reception of the second command response message ensures the integrity and continuity of data transmission. When the second command response message experiences a transmission anomaly, the step of resending the first command or resending the second command is executed. This allows for timely feedback on transmission problems, clearly informing the IoT device of the transmission anomaly, and giving the IoT device an opportunity to retransmit. This effectively reduces data loss caused by network fluctuations, device failures, and other reasons, thereby improving the reliability and stability of IoT communication.

[0378] In one exemplary embodiment, such as Figure 29 As shown, this disclosure provides an example flow of an IoT device management method, taking a network node as a reader as an example. This example flow includes a signaling interaction process between the IoT device and the reader. The example flow specifically includes:

[0379] Step 2901: The reader sends an initial trigger message (Paging) to the IoT device. This initial trigger message includes at least one of the following: a power status reporting indication, an indication of the IoT device access timing, an indication of the number of paging cycles and / or access timings, the length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, an access type indicator, and a service identifier.

[0380] Step 2902: The reader sends N first trigger messages (R2D trigger msg) to the IoT device, where N ≤ the number of access opportunities and N is a positive integer.

[0381] Step 2903: The IoT device sends a first message (Msg1) to the network node based on the indication in the initial trigger message. The first message carries at least one of the power status and the IoT device identifier.

[0382] Step 2904: The network node sends a second message (Msg2) to the IoT device. The second message contains at least one of the following: a segmentation request identifier, an IoT device identifier, an access layer identifier, a command indication, and associated information, as well as at least one of the following: information on time-domain resources and / or frequency-domain resources required by the third message, and the transport block size.

[0383] Step 2905: The IoT device sends a third message to the network node. The third message contains at least one of the following: IoT device identifier, segmented transmission identifier, inventory information, or command response.

[0384] Step 2906: If the network node does not receive the third message, proceed to step 2907; if the network node receives the third message, proceed to step 2908. Figure 29 (Not shown in the image).

[0385] Step 2907: The network node sends a first command to the IoT device, which includes a resource indication required for the retransmission of the third message. Figure 29 (Not shown in the image).

[0386] Step 2908: The network node sends a second command to the IoT device. The second command includes at least one of the following: command information, time-frequency resources required for the second command response message, resource block size, and offset value.

[0387] Step 2909: Send a second command response message to the network node.

[0388] It should be understood that, although Figures 2 to 6 , Figures 8 to 29The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figures 2 to 6 , Figures 8 to 29 At least some of the steps in the process may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be executed in turn or alternately with other steps or at least some of the steps or stages in other steps.

[0389] In one embodiment, such as Figure 30 As shown, an Internet of Things (IoT) device management device 3000 is provided, including: a first receiving module 3001 and a first transmitting module 3002, wherein:

[0390] The first receiving module 3001 is used to receive an initial trigger message sent by a network node. The initial trigger message includes at least one of the following: a power status reporting indication, an indication of the access timing for IoT devices, an indication of the number of paging cycles and / or access timings, length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, a network node identifier access type indicator, and a service identifier.

[0391] The first sending module 3002 is used to send a first message to a network node, the first message carrying at least one of the power status and the IoT device identifier.

[0392] In one embodiment, the IoT device identifier includes a temporary identifier generated locally by the IoT device and / or the device identifier of the IoT device.

[0393] In one embodiment, the network node includes either a reader or an intermediate node device.

[0394] In one embodiment, the intermediate node device includes a repeater, an IAB integrated access and backhaul node, a network control trunk (NCR), and a user equipment.

[0395] In one embodiment, a power status reporting indication is used to request the power status of an IoT device.

[0396] In one embodiment, the power status is the predicted power status of the IoT device at the present or a first future point in time;

[0397] Battery status includes communication status duration information and / or battery status indication;

[0398] Among them, the communication status duration information is the monitoring of the communication transmission from the network node to the IoT device after the IoT device has completed the communication transmission sent from the current IoT device to the network node.

[0399] In one embodiment, the power status is used to indicate whether the IoT device has the energy to perform a second round of communication transmission between the IoT device and the network node.

[0400] In one embodiment, the indication of when an IoT device accesses the network is the time-domain and / or frequency-domain resource location that instructs the IoT device to reply to the network node with an initial trigger message or command response message.

[0401] In one embodiment, the length information of the IoT device identifier to be triggered is used to indicate the length of the IoT device identifier to be triggered;

[0402] The length information includes at least one of the following: the overall length of the IoT device identifier to be triggered, the length of the Service Data Unit (SDU), and the paging length.

[0403] In one embodiment, the IoT device identifier to be triggered is used by the network node to trigger or select a single IoT device, a single group of IoT devices, or multiple non-grouped IoT devices;

[0404] If the initial trigger message does not contain the identifier of the IoT device to be triggered, the initial trigger message is used to instruct / select all IoT devices that have received the initial trigger message.

[0405] In one embodiment, the access type indicator is used to indicate the access type of the Internet of Things (IoT) device;

[0406] Access type indicators include contention-based random access and non-contention-based random access;

[0407] Access types include contention-based access and non-contention-based access.

[0408] In one embodiment, if the initial trigger message does not carry an access type indicator, the device 3000 further includes:

[0409] The first discrimination module is used to determine the access type based on the identifier of the IoT device to be triggered in the initial trigger message; or,

[0410] The second discrimination module is used to determine the access type based on the access timing and / or the number of access timings in the initial trigger message.

[0411] In one embodiment, the device 3000 further includes:

[0412] The second receiving module is used to receive at least one first trigger message sent by the network node. The first trigger message is used to indicate the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message.

[0413] In one embodiment, the first trigger message also carries a service identifier.

[0414] In one embodiment, the power status reporting indication is used to request the IoT device to report its current power status, and the first sending module 3002 is specifically used for:

[0415] If the initial trigger message contains a power status reporting indication and the IoT device supports power reporting, a first message carrying the power status is sent to the network node.

[0416] In one embodiment, the device 3000 further includes:

[0417] The storage module is used to store the business identifier contained in the initial trigger message and associate the business identifier with the responded information; wherein, the business identifier is used to identify the business request corresponding to the initial trigger message;

[0418] The first determining module is used to determine that the IoT device is the responding device selected by the initial trigger message if the service identifier contained in the initial trigger message is the same as the service identifier stored in the IoT device, and the previous paging process record associated with the service identifier contained in the initial trigger message is an access failure.

[0419] In one embodiment, the device 3000 further includes:

[0420] The third discrimination module is used to determine whether an initial trigger message needs to be replied to based on the business identifier;

[0421] The second determining module is used to determine the first response result if the IoT device stores a business identifier and the business identifier has no associated information. The first response result is that the initial trigger message has been responded to and there is no need to respond to this initial trigger message.

[0422] The third determining module is used to determine the second response result if the IoT device does not store a business identifier. The second response result is that a response is required to the initial trigger message.

[0423] In one embodiment, the device 3000 further includes:

[0424] The fourth discrimination module is used to determine whether an initial trigger message needs to be replied to based on the business identifier;

[0425] The fourth determining module is used to determine the third response result if the IoT device stores a business identifier and the associated information of the business identifier has been replied to. The third response result is that the initial trigger message has been responded to and there is no need to respond to this initial trigger message.

[0426] The fifth determining module is used to determine the fourth response result if the IoT device stores a business identifier and the associated information of the business identifier has not been responded to. The fourth response result is that a response is required to the initial trigger message.

[0427] In one embodiment, the device 3000 further includes:

[0428] The fifth discrimination module is used to determine whether it is necessary to reply to the initial trigger message based on the identifier of the IoT device to be triggered.

[0429] In one embodiment, the device 3000 further includes:

[0430] The third receiving module is used to receive a second message sent by a network node. The second message includes at least one of a segmentation request identifier, an IoT device identifier, an access layer identifier, a command instruction, and associated information, as well as at least one of information on time-domain resources and / or frequency-domain resources required by the third message and the transport block size.

[0431] In one embodiment, the association information includes at least one of the following:

[0432] Association information between IoT device identifiers and access layer identifiers;

[0433] Information relating command instructions and access stratum identifiers;

[0434] The association information between IoT device identifiers and command instructions.

[0435] In one embodiment, a segmentation request identifier is used to indicate whether a network node allows the transmission of a third message segment.

[0436] In one embodiment, the command instruction includes at least one of the following:

[0437] Commands for reading data, writing data, locking data, deleting data, and setting access passwords.

[0438] In one embodiment, the device 3000 further includes:

[0439] The execution module is used to execute the commands indicated in the second message;

[0440] The second sending module is used to send a third message to the network node. The third message contains at least one of the following: IoT device identifier, segmented transmission identifier, inventory information, or command response.

[0441] The segmentation transmission identifier is used to indicate whether more data needs to be reported during subsequent transmissions.

[0442] In one embodiment, the device 3000 further includes:

[0443] The fourth receiving module is used to receive a first command sent by the network node or a retransmitted second message if the transmission of the third message fails; the first command is used to indicate that the network node has not received the third message; the retransmitted second message is consistent with the command information in the initially transmitted second message;

[0444] The first command contains an indication of the scheduling resources required for the retransmission of the third message;

[0445] The scheduling resources include at least one of time-domain indication, frequency-domain indication, and spatial-domain indication.

[0446] In one embodiment, the device 3000 further includes:

[0447] The third sending module is used to retransmit the third message to the network node based on the first command.

[0448] In one embodiment, the device 3000 further includes:

[0449] The fifth receiving module is used to receive the second command sent by the network node; the second command contains scheduling information.

[0450] In one embodiment, the scheduling information included in the second command includes at least one of the following: command information, time-frequency resources required for the second command response message, resource block size, and offset value.

[0451] In one embodiment, the device 3000 further includes:

[0452] The generation module is used to generate data for the Data Service Data Unit (SDU) field in the second command to the upper layer of the Resource Description Framework (D2R) based on the scheduling information.

[0453] The SDU field is a field that starts from the offset+1th byte. It is indicated by the received data size field of the original upper-layer data SDU field. The SDU field includes all data starting from the received offset value.

[0454] In one embodiment, the device 3000 further includes:

[0455] The fourth sending module is used to send the second command response message to the network node or send the second command response message in segments.

[0456] In one embodiment, if the second command response message or the first segment of the second command response message contains an offset value, then offset = 0.

[0457] In one embodiment, such as Figure 31 As shown, an Internet of Things (IoT) device management device 3100 is provided, including: a first transmitting module 3101 and a first receiving module 3102, wherein:

[0458] The first sending module 3101 is used to send an initial trigger message to an IoT device. The initial trigger message includes at least one of the following: a power status reporting indication, an indication of the IoT device access timing, an indication of the number of paging cycles or access timings, length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, an access type indicator, a network node identifier, and a service identifier.

[0459] The first receiving module 3102 is used to receive a first message sent by an IoT device, the first message carrying at least one of a power status and an IoT device identifier.

[0460] In one embodiment, the network node includes either a reader or an intermediate node device.

[0461] In one embodiment, the intermediate node device includes a repeater, an IAB integrated access and backhaul node, a network control trunk (NCR), and a user equipment.

[0462] In one embodiment, the device 3100 further includes:

[0463] The determination module is used to determine the device status indication of IoT devices based on the battery status.

[0464] The device status indicator is used to indicate whether the IoT device remains in a communication state or transitions to a shutdown / sleep state. The shutdown and sleep states are executed after the current uplink transmission ends or the current paging round ends, and the shutdown and sleep states are non-communication states.

[0465] In one embodiment, the device 3100 further includes:

[0466] The second sending module is used to send at least one first trigger message to the Internet of Things (IoT) device. The first trigger message is used to indicate the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message.

[0467] In one embodiment, the device 3100 further includes:

[0468] The third sending module is used to send a second message to the IoT device based on the power status carried in the first message. The second message is a message sent when the network node configures the time and frequency resources of the third message.

[0469] In one embodiment, the second message includes at least one of a segmentation request identifier, an IoT device identifier, an access layer identifier, a command instruction, and associated information, as well as at least one of information on time-domain resources and / or frequency-domain resources required by the third message and the transport block size.

[0470] In one embodiment, the device 3100 further includes:

[0471] The execution module is used to re-execute the step of sending the initial trigger message to the IoT device if the first message is not received from the IoT device.

[0472] In one embodiment, the device 3100 further includes:

[0473] The second receiving module is used to receive a third message sent by an IoT device. The third message contains at least one of an IoT device identifier, a segmented transmission identifier, inventory information, or a command response. The segmented transmission identifier is used to indicate whether more data needs to be reported during subsequent transmission.

[0474] The command response messages are scheduled and configured based on the power status of IoT devices.

[0475] In one embodiment, the device 3100 further includes:

[0476] The fourth sending module is used to send a first command or resend a second message to the IoT device if the third message sent by the IoT device is not received. The first command is used to indicate that the network node has not received the third message. The resent second message is consistent with the command information in the initially transmitted second message.

[0477] The first command contains an indication of the scheduling resources required for the retransmission of the third message;

[0478] The scheduling resources include at least one of time-domain indication, frequency-domain indication, and spatial-domain indication.

[0479] In one embodiment, the resource indication required for the retransmission of the third message included in the first command includes at least one of the following:

[0480] Information on the time-domain and / or frequency-domain resources required by the third message and the transport block size, including at least one of the segmentation request identifier, IoT device identifier, access layer identifier, command indication and associated information.

[0481] In one embodiment, the second receiving module is specifically used to send a second command to the Internet of Things device. The second command includes at least one of command information, time-frequency resources required for the second command response message, resource block size, and offset value.

[0482] In one embodiment, the device 3100 further includes:

[0483] The third receiving module is used to receive the second command response message or the second command response message sent in segments by the IoT device.

[0484] In one embodiment, the device 3100 further includes:

[0485] The fourth receiving module is used to receive the first segment of the second command response message sent by the IoT device. The first segment contains a segmented transmission identifier.

[0486] In one embodiment, the device 3100 further includes:

[0487] The fifth sending module is used to send a first command or resend a second command to the IoT device if it does not receive a second command response message or the first segment of the second command response message sent by the IoT device.

[0488] In one embodiment, the device 3100 further includes:

[0489] The fifth receiving module is used to receive the second segment of the second command response message until the transmission of the second command response message is complete;

[0490] Otherwise, proceed with the steps of sending the first command to the IoT device or resending the second command.

[0491] Specific limitations regarding the IoT device management device can be found in the limitations of the IoT device management method described above, and will not be repeated here. Each module in the aforementioned IoT device management device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0492] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0493] Receive an initial trigger message sent by a network node. The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, paging cycle and / or number of access timings, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator and service identifier.

[0494] Send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier.

[0495] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0496] The access type is determined based on the identifier of the IoT device to be triggered in the initial trigger message; or,

[0497] The access type is determined based on the access timing and / or the number of access timings in the initial trigger message.

[0498] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0499] Receive at least one first trigger message sent by a network node, wherein the first trigger message is used to indicate the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message.

[0500] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0501] If the initial trigger message contains a power status reporting indication and the IoT device supports power reporting, a first message carrying the power status is sent to the network node.

[0502] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0503] Store the business identifier contained in the initial trigger message and associate the business identifier with the responded information; the business identifier is used to identify the business request corresponding to the initial trigger message;

[0504] If the service identifier contained in the initial trigger message is the same as the service identifier stored in the IoT device, and the previous paging process record associated with the service identifier contained in the initial trigger message is an access failure, then the IoT device is determined to be the responding device selected by the initial trigger message.

[0505] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0506] Based on the business identifier, determine whether it is necessary to reply to the initial trigger message;

[0507] If the IoT device stores a business identifier and the business identifier has no associated information, the first response result is determined. The first response result is that the initial trigger message has been responded to and there is no need to respond to this initial trigger message.

[0508] If the IoT device does not store a business identifier, the second response result is determined, which is that a response is required to the initial trigger message.

[0509] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0510] Based on the business identifier, determine whether it is necessary to reply to the initial trigger message;

[0511] If the IoT device stores a business identifier and the associated information of the business identifier has been responded to, the third response result is determined. The third response result indicates that the initial trigger message has been responded to and there is no need to respond to this initial trigger message.

[0512] If the IoT device stores a business identifier and the associated information of the business identifier is unanswered, the fourth response result is determined, which means that a response is required to the initial trigger message.

[0513] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0514] The receiver receives a second message sent by a network node. The second message contains at least one of a segmentation request identifier, an IoT device identifier, an access layer identifier, a command instruction, and associated information, as well as at least one of information on time-domain resources and / or frequency-domain resources required by the third message and the transport block size.

[0515] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0516] Execute the command indicated in the second message;

[0517] Send a third message to a network node, the third message containing at least one of an IoT device identifier, a segmented transmission identifier, inventory information, or a command response;

[0518] The segmentation transmission identifier is used to indicate whether more data needs to be reported during subsequent transmissions.

[0519] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0520] If the third message transmission fails, the receiving network node sends a first command, which indicates that the network node has not received the third message.

[0521] The first command contains resource instructions required for the retransmission of the third message.

[0522] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0523] Based on the first command, the third message is retransmitted to the network node.

[0524] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0525] Receive a second command sent by the network node; the second command contains scheduling information.

[0526] The scheduling information included in the second command includes at least one of the following: command information, time-frequency resources required for the second command response message, resource block size, and offset value.

[0527] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0528] Based on the scheduling information, generate a data transmission message from the upper layer of the Resource Description Framework (D2R) to the Data Service Data Unit (SDU) field in the second command.

[0529] The SDU field is a field that starts from the offset+1th byte. It is indicated by the received data size field of the original upper-layer data SDU field. The SDU field includes all data starting from the received offset value.

[0530] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0531] Send a second command response message or the first segment of a second command response message to the network node.

[0532] In one embodiment, an Internet of Things (IoT) device management system is provided, the IoT device management system including IoT devices and network nodes, wherein:

[0533] An Internet of Things (IoT) device is configured to receive an initial trigger message sent by a network node, the initial trigger message including at least one of the following: a power status reporting indication, an indication of the IoT device access timing, a paging cycle and / or the number of access timings, length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, an access type indicator, a network node identifier, and a service identifier; and to send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier.

[0534] Network nodes are used to send initial trigger messages to IoT devices and receive the first messages sent by IoT devices.

[0535] In one embodiment, a communication device is provided, see [link to previous document]. Figure 32 . Figure 32 This is a schematic diagram of the structure of the terminal device provided in an embodiment of the present invention. Figure 32 The terminal device 3200 shown includes at least one processor 3201, a memory 3202, at least one network interface 3204, and a user interface 3203. The various components in the terminal device 3200 are coupled together via a bus system 3205. It is understood that the bus system 3205 is used to implement communication between these components. In addition to a data bus, the bus system 3205 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in… Figure 1 Various buses are designated as bus system 3205. Additionally, this embodiment of the invention includes a transceiver 3206, which may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

[0536] The user interface 3203 may include a display, keyboard, or clicking device (e.g., mouse, trackball, touchpad, or touchscreen).

[0537] It is understood that the memory 3202 in the embodiments of the present invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 3202 of the systems and methods described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0538] In some implementations, memory 3202 stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 32021 and application program 32022.

[0539] The operating system 32021 includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application program 32022 includes various applications, such as a media player and a browser, used to implement various application functions. The program implementing the method of this embodiment can be included in the application program 32022.

[0540] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the following steps:

[0541] Receive an initial trigger message sent by a network node. The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, paging cycle and / or number of access timings, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, and service identifier.

[0542] Send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier.

[0543] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0544] The access type is determined based on the IoT device identifier to be triggered in the initial trigger message; or,

[0545] The access type is determined based on the access timing in the initial trigger message.

[0546] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0547] Receive at least one first trigger message sent by the network node, wherein the first trigger message is used to indicate the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message.

[0548] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0549] If the initial trigger message contains a power status reporting indication, a first message carrying the power status is sent to the network node.

[0550] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0551] Store the business identifier contained in the initial trigger message, and associate the business identifier with the responded information;

[0552] The business identifier is used to identify the business request corresponding to the initial trigger message.

[0553] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0554] Based on the business identifier, determine whether it is necessary to reply to the initial trigger message;

[0555] If the IoT device stores a business identifier and the business identifier has no associated information, the first response result is determined. The first response result is that the initial trigger message has been responded to and there is no need to respond to this initial trigger message.

[0556] If the IoT device does not store a business identifier, the second response result is determined, which is that a response is required to the initial trigger message.

[0557] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0558] Based on the business identifier, determine whether it is necessary to reply to the initial trigger message;

[0559] If the IoT device stores a business identifier and the associated information of the business identifier has been responded to, the third response result is determined. The third response result indicates that the initial trigger message has been responded to and there is no need to respond to this initial trigger message.

[0560] If the IoT device stores a business identifier and the associated information of the business identifier is unanswered, the fourth response result is determined, which means that a response is required to the initial trigger message.

[0561] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0562] The receiver receives a second message sent by a network node. The second message contains at least one of a segmentation request identifier, an IoT device identifier, an access layer identifier, a command instruction, and associated information, as well as at least one of information on time-domain resources and / or frequency-domain resources required by the third message and the transport block size.

[0563] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0564] Execute the command indicated in the second message;

[0565] Send a third message to a network node, the third message containing at least one of an IoT device identifier, a segmented transmission identifier, inventory information, or a command response;

[0566] The segmentation identifier is used to indicate whether the bit identified by the segmentation identifier is the final data bit.

[0567] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0568] If the third message transmission fails, the receiving network node sends a first command, which indicates that the network node has not received the third message.

[0569] The first command contains resource instructions required for the retransmission of the third message.

[0570] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0571] Based on the first command, the third message is retransmitted to the network node.

[0572] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0573] Receive a second command sent by a network node; the second command includes at least one of the following: command information, time-frequency resources required for the second command response message, and offset value.

[0574] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0575] Send a second command response message to the network node.

[0576] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0577] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0578] The above embodiments merely illustrate several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for managing Internet of Things (IoT) devices, characterized in that, The method is applied to Internet of Things (IoT) devices, and the method includes: Receive an initial trigger message sent by a network node. The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, paging cycle and / or access timing quantity indication, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, network node identifier, and service identifier. Send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier.

2. The method according to claim 1, characterized in that, The IoT device identifier includes a temporary identifier generated by the IoT device and / or the device identifier of the IoT device.

3. The method according to claim 1, characterized in that, The network node includes either a reader or an intermediate node device; The network node has the communication function to communicate with the Internet of Things device; The reader is used to send and receive signals with the IoT device.

4. The method according to claim 3, characterized in that, The intermediate node devices include repeaters, IAB integrated access and backhaul nodes, network control relays (NCRs), and user equipment.

5. The method according to claim 1, characterized in that, The power status reporting indication is used to request IoT devices to report their current power status information.

6. The method according to claim 1, characterized in that, The power status is the predicted power status of the IoT device at the present or a first future point in time. The power status includes communication status duration information and / or power status indication; The communication status duration information refers to the monitoring of communication transmission from the network node to the IoT device after the IoT device completes the current communication transmission sent to the network node.

7. The method according to claim 6, characterized in that, The power status is used to indicate whether the IoT device has the energy to perform a second round of communication transmission between the IoT device and the network node.

8. The method according to claim 1, characterized in that, The indication of when an IoT device accesses the network is to instruct the IoT device to reply to the network node with the time-domain and / or frequency-domain resource location of the initial trigger message or command response message.

9. The method according to claim 1, characterized in that, The length information of the IoT device identifier to be triggered is used to indicate the length of the IoT device identifier to be triggered. The length information includes at least one of the following: the overall length of the IoT device identifier to be triggered, the length of the Service Data Unit (SDU), and the paging length.

10. The method according to claim 1, characterized in that, The IoT device identifier to be triggered is used by the network node to trigger or select a single IoT device, a single group of IoT devices, or multiple non-group IoT devices. If the initial trigger message does not contain the identifier of the IoT device to be triggered, the initial trigger message is used to instruct / select all IoT devices that have received the initial trigger message.

11. The method according to claim 1, characterized in that, The access type indicator is used to indicate the access type of the IoT device; The access type indicator includes contention-based random access and non-contention-based random access; The access types include contention-based access and contention-free access.

12. The method according to claim 1, characterized in that, If the initial trigger message does not carry the access type indicator, the method further includes: The access type is determined based on the IoT device identifier to be triggered in the initial trigger message; or, The access type is determined based on the access timing and / or the number of access timings in the initial trigger message.

13. The method according to claim 1, characterized in that, The method further includes: Receive at least one first trigger message sent by the network node, wherein the first trigger message is used to indicate the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message.

14. The method according to claim 13, characterized in that, The first trigger message also carries a business identifier.

15. The method according to claim 1, characterized in that, Sending the first message to the network node includes: If the initial trigger message contains a power status reporting indication and the IoT device supports power reporting, a first message carrying the power status is sent to the network node.

16. The method according to claim 1, characterized in that, The method further includes: The service identifier contained in the initial trigger message is stored; wherein the service identifier is used to identify the service request corresponding to the initial trigger message; If the service identifier contained in the initial trigger message is the same as the service identifier stored in the IoT device, and the previous paging process record associated with the service identifier contained in the initial trigger message is an access failure, then the IoT device is determined to be the responding device selected by the initial trigger message.

17. The method according to claim 16, characterized in that, The method further includes: Based on the business identifier, determine whether it is necessary to reply to the initial trigger message; If the IoT device stores the service identifier and the service identifier has no associated information, a first response result is determined. The first response result is that the initial trigger message has been responded to and there is no need to respond to this initial trigger message. If the IoT device does not store the service identifier, a second response result is determined, which indicates that a response is required to the initial trigger message.

18. The method according to claim 16, characterized in that, The method further includes: Based on the business identifier, determine whether it is necessary to reply to the initial trigger message; If the IoT device stores a service identifier and the associated information of the service identifier has been responded to, a third response result is determined. The third response result indicates that the initial trigger message has been responded to and there is no need to respond to this initial trigger message. If the IoT device stores the service identifier and the associated information of the service identifier is unanswered, a fourth response result is determined, which means that a response is required to the initial trigger message.

19. The method according to claim 1, characterized in that, The method further includes: Based on the identifier of the IoT device to be triggered, determine whether it is necessary to reply to the initial trigger message.

20. The method according to claim 1, characterized in that, The method further includes: The network node sends a second message, which includes at least one of a segmentation request identifier, an IoT device identifier, an access layer identifier, a command instruction, and associated information, as well as at least one of information on time-domain resources and / or frequency-domain resources required by the third message and the transport block size.

21. The method according to claim 20, characterized in that, The associated information includes at least one of the following: The association information between the IoT device identifier and the access layer identifier; The command indicates the association information between the access layer identifier and the access layer identifier; The association information between the IoT device identifier and the command indication.

22. The method according to claim 20, characterized in that, The segmentation request identifier is used to indicate whether the network node allows the transmission of third message segments.

23. The method according to claim 20, characterized in that, The command instruction includes at least one of the following: Commands for reading data, writing data, locking data, deleting data, and setting access passwords.

24. The method according to claim 20, characterized in that, The method further includes: Execute the command indicated by the command described in the second message; Send a third message to the network node, the third message containing at least one of the IoT device identifier, segmented transmission identifier, inventory information, or command response; The segmented transmission identifier is used to indicate whether more data needs to be reported during subsequent transmissions.

25. The method according to claim 24, characterized in that, The method further includes: If the transmission of the third message fails, the network node receives a first command or a retransmitted second message; the first command indicates that the network node has not received the third message, and the retransmitted second message is consistent with the command information in the initially transmitted second message; The first command includes an indication of the scheduling resources required for the retransmission of the third message; The scheduling resources include at least one of time-domain indication, frequency-domain indication, and spatial-domain indication.

26. The method according to claim 25, characterized in that, The method further includes: Based on the first command, the third message is retransmitted to the network node.

27. The method according to claim 24, characterized in that, The method further includes: Receive a second command sent by the network node; the second command contains scheduling information; The scheduling information included in the second command includes at least one of the following: command information, time-frequency resources required for the second command response message, resource block size, and offset value.

28. The method according to claim 27, characterized in that, The method further includes: Based on the scheduling information, a data transmission message is generated for the Data Service Data Unit (SDU) field in the second command to the upper layer of the Resource Description Framework (D2R). The SDU field is a field starting from the offset+1th byte, indicated by the received data size field of the original upper-layer data SDU field, and includes all data starting from the received offset value.

29. The method according to claim 27, characterized in that, The method further includes: Send a second command response message to the network node or send the second command response message in segments.

30. The method according to claim 29, characterized in that, If the second command response message or the first segment of the second command response message contains an offset value, then offset = 0.

31. A method for managing Internet of Things (IoT) devices, characterized in that, The method is applied to a network node, and the method includes: Send an initial trigger message to the Internet of Things (IoT) device. The initial trigger message includes at least one of the following: power status reporting indication, indication of IoT device access timing, number of paging cycles or access timings, length information of the IoT device identifier to be triggered, IoT device identifier to be triggered, access type indicator, network node identifier, and service identifier. Receive a first message sent by the IoT device, the first message carrying at least one of the power status and the IoT device identifier.

32. The method according to claim 31, characterized in that, The network node includes either a reader or an intermediate node device; The network node has the communication function to communicate with the Internet of Things device; The reader is used to send and receive signals with the IoT device.

33. The method according to claim 32, characterized in that, The intermediate node devices include repeaters, IAB integrated access and backhaul nodes, network control relays (NCRs), and user equipment.

34. The method according to claim 31, characterized in that, The method further includes: Based on the battery status, determine the device status indication of the IoT device; The device status indicator is used to indicate whether the IoT device remains in a communication state or transitions to a shutdown / sleep state. The shutdown state and the sleep state are executed after the current uplink transmission ends or the current paging round ends, and the shutdown state and the sleep state are non-communication states.

35. The method according to claim 31, characterized in that, The method further includes: Send at least one first trigger message to the IoT device, wherein the first trigger message is used to indicate the starting point of the frequency domain resources and / or time domain resources used by the IoT device to send the first message.

36. The method according to claim 31, characterized in that, After receiving the first message sent by the IoT device, the method further includes: Based on the battery status carried in the first message, a second message is sent to the IoT device. The second message is a message sent when the network node configures the time-frequency resources of the third message.

37. The method according to claim 36, characterized in that, The second message includes at least one of a segmentation request identifier, an IoT device identifier, an access layer identifier, a command instruction, and associated information, as well as at least one of the information on time-domain resources and / or frequency-domain resources required by the third message and the transport block size.

38. The method according to claim 31, characterized in that, The method further includes: If the first message sent by the IoT device is not received, the step of sending the initial trigger message to the IoT device is repeated.

39. The method according to claim 36, characterized in that, The method further includes: The system receives a third message sent by the IoT device, the third message containing at least one of the IoT device identifier, segmented transmission identifier, inventory information, or command response; the segmented transmission identifier is used to indicate whether more data needs to be reported during subsequent transmission. The command response messages are scheduled and configured based on the power status of the IoT devices.

40. The method according to claim 36, characterized in that, The method further includes: If the third message sent by the IoT device is not received, a first command or a retransmitted second message is sent to the IoT device. The first command is used to indicate that the network node has not received the third message. The retransmitted second message is consistent with the command information in the initially transmitted second message. The first command includes an indication of the scheduling resources required for the retransmission of the third message; The scheduling resources include at least one of time-domain indication, frequency-domain indication, and spatial-domain indication.

41. The method according to claim 39, characterized in that, The step of scheduling and configuring command response messages based on the power status of the IoT device includes: Send a second command to the IoT device. The second command includes at least one of the following: command information, time-frequency resources required for the second command response message, resource block size, and offset value.

42. The method according to claim 41, characterized in that, The method further includes: Receive a second command response message or a segmented second command response message sent by the IoT device.

43. The method according to claim 41, characterized in that, The method further includes: The first segment of information received from the second command response message sent by the IoT device includes the segmented transmission identifier.

44. The method according to claim 41, characterized in that, The method further includes: If the second command response message or the first segment of the second command response message is not received from the IoT device, the first command is sent to the IoT device or the second command is resent.

45. The method according to claim 43, characterized in that, The method further includes: The second segment of the second command response message is received until the transmission of the second command response message is complete; Otherwise, perform the step of sending the first command to the IoT device or resending the second command.

46. ​​An Internet of Things (IoT) device management system, characterized in that, The system includes IoT devices and network nodes, wherein: The IoT device is configured to receive an initial trigger message sent by a network node, the initial trigger message including at least one of the following: a power status reporting indication, an indication of the IoT device access timing, a paging cycle and / or the number of access timings, length information of the IoT device identifier to be triggered, the IoT device identifier to be triggered, an access type indicator, a network node identifier, and a service identifier; and to send a first message to the network node, the first message carrying at least one of the power status and the IoT device identifier. The network node is used to send an initial trigger message to the IoT device and receive the first message sent by the IoT device.

Images