Internet-of-things terminal management method and related apparatus

Abstract

Disclosed in the embodiments of the present application are an Internet-of-Things terminal management method and a related apparatus. The Internet-of-Things terminal management method comprises: acquiring device information of an Internet-of-Things terminal; and managing the Internet-of-Things terminal on the basis of the device information of the Internet-of-Things terminal, wherein the management comprises at least one of access management and mobility management. In the embodiments of the present application, the Internet-of-Things terminal can be managed by means of the acquired device information, thereby achieving support of environment-passive Internet-of-Things technology.

Description

Management methods and related devices for Internet of Things (IoT) terminals

[0001] This application claims priority to Chinese Patent Application No. 202311861703.9, filed on December 28, 2023, entitled "Management Method and Related Device for Internet of Things Terminal", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, specifically to a management method and related apparatus for an Internet of Things (IoT) terminal. Background Technology

[0003] Passive environmental IoT is a low-power, self-powered passive wireless communication technology used for communication between IoT devices and sensors. It utilizes energy from the environment (such as light, heat, and vibration) for power, thus eliminating the need for batteries or wires. It offers advantages such as ease of installation and low maintenance costs. Passive environmental IoT technology is suitable for various scenarios, such as smart buildings, smart homes, and industrial automation, and can be used to achieve functions such as automated control, monitoring, and data collection.

[0004] Current mobile communication technologies are designed with end-to-end network architectures and protocols in mind, assuming terminals that require battery power or wired connections. This does not support passive IoT technologies. Therefore, how to support passive IoT technologies within mobile communication networks is a problem that those skilled in the art need to continuously research and solve. Summary of the Invention

[0005] To address the aforementioned technical problems, embodiments of this application provide a management method for IoT terminals, a management device for IoT terminals, a management equipment for IoT terminals, a computer-readable storage medium, and a computer program product.

[0006] In a first aspect, embodiments of this application provide a management method for an Internet of Things (IoT) terminal, applied to a core network element of a mobile network. The method includes: acquiring device information of the IoT terminal; and managing the IoT terminal based on the device information, wherein the management includes at least one of access management and mobility management.

[0007] Secondly, embodiments of this application provide a management device for an Internet of Things (IoT) terminal, applied to a core network element of a mobile network. The device includes: an acquisition module configured to acquire device information of the IoT terminal; and a management module configured to manage the IoT terminal based on the device information, wherein the management includes at least one of access management and mobility management.

[0008] Thirdly, embodiments of this application provide another method for managing IoT terminals, applied to access network elements or non-access network elements of a mobile network. The method includes: establishing a communication connection with the IoT terminal and establishing a communication connection with the core network of the mobile network; and managing the IoT terminal based on signaling interaction with the core network, wherein the management includes at least one of access management and mobility management.

[0009] Fourthly, embodiments of this application provide another management device for an Internet of Things (IoT) terminal, applied to an access network element or a non-access network element of a mobile network. The device includes: an establishment module configured to establish a communication connection with the IoT terminal and to establish a communication connection with the core network of the mobile network; and an interaction module configured to manage the IoT terminal based on signaling interaction with the core network, wherein the management includes at least one of access management and mobility management.

[0010] Fifthly, embodiments of this application provide a management device for an Internet of Things (IoT) terminal, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the management device for the IoT terminal implements the IoT terminal management method described above.

[0011] Sixthly, embodiments of this application provide a computer-readable storage medium storing computer-readable instructions thereon, which, when executed by a computer's processor, cause the computer to perform the IoT terminal management method described above.

[0012] In a seventh aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the IoT terminal management method described above.

[0013] In the technical solutions provided in the embodiments of this application, the Internet of Things (IoT) terminal can be a terminal in the passive IoT environment. The core network element of the mobile network obtains the device information of the IoT terminal, enabling the core network to manage the IoT terminal using the obtained device information, thereby realizing support for the passive IoT environment technology.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this application. Attached Figure Description

[0015] Figure 1 is a schematic diagram of the architecture of an exemplary IoT terminal management system;

[0016] Figure 2 is a flowchart illustrating an exemplary embodiment of the present application of a method for managing an Internet of Things (IoT) terminal;

[0017] Figure 3 is a flowchart illustrating a method for managing an IoT terminal, as shown in another exemplary embodiment of this application;

[0018] Figure 4 is a flowchart illustrating a method for managing an Internet of Things (IoT) terminal, as shown in yet another exemplary embodiment of this application.

[0019] Figure 5 is a flowchart illustrating a method for managing an Internet of Things (IoT) terminal, as shown in yet another exemplary embodiment of this application.

[0020] Figure 6A illustrates the transition diagram of different sub-states of an IoT terminal;

[0021] Figure 6B is a schematic diagram of the overall state transition based on the sub-state transition process shown in Figure 6A;

[0022] Figure 7 is a flowchart illustrating a method for managing an IoT terminal, as shown in another exemplary embodiment of this application;

[0023] Figure 8 is a block diagram illustrating a management device for an Internet of Things (IoT) terminal in an exemplary embodiment of this application;

[0024] Figure 9 is a block diagram illustrating a management device for an Internet of Things (IoT) terminal, as shown in another exemplary embodiment of this application;

[0025] Figure 10 shows a schematic diagram of the structure of a computer system suitable for implementing an IoT terminal management device according to an embodiment of this application. Detailed Implementation

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

[0027] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0028] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0029] In this application, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0030] The terms "first," "second," "third," and "fourth," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. The terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0031] As mentioned earlier, passive IoT technology has advantages such as low power consumption, wireless self-powered operation, easy installation, and low maintenance costs. However, current mobile communication technologies are designed based on end-to-end network architectures and protocols that require battery power or wired connections, and therefore do not support passive IoT technology.

[0032] Compared to terminals that require battery power or wired connections, IoT terminals in passive environmental IoT may encounter some unique situations during application. For example, IoT terminals may experience intermittent power outages, such as when the battery is low or unavailable. Since these terminals rely on solar energy to operate, they can only work during the day and will be powered off at night. Another example is that, to conserve energy, IoT terminals may default to turning off their transmitters (TX) or receivers (RX), preventing the core network from obtaining real-time status information for connectivity management.

[0033] To address these unique challenges of IoT terminals in passive IoT environments, this application proposes a management system for IoT terminals.

