Passive iot tag management method and device, electronic equipment and storage medium

Abstract

The application provides a passive Internet of Things label management method and device, electronic equipment and a storage medium. A NAS message sent by a target network is received. Time information in EMM information is determined according to the NAS message. A first validity result of the passive Internet of Things label is obtained according to the time information in the EMM and a first use validity period in the passive Internet of Things label. If the first validity result indicates that the passive Internet of Things label is invalid, the passive Internet of Things label is controlled to block communication, thereby facilitating management of the passive Internet of Things label.

Description

Technical Field

[0001] This application relates to the field of passive IoT technology, and in particular to a passive IoT tag management method, device, electronic device and storage medium. Background Technology

[0002] With the rapid development of IoT technology, passive IoT technology, as an efficient and low-cost IoT technology, has gradually been widely used. Unlike other IoT tags, passive IoT tags do not require battery power, so they can continue to function even if lost or discarded.

[0003] However, once a passive IoT tag loses its binding to a specific device or cargo, the information transmitted by the passive IoT tag becomes meaningless, and the invalid tag will also increase the communication burden of the base station and occupy valuable network resources.

[0004] Therefore, passive IoT tags in the existing technology have the problem of being difficult to manage. Summary of the Invention

[0005] This application provides a passive IoT tag management method, device, electronic device, and storage medium to solve the technical problem of the difficulty in managing passive IoT tags.

[0006] Firstly, this application provides a passive IoT tag management method, including:

[0007] Receive NAS messages sent by the target network;

[0008] Based on the NAS message, determine the time information in the EMM information;

[0009] Based on the time information in the EMM and the first validity period in the passive IoT tag, the first validity result of the passive IoT tag is obtained;

[0010] If the first validity result indicates that the passive IoT tag is invalid, then control the passive IoT tag to block communication.

[0011] Optionally, the method described above, before obtaining the first validity result of the passive IoT tag based on the time information in the EMM and the first validity period in the passive IoT tag, includes:

[0012] In response to the user's activation of the passive IoT tag, the first validity period of the passive IoT tag is determined and stored.

[0013] Optionally, the method described above, after obtaining the first validity result of the passive IoT tag based on the time information in the EMM and the first validity period in the passive IoT tag, includes:

[0014] If the first validity result indicates that the passive IoT tag is invalid, then the passive IoT tag is controlled to abandon the operation of the current service, and before receiving the next service, the step of receiving the NAS message sent by the target network is re-executed, wherein the current service is the service to be executed by the passive IoT tag, and the next service is the service following the current service.

[0015] Optionally, in the method described above, a registration message is sent to the AMF unit of the target network, so that the AMF unit receives first response information fed back by the UDM unit according to the registration message, and generates registration rejection information and a first processing strategy for the next registration request sent to the passive IoT tag according to the first response information. The first response information is response information representing the validity of the passive IoT tag fed back by the UDM unit according to the first query request sent by the AMF unit. The first query request is generated according to the registration message, and the first processing strategy is determined according to the 3GPP standard.

[0016] Receive the registration rejection information fed back by the AMF unit;

[0017] Based on the registration rejection information fed back by the AMF unit, the second validity result of the passive IoT tag is determined.

[0018] Optionally, the method described above, before sending a registration message to the AMF unit of the target network, so that the AMF unit receives first response information from the UDM unit according to the registration message, and generates a registration rejection message and a first processing strategy for the next registration request sent to the passive IoT tag according to the first response information, includes:

[0019] In response to the user's activation of the passive IoT tag, the second validity period of the passive IoT tag is determined;

[0020] The second validity period of the passive IoT tag is sent and stored in the UDM unit.

[0021] Optionally, after determining the second validity result of the passive IoT tag using the method described above, the process includes:

[0022] Compare the first validity result with the second validity result;

[0023] If the second validity result indicates that the passive IoT tag is invalid, and the first validity result indicates that the passive IoT tag is valid, a request to extend the limited period is generated.

[0024] Optionally, using the method described above, a service message is sent to the SMF / UPF unit of the target network, so that the SMF / UPF unit of the target network receives a second response message from the UDM unit based on the service message, and generates a service rejection message and a second processing strategy for the next service message to be sent to the passive IoT tag based on the second response message. The second response message is a response message from the UDM unit that characterizes the validity of the passive IoT tag based on the second query request sent by the SMF / UPF unit. The second query request is generated based on the service message, and the second processing strategy is determined according to the 3GPP standard.

