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 method and related device of Internet of Things terminal

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 28, 2023, with application number 202311861703.9 and invention name “Management Method and Related Device for Internet of Things Terminals”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a management method and related devices for Internet of Things terminals. Background Art

[0003] Passive IoT is a low-power, self-powered wireless communication technology for IoT devices and sensors. It utilizes environmental energy (such as light, heat, and vibration) for power, eliminating the need for batteries or wiring. It offers advantages such as easy installation and low maintenance. Passive IoT technology is suitable for a variety of scenarios, such as smart buildings, smart homes, and industrial automation, enabling automated control, monitoring, and data collection.

[0004] Current mobile communication technologies, in their end-to-end network architecture and protocol design, are based on terminals that require battery power or wired connections, and do not support passive IoT technologies. Therefore, how to support passive IoT technologies within mobile communication networks remains a challenge that researchers in this field must continuously research and address. Summary of the Invention

[0005] To solve the above technical problems, the embodiments of the present application provide a management method for an Internet of Things terminal, a management apparatus for an Internet of Things terminal, a management device for an Internet of Things terminal, a computer-readable storage medium, and a computer program product.

[0006] In the first aspect, an embodiment of the present application provides a management method for an Internet of Things terminal, which is applied to a core network element of a mobile network, and the method includes: obtaining device information of the Internet of Things terminal; managing the Internet of Things terminal according to the device information of the Internet of Things terminal, and the management includes at least one of access management and mobility management.

[0007] In the second aspect, an embodiment of the present application provides a management device for an Internet of Things terminal, which is applied to a core network element of a mobile network. The device includes: an acquisition module, configured to obtain device information of the Internet of Things terminal; a management module, configured to manage the Internet of Things terminal based on the device information of the Internet of Things terminal, and the management includes at least one of access management and mobility management.

[0008] On the third aspect, an embodiment of the present application provides another method for managing an Internet of Things terminal, which is applied to an access network element or a non-access network element of a mobile network. The method includes: establishing a communication connection with the Internet of Things terminal, and establishing a communication connection with the core network of the mobile network; managing the Internet of Things terminal based on signaling interaction with the core network, and the management includes at least one of access management and mobility management.

[0009] In a fourth aspect, an embodiment of the present application provides another management device for an Internet of Things terminal, which is 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 Internet of Things terminal, and to establish a communication connection with the core network of the mobile network; an interaction module, configured to manage the Internet of Things terminal based on signaling interaction with the core network, and the management includes at least one of access management and mobility management.

[0010] In the fifth aspect, an embodiment of the present application provides a management device for an Internet of Things terminal, comprising: one or more processors; 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 Internet of Things terminal implements the management method for the Internet of Things terminal as described above.

[0011] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium having computer-readable instructions stored thereon. When the computer-readable instructions are executed by a processor of a computer, the computer executes the management method of the Internet of Things terminal as described above.

[0012] In a seventh aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the management method of the Internet of Things terminal as described above.

[0013] In the technical solution provided in the embodiments of the present application, the Internet of Things terminal can be a terminal in an environmental passive Internet of Things. The core network network element of the mobile network obtains the device information of the Internet of Things terminal, so that the core network can use the obtained device information to manage the Internet of Things terminal, thereby realizing support for environmental passive Internet of Things technology.

[0014] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG1 is a schematic diagram of the architecture of an exemplary management system for IoT terminals;

[0016] FIG2 is a flow chart of a method for managing an Internet of Things terminal according to an exemplary embodiment of the present application;

[0017] FIG3 is a flowchart of a method for managing an Internet of Things terminal according to another exemplary embodiment of the present application;

[0018] FIG4 is a flowchart of a method for managing an Internet of Things terminal shown in another exemplary embodiment of the present application;

[0019] FIG5 is a flowchart of a method for managing an Internet of Things terminal shown in another exemplary embodiment of the present application;

[0020] FIG6A shows a schematic diagram of the transition between different sub-states of an IoT terminal;

[0021] FIG6B is an overall schematic diagram of state transition formed based on the sub-state transition process shown in FIG6A ;

[0022] FIG7 is a flowchart of a method for managing an Internet of Things terminal according to another exemplary embodiment of the present application;

[0023] FIG8 is a block diagram of a management device for an Internet of Things terminal according to an exemplary embodiment of the present application;

[0024] FIG9 is a block diagram of a management device for an Internet of Things terminal shown in another exemplary embodiment of the present application;

[0025] FIG10 shows a schematic diagram of the structure of a computer system of a management device for an Internet of Things terminal suitable for implementing an embodiment of the present application. DETAILED DESCRIPTION

[0026] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. When the following description refers to the drawings, identical numerals in different figures represent identical or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present 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 separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0028] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0029] In this application, "plurality" refers to two or more. "And / or" describes the relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

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

[0031] As mentioned above, environmental passive IoT technology has the advantages of low power consumption, wireless energy self-powering, easy installation, and low maintenance costs. However, since the end-to-end network architecture and protocol design of current mobile communication technology are based on terminals that require battery power or wired connections, it does not support environmental passive IoT technology.

[0032] Compared to terminals that require battery power or wired connections, IoT terminals in passive IoT environments may encounter unique scenarios during use. For example, IoT terminals may experience intermittent power outages, such as when the battery is low or unavailable. Because the terminals rely on solar power, they can only operate during the day and lose power at night. Another example is that to conserve energy, IoT terminals may disable their transmitters (Transport, TX) or receivers (Receive, RX) by default, preventing the core network from obtaining real-time IoT terminal status for connectivity management.

