Communication method and device, equipment and computer storage medium

Abstract

The invention relates to a communication method, device and equipment and a computer storage medium, and the communication method of an Internet of Things card comprises the steps: receiving an over-the-air card writing instruction from an Internet of Things card connection management platform; in response to the over-the-air card writing instruction, judging whether a network type management file exists in a main security domain of the Internet of Things card, and if the network type management file does not exist, newly adding a blank network type management file; and writing network type management strategy information into the network type management file, wherein a network condition for prohibiting use or allowing use is stipulated in the network type management strategy information. According to the embodiment of the invention, the Internet of Things card is strengthened, and the cost of the Internet of Things terminal can be prevented from being increased while the network connection between the Internet of Things terminal and the base station is prevented from being abnormal.

Description

Technical Field

[0001] This application relates to the field of IoT SIM card communication, and in particular to communication methods, apparatus, devices, and computer storage media for IoT SIM cards, IoT terminals, IoT SIM card connection management platforms. Background Technology

[0002] With the gradual decommissioning of 2G equipment and the migration of 2G users (on a scale of hundreds of millions), and the large-scale deployment of 5G, IoT operators (such as the main body of IoT connection management platforms) have received numerous complaints about abnormal Internet access of IoT terminals since the beginning of 2023.

[0003] For example, when the IoT terminal module supports 2G / NB / 4G networks, after the IoT terminal restarts, it displays a normal 2G signal but cannot access the internet. After restarting, it randomly connects to either 2G or 4G; when connected to 4G, internet access is normal, but when connected to 2G, there is a signal but internet access is abnormal. However, the IoT terminal does not support the configured network standard, or the customer cannot switch the IoT terminal's network standard to the specified network standard. Therefore, the customer requests service personnel to replace the IoT SIM card on-site. As another example, when the IoT terminal module supports 2G / NB / 4G / 5G networks, when the IoT terminal passes a 5G base station, it displays a very strong 5G signal, but the IoT terminal cannot access the internet normally. The customer requests a replacement IoT SIM card or on-site assistance. These kinds of abnormal complaints require IoT operators to spend a significant amount of time and manpower to assist customers with testing and SIM card replacement, placing immense pressure on IoT operators and posing a serious challenge to their customer support work. Summary of the Invention

[0004] This application provides a communication method, apparatus, device, and computer storage medium for strengthening IoT cards, thereby preventing network connection anomalies between IoT terminals and base stations while avoiding increased costs for IoT terminals.

[0005] The first aspect of this application provides a communication method for an IoT card, the communication method comprising: receiving an over-the-air write command from an IoT card connection management platform; responding to the over-the-air write command, determining whether a network standard management file exists in the main security domain of the IoT card, and if the network standard management file does not exist, adding a blank network standard management file; and writing network standard management policy information into the network standard management file, wherein the network standard management policy information specifies network conditions that are prohibited or permitted.

[0006] In some embodiments, the method further includes: restricting network connections between the IoT SIM card terminal and the base station based on network standard management policy information, wherein the network conditions include at least one of the base station ID, network standard, and the MME, AMF, MSC, and SGSN codes of the core network element.

[0007] In some embodiments, the network standard management policy information specifies a restricted base station ID list, which is a list of prohibited base station IDs. Restricting the network connection between the IoT SIM card terminal and the base station according to the network standard management policy information includes: taking the operation of the IoT terminal reading the IMSI as a trigger event, obtaining the currently pre-connected base station ID from the IoT terminal; and comparing the pre-connected base station ID with the restricted base station ID list in the network standard management policy information set in the IoT SIM card. If the pre-connected base station ID is in the restricted base station ID list, the IoT terminal is advised to select another base station. If the pre-connected base station ID is not in the restricted base station ID list, the IMSI is directly returned to the IoT terminal.

[0008] In some embodiments, when network conditions include network standards, restricting network connections between an IoT SIM card terminal and a base station based on network standard management policy information includes: capturing a successful network authentication comparison event between the IoT terminal and the base station; using the successful network authentication comparison event as a trigger condition, sending the network standard management policy information set in the IoT SIM card to the IoT terminal, so that the IoT terminal combines the network standard management policy information and the network standards it supports to determine the network standards ultimately supported by the IoT terminal, and sending the ultimately supported network standards to the base station.

[0009] The second aspect of this application provides a communication method for an IoT SIM card, the method comprising: capturing a successful network authentication comparison event between an IoT terminal and a base station; using the successful network authentication comparison event as a trigger condition, sending network standard management policy information set in the IoT SIM card to the IoT terminal, wherein the network standard management policy information specifies network standards that are prohibited or permitted, so that the IoT terminal, in combination with the network standard management policy information and the network standards it supports, determines the network standards that the IoT terminal ultimately supports, and sends the ultimately supported network standards to the base station.

[0010] A third aspect of this application provides a communication method executed by an Internet of Things (IoT) terminal. The communication method includes: receiving network standard management policy information sent by an IoT SIM card in response to a successful network authentication comparison event between the IoT terminal and a base station; the network standard management policy information is set within the IoT SIM card and specifies prohibited or permitted network standards; determining the network standards ultimately supported by the IoT terminal by combining the network standard management policy information and the network standards it supports; sending the ultimately supported network standards to the base station; and negotiating network standard information with the base station based on the ultimately supported network standards to establish a network connection based on the network standard management policy information.

[0011] The fourth aspect of this application provides a communication method for an IoT SIM card connection management platform. This communication method includes: receiving network anomaly information from a user; configuring network standard management policy information for the IoT SIM card experiencing the network anomaly; sending the network standard management policy information to the IoT SIM card via an over-the-air (OTA) write function, specifying network conditions that are prohibited or permitted in the network standard management policy information; and, after receiving a report indicating that the network standard management policy information has been successfully written to the IoT SIM card, enabling the IoT terminal to reconnect to the network.

[0012] The fifth aspect of this application provides a communication method for a communication system. The communication system includes: an IoT SIM card, an IoT SIM card connection management platform, and an IoT terminal. The communication method includes: the IoT SIM card connection management platform receiving network anomaly information from a user; configuring network standard management policy information for the IoT SIM card experiencing network anomalies; and sending the network standard management policy information to the IoT SIM card via an over-the-air (OTA) write function. The network standard management policy information specifies network conditions that are prohibited or permitted. The IoT SIM card receives an OTA write command from the IoT SIM card connection management platform. In response to the OTA write command, it determines whether a network standard management file exists in the IoT SIM card's main security domain. If no network standard management file exists, a blank network standard management file is created, and the network standard management policy information is written into the network standard management file. After receiving a report that the network standard management policy information has been successfully written to the IoT SIM card, the IoT SIM card connection management platform enables the IoT terminal to reconnect to the network. When the network conditions include a base station ID, the IoT SIM card uses the IoT terminal... The operation of reading the IMSI is a trigger event. The system obtains the currently pre-connected base station ID from the IoT terminal and compares it with the restricted base station ID list in the network standard management policy information set in the IoT SIM card. If the pre-connected base station ID is in the restricted base station ID list, the IoT terminal is advised to select another base station. If the pre-connected base station ID is not in the restricted base station ID list, the system responds normally to the IMSI. When network conditions include network standard, the IoT SIM card captures a successful network authentication comparison event between the IoT terminal and the base station. Using this successful network authentication comparison event as a trigger condition, the system sends the network standard management policy information set in the IoT SIM card to the IoT terminal. The IoT terminal combines the network standard management policy information with its own supported network standards to determine the final supported network standards and sends this final supported network standards to the base station. The IoT terminal and the base station negotiate network standard information based on the final supported network standards to establish a network connection based on the network standard management policy information.