[0034] Please refer to Figure 1, which is a schematic diagram of an exemplary IoT terminal management system architecture. The IoT terminal connects to the core network via a base station or relay device. Therefore, management of the IoT terminal can be achieved based on the signaling interaction between the base station or relay device and the core network. The device information of the IoT terminal required by the core network to manage the IoT terminal can be obtained directly from the IoT terminal or from other entities that possess the device information of the IoT terminal.

[0035] It should be noted that the IoT terminal in the example in Figure 1 may include IoT terminals in passive IoT environments, or IoT terminals in other IoT environments, and this application does not limit this.

[0036] Based on the system architecture shown in Figure 1, this application also proposes a management scheme for IoT terminals in a mobile network. The management scheme for IoT terminals provided in this application is described below.

[0037] In one exemplary embodiment, the mobile network needs to obtain device information of the IoT terminal in order to provide access and mobility management to the IoT terminal based on the device information of the IoT terminal.

[0038] For example, mobile networks can acquire device information of IoT terminals through direct or indirect means. Direct acquisition refers to the IoT terminal itself or other entities possessing the IoT terminal's device information sending this information to the mobile network. These other entities may be servers, assisting nodes, or other similar devices. Indirect acquisition refers to the mobile network, after identifying the communication connection of the IoT terminal, using the identification information obtained from identifying the IoT terminal to acquire the device information of the IoT terminal from a specific entity. This specific entity may be the same as the other entities mentioned above, or it may be a different device. For example, the specific entity may be a specific core network element; this application does not impose any limitations on this.

[0039] Whether the acquisition method is direct or indirect, a security mechanism can be introduced between the information acquirer and the information recipient. For example, the information acquirer and the information recipient can authenticate each other using a root key pre-configured in the Subscriber Identity Module (SIM) card and a preset security authentication algorithm, or they can authenticate using a SIM-free method such as a digital certificate. This application does not impose any restrictions on this.

[0040] The device information of an IoT terminal may include one or more of the following: location, application scenario, type, or other information.

[0041] The location information of an IoT terminal may include its specific location, or it may include type information corresponding to that location, such as whether it is an outdoor or indoor location. This application does not limit the content of this location information. For example, a mobile network can set management policies for an IoT terminal based on its location information. For instance, IoT terminals in indoor environments have limited mobility, so relevant management policies can be set based on this characteristic. It should be noted that this application does not limit the management policies set by the mobile network using the location information of the IoT terminal.

[0042] The application scenario information of an IoT terminal describes the application scenario in which the IoT terminal is located, such as factories, schools, roads, bridges, energy, and animal husbandry. This application does not limit the content of this application scenario. Similarly, the mobile network can also set management policies for the IoT terminal based on the application scenario information. For example, an IoT terminal installed on a bridge is usually stationary, so its mobility does not need to be managed. Likewise, this application does not restrict the management policies set by the mobile network based on the application scenario information of the IoT terminal.

[0043] The type information of the Internet of Things (IoT) terminal may include one or more of the information used to describe the energy characteristics of the IoT terminal and the information used to describe the communication connection type of the IoT terminal. This application also imposes content restrictions on this type of information.

[0044] The communication connection type of an IoT terminal can include active connection type or passive connection type. For example, in the active connection type, the IoT terminal first establishes a connection with the mobile network, then may deactivate the connection, and subsequently, when capabilities permit, may reconnect to the mobile network at a predetermined time and maintain the connection. In the passive connection type, the IoT terminal does not actively connect to the mobile network; it only establishes a connection for data transmission after being triggered by the mobile network or other devices. Therefore, the mobile network can perform network connection management for the IoT terminal based on its communication connection type, but this application does not limit the specific management strategy.

[0045] The energy characteristics of an IoT terminal may include one or more of the following: energy storage characteristics, energy collection capability, energy consumption rate, or other information. This application does not limit the specific content of the energy characteristics of an IoT terminal.

[0046] Energy storage characteristics can include either no energy storage capacity or a certain energy storage capacity. For the latter, further information on energy storage capacity, such as battery capacity, can be included.

[0047] Energy harvesting capability can include one or more of the energy harvesting methods and energy harvesting efficiency of the IoT terminal. For example, the energy harvesting methods of the IoT terminal can include one or more of solar energy, light energy, wind energy, electromagnetic energy, thermal energy, or other methods. As another example, energy harvesting efficiency can include absolute efficiency or relative efficiency. Absolute efficiency can refer to the energy harvested per unit time, while relative efficiency can refer to the percentage of energy harvested per unit time relative to the energy storage capacity of the IoT terminal.

[0048] Energy consumption rate is used to describe the efficiency of energy consumption by an IoT terminal due to communication, computing or other processing. For example, it may include one or more of the following: the absolute value of energy consumed per unit time, the percentage of energy consumed per unit time to the energy storage capacity of the IoT terminal, or the energy consumption rate of the IoT terminal due to communication.

[0049] Mobile networks can also manage network connections to IoT terminals based on their energy characteristics. For example, if an IoT terminal is powered by solar energy and lacks energy storage capabilities, the mobile network can control data transmission to cease at night. Alternatively, based on the IoT terminal's battery capacity, energy harvesting efficiency, and energy consumption rate, the mobile network can predict when the IoT terminal will be unable to supply power, and thus control data transmission accordingly. It should be noted that this application does not limit the specific content of the mobile network's management of IoT terminals based on their energy characteristics.

[0050] As can be seen from the above, in the technical solution provided in this application, the mobile network can manage the IoT terminals, such as access or mobility, by obtaining the device information of the IoT terminals as described above, thereby enabling the support of passive IoT technology in the mobile communication network.

[0051] It should be noted that the mobile network disclosed in this application may be a 5th generation mobile communication technology (5G) network or a 6th generation mobile communication technology (6G) network, but is not limited to these.

[0052] The embodiments of this application also propose other schemes for managing IoT terminals. For example, in an exemplary embodiment, the mobile network also provides access management for IoT terminals. The mobile network's access management for IoT terminals may include two parts: radio-side access management and core network-side access management.

[0053] Wireless access management refers to the direct establishment of a connection between network devices responsible for wireless access terminals in IoT terminals and mobile networks. The network devices responsible for wireless access terminals in mobile networks can be access network elements, such as base stations, or non-access network elements, such as relay devices or other devices. This application does not limit this.