[0033] In order to cope with these special conditions of IoT terminals in an environmentally passive IoT, the present application proposes a management system for IoT terminals.

[0034] Please refer to Figure 1, which shows an exemplary architecture diagram for an IoT terminal management system. IoT terminals connect to the core network via base stations or relay devices. Therefore, IoT terminal management is achieved through signaling exchanges between the base stations or relay devices and the core network. The core network can obtain the device information required for IoT terminal management directly from the IoT terminals or through other entities that possess the IoT terminal's device information.

[0035] It should be noted that the IoT terminal exemplified in FIG1 may include an IoT terminal in an environmental passive IoT, or may include an IoT terminal 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 solution for supporting the management of IoT terminals in a mobile network. The following describes the solution for managing IoT terminals provided by this application.

[0037] In an exemplary embodiment, the mobile network needs to obtain device information of the IoT terminal to provide access and mobility management for the IoT terminal according to the device information of the IoT terminal.

[0038] Exemplarily, the manner in which the mobile network obtains the device information of the IoT terminal includes a direct acquisition manner or an indirect acquisition manner. The direct acquisition manner means that the IoT terminal itself or other entities having the device information of the IoT terminal send the device information of the IoT terminal to the mobile network. Other entities are, for example, servers, assisting nodes and other devices. The indirect acquisition manner means that after the mobile network identifies the communication connection of the IoT terminal, it uses the identification information obtained by identifying the IoT terminal to obtain the device information of the IoT terminal from a specific entity. The specific entity may be the same as the other entities mentioned above, or may be a device different from other entities. For example, the specific entity may also be a specific core network element, and this application does not limit 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 use a pre-configured root key (rootkey) and a preset security authentication algorithm in the Subscriber Identity Module (SIM) card for authentication, or use a SIM-free method such as a digital certificate for authentication, which is not limited in this application.

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

[0041] The location information of the IoT terminal may include the specific location of the IoT terminal, and may also include type information corresponding to the location of the IoT terminal, such as an outdoor location or an indoor location. This application does not restrict the content of this location information. For example, the mobile network can set a management policy for the IoT terminal based on the location information of the IoT terminal. For example, the mobility of the IoT terminal in an indoor environment is relatively weak, so relevant management policies can be set based on this feature. It should be noted that this application does not restrict the management policy set by the mobile network through the location information of the IoT terminal.

[0042] The application scenario information of an IoT terminal is used to describe the application scenario in which the IoT terminal is located. For example, it can be an application scenario such as a factory, school, road, bridge, energy, or animal husbandry. This application does not impose any content restrictions on this application scenario. Similarly, the mobile network can also set management policies for the IoT terminal based on the application scenario information of the IoT terminal. For example, an IoT terminal installed on a bridge is usually stationary, so the mobility of the IoT terminal does not need to be managed. Similarly, this application still 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 IoT terminal may include one or more of information used to describe the energy characteristics of the IoT terminal and 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 the IoT terminal may include an active connection type or a passive connection type. For example, under the active connection type, the IoT terminal first establishes a connection with the mobile network, and then may deactivate the connection. Subsequently, if the capability is available, it may reconnect to the mobile network at a predetermined time and maintain the connection. Under the passive connection type, the IoT terminal will not actively connect to the mobile network, and will only establish a connection for data transmission after being triggered by the mobile network or other devices. Therefore, the mobile network can perform network connection management of the IoT terminal based on the communication connection type of the IoT terminal, but the specific management strategy is not limited in this application.

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

[0046] The energy storage characteristics may include no energy storage capability or a certain energy storage capability. For the latter, it may further include energy storage capability information, such as battery capacity.

[0047] Energy collection capability may include one or more of the IoT terminal's energy collection method and energy collection efficiency. For example, the IoT terminal's energy collection method may include one or more of solar energy, light energy, wind energy, electromagnetic energy, thermal energy, or other methods. For another example, energy collection efficiency may include absolute efficiency or relative efficiency. Absolute efficiency may refer to the amount of energy collected per unit time, while relative efficiency may refer to the percentage of the IoT terminal's energy storage capacity that is collected per unit time.

[0048] The energy consumption rate is used to describe the efficiency of energy consumed by the IoT terminal due to communication, calculation or other processing. For example, it may include one or more of the absolute value of energy consumed per unit time, the percentage of energy consumed per unit time as a percentage of the energy storage capacity of the IoT terminal, and the energy consumption rate of the IoT terminal due to communication consumption.

[0049] The mobile network can also perform network connection management for the IoT terminal based on the energy characteristics of the IoT terminal. For ease of understanding, for example, if the IoT terminal is powered by solar energy and does not have energy storage capabilities, the mobile network can control not to transmit data with the IoT terminal at night. For another example, based on the battery capacity, energy collection efficiency and energy consumption rate of the IoT terminal, the mobile network can predict that the IoT terminal will be unable to be powered at a certain point in the future, and therefore can perform corresponding data transmission control. It should be noted that this application does not limit the specific content of the mobile network's management of the IoT terminal based on the energy characteristics of the IoT terminal.

[0050] From the above, it can be seen that 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 recorded above, thereby supporting environmental passive IoT technology in the mobile communication network.

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

[0052] The embodiments of this application also propose other solutions for managing IoT terminals. For example, in one exemplary embodiment, the mobile network also provides access management for IoT terminals. Mobile network access management for IoT terminals can include two parts: wireless access management and core network access management.