[0013] In some embodiments, the structure of network standard management policy information includes: a restriction type flag, a service type flag, and restriction content. The restriction type flag indicates whether it is a blacklist or a whitelist; the service type flag indicates the type of network condition being restricted; and the restriction content indicates the specific restriction content for each network condition.

[0014] The sixth aspect of this application provides a communication device for an IoT card, comprising: a receiving module for receiving an over-the-air write command from an IoT card connection management platform; a file addition module for, in response to the over-the-air write command, determining whether a network standard management file exists in the main security domain of the IoT card, and if no network standard management file exists, adding a blank network standard management file; and a writing module for writing network standard management policy information into the network standard management file, wherein the network standard management policy information specifies network conditions that are prohibited or permitted.

[0015] In some embodiments, the device further includes: an acquisition module, which acquires the currently pre-connected base station ID from the IoT terminal based on the IoT terminal's operation of reading the IMSI as a trigger event; a comparison module, which compares the pre-connected base station ID with the list of restricted base station IDs in the network standard management policy information set in the IoT card; and a response module, which suggests that the IoT terminal reselect another base station if the pre-connected base station ID is in the list of restricted base station IDs, and responds normally to the IMSI if the pre-connected base station ID is not in the list of restricted base station IDs.

[0016] The seventh aspect of this application provides a communication device for an IoT SIM card, comprising: a capture module for capturing a successful network authentication comparison event between an IoT terminal and a base station; and a transmission module for sending network standard management policy information set in the IoT SIM card to the IoT terminal, triggered by the successful network authentication comparison event. The network standard management policy information specifies network standards that are prohibited or permitted, so that the IoT terminal combines the network standard management policy information and the network standards it supports to determine the network standards that the IoT terminal ultimately supports, and sends the ultimately supported network standards to the base station.

[0017] The eighth aspect of this application provides a communication device for an Internet of Things (IoT) terminal, comprising: a receiving module for receiving network standard management policy information sent by an IoT SIM card in response to a successful network authentication comparison event between the IoT terminal and a base station, wherein the network standard management policy information is set in the IoT SIM card and specifies network standards that are prohibited or permitted; a determining module for determining the network standards ultimately supported by the IoT terminal by combining the network standard management policy information and the network standards it supports; a sending module for sending the ultimately supported network standards to the base station; and a negotiation module for negotiating network standard information with the base station based on the ultimately supported network standards to establish a network connection based on the network standard management policy information.

[0018] The ninth aspect of this application provides a communication device for an IoT SIM card connection management platform, comprising: a receiving module for receiving network abnormality information from a user; a configuration module for configuring network standard management policy information for the IoT SIM card experiencing network abnormality; a distribution module for distributing the network standard management policy information to the IoT SIM card via an over-the-air (OTA) write function; and a reconnection module for enabling the IoT terminal to reconnect to the network after receiving a report that the network standard management policy information has been successfully written to the IoT SIM card.

[0019] The tenth aspect of this application provides a communication system for an IoT card, comprising: an IoT card, including a communication device for an IoT card according to the sixth or seventh aspect; an IoT terminal, including a communication device for an IoT terminal according to the eighth aspect; and an IoT card connection management platform, including a communication device for an IoT card connection management platform according to the ninth aspect, wherein the IoT card writes network standard management policy information issued by the IoT card connection management platform through an over-the-air card writing function into a network standard management file within the main security domain.

[0020] The eleventh aspect of this application provides a communication device, including: a processor and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the communication method of any one of the first to fifth aspects.

[0021] The twelfth aspect of this application provides a computer-readable storage medium, characterized in that the computer storage medium stores computer program instructions, which, when executed by a processor, implement the communication method of any one of the first to fifth aspects.

[0022] The thirteenth aspect of this application provides a computer program product, characterized in that it includes a computer program, which, when processed for execution, implements a communication method of any one of the first to fifth aspects.

[0023] According to the communication method, apparatus, device, and computer storage medium of this application, by utilizing the over-the-air card writing function of the connection management platform, network standard management policy information specifying prohibited or permitted network conditions is written into the network standard management file within the main security domain of the IoT card. This can strengthen the IoT card, that is, manage the network standard management policy from the perspective of the IoT card, thereby avoiding the need to improve the performance of existing IoT terminals. It can also avoid network connection anomalies between IoT terminals and base stations while avoiding increased costs for IoT terminals. Attached Figure Description

[0024] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 This is a schematic diagram illustrating an example of a communication system according to the first embodiment; Figure 2 This shows an example of a COS file system; Figure 3 This is a flowchart illustrating the communication method of the IoT card according to the second embodiment; Figure 4 This is a schematic diagram showing the structure of a communication device for an IoT card corresponding to the second embodiment; Figure 5 This is a schematic diagram illustrating an example of a data structure for network standard management strategy information; Figure 6 This is a flowchart illustrating the process of an IoT terminal accessing the Internet through authentication via an IoT SIM card in the prior art. Figure 7 This is a schematic flowchart of Embodiment 1 of the network access process for the IoT terminal of this application; Figure 8 This is a flowchart illustrating Embodiment 1 of the communication method of the IoT card according to the third embodiment of this application; Figure 9 This is a schematic diagram showing the structure of the communication device of the IoT card corresponding to Embodiment 1; Figure 10 This is a schematic flowchart of Embodiment 2 of the network access process for the IoT terminal of this application; Figure 11 This is a flowchart illustrating Embodiment 2 of the communication method of the IoT card according to the third embodiment of this application; Figure 12 This is a schematic diagram showing the structure of the communication device of the IoT card corresponding to Embodiment 2; Figure 13 This is a flowchart illustrating an example of a communication method for an IoT terminal according to the fourth embodiment; Figure 14 This is a schematic diagram of the communication device of the Internet of Things terminal corresponding to the fourth embodiment; Figure 15 This is a flowchart illustrating the communication method of the IoT card connection management platform according to the fifth embodiment; Figure 16 This is a schematic diagram showing the structure of a communication device for an IoT card connection management platform corresponding to the fifth embodiment; Figure 17(a) is a schematic diagram of an example of network policy configuration operation on the IoT SIM card connection management platform; Figure 17(b) is a schematic diagram of an example of viewing network policies on the IoT SIM card connection management platform. Figure 18 This is a flowchart illustrating the process by which an IoT terminal reconnects to the network based on instructions from an IoT SIM card connection management platform. Figure 19 This is a schematic diagram illustrating the hardware structure of the communication device provided in the sixth embodiment of this application. Detailed Implementation

