Method and system for temporary identifier management of internet of things device, communication device, medium, and product

By adopting a method for receiving and managing temporary identifiers for IoT devices, the problem that the Rel-18 protocol cannot support access and data transmission for extremely low-power devices is solved, enabling secure and successful data transmission and large-scale network coverage for IoT devices.

WO2026233459A1PCT designated stage Publication Date: 2026-11-12CHINA TELECOM CORP LTD TECHNOLOGY INNOVATION CENTER +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/096006
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-09
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

The existing Rel-18 protocol cannot support the access, temporary identifier configuration and data transmission of ultra-low power IoT devices, making it difficult for cellular networks to achieve seamless coverage and secure data transmission for environmental IoT devices.

Method used

By receiving initial trigger messages from network nodes, IoT devices manage temporary identifiers, including receiving and releasing temporary identifiers, using temporary identifiers for data transmission, and reconfiguring access resources when necessary, avoiding the transmission of permanent device identifiers in plaintext to ensure security and successful transmission.

Benefits of technology

It enables secure and successful data transmission to ultra-low-power IoT devices, supports seamless coverage of large-scale networks, reduces power consumption, and improves transmission success rate.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026096006_12112026_PF_FP_ABST
    Figure CN2026096006_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to a method and system for temporary identifier management of an Internet of Things device, a communication device, a medium, and a product. The method comprises: receiving an initial trigger message sent by a network node, wherein the initial trigger message comprises at least one of related information of a device to be triggered, an access type indicator, a first service identifier, and temporary identifier information, and the related information of the device to be triggered includes at least one of length information of the identifier of the device to be triggered and the identifier of the device to be triggered; and receiving a second initial trigger message sent by the network node, and releasing a temporary identifier, wherein the second initial trigger message comprises a second service identifier.
Need to check novelty before this filing date? Find Prior Art

Description

Temporary identification management methods, systems, communication equipment, media, and products for Internet of Things (IoT) devices

[0001] Related applications

[0002] This application claims priority to Chinese patent application filed on May 9, 2025, application number 2025105989475, entitled "Method, System, Communication Equipment, Medium and Product for Temporary Identification Management of Internet of Things Devices", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of wireless communication technology, and in particular to a method, system, communication device, medium, and product for temporary identification management of Internet of Things (IoT) devices. Background Technology

[0004] With the development of wireless communication technology, more and more IoT devices are interconnected, enabling dense deployment of these devices and making wireless communication technology more practical in the IoT field. Therefore, to support the inventory and data transmission services of IoT devices, the data transmission process and security strategies of IoT devices in the current 5G standard still need to be enhanced.

[0005] In traditional technologies, the current Rel-18 protocol does not support the access, temporary identifier configuration, command issuance, and data transmission of ultra-low-power IoT devices. This makes it difficult for cellular networks to support low-power, low-complexity IoT devices such as environmental IoT devices, and hinders the achievement of seamless, large-scale network coverage. Therefore, there is an urgent need for a method that supports temporary identifier configuration and data transmission for environmental IoT devices. Summary of the Invention

[0006] Firstly, this application provides a temporary identifier management method for IoT devices, applied to IoT devices; including:

[0007] Receive an initial trigger message sent by a network node. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier and at least one of the device identifiers.

[0008] Receive the second initial trigger message sent by the network node, and release the temporary identifier. The second initial trigger message contains the second service identifier.

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

[0010] Upon receiving the second initial trigger message, if a first service identifier already stored exists, the first service identifier is released; if the second initial trigger message carries a second service identifier, the second service identifier is stored or the first service identifier is replaced with the second service identifier.

[0011] In one embodiment, an access type indicator is used to indicate the access type of an IoT device; the access type indicator includes contention-based random access and non-contention-based access; the access type includes contention-based access and non-contention-based access.

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

[0013] Store the business identifier contained in the initial trigger message;

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

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

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

[0017] If the IoT device stores a service identifier and the service identifier has no associated information, a first response result is determined, indicating that the initial trigger message has been responded to, and no further response is needed for this initial trigger message. If the IoT device does not store a service identifier, a second response result is determined, indicating that the initial trigger message has not been responded to, and a response is needed for this initial trigger message. Or...

[0018] If the IoT device stores a service identifier and the service identifier is associated with successful access information, determine the first response result. The first response result indicates that the initial trigger message has been responded to and access was successful, so there is no need to respond to this initial trigger message. If the IoT device stores a service identifier but the service identifier has no associated information, determine the second response result. The second response result indicates that the initial trigger message has been responded to but access failed, so a response to this initial trigger message is required. If the IoT device stores a service identifier and the service identifier is associated with access failure information, determine the second response result. The second response result indicates that the initial trigger message has been responded to but access failed, so a response to this initial trigger message is required. If the IoT device does not store a service identifier, determine the third response result. The third response result indicates that the initial trigger message has not been responded to, so a response to this initial trigger message is required.

[0019] In one embodiment, the method further includes: when a second initial trigger message is received, if a stored first service identifier exists and the second service identifier is the same as the first service identifier, then the business process associated with the first service identifier is determined to have failed.

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

[0021] Send the first message to the network node. The first message carries the first temporary identifier or device identifier.

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

[0023] Receive a second message sent by a network node. The second message includes at least one of the following: device identifier, temporary identifier information, command instruction information, and association information, as well as downlink scheduling information.

[0024] Downlink scheduling information includes the time-domain and / or frequency-domain resources required for the third message, as well as the transport block size.

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

[0026] Based on the receipt of the first temporary identifier, determine whether the access has failed;

[0027] If the access type indicator indicates contention-based random access, and if a second message carrying the first temporary identifier is not received before the timer expires, the access is deemed to have failed, and the first service identifier is associated with the access failure information; or,

[0028] If a second message carrying the first temporary identifier is not received, and an initial trigger message carrying the first service identifier is received again from a network node, and the IoT device stores the first service identifier and the first service identifier has no associated information, then the access is determined to have failed.

[0029] If the access type indicator indicates non-contention access, and no confirmation message for the associated first service identifier is received before the timer expires, the access is deemed to have failed.

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

[0031] Receive at least one first trigger message sent by the network-side 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.

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

[0033] If the access type indicator indicates non-contention access and access fails, the first service identifier is not associated with the information. The starting point of the frequency domain resources and / or time domain resources used is determined according to the first trigger message, and the first message is resent.

[0034] In one embodiment, the device identifier includes a first temporary identifier, a second temporary identifier, and / or a permanent device identifier. The temporary identifier information includes a reuse instruction or temporary identifier generation information. The reuse instruction is used to indicate that the first temporary identifier is used as a temporary identifier. The temporary identifier generation information is used to indicate the temporary identifier assigned to the IoT device by the network node, or related information for generating the second temporary identifier.

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

[0036] Send a third message to the network node. The third message contains at least one of the following: device identifier, segmentation transmission identifier, inventory response information, and command response information.

[0037] In one embodiment, a segmentation transmission identifier is used to indicate whether the bit is the final data bit.

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

[0039] If a negative acknowledgment message is received from a network node, it is determined that the third message or the first message associated with the stored first service identifier failed to be sent.

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

[0041] If a negative acknowledgment message is received from a network node, a third message is resent to the network node. The third message may include a segmented response message or an unsegmented response message.

[0042] In one embodiment, releasing the temporary identifier includes:

[0043] If the second service identifier exists in the second initial trigger message, then release the first temporary identifier or the second temporary identifier;

[0044] Alternatively, if the command instruction information contains a deletion instruction, then release the first temporary identifier or the second temporary identifier;

[0045] Alternatively, if a third temporary identifier is received in the fourth message sent by the network node, the first or second temporary identifier is released.

[0046] Alternatively, if the IoT device completes the command reporting and the segmented transmission identifier indicates that the bit is the final data bit, then the first temporary identifier or the second temporary identifier is released.

[0047] Alternatively, if the IoT device loses power, release the first temporary identifier or the second temporary identifier.

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

[0049] Network nodes have communication capabilities to communicate with IoT devices; readers are used to send and receive signals with IoT devices.

[0050] Intermediate node equipment includes repeaters, IAB integrated access and backhaul nodes, network control trunks (NCRs), and user equipment.

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

[0052] If the initial trigger message contains temporary identifier generation information and the IoT device supports encryption algorithms, then a second temporary identifier is generated based on the temporary identifier key information.

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

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

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

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

[0057] The initial trigger message does not carry the identifier of the device to be triggered, indicating that the IoT device has been selected by the initial trigger message; or,

[0058] The device identifier to be triggered in the initial trigger message is sent to the higher layer. If the higher layer indicates that the device identifier to be triggered matches the device identifier, it is determined that the IoT device is selected by the first trigger message, and the higher layer generates an inventory response message, which contains the NAS message of the device identifier.

[0059] In one embodiment, if a downlink message associated with a first temporary identifier or a second temporary identifier is received from a network node, the method further includes:

[0060] If the IoT device stores a temporary identifier associated with the downlink message, it forwards the upper-layer data to the non-access layer, applies the uplink scheduling information, and instructs the physical layer on the uplink scheduling information for subsequent uplink transmission.

[0061] If the IoT device does not store a temporary identifier associated with the downlink message, and the downlink message is an upper-layer data forwarding message with a contention-free access type, then the temporary identifier is stored, the upper-layer data is forwarded to the non-access layer, the uplink scheduling information is applied, and the uplink scheduling information is indicated to the physical layer for subsequent uplink transmission.

[0062] Secondly, this application also provides a method for managing temporary identifiers of IoT devices, applied to network nodes; including:

[0063] Send an initial trigger message to the Internet of Things device. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier to be triggered and at least one of the device identifiers to be triggered.

[0064] Send a second initial trigger message to the IoT device to release the temporary identifier. The second initial trigger message contains a second business identifier.

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

[0066] Receive the first message sent by the IoT device. The first message carries a first temporary identifier or device identifier.

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

[0068] Send a second message to the Internet of Things device. The second message includes at least one of the following: device identifier, temporary identifier information, command instruction information, and association information, as well as downlink scheduling information.

[0069] Downlink scheduling information includes the time-domain and / or frequency-domain resources required for the third message, as well as the transport block size.

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

[0071] Receive a third message sent by an IoT device, the third message containing at least one of the following: device identifier, segmented transmission identifier, inventory response information, and command response information.

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

[0073] After the second message is sent, the timer times out and determines that the third message failed to be sent, and sends a negative acknowledgment message to the IoT device.

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