[0025] Receive the service rejection information fed back by the SMF / UPF unit;

[0026] Based on the service rejection information fed back by the SMF / UPF unit, the third validity result of the passive IoT tag is determined.

[0027] Optionally, the method described above, before sending a service message to the SMF / UPF unit of the target network, so that the SMF / UPF unit of the target network receives a second response message from the UDM unit based on the service message, and generates a service rejection information and a second processing strategy for the next service message sent to the passive IoT tag based on the second response message, includes:

[0028] In response to the user's activation of the passive IoT tag, the third validity period of the passive IoT tag is determined;

[0029] The third validity period of the passive IoT tag is sent and stored in the UDM unit.

[0030] Secondly, this application provides a passive IoT tag management device, comprising:

[0031] The acquisition module is used to receive NAS messages sent by the target network.

[0032] The determination module is used to determine the time information in the EMM information based on the NAS message.

[0033] The judgment module is used to obtain the first validity result of the passive IoT tag based on the time information in the EMM and the first validity period in the passive IoT tag.

[0034] The processing module is used to control the passive IoT tag to block communication.

[0035] Thirdly, this application provides an electronic device, including a processor and a memory communicatively connected to the processor;

[0036] The memory stores computer-executed instructions;

[0037] The processor executes computer execution instructions stored in the memory to implement the above method.

[0038] Fourthly, this application provides a storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the above-described method.

[0039] The passive IoT tag management method, apparatus, electronic device, and storage medium provided in this application receive NAS messages sent by a target network; determine the time information in the EMM information based on the NAS messages; obtain a first validity result of the passive IoT tag based on the time information in the EMM and the first validity period in the passive IoT tag; if the first validity result indicates that the passive IoT tag is invalid, control the passive IoT tag to block communication, making the passive IoT tag easy to manage and avoiding invalid tags from occupying too many network resources. Attached Figure Description

[0040] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0041] Figure 1 Flowchart of the passive IoT tag management method provided in the embodiments of this application Figure 1 ;

[0042] Figure 2 Flowchart of the passive IoT tag management method provided in the embodiments of this application Figure 2 ;

[0043] Figure 3 Flowchart of the passive IoT tag management method provided in the embodiments of this application Figure 3 ;

[0044] Figure 4 Flowchart of the passive IoT tag management method provided in the embodiments of this application Figure 4 ;

[0045] Figure 5 This is a schematic diagram of the passive IoT tag management device provided in the embodiments of this application;

[0046] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0047] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0048] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0049] Passive IoT is a new type of IoT technology that allows network nodes to harvest energy from the environment, enabling data sensing, transmission, and distributed computing. These nodes have no power cords or built-in batteries, yet still perform data collection, transmission, and distributed computing functions. Due to their battery-free nature, passive IoT tags can be adapted for large-scale deployments and are widely used in logistics, warehousing, and retail.

[0050] Passive IoT tags typically rely on relay devices for signal transmission. Located within the range of the passive IoT tag, the relay device connects to the tag via wireless communication technologies such as RFID, Bluetooth, or NFC (Near Field Communication). The relay device reads data from the tag through wireless communication and transmits the data to the base station. The base station then connects to the core network to transmit the data to the backend system for processing and analysis. Within the range of the passive IoT tag, it can achieve data collection and transmission through these methods.

[0051] In existing technologies, passive IoT tags can be lost or discarded at any time, rendering the information they transmit meaningless. For example, a discarded passive IoT tag can communicate with a base station and report its location, but since it is no longer bound to a specific device, its location is meaningless for the application layer and increases the communication burden on the base station, consuming network resources. Furthermore, traditional passive IoT technologies lack management of the validity period of passive IoT tags, making it impossible to determine whether a tag is still valid. This allows expired passive IoT tags to continue communicating with the network, further increasing network resource consumption and waste.

[0052] To address the aforementioned issues, this application provides a passive IoT tag management method. This method involves receiving a NAS message from a target network; determining the time information in the EMM information based on the NAS message; obtaining a first validity result for the passive IoT tag based on the time information in the EMM and the validity period in the passive IoT tag; and blocking communication for the passive IoT tag if the first validity result indicates that the passive IoT tag is invalid. Therefore, by determining whether the passive IoT tag is within its validity period, communication can be blocked for tags outside the validity period, thus preventing invalid passive IoT tags from consuming excessive network resources.