[0054] The method of wireless access management can be determined based on the communication connection type contained in the device information of the IoT terminal. For example, if the communication connection type of the IoT terminal is active connection, a communication connection is established between the IoT terminal and the network device responsible for wireless access by initiating the connection. If the communication connection type of the IoT terminal is passive connection, a communication connection is established between the IoT terminal and the network device responsible for wireless access by initiating the connection.

[0055] In the connection-initiated mode of an IoT terminal, the IoT terminal, when it has sufficient power and a need for data communication, can proactively initiate a communication connection request to the network device responsible for wireless access terminals in the mobile network. The communication connection request can carry usage information for a target network resource, which can be a shared network resource or a dedicated network resource. For shared network resources, the usage method can be contention-based random access, and the response window for random access can be extended to reduce the probability of collisions between different terminals in high-density scenarios. Dedicated network resources can be, for example, dedicated passive IoT frequency bands or wireless resources. In the latter case, it can specifically reserve specific random access codeword resources for passive IoT, thus meeting the dense deployment characteristics of IoT terminals.

[0056] In a network device responsible for initiating connections for wireless access terminals, the network device can wake up specific IoT terminals via broadcast, unicast, or multicast. For ease of management, different IoT terminals can be grouped according to application scenarios or other criteria. For example, IoT terminals with the same application scenario can be grouped together, and wake-up can be performed on a group-by-group basis. This avoids affecting all IoT terminals when waking up different ones. Different IoT terminals can also use specific wake-up information sequences in groups, and these sequences can be used as part of the identification information for the IoT terminals, enabling sequential wake-up of multiple IoT terminals within the same group.

[0057] The core network's access management is responsible for cooperating with the radio side to complete end-to-end access, including authentication during the radio side connection process and the establishment of connections at various protocol layers. These protocol layers are, for example, access layer (AS) or non-access layer (NAS) protocols, and can be divided into user plane protocols and control plane protocols. This application does not restrict the content and naming conventions of the relevant protocol layers. If the core network needs to establish a Protocol Data Unit (PDU) session, an Internet Protocol (IP) connection can be established after the PDU session is established.

[0058] In another embodiment, the mobile network also provides mobility management for IoT terminals. For example, the mobile network first needs to identify the mobility type of the IoT terminal in order to provide mobility management based on the IoT terminal's mobility type. The mobility type of the IoT terminal may include a stationary type, a first mobility type, or a second mobility type. It should be understood that the first mobility type and the second mobility type mentioned in this application are relative concepts, but the terminal's movement speed corresponding to the first mobility type should be lower than the terminal's movement speed corresponding to the second mobility type. This application does not impose specific conditions on the classification of these two types.

[0059] Mobile networks provide mobility management for IoT terminals based on their mobility type. This can be understood as setting corresponding network connection policies for IoT terminals according to their mobility type. For example, IoT terminals with a stationary mobility type do not need to perform location handover operations, and their paging mechanisms in non-idle states do not need to consider location changes. As another example, IoT terminals with a first mobility type have slow mobility, thus requiring protocols for paging and handover. IoT terminals with a second mobility type will inevitably have protocol requirements for paging and handover. This application does not limit the specific content of the mobility management strategies provided by the mobile network.

[0060] For IoT terminals of the first mobile type, network connectivity can also be optimized based on the characteristics of passive IoT environments. For example, for IoT terminals deployed indoors, the measurement frequency of neighboring cells can be reduced. The mobile network mainly manages measurement and handover decisions for the serving cell or neighbor cell that may be accessed, thereby saving energy. Another example is that the handover latency threshold can be relaxed, allowing data during handover to be retained for a longer period and forwarded to the IoT terminal when it is reactivated, thus adapting to the low-complexity and low-processing-capability requirements of passive IoT environments.

[0061] In some embodiments, network connectivity optimization may not be necessary for IoT terminals of the second mobile type. For example, outdoor-deployed IoT terminals may maintain the same measurement frequency for neighboring cells, or they may maintain the same handover delay threshold.

[0062] It should also be noted that the mobile network can identify the mobility type of an IoT terminal in the following ways: by actively receiving information, such as the IoT terminal or other entities reporting their mobility type to the mobile network; or by identifying the mobility type based on the device information of the IoT terminal; or by determining the mobility type through big data statistical learning on the application service side or configuration information from the operator. This application does not restrict the method of identifying the mobility type of the terminal.

[0063] In another embodiment, the management of the IoT terminal by the mobile network also includes the management of the IoT terminal's state. For example, the state of the IoT terminal may include at least one of several sub-states, or may be obtained by combining at least one of several sub-states:

[0064] The "deactivation sub-state" describes the deactivation of an IoT terminal by the mobile network. The deactivation of an IoT terminal by the mobile network can be temporary or permanent. IoT terminals in the permanent deactivation sub-state do not need to be reactivated, while IoT terminals in the temporary deactivation sub-state can be reactivated based on specific conditions. This embodiment does not impose any restrictions.

[0065] The power-off and energy harvesting sub-state describes the energy harvesting of an IoT terminal in the power-off state. The IoT terminal can periodically or quasi-periodically switch to this sub-state. If it has energy storage capacity, it can store energy.

[0066] The "Power off but not harvesting energy" sub-state describes an IoT terminal that is not harvesting energy while powered off.

[0067] The activation and energy harvesting sub-states describe the continuous energy harvesting of the IoT terminal in the activation state. During data transmission, the IoT terminal can perform periodic data transmission, and correspondingly turn off TX / RX while harvesting energy. If there is energy storage capability, energy storage can be performed. If there is no energy storage capability, energy harvesting and energy use can be performed simultaneously.

[0068] The "Active but not collecting energy" sub-state describes an IoT terminal that is not collecting energy while in the active state. During data transmission, the IoT terminal can perform periodic data transmission and intermittently turn off TX / RX. Since there is sufficient energy, no energy collection is performed.

[0069] In some embodiments, if the state of an IoT terminal includes a deactivated sub-state, a power-off and energy harvesting sub-state, or a power-off but not in an energy harvesting sub-state, the core network element will not perform access and mobility management on the IoT terminal.

[0070] In some embodiments, if the state of an IoT terminal includes an active and energy harvesting sub-state or an active but not in an energy harvesting sub-state, the core network element allows the IoT terminal to perform periodic data transmission.