[0053] Wireless side access management refers to establishing a direct connection between the IoT terminal and the network device responsible for the wireless access terminal in the mobile network. The network device responsible for the wireless access terminal in the mobile network can be an access network element, such as a base station, or a non-access network element, such as a relay device or other device. This application does not limit this.

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

[0055] In the mode where the IoT terminal initiates a connection, the IoT terminal can proactively initiate a communication connection request to the network device responsible for the wireless access terminal in the mobile network when it has its own energy and data communication needs. The communication connection request can carry information about the use of the target network resources, which can be shared network resources or dedicated network resources. The shared network resources can be used in a random access manner with contention, and the response window for random access can be extended, so as to reduce the probability of direct conflicts 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, specific random access codeword resources can be reserved for the passive IoT, so as to meet the dense deployment characteristics of IoT terminals.

[0056] In a mode where the network device responsible for wireless access terminals initiates a connection, the network device can wake up specific IoT terminals through broadcast, unicast, or multicast. Furthermore, for ease of management, different IoT terminals can be divided into different groups based on application scenarios or other criteria. For example, IoT terminals in the same application scenario can be grouped together, and the group can be used as the wake-up unit for IoT terminal wake-up. This way, when waking up different IoT terminals, it is possible to avoid affecting all IoT terminals. Different IoT terminals can also use a specific wake-up information sequence by group, and this sequence can be used as part of the identification information for identifying IoT terminals. This allows for the sequential awakening of multiple IoT terminals within the same group.

[0057] The access management on the core network side is responsible for cooperating with the wireless side to complete end-to-end access, including authentication during the connection process on the wireless side and the establishment of connections at each protocol layer. These protocol layers are, for example, protocols similar to the Access Stratum (AS) or the Non-Access Stratum (NAS), and can be divided into user plane protocols and control plane protocols. This application does not limit the content and naming of the relevant protocol layers. If the core network side 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 the IoT terminal. Exemplarily, the mobile network first needs to identify the mobility type of the IoT terminal in order to provide mobility management for the IoT terminal based on the mobility type of the IoT terminal. The mobility type of the IoT terminal can 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 movement speed corresponding to the first mobility type should be lower than the terminal movement speed corresponding to the second mobility type. This application does not limit the specific conditions for the classification of the two types.

[0059] The mobile network provides mobility management for the IoT terminal based on the mobility type of the IoT terminal, which can be understood as setting a corresponding network connection strategy for the IoT terminal based on the mobility type of the IoT terminal. For example, an IoT terminal with a stationary mobility type does not need to perform a location switching operation, and the paging mechanism in a non-idle state does not need to consider the change of location. For another example, an IoT terminal with a first mobility type has slow mobility, so there are protocol requirements in terms of paging and switching. An IoT terminal with a second mobility type will inevitably have protocol requirements in terms of paging and switching. This application also does not limit the specific content of the mobility management strategy 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 the passive IoT environment. For example, IoT terminals deployed indoors can reduce the frequency of measurements of adjacent cells. The mobile network mainly manages measurements and handover decisions for serving cells or neighbor cells that may be connected to save energy. For another example, the handover delay threshold can be relaxed so that the data in handover can be stored for a longer period of time, and the IoT terminal can be forwarded when the IoT terminal is reactivated, thereby adapting to the low-complexity and weak processing capability requirements of the passive IoT environment.

[0061] In some embodiments, for IoT terminals of the second mobility type, network connectivity optimization may not be necessary. For example, for IoT terminals deployed outdoors, the measurement frequency of adjacent cells may remain unchanged, or the handover delay threshold may remain unchanged.

[0062] It should also be noted that the way in which the mobile network identifies the mobility type of the IoT terminal can be active reception, for example, the IoT terminal or other entity reports its mobility type to the mobile network, or it can be identified based on the acquired device information of the IoT terminal, or it can be determined through big data statistical learning on the application service side or the configuration information of the operator. This application does not limit the method of identifying the terminal mobility type.

[0063] In another embodiment, the mobile network's management of the IoT terminal also includes management of the IoT terminal's status. Exemplarily, the IoT terminal's status may include at least one of the following sub-states, or may be a combination of at least one of the following sub-states:

[0064] The "Revoked" substate is used to describe when an IoT terminal is revoked by a mobile network. This revocation can be temporary or permanent. An IoT terminal in the "Permanently Revoked" substate does not need to be reactivated. An IoT terminal in the "Temporarily Revoked" substate can be reactivated based on specific conditions, which are not limited in this embodiment.

[0065] The shutdown and energy harvesting sub-state is used to describe the energy harvesting of the IoT terminal in the shutdown state. The IoT terminal can switch to this sub-state periodically or quasi-periodically. If energy storage capability is available, energy storage can be performed.

[0066] The power-off but not energy-harvesting sub-state is used to describe that the IoT terminal is not harvesting energy in the power-off state;

[0067] The activation and energy collection sub-state is used to describe the continuous energy collection of the IoT terminal in the activation state. During data transmission, the IoT terminal can perform periodic data transmission, turn off TX / RX accordingly, and collect energy. If energy storage capability is available, energy storage can be performed. If not, energy collection and energy use can be performed simultaneously.

[0068] The active but not energy harvesting sub-state is used to describe that the IoT terminal is not harvesting energy 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, energy harvesting is not performed.

[0069] In some embodiments, if the state of the Internet of Things terminal includes the abolished substate, the shutdown and energy collection substate, or the shutdown but not in the energy collection substate, the core network element does not perform access and mobility management on the Internet of Things terminal.