[0075] Send a downlink message associated with a first temporary identifier or a second temporary identifier to an IoT device.

[0076] Thirdly, this application also provides a temporary identification management system for Internet of Things (IoT) devices, including:

[0077] An IoT device is configured to receive an initial trigger message sent by a network node, the initial trigger message containing a first service identifier and / or temporary identifier key information, and the first message containing a first temporary identifier; it is also configured to receive a second initial trigger message sent by a network node, and release the temporary identifier, the second initial trigger message containing a second service identifier; the IoT device is capable of receiving and / or sending at least one of a Non-Access Stratum (NAS) message and a Media Access Control (MAC) message;

[0078] A network node is used to send an initial trigger message to an IoT device; it is also used to send a second trigger message to the IoT device; and it is also used to send a second message to the IoT device, the second message containing at least one of device identifier, temporary identifier related information, command instruction information and association information, as well as information on time domain resources and / or frequency domain resources required for the third message and the transport block size, the device identifier including a first temporary identifier, a second temporary identifier and / or a permanent device identifier, the temporary identifier related information including an indication to reuse the first temporary identifier or to allocate a new second temporary identifier.

[0079] In one embodiment, the IoT device is further configured to, upon receiving a second initial trigger message, release the first service identifier if a stored first service identifier already exists, and store the second service identifier or replace the first service identifier with the second service identifier if the second initial trigger message carries a new service identifier.

[0080] In one embodiment, the IoT device is further configured to determine whether the access has failed based on the receipt of the first temporary identifier;

[0081] If the access type indicator indicates contention-based random access, and if a second message carrying the first temporary identifier is not received before the timer expires, the access is deemed to have failed, and the first service identifier is associated with the access failure information; or,

[0082] If a second message carrying the first temporary identifier is not received, and an initial trigger message carrying the first service identifier is received again from a network node, and the IoT device stores the first service identifier and the first service identifier has no associated information, then the access is determined to have failed.

[0083] If the access type indicator indicates non-contention access, and no confirmation message for the associated first service identifier is received before the timer expires, the access is deemed to have failed.

[0084] In one embodiment, the IoT device is further configured to receive at least one first trigger message sent by the network-side device, the first trigger message being 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.

[0085] In one embodiment, the IoT device is further configured to, if the access type indicator indicates non-contention access and access fails, not associate the first service identifier information, determine the starting point of the frequency domain resources and / or time domain resources used according to the first trigger message, and resend the first message.

[0086] In one embodiment, the device identifier includes a first temporary identifier, a second temporary identifier, and / or a permanent device identifier. The temporary identifier information includes a reuse instruction or temporary identifier generation information. The reuse instruction is used to indicate that the first temporary identifier is used as a temporary identifier. The temporary identifier generation information is used to indicate the temporary identifier assigned to the IoT device by the network node, or related information for generating the second temporary identifier.

[0087] In one embodiment, a segmentation transmission identifier is used to indicate whether the bit is the final data bit.

[0088] In one embodiment, the IoT device is further configured to release the first temporary identifier or the second temporary identifier if the second initial trigger message contains a second service identifier;

[0089] If the command instruction message contains a deletion instruction, then release the first temporary identifier or the second temporary identifier;

[0090] If the fourth message received from the network node contains a third temporary identifier, then release the first temporary identifier or the second temporary identifier.

[0091] If the IoT device completes the command reporting and the segmented transmission identifier indicates that the bit is the final data bit, then the first temporary identifier or the second temporary identifier is released.

[0092] In one embodiment, the IoT device is further configured to generate a first temporary identifier based on the temporary identifier key information if the initial trigger message contains temporary identifier generation information and the IoT device supports an encryption algorithm.

[0093] In one embodiment, if the initial trigger message does not carry an access type indicator, the IoT device is further configured to determine the access type based on the device identifier to be triggered in the initial trigger message; or,

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

[0095] Fourthly, this application also provides a temporary identifier management device for IoT devices, applied to IoT devices; comprising:

[0096] The first receiving module is used to receive an initial trigger message sent by a network node. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier and at least one of the device identifiers.

[0097] The second receiving module is used to receive the second initial trigger message sent by the network node and release the temporary identifier. The second initial trigger message contains the second service identifier.

[0098] Fifthly, this application also provides a temporary identifier management device for Internet of Things (IoT) devices, applied to network nodes; comprising:

[0099] 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: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier to be triggered and at least one of the device identifiers to be triggered.

[0100] The second sending module is used to send a second initial trigger message to the IoT device and release the temporary identifier. The second initial trigger message contains a second service identifier.

[0101] Sixthly, this application also provides a communication device, including: a transmitter, a receiver, a processor, and a memory, wherein the memory stores a computer program;

[0102] The receiver is used to receive an initial trigger message sent by a network node. The initial trigger message contains at least one of the following: information about the device to be triggered, an access type indicator, a first service identifier, and temporary identification information. The information about the device to be triggered includes the length information of the device identifier and at least one of the device identifiers.

[0103] The receiver is also used to receive a second initial trigger message sent by a network node and release a temporary identifier. The second initial trigger message contains a second service identifier.

[0104] In a seventh aspect, this application also provides a communication device, including: a transmitter, a receiver, a processor, and a memory, wherein the memory stores a computer program;

[0105] A transmitter is used to send an initial trigger message to an IoT device. The initial trigger message contains at least one of the following: information about the device to be triggered, an access type indicator, a first service identifier, and temporary identifier information. The information about the device to be triggered includes the length information of the device identifier to be triggered and at least one of the device identifiers to be triggered.

[0106] The transmitter is also used to send a second initial trigger message to the IoT device and release a temporary identifier, the second initial trigger message containing a second business identifier.

[0107] Eighthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0108] Receive an initial trigger message sent by a network node. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier and at least one of the device identifiers.

[0109] Receive the second initial trigger message sent by the network node, and release the temporary identifier. The second initial trigger message contains the second service identifier.

[0110] Ninthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0111] Send an initial trigger message to the Internet of Things device. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier to be triggered and at least one of the device identifiers to be triggered.

[0112] Send a second initial trigger message to the IoT device to release the temporary identifier. The second initial trigger message contains a second business identifier.

[0113] In a tenth aspect, a computer program product is provided, comprising a computer program that, when executed by a processor, performs the following steps:

[0114] Receive an initial trigger message sent by a network node. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier and at least one of the device identifiers.

[0115] Receive the second initial trigger message sent by the network node, and release the temporary identifier. The second initial trigger message contains the second service identifier.

[0116] Eleventhly, a computer program product is provided, comprising a computer program that, when executed by a processor, performs the following steps:

[0117] Send an initial trigger message to the Internet of Things device. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier to be triggered and at least one of the device identifiers to be triggered.

[0118] Send a second initial trigger message to the IoT device to release the temporary identifier. The second initial trigger message contains a second business identifier.

[0119] Details of one or more embodiments of this application are set forth in the following drawings and description. Other features, objects, and advantages of this application will become apparent from the specification, drawings, and claims. Attached Figure Description

[0120] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0121] Figure 1 is an application environment diagram of a temporary identifier management method for IoT devices in one embodiment;

[0122] Figure 2 is a flowchart illustrating a temporary identifier management method for IoT devices in one embodiment;

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

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

[0125] Figure 5 is a flowchart illustrating the steps for determining the business identifier in one embodiment;

[0126] Figure 6 is a flowchart illustrating the step of determining whether to reply to the initial trigger message in one embodiment;

[0127] Figure 7 is a flowchart illustrating the steps for determining whether access has failed in one embodiment;

[0128] Figure 8 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;

[0129] Figure 9 is a flowchart illustrating the step of releasing a temporary identifier in one embodiment;

[0130] Figure 10 is a flowchart illustrating the steps for determining the access type in one embodiment;

[0131] Figure 11 is a flowchart illustrating the steps of applying uplink scheduling information in one embodiment;

[0132] Figure 12 is a flowchart illustrating a temporary identifier management method for IoT devices in another embodiment;

[0133] Figure 13 is a flowchart illustrating an example of a temporary identifier management method for IoT devices in one embodiment;

[0134] Figure 14 is an example diagram of the second message in one embodiment;

[0135] Figure 15 is another example diagram of the second message in one embodiment;

[0136] Figure 16 is a structural block diagram of a temporary identification management system for IoT devices in one embodiment;

[0137] Figure 17 is a structural block diagram of a temporary identifier management device for an Internet of Things (IoT) device in one embodiment;

[0138] Figure 18 is a structural block diagram of a temporary identifier management device for an Internet of Things (IoT) device in another embodiment;

[0139] Figure 19 is an internal structure diagram of a communication device in one embodiment. Detailed Implementation

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

[0141] Figure 1 is a schematic diagram of an application scenario for a temporary identifier management method for IoT devices provided in an embodiment of this application. As shown in Figure 1, the 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.

[0142] Among them, IoT devices 100 include zero-power devices, environmental IoT devices, and IoT devices with capacitors. Specifically, 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 monitoring 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.

[0143] The IoT device 100 can also be referred to as a user equipment (UE), tag, or sensor. Its structure includes at least one of read-only memory (ROM / OTP), non-volatile writable memory (NVM, such as EEPROM or small Flash), and volatile memory (RAM). When the IoT device is powered off, its permanent device identifier will not be released, but its temporary identifier and / or service identifier will be released.

[0144] Examples of IoT devices include:

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

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

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

[0148] In traditional technologies, temporary identifiers generated by the access layer are needed when IoT devices such as sensors upload data (e.g., during command processing after data storage). These access layer temporary identifiers differ from device identifiers and core network-generated identifiers; they are shorter, valid only within the coverage area of ​​the reader or intermediate node, and used for data transmission after access, applied in downlink scheduling information and uplink data reporting. However, the current Rel-18 protocol does not support access, temporary identifier configuration, command issuance, and data transmission for extremely low-power IoT devices. Considering the need for cellular networks to support low-power, low-complexity IoT devices such as environmental IoT devices, existing standards need to be enhanced to support temporary identifier configuration and data transmission for environmental IoT devices, thereby enabling data storage, command processing, and data collection for IoT devices.

[0149] Under the current agreement, the following problems may exist:

[0150] Security: Because IoT devices have a relatively simple structure, data is usually transmitted in plaintext (such as RFID transmission). If the real permanent identifier of the device is transmitted wirelessly, it is vulnerable to man-in-the-middle attacks (such as forwarding the data generated by the real device to the network again, which will cause network reception errors). This cannot meet the needs of industrial inventory processes for accuracy and security.