[0071] It is understandable that the power-off and energy harvesting sub-states and the power-off but not harvesting sub-state, as shown in the example above, can be combined into a single state, such as the power-off state, or other states. In this state, the mobile network does not need to pay attention to the energy harvesting information of the IoT terminal. Similarly, the activation and continuous energy harvesting sub-states and the activation but not harvesting sub-state, as shown in the example above, can be combined into a single state, such as the activation state, or other states. In this state, the IoT terminal can perform periodic data transmission, can turn off TX / RX, and can decide whether to harvest energy based on the energy storage status.

[0072] It should also be understood that the sub-states and the merging of sub-states shown above are merely illustrative examples to facilitate understanding of the state management of IoT terminals proposed in this application, and do not imply limitation. This application allows mobile networks to manage the state of IoT terminals in other ways, including using different sub-states or merging methods. Furthermore, the names of the sub-states in the examples above can be different, and this application does not impose any limitations on this.

[0073] It should also be noted that the mobile network manages IoT terminals based on their state or sub-state, and this management can include access and mobility management.

[0074] Based on the above, it can be concluded that the IoT terminal management solution provided in this application can be an IoT terminal in a passive environmental IoT environment. Therefore, this application enhances the characteristics of mobile networks for passive environmental IoT environments, including mobile network identification of IoT terminal types, and enhancement of mobile network access and mobility management based on terminal type and capabilities, combined with the supported service layer data characteristics, to meet the connectivity and accessibility requirements of passive environmental IoT environments. Furthermore, the IoT terminal management solution provided in this application also supports protocols for new types of passive environmental IoT terminals, especially under capacity constraints, to more efficiently meet the service needs of a wider range of passive environmental IoT applications.

[0075] Based on the IoT terminal management scheme provided above, this application also proposes a corresponding IoT terminal management method. Please refer to Figure 2, which is a flowchart illustrating an exemplary embodiment of the IoT terminal management method. This method is applied to core network elements of a mobile network. These core network elements can be Access and Mobility Management Function (AMF) elements or other network elements; this application does not impose any limitations on this.

[0076] As shown in Figure 2, in an exemplary embodiment, the management method for IoT terminals includes steps S210-S220, which are described in detail below:

[0077] S210, obtain device information of IoT terminals.

[0078] The core network elements of the mobile network acquire device information from IoT terminals in order to manage the IoT terminals based on the acquired device information.

[0079] Core network elements can acquire IoT terminal device information directly or indirectly. In the direct acquisition method, the IoT terminal or other entities possessing the IoT terminal's device information proactively send this information to the core network element, which then receives the information accordingly. In the indirect acquisition method, after identifying the IoT terminal's communication connection, the core network element uses the identification information obtained from identifying the IoT terminal to retrieve the IoT terminal's device information from a specific entity. This specific entity and the other entities can be the same device or different devices; this embodiment does not impose any limitations on this.

[0080] In some embodiments, based on the security authentication mechanism between the acquirer and the acquiree of the IoT terminal's device information, the core network element also performs a security authentication interaction between the acquiree of the IoT terminal's device information and itself. Only after passing the security authentication does the core network element acquire the IoT terminal's device information based on the acquiree of the IoT terminal's device information. It is understood that the acquiree of the IoT terminal's device information mentioned in this embodiment can be the IoT terminal itself or other entities possessing the IoT terminal's device information; this embodiment does not impose any limitations on this.

[0081] It should be noted that the exemplary content of the device information of the IoT terminal can also be found in the foregoing description, and will not be repeated in this embodiment.

[0082] S220, manages the IoT terminal based on the device information of the IoT terminal, and the management includes at least one of access management and mobility management.

[0083] After obtaining the device information of the IoT terminal, the core network elements can manage the IoT terminal based on this information, including access management and / or mobility management. It should be noted that the detailed content of the IoT terminal's device information has been described above and will not be repeated in this embodiment.

[0084] For example, when the device information of an IoT terminal includes location information and / or application scenario information, the core network element can determine the relevant characteristics of the IoT terminal based on the location information and / or application scenario, and then provide corresponding management for the IoT terminal based on the relevant characteristics of the IoT terminal.

[0085] When the device information of an IoT terminal includes its communication connection type, core network elements can manage the IoT terminal based on the relevant characteristics of the IoT terminal under different communication connection types.

[0086] When the device information of an IoT terminal includes its energy characteristics, core network elements can provide corresponding management for the IoT terminal based on these energy characteristics.

[0087] It should be noted that the management provided by the exemplary core network element for the IoT terminal is described above, and will not be repeated in this embodiment. It can be seen that in the method provided in this embodiment, the core network element can learn about the relevant characteristics of the IoT terminal based on the obtained device information of the IoT terminal, and provide a matching management solution to the IoT terminal based on these relevant characteristics. When the IoT terminal is an IoT terminal in a passive environmental IoT system, it can realize support for passive environmental IoT technology in the mobile communication network.

[0088] In another exemplary embodiment, as shown in FIG3, the management method for IoT terminals further includes S310-S320, which are described in detail below:

[0089] S310 receives authentication information sent by the access network element or non-access network element of the mobile network during the process of establishing a communication connection with the Internet of Things terminal.

[0090] As mentioned earlier, IoT terminal access management includes two parts: wireless side access management and core network side access management. Wireless side access management establishes a direct connection between the IoT terminal and mobile network access network elements (such as base stations) or non-access network elements (such as relay devices). Core network side access management is responsible for cooperating with the wireless side to complete end-to-end access, including authentication during the wireless connection process and the establishment of connections at various protocol layers. Therefore, core network elements receive authentication information sent by mobile network access network elements or non-access network elements during the process of establishing a communication connection with the IoT terminal.

[0091] After the authentication information is successfully authenticated, the S320 establishes a protocol layer connection between the control plane and the user plane of the IoT terminal.

[0092] After the aforementioned authentication information is successfully authenticated, the core network element establishes protocol layer connections between the control plane and user plane of the IoT terminal, such as the AS layer or NAS layer protocols described above. Therefore, the solution provided in this embodiment can further provide access management for IoT terminals in passive IoT environments, thereby enhancing the support of mobile communication networks for passive IoT technologies.

[0093] In another exemplary embodiment, as shown in FIG4, the management method for the Internet of Things terminal further includes S410-S420, which are described in detail below:

[0094] S410, Identify the mobility type of the IoT terminal, which includes one or more of a stationary type, a first mobility type, or a second mobility type, wherein the terminal moving speed corresponding to the first mobility type is lower than the terminal moving speed corresponding to the second mobility type.

[0095] The core network elements can identify the mobility type of IoT terminals based on the device information of the IoT terminals obtained above, such as location information and / or application scenario information. Alternatively, the IoT terminals or other entities can actively report their mobility types. Or, the identification can be based on big data statistical learning from the application service side or the configuration information of the operator. No restrictions are placed on the specific methods by which the core network elements identify the mobility type of IoT terminals.

[0096] The S420 manages the mobility of IoT terminals based on their mobility type.

[0097] Based on the identified mobility type of the IoT terminal, the core network elements can manage the mobility of the IoT terminal in the following ways: Stationary IoT terminals do not require location handover operations, and the paging mechanism in non-idle states does not need to consider location changes; IoT terminals of the first mobility type exhibit slow mobility, thus requiring protocols for paging and handover; IoT terminals of the second mobility type necessarily require protocols for paging and handover. It should be understood that the mobility management of IoT terminals by the core network elements described in this embodiment is merely an example and does not imply any limitation on the specific content of mobility management.

[0098] Therefore, the solution provided in this embodiment can further enhance the support of mobile communication networks for passive IoT technology by identifying the mobility type of IoT terminals in passive IoT.

[0099] In another exemplary embodiment, as shown in FIG5, the management method for IoT terminals further includes S510-S520, which are described in detail below:

[0100] S510 identifies the status of the IoT terminal, which describes information corresponding to the energy harvesting status of the IoT terminal.

[0101] This embodiment introduces state information related to the energy state of the IoT terminal to perform mobility management on the IoT terminal. The state of the IoT terminal is usually pre-defined. For example, as described above, the state of the IoT terminal may include at least one of the following sub-states, or be obtained by combining at least one of the following sub-states: deactivated sub-state, powered off and energy harvesting sub-state, powered off but not harvesting energy sub-state, activated and energy harvesting sub-state, and activated but not harvesting energy sub-state.

[0102] It should be noted that the state content represented by each sub-state is also described above, and will not be repeated in this embodiment. The sub-states in the examples above are merely illustrative and do not represent a limitation on the sub-states of the IoT terminal. In practical application scenarios, the sub-states in the above examples can be merged to obtain the state of the IoT terminal, or the sub-states in the above examples can be directly used as the state of the IoT terminal, and this embodiment does not impose any restrictions on this.

[0103] The S520 manages the access and mobility of IoT terminals based on their status.

[0104] During the access and mobility management of IoT terminals, the IoT terminals undergo relevant transitions. As shown in Figures 6A and 6B, an exemplary state machine is used to describe the state transitions of the IoT terminal. The transitions between different sub-states of the IoT terminal require relevant triggering conditions. For example, the example "<Power Off but Not Harvesting Energy Sub-State>" is triggered by the condition of starting energy harvesting to transition to "Power Off and Energy Harvesting Sub-State>". "<Power Off and Energy Harvesting Sub-State>" is triggered by the condition of stopping energy harvesting to transition to "Power Off but Not Harvesting Energy Sub-State>". "<Active but Not Harvesting Energy Sub-State>" is triggered by the condition of starting energy harvesting to transition to "Active and Harvesting Energy Sub-State>". "<Active and Harvesting Energy Sub-State>" is triggered by the condition of stopping energy harvesting to transition to "Active but Not Harvesting Energy Sub-State>". "<Power Off but Not Harvesting Energy Sub-State>" is triggered by the power-on condition to transition to "Active and Harvesting Energy Sub-State>". "<Active and Harvesting Energy Sub-State>" is correspondingly triggered by the power-off condition to transition to "Power Off but Not Harvesting Energy Sub-State>". If a core network element sends an abolition command to an IoT terminal, the IoT terminal will transition to the <abolition sub-state> based on the received abolition command.

[0105] It should be noted that the conditional information used to trigger the transition between the various sub-states in Figures 6A and 6B is also exemplary, and Figures 6A and 6B do not imply any limitation on this conditional information.

[0106] For example, after an IoT terminal undergoes a state transition, such as whether energy harvesting is performed in the power-off state, this is done by the IoT terminal itself, and the core network elements can also record the state transition of the IoT terminal accordingly.

[0107] As can be seen from the above, the solution provided in this embodiment can further enhance the support of mobile communication networks for passive IoT technology by introducing a new state management mechanism.

[0108] Based on the IoT terminal management scheme provided above, embodiments of this application also propose another IoT terminal management method as shown in Figure 7. This method is applied to access network elements or non-access network elements of a mobile network. The access network element can be a base station, and the non-access network element can be a relay device or other equipment; this application does not impose any limitations on this.

[0109] As shown in Figure 7, in an exemplary embodiment, the management method for IoT terminals includes steps S710-S720, which are described in detail below:

[0110] The S710 establishes communication connections with IoT terminals and with the core network of the mobile network.

[0111] For mobile network access network elements or non-access network elements, they need to establish communication connections with both IoT terminals and the core network of the mobile network, thereby establishing an information transmission link between IoT terminals and the core network.

[0112] For example, the way in which an access network element or a non-access network element establishes a communication connection with an IoT terminal may include the IoT terminal initiating a communication connection request, and the access network element or the non-access network element responding to the communication connection request by establishing a communication connection with the access network element or the non-access network element accordingly.

[0113] The communication connection request initiated by an IoT terminal can carry its usage information for a target network resource. This target network resource can be a dedicated network resource, such as a wireless resource reserved for the IoT terminal by an access network element or a non-access network element that can be used without contention, or a shared network resource. This allows the access network element or non-access network element to establish a communication connection with the IoT terminal on the communication frequency band corresponding to the target network resource. If a shared network resource is to be used, the access network element or non-access network element can also reserve specific random access codeword resources for the IoT terminal, or increase the response window for random access by the IoT terminal, to meet the dense deployment characteristics of IoT terminals.

[0114] The way in which access network elements or non-access network elements establish communication connections with IoT terminals may also include sending a wake-up command to the IoT terminal covered by the network signal, thereby establishing a communication connection with the woken-up IoT terminal.