[0053] The passive IoT tag management method provided in this application is implemented by a passive IoT tag. This implementation can receive NAS messages sent by the target network; determine the time information in the EMM information based on the NAS message; obtain a first validity result for the passive IoT tag based on the time information in the EMM and the validity period in the passive IoT tag; if the first validity result indicates that the passive IoT tag is invalid, then the passive IoT tag can be controlled to block communication.

[0054] NAS messages are used for non-access stratum communication between mobile terminals and networks. NAS messages carry EMM (EPS Mobility Management) information identifiers, which are used to carry information related to EPS mobility management. The target network, also known as the core network, is the central hub of the entire mobile communication network, responsible for the transmission, processing, and management of all signals. In IoT technology, the core network can act as a connection node between passive IoT tags and applications, transmitting information from passive IoT tags to various applications to enable various intelligent applications.

[0055] The EMM information includes parameters such as Local time zone, Universal time, and Network daylight saving time. When a passive IoT tag receives EMM information, it can determine the time information when it received the EMM information, and then determine whether it is within the validity period based on the time information.

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

[0057] Figure 1 This is a flowchart illustrating the passive IoT tag processing method provided in this application embodiment. The executing entity of this method can be a passive IoT tag or a server; this embodiment does not impose any particular limitations. Figure 1 As shown, the method may include:

[0058] S101, Receive NAS messages sent by the target network.

[0059] S102. Based on the NAS message, determine the time information in the EMM information.

[0060] S103. Based on the time information in the EMM and the first validity period in the passive IoT tag, obtain the first validity result of the passive IoT tag.

[0061] In passive IoT tags, the initial validity period is a self-defined effective usage period during which the tag can function normally. The initial validity period can be determined by the tag's structural design based on the data transmission frequency. The structure of the passive IoT tag is designed according to the circuitry and supporting electrical components based on the data transmission frequency, thus ensuring a definable initial validity period. When determining the data transmission frequency, factors such as the tag's battery life, data storage capacity, actual application scenarios, and alternative solutions need to be comprehensively considered to ensure the tag functions normally and meets relevant requirements.

[0062] The first validity result of the passive IoT tag is obtained based on time information and the first validity period. The first validity result includes valid and invalid. If valid, the passive IoT tag works normally. If invalid, the passive IoT tag terminates or stops working.

[0063] In some instances of this application, prior to step S103, a first validity period is agreed upon for the passive IoT tag, specifically as follows:

[0064] In response to a user's activation of a passive IoT tag, the first validity period of the passive IoT tag is determined and stored.

[0065] The first validity period of a passive IoT tag is determined by the frequency of its data transmission, which ensures that the first validity period of the tag is determined based on actual usage and user needs, thereby better meeting user needs and usage scenarios.

[0066] In some instances of this application, after the validity period result is used to characterize the passive IoT tag as invalid, the passive IoT tag can be processed as follows:

[0067] If the first validity result indicates that the passive IoT tag is invalid, then the passive IoT tag is controlled to abandon the operation of the current service, and before receiving the next service, the step of receiving the NAS message sent by the target network is re-executed.

[0068] The current service is the service that the passive IoT tag is about to execute, and the next service is the service following the current service, that is, the new service that needs to be executed after the current service is abandoned. After re-executing the step of receiving NAS messages sent by the target network, the passive IoT tag can obtain new time and status information, thus enabling it to correctly execute the next service.

[0069] When it is determined that the passive IoT tag has expired, in addition to blocking communication, the passive IoT tag can also be made to abandon the current service operation and re-execute the step of receiving NAS messages sent by the target network before receiving the next service.

[0070] Specifically, the current business operation can be understood as the task that the passive IoT tag needs to perform, such as reading data, writing data, or performing authentication. When the passive IoT tag fails, these operations may fail or produce incorrect results. Therefore, abandoning the current business operation can avoid the impact of invalid operations on subsequent data processing and business execution.

[0071] Through the above processing steps, this embodiment can more effectively handle failed passive IoT tags and avoid adverse effects on the IoT system. Simultaneously, re-executing the step of receiving NAS messages sent by the target network can also help the passive IoT tag restore its normal state and function.

[0072] S104. If the first validity result indicates that the passive IoT tag is invalid, then control the passive IoT tag to block communication.

[0073] If a passive IoT tag is determined to be invalid, its communication interface will be blocked. This can be achieved through software or hardware methods, such as disabling the passive IoT tag's communication module or setting it to silent mode. This prevents invalid tags from continuing to occupy network resources and causing erroneous operations.

[0074] This application embodiment can also stipulate the validity period of passive IoT tags on the network side, so as to determine whether the passive IoT tag is valid when it is registered. The specific steps are as follows:

[0075] In response to the user's activation of the passive IoT tag, the second validity period of the passive IoT tag is determined.

[0076] When a user needs to activate a passive IoT tag, this operation can be triggered through a corresponding device or application. The activation process may include steps such as activating the passive IoT tag, setting its usage parameters, and allocating resources. User operations can be performed through a user interface, such as by entering commands, selecting options, or scanning the passive IoT tag.

[0077] After responding to the user's card activation, the system needs to determine the second validity period of the passive IoT tag. This second validity period differs from the first. It can be determined based on the user's needs and settings, or it can be determined based on the system's default configuration or rules. For example, the user can set parameters such as the usage duration and validity period of the passive IoT tag according to actual needs, and the system will calculate the second validity period based on these parameters.

[0078] Then, the second validity period of the passive IoT tag is sent and stored in the UDM unit.

[0079] After determining the second validity period of the passive IoT tag, the system needs to send and store this information to the UDM unit. The UDM unit is a unified data management unit responsible for managing and storing data and information related to the passive IoT tag. By sending the second validity period to the UDM unit, the accuracy and consistency of this information can be ensured, and subsequent management and use of the passive IoT tag can be facilitated.

[0080] Sending the second validity period to the UDM unit can be achieved through network communication, such as transmitting the information to the server or database where the UDM unit resides via a wireless or wired network. Storing the second validity period can employ appropriate data structures and storage methods to ensure data reliability and security.

[0081] In this way, this embodiment can provide more flexible and personalized services to meet the needs of different users. At the same time, by sending and storing the second validity period to the UDM unit, the accuracy and consistency of passive IoT tag-related data can be ensured, improving the reliability and stability of the system.

[0082] Furthermore, in this embodiment of the application, when a passive IoT tag is registered, the validity determination can be used to decide whether to allow its registration and activation, specifically including the following steps:

[0083] First, a registration message is sent to the AMF (Access and Mobility Management Function) unit of the target network, so that the AMF unit receives the first response information fed back by the UDM unit based on the registration message, and generates a registration rejection message and a first processing strategy for the next registration request sent to the passive IoT tag based on the first response information.

[0084] The registration message contains relevant information about the passive IoT tag, such as authentication information and communication parameters. By sending the registration message, the passive IoT tag indicates its intention to register with the target network and requests relevant services.

[0085] After receiving the registration message from the passive IoT tag, the AMF unit forwards the message to the UDM unit. The UDM unit verifies the identity of the passive IoT tag and sends a first response message back to the AMF unit based on the verification result. The first response message contains information characterizing the validity of the passive IoT tag, such as the authentication result and validity period.

[0086] If the passive IoT tag fails authentication or its validity period expires, the AMF unit will generate a registration rejection message, notifying the passive IoT tag that its registration request has been rejected. Simultaneously, the AMF unit will generate a first processing strategy for the next registration request based on the first response information. This first processing strategy is determined according to 3GPP standards and may include, for example, configuring the authentication method and communication parameters for the passive IoT tag.

[0087] Secondly, the first response information is the response information representing the validity of the passive IoT tag returned by the UDM unit based on the first query request sent by the AMF unit. The first query request is generated based on the registration message, and the first processing strategy is determined according to the 3GPP standard.

[0088] Furthermore, it receives registration rejection information from the AMF unit.

[0089] The registration rejection information includes the reason for the rejection and possible handling suggestions. Based on the content of the registration rejection information, passive IoT tags can understand why their registration request was rejected and take appropriate action.

[0090] Finally, based on the registration rejection information fed back by the AMF unit, the second validity result of the passive IoT tag is determined.

[0091] If a passive IoT tag fails authentication or its validity period expires, its validity result remains invalid even if it has sent a registration message and received a response from the UDM unit. In this case, the passive IoT tag can take appropriate actions based on the second validity result, such as re-registering or taking other processing measures.

[0092] Through the above embodiments, the passive IoT tag management method of this application can more completely handle the registration process of passive IoT tags, including steps such as sending registration messages, receiving response information from UDM units, generating registration rejection information, and a first processing strategy. This ensures that passive IoT tags can correctly obtain services and avoids the impact of invalid operations on subsequent data processing and service execution. At the same time, the processing strategy determined according to 3GPP standards can also help passive IoT tags take appropriate measures to solve problems or improve their effectiveness.

[0093] In some embodiments of this application, when a passive IoT tag has both a first validity period and a second validity period after activation, and the two validity periods are different, the following steps are used to determine whether the passive IoT tag is valid:

[0094] Following the determination of the second validity result of the passive IoT tag, the following is also included:

[0095] Compare the first validity results and the second validity results;

[0096] If the second validity result indicates that the passive IoT tag is invalid, and the first validity result indicates that the passive IoT tag is valid, a request to extend the limited period is generated.

[0097] If the two results are inconsistent, further investigation or other measures may be required. If a passive IoT tag expires relative to the second validity period recorded by the UDM, but remains valid relative to the first validity period, an extension request can be generated to extend the validity period of the passive IoT tag or to provide the network with more time to confirm the tag's status. This improves the accuracy of the determination and makes the reuse of the passive IoT tag feasible. The extension request may include the passive IoT tag's identifier, the new validity period, and other relevant information.

[0098] After a passive IoT tag is registered, it may be abandoned or discarded after a period of use for various reasons. To prevent the passive IoT tag from continuing to receive service messages and thus consuming network resources, this application embodiment also provides a method to stop the passive IoT tag from receiving service messages by rejecting service requests. Specifically, it includes the following steps:

[0099] First, in response to the user's activation of the passive IoT tag, the third validity period of the passive IoT tag is determined.

[0100] Determining the third validity period is similar to determining the second validity period. When a user needs to activate a passive IoT tag, this operation can be triggered through a corresponding device or application. The activation process may include steps such as activating the passive IoT tag, setting its usage parameters, and allocating resources. User operations can be performed through a user interface, such as by entering commands, selecting options, or scanning the passive IoT tag.

[0101] After responding to the user's card activation, the system needs to determine the third validity period of the passive IoT tag. This third validity period can be determined based on the user's needs and settings, or it can be determined based on the system's default configuration or rules. For example, the user can set parameters such as the usage duration and validity period of the passive IoT tag according to actual needs, and the system will calculate the third validity period based on these parameters.

[0102] Then, the third validity period of the passive IoT tag is sent and stored in the UDM unit.

[0103] After determining the third validity period of the passive IoT tag, the system needs to send and store this information to the UDM unit. The UDM unit is a unified data management unit responsible for managing and storing data and information related to the passive IoT tag. By sending the third validity period to the UDM unit, the accuracy and consistency of this information can be ensured, and subsequent management and use of the passive IoT tag can be facilitated.

[0104] Sending the third-party usage validity period to the UDM unit can be achieved through network communication, such as transmitting the information to the server or database where the UDM unit resides via a wireless or wired network. Storing the third-party usage validity period can employ appropriate data structures and storage methods to ensure data reliability and security.

[0105] Furthermore, a service message is sent to the SMF / UPF unit of the target network, so that the SMF / UPF unit of the target network receives the second response message fed back by the UDM unit according to the service message, and generates a service rejection information and a second processing strategy for the next service message sent to the passive IoT tag according to the second response message.

[0106] The SMF (Session Management Function) and UPF (User Plane Function) are service management units in the target network, responsible for managing and controlling services and communication processes related to the passive IoT tag. When a passive IoT tag needs to perform a certain service, it needs to send a service message to the SMF / UPF unit in the target network. This message contains information related to the service, such as the passive IoT tag's identity information, service type, and required resources. This message can be sent to the SMF / UPF unit in the target network via a wireless or wired network. After receiving the service message, the SMF / UPF unit parses and processes the message, and performs corresponding service processing and resource allocation based on the information in the message.

[0107] After sending a service message to the SMF / UPF unit, the system receives a second response message from the UDM unit. This second response message contains response information characterizing the validity of the passive IoT tag, such as authentication results and resource allocation status. Based on the information in the second response message, the system can generate a service rejection message and a second processing strategy for the next service message.

[0108] The second response information is a response from the UDM unit, representing the validity of the passive IoT tag, based on the second query request sent by the SMF / UPF unit. The second query request is generated based on the service message, and the second processing strategy is determined according to the 3GPP standard. The service rejection information may include the reason for rejection and possible processing suggestions. If the service request cannot be completed due to reasons such as authentication failure of the passive IoT tag or insufficient resource allocation, the system will generate a service rejection message to notify the user. Simultaneously, the system can also generate a second processing strategy for the next service message based on the second response message, such as re-authentication or adjusting resource allocation.

[0109] Secondly, receive the service rejection information fed back by the SMF / UPF unit.

[0110] Finally, based on the service rejection information fed back by the SMF / UPF unit, the third validity result of the passive IoT tag is determined.