[0026] Before describing the technical solution of this application, we will first introduce the technical solution of the prior art.

[0027] Through investigation and analysis of numerous cases, the inventors of this application discovered that due to the fragmented, non-standardized, and controllable nature of the Internet of Things (IoT) industry, IoT terminals' network signal detection and intelligent switching capabilities are not as robust as those of smartphone terminals. This results in IoT terminals being unable to effectively coordinate with modules to switch from an abnormal network to a better network standard when network switching or attachment anomalies occur. Consequently, the terminals exhibit obvious internet connectivity issues, which cannot be reliably resolved manually. Analysis shows that currently, over 95% of IoT terminals do not support manual network standard setting or automatic search and switching to a better network, leading to frequent internet connectivity failures due to attachment to abnormal network standards, resulting in a large influx of complaints to IoT operators.

[0028] According to the inventors' research findings, the current industry mainly addresses the problem of IoT terminals being unable to flexibly switch network standards to better networks when experiencing abnormal internet access by using the following methods: enhancing the capabilities of the IoT terminal module by adding third-party enhancement and auxiliary function modules; or, using a dual-SIM, dual-module approach for the IoT terminal to monitor and switch network quality; or, modifying the IoT terminal to enable it to support autonomous network switching capabilities.

[0029] However, if the functionality of IoT terminal modules is improved to enable autonomous switching between multiple modules and multiple standards, it places higher demands on the capabilities of IoT terminal modules, MCUs, control modules, etc., which will lead to an increase in the manufacturing cost of IoT terminals. Moreover, IoT terminals themselves are characterized by diversity and low cost, so the applicability of this solution is relatively small.

[0030] Moreover, in this field, the main function of ordinary IoT cards and SIM cards is to serve as network access identity credentials provided by operators. In a narrow sense, they can be understood as physical credentials that can interact with the core network. The main function of SIM cards is to store user authentication information and necessary keys, which are used to verify the user's identity during the network authentication process. They do not directly participate in the process of IoT terminals selecting the network standard to access.

[0031] This application proposes a communication method, apparatus, device, and computer storage medium for strengthening IoT cards, standardizing network management from the perspective of IoT cards, and avoiding increased costs for IoT terminals.

[0032] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0033] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0034] First Implementation Method The first embodiment of this application provides a communication system for an IoT card. Figure 1 This is a schematic diagram illustrating an example of a communication system according to the first embodiment.

[0035] like Figure 1 As shown, the communication system involved in the first embodiment includes an IoT card 10, an IoT terminal 20, and an IoT card connection management platform 30.

[0036] The IoT SIM card 10 is a smart card specifically designed for mobile communication access services for the Internet of Things (IoT), also known as an IoT SIM card. The IoT SIM card 10 is inserted into the IoT terminal 20 to communicate with it. Furthermore, it can also communicate with the IoT SIM card connection management platform 30 via the over-the-air (OTA) card writing function.

[0037] The IoT terminal 20 is a key device in the IoT system that connects the sensor network and the transmission network. The IoT terminal 20 can communicate not only with the IoT SIM card 10, but also with the base station 40 via the network. After selecting the base station 40 to connect to, the IoT terminal 20 negotiates the network standard with the base station 40 and establishes a network connection using the negotiated network standard.

[0038] The IoT SIM card connection management platform 30 is a cloud-based system that provides centralized management and connection services for IoT SIM cards. The IoT SIM card connection management platform 30 can configure network standard management policy information and send this information to the IoT SIM card 10 via over-the-air (OTA) writing function. For example, upon receiving a complaint or feedback from user 50 regarding abnormal internet access, the platform can configure network standard management policy information and send it to the IoT SIM card 10.

[0039] The communication methods and devices for the IoT SIM card 10, IoT terminal 20, and IoT SIM card connection management platform 30 will be described in detail in the following embodiments.

[0040] Second Implementation Method The second embodiment of this application provides a communication method for an IoT card, namely a communication method performed by the IoT card 10.

[0041] Before describing the second implementation method, we will first introduce the operating system and file system of the IoT card 10.

[0042] The IoT SIM card 10 is equipped with a smart card operating system (COS). The COS is primarily used to receive and process various information sent to the SIM card from external sources (such as the IoT terminal 20), execute various commands sent from the external source (such as authentication operations), manage the memory space within the card, and send response information back to the external source. Generally, the COS system model of the IoT SIM card 10 includes: a communication management module, a security management module, an application processing module, and a file management module. External information (commands or data) enters the COS through the communication management module. The security management module authenticates and checks its legitimacy. The application processing module then interprets the meaning (execution, storage) of the external information. Finally, the file management module operates on the files in the EEPROM based on the interpretation results from the application processing module. If the COS needs to respond to external information, the file management module reads the file data from the EEPROM and transmits it to the application processing module, or the application processing module directly extracts the execution results according to the commands in the external information. After authentication and verification by the security management module, this information or data is fed back to the external source through the communication management module, thus completing a full processing cycle. Traditional Card Operating System (COS) and card applications are developed and loaded into the chip in a secure environment. In recent years, open operating system platforms such as JavaCard™, MultOS, and Windows for Smart Card have made significant progress. This has greatly facilitated the application development of smart IC cards and the realization of one card for multiple uses, and allows for the dynamic loading, updating, or deletion of card applications.

[0043] All data on the IoT 10 is stored in the card data storage area as files, forming the COS file system. Figure 2 This shows an example of a COS file system.

[0044] exist Figure 2 In this context, MF represents the root directory, DF represents a directory, and EF represents a file. On the IoT 10, each directory or file has its own ID, called the FID.

[0045] Based on the above background, a communication method for the IoT card 10 according to the second embodiment of this application is proposed.

[0046] Figure 3 This is a flowchart illustrating the communication method of the IoT card 10 according to the second embodiment. Figure 3 As shown, the communication method includes steps S110 to S130.

[0047] Figure 4This is a schematic diagram showing the structure of the communication device of the IoT card 10 corresponding to the second embodiment. In other words, the communication method of the IoT card 10 in the second embodiment can also be implemented as a communication device of the IoT card 10. Figure 4 As shown, the communication device includes: a receiving module 110, a file addition module 120, and a writing module 130.

[0048] In step S110, the receiving module 110 of the IoT card 10 receives the over-the-air card writing command from the IoT card connection management platform 30.

[0049] Over-the-air card writing commands can be implemented via data connection and SMS, etc. This application does not impose any particular restrictions on this, and any existing method can be used.