[0151] Energy saving: The device identifier is longer. If the device identifier is reported through the air interface, it may need to be transmitted in segments, which increases the burden on the interface and brings greater power consumption to IoT devices.

[0152] The probability of data packet transmission failure is high: If the device identifier is reported over the air interface, it may be necessary to transmit in segments. However, the power of IoT devices is limited, and the command response to the reader or intermediate node needs to report a large data packet (such as EPC). Therefore, it is easy to cause the problem of insufficient power and transmission failure. Using a shorter temporary identifier can reduce the data packet size and improve the success rate of transmission.

[0153] Based on the above requirements and reasons, the current 3GPP Rel-18 protocol cannot meet the network's optimization needs for identification configuration and data transmission of ultra-low power IoT devices. It is necessary to standardize it through a new method so that when the network stores and collects data from IoT devices through readers or intermediate nodes, it can use temporarily generated identifiers to ensure communication security and make flexible resource allocation.

[0154] Based on the aforementioned traditional technologies, this application provides a method for managing temporary identifiers of IoT devices. By using the temporary identifier-related information contained in the initial trigger message sent by the network node, the IoT device can identify the time / frequency domain resources required for commands sent to the IoT device and associated reporting in subsequent data transmissions through a first or second temporary identifier, and release the temporary identifier in a timely manner. This eliminates the need to transmit permanent device identifiers in plaintext, ensuring the secure and successful transmission of IoT-related services.

[0155] The IoT devices described in this application support dense deployment and can form large-scale networks with seamless coverage (such as environmental IoT devices). This is a new IoT technology that opens up new markets within the 3rd Generation Partnership Project (3GPP) system. Its number of connections and / or device density may be several orders of magnitude higher than existing 3GPP IoT technologies, and its complexity and power consumption may be several orders of magnitude lower than existing 3GPP-standardized Low Power Wide Area (LPWA) technologies such as Narrow Band Internet of Things (NB-IoT) and LTE-based Machine-to-Machine Communication (LTE-MTC).

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

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

[0158] In an exemplary embodiment, as shown in FIG2, a temporary identifier management method for an Internet of Things (IoT) device is provided. Taking the application of this method to the IoT device 100 in FIG1 as an example, the method includes the following steps:

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

[0160] The initial trigger message (i.e., the downlink paging message) contains at least one of the following: information about the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The information about the device to be triggered includes the length information of the device identifier and at least one of the device identifiers.

[0161] Specifically, the indication for the timing of IoT device access 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.

[0162] The initial trigger message carries time-domain and frequency-domain resources. Since there is no local clock, timing alignment cannot be directly achieved based on this message. After receiving the initial trigger message, the IoT device selects the time slot it wants to use from the given time-domain resources. It only provides a range of available time-domain resources, rather than explicitly specifying a particular, precise access time slot.

[0163] Access indication refers to an indication of the timing of IoT device access (the time-domain and / or frequency-domain resource location for the IoT device to reply to the reader or intermediate node with a trigger message), the paging cycle (the time interval for sending paging messages to user equipment in an idle or inactive state), or the number of access opportunities.

[0164] The relevant information for the device to be triggered includes the length of the device identifier and at least one of the device identifiers. The length of the device identifier indicates the length of the paging ID (because the size of the paging ID is not fixed, length info is required). The device identifier, or the identifier of the paged device, i.e., the device ID or a combination of multiple device IDs, is used to trigger / select a single device, a group of devices, or multiple non-grouped devices. When the access trigger message does not carry the device identifier, it means that all IoT devices that received the access trigger message are triggered / selected. For group paging, the corresponding paging ID is obtained by masking or truncating the device ID, retaining only the first or second half of the device ID.

[0165] In an exemplary embodiment, an access type indicator is used to indicate the access type of the IoT device. The access type indicator includes Contention Based Random Access (CBRA) and Contention-Free Access (CFA). The access type indicator is a 1-bit indicator, where 0 represents CBRA and 1 represents CFA; or 0 represents CFA and 1 represents CBRA. Specifically, the access type includes contention-based access and contention-free access.

[0166] First transaction ID: Associated with the service request corresponding to this access trigger message.

[0167] Temporary identifier information refers to the key information of a symmetric key encryption algorithm.

[0168] For example, when an IoT device is in an idle (IDLE) or deep sleep (PSM) state, a 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 to ensure accurate addressing. Furthermore, the payload of the initial trigger message also carries one or more parameters for managing the temporary identifier of the IoT device. For example, the parameters may include at least one of the following: relevant information about the device to be triggered, an access type indicator, a first service identifier, and temporary identifier information. The relevant information about the device to be triggered includes the length of the device identifier and the device identifier itself. Thus, the IoT device can wake up the corresponding processing thread based on the received initial trigger message.

[0169] Step 204: Receive the second initial trigger message sent by the network node and release the temporary identifier.

[0170] The second initial trigger message contains a second business identifier.

[0171] Specifically, a service identifier is associated with a service request sent by the core network, meaning that each service request has a corresponding service identifier to uniquely identify the request. The service identifier is a service request association identifier and / or network node identifier sent by the core network based on the service request association identifier sent by the core network. The service request association identifier sent by the core network is used to uniquely identify a service request and is typically generated by the core network and sent to other network nodes to track and associate the same service request across different nodes. The network node identifier identifies a specific network node within the network.

[0172] For example, the first service identifier and the second service identifier are used to identify the corresponding initial trigger messages, which may come from two different service requests (i.e., different service types or operations), or they may be the same service request but from different network nodes (i.e., the same service request is triggered or processed by multiple network nodes). If the service request association identifiers sent by the core network for two service requests are different, then they are different service requests; if the service request association identifiers sent by the core network are the same but the network node identifiers are different, then the same service request may be triggered or processed by different network nodes. By combining the service request association identifier and the network node identifier sent by the core network, the source and type of service requests can be distinguished more precisely.

[0173] In the aforementioned temporary identifier management method for IoT devices, the temporary identifier information contained in the initial trigger message sent by the network node allows the IoT device to identify the time / frequency domain resources required for the command sent to the IoT device and the associated reporting during subsequent data transmission through the first or second temporary identifier, and release the temporary identifier in a timely manner. This eliminates the need to transmit the permanent device identifier in plaintext, ensuring the secure and successful transmission of IoT-related services.

[0174] In an optional embodiment, the topology corresponding to the currently densely deployed IoT network includes a first topology and a second topology, etc. As shown in Figure 3, the first topology involves direct bidirectional communication between IoT devices and base stations. 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.

[0175] As shown in Figure 4, 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.

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

[0177] Examples of scenarios involving IoT devices include: Scenario 1 (indoor to indoor) with indoor microcell base stations and Scenario 2 (indoor to outdoor) in the first topology. The second topology consists of indoor UEs (user equipment) as intermediate nodes under network control, and outdoor macrocell base stations.

[0178] In an exemplary embodiment, as shown in Figure 5, when the IoT device receives the second trigger message, it also needs to determine whether the service identifier needs to be released or replaced based on whether the same service identifier is stored. Therefore, the method further includes:

[0179] Step 502: Upon receiving the second initial trigger message, if a stored first service identifier already exists, release the first service identifier.

[0180] For example, if an IoT device receives a new initial trigger message (i.e., the second initial trigger message), it needs to check whether the previous service identifier (i.e., the first service identifier) ​​has already been stored. If the first service identifier has already been stored, it needs to release the identifier when the new trigger message is received to ensure that the IoT device does not confuse the old and new service requests and avoids processing errors due to the existence of the old identifier.

[0181] Step 504: If the second initial trigger message carries a second service identifier, store the second service identifier or replace the first service identifier with the second service identifier.

[0182] For example, if the second initial trigger message carries a new service identifier (i.e., the second service identifier), the identifier needs to be stored in the device. For instance, it can directly replace the previous first service identifier, that is, use the new identifier to overwrite the old identifier, to ensure that the system always uses the latest service identifier to process the currently received service request.

[0183] In this embodiment, when a new initial trigger message is received, the previously stored service identifier is cleared or released. If the new trigger message carries a service identifier, it is stored or updated with a new service identifier to ensure that the IoT device always processes the latest service requests and to ensure the secure and successful transmission of IoT-related services.

[0184] In one exemplary embodiment, a business identifier contained in the initial trigger message is stored.

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

[0186] Specifically, the same business identifier indicates that the paging message is associated with the same business request, while different business identifiers indicate that the paging message is associated with different business requests, or that the paging message comes from different network nodes.

[0187] In an exemplary embodiment, the IoT device can also set associated information for the service identifier. This associated information indicates whether a response has been made to the initial trigger message sent by the network node. The following describes two scenarios: contention-based random access and non-contention-based access. It should be noted that the service identifier discussed in the embodiment corresponding to Figure 6 can refer to either a first service identifier or a second service identifier. As shown in Figure 6, the method may further include:

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

[0189] For example, an IoT device determines whether it needs to respond to the corresponding initial trigger message based on a service identifier. For instance, it might determine whether to respond to the corresponding initial trigger message (also called the first initial trigger message) based on a first service identifier, or it might determine whether to respond to the corresponding second initial trigger message based on a second 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, a response record can be created using the service identifier and its associated information. That is, when the IoT device stores the service identifier, it also stores the associated information corresponding to the service identifier. Through this associated information, it can determine whether to respond to the initial trigger message carrying the service identifier.

[0190] Step 604: The IoT device stores a service identifier, but the service identifier has no associated information, and the first response result is determined.

[0191] The first response result indicates that a response has already been given to the corresponding initial trigger message, and no response is needed to the current initial trigger message. For example, the first response result could be "A response has already been given to the first initial trigger message, and no response is needed to the current first initial trigger message." Or, the first response result could be "A response has already been given to the second initial trigger message, and no response is needed to the current second initial trigger message."

[0192] For example, if the access type indicator indicates contention-based random access, and if the IoT device has stored a service identifier and the associated information of the service identifier has been responded to, it indicates that the IoT device has responded to the corresponding initial trigger message. The IoT device determines the first response result, which is that it has responded to the corresponding initial trigger message and does not need to respond to this initial trigger message, thereby avoiding duplicate responses.

[0193] Step 606: If the IoT device does not store a service identifier, determine the second response result. The second response result is that no response was made to the initial trigger message, but a response is required to the current initial trigger message. For example, the second response result could be that no response was made to the first initial trigger message, but a response is required to the current first initial trigger message; or the second response result could be that no response was made to the second initial trigger message, but a response is required to the current second initial trigger message.

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