[0111] Passive IoT tags determine their validity based on received rejection information. If rejected, appropriate actions may need to be taken, such as re-registration or other processing measures.

[0112] Through the above steps, this application enables the verification of the validity of passive IoT tags in the target network and performs corresponding processing based on the verification results. This method ensures that only valid passive IoT tags can perform corresponding services, thereby improving the reliability and security of the system. Simultaneously, the processing strategies defined according to 3GPP standards help passive IoT tags take appropriate measures to resolve issues or improve their validity results.

[0113] The passive IoT tag management method provided in this application receives NAS messages sent by a target network; determines the time information in the EMM information based on the NAS messages; obtains a first validity result for the passive IoT tag based on the time information in the EMM and the first validity period in the passive IoT tag; if the first validity result indicates that the passive IoT tag is invalid, the passive IoT tag is controlled to block communication, thereby facilitating the management of passive IoT tags. Specifically, the passive IoT tag management method provided in this application can accurately obtain the status and time information of the passive IoT tag by receiving NAS messages sent by the target network and parsing the identification and time information therein, thereby improving the accuracy of validity verification. Furthermore, based on the validity verification result, the communication interface of the passive IoT tag can be automatically controlled to block operations, avoiding the problem of invalid tags occupying network resources and causing malfunctions. At the same time, through automated validity verification and communication blocking operations, manual intervention and management costs can be reduced, improving the operating efficiency and stability of the IoT system.

[0114] Figure 2 This application provides a passive IoT tag management method in some embodiments, wherein the execution subject of the method is a passive IoT tag, such as... Figure 2 As shown, the method may include:

[0115] S201. Deploy clock synchronization and judgment devices in passive IoT tags.

[0116] Deploy a clock synchronization device in the passive IoT tag to synchronize with the network time. Simultaneously, deploy a determination device to verify the validity of the passive IoT tag.

[0117] S202. The user activates the passive IoT tag and agrees on the validity period of the tag. This information is recorded in the passive IoT tag.

[0118] Users activate passive IoT tags and set their validity period. This information is recorded in the passive IoT tag and used as a basis for subsequent validity assessment.

[0119] S203. Receive the NAS message sent by the target network and obtain the time information in the EMM information. Compare the record's validity period with the obtained time information.

[0120] The passive IoT tag receives a NAS (Network Access Service) message from the network, which contains relevant parameters and information required for communication with the passive IoT tag. The passive IoT tag retrieves the time information from the EMM (Equipment Management Message) information in the NAS message. This time information is used to compare with the clock stored in the passive IoT tag.

[0121] S204. If the current time is not within the validity period:

[0122] It will no longer receive or judge signals (information) sent by subsequent base stations, and will no longer operate or process subsequent services; or, it will abandon the current service operation and processing, and wait for the next communication with the network.

[0123] If the current time is outside the validity period, the passive IoT tag will no longer receive or interpret signals (information) sent by subsequent base stations, and will not perform any operations or processing for subsequent services. This avoids unnecessary resource consumption and communication. If the current time is outside the validity period, the passive IoT tag will abandon the current service operation and processing, and wait for the next communication with the network. This ensures that the passive IoT tag can continue to communicate and process services within its validity period.

[0124] Figure 3 This application provides a passive IoT tag management method in some embodiments. The execution subject of this method is a server. This embodiment does not impose any special limitations on this method, which may include:

[0125] S301. When a user activates a passive IoT tag and agrees on the tag's validity period, this information is recorded in UDM (Unified Data Management).

[0126] S302. The passive IoT tag sends a registration message to the target network, and the AMF (Access and Mobility Management Function) verifies the user information with the UDM.

[0127] If the S303 UDM returns a response message indicating that the passive IoT tag has expired (illegal user), the AMF will refuse the passive IoT tag from registering on the network.

[0128] S304. In accordance with existing 3GPP standards, start timers, counters, and other parameters to respond to subsequent registration requests for the tag.

[0129] Figure 4This application provides a passive IoT tag management method in some embodiments. The execution subject of this method is a server. This embodiment does not impose any special limitations on this method, which may include:

[0130] S401. The user activates the passive IoT tag and agrees on the validity period of the tag. This information is recorded in UDM (Unified Data Management).

[0131] S402: Passive IoT tags send service messages to the target network, and SMF / UPF (Session Management Function / User Plane Function) checks user information with UDM.

[0132] If the S403 or UDM returns a response message indicating that the passive IoT tag has expired (illegal user), the MF / UPF will refuse the passive IoT tag from transmitting services on the network.