[0070] In some embodiments, if the state of the Internet of Things terminal includes an activated and energy collection sub-state or an activated but not energy collection sub-state, the core network element allows the Internet of Things terminal to perform periodic data transmission.

[0071] It is understood that the shutdown and energy collection sub-state and the shutdown but not performing energy collection sub-state as shown in the above example can also be combined to obtain a state, such as the shutdown state, or can be called another state. In this state, the IoT terminal can ignore the relevant information about the IoT terminal's energy collection. Similarly, the activation and continuous energy collection sub-state and the activation but not performing energy collection sub-state as shown in the above example can also be combined to obtain a state, such as the activation state, or can be called another state. In this state, the IoT terminal can perform periodic data transmission, can turn off TX / RX, and can decide whether to perform energy collection based on the energy storage situation.

[0072] It should also be understood that the sub-states and sub-state merging examples above are merely illustrative examples of the state management of IoT terminals proposed in this application and are not intended to be limiting. This application allows for other sub-states or sub-state merging methods in the mobile network's state management of IoT terminals. Furthermore, the sub-states in the examples above may be named in other ways, and this application does not impose any limitations thereon.

[0073] It should also be noted that the mobile network manages the IoT terminal based on the state or sub-state of the IoT terminal, and the management of the IoT terminal may include access and mobility management.

[0074] Based on the above content, it can be concluded that in the management solution for IoT terminals provided by this application, IoT terminals can be IoT terminals in an environmental passive IoT. Therefore, this application realizes the enhancement of the characteristics of mobile networks for environmental passive IoT, including the mobile network's identification of the type of IoT terminals, and based on the terminal type and capabilities, combined with the supported service layer data characteristics, the access and mobility management of the mobile network are enhanced to meet the connection accessibility of the environmental passive IoT. In addition, the management solution for IoT terminals provided by the application also realizes protocol support for new types of environmental passive IoT terminals, especially in the case of limited capabilities, to meet more business needs of environmental passive IoT with higher efficiency.

[0075] Based on the IoT terminal management solution provided above, the present application also provides a corresponding IoT terminal management method. Please refer to Figure 2, which is a flow chart of an IoT terminal management method according to an exemplary embodiment of the present application. This method is applied to a core network element of a mobile network. The core network element can be an Access and Mobility Management Function (AMF) element or other network element, and this application is not limited to this.

[0076] As shown in FIG2 , in an exemplary embodiment, the method for managing an IoT terminal includes steps S210 to S220 , which are described in detail as follows:

[0077] S210, obtaining device information of the IoT terminal.

[0078] The core network element of the mobile network obtains the device information of the IoT terminal and manages the IoT terminal according to the obtained device information.

[0079] The core network element can obtain the device information of the IoT terminal either directly or indirectly. In the direct acquisition method, the IoT terminal or other entity that has the device information of the IoT terminal will proactively send the device information of the IoT terminal to the core network element. Therefore, the core network element can receive the device information sent by the IoT terminal or other entity accordingly. In the indirect acquisition method, after identifying the communication connection of the IoT terminal, the core network element uses the identification information obtained by identifying the IoT terminal to obtain the device information of the IoT terminal from a specific entity. The specific entity and the other entity can be the same device or different devices, and this embodiment does not limit this.

[0080] In some embodiments, based on a 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 the security authentication is passed 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 another entity that possesses the IoT terminal's device information, and this embodiment does not limit this.

[0081] It should be noted that the exemplary content of the device information of the IoT terminal can also be found in the above records, which will not be elaborated in this embodiment.

[0082] S220: Manage the IoT terminal according to the device information of the IoT terminal, where the management includes at least one of access management and mobility management.

[0083] After the core network element obtains the device information of the IoT terminal, it can manage the IoT terminal based on the device information of the IoT terminal, for example, including access management and / or mobility management. It should be noted that the details of the device information of the IoT terminal have been introduced in the above description and will not be repeated in this embodiment.

[0084] For example, when the device information of the 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 thus provide corresponding management of the IoT terminal based on the relevant characteristics of the IoT terminal.

[0085] In the case where the device information of the IoT terminal includes the communication connection type of the IoT terminal, the core network element can provide management for the IoT terminal based on relevant characteristics of the IoT terminal under different communication connection types.

[0086] In the case where the device information of the IoT terminal includes the energy characteristics of the IoT terminal, the core network element can provide corresponding management for the IoT terminal according to the energy characteristics of the IoT terminal.

[0087] It should be noted that the exemplary core network element's management of the IoT terminal is described above and will not be elaborated in this embodiment. It can be seen that in the method provided in the embodiment, the core network element can obtain the relevant characteristics of the IoT terminal based on the acquired device information of the IoT terminal and provide a matching management solution to the IoT terminal based on these relevant characteristics. If the IoT terminal is an IoT terminal in an environmentally passive IoT, support for environmentally passive IoT technology can be achieved in the mobile communication network.

[0088] In another exemplary embodiment, as shown in FIG3 , the method for managing an IoT terminal further includes S310 - S320 , which are described in detail as follows:

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

[0090] As mentioned previously, IoT terminal access management consists of two parts: wireless access management and core network access management. Wireless access management directly establishes connections between IoT terminals and mobile network access network elements (such as base stations) or non-access network elements (such as relay devices). Core network access management is responsible for coordinating with the wireless side to complete end-to-end access, including authentication during the wireless connection process and establishing 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 IoT terminals.

[0091] S320: After the authentication information passes authentication, a control plane and a user plane protocol layer connection is established with the IoT terminal.