[0195] Step 608: If the IoT device stores a service identifier and the service identifier is associated with successful access information, determine the first response result. The first response result indicates that the initial trigger message has been responded to and access has been successful, and there is no need to respond to this initial trigger message. For example, the first response result indicates that the first initial trigger message has been responded to and access has been successful, and there is no need to respond to this first initial trigger message; or the first response result indicates that the second initial trigger message has been responded to and access has been successful, and there is no need to respond to this second initial trigger message.

[0196] For example, if the access type indicator indicates non-contention access, and if the IoT device stores a service identifier and the service identifier is associated with successful access information, 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, thereby avoiding duplicate responses.

[0197] Step 610: If the IoT device stores a service identifier and the service identifier has no associated information, determine the second response result.

[0198] The second response result indicates that a response to the initial trigger message was initiated but access failed, and a response to the current initial trigger message is required. For example, the second response result could be that a response to the first initial trigger message was initiated but access failed, and a response to the current first initial trigger message is required; or the second response result could be that a response to the second initial trigger message was initiated but access failed, and a response to the current second initial trigger message is required.

[0199] For example, if the IoT device stores a service identifier and the service identifier has no associated information, it indicates that the IoT device responded to the initial trigger message, but the response failed to access the device. The IoT device determines a second response result, which is that it has responded to the initial trigger message but the access failed, and it needs to respond to the initial trigger message this time.

[0200] Step 612: If the IoT device stores a service identifier and the service identifier is associated with access failure information, determine the second response result.

[0201] The second response result indicates that a response to the initial trigger message was initiated but access failed, and a response to the current initial trigger message is required. For example, the second response result could be that a response to the first initial trigger message was initiated but access failed, and a response to the current first initial trigger message is required; or the second response result could be that a response to the second initial trigger message was initiated but access failed, and a response to the current second initial trigger message is required.

[0202] For example, if an IoT device stores a service identifier and the service identifier is associated with access failure information, it indicates that the IoT device responded to the initial trigger message, but the access failed. The IoT device determines a second response result, which is that it has responded to the initial trigger message but the access failed, and it needs to respond to this initial trigger message.

[0203] Step 614: If the IoT device does not store a business identifier, determine the third response result.

[0204] The third response result indicates that no response was given to the initial trigger message, and a response is required to this initial trigger message. For example, the third response result could be that no response was given to the first initial trigger message, and a response is required to this first initial trigger message; or the third response result could be that no response was given to the second initial trigger message, and a response is required to this second initial trigger message.

[0205] For example, if the IoT device does not store a service identifier, it indicates that the IoT device has not responded to the initial trigger message and has not stored the initial trigger message. Therefore, the IoT device determines a third response result, which is that a response to the current initial trigger message is required.

[0206] In an exemplary embodiment, when an IoT device receives a second initial trigger message, if a first service identifier already exists and the second service identifier is the same as the first service identifier, then the business process associated with the first service identifier is determined to have failed.

[0207] In one exemplary embodiment, the method may further include:

[0208] Send the first message to the network node.

[0209] The first message carries a first temporary identifier or device identifier.

[0210] For example, if the initial trigger message contains temporary identifier key information and the IoT device supports encryption algorithms, a first temporary identifier is generated based on the key information. If the IoT device does not support encryption algorithms, a 16-bit temporary identifier can be generated based on RN16.

[0211] Device identification includes a first temporary identifier generated locally by the IoT device or the device identifier of the IoT device.

[0212] Specifically, when the access type is CFA, the first message will carry the device identifier, while when the access type is CBRA, the first message will carry a temporary identifier.

[0213] For example, when an IoT device determines that it needs to respond to the current initial trigger message, the IoT device sends a first message to the network node, reporting the first temporary identifier. If the IoT device has already stored the service identifier, then the IoT device has already responded to the initial trigger message for that service and does not need to respond to this current initial trigger message.

[0214] In one exemplary embodiment, the method may further include:

[0215] Receive the second message sent by the network node.

[0216] The second message includes at least one of the following: device identifier, temporary identifier information, command instruction information, and associated information, as well as downlink scheduling information; the downlink scheduling information is the information on time domain resources and / or frequency domain resources required by the third message and the transport block size.

[0217] Specifically, the device identifier includes a first temporary identifier, a second temporary identifier, and / or a permanent device identifier. The second message sent by the network node contains the device identifier from the first message, so that the IoT device knows that the message is sent to it and the competition for access is successful.

[0218] When the access type is CBRA, the second message carries the device identifier reported by the IoT device for conflict resolution; when the access type is CFA, the second message carries a command instruction.

[0219] The information related to the temporary identifier includes an indication to reuse the first temporary identifier or to allocate a new second temporary identifier, which is also 16 bits and is allocated by the network node.

[0220] When the access type is CFA, the command instruction information includes reading data, writing data, locking data, deleting data, setting access password, etc.

[0221] The associated information includes at least one of the following: the association information between the device identifier and the access layer identifier; the association information between the command indication and the access layer identifier; and the association information between the device identifier and the command indication.

[0222] Downlink scheduling information includes information on the time-domain and / or frequency-domain resources required for the third response message.

[0223] For example, after the network node and the IoT device complete paging (i.e., the interaction between the initial trigger message and the first message is completed), the IoT device can receive a second message sent by the network node. This second message is the network node's management of the IoT device's temporary identifier. Specifically, to determine which temporary identifier the IoT device should use for subsequent data transmission with the network node, the network node can send a second message based on the first temporary identifier or device identifier reported by the IoT device. The IoT device can then identify whether the second message is addressed to it to determine if the connection was successful. Furthermore, based on the instructions in the second message, the network node can determine whether to reuse the first temporary identifier for data transmission or use the new second temporary identifier allocated by the second message. Additionally, the IoT device can also determine the time-domain and / or frequency-domain resources required to send a third message to the network node based on the second message, thereby achieving reliable communication and state synchronization between the IoT device and the network node.

[0224] In an exemplary embodiment, as shown in FIG7, the IoT device may further set association information for the first temporary identifier. The association information of the first temporary identifier indicates whether the response to the initial trigger message sent by the network node has failed to access the network. Therefore, the method may further include:

[0225] Step 702: Determine whether the access failed based on the receipt of the first temporary identifier.

[0226] For example, the IoT device uses the first temporary identifier to determine whether the response to the initial trigger message has failed to connect. Specifically, when the IoT device receives the initial trigger message from the network node, the network node will resend the temporary identifier reported by the IoT device. To avoid connection failure, the first temporary identifier can be used for this determination.

[0227] Step 704: If the access type indicator indicates contention-based random access, and if no second message carrying the first temporary identifier is received before the timer expires, the access is determined to have failed, and the first service identifier is associated with the access failure information.

[0228] For example, a timer is set to limit the time a device waits for a network response. In contention-based random access, network resources are limited and multiple devices compete for access. If a device does not receive a response message from the network for the first temporary identifier within the specified time, it indicates that the IoT device's response has not been received by the network node, and the IoT device determines that the access has failed.

[0229] Step 706: If a second message carrying the first temporary identifier is not received, and if an initial trigger message carrying the first service identifier is received again from the network node, and the IoT device stores the first service identifier and the first service identifier has no associated information, then the access is determined to have failed.

[0230] For example, if a second message carrying the first temporary identifier is not received, but an initial trigger message carrying the first service identifier is received again from a network node, and the IoT device stores the first service identifier and the first service identifier has no associated information, then it indicates that the IoT device is responding repeatedly, and the IoT device determines that the access has failed.

[0231] Step 708: If the access type indicator indicates non-contention access, and if no confirmation message for the associated first service identifier is received before the timer expires, the access is deemed to have failed.

[0232] For example, if the access type indicator indicates non-contention access, and no confirmation message for the associated first service identifier is received before the timer expires, it indicates that the IoT device has not accessed the network node, and the IoT device determines that the access has failed.

[0233] In this embodiment, by determining whether the access has failed based on the receipt of the first temporary identifier, the IoT device can proactively detect access anomalies, avoid repeated responses, and improve communication reliability and efficiency.

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

[0235] Receive at least one first trigger message sent by the network-side device.

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

[0237] For example, after sending the initial trigger message, the network node sends at least one first trigger message 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 first trigger messages (N ≤ access timing). Specifically, the first trigger message itself can carry frequency domain resource information and / or time domain resource information. In the time domain, as shown in Figure 8, after the network node sends the initial trigger message (Q), the network node sends at least one first trigger message, which is immediately followed by the time slot (msg1 slot) where the first message is located. That is, the first trigger message is immediately followed by the Nth time domain resource. In this way, the starting point of the frequency domain resource indicated by the first trigger message determines the frequency band position occupied by the IoT device for data transmission, which helps to avoid signal interference and achieve reasonable allocation of spectrum resources. The starting point of the time domain resource clarifies the specific time when the IoT device starts sending data, so that the data transmission of the IoT device keeps synchronized with the network scheduling rhythm, effectively ensuring the timeliness and orderliness of data transmission.

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

[0239] If the access type indicator indicates non-contention access and access fails, the first service identifier is not associated with the information. The starting point of the frequency domain resources and / or time domain resources used is determined according to the first trigger message, and the first message is resent.

[0240] For example, if the access type indicator indicates non-contention access and access fails, the first service identifier is not associated with information to record the response result. The IoT device then determines the starting point of the frequency domain resources and / or time domain resources used based on the first trigger message and resends the first message to ensure that the IoT device and the network node can access each other successfully.

[0241] In this embodiment, by not associating the first service identifier with information and retransmitting the first message when access fails in a non-contention-based access scenario, the retransmission mechanism can reduce the access latency of devices in large-scale networks. Furthermore, IoT devices do not need to maintain the event state of the first service identifier, making the protocol state machine simpler and reducing the complexity and power consumption of device implementation. This makes it suitable for lower-power IoT devices.

[0242] In one exemplary embodiment, the device identifier includes a first temporary identifier, a second temporary identifier, and / or a permanent device identifier.

[0243] The temporary identifier information includes a reuse instruction or temporary identifier generation information. The reuse instruction indicates that the first temporary identifier should be used as the temporary identifier. The temporary identifier generation information indicates the temporary identifier that the network node assigns to the IoT device, or is related to generating the second temporary identifier, such as symmetric key information. The temporary identifier is used only at the access layer.

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

[0245] Send a third message to the network node.

[0246] The third message includes at least one of the following: device identifier, segmented transmission identifier, inventory response information, and command response information.