[0133] S404. In accordance with existing 3GPP standards, start timers, counters, and other parameters to respond to subsequent service requests for this tag.

[0134] The embodiments described above in this application, by performing validity checks and taking corresponding communication blocking measures within the network, can reduce the invalid resource consumption of the core network and the bearer network. By rejecting the registration and service requests of invalid or unauthorized users, network resources can be avoided for these invalid users, thereby optimizing the utilization and management of network resources. Simultaneously, by processing and responding according to 3GPP standards, network security and stability can be ensured.

[0135] Figure 5 This is a schematic diagram of the passive IoT tag management device provided in an embodiment of this application. Figure 5 As shown, the passive IoT tag management device 500 includes: an acquisition module 510, a determination module 520, a judgment module 530, and a processing module 540. Wherein:

[0136] The acquisition module 510 is used to receive NAS messages sent by the target network.

[0137] The determination module 520 is used to determine the time information in the EMM information based on the NAS message.

[0138] The judgment module 530 is used to obtain the first validity result of the passive IoT tag based on the time information in the EMM and the first validity period in the passive IoT tag.

[0139] The processing module 540 is used to control the passive IoT tag to block communication.

[0140] In this embodiment of the application, the acquisition module 510 can also be specifically used for:

[0141] In response to a user's activation of a passive IoT tag, the first validity period of the passive IoT tag is determined and stored.

[0142] In this embodiment of the application, the processing module 540 can also be specifically used for:

[0143] If the first validity result indicates that the passive IoT tag is invalid, then the passive IoT tag is controlled to abandon the operation of the current service, and before receiving the next service, the step of receiving the NAS message sent by the target network is re-executed. Here, the current service is the service to be executed by the passive IoT tag, and the next service is the service following the current service.

[0144] In this embodiment of the application, the processing module 540 can also be specifically used for:

[0145] A registration message is sent to the AMF unit of the target network, so that the AMF unit receives the first response information fed back by the UDM unit according to the registration message, and generates a registration rejection message and a first processing strategy for the next registration request sent to the passive IoT tag according to the first response information. The first response information is the response information representing the validity of the passive IoT tag fed back by the UDM unit according to the first query request sent by the AMF unit. The first query request is generated according to the registration message, and the first processing strategy is determined according to the 3GPP standard.

[0146] Receive the registration rejection message from the AMF unit;

[0147] Based on the registration rejection information fed back by the AMF unit, the second validity result of the passive IoT tag is determined.

[0148] In this embodiment of the application, the processing module 540 can also be specifically used for:

[0149] According to the service message, the second response message fed back by the UDM unit is received, and according to the second response message, the service rejection information and the second processing strategy for the next service message sent to the passive IoT tag are generated. The second response information is the response information representing the validity of the passive IoT tag fed back by the UDM unit according to the second query request sent by the SMF / UPF unit. The second query request is generated according to the service message, and the second processing strategy is determined according to the 3GPP standard.

[0150] Receive service rejection information from the SMF / UPF unit;

[0151] Based on the service rejection information fed back by the SMF / UPF unit, the third validity result of the passive IoT tag is determined.

[0152] As can be seen from the above, the passive IoT tag management device 500 in this embodiment consists of an acquisition module 510 for receiving NAS messages sent by the target network; a determination module 520 for determining the time information in the EMM information based on the NAS message; a judgment module 530 for obtaining the first validity result of the passive IoT tag based on the time information in the EMM and the first validity period in the passive IoT tag; and a processing module 540 for controlling the passive IoT tag to block communication, thereby facilitating the management of failed passive IoT tags and avoiding the failure of passive IoT tags from occupying too many resources.

[0153] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device 600 may include a processor 601 with one or more processing cores, a memory 602 with one or more computer-readable storage media, a communication component 603, and other components. The processor 601, memory 602, and communication component 603 are connected via a bus.

[0154] In the specific implementation process, at least one processor 601 executes computer execution instructions stored in memory 602, causing at least one processor 601 to execute the passive IoT tag management method described above.

[0155] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0156] In the above Figure 6 In the illustrated embodiments, it should be understood that the processor 601 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0157] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0158] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0159] In some embodiments, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the steps in any of the passive IoT tag management methods described above.

[0160] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0161] It should be further noted that although the steps in the flowchart 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 flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0162] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0163] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0164] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0165] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0166] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as these combinations of technical features do not contradict each other, they should be considered within the scope of this specification.