[0115] For example, access network elements or non-access network elements can send wake-up commands via broadcast, unicast, or multicast. To facilitate the management of different IoT terminals, they can also be divided into different groups according to application scenarios or other criteria. After obtaining group information from multiple IoT terminals covering the network signal, wake-up commands are sent based on this group information, with each group as the wake-up unit. This avoids affecting all IoT terminals when waking up different ones. Furthermore, when grouping IoT terminals, a wake-up order can be set for each IoT terminal within the same group to obtain a wake-up information sequence. Based on the wake-up information sequence contained in the group information, access network elements or non-access network elements sequentially send wake-up commands to the IoT terminals in the corresponding groups, thereby achieving sequential wake-up of multiple IoT terminals.

[0116] The S720 manages IoT terminals based on signaling interaction with the core network, including at least one of access management and mobility management.

[0117] Based on the information transmission link between the IoT terminal and the core network established above, access network elements or non-access network elements manage the IoT terminal through signaling interaction with the core network.

[0118] When the device information of the IoT terminal is actively reported to the core network element by the IoT terminal, the access network element or non-access network element will also receive the device information of the IoT terminal, and then transmit the received device information of the IoT terminal to the core network element so that the core network element can perform corresponding management on the IoT terminal according to the received device information of the IoT terminal.

[0119] It should be understood that, based on the information transmission link established above between the IoT terminal and the core network element, access network elements or non-access network elements can participate in the transmission process of any information required to be transmitted on this information transmission link, and are not limited to the information in the examples above. Therefore, when the IoT terminal includes an IoT terminal in passive environmental IoT, the method provided in this embodiment can support passive environmental IoT technology from the wireless side of the mobile network.

[0120] Please refer to Figure 8, which is a block diagram of an IoT terminal management device illustrated in an exemplary embodiment of this application. The device is applied to a core network element of a mobile network.

[0121] As shown in Figure 8, the exemplary IoT terminal management device 800 includes:

[0122] The acquisition module 810 is configured to acquire device information of IoT terminals;

[0123] The management module 820 is configured to manage the IoT terminal based on the device information of the IoT terminal, and the management includes at least one of access management and mobility management.

[0124] In another exemplary embodiment, the management device 800 of the Internet of Things terminal further includes a first identification module, which is configured to:

[0125] Identify the mobility type of IoT terminals. The mobility type includes one or more of the following: stationary type, first mobility type, or second mobility type. The terminal moving speed corresponding to the first mobility type is lower than the terminal moving speed corresponding to the second mobility type.

[0126] Based on the mobility type of IoT terminals, mobility management is implemented for IoT terminals.

[0127] In another exemplary embodiment, the first identification module is configured to identify the mobility type of the IoT terminal based on the device information of the IoT terminal.

[0128] In another exemplary embodiment, the first identification module is configured to: if the mobility type of the IoT terminal is stationary, then not to perform a location switching operation on the IoT terminal.

[0129] In another exemplary embodiment, the first identification module is configured to: if the mobility type of the IoT terminal is a first mobility type, then reduce the measurement frequency of neighboring cells for the IoT terminal.

[0130] In another exemplary embodiment, the first identification module is configured to relax the delay threshold for cell handover performed by the IoT terminal if the mobility type of the IoT terminal is a first mobility type.

[0131] In another exemplary embodiment, the first identification module is configured to: if the mobility type of the IoT terminal is the second mobility type, then maintain the measurement frequency of the adjacent cells for the IoT terminal unchanged.

[0132] In another exemplary embodiment, the first identification module is configured to: if the mobility type of the IoT terminal is the second mobility type, then keep the delay threshold value of the cell handover performed by the IoT terminal unchanged.

[0133] In another exemplary embodiment, the management device 800 of the Internet of Things terminal further includes a second identification module, which is configured to:

[0134] Identify the status of IoT terminals; the status of IoT terminals is used to describe information corresponding to the energy harvesting status of IoT terminals.

[0135] Based on the status of IoT terminals, access and mobility management of IoT terminals are implemented.

[0136] In another exemplary embodiment, the second identification module is further configured to:

[0137] Send a deactivation command to the Internet of Things (IoT) terminal.

[0138] In another exemplary embodiment, the state of the IoT terminal includes at least one of the following sub-states, or is obtained by combining at least one of the following sub-states:

[0139] Deprecated substate;

[0140] Power off and energy harvesting sub-states;

[0141] Power off but not in energy harvesting sub-state;

[0142] Activation and energy harvesting sub-states;

[0143] Activated but not in an energy harvesting sub-state.

[0144] In another exemplary embodiment, the management device 800 of the Internet of Things (IoT) terminal further includes an invalidation module, which is used to send an invalidation instruction to the IoT terminal, the invalidation instruction being used to trigger the IoT terminal to transition to an invalidation sub-state.

[0145] In another exemplary embodiment, the first identification module is configured to: if the state of the IoT terminal includes the abandoned sub-state, the power-off and energy harvesting sub-state, or the power-off but not in the energy harvesting sub-state, then no access and mobility management will be performed on the IoT terminal.

[0146] In another exemplary embodiment, the first identification module is configured to allow the IoT terminal to perform periodic data transmission if the state of the IoT terminal includes the activation and energy harvesting sub-state or the activation but not performing the energy harvesting sub-state.

[0147] In another exemplary embodiment, the management device 800 of the Internet of Things terminal further includes a connection module configured to:

[0148] Receive authentication information sent by access network elements or non-access network elements of the mobile network during the process of establishing a communication connection with the Internet of Things terminal;

[0149] After the authentication information is successfully authenticated, a protocol layer connection is established between the control plane and the user plane of the IoT terminal.

[0150] In another exemplary embodiment, the acquisition module 810 is further configured to receive device information of the IoT terminal sent by the IoT terminal or other entities, wherein the other entities have the device information of the IoT terminal.

[0151] In another exemplary embodiment, the acquisition module 810 is further configured to, after recognizing the communication connection of the IoT terminal, acquire the device information of the IoT terminal from a specific entity based on the device identifier of the IoT terminal.

[0152] In another exemplary embodiment, the management device 800 of the Internet of Things terminal further includes an authentication module, which is configured to perform secure authentication interaction between the party whose device information of the Internet of Things terminal is being acquired and the core network element, and only after passing the secure authentication will the device information of the Internet of Things terminal be acquired through the acquisition module 810.