[0247] For example, 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 sent by the network node, which contains command instructions. The IoT device identifier allows the network node to quickly and accurately locate the sender, enabling efficient communication between the IoT device and the network node, improving management efficiency and data transmission accuracy. The transmission of inventory response information allows the network node to monitor device resource status in real time, facilitating rational resource allocation and system optimization. The command response information in the third message sent by the IoT device establishes a two-way feedback loop between the device and the network, ensuring that device operation meets network expectations and enhancing the reliability and stability of system interaction.

[0248] In one exemplary embodiment, a segmentation transmission identifier is used to indicate whether the bit is the final data bit.

[0249] Specifically, the segmentation identifier is located at the end of the third response message, occupying 1 bit, and indicates whether the third response message contains complete response information and whether there is any other information to be transmitted. If the segmentation identifier is 1, then this bit is not the final bit; if the identifier is 0, then this bit is the final bit. When the third message is a segmented transmission, the segmentation identifier is mandatory.

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

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

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

[0253] If a negative acknowledgment message is received from a network node, it is determined that the third message or the first message associated with the stored first service identifier failed to be sent.

[0254] For example, 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, that is, the network node does not successfully receive the third message, the network node will send a negative acknowledgment message to the IoT device. The negative acknowledgment message is a message that triggers the IoT device to retransmit, indicating that the network node has not received the third message.

[0255] Specifically, network nodes explicitly inform IoT devices of the failure to receive the third message via a negative acknowledgment message. This message not only conveys the failure status but also includes resource indications for retransmission, covering key parameters such as the specific location and range of frequency and time domain resources, and the transport block size. By receiving this negative acknowledgment message and obtaining these resource indications, IoT devices can accurately determine when and which network resources to use for retransmission, effectively preventing further transmission failures, ensuring successful data delivery to the network node, and maintaining the stability of the communication link and the integrity of data exchange.

[0256] For example, a negative acknowledgment message is used to indicate that the inventory response message transmission failed. When the access type is CBRA, the inventory response message associated with the stored first service identifier refers to the third message; when the access type is CFA, the inventory response message associated with the stored first service identifier refers to the first message.

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

[0258] If a negative acknowledgment message is received from a network node, the third message is resent to the network node.

[0259] The third message includes either a segmented response message or an unsegmented response message.

[0260] For example, when an IoT device receives a negative acknowledgment message from a network node, the IoT device, based on the negative acknowledgment message, determines that the network node has not successfully received the third message. In this way, the IoT device retransmits the third message to the network node based on the resource indication required for retransmission of the third message contained in the negative acknowledgment message.

[0261] In this embodiment, when the transmission of the third message fails, the network node explicitly informs the IoT device of the transmission anomaly through a negative acknowledgment message. 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 negative acknowledgment message includes resource indications for retransmitting the third message. This provides IoT devices with precise retransmission instructions, enabling them to accurately use the specified frequency domain, time domain resources, and transmission block size for data retransmission. This reduces the probability of conflicts with other data transmissions during retransmission, enhances the reliability and stability of the communication link, and ensures the continuity and integrity of the IoT system's business processes.

[0262] In an exemplary embodiment, as shown in FIG9, the IoT device releases the first or second temporary identifier after determining the following conditions or any combination of two of them. The method further includes the following steps:

[0263] Step 902: If the second service identifier exists in the second initial trigger message, then release the first temporary identifier or the second temporary identifier.

[0264] For example, since different service identifiers are associated with different service requests, if an IoT device receives a second initial trigger message containing a second service identifier sent by a network node, it indicates that a new service process has begun. At this time, the first or second temporary identifier is released so that the IoT device can focus on processing the new service request.

[0265] Step 904: If the command instruction information contains a deletion instruction, then release the first temporary identifier or the second temporary identifier.

[0266] For example, if the command instruction information contains a deletion instruction, it indicates that the network node requires the IoT device to clear the currently used first or second temporary identifier, and the IoT device follows the instruction to release the identifier.

[0267] Step 906: If the fourth message received from the network node contains a third temporary identifier, then release the first temporary identifier or the second temporary identifier.

[0268] For example, if a third temporary identifier is received in the fourth message sent by the network node, it indicates that the network node specifies the third temporary identifier for subsequent data transmission. Therefore, the IoT device releases the first or second temporary identifier.

[0269] Step 908: If the IoT device completes the command reporting and the segmented transmission identifier indicates that the bit is the final data bit, then release the first temporary identifier or the second temporary identifier.

[0270] For example, if an IoT device completes a command report and the segmented transmission identifier indicates that the bit is the final data bit, it indicates that it is not a segmented transmission and no further data transmission is required. The IoT device then releases the first or second temporary identifier.

[0271] Step 910: If the IoT device loses power, release the first temporary identifier or the second temporary identifier.

[0272] For example, steps 902-908 above are implemented when the IoT device is powered on, while when the IoT device is powered off, the first temporary identifier or the second temporary identifier is released.

[0273] In this embodiment, by releasing the old temporary identifier when the IoT device enters a new business process, the resource occupation can be reduced. The release of the temporary identifier can free up the storage resources on the device side, reduce the hardware cost of the device, and the device does not need to maintain the state transition logic of multiple identifiers, which simplifies the complexity of protocol implementation and optimizes the efficiency and reliability of data transmission.

[0274] In one exemplary embodiment, the network node includes either a reader or an intermediate node device;

[0275] Network nodes have communication capabilities to communicate with IoT devices; readers are used to send and receive signals with IoT devices.

[0276] Intermediate node equipment includes repeaters, IAB integrated access and backhaul nodes, network control trunks (NCRs), and user equipment.

[0277] The Network Control Relay (NCR) is a relay node uniformly controlled by the network side (e.g., gNB or core network). Its main purpose is 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 entirely controlled by the network, emphasizing centralized scheduling and resource management.

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

[0279] If the initial trigger message contains temporary identifier generation information and the IoT device supports encryption algorithms, then a second temporary identifier is generated based on the temporary identifier key information.

[0280] For example, if the initial trigger message contains temporary identifier generation information and the IoT device supports encryption algorithms, such as symmetric key encryption algorithms, the IoT device generates a second temporary identifier based on the symmetric key information in the temporary identifier generation information. The second temporary identifier is used for subsequent data transmission. Network nodes can independently derive this identifier using the same key information to achieve two-way verification.

[0281] In this embodiment, a temporary identifier is dynamically generated through an encryption algorithm, eliminating the need to transmit the permanent device identifier in plaintext, thus ensuring the secure and successful transmission of IoT-related services.

[0282] In an exemplary embodiment, as shown in FIG10, if the initial trigger message does not carry an access type indicator, the method further includes:

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

[0284] For example, if the initial trigger message sent by the network node does not carry an access type indicator, but carries an IoT device identifier to be triggered, the IoT device determines the access type based on the IoT device identifier to be triggered.

[0285] Specifically, 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.

[0286] Step 1004: Determine the access type based on the access timing in the initial trigger message.

[0287] For example, if the initial trigger message sent by the network node does not carry an access type indicator, but carries the access timing of the IoT device, the IoT device determines 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 the IoT device and the access timing, then the IoT device is determined to have contention-free access.

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

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

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

[0291] If the initial trigger message does not carry the identifier of the device to be triggered, it is determined that the IoT device has been selected by the initial trigger message; or, the identifier of the device to be triggered in the initial trigger message is sent to the higher layer. If the higher layer indicates that the identifier of the device to be triggered matches the device identifier, it is determined that the IoT device has been selected by the first trigger message, and the higher layer generates an inventory response message.

[0292] The inventory response message includes a NAS message identifying the device.

[0293] For example, the protocol stack of an IoT device includes at least a Physical Layer (PHY), a Medium Access Control Layer (MAC), and a Non-Access-Stratum (NAS). If the initial trigger message does not carry a device identifier to be triggered, the MAC layer determines that the IoT device has been selected by the initial trigger message and indicates to the NAS that the IoT device has been selected. If the initial trigger message carries a device identifier to be triggered, the device identifier to be triggered is sent to the NAS. If the NAS indicates that the device identifier to be triggered matches the device identifier, it determines that the IoT device has been selected by the first trigger message, and the NAS generates a disk response message.

[0294] In an exemplary embodiment, as shown in FIG11, if a downlink message associated with a first temporary identifier or a second temporary identifier is received from a network node, the method further includes:

[0295] Step 1102: If the IoT device stores a temporary identifier associated with the downlink message, it forwards the upper-layer data to the non-access layer, applies the uplink scheduling information, and instructs the physical layer on the uplink scheduling information for subsequent uplink transmission.

[0296] For example, if an IoT device receives a downlink message from a network node associated with a first temporary identifier or a second temporary identifier, and the device's local storage contains a temporary identifier associated with that message, the IoT device compares the temporary identifier in the downlink message with the identifier in its local storage to confirm that the message source is legitimate and the target is itself. It then forwards the upper-layer data (such as NAS layer data or application layer instructions) in the message to the Non-Access Layer (NAS layer) for processing by higher-layer protocols. The uplink scheduling information (such as resource block allocation or modulation and coding scheme MCS) carried in the application downlink message is then directed to the physical layer (PHY layer) for subsequent uplink data transmission (such as response messages or status reporting).

[0297] Step 1104: If the IoT device does not store a temporary identifier associated with the downlink message, and the downlink message is an upper-layer data forwarding message with a contention-free access type, then store the temporary identifier, forward the upper-layer data to the non-access layer, apply the uplink scheduling information, and instruct the physical layer on the uplink scheduling information for subsequent uplink transmission.

[0298] For example, if an IoT device does not store a temporary identifier associated with a downlink message, but meets the following conditions: the downlink message is an upper-layer data forwarding message (such as NAS layer data or application layer instructions); the access type is contention-free access (such as contention-free resource allocation based on a random access preamble, or pre-configured dedicated resources), then the IoT device will store the temporary identifier in the downlink message locally, establishing a context association with subsequent communication. It will then forward the upper-layer data to the NAS layer and apply uplink scheduling information to the PHY layer.

[0299] In this embodiment, the IoT device confirms the legitimacy of the message source by identifier comparison, associates the temporary identifier with the subsequent uplink scheduling information, reduces signaling overhead, and in the case of no contention access, the IoT device can directly use dedicated resources to transmit uplink data without competing for resources through a random access process, thereby reducing latency.

[0300] In an exemplary embodiment, as shown in FIG12, a temporary identifier management method for IoT devices is provided. Taking the application of this method to network node 200 in FIG1 as an example, the method includes the following steps:

[0301] Step 1202: Send an initial trigger message to the IoT device. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier and at least one of the device identifiers.

[0302] Step 1204: Send a second initial trigger message to the IoT device and release the temporary identifier. The second initial trigger message contains the second service identifier.

[0303] In the aforementioned temporary identifier management method for IoT devices, the temporary identifier information contained in the initial trigger message sent by the network node allows the IoT device to identify the time / frequency domain resources required for the command sent to the IoT device and the associated reporting during subsequent data transmission through the first or second temporary identifier, and release the temporary identifier in a timely manner. This eliminates the need to transmit the permanent device identifier in plaintext, ensuring the secure and successful transmission of IoT-related services.

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

[0305] Receive the first message sent by the IoT device.

[0306] The first message carries a first temporary identifier or device identifier.

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

[0308] Send a second message to the Internet of Things device. The second message includes at least one of the following: device identifier, temporary identifier information, command instruction information, and association information, as well as downlink scheduling information.

[0309] Downlink scheduling information includes the time-domain and / or frequency-domain resources required for the third message, as well as the transport block size.

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

[0311] Receive a third message sent by an IoT device, the third message containing at least one of the following: device identifier, segmented transmission identifier, inventory response information, and command response information.

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

[0313] After the second message is sent, the timer times out and determines that the third message failed to be sent, and sends a negative acknowledgment message to the IoT device.

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

[0315] Send a downlink message associated with a first temporary identifier or a second temporary identifier to an IoT device.

[0316] In an exemplary embodiment, as shown in FIG13, this disclosure provides an example flow of a temporary identifier management method for IoT devices. Taking an IoT device (AIoT device) instance as topology 1 and 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:

[0317] Step 1302: The AIoT device receives a paging message from the reader, namely the initial trigger message (Msg0), which includes a power status reporting indication, Q parameters, group ID, and service ID.

[0318] Step 1304: The AIoT device reads the Q parameter to determine that the access is a contention-based access, and calculates the number of access opportunities as 2Q-1; where the Q parameter is the number of paging cycles or access opportunities indicated in the paging message. The reader is configured with a positive integer.

[0319] Step 1306: The AIoT device reads the service ID, retrieves it from local storage, determines that the core network service has not been responded to, and generates a temporary identifier locally based on RN16.

[0320] Step 1308: The AIoT device sends Msg1, which carries the first temporary identifier, to the reader and stores the service identifier.

[0321] Step 1310: The AIoT device receives Msg2 sent by the reader, which carries an instruction to continue using the first temporary identifier, a frequency domain location indication, and "READ" command information, executes the command, and sends Msg3 carrying sensor data on the configured frequency domain resources.

[0322] In an exemplary embodiment, the reader assigns a second temporary identifier (AS ID) in the second message. The following figures show two examples of the second message: Figure 14 shows the CBRA process reported simultaneously with the first temporary identifier (random ID), and Figure 15 shows the process reported simultaneously with command information (CFA).

[0323] For example, in Figure 14, the second message includes: Message type of Msg2 - Random ID - Access Layer Temporary ID - Msg3 transmission resource.

[0324] For example, in Figure 15, the second message includes: message type - access stratum temporary identifier (AS ID) - command - downlink to random access response resource (D2R resource of command response).

[0325] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0326] Based on the same inventive concept, this application also provides a temporary identifier management system for IoT devices to implement the temporary identifier management method for IoT devices described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations of one or more embodiments of the temporary identifier management system for IoT devices provided below can be found in the limitations of the temporary identifier management method for IoT devices described above, and will not be repeated here.

[0327] In one exemplary embodiment, as shown in FIG16, a temporary identification management system 1600 for Internet of Things (IoT) devices is provided, including: IoT device 1602 and network node 1604.

[0328] The IoT device 1602 is used to receive an initial trigger message sent by the network node 1604, the initial trigger message containing a first service identifier and / or temporary identifier key information, and the first message containing a first temporary identifier; it is also used to receive a second initial trigger message sent by the network node 1604 and release the temporary identifier, the second initial trigger message containing a second service identifier; the IoT device 1602 is capable of receiving and / or sending at least one of a Non-Access Stratum (NAS) message and a Media Access Control (MAC) message.

[0329] Network node 1604 is configured to send an initial trigger message to IoT device 1602; and to send a second trigger message to IoT device 1602; and to send a second message to IoT device 1602, the second message containing at least one of device identifier, temporary identifier related information, command instruction information and association information, as well as information on time domain resources and / or frequency domain resources required for the third message and the transport block size, the device identifier including a first temporary identifier, a second temporary identifier and / or a permanent device identifier, the temporary identifier related information including an indication to reuse the first temporary identifier or to allocate a new second temporary identifier.

[0330] In this embodiment, by using the temporary identifier information contained in the initial trigger message sent by the network node, the IoT device can identify the time / frequency domain resources required for the command sent to the IoT device and the associated reporting in subsequent data transmissions through the first or second temporary identifier, and release the temporary identifier in a timely manner, thereby eliminating the need to transmit the permanent device identifier in plaintext and ensuring the secure and successful transmission of IoT-related services.

[0331] In an exemplary embodiment, the IoT device 1602 is further configured to, upon receiving a second initial trigger message, release the first service identifier if a stored first service identifier already exists, and store the second service identifier or replace the first service identifier with the second service identifier if the second initial trigger message carries a new service identifier.

[0332] In an exemplary embodiment, the IoT device 1602 is further configured to determine whether the access has failed based on the receipt of the first temporary identifier;

[0333] If the access type indicator indicates contention-based random access, and if a second message carrying the first temporary identifier is not received before the timer expires, the access is deemed to have failed, and the first service identifier is associated with the access failure information; or,

[0334] If a second message carrying the first temporary identifier is not received, and an initial trigger message carrying the first service identifier is received again from network node 1604, and IoT device 1602 stores the first service identifier and the first service identifier has no associated information, then the access is determined to have failed.

[0335] If the access type indicator indicates non-contention access, and no confirmation message for the associated first service identifier is received before the timer expires, the access is deemed to have failed.

[0336] In an exemplary embodiment, the IoT device 1602 is further configured to receive at least one first trigger message sent by a network-side 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 1602 to send the first message.

[0337] In an exemplary embodiment, the IoT device 1602 is further configured to, if the access type indicator indicates non-contention access and access fails, not associate the first service identifier information, determine the starting point of the frequency domain resources and / or time domain resources used according to the first trigger message, and resend the first message.

[0338] In an exemplary embodiment, the device identifier includes a first temporary identifier, a second temporary identifier, and / or a permanent device identifier. The temporary identifier information includes a reuse instruction or temporary identifier generation information. The reuse instruction is used to indicate that the first temporary identifier is used as a temporary identifier. The temporary identifier generation information is used to indicate the temporary identifier assigned by the network node 1604 to the IoT device 1602, or related information for generating the second temporary identifier.

[0339] In one exemplary embodiment, a segmentation transmission identifier is used to indicate whether the bit is the final data bit.

[0340] In an exemplary embodiment, the IoT device 1602 is further configured to release the first temporary identifier or the second temporary identifier if a second service identifier is present in the second initial trigger message.

[0341] If the command instruction message contains a deletion instruction, then release the first temporary identifier or the second temporary identifier;

[0342] If the fourth message received from network node 1604 contains a third temporary identifier, then release the first temporary identifier or the second temporary identifier.

[0343] If the IoT device 1602 completes the command reporting and the segmented transmission identifier indicates that the bit is the final data bit, then the first temporary identifier or the second temporary identifier is released.

[0344] In an exemplary embodiment, the IoT device 1602 is further configured to generate a second temporary identifier based on the temporary identifier key information if the initial trigger message contains temporary identifier generation information and the IoT device 1602 supports encryption algorithms.

[0345] In an exemplary embodiment, if the initial trigger message does not carry an access type indicator, the IoT device 1602 is further configured to determine the access type based on the device identifier to be triggered in the initial trigger message; or,

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

[0347] In an exemplary embodiment, as shown in FIG17, a temporary identifier management device 1700 for Internet of Things (IoT) devices is provided, comprising: a first receiving module 1702 and a second receiving module 1704, wherein:

[0348] The first receiving module 1702 is used to receive an initial trigger message sent by a network node. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier and at least one of the device identifiers.

[0349] The second receiving module 1704 is used to receive the second initial trigger message sent by the network node and release the temporary identifier. The second initial trigger message contains the second service identifier.

[0350] In one exemplary embodiment, the device 1700 further includes:

[0351] The first identifier module is used to, upon receiving the second initial trigger message, release the first service identifier if a stored first service identifier already exists, and store the second service identifier or replace the first service identifier with the second service identifier if the second initial trigger message carries a second service identifier.

[0352] In one exemplary embodiment, an access type indicator is used to indicate the access type of an IoT device; the access type indicator includes contention-based random access and non-contention-based access; the access type includes contention-based access and non-contention-based access.

[0353] In one exemplary embodiment, the device 1700 further includes:

[0354] The second identifier module is used to store the business identifier contained in the initial trigger message; wherein, the business identifier is used to identify the business request corresponding to the initial trigger message.

[0355] In one exemplary embodiment, the device 1700 further includes:

[0356] The first judgment module is used to determine whether an initial trigger message needs to be replied to based on the business identifier.

[0357] The first response 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 the current initial trigger message. If the IoT device does not store a business identifier, the second response result is determined. The second response result is that the initial trigger message has not been responded to and a response to the current initial trigger message is required.

[0358] The second response module is used to determine the following: If the IoT device stores a service identifier and the service identifier is associated with successful access information, determine the first response result, which indicates that the initial trigger message has been responded to and access was successful, and no response to this initial trigger message is required; if the IoT device stores a service identifier but the service identifier has no associated information, determine the second response result, which indicates that the initial trigger message has been responded to but access failed, and a response to this initial trigger message is required; if the IoT device stores a service identifier and the service identifier is associated with access failure information, determine the second response result, which indicates that the initial trigger message has been responded to but access failed, and a response to this initial trigger message is required; if the IoT device does not store a service identifier, determine the third response result, which indicates that the initial trigger message has not been responded to, and a response to this initial trigger message is required.

[0359] In one exemplary embodiment, the device 1700 further includes:

[0360] The first determination module is used to determine that the business process associated with the first business identifier has failed if a stored first business identifier exists and the second business identifier is the same as the first business identifier when the second initial trigger message is received.

[0361] In one exemplary embodiment, the device 1700 further includes:

[0362] The first message module is used to send the first message to the network node. The first message carries the first temporary identifier or device identifier.

[0363] In one exemplary embodiment, the device 1700 further includes:

[0364] The second message module is used to receive a second message sent by a network node. The second message includes at least one of device identifier, temporary identifier information, command instruction information and association information, as well as downlink scheduling information. The downlink scheduling information is information on the time domain resources and / or frequency domain resources required by the third message and the transport block size.

[0365] In one exemplary embodiment, the device 1700 further includes:

[0366] The second judgment module is used to determine whether the access has failed based on the receipt of the first temporary identifier.

[0367] The first association module is used to determine access failure if the access type indicator indicates contention-based random access and if a second message carrying the first temporary identifier is not received before the timer expires, and to associate the first service identifier with the access failure information.

[0368] The second association module is used to determine access failure if it does not receive a second message carrying the first temporary identifier, but receives an initial triggering message carrying the first service identifier from the network node, and the IoT device stores the first service identifier and the first service identifier has no association information.

[0369] The third association module is used to determine access failure if the access type indicator indicates non-contention access and if no confirmation message of the associated first service identifier is received before the timer expires.

[0370] In one exemplary embodiment, the device 1700 further includes:

[0371] The trigger message module is used to receive at least one first trigger message sent by the network-side 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.

[0372] In one exemplary embodiment, the device 1700 further includes:

[0373] The first retransmission module is used to, if the access type indicator indicates non-contention access and the access fails, not associate the first service identifier with the information, determine the starting point of the frequency domain resources and / or time domain resources used according to the first trigger message, and retransmit the first message.

[0374] In an exemplary embodiment, the device identifier includes a first temporary identifier, a second temporary identifier, and / or a permanent device identifier. The temporary identifier information includes a reuse instruction or temporary identifier generation information. The reuse instruction is used to indicate that the first temporary identifier is used as a temporary identifier. The temporary identifier generation information is used to indicate the temporary identifier assigned to the IoT device by the network node, or related information for generating the second temporary identifier.

[0375] In one exemplary embodiment, the device 1700 further includes:

[0376] The third message module is used to send a third message to the network node. The third message includes at least one of the following: device identifier, segmentation transmission identifier, inventory response information, and command response information.

[0377] In one exemplary embodiment, a segmentation transmission identifier is used to indicate whether the bit is the final data bit.

[0378] In one exemplary embodiment, the device 1700 further includes:

[0379] The negative reception module is used to determine whether the third message or the first message associated with the stored first service identifier has failed to be sent if a negative acknowledgment message is received from a network node.

[0380] In one exemplary embodiment, the device 1700 further includes:

[0381] The negation retransmission module is used to resend a third message to the network node if a negative acknowledgment message is received. The third message may include a segmented response message or an unsegmented response message.

[0382] In an exemplary embodiment, the second receiving module 1704 is further configured to release the first temporary identifier or the second temporary identifier if the second initial trigger message contains a second service identifier; release the first temporary identifier or the second temporary identifier if the command indication information contains a deletion indication; release the first temporary identifier or the second temporary identifier if the fourth message sent by the network node contains a third temporary identifier; and release the first temporary identifier or the second temporary identifier if the IoT device completes command reporting and the segmented transmission identifier indicates that the bit is the final data bit.

[0383] In an exemplary embodiment, the network node includes at least one of the following: base stations of different standards, network nodes, readers, repeaters, IAB nodes, NCR devices, and user equipment; the network node has communication functions for communicating with IoT devices; the network node includes at least one reader; the reader is used for transmitting and receiving signals with IoT devices.

[0384] In one exemplary embodiment, the device 1700 further includes:

[0385] The identifier generation module is used to generate a second temporary identifier based on the temporary identifier key information if the initial trigger message contains temporary identifier generation information and the IoT device supports the encryption algorithm.

[0386] In an exemplary embodiment, if the initial trigger message does not carry an access type indicator, the device 1700 further includes:

[0387] The third judgment module is used to determine the access type based on the device identifier to be triggered in the initial trigger message.

[0388] The fourth judgment module is used to determine the access type based on the access timing in the initial trigger message.

[0389] In one exemplary embodiment, the device 1700 further includes:

[0390] The first triggering module is used to determine if the IoT device is selected by the initial triggering message when the initial triggering message does not carry the identifier of the device to be triggered.

[0391] The second triggering module is used to send the device identifier to be triggered in the initial triggering message to the higher layer. If the higher layer indicates that the device identifier to be triggered matches the device identifier, it is determined that the IoT device is selected by the first triggering message, and the higher layer generates an inventory response message, which contains the NAS message of the device identifier.

[0392] In an exemplary embodiment, if a downlink message associated with a first temporary identifier or a second temporary identifier is received from a network node, the device 1700 further includes:

[0393] The first forwarding module is used to forward upper-layer data to the non-access layer if the IoT device stores a temporary identifier associated with the downlink message, apply uplink scheduling information, and instruct the physical layer on the uplink scheduling information for subsequent uplink transmission.

[0394] The second forwarding module is used to store a temporary identifier if the IoT device does not store a temporary identifier associated with the downlink message, and the downlink message is an upper-layer data forwarding message with a contention-free access type. In this case, the module forwards the upper-layer data to the non-access layer, applies uplink scheduling information, and instructs the physical layer on the uplink scheduling information for subsequent uplink transmission.

[0395] The modules in the temporary identifier management device for the aforementioned IoT devices 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, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0396] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the above method embodiments.

[0397] In an exemplary embodiment, as shown in FIG18, a temporary identifier management device 1800 for Internet of Things (IoT) devices is provided, comprising: a first sending module 1802 and a second sending module 1804, wherein:

[0398] The first sending module 1802 is used to send an initial trigger message to an IoT device. The initial trigger message includes at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier and at least one of the device identifiers.

[0399] The second sending module 1804 is used to send a second initial trigger message to the Internet of Things device and release a temporary identifier. The second initial trigger message contains a second service identifier.

[0400] In one exemplary embodiment, the device 1800 further includes:

[0401] The first message receiving module is used to receive the first message sent by the Internet of Things device. The first message carries a first temporary identifier or device identifier.

[0402] In one exemplary embodiment, the device 1800 further includes:

[0403] The second message sending module is used to send a second message to the Internet of Things device. The second message includes at least one of the following: device identifier, temporary identifier information, command instruction information and association information, as well as downlink scheduling information.

[0404] Downlink scheduling information includes the time-domain and / or frequency-domain resources required for the third message, as well as the transport block size.

[0405] In one exemplary embodiment, the device 1800 further includes:

[0406] The third message receiving module is used to receive a third message sent by an IoT device. The third message includes at least one of the following: device identifier, segmented transmission identifier, inventory response information, and command response information.

[0407] In one exemplary embodiment, the device 1800 further includes:

[0408] The negative acknowledgment sending module is used to send negative acknowledgment messages to IoT devices.

[0409] In one exemplary embodiment, the device 1800 further includes:

[0410] The downlink message sending module is used to send downlink messages associated with a first temporary identifier or a second temporary identifier to IoT devices.

[0411] In one embodiment, a communication device is provided, as shown in FIG19. FIG19 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present invention. The terminal device 1900 shown in FIG19 includes: at least one processor 1902, a memory 1904, at least one network interface 1906, and a user interface 1908. The various components in the terminal device 1900 are coupled together through a bus system 1910. It is understood that the bus system 1910 is used to realize the connection and communication between these components. In addition to a data bus, the bus system 1910 also includes a power bus, a control bus, and a status signal bus. However, for clarity, all buses are labeled as bus system 1910 in FIG19. In addition, in this embodiment of the present invention, a transceiver 1912 is also included. The transceiver 1912 may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

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