[0050] In step S120, the file addition module 120 of the IoT card 10 responds to the over-the-air write command and determines whether a network standard management file already exists in the main security domain of the MF directory in the IoT card's COS file system. Since setting a network standard management file in the main security domain is one of the unique inventive features of this application, the IoT card 10, upon first receiving the over-the-air write command from the IoT card connection management platform 30, does not contain this network standard management file. Therefore, it is determined that the network standard management file does not exist, and a blank network standard management file is added to the main security domain.

[0051] That is, when it is determined that there is no network standard management file in the main security domain, after adding a network standard management file in the main security domain, proceed to step S130.

[0052] When the IoT card connection management platform 30 receives an over-the-air card writing command again, since the network standard management file already exists, there is no need to add one. The network standard management policy information can be written into the existing network standard management file. In other words, the original network standard management policy information can be modified.

[0053] That is, when it is determined that a network standard management file exists in the main security domain, proceed directly to step S130.

[0054] As an example, in the main security domain of the MF directory in the COS file system of IoT SIM 10, a blank network standard management file (EF file) is added, and a fixed FID is set for the EF file. This EF file represents the network standard management file. For example, the network standard management file is named 0xAA00A1, where 0x represents hexadecimal and AA00A1 is the file name (FID) of IoT SIM 10.

[0055] In step S130, the writing module 130 of the IoT card 10 writes network standard management policy information into the network standard management file. Here, the network standard management policy information specifies network conditions that are prohibited or permitted. For example, these network conditions include at least one of the following: base station ID, network standard, and the MME, AMF, MSC, and SGSN codes of the core network element.

[0056] In this embodiment, by responding to the over-the-air write command of the IoT SIM card connection management platform, the main security domain file system structure of the IoT SIM card is improved, and network standard management policy information specifying network conditions that prohibit or allow use is written. This enhances the functionality of the IoT SIM card and standardizes network standard management from the perspective of the IoT SIM card, thus avoiding the need to change the structure of the IoT terminal and preventing an increase in the cost of the IoT terminal.

[0057] The following describes an example of the structure of the network standard management file and the network standard management policy information written into the network standard management file.

[0058] The digital structure of network standard management documents and network standard management policy information includes: restriction type tags, service type tags, and restriction content.

[0059] The restriction type flag indicates whether the restriction type is a whitelist or a blacklist; in other words, whether it's prohibited or permitted. When both a blacklist and a whitelist exist, the blacklist can be set to have higher priority.

[0060] The service type flag indicates which of the following network conditions is restricted: network standard, base station, core network element MME, AMF, MSC, SGSN encoding, etc.

[0061] The restriction content indicates the specific restrictions for each network condition. For example, when the service type tag indicates that the restricted network condition is a network standard, the restriction content can be a list of network standards; when the service type tag indicates that the restricted network condition is a base station, the restriction content can be a list of base station IDs.

[0062] When the service type label indicates the network standard, for example, the restriction content is to prohibit access to 2G-GSM network, 2G-CDMA network, etc.

[0063] Figure 5 This is a schematic diagram illustrating an example data structure for network standard management strategy information. Figure 5 In the example shown, 0x010002010A… is written as network standard management policy information.

[0064] The 0x does not exist in the actual encoding; it is only used to indicate that the content is in hexadecimal and its value ranges from 0 to F.

[0065] The following is for reference. Figure 5 Taking 0x010002010A… as an example, the meaning of different positions in the network standard management strategy information is explained.

[0066] exist Figure 5 In this context, the leftmost 0 indicates that the restriction type is a blacklist. That is, this bit represents the restriction type, consists of one hexadecimal bit, occupies half a byte, and is used to identify whether it is a blacklist or a whitelist. Specifically, when the restriction type is a blacklist, the value is 0, and when the restriction type is a whitelist, the value is 1.

[0067] exist Figure 5 In this context, the second digit from the left, 1, indicates that the service type is the network standard. That is, this digit represents the service type and consists of one hexadecimal digit, occupying half a byte. For example, 1 represents the network standard, and 2 represents the base station ID.

[0068] exist Figure 5 In this context, the third bit from the left, 0002, indicates that the data content is 2 bytes long. In other words, this bit represents the length of the data content, i.e., the number of bytes.

[0069] exist Figure 5 In this encoding, the fourth bit from the left, 01, indicates 2G (GSM standard), which is encoding content 1 representing the network standard. The fifth bit from the left, 0A, indicates 4G-TD-LTE standard, which is encoding content 2 representing the network standard. That is, each of these encoding contents representing the network standard occupies 2 hexadecimal bits, or 1 byte. This encoding content is determined by the operator; for example, 01 represents 2G-GSM, 0A represents 4G-TD-LTE, 0B represents 4G-FDD-LTE, etc.

[0070] Therefore, it can be concluded that in Figure 5 In the example, the 2G-GSM and 4G-TD-LTE network standards have been banned.

[0071] In this example, by defining a specific data structure for the network standard management file and the network standard management policy information written therein, including restriction type tags, service type tags, and restriction content, it is possible to reasonably restrict various network conditions using the network standard management policy information, which can be applied to situations where connection anomalies occur due to various network conditions.

[0072] In some embodiments, network connectivity between IoT SIM card terminals and base stations can be restricted based on network standard management policy information.

[0073] Here, "restricting network connections between IoT SIM card terminals and base stations" means that when initially establishing a network connection between an IoT SIM card terminal and a base station, or when resetting the network connection, the network connection must be established under network conditions prohibited by the network standard management policy information. For example, in Figure 5 In the example shown, IoT SIM 10 enables the use of two network standards in the network connection between IoT terminal 20 and base station 40.

[0074] According to this embodiment, the network connection between the IoT SIM card terminal and the base station can be changed in accordance with the network standard management policy information. This allows the network standard management policy information in the IoT SIM card to be used to avoid network anomalies without changing the structure of the IoT terminal, thereby avoiding increasing the cost of the IoT terminal.

[0075] Third Implementation Method The third embodiment of this application provides a communication method for an IoT card, namely, a communication method executed by the IoT card 10. The third embodiment is characterized by, based on the second embodiment, or assuming that network standard management policy information is already set within the IoT card, restricting network connections corresponding to the restriction conditions according to the network standard management policy information. For example, if the network standard management policy information specifies a blacklist of base station IDs, and the base station ID to be connected to belongs to that blacklist, then the base station is changed; or, if the network standard management policy information specifies a blacklist of network standards, and the network standard belongs to that blacklist, then the network standard is changed, and so on.

[0076] Before describing the third embodiment, the process of Internet of Things (IoT) terminals accessing the Internet via IoT SIM card authentication in the prior art will be explained below. Figure 6 This is a flowchart illustrating the process of an IoT terminal accessing the Internet through authentication via an IoT SIM card in the prior art.