[0092] After the authentication information is authenticated, the core network element establishes a control plane and user plane protocol layer connection with the IoT terminal, such as the AS layer or NAS layer protocols described above. Therefore, the solution provided in this embodiment can further provide accessibility management for IoT terminals in an ambient passive IoT environment, thereby enhancing mobile communication network support for ambient passive IoT technologies.

[0093] In another exemplary embodiment, as shown in FIG4 , the method for managing an IoT terminal further includes S410 - S420 , which are described in detail as follows:

[0094] S410: Identify a mobility type of an IoT terminal, where the mobility type includes one or more of a stationary type, a first mobility type, or a second mobility type. A terminal movement speed corresponding to the first mobility type is lower than a terminal movement speed corresponding to the second mobility type.

[0095] The core network network element can identify the mobility type of the IoT terminal based on the device information of the IoT terminal obtained above, for example, it can be determined based on location information and / or application scenario information, or the IoT terminal or other entity can actively report the mobility type, or it can be determined based on big data statistical learning on the application service side or the configuration information of the operator. The specific method of the core network network element to identify the mobility type of the IoT terminal is not restricted here.

[0096] S420: Perform mobility management on the IoT terminal based on the mobility type of the IoT terminal.

[0097] Based on the identified mobility type of the IoT terminal, the core network element may perform mobility management on the IoT terminal, including: Stationary IoT terminals do not need to perform location switching operations, and the paging mechanism in the non-idle state does not need to consider location changes; IoT terminals of the first mobility type have slow mobility, so there are protocol requirements for paging and handover; IoT terminals of the second mobility type inevitably have protocol requirements for paging and handover. It should be understood that the mobility management of IoT terminals by the core network element described in this embodiment is only an example and does not limit the specific content of mobility management.

[0098] Therefore, the solution provided in this embodiment can further enhance the support of the mobile communication network for the environmental passive Internet of Things technology based on the identified terminal mobility type by identifying the mobility type of the Internet of Things terminal in the environmental passive Internet of Things.

[0099] In another exemplary embodiment, as shown in FIG5 , the method for managing an IoT terminal further includes S510 - S520 , which are described in detail as follows:

[0100] S510, identifying a state of an IoT terminal, where the state of the IoT terminal is used to describe information corresponding to an energy collection state of the IoT terminal.

[0101] The solution of this embodiment introduces state information related to the energy state of IoT terminals to perform mobility management for IoT terminals. The state of an IoT terminal is typically pre-agreed. For example, as described above, the state of an IoT terminal can include at least one of the following sub-states, or a combination of at least one of the following sub-states: a deactivated sub-state, a powered-off and energy-harvesting sub-state, a powered-off but not energy-harvesting sub-state, an activated and energy-harvesting sub-state, and an activated but not energy-harvesting sub-state.

[0102] It should be noted that the state content represented by each sub-state can also be found in the above description, and this embodiment does not elaborate on it. The sub-states as shown above are only exemplary and do not limit the sub-states of the IoT terminal. In actual application scenarios, the sub-states of the above examples can be merged to obtain the state of the IoT terminal, or the sub-states of the above examples can be directly used as the state of the IoT terminal, and this embodiment does not limit this.

[0103] S520: Perform access and mobility management on the IoT terminal based on the status of the IoT terminal.

[0104] During the access and mobility management of IoT terminals, IoT terminals will perform relevant transitions. As shown in Figures 6A and 6B, an exemplary state machine is used to describe the state transition of IoT terminals. The state machine requires relevant trigger conditions for transitions between different sub-states of the IoT terminal. For example, the <Power Off but Not Energy Harvesting Sub-state> is triggered by the condition of starting energy harvesting to transition to the <Power Off and Energy Harvesting Sub-state>, which is triggered by the condition of stopping energy harvesting to transition to the <Power Off but Not Energy Harvesting Sub-state>, the <Active but Not Energy Harvesting Sub-state> is triggered by the condition of starting energy harvesting to transition to the <Active and Energy Harvesting Sub-state>, the <Active and Energy Harvesting Sub-state> is triggered by the condition of stopping energy harvesting to transition to the <Active but Not Energy Harvesting Sub-state>, the <Power Off but Not Energy Harvesting Sub-state> is triggered by the condition of starting energy harvesting to transition to the <Active and Energy Harvesting Sub-state>, the <Active and Energy Harvesting Sub-state> is triggered by the condition of stopping energy harvesting to transition to the <Active but Not Energy Harvesting Sub-state>, the <Power Off but Not Energy Harvesting Sub-state> is triggered by the power-on condition to transition to the <Active and Energy Harvesting Sub-state>, and the <Active and Energy Harvesting Sub-state> is triggered by the power-off condition to transition to the <Power Off but Not Energy Harvesting Sub-state>. If the core network element sends a discontinue instruction to the IoT terminal, the IoT terminal transitions to the <discontinue substate> according to the received discontinue instruction.

[0105] It should be noted that the condition information used to trigger the mutual transition of each sub-state illustrated in FIG. 6A and FIG. 6B is also exemplary, and FIG. 6A and FIG. 6B do not limit this condition information.

[0106] For example, after the state transition of the IoT terminal occurs, for example, whether energy collection is performed in the shutdown state is completed by the IoT terminal itself, and the core network element can also make corresponding records of the state transition of the IoT terminal.

[0107] From the above, it can be seen that the solution provided by this embodiment can further enhance the support of the mobile communication network for the environmental passive Internet of Things technology by introducing a new state management mechanism.