[0413] It is understood that the memory 1904 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 (DDRSDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 1904 of the systems and methods described in this embodiment is intended to include, but is not limited to, these and any other suitable types of memory.

[0414] In some implementations, memory 1904 stores elements, executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 19041 and application program 19042.

[0415] The operating system 19041 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 19042 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 application program 19042.

[0416] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the steps in the above-described method embodiments.

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

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

[0419] The embodiments described above are merely illustrative of 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 patent application. 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 temporary identifiers of Internet of Things (IoT) devices, applied to IoT devices; the method includes: Receive an initial trigger message sent by a network node. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier and at least one of the device identifiers. If the initial trigger message does not carry the identifier of the device to be triggered, it is determined that the IoT device is selected, and the non-access layer is indicated that the IoT device is selected. Receive the second initial trigger message sent by the network node and release the temporary identifier; wherein, the second initial trigger message contains a second service identifier; When a second initial trigger message is received, if the second initial trigger message carries a second service identifier and the second service identifier is different from the stored first service identifier, then the stored first service identifier is released or cleared, and the second service identifier is stored, or the stored first service identifier is replaced with the second service identifier. 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 access; the access type includes contention-based access and non-contention-based access; If the access type indicator contained in the second initial trigger message is a non-contentionable access, release the temporary identifier; A third message is sent to the network node, the third message containing at least one of a device identifier, a segmented transmission identifier, a disk response information, and a command response information; the segmented transmission identifier is used to indicate whether the bit is the final data bit, that is, whether there is any subsequent data to be sent; If a negative acknowledgment message is received from the network node, and the temporary identifier information contained in the negative acknowledgment message is consistent with the temporary identifier stored locally, the temporary identifier is released.

2. The method according to claim 1, wherein the method further comprises: Store the service identifier contained in the initial trigger message; The service identifier is used to identify the service request corresponding to the initial trigger message.

3. The method according to claim 1, wherein the method further comprises: Based on the first service identifier, determine whether it is necessary to reply to the initial trigger message, and based on the second service identifier, determine whether it is necessary to reply to the second initial trigger message; If the IoT device does not store the first service identifier or the second service identifier, it is determined that it has not responded to the corresponding initial trigger message, and it needs to respond to the current initial trigger message or the second initial trigger message. If the IoT device has stored the first service identifier or the second service identifier, and the stored service identifier is associated with successful access information, then it is determined that the corresponding initial trigger message has been responded to and the network access has been successful, and there is no need to respond to this initial trigger message or the second initial trigger message. If the IoT device has stored the first service identifier or the second service identifier, and the stored service identifier currently has no associated information, then: It has been determined that a response has already been made to the corresponding initial trigger message, and there is no need to respond to this initial trigger message or the second initial trigger message; or If it has been determined that a response has been made to the corresponding initial trigger message but the access failed, a response is required to the current initial trigger message or the second initial trigger message.

4. The method according to claim 3, wherein the method further comprises: If the IoT device has stored the first service identifier or the second service identifier, and the stored service identifier is associated with access failure information, then it is determined that a response has been made to the corresponding initial trigger message but access failed, and a response is required to this initial trigger message or the second initial trigger message: When a negative acknowledgment (NACK) message is received from the network side or a timer expires, the locally stored service identifier is associated with the access failure information.

5. The method according to claim 1, wherein the method further comprises: Upon receiving the second initial trigger message, if a first business identifier already exists and the second business identifier is the same as the first business identifier, then the business process associated with the first business identifier is determined to have failed.

6. The method according to claim 1, wherein the method further comprises: A first message is sent to the network node, the first message carrying a first temporary identifier or device identifier.

7. The method according to claim 1, wherein the method further comprises: The system receives a second message sent by the network node, the second message containing at least one of device identifier, temporary identifier information, command instruction information and association information, as well as downlink scheduling information; The downlink scheduling information is the information on the time-domain resources and / or frequency-domain resources required for the third message, as well as the transport block size.

8. The method according to claim 1, wherein the method further comprises: Based on the receipt of the first temporary identifier, determine whether the access has failed; If the access type indicator indicates contention-based random access, and if a second message carrying the first temporary identifier is not received before the timer expires, the access is determined to have failed, and the first service identifier is associated with the access failure information. or, If a second message carrying the first temporary identifier is not received, and if an initial trigger message carrying the first service identifier is received again from the network node, and the IoT device stores the first service identifier and the first service identifier has no associated information, then the access is determined to have failed. If the access type indicator indicates non-contention access, and no confirmation message associated with the first service identifier is received before the timer expires, the access is determined to have failed.

9. The method according to claim 1, wherein the method further comprises: The device receives at least one first trigger message sent by the network-side 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.

10. The method of claim 9, wherein the method further comprises: If the access type indicator indicates non-contention access and access fails, the first service identifier is not associated with the information. The starting point of the frequency domain resources and / or time domain resources used is determined according to the first trigger message, and the first message is resent.

11. The method of claim 7, wherein the device identifier includes a first temporary identifier, a second temporary identifier, and / or a permanent device identifier, and the temporary identifier information includes a reuse instruction or temporary identifier generation information; the reuse instruction is used to indicate that the first temporary identifier is used as a temporary identifier; the temporary identifier generation information is used to indicate the temporary identifier assigned by the network node to the IoT device, or related information for generating the second temporary identifier.

12. The method according to claim 1, wherein the method further comprises: If a negative acknowledgment message is received from the network node, it is determined that the third message or the first message associated with the stored first service identifier has failed to be sent.

13. The method according to claim 1, wherein the method further comprises: If a negative acknowledgment message is received from the network node, a third message is resent to the network node. The third message may include a segmented response message or an unsegmented response message.

14. The method of claim 1, wherein the release of the temporary identifier further comprises: If the second service identifier exists in the second initial trigger message, then release the first temporary identifier or the second temporary identifier; Alternatively, if the command instruction information contains a deletion instruction, then release the first temporary identifier or the second temporary identifier; Alternatively, if a third temporary identifier is received in the fourth message sent by the network node, the first temporary identifier or the second temporary identifier is released. Alternatively, if the IoT device completes the command reporting and the segmented transmission identifier indicates that the bit is the final data bit, then the first temporary identifier or the second temporary identifier is released. Alternatively, if the IoT device loses power, the first temporary identifier or the second temporary identifier is released.

15. The method of claim 1, wherein the network node comprises any one of a reader and an intermediate node device; The network node has communication capabilities to communicate with the IoT device; the reader is used to send and receive signals with the IoT device. The intermediate node devices include repeaters, IAB integrated access and backhaul nodes, network control relays (NCRs), and user equipment.

16. The method of claim 1, wherein the method further comprises: If the initial trigger message contains temporary identifier generation information and the IoT device supports encryption algorithms, then a second temporary identifier is generated based on the temporary identifier key information.

17. The method according to claim 1, wherein if the initial trigger message does not carry the access type indicator, the method further comprises: The access type is determined based on the device identifier to be triggered in the initial trigger message; or, The access type is determined based on the access timing in the initial trigger message.

18. The method of claim 1, wherein the method further comprises: The initial trigger message carries the identifier of the device to be triggered. The identifier of the device to be triggered in the initial trigger message is sent to the non-access layer. If the non-access layer indicates that the identifier of the device to be triggered matches the device identifier, it is determined that the IoT device is selected by the first trigger message, and the non-access layer generates a disk storage response message. The disk storage response message contains the NAS message of the device identifier.

19. The method of claim 1, wherein if a downlink message associated with a first temporary identifier or a second temporary identifier is received from the network node, the method further comprises: If the IoT device stores a temporary identifier associated with the downlink message, the IoT device will compare the temporary identifier in the downlink message with the temporary identifier stored locally to confirm that the message target is itself. Then, it will forward the upper-layer data in the message to the non-access layer, apply the uplink scheduling information, and instruct the physical layer on the uplink scheduling information for subsequent uplink transmission. If the IoT device does not store a temporary identifier associated with the downlink message, and the downlink message is an upper-layer data forwarding message with a contention-free access type, then the temporary identifier in the downlink message is stored, the upper-layer data is forwarded to the non-access layer, uplink scheduling information is applied, and the uplink scheduling information is indicated to the physical layer for subsequent uplink transmission.

20. A method for managing temporary identifiers of Internet of Things (IoT) devices, applied to network nodes; the method includes: Send an initial trigger message to an IoT device. The initial trigger message contains at least one of the following: relevant information of the device to be triggered, access type indicator, first service identifier, and temporary identifier information. The relevant information of the device to be triggered includes the length information of the device identifier to be triggered and at least one of the device identifiers to be triggered. Send a second initial trigger message to the IoT device to release a temporary identifier. The second initial trigger message contains a second service identifier.

21. The method of claim 20, wherein the method further comprises: Receive a first message sent by the IoT device, the first message carrying a first temporary identifier or device identifier.

22. The method of claim 20, wherein the method further comprises: Send a second message to the IoT device, the second message containing at least one of device identifier, temporary identifier information, command instruction information and association information, as well as downlink scheduling information; The downlink scheduling information is the information on the time-domain resources and / or frequency-domain resources required for the third message, as well as the transport block size.

23. The method of claim 20, wherein the method further comprises: The third message sent by the IoT device is received, the third message including at least one of device identifier, segmented transmission identifier, inventory response information and command response information.

24. The method of claim 20, wherein the method further comprises: After the second message is sent, the timer times out and determines that the third message has failed to be sent, and sends a negative confirmation message to the IoT device.

25. The method of claim 20, wherein the method further comprises: Send a downlink message associated with a first temporary identifier or a second temporary identifier to the IoT device.

26. A temporary identification management system for Internet of Things (IoT) devices, comprising: An IoT device is configured to receive an initial trigger message sent by a network node, the initial trigger message containing a first service identifier and / or temporary identifier key information, the first message containing a first temporary identifier; and is also configured to receive a second initial trigger message sent by the network node, and release the temporary identifier, the second initial trigger message containing a second service identifier; the IoT device is capable of receiving and / or sending at least one of a Non-Access Stratum (NAS) message and a Media Access Control (MAC) message; Network nodes are used to send initial trigger messages to the IoT devices; It is also used to send a second trigger message to the IoT device; It is also used to send a second message to an Internet of Things device, the second message containing at least one of device identifier, temporary identifier related information, command instruction information and association information, as well as information on time domain resources and / or frequency domain resources required for the third message and the transport block size, the device identifier including the first temporary identifier, the second temporary identifier and / or the device permanent identifier, the temporary identifier related information including an indication to reuse the first temporary identifier or to allocate a new second temporary identifier.

27. The system according to claim 26, wherein the IoT device is further configured to, upon receiving the second initial trigger message, release the first service identifier if a stored first service identifier already exists, and store the second service identifier or replace the first service identifier with the second service identifier if the second initial trigger message carries a new service identifier.

28. The system of claim 26, wherein the IoT device is further configured to determine whether the access has failed based on the receipt of the first temporary identifier; If the access type indicator indicates contention-based random access, and if a second message carrying the first temporary identifier is not received before the timer expires, the access is determined to have failed, and the first service identifier is associated with the access failure information. or, If a second message carrying the first temporary identifier is not received, and if an initial trigger message carrying the first service identifier is received again from the network node, and the IoT device stores the first service identifier and the first service identifier has no associated information, then the access is determined to have failed. If the access type indicator indicates non-contention access, and no confirmation message associated with the first service identifier is received before the timer expires, the access is determined to have failed.

29. The system of claim 26, wherein the IoT device is further configured to receive at least one first trigger message sent by the network-side device, the first trigger message being 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.

30. The system of claim 26, wherein the IoT device is further configured to, if the access type indicator indicates non-contention access and access fails, not associate the first service identifier with information, determine the starting point of the frequency domain resources and / or time domain resources used according to the first trigger message, and resend the first message.

31. The system of claim 26, wherein the device identifier includes a first temporary identifier, a second temporary identifier, and / or a permanent device identifier, and the temporary identifier information includes a reuse instruction or temporary identifier generation information; the reuse instruction is used to indicate that the first temporary identifier is used as a temporary identifier; the temporary identifier generation information is used to indicate the temporary identifier assigned by the network node to the IoT device, or related information for generating the second temporary identifier.

32. The system of claim 26, wherein the segmentation transmission identifier is used to indicate whether a bit is a final data bit.

33. The system of claim 26, wherein the IoT device is further configured to release the first temporary identifier or the second temporary identifier if a second service identifier is present in the second initial trigger message; If the command instruction information contains a deletion instruction, then release the first temporary identifier or the second temporary identifier; If a third temporary identifier is received in the fourth message sent by the network node, then the first temporary identifier or the second temporary identifier is released. If the IoT device completes the command reporting and the indicator bit in the segmented transmission identifier is the final data bit, then the first temporary identifier or the second temporary identifier is released.

34. The system according to claim 26, wherein the IoT device is further configured to generate a second temporary identifier based on the temporary identifier key information if the initial trigger message contains temporary identifier generation information and the IoT device supports an encryption algorithm.

35. The system according to claim 26, wherein if the initial trigger message does not carry an access type indicator, the IoT device is further configured to determine the access type based on the device identifier to be triggered in the initial trigger message; or, The access type is determined based on the access timing in the initial trigger message.