[0077] like Figure 6As shown, the existing IoT terminal network access process is as follows: In the case of a base station broadcast network, in step S601, the IoT terminal powers on; then, in step S602, the IoT terminal searches for nearby base station signals and selects a base station; in step S603, the terminal reads the IMSI from the IoT SIM card; in step S604, the IoT terminal sends the IMSI to the base station; in step S605, the base station generates a set of random numbers based on the IMSI and sends the random numbers to the IoT terminal; in step S606, the IoT terminal sends the random numbers to the IoT SIM card, and the IoT SIM card calculates the random numbers based on the Ki value. The system outputs the result (SRES) and transmits it to the IoT terminal. In step S607, the IoT terminal transmits the SRES to the base station. In step S608, the base station (network system) finds the Ki corresponding to this IMSI from the database and calculates SRES1 using the same random number and the same algorithm. The system then compares SRES and SRES1. In step S609, if SRES = SRES1, the authentication is successful, and the IoT terminal's identity is considered valid. In step S610, the IoT terminal and the base station negotiate the network standard. In step S611, the IoT terminal connects to the base station using the negotiated network standard.

[0078] In the third embodiment of this application, as an example of restricting network connections corresponding to restriction conditions based on the network standard management policy information, when the restriction conditions include base station IDs that are prohibited or allowed to be used, such as... Figure 7 As shown, it is possible to Figure 6 Add step S70 between steps S603 and S604.

[0079] In step S70, the IoT card can detect network standard management policy information and verify the base station ID. If connection to the base station is allowed, proceed to the next step; otherwise, it is recommended that the IoT terminal 20 replace the allowed base station 40. Figure 7 This is a schematic flowchart of Embodiment 1 of the network access process for the IoT terminal 20 of this application. That is, step S70 is an embodiment of the communication method of the IoT card in the third embodiment of this application.

[0080] The following describes step S80 using... Figure 8 Please provide a detailed explanation. Figure 8 This is a flowchart illustrating Embodiment 1 of the communication method of the IoT card according to the third embodiment of this application. Figure 8 As shown, Embodiment 1 of the communication method includes steps S810 to S830.

[0081] In this embodiment 1, it is assumed that the network standard management policy information already stores prohibited or permitted base station codes (base station IDs) through the second implementation method of this application or by directly writing them into the initial IoT card. For example, the network standard management policy information stores a restricted base station ID list, which is a list of prohibited base station IDs. In other words, at this time, the network standard management policy information can be: the restriction type is a blacklist, the service type is a base station, and the restricted service content is a restricted base station ID list.

[0082] The third embodiment of the communication method of the IoT card, in Example 1, can also be implemented as a communication device of the IoT card. Figure 9 This is a schematic diagram showing the structure of a communication device for an IoT card corresponding to Embodiment 1. For example... Figure 9 As shown, the communication device of the IoT card includes: an acquisition module 910, a comparison module 920, and a response module 930.

[0083] In step S810, the acquisition module 910 obtains the currently pre-connected base station ID from the IoT terminal 20, triggered by the operation of the IoT terminal 20 reading the IMSI in step S603.

[0084] In step S820, the comparison module 920 compares the pre-connected base station ID with the list of restricted base station IDs in the network standard management policy information set in the IoT SIM card. In other words, the comparison module 920 determines whether the pre-connected base station ID is in the list of restricted base station IDs in the network standard management policy information set in the IoT SIM card.

[0085] If the pre-connected base station ID is in the restricted base station ID list, it is recommended that IoT terminal 20 select another base station. Alternatively, a connection error event response can be sent to IoT terminal 20. In this case, after IoT terminal 20 selects base station 40 again, it returns to step S810.

[0086] If the pre-connected base station ID is not in the restricted base station ID list, proceed directly to the next step.

[0087] In step S830, the response module 930 returns the IMSI to the IoT terminal 20.

[0088] After step S830, the IoT terminal 20 that receives the IMSI can proceed with the subsequent step S604 with the selected base station 40.

[0089] In Example 1, when a list of restricted base station IDs is stored in the network standard management policy information, the pre-connected base station ID is obtained by using the operation of the IoT terminal reading the IMSI as a trigger event and comparing it with the list of restricted base station IDs. This allows the IoT terminal to switch base stations at an appropriate time, ensuring good compatibility with existing Internet access procedures and timely avoiding connection anomalies, thereby improving the efficiency and reliability of IoT terminal Internet access.

[0090] In the third embodiment of this application, as another example of restricting network connections corresponding to restriction conditions based on the network standard management policy information, when the restriction conditions include prohibiting or allowing the use of network standards, such as... Figure 10 As shown, it is possible to Figure 6 Add step S100 between steps S609 and S610.

[0091] In step S100, a network authentication comparison success event between IoT terminal 20 and base station 40 is triggered, and network standard management policy information is sent to IoT terminal 20 so that IoT terminal 20 can consider the network standards allowed by the network standard management policy information and avoid these network standards in the negotiation with the base station. Figure 10 This is a schematic flowchart of Embodiment 2 of the network access process of the IoT terminal 20 of this application. That is, step S100 is another embodiment of the communication method of the IoT card in the third embodiment of this application.

[0092] The following describes step S100 using... Figure 11 Please provide a detailed explanation. Figure 11 This is a flowchart illustrating Embodiment 2 of the communication method of the IoT card according to the third embodiment of this application. Figure 11 As shown, Embodiment 2 of the communication method includes steps S111 to S112.

[0093] In this second embodiment, it is assumed that the network standards for which use is prohibited or permitted have been stored in the network standard management policy information through the second implementation method of this application or by directly writing it into the initial IoT card. That is, the restriction conditions include the network standards for which use is prohibited or permitted. For example, the network standard management policy information may be: the restriction type is a blacklist, the service type is a network standard, and the restricted service content is 2G-GSM network.

[0094] Embodiment 2 of the communication method of the IoT card in the third embodiment can also be implemented as a communication device of the IoT card. Figure 12 This is a schematic diagram showing the structure of the communication device for the IoT card corresponding to Embodiment 2. For example... Figure 12 As shown, the communication device of the IoT card includes: a capture module 1210 and a transmission module 1220.

[0095] In step S111, the capture module 1210 captures the successful network authentication comparison event between the IoT terminal 20 and the base station 40.

[0096] like Figure 10 As shown, in step S609, if SRES = SRES' and SRES and SRES' are equal, then the identity authentication of IoT terminal 20 is successful, that is, the network authentication comparison is successful. In step S1110, the capture module 1210 captures the successful network authentication comparison event.

[0097] In step S112, the sending module 1220 sends the network standard management policy information set in the IoT card to the IoT terminal 20 based on the successful network authentication comparison event. This enables the IoT terminal 20 to combine the network standard management policy information with the network standards it supports to determine the network standards it ultimately supports, and then sends the ultimately supported network standards to the base station 40.

[0098] In Example 2, a successful network authentication comparison event between the IoT terminal and the base station is captured by the IoT SIM card. This event triggers the sending of network standard management policy information to the IoT terminal. As a result, the IoT terminal uses the network standard management policy information stored in the IoT SIM card as part of its network capabilities. Considering the network standard negotiation between the IoT terminal and the base station (network system), this avoids selecting a restricted network standard during the negotiation. It has good compatibility with existing Internet access procedures, can promptly prevent network anomalies, and improves the efficiency and reliability of Internet access for IoT terminals.