[0108] Based on the IoT terminal management solution provided above, an embodiment of the present application further provides another IoT terminal management method as shown in Figure 7. This method is applied to an access network element or a non-access network element of a mobile network. The access network element may be a base station, and the non-access network element may be a relay device or other device, which is not limited in this application.

[0109] As shown in FIG7 , in an exemplary embodiment, the method for managing an IoT terminal includes steps S710 to S720 , which are described in detail as follows:

[0110] S710: Establish a communication connection with the IoT terminal and a communication connection with the core network of the mobile network.

[0111] For the access network element or non-access network element of the mobile network, it needs to establish a communication connection with the IoT terminal and also with the core network of the mobile network, thereby building an information transmission link between the IoT terminal and the core network.

[0112] Exemplarily, the way in which an access network element or a non-access network element establishes a communication connection with an Internet of Things terminal may include: the Internet of Things terminal initiates a communication connection request, and the access network element or the non-access network element responds to the communication connection request and establishes a communication connection with the access network element or the non-access network element accordingly.

[0113] The communication connection request initiated by the IoT terminal can carry its usage information for the target network resource. The target network resource can be a dedicated network resource, such as a wireless resource reserved by an access network element or a non-access network element for the IoT terminal to use without competition, or a shared network resource, thereby enabling the access network element or the 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 shared network resources are to be used, the access network element or the non-access network element can also reserve specific random access codeword resources for the IoT terminal, or increase the response window for random access of the IoT terminal to meet the dense deployment characteristics of the IoT terminal.

[0114] The way in which an access network element or a non-access network element establishes a communication connection with an IoT terminal may also include the access network element or the non-access network element sending a wake-up command to the IoT terminal covered by the network signal, thereby establishing a communication connection with the awakened IoT terminal.

[0115] Exemplarily, the access network element or the non-access network element can send the wake-up instruction by broadcasting, unicasting, or multicasting. In order to facilitate the management of different IoT terminals, the IoT terminals can also be divided into different groups according to application scenarios or other criteria. After obtaining the group information obtained by grouping multiple IoT terminals covered by the network signal, the wake-up instruction is sent based on the group information, with the group as the wake-up unit. In this way, when waking up different IoT terminals, it is possible to avoid affecting all IoT terminals. In addition, when grouping the IoT terminals, a wake-up order can be set for each IoT terminal in the same group to obtain a wake-up information sequence. The access network element or the non-access network element sends the wake-up instruction to the IoT terminals in the corresponding group in sequence based on the wake-up information sequence contained in the group information, thereby realizing the sequential wake-up of multiple IoT terminals.

[0116] S720: Manage the IoT terminal based on signaling interaction with the core network, where the management includes 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, the access network element or the non-access network element manages the IoT terminal based on the signaling interaction with the core network.

[0118] In the case where the device information of the IoT terminal is actively reported by the IoT terminal to the core network network element, the access network network element or the non-access network 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 network element, so that the core network network element performs corresponding management on the IoT terminal based on 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, the access network element or the non-access network element can participate in the transmission process of any information required to be transmitted on the information transmission link, and is not limited to the information in the above examples. Therefore, when the IoT terminal includes an IoT terminal in an environmental passive IoT, the method provided in this embodiment can achieve support for environmental passive IoT technology from the wireless side of the mobile network.

[0120] Please refer to FIG8 , which is a block diagram of a device for managing an Internet of Things terminal according to an exemplary embodiment of the present application. The device is applied to a core network element of a mobile network.

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

[0122] An acquisition module 810 is configured to acquire device information of an IoT terminal;

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

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

[0125] Identify the mobility type of the IoT terminal, where the mobility type includes one or more of a stationary type, a first mobility type, or a second mobility type, where a terminal movement speed corresponding to the first mobility type is lower than a terminal movement speed corresponding to the second mobility type;

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

[0127] In another exemplary embodiment, the first identification module is configured to: identify the mobility type of the Internet of Things terminal according to the device information of the Internet of Things terminal.

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

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

[0130] In another exemplary embodiment, the first identification module is configured to: if the mobility type of the Internet of Things terminal is the first mobility type, relax the delay threshold of the cell switching performed by the Internet of Things terminal.

[0131] In another exemplary embodiment, the first identification module is configured to: if the mobility type of the Internet of Things terminal is the second mobility type, keep the measurement frequency of the neighboring cells unchanged for the Internet of Things terminal.

[0132] In another exemplary embodiment, the first identification module is configured to: if the mobility type of the Internet of Things terminal is the second mobility type, keep the delay threshold value of the cell switching performed by the Internet of Things 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] Identifying the state of the IoT terminal, where the state of the IoT terminal is used to describe information corresponding to the energy collection state of the IoT terminal;

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

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

[0137] Send a cancellation instruction to the 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] Abolish substate;

[0140] Shutdown and energy harvesting substates;

[0141] Shutdown but not in energy harvesting substate;

[0142] Activation and energy harvesting substates;

[0143] Active but not in energy harvesting substate.

[0144] In another exemplary embodiment, the management device 800 for the Internet of Things terminal further includes a revocation module, which is used to send a revocation instruction to the Internet of Things terminal, and the revocation instruction is used to trigger the Internet of Things terminal to transition to the revocation sub-state.

[0145] In another exemplary embodiment, the first identification module is configured as follows: if the state of the Internet of Things terminal includes the abolition sub-state, the shutdown and energy collection sub-state, or the shutdown but not energy collection sub-state, then access and mobility management of the Internet of Things terminal is not performed.