[0167] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0168] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A passive IoT tag management method, characterized in that, include: Receive NAS messages sent by the target network; Based on the NAS message, determine the time information in the EMM information; Based on the time information in the EMM and the first validity period in the passive IoT tag, the first validity result of the passive IoT tag is obtained; If the first validity result indicates that the passive IoT tag is invalid, then control the passive IoT tag to block communication; A registration message is sent to the AMF unit of the target network, so that the AMF unit receives the first response information fed back by the UDM unit according to the registration message, and generates a registration rejection message and a first processing strategy for the next registration request sent to the passive IoT tag according to the first response information. The first response information is the response information representing the validity of the passive IoT tag fed back by the UDM unit according to the first query request sent by the AMF unit, and the first query request is generated according to the registration message. Receive the registration rejection information fed back by the AMF unit; Based on the registration rejection information fed back by the AMF unit, the second validity result of the passive IoT tag is determined; Compare the first validity result with the second validity result; If the second validity result indicates that the passive IoT tag is invalid, and the first validity result indicates that the passive IoT tag is valid, a request to extend the limited period is generated.

2. The method according to claim 1, characterized in that, Before obtaining the first validity result of the passive IoT tag based on the time information in the EMM and the first validity period in the passive IoT tag, the method further includes: In response to the user's activation of the passive IoT tag, the first validity period of the passive IoT tag is determined and stored.

3. The method according to claim 1, characterized in that, After obtaining the first validity result of the passive IoT tag based on the time information in the EMM and the first validity period in the passive IoT tag, the method further includes: If the first validity result indicates that the passive IoT tag is invalid, then the passive IoT tag is controlled to abandon the operation of the current service, and before receiving the next service, the step of receiving the NAS message sent by the target network is re-executed, wherein the current service is the service to be executed by the passive IoT tag, and the next service is the service following the current service.

4. The method according to claim 1, characterized in that, Before sending a registration message to the AMF unit of the target network, so that the AMF unit receives first response information from the UDM unit based on the registration message, and generates a registration rejection message and a first processing strategy for the next registration request sent to the passive IoT tag based on the first response information, the method further includes: In response to the user's activation of the passive IoT tag, the second validity period of the passive IoT tag is determined; The second validity period of the passive IoT tag is sent and stored in the UDM unit.

5. The method according to claim 1, characterized in that, The method further includes: A service message is sent to the SMF / UPF unit of the target network, so that the SMF / UPF unit of the target network receives a second response message from the UDM unit according to the service message, and generates a service rejection message and a second processing strategy for the next service message to be sent to the passive IoT tag according to the second response message. The second response message is response information representing the validity of the passive IoT tag fed back by the UDM unit according to the second query request sent by the SMF / UPF unit. Receive the service rejection information fed back by the SMF / UPF unit; Based on the service rejection information fed back by the SMF / UPF unit, the third validity result of the passive IoT tag is determined.

6. The method according to claim 5, characterized in that, Before sending a service message to the SMF / UPF unit of the target network, so that the SMF / UPF unit of the target network receives a second response message from the UDM unit based on the service message, and generates a service rejection message and a second processing strategy for the next service message sent to the passive IoT tag based on the second response message, the method further includes: In response to the user's activation of the passive IoT tag, the third validity period of the passive IoT tag is determined; The third validity period of the passive IoT tag is sent and stored in the UDM unit.

7. A passive IoT tag management device, characterized in that, include: The acquisition module is used to receive NAS messages sent by the target network; The determination module is used to determine the time information in the EMM information based on the NAS message; The judgment module is used to obtain the first validity result of the passive IoT tag based on the time information in the EMM and the first validity period in the passive IoT tag; The processing module is used to control the passive IoT tag to block communication and to send a registration message to the AMF unit of the target network, so that the AMF unit receives the first response information fed back by the UDM unit according to the registration message, and generates a registration rejection message and a first processing strategy for the next registration request sent to the passive IoT tag according to the first response information. The first response information is the response information representing the validity of the passive IoT tag fed back by the UDM unit according to the first query request sent by the AMF unit, and the first query request is generated according to the registration message. Receive the registration rejection information fed back by the AMF unit; Based on the registration rejection information fed back by the AMF unit, the second validity result of the passive IoT tag is determined; Compare the first validity result with the second validity result; If the second validity result indicates that the passive IoT tag is invalid, and the first validity result indicates that the passive IoT tag is valid, a request to extend the limited period is generated.

8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that, The storage medium stores computer execution instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 6.

Images