[0099] Although two embodiments, Embodiment 1 and Embodiment 2, have been described above, they can be used in combination. In this case, the network standard management strategy information includes both the base station and the network standard, thereby further improving the efficiency and reliability of IoT terminals accessing the internet from both the base station and network standard perspectives. At this time, the corresponding communication method is... Figure 6 Based on this, it can simultaneously include steps S80 and S100; the corresponding communication device can simultaneously include... Figure 9 and Figure 12 The structure.

[0100] This third implementation method assumes that network standard management policy information has been written into the IoT card. Therefore, it can also be combined with the second implementation method. That is, the network standard management policy information is written into the IoT card based on the communication method of the second implementation method, and then the network connection is restricted accordingly based on the communication method of the third implementation method and the network standard management policy information. In other words, the combined communication method can execute... Figure 3 After processing, execute. Figure 7 and / or Figure 10 The processing. At this time, the corresponding communication device may include... Figure 4 and Figure 9 structure, or Figure 4 and Figure 12 structure, or Figure 4 , Figure 9 , Figure 12 The entire structure.

[0101] In the third embodiment, two implementations are provided to restrict network connections based on network standard management policy information. This enables timely restriction of network connections in accordance with network standard management policy information that specifies prohibited or permitted base stations and / or network standards, thereby preventing network anomalies and improving the efficiency and reliability of Internet of Things (IoT) terminals accessing the Internet.

[0102] Fourth Implementation Method The fourth embodiment of this application provides a communication method for an Internet of Things (IoT) terminal 20. This communication method for the IoT terminal 20 includes processing on the IoT terminal 20 side corresponding to the processing of the IoT card 10 in Embodiment 2 of the third embodiment.

[0103] Figure 13 This is a flowchart illustrating an example of a communication method for an IoT terminal 20 according to the fourth embodiment. For example... Figure 13 As shown, the communication method includes steps S131 to S134.

[0104] Figure 14 This is a schematic diagram of the communication device of the Internet of Things terminal 20 corresponding to the fourth embodiment. For example... Figure 14 As shown, the communication device includes: a receiving module 1410, a determining module 1420, a sending module 1430, and a negotiation module 1440.

[0105] In step S131, the receiving module 1410 of the IoT terminal 20 receives network standard management policy information sent by the IoT card in response to the successful network authentication comparison event between the IoT terminal 20 and the base station 40. This network standard management policy information is set in the IoT card and specifies the network standards that are prohibited or allowed to be used.

[0106] In step S132, the determination module 1420 of the IoT terminal 20 combines the network standard management strategy information and the network standards it supports to determine the network standards that the IoT terminal 20 ultimately supports.

[0107] In step S133, the transmitting module 1430 of the IoT terminal 20 transmits the final supported network standard to the base station 40.

[0108] In step S134, the negotiation module 1440 of the IoT terminal 20 negotiates network standard information with the base station 40 based on the ultimately supported network standard, and establishes a network connection based on network standard management strategy information.

[0109] The following, as an example, describes the processing of the IoT card in Embodiment 2 of the third embodiment and... Figure 13 The processing of the IoT terminal 20 shown will be explained.

[0110] If we assume that the IoT terminal 20 itself supports 2G-GSM, 4G-TD-LTE, and 4G-FDD-LTE network standards, but due to the 2G migration, some 2G devices in remote areas where the terminal is located are no longer functioning properly, resulting in intermittent network quality, then the IoT SIM card connection management platform 30 writes the aforementioned network standard management policy information prohibiting the 2G-GSM network standard to the IoT SIM card via over-the-air SIM card writing. At this time, the IoT SIM card sends the network standard management policy information to the IoT terminal 20, triggered by a successful network authentication comparison event. The IoT terminal 20 receives this network standard management policy information and, combining it with its supported network standards, in step S610, informs the base station 40 that the IoT terminal 20 supports 4G-TD-LTE and 4G-FDD-LTE, thereby establishing a network connection with the base station 40 using either the 4G-TD-LTE or 4G-FDD-LTE network standard. In other words, the final network standard negotiated between the IoT terminal 20 and the base station 40 will not include 2G-GSM, thereby avoiding network anomalies caused by the IoT terminal 20 attaching to the 2G network.

[0111] In the fourth embodiment, the IoT terminal 20 negotiates the network standard with the base station 40 by considering the network standard management policy information in the IoT card that specifies the network standards that are prohibited or permitted. Therefore, it can restrict network connections in a timely manner, prevent network anomalies, and improve the efficiency and reliability of IoT terminal accessing the Internet.

[0112] Fifth Implementation Method The fifth embodiment of this application provides a communication method for an IoT SIM card connection management platform, namely a communication method executed by the IoT SIM card connection management platform 30. Figure 15 This is a flowchart illustrating the communication method of the IoT SIM card connection management platform according to the fifth embodiment. Figure 15 As shown, the communication method includes steps S151 to S154.

[0113] Figure 16This is a schematic diagram showing the structure of a communication device for an IoT card connection management platform corresponding to the fifth embodiment. (Example) Figure 16 As shown, the communication method includes: a receiving module 1610, a configuration module 1620, a sending module 1630, and a reconnection module 1640.

[0114] In step S151, the receiving module 1610 of the IoT card connection management platform 30 receives network connection abnormality information from the user; When the IoT SIM card connection management platform 30 receives a complaint or feedback from user 50 regarding abnormal internet access, the IoT SIM card connection management platform 30 receives the abnormal internet access information.

[0115] In step S152, the configuration module 1620 of the IoT SIM card connection management platform 30 configures network standard management policy information for IoT SIM cards that have experienced network connection abnormalities.

[0116] Administrators or users of the IoT SIM card connection management platform 30 can select the target IoT SIM card number and configure the network standard restriction policy on the IoT SIM card through the IoT SIM card connection management platform 30 page.

[0117] Figure 17(a) is a schematic diagram showing an example of network policy configuration operation on the IoT SIM card connection management platform 30; Figure 17(b) is a schematic diagram showing an example of network policy viewing operation on the IoT SIM card connection management platform 30. The following will use the examples shown in Figures 17(a) and (b) to explain the process of configuring network standard management policy information.

[0118] As shown in Figure 17(a), the network standard management policy information includes two service types: network standard and base station. Blacklists or whitelists, along with specific restrictions, are stored for each service type. For example, for an IoT card with card number 14400001111, a blacklist is stored for the network standard, restricting it to 2G-GSM. A blacklist is also stored for the base station, with base station ID 460AAAB6.

[0119] In the example of Figure 17(a), clicking the "Details" button in "Current Policy" allows you to view the network policy, which opens the page shown in Figure 17(b), where you can further view the details of the network policy management information.

[0120] In step S153, the distribution module 1630 of the IoT card connection management platform 30 distributes network standard management policy information to the IoT card through the over-the-air card writing function.