[0146] In another exemplary embodiment, the first identification module is configured to allow the Internet of Things terminal to perform periodic data transmission if the state of the Internet of Things terminal includes the activation and energy collection substate or the activation but not energy collection substate.

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

[0148] Receiving authentication information sent by an access network element or a non-access network element of a mobile network during the process of establishing a communication connection with an IoT terminal;

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

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

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

[0152] In another exemplary embodiment, the management device 800 of the Internet of Things terminal also includes an authentication module, which is configured to perform security authentication interaction between the party obtaining the device information of the Internet of Things terminal and the core network element, and only after passing the security authentication, obtain the device information of the Internet of Things terminal 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 energy characteristics and communication connection types of the Internet of Things terminal.

[0155] In another exemplary embodiment, the energy characteristics of the IoT terminal include one or more of energy storage characteristics, energy collection capabilities, and energy consumption speed.

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

[0157] Please refer to Figure 9, which is a block diagram of a management device for an Internet of Things terminal shown in another exemplary embodiment of the present 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 FIG9 , the exemplary IoT terminal management device 900 includes:

[0159] An establishing module 910 is configured to establish a communication connection with an IoT terminal and a communication connection with a core network of a mobile network;

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

[0161] In another exemplary embodiment, the establishing module 910 is further configured to:

[0162] Receive a communication connection request sent by an IoT terminal, the communication connection request carrying usage information for a target network resource;

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

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

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

[0166] When the communication connection request contains usage information for 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.

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

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

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

[0170] As in the management device 900 of the Internet of Things terminal in the above example, the Internet of Things terminal can be an Internet of Things terminal in an environmental passive Internet of Things, so the mobile network's support for the environmental passive Internet of Things technology is realized based on the wireless side of the mobile network.

[0171] It should be noted that the IoT terminal management device provided in the above-described embodiments and the IoT terminal management method provided in the above-described embodiments are based on the same concept. The specific manner in which each module and unit performs operations has been described in detail in the method embodiments and will not be repeated here. In actual applications, the IoT terminal management device provided in the above-described embodiments can, as needed, allocate the aforementioned functions to different functional modules, i.e., divide the internal structure of the device into different functional modules to perform all or part of the functions described above. This is not a limitation herein.

[0172] An embodiment of the present application also provides a management device for an Internet of Things terminal, comprising: one or more processors; 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 Internet of Things terminal implements the management method for the Internet of Things terminal provided in the above-mentioned embodiments.

[0173] Figure 10 shows a schematic diagram of the structure of a computer system for a management device for an IoT terminal suitable for implementing an embodiment of the present application. It should be noted that the computer system 1000 for a management device for an IoT terminal shown in Figure 10 is merely an example and should not limit the functionality and scope of use of the embodiments of the present 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 according to the program stored in the read-only memory (ROM) 1002 or the program loaded from the storage part 1008 into the random access memory (RAM) 1003, such as executing the method described in the above embodiment. Various programs and data required for system operation are also stored in the RAM 1003. The CPU 1001, ROM 1002 and RAM 1003 are connected to each other 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 the I / O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 1008 including a hard disk; and a communication section 1009 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. Removable media 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 1010 as needed, so that computer programs read therefrom can be installed into the storage section 1008 as needed.

[0176] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1009, and / or installed from a removable medium 1011. When the computer program is executed by the central processing unit (CPU) 1001, the various functions defined in the system of the present application are executed.

[0177] It should be noted that the computer-readable medium shown in the embodiments of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. The computer program contained in the computer-readable medium may 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 possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0179] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. In some cases, the names of these units do not constitute limitations on the units themselves.

[0180] Another aspect of the present application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned method for managing an IoT terminal. The computer-readable storage medium may be included in the IoT terminal management device described in the above embodiments, or may exist independently and not be incorporated into the IoT terminal management device.

[0181] Another aspect of the present application provides a computer program product or computer program, which includes 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 method for managing an IoT terminal provided in each of the above embodiments.

[0182] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. Ordinary technicians in this field can easily make corresponding changes or modifications based on the main ideas and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.

[0183] It is understandable that in the specific implementation of this application, when the above embodiments of this application are applied to specific products or technologies, the user's permission or consent is required for the collection, use and processing of relevant data, which must comply with the relevant laws, regulations and standards of the relevant countries and regions.

Claims

1. A management method for an Internet of Things terminal, characterized in that, A core network element applied to a mobile network, the method comprising: Obtain device information of the Internet of Things (IoT) terminal; Manage the IoT terminal according to the device information of the IoT terminal, where the management includes at least one of access management and mobility management.

2. The method according to claim 1, wherein The method further comprises: Identify the mobility type of the IoT terminal, where the mobility type includes one or more of a stationary type, a first mobility type, or a second mobility type, and the terminal moving speed corresponding to the first mobility type is lower than the terminal moving speed corresponding to the second mobility type; Perform mobility management on the IoT terminal in combination with the mobility type of the IoT terminal.

3. The method according to claim 2, wherein The identifying the mobility type of the IoT terminal includes: Identify the mobility type of the IoT terminal according to the device information of the IoT terminal.

4. The method according to claim 2 or 3, characterized in that, The performing mobility management on the IoT terminal in combination with the mobility type of the IoT terminal includes: If the mobility type of the IoT terminal is the stationary type, do not perform a location switching operation on the IoT terminal.

5. The method according to claim 2 or 3, characterized in that, The performing mobility management on the IoT terminal in combination with the mobility type of the IoT terminal includes: If the mobility type of the IoT terminal is the first mobility type, reduce the measurement frequency of adjacent cells for the IoT terminal.