[0153] In another exemplary embodiment, the device information includes one or more of location information, application scenario information, and type information.

[0154] In another exemplary embodiment, the type information includes one or more of the IoT terminal's energy characteristics and communication connection type.

[0155] In another exemplary embodiment, the energy characteristics of the IoT terminal include one or more of the following: energy storage characteristics, energy collection capability, and energy consumption rate.

[0156] In the IoT terminal management device 800 of the example above, the IoT terminal can be an IoT terminal in the passive IoT of the environment. Therefore, the core network side based on the mobile network realizes the support of the mobile network for the passive IoT technology of the environment.

[0157] Please refer to Figure 9, which is a block diagram of an IoT terminal management device shown in another exemplary embodiment of this application. The device is applied to an access network element or a non-access network element of a mobile network. The access network element can be a base station, and the non-access network element can be a relay device or other device.

[0158] As shown in Figure 9, the exemplary IoT terminal management device 900 includes:

[0159] Establish module 910, configured to establish a communication connection with the Internet of Things terminal and a communication connection with the core network of the mobile network;

[0160] The interaction module 920 is configured to manage IoT terminals based on signaling interaction with the core network, and the management includes at least one of access management and mobility management.

[0161] In another exemplary embodiment, the establishment module 910 is further configured as follows:

[0162] Receive communication connection requests sent by IoT terminals, which carry usage information for target network resources;

[0163] In response to a communication connection request, a communication connection is established with the IoT terminal on the communication frequency band corresponding to the target network resource.

[0164] In another exemplary embodiment, the target network resource includes dedicated network resources or shared network resources.

[0165] In another exemplary embodiment, the establishment module 910 is further configured to:

[0166] When a communication connection request includes usage information for shared network resources, specific random access codeword resources can be reserved for IoT terminals, or the response window for random access by IoT terminals can be increased.

[0167] In another exemplary embodiment, the establishment module 910 is further configured to: send a wake-up command to an IoT terminal covered by network signal; and establish a communication connection with the woken-up IoT terminal.

[0168] In another exemplary embodiment, the establishment module 910 is further configured to: obtain group information obtained by grouping multiple IoT terminals covered by network signals; and send a wake-up command based on the group information corresponding to the IoT terminals, with the group as the wake-up unit.

[0169] In another exemplary embodiment, the establishment module 910 is further configured to: send wake-up instructions sequentially to the IoT terminals in the corresponding group based on the wake-up information sequence contained in the group information.

[0170] In the IoT terminal management device 900 of the example above, the IoT terminal can be an IoT terminal in the passive IoT of the environment. Therefore, the wireless side based on the mobile network realizes the support of the mobile network for the passive IoT technology of the environment.

[0171] It should be noted that the IoT terminal management device and the IoT terminal management method provided in the above embodiments belong to the same concept. The specific ways in which each module and unit performs operations have been described in detail in the method embodiments and will not be repeated here. In practical applications, the IoT terminal management device provided in the above embodiments can allocate the above functions to different functional modules as needed, that is, divide the internal structure of the device into different functional modules to complete all or part of the functions described above, and this is not a limitation here.

[0172] Embodiments of this application also provide a management device for an Internet of Things (IoT) terminal, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the management device for the IoT terminal implements the management method for the IoT terminal provided in the above embodiments.

[0173] Figure 10 shows a schematic diagram of the structure of a computer system suitable for implementing an IoT terminal management device according to embodiments of this application. It should be noted that the computer system 1000 for the IoT terminal management device shown in Figure 10 is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0174] As shown in Figure 10, the computer system 1000 includes a Central Processing Unit (CPU) 1001, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 1002 or programs loaded from storage portion 1008 into Random Access Memory (RAM) 1003, such as performing the methods described in the above embodiments. The RAM 1003 also stores various programs and data required for system operation. The CPU 1001, ROM 1002, and RAM 1003 are interconnected via a bus 1004. An Input / Output (I / O) interface 1005 is also connected to the bus 1004.

[0175] The following components are connected to I / O interface 1005: an input section 1006 including a keyboard, mouse, etc.; an output section 1007 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to I / O interface 1005 as needed. Removable media 1011, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1010 as needed so that computer programs read from them can be installed into storage section 1008 as needed.

[0176] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1009, and / or installed from removable medium 1011. When the computer program is executed by central processing unit (CPU) 1001, it performs various functions defined in the system of this application.

[0177] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium, a computer-readable storage medium, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. Computer programs contained on computer-readable media can be transmitted using any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0178] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0179] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0180] Another aspect of this application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the management method for the Internet of Things (IoT) terminal as described above. This computer-readable storage medium may be included in the management device for the IoT terminal described in the above embodiments, or it may exist independently and not incorporated into the management device for the IoT terminal.

[0181] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the IoT terminal management method provided in the various embodiments described above.

[0182] The above description is merely a preferred exemplary embodiment of this application and is not intended to limit the implementation of this application. Those skilled in the art can easily make corresponding modifications or alterations based on the main concept and spirit of this application. Therefore, the scope of protection of this application should be determined by the scope of protection claimed in the claims.

[0183] It is understood that in the specific embodiments of this application, data related to device information and other information of passive IoT in the environment are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

Claims

1. A management method of an Internet of Things terminal, characterized by, The method, applied to core network elements of a mobile network, includes: Obtain the device information of the IoT terminal; The IoT terminal is managed based on its device information, and the management includes at least one of access management and mobility management.

2. The method of claim 1, wherein, The method further includes: Identify the mobility type of the IoT terminal, the mobility type including one or more of stationary type, first mobility type or second mobility type, wherein the terminal moving speed corresponding to the first mobility type is lower than the terminal moving speed corresponding to the second mobility type; Mobility management is performed on the IoT terminal based on its mobility type.

3. The method of claim 2, wherein, The identification of the mobility type of the IoT terminal includes: Based on the device information of the IoT terminal, the mobility type of the IoT terminal is identified.

4. The method according to claim 2 or 3, characterized in that, The mobility management of the IoT terminal, based on its mobility type, includes: If the mobility type of the IoT terminal is stationary, then no location switching operation will be performed on the IoT terminal.

5. The method according to claim 2 or 3, characterized in that, The mobility management of the IoT terminal, based on its mobility type, includes: If the mobility type of the IoT terminal is the first mobility type, then the measurement frequency of neighboring cells is reduced for the IoT terminal.