[0121] In the example of Figure 17(a), after configuring the network policy and verifying that it is correct, when the "Issue Command" button in "Status" is clicked, the IoT card connection management platform 30 can send an over-the-air writing command to the IoT card 10 through the over-the-air writing function, and send the network standard management policy information to the network standard management file of the target IoT card.

[0122] In step S154, after the IoT card connection management platform 30’s reconnection module 1640 receives the report result that the network standard management policy information has been successfully written to the IoT card, the IoT terminal reconnects to the network.

[0123] The IoT card responds to the over-the-air write command and determines whether a network standard management file exists in the main security domain of the IoT card. If no network standard management file exists, a blank network standard management file is added. The IoT card receives the network standard management information and writes it into the newly added or existing network standard management file in the card. After the writing is completed, it responds with a write success result, that is, it reports the result to the IoT card connection management platform 30.

[0124] After receiving the successful write report, the IoT SIM card connection management platform 30 enables the IoT terminal to reconnect to the network, i.e., resets the IoT terminal's network connection. For example, the IoT SIM card connection management platform 30 can issue a command to the IoT terminal to disconnect from the network side, triggering the IoT terminal 20 to reattach to the network. This triggers the IoT SIM card network restriction management policy to take effect immediately, switching the IoT SIM card with internet access failure to the network selected based on the network standard management policy information, thereby restoring normal internet access.

[0125] Figure 18 This is a flowchart illustrating the process by which an IoT terminal reconnects to the network based on instructions from an IoT SIM card connection management platform. Figure 18 In the example, assume that the network restriction management policy information specifies the network types that are prohibited.

[0126] like Figure 18 As shown, after receiving the update completion report from IoT SIM card 10, IoT SIM card connection management platform 30 sends an instruction to base station 40 to disconnect the network connection of IoT terminal 20 in step S1801.

[0127] In step S1802, base station 40 causes IoT terminal 20 to go offline, thereby disconnecting the network connection between IoT terminal 20 and base station 40.

[0128] In step S1803, IoT terminal 20 searches for base stations again.

[0129] In step S1804, IoT terminal 20 performs SRES comparison.

[0130] In step S1805, the IoT card 10 receives the confirmation that the IoT terminal 20 has completed the SRES comparison, that is, it captures the successful network authentication comparison between the IoT terminal 20 and the base station 40.

[0131] In step S1806, IoT SIM card 10 sends network restriction management policy information to IoT terminal 20.

[0132] In step S1807, when IoT terminal 20 and base station 40 negotiate network standards, the network restriction management policy information is taken into account during the negotiation.

[0133] In step S1808, the negotiation between IoT terminal 20 and base station 40 is completed, and IoT terminal 20 resumes internet access.

[0134] The processing details of steps S1805 to S1808 described above can also be found in the processing of IoT card 10 in Embodiment 2 of the third embodiment and the processing of IoT terminal 20 in the fourth embodiment.

[0135] In the fifth embodiment, by using the IoT card connection management platform 30 to configure network standard management policy information and sending it to the IoT card via the over-the-air card writing function, the network standard management policy information in the IoT card can be remotely set and updated. Based on the network standard management policy information, the network connection can be reset. This not only avoids network connection abnormalities but also enhances the function of the IoT card. It standardizes network standard management from the perspective of the IoT card, thus avoiding changes to the structure of the IoT terminal and preventing an increase in the cost of the IoT terminal.

[0136] Sixth Implementation Method Figure 19 This is a schematic diagram illustrating the hardware structure of the communication device provided in the sixth embodiment of this application.

[0137] The communication device may include a processor 1901 and a memory 1902 storing computer program instructions.

[0138] Specifically, the processor 1901 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0139] Memory 1902 may include mass storage for data or instructions. For example, and not limitingly, memory 1902 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. In one instance, memory 1902 may include removable or non-removable (or fixed) media, or memory 1902 may be non-volatile solid-state memory. Memory 1902 may be internal or external to the integrated gateway disaster recovery device.

[0140] In one instance, memory 1902 may be read-only memory (ROM). In one instance, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.

[0141] Memory 1902 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Thus, generally, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this disclosure.

[0142] The processor 1901 implements the communication methods in the first to fifth embodiments by reading and executing computer program instructions stored in the memory 1902.

[0143] In examples implementing the communication methods of the first to fifth embodiments, the communication device may further include a communication interface 1903 and a bus 1904. Wherein, as Figure 11 As shown, the processor 1901, memory 1902, and communication interface 1903 are connected via bus 1904 and communicate with each other.

[0144] The communication interface 1903 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0145] Bus 1904 includes hardware, software, or both, that couples components of an online data flow metering device together. For example, and not as a limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 1904 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, this application contemplates any suitable bus or interconnect.

[0146] Alternatively, in conjunction with the communication methods described in the above embodiments, this application may also provide a computer storage medium. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the communication methods described in the above embodiments.

[0147] The embodiments of this application also provide a computer program product, including a computer program, which, when processed and executed, implements any of the communication methods described in the above embodiments.

[0148] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0149] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (ROM), flash memory, erasable read-only memory (EROM), floppy disks, compact disc read-only memory (CD-ROM), optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0150] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0151] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0152] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A communication method for an IoT card, characterized in that, include: Receive over-the-air card writing instructions from the IoT SIM card connection management platform; In response to the over-the-air write command, determine whether a network standard management file exists in the main security domain of the IoT card. If no network standard management file exists, add a blank network standard management file. as well as Network standard management policy information is written into the network standard management file, which specifies the network conditions that are prohibited or permitted.

2. The communication method according to claim 1, characterized in that, Also includes: The network connection between the IoT SIM card terminal and the base station is restricted based on the network standard management policy information. The network conditions include at least one of the following: base station ID, network standard, and the MME, AMF, MSC, and SGSN codes of the core network elements.

3. The communication method according to claim 2, characterized in that, The network standard management policy information specifies a restricted base station ID list, which is a list of base station IDs that are prohibited from use. Restricting network connections between IoT SIM card terminals and base stations based on the network standard management policy information includes: The operation of reading the IMSI by the IoT terminal is used as a trigger event to obtain the currently pre-connected base station ID from the IoT terminal; and The pre-connected base station ID is compared with the list of restricted base station IDs in the network standard management policy information set in the IoT card. If the pre-connected base station ID is in the list of restricted base station IDs, the IoT terminal is advised to select another base station. If the pre-connected base station ID is not in the list of restricted base station IDs, the IMSI is returned directly to the IoT terminal.

4. The communication method according to claim 2, characterized in that, When the network conditions include network standard. Restricting network connections between IoT SIM card terminals and base stations based on the network standard management policy information includes: Capture successful network authentication comparison events between IoT terminals and base stations; Triggered by the successful network authentication comparison event, the network standard management policy information set in the IoT card is sent to the IoT terminal, so that the IoT terminal can combine the network standard management policy information and the network standards it supports to determine the network standards it ultimately supports, and send the ultimately supported network standards to the base station.