6. The method according to claim 2 or 3, characterized in that The performing mobility management on the IoT terminal in combination with the mobility type of the IoT terminal includes: If the mobility type of the IoT terminal is the first mobility type, relax the time delay threshold for cell switching performed by the IoT terminal.

7. The method according to claim 2 or 3, characterized in that, The performing mobility management on the IoT terminal in combination with the mobility type of the IoT terminal includes: If the mobility type of the IoT terminal is the second mobility type, keep the measurement frequency of adjacent cells unchanged for the IoT terminal.

8. The method according to claim 2 or 3, characterized in that, The performing mobility management on the IoT terminal in combination with the mobility type of the IoT terminal includes: If the mobility type of the IoT terminal is the second mobility type, keep the time delay threshold for cell switching performed by the IoT terminal unchanged.

9. The method according to claim 1, characterized in that, The method further comprises: Identify the state of the IoT terminal, where the state of the IoT terminal is used to describe information corresponding to the energy harvesting state of the IoT terminal; Perform access and mobility management on the IoT terminal in combination with the state of the IoT terminal.

10. The method according to claim 9, characterized in that, The state of the IoT terminal includes at least one of the following multiple sub-states, or is obtained by combining at least one of the following multiple sub-states: A deactivated sub-state, used to describe that the IoT terminal is deactivated by the mobile network; A shutdown and energy harvesting sub-state; A shutdown but not energy harvesting sub-state; An active and energy harvesting sub-state; An active but not energy harvesting sub-state.

11. The method according to claim 10, wherein The method further comprises: Send a deactivation instruction to the IoT terminal, where the deactivation instruction is used to trigger the IoT terminal to transition to the deactivated sub-state.

12. The method according to claim 10, wherein The performing access and mobility management on the IoT terminal in combination with the state of the IoT terminal includes: If the state of the Internet of Things (IoT) terminal includes the deactivated sub-state, the shutdown and energy harvesting sub-state, or the shutdown but not energy harvesting sub-state, no access and mobility management is performed on the IoT terminal.

13. The method according to claim 10, wherein Performing access and mobility management on the IoT terminal in combination with the state of the IoT terminal includes: If the state of the IoT terminal includes the active and energy harvesting sub-state or the active but not energy harvesting sub-state, 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: Receiving authentication information sent by an access network element or a non-access network element of a mobile network during the process of establishing a communication connection with the IoT terminal; After the authentication information passes the authentication, establishing protocol layer connections for the control plane and the user plane with the IoT terminal.

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

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

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

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

19. The method according to claim 17, wherein, The energy characteristics of the IoT terminal include one or more of energy storage characteristics, energy harvesting capabilities, and energy consumption speed.

20. A management method for an Internet of Things terminal, characterized in that, Applied to an access network element or a non-access network element 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; Based on signaling interaction with the core network, managing the IoT terminal, where the management includes at least one of access management and mobility management.

21. The method according to claim 20, wherein Establishing a communication connection with the IoT terminal includes: Receiving a communication connection request sent by the IoT terminal, where the communication connection request carries usage information for target network resources; In response to the communication connection request, establishing a communication connection with the IoT terminal on the communication frequency band corresponding to the target network resources.

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

23. The method according to claim 22, wherein In response to the communication connection request, establishing a communication connection with the IoT terminal on the communication frequency band corresponding to the target network resources includes: When the communication connection request includes usage information for the shared network resources, reserving specific random access codeword resources for the IoT terminal or increasing the response window for the IoT terminal's random access.

24. The method according to claim 20, wherein Establishing a communication connection with the IoT terminal includes: Sending a wake-up instruction to IoT terminals covered by the network signal; Establishing a communication connection with the woken-up IoT terminal.

25. The method according to claim 24, wherein Sending a wake-up instruction to IoT terminals covered by the network signal includes: Obtain the group information obtained by dividing multiple Internet of Things (IoT) terminals with network signal coverage into groups; Send wake-up instructions with the group as the wake-up unit according to the group information corresponding to the IoT terminal.

26. The method according to claim 24, wherein The step of sending the wake-up instructions with the group as the wake-up unit according to the group information corresponding to the IoT terminal includes: Based on the wake-up information sequence contained in the group information, send wake-up instructions to the IoT terminals in the corresponding group in sequence.

27. A management device for an Internet of Things terminal, characterized in that, Applied to a core network element of a mobile network, the device includes: An acquisition module configured to acquire the device information of the IoT terminal; A management module configured to manage the IoT terminal according to the device information of the IoT terminal, where the management includes at least one of access management and mobility management.

28. A management device for an Internet of Things terminal, characterized in that, Applied to an access network element or a non-access network element of a mobile network, the device includes: A establishment module configured to establish a communication connection with the IoT terminal and establish a communication connection with the core network of the mobile network; An interaction module configured to manage the IoT terminal based on signaling interaction with the core network, where the management includes at least one of access management and mobility management.

29. A management device for an Internet of Things terminal, characterized in that, Comprising: One or more processors; A memory for storing one or more programs, when the one or more programs are executed by the one or more processors, enabling the management device of the IoT terminal to implement the method for managing the IoT terminal according to any one of claims 1-19 or 20-26.

30. A computer-readable storage medium, characterized in that, Stored thereon are computer-readable instructions, when the computer-readable instructions are executed by a processor of a computer, causing the computer to execute the method for managing the IoT terminal according to any one of claims 1-19 or 20-26.

31. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by a processor, the method according to any one of claims 1-19 or 20-26 is implemented.

Images