6. The method according to claim 2 or 3, characterized in that, The mobility management of the IoT terminal, based on its mobility type, includes: If the mobility type of the IoT terminal is the first mobility type, then the delay threshold for cell handover performed by the IoT terminal is relaxed.

7. The method of claim 2 or 3, wherein, The mobility management of the IoT terminal, based on its mobility type, includes: If the mobility type of the IoT terminal is the second mobility type, then the measurement frequency of the adjacent cells for the IoT terminal remains unchanged.

8. The method of claim 2 or 3, wherein, The mobility management of the IoT terminal, based on its mobility type, includes: If the mobility type of the IoT terminal is the second mobility type, then the delay threshold value for cell handover performed by the IoT terminal remains unchanged.

9. The method of claim 1, wherein, The method further includes: The state of the IoT terminal is identified, and the state of the IoT terminal is used to describe information corresponding to the energy harvesting state of the IoT terminal. Based on the status of the IoT terminal, access and mobility management are performed on the IoT terminal.

10. The method of claim 9, wherein, The state of the IoT terminal includes at least one of the following sub-states, or is obtained by combining at least one of the following sub-states: The deactivated sub-state is used to describe the IoT terminal being deactivated by the mobile network; Power off and energy harvesting sub-states; Power off but not in energy harvesting sub-state; Activation and energy harvesting sub-states; Activated but not in an energy harvesting sub-state.

11. The method of claim 10, wherein, The method further includes: A deregistration command is sent to the IoT terminal, which triggers the IoT terminal to transition to the deregistration sub-state.

12. The method of claim 10, wherein, The step of managing the access and mobility of the IoT terminal based on its status includes: If the state of the IoT terminal includes the abandoned sub-state, the power-off and energy harvesting sub-state, or the power-off but not in the energy harvesting sub-state, then no access and mobility management will be performed on the IoT terminal.

13. The method of claim 10, wherein, The step of managing the access and mobility of the IoT terminal based on its status includes: If the state of the IoT terminal includes the activation and energy harvesting sub-state or the activation but not in the energy harvesting sub-state, then the IoT terminal is allowed to perform periodic data transmission.

14. The method according to any one of claims 1 to 13, characterized in that, The method further includes: Receive authentication information sent by the access network element or non-access network element of the mobile network during the process of establishing a communication connection with the IoT terminal; After the authentication information is successfully authenticated, a protocol layer connection between the control plane and the user plane is established with the IoT terminal.

15. The method according to any one of claims 1 to 14, characterized in that, The process of obtaining the device information of the IoT terminal includes: The device receives device information of the IoT terminal sent by the IoT terminal or other entity, wherein the other entity has the device information of the IoT terminal.

16. The method according to any one of claims 1 to 14, characterized in that, The process of obtaining the device information of the IoT terminal includes: After identifying the communication connection of the IoT terminal, the device information of the IoT terminal is obtained from a specific entity based on the device identifier of the IoT terminal.

17. The method according to any one of claims 1 to 16, characterized in that, The device information includes one or more of the following: location information, application scenario information, and type information.

18. The method of claim 17, wherein, The type information includes one or more of the energy characteristics and communication connection types of the IoT terminal.

19. The method of claim 17, wherein, The energy characteristics of the IoT terminal include one or more of the following: energy storage characteristics, energy collection capability, and energy consumption rate.

20. A management method of an Internet of Things terminal, characterized by, The method, applied to access network elements or non-access network elements in a mobile network, includes: Establish a communication connection with the IoT terminal and establish a communication connection with the core network of the mobile network; The IoT terminal is managed based on signaling interaction with the core network, and the management includes at least one of access management and mobility management.

21. The method of claim 20, wherein, Establishing a communication connection with the IoT terminal includes: Receive a communication connection request sent by the IoT terminal, the communication connection request carrying usage information for the target network resources; In response to the communication connection request, a communication connection is established with the IoT terminal on the communication frequency band corresponding to the target network resource.

22. The method of claim 21, wherein, The target network resources include dedicated network resources or shared network resources.

23. The method of claim 22, wherein, The step of establishing a communication connection with the IoT terminal on the communication frequency band corresponding to the target network resource in response to the communication connection request includes: When the communication connection request includes usage information for the shared network resources, specific random access codeword resources are reserved for the IoT terminal, or the response window for random access of the IoT terminal is increased.

24. The method of claim 20, wherein, Establishing a communication connection with the IoT terminal includes: Send a wake-up command to IoT terminals within network signal coverage; Establish a communication connection with the awakened IoT terminal.

25. The method of claim 24, wherein, Sending a wake-up command to an IoT terminal covered by network signal includes: Obtain group information by grouping multiple IoT terminals covered by network signals; Based on the group information corresponding to the IoT terminal, a wake-up command is sent with the group as the wake-up unit.

26. The method of claim 24, wherein, The step of sending the wake-up command based on the group information corresponding to the IoT terminal, using the group as the wake-up unit, includes: Based on the wake-up information sequence contained in the group information, wake-up commands are sent sequentially to the IoT terminals in the corresponding groups.

27. A management apparatus of an Internet of Things terminal, characterized by, The device, which is used in core network elements of mobile networks, includes: The acquisition module is configured to acquire device information of the IoT terminal; The management module is configured to manage the IoT terminal based on the device information of the IoT terminal, and the management includes at least one of access management and mobility management.

28. A management apparatus of an Internet of Things terminal, characterized by, The device is used for access network elements or non-access network elements in mobile networks, and includes: The module is configured to establish a communication connection with the IoT terminal and a communication connection with the core network of the mobile network. The interaction module is configured to manage the IoT terminal based on signaling interaction with the core network, and the management includes at least one of access management and mobility management.

29. A management device of an Internet of Things terminal, characterized by, include: One or more processors; A memory for storing one or more programs, which, when executed by one or more processors, cause the management device of the Internet of Things (IoT) terminal to implement the management method of the IoT terminal as described in any one of claims 1-19 or 20-26.

30. A computer-readable storage medium, characterized in that, It stores computer-readable instructions, which, when executed by the computer's processor, cause the computer to perform the management method of the Internet of Things terminal according to any one of claims 1-19 or 20-26.

31. A computer program product comprising computer programs / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the method as described in any one of claims 1-19 or 20-26.

Images