5. A communication method for an IoT card, characterized in that, include: Capture successful network authentication comparison events between IoT terminals and base stations; Triggered by the successful network authentication comparison event, the network standard management policy information set in the IoT card is sent to the IoT terminal. The network standard management policy information specifies the network standards that are prohibited or allowed to be used, so that the IoT terminal can combine the network standard management policy information with the network standards it supports to determine the network standards that the IoT terminal ultimately supports, and send the ultimately supported network standards to the base station.

6. A communication method executed by an Internet of Things (IoT) terminal, characterized in that, include: The IoT card receives network standard management policy information in response to a successful network authentication comparison event between the IoT terminal and the base station. The network standard management policy information is set in the IoT card and specifies the network standards that are prohibited or allowed to be used. By combining the network standard management strategy information and the network standards it supports, the final network standard supported by the IoT terminal is determined. The final supported network standard is sent to the base station; as well as Based on the ultimately supported network standard, negotiate network standard information with the base station to establish a network connection based on the network standard management policy information.

7. A communication method for connecting an IoT SIM card to a management platform, characterized in that, include: Receive network error information from users; Configure network standard management policy information for IoT cards that experience network connection abnormalities. The network standard management policy information is sent to the IoT card through the over-the-air card writing function. The network standard management policy information specifies the network conditions that are prohibited or allowed to be used. as well as After receiving the report result that the network standard management policy information has been successfully written to the IoT card, the IoT terminal reconnects to the network.

8. A communication method for a communication system, characterized in that, The communication system includes: an IoT SIM card, an IoT SIM card connection management platform, and an IoT terminal. The communication method includes: The IoT SIM card connection management platform receives network anomaly information from users, configures network standard management policy information for IoT SIM cards experiencing network anomalies, and sends the network standard management policy information to the IoT SIM card through the over-the-air card writing function. The network standard management policy information specifies the network conditions that are prohibited or permitted to be used. The IoT card receives an over-the-air write command from the IoT card connection management platform. In response to the over-the-air write command, it determines whether a network standard management file exists in the main security domain of the IoT card. If no network standard management file exists, a blank network standard management file is added, and network standard management policy information is written into the network standard management file. After the IoT SIM card connection management platform receives the report result that the network standard management policy information has been successfully written to the IoT SIM card, it enables the IoT terminal to reconnect to the network. When the network conditions include a base station ID, the IoT SIM card uses the IoT terminal's operation of reading the IMSI as a trigger event to obtain the currently pre-connected base station ID from the IoT terminal. The pre-connected base station ID is compared with the restricted base station ID list in the network standard management policy information set in the IoT SIM card. If the pre-connected base station ID is in the restricted base station ID list, the IoT terminal is advised to reselect another base station. If the pre-connected base station ID is not in the restricted base station ID list, the IMSI is responded to normally. When the network conditions include network standard, the IoT SIM card captures a successful network authentication comparison event between the IoT terminal and the base station. Using this successful network authentication comparison event as a trigger, the IoT SIM card sends the network standard management policy information stored in it to the IoT terminal. The IoT terminal combines the network standard management policy information with its own supported network standards to determine the network standard it ultimately supports, and sends the ultimately supported network standard to the base station. The IoT terminal and the base station negotiate network standard information based on the ultimately supported network standard to establish a network connection based on the network standard management policy information.

9. The communication method according to any one of claims 1 to 8, characterized in that, The structure of the network standard management policy information includes: restriction type marker, service type marker, and restriction content. The restriction type flag indicates whether it is a blacklist or a whitelist; The service type flag indicates the type of network conditions that are restricted; The restrictions mentioned refer to the specific restrictions imposed on each network condition.

10. A communication device for an IoT card, characterized in that, include: The receiving module receives over-the-air card writing commands from the IoT card connection management platform; The file addition module, in response to the over-the-air write command, determines whether a network standard management file exists in the main security domain of the IoT card. If no network standard management file exists, a blank network standard management file is added. as well as The writing module writes network standard management policy information into the network standard management file, which specifies the network conditions that are prohibited or permitted.

11. The communication device for an IoT card according to claim 10, characterized in that, Also includes: The acquisition module uses the operation of the IoT terminal reading the IMSI as a trigger event to obtain the currently pre-connected base station ID from the IoT terminal; The comparison module compares the pre-connected base station ID with the list of restricted base station IDs in the network standard management policy information set in the IoT card; as well as The response module suggests that if the pre-connected base station ID is in the restricted base station ID list, the IoT terminal should reselect another base station; if the pre-connected base station ID is not in the restricted base station ID list, the IMSI should be responded to normally.

12. A communication device for an Internet of Things (IoT) card, characterized in that, include: The capture module captures successful network authentication comparison events between IoT terminals and base stations. as well as The sending module, triggered by the successful network authentication comparison event, sends the network standard management policy information set in the IoT card to the IoT terminal. The network standard management policy information specifies the network standards that are prohibited or allowed to be used, so that the IoT terminal can combine the network standard management policy information with its own supported network standards to determine the network standards that the IoT terminal ultimately supports, and send the ultimately supported network standards to the base station.

13. A communication device for an Internet of Things (IoT) terminal, characterized in that, include: The receiving module receives network standard management policy information sent by the IoT card in response to a successful network authentication comparison event between the IoT terminal and the base station. The network standard management policy information is set in the IoT card and specifies the network standards that are prohibited or allowed to be used. The determination module, combining the network standard management strategy information and the network standards it supports, determines the final network standard supported by the IoT terminal; The transmitting module sends the final supported network standard to the base station; as well as The negotiation module negotiates network standard information with the base station based on the ultimately supported network standard, and establishes a network connection based on the network standard management policy information.

14. A communication device for connecting an IoT SIM card to a management platform, characterized in that, include: The receiving module receives network error information from the user; The configuration module configures network standard management policy information for IoT cards that experience network connectivity issues. The distribution module distributes network standard management policy information to the IoT card via the over-the-air card writing function; as well as After the reconnection module receives the report result that the network standard management policy information has been successfully written to the IoT card, it enables the IoT terminal to reconnect to the network.

15. A communication system for an Internet of Things (IoT) card, characterized in that, include: An IoT SIM card, including a communication device for an IoT SIM card as described in any one of claims 10-12; The Internet of Things (IoT) terminal includes the communication device of the IoT terminal as described in claim 13; as well as An IoT SIM card connection management platform, including the communication device of the IoT SIM card connection management platform as described in claim 14. The IoT SIM card writes the network standard management policy information issued by the IoT SIM card connection management platform through the over-the-air card writing function into the network standard management file in the main security domain.

16. A communication device, characterized in that, The device includes: a processor and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the communication method as described in any one of claims 1-9.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the communication method as described in any one of claims 1-9.

18. A computer program product, characterized in that, Includes a computer program, which, when executed, implements the communication method as described in any one of claims 1-9.

Images